Re: Next steps for rfc6874bis

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 12 August 2021 21:26 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 6147C3A1872 for <ipv6@ietfa.amsl.com>; Thu, 12 Aug 2021 14:26:00 -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 RIDzk2EYNzsQ for <ipv6@ietfa.amsl.com>; Thu, 12 Aug 2021 14:25:56 -0700 (PDT)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 2FF5D3A1822 for <ipv6@ietf.org>; Thu, 12 Aug 2021 14:25:56 -0700 (PDT)
Received: by mail-pl1-x62e.google.com with SMTP id b7so9085672plh.7 for <ipv6@ietf.org>; Thu, 12 Aug 2021 14:25:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=kny8U6S6xaMu9d0H2noJWGQVhiDyxHkJN7u/YUxmdxI=; b=THjCJH7P74T6zDgJlvvl3gbG4510tM9GQDux4TTwD8VBxgXqVnPA3O5ggVM50ZRzs3 THQ6IynnkEIEzYEf9yenxDcKKSkfCxBj6CLaQBJ6crMypf3oqrETmzSfiuHnVcDqexSg fSP3VPrwSrNbW/2Hj1MunSsDYpJ4VuNpsVlqEjmDeCxZLfPk5LBa+Cf6GbL6+KrMYqI9 8PN4B//R5huOWCBl9L6tnJ9CisTGE6V0GSojD7jd2DB/Ysfl1a4cxmJ8bzUyzFHyOuu1 0eD9/YLqZ3J9VtuMKc2xf2QGU+HO+R1jMbO37R2Np9wsEVs1bmty4r2hF40TJq0WFhvn 4HYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=kny8U6S6xaMu9d0H2noJWGQVhiDyxHkJN7u/YUxmdxI=; b=IjQMKU9/gGeZ1vu7Uu/RBfDGYGnyqapD9bZm+NZLPxBJ7wdgIdH9ZQYvOI23WPSuuG CfDXOTPgMHZbghe1GdcamXU01GaQe2eR58O8uL6tKzw8s9P3+BuEepDJp3pdxFKYMNdj 0YPtr7r167z1wKm2xviI5M29ya0xgegmvK9iNaExbQirBiKSwlDtTQz9TQOktKrlY60O LL4enugKqyTdYpwW6KkLyP8DBsIB0PFenYAhAS2LvuWpJbWTZS/TZL8nvE2UnLqmTyJz 24gpUDLwn4OZQVacWEK4EHqIrYRB3mEkkYhMRc60uJWcDwap8FuWkAGMER/NCbMsImuc nVhA==
X-Gm-Message-State: AOAM530a70pG1lCJWIoNgJ6bTZteQtogOBRtzpEdV3Y2bY6sL4J09oF7 Ny9YQzoWRzFbt4R0k4kZk/Fh72YTTc3khQ==
X-Google-Smtp-Source: ABdhPJwuV/vSyCoQibY4GefnQUs2bKBnX7cXty5YtOWNUARG0P65dgH+qMlfXRYCxdgpFMXM6TKt3A==
X-Received: by 2002:aa7:82cf:0:b029:3c4:4daa:fd68 with SMTP id f15-20020aa782cf0000b02903c44daafd68mr5999958pfn.66.1628803553253; Thu, 12 Aug 2021 14:25:53 -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 x19sm4556088pfa.104.2021.08.12.14.25.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 12 Aug 2021 14:25:52 -0700 (PDT)
Subject: Re: Next steps for rfc6874bis
To: Kerry Lynn <kerlyn@ieee.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: 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> <CABOxzu0k9siJ_JuERi9COgt966iP4Xe3Yq=AcpXOFL14qSW3UQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <070c2752-de53-9419-f023-0b78d71d226e@gmail.com>
Date: Fri, 13 Aug 2021 09:25:48 +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: <CABOxzu0k9siJ_JuERi9COgt966iP4Xe3Yq=AcpXOFL14qSW3UQ@mail.gmail.com>
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/eb0fJcqwS2UHWd8XGFmRFw5Hf-w>
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:26:00 -0000

Kerry,

> - If this has to be approved by the browser community as a condition
>   of it becoming widely available, do we know if they will support link
>   local addresses in principle?

That is exactly what we need to check, but not on this list because they
aren't here. We (the co-authors) will take this on.

Regards
   Brian Carpenter

On 13-Aug-21 05:24, Kerry Lynn wrote:
> If I could add my $0.02 (even though I'm not current on all the
> discussions and details):
> - I believe http://[fe80::%eth0] _used to work_ in Mozilla browsers;
>   we're talking maybe early 2000s. The earliest version I can find 
online
>   is c. 2015. Pretty sure I might have old VMs that can demonstrate
>   the functionality. (Let's assume there's an existence proof for parsing
>   a naked '%' between square brackets.)
> - If this has to be approved by the browser community as a condition
>   of it becoming widely available, do we know if they will support 
link
>   local addresses in principle? (If not, then the utility of this for e.g.
>   consumer router setup is moot.)
> - If the browser community can support this in principal, then we can
>   discuss EBNF. I strongly favor the syntax above, but any single char
>   is better than "%25". Certain OSes (not naming any names) use
>   numeric ZoneIDs and I think the cognitive dissonance of "%25<nn>"
>   is problematic.
> - If the browser community cannot support this, then we could perhaps
>   develop a patch for cURL to make it available at least for the engineering
>   community (I haven't checked cURL to see if it's already supported).
> 
> Cheers, Kerry
>