Re: [6lo] Fwd: [Technical Errata Reported] RFC4944 (4359)

[Ralph Droms <[e-mail]>]

Looks OK to me.  I have no objection to marking it Verified.

> On May 28, 2015, at 8:04 AM 5/28/15, Brian Haberman <[e-mail]> wrote:
> 
> All,
>     I would like feedback on this erratum.  It appears to be correct,
> in my view.  Any objections to me marking it Verified?
> 
> Regards,
> Brian
> 
> 
> -------- Forwarded Message --------
> Subject: [Technical Errata Reported] RFC4944 (4359)
> Date: Thu,  7 May 2015 12:07:39 -0700 (PDT)
> From: RFC Errata System <[e-mail]>
> To: [e-mail],
> [e-mail], [e-mail],
> [e-mail], [e-mail],
> [e-mail], [e-mail], [e-mail]
> CC: [e-mail], [e-mail],
> [e-mail]
> 
> The following errata report has been submitted for RFC4944,
> "Transmission of IPv6 Packets over IEEE 802.15.4 Networks".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=4944&eid=4359
> 
> --------------------------------------
> Type: Technical
> Reported by: Gabriel Montenegro <[e-mail]>
> 
> Section: 5.1
> 
> Original Text
> -------------
>   ESC:  Specifies that the following header is a single 8-bit field for
>      the Dispatch value.  It allows support for Dispatch values larger
>      than 127.
> 
> Corrected Text
> --------------
>   ESC:  Specifies that the following header is a single 8-bit field for
>      the Dispatch value.  It allows support for Dispatch values larger
>      than 63.
> 
> Notes
> -----
> The (non-ESCaped) Dispatch value is a 6-bit selector. However, it used
> to be a 7-bit selector, which has a value at most 127. When the field
> became a 6-bit selector, this maximum became 63, but the referring text
> was never updated.
> 
> For historical reference, see an early version from IETF 67 proposing
> the Dispatch value within the Dispatch header as a 7-bit field:
> 
> http://6lowpan.tzi.org/FrontPage?action=AttachFile&do=view&target=tentative-draft2-ietf-6lowpan-format-07.txt
> 
>   The dispatch type is defined by a zero-bit as the first bit.  The
>   dispatch type and header is shown here:
> 
>                        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
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |0|  Dispatch   |  type-specific header
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> 
>   Dispatch               7-bit selector.  Identifies the type of header
>                          immediately following the Dispatch type.
> 
> The relevant slides also show this (slide 8):
> http://6lowpan.tzi.org/FrontPage?action=AttachFile&do=view&target=6lowpan-header-proposal-2.ppt
> 
> 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 (IESG)
> can log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC4944 (draft-ietf-6lowpan-format-13)
> --------------------------------------
> Title               : Transmission of IPv6 Packets over IEEE 802.15.4
> Networks
> Publication Date    : September 2007
> Author(s)           : G. Montenegro, N. Kushalnagar, J. Hui, D. Culler
> Category            : PROPOSED STANDARD
> Source              : IPv6 over Low power WPAN
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG
> 
> 
> 
> -- 
> This message has been scanned for viruses and dangerous content by
> E.F.A. Project, and is believed to be clean.
> 
> Click here to report this message as spam.
> http://efa.daedelus.com/cgi-bin/learn-msg.cgi?id=97F1D60054.A616F&token=a00583b5361cce8776745f1ea05415c9
> 
> 
> 
> _______________________________________________
> 6lo mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/6lo