Yes, I know that, we have the same problem. However, considering your results in section 7.3, I'm not sure what coverage is presented there. Is that the coverage of link or node protection? If that is only link protection, can you please add the same for node protection? Did you take into consideration that we almost always need bidirectional connection? That would be nice to add this information to the draft.
Gabor -----Original Message----- From: Stewart Bryant [mailto:[email protected]] Sent: Friday, June 01, 2012 12:35 PM To: Gábor Sándor Enyedi Cc: Alia Atlas; [email protected] Subject: Re: opinions on adoption of draft-shand-remote-lfa as a WG draft Gabor Those are very reasonable questions, however it is quite a difficult problem to address since we need real topologies and these are only available under non-disclosure from network operators. This has historically been a particular problem for the academic IPFRR researchers. Section 7.3 of the draft is a survey of a number of operational networks that we have analyzed. Stewart (as author) On 01/06/2012 09:34, Gábor Sándor Enyedi wrote: > I conditionally support it. I think we need several further studies; e.g. > what are the RLFA friendly topologies, how can I improve my network to keep > up full coverage (and what extra cost that has), what is the bidirectional > coverage of RLFA (if path cannot be protected in either directions, the route > is not protected), how many targeted LDP sessions are needed when the network > is not the one operated by Stephane Litkowski, what is the coverage when > there was a failure in our network previously and so on. > > Gabor > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Alia Atlas > Sent: Wednesday, May 30, 2012 6:59 PM > To: [email protected] > Subject: opinions on adoption of draft-shand-remote-lfa as a WG draft > > draft-shand-remote-lfa was presented favorably this last IETF. There is > known IPR associated with it on file ( https://datatracker.ietf.org/ipr/1770/ > ) This draft presents a solution for IP/LDP fast-reroute that does not > guarantee 100% coverage but can substantially improve coverage over LFAs. > > We would like to initiate a WG poll to determine whether to adopt > draft-shand-remote-lfa. > We are, of course, interested in opinions and reasoning rather than simple > yes/no. > > Thanks, > Alia > _______________________________________________ > rtgwg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/rtgwg > _______________________________________________ > rtgwg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/rtgwg > -- For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html _______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
