Hi Tom,
Thanks for the review.
On Friday, I will update draft-bonica-6man-comp-rtg-hdr. It will contain a
section on mutability. It will say:
- the Segments Left field is mutable
- every other field in the CRH is immutable
I will also update draft-bonica-6man-vpn-dest-opt and
draft-bonica-6man-seg-end-opt. Both of those request an IANA option type with
the CHG bit equal to 0. So they are both immutable.
SID encoding isn't entirely opportunistic. Since the last IETF, we realized
that it would be burdensome for every vendor to support all three SID lengths.
So, we said that implementations MUST support 32-bit encoding and MAY support
16 bit encoding. (We dropped 8-bit encoding entirely).
A side effect of this decision is that a node should only send CRH's with
16-bit encoding every other node in the domain supports 16-bit encoding. So,
network operators will need to configure the SID length on each node, with the
default being 32.
Ron
Juniper Business Use Only
-----Original Message-----
From: Tom Herbert <[email protected]>
Sent: Wednesday, July 3, 2019 2:48 PM
To: Ron Bonica <[email protected]>
Cc: SPRING WG <[email protected]>; 6man WG <[email protected]>
Subject: Comments on draft-bonica-spring-srv6-plus
Hi Ron,
Thanks for the draft.
I think the name SRV6+ might be a little misleading in that it could be
misinterpreted as SRV6+ being a superset of SRV6. Specifically,
SRV6+ doesn't allow 128 bit SIDs which seems inherent in SRV6 and so
the primary function (and implementation) of SRV6 isn't compatible. It doesn't
seem like it would be that much effort to allow a 128 bit SID size to be
compatible.
I don't understand the rationale for needing a MSV to be explictly configured
throughout the domain. Couldn't the appropriate SID size be chosen by the
sender at run time. For instance, if all the SIDs in a list are less than
65,536 then 16 bit SIDs can be used, else 32 bit SIDs are used (I assume 16 and
32 bit SIDs are in same number space).
Since CRH has the bits stating the SID length there is no ambiguity at the
receiver. SID compression is opportunistic and it's always good practice to
avoid situations that require wide scale renumbering.
Please add a section on mutability requirements of protocol fields so that
there is no ambiguity.
Tom
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
