Re: [dhcwg] [Technical Errata Reported] RFC8357 (6008)

Megan Ferguson <mferguson@amsl.com> Mon, 16 March 2020 04:57 UTC

Return-Path: <mferguson@amsl.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E1113A0B45 for <dhcwg@ietfa.amsl.com>; Sun, 15 Mar 2020 21:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uELPm5o63qwI for <dhcwg@ietfa.amsl.com>; Sun, 15 Mar 2020 21:57:22 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB56F3A0B40 for <dhcwg@ietf.org>; Sun, 15 Mar 2020 21:57:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 06EDB202140; Sun, 15 Mar 2020 21:57:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lq83eEf9Gx9G; Sun, 15 Mar 2020 21:57:22 -0700 (PDT)
Received: from [10.0.1.18] (unknown [47.144.155.28]) by c8a.amsl.com (Postfix) with ESMTPA id 96DB620213F; Sun, 15 Mar 2020 21:57:22 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Megan Ferguson <mferguson@amsl.com>
In-Reply-To: <BN7PR11MB2547CAD76C7D4BD31C5E04C8CFE20@BN7PR11MB2547.namprd11.prod.outlook.com>
Date: Sun, 15 Mar 2020 21:57:20 -0700
Cc: RFC System <rfc-editor@rfc-editor.org>, "naiming@cisco.com" <naiming@cisco.com>, "Enke Chen (enkechen)" <enkechen@cisco.com>, "suresh@kaloom.com" <suresh@kaloom.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "tomasz.mrugalski@gmail.com" <tomasz.mrugalski@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E0BC6F3-31DE-454F-9B86-E2349E00A612@amsl.com>
References: <20200305110746.D2F46F406C9@rfc-editor.org> <29896430-72A9-44E8-B3C6-6FBC67CD4D61@cisco.com> <BN7PR11MB2547CAD76C7D4BD31C5E04C8CFE20@BN7PR11MB2547.namprd11.prod.outlook.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "bortzmeyer+ietf@nic.fr" <bortzmeyer+ietf@nic.fr>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/Gj0l7YV96iRobL0qMicwb_N2_i8>
Subject: Re: [dhcwg] [Technical Errata Reported] RFC8357 (6008)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Mar 2020 04:57:26 -0000

Hi Bernie,

Apologies for the much-delayed reply.

We went ahead and edited this report as we believe you intended.  Please review and confirm.

https://www.rfc-editor.org/errata/eid6008

Thank you.

RFC Editor/mf


On Mar 5, 2020, at 2:32 PM, Bernie Volz (volz) <volz@cisco.com> wrote:

> The change to the diagram seems to have happened during the RFC process (the -10 draft has the correct diagram).
>  
> I don't recall how we can handle errata and whether it is better to "cancel" the current one and substitute a different one that has the correct text, as follows:
>  
> The incorrect "diagram" is in Section 4.2:
>  
>        0                   1                   2                   3
>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |    OPTION_RELAY_PORT    |         Option-Len                  |
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |    Downstream Source Port     |
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>  
> The correct diagram (from draft-ietf-dhc-relay-port-10 after updating the option name which is what I think caused the issue):
>  
>        0                   1                   2                   3
>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |       OPTION_RELAY_PORT       |         Option-Len            |
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |    Downstream Source Port     |
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>  
> Note: You need to assure that the diagrams are in a fixed space font (such as Courier New).
>  
> As per RFC8415, the option code (OPTION_RELAY_PORT) and option length fields (Option-Len) are both 16-bits – seehttps://tools.ietf.org/html/rfc8415#section-21.1).
>  
> 	• Bernie
>  
> -----Original Message-----
> From: Bernie Volz (volz) 
> Sent: Thursday, March 5, 2020 7:05 AM
> To: RFC Errata System <rfc-editor@rfc-editor.org>
> Cc: naiming@cisco.com; Enke Chen (enkechen) <enkechen@cisco.com>; suresh@kaloom.com; Eric Vyncke (evyncke) <evyncke@cisco.com>; tomasz.mrugalski@gmail.com; bortzmeyer+ietf@nic.fr; dhcwg@ietf.org
> Subject: Re: [dhcwg] [Technical Errata Reported] RFC8357 (6008)
>  
> The diagram is a bit off, but the text is correct that option-code and option-len are both 16-bits.
>  
> We can log errata that diagram is broken, but the text is correct.
>  
> - Bernie
>  
> > On Mar 5, 2020, at 6:08 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> >
> > The following errata report has been submitted for RFC8357,
> > "Generalized UDP Source Port for DHCP Relay".
> >
> > --------------------------------------
> > You may review the report below and at:
> > https://www.rfc-editor.org/errata/eid6008
> >
> > --------------------------------------
> > Type: Technical
> > Reported by: Stéphane Bortzmeyer <bortzmeyer+ietf@nic.fr>
> >
> > Section: 4.2
> >
> > Original Text
> > -------------
> > Option-Code:  OPTION_RELAY_PORT. 16-bit value, 135.
> >
> > Option-Len:  16-bit value to be set to 2.
> >
> > Corrected Text
> > --------------
> > Option-Code:  OPTION_RELAY_PORT. 13-bit value, 135.
> >
> > Option-Len:  19-bit value to be set to 2.
> >
> > Notes
> > -----
> > Discrepancy between the diagram and the text noted by
> > draft-mcquistin-augmented-ascii-diagrams-02
> >
> > 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.
> >
> > --------------------------------------
> > RFC8357 (draft-ietf-dhc-relay-port-10)
> > --------------------------------------
> > Title               : Generalized UDP Source Port for DHCP Relay
> > Publication Date    : March 2018
> > Author(s)           : N. Shen, E. Chen
> > Category            : PROPOSED STANDARD
> > Source              : Dynamic Host Configuration
> > Area                : Internet
> > Stream              : IETF
> > Verifying Party     : IESG
> >
> > _______________________________________________
> > dhcwg mailing list
> > dhcwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/dhcwg