draft-ietf-ccamp-gmpls-general-constraints-ospf-te-00.txt   draft-ietf-ccamp-gmpls-general-constraints-ospf-te-01.txt 
Network work group Fatai Zhang Network work group Fatai Zhang
Internet Draft Young Lee Internet Draft Young Lee
Intended status: Standards Track Jianrui Han Intended status: Standards Track Jianrui Han
Huawei Huawei
G. Bernstein G. Bernstein
Grotto Networking Grotto Networking
Yunbin Xu Yunbin Xu
CATR CATR
Expires: September 14, 2011 March 14, 2011 Expires: March 13, 2012 September 13, 2011
OSPF-TE Extensions for General Network Element Constraints OSPF-TE Extensions for General Network Element Constraints
draft-ietf-ccamp-gmpls-general-constraints-ospf-te-00.txt draft-ietf-ccamp-gmpls-general-constraints-ospf-te-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 provisions of BCP 78 and BCP 79. the 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.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 14, 2011. This Internet-Draft will expire on March 13, 2012.
Abstract Abstract
Generalized Multiprotocol Label Switching can be used to control a Generalized Multiprotocol Label Switching can be used to control a
wide variety of technologies including packet switching (e.g., MPLS), wide variety of technologies including packet switching (e.g., MPLS),
time-division (e.g., SONET/SDH, OTN), wavelength (lambdas), and time-division (e.g., SONET/SDH, OTN), wavelength (lambdas), and
spatial switching (e.g., incoming port or fiber to outgoing port or spatial switching (e.g., incoming port or fiber to outgoing port or
fiber). In some of these technologies network elements and links may fiber). In some of these technologies network elements and links may
impose additional routing constraints such as asymmetric switch impose additional routing constraints such as asymmetric switch
connectivity, non-local label assignment, and label range limitations connectivity, non-local label assignment, and label range limitations
skipping to change at page 2, line 20 skipping to change at page 2, line 20
MPLS (GMPLS). MPLS (GMPLS).
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction.................................................2 1. Introduction ................................................ 2
2. Node Information.............................................3 2. Node Information ............................................ 3
2.1. Connectivity Matrix.....................................4 2.1. Connectivity Matrix..................................... 4
3. Link Information.............................................4 3. Link Information ............................................ 4
3.1. Port Label Restrictions.................................5 3.1. Port Label Restrictions................................. 5
3.2. Available Labels........................................5 3.2. Available Labels........................................ 5
3.3. Shared Backup Labels....................................6 3.3. Shared Backup Labels.................................... 6
4. Routing Procedures...........................................6 4. Routing Procedures .......................................... 6
5. Security Considerations......................................7 5. Security Considerations...................................... 7
6. IANA Considerations..........................................7 6. IANA Considerations ......................................... 7
6.1. Node Information........................................7 6.1. Node Information........................................ 7
6.2. Link Information........................................7 6.2. Link Information........................................ 7
7. References...................................................8 7. References .................................................. 8
7.1. Normative References....................................8 7.1. Normative References.................................... 8
7.2. Informative References..................................9 7.2. Informative References.................................. 9
8. Authors' Addresses...........................................9 8. Authors' Addresses .......................................... 9
Acknowledgment.................................................11 Acknowledgment ................................................ 11
1. Introduction 1. Introduction
Some data plane technologies that wish to make use of a GMPLS control Some data plane technologies that wish to make use of a GMPLS control
plane contain additional constraints on switching capability and plane contain additional constraints on switching capability and
label assignment. In addition, some of these technologies should be label assignment. In addition, some of these technologies should be
capable of performing non-local label assignment based on the nature capable of performing non-local label assignment based on the nature
of the technology, e.g., wavelength continuity constraint in WSON of the technology, e.g., wavelength continuity constraint in WSON
[WSON-Frame]. Such constraints can lead to the requirement for link [RFC6163]. Such constraints can lead to the requirement for link by
by link label availability in path computation and label assignment. link label availability in path computation and label assignment.
[GEN-Encode] provides efficient encodings of information needed by [GEN-Encode] provides efficient encodings of information needed by
the routing and label assignment process in technologies such as WSON the routing and label assignment process in technologies such as WSON
and are potentially applicable to a wider range of technologies. and are potentially applicable to a wider range of technologies.
This document defines extensions to the OSPF routing protocol based This document defines extensions to the OSPF routing protocol based
on [GEN-Encode] to enhance the Traffic Engineering (TE) properties of on [GEN-Encode] to enhance the Traffic Engineering (TE) properties of
GMPLS TE which are defined in [RFC3630], [RFC4202], and [RFC4203]. GMPLS TE which are defined in [RFC3630], [RFC4202], and [RFC4203].
The enhancements to the Traffic Engineering (TE) properties of GMPLS The enhancements to the Traffic Engineering (TE) properties of GMPLS
TE links can be announced in OSPF TE LSAs. The TE LSA, which is an TE links can be announced in OSPF TE LSAs. The TE LSA, which is an
skipping to change at page 6, line 5 skipping to change at page 6, line 5
represent the Available Labels described in [GEN-Encode]. Usually, it represent the Available Labels described in [GEN-Encode]. Usually, it
depends on the implementation to one of the approaches. In WSON depends on the implementation to one of the approaches. In WSON
networks, considering that the continuity of the available or networks, considering that the continuity of the available or
unavailable wavelength set can be scattered for the dynamic unavailable wavelength set can be scattered for the dynamic
wavelength availability, so it may burden the routing to reorganize wavelength availability, so it may burden the routing to reorganize
the wavelength set information when the Inclusive (/Exclusive) List the wavelength set information when the Inclusive (/Exclusive) List
(/Range) approaches are used to represent Available Wavelengths (/Range) approaches are used to represent Available Wavelengths
information. Therefore, it is RECOMMENDED that only the Bitmap Set be information. Therefore, it is RECOMMENDED that only the Bitmap Set be
used for representation Available Wavelengths information. used for representation Available Wavelengths information.
The ''Base Label'' and ''Last Label'' in label set defined in [GEN-Encode] The "Base Label" and "Last Label" in label set defined in [GEN-Encode]
corresponds to base wavelength label and last wavelength label in corresponds to base wavelength label and last wavelength label in
WSON, the format of which is described as follows: WSON, the format of which is described as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Grid | C.S. | Reserved | n | |Grid | C.S. | Reserved | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The detailed information related to wavelength label can be referred The detailed information related to wavelength label can be referred
to [Lambda-Labels]. to [RFC6205].
3.3. Shared Backup Labels 3.3. Shared Backup Labels
Shared Backup Labels indicates the labels available for shared backup Shared Backup Labels indicates the labels available for shared backup
use on a link as described in [GEN-Encode]. use on a link as described in [GEN-Encode].
The Shared Backup Labels is a sub-TLV (the type is TBD by IANA) of The Shared Backup Labels is a sub-TLV (the type is TBD by IANA) of
the Link TLV. The length is the length of value field in octets. The the Link TLV. The length is the length of value field in octets. The
meaning and format of this sub-TLV are defined in Section 5.2 of meaning and format of this sub-TLV are defined in Section 5.2 of
[GEN-Encode]. The Shared Backup Labels sub-TLV may occur at most once [GEN-Encode]. The Shared Backup Labels sub-TLV may occur at most once
within the link TLV. within the link TLV.
4. Routing Procedures 4. Routing Procedures
All the sub-TLVs are nested to top-level TLV(s) and contained in All the sub-TLVs are nested to top-level TLV(s) and contained in
Opaque LSAs. The flooding of Opaque LSAs must follow the rules Opaque LSAs. The flooding of Opaque LSAs must follow the rules
specified in [RFC2328], [RFC2370], [RFC3630], [RFC4203] and [RFC5786]. specified in [RFC2328], [RFC2370], [RFC3630], [RFC4203] and [RFC5786].
Considering the routing scalability issues in some cases, the routing Considering the routing scalability issues in some cases, the routing
protocol should be capable of supporting the separation of dynamic protocol should be capable of supporting the separation of dynamic
information from relatively static information. information from relatively static information to avoid unnecessary
updates of static information when dynamic information is changed. A
In the WSON networks, the node information and link information can standard-compliant approach is to separate the dynamic information
be classified as two kinds: one is relatively static information such sub-TLVs from the static information sub-TLVs, each nested to top-
as Node ID, Connectivity Matrix information; the other is dynamic level TLV ([RFC3630 and RFC5876]), and advertise them in the separate
information such as Available Wavelengths information. [GEN-Encode] OSPF TE LSAs.
give recommendations of typical usage of previously defined sub-TLVs
which contain relatively static information and dynamic information.
An implementation SHOULD take measures to avoid frequent updates of
relatively static information when the relatively static information
is not changed.
For node information, since the Connectivity Matrix information is For node information, since the Connectivity Matrix information is
static, the LSA containing the Node Attribute TLV can be updated with static, the LSA containing the Node Attribute TLV can be updated with
a lower frequency to avoid unnecessary updates. a lower frequency to avoid unnecessary updates.
For link information, a mechanism MAY be applied such that static For link information, a mechanism MAY be applied such that static
information and dynamic information of one TE link are contained in information and dynamic information of one TE link are contained in
separate Opaque LSAs, which are updated with different frequencies, separate Opaque LSAs. For example, the Port Label Restrictions
to avoid unnecessary updates of static information when dynamic information sub-TLV and Available Labels information sub-TLV can be
information is changed. nested to the top level link TLVs and advertised in the separate LSAs.
Note that as with other TE information, an implementation SHOULD take Note that as with other TE information, an implementation SHOULD take
measures to avoid rapid and frequent updates of routing information measures to avoid rapid and frequent updates of routing information
that could cause the routing network to become swamped. A threshold that could cause the routing network to become swamped. A threshold
mechanism MAY be applied such that updates are only flooded when a mechanism MAY be applied such that updates are only flooded when a
number of changes have been made to the label availability (e.g., number of changes have been made to the label availability
wavelength availability) information within a specific time. Such information (e.g., wavelength availability) within a specific time.
mechanisms MUST be configurable if they are implemented. Such mechanisms MUST be configurable if they are implemented.
5. Security Considerations 5. Security Considerations
This document does not introduce any further security issues other This document does not introduce any further security issues other
than those discussed in [RFC 3630], [RFC 4203]. than those discussed in [RFC 3630], [RFC 4203].
6. IANA Considerations 6. IANA Considerations
[RFC3630] says that the top level Types in a TE LSA and Types for [RFC3630] says that the top level Types in a TE LSA and Types for
sub-TLVs for each top level Types must be assigned by Expert Review, sub-TLVs for each top level Types must be assigned by Expert Review,
skipping to change at page 8, line 44 skipping to change at page 8, line 39
Support of Generalized Multi-Protocol Label Switching Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, October 2005. (GMPLS)", RFC 4203, October 2005.
[RFC5786] R. Aggarwal and K. Kompella, "Advertising a Router's Local [RFC5786] R. Aggarwal and K. Kompella, "Advertising a Router's Local
Addresses in OSPF Traffic Engineering (TE) Extensions", RFC Addresses in OSPF Traffic Engineering (TE) Extensions", RFC
5786, March 2010. 5786, March 2010.
[GEN-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, " General [GEN-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, " General
Network Element Constraint Encoding for GMPLS Controlled Network Element Constraint Encoding for GMPLS Controlled
Networks", work in progress: draft-ietf-ccamp-general- Networks", work in progress: draft-ietf-ccamp-general-
constraint-encode-04.txt, December 2010. constraint-encode-05.txt, May 2011.
[Lambda-Labels] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, " [RFC6205] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, " Generalized
Generalized Labels for Lambda-Switching Capable Label Labels for Lambda-Switching Capable Label Switching
Switching Routers", work in progress: draft-ietf-ccamp- Routers", work in progress: draft-ietf-ccamp-gmpls-g-694-
gmpls-g-694-lambda-labels-11.txt, January 2011. lambda-labels-11.txt, January 2011.
7.2. Informative References 7.2. Informative References
[WSON-Frame] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS [RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS and
and PCE Control of Wavelength Switched Optical Networks PCE Control of Wavelength Switched Optical Networks (WSON)",
(WSON)", work in progress: draft-ietf-ccamp-rwa-WSON- work in progress: draft-ietf-ccamp-rwa-WSON-Framework-
Framework-12.txt, February 2011. 12.txt, February 2011.
[WSON-Info] Y. Lee, G. Bernstein, D. Li, W. Imajuku, "Routing and [WSON-Info] Y. Lee, G. Bernstein, D. Li, W. Imajuku, "Routing and
Wavelength Assignment Information Model for Wavelength Wavelength Assignment Information Model for Wavelength
Switched Optical Networks", work in progress: draft-ietf- Switched Optical Networks", work in progress: draft-ietf-
ccamp-rwa-info-10.txt, March 2011. ccamp-rwa-info-12.txt, September 2011.
8. Authors' Addresses 8. Authors' Addresses
Fatai Zhang Fatai Zhang
Huawei Technologies Huawei Technologies
F3-5-B R&D Center, Huawei Base F3-5-B R&D Center, Huawei Base
Bantian, Longgang District Bantian, Longgang District
Shenzhen 518129 P.R.China Shenzhen 518129 P.R.China
Phone: +86-755-28972912 Phone: +86-755-28972912
skipping to change at page 9, line 43 skipping to change at page 9, line 43
Phone: (972) 509-5599 (x2240) Phone: (972) 509-5599 (x2240)
Email: ylee@huawei.com Email: ylee@huawei.com
Jianrui Han Jianrui Han
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
F3-5-B R&D Center, Huawei Base F3-5-B R&D Center, Huawei Base
Bantian, Longgang District Bantian, Longgang District
Shenzhen 518129 P.R.China Shenzhen 518129 P.R.China
Phone: +86-755-28972913 Phone: +86-755-28977943
Email: hanjianrui@huawei.com Email: hanjianrui@huawei.com
Greg Bernstein Greg Bernstein
Grotto Networking Grotto Networking
Fremont CA, USA Fremont CA, USA
Phone: (510) 573-2237 Phone: (510) 573-2237
Email: gregb@grotto-networking.com Email: gregb@grotto-networking.com
Yunbin Xu Yunbin Xu
 End of changes. 15 change blocks. 
52 lines changed or deleted 47 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/