Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)

[Jefsey <[e-mail]>]

At 22:55 04/11/2014, Miles Fidelman wrote:
>If we think such matters are "nonsense," and/or outside our scope of 
>expertise - then, by definition, we should not be the (only) ones 
>addressing them.

Two quotes of RFC 3935 - IETF Mission statement - might be of some 
help IRT this legal and multilateral engineering endeavour?

"Technical competence - the issues on which the IETF produces its 
documents are issues where the IETF has the competence needed to 
speak to them, and that the IETF is willing to listen to technically 
competent input from any source.  Technical competence also means 
that we expect IETF output to be designed to sound network 
engineering principles - this is also often referred to as 
"engineering quality"."

"Protocol ownership - when the IETF takes ownership of a protocol or 
function, it accepts the responsibility for all aspects of the 
protocol, even though some aspects may rarely or never be seen on the 
Internet.  Conversely, when the IETF is not responsible for a 
protocol or function, it does not attempt to exert control over it, 
even though it may at times touch or affect the Internet.'

jfc