Part of my concern is that the document claims that this technique is
necessary to use resource reservation with segment routing. Given that
we know there are existing ways people do use resource reservation with
SR, it is not necessary.
The term "isolation" has been extensively debated in the traffic
engineering working group, and the proponents have not been able to make
a clear case for it.
Yours,
Joel
On 5/21/2020 9:07 AM, Dongjie (Jimmy) wrote:
Hi Joel,
Thanks for your comment.
In this document, isolation means resource isolation, more specifically, a set
of dedicated network resources are allocated on a group of network nodes and
links, and SR SIDs are used to represent the allocated network resources. As
mentioned by Aijun, this is described in section 5, it could be clarified
earlier in the draft if needed.
As for your statement regarding diffserv, I agree it has been widely used in
network thanks to its simplicity and scalability. Whether it can address all
services needs may be questionable. In IETF there have been many efforts to
meet specific service requirements by reserving network resources, such as
RSVP-TE, Detnet, etc. This draft aims to enhance SR with such capability.
Best regards,
Jie
-----Original Message-----
From: Joel M. Halpern [mailto:j...@joelhalpern.com]
Sent: Thursday, May 21, 2020 11:01 AM
To: qinfengwei <qinfeng...@chinamobile.com>; Dongjie (Jimmy)
<jie.d...@huawei.com>; 'SPRING WG' <spring@ietf.org>
Cc: draft-dong-spring-sr-for-enhanced-...@ietf.org
Subject: Re: [spring] 答复: Progressing
draft-dong-spring-sr-for-enhanced-vpn to enable SR with resource
management
This email (and the underlying document) asserts a need for "isolation"
without defining isolation, and without recognizing that the service needs
can be met by existing packet technologies.
The document also asserts that resource management requires packet based
resource reservation. We have significant evidence that diffserv treatment
coupled with central (PCE or equivalent) resource management can address
these needs.
At the very least, the discussion of isolation should be removed from the
document before it is evaluated for adoption.
Yours,
Joel
On 5/20/2020 10:47 PM, qinfengwei wrote:
Hi all,
At present, 5G applications have been widely developed, recently, many
enterprises require dedicated network resources to achieve isolation
from other services in the network, such as southern power grid, Migu
live video and Tencent cloud games. This document provides the
mechanism to enhance SR with resource identification capability. This
is an important feature to meet different customer’s requirement in
our network. Thus we believe it is a generic and useful enhancement to
SR, and hope it could move forward quickly in the WG.
Thanks,
Fengwei Qin
*发件人:*spring [mailto:spring-boun...@ietf.org] *代表 *Dongjie
(Jimmy)
*发送时间:*2020年5月19日18:38
*收件人:*SPRING WG
*抄送:*draft-dong-spring-sr-for-enhanced-...@ietf.org
*主题:*[spring] Progressing draft-dong-spring-sr-for-enhanced-vpn to
enable SR with resource management
Hi all,
The latest version of draft-dong-spring-sr-for-enhanced-vpn was
uploaded in March, which describes a generic enhancement to SR to
support resource representation and identification, by introducing the
resource semantics to SR SIDs. With such enhancement, SR could be used
not only for explicit path steering, but could also be used to build
resource guaranteed paths or virtual networks. Such SR based resource
guaranteed paths or virtual networks can be used as the underlay to
support different VPN services. The mechanism introduced in this
document is complementary to the existing SR functionalities, and
helps to complete the tool set of segment routing.
Based on the discussion on mail list and the presentations on previous
IETF meetings, this draft has been revised several times, all the
comments received so far has been resolved and reflected in the
current version. To move forward, the authors would like to know if
there are further comments on this document, and people’s opinion on
whether it is in the right direction.
Comments and feedbacks are welcome.
Best regards,
Jie
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
