[mpls] HEADS UP!! ----Re: Document (draft-ietf-mpls-rmr) returned to working group - poll for interest.
Loa Andersson <loa@pi.nu> Mon, 19 October 2020 03:25 UTC
Return-Path: <loa@pi.nu>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DFA23A1274; Sun, 18 Oct 2020 20:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 yqtF4VqSzqfu; Sun, 18 Oct 2020 20:25:43 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEE953A1277; Sun, 18 Oct 2020 20:25:42 -0700 (PDT)
Received: from [192.168.1.11] (unknown [124.104.122.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 26D36321AE7; Mon, 19 Oct 2020 05:25:38 +0200 (CEST)
From: Loa Andersson <loa@pi.nu>
To: "mpls@ietf.org" <mpls@ietf.org>
Cc: "mpls-ads@ietf.org" <mpls-ads@ietf.org>, "draft-ietf-mpls-rmr@ietf.org" <draft-ietf-mpls-rmr@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
References: <b0453453-b7c9-ed06-f359-459137ad4c2a@pi.nu>
Message-ID: <a16d3c18-ab56-bca1-805f-2e795e4f7d1c@pi.nu>
Date: Mon, 19 Oct 2020 11:24:57 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <b0453453-b7c9-ed06-f359-459137ad4c2a@pi.nu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/b8aDSn2O8pY8rCNYRPK9zivz_po>
Subject: [mpls] HEADS UP!! ----Re: Document (draft-ietf-mpls-rmr) returned to working group - poll for interest.
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2020 03:25:45 -0000
Working Group A little more than a week ago I sent this mail to the working group, asking about the interest to continue the work on draft-ietf-mpls-rmr. As of today I have not seen any reaction whatsoever. I could take that to mean (unless there are a lot of mails the rest of this week) that there are no interest to continue working on the document. I'm intrested to see all kinds of reactions e.g.: - No, I don't think this is something the working group should do - Hmmm, I don't have an opinion one way or another, if there are enough support to do continue working on it, I don't care if it is progressed. - Yes, given that there are enough support we should go ahead an re- review the document, update and request publication. For all categories it is good if you have technical motivations. /Loa On 03/10/2020 00:04, Loa Andersson wrote: > Working Group, > > This mail starts a two week poll to establish the interest to continue > work on draft-ietf-mpls-rmr. > > draft-ietf-mpls-rmr were returned to the working to the working group > (about 2 weeks ago). > > Normally a document is returned this late in the process when a > necessary change is discovered that requires working group consensus > (i.e. a wglc) to implement. This time the document were returned due to > lack of (or very slow) response to directorate or the IESG reviews. > > When a document is returned for a well defined technical change it is > fairly easy to handle, we make the change and do a wglc. > > I have spent time trying to figure out what to do in a case like this. > There is very little information in our process document. The wg chairs > has converged on the following small process. > > - establish wg interest for the document, i.e. is this something we want > to do and do we have interest participating in progressing the document. > - leave approximately 2 weeks for working group discussion > - wglc > - when comments from the wglc is resolved, redo the publication request > > This document start a two week poll to establish the level of interest > to continue to work on draft-ietf-mpls-rmr. > > Please answer the following 2 questions: > > - do you think draft-ietf-mpls-rmr is need and will actually be deployed? > > - do you have the cycles to contribute to progressing the document > > /Loa > for the working group chairs > > -- Loa Andersson email: loa@pi.nu Senior MPLS Expert loa.pi.nu@gmail.com Bronze Dragon Consulting phone: +46 739 81 21 64
- [mpls] Document (draft-ietf-mpls-rmr) returned to… Loa Andersson
- [mpls] HEADS UP!! ----Re: Document (draft-ietf-mp… Loa Andersson
- Re: [mpls] HEADS UP!! ----Re: Document (draft-iet… LUIS MIGUEL CONTRERAS MURILLO
- Re: [mpls] Document (draft-ietf-mpls-rmr) returne… Kireeti Kompella