Re: [CCAMP] Benjamin Kaduk's No Objection on draft-ietf-ccamp-microwave-framework-06: (with COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Tue, 29 May 2018 18:26 UTC

Return-Path: <kaduk@mit.edu>
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 2F91B12DA4F; Tue, 29 May 2018 11:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5DbCVIngg7nU; Tue, 29 May 2018 11:26:55 -0700 (PDT)
Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22D3C12EBDE; Tue, 29 May 2018 11:26:55 -0700 (PDT)
X-AuditID: 12074422-54dff70000000f17-d9-5b0d9b6ddcdb
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 68.BF.03863.E6B9D0B5; Tue, 29 May 2018 14:26:54 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id w4TIQqOi018362; Tue, 29 May 2018 14:26:52 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w4TIQkMC020289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 29 May 2018 14:26:49 -0400
Date: Tue, 29 May 2018 13:26:46 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: "Yemin (Amy)" <amy.yemin@huawei.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-ccamp-microwave-framework@ietf.org" <draft-ietf-ccamp-microwave-framework@ietf.org>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, "ccamp-chairs@ietf.org" <ccamp-chairs@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Message-ID: <20180529182646.GK27985@kduck.kaduk.org>
References: <152708147191.26780.6549547106343200107.idtracker@ietfa.amsl.com> <9C5FD3EFA72E1740A3D41BADDE0B461FCF0194CD@DGGEMA501-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <9C5FD3EFA72E1740A3D41BADDE0B461FCF0194CD@DGGEMA501-MBX.china.huawei.com>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNKsWRmVeSWpSXmKPExsUixCmqrJs3mzfa4NlkbovNHRvYLJbu2MRk 8WTODRaLacuXMVk87V7EaDHjz0RmBzaPX1+vsnm0HHnL6rFkyU+mAOYoLpuU1JzMstQifbsE roxVu+ULurUqzs3ZyNbA+FGhi5GTQ0LARGLHhSVsXYxcHEICi5kklv05AuVsZJRY/eokM0iV kMBVJokn8+RBbBYBVYknUxaygNhsAioSDd2XgWo4OEQENCReNoeB9DILrGaSmDjpPyNIjbBA usTxTUvB6nmBti35eIsdYsFMRoldfyczQyQEJU7OfAJWxCygLvFn3iWwocwC0hLL/3FAhOUl mrfOBivnFAiTuLCwnx3EFhVQltjbd4h9AqPgLCSTZiGZNAth0iwkkxYwsqxilE3JrdLNTczM KU5N1i1OTszLSy3SNdXLzSzRS00p3cQIigN2F6UdjBP/eR1iFOBgVOLhNYjgjRZiTSwrrsw9 xCjJwaQkymtRBBTiS8pPqcxILM6ILyrNSS0+xCjBwawkwlu6lydaiDclsbIqtSgfJiXNwaIk zpu7iDFaSCA9sSQ1OzW1ILUIJivDwaEkwWs2C2ioYFFqempFWmZOCUKaiYMTZDgP0HBBkBre 4oLE3OLMdIj8KUZFKXHeTzOBEgIgiYzSPLheUJqSyN5f84pRHOgVYV5OkHYeYIqD634FNJgJ aPCTidwgg0sSEVJSDYwh649+TRQQOHZlVnfQcn+L51/blI6Xm7XrHvM9WWuxcaKc97qi344C 5i/apq6Qzec13fxr0+05r+MWps2xfX9GovbM65+LDDxd1zaqfb7XE/N4l8mpOxsucJjmub50 alZMOvaY2+Gi2uPo7cmGG36wrVJz2OJyxFZ2dzQL5wLzJoP0hrYvm5qUWIozEg21mIuKEwG2 Ti2ZLgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/Yurbz3Z8SyKZ42QiHF_Rsov9F80>
Subject: Re: [CCAMP] Benjamin Kaduk's No Objection on draft-ietf-ccamp-microwave-framework-06: (with COMMENT)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 29 May 2018 18:26:58 -0000

Hi Amy,

No worries about the late response; all these updates work for me.

Thanks,

Benjamin

