Robert,
I'm amazed that after all these decades of RSVP and rsvp-te implementations
there are those who still state that there is no resource allocation or
management in the data plane. The RFCs are quiet on the topic of how
reservations are managed/enforced and it is up to the vendor to choose
ds,
Sasha
Office: +972-39266302
Cell: +972-549266302
Email: alexander.vainsht...@ecitele.com
-Original Message-
From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Lou Berger
Sent: Tuesday, July 3, 2018 4:54 PM
To: Robert Raszuk ; Jeff Tantsura
Cc: SPRING WG List ; Li
very TE LSP is and E-LSP or L-LSP.
And since this is SPRING SR since day one claims full support for
diffserv both in SR-MPLS as well as SRv6 architectures.
Sure - feel free to see my comments in the context of SR-TE (only)
rather than SR with DiffServ.
Lou
Best,
R.
On Tue, J
Hi Robert,
On 7/3/2018 4:07 AM, Robert Raszuk wrote:
Hello Jeff,
“What exactly do you call by "resource allocation" in WAN ?” –
anything that is not “best effort”, BW reservation, protection
type, number of hops, latency, you name it…
Somehow, between ATM and now
**
that you receive, and strive to resolve them through
discussion or by updating the draft.
Document: draft-ietf-spring-resiliency-use-cases-08
Reviewer: Lou Berger
Review Date: April 24
Intended Status: Informational
Summary:
I have some minor comments about this document that I think would be
