Re: I-D Action: draft-carpenter-6man-rfc6874bis-00.txt

Brian Carpenter <brian.e.carpenter@gmail.com> Mon, 05 July 2021 09:06 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 962FB3A0B12 for <ipv6@ietfa.amsl.com>; Mon, 5 Jul 2021 02:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 iUKQ8L9DJqKY for <ipv6@ietfa.amsl.com>; Mon, 5 Jul 2021 02:06:37 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 8E1553A0B0A for <ipv6@ietf.org>; Mon, 5 Jul 2021 02:06:36 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id t17so31342969lfq.0 for <ipv6@ietf.org>; Mon, 05 Jul 2021 02:06:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FqyZ26dy/trMba/P6vfscPSPF7zy/DWC6pEBgS02g00=; b=qpar/UIyti/QyIQa9GS/UT12wb4/uhlSzmBc++qL6eE8hgbyYfF7s+zZZDKnwYmsWm agHTT41RDcsxX4ShOe4yi2zTIfg28mNNDGvceltvkDy5lawn1h8qWiGgZCttS1HpScFs ol3/VNRqMlchsQ+YgIQcpLKUKEOF2+/maJpOhCVEPXbiHZHjzkeRLvLg5IjBV56OloqI igOTCs42nV0IzkK5inc5GmAA8pzN2pQO5J4WBHtSuDWjEk/bD047KSsVopjMOIuqgIDO ls4AMWW0rjhxJ4Q1XXA52GEp+4QLxUsQ/ZJn7amGa7DXK3k4AKcIfKbrV4SKD1ZFNlzN xYvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FqyZ26dy/trMba/P6vfscPSPF7zy/DWC6pEBgS02g00=; b=GMmtROBkNo/YJg/EDrv+2yvqa5+FXpKGLrmtmZ8UaEMyomjmWWqe4MZjhtHSCqwQfI xNQkC1sxA66o+18Id9XuSv2m/ZTdaqosD6FT73KZPKqmjT24Mw/uIPfn9M085kH0u32a HEM/QhLVlOFiKZ0fmn2r0S9jsOeCE1sOe44C/XC+afAnsE6p8LflXMsKlTS8zsqZKLqr lQEYM5xRj7+hRQeTPm2pNVZxY88gDU9zvvxxd98LRFM00p5dcoxomAuutBnqDMoq/Amc McexjP2T0IAEUAXd8V4Z8juZFV56BLHBR4RGA5LcymN0dInt9tOjsjArKw0H+bZEdsni BMMg==
X-Gm-Message-State: AOAM530guovCJ3/svtxMPlUQYqF6R2Wiid03Clt5WePYXqcDLv1Ti0bW Z/SokO6PxSittj8G+i4Zq6UU0JY9Z+UjWHiYBDM=
X-Google-Smtp-Source: ABdhPJzxFCZ/wHFpZxnDnj48rjVmff5fAi1DbVdKwL0MHmsmT0QmvN3RGJl9GmE+B2tckBITQ7AGVh9ukrvhvfsoQMs=
X-Received: by 2002:a05:6512:ad2:: with SMTP id n18mr9792590lfu.543.1625475993933; Mon, 05 Jul 2021 02:06:33 -0700 (PDT)
MIME-Version: 1.0
References: <162545101341.19246.8566193740265797873@ietfa.amsl.com> <95a7dbe5-e0a3-4676-9dcc-005ff53725e0@gmail.com> <CA+9kkMD3iSgo-KMM5Ed8bVnVCu_G3f2kB6zHKoOx2ta=x8QucA@mail.gmail.com>
In-Reply-To: <CA+9kkMD3iSgo-KMM5Ed8bVnVCu_G3f2kB6zHKoOx2ta=x8QucA@mail.gmail.com>
From: Brian Carpenter <brian.e.carpenter@gmail.com>
Date: Mon, 5 Jul 2021 21:06:22 +1200
Message-ID: <CANMZLAbmdWHDRBPpHgy_e4_0-WUVW2gjnbXWwu2pF_xi-S0vWQ@mail.gmail.com>
Subject: Re: I-D Action: draft-carpenter-6man-rfc6874bis-00.txt
To: Ted Hardie <ted.ietf@gmail.com>
Cc: 6man <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000359a2b05c65c9f70"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/A_0xMRLVxwO4QfmAwRvnl2qTTp8>
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, 05 Jul 2021 09:06:42 -0000

