Presentation

Start Time Duration Information

0 15:50 5

Title: Administrivia - WG Status - Reporting on WG drafts not being presented

Presenter: Chairs

1 15:55 10

Title: A framework and YANG model for Management and Control of microwave and millimeter wave interface parameters

Draft: https://tools.ietf.org/html/draft-ietf-ccamp-microwave-framework-02

Draft: https://tools.ietf.org/html/draft-ietf-ccamp-mw-yang-02

Presenter: Amy Ye

Daniele Ceccarelli: we have decided to close the DT.

They have done a great job, had an hackathon in Prague, all the deliverables have been adopted by the WG. They are stable and close to the WG LC. Closing the DT doesn't mean we are not accepting any more contributions on microwave. I hope it was just the starting point.

Amy Ye: we are also considering for next step to visit the topology augment for microwave.

2 16:05 8

Title: OTN Topology YANG model and OTN tunnel model

Draft: https://tools.ietf.org/html/draft-ietf-ccamp-otn-topo-yang-02

Draft: https://tools.ietf.org/html/draft-sharma-ccamp-otn-tunnel-model-01

Presenter: Zheyu Fan

Fatai Zhang: Besides the path computation draft, this work also need to align with the TE tunnel draft.

Zheyu Fan: Yes, will do that.

3 16:13 7

Title: WSON Topology YANG models and WSON tunnel model

Draft: https://tools.ietf.org/html/draft-ietf-ccamp-wson-yang-08

Draft: https://tools.ietf.org/html/draft-lee-ccamp-wson-tunnel-model-02

Presenter: Young Lee

(Regarding the first draft)

Dieter Beller: There is no definition in the draft regarding the channel numbers. I think you are defining those in the wavelength range type. What are the channel numbers used in the draft, how are they defined?

Young Lee: we can talk offline.

Dieter: I have also a few questions regarding the grouping use some link attributes and there are some issues that we should discuss. We can take that offline.

Young Lee: OK.

Fatai Zhang: In your next step, you said you are going to add some impairment data on topology, this kind of information may depend on the encoding of the impairment. The encoding of impairment is individual draft and may take much time to move forward for the encoding draft. So if you are going to add this kind of impairment information to WSON topology, it needs to take much longer time.

Young Lee: we can also move without this and later we think about augment. It may be better consistent with GMPLS approach.

Daniele Ceccarelli: like what we did in WSON. Maybe you follow that as impairment-free and impairment-aware.

Young Lee: OK. No problem.

(Regarding the second draft)

Young Lee: are you going to put it in the list?

Daniele Ceccarelli: we are going to take this work to the list. we want to speed up the YANG models in this WG, including WSON/OTN/Flexi-grid/Microwave. This is our priority because the market window is open now and we need to hurry up.

4 16:20 6

Title: Transport Northbound applicability statment and use cases

Draft: https://tools.ietf.org/html/draft-tnbidt-ccamp-transport-nbi-analysis-uc1-00

Presenter: Italo Busi

(combined with the next topic)

5 16:26 6

Title: Analysis of Transport North Bound Interface Use Case 3

Draft: https://tools.ietf.org/html/draft-tnbidt-ccamp-transport-nbi-analysis-uc3-00

Presenter: Italo Busi

Daniele Ceccarelli: I have one question on the plug-id, dose it allow to understand whether the relationship between the two topologies is peering or client-server?

Italo Busi: The link is to be peer. By definition, the inter-domain link is the same layer.

Fatai Zhang: I would like to suggest the authors or the DT to take Igor's draft as input, because that draft also talks about use cases and describe how to use the YANG models for the transport network. That's a good foundation for the DT to take as an input.

Italo Busi: Yes, we will take that as input.

6 16:32 10

Title: A YANG Data Model for Client-layer Topology, Client-layer Tunnel and Optical Transport Network Client Signals;

Draft: https://tools.ietf.org/html/draft-zheng-ccamp-client-topo-yang-01

Draft: https://tools.ietf.org/html/draft-zheng-ccamp-client-tunnel-yang-01

Draft: https://tools.ietf.org/html/draft-zheng-ccamp-otn-client-signal-yang-01

Presenter: Haomian Zheng

Amy Ye: this is very useful work especially for Ethernet which is a very common client-server service even in the microwave. In our case, we were deploying the QinQ Ethernet model and Ethernet service. So I want to know whether this model is addressing that or is going to address that in the future.

