The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] clarification on : draft-ietf-l3vpn-rt-constrain ver 2
Hi Note : re-send as it seem the original did not got replicated/distributed by the server . consider the simple case : PE11,PE12,PE13 client for RR1 . PE21,PE22,PE23 client for RR2. PE11 , advertise RT NLRI say (1,4) . where 1 is the AS Nbr and 4 is the RT . similarly PE12 and PE13 (all the 3 PE's are interested to receive VPNv4 route with RT=4) RR1 will do the best path selection and say it is the one received from PE11 . RR1 will advertise the following : 1)To PE11 ,PE12 and PE13 . chnage the orginator-id and next-hop to itself (as indicated in the draft) and send to all the 3 client and 2) send to RR2 with orig-id set as PE11 and next-hop unchanged (ie:PE11 ) My question : PE11 withdraw the advertisement . RR1 have to do the best path (say this time the one from PE12) and readvertise as above . my guess this step is not needed and better to be eliminated by the following : When sending advertisement to non client peer , the RR set the orig-ID and next-hop to itself . so when PE11 withdraw his advertisement RR1 simply have to do nothing . As an anology with multicast , when memeber leave the group and as far as still their is other memeber so no specific action needed to inform the other multicast peer . is the above workable ???,any points i am missing ??. Brgds _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml |
|