1 / 9

MLN/MRN Routing Considerations for OTN

MLN/MRN Routing Considerations for OTN. Khuzema Pithewan ( kpithewan@infinera.com ) Rajan Rao ( rrao@infinera.com ) Date: Jul 30 th 2012. OSPF-TE extensions for OTNv3 support (draft-ietf-ccamp-gmpls-ospf-g709v3).

melosa
Download Presentation

MLN/MRN Routing Considerations for OTN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MLN/MRN Routing Considerations for OTN Khuzema Pithewan (kpithewan@infinera.com) RajanRao (rrao@infinera.com) Date: Jul 30th 2012

  2. OSPF-TE extensions for OTNv3 support(draft-ietf-ccamp-gmpls-ospf-g709v3) ISCD Format as defined by the extension requires available bandwidth for a signal Type + Hierarchy in a TLV in SCSI area. SCSI can have multiple of these TLVs.

  3. RFC 6001 : GMPLS Protocol Extensions for MLN/MRN RFC 6001 defines IACD to advertize the capacity available between 2 ISCDs (belong to 2 different layer/regions).

  4. Problem for multi-layer technology like OTN w.r.t. MRN • RFC 6001 assumes SwitchCap and Encoding type is good enough to represent the bandwidth associated with an interface (i.e. ISCD) • While OTN extensions as defined today, captures more than one layer in one ISCD. • IACD must associate to one of the layer in OTN ISCD.

  5. What is required to connect OTN Layer with other region (MRN)? • A Layer in OTN (SwCap=OTN-TDM, Encoding=G.709 ODUk), is identified by • Signal Type • Hierarchy • TSG • Terminating/Switching • An IACD must carry above information to unambiguously identify a layer in OTN MultiLayer interface

  6. How do we connect : Option -1 Considering current definition of the SCSI for OTN extension for OSPF, IACD’s Adjustment Capability specific information for OTN needs to carry all the information to correctly identify the layer in the OTN TE Link ISCD. IACD (As defined by RFC 6001) Adjustment Capability-specific information for OTN New Proposal

  7. Option -2 • Make a minor change to OTN Extension of OSPF such that one ISCD identifies a layer. • Define a separate construct for information which in conjunction with SwCapand EncType identifies a layer. • LayerIDConsruct { • Signal Type • Hierarchy • TSG • Terminating/Switching Flag • } • Use the *same* construct in IACD that has one of the region as OTN.

  8. Option -2 (Contd) • Break currently defined TLVs in SCSI in 2 parts. • Layer ID TLV • BW TLV Layer ID TLV can be used as it is IACD’s Adjustment Capability-specific information

  9. Next Steps • Workgroup feedback on the options • Submission of new draft

More Related