Re: IETF Last Call conclusion for draft-ietf-6man-rfc2460bis-08

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



What's wrong or what is missing in https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-05

?

On Mar 30, 2017 16:05, <otroan@xxxxxxxxxxxxx> wrote:
Robert,

> Correct me if I am missing someting but the entire debate is not about describing or not header insertion.
>
> I am under assumption that originating hosts still can legally insert it.
>
> It is all about to modify EH in flight - right ? Moreover concerns raised are about side effects of it like MTU .. not lack of instructions on how to insert, modify or remove EH elements.
>
> So what exactly are you expecting WG to deliver as next step if 2460bis goes fwd ? Is detecting the max MTU on end to end path even in 6man's charter ?

You can write a new protocol specification independently of 2460bis that does whatever it has to do, and then we can argue over that document on its own merits.

Cheers,
Ole

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]