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:[email protected]] *代表 *Dongjie (Jimmy)
*发送时间:*2020年5月19日18:38
*收件人:*SPRING WG
*抄送:*[email protected]
*主题:*[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
[email protected]
https://www.ietf.org/mailman/listinfo/spring
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
