RE: Fwd: [Nea] Re: use of a design team to develop requirements

[Khaja Ahmed <khaja at windows.microsoft.com>]

I should add... in the meantime, our discussion on the group, in this
thread, should be consistent with the charter.  You should start a
separate thread requesting charter revision if you intend to pursue
that.  

Khaja

-----Original Message-----
From: Khaja Ahmed [mailto:khaja at windows.microsoft.com] 
Sent: Wednesday, December 13, 2006 4:19 PM
To: Keith Moore
Cc: nea at ietf.org
Subject: RE: Fwd: [Nea] Re: use of a design team to develop requirements

I appealed to the chairs and the AD.  Their position was that the
charter should not be changed and it is what it is.  So, whether it
flies or not, this is what we are stuck with for now.  If you have some
way of changing that, I would love to see internet wide back in scope.

Khaja

-----Original Message-----
From: Keith Moore [mailto:moore at cs.utk.edu] 
Sent: Wednesday, December 13, 2006 4:15 PM
To: Khaja Ahmed
Cc: nea at ietf.org
Subject: Re: Fwd: [Nea] Re: use of a design team to develop requirements

> [Khaja] it is not the goals of this WG to produce and protocol that
> scales to the internet. This is meant to be an enterprise only
solution.
> When I raised this question previously the chairs ruled, and the ADs
> have concurred, that internet wide behavior (implying ISP
participation)
> is out of scope.  Enterprise behavior is the only thing we can
consider.

Maybe the ADs disagree, but I don't think this flies, for several
reasons:

One is that IETF has a long history of requiring that its protocols work

at Internet scale, even if they are only intended for use within an 
enterprise network.  For instance, we require that protocols have robust

authentication even if they're generally expected to be used only behind

firewalls.

Another is that even if a protocol is only intended to be used on an 
enterprise network, it will necessarily be installed on large numbers of

hosts that are occasionally plugged into other networks, and the 
security implications of this need to be examined.

Keith


_______________________________________________
Nea mailing list
Nea at ietf.org
https://www1.ietf.org/mailman/listinfo/nea

_______________________________________________
Nea mailing list
Nea at ietf.org
https://www1.ietf.org/mailman/listinfo/nea

_______________________________________________
Nea mailing list
Nea at ietf.org
https://www1.ietf.org/mailman/listinfo/nea