Hi Dino, > I would propose that the Capabilities Type LCAF be encoded as a bit-string. > Where each bit position indicates the LCAF Type value. We would have 2 > fields, an EID field and a RLOC field so it can be conveyed which Types are > supported for EID encoded fields or RLOC encoded fields in any LISP control > message. > > [...] > > Comments?
Will a bit string be able to provide enough detail? LCAF types can be combined in many ways... > If people are interested I can draft up the details for the -03 version. Or > if you think we should post the -03 version just with the current changes, I > can do that. I would like to see it in -03 > And also comment if you think we should go with the JSON Data Model Type for > -03 or put it into -04 with perhaps this Capabilities LCAF. Also for -03 I would say. This will very probably not be the final draft, so why publish -03 now when we know that this will be added to -04 :-) Thanks, Sander. _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
