Re: [CCAMP] FW: New Version Notification for draft-gstk-ccamp-actn-optical-transport-mgmt-03.txt
daniel@olddog.co.uk Fri, 12 April 2024 14:58 UTC
Return-Path: <dk@danielking.net>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89B04C14F69B for <ccamp@ietfa.amsl.com>; Fri, 12 Apr 2024 07:58:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.635
X-Spam-Level:
X-Spam-Status: No, score=-1.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=danielking-net.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nvNJbibocrgA for <ccamp@ietfa.amsl.com>; Fri, 12 Apr 2024 07:58:11 -0700 (PDT)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC161C15106C for <ccamp@ietf.org>; Fri, 12 Apr 2024 07:58:11 -0700 (PDT)
Received: by mail-wr1-x42e.google.com with SMTP id ffacd0b85a97d-343cfa6faf0so753736f8f.0 for <ccamp@ietf.org>; Fri, 12 Apr 2024 07:58:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielking-net.20230601.gappssmtp.com; s=20230601; t=1712933889; x=1713538689; darn=ietf.org; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:cc:to:from:sender:from:to:cc:subject:date :message-id:reply-to; bh=9+V46yFbFP+7/MxJeEeAb4vOiSXuLlGwIEh6PkKs15g=; b=ppITSFsBKiUjMPKb5AzzCLiT5hk7jdPFB4QWGIIMem4e2yA5HX8yI4sJrMnMgo769L QCvt8DProR3CL7NG9U5ypKodQQzWtGXi91ag9mobsoYLlax78Q3kPMQIBIBxlIV6eQ3r kV3dGUxAb5+Qsq1P0y6oXjZAM96lF/F357xvMOc5n0FweIv9Jpqt9irUPbw+FlWNH5Mh Fq5vagHW3TU48eJeu5XrDABPasrzouuCTg9gH5L2hHW6lNO3ybXcYmrkhIS3v8hfLQlS xceBsV09efpPRuurNO0dNyJjg/uf6ZdxLlOA07F+wPduRgvTALT70h7ailttyAFVz2+s Ju1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712933889; x=1713538689; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:cc:to:from:sender:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=9+V46yFbFP+7/MxJeEeAb4vOiSXuLlGwIEh6PkKs15g=; b=KcXWlvWJgGKdtweWJ2l2uFdJvQKeW5/DqybbfR5rYN8MHL4hV9K1QpOpONQ9uzO1SS +18pgnV5bZWHywe/JhKluFcXo71hesMIyeKWgxvq9i8+kzIO8R3ai00WvVogCHZhEem1 Tb9XfVANQ/wd6fGRpqe1DibqxmCXgvK9aQpxBb6H983RQSbySQKr6onvaLanPpyCsupo +7tMWG5LOk7m9DDLx6abc0RJK49L3ElvilKSYV7aeUrtf5Gvw6vK8YPD3PxGlr69eqPB R02YzgJF75xn4CCMs3zCVvgL/OkL/t1PfnZ/AWa27hZu08PmuVxLJXbhvP/0/OPK6mOM nI2g==
X-Gm-Message-State: AOJu0YyhN/Y1JleZyVArY+b9J5mz9QS4Xqfp3cI56oz8QkFXRltNjqqT 6aNaVntumYQr9LOr3IeTBTE7YDCTc35bFnmn90I0B9sQsW4SUWL+TLDxqCWLi9RRU5bJY6e+E8E SYw==
X-Google-Smtp-Source: AGHT+IE0tPh8f6MKxhWnRrD0Wmji5HjMy34TCtRkV8ZM+fHaXEqI7f9H2EuVsOcgLSa7q79xL1x84A==
X-Received: by 2002:a5d:614d:0:b0:341:865b:65c9 with SMTP id y13-20020a5d614d000000b00341865b65c9mr2552659wrt.22.1712933888676; Fri, 12 Apr 2024 07:58:08 -0700 (PDT)
Received: from CIPHER ([2a00:23c7:115:2301:a49e:5788:7d28:719e]) by smtp.gmail.com with ESMTPSA id h7-20020a5d4fc7000000b00341ba91c1f5sm4430953wrw.102.2024.04.12.07.58.04 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Apr 2024 07:58:05 -0700 (PDT)
Sender: Daniel King <dk@danielking.net>
X-Google-Original-Sender: <dk@danielking.net>
From: daniel@olddog.co.uk
To: "'Daniele Ceccarelli (dceccare)'" <dceccare@cisco.com>
Cc: 'CCAMP' <ccamp@ietf.org>
References: <171290744876.60694.7366484710312081276@ietfa.amsl.com> <00ad01da8cad$dc945370$95bcfa50$@olddog.co.uk> <CY8PR11MB73403A624C118B56FF3B9B1ED4042@CY8PR11MB7340.namprd11.prod.outlook.com>
In-Reply-To: <CY8PR11MB73403A624C118B56FF3B9B1ED4042@CY8PR11MB7340.namprd11.prod.outlook.com>
Date: Fri, 12 Apr 2024 15:58:04 +0100
Message-ID: <010a01da8ce9$d296fcb0$77c4f610$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_010B_01DA8CF2.345CEB50"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHnZu/sxTI+z6mhS2w9TRwTP7qrwwGJpYhxAdarl5SxL/vy4A==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/I7gQ_Pyc0gt3d0p34dSkePqap1U>
Subject: Re: [CCAMP] FW: New Version Notification for draft-gstk-ccamp-actn-optical-transport-mgmt-03.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2024 14:58:15 -0000
Hi Daniele, Wow, thanks for reading the latest version so quickly. A few responses inline (DK>>): BR, Dan. From: Daniele Ceccarelli (dceccare) <dceccare@cisco.com> Sent: Friday, April 12, 2024 1:48 PM To: daniel@olddog.co.uk; 'CCAMP' <ccamp@ietf.org> Subject: RE: [CCAMP] FW: New Version Notification for draft-gstk-ccamp-actn-optical-transport-mgmt-03.txt Hi Dan, Thanks for the heads up. Just a few comments from my side: 1. Is there a related "non technology specific" work ongoing in e.g. TEAS? I couldn't find it. I was expecting as usual to see a generic work and then the optical extensions in CCAMP, but I don't have any objection if you want to apply it to optical networks only. DK>> Ah, a few others (Victor and Oscar) raised a similar point. We would agree that FCAPS-like capability, in the context of ACTN, would be useful for various technologies. However, our (authors) preference was to focus on optical, specifically OTN and WDM. 2. Does FGNM exist as term also outside the context of ACTN or is something new that you're defining here only for ACTN and more specifically only for ACTN optical networks? DK>> Ah terminology, a tough issue these days as we exhausted TLAs over a decade again ([RFC5513]). For this proposal, we switched to Four Letter Acronyms and debated how to describe fine-grain control of management functions - our proposal is ACTN-based FGNM. As you are aware, the ITU-T is working on Fine-grained OTN bandwidth for the data plane, so we need to ensure no confusion of term(s) occur. 3. Figure 1 in my opinion should be provided as example and not made prescriptive. The OSS might connect to the MDSC, not necessarily to the domain controller. Moreover it could connect to different components for different purposes. Maybe what you could do is to have an OSS container sitting on top of the entire hierarchy with a box inside it called e.g. OSS-FCAPS that connects to the domain controller. This allows representing what you're targeting, without implying any architectural obligation. DK>> Great, indeed that could be a good deployment scenario. Would you send me the updated ASCII art with the additional functional components and interfaces? We could use the expanded Figure 1 as general ACTN-based architecture with available functional components; then we can describe two deployment examples with benefits/capabilities for: (1) connecting to MDSC and (2) Connecting Domain Controller)), in Section 5.4. “Fine-Grain Network Management Examples”. Hey, it sounds like you are dangerously close to being an author/contributor 😊 ...while further reading the draft I think I found myself the answer to question 1...i'll paste it here for who might have the same question: This can make generalisation of configuration and management hard, and means that the nature of ACTN FGNM is different in an optical network than it might be in a more general (and specifically, packet-based) TE network. DK>> Appreciate that, thanks! Cheers Daniele -----Original Message----- From: CCAMP <ccamp-bounces@ietf.org <mailto:ccamp-bounces@ietf.org> > On Behalf Of daniel@olddog.co.uk <mailto:daniel@olddog.co.uk> Sent: Friday, April 12, 2024 9:49 AM To: 'CCAMP' <ccamp@ietf.org <mailto:ccamp@ietf.org> > Subject: [CCAMP] FW: New Version Notification for draft-gstk-ccamp-actn-optical-transport-mgmt-03.txt Morning CCAMP'rs, We have made good progress on Fine-Grain Network Management (FGNM) for optical networks using the ACTN architecture. Please use this link for the changes since 01/02 and 03: <https://shorturl.at/mEGJ4> https://shorturl.at/mEGJ4 Substantive updates include: - Tightening the scope and intention of FGNM - Updating the interface architecture between FGNM and ACTN - Highlighting mechanisms to extract optical resource information - Discussing the role of the ACTN MPI interface - Linking the I-D to recent work proposed by Chaode ( <https://datatracker.ietf.org/doc/draft-yu-ccamp-te-fgnm-yang/> https://datatracker.ietf.org/doc/draft-yu-ccamp-te-fgnm-yang/) - Adding Manageability Considerations and expanding Security Considerations - New co-author (Choade) - Thanks to Daniele and Victor for previous feedback on the I-D We would appreciate further review and thoughts on the proposal from the working group. BR, Dan. -----Original Message----- From: <mailto:internet-drafts@ietf.org> internet-drafts@ietf.org < <mailto:internet-drafts@ietf.org> internet-drafts@ietf.org> Sent: Friday, April 12, 2024 8:37 AM To: Adrian Farrel < <mailto:adrian@olddog.co.uk> adrian@olddog.co.uk>; Chaode Yu < <mailto:yuchaode@huawei.com> yuchaode@huawei.com>; Daniel King < <mailto:daniel@olddog.co.uk> daniel@olddog.co.uk>; Xing Zhao < <mailto:zhaoxing@caict.ac.cn> zhaoxing@caict.ac.cn>; XingZhao < <mailto:zhaoxing@caict.ac.cn> zhaoxing@caict.ac.cn> Subject: New Version Notification for draft-gstk-ccamp-actn-optical-transport-mgmt-03.txt A new version of Internet-Draft draft-gstk-ccamp-actn-optical-transport-mgmt-03.txt has been successfully submitted by Daniel King and posted to the IETF repository. Name: draft-gstk-ccamp-actn-optical-transport-mgmt Revision: 03 Title: Integrating YANG Configuration and Management into an Abstraction and Control of TE Networks (ACTN) System for Optical Networks Date: 2024-04-12 Group: Individual Submission Pages: 21 URL: <https://www.ietf.org/archive/id/draft-gstk-ccamp-actn-optical-transport-mgmt-03.txt> https://www.ietf.org/archive/id/draft-gstk-ccamp-actn-optical-transport-mgmt-03.txt Status: <https://datatracker.ietf.org/doc/draft-gstk-ccamp-actn-optical-transport-mgmt/> https://datatracker.ietf.org/doc/draft-gstk-ccamp-actn-optical-transport-mgmt/ HTMLized: <https://datatracker.ietf.org/doc/html/draft-gstk-ccamp-actn-optical-transport-mgmt> https://datatracker.ietf.org/doc/html/draft-gstk-ccamp-actn-optical-transport-mgmt Diff: <https://author-tools.ietf.org/iddiff?url2=draft-gstk-ccamp-actn-optical-transport-mgmt-03> https://author-tools.ietf.org/iddiff?url2=draft-gstk-ccamp-actn-optical-transport-mgmt-03 Abstract: Many network technologies are operated as Traffic Engineered (TE) networks. Optical networks are a particular case, and have complex technology-specific details. Abstraction and Control of TE Networks (ACTN) is a management architecture that abstracts TE network resources to provide a limited network view for customers to request and self-manage connectivity services. It also provides functional components to orchestrate and operate the network. Management of legacy optical networks is often provided via Fault, Configuration, Accounting, Performance, and Security (known as FCAPS) using mechanisms such as the Multi-Technology Operations System Interface (MTOSI) and the Common Object Request Broker Architecture (CORBA). FCAPS can form a critical part of configuration management and service assurance for network operations. However, the ACTN architecture as described in RFC 8453 does not include consideration of FCAPS. This document enhances the ACTN architecture as applied to optical networks by introducing support for FCAPS. It considers which elements of existing IETF YANG work can be used to solve existing scenarios and emerging technologies, and what new work may be needed. In doing so, this document adds fine-grained network management to the ACTN architecture. This enhanced architecture may then be used to evolve networks from CORBA and MTOSI FCAPS interfaces to IETF- based YANG and RESTful API capabilities. The IETF Secretariat _______________________________________________ CCAMP mailing list <mailto:CCAMP@ietf.org> CCAMP@ietf.org <https://www.ietf.org/mailman/listinfo/ccamp> https://www.ietf.org/mailman/listinfo/ccamp
- [CCAMP] FW: New Version Notification for draft-gs… daniel
- Re: [CCAMP] FW: New Version Notification for draf… Daniele Ceccarelli (dceccare)
- Re: [CCAMP] FW: New Version Notification for draf… daniel
- Re: [CCAMP] FW: New Version Notification for draf… Adrian Farrel
- Re: [CCAMP] FW: New Version Notification for draf… Daniele Ceccarelli (dceccare)
- Re: [CCAMP] FW: New Version Notification for draf… Adrian Farrel