RE: Last Call: Internet Printing Protocol (IPP): Event Notifications and Subscriptions to Proposed Standard

["IANA" <iana@iana.org>]

See inline.

> -----Original Message-----
> From: ned.freed@mrochek.com [mailto:ned.freed@mrochek.com]
> Sent: Friday, January 31, 2003 2:58 PM
> To: IANA
> Cc: iesg@ietf.org; bob@herriot.com; hastings@cp10.es.xerox.com;
> harryl@us.ibm.com; carl@manros.com
> Subject: RE: Last Call: Internet Printing Protocol (IPP): Event
> Notifications and Subscriptions to Proposed Standard
> 
> 
> > IESG:
> 
> > The IANA has reviewed the following Internet-Drafts which
> > are in Last Call and has the following comments with
> > regards to the publication of these documents:
> 
> >  o "Internet Printing Protocol (IPP): Event Notifications and
> >    Subscriptions"
> >  	<draft-ietf-ipp-not-spec-10.txt>
> 
> > We would like to suggest in section 24.7.2.3, that there is
> > mention of the reviewer sending a message or contacting the
> > IANA when a request is ready for registration.  Adding this
> > will make it a bit more clear.
> 
> OK, how about:
> 
> 24.7.2.3 IANA Registration
> 
>    Provided that the Delivery Method registration proposal has either
>    passed review or has been successfully appealed to the IESG, the IANA
>    will be notified by the delivery method reviewer and asked to register
>    the Delivery Method and make it available to the community.
> 
> I can make this change with an RFC Editor note if there are no 
> other changes.

Seems OK to me.

> 
> > We understand a new sub-registry in the IPP Registry will
> > be created for "Events and Delivery Methods".  Are there any
> > defined registrations for this registry in this document?
> 
> Not in this document, however, the companion document 
> draft-ietf-ipp-notify-get-08.txt registers one. I expect this to 
> be the only
> registration made in the short term.

OK.

> 
> > We understand the following registrations will be made upon
> > approval of this document:
> 
> > 6 registrations in the "ENUM ATTRIBUTE VALUES" IPP registry
> > (the value will need to be confirmed with the IPP expert)
> 
> check.
> 
> > 28 registrations in the "ATTRIBUTES" IPP registry
> 
> check.
> 
> > 8 registrations in the "OPERATIONS" IPP registry
> 
> There are 9 by my count:
> 
> 1   Cancel-Subscription Operation                  RFC NNNN    11.2.7
> 2   Create-Job-Subscriptions Operation             RFC NNNN    11.1.1
> 3   Create-Printer-Subscriptions Operation         RFC NNNN    11.1.2
> 4   Get-Printer-Attributes - Extensions            RFC NNNN    11.2.3
> 5   Get-Subscription-Attributes Operation          RFC NNNN    11.2.4
> 6   Get-Subscriptions Operation                    RFC NNNN    11.2.5
> 7   Job Creation Operations - Extensions           RFC NNNN    11.1.3
> 8   Renew-Subscription Operation                   RFC NNNN    11.2.6
> 9   Validate-Job Operation - Extensions            RFC NNNN    11.2.2

Ack. (my counting was off)

> 
> > 4 registration in the "STATUS CODES" IPP registry
> > (the values will need to be confirmed with the IPP expert)
> 
> I only see 2. I think you are misreading table subheadings as entries.

Ack and understand.

> 
> > 2 registrations in the "ATTRIBUTE GROUP TAGS" IPP registry
> > (the values will need to be confirmed with the IPP expert)
> 
> check.
> 
> >  o "Internet Printing Protocol (IPP): The 'ippget' Delivery Method for
> >    Event Notifications"
> >  	<draft-ietf-ipp-notify-get-08.txt>
> 
> > We understand the following registrations will be made upon
> > approval of this document:
> 
> > 3 registrations in the "KEYWORD ATTRIBUTE VALUES" IPP registry
> 
> I don't think this is correct. It looks to me like the boilerplate from
> not-spec is still present. Authors, can you clarify?

Clarification would be great.  I thought I saw this in section 15.2

> 
> > 1 registration in the "ENUM ATTRIBUTE VALUES" IPP registry
> > (the value will need to be confirmed with the IPP expert)
> 
> check.
> 
> > 1 registration in the "ATTRIBUTES" IPP registry
> 
> check.
> 
> > 1 registration in the "OPERATIONS" IPP registry
> 
> check.
> 
> > 1 registration in the "STATUS CODES" IPP registry
> 
> check.
> 
> Authors, shouldn't this document also make an entry in the new "Events
> and delivery methods" registry?
> 
> 				Ned
> 

Checking on this would be great too!

Thanks,

Michelle