A second IETF last call for RFC2911bis to address some of the normative references we have to informative documents...
Sent from my iPhone
Begin forwarded message:
> Resent-From: alias-bounces at ietf.org> From: The IESG <iesg-secretary at ietf.org>
> Date: August 9, 2016 at 10:40:53 AM EDT
> Resent-To: msweet at apple.com, blueroofmusic at gmail.com> To: IETF-Announce <ietf-announce at ietf.org>
> Cc: alexey.melnikov at isode.com, Barry Leiba <barryleiba at computer.org>, barryleiba at computer.org, draft-sweet-rfc2911bis at ietf.org> Subject: Last Call: <draft-sweet-rfc2911bis-10.txt> (Internet Printing Protocol/1.1: Model and Semantics) to Proposed Standard
> Reply-To: ietf at ietf.org>>> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Internet Printing Protocol/1.1: Model and Semantics'
> <draft-sweet-rfc2911bis-10.txt> as Proposed Standard
>> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
>ietf at ietf.org mailing lists by 2016-09-06. Exceptionally, comments may be
> sent to iesg at ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>> This is the Second IETF LC to explicitly call out DownRefs (see below).
>> Abstract
>> The Internet Printing Protocol (IPP) is an application level protocol
> for distributed printing using Internet tools and technologies. This
> document describes a simplified model consisting of abstract objects,
> attributes, and operations that is independent of encoding and
> transport. The model consists of several objects including Printers
> and Jobs. Jobs optionally support multiple Documents.
>> IPP semantics allow End Users and Operators to query Printer
> capabilities, submit print Jobs, inquire about the status of print
> Jobs and Printers, and cancel, hold, and release print Jobs. IPP
> semantics also allow Operators to pause and resume Jobs and Printers.
>> Security, internationalization, and directory issues are also
> addressed by the model and semantics. The IPP message encoding and
> transport are described in IPP/1.1: Encoding and Transport
> [RFC2910bis].
>> This document obsoletes RFCs 2911, 3381, and 3382.
>> The file can be obtained via
>https://datatracker.ietf.org/doc/draft-sweet-rfc2911bis/>> IESG discussion can be tracked via
>https://datatracker.ietf.org/doc/draft-sweet-rfc2911bis/ballot/>>> No IPR declarations have been submitted directly on this I-D.
>> The document contains these normative downward references.
> See RFC 3967 for additional information:
> rfc2818: HTTP Over TLS (Informational - IETF stream)
> rfc1977: PPP BSD Compression Protocol (Informational - IETF stream)
> rfc1952: GZIP file format specification version 4.3 (Informational - Legacy stream)
> rfc1951: DEFLATE Compressed Data Format Specification version 1.3 (Informational - Legacy stream)
> rfc3196: Internet Printing Protocol/1.1: Implementor's Guide (Informational)
> rfc7612: Lightweight Directory Access Protocol (LDAP): Schema for Printer Services (Informational)
> rfc2565: Internet Printing Protocol/1.0: Encoding and Transport (Experimental)
> rfc2566: Internet Printing Protocol/1.0: Model and Semantics (Experimental)
>> Note that some of these references may already be listed in the acceptable Downref Registry.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20160809/a6502050/attachment.html>