ccamp wg, ietf 79th, beijing, china draft-zhang-ccamp-gmpls-evolving-g709-06.txt gmpls signaling...

7
CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-evolving-g709-06.txt GMPLS Signaling Extensions for the Evolving G.709 OTN Control Fatai Zhang <[email protected]> Guoying Zhang <[email protected]> Sergio Belotti <sergio.belotti@alcatel- lucent.it> Daniele Ceccarelli <[email protected]>

Upload: frank-webster

Post on 16-Jan-2016

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-evolving-g709-06.txt GMPLS Signaling Extensions for the Evolving G.709 OTN Control Fatai Zhang

CCAMP WG, IETF 79th, Beijing, China

draft-zhang-ccamp-gmpls-evolving-g709-06.txt

GMPLS Signaling Extensions for the Evolving G.709 OTN Control

Fatai Zhang <[email protected]>

Guoying Zhang <[email protected]>

Sergio Belotti <[email protected]>

Daniele Ceccarelli <[email protected]>

Page 2: CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-evolving-g709-06.txt GMPLS Signaling Extensions for the Evolving G.709 OTN Control Fatai Zhang

Authors/Contributors

• Fatai zhang (@Huawei)• Guoying Zhang (@CATR)• Sergio Belotti (@Alcatel-Lucent)• Daniele Ceccarelli (@Ericsson)• Yi Lin (@Huawei)• Yunbin Xu (@CATR)• Pietro Grandi (@Alcatel-Lucent)• Diego Caviglia(@Ericsson)

Page 3: CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-evolving-g709-06.txt GMPLS Signaling Extensions for the Evolving G.709 OTN Control Fatai Zhang

Changes from Version 05

• Alignment with [OTN-FWK] and [OTN-INFO] drafts

– Some information is moved to [OTN-FWK] and [OTN-INFO] to avoid reduplicate description

• No significant change is made in this version

Page 4: CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-evolving-g709-06.txt GMPLS Signaling Extensions for the Evolving G.709 OTN Control Fatai Zhang

Removing of Reduplicate Text • The overview of mapping & multiplexing structure

is removed since it has been described in [OTN-FWK]

• The information model of ODU label and TPN is moved to [OTN-INFO]

• The data plane backward compatibility is moved to [OTN-FWK]– Explained in the [OTN-FWK] presentation

Page 5: CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-evolving-g709-06.txt GMPLS Signaling Extensions for the Evolving G.709 OTN Control Fatai Zhang

Open Discussion: Relationship between Label and TPN

• Put TPN into ODU label object or use a separate TPN object?

……ODU3 link

BA

• More flexible for variant cases:

• TPN is allocates by DP (e.g. AutoMSI (deprecated in 2009) was used for the legacy equipments)

• TPN is allocated by MP • TPN is allocated by CP

• Saving bits and make the message more compact

• Logically reasonable if TPN is allocated by CP

Label: indicate the selected TSs

Label (TS) = 1,2,5,6TPN = 2

TPN: a port number for the selected TSs

Decoupling label and TPN Combining label and TPN

OR

Page 6: CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-evolving-g709-06.txt GMPLS Signaling Extensions for the Evolving G.709 OTN Control Fatai Zhang

Open Discussion: Multi-stage Multiplexing

ODU3 Link

ODU2 Connection

ODU0 Connection

ODU3 LinkA B C D E

2-stage multiplexing

2-stage demultiplexing

ODU2 Cross-connectODU0 is NOT visible

• ODU2 cross-connects between B and D in the Data Plane (i.e. ODU2 trail) MUST be created because node C doesn’t support ODU0

• The path of ODU0 is A-B-D-E, and node C only performs ODU2 cross-connection and is not aware of the ODU0

• ODU2 connection (B-C-D) should be treated as Tunnel for the ODU0– The creation of ODU0 and ODU2 Tunnel by CP is MLN stuff [RFC4206] and [RFC4206bis].

How to create ODU2 trail for ODU0 by CP (RSVP-TE)?We can not use ODU0 TP or label info to request ODU2 trail.It should comply with the principle of H-LSP (MLN stuff).

Page 7: CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-evolving-g709-06.txt GMPLS Signaling Extensions for the Evolving G.709 OTN Control Fatai Zhang

Next Steps

• Adopt it as a WG document– Significant agreement have been achieved and quite

stable for quite long time

• Put TPN into the label object if the meeting agrees

• Refine it based on the feedback from the meeting or mailing list