Re: Fwd: [Nea] Re: use of a design team to develop requirements
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



Mike Fratto wrote:

> Ok, I am not going to act as charter police, but what you are
> describing is a matter local policy and a matter of deployed
> infrastructure regarding both assessment and enforcement.

  If all requirements are a matter of local policy, then this WG will
never develop a standard.

> I think your problem statement is too specific and really is kind of
> obvious.

  It still needs saying.  Much of the NEA architecture and requirements
are obvious to many, but perhaps not to all.  That's why we have working
groups and public discussions: to publicly ensure we have consensus.

> Network owners want to control access to network resources based on a
> one or more factors such as ...

  Many versions of this have been deployed already, some for decades.  I
believe we need to spend *some* time enumerating what's deployed and
what works, before we go design complex systems systems.  If we don't,
then there's a good chance we will re-invent what already exists.

> Making the resonable asusmption that NAC is being deployed, the
> problem with the NAC market today is that there are three competing
> frameworks, Cisco Network Admission Contron, Microsoft Network Access
> Protection, and the Trusted Computing Group Trusted Network Connect.

  How does the TNC overlap with NEA?  The chair of NEA is also the chair
of TNC, but I haven't seen any statement about that topic.

> Cisco and Microsoft have announced interoperabilty plans, but neither
> interperate with TNC. That means there is a very real possibility that
> the market will continue to be fractured and that means interoperation
> will be  impossible and that hurts organizations deploying NAC.

  Interoperation of... what, exactly?  Again, discussion of the
requirements and architecture is on topic for this list.  You're
skipping over that entirely, and assuming certain technologies.

  Alan DeKok.
--
  http://deployingradius.com       - The web site of the book
  http://deployingradius.com/blog/ - The blog

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




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.