I tend to agree with Robert - The point is if we are going to advocate source
routing for both unicast (using SR) and multicast (using BIER) then we have to
have a comparative analysis done for what that entails in terms of existing
carriers using MPLS in their core and using LDP/RSVP-TE for "both unicast and
multicast at the sametime" and being able to achieve traffic engineering and
fast rerouting capability for both types of traffic at the sametime using one
set of protocol.
If SR and BIER are disjoint from each other, then are we providing the same (or
better) level of service from a protocol perspective to the carriers to meet
their demands for unicast and multicast at the sametime?
The reason I bring this up is because it would probably be the last resort for
a carrier to have to deploy both SR/BIER as well as LDP/RSVP to meet their
demands around both multicast and unicast traffic.
thanks,Usman
From: Robert Raszuk <[email protected]>
To: stefano previdi <[email protected]>
Cc: Usman Latif <[email protected]>; [email protected]; "[email protected]"
<[email protected]>
Sent: Tuesday, 15 September 2015, 20:07
Subject: Re: [spring] Query related to SR Architecture
Stefano,How SR controller is to be aware about amount of multicast traffic on a
per link basis in a given network to wisely select optimal paths for unicast
?Are you advocating completely disjoined topologies for unicast and multicast ?
If so it would be great to document it somewhere ... perhaps even as BCP.Of
course there are more solutions for engineered coexistance of both in the same
topology, but just saying go to BIER IMHO is not sufficient :)Best,
R.Hi,
if you're an operator (SP, content, etc) and looking for a multicast solution,
maybe you should have a look at BIER WG.
Thanks.
s.
On Sep 15, 2015, at 9:44 AM, Usman Latif <[email protected]> wrote:
> Hi,
>
> I have a basic question around SPRING/SR.
>
> How can an IP/MPLS carrier in the market today deploy SPRING in their core
> network without SR being able to support efficient multicast routing in the
> network?
> Are we not restricting carriers by proposing the SPRING/SR architecture when
> we know it does not efficiently support routing of multicast traffic?
>
> I would like get some feedback on this point
>
>
> thanks,
> Usman
> _______________________________________________
> spring mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/spring
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
