Re: [netmod] [Teas] Key collision between configured and ephemeral list entries

tom petch <ietfc@btconnect.com> Wed, 12 June 2019 09:39 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 3F70312013A; Wed, 12 Jun 2019 02:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.247
X-Spam-Level:
X-Spam-Status: No, score=0.247 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] 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 kfMYqkTGHMBi; Wed, 12 Jun 2019 02:39:36 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20102.outbound.protection.outlook.com [40.107.2.102]) (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 CF077120137; Wed, 12 Jun 2019 02:39:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wgNeBGdEJh+zIfwoA/ZnJLVqZg5Ds5o/QwpVthxWQeo=; b=nzlEhmXlMwh8lzo+UKXLFUzdOj3xi6VuvzBv++AnaBysgedPZS14wPPMUeZyq4YAdSkDaf8s8zZKKZfEDIawfzll5vaEhbuPOKOy9K5Jt+Iah9LsdlHu/qEtZcXQrMn7zcKC1gd8C5u6naFaBalgRtcQErB5L3JraASmsa9UeZ0=
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com (10.175.242.156) by VI1PR07MB5136.eurprd07.prod.outlook.com (20.178.9.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.8; Wed, 12 Jun 2019 09:39:33 +0000
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::7537:44ee:88c1:dd6d]) by VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::7537:44ee:88c1:dd6d%7]) with mapi id 15.20.1987.010; Wed, 12 Jun 2019 09:39:33 +0000
From: tom petch <ietfc@btconnect.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Italo Busi <Italo.Busi@huawei.com>
CC: "netmod@ietf.org" <netmod@ietf.org>, Tarek Saad <tsaad.net@gmail.com>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [netmod] [Teas] Key collision between configured and ephemeral list entries
Thread-Index: AQHVIQK918sq4+j40USJE5MEDi7yVA==
Date: Wed, 12 Jun 2019 09:39:32 +0000
Message-ID: <03f101d52102$217a1dc0$4001a8c0@gateway.2wire.net>
References: <BYAPR11MB26314CD2365C6AEC39E696EDB51F0@BYAPR11MB2631.namprd11.prod.outlook.com> <BL0PR06MB4321DA01042ECAAD88E8420AFC1F0@BL0PR06MB4321.namprd06.prod.outlook.com> <91E3A1BD737FDF4FA14118387FF6766B2774E51F@lhreml504-mbs> <028b01d51933$1015fa80$4001a8c0@gateway.2wire.net> <91E3A1BD737FDF4FA14118387FF6766B2775CF49@lhreml504-mbs> <CABCOCHTFSfizdqszABgyv+SBHW2+5W5WF-HJvVo=EAJFcUnvJA@mail.gmail.com> <20190611160106.5o3pslwmnhaoyjzx@anna.jacobs.jacobs-university.de> <91E3A1BD737FDF4FA14118387FF6766B2775D052@lhreml504-mbs> <20190611171900.xzzwofx5nwtj77cv@anna.jacobs.jacobs-university.de> <91E3A1BD737FDF4FA14118387FF6766B2775D16D@lhreml504-mbs> <20190611183630.4ymx7libdotuqfbo@anna.jacobs.jacobs-university.de>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0007.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:62::19) To VI1PR07MB3118.eurprd07.prod.outlook.com (2603:10a6:802:20::28)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.215.234]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1c64d704-ab51-4e97-85ef-08d6ef19dfc3
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:VI1PR07MB5136;
x-ms-traffictypediagnostic: VI1PR07MB5136:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <VI1PR07MB51365288FC64AE7EB78AD68DA0EC0@VI1PR07MB5136.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0066D63CE6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(136003)(396003)(346002)(376002)(366004)(199004)(189003)(13464003)(6116002)(44736005)(486006)(110136005)(6512007)(2906002)(6486002)(186003)(4720700003)(54906003)(6306002)(64756008)(66476007)(84392002)(66066001)(8936002)(26005)(476003)(66556008)(73956011)(316002)(66946007)(99286004)(81166006)(66446008)(446003)(229853002)(62236002)(6436002)(44716002)(1556002)(61296003)(6506007)(305945005)(76176011)(7736002)(102836004)(14454004)(50226002)(25786009)(71190400001)(81816011)(478600001)(81686011)(966005)(8676002)(4326008)(14496001)(5660300002)(68736007)(256004)(53936002)(81156014)(71200400001)(52116002)(86362001)(6246003)(386003)(9686003)(3846002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB5136; H:VI1PR07MB3118.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: QC2wYHiPmaJeA/s4YV8wRMYQUCzbpDkgQ8Szlc6pY1F1dnITyH/up8BQqGCS8zd8QGnBn9UMuI+09BKZql++3kaOPvoCsQjSYEMBs1CYjmy1/51iauHkSPAS4qVA6e09XQqqSWGE469nQVDT9H/OVMZN2T6OJboCUfFCKe6wa3/5v1S0RcdF4hWmWCTNX66oKedSc1sln9cOL9YiAFilFmbuL0iZ1BHMQt7RvNPPzE7zz+w4pmg0H0zStFriAClwr5pEwpMmmkGwr7MDvR9SIW1JViB4n+bwtypYtgjk/jnD2d26w18Xkm+P6DecurW02SsoJZiWNfam98Mkztk7oxXIlXY2581TEu1YgLMhC09znVPt4jxQAwwQKtzDUJZPdunwJXBv1QdmvVbWkPLZSTWwOxY/DWDTdDu9tBxgJ74=
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <56B92DA131454844A069495BEFE03B5E@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1c64d704-ab51-4e97-85ef-08d6ef19dfc3
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jun 2019 09:39:33.0425 (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: ietfc@btconnect.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5136
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/pQSDk_bXrcLU1q2p3y4ZcSW69Mc>
Subject: Re: [netmod] [Teas] Key collision between configured and ephemeral list entries
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 12 Jun 2019 09:39:38 -0000

----- Original Message -----
From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>;
Sent: Tuesday, June 11, 2019 7:36 PM

> On Tue, Jun 11, 2019 at 05:43:27PM +0000, Italo Busi wrote:
>
> > [Italo Busi] If the client knows the prefix used by the server, it
> > can pick up a different prefix and use it to tag its own entries. I
> > think this rule is not really complex and it seems much simpler than
> > managing unintended name clashes
>
> A prefix only helps a little. Once you have multiple clients creating
> entries, you will have to handle collisions again. Sometimes solving
> the more general case leads to solutions that also work nicely in
> simpler special cases.

Picking up on the point earlier about needing a rule about what to do
when a collision occurs, the collision only occurs when the second (or
third?) entry is created and AFAICT that is unpredictable, the
configuration may occur first or the ephemeral one.  If the rule is that
one or the other datastore takes precedence, then you have a name which
changes its meaning at this point, which seems undesirable.

Hence, the only rule I can see being acceptable is that the first one
wins, regardless of which it is,  and the second and subsequent are
rejected as invalid.

But then you cannot rely on the prefix telling you where the name came
from - of course, YANG origin will still be accurate.

Tom Petch

> /js
>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod