[lisp] Fwd: Proposing "Encapsulation Format" LCAF type

[Dino Farinacci <[e-mail]>]

I sent this out a couple of weeks ago. There has been some discussion but wanted to move this along. So bringing this back on the list.

I had some private discussions with Damien and Darrel, who had comments on the idea as well as the format of this new Encapsulation Format LCAF type. I would like to summarize the discussion and open discussion up on the list.

I would like to submit this by end of week if there are no strong objections.

To summarize the comments from Damien, Darrel, Luigi, and Joel (please correct me if I missed anything):

(1) My goal of this new LCAF type was to create a specific need to identify what encapsulations a decapsulator can support and not make this a general negotiation facility. The proposal is to not document all types of encapsulation formats that have ever been designed in the IETF but ones that are or may gain popularity in the industry for data-center overlay applications.

(2) There was a request to make the format more general to allow data-plane options to be transmitted in Map-Reply messages. The current format uses only 7 bits out of 32 bits, so future encapsulations can be added. Therefore, the current format is extensible but purposely not generally extensible. If we need to add anything more, we can always add new LCAF types in the future.

(3) A compromise among Dino, Darrel, and Damien was to submit what we have now for experimentation and to discuss more about a adding an LCAF type that will more general to convey data-plane parameters. The chairs indicated we should discuss adding this as a WG item when the recharter discussions occur.

See diff enclosed.

Thanks,
Dino

> Begin forwarded message:
> 
> From: Dino Farinacci <[e-mail]>
> Subject: Proposing "Encapsulation Format" LCAF type
> Date: November 13, 2014 at 12:45:42 PM PST
> To: LISP mailing list list <[e-mail]>
> 
> I've been having discussions with various people and there is a rough concensus that if the LISP mapping system can aid in helping encapsulators know what encapsulation formats a decapsulator supports, we will get better interoperability in the face of the myriad of overlay data-planes that are being proposed in the IETF.
> 
> Here is the section that was added to the LCAF draft:
> 

> 
> 
> 
> Proposed -07 and html diff also enclosed.
> 
> Dino
> 

> 
> 
>