Re: [spring] Implementation Report on draft-ietf-spring-segment-routing-ldp-interop

Hi Robin

The mapping server is already implemented. And it is not that complex at all

As for the support of inter-AS option "C", there are two solutions
(1) "draft-filsfils-spring-sr-recursing-info-01" provides a way to use 
the prefix-SID of one address for another one. So refering to the second 
figure in the your draft "draft-li-spring-compare-sr-ldp-rsvpte-00", 
ASBR12 can  inject the IP addresses of "PE21" and "PE22" in the IGP of 
AS1 and use the IP address of ASBR11 itself as the "Recursing SID Address".
(2) "draft-ietf-spring-segment-routing-ldp-interop" suggests using 
BGP-LU to distribute the remote domain information as Jon Mitchell 
mention in his email. At the first glance, it may seem like an issue for 
some platforms. However, as it is mentioned in 
"draft-bashandy-rtgwg-bgp-pic-02" which was presented in the last IETF, 
it is actually very easy to flatten a 2 level recursion into a single 
level of recursion, thereby supporting any hardware capability

Thanks

Ahmed

On 11/2/2015 5:21 PM, Lizhenbin wrote:
>
> Hi Folks,
>
> I proposed my concern on the implementation of interoperability 
> between LDP and SR again in IETF. I also would like to remind you of 
> my draft again:
>
> https://tools.ietf.org/html/draft-li-spring-compare-sr-ldp-rsvpte-00
>
> In this draft I explained the possible challenges of SR comparing LDP. 
> And in sec 6 I summary the possible challenge of Interoperability 
> between SR and LDP/RSVP-TE. Until now I believe that there will be 
> much challege for the implementation. In fact in order to solve the 
> possbile issue I mentioned in the draft, the mapping server has been 
> introduced. Is it some central-control based solution in the IGP/LDP 
> distributed environment? I worried that there still more issues which 
> have to be solved and propose great challenge for the implementor on 
> the feature and when new mechanisms are introduced they will propose 
> new challenges again. If so, this may be nightmare for the developer 
> of the feature. Hope if there were the implementation the 
> implementation report on 
> draft-ietf-spring-segment-routing-ldp-interop-00 can be publised 
> accomanying the draft to demonstrate what can be done and maye what 
> can not be done. This will be much helpful to the implementors and 
> operators to consider their possible choice to cope with this interop 
> issue: take the challenge, leave it or replace the LDP network with SR 
> all at once without introducing the interoperability issue.
>
> Best Regards,
>
> Zhenbin(Robin)
>
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring