datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

OSPF-TE extensions for MLNMRN based on OTN
draft-rao-ccamp-mlnmrn-otn-ospfte-ext-03

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-10-19
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

INTERNET-DRAFT                                          Khuzema Pithewan
Intended Status: Standard Track                                Rajan Rao
                                                                Infinera
Expires: April 20, 2014                                 October 17, 2013

              OSPF-TE extensions for MLNMRN based on OTN 
              draft-rao-ccamp-mlnmrn-otn-ospfte-ext-03.txt

Abstract

   This document specifies OSPF extensions for multi-layer/multi-region
   where one of the regions is multi-layer e.g. OTN, SONET/SDH.

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) 2013 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 April 20, 2014                 [Page 1]
INTERNET DRAFTdraft-rao-ccamp-mlnmrn-otn-ospfte-ext-03.txt  Oct 17, 2013

   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 Layer Identification . . . . . . . . . . . . . . . . . . . . . .  3
   3 OTN Layer ID . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4 SONET/SDH Layer Identification . . . . . . . . . . . . . . . . .  6
   5 Procedure  . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   6 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     6.1. Ethernet and OTN  . . . . . . . . . . . . . . . . . . . . .  7
     6.2. OTN and FlexGrid  . . . . . . . . . . . . . . . . . . . . .  7
     6.3. OTN and SONET/SDH . . . . . . . . . . . . . . . . . . . . .  8
     6.4. OTN and OTN . . . . . . . . . . . . . . . . . . . . . . . .  8
   7 IANA Considerations  . . . . . . . . . . . . . . . . . . . . . .  8
   8 Security Considerations  . . . . . . . . . . . . . . . . . . . .  9
   9 References . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . .  9

 

Khuzema Pithewan         Expires April 20, 2014                 [Page 2]
INTERNET DRAFTdraft-rao-ccamp-mlnmrn-otn-ospfte-ext-03.txt  Oct 17, 2013

1 Introduction

   In order to do end-to-end path computation, where a path may involve
   more than one region and part of single routing domain, TE Links
   connecting the two regions need to have bandwidth capacity advertised
   for the switch that connects the two regions. This document specifies
   the OSPF extensions that are required if any of the region is a
   multi-layer network. 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. 

[include full document text]