Re: [netmod] syslog-model-17 shepherd writeup issues -references

"t.petch" <ietfc@btconnect.com> Thu, 14 December 2017 11:55 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08ADD126BF0; Thu, 14 Dec 2017 03:55:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-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=btconnect.onmicrosoft.com
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 1TfWs04l9sGl; Thu, 14 Dec 2017 03:55:28 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0091.outbound.protection.outlook.com [104.47.1.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 518D3128959; Thu, 14 Dec 2017 03:55:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=X9feSYdBJgXNSHFA6BvyjrF5fQ9D3JWvOeMTERMROmw=; b=LPipBPXb/gCwRQHkikaAN8pHcowrCVQfUYknImr/qVu2SAx/cBwp+OBRyz8ILJx33aAV02aLPBrhmgrfJYQADu+WFuA1efDP5nl32vS7pYX3qgQ451Eo8IWnApNuGL7V/WBKYFbQZQ1V8lS/JMXVj20pxp5tQwpd8LCI//Qtwz4=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
Received: from pc6 (86.169.153.236) by AM5PR0701MB2993.eurprd07.prod.outlook.com (2603:10a6:203:48::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.323.4; Thu, 14 Dec 2017 11:55:24 +0000
Message-ID: <004401d374d1$e1fb3540$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Clyde Wildes (cwildes)" <cwildes@cisco.com>, "Benoit Claise (bclaise)" <bclaise@cisco.com>, Kent Watsen <kwatsen@juniper.net>, netmod@ietf.org
Cc: draft-ietf-netmod-syslog-model@ietf.org
References: <49B4BE2F-6912-49BE-9E4A-830146309AB2@juniper.net> <019b01d32c76$fa7dfc40$4001a8c0@gateway.2wire.net> <8CF097E4-CEB7-4C4E-AC7D-F7F896CD1BB7@juniper.net> <00ae01d32d74$49e24c20$4001a8c0@gateway.2wire.net> <5CE9EE07-D75D-4E5C-BC70-1F969732A526@juniper.net> <8e873d52-a6bd-87ee-9ff5-62c85eb5b6dc@cisco.com> <8015AC50-45CE-4813-B77B-8D1D3D3BC349@cisco.com>
Date: Thu, 14 Dec 2017 11:51:12 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.169.153.236]
X-ClientProxiedBy: AM4PR0202CA0023.eurprd02.prod.outlook.com (2603:10a6:200:89::33) To AM5PR0701MB2993.eurprd07.prod.outlook.com (2603:10a6:203:48::15)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 549a3a17-4a63-45bb-47dd-08d542e98f78
X-Microsoft-Antispam: UriScan:(178726229863574); BCL:0; PCL:0; RULEID:(5600026)(4604075)(4534020)(4602075)(4627115)(8989060)(201703031133081)(201702281549075)(8990040)(2017052603307); SRVR:AM5PR0701MB2993;
X-Microsoft-Exchange-Diagnostics: 1; AM5PR0701MB2993; 3:UVnGEel7stGPGte4xi9GzwQO1QYJORlsKoqHdcOoI9OL/ft5JvNS2aPZGpTJekEhYeaXDOrQCE8k80Pe4qsdToXw5W6oLru/PLK7Vd60WNAIp7toMzYXLX5DZBBBo/mOu4wTl70hJPhQM04ZrgK8i10Wh2uEui6yiHALCRqhMP41c+B6+ID6aPVKfAeGU9eq/DC+Yp7pOBdTna54SDzLjuqndM4iwf/aydwG3NMA4jUUQcVOe4owWwC91SDCc1LcJr/0l5CgdSZJK1ncYYUcJUit/MaOX+b9jwv26EYFodY=; 25:/MDgCQOpVwyCrv/BM6ARIvFf9RsIAd/MpB6TJP4SJVMWqC7KJ5HPrwEZIaJsym2joDg97zevNLsOLv7Fa4P3KPzF7zB8L2sLOFl/OX9+Dy0kspAilYw3mgdyvBYx6dcimVptUBbvCvBf9DlsO9OY1QbggyLPTdn3zosy15uQUMwVXyaK1ooI/ZNLtNJrAU2YhHd3iIbznNUtp3IIPMPazmEtQFd9TvwmVB8kye5/TNzydATJ7UJkIWYcWlQ8/MmjKO7uGOn+u5nvQMBOWD2Qwp19zpl8FUKXUOrdl6ABqA00VoDz8dPSlbubJyT/uXUpo9oSCuocY6IH49y/pQTFi4nOBF+vM7lp3bvxisoZLqU=; 31:T9qNAN2+Sz68scmFfgvh6x13uEZjrZV+66QsPmRdDLw/SyEMiuiK0bSlm1bfvkfpyIzVO0R3X6y501tZKdVqM85QQQwZt5YmX3Xbg/6UZfhD1BLDr7NFLc/52gXaO8VyFfFmyyL85itCSBJFdA3E7M5BfTTQL/PjV2qJ154DhNzRRA78hn1yxhCNn9DBbupgs2X+UzJpdRWWl6RbCORHxfghjIY/UPFEux35U8T35h8=
X-MS-TrafficTypeDiagnostic: AM5PR0701MB2993:
X-Microsoft-Antispam-PRVS: <AM5PR0701MB299344DC45F4A0C147DDF1C8A00A0@AM5PR0701MB2993.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(178726229863574)(138986009662008)(95692535739014);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3002001)(3231023)(61426038)(61427038)(6041248)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123555025)(20161123560025)(20161123564025)(6072148)(201708071742011); SRVR:AM5PR0701MB2993; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:AM5PR0701MB2993;
X-Microsoft-Exchange-Diagnostics: 1; AM5PR0701MB2993; 4:I8ncE/dYva2xTvoJ38kwPTf8mT7cZYgQElwxP2pYzrAr65aK4xBW60V74PtfeeHLPH6F21t88Tcm65S4ke91eLPbwY3n4d674x3tTiRZBtGAoHi6egQrtG+pF4rzMxksKhP+PDoKPk6LizZ86gr0VGKhVKd3Ix0vTnFuogPxBEnPov6IOTMFUJImWO2qiUb6HlIlpYcbhfZFW4jc3prb4GY34OE+ObEOrDWxB6O7Hwz44IAsQGi9ULLJcqf+dZkJq/mZ8oUFYtWB7fUbbErsV7JY62GInswj6rRxL4XBCIWyLhXbXZ/sZ/081p5JcQi/i58h9Nqcf6/Sz/kjgSoIr0isaxgam3X4+PaMyF/XxcbaWJmkrVDyeKrfO2RyB2t+
X-Forefront-PRVS: 05214FD68E
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(376002)(39860400002)(396003)(366004)(346002)(51444003)(57704003)(189003)(24454002)(199004)(13464003)(81816011)(76176011)(6116002)(7736002)(3846002)(81686011)(47776003)(305945005)(53936002)(4720700003)(68736007)(5660300001)(25786009)(84392002)(6666003)(4326008)(66066001)(62236002)(44716002)(6246003)(50226002)(23676004)(52116002)(8936002)(14496001)(6496006)(5820100001)(50466002)(61296003)(229853002)(33896004)(16526018)(93886005)(97736004)(9686003)(6306002)(6486002)(1456003)(8666007)(966005)(316002)(1941001)(53546011)(2906002)(386003)(116806002)(86362001)(2870700001)(81166006)(81156014)(575784001)(8676002)(230783001)(106356001)(110136005)(105586002)(478600001)(59450400001)(1556002)(44736005)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM5PR0701MB2993; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en;
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: 1;AM5PR0701MB2993;23:sRtNOsNUC8U2OxpNHO43RIHxkGBHj0DVHdO1fk3bHeH5eg2NaoM/icSLzPHVk+V3POO0FePq8LbA8bO+NbJGL8f/fYm6778dBvbwEie7xz9uPzFyiD3/Q2pFb8hMJyJ768dIxTLGu03uX94iY2JUx0zZjO/PQ7uFy3vu2WhZb1yq1glHaxsVz+63d863QWhsAiydJCDyCY2QSOxdi8d4bQGPe1XiXwsicwJ1HIfJb78b8zUZj2p0y/d5uLeDmuoJZGvAMNQF59oNsgeJsbo/q1A3lLlIH9OhrKdGdF2C4YyMkM0W0DqbP/Kr0azjPvyq9Nf38HpfdvDprx9RwvWTdfImuxLu1BdRdhQEKBtdNZPXXb5EBtisMkKVgj26Pk9gP1Ccd73zE/Ux5/LMyGH8RCLpISy5hTcXYZ787jWOqOTjon18YAsJemmt4ksAc0I8b8jiDlPGOrCgfh6hz/mVZOYN2yzJvEYmzN/zMlQxCfiw8sllsBHwc0J9rpI5Ig4Nx1t1R3s6lNt8ecVB1B3FMDQ8Epi7YLNFsdiSC3Leyi0puzx57CV748eQ5ztyyh+eDSBEkxWL+bAhmcn3UCtTSDi6l70pcsqnjgTI+hmDC5JVUhsYoRpsURjA7if9P4T0EUr0WRM6w4L9VWXrH1ILRzJfPWYKNcFFKxCQIQWdGU8NldMHJZkJByCyFMbBUS5DhUvm2J37HmV522QUgUfFi+yQVfhsP4dlK9DSh21GkIwb47g6SWeZ+vVVHlpYos4WMgGL4Sf0KiDaR0avPIdl9b4jxFF+co96luYF7I/o2AYe8bMW1jna+X77OFUWk+QFRw4UDhPSIARjD98vluabdqTNMDN7FG/DQbbR2KwOxzGYqz8AsjHAlWy3soxMtGveN4b5Q2GViCGdkjWh6BiS4VG/9Km2HmdZdhgkCCn64kbH6ccW2JDrXS6ABES17BUeVuaoKY4zxFzIErZ7C6Dq4TGLzCMRrTUI6UCLTr3P7hv8fc31CzviPHjo9sfApMOKUc7eXDOebuIB7DWVTHMHeSX77uN2ZmHTuxj6AdFOEhX40iDV9plhZw432wpWCl2+ihrGYZ4eWTWQ3Nv0k1hKjfwUZ9/S7Nf/ciaeAbbxMpNvNF8ZWmjhuBQmoNn1WI5HpsCsqp4oi7jL/YZmmyM6aWqwZASvoSJOHmP1POcIzek/KTy/ITW0qRwjyF0/s+lisHrMdj+zt9rKLAjFZJSRTMNkG1RkJbwQBwomftAJ7bFsNG4ugF+Ux3rlGMTwNvKgpSL8WPM5PAidN2GUjPn/ECoiJ3oljDLoEe17pm/grzQyZMC5q7i6J258YY35d3jSa9SBTQWp2/WfIiVZCRlqYHRGXWta4wl4fA4ls//Hw6egEyeBgE41hpI6SSF+GW8Wl0adUjEBdvYxyMh9ENhq4OWeQywNWrULpNKcCJuagcd42HrJ2dMJrQdVycCV6KAqIVUz39K/WQG3R8Pbzffw1J2HfGX3JrVxjOExTqblth1LTdfCQc0t3JXGMwAbgoc4+KkwSuMX5x0XCOF6joU4/PtPehQ/Uzwa+h3OOoBV2ghSt4h3rwISxC1yGyx0QVfgbNtiUV0qtlzFpjEWq5YPAJrfayvqyxIVpzmgWXZSjUY=
X-Microsoft-Exchange-Diagnostics: 1; AM5PR0701MB2993; 6:6nkc8K9vSyFGIkGv1U3Ga2HP9YtP/d5UX/Zw4Tt4/3BNJqxExsUahb0UeMF7tlraE88nexFw8F0yyi9ewlG81yh3gdBamP3zkPyvMxTp+tb9fCFsoqxAU8EaiEO3+9m/GffdMz0vg5HwwZ9XXzFW6i4yvHZZ6pCTsixMxOtAfIqWNSmv4MZMPzNwzLtpp8JDAgOkkOCtCe6Qe+o184+q+hbfmAxeErZl954oTQ4v6u9UIgdxG6iEn0PohOYR7etq+/bN+msp3bkk2RfEKLhmYC1aElec+GAAd4L4FuJ7PzwI9P/IETZL9KlzalSNbaoNLukE/49hBWXV5Xys8OyVuUd/h0w/QyhESgHu9+MqvLY=; 5:UTmkgJUhAQGhsOJZZ/d/M1hqbw158RpjtWNeSPcI2vKSCYDv4A6IsnuzGqK7VEYiTQfXcfJFU19/Ae0Rp+zVYgku5y0sAB58a3mYyi3R+yBQb34cwYQWAYqAitGffAlrq9yarTEP6LcVKdjLhfn0fYsib3cQ2isQZqZZkST0zec=; 24:NtYiVaKaHsnnZRkqQKA0hleTyV/i5AxXfdV/Z/XfGCzxKvPgHKjSzJ3j8MdhdtugNNQlxIuvf3QrtVYnZzcT15/3dyjXV16ClQFBn1CBGSo=; 7:dPwqwRQT5u6voarcVAiscluMuGmOwiCtqUfTpv16lG9CYmsWCxSfE0N5ZEHgnteAV7QN8Rg55dtSveR6kgpQthbPnrcYiOeJiFtvDacdjdMTb9yCFSCzKlPVuFmQUrreRZkfaqQDPcfgMHcyvO8mXC8yFV7EzFvO0L+2jzXEpX4xW/qpKrKB6q5iqYtEuLc2O9+ZHOgE6DqJohMr6f6yorsdM/EofB5gvsXvw/Q8j4K1WD3plI8rQkArBB8acKyN
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Dec 2017 11:55:24.0412 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 549a3a17-4a63-45bb-47dd-08d542e98f78
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2993
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/dYWP-WY1l_LS93Y7JQHeLE0KYkM>
Subject: Re: [netmod] syslog-model-17 shepherd writeup issues -references
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 11:55:32 -0000

