Re: Next steps for rfc6874bis
Nick Hilliard <nick@foobar.org> Thu, 12 August 2021 10:31 UTC
Return-Path: <nick@foobar.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 809A53A03F2 for <ipv6@ietfa.amsl.com>; Thu, 12 Aug 2021 03:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ylRn72xgWaGj for <ipv6@ietfa.amsl.com>; Thu, 12 Aug 2021 03:31:07 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BF713A03F5 for <ipv6@ietf.org>; Thu, 12 Aug 2021 03:31:06 -0700 (PDT)
X-Envelope-To: ipv6@ietf.org
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 17CAUuRv033349 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Aug 2021 11:30:57 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be crumpet.local
Subject: Re: Next steps for rfc6874bis
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, 6man <ipv6@ietf.org>
References: <667b9ebb-3c99-8c5b-fa57-796e5bb84b4c@gmail.com> <3269d750-2e97-9bb2-550a-94b652d689a4@foobar.org> <1ea4c0e5-fd7c-c39a-28a6-681f6c40af8c@gmail.com> <27470.1628692112@localhost> <406d13b3-4b30-1a1a-5cd7-27a36157a3ea@gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <136ffa06-9f35-37ca-bab6-13e21ec4e75e@foobar.org>
Date: Thu, 12 Aug 2021 11:30:55 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.48
MIME-Version: 1.0
In-Reply-To: <406d13b3-4b30-1a1a-5cd7-27a36157a3ea@gmail.com>
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/ipv6/CE12h2b_9_nlS_5A_xjcBQlGDXQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Aug 2021 10:31:13 -0000
Brian E Carpenter wrote on 12/08/2021 03:19: > OK, but maybe we should update the draft to state that clearly as an > open issue. well, is there a reasonable chance that this can be dealt with in future? If not, then the most realistic option is to mark it as CANTFIX and move on. Maybe in this case, the draft could note that there's an issue but no real hope of resolution? Nick
- Next steps for rfc6874bis Brian E Carpenter
- Re: Next steps for rfc6874bis Michael Richardson
- Re: Next steps for rfc6874bis Nick Hilliard
- Re: Next steps for rfc6874bis Brian E Carpenter
- Re: Next steps for rfc6874bis Michael Richardson
- Re: Next steps for rfc6874bis Brian E Carpenter
- Re: Next steps for rfc6874bis David Farmer
- Re: Next steps for rfc6874bis Nick Hilliard
- Re: Next steps for rfc6874bis Michael Richardson
- Re: Next steps for rfc6874bis Kerry Lynn
- Re: Next steps for rfc6874bis Michael Richardson
- Re: Next steps for rfc6874bis Mark Smith
- Re: Next steps for rfc6874bis Michael Richardson
- Re: Next steps for rfc6874bis Kerry Lynn
- Re: Next steps for rfc6874bis Brian E Carpenter
- Re: Next steps for rfc6874bis Brian E Carpenter
- Re: Next steps for rfc6874bis Brian E Carpenter
- Re: Next steps for rfc6874bis Brian E Carpenter
- Re: Next steps for rfc6874bis Brian E Carpenter
- Re: Next steps for rfc6874bis Philip Homburg
- Re: Next steps for rfc6874bis Jürgen Schönwälder
- Re: Next steps for rfc6874bis Philip Homburg
- Re: Next steps for rfc6874bis Nick Hilliard
- Re: Next steps for rfc6874bis Philip Homburg
- Re: Next steps for rfc6874bis Bob Hinden
- Re: Next steps for rfc6874bis Brian E Carpenter
- Re: Next steps for rfc6874bis Philip Homburg
- Re: Next steps for rfc6874bis Brian Carpenter
- Re: Next steps for rfc6874bis Philip Homburg
- Re: Next steps for rfc6874bis Brian E Carpenter
- Re: Next steps for rfc6874bis Philip Homburg
- Re: Next steps for rfc6874bis Carsten Bormann