IPP Mail Archive: RE: IPP> I-D ACTION:draft-ietf-ipp-notify-

IPP Mail Archive: RE: IPP> I-D ACTION:draft-ietf-ipp-notify-

RE: IPP> I-D ACTION:draft-ietf-ipp-notify-get-08.txt [The 'ippget ' Delivery Method for Event Notifications]

From: Hastings, Tom N (hastings@cp10.es.xerox.com)
Date: Thu Oct 17 2002 - 17:49:08 EDT

  • Next message: Dennis Carney: "IPP> ACT - IPP "-actual" attributes downloaded, version 0.1"

    I've down loaded the corresponding .pdf, .doc, and .txt versions to the PWG
    FTP site:

    ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get-021010.pdf
    ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get-021010.doc

    ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get-021010-rev.pdf
    ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get-021010-rev.doc

    ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get-021010.txt
    ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-notify-get-08.txt

    Both the IPP Event Notifications and Subscriptions spec and this IPPGET
    Delivery Method spec passed IPP WG Last Call this summer with the agreement
    to remove the redirect from the IETF Document. This draft has the redirect
    removed and meets all of the RFC Editor's requirements for RFCs and the IANA
    Registry information as well.

    As stated in both documents, the IPPGET Delivery Method is the REQUIRED
    Delivery Method. Other Delivery Methods are OPTIONAL.

    Carl-Uno will be asking the AD to process these two notification specs
    through the IESG as standards track documents.

    Tom

    -----Original Message-----
    From: Carl [mailto:carl@manros.com]
    Sent: Wednesday, October 16, 2002 08:53
    To: ipp@pwg.org
    Subject: IPP> I-D ACTION:draft-ietf-ipp-notify-get-08.txt

    To: IETF-Announce: ;
    Cc: ipp@pwg.org
    From: Internet-Drafts@ietf.org
    Reply-to: Internet-Drafts@ietf.org
    Subject: I-D ACTION:draft-ietf-ipp-notify-get-08.txt
    Date: Wed, 16 Oct 2002 07:24:36 -0400
    Sender: nsyracus@cnri.reston.va.us

    --NextPart

    A New Internet-Draft is available from the on-line Internet-Drafts
    directories.
    This draft is a work item of the Internet Printing Protocol Working Group of
    the IETF.

            Title : Internet Printing Protocol (IPP): The 'ippget'
                              Delivery Method for Event Notifications
            Author(s) : R. Herriot, T. Hastings, H. Lewis
            Filename : draft-ietf-ipp-notify-get-08.txt
            Pages : 35
            Date : 2002-10-15

    This document describes an extension to the Internet Printing
    Protocol/1.1: Model and Semantics (RFC 2911, RFC 2910). This
    document specifies the 'ippget' Pull Delivery Method for use with the
    'Internet Printing Protocol (IPP): Event Notifications and
    Subscriptions' specification (ipp-ntfy). This IPPGET Delivery Method
    is REQUIRED for all clients and Printers that support ipp-ntfy. The
    Notification Recipient, acting as a client, fetches (pulls) Event
    Notifications using the Get-Notifications operation defined in this
    document.

    A URL for this Internet-Draft is:
    http://www.ietf.org/internet-drafts/draft-ietf-ipp-notify-get-08.txt

    To remove yourself from the IETF Announcement list, send a message to
    ietf-announce-request with the word unsubscribe in the body of the message.

    Internet-Drafts are also available by anonymous FTP. Login with the username
    "anonymous" and a password of your e-mail address. After logging in,
    type "cd internet-drafts" and then
            "get draft-ietf-ipp-notify-get-08.txt".

    A list of Internet-Drafts directories can be found in
    http://www.ietf.org/shadow.html
    or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

    Internet-Drafts can also be obtained by e-mail.

    Send a message to:
            mailserv@ietf.org.
    In the body type:
            "FILE /internet-drafts/draft-ietf-ipp-notify-get-08.txt".

    NOTE: The mail server at ietf.org can return the document in
            MIME-encoded form by using the "mpack" utility. To use this
            feature, insert the command "ENCODING mime" before the "FILE"
            command. To decode the response(s), you will need "munpack" or
            a MIME-compliant mail reader. Different MIME-compliant mail readers
            exhibit different behavior, especially when dealing with
            "multipart" MIME messages (i.e. documents which have been split
            up into multiple messages), so check your local documentation on
            how to manipulate these messages.

    Below is the data which will enable a MIME compliant mail reader
    implementation to automatically retrieve the ASCII version of the
    Internet-Draft.

    --NextPart
    Content-Type: Multipart/Alternative; Boundary="OtherAccess"

    --OtherAccess
    Content-Type: Message/External-body;
            access-type="mail-server";
            server="mailserv@ietf.org"

    Content-Type: text/plain
    Content-ID: <2002-10-15141540.I-D@ietf.org>

    ENCODING mime
    FILE /internet-drafts/draft-ietf-ipp-notify-get-08.txt

    --OtherAccess
    Content-Type: Message/External-body;
            name="draft-ietf-ipp-notify-get-08.txt";
            site="ftp.ietf.org";
            access-type="anon-ftp";
            directory="internet-drafts"

    Content-Type: text/plain
    Content-ID: <2002-10-15141540.I-D@ietf.org>

    --OtherAccess--

    --NextPart--



    This archive was generated by hypermail 2b29 : Thu Oct 17 2002 - 17:49:48 EDT