Re: Options for draft-ietf-6man-uri-zoneid

Kerry Lynn <kerlyn@ieee.org> Fri, 04 May 2012 14:31 UTC

Return-Path: <kerlyn2001@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 6440621F859E for <ipv6@ietfa.amsl.com>; Fri, 4 May 2012 07:31:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.261
X-Spam-Level:
X-Spam-Status: No, score=-102.261 tagged_above=-999 required=5 tests=[AWL=-0.169, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, 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 O7HjTWkA4G8F for <ipv6@ietfa.amsl.com>; Fri, 4 May 2012 07:31:02 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1866221F859A for <ipv6@ietf.org>; Fri, 4 May 2012 07:31:01 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so2375864lbb.31 for <ipv6@ietf.org>; Fri, 04 May 2012 07:31:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=u6s8TjKzwTMVohy4yP0xvJnecRfR+3VG/Y217PnrEkg=; b=UI/lDJGH34LgsMOfDK7fm1Wolz1PdIPcfS2hXKaEJgdqQFNr1PCyCgIzLXcy2wkpal Bs1qC/A7pWft4YCh7BABI8iE+PvL1eKV+fZkTf30lkYinDPBvMnu4JjbeNnIg9JRaJfd hFuF2PnrO8PTPVhrm+r4AW84oPlTt46+VX5O8o9MWxMeYZI5eZkzi2fchRlfYIyN7S29 f82k46zYU/9bJEakKbMK0Zeams46gg/oh0X7vNs1lB3OTxgMxyMwAufBl7j+W+zO0MD3 tQNozSNYVLqB9uAygdnCI8Lq3ABNyTPPHkeQwJ420rIELrD8s2YLAos5vq+fuTZJUOr/ ZMBg==
MIME-Version: 1.0
Received: by 10.152.128.201 with SMTP id nq9mr6032443lab.26.1336141860918; Fri, 04 May 2012 07:31:00 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.112.18.138 with HTTP; Fri, 4 May 2012 07:31:00 -0700 (PDT)
In-Reply-To: <20120504141059.GC13761@elstar.local>
References: <4F9CF3A8.7000801@gmail.com> <00a401cd29ca$41453680$4001a8c0@gateway.2wire.net> <F5F897FF-6E59-45EA-B5D1-A4F1363718B4@cisco.com> <20120504134409.GA13761@elstar.local> <4FA3DF9C.90802@viagenie.ca> <20120504141059.GC13761@elstar.local>
Date: Fri, 04 May 2012 10:31:00 -0400
X-Google-Sender-Auth: blp2fqUXdepOllJrbRlY-SEWkAM
Message-ID: <CABOxzu2YjfJmZemLG6dxDwSJtbr3swm1O=Df08S84T6k=bZ8Jw@mail.gmail.com>
Subject: Re: Options for draft-ietf-6man-uri-zoneid
From: Kerry Lynn <kerlyn@ieee.org>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Simon Perreault <simon.perreault@viagenie.ca>, ipv6@ietf.org
Content-Type: multipart/alternative; boundary="f46d042d0596fd546f04bf36c422"
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: Fri, 04 May 2012 14:31:03 -0000

On Fri, May 4, 2012 at 10:10 AM, Juergen Schoenwaelder <
j.schoenwaelder@jacobs-university.de> wrote:

> On Fri, May 04, 2012 at 09:54:36AM -0400, Simon Perreault wrote:
> > On 2012-05-04 09:44, Juergen Schoenwaelder wrote:
> > >On Fri, May 04, 2012 at 08:29:11AM -0500, Rajiv Asati (rajiva) wrote:
> > >>+1 for option 3 with hyphen.
> > >>
> > >>I like to be able to read the URI without having to put my glasses on.
> > >
> > >Interface names can contain other fancy characters and hence this one
> > >will simply not work in the general case.
> >
> > The character just after the address is "special". We know it is
> > special because it is just after the address. It can never be
> > confused with the interface name itself. We could even choose
> > something ridiculous, e.g. "x", as the special character and there
> > would be no possibility of conflict.
>
> Or even '%'.  Oops... never mind.


> My understanding is that URI formats place restrictions on the set of
> allowed unquoted characters. Some vendors (e.g. Juniper) use interface
> names that even contain slashes, e.g. fe-0/0/0. While replacing the %
> separating the zone identifier (typically an interface name) solves
> one problem, it does not solve the problems with fancy characters in
> the zone identifier.
>
> If you look at the draft, you see that Brian has defined
ZoneID = 1*( unreserved / pct-encoded )
so any "fancy" characters would need to be pct-encoded in the URI
representation, but not in the UI.

Do we want to take this one step further and update RFC 5952 with some
sort of canonical representation for link-local addresses?  I'm thinking
that
in the fullness of time it would certainly be nice to have cut-and-paste
compatibility across IPv6 utilities.  We could certainly retrofit e.g. ping6
to use either '%' or '-'.  The folks who use it now (wizards) could continue
to use the old separator or do the mental gymnastics in their heads (they
are wizards, after all).  Folks like my mom wouldn't even have to be aware
that '%' was ever used (unless they're history of technology majors).

-K-



> /js
>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>