Re: [MBONED] [Technical Errata Reported] RFC8777 (6688)

[Warren Kumari <[e-mail]>]

Hi all,

I'd appreciate some feedback here - I think that this Errata should be
marked Verified, but I might be missing something.


>From what I can see,
https://datatracker.ietf.org/doc/html/rfc8777#section-4.2 speaketh thusly:
The AMTRELAY RData consists of an 8-bit precedence field, a 1-bit
   "Discovery Optional" field, a 7-bit type field, and a variable length
   relay field."

There are some more discussions around what various type codes mean, but
nothing else about the field size.

The IANA Considerations section then says: "Relay type numbers 4 through
255 can be assigned with a policy of Specification Required"

You can’t put 10 pounds of manure into a five-pound bag, and you can't fit
255 values in a 7 bit field.


I'm planning on marking this verified on Monday the 4th of October[0]
unless someone tells me otherwise.

W
[0]: I'm going to be at a conference for much of next week, and will have a
hard time keeping up with mail.


On Sun, Sep 19, 2021 at 1:03 PM RFC Errata System <[e-mail]>
wrote:

> The following errata report has been submitted for RFC8777,
> "DNS Reverse IP Automatic Multicast Tunneling (AMT) Discovery".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6688
>
> --------------------------------------
> Type: Technical
> Reported by: Dick Franks <[e-mail]>
>
> Section: 5
>
> Original Text
> -------------
>    +-------+---------------------------------------+
>    | 3     | A wire-encoded domain name is present |
>    +-------+---------------------------------------+
>    | 4-255 | Unassigned                            |
>    +-------+---------------------------------------+
>
>       Table 2: Initial Contents of the "Relay Type
>                     Field" Registry
>
>    Values 0, 1, 2, and 3 are further explained in Sections 4.2.3 and
>    4.2.4.  Relay type numbers 4 through 255 can be assigned with a
>    policy of Specification Required (as described in [RFC8126]).
>
> Corrected Text
> --------------
>    +-------+---------------------------------------+
>    | 3     | A wire-encoded domain name is present |
>    +-------+---------------------------------------+
>    | 4-127 | Unassigned                            |
>    +-------+---------------------------------------+
>
>       Table 2: Initial Contents of the "Relay Type
>                     Field" Registry
>
>    Values 0, 1, 2, and 3 are further explained in Sections 4.2.3 and
>    4.2.4.  Relay type numbers 4 through 127 can be assigned with a
>    policy of Specification Required (as described in [RFC8126]).
>
> Notes
> -----
> Relay Type is a 7 bit field, the MS bit of the wire-format  octet contains
> the D-bit.
>
> 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.
>
> --------------------------------------
> RFC8777 (draft-ietf-mboned-driad-amt-discovery-13)
> --------------------------------------
> Title               : DNS Reverse IP Automatic Multicast Tunneling (AMT)
> Discovery
> Publication Date    : April 2020
> Author(s)           : J. Holland
> Category            : PROPOSED STANDARD
> Source              : MBONE Deployment
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
>


-- 
The computing scientist’s main challenge is not to get confused by the
complexities of his own making.
  -- E. W. Dijkstra