Haomian Zheng: currently there is no QinQ stuffs, but we can integrate that in the future. I agree with you that microwave is a potential server to the Ethernet service.

Daniele Ceccarelli: as proposed on the mailing list, my suggestion is to try to see what is the generalized part and bring it to TEAS. Then do technology-specific extensions in CCAMP.

Haomian Zheng: I agree with this approach. This work is augmenting the TE generic models. The scope would still be within TE.

Young Lee: we have a L1CSM model. So you do not have to do everything here, but focus on Ethernet.

Haomian Zheng: this work would be at the network side and nothing to do with customer service. We assume the work to be MPI while the LxSM and L1csm is applied on CMI. There is a terminology issue that both of them are called service model. We would like to hear from the WG if there is a better name.

Italo Busi: For QinQ, if it is a QinQ point-to-point TE tunnel, it is an Ethernet tunnel, which is supported here. If it is a connection-less QinQ that we have not analyzed that option. So it depends on which type of QinQ implementation you are looking at. This model is for MPI, it is not for CMI, where L1CSM is for CMI. So you need to translate the L1CSM requested to the MDSC into this command that goes to the PNC. We need to align with the "client".

Jeff Tantsura: IEEE 802.1 is working on Ethernet and QinQ, so we should align with those models. Need to align with I2RS.

Haomian Zheng: OK.

7 16:42 10

Title: A Yang Data Model for L1 Connectivity Service Model (L1CSM)

Draft: https://tools.ietf.org/html/draft-fioccola-ccamp-l1csm-yang-00

Presenter: Giuseppe Fioccola

David Sinicrope: Definitely need to send an LS to MEF. Dave Martin from Nokia is driving this work in MEF.

Jeff Tantsura: LS to MEF have been brought a few times this week, not only on L1VPN but also on life cycle management. So from IAB perspective, we are going to make it.

Sergio Belotti: Dave is aware of my contribution to this work, but there is no official documentation from MEF. I agree that an LS to MEF is needed.

Young Lee: You need an LS only if this is a WG document, otherwise there is no point.

Daniele Ceccarelli: You are right, and the IETF should be aware of this work going on in MEF, but only some companies are allowed to reach the MEF document.

David Sinicrope: we may need to use the informal approach to MEF, and make them aware of such work to trigger an official liaison.

Daniele Ceccarelli: the problem in MEF is that the document is not available to everyone.

David Sinicrope: we can use the informal channel to ask MEF to send LS to CCAMP. I don't think we should take a WG document as the work is on MEF.

Deborah A Brungard: Can do informally, we would need a formal liaison from them. IETF's work is open. They can access this document. If MEF's participants find this work is interesting, they can send a liaison to us. It is not for us to hear that MEF (a closed group) may be working on something and we send them a liaison.

Fatai Zhang: what do you mean by L1 here? ODU pipe or also include such as WSON?

Giuseppe Fioccola: it is basically connection. We need to make some examples about that in next step.

8 16:52 5

Title: Flexigrid and flexigrid media channel YANG models

Draft: https://tools.ietf.org/html/draft-vergara-ccamp-flexigrid-yang-05

Draft: https://tools.ietf.org/html/draft-vergara-ccamp-flexigrid-media-channel-yang-00

Presenter: Young Lee

Daniele Ceccarelli: What is the issue with terminology?

Young Lee: media-channel, may be called flexi-grid TE tunnel.

Dieter Beller: regarding the available-operational-mode attribute, it should be read-only.

Young Lee: you are right. It should be read-only.

Daniele Ceccarelli: as I said, our priority is on YANG models. It's in the pipe.

9 16:57 10

Title: GMPLS Routing and Signaling Framework for Flexible Ethernet (FlexE)

Draft: https://tools.ietf.org/html/draft-izh-ccamp-flexe-fwk-04

Presenter: Loa Andersson

David Sinicrope: There was a liaison to CCAMP months ago from BBF letting CCAMP know they are doing a similar work. There has been a lot of discussion on what is the applicability of GMPLS to FlexE and there has been a lot of confusion. If you adopt this document it would be good to send a liaison to BBF saying this is the applicability of GMPLS.

Loa Andersson: Fast protection is an applicability

David Sinicrope: The selection of FlexE capable links at the client layer is new, what I’ve seen in other sections is the signaling of some FlexE info that allows creating a FlexE path at the FlexE layer. What is the label in that cases? Is there FlexE switching?

Loa Andersson: what we are communication is link capabilities that a path requires. That’s why we need the routing system.

