[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
I send ID summary mail.
NAME OF I-D:
There exist requirements of provider-provisioned virtual private
networks (PPVPN) spanning multiple differently implemented SP
networks from SPs perspective. This document proposes an
interworking method at the interface for implementing PPVPNs spanning
multiple SP networks with different technologies; it proposes the
establishment of connections making use of GRE, IPsec, Frame Relay,
or ATM connections at network interface, and describes how required
services of the PPVPNs, such as security/privacy, quality of service,
extranets, dynamic routing, and multicast, are achieved through
network interface. It further discusses the applicability and
scalability of the proposed interworking method and concludes that
the proposed method has high applicability in interworking various
types of PPVPN capable SP networks, and that justifies the relative
scalability limitation which is not a critical drawback of the
- Callon, R., Suzuki, M., et al., "A Framework for PPVPNs."
- McDysan, D. et al., "Service Requirements for Provider Provisioned Virtual
- Gleeson, B. et al., "A Framework for IP Based Virtual Private Networks,"
- Rosen, E. et al., "BGP/MPLS VPNs."
- GMN-CL home page:
- Muthukrishnan, K. et al., "A Core MPLS IP VPN Architecture."
- Ould-Brahim H. et al., "Network based IP VPN Architecture Using Virtual
- Grossman, D. and Heinanen, J., "Multiprotocol Encapsulation over ATM
Adaptation Layer 5," RFC 2684.
- Rosen E. et al., "Multiprotocol Label Switching Architecture."
- Blake S. et al., "An architecture for Differentiated Services," RFC 2475.
- Dommety, G., "Key and Sequence Number Extensions to GRE," RFC 2890.
- Kent, S. and Atkinson, R., "Security Architecture for the Internet
Protocol," RFC 2401.
WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK
The proposed draft fits in ppvpn WG.
Applications +-------+ +-------+ (new) Hour glass
that use CCAMP: \ | TE-WG | | PPVPN | ... /
\ +-------+ +-------+ /
\ +----------------------+ /
\ | CCAMP | /
\ |-----------+----------| /
/ | C | M --|------ IGP LSA ext
/ | control | measure | \
/ +----------------------+ \
Technologies to / +----+ +----+ +----+ +----+ +----+ \
measure/control:/ |MPLS| |OPT | |RPR | |ATM | | FR |...\
+----+ +----+ +----+ +----+ +----+
WHY IS IT TARGETED AT THIS WG
Ppvpn WG is close to the topic of the proposed draft, however, the topic is
not explicitly stated in the current ppvpn charter.
Thus, I would state additional explanation in the next item JUSTIFICATION.
- Why the WG should consider this work:
Defining and specifying a limited number of approaches (BGP-VPN, Virtual
Router, IPsec VPN, layer 2-VPN) as well as achieving interoperability within
each approach are included in the working items of the ppvpn WG.
Inter-AS VPN interconnections for constructing VPNs spanning multiple AS$B!G(Bs
or service providers are also explicitly stated to be considered in the
However, multi-vendor PPVPN interworking among different approaches is not
explicitly considered in the charter of ppvpn WG.
From the service providers$B!G(B point of view, it must be supported, since it
significantly increases the flexibility in deploying PPVPN.
I feel that this topic had already been supported by not a few attendants
at the 50th IETF meeting.
- What the description of a possible new work item would be for the WG.
"The working group will consider multi-vendor PPVPN interworking among
- Possible milestones for that work item.
Done Post as an Internet-draft (-00.txt)
Mar 01 Requirements of the interworking was discussed and supported.
(Done) Begin discussion of the proposed solution.
Nov 01 Post revised Internet-draft (-01.txt)
Jan 02 Submit document to IESG