Re: [mpls] YANG for MPLS-TP?
Loa Andersson <loa@pi.nu> Fri, 02 February 2018 04:35 UTC
Return-Path: <loa@pi.nu>
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 3867312EC9C; Thu, 1 Feb 2018 20:35:53 -0800 (PST)
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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 5FoPUlEgSvTd; Thu, 1 Feb 2018 20:35:50 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC9B212EC91; Thu, 1 Feb 2018 20:35:49 -0800 (PST)
Received: from [192.168.1.10] (unknown [119.94.175.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 2640118013B2; Fri, 2 Feb 2018 05:35:41 +0100 (CET)
To: Greg Mirsky <gregimirsky@gmail.com>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
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>, "draft-ietf-mpls-static-yang@ietf.org" <draft-ietf-mpls-static-yang@ietf.org>
References: <HE1PR0301MB226639582EEEE9D50D74E7889D540@HE1PR0301MB2266.eurprd03.prod.outlook.com> <CA+RyBmVr23G6rkOC05TXZnvh-+2YuVCOg5Vx_EiVWCtM+x3-pA@mail.gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <6ce854e5-f725-00c4-107b-0190d5dda625@pi.nu>
Date: Fri, 02 Feb 2018 12:35:34 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CA+RyBmVr23G6rkOC05TXZnvh-+2YuVCOg5Vx_EiVWCtM+x3-pA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/2Jj3rwl8Ql87m6lSZJum3oeWQJo>
Subject: Re: [mpls] YANG for MPLS-TP?
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: Fri, 02 Feb 2018 04:35:53 -0000
Greg, Sasha, working group, First, yes Greg is right, review of e.g. draft-zhang-mpls-tp-yang-oam, comments on if this is something we should work on would be very good. Second, I take it that you talk about a new MPLS-TP yang document. Between draft-zhang-mpls-tp-yang-oam and draft-ietf-mpls-static-yang, what is needed. Could that be covered in one the existing documents. /Loa On 2018-01-31 09:32, Greg Mirsky wrote: > Hi Sasha, > although we had MPLS WG invited to the discussion, I'm calling on Loa > (hi, Loa!) to look into it. > Your the most detailed questions prompted me to investigate and ask my > colleagues. Indeed, ITU-T SG-15 is working on G.8152 Protocol-neutral > management information model for the MPLS-TP network element. SG-15 uses > UML to define informational model so that, as I understand, YANG data > model can be produced automatically (almost). I haven't inspected the > document in all the details but got feeling that MPLS-TP Identifiers and > MPLS-TP OAM, ITU-style, have been addressed. Taking on IETF-style > MPLS-TP OAM YANG model seems to me both logical and useful. Should we, > or someone else interested, take on MPLS-TP Linear and Ring protection > RFCs - depends on whether SG-15 using G.8131 sufficiently cover RFC 6378. > I'm very much interested to have comments from MPLS WG whether work on > aspects of MPLS-TP data model, including > draft-zhang-mpls-tp-yang-oamĀ ,is of interest and has WG support. > > Regards, > Greg > > On Tue, Jun 14, 2016 at 3:22 AM, 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>). 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 <tel:+972%203-926-6302>____ > > Cell: +972-549266302 <tel:+972%2054-926-6302>____ > > 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 > <https://www.ietf.org/mailman/listinfo/mpls> > > -- Loa Andersson email: loa@pi.nu Senior MPLS Expert Huawei Technologies (consultant) phone: +46 739 81 21 64
- Re: [mpls] YANG for MPLS-TP? Huub van Helvoort
- Re: [mpls] YANG for MPLS-TP? Alexander Vainshtein
- [mpls] YANG for MPLS-TP? Alexander Vainshtein
- Re: [mpls] YANG for MPLS-TP? Huub van Helvoort
- Re: [mpls] YANG for MPLS-TP? Huub van Helvoort
- Re: [mpls] YANG for MPLS-TP? Alexander Vainshtein
- Re: [mpls] YANG for MPLS-TP? Alexander Vainshtein
- Re: [mpls] YANG for MPLS-TP? Greg Mirsky
- Re: [mpls] YANG for MPLS-TP? Loa Andersson