IPP Mail Archive: IPP> ADM - IETF IPP WG Last Call for IPP:

IPP> ADM - IETF IPP WG Last Call for IPP: The INDP Notification Delive ry Method and Protocol/1.0 <draft-ietf-ipp-indp-method-02.txt>

From: Manros, Carl-Uno B (cmanros@cp10.es.xerox.com)
Date: Tue Jul 25 2000 - 12:26:58 EDT

  • Next message: Manros, Carl-Uno B: "IPP> ADM - Job and Printer Set Operations and The 'collection' attribu te syntax"

    All,

    This is a working group Last Call for the following IPP
    Notification document:

      IPP: The INDP Notification Delivery Method and Protocol/1.0
      <draft-ietf-ipp-indp-method-02.txt>

    The latest version of this document has been forwarded to
    the Internet Draft directory.

    In my message yesterday I stated that the 'indp:' draft didn't make
    the cut-off for IETF 48. I was wrong, it showed up today, so I am
    now adding this document to the 4 documents from yesterday.
    They now all have the same closing date for comments.
    -----

    The Last Call notice follows:

            This is a formal request for final comments within the IETF IPP
    working group for one document. The document is:

    "Internet Printing Protocol (IPP): The INDP Notification Delivery Method
        and Protocol/1.0

    which is being proposed for forwarding on to the IESG for consideration as
    Standards Track document to complement the previous suite of IPP/1.0 and
    IPP/1.1 documents. This is a working group product, which has been
    thoroughly discussed since early 1999.

    Note that the "The INDP Notification Delivery Method" document is only
    one of several possible notification delivery documents on which the WG has
    been working. Expect to see further such documents for IPP WG Last Call.

    The purpose of a working group Last Call is in the style of "speak now or
    forever hold your peace" in case there are fundamental objections which have
    not gotten previous or adequate discussion, or minor errors which need
    correction.

    Last Calls are for a minimum of 2 weeks. We will start the Last Call period
    today Tuesday 25 July, 2000 and the period for working group comments
    will close on Wednesday 9 August, 2000 (US Pacific time reference) to span
    the upcoming IETF 48 meeting.

    The relevant documents are:

            Title : Internet Printing Protocol (IPP): The INDP
    Notification
                              Delivery Method and Protocol/1.0
            Author(s) : H. Parra, T. Hastings
            Filename : draft-ietf-ipp-indp-method-02.txt
            Pages : 22
            Date : 24-Jul-00
            
    The IPP notification extension document [ipp-ntfy] defines operations
    that a client can perform in order to create Subscription Objects in a
    Printer and carry out other operations on them. The Subscription Object
    specifies that when one of the specified Events occurs, the Printer
    sends an asynchronous Event Notification to the specified Notification
    Recipient via the specified Delivery Method (i.e., protocol).

    A URL for this Internet-Draft is:
    http://www.ietf.org/internet-drafts/draft-ietf-ipp-indp-method-02.txt

    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-indp-method-02.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-indp-method-02.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.

    ---
    

    Sincerely,

    Carl-Uno Manros Chair of IETF IPP WG

    Principal Engineer - Xerox Architecture Center - Xerox Corporation 701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231 Phone +1-310-333 8273, Fax +1-310-333 5514 Email: manros@cp10.es.xerox.com



    This archive was generated by hypermail 2b29 : Tue Jul 25 2000 - 12:36:03 EDT