答复: Re: issues about draft-ietf-bfd-rfc5884-clarifications-02

[[e-mail]]

Hi Mallik

Source address is also a good method. But it is better to form as 
standard.

thanks





"MALLIK MUDIGONDA (mmudigon)" <[e-mail]> 
2015-07-16 下午 02:16

收件人
"S. Davari" <[e-mail]>, "[e-mail]" 
<[e-mail]>
抄送
"[e-mail]" <[e-mail]>
主题
Re: issues about draft-ietf-bfd-rfc5884-clarifications-02






Hi,

I think the question is 2 different ingress LSRs using the same FEC, LSP, 
Discriminator values. Discriminator values can be the same for 2 different 
ingress LSRs and if the other values are same we can always use the Source 
address to differentiate. Am I missing something?

Regards
Mallik

From: "S. Davari" <[e-mail]>
Date: Wednesday, 15 July 2015 20:12
To: "[e-mail]" <[e-mail]>
Cc: "[e-mail]" <[e-mail]>
Subject: Re: issues about draft-ietf-bfd-rfc5884-clarifications-02

Hi

Why can't the ingress allocate different LD to each of those BFD sessions?

Regards, 
Shahram


On Jul 15, 2015, at 7:30 AM, "[e-mail]" <
[e-mail]> wrote:


hi authors 

It is neccessary to address the case that different ingress LSR establish 
BFD session with the same egress LSR, with same FEC, same local 
descriminator.
I think it is very useful to introduce a BFD Initiator TLV to LSP ping 
echo request message, to distinguish different ingress LSR. So that 
ingress allocate LD based on tuple <FEC, LSP> as defined in this draft, 
but egress allocate LD based on tuple <Initiator, FEC, RD>. 

thanks 
deccan 


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail 
(and any attachment transmitted herewith) is privileged and confidential 
and is intended for the exclusive use of the addressee(s).  If you are not 
an intended recipient, any disclosure, reproduction, distribution or other 
dissemination or use of the information contained is strictly prohibited. 
If you have received this mail in error, please delete it and notify us 
immediately.





--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail 
(and any attachment transmitted herewith) is privileged and confidential 
and is intended for the exclusive use of the addressee(s).  If you are not 
an intended recipient, any disclosure, reproduction, distribution or other 
dissemination or use of the information contained is strictly prohibited. 
If you have received this mail in error, please delete it and notify us 
immediately.




--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.