1. ===!"§ Deutsche Telekom ASON support for NG-SDH Comments and questions on TILAB contribution Georg Lehr, T-Systems

2. Page 1 NOBEL WP4 meeting December 1st, 2004 ===!"§ Deutsche Telekom Chapter 4: ASON support for GFP/LCAS/VCAT Benefits of ASON support for interaction... as I understood the paper The UNI interface, besides the classical setup and teardown primitives, should allow modification of the bandwidth allocated to a call. It is charge of the network, according to its VC granularity, to choose the number of VCs that are necessary to fulfil the client request. In case of devices lacking in the signalling interface, the egress node could implement an automatic trigger mechanism that, monitoring the amount of traffic received from the client device, adds or removes VCs to the corresponding VCG. ASTN Signalling can support bidirectional LSP setup by EMS/NMS. Resilience: – control plane can perform the routing, but routing protocols need to be enhanced by information regarding delay. On signalling level, information must be provided to correlate the connections to the VCG – CP resilience mechanisms can be added to the single connections (restoration, protection?)

3. Page 2 NOBEL WP4 meeting December 1st, 2004 ===!"§ Deutsche Telekom Chapter 4: ASON support for GFP/LCAS/VCAT Benefit: bandwidth modification Domain 2 SDH network Ethernet clients UNI Domain 1 SDH network Domain 3 SDH network UNI Ethernet client Ethernet client Time Traffic Set up and tear down connections according to load at the UNI

4. Page 3 NOBEL WP4 meeting December 1st, 2004 ===!"§ Deutsche Telekom Chapter 4: ASON support for GFP/LCAS/VCAT Bidirectional LSP setup Ingress node Ingress node Intermediate node i Intermediate node j Intermediate node j Egress node Path Resv LCAS ADD LCAS OK LCAS EOS LCAS ADD LCAS OK LCAS EOS IngressEgress node NMS set up soft permanent LSP

5. Page 4 NOBEL WP4 meeting December 1st, 2004 ===!"§ Deutsche Telekom Chapter 4: ASON support for GFP/LCAS/VCAT Bandwidth Modification over UNI Ingress node Ingress node Intermediate node i Intermediate node j Intermediate node j Egress node Path Resv LCAS ADD LCAS OK LCAS EOS LCAS ADD LCAS OK LCAS EOS IngressEgress node UNI UNI signaling ?

6. Page 5 NOBEL WP4 meeting December 1st, 2004 ===!"§ Deutsche Telekom Conclusions valuable input: chance to develop innovative functionality in NOBEL plans to also consider UNI bandwidth modification? impact of GFP? relationship to UNI TF ?

7. Page 6 NOBEL WP4 meeting December 1st, 2004 ===!"§ Deutsche Telekom Open issues how to notify LCAS capability – within the carrier: ingress to egress (routing/management) – Interdomain ingress (Operator A) – egress (Operator B) Multilayer issues where the LCAS functionality is not at the edge is GFP an issue (Protocol agnostic interface) ? charging diverse routing delay / advertisement of the delay budget ?

8. Page 7 NOBEL WP4 meeting December 1st, 2004 ===!"§ Deutsche Telekom LCAS capable nodeEthernet node