[mpls] On Up and Down MEP in MPLS-TP (RE: 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)

Gregory Mirsky <gregory.mirsky@ericsson.com> Tue, 12 March 2013 18:56 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 AE8F921F8A67 for <mpls@ietfa.amsl.com>; Tue, 12 Mar 2013 11:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pv-+8ShLTnPr for <mpls@ietfa.amsl.com>; Tue, 12 Mar 2013 11:56:35 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 38B9A11E8176 for <mpls@ietf.org>; Tue, 12 Mar 2013 11:56:35 -0700 (PDT)
X-AuditID: c618062d-b7f0d6d00000097e-b4-513f7a6295dd
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id DD.64.02430.26A7F315; Tue, 12 Mar 2013 19:56:34 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0318.004; Tue, 12 Mar 2013 14:56:10 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Shahram Davari <davari@broadcom.com>, "hideki.endo.es@hitachi.com" <hideki.endo.es@hitachi.com>
Thread-Topic: On Up and Down MEP in MPLS-TP (RE: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)
Thread-Index: AQHOH1NCxu+w5AH5Vkey9NP/4JqeRA==
Date: Tue, 12 Mar 2013 18:56:09 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF11206FBD5@eusaamb103.ericsson.se>
References: <512C960E.70109@pi.nu> <4A6CE49E6084B141B15C0713B8993F281BD962A2@SJEXCHMB12.corp.ad.broa> <4A6CE49E6084B141B15C0713B8993F281BD9AAF4@SJEXCHMB12.corp.ad.broa> <XNM1$7$0$0$$6$1$2$A$5004088U513f719e@hitachi.com> <4A6CE49E6084B141B15C0713B8993F281BD9AB6D@SJEXCHMB12.corp.ad.broadcom.com>
In-Reply-To: <4A6CE49E6084B141B15C0713B8993F281BD9AB6D@SJEXCHMB12.corp.ad.broadcom.com>
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_7347100B5761DC41A166AC17F22DF11206FBD5eusaamb103ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42KZXLonSjepyj7QoL3DzGJ9r6dF862z7BbX v7xnsljysoPd4vulJSwWt5auZHVg85h1/yybR+uZNSweS5b8ZPL4cvkzWwBLFJdNSmpOZllq kb5dAldGf9dm9oK3pRUvb0xnbWB8l9rFyMkhIWAisXzpYVYIW0ziwr31bF2MXBxCAkcYJbbe X80C4SxnlNh76wQjSBWbgJHEi4097CC2iECqxOy+fjYQm1ngF1DHJT0QW1igWOLGjHtQNRUS O07NgbL1JJZ+mgRWzyKgKnFi7Q6wmbwC3hLLtu9mhFi2jkniT8M3sCJOgXCJK5+vgxUxAp33 /dQaJohl4hK3nsxngjhbQGLJnvPMELaoxMvH/6DeUZb4PucRC0R9vkTD5EdsEMsEJU7OfMIy gVF0FpJRs5CUzUJSBhHXkViw+xMbhK0tsWzha2YY+8yBx0zI4gsY2VcxcpQWp5blphsZbGIE xuQxCTbdHYx7XloeYpTmYFES5w1yvRAgJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgbG0Qv+k xR+mf0dP3GhY9ea5rJnIo4kCkzhZ2X+dq0+3sVnmbymkdcoz52bJHxYH7o6FlyvVJn98fvfl EY3Em/XbJ26Nyp2w+cu/vRo++w+cVL7T3N74oP6e/fGP1z/7Hpu24Otv9trbS448DV+wW+nY izjHlYpMQisWnBatv7bs42v/otc7QjblKrEUZyQaajEXFScCAHd7WtqXAgAA
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "mpls-ads@tools.ietf.org" <mpls-ads@tools.ietf.org>, "draft-ietf-mpls-tp-mip-mep-map@tools.ietf.org" <draft-ietf-mpls-tp-mip-mep-map@tools.ietf.org>
Subject: [mpls] On Up and Down MEP in MPLS-TP (RE: 2nd working group last call ondraft-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: Tue, 12 Mar 2013 18:56:37 -0000

Dear All,
What would be the most appropriate subject to continue this discussion? I'll give it a try, please feel free to change it.

I think that there's nothing that can preclude from supporting UP MEP on MPLS-TP LSP, according to UP MEP definition of RFC 6371, even when multpiple PWs mapped to that LSP. Same, I think, is the true for  p2mp PW. Note that service, VPWS, is not part of MPLS-TP architecture.

        Regards,
                Greg

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Shahram Davari
Sent: Tuesday, March 12, 2013 11:30 AM
To: hideki.endo.es@hitachi.com
Cc: mpls@ietf.org; mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-mip-mep-map@tools.ietf.org; mpls-ads@tools.ietf.org
Subject: Re: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map

Hideki,

So far no RFC or draft has talked about Down or UP MEP for LSPs. But if you think about it logically LSPs can't have UP-MEP because LSP can carry many PWs and each PW may enter the LSP from a different port/interface.  PWs can have UP-MEP but only for P2P services (VPWS), otherwise they can't have UP-MEP either (same as LSP).

My suggestion is to correct figures and change UP-MEPs to Down-MEPs for LSPs. Also to mention UP-MEP is out of scope.

Thx
SD

-----Original Message-----
From: hideki.endo.es@hitachi.com [mailto:hideki.endo.es@hitachi.com]
Sent: Tuesday, March 12, 2013 11:20 AM
To: Shahram Davari
Cc: loa@pi.nu; mpls@ietf.org; mpls-ads@tools.ietf.org; mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-mip-mep-map@tools.ietf.org
Subject: Re:Re: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map

Hi Shahram,

Just one comment.

>I would also argue that LSPs can't have UP-MEPs, since PWs from many ingress ports can enter an LSP  and therefore the LSP can't start on the ingress interface.

I think this depends on implementations.
Any RFC don't restrict to DOWN-MEPs in an LSP.

Anyway, MEP mechanism is out of scope in this draft as you said.

Thanks,
Hideki Endo

>Hi,
>
>Although I mentioned I am Ok with the draft to be advanced to RFC, but after reviewing it in more details it appears that the draft, in spite of its name, does talk about UP-MEP at all and only talks about UP-MIP, while the figures show UP-MEPs for LSPs.  Even if the scope of the draft is UP-MIP, considering that there can't be a MIP without a MEP,  the draft should have some wording regarding UP-MEPs and their applicability to LSPs and PWs. I would also argue that LSPs can't have UP-MEPs, since PWs from many ingress ports can enter an LSP  and therefore the LSP can't start on the ingress interface.
>
>A quick fix at this point is to mention UP-MEP is out of scope and change the figures to only show Down-MEPs. A better fix is to elaborate on UP-MEP and its applicability and placement, etc.
>
>Regards,
>Shahram
>
>
>
>-----Original Message-----
>From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
>Shahram Davari
>Sent: Wednesday, March 06, 2013 11:30 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] 2nd working group last call on
>draft-ietf-mpls-tp-mip-mep-map
>
>My Comments are addressed and I support this draft to be published as Informational  RFC.
>
>Thx
>Shahram
>
>-----Original Message-----
>From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
>Loa Andersson
>Sent: Tuesday, February 26, 2013 3:02 AM
>To: 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: [mpls] 2nd working group last call on
>draft-ietf-mpls-tp-mip-mep-map
>
>Working Group,
>
>draft-ietf-mpls-tp-mip-mep-map-05.txt has been updated after a previous
>last call, due to the nature a and extent of the updates we have chosen
>to start a 2nd wg last call.
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-mip-mep-map
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-mpls-tp-mip-mep-map-05
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-tp-mip-mep-map-05
>
>Please send your comments, including approval of the documents and the
>updates to the mpls working group list (mpls@ietf.org)
>
>This working group last call ends March 13, 2013.
>
>/Loa
>for the MPLS working group co-chairs
>--
>
>
>Loa Andersson                        email: loa@mail01.huawei.com
>Senior MPLS Expert                          loa@pi.nu
>Huawei Technologies (consult)        phone: +46 739 81 21 64
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>
>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>
>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>


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