status of l3 ppvpn working group documents march 2004.pptVIP

Status of L3 PPVPNWorking Group Documents March 2004 – Seoul IETF Ross Callon Ron Bonica Rick Wilder Requirements/Frameworks L3 Framework draft-ietf-l3vpn-framework-00.txt No change (RFC Ed Q; document approved for publication) Security Framework draft-ietf-l3vpn-security-framework-01.txt Updated to resolve security directorate comments To be resubmitted to IESG ASAP L3 Service reqts draft-ietf-l3vpn-requirements-00.txt Update in progress based on IESG comments Generic Reqts draft-ietf-l3vpn-generic-reqts-03.txt See following slide Generic Requirements Has been updated in response to IESG comments 3 scenarios for deployment of VPNs Single provider, single-AS Single-provider, multi-AS Multi-provider Increase in Scaling requirements Capitalize key words (MUST, SHOULD, MAY, …) Clean up references Editorial / clarification Has passed l3vpn working group last call Needs l2vpn working group last call Then to be resubmitted to IESG Base Documents BGP/MPLS IP VPNs draft-ietf-l3vpn-rfc2547bis-01.txt and draft-ietf-l3vpn-as2547-03.txt Security analysis added to AS Passed WG last call last October Updated based on IESG comments There is one comment to be resolved on applicability statement VR Architecture draft-ietf-l3vpn-vpn-vr-01.txt and draft-ietf-l3vpn-as-vr-01.txt CE/IPSec Architecture draft-ietf-l3vpn-ce-based-02.txt and draft-declercq-l3vpn-ce-based-as-00.txt Security analyses have been added to each AS Both will be last called ASAP (beginning next week) AS Guidelines Terminology AS Guidelines ASs are done (two will enter WG last call ASAP) Guidelines document has timed out Question to WG: Should we leave it that way? Terminology draft-andersson-ppvpn-terminology-04.txt Passed WG last call (l3vpn and l2vpn) Minor update in the works To be submitted to IESG ASAP MIBs Network Management Framework for OAM draft-ietf-l3vpn-mgt-fwk-01.txt Is now working group document Presentation to follow Textual Conventions draft-ietf-l3vpn-tc-mib-01.txt M