RE: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>

[<[e-mail]>]

Hi Darren, 

I may missed where this was discussed, but this text is underspecified/not clear. 

The text says explicitly that the use of this tag is out of scope. It is weird to provision a field for something we don't know/understand (from the reading of the spec).

Cheers,
Med

> -----Message d'origine-----
> De : Darren Dukes (ddukes) [mailto:[e-mail]]
> Envoyé : lundi 3 juin 2019 21:47
> À : BOUCADAIR Mohamed TGI/OLN
> Cc : Bob Hinden; IPv6 List
> Objet : Re: 6man w.g. last call for <draft-ietf-6man-segment-routing-
> header-19.txt>
> 
> Hi Med, this was closed by the WG during the previous last call,
> concluding with this text.
> 
> Darren
> 
> > On May 27, 2019, at 5:02 AM, [e-mail] wrote:
> >
> > Hi Bob, all,
> >
> > I do still don't understand the intent of this field:
> >
> >   o  Tag: tag a packet as part of a class or group of packets, e.g.,
> >      packets sharing the same set of properties.  When tag is not used
> >      at source it MUST be set to zero on transmission.  When tag is not
> >      used during SRH Processing it SHOULD be ignored.  Tag is not used
> >      when processing the SID defined in Section 4.3.1.  It may be used
> >      when processing other SID types which are not defined in this
> >      document.  The allocation and use of tag is outside the scope of
> >      this document.
> >
> > In the absence of a clear definition of this field, it is better to set
> these bits as unassigned.
> >
> > Cheers,
> > Med
> >
> >> -----Message d'origine-----
> >> De : ipv6 [mailto:[e-mail]] De la part de Bob Hinden
> >> Envoyé : mercredi 22 mai 2019 15:40
> >> À : IPv6 List
> >> Cc : Bob Hinden
> >> Objet : 6man w.g. last call for <draft-ietf-6man-segment-routing-
> header-
> >> 19.txt>
> >>
> >> Hello,
> >>
> >> This message starts a new two week 6MAN Working Group Last Call on
> >> advancing:
> >>
> >>       Title           : IPv6 Segment Routing Header (SRH)
> >>       Authors         : Clarence Filsfils
> >>                         Darren Dukes
> >>                         Stefano Previdi
> >>                         John Leddy
> >>                         Satoru Matsushima
> >>                         Daniel Voyer
> >> 	Filename        : draft-ietf-6man-segment-routing-header-19.txt
> >> 	Pages           : 32
> >> 	Date            : 2019-05-21
> >>
> >>    https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header
> >>
> >> as a Proposed Standard.
> >>
> >> This document was in an extended last call that started in March of
> 2018.
> >> An issue tracker was set up, and eight new versions of the draft were
> >> produced and discussed on the list and at face to face 6man sessions.
> >> All of the issues in the tracker have been closed.  The chairs believe
> it
> >> is ready to advance, but given the number of changes and the time that
> >> elapsed, a new w.g. last call is warranted.  Please review the new
> >> document.
> >>
> >> Our thanks to the authors/editors and the working group for the work on
> >> this document.
> >>
> >> Substantive comments and statements of support for publishing this
> >> document should be directed to the mailing list. Editorial suggestions
> can
> >> be sent to the author.  This last call will
> >> end on 5 June 2019.
> >>
> >> Thanks,
> >> Bob & Ole
> >>
> >>
> >>
> >>
> >> --------------------------------------------------------------------
> >> IETF IPv6 working group mailing list
> >> [e-mail]
> >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >> --------------------------------------------------------------------
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > [e-mail]
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------