Subject: FYI: PPVPN Internet Draft relocation to L3vpn working group

From: Ross Callon <[email-masked]>
Date: Tue, 22 Jul 2003 12:16:57 -0400

As a result of the ppvpn split into two working groups, the
various working group documents need to be re-issued.
Some will be re-issued as l3vpn documents, some as
l2vpn documents.

The message below is requesting the appropriate documents
be re-issued as l3vpn documents (the Layer 2 documents 
were requested separately by the L2 chairs). 

thanks, Ross

>X-Sender: [email-masked]
>X-Mailer: QUALCOMM Windows Eudora Version 4.3
>Date: Tue, 22 Jul 2003 12:10:30 -0400
>To: [email-masked]
>From: Ross Callon <[email-masked]>
>Subject: PPVPN Internet Draft relocation to L3vpn working group
>Cc: [email-masked]
>
>Due to the split of the ppvpn working group into two working 
>groups, we would like the following internet drafts re-issued with 
>a new name. All should be considered to be l3vpn working group 
>drafts:
>
>draft-ietf-ppvpn-requirements-06.txt 
>(Service requirements for Layer 3 Provider Provisioned Virtual Private Networks) 
>should be re-issued as draft-ietf-l3vpn-requirements-00.txt
>
>draft-ietf-ppvpn-framework-08.txt 
>(A Framework for Layer 3 Provider Provisioned Virtual Private Networks) 
>should be re-issued as draft-ietf-l3vpn-framework-00.txt
>
>draft-ietf-ppvpn-ce-based-03.txt 
>(An Architecture for Provider Provisioned CE-based Virtual Private Networks using IPsec) 
>should be re-issued as draft-ietf-l3vpn-ce-based-00.txt
>
>draft-ietf-ppvpn-bgp-ipv6-vpn-03.txt 
>(BGP-MPLS VPN extension for IPv6 VPN) 
>should be re-issued as draft-ietf-l3vpn-bgp-ipv6-00.txt
>
>draft-ietf-ppvpn-mpls-vpn-mib-05.txt 
>(MPLS/BGP Virtual Private Network Management Information Base Using SMIv2) 
>should be re-issued as draft-ietf-l3vpn-mpls-vpn-mib-00.txt
>
>draft-ietf-ppvpn-rfc2547bis-04.txt 
>(BGP/MPLS VPNs) 
>should be re-issued as draft-ietf-l3vpn-rfc2547bis-00.txt
>
>draft-ietf-ppvpn-ipsec-2547-03.txt 
>(Use of PE-PE IPsec in RFC2547 VPNs) 
>should be re-issued as draft-ietf-l3vpn-ipsec-2547-00.txt
>
>draft-ietf-ppvpn-gre-ip-2547-02.txt 
>(Use of PE-PE GRE or IP in RFC2547 VPNs) 
>should be re-issued as draft-ietf-l3vpn-gre-ip-2547-00.txt
>
>draft-ietf-ppvpn-bgpvpn-auto-05.txt 
>(Using BGP as an Auto-Discovery Mechanism for Provider-provisioned VPNs) 
>should be re-issued as draft-ietf-l3vpn-bgpvpn-auto-00.txt
>
>draft-ietf-ppvpn-vpn-vr-04.txt 
>(Network based IP VPN Architecture using Virtual Routers) 
>should be re-issued as draft-ietf-l3vpn-vpn-vr-00.txt 
>
>draft-ietf-ppvpn-vr-mib-05.txt 
>(Virtual Router Management Information Base Using SMIv2) 
>should be re-issued as draft-ietf-l3vpn-vr-mib-00.txt
>
>draft-ietf-ppvpn-tc-mib-02.txt 
>(Definition of Textual Conventions for Provider Provisioned Virtual 
>Private Network (PPVPN) Management) 
>should be re-issued as draft-ietf-l3vpn-tc-mib-00.txt
>
>draft-ietf-ppvpn-as2547-01.txt 
>(Applicability Statement for VPNs Based on rfc2547bis) 
>should be re-issued as draft-ietf-l3vpn-as2547-00.txt
>
>draft-ietf-ppvpn-applicability-guidelines-02.txt 
>(Guidelines of Applicability Statements for PPVPNs) 
>should be re-issued as draft-ietf-l3vpn-applicability-guidelines-00.txt
>
>draft-ietf-ppvpn-as-vr-02.txt 
>(Applicability Statement for Virtual Router-based Layer PPVPN approaches) 
>should be re-issued as draft-ietf-l3vpn-as-vr-00.txt 
>
>draft-ietf-ppvpn-l3vpn-auth-03.txt 
>(CE-to-CE Member Verification for Layer 3 VPNs) 
>should be re-issued as draft-ietf-l3vpn-auth-00.txt
>
>draft-ietf-ppvpn-generic-reqts-03.txt 
>(Generic Requirements for Provider Provisioned VPN) 
>should be re-issued as draft-ietf-l3vpn-generic-reqts-00.txt
>
>draft-ietf-ppvpn-ospf-2547-01.txt 
>(OSPF as the PE/CE Protocol in BGP/MPLS VPNs) 
>should be re-issued as draft-ietf-l3vpn-ospf-2547-00.txt
>
>thanks, Ross