Internet DRAFT - draft-rao-ccamp-otn-mlnmrn-ospfte-ext
draft-rao-ccamp-otn-mlnmrn-ospfte-ext
INTERNET-DRAFT Khuzema Pithewan
Intended Status: Standard Track Rajan Rao
Infinera
Expires: February 2, 2013 August 1, 2012
OSPF-TE extensions for MLNMRN based on OTN
draft-rao-ccamp-otn-mlnmrn-ospfte-ext-00.txt
Abstract
This document specifies OSPF extensions for multi-layer/multi-region
where one of the regions is OTN.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Khuzema Pithewan Expires February 2, 2013 [Page 1]
INTERNET DRAFTdraft-rao-ccamp-otn-mlnmrn-ospfte-ext-00.txtAugust 1, 2012
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. OTN Layer Identification . . . . . . . . . . . . . . . . . . . 3
3. Interface Adjustment Capability Extensions for OTN . . . . . . 4
4 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
6 Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
Khuzema Pithewan Expires February 2, 2013 [Page 2]
INTERNET DRAFTdraft-rao-ccamp-otn-mlnmrn-ospfte-ext-00.txtAugust 1, 2012
1 Introduction
This document specifies the OSPF extensions required to work in
multi-region networks involving OTN. The specification is based on
the requirement as specified in RFC 5212. As per the said RFC, ISCD
characterizes the information associated to one or more network
layers. Same RFC also says that the information about the adjustment
capabilities of the nodes in the network allow the path computation
process to select an end-to-end multi-layer or multi- region path
that includes links with different switching capabilities joined by
LSRs that can adapt (i.e., adjust) the signal between the links. By
inference, information about the adjustment capabilities should be
able to identify a layer in ISCD, if ISCD specifies more than one
layer.
RFC6001 specifies how to advertise adjustment capabilities between
two switching regions. IACD definition has provision to extend it for
a specific technology through Adjustment Capability Specific
information (ACSI) field, if required. ACSI field can be used to
identify a layer in the multi-layer ISCD. OTN being defined as multi-
layer ISCD, the corresponding IACD needs to be extended to be able to
carry layer identification so as to enable multi-layer/multi-region
path computation.
2. OTN Layer Identification
[GMPLS-OTN-OSPF] defines attributes that identifies a layer in multi-
layer OTN ISCD. These attributes are part of Bandwidth sub-TLV in
Switch capability specific information of ISCD. These attributes are
reproduced here for completeness sake.
* Signal Type: Layer for which bandwidth is being advertised.
* Hierarchy : also called as multiplexing branch that specifies all
the layers between server layer and signal type.
* TSG : Time Slot Granularity
Khuzema Pithewan Expires February 2, 2013 [Page 3]
INTERNET DRAFTdraft-rao-ccamp-otn-mlnmrn-ospfte-ext-00.txtAugust 1, 2012
3. Interface Adjustment Capability Extensions for OTN
RFC6001 defines IACD sub-TLV as follows. Please refer to the RFC for
definition of individual fields of the sub-TLV.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lower SC | Lower Encoding| Upper SC | Upper Encoding|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max LSP Bandwidth at priority 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max LSP Bandwidth at priority 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max LSP Bandwidth at priority 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max LSP Bandwidth at priority 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max LSP Bandwidth at priority 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max LSP Bandwidth at priority 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max LSP Bandwidth at priority 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max LSP Bandwidth at priority 7 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Adjustment Capability-specific information |
| (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Adjustment Capability-specific information abbreviated as ACSI
henceforth for OTN G.709v3 carries LayerID Sub-TLV which is defined
as follows
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 (LayerID TLV) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signal type | Num of stages |TSG | Res | Stage#1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stage#2 | ... | Stage#N | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The definition & meaning of fields used in the above sub-TLV is same
as in bandwidth sub-TLV of ISCD as defined in [GMPLS-OTN-OSPF]. This
LayerID sub-TLV is applicable only when one of the regions is OTN,
which means either lower or upper SC and Encoding type MUST have
Switch Cap as OTN-TDM and encoding type as G.709 ODUk. The 8
Khuzema Pithewan Expires February 2, 2013 [Page 4]
INTERNET DRAFTdraft-rao-ccamp-otn-mlnmrn-ospfte-ext-00.txtAugust 1, 2012
priorities of the BW as defined in main IACD structure, is adjustment
capability between the two regions where one of the region is
identifies by LayerID sub-TLV.
4 Procedure
A node advertising IACD for the bandwidth between a non-OTN interface
and an OTN interface MUST include the Layer ID TLV as part of ACSI as
defined above. For multi-region path computation, the path computing
node MUST look at the LayerID sub-TLV (in ACSI part of IACD) if
lower/upper SC and encoding type is OTN-TDM and G.709 ODUk
respectively to identify the layer in OTN ISCD.
5 IANA Considerations
TBD
6 Security Considerations
TBD
7 References
[RFC5212] K. Shiomoto, Papadimitriou, D.,JL. Le Roux, Vigoureux, M.,
Brungard, D., "Requirements for GMPLS-Based Multi-Layer
and Multi-Region Networks (MLN/ MRN)",RFC 5212, July 2008.
[RFC6001] Papadimitriou, D., Vigoureux, M., Shiomoto, K., Brungard,
D., and JL. Le Roux, "Generalized MPLS (GMPLS) Protocol
Extensions for Multi-Layer and Multi-Region Networks
(MLN/MRN)", RFC 6001, October 2010.
[GMPLS-OTN-OSPF] Traffic Engineering Extensions to OSPF for
Generalized MPLS (GMPLS)
8 Authors' Addresses
Khuzema Pithewan
Infinera
140 Caspian Ct., Sunnyvale, CA 94089
Email: kpithewan@infinera.com
Rajan Rao
Infinera
140 Caspian Ct., Sunnyvale, CA 94089
Email: rrao@infinera.com
Khuzema Pithewan Expires February 2, 2013 [Page 5]