>>>>> "Lars" == Lars Eggert <lars.egg...@nokia.com> writes:
Lars> Hi, yes, because RFC2460 says "MUST use always" and the
Lars> intent here is to loosen that restriction for LISP and AMT.
Lars> (And I'm sure Noel will again call this "red-tape legalese",
Lars> but the fact is that this change revises the standing IETF
Lars> consensus, and there's a process for that.)
Something that apparently isn't obvious to some WG participants who
have contacted me off-list is that it is quite possible to change an
IETF consensus. When Margaret, Lars and I talk about doing things
like updating RFC 2460, we're not talking about what we think should
be a obstruction once we've done the work to decide what the right
technical direction is.
We've all been on the IESG and are used to these sorts of updates as a
routine matter of IETF business.
In the simplest case, you're talking about writing a potentially short
draft that updates the spec in question. You then find the
appropriate AD or working group to sponsor the draft and go through
the normal process.
Yes, you do actually have to build consensus. For some updates,
that's easy, for others it is very difficult. That's how we all
convince each other that we actually have thought things through and
come to the right decision.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
