Re: [mpls] The MPLS WG has placed draft-mirsky-mpls-bfd-bootstrap-clarify in state "Candidate for WG Adoption"
Joel Halpern <jmh@joelhalpern.com> Sat, 20 January 2024 05:24 UTC
Return-Path: <jmh@joelhalpern.com>
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 279EFC14F70F; Fri, 19 Jan 2024 21:24:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3OUtDdsM36hz; Fri, 19 Jan 2024 21:24:03 -0800 (PST)
Received: from maila1.tigertech.net (maila1.tigertech.net [208.80.4.151]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47786C14F6EF; Fri, 19 Jan 2024 21:24:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila1.tigertech.net (Postfix) with ESMTP id 4TH4fB6xyDz4TH60; Fri, 19 Jan 2024 21:24:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1705728242; bh=HTNuCH9uGguY6Z4hHF/StkfWJ8vk+KV74+/U17GHyJo=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=ZM/8bmcsKlCKWwwrdkInYl0wAGKJ6wMwTvV5Y8RlXYfNNG8f9uxQsz1fuNBKP9u2i qxULKGuzJ21zRyv8Uf5GAAL6Oo3Mirt2Tk6oUvaTQ3YRVyz3k2p7lctH/DLd7Vn1kM Ol0/E0DseLN8Rn/JTi6UgzzEQjtaMfXIxbG5Cweg=
X-Quarantine-ID: <Bd1zqshS6lai>
X-Virus-Scanned: Debian amavisd-new at a1.tigertech.net
Received: from [192.168.21.84] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila1.tigertech.net (Postfix) with ESMTPSA id 4TH4f867f1z4TH5G; Fri, 19 Jan 2024 21:23:59 -0800 (PST)
Message-ID: <969962a3-0448-468d-b0b5-cc88921cb185@joelhalpern.com>
Date: Sat, 20 Jan 2024 00:23:57 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: loa@pi.nu, adrian@olddog.co.uk
Cc: draft-mirsky-mpls-bfd-bootstrap-clarify@ietf.org, mpls@ietf.org
References: <170565749323.16365.15858283842903876028@ietfa.amsl.com> <1bc61da8-6025-4ec1-80fb-86dee75da0bf@joelhalpern.com> <07bd01da4af2$bea8b740$3bfa25c0$@olddog.co.uk> <58b9f8e36b9076e947ee4eb8b1707be0.squirrel@pi.nu>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <58b9f8e36b9076e947ee4eb8b1707be0.squirrel@pi.nu>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/A50JT1RpNu8k00-hxSAOnyM79NY>
Subject: Re: [mpls] The MPLS WG has placed draft-mirsky-mpls-bfd-bootstrap-clarify in state "Candidate for WG Adoption"
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 20 Jan 2024 05:24:07 -0000
Thanks Loa. I have apparently long misinterpreted the tag. (This seems to be a variation on the nomcom favorite confusion between nominee and candidate. ) I wonder if the tag could be "WG Adoption has been requestedd by the authors"? Yours, Joel On 1/19/2024 11:39 PM, loa@pi.nu wrote: > Adrian, Joel and working group, > > I was there when we added the "Candidate for WG Adoption" state to the > tracker. The reason was that a working group may need to do some checks > and actions before starting the WGAP. > > I always claimed the the name of the state is not intuitive, but we were > updating the tracker in real-time, and Robert said that we could change > name later. > > However, I have never been able to come up with a better name. > > The point is that "Candidate for WG Adoption" does not call for comments, > but is there to let chairs with authors and stakeholders to prepare the > WGAP, > > That said it is never wrong to comment, whatever state a document is in. > > /Loa > >> Thanks Joel, and noted. >> >> We haven't actually started an adoption poll, merely reacted to the >> authors saying that they would like the document adopted by marking the >> draft as "on the path towards an adoption poll" while we do the usual >> sanity checks. >> >> Cheers, >> Adrian >> >> -----Original Message----- >> From: mpls <mpls-bounces@ietf.org> On Behalf Of Joel Halpern >> Sent: 19 January 2024 15:25 >> To: draft-mirsky-mpls-bfd-bootstrap-clarify@ietf.org; mpls@ietf.org >> Subject: Re: [mpls] The MPLS WG has placed >> draft-mirsky-mpls-bfd-bootstrap-clarify in state "Candidate for WG >> Adoption" >> >> Since this seems to be the correct base message for responding to the >> adoption call... >> >> I have read the document. It is clear. It appears to be a useful >> update to 5884 and to provide helpful clarifications to the standard. I >> support adoption. >> >> Once adopted, I do suggest that the second paragraph of section 5, >> particularly "Considering that this..." be reworded. >> >> Yours, >> >> Joel >> >> On 1/19/2024 4:44 AM, IETF Secretariat wrote: >>> The MPLS WG has placed draft-mirsky-mpls-bfd-bootstrap-clarify in state >>> Candidate for WG Adoption (entered by Adrian Farrel) >>> >>> The document is available at >>> https://datatracker.ietf.org/doc/draft-mirsky-mpls-bfd-bootstrap-clarify/ >>> >>> >>> _______________________________________________ >>> mpls mailing list >>> mpls@ietf.org >>> https://www.ietf.org/mailman/listinfo/mpls >> _______________________________________________ >> mpls mailing list >> mpls@ietf.org >> https://www.ietf.org/mailman/listinfo/mpls >> >> _______________________________________________ >> mpls mailing list >> mpls@ietf.org >> https://www.ietf.org/mailman/listinfo/mpls >> >
- [mpls] The MPLS WG has placed draft-mirsky-mpls-b… IETF Secretariat
- Re: [mpls] The MPLS WG has placed draft-mirsky-mp… Joel Halpern
- Re: [mpls] The MPLS WG has placed draft-mirsky-mp… Adrian Farrel
- Re: [mpls] The MPLS WG has placed draft-mirsky-mp… loa
- Re: [mpls] The MPLS WG has placed draft-mirsky-mp… Joel Halpern