Alvaro,
Please refer to following comments regarding Section 2.1 and 2.2 of
draft-martin-spring-segment-routing-ipv6-use-cases
These sections describe the use cases of segment routing in home network and
access network. I would like to quote the text which concerns MPLS scalability
in section 2:
'
4. There is a need to connect millions of addressable segment
endpoints, thus high routing scalability is a requirement.
'
I am glad that authors can take into account scalability issue. But scalability
will be from multiple aspects. For the scenarios of the home network and access
network which likes to use IPv6 segment routing, the complex configuration for
the explicit routing will also be a challenge on scalability. In addition, in
these scenarios, the end user is easily involved. I wonder if the user could do
or likes to do such professional path policy configuration. Maybe SDN is a
possible solutions. But for the home network and the access network, there
maybe huge number of devices to control (e.g. 100, 000 access nodes mentioned
in seamless MPLS). It will also propose enough scalability challenge to the
possible controller. From my own point of view, the use case proposed here is
not persuasive enough until now.
Regards,
Zhenbin(Robin)
> Hi!
>
> This message officially starts the call for adoption for
> draft-martin-spring-segment-routing-ipv6-use-cases.
>
> Please indicate your position about adopting this use cases draft by
> end-of-day on March 27, 2014.
>
> http://tools.ietf.org/html/draft-martin-spring-segment-routing-ipv6-us
> e-ca
ses
>
> Thanks!
>From section 2.5:
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
