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

[Gregory Mirsky <[e-mail]>]

Hi Shahram,
I don't see line cards and distinct switch fabric in what's called "pizza boxes", a.k.a. fixed configuration nodes.

True, some implementations would not be able to support UP MEP but, IMHO, that is not good enough reason not to define it and even less of good reason not to support in capable implementations.

    Regards,
        Greg

________________________________
From: Shahram Davari [mailto:[e-mail]]
Sent: Wednesday, March 13, 2013 4:01 PM
To: Gregory Mirsky
Cc: [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]
Subject: RE: On Up and Down MEP in MPLS-TP (RE: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)

Greg,

You keep mentioning implementation. I am not arguing or discussing any implementation. I don't even care about implementation, but we should not ignore the fact that routers are implemented via Line-cards and switch fabrics.

Thx
Shahram


From: Gregory Mirsky [mailto:[e-mail]]
Sent: Wednesday, March 13, 2013 3:37 PM
To: Shahram Davari
Cc: [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]
Subject: RE: On Up and Down MEP in MPLS-TP (RE: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)

Hi Shahram,
I think that we came to state of declaring personal preferences and discussing specifics of various implementations.

    Best regards,
        Greg

________________________________
From: Shahram Davari [mailto:[e-mail]]
Sent: Wednesday, March 13, 2013 3:31 PM
To: Gregory Mirsky
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: On Up and Down MEP in MPLS-TP (RE: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)
Hi Greg,

Correct, but we can't define a MEP that can only support a subset of OAM specially the less desirable ones. Besides Synthetic loss is not accurate and as far as I know, not many users are interested in Synthetic loss.

Thx
SD

From: Gregory Mirsky [mailto:[e-mail]]
Sent: Wednesday, March 13, 2013 3:13 PM
To: Shahram Davari
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: On Up and Down MEP in MPLS-TP (RE: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)

Hi Shahram,
as indicated before, Synthetic LM is viable option and will work just fine from UP MEP. Would you agree?

    Regards,
        Greg

________________________________
From: Shahram Davari [mailto:[e-mail]]
Sent: Wednesday, March 13, 2013 2:21 PM
To: Gregory Mirsky
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: Re: On Up and Down MEP in MPLS-TP (RE: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)
Greg,

First of all MPLS-TP LM can use direct Loss measurement of RFC6374.

Secondly I am not asking on what is your implementation. I am asking logically how do you do LM for LSP UPMEP. You have to let the data packets go through forwarding and queuing and be actually delivered to the egress interface before you can increment receive LM counter. Just examining the forwarding result is not enough since for example the link between egress line card and the fabric can be broken or have errors.



Regards,
Shahram


On Mar 13, 2013, at 1:06 PM, "Gregory Mirsky" <[e-mail]<mailto:[e-mail]>> wrote:
Hi Shahram,
I believe that MPLS-TP LM is what is called Synthetic Loss Measurement and does not require reporting in-profile counters. If my understanding is correct, then I don't see how location of UP MEP in relation to PW A and PW B is important. Besides, could you refer me to definition of in-profile and out-ot-profile in regard to MPLS-TP. Much obliged.
As for your challenge I do have solution but, I believe, it is HW specific. Sorry if you can not do that.

    Regards,
        Greg

________________________________
From: Shahram Davari [mailto:[e-mail]]
Sent: Wednesday, March 13, 2013 12:55 PM
To: Gregory Mirsky; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: On Up and Down MEP in MPLS-TP (RE: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)
Greg,
We have a fundamental difference of opinion.  I have been involved in the OAM for over a decade now and one of the fundamental architectural requirements is that OAM packets MUST follow the data packets in the network and inside a switch/router up to the observation point (MEP). So it is not acceptable for data packets to be on Interface A and for MEP to be on Interface B.
In the example I gave, can you please tell me how you can do Loss Measurement for the LSP with UP-MEP? How do you increment the LSP UP-MEP receive LM counters for packets received from PW-A and PW-B? and where is the LSP-UP-MEP located?
Thx
Shahram
From: Gregory Mirsky [mailto:[e-mail]]
Sent: Wednesday, March 13, 2013 12:42 PM
To: Shahram Davari; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: On Up and Down MEP in MPLS-TP (RE: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)
Hi Shahram,
UP MEP, whether as defined by RFC 6371 or as defined elsewhere, e.g. IEEE 802.1ag, is not required to be co-located with an ingress to monitored service, e.g. attachement circuit, but with logical interface that represents monitored service. Location of UP MEP is undefined as long as it complies with where is sends to and receives from OAM packets/frames. In case of MPLS this element if MPLS forwarding function, in case of Ethernet - Bridge Relay Entity. For MPLS, as long as OAM packets sent to forwarding and get proper encapsulation, IMHO, we have ourselves an UP MEP. How packet being bounced within a node to get such treatment, I think, is implementation specific.
    Regards,
        Greg
________________________________
From: Shahram Davari [mailto:[e-mail]]
Sent: Wednesday, March 13, 2013 11:59 AM
To: Gregory Mirsky; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: On Up and Down MEP in MPLS-TP (RE: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)
Greg,
RFC6371 is very high level and does not define whether UP MEP applies to LSP or PW.  Assume there are 2 ingress interfaces A & B. Each interface maps Ethernet traffic to its own PW (PW-A and PW-B). Now assume both these PWs go inside the same LSP that exists Interface C. Now please explain if we were to have an UP-MEP for LSP then on which interface would that LSP UP-MEP reside? Interface A? B? C?
This simple example shows you can't have an LSP UP-MEP.
Thx
SD
From: Gregory Mirsky [mailto:[e-mail]]
Sent: Tuesday, March 12, 2013 11:56 AM
To: Shahram Davari; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: On Up and Down MEP in MPLS-TP (RE: [mpls] 2nd working group last call ondraft-ietf-mpls-tp-mip-mep-map)
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: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of Shahram Davari
Sent: Tuesday, March 12, 2013 11:30 AM
To: [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
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: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]
Sent: Tuesday, March 12, 2013 11:20 AM
To: Shahram Davari
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
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: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of
>Shahram Davari
>Sent: Wednesday, March 06, 2013 11:30 AM
>To: Loa Andersson; [e-mail]<mailto:[e-mail]>
>Cc: <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>;
>[e-mail]<mailto:[e-mail]>
>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: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of
>Loa Andersson
>Sent: Tuesday, February 26, 2013 3:02 AM
>To: [e-mail]<mailto:[e-mail]>
>Cc: <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>;
>[e-mail]<mailto:[e-mail]>
>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 ([e-mail]<mailto:[e-mail]>)
>
>This working group last call ends March 13, 2013.
>
>/Loa
>for the MPLS working group co-chairs
>--
>
>
>Loa Andersson                        email: [e-mail]<mailto:[e-mail]>
>Senior MPLS Expert                          [e-mail]<mailto:[e-mail]>
>Huawei Technologies (consult)        phone: [phone]
>_______________________________________________
>mpls mailing list
>[e-mail]<mailto:[e-mail]>
>https://www.ietf.org/mailman/listinfo/mpls
>
>
>_______________________________________________
>mpls mailing list
>[e-mail]<mailto:[e-mail]>
>https://www.ietf.org/mailman/listinfo/mpls
>
>
>_______________________________________________
>mpls mailing list
>[e-mail]<mailto:[e-mail]>
>https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/mpls