IETF Logo Mail Archive

Re: Link-local IPv6 addresses in URIs

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 22 November 2011 02:57 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 4041311E8087 for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 18:57:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.2
X-Spam-Level:
X-Spam-Status: No, score=-103.2 tagged_above=-999 required=5 tests=[AWL=-0.201, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vul5IMCXhOic for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 18:56:59 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E58AA11E8085 for <ipv6@ietf.org>; Mon, 21 Nov 2011 18:56:58 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so3817287vcb.31 for <ipv6@ietf.org>; Mon, 21 Nov 2011 18:56:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=c9FemJ/rG4gBlfT9l/y0rj1d3jbwuQBA4FwQdWYeen8=; b=FxoJkd4vwH8v5LRIw63KrFzL+O/JysVv9N9UMoSgrBuO1mVXuM873h7ublv0EUJurs IXCdRmJdtluCJwz/Se4mHuBQ38ETI2SoPi4ILmmYKYkUJkbkgkeCdC46wFcFt5eT3CTB fObGPnLAfeFK6omcX/NuujBpVGpuRAr5uqVM8=
Received: by 10.52.21.148 with SMTP id v20mr16087920vde.89.1321930618488; Mon, 21 Nov 2011 18:56:58 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id a2sm11412294vdj.3.2011.11.21.18.56.55 (version=SSLv3 cipher=OTHER); Mon, 21 Nov 2011 18:56:57 -0800 (PST)
Message-ID: <4ECB0F84.5080802@gmail.com>
Date: Tue, 22 Nov 2011 15:57:08 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Tomoyuki Sahara <sahara@surt.net>
Subject: Re: Link-local IPv6 addresses in URIs
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com> <880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org> <CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com> <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com>
In-Reply-To: <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>, Kerry Lynn <kerlyn2001@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 22 Nov 2011 02:57:03 -0000

On 2011-11-18 15:27, Tomoyuki Sahara wrote:
> Hi,
> 
> That sounds good to me too.
> 
>> My ABNF is pretty rusty, so I offer the following extension to the RFC 3986
>> IPv6address rule only as a starting point:
>> / "FE80::" [ *3( h16 ":" ) h16 ] [ "%" 1*4(ALPHA / DIGIT) ]

That's one option; another one is to define the syntax for *any*
address format and restrict it to fe80::/10 by a SHOULD.
I'm inclined towards the latter, in case some other use case
shows up later.

> 
> I have some comments:
> 
>   - An interface name may be longer than 4 characters.  But I know we should
>     have some limit so I suggest 15 because it's maximum length of interface
>     name on *BSD and Linux systems.

Seems reasonable.

> 
>   - FYI, there was an attempt to define textual representation of zone id:
>     http://tools.ietf.org/html/draft-ietf-ipngwg-scoping-arch-04#section-12

That's RFC 4007 now.

> 
>   - Can we have a dot in interface name?  On Linux systems, VLAN interfaces
>     have one.  An example in the draft above has "%pvc1.3" (may be an ATM
>     interface?).

Yes, we can use the character set "unreserved" from the URI syntax
which is defined by

   unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"

      Brian

v2.20.0 | Report a Bug | By Email