draft-ietf-l3vpn-ipsec-2547-00.txt   draft-ietf-l3vpn-ipsec-2547-01.txt 
Network Working Group Eric C. Rosen Network Working Group Eric C. Rosen
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Expiration Date: August 2003 Expiration Date: February 2004
Jeremy De Clercq Jeremy De Clercq
Olivier Paridaens Olivier Paridaens
Yves T'Joens Yves T'Joens
Alcatel Alcatel
Chandru Sargor Chandru Sargor
Cosine Communications Cosine Communications
February 2003 August 2003
Use of PE-PE IPsec in RFC2547 VPNs Use of PE-PE IPsec in RFC2547 VPNs
draft-ietf-l3vpn-ipsec-2547-03.txt draft-ietf-l3vpn-ipsec-2547-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 15, line 17 skipping to change at page 15, line 17
enhancement to IPsec ever needed to reclaim the SPI sub-field used to enhancement to IPsec ever needed to reclaim the SPI sub-field used to
carry the label, etc., etc.). Failure to preserve the layering also carry the label, etc., etc.). Failure to preserve the layering also
complicates the situation in which the transport is sometimes IPsec complicates the situation in which the transport is sometimes IPsec
and sometimes MPLS. Keeping the MPLS VPN functionality in the MPLS and sometimes MPLS. Keeping the MPLS VPN functionality in the MPLS
layer and out of the IPsec layer certainly seems worthwhile. layer and out of the IPsec layer certainly seems worthwhile.
4. Authors' Addresses 4. Authors' Addresses
Eric C. Rosen Eric C. Rosen
Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive 1414 Massachusetts Avenue
Chelmsford, MA, 01824 Boxborough, MA 01719
Email: erosen@cisco.com Email: erosen@cisco.com
Jeremy De Clercq Jeremy De Clercq
Alcatel Alcatel
Francis Wellesplein 1 Francis Wellesplein 1
2018 Antwerpen, Belgium 2018 Antwerpen, Belgium
Phone: +32 3 240 4752 Phone: +32 3 240 4752
Email: jeremy.de_clercq@alcatel.be Email: jeremy.de_clercq@alcatel.be
Olivier Paridaens Olivier Paridaens
skipping to change at page 16, line 20 skipping to change at page 16, line 20
Chandru Sargor Chandru Sargor
CoSine Communications CoSine Communications
1200 Bridge Parkway 1200 Bridge Parkway
Redwood City, CA 94065 Redwood City, CA 94065
Email: csargor@cosinecom.com Email: csargor@cosinecom.com
5. References 5. References
[MPLS-in-IP/GRE] "Encapsulating MPLS in IP or GRE",, Worster et. al., [MPLS-in-IP/GRE] "Encapsulating MPLS in IP or GRE",, Worster et. al.,
draft-ietf-mpls-in-ip-or-gre-00.txt, January 2003 draft-ietf-mpls-in-ip-or-gre-01.txt, July 2003
[RFC2547bis] BGP/MPLS VPNs, Rosen et. al., draft-ietf-ppvpn- [RFC2547bis] BGP/MPLS IP VPNs, Rosen et. al., draft-ietf-l3vpn-
rfc2547bis-03.txt, October 2002 rfc2547bis-00.txt, July 2003
[VPN-SPI] BGP/IPsec VPN, De Clercq et. al., draft-declercq-bgp- [VPN-SPI] BGP/IPsec VPN, De Clercq et. al., draft-declercq-bgp-
ipsec-vpn-01.txt, February 2001 ipsec-vpn-01.txt, February 2001
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/