Pablo,
I am not sure that your use of this field is in accordance with Section 4.7 of
RFC 8200.
Ron
Juniper Internal
> -Original Message-
> From: Pablo Camarillo (pcamaril)
> Sent: Tuesday, May 7, 2019 3:09 AM
> To:
Fair enough.
Ron
Juniper Internal
> -Original Message-
> From: Pablo Camarillo (pcamaril)
> Sent: Tuesday, May 7, 2019 3:12 AM
> To: Ron Bonica ; SPRING WG ; 6man
> WG
> Subject: Re: SRv6 Network Programming: More Headers
>
> Hi Ron,
>
> Your guess is wr
On Tue, May 7, 2019 at 7:17 AM Tom Herbert wrote:
>
> On Tue, May 7, 2019 at 7:05 AM Mark Smith wrote:
> >
> >
> >
> > On Tue., 7 May 2019, 23:39 Joel M. Halpern, wrote:
> >>
> >> That is not what Next-Header means.
> >> Even with this explanation, it is clear that 59 is NOT the right value
> >>
On Tue, May 7, 2019 at 7:05 AM Mark Smith wrote:
>
>
>
> On Tue., 7 May 2019, 23:39 Joel M. Halpern, wrote:
>>
>> That is not what Next-Header means.
>> Even with this explanation, it is clear that 59 is NOT the right value
>> for the next header.
>
>
> If the SID value isn't a reserved for this
On Tue., 7 May 2019, 23:39 Joel M. Halpern, wrote:
> That is not what Next-Header means.
> Even with this explanation, it is clear that 59 is NOT the right value
> for the next header.
>
If the SID value isn't a reserved for this purpose, permanent and globally
unique value, how would a troubles
That is not what Next-Header means.
Even with this explanation, it is clear that 59 is NOT the right value
for the next header.
Yours,
Joel
On 5/7/19 3:08 AM, Pablo Camarillo (pcamaril) wrote:
Hi Ron,
We use the next header value 59 to identify at the receiver that there is no
other kind of
Hi Ron,
Your guess is wrong. Please read the sentence right after the one you quote.
"The effective next-header (ENH) is the next-header field of the IP
header when no SRH is present, or is the next-header field of the
last SRH.
In this version of the document, we assume that there a
Hi Ron,
We use the next header value 59 to identify at the receiver that there is no
other kind of Internet Protocol beneath to be processed.
Note that we are *not* using 59 to identify the fact that it is an ethernet
header (i.e. other non Internet-Protocols would also use the 59 to identify
