Re: [mpls] New version of draft-boutros-mpls-tp-loopback-01
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [mpls] New version of draft-boutros-mpls-tp-loopback-01



Hi Sami,

Thanks for the reply.

Two more questions at the bottom:

------------------------
Sami Boutros wrote:
Hi Huub,

At 11:49 AM 11/6/2008, Huub van Helvoort wrote:
Hi Sami,

You wrote:

Please find the updated version of the draft @
http://www.tla-group.com/~loa/draft-boutros-mpls-tp-loopback-01.txt

A few questions for clarification:

-1- if node B is in FLB what does it do with OAM packets that
    have as destination the MEP at the end of the LSP, or any
    MIP that may be located between node B and node C.

We are going to address this in a next revision, to allow OAM pkts
to go pass the MIP node where the loopback happens.

-2- if node B is in OLB what does it do with OAM packets that
    have as destination the MEP at the end of the LSP, or any
    MIP that may be located between node B and node C.

Same as above.

-3- if node B is in FLB are data packets looped back only to
    node A or are they still forwarded/bridged to node C as well.

Only looped back to A.

-4- are the error reponses to a) malformed message b) unknown
    TLV and c) authentication failure, only applicable to the
    lopback messages or they they generic.

They are for loopback messages, but could apply as well to other
messages in the future.

If a message is malformed, how can it be determined that it
was actually a loopback message?
And would it also be possible that a message is malformed such
that it looks like a loopback message?

Regards, Huub.


--
================================================================
                  http://www.van-helvoort.eu/
================================================================
Always remember that you are unique...just like everyone else...
_______________________________________________
mpls mailing list
mpls at ietf.org
https://www.ietf.org/mailman/listinfo/mpls



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.