1 / 10

Xihua Fu , Qilei Wang, Yuanlin Bao ZTE Corporation Ruiquan Jing, Xiaoli Huo China Telecom

RSVP-TE Signaling Extension for Explicit Control of LSP Boundary in MRN/MLN draft-fuxh-ccamp-boundary-explicit-control-ext-01.txt. Xihua Fu , Qilei Wang, Yuanlin Bao ZTE Corporation Ruiquan Jing, Xiaoli Huo China Telecom. Requirement for Explicit Control of LSP Boundary.

hila
Download Presentation

Xihua Fu , Qilei Wang, Yuanlin Bao ZTE Corporation Ruiquan Jing, Xiaoli Huo China Telecom

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. RSVP-TE Signaling Extension for Explicit Control of LSP Boundary in MRN/MLN draft-fuxh-ccamp-boundary-explicit-control-ext-01.txt Xihua Fu, Qilei Wang, Yuanlin Bao ZTE Corporation Ruiquan Jing, Xiaoli Huo China Telecom

  2. Requirement for Explicit Control of LSP Boundary • Selection of Server layer/Sub-layer • [RFC 4206] only describes a region boundary determination algorithm. • It needs to explicitly describe which server layer and/or sub-layer should be triggered.

  3. Requirement for Explicit Control of LSP Boundary • Selection/Creation of FA-LSP based on the Latency agreement between operator and its user. • Latency characteristic of each OTN FA-LSP is different. • The selection or creation of FA-LSP should base on the Latency agreement between operator and its client. • It needs to explicitly inform boundary nodes the latency agreement parameters.

  4. Requirement for Explicit Control of LSP Boundary • Configuration of Multi Stages Multiplexing • In following figure, the server layer and sub-layer information is not enough for data plane to know that ODU0 is mapped into ODU3 tunnel by ODU0-ODU1-ODU3 then ODU4. • It needs to explicitly indicates the multiplexing hierarchies (e.g., ODU0-ODU1-ODU3-ODU4) used for boundary node to configure it to the data plane and trigger one specific corresponding tunnel creation.

  5. The ERBO (Explicit Route Boundary Object) is introduced in PATH message It has ever been presented in 76th and 77th meeting in CCAMP and PCE. http://www.ietf.org/proceedings/76/slides/ccamp-28/ccamp-28.htm http://www.ietf.org/proceedings/77/slides/pce-13/pce-13_files/v3_document.htm It is used for the explicitly control hierarchy LSP creation. ERBO has the same format as the ERO. Explicit Route Boundary Control

  6. BOUNDARY_ATTRIBUTES • A new sub-object (BOUNDARY_ATTRIBUTES) is introduced into ERBO to carry the attributes associated with boundary nodes. • It follows an IPv4 or IPv6 or unnumbered interface ID sub-object in ERBO. • A list of attribute TLV can be inserted into ERBO, such as Server layer/Sub layer information, Multi Stages Multiplexing hierarchy information and latency characteristic.

  7. BOUNDARY_ATTRIBUTES • Server layer/sub layer attribute TLV and Multiplexing hierarchy attribute TLV is shown below. • Server layer attribute TLV indicates the server layer and sub layer to be triggered . • Multiplexing hierarchy attribute TLV indicates the Multi Stage Multiplexing hierarchy information.

  8. BOUNDARY_ATTRIBUTES • Latency attribute TLV • This sub-TLV include minimum, maximum, average and variation latency performance parameters which the FA-LSP must meet.

  9. Procedure of Signaling • Source node sends RSVP-TE path message with ERBO which indicates one or multiple pairs of boundary nodes and some related attributes. • Intermediate node will extract a pair of boundary nodes from ERBO and related attribute. • It triggers the FA-LSP creation or selection according to the BOUNDARY ATTRIBUTE in ERBO.

  10. Next steps • Refine the document according to the feedback of meeting and mailing list.

More Related