Re: [spring] Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming

S Moonesamy <sm+ietf@elandsys.com> Fri, 28 February 2020 09:37 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B51863A1416 for <spring@ietfa.amsl.com>; Fri, 28 Feb 2020 01:37:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cwrt5RmIK7DF for <spring@ietfa.amsl.com>; Fri, 28 Feb 2020 01:37:02 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 9C8603A1415 for <spring@ietf.org>; Fri, 28 Feb 2020 01:37:00 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.182.47]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 01S9aeFJ004903 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Feb 2020 01:36:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1582882614; x=1582969014; i=@elandsys.com; bh=QGkt1xyu8973Iz6EM8WyCSQ5PVl9aPt1sPY3HkPgLLM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HN7kPN1BREx8TYEfIzxSlRTiet9UrvKL1YOJ9kwzct+eXHJL/qrVkOKy6cSJ+cxfD 9QIXvT3sOawcChjad1/8E1wcvi0+AI4PENTO8p8L2TZ12eN5yl3ENyX6TNejfvIOvK gUuLf0TtTYhM0JQvaoqeMZRdhhPx8CVe3kVzZ4h4=
Message-Id: <6.2.5.6.2.20200228011557.0bd1a0b0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 28 Feb 2020 01:36:09 -0800
To: bruno.decraene@orange.com, spring@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Warren Kumari <warren@kumari.net>, Martin Vigoureux <martin.vigoureux@nokia.com>, Rob Shakir <robjs@google.com>
In-Reply-To: <23106_1582880310_5E58D636_23106_323_2_53C29892C857584299CB F5D05346208A48DC9786@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
References: <F88E3F76-DD4B-4807-A458-85FABFF20D96@gmail.com> <5D218BFB-0D6F-4F7D-858F-B571A67DC47F@leddy.net> <CAHw9_iJ_ipEvU0NUx44XbK0_DrLe_GRw6G=m+chK4wZcRP8BMg@mail.gmail.com> <ACA082A4-BC78-4C63-9F91-5C9A44F47642@cisco.com> <b693c244-95f9-473e-de21-166393280d18@gmail.com> <CAHw9_iL6oM73JnSU1QL0+PRohSH6sEskD=enH7QsPrWiUfStDg@mail.gmail.com> <6.2.5.6.2.20200227113437.10ad6088@elandnews.com> <23106_1582880310_5E58D636_23106_323_2_53C29892C857584299CBF5D05346208A48DC9786@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/OAzziVP4LYE0PQ1y8VAJgnknv9U>
Subject: Re: [spring] Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2020 09:37:04 -0000

Dear Mr Decraene,
At 12:58 AM 28-02-2020, bruno.decraene@orange.com wrote:
>1) People have the right to express, including to hum sometimes, but 
>decision is not based on the number of "+1".
>Do you have the impression that the decision is based on some voting 
>scheme? (Assuming the decision was made in the first place...) If 
>so, could you please help me see what makes you feel so?

My comment about the above was a response to the comment at 
https://mailarchive.ietf.org/arch/msg/spring/nIAqSeZJKq64QHbyy_ZrNqk_CXg/

>2) As regards to the timing, the duration of the call for comments 
>has indeed elapsed.
>If your comment is related to the actual work, as you may have seen, 
>there has been a high number of comments on the list so there is 
>work to be done on the resolution of the comments. The more 
>comments, the more time. The harder the comment, the more time. I 
>can't provide or force people to provide an ETA for the resolutions 
>of comments. I think that working on improving the document is more 
>important than a few weeks delay. BTW, I'm not aware of specific 
>timing requirement to advance a document to RFC. Closest things I've 
>seen is "SOON" [1] and "timely" [2]

I enquired about the working group process.  I don't see anything in 
the reference to RFC 2026 about Working Group procedures.  The second 
reference is to an Internet-Draft about the definition of the word 
"timely".  As far as I am aware, that Internet-Draft is not part of 
IETF Working Group procedures.

>If your question is related to formal state, is your point that the 
>datatracker state should have been moved from " In WG Last Call " to 
>" Revised I-D Needed - Issue raised by WGLC ". If so, I tend to 
>agree with you. Could/will also be " Doc Shepherd Follow-up 
>Underway" at some point.
>
>That been said, as I've said on the list, the end of the WG LC is 
>not the end of the ability for the WG to make technical comments on 
>the list. [3]. One example may be the latest comment from Chris Bowers.
>
>3) Your specific questions been answered, it's not crystal clear to 
>me what are you trying to achieve with your email. Do you believe 
>the document should advance faster, slower, not advance? That your 
>comments were not adequately answered? (although I'm not seen any 
>comment from your side on the mailing list). Please help me 
>understand your root concern.

My question was about when the the Working Group Last Call ends.  I 
don't view it as appropriate to determine whether the document should 
advance faster or slower as I am not responsible to make such a determination.

Regards,
S. Moonesamy