Re: [CCAMP] FW: I-D Action: draft-ietf-ccamp-mw-yang-03.txt

Daniele Ceccarelli <daniele.ceccarelli@ericsson.com> Tue, 03 April 2018 09:12 UTC

Return-Path: <daniele.ceccarelli@ericsson.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 0AA2E1270AB for <ccamp@ietfa.amsl.com>; Tue, 3 Apr 2018 02:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level:
X-Spam-Status: No, score=-4.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=hA1MCLQ8; dkim=pass (1024-bit key) header.d=ericsson.com header.b=NTzUcTCD
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 kQ6OAELW3x7X for <ccamp@ietfa.amsl.com>; Tue, 3 Apr 2018 02:12:20 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 225B4124205 for <ccamp@ietf.org>; Tue, 3 Apr 2018 02:12:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1522746738; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=J627ycTDdOwl2prNzEkxS/Shph4J3FHP3tSO4RUtw2o=; b=hA1MCLQ8ORZBHMPSHvJGdu1gwFnPtvle9imtGiOps9mRbCD/osX9nN1K0zlcqI1N msFnz17DfMtepbc2LZUoOAaVEcjFRiRILMcfgFdY1uN8jP9csWIl3Fid0Bva/Lh9 Sy7PXk26saQK1J1nQH9TT/X06NO8KLf0JSpVLVMdZPg=;
X-AuditID: c1b4fb25-5a75a9c00000522b-90-5ac34572bea8
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 7B.F1.21035.27543CA5; Tue, 3 Apr 2018 11:12:18 +0200 (CEST)
Received: from ESESSMB502.ericsson.se (153.88.183.163) by ESESSHC020.ericsson.se (153.88.183.78) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 3 Apr 2018 11:12:17 +0200
Received: from ESESSMB502.ericsson.se (153.88.183.163) by ESESSMB502.ericsson.se (153.88.183.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.26; Tue, 3 Apr 2018 11:12:17 +0200
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB502.ericsson.se (153.88.183.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.26 via Frontend Transport; Tue, 3 Apr 2018 11:12:17 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=+9hkCxHOLAQeX/+ON+OuxO12lr/iaRni2vvBHt3bxo8=; b=NTzUcTCDFGUtneB4HQFq1mS+k8ou0jBD8P1nZUa3OqDs+h/N1TvbOfkjUnChTceq2K3CCEOGpZwicCpToPLIISQkHX/tnLEqexnD99BQLf1TnMOhTbNvWrrqBC8HLKpdUxtAvKZLWiYyrAaQeT8XAhV/QodbxerNXhhAh8gjt2k=
Received: from VI1PR07MB3167.eurprd07.prod.outlook.com (10.175.243.17) by VI1PR07MB1551.eurprd07.prod.outlook.com (10.165.238.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.653.4; Tue, 3 Apr 2018 09:12:16 +0000
Received: from VI1PR07MB3167.eurprd07.prod.outlook.com ([fe80::cc6:bb7b:c27f:fd40]) by VI1PR07MB3167.eurprd07.prod.outlook.com ([fe80::cc6:bb7b:c27f:fd40%2]) with mapi id 15.20.0653.011; Tue, 3 Apr 2018 09:12:15 +0000
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: t.petch <ietfc@btconnect.com>, Jonas Ahlberg <jonas.ahlberg@ericsson.com>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: [CCAMP] FW: I-D Action: draft-ietf-ccamp-mw-yang-03.txt
Thread-Index: AQHTrwbI4PuQFJehxEGHTkuM+a5V+aO7PcIqgAMlE4CAACEFzIACzqoAgBGOKC+ACCo6gIASkmLNgAFcQvA=
Date: Tue, 3 Apr 2018 09:12:15 +0000
Message-ID: <VI1PR07MB316761A55ACF9BEED78F9935F0A50@VI1PR07MB3167.eurprd07.prod.outlook.com>
References: <151965140712.31478.7598037460289428995@ietfa.amsl.com> <HE1PR0702MB35322C311CF8F8B0E7C95CC789C10@HE1PR0702MB3532.eurprd07.prod.outlook.com> <009f01d3b14d$7a44be40$4001a8c0@gateway.2wire.net> <HE1PR0702MB3532600A2F82A3539D57E33689C40@HE1PR0702MB3532.eurprd07.prod.outlook.com> <009a01d3b2f0$8e3046a0$4001a8c0@gateway.2wire.net> <HE1PR0702MB3532508C2AC3BA30986AC66D89DA0@HE1PR0702MB3532.eurprd07.prod.outlook.com> <033301d3bd1e$ddcf5f60$4001a8c0@gateway.2wire.net> <HE1PR0702MB3532B3072B04855F2836942689AA0@HE1PR0702MB3532.eurprd07.prod.outlook.com> <020101d3ca7d$8793a7c0$4001a8c0@gateway.2wire.net>
In-Reply-To: <020101d3ca7d$8793a7c0$4001a8c0@gateway.2wire.net>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=daniele.ceccarelli@ericsson.com;
x-originating-ip: [93.38.67.165]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB1551; 7:1cU8OjVa+TJVfMLrq/f7zMdZbOecS2nP+btfZgdOFz7ALCZxflCxzrJmAOkWl5OQ2qV9lvaOQSm1FdxYUd2CBF0MFMP5Jl3r1x1TxdHKT/CzjItYdb+6HUqS6FgJ8jzIrnfErH8JiZ0giZeVtUT6wk52Gykjtq1SB5QMNYZUv9J1N51M6G2MjvYjoCf+JayycScxoENiEAkt2L9zc4no01MkB8YeWdR42q2SJkYTH0g5n1snnOf9w+Is8NVVS5aR
x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR;
x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10009020)(346002)(376002)(396003)(39860400002)(39380400002)(366004)(377424004)(13464003)(189003)(199004)(65554003)(86362001)(486005)(81166006)(81156014)(106356001)(446003)(3846002)(6116002)(68736007)(486005)(105586002)(6436002)(3280700002)(5660300001)(345774005)(8936002)(8676002)(2906002)(2900100001)(476003)(3660700001)(478600001)(25786009)(14454004)(966005)(66066001)(5250100002)(74316002)(229853002)(76176011)(186003)(97736004)(2501003)(59450400001)(53936002)(6246003)(9686003)(305945005)(26005)(99286004)(102836004)(11346002)(55016002)(8666007)(7696005)(110136005)(93886005)(316002)(296002)(53546011)(6506007)(6306002)(7736002)(33656002)(390854003); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB1551; H:VI1PR07MB3167.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
x-ms-office365-filtering-correlation-id: f28bf829-d4ad-49e0-05ce-08d59942fe58
x-microsoft-antispam: UriScan:(178726229863574); BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB1551;
x-ms-traffictypediagnostic: VI1PR07MB1551:
x-microsoft-antispam-prvs: <VI1PR07MB1551A1973039AF78D001811CF0A50@VI1PR07MB1551.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(178726229863574)(120809045254105)(166708455590820)(788757137089);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231221)(944501327)(52105095)(6041310)(20161123560045)(20161123558120)(20161123564045)(201703131423095)(201703031522075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(6072148)(201708071742011); SRVR:VI1PR07MB1551; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1551;
x-forefront-prvs: 0631F0BC3D
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: H/HrbjY9nA4LoAf5aOs39UVefSPHqk9J/NYjJBldNYTWEzAjlAKCFDtfGq3uGuzX0zV4edSD739RcdnDunRg+88Mhf2UkqbUsmOdAHvX2UZiWCGW+S9wz5MGCvd/Mq3C9aJdXngFAEljA3Kq8PIZaNP1oV43g4gjJnQK0fATGvk7tck0KvoEa36jxFhFKpNd5tadCTzBmekdfjjwfMLux7LYfXP3V46lI7EXNyN1CwEP1biIJOplg/5fKuwYz2ZMVz/4WzEuyLZtKTQoczQWzX7dP3P4Cy9p6A+u0qT25O9L+sEXU7WPOd+c6PQhY669fTFh929DbpBqq0378rPKdhcIC/gASErdXeDPhanF9agoiIneowKiDGWcYqhNIfcb9tO3kxN5J5cFc5TktOzkIq12Iqk7uIWESG7vAugfQhQ=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f28bf829-d4ad-49e0-05ce-08d59942fe58
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Apr 2018 09:12:15.5459 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1551
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SbUhTYRTHe+69m3fDxXX5clAEHUWhObVXicj6sPKDlkRFjCy3vOhwTrtX Je1DEiQ2Ga2YlaItc0mF0YsrhwrqfCNMzTlM0ybaEGVCpjidguV2F/Tt9z///znneR4eEheX 88JJlaaQZjQKtYQvJKovt5yNY2Td8oROU1CSs3acSBqbnSZOYimtvesBKSaTB0vH5MLjWbRa VUwz8ScyhTmuejdR4Mq9Web6hspQ00UtEpBAHYIZRxXuZTHVg2Bu5JwWCbe5GYF91kxwwo3A bf/tFyYM3o/28ryCoJYxeOdpwjnnAQamNgPGiWkEd5Ye8rWIJPnUMXBaU71LgikGOvWTPC/v omTgcrRiXP00zE56cI6VUPVyAHmZoHaD7cemLyOirsBEzyqPm79CwMabcV+DgEqG4YUp31BE RYK+7bmvGafC4LvTiHE3pcDUPoxzHAILP7f8eSW8vWvxZ6Lgo62f4DgSbMZK5F0GlBkDw9o8 4oxE6H/V4R80yIc/GwKO06BivdGfmUBgqS7iOAbsZYP+ei7095kDOL4Fuq5HmB4l1Px3Vo6l MF5l4HMcC431LrzG9wBB8LnaSTxDxGsUwtKsMi/7wEEpzaius2y+RqqhCz+g7d/RZd7cY0Gj i6esiCKRJFBEJHfLxTxFMVuSZ0VA4pJg0VC7VS4WZSlKSmkm/xpTpKZZK4ogCUmYaOZos1xM ZSsK6VyaLqCZfy5GCsLLEKs3q5c/ZceXrkXvw+ua4ivLX7TodmZcWrlhPDwnHdzKq6s/c++L 4/YTicEi4wWkqLV7F92Bnh4ZOVSvE7rSzkcrr9Z91dTawnd0PJY19I3EXggVP/01lbw2kppe bnAanftXVUfSbY6KgZrIhrG4+ajQtPszxJIu096eUVEeISHYHEViDM6wir8tZ7idGQMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/dUNHBkQxoS74ApG21C2ob8TNzpI>
Subject: Re: [CCAMP] FW: I-D Action: draft-ietf-ccamp-mw-yang-03.txt
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, 03 Apr 2018 09:12:24 -0000

Good point Tom,

i don't think we need a reference any longer. 

BR
Daniele  

> -----Original Message-----
> From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of t.petch
> Sent: lunedì 2 aprile 2018 14:22
> To: Jonas Ahlberg <jonas.ahlberg@ericsson.com>om>; ccamp@ietf.org
> Subject: Re: [CCAMP] FW: I-D Action: draft-ietf-ccamp-mw-yang-03.txt
> 
> Jonas
> 
> I am sorry I did not get back to you earlier; IETF weeks and their aftermath I
> always find hectic (and am still catching up on this, a Bank Holliday:-).
> 
> I have looked at the module as now published and yes, it looks good.
> 
> I did wonder about the Informative Reference to ahlberg-ccamp-microwave-
> radio-link
> long expired and so not so easy to get hold of.
> 
> I was thinking that it could be recycled just so that there is a version readily
> available for anyone wanting to chase down the reference but, given its
> content, it would probably throw up 1001 warnings or worse; so, probably
> left as it is.
> 
> Should it still be there as a reference?  Probably one for the chairs to assess.
> 
> Tom Petch
> 
> 
> ----- Original Message -----
> From: "Jonas Ahlberg" <jonas.ahlberg@ericsson.com>
> To: "t.petch" <ietfc@btconnect.com>om>; <ccamp@ietf.org>
> Sent: Wednesday, March 21, 2018 5:48 PM
> 
> Hi,
> 
> Thank you for the feedback.
> 
> We have now updated the draft, A YANG Data Model for Microwave Radio
> Link, based on the comments received in mail and on the presentation earlier
> today, see below We would like your comments before we submit it as a
> new revision.
> 
> The changes are:
> - "Interface identities", "Radio-link-terminal mode identities" , "Coding and
> modulation identities", and "TDM-type identities" have been broken out
> from the main module and put in a new module "ietf-microwave-types".
> 
> - Added an editor's note that "ID-draft editors" should be changed to
> "Editors"
> 
> - Added a single editor's note that all XXXX should be replaced with the
> proper RFC number, instead of one note for each case
> 
> - Updated draft-ietf-netmod-rfc7223bis to RFC8343
> 
> - Updated requirements language with a reference to RFC8174
> 
> - Updated to a consistent use of dot "." as the decimal separator
> 
> - Added QAM, BPSK, and QPSK to the list of acronyms
> 
> Dates remain to be updated before submission.
> 
> The complete text file can be found on the GitHub https://github.com/ietf-
> ccamp-mw/IETF-CCAMP-Microwave-YANG-Data-Model/tr
> ee/master/YANG%20Data%20Model/2018-03%20-%20draft-ietf-ccamp-mw-
> yang-05
> 
> Regards
> JonasA
> 
> 
> -----Original Message-----
> From: t.petch [mailto:ietfc@btconnect.com]
> Sent: den 16 mars 2018 13:01
> To: Jonas Ahlberg <jonas.ahlberg@ericsson.com>om>; ccamp@ietf.org
> Subject: Re: [CCAMP] FW: I-D Action: draft-ietf-ccamp-mw-yang-03.txt
> 
> Jonas
> 
> A structural thought.
> 
> You have a number of 'enumerations' such as  coding-modulation and tdm-
> type.  How stable are they?  How does their life cycle compare with that of
> the rest of the YANG module?
> 
> There is a tendency, prevalent in MIB modules but carried across to YANG, of
> seeing these as more volatile and being placed in a separate module, a
> separate RFC even (e.g interfaces and interface types), so that when they
> change, rather than having to reissue the entire module, just the module
> with the enumerations is reissued.  (The ultimate in this is having the control
> of the list placed in the hands of IANA with a revision policy of Expert Review
> so that nothing needs re-issuing).
> 
> I started to say that I am not familiar enough with the likely evolution of .....
> and then saw that I can see no reference for QAM to follow that line of
> thought.  I think you need a reference for QAM.  I would also include QAM in
> the list of abbreviations, perhaps with BPSK.
> 
> Tom Petch
> 
> ----- Original Message -----
> From: "Jonas Ahlberg" <jonas.ahlberg@ericsson.com>
> To: "t.petch" <ietfc@btconnect.com>om>; <ccamp@ietf.org>
> Sent: Monday, March 05, 2018 8:02 AM
> Subject: RE: [CCAMP] FW: I-D Action: draft-ietf-ccamp-mw-yang-03.txt
> 
> 
> Hi Tom,
> I tried to address your comments in time to make a new submission before
> the cut-off time today. Maybe I was too quick, but I expect that we will get
> more comments after our presentation/discussion at IETF101 and we plan for
> a new submission after that. Then we will include your comments as well.
> Once again, thanks for your effort to review our draft.
> 
> Regards
> JonasA
> 
> -----Original Message-----
> From: t.petch [mailto:ietfc@btconnect.com]
> Sent: den 3 mars 2018 14:07
> To: Jonas Ahlberg <jonas.ahlberg@ericsson.com>om>; ccamp@ietf.org
> Subject: Re: [CCAMP] FW: I-D Action: draft-ietf-ccamp-mw-yang-03.txt
> 
> Jonas
> 
> That was quick.  You have addressed almost all my comments  (I was
> expecting more time to have another read - I am sure I had some typos
> which I have not found on a further read!)
> 
> I still see
> ID-draft editors:
> in the contact clause which is true right now but which should become
> Editors:
> at some point.
> 
> You have added a note the the RFC Editor for most but not quite all the uses
> of XXXX - the ones that might be added are in the IANA Requirements.
> (There are so many XXXX these days that some editors just put a blanket
> statement at the top rather than trying to flag each one).
> 
>  Requirements Language
> These days usually includes a reference  to  [RFC8174]  - see for example
> draft-ietf-netmod-rfc7223bis
> 
> Finally, the decimal point is represented in places with a period and in places
> with a comma; USA versus Europe perhaps. I am ok with it and suspect that
> this is a deliberate choice on your part and is probably the right choice for the
> technical content but might raise some comment.
> ..
> Tom Petch
> 
> 
> ----- Original Message -----
> From: "Jonas Ahlberg" <jonas.ahlberg@ericsson.com>
> To: "t.petch" <ietfc@btconnect.com>om>; <ccamp@ietf.org>
> Sent: Saturday, March 03, 2018 11:11 AM
> 
> Hi Tom,
> 
> Thank you very much for your review of the microwave yang draft.
> We hope that we have addressed your comments in the 04 revision of the
> draft uploaded today.
> 
> Thanks again,
> JonasA
> 
> 
> A new version of I-D, draft-ietf-ccamp-mw-yang-04.txt has been successfully
> submitted by Jonas Ahlberg and posted to the IETF repository.
> 
> Name: draft-ietf-ccamp-mw-yang
> Revision: 04
> Title: A YANG Data Model for Microwave Radio Link Document date:
> 2018-03-03
> Group: ccamp
> Pages: 46
> URL:
> https://www.ietf.org/internet-drafts/draft-ietf-ccamp-mw-yang-04.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-ccamp-mw-yang/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-ccamp-mw-yang-04
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-mw-yang-04
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-mw-yang-04
> 
> Abstract:
>    This document defines a YANG data model for control and management
>    of the radio link interfaces, and their connectivity to packet
>    (typically Ethernet) interfaces in a microwave/millimeter wave node.
>    The data nodes for management of the interface protection
>    functionality is broken out into a separate and generic YANG data
>    model in order to make it available also for other interface types.
> 
> 
> -----Original Message-----
> From: t.petch [mailto:ietfc@btconnect.com]
> Sent: den 1 mars 2018 12:06
> To: Jonas Ahlberg <jonas.ahlberg@ericsson.com>om>; ccamp@ietf.org
> Subject: Re: [CCAMP] FW: I-D Action: draft-ietf-ccamp-mw-yang-03.txt
> 
> Jonas
> 
> Some administrative thoughts on the YANG in  this I-D, most applying to both
> YANG modules.
> 
> The contact list has  i-d draft authors; suggest editors
> 
> The description clause copyright statement is incomplete.
> 
> The description clause lacks a statement as to which RFC this comes from.
> 
> The revision should say 'Initial revision'
> 
> Add an RFC editor note to replace the dates (plural)
> 
> The case of xxxx varies; suggest making it XXXX and adding note to the RFC
> Editor to replace <all> occurrences thereof.  Some in the YANG module might
> get missed (and some authors use xxxx to mean one thing and XXXX for
> something else:-).
> 
> import ietf-interface-protection
> add a reference; in the RFC it may be obvious where this can be found but
> when the YANG module is extracted and on its own, there will be hundreds
> of potential RFC to choose from
> 
> import iana-if-type
> Again I would add a reference - I know, it is well known but I am  fan of
> stating the obvious in a technical document
> 
>  import ietf-yang-types
> ditto
> 
> You reference rfc7223bis
> Suggest adding a note to the RFC Editor to replace this with the number
> assigned to that when it becomes an RFC; the RFC Editor has asked for such a
> note.
> 
> ETSI References need more work.  The YANG module has references to  ETSI
> TR 102 311  ETSI EN 302 217-1  ETSI EN 301 129 all of which should appear in
> the Normative References of the I-D and none of which do; and they then
> need to appear in the text part of the I-D lest they are flagged as unused
> references
> 
> You do have
> EN 302 217-2 [EN302217-2]
> but that is a different version:-)
> 
> And there is a general problem; the reference clause uses ETSI EN 302
> 217-1 whereas the existing Reference for EN302217-2 drops the ETSI and
> drops the spaces; obviously the same?  May be.
> 
> So I think you should include a paragraph, or table, perhaps as Section
> 4.1 saying something like
> 
> "   This module imports typedefs from [RFC6991] and
>    [RFC7223bis], ....
> 
>  and it references
> 
>  ETSI TR 102 311  [TR102311]
>  ETSI EN 302 217-1 [EN302217-1]
>  ETSI EN 301 129 [EN301129]    "
> which is the sort of thing that
> draft-ietf-netmod-rfc7277bis
> does.
> 
> reference "ITU-T G.826";
> reference "ITU-T Rec. G.808.1";
> ditto
> (and perhaps making the style the same, with or without Rec., even spelling
> it out )
> 
>  Tom Petch
> 
> ----- Original Message -----
> From: "Jonas Ahlberg" <jonas.ahlberg@ericsson.com>
> To: <ccamp@ietf.org>
> Sent: Monday, February 26, 2018 1:35 PM
> 
> > Dear CCAMPers,
> >
> > The draft of the YANG Data Model for Microwave Radio Link has now been
> updated.
> > The structure, format and content of the document have been changed to
> adhere to "Guidelines for Authors and Reviewers of YANG Data Model
> Documents", draft-ietf-netmod-rfc6087bis-15.
> > A few editorial changes of the actual yang models have also been done,
> but the structure and content remains however the same.
> >
> > In all, the authors believe the draft addresses all the comments and
> would like to ask for WG LC.
> >
> > BR,
> > JonasA (on behalf of the co-authors)
> >
> >
> >
> > -----Original Message-----
> > From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> > Sent: den 26 februari 2018 14:23
> > To: i-d-announce@ietf.org
> > Cc: ccamp@ietf.org
> > Subject: [CCAMP] I-D Action: draft-ietf-ccamp-mw-yang-03.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Common Control and Measurement Plane
> WG of the IETF.
> >
> >         Title           : A YANG Data Model for Microwave Radio Link
> >         Authors         : Jonas Ahlberg
> >                           Ye Min
> >                           Xi Li
> >                           Daniela Spreafico
> >                           Marko Vaupotic
> > Filename        : draft-ietf-ccamp-mw-yang-03.txt
> > Pages           : 44
> > Date            : 2018-02-26
> >
> > Abstract:
> >    This document defines a YANG data model for control and management
> >    of the radio link interfaces, and their connectivity to packet
> >    (typically Ethernet) interfaces in a microwave/millimeter wave
> node.
> >    The data nodes for management of the interface protection
> >    functionality is broken out into a separate and generic YANG data
> >    model in order to make it available also for other interface types.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-ccamp-mw-yang/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-ccamp-mw-yang-03
> > https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-mw-yang-03
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-mw-yang-03
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > CCAMP mailing list
> > CCAMP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ccamp
> >
> > _______________________________________________
> > CCAMP mailing list
> > CCAMP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ccamp
> 
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp