On November 2, 2017 at 7:59:31 AM, stefano previdi (stef...@previdi.net) wrote:
Stefano: Hi! > I would also strongly recommend that you include a Deployment/Operations Section. what exactly would you expect to find in such section ? We have the Manageability section which illustrates how SR can be managed. An operation/deployment section will have to be exhaustive and illustrative on the different use-cases that SR addresses and hence can become pretty large. To my view, the draft focuses on architecture, not on deployment or operation. These are mostly described in the different use-cases drafts. Expectations: take a look at rfc5706. There’s a lot in there, including manageability, which this document already has. To be specific, a couple of things come to mind: - considerations about when/why the same SRGB should be used. The text says that it is “strongly recommended”, but it would be nice to explain further the pros/cons. - considerations about deciding when/why someone may decide to sub-divide the network into multiple domains vs keeping just one. Is it a scalability issue, or just operational simplicity? Note that the use case documents justify the need for Segment Routing, they don’t talk about how to deploy it. The concepts above (SRGB and SR Domain) are presented in this document and statements are made about them but no further explanation is given — that is why I would strongly recommend (that is not a MUST) that you include a Deployment/Operations Considerations Section. Thanks! Alvaro.
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
