draft-ietf-pce-vpn-req-00.txt   draft-ietf-pce-vpn-req-01.txt 
Network Working Group S. Yasukawa Network Working Group S. Yasukawa
Internet Draft NTT Internet Draft NTT
Category: Informational A. Farrel (Ed.) Category: Informational A. Farrel (Ed.)
Created: March 24, 2009 Old Dog Consulting Created: October 19, 2009 Old Dog Consulting
Expires: September 24, 2009 Expires: April 19, 2010
PCC-PCE Communication Requirements for VPNs PCC-PCE Communication Requirements for VPNs
draft-ietf-pce-vpn-req-00.txt draft-ietf-pce-vpn-req-01.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with the
the provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
skipping to change at page 2, line 23 skipping to change at page 2, line 23
3.1.1. Per-VPN Policy ............................................. 5 3.1.1. Per-VPN Policy ............................................. 5
3.1.2. Per-VPN Constraints and Algorithms ......................... 5 3.1.2. Per-VPN Constraints and Algorithms ......................... 5
3.1.3. Per-VPN Resources .......................................... 5 3.1.3. Per-VPN Resources .......................................... 5
3.1.4. LSP Protection Schemes and Resource Sharing ................ 5 3.1.4. LSP Protection Schemes and Resource Sharing ................ 5
3.2. Customer Control of The Core Network ......................... 6 3.2. Customer Control of The Core Network ......................... 6
3.3. Private Address Spaces ....................................... 6 3.3. Private Address Spaces ....................................... 6
3.4. CE-CE Service Protection Schemes ............................. 6 3.4. CE-CE Service Protection Schemes ............................. 6
3.5. Aggregation Schemes .......................................... 7 3.5. Aggregation Schemes .......................................... 7
3.5.1. Sharing Core Tunnels ....................................... 7 3.5.1. Sharing Core Tunnels ....................................... 7
3.5.2. Handling Core Scalability .................................. 7 3.5.2. Handling Core Scalability .................................. 7
3.6. Multicast Considerations ..................................... 7 3.6. Multicast Considerations ..................................... 8
3.6.1. Unicast or Multicast LSPs .................................. 8 3.6.1. Unicast or Multicast LSPs .................................. 8
3.6.2. P2MP Traffic Engineering ................................... 9 3.6.2. P2MP Traffic Engineering ................................... 9
3.6.3. Aggregation onto P2MP LSPs ................................. 9 3.6.3. Aggregation onto P2MP LSPs ................................. 9
3.7. VPN Establishment/Addition/Deletion .......................... 9 3.7. VPN Establishment/Addition/Deletion .......................... 9
3.8. Interworking Between Multiple VPN Domains .................... 9 3.8. Interworking Between Multiple VPN Domains ................... 10
4. PCECP Requirements for PCE Support of VPNs .................... 10 4. PCECP Requirements for PCE Support of VPNs .................... 10
4.1. Identification of VPN ....................................... 10 4.1. Identification of VPN ....................................... 10
4.2. Identification of Related VPNs .............................. 10 4.2. Identification of Related VPNs .............................. 10
4.3. Scoping of Addresses ........................................ 10 4.3. Scoping of Addresses ........................................ 11
4.4. Cooperation between Customer PCE and Core PCE ............... 11 4.4. Cooperation between Customer PCE and Core PCE ............... 11
4.5. Path Diversity .............................................. 11 4.5. Path Diversity .............................................. 11
4.6. Point-to-Multipoint ......................................... 11 4.6. Point-to-Multipoint ......................................... 11
4.7. Incorporating Path Calculation During VPN Membership 4.7. Incorporating Path Calculation During VPN Membership
Discovery ................................................. 11 Discovery ................................................. 11
5. Manageability Considerations .... ............................. 12 5. Manageability Considerations .... ............................. 12
5.1 Control of Function and Policy ............................... 12 5.1 Control of Function and Policy ............................... 12
5.2 Information and Data Models .................................. 12 5.2 Information and Data Models .................................. 12
5.3 Liveness Detection and Monitoring ............................ 12 5.3 Liveness Detection and Monitoring ............................ 12
5.4 Verifying Correct Operation .................................. 12 5.4 Verifying Correct Operation .................................. 12
5.5 Requirements on Other Protocols and Functional Components .... 12 5.5 Requirements on Other Protocols and Functional Components .... 12
5.6 Impact on Network Operation .................................. 13 5.6 Impact on Network Operation .................................. 13
5.7 Other Considerations ......................................... 13 5.7 Other Considerations ......................................... 13
6. Security Considerations ....................................... 13 6. Security Considerations ....................................... 13
7. IANA Considerations ........................................... 13 7. IANA Considerations ........................................... 14
8. Acknowledgments ............................................... 13 8. Acknowledgments ............................................... 14
9. References .................................................... 14 9. References .................................................... 14
9.1. Normative References ........................................ 14 9.1. Normative References ........................................ 14
9.2. Informative References ...................................... 14 9.2. Informative References ...................................... 14
10. Author's Address ............................................. 15 10. Author's Address ............................................. 16
1. Introduction 1. Introduction
The Virtual Private Network (VPN) is an important service offered by The Virtual Private Network (VPN) is an important service offered by
network providers to their customers. A lot of different VPN network providers to their customers. A lot of different VPN
technologies such as IP-VPN and VPLS [RFC2764], [RFC4761], [RFC4762] technologies such as IP-VPN and VPLS [RFC2764], [RFC4761], [RFC4762]
have been developed and are deployed into many service providers' have been developed and are deployed into many service providers'
networks to enhance their service capabilities. VPN technologies have networks to enhance their service capabilities. VPN technologies have
also has been extended to support multicast services [RFC4834] and also has been extended to support multicast services [RFC4834] and
layer 1 servics [RFC4847]. layer 1 servics [RFC4847].
skipping to change at page 13, line 50 skipping to change at page 14, line 11
on the PCECP above those described in [RFC4657], but the on the PCECP above those described in [RFC4657], but the
application of PCE in support of VPNs does require that those application of PCE in support of VPNs does require that those
security requirements be correctly implemented and applied. security requirements be correctly implemented and applied.
7. IANA Considerations 7. IANA Considerations
This document makes no requests for IANA action. This document makes no requests for IANA action.
8. Acknowledgments 8. Acknowledgments
TBA TBD
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to indicate [RFC2119] Bradner, S., "Key words for use in RFCs to indicate
requirements levels", RFC 2119, March 1997. requirements levels", RFC 2119, March 1997.
[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and
McManus, J., "Requirements for Traffic Engineering Over McManus, J., "Requirements for Traffic Engineering Over
skipping to change at page 15, line 50 skipping to change at page 16, line 10
[PCE-P2MP-REQ] Yasukawa, S. and Farrel, A., "PCC-PCE Communication [PCE-P2MP-REQ] Yasukawa, S. and Farrel, A., "PCC-PCE Communication
Requirements for Point-to-Multipoint Traffic Requirements for Point-to-Multipoint Traffic
Engineering", draft-ietf-pce-p2mp-req, work in Engineering", draft-ietf-pce-p2mp-req, work in
progress. progress.
10. Author's Address 10. Author's Address
Seisho Yasukawa (Ed.) Seisho Yasukawa (Ed.)
NTT Corporation NTT Corporation
9-11, Midori-Cho 3-Chome 9-11, Midori-Cho 3-Chome
Musashino-Shi, Tokyo 180-8585 Japan Musashino-Shi, Tokyo 180-8585,
Phone: +81 422 59 4769 Japan
EMail: s.yasukawa@hco.ntt.co.jp Email: yasukawa.seisho@lab.ntt.co.jp
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
EMail: adrian@olddog.co.uk EMail: adrian@olddog.co.uk
Intellectual Property Statement Full Copyright Statement
The IETF Trust takes no position regarding the validity or scope of
any Intellectual Property Rights or other rights that might be
claimed to pertain to the implementation or use of the technology
described in any IETF Document or the extent to which any license
under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any
such rights.
Copies of Intellectual Property disclosures made to the IETF
Secretariat and any assurances of licenses to be made available, or
the result of an attempt made to obtain a general license or
permission for the use of such proprietary rights by implementers or
users of this specification can be obtained from the IETF on-line IPR
repository at http://www.ietf.org/ipr
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
any standard or specification contained in an IETF Document. Please
address the information to the IETF at ietf-ipr@ietf.org.
The definitive version of an IETF Document is that published by, or
under the auspices of, the IETF. Versions of IETF Documents that are
published by third parties, including those that are translated into
other languages, should not be considered to be definitive versions
of IETF Documents. The definitive version of these Legal Provisions
is that published by, or under the auspices of, the IETF. Versions of
these Legal Provisions that are published by third parties, including
those that are translated into other languages, should not be
considered to be definitive versions of these Legal Provisions.
For the avoidance of doubt, each Contributor to the IETF Standards
Process licenses each Contribution that he or she makes as part of
the IETF Standards Process to the IETF Trust pursuant to the
provisions of RFC 5378. No language to the contrary, or terms,
conditions or rights that differ from or are inconsistent with the
rights and licenses granted under RFC 5378, shall have any effect and
shall be null and void, whether published or posted by such
Contributor, or included with or in such Contribution.
Disclaimer of Validity
All IETF Documents and the information contained therein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your Please review these documents carefully, as they describe your rights
rights and restrictions with respect to this document. and restrictions with respect to this document.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s)
controlling the copyright in such materials, this document may not
be modified outside the IETF Standards Process, and derivative
works of it may not be created outside the IETF Standards Process,
except to format it for publication as an RFC or to translate it
into languages other than English.
 End of changes. 13 change blocks. 
70 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/