Hi Donald, Thanks for the reply and explanation for my third comment.
Regards, Rob > -----Original Message----- > From: iesg <iesg-boun...@ietf.org> On Behalf Of Donald Eastlake > Sent: Tuesday, October 17, 2023 7:14 AM > To: Rob Wilton (rwilton) <rwil...@cisco.com> > Cc: The IESG <i...@ietf.org>; draft-ietf-intarea-rfc7042...@ietf.org; intarea- > cha...@ietf.org; int-area@ietf.org; g...@gigix.net > Subject: Re: Robert Wilton's No Objection on draft-ietf-intarea-rfc7042bis-10: > (with COMMENT) > > Hi Rob, > > On Mon, Oct 16, 2023 at 11:34 AM Robert Wilton via Datatracker > <nore...@ietf.org> wrote: > > > > Robert Wilton has entered the following ballot position for > > draft-ietf-intarea-rfc7042bis-10: No Objection > > > > ... > > > > ---------------------------------------------------------------------- > > COMMENT: > > ---------------------------------------------------------------------- > > > > Hi, > > > > Thanks for taking the time to update this document - it is quite a dry > > read! I > > have a few minor comments for your consideration: > > > > Minor level comments: > > > > (1) p 4, sec 1.1. Notations Used in This Document > > > > "MAC" Media Access Control, not Message Authentication Code. > > "MAC-48" A 48-bit MAC address. This term is obsolete. If globally > > unique, use EUI-48. > > > > Note, this list doesn't appear to define EUI-48, only EUI. Perhaps forward > > reference section 2.1 or add it to the list for completeness? > > Ok. > > > (2) p 6, sec 2.1. 48-Bit MAC Identifiers, OUIs, and Other Prefixes > > > > Table 1 > > The bottom (least significant) four bits of the first octet of the > > 3-octet 48-bit MAC have special meaning, as shown in Figure 1, and > > are referred to below as the M, X, Y, and Z bits. > > > > By 3-octet 48-bit MAC, are you referring to MA-L? Otherwise, I would assume > > that all 48-bit MACs are 6-octets long ... > > That's a great catch. Maybe it was supposed to be "3-octet MAC prefix" > or something but changing to 6-octet seems clearer and well as making > it correct. > > > (3) p 10, sec 2.1.5. 48-Bit IANA MAC Assignment Considerations > > > > * must be documented in an Internet-Draft or RFC. > > > > If they are in an Internet-Draft then is that sufficient for a permanent > > assignment, or only a temporary one. Anyone can write an internet-draft ... > > The intent was that an ID was sufficient for a permanent small > assignment. There are a ton of MAC addresses available. Given the > other constraints on the expert - like not using it to bypass the IEEE > and must be for an IETF protocol (which I would take to mean a draft > that has least been adopted by a WG) or closely related protocol, I'm > not particularly worried about the easy of writing and posting an ID. > The Expert gets to factor all this into their judgement. > > Thanks, > Donald > =============================== > Donald E. Eastlake 3rd +1-508-333-2270 (cell) > 2386 Panoramic Circle, Apopka, FL 32703 USA > d3e...@gmail.com > > > Regards, > > Rob _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
