With regard to the generic LCAF, it seems that each usage would have to
specify what it was actually going to use it for, but this would not be
captured in the mapping system.
This would seem to lead to the situation where one entity is looking
things up with one purpose in mind, but finds mapping for some other
purpose, which it can not support.
Yours,
Joel
On 9/2/13 1:21 PM, Alberto Rodriguez-Natal wrote:
Dear Dino, all,
Here are some ideas we have for new types of LCAFs.
First, we will like to see a 5-tuple LCAF to allow mapping lookups based
on flows. In the attached TXT there is a proposed format. It allows to
perform exact match flow lookups, as well as best match lookups using
port range and prefix mask length. The proposed 5-tuple LCAF is based on
current types 4 and 12, and can be a new type itself, or be merged with
those types.
Second, we find interesting to have a generic (self-defined) LCAF type.
A format like that will allow complex and/or experimental LISP
applications. We aim for a binary JSON-like format. This LCAF type
almost needs no definition, just a new LCAF type number and an agreement
on the binary specification to use. Personally, I like the Universal
Binary JSON Specification (http://ubjson.org/).
I would like to know what the WG thinks of these proposals.
Thanks,
Alberto
On 2 September 2013 18:08, Dino Farinacci <[email protected]
<mailto:[email protected]>> wrote:
I have some updates that I will post to the list but if anyone
thinks there are pending changes and you have told or requested of
me to add text, can you please repost in this list so the entire
working group can see the request and be part of the discussion.
Thanks,
Dino
Begin forwarded message:
*From:* IETF Secretariat <[email protected]
<mailto:[email protected]>>
*Date:* September 2, 2013 at 4:42:06 AM PDT
*To:* "Dino Farinacci" <[email protected]
<mailto:[email protected]>>, "David Meyer" <[email protected]
<mailto:[email protected]>>, "Job Snijders" <[email protected]
<mailto:[email protected]>>
*Cc:* "Terry Manderson" <[email protected]
<mailto:[email protected]>>, "Joel M. Halpern"
<[email protected] <mailto:[email protected]>>
*Subject:* *Expiration impending: <draft-ietf-lisp-lcaf-02.txt>*
The following draft will expire soon:
Name: draft-ietf-lisp-lcaf
Title: LISP Canonical Address Format (LCAF)
State: I-D Exists
Expires: 2013-09-11 (in 1 week, 1 day)
_______________________________________________
lisp mailing list
[email protected] <mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
