[manet] Re: Gunter Van de Velde's No Objection on draft-ie tf-manet-dlep-traffic-classification-13: (with COMMENT)

"Gunter van de Velde \(Nokia\)" <[email protected]>
Newsgroups gmane.ietf.manet
Message-ID <AS1PR07MB858970CE9147B790E175C62FE0FB2@AS1PR07MB8589.eurprd07.prod.outlook.com>
Sounds as a correct observation about the square brackets Donald.

Be well,
G/

-----Original Message-----
From: Donald Eastlake <[email protected]> 
Sent: Saturday, February 15, 2025 3:24 AM
To: Gunter van de Velde (Nokia) <[email protected]>
Cc: The IESG <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: Gunter Van de Velde's No Objection on draft-ietf-manet-dlep-traffic-classification-13: (with COMMENT)


CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.



Hi Gunter,

On Thu, Feb 6, 2025 at 4:32 PM Gunter Van de Velde via Datatracker <[email protected]> wrote:
> Gunter Van de Velde has entered the following ballot position for
> draft-ietf-manet-dlep-traffic-classification-13: No Objection
>
> ...
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> # Gunter Van de Velde, RTG AD, comments for
> draft-ietf-manet-dlep-traffic-classification-13
>
> # The line numbers used are rendered from IETF idnits tool:
> https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/arch
> ive/id/draft-ietf-manet-dlep-traffic-classification-13.txt
>
> # Many thanks to Darren Dukes for the RTGDIR review follow up.
>
> # Detailed Review
> # ===============
>
> 315                       0   1   2   3   4   5   6   7
> 316                     +---+---+---+---+---+---+---+---+
> 317                     |         DSCP          |  MBZ  |
> 318                     +---+---+---+---+---+---+---+---+
> 319
> 320                       DSCP: Differentiated Services Codepoint
> 321                       MBZ:  MUST be zero
>
> GV> This reads odd. Why the uppercase "MUST" and then all lower case "be zero"
> instead of "Be Zero". What most the device do when MBZ happens to be not zero?
> Same MBZ observation applies to line402 of the document. What about 
> the
> following:
>
> "
> DSCP: Differentiated Services Codepoint (RFC 2474).
> MBZ: Must Be Zero MUST be set to zero when transmitted. Receivers MUST 
> ignore this field upon reception. "

Thanks for the suggested wording change which looks good to me except that I think the [RFC2474] reference should use square bacets.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA  [email protected]
_______________________________________________
manet mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.