Since its vendor specific LCAF, vendor might intend to use this for its vendor spefic usage/purpose in generic lisp message. Means, if recever is same vendor as transmitter, that usage is applicable, otherwise ignore/drop vendor specific LCAF but generic lisp message should still be procssed as per lisp specification.
Hence, for unknown LCAF, only tlv should be droped and not whole message. My 2 cents.. Thanks, Prakash ________________________________ From: lisp <[email protected]> on behalf of Alvaro Retana <[email protected]> Sent: Wednesday, April 13, 2022, 4:39 AM To: [email protected] Cc: [email protected]; [email protected] Subject: [lisp] Unknown LCAF Types (?) (draft-ietf-lisp-vendor-lcaf) Hi! The recent GenArt review and the comment about unknown OUIs got me thinking. What should a LISP device do if it receives an unknown LCAF Type? It seems to me that the intent is to tightly control the use of specific LCAFs in specific deployments. Nonetheless, there's always a chance than an unknown Type is received. I looked at rfc8060 but found no indication there. Did I miss it? I assume that the message containing an unknown Type MUST be dropped. Or should it just be the specific TLV? In either case, if that is not specified then we could use draft-ietf-lisp-vendor-lcaf to specify that behavior -- and formally update rfc8060. ?? Thanks! Alvaro. _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
