> But even with same vendor but old implementation, the LCAF type should be > ignored by old when new sends to old.
Yes, agree. Thanks, Prakash On 4/13/22, 2:39 PM, "Dino Farinacci" <[email protected]> wrote: > On Apr 13, 2022, at 2:33 PM, Prakash Jain (prakjain) <[email protected]> wrote: > > 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. Agree. But even with same vendor but old implementation, the LCAF type should be ignored by old when new sends to old. Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
