Re: [CCAMP] Charter update

Hi all,

Thanks for your comments. I think I’ve included all of them in the updated version below.
We’ll proceed with the submission.

Thanks,
Daniele, Fatai, Oscar.
--

The CCAMP working group is responsible for standardizing a common control plane and a separate common measurement plane for non-packet technologies found in the Internet and in the networks of telecom service providers (ISPs and SPs). Examples of the devices in such networks include photonic cross-connects, OEO switches, ROADMs, TDM switches, microwave links, and Ethernet switches.
In this context, measurement refers to the acquisition and distribution of attributes relevant to the setting up of tunnels and paths.
The working group develops extensions to core Traffic Engineering protocols that are under the care of other working groups as well as YANG models for the control and management of non-packet networks (this includes both device models and network models). The CCAMP working group will coordinate with the TEAS working group to ensure that extensions that can be generalized for use with more than one technology are made appropriately, and with the working groups that have responsibility for the specific protocols.

CCAMP WG work scope includes:

  *   Definition of protocol-independent metrics and parameters (measurement attributes) for describing links and paths that are required for routing and signaling in technology-specific networks. These will be developed in conjunction with requests and requirements from other WGs to ensure overall usefulness.
  *   Maintenance and extension of the Link Management Protocol (LMP)
  *   Functional specification of extensions for GMPLS-related routing  (OSPF, ISIS) and signaling (RSVP-TE) protocols required for path establishment and maintenance in non-packet, technology-specific  networks. Protocol formats and procedures that embody these extensions will be done jointly with the WGs supervising those  protocols and the TEAS working group has the responsibility to determine whether such protocol extensions should be generalized for Traffic Engineering in any network. This may include protocol work to support data planes that have already been approved by another Standards Development Organization. Note that the specification or modification of data  planes is out of scope of this working group.
  *   Definition of management objects (e.g., as part of MIB modules or YANG models) and control of OAM techniques relevant to the  protocols and extensions specified within the WG. The OAM work will be synchronized with relevant working groups (e.g. IPPM, OPSAWG, BFD) and SDOs (e.g. ITU-T).
  *   Description of  non-packet-specific aspects of traffic engineering including for multi-areas/multi-AS/multi-layer scenarios and  define protocol extensions in cooperation with the TEAS and  PCE working groups.
  *   Description of non-packet-specific (e.g. Ethernet, TDM, OTN, WDM, …)  aspects (requirements, use cases, …) of network slicing and protocol and Yang models extensions in cooperation with the TEAS and  PCE working groups.
  *   Definition how the properties of network resources gathered by a measurement protocol (or by other means such as configuration) can be distributed in existing routing protocols, such as OSPF,  IS-IS, and BGP-LS. CCAMP will work with the WGs that supervise  these.
The CCAMP WG currently works on the following tasks:

  *   Protocol extensions and YANG models in support of optical networks (e.g. WSON, flexi grid) with and without awareness of the optical impairments.

  *   Protocol extensions and YANG models in support of TDM networks (e.g. OTN).
  *   YANG models in support of microwave networks.
  *   YANG models fin support of L1 services
  *   Client TE topologies
  *   Maintenance of existing protocol extensions for non-packet technology-specific networks (Ethernet, TDM, OTN) already specified by CCAMP.
  *   Maintenance of LMP.

From: Greg Mirsky <gregimirsky@gmail.com>
Sent: den 31 mars 2021 21:41
To: Belotti, Sergio (Nokia - IT/Vimercate) <sergio.belotti@nokia.com>
Cc: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>; adrian@olddog.co.uk; CCAMP <ccamp@ietf.org>
Subject: Re: [CCAMP] Charter update

Hi Sergio, et al.,
I agree that there would be benefits of coordinating CCAMP work related to OAM with other SDOs. At the same time, IETF has several WGs, e.g., IPPM, OPSAWG, BFD, and RTGWG, where various aspects of OAM and on-path telemetry have been discussed and a good number of RFCs already published and more will be. It seems reasonable to look if some of the existing solutions are applicable to problems discussed in the CCAMP WG.

Regards,
Greg

On Wed, Mar 31, 2021 at 1:30 AM Belotti, Sergio (Nokia - IT/Vimercate) <sergio.belotti@nokia.com<mailto:sergio.belotti@nokia.com>> wrote:
Hi Daniele, Adrian,

About OAM, LIME is clearly gone,  shall we put a reference to other SDO traditionally involved in OAM standardization like ITU-T or industrial forum like ONF ? Just a question.

About this part:
“The CCAMP WG currently works on the following tasks:

  *   Protocol extensions and YANG models in support of optical networks (e.g. WSON, flexi grid) with and without awareness of the optical impairments.
