This update resolves the remaining Discuss and Comments from the IESG review. Specifically: Roman Danyliw (1) - Section 7.1 clarification of source routing attacks. Ben Kaduk (1) - removed local configuration text from 2.1.2.1 around what the HMAC protects, protect RESERVED bits, added text to programmatically verify destination address. Ben Kaduk (4) - change the scope of the KEY ID to SR Domain global. Barry Leiba - s/register/registry/ Thanks to all the reviewers who have provided valuable comments, and spent time to thoroughly review and work through solutions to the issues they saw.. I believe this is the final draft revision. Thanks Darren > This update resolves most open discuss and comments raised during IESG last call. > This update does not resolve discuss items from Ben (1 and 4) and Roman (1). > Those to be updated in a subsequent revision. > On Oct 10, 2019, at 3:15 PM, internet-drafts@xxxxxxxx wrote: > > > A new version of I-D, draft-ietf-6man-segment-routing-header-25.txt > has been successfully submitted by Darren Dukes and posted to the > IETF repository. > > Name: draft-ietf-6man-segment-routing-header > Revision: 25 > Title: IPv6 Segment Routing Header (SRH) > Document date: 2019-10-10 > Group: 6man > Pages: 32 > URL: https://www.ietf.org/internet-drafts/draft-ietf-6man-segment-routing-header-25.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-6man-segment-routing-header/ > Htmlized: https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-25 > Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-6man-segment-routing-header > Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-segment-routing-header-25 > > Abstract: > Segment Routing can be applied to the IPv6 data plane using a new > type of Routing Extension Header called the Segment Routing Header. > This document describes the Segment Routing Header and how it is used > by Segment Routing capable nodes. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat >
