Re: [mpls] WGLC, IPR and implementation poll for draft-ietf-mpls-mldp-yang-06
tom petch <ietfc@btconnect.com> Tue, 08 October 2019 12:01 UTC
Return-Path: <ietfc@btconnect.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 691811202A0; Tue, 8 Oct 2019 05:01:06 -0700 (PDT)
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 0WLP76yB4EsE; Tue, 8 Oct 2019 05:01:04 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50135.outbound.protection.outlook.com [40.107.5.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA0D0120274; Tue, 8 Oct 2019 05:01:03 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CuMA2YYdP89+GXAjeMiTkAF5xkeLSUH28YkQVv3TJbgO2bPNe3c6g3/QQkMyPvhMvjfRtGicQxNj1PXBDLTZjM5lsEIqBPoINsOx8gc0k1G2lIDpmc8uo/xB94HWZv4RjfJ2aoNDkmYB0X0gSij04QYqDKBbIAQCBLxanYSDgdpZPLXLxFfUmaKj0/GV2cA/1XPf9LHYvpyAjzGkGe3eCVuwlVKTOXtuTMLKmCw7abv+5uuRD4S6mEcm67+cwF9cMMKN6J6hl15pZA2rn9ipZcECYmScMM/+svETdwHlYBfhzNxayL4MQ6Pf+S2R7vP+hjSIoqJGibaJc23qzwaQ/g==
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=ENYcsiI4VYvy4Q57J3BzaTiu7Cn3JzMkcf/yyzpp4l0=; b=V6mLYhDBo/+myM/+Od6E9KxQBuWNsqRsHvb4GUjXuGb9jW1XGWgSSrbpbrBwLVPg9lNa6fI49lQqmrRk2xAzBW40gsO7PAaLIF1MYoKnyb+sy5v8ZAF9Lo6Y49CWGlAeVXWrdUWyxX6foZjUFNAX4p3IgRAbBzJgt+C3SrDJ3VNLpZU8eddCTg8MNuGNPOxA2vH/8HCKQVPJyf+jb8KYosTaKWQivSzv0X/TXVgfSraMf8J3xXXgoch3peF1hiuOsvMn/HLDr7zGd1D/h+uaH5/wfkzXsdEuWR2JVtyGlUFsw43b206pnSEU8Qgu8SCjA+3cWVM7EzC8sONsavO2Ww==
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=ENYcsiI4VYvy4Q57J3BzaTiu7Cn3JzMkcf/yyzpp4l0=; b=RNDoDqpsaC3PCoUYpD+S98e1lLbXXimUfr3GLtMmd9Rm1mGCOza5C3Z24/z06ZouknrtldMDQM2Yg845AofXG7S/CPCf6yJ5gBj0qb28OqplNqMS2v5S8ub/3i7GQblEc69+oAH8L+UFsWU03XRT1Jt6umtSSFMXhmEMFL6gd08=
Received: from DB7PR07MB5147.eurprd07.prod.outlook.com (20.178.42.32) by DB7PR07MB5177.eurprd07.prod.outlook.com (20.178.42.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.13; Tue, 8 Oct 2019 12:00:51 +0000
Received: from DB7PR07MB5147.eurprd07.prod.outlook.com ([fe80::d5a9:784f:d667:ef14]) by DB7PR07MB5147.eurprd07.prod.outlook.com ([fe80::d5a9:784f:d667:ef14%4]) with mapi id 15.20.2347.016; Tue, 8 Oct 2019 12:00:51 +0000
From: tom petch <ietfc@btconnect.com>
To: Tarek Saad <tsaad.net@gmail.com>, "draft-ietf-mpls-mldp-yang@ietf.org" <draft-ietf-mpls-mldp-yang@ietf.org>
CC: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Thread-Topic: WGLC, IPR and implementation poll for draft-ietf-mpls-mldp-yang-06
Thread-Index: AQHVfdAH80Y0dpWykU6LbqlArWeDJg==
Date: Tue, 08 Oct 2019 12:00:50 +0000
Message-ID: <06af01d57dcf$ba69dd20$4001a8c0@gateway.2wire.net>
References: <BYAPR19MB3415A091AA3F8F229A1493FEFCB30@BYAPR19MB3415.namprd19.prod.outlook.com> <DM6PR19MB368966709D9C935C88E7E7EAFC9D0@DM6PR19MB3689.namprd19.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0475.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a2::31) To DB7PR07MB5147.eurprd07.prod.outlook.com (2603:10a6:10:68::32)
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.211.103]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6f1a6db0-139d-4548-b7bc-08d74be729a2
x-ms-traffictypediagnostic: DB7PR07MB5177:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <DB7PR07MB51773B3A1CA7A9458E7F55B4A09A0@DB7PR07MB5177.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-forefront-prvs: 01842C458A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(366004)(39860400002)(376002)(136003)(346002)(13464003)(189003)(199004)(76176011)(71190400001)(6246003)(9686003)(186003)(6512007)(81816011)(7736002)(52116002)(99286004)(6306002)(229853002)(26005)(446003)(966005)(486006)(25786009)(1556002)(478600001)(64756008)(66476007)(54906003)(66446008)(62236002)(44716002)(4326008)(71200400001)(66556008)(66946007)(305945005)(102836004)(81156014)(386003)(8936002)(6506007)(61296003)(53546011)(5660300002)(110136005)(8676002)(50226002)(2501003)(316002)(81166006)(6116002)(3846002)(44736005)(6436002)(81686011)(6486002)(14454004)(14496001)(476003)(4720700003)(14444005)(2906002)(66066001)(86362001)(256004)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR07MB5177; H:DB7PR07MB5147.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: eP9sBv/2u/OkvKDXLR83T4jZzbU3H1XeLSpGIOEr6a3JmXZq0m96nTuCJtgYVZOafgDxRBG6Ds3yH+PW9NM25dZd6U4Jg493gTzwFn8IibLzHrhVfP1L1hGWJAbSkpcKVbngx/6fc9afbSNR+ujQtMqg9KKO+uMSUudPVaHllXytGjzgydTRmHcNu66S3fciQtzX6psv8SH5qsli/8h2yfMErXXkG9BfkWpyB96NRlcDrcGnZepDRwhPpPfdRMxjyOAL7wWiTOBOM/lrn1+QzDKpzwZF40H/UPifAQVLffX3UgBY+795VIawaXzFKnibHs/YQZLWFjbDTKg1tQKqeePzH7ZMhaT2EI2DGmQiSZ4enK4uLkK4XNeEQRETAx05MXOAIHoUjFV7H4yVp2M8Zk7n2ZHrNuUx5h1P4vd+l5x9RSjaTDH/bKGZZvd6PGqeWs/qVigo1gnembYejx+aFw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <956710EF07E80949B16541341541D72E@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6f1a6db0-139d-4548-b7bc-08d74be729a2
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Oct 2019 12:00:50.8470 (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: z2PpLzTO0A+lv5hSCzEPeqYWm7+aueARfa40QaGP68zN3v21r0/kHCdGIZtawY9ugHZMRSGVpuJgWHrRauZpRw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB5177
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/e18OGGYVaPt1PfGjSw_oUJUJ7bE>
Subject: Re: [mpls] WGLC, IPR and implementation poll for draft-ietf-mpls-mldp-yang-06
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 08 Oct 2019 12:01:07 -0000
Tarek Well, yes. I also commented about " [Ed Note: Some of the topics in the above list are to be addressed/ extended in a later revision of this document]." and "8. Open Items A list of open items that are to be addressed in future revisions of this document follows: o Specify default values for configuration parameters" both of which I would see as needing fixing before going further. Nothing wrong with describing options for future work in an RFC but, as written, it reads to me as if this I-D needs further work. And I was hoping for a version where the line length was fixed, making it easier to read, before submitting other comments. I did note s.1.1 / alongwith /along with / s.3 +-- rw some_ldp_container I do not understand this /ipv4/IPv4/ s.4.2 /mldp/mLDP/ I suggest expand on first use VRF FRR AF s.5.3.1 /address-familty /address-family / (or just AF) RFC XXXX stands for both "Base YANG Data Model for MPLS mLDP" and "A YANG Data Model for MPLS LDP" the first of which does not exist:-) I suggest using XXXX for this I-D and YYYY for MPLS LDP " MP capabilities need to be explicitly enabled under container capability."; I am uncertain which container this refers to - I need a longer path Tom Petch ----- Original Message ----- From: "Tarek Saad" <tsaad.net@gmail.com> To: <draft-ietf-mpls-mldp-yang@ietf.org> Cc: <mpls@ietf.org>; <mpls-chairs@ietf.org>; "tom petch" <ietfc@btconnect.com> Sent: Tuesday, October 01, 2019 8:27 PM Subject: Re: WGLC, IPR and implementation poll for draft-ietf-mpls-mldp-yang-06 This WGLC is now closed. Authors, There are comments that were received from Tom related to line length exceptions in the draft. Can those be addressed before we can proceed further? Regards, Tarek From: Tarek Saad <tsaad.net@gmail.com> Date: Friday, September 13, 2019 at 4:34 PM To: "draft-ietf-mpls-mldp-yang@ietf.org" <draft-ietf-mpls-mldp-yang@ietf.org> Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org> Subject: WGLC, IPR and implementation poll for draft-ietf-mpls-mldp-yang-06 Working Group, This email starts WG Last Call, IPR and implementation poll for draft-ietf-mpls-mldp-yang-06. This WGLC ends on 9/27. Please review the document and send any comments to the mpls wg mailing list (mpls@ietf.org<mailto:mpls@ietf.org>). If you’re a co-author/contributor, please explicitly respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. If you're not a co-author/contributor, you need to respond only if you are aware of any relevant IPR not yet disclosed in conformance with IETF rules. Currently there are no disclosed IPRs that can be found here: https://datatracker.ietf.org/ipr/search/?draft=draft-ietf-mpls-mldp-yang &submit=draft&rfc=&doctitle=&group=&holder=&iprtitle=&patent= We are also polling for any existing implementation. Regards, Tarek (for the MPLS WG Chairs)
- [mpls] WGLC, IPR and implementation poll for draf… Tarek Saad
- Re: [mpls] WGLC, IPR and implementation poll for … Jeff Tantsura
- Re: [mpls] WGLC, IPR and implementation poll for … Loa Andersson
- Re: [mpls] WGLC, IPR and implementation poll for … tom petch
- Re: [mpls] WGLC, IPR and implementation poll for … tom petch
- Re: [mpls] WGLC, IPR and implementation poll for … Tarek Saad
- Re: [mpls] WGLC, IPR and implementation poll for … tom petch
- Re: [mpls] WGLC, IPR and implementation poll for … Tarek Saad