Re: Next steps on Extension Header Insertion

[[e-mail]]

>> To make my point clear: I'm rather agnostic about SR, but I'm against
>> ambiguity in a std track documents, particularly when behind such
>> ambiguity there's the potential for a lot of problems.
> 
> Well said. Ambiguity is harmful here and will cause serious problems later.

There is absolutely no evidence that the lack of normative text here has led to any problems...

Regardless, it is also impossible to specify all the things creative people shouldn't be allowed to do. And that's probably not the purpose of standardisation either. It is to specify enough to make implementation interoperable.

I'm just trying to point out that we shouldn't blow this issue out of proportion. Whatever we end up doing here, it is hard to see it being particularly important, nor have any big consequences. It would have been nice if the IETF could have decreed that the Internet MUST be end to end transparent, and that middleboxes MUST not exist, but...

Cheers,
Ole