Qilei Wang: FlexE can be used to carry not only MPLS but also other types of traffic.

David Sinicrope: What is the relationship between the LSP set up with GMPLS and the FlexE that is setup underneath? And how do they relate?

Loa Andersson: What is setup in the FlexE layer is announced in the upper layer routing system. The routing system know what is the capability of the links (via TE parameters).

Gabriele Galimberti: Do you think to extend the LSP also to WDM networks? I.e. a UNI interfaces between FlexE and WDM? In other words, can the shim between the two nodes be a WSM network?

Loa Andersson: Yes, but need to be verified.

Dieter Beller: From the draft it seems there is FlexE switch, please correct it. There is also a locking mechanism defined that allows changing the bandwidth of a group. This is not aligned with the FlexE implementation agreement.

10 17:07 10

Title: GMPLS Routing and Signaling Framework for B100G & GMPLS Signaling Extensions for B100G

Draft: https://tools.ietf.org/html/draft-merge-ccamp-otn-b100g-fwk-02

Draft: https://tools.ietf.org/html/draft-merge-ccamp-b100g-signalling-00

Presenter: Qilei Wang

11 17:17 8

Title: OSPF Extensions for the GMPLS Control of OTN B100G Network

Draft: https://tools.ietf.org/html/draft-merge-ccamp-otn-b100g-routing-ext-00

Presenter: Zheyu Fan

Daniele Ceccarelli: Since you are defining a new switching capability please consider using the Generalized SCSI.

12 17:25 10

Title: Interworking of GMPLS Control and Centralized Controller System

Draft: https://tools.ietf.org/html/draft-zheng-ccamp-gmpls-controller-inter-work-00

Presenter: Haomian Zheng

Dieter Beller: useful work as defines how the ACTN components interact with GMPLS. Answering first of the 4 questions in the slides. Question1 (how GMPSL helps report topology to controller): The PNC can listen to the IGP.

Haomian Zheng: Different people might have different understanding, better describe it.

Daniele Ceccarelli: Agree on usefulness of the work. What is the relationship with T-NBI design team?

Haomian Zheng: This is mode device interaction, not NBI.

Italo Busi: We look at the NBI, we don’t care about how the PNC translates the actions into device language.

Young Lee: Are you also scoping PCEP when you say GMPLS?

Haomian Zheng: PCEP is classified as centralized soluiton, not as GMPLS.

Young Lee: please consider alignment with PCE WG on this.

Julien Meuric (remote): It seems to me there is much overlap with existing PCE documents like RFC4655. Agree with Young.

Sergio Belotti: Support the work. It opens the door to work on the SBI.

Rudiger Kunze: What problem do we want to solve in addition to what we have in PCE WG? Maybe I2RS is the right way to go on.

13 17:35 8

Title: Signaling extensions for Media Channel sub-carriers configuration in Spectrum Switched Optical Networks (SSON) in Lambda Switch Capable (LSC) Optical Line Systems.

Draft: https://tools.ietf.org/html/draft-ggalimbe-ccamp-flexigrid-carrier-label-02

Presenter: Gabriele Galimberti

Dieter Beller: Reservations on the work, this is a proprietary solution even if experimental.

Gabriele Galimberti: Let’s discuss together what we’re addressing here. Even if you don’t have issues with implementation yet, you’ll have them soon.

Julien Meuric (remote): Ok for experimental but please keep it in CCAMP and not individual stream.

14 17:43 7

Title: Extension to LMP for DWDM Optical Line Systems to manage the application code of optical interface parameters in DWDM application

Draft: https://tools.ietf.org/html/draft-dharinigert-ccamp-dwdm-if-lmp-05

Draft: https://tools.ietf.org/html/draft-ggalimbe-ccamp-flex-if-lmp-03

Presenter: Ruediger Kunze

Dieter Beller: question regarding the new parameters introduced. I’ve not seen them referenced or defined.

Gabriele Galimberti: They’ll be in the upcoming version of G.698.2

15 17:50 10 Title: YANG Alarm Module

Draft: https://tools.ietf.org/id/draft-vallin-ccamp-alarm-module-01.txt

Presenter: Stefan Vallin (REMOTE)

Daniele Ceccarelli: The draft generated a lot of discussion on the list and there is also rather good support. I didn’t see any next steps in the presentation but I guess you’ll ask for WG adoption eventually.

Stefan Vallin: Yes, and will incorporate comments from the list.