draft-ietf-ccamp-rfc5787bis-02.txt   draft-ietf-ccamp-rfc5787bis-03.txt 
INTERNET-DRAFT A. Malis, ed. INTERNET-DRAFT A. Malis, ed.
Intended Status: Proposed Standard Verizon Communications Intended Status: Proposed Standard Verizon Communications
Expires: January 6, 2012 A. Lindem, ed. Expires: February 9, 2012 A. Lindem, ed.
Ericsson Ericsson
July 5, 2011 D. Papadimitriou, ed.
Alcatel-Lucent
August 8, 2011
Updates to ASON Routing for OSPFv2 Protocols (RFC 5787bis) Updates to ASON Routing for OSPFv2 Protocols (RFC 5787bis)
draft-ietf-ccamp-rfc5787bis-02.txt draft-ietf-ccamp-rfc5787bis-03.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with 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 other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 2, line 31 skipping to change at page 3, line 31
Note that this work is scoped to the requirements and evaluation Note that this work is scoped to the requirements and evaluation
expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations
current when those documents were written. Future extensions of current when those documents were written. Future extensions of
revisions of this work may be necessary if the ITU-T Recommendations revisions of this work may be necessary if the ITU-T Recommendations
are revised or if new requirements are introduced into a revision of are revised or if new requirements are introduced into a revision of
RFC 4258. RFC 4258.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. Conventions Used in This Document . . . . . . . . . . . . 5 1.1. Conventions Used in This Document . . . . . . . . . . . . 6
2. Routing Areas, OSPF Areas, and Protocol Instances . . . . . . 5 2. Routing Areas, OSPF Areas, and Protocol Instances . . . . . . 6
3. Terminology and Identification . . . . . . . . . . . . . . . . 6 3. Terminology and Identification . . . . . . . . . . . . . . . . 7
4. Reachability . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Reachability . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Link Attribute . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Link Attribute . . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. Local Adaptation . . . . . . . . . . . . . . . . . . . . . 7 5.1. Local Adaptation . . . . . . . . . . . . . . . . . . . . . 8
5.2. Bandwidth Accounting . . . . . . . . . . . . . . . . . . . 8 5.2. Bandwidth Accounting . . . . . . . . . . . . . . . . . . . 9
6. Routing Information Scope . . . . . . . . . . . . . . . . . . 8 6. Routing Information Scope . . . . . . . . . . . . . . . . . . 9
6.1. Link Advertisement (Local and Remote TE Router ID 6.1. Link Advertisement (Local and Remote TE Router ID
Sub-TLV) . . . . . . . . . . . . . . . . . . . . . . . . . 9 Sub-TLV) . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.2. Reachability Advertisement (Local TE Router ID sub-TLV) . 10 6.2. Reachability Advertisement (Local TE Router ID sub-TLV) . 11
7. Routing Information Dissemination . . . . . . . . . . . . . . 11 7. Routing Information Dissemination . . . . . . . . . . . . . . 12
7.1 Import/Export Rules . . . . . . . . . . . . . . . . . . . . 11 7.1 Import/Export Rules . . . . . . . . . . . . . . . . . . . . 12
7.2 Loop Prevention . . . . . . . . . . . . . . . . . . . . . . 11 7.2 Loop Prevention . . . . . . . . . . . . . . . . . . . . . . 12
7.2.1 Inter-RA Export Upward/Downward Sub-TLVs . . . . . . . 12 7.2.1 Inter-RA Export Upward/Downward Sub-TLVs . . . . . . . 13
7.2.2 Inter-RA Export Upward/Downward Sub-TLV Processing . . 13 7.2.2 Inter-RA Export Upward/Downward Sub-TLV Processing . . 14
8. OSPFv2 Scalability . . . . . . . . . . . . . . . . . . . . . . 13 8. OSPFv2 Scalability . . . . . . . . . . . . . . . . . . . . . . 14
9. Security Considerations . . . . . . . . . . . . . . . . . . . 14 9. Security Considerations . . . . . . . . . . . . . . . . . . . 15
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
10.1. Sub-TLVs of the Link TLV . . . . . . . . . . . . . . . . 14 10.1. Sub-TLVs of the Link TLV . . . . . . . . . . . . . . . . 15
10.2. Sub-TLVs of the Node Attribute TLV . . . . . . . . . . . 15 10.2. Sub-TLVs of the Node Attribute TLV . . . . . . . . . . . 16
10.3. Sub-TLVs of the Router Address TLV . . . . . . . . . . . 15 10.3. Sub-TLVs of the Router Address TLV . . . . . . . . . . . 16
11. Management Considerations . . . . . . . . . . . . . . . . . 16 11. Management Considerations . . . . . . . . . . . . . . . . . 17
11.1. Routing Area (RA) Isolation . . . . . . . . . . . . . . . 16 11.1. Routing Area (RA) Isolation . . . . . . . . . . . . . . . 17
11.2 Routing Area (RA) Topology/Configuration Changes . . . . . 16 11.2 Routing Area (RA) Topology/Configuration Changes . . . . . 17
12. Comparison to Requirements in RFC 4258 . . . . . . . . . . . 16 12. Comparison to Requirements in RFC 4258 . . . . . . . . . . . 17
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
13.1. Normative References . . . . . . . . . . . . . . . . . . 22 13.1. Normative References . . . . . . . . . . . . . . . . . . 23
13.2. Informative References . . . . . . . . . . . . . . . . . 23 13.2. Informative References . . . . . . . . . . . . . . . . . 24
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
Appendix A. ASON Terminology . . . . . . . . . . . . . . . . . . 25 Appendix A. ASON Terminology . . . . . . . . . . . . . . . . . . 26
Appendix B. ASON Routing Terminology . . . . . . . . . . . . . . 26 Appendix B. ASON Routing Terminology . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
The Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] The Generalized Multiprotocol Label Switching (GMPLS) [RFC3945]
protocol suite is designed to provide a control plane for a range of protocol suite is designed to provide a control plane for a range of
network technologies including optical networks such as time division network technologies including optical networks such as time division
multiplexing (TDM) networks including SONET/SDH and Optical Transport multiplexing (TDM) networks including SONET/SDH and Optical Transport
Networks (OTNs), and lambda switching optical networks. Networks (OTNs), and lambda switching optical networks.
The ITU-T defines the architecture of the Automatically Switched The ITU-T defines the architecture of the Automatically Switched
skipping to change at page 24, line 14 skipping to change at page 25, line 14
[G.805] ITU-T Rec. G.805, "Generic Functional Architecture of [G.805] ITU-T Rec. G.805, "Generic Functional Architecture of
Transport Networks)", March 2000. Transport Networks)", March 2000.
[G.8080] ITU-T Rec. G.8080/Y.1304, "Architecture for the [G.8080] ITU-T Rec. G.8080/Y.1304, "Architecture for the
Automatically Switched Optical Network (ASON)," June Automatically Switched Optical Network (ASON)," June
2006 (and Amendments 1 (March 2008) and 2 (Sept. 2010)). 2006 (and Amendments 1 (March 2008) and 2 (Sept. 2010)).
14. Acknowledgements 14. Acknowledgements
The editors would like to thank Dimitri Papadimitriou for editing RFC The editors would like to thank Lyndon Ong, Remi Theillaud, Stephen
5787, from which this document is derived, and Lyndon Ong, Remi Shew, Jonathan Sadler, Deborah Brungard, and Lou Berger for their
Theillaud, Stephen Shew, Jonathan Sadler, Deborah Brungard, and Lou useful comments and suggestions.
Berger for their useful comments and suggestions.
Appendix A. ASON Terminology Appendix A. ASON Terminology
This document makes use of the following terms: This document makes use of the following terms:
Administrative domain: (See Recommendation [G.805].) For the Administrative domain: (See Recommendation [G.805].) For the
purposes of [G7715.1], an administrative domain represents the purposes of [G7715.1], an administrative domain represents the
extent of resources that belong to a single player such as a extent of resources that belong to a single player such as a
network operator, a service provider, or an end-user. network operator, a service provider, or an end-user.
Administrative domains of different players do not overlap amongst Administrative domains of different players do not overlap amongst
skipping to change at line 1197 skipping to change at page 28, line 43
Waltham MA 02451 USA Waltham MA 02451 USA
EMail: andrew.g.malis@verizon.com EMail: andrew.g.malis@verizon.com
Acee Lindem Acee Lindem
Ericsson Ericsson
102 Carric Bend Court 102 Carric Bend Court
Cary, NC 27519 Cary, NC 27519
EMail: acee.lindem@ericsson.com EMail: acee.lindem@ericsson.com
Dimitri Papadimitriou
Alcatel-Lucent
Copernicuslaan, 50
2018 Antwerpen, Belgium
EMail: dimitri.papadimitriou@alcatel-lucent.com
 End of changes. 7 change blocks. 
40 lines changed or deleted 41 lines changed or added

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