Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
2017-02-08 07:55:44Fernando,
Because if we did, the loophole for people to violate the standard would disappear (talk about Segment Routing).
There is nothing stopping a future IETF from publishing a document specifying header insertion, even if 2460bis where to ban it. Best regards, Ole
signature.asc
Description: Message signed with OpenPGP
| Previous by Date: | Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity, Alexey Melnikov |
|---|---|
| Next by Date: | Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity, Andrew Sullivan |
| Previous by Thread: | Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard, Fernando Gont |
| Next by Thread: | Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard, Fernando Gont |
| Indexes: | [Date] [Thread] [Top] [All Lists] |