Re: [dhcwg] [Technical Errata Reported] RFC6704 (4995)

[Suresh Krishnan <[e-mail]>]

> On Apr 19, 2017, at 6:16 PM, Megan Ferguson <[e-mail]> wrote:
> 
> Hi Suresh,
> 
> Just forwarding this message from Amanda at IANA for FYI as I see you were not CC’d.

Thanks Megan. I will go and verify the Erratum.

Regards
Suresh


> 
> Thank you.
> 
> RFC Editor/mf
> 
>> Begin forwarded message:
>> 
>>> From: "Amanda Baber via RT" <[e-mail]>
>>> Subject: [IANA #957997] [IANA] Fwd: [Technical Errata Reported] RFC6704 (4995)
>>> Date: April 18, 2017 at 2:16:19 PM PDT
>>> Cc: [e-mail], [e-mail], [e-mail]
>>> Reply-To: [e-mail]
>>> 
>>> Hi Bernie,
>>> 
>>> Megan forwarded us this note about errata 4995.
>>> 
>>> Because the IANA Considerations section specifically says that the entry in the length field is "1," and it's an IETF Consensus registry, we would need an AD-verified errata report in order to change the length to "n." We'll add a link to the errata report to the reference field when we make the change.
>>> 
>>> Best regards,
>>> 
>>> Amanda Baber
>>> Lead IANA Services Specialist
> 
> 
> 
> On Apr 19, 2017, at 12:14 PM, Suresh Krishnan <[e-mail]> wrote:
> 
>> Hi Bernie,
>> I will try to figure out how to do the IANA update. I will hold onto the erratum until then.
>> 
>> Thanks
>> Suresh
>> 
>>> On Apr 19, 2017, at 8:36 AM, Bernie Volz (volz) <[e-mail]> wrote:
>>> 
>>> This erratum is verified. Please update it to reflect that is verified.
>>> 
>>> We can then notify IANA to have the table corrected.
>>> 
>>> - Bernie Volz
>>> 
>>> On 4/14/17, 2:56 PM, "RFC Errata System" <[e-mail]> wrote:
>>> 
>>>  The following errata report has been submitted for RFC6704,
>>>  "Forcerenew Nonce Authentication".
>>> 
>>>  --------------------------------------
>>>  You may review the report below and at:
>>>  http://www.rfc-editor.org/errata_search.php?rfc=6704&eid=4995
>>> 
>>>  --------------------------------------
>>>  Type: Technical
>>>  Reported by: Niels Widger <[e-mail]>
>>> 
>>>  Section: 4
>>> 
>>>  Original Text
>>>  -------------
>>>     IANA has assigned the following new DHCPv4 option code from the
>>>     registry "BOOTP Vendor Extensions and DHCP Options" maintained at
>>>     http://www.iana.org/assignments/bootp-dhcp-parameters:
>>> 
>>>     Tag: 145
>>> 
>>>     Name: FORCERENEW_NONCE_CAPABLE
>>> 
>>>     Data length: 1
>>> 
>>>     Description: Forcerenew Nonce Capable
>>> 
>>>     Reference: this document
>>> 
>>>  Corrected Text
>>>  --------------
>>>     IANA has assigned the following new DHCPv4 option code from the
>>>     registry "BOOTP Vendor Extensions and DHCP Options" maintained at
>>>     http://www.iana.org/assignments/bootp-dhcp-parameters:
>>> 
>>>     Tag: 145
>>> 
>>>     Name: FORCERENEW_NONCE_CAPABLE
>>> 
>>>     Data length: n
>>> 
>>>     Description: Forcerenew Nonce Capable
>>> 
>>>     Reference: this document
>>> 
>>>  Notes
>>>  -----
>>>  RFC 6704 Section 3.1.1 states that the FORCERENEW_NONCE_CAPABLE option is variable length and contains a list of algorithm types:
>>> 
>>>  The FORCERENEW_NONCE_CAPABLE option contains code 145, length n, and
>>>     a sequence of algorithms the client supports:
>>> 
>>>               Code   Len   Algorithms
>>>              +-----+-----+----+----+----+
>>>              | 145 |  n  | A1 | A2 | A3 | ....
>>>              +-----+-----+----+----+----+
>>> 
>>>                   Figure 1: FORCERENEW_NONCE_CAPABLE Option
>>> 
>>>  Instructions:
>>>  -------------
>>>  This erratum is currently posted as "Reported". If necessary, please
>>>  use "Reply All" to discuss whether it should be verified or
>>>  rejected. When a decision is reached, the verifying party  
>>>  can log in to change the status and edit the report, if necessary. 
>>> 
>>>  --------------------------------------
>>>  RFC6704 (draft-ietf-dhc-forcerenew-nonce-07)
>>>  --------------------------------------
>>>  Title               : Forcerenew Nonce Authentication
>>>  Publication Date    : August 2012
>>>  Author(s)           : D. Miles, W. Dec, J. Bristow, R. Maglione
>>>  Category            : PROPOSED STANDARD
>>>  Source              : Dynamic Host Configuration
>>>  Area                : Internet
>>>  Stream              : IETF
>>>  Verifying Party     : IESG
>>> 
>>> 
>> 
>