[apps-discuss] Review of draft-ietf-6man-uri-zoneid-05

Yves Lafon <ylafon@w3.org> Mon, 26 November 2012 14:56 UTC

Return-Path: <ylafon@w3.org>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 222EC21F8452; Mon, 26 Nov 2012 06:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level:
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_111=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ZsZWde227ym; Mon, 26 Nov 2012 06:56:45 -0800 (PST)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by ietfa.amsl.com (Postfix) with ESMTP id 786D421F843F; Mon, 26 Nov 2012 06:56:45 -0800 (PST)
Received: from ylafon by jay.w3.org with local (Exim 4.69) (envelope-from <ylafon@w3.org>) id 1Td070-0005OG-GL; Mon, 26 Nov 2012 09:56:42 -0500
Date: Mon, 26 Nov 2012 09:56:42 -0500
From: Yves Lafon <ylafon@w3.org>
To: apps-discuss@ietf.org, draft-ietf-6man-uri-zoneid@tools.ietf.org
Message-ID: <alpine.DEB.1.10.1211260945020.15401@wnl.j3.bet>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
Cc: appsdir@ietf.org, iesg@ietf.org
Subject: [apps-discuss] Review of draft-ietf-6man-uri-zoneid-05
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 14:56:46 -0000

I have been selected as the Applications Area Directorate reviewer for
this draft (for background on appsdir, please see
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate).

Please resolve these comments along with any other Last Call comments
you may receive. Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-6man-uri-zoneid-05
Title: IPv6 Zone Identifiers in Address Literals and Uniform Resource 
Identifiers
Reviewer: Yves Lafon
Review Date: 26 November 2012
IETF Last Call Date: 2012-11-23

Summary: The document is almost ready to progress, but some clarifications 
are needed on two points explicited below.

In section 3:
<<
    This document implies that all browsers should recognise a ZoneID
    preceded by an escaped "%".  In the spirit of "be liberal with what
    you accept", we also recommend that URI parsers accept bare "%" signs
    (i.e., a "%" not followed by two valid hexadecimal characters).  This
    makes it easy 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.
>>

Does it mean that such URIs can be present in an HTML document or that 
they MAY allow bare "%" signs when the URI is pasted in the address bar? 
(Those are two different use cases, and browsers may have different code 
paths for both).

In section 4:
It says
<<
    An HTTP server or proxy MUST ignore any ZoneID attached to an
    incoming URI, as it only has local significance at the sending host.
>>

A proxy can be considered as a sending host, so does it mean that a the 
receiving end MUST strip all ZoneID before processing the request? (and it 
would be a significant change to implementations), or could this be 
resolved by mandating Web browser to strip ZoneID prior to sending the 
request as it is only significant for the sending host and as it is the 
implementation that needs to be updated to recognize the new syntax?

-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves