Re: [CCAMP] John Scudder's Discuss on draft-ietf-ccamp-layer1-types-16: (with DISCUSS and COMMENT)

Italo Busi <Italo.Busi@huawei.com> Wed, 14 February 2024 13:35 UTC

Return-Path: <Italo.Busi@huawei.com>
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 2F647C14F70F; Wed, 14 Feb 2024 05:35:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.205
X-Spam-Level:
X-Spam-Status: No, score=-4.205 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 FVXsSSUgLk-9; Wed, 14 Feb 2024 05:35:05 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B676C14F6FB; Wed, 14 Feb 2024 05:35:05 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TZfGy2LX3z67M9n; Wed, 14 Feb 2024 21:31:22 +0800 (CST)
Received: from frapeml500006.china.huawei.com (unknown [7.182.85.219]) by mail.maildlp.com (Postfix) with ESMTPS id 726A114140B; Wed, 14 Feb 2024 21:35:03 +0800 (CST)
Received: from frapeml500007.china.huawei.com (7.182.85.172) by frapeml500006.china.huawei.com (7.182.85.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Wed, 14 Feb 2024 14:35:03 +0100
Received: from frapeml500007.china.huawei.com ([7.182.85.172]) by frapeml500007.china.huawei.com ([7.182.85.172]) with mapi id 15.01.2507.035; Wed, 14 Feb 2024 14:35:03 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: John Scudder <jgs@juniper.net>, The IESG <iesg@ietf.org>
CC: "draft-ietf-ccamp-layer1-types@ietf.org" <draft-ietf-ccamp-layer1-types@ietf.org>, "ccamp-chairs@ietf.org" <ccamp-chairs@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "dceccare@cisco.com" <dceccare@cisco.com>, "daniel@olddog.co.uk" <daniel@olddog.co.uk>
Thread-Topic: [CCAMP] John Scudder's Discuss on draft-ietf-ccamp-layer1-types-16: (with DISCUSS and COMMENT)
Thread-Index: AQHaKgpjK9kaV9nbQU2WtiT4AyX1lbEKMGDA
Date: Wed, 14 Feb 2024 13:35:03 +0000
Message-ID: <ea33118f6dfc4e0f9e50c0b3aaa2d173@huawei.com>
References: <170206268706.8097.1289884995538925699@ietfa.amsl.com>
In-Reply-To: <170206268706.8097.1289884995538925699@ietfa.amsl.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.203.246.111]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/kg7sKuge8PNBOWURo-n1ieuJbws>
Subject: Re: [CCAMP] John Scudder's Discuss on draft-ietf-ccamp-layer1-types-16: (with DISCUSS and COMMENT)
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: Wed, 14 Feb 2024 13:35:09 -0000

Dear John, 

Thank you for the review, the authors have updated the document to address your comments and posted the updated document as draft-ietf-ccamp-layer1-types-17.

Updates include:

- Fixing first use of OTN LTP
- Updated YANG build dates

Again, thanks for the support and review. 

Authors, Haomian and Italo.

> -----Original Message-----
> From: John Scudder via Datatracker <noreply@ietf.org>
> Sent: venerdì 8 dicembre 2023 20:11
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-ccamp-layer1-types@ietf.org; ccamp-chairs@ietf.org;
> ccamp@ietf.org; dceccare@cisco.com; daniel@olddog.co.uk;
> daniel@olddog.co.uk
> Subject: [CCAMP] John Scudder's Discuss on draft-ietf-ccamp-layer1-types-16:
> (with DISCUSS and COMMENT)
> 
> John Scudder has entered the following ballot position for
> draft-ietf-ccamp-layer1-types-16: Discuss
> 
> When responding, please keep the subject line intact and reply to all email
> addresses included in the To and CC lines. (Feel free to cut this introductory
> paragraph, however.)
> 
> 
> Please refer to
> https://www.ietf.org/about/groups/iesg/statements/handling-ballot-
> positions/
> for more information about how to handle DISCUSS and COMMENT
> positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-ccamp-layer1-types/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> I am balloting DISCUSS to ensure this point isn't missed, but intend to
> convert
> to YES; this is an excellent document.
> 
> Please don't forget to consider Tom Petch's review,
> https://mailarchive.ietf.org/arch/msg/last-call/akNb8PDxCI5lw-
> HWx474EcMp1Cg/ In
> particular, Tom points out some references to possibly-outdated external
> specifications.
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> In section 4.4 you mention OTN LTPs, I assume you're talking about "logical
> termination points". Please consider expanding LTP, I did check in RFC 7062
> to
> see if it's defined there; it's not.
> 
> Also, when you produce a new version, please make sure you update the
> 2022
> dates... unless there's some reason not to?
> 
> 
>