Gorry - Thanx for your review.
In regards to: > “A TLV may contain information in its fixed part that is not part of the key.” > - Could this be an RFC 2119 “MAY”? This draft is not specifying any encoding changes to any TLV (this is explicitly stated in Section 4). The text you quote is simply a description of what is the case for TLVs which have been defined by other documents - not a normative statement about how TLVs are encoded. I therefore think lower case is correct here. Les > -----Original Message----- > From: Gorry Fairhurst via Datatracker <nore...@ietf.org> > Sent: Monday, March 24, 2025 12:15 PM > To: The IESG <i...@ietf.org> > Cc: draft-ietf-lsr-multi-...@ietf.org; lsr-cha...@ietf.org; lsr@ietf.org; > yingzhen.i...@gmail.com; yingzhen.i...@gmail.com > Subject: Gorry Fairhurst's No Objection on draft-ietf-lsr-multi-tlv-11: (with > COMMENT) > > Gorry Fairhurst has entered the following ballot position for > draft-ietf-lsr-multi-tlv-11: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to > https://www.ietf.org/about/groups/iesg/statements/handling-ballot- > positions/ > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-lsr-multi-tlv/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thank you for writing this document, I have only one comment: > “A TLV may contain information in its fixed part that is not part of the key.” > - Could this be an RFC 2119 “MAY”? > > _______________________________________________ Lsr mailing list -- lsr@ietf.org To unsubscribe send an email to lsr-le...@ietf.org
