1 / 7

PCEP Extensions in support of WSON Signal Compatibility Constraints

PCEP Extensions in support of WSON Signal Compatibility Constraints. <draft-lee-pce-wson-signal-compatibility-00.txt>. Young Lee ylee@huawei.com Huawei Greg Bernstein gregb@grotto-networking.com Grotto Networking. Motivation/Background.

mahola
Download Presentation

PCEP Extensions in support of WSON Signal Compatibility Constraints

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. PCEP Extensions in support of WSON Signal Compatibility Constraints <draft-lee-pce-wson-signal-compatibility-00.txt> Young Lee ylee@huawei.com Huawei Greg Bernstein gregb@grotto-networking.com Grotto Networking

  2. Motivation/Background • Signal compatibility is an essential path computation constraint in path computation of WSON networks where network elements can be limited to processing WSON signals with specific characteristics and attributes. • Signal compatibility framework has been addressed in the CCAMP WG as a part of WSON work items: <draft-bernstein-ccamp-wson-compatibility-01.txt>

  3. Signal Compatibility Constraints • On a high-level the following network element information would be required for the path computation element (PCE) to be able to compute a constrained path that satisfies signal compatibility and processing constraints: • Input Compatibility: the type of signals it can receive (modulation types, rate, FEC types) • Regeneration Capability: the types of processing/enhancement it can perform (1R, 2R, 3R) • The types of conversions it can perform (modulation types, FEC types) • Output Format: the type of signals it can transmit (modulation types, rate, FEC types)

  4. Requirement #1 • When requesting a path computation (PCReq) to PCE, the PCC should be able to indicate the following: • The acceptable signal attributes at the transmitter (at the source): (i) modulation types; (ii) FEC types • The acceptable signal attributes at the receiver (at the sink): (i) modulation types; (ii) FEC types • The GPID type of an LSP (This might have already been fulfilled in PCEP enhancements for GMPLS)

  5. Requirements #2 • The PCE should be able to respond (PC Rep) to the PCC with the following: • The conformity of the requested optical characteristics associated with the resulting LSP with the source, sink and NE along the LSP. • Additional LSP attributes modified along the path (e.g., modulation format change, etc.) • Special node processing with the resulting LSP (e.g., regeneration point)

  6. Example Attribute: Modulation Type List sub-TLV • S: Standard (1); Vendor Specific (0) • 1 : optical tributary signal class NRZ 1.25G • 2: optical tributary signal class NRZ 2.5G • 3: optical tributary signal class NRZ 10G • 4: optical tributary signal class NRZ 40G • 5: optical tributary signal class RZ 40G • I: Input Mod Format (1) Output (0)

  7. Summary & Next Steps • Refine requirements. • Adopt as a PCE WG document 

More Related