Re: [mpls] YANG for MPLS-TP?

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Tue, 14 June 2016 11:29 UTC

Return-Path: <Alexander.Vainshtein@ecitele.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 4D23112DB82; Tue, 14 Jun 2016 04:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eci365.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 iWoM_FmK9pqi; Tue, 14 Jun 2016 04:29:32 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0112.outbound.protection.outlook.com [104.47.2.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17E7D12DB6F; Tue, 14 Jun 2016 04:29:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector1-ecitele-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=pThTFp91admNaFeDoC2GrHINeCLO+x27bpPfIlnbNJU=; b=V0ODzADLIXrYw2OGR7zh4wsaLFHx+wuMvr1xNVjup3AgR3jo5tU1cNoZFGjVUufxd9pmsbjJd0tFgpK54H0bsN3mAMJHPxnmv/bl6g59e8rebo5GEjvOruItpE9/76Ri8tUAgqLNwnBStSBQSuXFjCOD6YZl7yfCl7fd+u3mZPM=
Received: from HE1PR0301MB2266.eurprd03.prod.outlook.com (10.168.31.153) by HE1PR0301MB2267.eurprd03.prod.outlook.com (10.168.31.154) with Microsoft SMTP Server (TLS) id 15.1.517.8; Tue, 14 Jun 2016 11:29:27 +0000
Received: from HE1PR0301MB2266.eurprd03.prod.outlook.com ([10.168.31.153]) by HE1PR0301MB2266.eurprd03.prod.outlook.com ([10.168.31.153]) with mapi id 15.01.0517.011; Tue, 14 Jun 2016 11:29:25 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Huub van Helvoort <huubatwork@gmail.com>
Thread-Topic: [mpls] YANG for MPLS-TP?
Thread-Index: AdHGIzK2KJjYzQelTo2t4MmyNPnKTAAC3qqAAAAvsVA=
Date: Tue, 14 Jun 2016 11:29:25 +0000
Message-ID: <HE1PR0301MB226644496E8CDE7F697AE2789D540@HE1PR0301MB2266.eurprd03.prod.outlook.com>
References: <HE1PR0301MB226639582EEEE9D50D74E7889D540@HE1PR0301MB2266.eurprd03.prod.outlook.com> <CAHOc_FSEth10wUj-7ON+D5HKKmUt8DzcF7X2hfy4Yk5dHLH+VQ@mail.gmail.com>
In-Reply-To: <CAHOc_FSEth10wUj-7ON+D5HKKmUt8DzcF7X2hfy4Yk5dHLH+VQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Alexander.Vainshtein@ecitele.com;
x-originating-ip: [147.234.241.1]
x-ms-office365-filtering-correlation-id: c1739fdc-1d66-4d8b-1628-08d39447241c
x-microsoft-exchange-diagnostics: 1; HE1PR0301MB2267; 6:hwuQGj2D5QdMeB3T38nhoX3W2V33QtZfJLGZZ5yFHoMpWu+i4HAzFbCgKZbpOkF977KDzRtHV6ch7B3UEWW66eQEifncdWv8Kh5mbNIE33lTL4R21pYo1iBVq6XDXC2LxYZWBW9y8wWkt+L6bVthv8RGXrk+AtDnOPFvYuzQWSPNZPtz89mEeO8YCqf1EQ3utJGe7vuWRnmACXuhgk80lACbp4WBjF1zko8/6VtYAO6i7HicYYXMThTg+W1F05FLJOB1jinidnlFZlOBSEDKOWNJz/EPFfHkHbfq8bGDoKY4oLW/JYLfA95qtWRhghW4; 5:Ou6YfSGJ/tzTNwcUevw+lb23n+mRiOhTSQoQMSUM/WGfPTSPrOBzEzHvJCMbQ8zkKBcHD2BPUDJjBlox3bfKDRNIYC5Yu5J7ek/KdDxriBjzbY1gTjcL0u0j56vqBK0w7fKhPrTpZaBW37Ckiyjb/g==; 24:iB+/DoAuRJQngGp2XTFakK2t6cDnPPUmSDAJ11CFXTIDjRIZ8GGG3e769rLUCQ1OJBKFnPuUJl5jmXrNRO1Nb0a5HG3n2MsUdSrbVBTGgYw=; 7:5fk61Whdt6FDeQXG3wkufBIbbvsFNCsaQZlDgke7cOPfXKmsnnPoIVwYXvJndiTl3+4MSLJ2ib47Sz5d7eIH0zBoo1lAMg8ITDiUPBeY3iR27Mious0EMGXiPd0FvuEzRkkWn8uWUaGg/6ftB2KblBYmoAPQHPs60sO39+Rxf0efjlxCQ7dKEzcDowKxBpax19tdpDIb1T46DvlPjiclNw==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:HE1PR0301MB2267;
x-microsoft-antispam-prvs: <HE1PR0301MB226760A813574826BF253FD19D540@HE1PR0301MB2267.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(21748063052155)(279101305709854);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026); SRVR:HE1PR0301MB2267; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0301MB2267;
x-forefront-prvs: 09730BD177
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(24454002)(53754006)(377454003)(199003)(189002)(252514010)(51874003)(19617315012)(122556002)(86362001)(4326007)(66066001)(2906002)(106356001)(105586002)(586003)(19300405004)(1411001)(3846002)(102836003)(6116002)(790700001)(7906002)(10400500002)(8936002)(9686002)(19609705001)(16236675004)(19580405001)(5004730100002)(19625215002)(77096005)(5002640100001)(19580395003)(76176999)(54356999)(74316001)(2950100001)(189998001)(2900100001)(87936001)(76576001)(15975445007)(33656002)(3280700002)(101416001)(5008740100001)(92566002)(81166006)(81156014)(8676002)(50986999)(97736004)(4001430100002)(3660700001)(110136002)(107886002)(5003600100002)(68736007); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0301MB2267; H:HE1PR0301MB2266.eurprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; CAT:NONE; LANG:en; CAT:NONE;
received-spf: None (protection.outlook.com: ecitele.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0301MB226644496E8CDE7F697AE2789D540HE1PR0301MB2266_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jun 2016 11:29:25.7460 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0301MB2267
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/J4PEKn44l5pqxPM1RNA6dcFH6ao>
Cc: "draft-ietf-mpls-static-yang@ietf.org" <draft-ietf-mpls-static-yang@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>
Subject: Re: [mpls] YANG for MPLS-TP?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
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, 14 Jun 2016 11:29:35 -0000

Huub hi!

Lots of thanks for a prompt response.

I have mentioned draft-zhang and even provided a link to it. I have also commented that it seems very much incomplete.

But what is even more important, I do not understand how MPLS-TP OAM can be modeled without an MPLS-TP data model being defined.
E.g., if I want to apply an OAM operation (say, LSP-Ping on an MPLS-TP LSP), how can I do it if MPLS-TP LSP itself is not defined?

Regards,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com

From: Huub van Helvoort [mailto:huubatwork@gmail.com]
Sent: Tuesday, June 14, 2016 2:20 PM
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Cc: mpls@ietf.org; draft-ietf-mpls-static-yang@ietf.org; Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>
Subject: Re: [mpls] YANG for MPLS-TP?


Hello Sacha,

For MPLS-TP OAM there is draft-zhang-mpls-tp-oam.

Regards, Huub.

sent from Huawei Nexus
On 14 Jun 2016 12:22 p.m., "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
Hi all,
I wonder what are the WG plans (if any) regarding YANG data models for MPLS-TP.

While it is obviously true that static MPLS and MPLS-TP are different (neither is the subset of the other), MPLS-TP is today the most important application of static MPLS.

However, after looking up  draft-ietf-mpls-static-yang<https://datatracker.ietf.org/doc/draft-ietf-mpls-static-yang/?include_text=1> I did not find there any mention of MPLS-TP-specific issues.

One example that comes to mind is co-routed bi-directional and associated bi-directional MPLS-TP LSPs. Other issues include:

1.       MPLS-TP Identifiers (i.e. YANG model for RFC 6370<https://tools.ietf.org/html/rfc6370>)0>). From my POV such a data model is a pre-requisite for all MPLS-TP-related work

2.       MPLS-TP protection mechanisms

3.       MPLS-TP OAM mechanisms. There is an individual draft<https://datatracker.ietf.org/doc/draft-zhang-mpls-tp-yang-oam/?include_text=1> that tries to address these issues, but it looks to me like very much incomplete. E.g.:

o   It does not even mention RFC 6428<https://tools.ietf.org/html/rfc6428>

o   While RFC 6427<https://tools.ietf.org/html/rfc6427> appears in the list of Normative references in this draft, there are no actual references to this document.

Any inputs in this regard would be highly appreciated.

Regards, and lots of thanks in advance,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>


_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls