Re: Options for draft-ietf-6man-uri-zoneid
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Sun, 29 April 2012 08:29 UTC
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 B9C8E21F8557 for <ipv6@ietfa.amsl.com>; Sun, 29 Apr 2012 01:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.094
X-Spam-Level:
X-Spam-Status: No, score=-103.094 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTTP_ESCAPED_HOST=0.134, 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 6LGcYHGz0ZYr for <ipv6@ietfa.amsl.com>; Sun, 29 Apr 2012 01:29:45 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id A512B21F8552 for <ipv6@ietf.org>; Sun, 29 Apr 2012 01:29:44 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8B23120C6B; Sun, 29 Apr 2012 10:29:43 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 7-OXDOqSaS2E; Sun, 29 Apr 2012 10:29:43 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1724720C6A; Sun, 29 Apr 2012 10:29:43 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id DDA751EC2DA3; Sun, 29 Apr 2012 10:29:44 +0200 (CEST)
Date: Sun, 29 Apr 2012 10:29:44 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Options for draft-ietf-6man-uri-zoneid
Message-ID: <20120429082944.GA92270@elstar.local>
Mail-Followup-To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
References: <4F9CF3A8.7000801@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4F9CF3A8.7000801@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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: Sun, 29 Apr 2012 08:29:45 -0000
On Sun, Apr 29, 2012 at 08:54:16AM +0100, Brian E Carpenter wrote: > Hi, > > In the IETF 83 discussion of draft-ietf-6man-uri-zoneid-00, > there was no clear consensus on the approach to pursue. In fact, > almost the same discussion occurred around draft-fenner-literal-zone > several years ago, but at that time the topic was simply dropped. > > This note summarises the main options. As a reminder, the problem to > be solved is how to tell a browser which interface to use when sending > packets to a literal link-local address. The reason for doing this is > purely for diagnostic purposes, since the Zone ID that identifies an > interface has no significance outside the sending host. For more details, > see the two drafts mentioned above. > > What we have today: link local address with no Zone ID > http://[fe80::a] > > The user cannot select the outgoing interface if there is more than one. > > The obvious solution would be to use the RFC4007 syntax (for an > example Zone ID of en1): > > http://[fe80::a%en1] > > However, this is impossible because % is *always* an escape character in > URI syntax [RFC3986]. There is no chance of the URI community accepting > such a hack to the syntax, so it isn't an option for us. > > The available options are therefore > > 1) Leave the problem unsolved. > > This would mean that per-interface diagnostics would still have to be > performed using ping or ping6 > > ping fe80::a%en1 > > Advantage: works today. > > Disadvantage: less convenient than using a browswer. > > 2) Escaping the escape character as allowed by RFC 3986: > > http://[fe80::a%25en1] > > Advantage: allows use of browser. > Disadvantage: ugly and confusing, doesn't allow simple cut and paste. > > 3) With alternative separator such as _ > > http://[fe80::a_en1] > > Advantage: allows use of browser. > Disadvantage: doesn't allow simple cut and paste. > > 4) With the "IPvFuture" syntax left open in RFC 3986: > > http://[v6.fe80::a_en1] > > Advantage: allows use of browser. > Disadvantage: ugly and redundant, doesn't allow simple cut and paste. > > Thus, the WG has to choose between options 1), 2), 3) and 4). If we want to solve this at all, I think 2) is the way to go since this format is after all easier to understand than format 3) or 4), which add yet another notation, and also because there might be other characters in the zone ID that need escaping as well. And since URLs are used not just by plain good old http and web browsers, I think we will have to find and document a common solution for this. /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/>
- Re: Options for draft-ietf-6man-uri-zoneid t.petch
- Options for draft-ietf-6man-uri-zoneid Brian E Carpenter
- Re: Options for draft-ietf-6man-uri-zoneid Juergen Schoenwaelder
- Re: Options for draft-ietf-6man-uri-zoneid Kerry Lynn
- Re: Options for draft-ietf-6man-uri-zoneid Brian E Carpenter
- Re: Options for draft-ietf-6man-uri-zoneid Ole Trøan
- Re: Options for draft-ietf-6man-uri-zoneid Rajiv Asati (rajiva)
- Re: Options for draft-ietf-6man-uri-zoneid Juergen Schoenwaelder
- Re: Options for draft-ietf-6man-uri-zoneid Simon Perreault
- Re: Options for draft-ietf-6man-uri-zoneid t.petch
- Re: Options for draft-ietf-6man-uri-zoneid Juergen Schoenwaelder
- Re: Options for draft-ietf-6man-uri-zoneid Kerry Lynn
- Re: Options for draft-ietf-6man-uri-zoneid Brian E Carpenter
- Re: Options for draft-ietf-6man-uri-zoneid Brian E Carpenter
- Re: Options for draft-ietf-6man-uri-zoneid Brian E Carpenter
- Re: Options for draft-ietf-6man-uri-zoneid Ole Trøan
- Re: Options for draft-ietf-6man-uri-zoneid Carsten Bormann
- Re: Options for draft-ietf-6man-uri-zoneid Brian E Carpenter
- Re: Options for draft-ietf-6man-uri-zoneid Juergen Schoenwaelder
- Re: Options for draft-ietf-6man-uri-zoneid t.petch
- Re: Options for draft-ietf-6man-uri-zoneid Brian E Carpenter
- Re: Options for draft-ietf-6man-uri-zoneid Juergen Schoenwaelder
- Re: Options for draft-ietf-6man-uri-zoneid t.petch