Re: [mpls] working group last call on draft-ietf-mpls-tp-mip-mep-map

Gregory Mirsky <gregory.mirsky@ericsson.com> Mon, 03 December 2012 20:46 UTC

Return-Path: <gregory.mirsky@ericsson.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 2C06021F8890 for <mpls@ietfa.amsl.com>; Mon, 3 Dec 2012 12:46:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.525
X-Spam-Level:
X-Spam-Status: No, score=-6.525 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brjhw1c7x0JB for <mpls@ietfa.amsl.com>; Mon, 3 Dec 2012 12:46:47 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id EA94F21F888E for <mpls@ietf.org>; Mon, 3 Dec 2012 12:46:46 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id qB3KtpF3005168; Mon, 3 Dec 2012 14:55:53 -0600
Received: from EUSAAHC003.ericsson.se (147.117.188.81) by eusaamw0712.eamcs.ericsson.se (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Mon, 3 Dec 2012 15:46:39 -0500
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0318.001; Mon, 3 Dec 2012 15:46:39 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Rolf Winter <Rolf.Winter@neclab.eu>, Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: working group last call on draft-ietf-mpls-tp-mip-mep-map
Thread-Index: AQHN0VxJlaR5XVhT/UaZmQSyL/75l5gHYOjwgAB15ID//6/AQA==
Date: Mon, 03 Dec 2012 20:46:39 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF11201E9F9@eusaamb103.ericsson.se>
References: <5098CF68.2000105@pi.nu> <XNM1$7$0$0$$6$1$2$A$5003661U50a19cc6@hitachi.com> <50A3B5C0.4060203@pi.nu> <50B88D2A.30504@pi.nu> <791AD3077F94194BB2BDD13565B6295D555415BF@DAPHNIS.office.hd> <7347100B5761DC41A166AC17F22DF11201E837@eusaamb103.ericsson.se> <791AD3077F94194BB2BDD13565B6295D5554285D@DAPHNIS.office.hd>
In-Reply-To: <791AD3077F94194BB2BDD13565B6295D5554285D@DAPHNIS.office.hd>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF11201E9F9eusaamb103ericsso_"
MIME-Version: 1.0
Cc: "mpls-ads@tools.ietf.org" <mpls-ads@tools.ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-ietf-mpls-tp-mip-mep-map@tools.ietf.org" <draft-ietf-mpls-tp-mip-mep-map@tools.ietf.org>
Subject: Re: [mpls] working group last call on draft-ietf-mpls-tp-mip-mep-map
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 03 Dec 2012 20:46:48 -0000

Hi Rolf,
I've been thinking about that requirement for some time and am not convinced that such requirement, support multiple MIP per LSP/PW on given LSR/PE, exists. AFAIK, in Ethernet OAM only support of single MIP per MD/MEG Level is required and support of multiple MIPs is optional. True, multiple MIPs of different MD/MEG Levels might be enabled on a node but in MPLS-TP we use SPME to model MD/MEG Levels and thus such MIPs are on different LSPs. As for p2mp case, I'm not sure how dat-plane loopback can be used on uni-directional construct.

        Regards,
                Greg

-----Original Message-----
From: Rolf Winter [mailto:Rolf.Winter@neclab.eu]
Sent: Monday, December 03, 2012 12:15 PM
To: Gregory Mirsky; Loa Andersson; mpls@ietf.org
Cc: mpls-ads@tools.ietf.org; mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-mip-mep-map@tools.ietf.org
Subject: RE: working group last call on draft-ietf-mpls-tp-mip-mep-map

Hi Greg,

But that's the whole point of the document. There can be multiple in- and out-MIPs per LSP plus in the P2MP case there can be multiple out-MIPs per node. It cannot be based local configuration. There has to be information inside the OAM frame to address the respective MIP. Section 4 of the document has a (I believe) pretty good example of this.

Best,

Rolf

NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014


> -----Original Message-----
> From: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
> Sent: Montag, 3. Dezember 2012 19:20
> To: Rolf Winter; Loa Andersson; mpls@ietf.org
> Cc: mpls-ads@tools.ietf.org; mpls-chairs@tools.ietf.org; draft-ietf-
> mpls-tp-mip-mep-map@tools.ietf.org
> Subject: RE: working group last call on draft-ietf-mpls-tp-mip-mep-map
>
> Hi Rolf,
> Do you envision that multiple MIPs, both in- and out-, required to be
> supported on a given LSP/PW? I think that     only single MIP required
> per LSP/PW on an LSR/PE node. If that is the case, then there might be
> no apparent need to explicitly address in- and out- MIP as such
> distinction becomes part of local configuration.
>
>       Regards,
>               Greg
>
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of Rolf Winter
> Sent: Monday, December 03, 2012 5:42 AM
> To: Loa Andersson; mpls@ietf.org
> Cc: mpls-ads@tools.ietf.org; mpls-chairs@tools.ietf.org; draft-ietf-
> mpls-tp-mip-mep-map@tools.ietf.org
> Subject: Re: [mpls] working group last call on draft-ietf-mpls-tp-mip-
> mep-map
>
> Loa,
>
> These have been mentioned:
>
> 1. CV between a MEP and a MIP
> 2. traceroute over an MPLS-TP LSP and/or an MPLS-TP PW containing MIPs
> 3. data-plane loopback configuration at a MIP 4. diagnostic tests
>
> Best,
>
> Rolf
>
> NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road,
> London W3 6BL | Registered in England 2832014
>
>
> > -----Original Message-----
> > From: Loa Andersson [mailto:loa@pi.nu]
> > Sent: Freitag, 30. November 2012 11:41
> > To: mpls@ietf.org
> > Cc: mpls-chairs@tools.ietf.org; Martin Vigoureux;
> > draft-ietf-mpls-tp- mip-mep-map@tools.ietf.org;
> > mpls-ads@tools.ietf.org
> > Subject: Re: working group last call on draft-ietf-mpls-tp-mip-mep-
> map
> >
> > Authors,
> >
> > Can you plese give me an indication of which OAM functions the
> > separation of in and out MIPs are intended for?
> >
> > /Loa
> >
> >
> >
> > On 2012-11-14 16:16, Loa Andersson wrote:
> > >
> > > Working Group,
> > >
> > > This is to start a 2 week working group last call on
> > > draft-ietf-mpls-tp-mip-mep-map.
> > >
> > > Please send your comments to the mpls working group mailing list
> > > (mpls@ietf.org).
> > >
> > > Please send both technical comments, and if you are happy with the
> > > document as is also indications of support.
> > >
> > > This working group last call will end on November 28.
> > >
> > > /Loa
> > > for the wg co-chairs
> > >
> > >
> >
> > --
> >
> >
> > Loa Andersson                         email:
> loa.andersson@ericsson.com
> > Sr Strategy and Standards Manager            loa@pi.nu
> > Ericsson Inc                          phone: +46 10 717 52 13
> >                                               +46 767 72 92 13
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls