I find the goals and schedule acceptable.
>>>>> "Yoav" == Yoav Nir <[email protected]> writes:
Yoav> In an environment with many IPsec gateways and remote clients
Yoav> that share an established trust infrastructure (in a single
Yoav> administrative domain or across multiple domains), customers
Yoav> want to get on-demand mesh IPsec capability for
Yoav> efficiency. However, this cannot be feasibly accomplished only
Yoav> with today's IPsec and IKE due to problems with address
Yoav> lookup, reachability, policy configuration, etc.
Yoav> The IPsecME working group will handle this large scale VPN
Yoav> problem by delivering the following:
Yoav> * The working group will create a problem statement document
Yoav> including use cases, definitions and proper requirements for
Yoav> discovery and updates. This document would be
Yoav> solution-agnostic. Should reach WG last call around October
Yoav> 2012.
Yoav> * The working group will review and help publish Informational
Yoav> documents describing current vendor proprietary
Yoav> solutions. These should be ready for IETF last call by August
Yoav> 2012.
Yoav> * The working group will choose a common solution for the
Yoav> discovery and update problems that will satisfy the
Yoav> requirements in the problem statement document. The working
Yoav> group may consider multiple proposals, and then choose one to
Yoav> bring to the standards track.
Yoav> _______________________________________________ IPsec mailing
Yoav> list [email protected]
Yoav> https://www.ietf.org/mailman/listinfo/ipsec
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec
