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

"t.petch" <ietfc@btconnect.com> Sun, 17 December 2017 20:33 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 B0E24124D37; Sun, 17 Dec 2017 12:33:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 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] 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 45xnLKirOlWl; Sun, 17 Dec 2017 12:33:19 -0800 (PST)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00110.outbound.protection.outlook.com [40.107.0.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E613124B0A; Sun, 17 Dec 2017 12:33:18 -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=YiFbEBqZ5y0BEoQtQ/E9O4PQpHFdYydVLD0+VZlhJsk=; b=cUNXmO0TpktUsT2Ha/tZ/pSFYPTrlm4/szyelj1MB28OgvMwdrQDCvXD6jTCu0dfVsKpozBFZ+KH/B26RB3w/zC53h52ZbyMOsnpZ4VgP5f01HRkZytKNZfzQ/QA3lvfyjGMnJ69U4ZRJUm4r2DlEQN4zCvam43WEMIL+aA2srQ=
Received: from pc6 (86.169.153.236) by HE1PR0701MB3002.eurprd07.prod.outlook.com (2603:10a6:3:4d::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.345.10; Sun, 17 Dec 2017 20:33:14 +0000
Message-ID: <00f801d37775$b508ad00$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> <004401d374d1$e1fb3540$4001a8c0@gateway.2wire.net> <872D5B29-8411-44AE-BAD2-BAA7D1F50F7B@cisco.com>
Date: Sun, 17 Dec 2017 20:29:05 -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: DB6PR0501CA0012.eurprd05.prod.outlook.com (2603:10a6:4:8f::22) To HE1PR0701MB3002.eurprd07.prod.outlook.com (2603:10a6:3:4d::8)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 54ae2d84-47d8-4040-2ec9-08d5458d6625
X-Microsoft-Antispam: UriScan:(178726229863574); BCL:0; PCL:0; RULEID:(5600026)(4604075)(4534020)(4602075)(4627115)(8989060)(201703031133081)(201702281549075)(8990040)(2017052603307)(7153051); SRVR:HE1PR0701MB3002;
X-Microsoft-Exchange-Diagnostics: 1; HE1PR0701MB3002; 3:RBpuJY8dEKNwU3wxiT29KYnU/blNNPjZKBS3caJ2f7DqOGFIUrR7FkzTCNpUCUWFnsj2ihxcyJprfj5CnS2cbfRxS6XAKE3Egq8ld9hPSl8q2hgnU4otxHJJRBnRB3DKYXqXpb6q/gIqG/tG2dWuP9h5uBqbkg8vBJSE8dk7ucIzw/UiTBQyl6z61nnK6KYSOYnTjrKobyD2PHBW+YGapL+klOOz/Wmcfg8RHIn5548YKul+Sb1LVmWywTcjcBayeKlesyJ2tQqtR20pMaFue/sGStrrAK0hQkacnjwY4cI=; 25:1gGA4U12F/eXPCL1wh0j26TsqpE8ZBIN7crDgDGEb5We+K3bN1LGLpmiCiaqmMGRSl7ApAmJ8XT6RGdo29Kb4EZGbqfZiStBcsUolwrsv1cATEKv7w3NTVq9lVd6ahTl7ga43M8beYxQEFK4ADzNC8aurlpSqYxFJ8MXcEqNqeqZi8DQf6PcOo3pKD6U5ijQ4jGERcdYJ7p8p1UsH574IS1jkt2ZBXRqFKsbAYUF71eAqx0k2tCJ1bptBR7bFGwyvu+K57cY3tY+tksb80prh/xI7Ziq3HxW/ZnrWFDZMCv9As/p6QReDapQV133bgp6+uyvVt5TXvx6h/j6616gEA==; 31:GXmKi/izu3z5Pnb7ivhLEEWodIOCtK32cpMZoMJ4ACU+VPk2krObBJmc5ooSjDs042RdSmjikxsmwX0krcUbZpVOvWvpqxTteESgaDj0FDQOyl44erCVxmOJFvZcc/jRKJLs9s+WUi1iP6PTLEOtqviZdOuTDhHiQOKYV8LGyEvIWaU1GhZ0vhMSqJAWmvtrcUlbc2U0nagRnBefS/hezzFve36M0aQOiFxNXR8+Iew=
X-MS-TrafficTypeDiagnostic: HE1PR0701MB3002:
X-Microsoft-Antispam-PRVS: <HE1PR0701MB3002AAE7FD85A7711251D3B8A0090@HE1PR0701MB3002.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)(3002001)(3231023)(10201501046)(93006095)(93001095)(61426038)(61427038)(6041248)(20161123560025)(20161123558100)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123562025)(6072148)(201708071742011); SRVR:HE1PR0701MB3002; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:HE1PR0701MB3002;
X-Microsoft-Exchange-Diagnostics: 1; HE1PR0701MB3002; 4:3CrBUoI2Qbr249OpWM3/l3mYty16u7TjuwUi+N/YtuS4H8cW0MQ3oAC5h5wJ/FclCXdIa5HQeCRs7iAVuQfIP+JuxzpTz2dX4VHaGsbaYo9eLf2b3kQAXc9Ch8SkBcnS68tfdDVmPgaPD10XPs6HegvRSLT+bZMoYomFcKsZzsh2INhPeV3XeZO9v1RZ9YRlkRYoVTJUPZagZlBgg6+9GCp27ZjXAUk5TRrTUY+imTQb9aMd9epeMAPl/f0F9gNguxIsnncVkbSwoPhR+6Va19E901QATNR+wcNFHg52BU2FsowM0XADmpLrft1XcfJU/asNO034PRLqp7R/ww4AcbxT/brO7nwGznz1dcZ3JnXH5kf0c4OnSyUcae2Mb2lA
X-Forefront-PRVS: 05245CA661
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(39860400002)(346002)(396003)(376002)(366004)(13464003)(53474002)(57704003)(189003)(24454002)(51444003)(199004)(14496001)(6116002)(50466002)(59450400001)(110136005)(478600001)(966005)(86362001)(575784001)(116806002)(44736005)(229853002)(93886005)(6306002)(8676002)(81166006)(81156014)(106356001)(105586002)(6486002)(8666007)(3846002)(1556002)(230783001)(9686003)(7736002)(305945005)(316002)(5660300001)(53936002)(6246003)(4326008)(84392002)(4720700003)(6666003)(1456003)(52116002)(2486003)(62236002)(2870700001)(47776003)(44716002)(76176011)(81816011)(386003)(66066001)(53546011)(25786009)(81686011)(6496006)(23676004)(68736007)(1941001)(61296003)(8936002)(16526018)(33896004)(2906002)(97736004)(50226002)(116284003)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0701MB3002; 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)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3MDFNQjMwMDI7MjM6SytwdnlrUDlqZ1dFN1BhZ0Z3YWJjYkg4?= =?utf-8?B?RlhmMEE3YkgrSjZWZXNOMzVZQ2h2RjB5RC94ZEJQbEZxd1Nrc0t3K1c4S05X?= =?utf-8?B?c3pjTEZpODhETjU1VWlYYnVGQ2N1YVpieldpWDRZV3ozYXR4ZjNOSlVHN0RE?= =?utf-8?B?dVI2WDY2SjFab0V2Unh5WFBHbzhzcmlNUUJGREUrdmo4aWRUZDQrbTJ1eGZE?= =?utf-8?B?V3k2elNzdnEzQzhCTFdraHMvQkFVei9ZMUtLU0N3TEdXMmMxZ25LNWQ2WWZk?= =?utf-8?B?a1hBamR4dUF5OEVSUGo1aVk5K3FaMmNkcmowYTlXRjRra2UrakdaMlVoYi8w?= =?utf-8?B?L044Wjc5UmNoOVpiRGlmTWdOajdGaTZsQTZibjV4VXRYc3I5OUxlSWdVaFJO?= =?utf-8?B?Z1dIMTZ1MGFKQzFPMVJtWXgzdlNFdy9wOVFRUWpDM05mOUUrNjhMTjFJNldY?= =?utf-8?B?cEtYNXR3ME5CRUFMMkhrbmpNYUo0UXJUYmhyM1RSVGM3aWpWMlFLbnpsWkRu?= =?utf-8?B?TkpYbTVKRThZVWdTTkd0Y1E3bEdDM3I2dGt5NGd4Rkkrci9pSE02RFVJSFZj?= =?utf-8?B?UzRVV0ZNY1hkVHpJWDNoYnNsejVsWndlT3MxVGh5RkM1dCtJalE2MEpEUEUw?= =?utf-8?B?YTVBVnRFODdIcFRoWUxGcDArTmlNdUZHU0pUWjJYeFY2RmdHQ0w0NWxMMkVV?= =?utf-8?B?QTJGUXQzTjllLzY1bUxUM2JiclNmZ2tvSkZvUEtlbUp2NFdIemhWYlYzRlhU?= =?utf-8?B?OVlKUXdaWmx3TVJFVVBTTVd1aXZuZlNiOERjZ3dFUWpUNnlDeWQzWUs0UFI5?= =?utf-8?B?RmY4UXgwVlUxVVBjVm9IZ0NkR3dkTWRMU3ZyTkdOL3BxY3ZPVTh4Vm45cWxS?= =?utf-8?B?aVFnZFRCRnNBblRsbFhwTTY3RU5ncEFlOGNCb1ZWTWd3eEh3eHRPaUw3VDl3?= =?utf-8?B?cWVKb0I4V1NSU2dkNkZPK2tRMUJqUkFWWm44RWpGMFRLTlk2Mmt2b1ZDZ3lv?= =?utf-8?B?RkdEUFNHaG1wTTJvbzdsM2ovb1V5ZWFRc0g2NDRGNEJUK3JWYTk1c2FMZmR6?= =?utf-8?B?d3FyYkVyMXdkK1VzVHkvM2VkanAvZ2Z6S05mVXlEbHRYVU1HT1d0THRrMS9Z?= =?utf-8?B?Z29DYmllSUZ5c1pXNm1pR2s4NklhSTBydEJsaUk5OWhOR2FmaklNQ1VPWGJN?= =?utf-8?B?dkZEVlJ0UC9DNUczU0RTV3JHSnNOVTlUdG83NFNWTEFUUGttb1liNWNyMG1Y?= =?utf-8?B?bXNJSVk3bEZHSnFFc2FGcXRxck1zMTJ2aU8xbjIybyttMlJ0VXNjZDB6Q095?= =?utf-8?B?NVlsV3FtNDRDZnF4anFVbUxJdkhPSFBuWTl1NC9FNWtLTUxDenFXcEtIS1Zo?= =?utf-8?B?RkNOckpTR0cxWjJEUmNyL0xFQTVFMkZsM0lIcTBUN214NVZVMWNFRWg1cURD?= =?utf-8?B?ZDlaSytpT1hNbFNJalhRR3kvR090c0hJL0ZYTldJUnRIcnYwUVZkK2hQb3N6?= =?utf-8?B?dzVBaEF5bHJKMGdLbmdMMHY4MG5PYlg1VGsrL1VQK3hTekJuOVRWYkxjRjli?= =?utf-8?B?OEEwSTIyaStrV0EwSmY2dThTb0dsNDFwMFpBWlh6dVA1Um85eWRlRWJ6TnpV?= =?utf-8?B?MTN5NmxWN25QdFdOODRiMzhQNXcrYUoyWW5YSkoyNWVrY0I2bytjMGQxaUdL?= =?utf-8?B?a3pVUlhlbGhNelk0aCtsWlcya2xWUSt3VUd5cDZkQnk2ZnYveUJKWTRuZk9h?= =?utf-8?B?aVEwNndlNkUreG1OVHZqZEt1N2hJUUpXMkp1VTdoR25tMnQzam5aRWsrWmpN?= =?utf-8?B?TVF5Q3BEZ2hkV1F3TzRqbHdscGJTTHpEVkRNdi9GSmZtdW5yZS9scU1WdjlX?= =?utf-8?B?aUdUM3R1anZIZ0sxai9nUWRVVzRBK0lyY2Y3ZnVzNHVyWWdza01jMU5uRXZv?= =?utf-8?B?NmVWU21RRmlNRmFBSmp4SWhnaENRNzd4QmY3a1hyN3ZLSVZ3YUUrS2NzbnlY?= =?utf-8?B?eVM2WG1iOGR2YzVyVVorZU5sNkZJVTRpMjBkY2JUSUduSTViVTg0bUpMWkQ1?= =?utf-8?B?dW05ME9RSnF5R2EyaGpLNHpVVzJHeVdQMkcrSU5zd1kxTjNET2RXZkt3VjNk?= =?utf-8?B?RXhCVjAvblFQYTJWaGo5cGJPeDFEQmMrRzY2c3BndGVBZCtRVEptNVppZ0FL?= =?utf-8?B?b2Q3WHhLNkxvYTNITFMwRmNiT0JETjVyTXh6ZXkwMEhGRTNuem1CT2lrcDNW?= =?utf-8?B?ckoxcjVuMVBOZnk4bUpzcmk5QVZZTG1XVEJvbFVJYzRUOXFKallIc0NRPT0=?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR0701MB3002; 6:0/nycMlotd6xeluxcJp0Z4mgG9qiZq78QP4lun6FSQuZb80ajaX8iAfnzUX4mN9C9+chk30svCnrwQ8F/eArNR5aFINRXQs6VxynFkS3QEHy14TMnOmzBqWsNskfl9lOYtdG42ffxnswTIl0sAkKYETFRS62PSXVxZC4XCB6zCWzyhKaYZJOb4LIYapObBIRO4ucNlX3Nl2lGNVJU13rfTfOrxbmtREPgmVaTnNSxMJwNTBbVuGaoSbKq+qFWlMGlwqQy6Tzr6axKtOqd1lKrK/c8ktFQb6JbjxjLavCDxxffjoNs7uKKk3m54Iq9AJXnL/5gdsjuMrglP00Q7R7XaZfK2Brm/EILtC3YLygaFI=; 5:KWsiKc0hWnYLcA+cSW1weeLrwweWE6N8MVw71xAGQY3O+vjobfCphHxytIw7f8+Hb8TQPwf63m8+vTlOhNjZmVdshBWQ42daTuHXfYZW/s6+oUdh/oKLev1ubAc5jLUc7a9iLtqHQlK1Np/PBmzDgcrqge2b8QiUeDTdww/ERgg=; 24:0lPtx8nJGGBYcp28dzqapbGH1cGUxf76mlub7Dl+Cx9OYAe9Y5xaDkPoWqySSVtFxRp2zWSG9BK5/TRasjffpYEO2Afv64qTIbJHKu3UJ3k=; 7:U5QURb5WtSmEH27ahr+DCcfsnrpmHwgH9hBKoIV2dKOx5FEcDGMZjJL7p9PWfcCLP8hgKOIGTTsPjIREtEpMp9NyysIlyQnF0AF16NL9ecGdwVp/m3rnUtZ33DGg5lTjlKYqLXbaZ1H7+HF4ifFdW+wftWqkMWrOx3n8XZNmWLU6aokYbs374zJjxiC43mYUj4SDa34FK0F00aysjFmvi2c6GNqCBq/AsmiqeVPVZpe1Ekk9s/JyqDmVlzMgF43i
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 17 Dec 2017 20:33:14.1554 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 54ae2d84-47d8-4040-2ec9-08d5458d6625
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB3002
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/FkEzQeLJ31FiijFk-S-ojyafMdw>
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: Sun, 17 Dec 2017 20:33:23 -0000

