Re: New Version Notification for draft-voyer-6man-extension-header-insertion-08.txt

Hi, a few comments:

>From the introduction:

"In each deployment, traffic traversing an SR domain is encapsulated
in an outer IPv6 header for its journey through the SR domain."

Is encapsulation a requirement of SR then?

"To implement transport services within the SR domain, insertion or
removal of an SRH after the outer IPv6 header is performed."

I'm missing something fundamental here. If a packet is already being
encapsulated on ingress into the SR domain then why is SRH insertion
necessary at all? The encapsulation could just be IPv6 header plus the
segment routing header. The outer header plus SRH is then
automatically removed at the destination endpoint (presumably the
egress node for the SR domain). That would be exactly the
"encapsulation" alternative to EH insertion and fully compliant with
RFC8200.

Section 2 seems irrelevant to the discussion. The implication of this
and some of the other wording in the document seem to be more about
accommodating how the protocol has been implemented, as opposed to
setting the requirements those implementations need to follow. IMO,
this section can be removed without loss of content.

I am very surprised that the draft doesn't at least reference RFC8200
given that it is always raised as the standard prohibiting EH
insertion. I would expect at least an acknowledgement of the
requirements and hopefully an explanation if this is to be an
exception to RFC8200 requirements.

Tom

On Wed, Nov 20, 2019 at 7:32 PM Darren Dukes (ddukes) <ddukes@cisco.com> wrote:
>
> Hello 6man Working Group.
>
> This update has the following major changes:
> 1 - Revision 7 provided a normative definition of SRH insertion and removal.
> 2 - This rewrite shifts from the normative definition of SRH insertion within an SR Domain to a description of deployments of the same.
> 3 - Intended status has changed from proposed standard to informational.
>
> Thanks,
>   Darren, on behalf of the authors.
>
> > On Nov 20, 2019, at 1:22 PM, internet-drafts@ietf.org wrote:
> >
> >
> > A new version of I-D, draft-voyer-6man-extension-header-insertion-08.txt
> > has been successfully submitted by Darren Dukes and posted to the
> > IETF repository.
> >
> > Name:         draft-voyer-6man-extension-header-insertion
> > Revision:     08
> > Title:                Deployments With Insertion of IPv6 Segment
> >    Routing Headers
> > Document date:        2019-11-19
> > Group:                Individual Submission
> > Pages:                12
> > URL:            https://www.ietf.org/internet-drafts/draft-voyer-6man-extension-header-insertion-08.txt
> > Status:         https://datatracker.ietf.org/doc/draft-voyer-6man-extension-header-insertion/
> > Htmlized:       https://tools.ietf.org/html/draft-voyer-6man-extension-header-insertion-08
> > Htmlized:       https://datatracker.ietf.org/doc/html/draft-voyer-6man-extension-header-insertion
> > Diff:           https://www.ietf.org/rfcdiff?url2=draft-voyer-6man-extension-header-insertion-08
> >
> > Abstract:
> >   SRv6 is deployed in multiple provider networks.
> >
> >   This document describes the usage of SRH insertion and deletion
> >   within the SR domain and how security and end-to-end integrity is
> >   guaranteed.
> >
> >
> >
> >
> >
> > 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
> >
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------