Hi! That makes sense.
Just confirm, the behavior is not specified in rfc8060, right? It seems to me that it would be good to specify it somewhere and draft-ietf-lisp-vendor-lcaf looks as good a place as any - do you agree? Thanks! Alvaro. On April 13, 2022 at 1:50:33 PM, Dino Farinacci ([email protected]) wrote: > I assume that the message containing an unknown Type MUST be dropped. > Or should it just be the specific TLV? It should be ignored. The term "dropped" implies the packet with an unknown LCAF should be dropped. But there can be other LCAFs encoded that are knownn that should be processed. Here is an example: An EID-record with an rloc-count of 3, one RLOC-record is an IPv4 address, another one an IPv6 address, and the final one is a "foobar" address (or unknown). The EID should be processed with an RLOC-set of 2. Dino
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