- Protocol extensions in support of flexible grid lambda networks”

It seems to me the same concept in the two bullets right?

Third: we started with OTN suggesting extension in network slicing technology specific.
Maybe something related to “slicing” should be added.

Thanks
Sergio

From: CCAMP <ccamp-bounces@ietf.org<mailto:ccamp-bounces@ietf.org>> On Behalf Of Daniele Ceccarelli
Sent: Wednesday, March 31, 2021 9:00 AM
To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'CCAMP' <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: Re: [CCAMP] Charter update

Hi Adrian,

Thanks for spotting it.
The ” Strikethrough” got lost when pasting the content into the mail.

Actually that applies to two statements:

  *   The OAM work will be synchronized with the LIME WG (WG closed)
  *   Protocol extensions in support of flexible grid lambda networks. (which is now included in the first bullet of the list).

Thanks,
Daniele

From: Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Sent: den 31 mars 2021 00:22
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com<mailto:daniele.ceccarelli@ericsson.com>>; 'CCAMP' <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: RE: [CCAMP] Charter update

Hi,

Thanks for the work on this. It’s looking good.

Small point

  *   “OAM work will be synchronized with the LIME WG”
LIME was closed down just over 3 years ago

Cheers,
Adrian

From: CCAMP <ccamp-bounces@ietf.org<mailto:ccamp-bounces@ietf.org>> On Behalf Of Daniele Ceccarelli
Sent: 30 March 2021 13:03
To: CCAMP <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: [CCAMP] Charter update

Hi working group,

as briefly anticipated during the CCAMP session at IETF110 please find below the proposal for the update to the charter.
Please send you comments/suggestions before April 15th.

Thanks
Daniele , Fatai, Oscar
------

The CCAMP working group is responsible for standardizing a common control plane and a separate common measurement plane for non-packet technologies found in the Internet and in the networks of telecom service providers (ISPs and SPs). Examples of the devices in such networks include photonic cross-connects, OEO switches, ROADMs, TDM switches, microwave links, and Ethernet switches.
In this context, measurement refers to the acquisition and distribution of attributes relevant to the setting up of tunnels and paths.
The working group develops extensions to core Traffic Engineering protocols that are under the care of other working groups as well as YANG models for the control and management of non-packet networks (this includes both device models and network models). The CCAMP working group will coordinate with the TEAS working group to ensure that extensions that can be generalized for use with more than one technology are made appropriately, and with the working groups that have responsibility for the specific protocols.

CCAMP WG work scope includes:

  *   Definition of protocol-independent metrics and parameters (measurement attributes) for describing links and paths that are required for routing and signaling in technology-specific networks. These will be developed in conjunction with requests and requirements from other WGs to ensure overall usefulness.
  *   Maintenance and extension of the Link Management Protocol (LMP)
  *   Functional specification of extensions for GMPLS-related routing  (OSPF, ISIS) and signaling (RSVP-TE) protocols required for path establishment and maintenance in non-packet, technology-specific  networks. Protocol formats and procedures that embody these   extensions will be done jointly with the WGs supervising those  protocols and the TEAS working group has the responsibility to   determine whether such protocol extensions should be generalized  for Traffic Engineering in any network. This may include protocol work to support data planes that have  already been approved by another Standards Development Organization. Note that the specification or modification of data  planes is out of scope of this working group.
  *   Definition of management objects (e.g., as part of MIB modules or YANG models) and control of OAM techniques relevant to the  protocols and extensions specified within the WG. The OAM work will be synchronized with the LIME WG
  *   Describe non-packet-specific aspects of traffic engineering including for multi-areas/multi-AS/multi-layer scenarios and  define protocol extensions in cooperation with the TEAS and  PCE working groups.
  *   Define how the properties of network resources gathered by a measurement protocol (or by other means such as configuration) can be distributed in existing routing protocols, such as OSPF,  IS-IS, and BGP-LS. CCAMP will work with the WGs that supervise  these.
The CCAMP WG currently works on the following tasks:

  *   Protocol extensions and YANG models in support of optical networks (e.g. WSON, flexi grid) with and without awareness of the optical impairments.
- Protocol extensions in support of flexible grid lambda networks.

  *   Protocol extensions and YANG models in support of TDM networks (e.g. OTN).
  *   YANG models in support of microwave networks.
  *   YANG models fin support of L1 services
  *   Client TE topologies
  *   Maintenance of existing protocol extensions for non-packet technology-specific networks (Ethernet, TDM, OTN) already specified by CCAMP.
  *   Maintenance of LMP.

_______________________________________________
CCAMP mailing list
CCAMP@ietf.org<mailto:CCAMP@ietf.org>
https://www.ietf.org/mailman/listinfo/ccamp