Subject: [Srcomp] REQ-8-26-SPRING-SRV6-MIGRATION-01

From: "Henderickx, Wim (Nokia - BE/Antwerp)" <[email-masked]>
Date: Wed, 26 Aug 2020 08:05:24 +0000

Short Name: SPRING MIGRATION FROM SRV6

Description: The compression algorithm must allow for a smooth migration

Rationale: Having a solution that complies to RFC7855/NPG, would allow for a natural evolution for customers who deployed SRv6 already. This requirement tries to validate the impact that is required in control-plane, data-plane, addressing, framework. A solution that minimizes the impact would be preferred.

Metric:

  *   Compliance to RFC7855 and https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-16<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-16__;!!NEt6yMaO-gk!VJ3OZLtYdWK_l8KxGPIM0o60zhIpoYAx3DwJLjs3gIyIH8-Y_Fk7RacckPjCT8_5$>
  *   Impact on data-plane operation (if the HW would operate in a different way compared to the original operation)
  *   Impact on control-plane. (if the control plane needs to be updated to support the new compression mechanism)
  *   Impact on framework/addressing/ec (if the framework need addressing changes, etc)

Category: Migration

PS. This is a rework of REQ-7-27-SPRING-FRAMEWORK-01, so REQ-7-27-SPRING-FRAMEWORK-01 can be obsoleted