1 / 9

E-NNI Routing 2.0: Advertisement of Local Adaptation and Connection Type

E-NNI Routing 2.0: Advertisement of Local Adaptation and Connection Type. February 4, 2008 oif2008.068.00 Lyndon Ong Ciena. G.7715.1 Requirements. G.7715.1 Text Local connection type

rock
Download Presentation

E-NNI Routing 2.0: Advertisement of Local Adaptation and Connection Type

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. E-NNI Routing 2.0: Advertisement of Local Adaptation and Connection Type February 4, 2008 oif2008.068.00 Lyndon Ong Ciena

  2. G.7715.1 Requirements • G.7715.1 Text • Local connection type • Local connection type: This attribute identifies whether the local SNP represents a TCP, CP, or can be flexibly configured as either a TCP or a CP. Figure 4 illustrates this attribute. • Local adaptations supported • Local client adaptations supported: This attribute represents the set of client layer adaptations supported by the TCP associated with the local SNPP. This is only applicable when the local SNP represents a TCP or can be flexibly configured as either a TCP or CP.

  3. G.7715.1 Figure 4

  4. Standards Support for Local Connection Type • Does not appear to be addressed yet in standards • Previous OIF contributions going back to 2003 proposed advertisement of “transit/sync connectivity” • Never adopted by OIF, ITU or IETF • Need to revisit proposals on this

  5. Possible Scenario of Use for Local Connection Type • Certain paths may be prohibited Carrier Network N-2 Core Domain 1 N-7 I-NNI Core Domain 2 Node-A N-1 N-3 E-NNI N-4 N-6 Node-Z1 I-NNI Domain A E-NNI E-NNI Domain Z1 N-5 N-8 E-NNI E-NNI Node-B Link C-1 LinkC-2 Node-C2 Node-C1 Domain B Domain C Allowed NOT Allowed

  6. Standards Status on Local Adaptation Supported • IETF ASON Routing Extensions draft • Proposes to use multiple Interface Switching Capability Descriptors to indicate adaptation and termination • The Interface Switching Capability Descriptor (ISCD) TE Attribute [RFC4202] identifies the ability of the TE link to support cross- connection to another link within the same layer and the ability to use a locally terminated connection that belongs to one layer as a data link for another layer (adaptation capability). However, the information associated to the ability to terminate connections within that layer (referred to as the termination capability) is embedded with the adaptation capability. • ability to describe adaptations based on switching capability values

  7. ISCD • +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Switching Cap | Encoding | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Switching Capability-specific information | | (variable) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The Switching Capability (Switching Cap) field contains one of the following values: 1 Packet-Switch Capable-1 (PSC-1) 2 Packet-Switch Capable-2 (PSC-2) 3 Packet-Switch Capable-3 (PSC-3) 4 Packet-Switch Capable-4 (PSC-4) 51 Layer-2 Switch Capable (L2SC) 100 Time-Division-Multiplex Capable (TDM) 150 Lambda-Switch Capable (LSC) 200 Fiber-Switch Capable (FSC)

  8. Standards Status (alternative) • IETF MLN/MRN draft • Defines a new IACD sub-object for adaptation Therefore, within multi-region networks, the advertisement of the so-called adaptation capability to terminate LSPs (not the interface capability since the latter can be inferred from the bandwidth available for each switching capability) provides critical information to take into account when performing multi-region path computation. This concept enables a node to discriminate the remote nodes (and thus allows their selection during path computation) with respect to their adaptation capability e.g. to terminate LSPs at the PSC or LSC level. The interface switching capability descriptor (IACD) provides the information for the forwarding/switching) capability only.

  9. IACD • 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Switching Cap | Encoding | Switching Cap | 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Adaptation Capability-specific information | | (variable) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Where: - first Switching Capability (SC) field (byte 1): lower switching capability (as defined for the existing ISC sub-TLV) - first Encoding field (byte 2): as defined for the existing ISC sub-TLV - second SC value (byte 3): upper switching capability (new) - second encoding value (byte 4): set to the encoding of the available adaptation pool and to 0xFF when the corresponding SC value has no access to the wire (i.e. there is no ISC sub-TLV for this upper switching capability)

More Related