PCEP Extensions in support of WSON Signal Compatibility Con

PCEP Extensions in support of WSON Signal Compatibility Con - Description

. <draft-lee-pce-wson-signal-compatibility-00.txt>. Young Lee . ylee@huawei.com. . Huawei. Greg Bernstein . gregb@grotto-networking.com. Grotto Networking. Motivation/Background. Signal compatibility is an essential . ID: 426330 Download Presentation

54K - views

PCEP Extensions in support of WSON Signal Compatibility Con

. <draft-lee-pce-wson-signal-compatibility-00.txt>. Young Lee . ylee@huawei.com. . Huawei. Greg Bernstein . gregb@grotto-networking.com. Grotto Networking. Motivation/Background. Signal compatibility is an essential .

Similar presentations


Download Presentation

PCEP Extensions in support of WSON Signal Compatibility Con




Download Presentation - The PPT/PDF document "PCEP Extensions in support of WSON Signa..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.



Presentation on theme: "PCEP Extensions in support of WSON Signal Compatibility Con"— Presentation transcript:

Slide1

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

Slide2

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>

Slide3

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)

Slide4

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)

Slide5

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)

Slide6

Example Attribute: Modulation Type List sub-TLV

S: Standard (1); Vendor Specific (0)1 : optical tributary signal class NRZ 1.25G2: optical tributary signal class NRZ 2.5G3: optical tributary signal class NRZ 10G4: optical tributary signal class NRZ 40G5: optical tributary signal class RZ 40GI: Input Mod Format (1) Output (0)

Slide7

Summary & Next Steps

Refine requirements.

Adopt as a PCE WG document

Slide8

Slide9

Slide10