IETF Logo Mail Archive

Re: [core] Questions/comments on draft-ietf-core-sid-04

Michel Veillette <Michel.Veillette@trilliant.com> Tue, 17 July 2018 18:35 UTC

Return-Path: <Michel.Veillette@trilliant.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD2D130FAE; Tue, 17 Jul 2018 11:35:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trilliant.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 LX_iC_8hMXgt; Tue, 17 Jul 2018 11:35:36 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0120.outbound.protection.outlook.com [104.47.33.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03D9613107D; Tue, 17 Jul 2018 11:35:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Trilliant.onmicrosoft.com; s=selector1-Trilliant-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=00k1JpGa06mD6SPqUlz/YyKkrc5BWqSOKQXSZgku42c=; b=eCUbz/Z8gGWVKRBS+9NWWinP3xG/hyYUAgV9X85p4i3WYQliv4gZhP8tXHc7vzhpohdzyN31WAmo+5SEAVOhihxlDSm9iYazchg8DX9eFgLjdign2rQzuLlYR4X47MfLWhCEJ9r2gD+8FPteEpty2dSoOftR2+0vKpnizowIJbA=
Received: from DM5PR06MB2777.namprd06.prod.outlook.com (10.175.107.139) by DM5PR06MB2778.namprd06.prod.outlook.com (10.175.107.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.952.20; Tue, 17 Jul 2018 18:35:33 +0000
Received: from DM5PR06MB2777.namprd06.prod.outlook.com ([fe80::b822:6d77:2b7f:e300]) by DM5PR06MB2777.namprd06.prod.outlook.com ([fe80::b822:6d77:2b7f:e300%5]) with mapi id 15.20.0952.021; Tue, 17 Jul 2018 18:35:33 +0000
From: Michel Veillette <Michel.Veillette@trilliant.com>
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "draft-ietf-core-sid@ietf.org" <draft-ietf-core-sid@ietf.org>
CC: "core@ietf.org" <core@ietf.org>
Thread-Topic: Questions/comments on draft-ietf-core-sid-04
Thread-Index: AQHUHfjMVEMw08sPw0STjWF2kfjwDKSTtudg
Date: Tue, 17 Jul 2018 18:35:33 +0000
Message-ID: <DM5PR06MB2777CEBF0002C7BA8E1485A29A5C0@DM5PR06MB2777.namprd06.prod.outlook.com>
References: <510E8389-232B-4AFC-B359-CB9330C15280@cisco.com>
In-Reply-To: <510E8389-232B-4AFC-B359-CB9330C15280@cisco.com>
Accept-Language: fr-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michel.Veillette@trilliant.com;
x-originating-ip: [31.133.142.43]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR06MB2778; 7:xN+gD7x0wWVikJYl3rluS28wv6DguCK+lGGipcb63Dfb8H4Xs6t71XSXevPU1fWNQGyOi2Mhq+x2eHPH4QaK0ol8ZioK+iesIS0XEX24/9DYs+D8GxbLzujrw5aeyUsKZVDQIBw4sKUppL4JX/AkYxddwGxTtgyQ9DlrGxbKx9fJfwfUupNn6V0eTKvdVJgI+RsXyTQLU7y2hAd5upqi8EPBaQFAzEkG3sRYPjFDaKbBGkOKRuPOJcGvD1I3Zwre
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 56c058e8-75b7-4050-caf1-08d5ec1414e7
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(7193020); SRVR:DM5PR06MB2778;
x-ms-traffictypediagnostic: DM5PR06MB2778:
x-microsoft-antispam-prvs: <DM5PR06MB277822949F29E32CB15127179A5C0@DM5PR06MB2778.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(95692535739014)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231311)(944501410)(52105095)(93006095)(93001095)(10201501046)(3002001)(149027)(150027)(6041310)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:DM5PR06MB2778; BCL:0; PCL:0; RULEID:; SRVR:DM5PR06MB2778;
x-forefront-prvs: 073631BD3D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(376002)(346002)(366004)(396003)(39850400004)(189003)(199004)(102836004)(8936002)(26005)(5660300001)(68736007)(7736002)(6306002)(76176011)(9326002)(4326008)(54896002)(33656002)(6506007)(53546011)(2906002)(478600001)(72206003)(97736004)(8676002)(186003)(106356001)(105586002)(81166006)(81156014)(6246003)(446003)(11346002)(486006)(476003)(14454004)(2900100001)(14444005)(25786009)(7696005)(6436002)(6116002)(74316002)(53936002)(790700001)(110136005)(316002)(55016002)(66066001)(256004)(2501003)(3846002)(9686003)(99286004)(229853002)(5250100002)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR06MB2778; H:DM5PR06MB2777.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: trilliant.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 5l+ceF5f+J7Ivbk1eL/XbgMrO/MFnSvkjb6sbf87ju+pq6tAh/S4wL9FljlBpU5m7bImorAre+fAoy2JY/xGQ8pMph8a+D2mqxrUAR3392RWyszWQ+LDMvrT2IWJ7eLnWV6xagPqLPUU3zHMbfq1qqtXCXXnUnTBDU0bShS4zlC8caLSyoeg3g0SIbMhgtW+T9G2+BcUBk+LYKdY1Zb2Fxa7wmwILANa5JV5Uq8NgLJ4ONbIVNv4YDaRkFZWwCRSIfPA4dtT6dfp8sqYu8GlhGhdtP2jCa0NLqViXU7uzCcVkEfEhwJ+CXL87KnB+8UfcowIB+dDyRA/vReiF7zBMeimYO616sOlvp9JP87w5Xg=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR06MB2777CEBF0002C7BA8E1485A29A5C0DM5PR06MB2777namp_"
MIME-Version: 1.0
X-OriginatorOrg: Trilliant.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 56c058e8-75b7-4050-caf1-08d5ec1414e7
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Jul 2018 18:35:33.5788 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB2778
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/H_c6K9NkBSunWuTRK13BiuabQqg>
Subject: Re: [core] Questions/comments on draft-ietf-core-sid-04
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2018 18:35:41 -0000

Hi Reshad

About "why not have 2 levels instead"

The current single list solution has been selected for its simplicity to implement the sip.py pyang plugin.
The size of this module was not a concern since we had no intents to implement this module in the constrained device itself.
'yang-data' might be used in the next version to clarify this point.

About "Would it be useful to have another key based on sid".

Unless I'm wrong, YANG allow a single 'key' statement per list.
However, a 'unique' statement can be added to verify the uniqueness of this leaf.

Regards,
Michel

From: Reshad Rahman (rrahman) [mailto:rrahman@cisco.com]
Sent: Tuesday, July 17, 2018 2:06 PM
To: draft-ietf-core-sid@ietf.org
Cc: core@ietf.org
Subject: Questions/comments on draft-ietf-core-sid-04

Hi,

For “list items”:

  1.  It is a list with composite key namespace and identifier, why not have 2 levels instead, i.e. a namespace list (keyed on namespace) and each namespace has a list of identifiers (keyed on identifier)
  2.  Would it be useful to have another key based on sid?

Regards,
Reshad.

v2.23.0 | Report a Bug | By Email