Clyde

Sorry for being unclear

OLD
   This module imports typedefs from [RFC6021], [RFC7223], groupings
   from [RFC yyyy], and [RFC xxxx], and it references [RFC5424],
   [RFC5425], [RFC5426], [RFC6587], and [RFC5848].

NEW
   This module imports typedefs from [RFC6021], [RFC7223], groupings
   from [RFC yyyy], and [RFC xxxx], and it references [RFC5424],
   [RFC5425], [RFC5426], [RFC6587], [RFC5848], and
   [Std-1003.1-2008].

would satisfy me.

Tom Petch


----- Original Message -----
From: "Clyde Wildes (cwildes)" <cwildes@cisco.com>;
Sent: Thursday, December 14, 2017 5:05 PM


> Tom,
>
> This does not satisfy the reference requirement?
>
>     leaf pattern-match {
>       if-feature select-match;
>       type string;
>       description
>         "This leaf describes a Posix 1003.2 regular expression
>          string that can be used to select a syslog message for
>          logging. The match is performed on the SYSLOG-MSG field.";
>       reference
>         "RFC 5424: The Syslog Protocol
>          Std-1003.1-2008 Regular Expressions";
>     }
>
> Please help me understand what more you want.
>
> Thanks,
>
> Clyde
>
> On 12/14/17, 3:55 AM, "t.petch" <ietfc@btconnect.com>; wrote:
>
>     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
>     >
>     >
>     >
>     >
>
>
>
>