On Mon, May 28, 2018 at 07:22:07AM +0000, Yemin (Amy) wrote:
> Hi Benjamin,
> 
> 
> 
> Thanks for the comments, and sorry for the late response.
> 
> Please see reply inline in blue.
> 
> 
> 
> BR,
> 
> Amy
> 
> -----Original Message-----
> From: Benjamin Kaduk [mailto:kaduk@mit.edu]
> Sent: Wednesday, May 23, 2018 9:18 PM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-ccamp-microwave-framework@ietf.org; Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>om>; ccamp-chairs@ietf.org; daniele.ceccarelli@ericsson.com; ccamp@ietf.org
> Subject: Benjamin Kaduk's No Objection on draft-ietf-ccamp-microwave-framework-06: (with COMMENT)
> 
> 
> 
> Benjamin Kaduk has entered the following ballot position for
> 
> draft-ietf-ccamp-microwave-framework-06: No Objection
> 
> 
> 
> 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/iesg/statement/discuss-criteria.html
> 
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> 
> 
> 
> The document, along with other ballot positions, can be found here:
> 
> https://datatracker.ietf.org/doc/draft-ietf-ccamp-microwave-framework/
> 
> 
> 
> 
> 
> 
> 
> ----------------------------------------------------------------------
> 
> COMMENT:
> 
> ----------------------------------------------------------------------
> 
> 
> 
> I have a similar sentiment to Mirja, in that this document seems to be describing the result of WG deliberations and the conclusions that have been reached as to the path for future work.  As such, it's unclear that there is lasting technical value to the Internet Community from publication as an RFC (as opposed to remaining as a WG-internal document until the publication of the associated follow-up work).  That said, I am not making this a blocking objection.
> 
> 
> 
> I'm happy to see the secdir thread coming to a conclusion about SDN vs. NMS -- thanks for working to clear that up.
> 
> 
> 
> Otherwise, I just have some grammatical/style nits that I noted while reading.
> 
> 
> 
> Is there any need to disambiguate "Wireless carrier" (i.e., a type of
> 
> company) vs. "carrier frequency"?  (I could certainly see an argument for "no", given the target audience.)
> 
> [Amy] Maybe not necessary. Carrier is a widely used term in wireless technology.
> 
> 
> 
> Sections 1 and 2 differ about the lower bound for "microwave radio"
> 
> spectrum (1GHz vs. 1.4 GHz).
> [Amy] Thanks for pointing it out. Should be 1.4GHz.
> 
> 
> 
> Section 2
> 
> 
> 
>    [...] Using multi-carrier systems operating in frequency bands
> 
>    with wider channels, the technology will be capable of providing
> 
>    capacities up 100 Gbps.
> 
> 
> 
> nit: "capacities of up to"
> [Amy] will fix it.
> 
> 
> 
> Section 3.2
> 
> 
> 
>    [...] Hence, an
> 
>    open and standardized node management interface are required in a
> 
>    multi-vendor environment.  Such standardized interface enables a
> 
>    unified management and configuration of nodes from different vendors
> 
>    by a common set of applications.
> 
> 
> 
> nit: singular/plural disagreement between "an" and "are"; also between "such" (vs. "such a") and "interface enables" (vs.
> 
> "interfaces enable")
> [Amy] will fix it, see below:
>    Hence, an
>    open and standardized node management interface is required in a
>    multi-vendor environment.  Such a standardized interface enables a
>    unified management and configuration of nodes from different vendors
>    by a common set of applications.
> 
> 
> 
> 
> 
>    On top of SDN applications to configure, manage and control the nodes
> 
>    and their associated transport interfaces including the L2 Ethernet
> 
>    and L3 IP interfaces as well as the radio interfaces, there are also
> 
>    a large variety of other more advanced SDN applications that can be
> 
>    exploited and/or developed.
> 
> 
> 
> FYI, the word "exploited" has connotations (in some circles) of a malicious hack, i.e., that such an application has vulnerabilities that are exploited for nefarious purposes.  (So far as I know, "utilized" does not.)
> [Amy] Thanks for suggestion, will change to "utilized”.
> 
> 
> 
> The subsections in Section 4 read, stylistically, as if they are bullet points under the heading of "use cases".  I wonder if there would be benefit from adding some generic text about "This use case involves ..." to them.
> [Amy] How about add the following sentence to the end of first paragraph in section 4:
> The use cases involves configuration management, inventory, status and statistics, performance management, fault management, troubleshooting and rout cause analysis.
> 
> 
> 
> nit: In Section 6.1, "data plane technology specific" is used (multiple
> 
> times) as a compound adjective, which requires some hyphenation.  (I believe different style guides have conflicting recommendations, but at least a hyphen in "technology-specific" is generally accepted.)
> [Amy] will use "technology-specific".
> 
> 
> 
>