Ciso Luigi, please see below...
On 6/2/20, 12:11 AM, "Luigi Iannone" <[email protected]> wrote:
> On 1 Jun 2020, at 07:53, Fabio Maino (fmaino) <[email protected]> wrote:
>
> Ciao Luigi,
> The reason is to allow to experiment with shim headers and non-shim
headers at the same time. As you may remember shim headers have a more fixed
encodng and must be located before non-shim headers.
That is OK for me.
But my question is why this:
> 0x7E to 0x7F: Experimentation and testing
FM> The two above are for experimentation of NON shim headers
> 0x80 to 0xFD: Unassigned (shim headers)
> 0xFE to 0xFF: Experimentation and testing
>FM These two are for experimentation of shim headers.
Shim headers are placed (and processed) first, so we want to give the freedom
to experiment with both.
For example, one would want to experiment with a shim header (identified by
0xFE) that carries some special metadata for IPv4 payloads, while someone else
would want to experiment with IPv8 payloads (identified with 0x7E). A third
person might want to experiment, at the same time, with a shim header that
carries special metadata for IPv8.
Fabio
Instead of this (range has been adapted):
0x7E to 0xFB: Unassigned (shim headers)
0xFC to 0xFF: Experimentation and testing
??
Certainly I am missing something ;-)
Ciao
L.
>
> Thanks,
> Fabio
>
>
>
> On 5/31/20, 10:47 PM, "Luigi Iannone" <[email protected]> wrote:
>
> Thank you for updating the document.
>
> I have a quick question.
>
> Looking at the next protocol values we now see:
>
> 0x7E to 0x7F: Experimentation and testing
> 0x80 to 0xFD: Unassigned (shim headers)
> 0xFE to 0xFF: Experimentation and testing
>
> Can you provide a rationale why not having just one bigger
experimentation and testing range instead of two with an unassigned range in
the middle?
>
> Thanks
>
> Ciao
>
> L.
>
>
>
>> On 1 Jun 2020, at 07:41, [email protected] wrote:
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
>> This draft is a work item of the Locator/ID Separation Protocol WG of
the IETF.
>>
>> Title : LISP Generic Protocol Extension
>> Authors : Fabio Maino
>> Jennifer Lemon
>> Puneet Agarwal
>> Darrel Lewis
>> Michael Smith
>> Filename : draft-ietf-lisp-gpe-15.txt
>> Pages : 15
>> Date : 2020-05-31
>>
>> Abstract:
>> This document describes extentions to the Locator/ID Separation
>> Protocol (LISP) Data-Plane, via changes to the LISP header, to
>> support multi-protocol encapsulation.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-lisp-gpe/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-lisp-gpe-15
>> https://datatracker.ietf.org/doc/html/draft-ietf-lisp-gpe-15
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-gpe-15
>>
>>
>> Please note that it may take a couple of minutes from the time of
submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>>
>> _______________________________________________
>> lisp mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/lisp
>
>
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
