Hi Joel,
the phrase "circuit style" attracted my attention and reviewed the draft.
I think segment routing should provide good support for proper traffic
engineering (guaranteed bandwidth, recovery, path constraints etc.) hence i
believe the draft should be adopted.
Cheers,
Daniele
On Fri, May 1
Hi Daniele,
Could you kindly elaborate on what level of "guaranteed bandwidth" you
expect SR to provide ? Especially in the context of _circuit_ emulation ?
And even if you build the mechanism to account for bandwidth on a per class
of service basis and use controller to push your policies everyw
Hi Robert,
i had in mind something with the same capabilities/characteristics of
RSVP-TE.
The same problem has been addressed for decades by operators using LDP for
90% of the traffic and RSVP-TE just for a small portion of the traffic
(e.g. phone call back in the days).
With mix of admission cont
Hi Weiqiang,
This draft proposed an interesting solution for dynamic SRv6 deployment,
especially with centralized management of SRv6 locator prefix. As the draft
descripted, it is valuable to simplify the CPEs to join in the SRv6 domain. I
wonder whether if this could be done by current exist
> If you want to have a network slice for remote surgery probably you
> need something more reliable, but otherwise it's a good enough solution.
Spot on !
And that is my main point. We are reusing notion of completely different
technology like SONET/SDH containers.
And that is to create only a p
Hi Robert,
i wouldn't just focus on the guaranteed bandwidth (which in any case has
been working with RSVP-TE and this solution will provide something as good
as that), but also on the other key requirements that SR-CS can meet (like
correctly identified in the draft):
- Predictable E2E TE paths w
> why intense admission control would be a problem in the network ?
Imagine you are Tier 1 and not selling access, but doing basic peering with
other Tier 1s.
What admission control do you configure there ?
Equal to your ingress bw ? That's of no use as physics is your ceiling
already.
Lower th
Speaking only as an individual.
I am unable to follow your argument here.
If you are a service provider (any tier, any kind) either you are
offering some of your customers circuit-like services, or you aren't.
If you aren't, then this draft does nothing for you, and does you no
harm, because
Hi Joel,
> Your argument, retained below, seems to assume that you simply offer
> the service to all customers for all traffic.
Nope, not at all.
My point is that to offer the service in reality of operational networks as
described in the draft is hard if not impossible.
What you can offer is t
Hi Aihua,
Thanks for your comments.
The allocation process of SRv6 Locator in this draft follows the DHCPv6 prefix
allocation process.
Compared to IPv6 prefix allocation process, the allocation process of SRv6
prefix has some new requirements.
For example, while assigning the Locator prefi
10 matches
Mail list logo
