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 <farina...@gmail.com> 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 <ietf-secretariat-re...@ietf.org>
> *Date:* September 2, 2013 at 4:42:06 AM PDT
> *To:* "Dino Farinacci" <farina...@gmail.com>, "David Meyer" <d...@cisco.com>,
> "Job Snijders" <j...@instituut.net>
> *Cc:* "Terry Manderson" <terry.mander...@icann.org>, "Joel M. Halpern" <
> j...@joelhalpern.com>
> *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
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>
>
     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |           AFI = 16387         |     Rsvd1     |     Flags     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |   Type = ?    |     Rsvd2     |             4 + n             |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |           Source-port         |         Src-port-range        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |            Dest-port          |         Dst-port-range        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |    Reserved   |   Protocol    |   Source-ML   |    Dest-ML    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |              AFI = x          |         Source-Prefix ...     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |              AFI = x          |     Destination-Prefix ...    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
_______________________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to