That is correct. ________________________________ From: spring <spring-boun...@ietf.org> on behalf of Tal Mizrahi <tal.mizrahi....@gmail.com> Sent: Tuesday, August 1, 2023 4:29 AM To: draft-ietf-spring-srv6-srh-compress...@ietf.org <draft-ietf-spring-srv6-srh-compress...@ietf.org>; spring@ietf.org <spring@ietf.org> Subject: [spring] Question regarding draft-ietf-spring-srv6-srh-compression
Dear Authors, I have a question regarding the following two paragraphs from the draft (at the bottom of the message). If I understand the text correctly, if the compressed segment list fits into a single SID, then the entire compressed list can be encoded in the DA, and the packet can be sent without an SRH. Note that this is specifically relevant with the NEXT-C-SID flavor. I would highly appreciate if you can confirm my understanding. Thanks, Tal. Quoting the relevant text from the draft: Regardless of how a compressed segment list is produced, it is encoded in the IPv6 header and optional SRH as described in Section 4.1 and 4.1.1 of [RFC8754]. The text is reproduced below for reference. A source node steers a packet into an SR Policy. If the SR Policy results in a Segment List containing a single segment, and there is no need to add information to the SRH flag or add TLV; the DA is set to the single Segment List entry, and the SRH MAY be omitted. _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
