IETF Logo Mail Archive

Re: Next steps for rfc6874bis

Nick Hilliard <nick@foobar.org> Mon, 16 August 2021 16:13 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 1F32D3A0D45 for <ipv6@ietfa.amsl.com>; Mon, 16 Aug 2021 09:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-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 TAHIN2x7RiY6 for <ipv6@ietfa.amsl.com>; Mon, 16 Aug 2021 09:13:19 -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 002133A0D43 for <ipv6@ietf.org>; Mon, 16 Aug 2021 09:13:17 -0700 (PDT)
X-Envelope-To: ipv6@ietf.org
Received: from crumpet.local ([109.78.208.46]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 17GGDBcU087792 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 Aug 2021 17:13:11 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host [109.78.208.46] claimed to be crumpet.local
Subject: Re: Next steps for rfc6874bis
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
Cc: ipv6@ietf.org, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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> <m1mFccG-0000I3C@stereo.hq.phicoh.net> <20210816134703.meb4pfloazkco22n@anna.jacobs.jacobs-university.de> <m1mFdCV-0000HvC@stereo.hq.phicoh.net>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <e1dd5e83-31d2-8b8b-2608-309f8d8d9cd0@foobar.org>
Date: Mon, 16 Aug 2021 17:13:10 +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: <m1mFdCV-0000HvC@stereo.hq.phicoh.net>
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/5ub47Rh8mAkstPz95GeePR69oa0>
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: Mon, 16 Aug 2021 16:13:21 -0000

Philip Homburg wrote on 16/08/2021 15:02:
> At some point we can make '%' to be something the MAY be supported. But I
> assume that will only happen after we have mostly switched to the new
> character.

Given the IETF's general reluctance to deprecate standards, the most 
likely outcome of this suggestion would be that both "%" and "-" would 
need to be supported indefinitely.  This would be a regression.

Nick

v2.23.0 | Report a Bug | By Email