IETF Logo Mail Archive

Re: [netmod] two options for removing /foo-state trees?

Kent Watsen <kwatsen@juniper.net> Thu, 07 September 2017 19:30 UTC

Return-Path: <kwatsen@juniper.net>
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 0E8C6132964 for <netmod@ietfa.amsl.com>; Thu, 7 Sep 2017 12:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.011
X-Spam-Level:
X-Spam-Status: No, score=-3.011 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_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, 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=juniper.net
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 EpS9P51bXPl4 for <netmod@ietfa.amsl.com>; Thu, 7 Sep 2017 12:30:46 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0131.outbound.protection.outlook.com [104.47.33.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CF76132811 for <netmod@ietf.org>; Thu, 7 Sep 2017 12:30:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8T8Hhmqo4YHy4i2to7AmXw4+ItBQj40Cujo6G2ixNQs=; b=L7lHIee3CcEvsUqCkTu2Vm0icXAtNhhWlaexbIb4vMZOF2+FCzAeEQZR2aZQNqbSlFqDhK/+deYgeD0onJlSZQ+fxpbZdTBUXdui60BkItxlIq8pFdyEGENrraT33Z+fBsd5ij5SQCC20kTYfg2rfKeyI5IZGoivPNWn6h1+Whs=
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com (10.160.117.151) by BN3PR0501MB1251.namprd05.prod.outlook.com (10.160.183.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.56.4; Thu, 7 Sep 2017 19:30:44 +0000
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) by BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) with mapi id 15.20.0056.003; Thu, 7 Sep 2017 19:30:44 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "Acee Lindem (acee)" <acee@cisco.com>, Lou Berger <lberger@labn.net>, Martin Bjorklund <mbj@tail-f.com>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] two options for removing /foo-state trees?
Thread-Index: AQHTJzZlKMfT3FTQbEyg9FUCwcWxgKKoJxiAgAFZEgCAAAPFAIAACi2A
Date: Thu, 07 Sep 2017 19:30:44 +0000
Message-ID: <B0660268-33F0-4EA0-82D7-516811C0E406@juniper.net>
References: <D94B3E90-8676-4790-A186-84CB7DC18B49@juniper.net> <20170906.200545.1646568136744118938.mbj@tail-f.com> <9acc6055-c7b0-8c80-3468-72b090b9253f@labn.net> <D5D6D48D.C6D1C%acee@cisco.com>
In-Reply-To: <D5D6D48D.C6D1C%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1251; 6:PhVC6r6aB48HY2gCWiyXdmYUwDqdkjYKwOzpyjBDnckuMrl/8uwCYcecyZiKiOyNSr9WxaTexG7lcXh5buNY++Cd9CIXVByVnISpF4o9Z74pbd3g8BmSC61EE1+5TZMfX/VJahP4XF2SaVIF/oAxoU3kWGiG6Es/7h2t3p3achzVyY4TjndaWgTrzhLEkMWk6SQPXFgn5bUMF2AI6zo+cJd1tZ/zoeIB4cHIefcoyMLwZ/F05OFJhiALX7uWhcA/1jdFrmuzk5KL1q/nTL3UkSuMKMNf2B1xJ8NR6GEorXB6rkwuKnZDDfYkCJMkTxscfk9mYf5dDPXAWfB2oRE8iw==; 5:+B45SSgdY5pRtMeHLWlugYKFKy+t/VmMQOJbeUbZoSRnvNxpC6mmiykZFK77clY8WedUy4tZt5MmF5mEJ7z+mIf8BqgW8iSJnRmVx480B8ApKbgC2Dx0DYOO+QYS7RTqclgBR8YIoObcmMm1ni9fuw==; 24:09e6OWpLGGRDT7qcVOkKVlFqS3KSR7PPWLmoqsegK3o0WKDh0uaQcXVV18eAAOAuE1MGyYEN33CHDm9XV+2KBjpnXhxzVqO80fGsucQJ3kg=; 7:D362OPLq2X8N6J+G8H0nTwIX+fxducDyFm0DCA1jSOlAjGVuu3rQ4jd+jWtlz7wHFXyEw9s+Jv5aC50bP5t+oUxv6AKG6C2bf2cHnu4ZPvZBKG+dCxy+nI2NmwQ3f3BeCet5hqwH3sp4CnQL89enRpoRRDejdjMeN/5gg2CLYATjS51Nay4eJqR2x27aqUj+hkLTj3oLPGn74E7Yxi919SuELrZSVR2VMLDBmKKXdRI=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 93168d81-e9e8-4f98-e902-08d4f626eef7
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(48565401081)(300000503095)(300135400095)(2017052603199)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BN3PR0501MB1251;
x-ms-traffictypediagnostic: BN3PR0501MB1251:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kwatsen@juniper.net;
x-exchange-antispam-report-test: UriScan:;
x-microsoft-antispam-prvs: <BN3PR0501MB12517D7C5958EEFC08D640AFA5940@BN3PR0501MB1251.namprd05.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(10201501046)(100000703101)(100105400095)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123562025)(20161123560025)(20161123558100)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN3PR0501MB1251; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN3PR0501MB1251;
x-forefront-prvs: 04238CD941
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(189002)(199003)(6436002)(81156014)(8936002)(8676002)(305945005)(229853002)(81166006)(68736007)(7736002)(86362001)(83506001)(83716003)(6512007)(6246003)(6506006)(6486002)(77096006)(82746002)(2950100002)(97736004)(4001350100001)(99286003)(14454004)(36756003)(189998001)(53936002)(66066001)(3280700002)(25786009)(2900100001)(3846002)(105586002)(106356001)(101416001)(6116002)(3660700001)(33656002)(4326008)(102836003)(54356999)(478600001)(93886005)(50986999)(5660300001)(76176999)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1251; H:BN3PR0501MB1442.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <9B30A4EB3516AE4BAA7F12823C985F64@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Sep 2017 19:30:44.4028 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1251
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/mhorI4DFugFJz_VVQEaiDiBBKL0>
Subject: Re: [netmod] two options for removing /foo-state trees?
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, 07 Sep 2017 19:30:48 -0000

Hi Acee,

> Ok - it is less painful if we only have to deprecate the *-state nodes.

Does this mean you're okay reposting your ID similar to Martin's?
I ask as a chair interested in starting the adoption process on
these nmda-update drafts.

> However, what about secondary and tertiary implications of moving to
> NDMA? If we change a path from “interface-state-ref” to “interface-ref”
> to reference an interface, I’d hope no one would expect the old
> statement to be kept around… 

But the old statement would be kept around, in its deprecated form.
Of course, the nmda-guidelines should cause those downstream modules
to be updated to NMDA as well, so hopefully just a short-lived issue.


Kent

v2.14.0 | Report a Bug | By Email