Clyde

A quick glance at -18 shows that there is now a Normative Reference for
Posix - good- but I do not see it referenced - not so good:-(

I think that there needs to be a reference in 4.1

Tom Petch


----- Original Message -----
From: "Clyde Wildes (cwildes)" <cwildes@cisco.com>
To: "Benoit Claise (bclaise)" <bclaise@cisco.com>; "Kent Watsen"
<kwatsen@juniper.net>; "t.petch" <ietfc@btconnect.com>;
<netmod@ietf.org>
Cc: <draft-ietf-netmod-syslog-model@ietf.org>
Sent: Wednesday, September 27, 2017 5:26 PM
Subject: Re: [netmod] syslog-model-17 shepherd writeup
issues -references


> Benoit,
>
> There were approximately 24 changes requested from you, Kent, Robert
Wilton, and Tom Petch. I have made approximately half of them and will
try to finish another revision of the draft by Friday.
>
> Thanks,
>
> Clyde
>
> On 9/27/17, 3:24 AM, "Benoit Claise (bclaise)" <bclaise@cisco.com>
wrote:
>
>     Clyde,
>
>     Do you know your next step to progress this document?
>
>     Regards, Benoit
>     > I meant to say something about the .1 vs .2 difference.  My
comment
>     > assumes that it's supposed to be .1, but we of course should use
>     > whatever is correct.
>     >
>     > I also don't know much about that standards body.
>     >
>     > K.
>     >
>     >
>     >
>     > ----- Original Message -----
>     > From: "Kent Watsen" <kwatsen@juniper.net>
>     > Sent: Wednesday, September 13, 2017 6:08 PM
>     >
>     >> Hi Tom,
>     >>
>     >> Thanks.  The fix I'm looking for is for the 'pattern-match'
leaf
>     >> to have a 'reference' statement to Std-1003.1-2008, and for
S4.1
>     >> to also list Std-1003.1-2008 as a draft-level reference.
>     > and I am unfamiliar with that standards body so am looking for a
little
>     > more.
>     >
>     > Is STD-nnnn always Posix or do we need to say Posix 1003 or
Posix
>     > Std-1003 or is Std-1003 completely unrelated to Posix 1003?
>     >
>     > Is there a difference between Std-1003.1-2008 and Posix 1003.2
ie is the
>     > .1 or .2 significant?  You want Std-1003.1; the description
contains
>     > Posix 1003.2; the normative Reference is to Std-1003.1-2008.
>     >
>     > You pointed out that the Normative Reference is not used; well
if we can
>     > sort out what the standard is and get the right label in
Normative
>     > References then we can - must - include this in Section 4.1
which will
>     > resolve that comment of yours.
>     >
>     > The discussions last July had Clyde saying he wants Posix 1003.2
so if
>     > Std-1003 and Posix 1003 are the same but .1 and.2 are different,
then
>     > you are asking for a semantic change against Clyde's wishes.
>     >
>     > I hope my confusion is sufficiently clear, at least to Clyde!
>     >
>     > Tom Petch
>     >
>     >> I was going to point out the typo "the the" as well, but
figured
>     >> that the RFC Editor would get it.
>     >>
>     >> K. // shepherd
>     >>
>     >>
>     >> --
>     >>
>     >> Kent
>     >>
>     >> You flag Std-1003.1-2008 as listed as a normative reference but
not
>     > used
>     >> anywhere in the document.  In the Descriptions, but not in the
s.4.1
>     >> references, I see
>     >>
>     >> This leaf describes a Posix 1003.2 regular expression ...
>     >>
>     >> twice, which may, or may not, relate to this issue.
>     >>
>     >> Back in July, clyde said
>     >> "I will insert a normative reference to POSIX 1003.2 in the
next
>     >> revision of the draft."
>     >>
>     >> In a similar vein, RFC6991 appears in a reference statement but
>     > nowhere
>     >> else.
>     >>
>     >> As you point out, RFC6021 is referenced but is obsoleted by
RFC6991 so
>     >> should not be.
>     >>
>     >> And in a slightly different vein,
>     >>
>     >>     registry [RFC7895]/>.  Following the format in [RFC7950]/>,
the the
>     >>
>     >> looks odd for plain text and for the repetition of 'the'..
>     >>
>     >> Tom Petch
>     >>
>     >> ----- Original Message -----
>     >> From: "Kent Watsen" <kwatsen@juniper.net>
>     >> To: <netmod@ietf.org>
>     >> Cc: <draft-ietf-netmod-syslog-model@ietf.org>
>     >> Sent: Tuesday, September 12, 2017 10:50 PM
>     >> Subject: [netmod] syslog-model-17 shepherd writeup issues
>     >>
>     >>
>     >>> Clyde, all,
>     >>>
>     >>> In reviewing the draft for Shepherd writeup, I found the
following
>     >> issues that I think need to be addressed before the document
can be
>     > sent
>     >> to Benoit for AD review:
>     >>>
>     >>> 1. Idnits found the following:
>     >>>
>     >>>    Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 1
comment
>     >> (--).
>     >>>      ** There are 2 instances of too long lines in the
document, the
>     >> longest one
>     >>>           being 3 characters in excess of 72.
>     >>>
>     >>>      ** Obsolete normative reference: RFC 6021 (Obsoleted by
RFC
>     > 6991)
>     >>>      ** Downref: Normative reference to an Historic RFC: RFC
6587
>     >>>
>     >>>      == Missing Reference: 'RFC5425' is mentioned on line 359,
but
>     > not
>     >> defined
>     >>>           '[RFC5425], [RFC5426], [RFC6587], and [RFC5848]....'
>     >>>
>     >>>       == Unused Reference: 'RFC7895' is defined on line 1406,
but no
>     >> explicit
>     >>>            reference was found in the text
>     >>>            '[RFC7895]  Bierman, A., Bjorklund, M., and K.
Watsen,
>     > "YANG
>     >> Module L...'
>     >>>       == Unused Reference: 'RFC6242' is defined on line 1435,
but no
>     >> explicit
>     >>>            reference was found in the text
>     >>>            '[RFC6242]  Wasserman, M., "Using the NETCONF
Protocol
>     > over
>     >> Secure Sh...'
>     >>>
>     >>> 2. `rfcstrip` extracted "ietf-syslog.yang",  which is missing
>     >> "@yyyy-mm-dd" in its name
>     >>> 3.  neither `pyang` nor `yanglint` found any errors with
>     >> ietf-syslog.yang.    pyang says
>     >>>        for vendor-syslog-types-example: statement "identity"
must
>     > have
>     >> a "description"
>     >>>        substatement.
>     >>>
>     >>> 4. testing the examples in the draft against yanglint:
>     >>>        - for both examples: Missing element's "namespace".
(/config)
>     >>>        - just removing the "<config>" element envelop resolves
this
>     >> error.
>     >>> 5. the 2nd example uses IP address "2001:db8:a0b:12f0::1", but
this
>     >> SHOULD be a
>     >>>       domain name (e.g., foo.example.com)
>     >>>
>     >>> 6. in the YANG module, anywhere you have an RFC listed in a
>     >> 'description' statement,
>     >>>       there should be a 'reference' statement for that RFC.
>     >>>
>     >>> 7. in the tree diagram, the leafrefs no longer indicate what
they
>     >> point at, they now all
>     >>>       just say "leafref".  Did you do this on purpose, or are
you
>     > using
>     >> a different tree
>     >>>       output generator from -15?
>     >>>
>     >>> 8. RFC6536 is listed as a normative reference, but it probably
>     > should
>     >> be informative.
>     >>> 9. Std-1003.1-2008 is listed as a normative reference, but it
is not
>     >> used anywhere in the document.
>     >>> 10. RFC6242 is listed as an informative reference, but it is
not
>     > used
>     >> anywhere in the document.
>     >>> 11. the document fails to declare its normative references to
>     >> ietf-keystore and ietf-tls-client-server.
>     >>>          Note: you manually entered the "[RFC yyyy], and [RFC
xxxx]"
>     >> references…
>     >>> 12.  The IANA considerations section seems asymmetric.  Either
put
>     >> both registry insertions into
>     >>>          subsections, or keep them both at the top-level…
>     >>>
>     >>> 13. reviewing the final document against my original YD
review, I
>     > have
>     >> the following responses.  Let's be sure to close out these
items as
>     >> well.  Ref:
>     > https://mailarchive.ietf.org/arch/msg/netmod/10lo41Ud4A3ZN11
>     >> s-0gOfCe8NSE
>     >>> 1. ok
>     >>> 2. better
>     >>> 3. should be: s/the message/these messages/  [RFC Editor
might've
>     >> caught this]
>     >>> 4. better
>     >>> 5. still feel the same way, but no biggee
>     >>> 6. better, but from 8174, you should add the part "when, and
only
>     >> when, they appear in all capitals, as shown here."
>     >>> 7. fixed
>     >>> 8. fixed
>     >>> 9. you did what I asked, but the result still isn't
satisfying...
>     >>> 10. some improvements made in this area, but my ask wasn't
among
>     > them
>     >>> 11. better
>     >>> 12. better, but I think the 4th line should be indented too,
right?
>     >>> 13. better, but I wish you called S1.3 "Tree Diagram Notation"
>     >>> 14. fixed
>     >>> 15. fixed
>     >>> 16. fixed
>     >>> 17. fine
>     >>> 18. still a weird line brake here.  try putting the quoted
string on
>     >> the next line.
>     >>> 19. fixed
>     >>> 20. fixed
>     >>> 21. not fixed (re: yang-security-guidelines)
>     >>> 22. fine
>     >>>
>     >>>
>     >>> PS: please also be sure to follow-up with Benoit on his AD
review.
>     >>>
>     >>> Thanks,
>     >>> Kent  // shepherd & yang doctor
>     >>>
>     >>>
>     >>>
>     >>> _______________________________________________
>     >>> netmod mailing list
>     >>> netmod@ietf.org
>     >>> https://www.ietf.org/mailman/listinfo/netmod
>     >>>
>     >>
>     >>
>     >>
>     >
>     >
>     > _______________________________________________
>     > netmod mailing list
>     > netmod@ietf.org
>     > https://www.ietf.org/mailman/listinfo/netmod
>
>
>
>