Hi Shahram Different ingress LSR allocate LD independently, and always automatically. It is not a static configuration.
Thanks Deccan "S. Davari" <[email protected]> 2015-07-15 下午 10:42 收件人 "[email protected]" <[email protected]> 抄送 "[email protected]" <[email protected]> 主题 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, "[email protected]" < [email protected]> 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.
