Robert, The default and CS topologies would each advertise their own resource-aware Node and Adj-SIDs, and these SID’s would be resource-aware with strictly separated resources. Physical links would be shared, but “soft” resources (queues, buffers etc.) would not.
Regards, Sasha From: Robert Raszuk <rob...@raszuk.net> Sent: Thursday, June 15, 2023 6:34 PM To: Alexander Vainshtein <alexander.vainsht...@rbbn.com> Cc: Christian Schmutzer (cschmutz) <cschm...@cisco.com>; spring@ietf.org; Dongjie (Jimmy) <jie.d...@huawei.com>; Stewart Bryant <stewart.bry...@gmail.com> Subject: Re: [EXTERNAL] Re: [spring] A technical concern regarding draft-schmutzer-spring-cs-sr-policy-00 Hi, I have probably did not say it explicitly, but the default topology would use its own resources – and experience its own problems, strictly orthogonal to whatever happens in the dedicated CS topology. IMHO and FWIW this could be treated as a possible approach for implementing the (in)famous “network slicing”. Isn't the default topo an underlay for any custom topology ? You seems to think that default topology can function "in parallel", but this is not how I understand it. As for “circuit switching over connectionless paradigm” – well, TDM circuit emulation has been standardized by the IETF years ago, has been quite widely deployed, and, AFAIK, is still growing as more operators try to scrap their SDH networks. Yeh happened to be for a number of years on a customer side using such an "invention" and my resistance to the subject draft is coming from this (bad) experience. Sure it is cool for operators ... not so for customers. I even wrote a draft one time trying to detect the hidden problems by such innovations: https://www.ietf.org/archive/id/draft-turaga-mpls-test-labels-01.txt<https://clicktime.symantec.com/15siFAWXYQbeXVKrxySKo?h=x62Izj8EA1ochFQn_IOjg5vppMp6uauU1mfZg75quk4=&u=https://www.ietf.org/archive/id/draft-turaga-mpls-test-labels-01.txt> Thx, R. Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
