Dhruv,
You raise a very good question. What makes us think that the largest network
diameter is 16? Next year, it may be 32! Maybe we need to rethink this
requirement.
An IPv6 routing header can contain no more than 2,048 bytes. Therefore, an SRH
without compression can support an SR path that contains as many as 127
segments. Maybe the requirement should be rewritten as follows:
NEW>
Description: The compression proposal MUST be able to represent SR
paths that contain up to 127 segments.
Rationale: The SRH, without compression, can represent SR
paths that contain up to 127 segments. Compression mechanisms must have the
same capability.
Metric: The compression proposal must be able to steer a packet
through an SR path that contains up to 127 segments.
<NEW
This shouldn't be too controversial because all of the proposed compression
mechanisms can satisfy the requirement.
Ron
Juniper Business Use Only
From: spring <[email protected]> On Behalf Of Dhruv Dhody
Sent: Monday, September 20, 2021 12:56 PM
To: [email protected]
Cc: [email protected]
Subject: Re: [spring] WG Adoption call -
draft-srcompdt-spring-compression-requirement -
draft-srcompdt-spring-compression-analysis
[SNIP]
In Section 4.2.3
Description: The compression proposal MUST be able to represent SR paths that
contain up to 16 segments.
Rationale: Strict TE paths require SID list lengths proportional to the
diameter of the SR domain.
It would be nice to include why the number "16" in the rationale.
[SNIP]
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
