RE: Last Call: Security Ticket Control Sub-option for the CableLabs Client Configuration Option to Proposed Standard

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

Nope.  Just as long as that change is in the final version.

:) Thanks,

Michelle

-----Original Message-----
From: Paul Duffy [mailto:paduffy@cisco.com]
Sent: Monday, May 12, 2003 3:55 PM
To: IANA
Cc: iesg@ietf.org; rdroms@cisco.com
Subject: RE: Last Call: Security Ticket Control Sub-option for the
CableLabs Client Configuration Option to Proposed Standard


At 03:43 PM 5/12/2003 -0700, IANA wrote:
>Can you include this in the I-D
>in the IANA Considerations section?
>
>That would be very helpful.

Yes, I could.  But I am holding off on another draft for a few other
changes the AD requested.  Do you need this now?

Cheers,



>Thank you,
>
>Michelle
>IANA
>
>
>-----Original Message-----
>From: Paul Duffy [mailto:paduffy@cisco.com]
>Sent: Monday, May 12, 2003 2:14 PM
>To: IANA
>Cc: iesg@ietf.org; rdroms@cisco.com
>Subject: RE: Last Call: Security Ticket Control Sub-option for the
>CableLabs Client Configuration Option to Proposed Standard
>
>
>OK...now I understand...please see inline...
>
>At 12:54 PM 5/12/2003 -0700, IANA wrote:
> >Hi Paul,
> >
> >Thanks for your message.  My Last Call comment may not have
> >been clear.
> >
> >I meant that the "name" of the sub-option did not appear to
> >be listed in the IANA Considerations section.  For example,
> >if 9 is the available code at the time of assignment the
> >registry would look like the following:
> >
> >DHCP Cablelabs Client Configuration Option Type 122 Sub-Option Codes per
> >[RFC3495]
> >
> >Code    Sub-Option Description                   Reference
> >-----   -----------------------                  ---------
> >     1   TSP's Primary DHCP Server Address        [RFC3495]
> >     2   TSP's Secondary DHCP Server Address      [RFC3495]
> >     3   TSP's Provisioning Server Address        [RFC3495]
> >     4   TSP's AS-REQ/AS-REP Backoff and Retry    [RFC3495]
> >     5   TSP's AP-REQ/AP-REP Backoff and Retry    [RFC3495]
> >     6   TSP's Kerberos Realm Name                [RFC3495]
> >     7   TSP's Ticket Granting Server Utilization [RFC3495]
> >     8   TSP's Provisioning Timer Value           [RFC3495]
> >     9   ?????                                    [RFCXXXX]
> >10-255   Reserved for future extensions
> >
> >What I could not see, and maybe it is in the document, was
> >the Sub-Option Description that will go in the registry.
>
>Sub-Option Description would be "TSP's Security Ticket Control."
>
>Sorry for the confusion.
>
>
> >I hope that helps.
> >
> >Michelle
> >IANA
> >
> >
> >
> >
> >-----Original Message-----
> >From: Paul Duffy [mailto:paduffy@cisco.com]
> >Sent: Monday, May 12, 2003 8:30 AM
> >To: IANA
> >Cc: iesg@ietf.org; rdroms@cisco.com
> >Subject: RE: Last Call: Security Ticket Control Sub-option for the
>CableLabs
> >Client Configuration Option to Proposed Standard
> >
> >
> >...inline please...
> >
> >At 12:27 PM 5/8/2003 -0700, IANA wrote:
> >
> >IESG:
> >
> >The IANA has reviewed the following Internet-Draft which is
> >in Last Call: <draft-ietf-dhc-pktc-kerb-tckt-01.txt>, and
> >has the following comments with regards to the publication of
> >this document:
> >
> >The IANA Considerations section says the following:
> >
> >       IANA is requested to assign a sub-option code to this sub-option
> >       from the "CableLabs Client Configuration" sub-option number space
> >       (maintained within the BOOTP-DHCP Parameters Registry).
> >
> >There is no mention in the IANA Considerations section what the new
> >sub-option is
> >
> >IESG would not permit the author to select the sub-option number
> >assignment...I was told this is entirely up to IANA.  If this is not the
> >case and you are asking my preference, please assign this sub-option the
> >number 9.
> >
> >
> >and which sub-option it is a sub-option to.  (that was
> >a mouthful)
> >
> > From http://www.iana.org/assignments/bootp-dhcp-parameters.  Under the
> >heading...
> >
> >"DHCP Cablelabs Client Configuration Option Type 122 Sub-Option Codes per
> >[RFC3495]"
> >
> >Thanks,
> >
> >
> >
> >If this information is in the documen, there is no pointer to
> >what section in the document this information is described.
> >
> >We understand that a new sub-option registry will be created.
> >Please make sure any instructions on adding further sub-options
> >is described.
> >
> >Please respond to the IANA about our concerns with regards to this
> >document.  Failing to do so may cause delay of the approval and
> >publication of your document.
> >
> >Thank you.
> >
> >Michelle S. Cotton
> >(on behalf of the IANA)
> >
> >
> >--
> >
> >
> >Paul Duffy
> >Cisco Systems, Inc.
> >paduffy@cisco.com
>
>--
>
>Paul Duffy
>Cisco Systems, Inc.
>paduffy@cisco.com

--

Paul Duffy
Cisco Systems, Inc.
paduffy@cisco.com