Re: Next steps for rfc6874bis

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 12 August 2021 21:33 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 96E613A005C for <ipv6@ietfa.amsl.com>; Thu, 12 Aug 2021 14:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 8O-MCTXfdbNm for <ipv6@ietfa.amsl.com>; Thu, 12 Aug 2021 14:33:42 -0700 (PDT)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 757283A003D for <ipv6@ietf.org>; Thu, 12 Aug 2021 14:33:42 -0700 (PDT)
Received: by mail-pj1-x102b.google.com with SMTP id qe12-20020a17090b4f8c00b00179321cbae7so2277050pjb.2 for <ipv6@ietf.org>; Thu, 12 Aug 2021 14:33:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=eTFQYMZgfnrZ+Kbw/Y5BMAEszJc67BbVQWqRdTyX+rM=; b=Z7U9QvBlNZ08nGoG+YF5h63f3eTbWPfZaYOikk2oEKlOo/wfqaz4gDIc582W7P6BuR eQwAd8eNLZyfKLG8bxFEAXGKMlZplSpURIVpgHEFxfsuuvqklovOT4KQ736neZpIV6eZ p3sZdAlMeUPZv3vjP1WBPKDMdWVDEUMwBBF9Lk1vy3MzuKS4txKg2ZNxXPBw2/LSexu+ AJ/YwZWn89G6PLsD+h6A1AvpdGe+QE+va5LUiHK0wM1guF1jeL4vpfmPftyq1LfE036B 98i2sGldYsyojuWP4UcEaBztGgdV9Ed46HIJnpBQCF7bv90O6lDDBeEX0bq5SbdpnYL2 pceg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=eTFQYMZgfnrZ+Kbw/Y5BMAEszJc67BbVQWqRdTyX+rM=; b=SZ4OdbP99z1maTEn/VTywCMz+plE8rRi1sqSaKYFktkxOF9zAQg2gOeUnUzuXkeUw1 hMRq32EvKWBLB1X5tsIi+6vERzzl7y7uVzn7GCPBVG/djf7h0AB918I8vI+dV7MJUNNO aLoQcNvbV1Ae79VC+cbZraSK26OjKAVfMLEPMCMyj3cwPEUFOvy2eAWJHB9fJVPLJ7FL YuJtSupKBYKWCgxWFl9KfsEtRGXDQjizJr3WmTOOVtiBd20qgETt9sSdLDOUMF0Y3LMQ jniMXQ1Z8YrP+hlv+MJiHm5j9zgwHUaoTtkk+GzjAzPPcFziSSKKZxRWoarNlPOEUoDh f2Ag==
X-Gm-Message-State: AOAM533C+vXrgEcFwbzFPdhUT7kmfzaSEqKsJs4Lenv6zMIOhz9hdDhq CGkVlVuExu5hM1PE7qn0NzP3kqqXf03wRg==
X-Google-Smtp-Source: ABdhPJyZBAI4ilUCP4dkukcIb66USIMpPq5LMpjcGoN10xMYLqKUS2YAni6m5LknoNKxsLoP2HWJwA==
X-Received: by 2002:a17:90b:1c07:: with SMTP id oc7mr18699626pjb.122.1628804020768; Thu, 12 Aug 2021 14:33:40 -0700 (PDT)
Received: from ?IPv6:2406:e003:1188:5b01:80b2:5c79:2266:e431? ([2406:e003:1188:5b01:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id k197sm4454699pfd.190.2021.08.12.14.33.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 12 Aug 2021 14:33:40 -0700 (PDT)
Subject: Re: Next steps for rfc6874bis
To: 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> <31519.1628777761@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <dfc093dd-69f9-aeb1-cc64-c61d26a0a33b@gmail.com>
Date: Fri, 13 Aug 2021 09:33:36 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <31519.1628777761@localhost>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/B8BgYUQNqf2Zy1C1PmMC8a5zoU8>
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 21:33:51 -0000

On 13-Aug-21 02:16, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     >> 1) in order to maintain cut&paste, if we do %25, then we have to
>     >> change everything anyway.
> 
>     > I agree; it would be wonderful if the browser implementors could deal
>     > with a non-encoded % but that is unclear right now.
> 
> I mean that command-line tools will need to support %25.
> 
>     >> 3) On GNU-Linux glibc systems, it's probably an update to
>     >> getaddrinfo()
>     > only.
>     >> A new character is probably easier to put in than %25.
> 
>     > Much easier. I would never envisage supporting percent-encoding in the
>     > socket API.
> 
> I would. If the goal is to have a consistent thing we can copy and paste,
> then we should support that.

Hmm. But anyway, this is all handwaving until we have a sensible dialogue
with the browser people.

   Brian

> 
>     >> That could happen really quickly.
> 
>     > I'm not convinced. Across all o/s and all libraries? Quickly?
> 
> In less than the 2021-2011 = 10 years, we've just spent? sure.
> 
> Would OSes with LTS releases do it within their LTS release? Maybe.
> If not, we are looking at 4-5 years for it to become ubiquitous.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
>