Document: draft-ietf-spring-resource-aware-segments Title: Introducing Resource Awareness to SR Segments Reviewer: Himanshu Shah Review result: Has Issues
Following text can be improvised for better reading – “Although a centralized controller can have a global view of network state and can provision different services using different SR paths, in data packet forwarding it still relies on the DiffServ QoS mechanism [RFC2474] [RFC2475] to provide coarse-grained traffic differentiation in the network.” -- Although a centralized controller can have a global view of network state and can provision different services using different SR paths. However, in data packet forwarding it still relies on the DiffServ QoS mechanism [RFC2474] [RFC2475] to provide coarse-grained traffic differentiation in the network. -- In general, my view of this draft is that it mainly proposes using multiple SIDs, each SID associated with some TE resource that can be taken advantage mostly by controller for desired traffic engineering. So, it introduces the ‘high level’ concept (similar to L-LSP) without any other associated details (IGP extensions, link attributes, etc) that are necessary to make it work as a solution. But since this work is approved by the working group, it should be categorized, perhaps as informational rather than standardized track. It also appears that since one vendor has implemented the solution, this draft is more of an effort to legitimize that as standards track but without the associated details, there may or may not ever be an interoperable solution that IETF is chartered to provide. _______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org
