Re: The IETF environment

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

 



Dave Crocker wrote:
On 4/25/2014 7:56 AM, Ned Freed wrote:
An obvious counterexample is what recently happened in perpass and
the various works it has started. Regardless of what anyone thinks of
perpass or its outcome, a fair characterization is that it was an
IETF repsonse to the message delivered by Snoden et al.

Yup. It's a singular example, but that's the point. It's not what the IETF (usually) does.


Silly question, but perhaps relevant in the context of the IANAxfr discussions: So, a lot of what IANA does is covered by an MOU between IETF and IANA. What happens if IANA doesn't honor it's end of the MOU? I don't believe it has any recourse measures spelled out. Beyond that, how would "the IETF" actually notice and respond? (Both informally and formally.)

Seems to be another example of a key role that belongs to the IETF that contrasts a bit with its historical way of operating.

Miles Fidelman



--
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra





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