On April 12, 2022 at 3:14:41 AM, Luigi Iannone wrote: > > On 11 Apr 2022, at 22:35, Christer Holmberg via Datatracker wrote: Hi! Sorry I missed this before. ... > > Section 3 says: > > > > "If a LISP device receives a LISP message containing a Vendor Specific > > LCAF with an OUI that it does not understand, it MUST drop the > > message and it SHOULD create a log message." > > > > This sounds like an update to LISP. > > > > Excellent point. Actually this document updates RFC 8060, and this should be > stated in the document. The word "updates" has a specific connotation in an RFC. One interpretation is that the functionality defined in this document has to be considered part of the original (rfc8060 in this case). It also requires an indication in the header. The text above talks about what a node that supports this specification is required to do. rfc8060-only nodes are not affected. IOW, the statement above qualifies as a formal update. The introduction of a new LCAF doesn't require a formal update either because new LCAFs are defined using the registry. s/updates/extends/g Thanks! Alvaro. -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
