Re: [spring] Chair Review of draft-ietf-spring-srv6-srh-compression-11

[Joel Halpern <[e-mail]>]

While different WGs use issue trackers differently, in SPRING we 
consider the email list the primary source of information.  We use the 
issue tracker to help us track long term issues.  We also use it when 
the chairs when to be explixcit about how we understand the issue.  At 
the current time, there is no lack of discussion of these issues on the 
list, so we do not need an "issue" record to record it.  Also, given the 
range of views being expresssed (which is veyr good) we would 
practically have to copy the exchanges intot he issue tracker to get it 
all, which would not help anyone.

For SPRING, the issue tracker is a tool, just as the open issue section 
of the draft was a tool, to help us do our work.

Yours,

Joel

On 3/27/2024 7:12 AM, Robert Raszuk wrote:
> Andrew,
>
> In IETF process issues should be opened by those who claim their 
> existence not by the authors of the document.
>
> And repo shows 5 closed issues:
>
> https://github.com/ietf-wg-spring/draft-ietf-spring-srv6-srh-compression/issues?q=is%3Aissue+is%3Aclosed
>
> Maybe authors could keep latest version of the draft in there, but 
> this is usually chairs decision how they do version control on active 
> WG documents.
>
> Cheers,
> R.
>
>
> On Wed, Mar 27, 2024 at 12:02 PM Andrew Alston - IETF 
> <[e-mail]> wrote:
>
>     Interesting Robert,
>
>     That entire repo is entirely empty – was last updated on Feb 11th
>     – and directly conflicts with the slide deck presented at 119
>     which expressly lists the checksum issue as an open issue.
>
>     As per
>     https://datatracker.ietf.org/meeting/119/materials/slides-119-spring-compressed-srv6-segment-list-encoding
>
>     Andrew
>
>     *
>     *
>
>     Internal All Employees
>
>     From: Robert Raszuk <[e-mail]>
>     *Date: *Wednesday, 27 March 2024 at 13:58
>     *To: *Nick Hilliard <[e-mail]>
>     *Cc: *Andrew Alston - IETF <[e-mail]>,
>     [e-mail] <[e-mail]>, [e-mail]
>     <[e-mail]>
>     *Subject: *Re: [spring] Chair Review of
>     draft-ietf-spring-srv6-srh-compression-11
>
>     Nick,
>
>     So which part of RFC7282 ?
>
>     In tracker I see zero open issues:
>     https://github.com/ietf-wg-spring/draft-ietf-spring-srv6-srh-compression/issues
>
>     All issues have been addressed.
>
>     So what is the problem ?
>
>     Thx,
>     R.
>
>     On Wed, Mar 27, 2024 at 11:43 AM Nick Hilliard <[e-mail]>
>     wrote:
>
>         Robert Raszuk wrote on 27/03/2024 10:13:
>         > WGLC on this doc started Jan 22nd - Today we have March 27th
>         - was the
>         > result of the working group's last call announced and I
>         missed it ?
>         > Looking at the list it seems this draft got pretty
>         overwhelming support
>         > already. Why are we not progressing ? What is holding us ?
>
>         rfc7282.
>
>         Consensus is not weight of numbers.
>
>         Nick
>