IETF Logo Mail Archive

[mpls] Use of leaf-lists in draft-ietf-mpls-static-yang

Aidan Copeland <aidan.copeland@metaswitch.com> Wed, 29 March 2017 15:30 UTC

Return-Path: <aidan.copeland@metaswitch.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A37AB1296F5; Wed, 29 Mar 2017 08:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level:
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=metaswitch.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 Q6YGIIB7oxEk; Wed, 29 Mar 2017 08:30:13 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0128.outbound.protection.outlook.com [104.47.41.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 324D31296E7; Wed, 29 Mar 2017 08:30:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=N23FFoY2Vl9CWmf2sb/cOyVhZpbHfVux+NX1wxo0yCk=; b=MvLeorVpib8jo+7DXcGc+25tulPUD1L05lqW4FDeIWelPdcYoIai6ORWRTEtQ8+ZZxS0JxIHJCPIg0C7epgFUMlAP67itz317ZQ6SMksnpIL3d3qyEIiCFxaaiJt0x3VEtcztq3lK1Sjj+ukAfWhzAshJV6Q4Dabv9HZbY+SyWc=
Received: from BL2PR02MB2066.namprd02.prod.outlook.com (10.167.96.150) by BY2PR0201MB1911.namprd02.prod.outlook.com (10.163.75.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.991.14; Wed, 29 Mar 2017 15:30:09 +0000
Received: from BL2PR02MB2066.namprd02.prod.outlook.com ([10.167.96.150]) by BL2PR02MB2066.namprd02.prod.outlook.com ([10.167.96.150]) with mapi id 15.01.0977.021; Wed, 29 Mar 2017 15:30:07 +0000
From: Aidan Copeland <aidan.copeland@metaswitch.com>
To: "draft-ietf-mpls-static-yang@ietf.org" <draft-ietf-mpls-static-yang@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: Use of leaf-lists in draft-ietf-mpls-static-yang
Thread-Index: AdKol+KJ/4b/UbzHSOirBqv9oxg+hg==
Date: Wed, 29 Mar 2017 15:30:07 +0000
Message-ID: <BL2PR02MB20660E93F80140BFF1FDA2E0E9350@BL2PR02MB2066.namprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=metaswitch.com;
x-originating-ip: [2620:104:4000:7064:ec31:f1ec:1fac:4e94]
x-microsoft-exchange-diagnostics: 1; BY2PR0201MB1911; 7:oL9NH16r6pDggV/oyDNEXIZY3UK4EaXEgyyKn93kmvXlZxIuMH2ECaKd7nPfR1Jsic40yqCS11GR8Oy8Xz5QLoWY9SVCv+vjEcrVW9vR6RPPZpPPvDqo3dYyXrAUQPlb41ptqSOGTj3sWAuRKv8AEhT88KutMDccZHHu9jE3Gfx1oQhlcID+yXnePGiTQM9/S16jXzI/PKKzoKlLzMLltNAtW1luAdDJr7SlfLAfbuyGwGpa8qSP+DIcSDl4g6NhaH8MGsulaRh7tpT29Wm7L2iBmBIU18ZauWl+5w9WuhKbzyOeXzMALV3GCGpXSN21g96NdPs71Cvp8aN9wbmIOQ==
x-forefront-antispam-report: SFV:SKI; SCL:-1SFV:NSPM; SFS:(10019020)(6009001)(39840400002)(39400400002)(39450400003)(39410400002)(51444003)(8676002)(3280700002)(25786009)(77096006)(230783001)(81166006)(189998001)(6506006)(6436002)(5660300001)(450100002)(3660700001)(55016002)(7696004)(2900100001)(6306002)(99286003)(54896002)(50986999)(54356999)(33656002)(122556002)(74316002)(38730400002)(9686003)(2906002)(53936002)(102836003)(6116002)(790700001)(2501003)(7736002)(86362001)(8936002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0201MB1911; H:BL2PR02MB2066.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-ms-office365-filtering-correlation-id: fb65be3d-27e7-4a26-e31a-08d476b87b07
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:BY2PR0201MB1911;
x-microsoft-antispam-prvs: <BY2PR0201MB1911668DF04F2492D3B60479E9350@BY2PR0201MB1911.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123558025)(201703131423075)(201702281528075)(201703061421075)(201703061406075)(20161123562025)(20161123555025)(20161123560025)(20161123564025)(6072148); SRVR:BY2PR0201MB1911; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0201MB1911;
x-forefront-prvs: 0261CCEEDF
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BL2PR02MB20660E93F80140BFF1FDA2E0E9350BL2PR02MB2066namp_"
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Mar 2017 15:30:07.3913 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB1911
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/M6EQnAOfLhaRRT3Dhvl0sMQgks8>
Subject: [mpls] Use of leaf-lists in draft-ietf-mpls-static-yang
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Mar 2017 15:30:16 -0000

Hi Tarek, all,

I think that there is an error in the use of a leaf-list to represent the set of outgoing MPLS labels to impose for an outgoing path.

RFC7950, section 7.7, states

In configuration data, the values in a leaf-list MUST be unique.

This means that a leaf-list is not suitable to represent a label stack, where the same label value may be used more than once.

I think the best solution is instead to specify the set of outgoing labels as a list of outgoing label containers, keyed by label index and containing the outgoing label value.

Do you agree with this, or do you think a different mechanism would be better?

Regards

Aidan

v2.23.0 | Report a Bug | By Email