Subject: [Srcomp] DT Charter

From: Ron Bonica <[email-masked]>
Date: Sun, 22 Nov 2020 22:18:49 +0000

Folks,

SRv6, as currently specified, is built upon a set of design principles. Design principles are built upon operational requirements.

When the SPRING WG specified SRv6, it overlooked some important operational requirements. This oversight resulted in design deficiencies and design deficiencies resulted in the formation of this design team.  If SRv6, as currently specified, were perfect, this design team would not exist.

Every time this design team discovers a previously overlooked requirement, it suggests two possible actions:

  *   Backing out an old design principle, and replacing it with a new one
  *   Adding a new design principle, without backing out an old one.

The requirements in Appendix A cast a shadow on  the first class of actions. They:

  *   Definitely benefit vendors, who might have to rework released code
  *   May benefit brownfield operators, who have already deployed code that might benefit from upgrade

However, they limit the possibilities for greenfield operators, who should not be encumbered by old design decisions.

Although I am a vendor who has already implemented SRv6, as currently implemented, I feel strongly about the future of SRv6. It could be a great innovation. However, if we want it to have a great future, we should address its oversights now. Casting a shadow over some design principles simply because they are new doesn't help.

So, if we are going to include the requirements in Appendix A in the main body of the text, we should include a preface about how they limit future solutions, who they benefit, and who they do not benefit.

                                                                                            Ron

Juniper Business Use Only