Ted, I agree about the complexity. otoh I believe that at least one browser
used to do this. How about saying that such a mechanism is not forbidden?

Regards,
    Brian Carpenter
    (via tiny screen & keyboard)

On Mon, 5 Jul 2021, 20:06 Ted Hardie, <ted.ietf@gmail.com> wrote:

> Hi Brian, Bob,
>
> Your draft says:
>
>    In the spirit of "be liberal with what you
>    accept", we also suggest that URI parsers accept bare "%" signs when
>    possible (i.e., a "%" not followed by two valid and meaningful
>    hexadecimal characters).  This would make it possible for a user to
>    copy and paste a string such as "fe80::a%en1" from the output of a
>    "ping" command and have it work.  On the other hand, "%ee1" would
>    need to be manually rewritten to "fe80::a%25ee1" to avoid any risk of
>    misinterpretation.
>
> I would prefer the document without this suggestion, as I think the
> resulting logic for a uri parser is a good bit harder than the " %s are
> handled differently within IPv6 literals" approach.  This requires the
> parser to treat %s  differently within IPv6 literals except when the result
> would be a "valid and meaningful" pair of hexadecimal characters.  If I
> follow your logic correctly, that would mean not simply checking to be sure
> that these are hex but also checking to be sure that the resulting
> characters are within the syntax for the ZoneID production.
>
> I think the proposal is much cleaner without this, and I encourage you to
> reconsider including it.
>
> regards,
>
> Ted Hardie
>
>
> On Mon, Jul 5, 2021 at 3:41 AM Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
>
>> Hi,
>>
>> In case people aren't aware, no web browser that we know of supports
>> RFC6874, i.e. the extension to URI/URL syntax for a link-local
>> zone index in literal IPv6 addresses. This is annoying in several
>> use cases.
>>
>> This new draft tackles what seems to be the main objection from
>> the browser community, namely that RFC6874 requires browsers to
>> remove the zone index before sending the URL out in a standard
>> HTTP message. That's a coding annoyance and it also breaks HTTP/1.1
>> rules for the "Host" header according to RFC7230.
>>
>> There's background to this issue at:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=700999 (still live but
>> officially closed WONTFIX) and
>> https://github.com/whatwg/url/issues/392
>>
>> The new draft proposes to update the RFC accordingly. The changes
>> are relatively small but significant. There's a diff between the
>> RFC and this draft at:
>>
>> https://www.cs.auckland.ac.nz/~brian/Diff-rfc6874-draft-carpenter-6man-rfc6874bis-00.html
>>
>> Comments welcome. If we want to go ahead with this fix, we will need to
>> reach out to the URI specialists and the browser community, to be sure
>> it isn't a waste of time.
>>
>> Regards
>>      Brian & Bob
>>
>>
>> -------- Forwarded Message --------
>> Subject: I-D Action: draft-carpenter-6man-rfc6874bis-00.txt
>> Date: Sun, 04 Jul 2021 19:10:13 -0700
>> From: internet-drafts@ietf.org
>> Reply-To: internet-drafts@ietf.org
>> To: i-d-announce@ietf.org
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>>         Title           : Representing IPv6 Zone Identifiers in Address
>> Literals and Uniform Resource Identifiers
>>         Authors         : Brian Carpenter
>>                           Robert M. Hinden
>>         Filename        : draft-carpenter-6man-rfc6874bis-00.txt
>>         Pages           : 10
>>         Date            : 2021-07-04
>>
>> Abstract:
>>    This document describes how the zone identifier of an IPv6 scoped
>>    address, defined as <zone_id> in the IPv6 Scoped Address Architecture
>>    (RFC 4007), can be represented in a literal IPv6 address and in a
>>    Uniform Resource Identifier that includes such a literal address.  It
>>    updates the URI Generic Syntax specification (RFC 3986) accordingly,
>>    and obsoletes RFC 6874.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-carpenter-6man-rfc6874bis/
>>
>> There is also an HTML version available at:
>> https://www.ietf.org/archive/id/draft-carpenter-6man-rfc6874bis-00.html
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>