Hi All, [Email sent under separate cover to 6man, srv6ops, and spring. Discussion on the 6man list, please.]
When draft-ietf-spring-srv6-srh-compression was going through IETF review, several people raised the concern that it was at odds with RFC 8754 which says that the SID list is composed of 128 bit IPv6 addresses. Where we seem to have moved to is that: - IPv6 Destination Address fields must contain routable 128 bit IPv6 addresses - On receipt, the Destination Adress may be looked up to find a FIB entry that represents a SID - When the SRH is processed, the next entry in the SID list is mapped to a new value for the Destination Address None of that is a change to the SRv6 architecture or to the SRH processing described in RFC 8754. But the last point "mapped to" is a slight variation to "copied to". This new I-D that Suresh and I have written aims to make that simple clarification without inducing any change to the previous work. The hope is that will enable future works without a repeat of the painful discussions with the IESG. We are unsure whether this document should formally update RFC 8754. All opinions welcome. Cheers, Adrian _______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org
