PDF《PPVPN WG》

2 interface, such as Frame Relay or ATM, to the VPN customer, while using IP-based mechanisms in the provider infrastructure to improve scalability and configurability over traditional L2 networks). PPVPN WG charter (cont.) ? Consideration of inter-AS (SP) VPNs ? Each technical approach document will C evaluate how well it meets the requirements (req. doc) C address scalability and manageability issues, operational aspects C analyze the threat and security aspects of PPVPNs, including appropriate mandatory-to-implement technologies and management mechanisms to ensure adequate security, privacy of user data. Analysis will include cryptographic security from customer site to customer site using IPSEC. ? An applicability statement for each approach C describing the environments in which the approach is suitable for deployment, including analysis of scaling impact of the approach on SPs and threat analysis ? Coordination with IETF PWE3 and ITU-T efforts PPVPN WG charter (cont.) ? ITU-T : see related slot in agenda ? After the PWE3 BOF on Wednedsday : C PWE3 charter proposal will clearly include work in coordination with the PPVPN WG ? avoid overlapping, avoid mutual imposition of constraints C PWE3 chairs will submit the charter proposal to the pwe3 list, I asked Luca to distributed it to the ppvpn list too C PWE3 will basically work on encapsulation and e-2-e signaling C clearly identify asap if and where overlapping may happen ? sensible area : encapsulation for L2 VPN (Kompella draft), what else ? ? please comment on the list Coordination with ITU-T and PWE3 Goals and Milestones ? DONE : C Formulate a plan and begin approaching SPs for input on scaling and other requirements C Begin discussion (based on submitted IDs) on candidate approaches against the service requirements C Begin discussion of the framework and the service requirement documents (two design teams formed, an interim meeting was held) ?

2 IDs (moved to WG documents in agreement with ADs) : framework ID, requirements ID ? NOT DONE : C Identify a limited set of candidate approaches, build design teams C Mar 01: Begin discussion of applicability statements C Aug

01 : Submit framework, req IDs to IESG ->

Info RFCs C Mar

02 : Submit candidate approaches, applicability statements to IESG for publication C Mar 02: Charter update or WG disband Administrativia ? I asked Ananth Nagarajan to take minutes as in San Diego ? Blue sheets ? Speakers please : C respect time C focus on requirements and framework issues C no presentation of your IDs, just content overview C later, send me by e-mail your presentation (they will be posted on the PPVPN informal server) Next steps from now According to our milestones ? REQ and FRAME IDs : continue work for Info RFCs after London (tight schedule) C some work already planned by the two design teams ? missing sections, alignment, revision/enhancements to current text C PLEASE COMMENT ON THE LIST FROM NOW (on various pieces of work) (Requirements from Providers, etc.) C need to complete or solve open items C additi........