IETF Logo Mail Archive

Re: Yang update from IESG ?

tom petch <daedulus@btconnect.com> Tue, 19 November 2019 09:46 UTC

Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95F1D120854; Tue, 19 Nov 2019 01:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level:
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 bWMmSZMz_eJo; Tue, 19 Nov 2019 01:46:13 -0800 (PST)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30109.outbound.protection.outlook.com [40.107.3.109]) (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 EDF3C120824; Tue, 19 Nov 2019 01:46:12 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ikyV50KgjBVjXPFOIG/74rtVPOH8PgE1/2vjJOmkBB1XQfk0PIJFB8zKdFcGT1G8A3+F6/AeouoVLLHqZQbNR0zheLwpjPI8NZHi2Vl5N8GtONr54QMvNMZNCZdYb0htq7IHe0K5f5xjTaA7OT+jntacIbXyOPEkDsWi2hz/tS+9Q1ITh2RPPlJKfMwFtDwoUHO8cYT1vpowIQhIibG9qhEYakSyOxsY4g7bk/h8usmPDppGmmv4xRkL1xik3H74FOFdN1BBDMyMOXZdr1yLzxwFmCmFWYIrvrZe4b4fd+k/RuyvpCYyX3YE4TBZHF5J7aBWPptbBGaAzQMmKW9gUg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6OJHnJVf4H1ZvXiNqQOsj6OZzXPex2wqCZwhZWYm7vA=; b=ZyivsvkcBYRN51Kq31LZn/CaD7/JiFeXNX8fo1MgqiKyE0dyHy8I/FZR5n1TOeiUO2DIue6bFXyI1azOrBiXkuakEvKXRohVkH6MVqmdIuQvoNQxdkRaXQjWctdpXSKrm3vXULfcCXytrdbJ05CZzHkY4kG+3cQQV7xZlV6qvVCK4b5X5E4T0UW/hVQUPoaiOQm0egzwJrx+HRpZCSUEEWbGmtcUrR3Ohn5fuAmktbBM9/ZD1riL0/P9U2l0L4t+YEKvMVq80l+82nf3Rv+My4DCQHQBnRtQfwv1Z2kFpL94cA7Kc5SOnFC7yeU7RI8IAvHCDtVwb4n7c/v/mZJD/A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6OJHnJVf4H1ZvXiNqQOsj6OZzXPex2wqCZwhZWYm7vA=; b=C68w3ixzwUqlQjGNAyePNGE4CcIs3SXkoESwfrPUgvlXfJ2R3Sz0h+hlM66F9HGYYR3REsdukzAySvkq+SoQdakQ0TMVntocNWFmA1Fyn34q3yRd3OBqaSgHS4DdNHy3Hyh/aC3aebmut610pOLbVkDfTdz1lD4BLStA35TNLcY=
Received: from AM0PR07MB5716.eurprd07.prod.outlook.com (20.178.115.216) by AM0PR07MB6322.eurprd07.prod.outlook.com (10.186.174.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2474.9; Tue, 19 Nov 2019 09:46:11 +0000
Received: from AM0PR07MB5716.eurprd07.prod.outlook.com ([fe80::8d07:c426:c2d7:51f2]) by AM0PR07MB5716.eurprd07.prod.outlook.com ([fe80::8d07:c426:c2d7:51f2%3]) with mapi id 15.20.2474.015; Tue, 19 Nov 2019 09:46:11 +0000
From: tom petch <daedulus@btconnect.com>
To: Ladislav Lhotka <lhotka@nic.cz>, Michael Richardson <mcr+ietf@sandelman.ca>, Roman Danyliw <rdd@cert.org>, "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Paul Wouters <paul@nohats.ca>
Subject: Re: Yang update from IESG ?
Thread-Topic: Yang update from IESG ?
Thread-Index: AQHVnr4sliAUy8NxTEe4E4yIv7Lsmg==
Date: Tue, 19 Nov 2019 09:46:10 +0000
Message-ID: <00e901d59ebe$1cdb3300$4001a8c0@gateway.2wire.net>
References: <alpine.LRH.2.21.1911131435240.22669@bofh.nohats.ca> <359EC4B99E040048A7131E0F4E113AFC01E70B0061@marchand> <alpine.LRH.2.21.1911180102380.9256@bofh.nohats.ca> <10541.1574083581@dooku.sandelman.ca> <e745d480c113b09eb4f6761cf48ef1e997fc3e6c.camel@nic.cz>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: CWLP123CA0075.GBRP123.PROD.OUTLOOK.COM (2603:10a6:401:5b::15) To AM0PR07MB5716.eurprd07.prod.outlook.com (2603:10a6:208:11e::24)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.211.103]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 66cfa3dd-d932-45ad-5eba-08d76cd54f1b
x-ms-traffictypediagnostic: AM0PR07MB6322:
x-microsoft-antispam-prvs: <AM0PR07MB632290D0560A461AE39968EBC64C0@AM0PR07MB6322.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 022649CC2C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(346002)(376002)(396003)(39860400002)(366004)(13464003)(51914003)(189003)(199004)(186003)(52116002)(81816011)(26005)(81686011)(44736005)(6486002)(2201001)(76176011)(8676002)(71200400001)(386003)(6506007)(71190400001)(4720700003)(8936002)(6246003)(229853002)(62236002)(44716002)(15650500001)(86362001)(14496001)(50226002)(6436002)(6512007)(81156014)(102836004)(66476007)(9686003)(64756008)(66446008)(66946007)(66556008)(2906002)(7736002)(305945005)(14454004)(4001150100001)(110136005)(478600001)(81166006)(99286004)(316002)(6116002)(25786009)(3846002)(3480700005)(1556002)(66066001)(476003)(446003)(486006)(256004)(2501003)(5024004)(5660300002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR07MB6322; H:AM0PR07MB5716.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: bQMFbGFvFCv5yxWGo+EuL/C1z92LIGDBIJfb5gYvZFDO4DgCVGvanFTqnQXX7XobBHQZ6aet+hajWbGaYpFqO8/Qnfqu9kCVKNhIVMxXUw/bOp1IlrFrRDtgmb7cx6Bq9D5R3lZ5e//LGhDub1JRXDC5TcojDMPWykdFnf6DJwpClA/DuDJ9ir/TxoXz9AFVMz13K0Nq8+sjMxi8z25zMENOzOtidGgTJhK0yJrNXBcn9Ld4Kyy1DRl271SLB2lmnXiXIsXTC3YNVZofevdpfOC7HE9hQ6VI/xKpTJjsSQA3BnaCtoBY/k4CAob5motrdXvrcIVQr49/F1odkhUmYGhulzJfw8zi38x8xcX6uCOUnwt/El1FbQYxc6Gp79nB0P0tv4dITLrjsbn3CfVOEGHrKgyGU4X8y7HKp2OracvqBL6wMfmHxr5a/Yj22kvT
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <FD0F5A87ED7236499D018A8B9E29368A@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 66cfa3dd-d932-45ad-5eba-08d76cd54f1b
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Nov 2019 09:46:10.9131 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: fXnVouLeWrYBqXZyGJnTyI8HaO2SCETrinEJuFn3Hmc3B4X8OcUo0291LcZ/VziwC2EAYvAQ/CE/ETWsBgmJSA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB6322
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oEtpC4QhZLVROsMh6ro1t8Tj6fU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2019 09:46:18 -0000

----- Original Message -----
From: "Ladislav Lhotka" <lhotka@nic.cz>
Sent: Monday, November 18, 2019 2:07 PM

> On Mon, 2019-11-18 at 21:26 +0800, Michael Richardson wrote:
> > Paul Wouters <paul@nohats.ca> wrote:
> >     >>> During a plenary at the last or second last IETF, I raised
an issue
> >     >>> about people stuffing incomplete and obsolete/deprecated
partial IANA
> >     >>> registiries in yang drafts/RFCs. The IESG confirmed this as
a problem
> >     >>> to me and one of the IESG members said they were aware and
would get
> >     >>> back on this.
> >     >>>
> >     >>> I have not heard anything. The issue is still a problem.
Originally,
> >     >>> this came up in i2nsf/ipsecme, and has now resurfaced for me
in
> >     >>> dnsop.
> >
> >     >> The IESG talked about this issue during the last IETF
meeting.  See
> >     >> attached.
> >     >>
> >     >> The outcome of this discussion was that there is no single
"right
> >     >> answer" and individual ADs should intervene on specific
instances as
> >     >> appropriate.
> >
> >     > Thanks for the answer. Unfortunately, it is not much of
guidance and
> >     > does not really address the issue I raised, namely that we are
putting
> >     > snapshots of IANA registries in RFC documents. One of your
three Design
> >     > Patterns still does this.
> >
> > I also am unhappy with this situation.
> >
> > As far as I can tell it means that IANA will be maintaining YANG
modules.
> > I don't understand how this is going to work for real products.
>
> IANA has been doing it for more than five years for a couple of YANG
modules
> (six by now), and I am not aware of any troubles so far.

In fact, this practice, of having IANA maintain modules, goes back to at
least RFC2677 in August 1999 so I would expect any troubles to have come
to light by now.

Tom Petch


> Lada
>
> >
> --
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67

v2.23.0 | Report a Bug | By Email