IETF Logo Mail Archive

Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard

Barry Leiba <barryleiba@computer.org> Fri, 17 June 2011 13:44 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E10C11E814B for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 06:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.891
X-Spam-Level:
X-Spam-Status: No, score=-102.891 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 8V3jaywz-mkF for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 06:44:13 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 003DF11E8148 for <ietf@ietf.org>; Fri, 17 Jun 2011 06:44:12 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1805602gxk.31 for <ietf@ietf.org>; Fri, 17 Jun 2011 06:44:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=E/wv4cRcSlU03Wf7ejPpkLUogE16x9474rQSaotC28A=; b=Xjg15vxdOo0ELL8P83lk9r/DLVMOlDWL+reHQDClltuZ7MgCcusTbrVudj40Lt7BXq bxwLhd/uTHzvmv9l8oGvfm/a9m+U+5rtm0rEf2AEORV9Sc97yD2JxKxppiuELUYFnHb/ VDpwHyozVi2lZUSL3aziXzXksW637L3p23cJ4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=kXuC2Kg4H4aF3XtocEMZed12QqBT6whYzukETDvWWR14r2OJNlqC6Uk0XiC92DumOI K/to0Tw1KdkURPQP81MbdVbrTF/wyhXbQOq/xM0i6QLFceLq9Qmf9mugn2ysdyyEWRLB /RR5nAucieuaX5nKL3zDQXYDGykOCP5WVr+YE=
MIME-Version: 1.0
Received: by 10.236.192.201 with SMTP id i49mr3344103yhn.525.1308318252444; Fri, 17 Jun 2011 06:44:12 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.236.42.200 with HTTP; Fri, 17 Jun 2011 06:44:12 -0700 (PDT)
In-Reply-To: <29624.1308317564@marajade.sandelman.ca>
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF885B5.4020202@gmx.de> <4DF8CA3D.7020904@gmail.com> <20110615201644.GB69872@shinkuro.com> <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com> <29624.1308317564@marajade.sandelman.ca>
Date: Fri, 17 Jun 2011 09:44:12 -0400
X-Google-Sender-Auth: Myey97WtcssSHNqgR7leBtXZxsw
Message-ID: <BANLkTinzzcaGZYW-DO2n9mrgV8SdWaHQQw@mail.gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Michael Richardson <mcr@sandelman.ca>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, Boris Zbarsky <bzbarsky@mit.edu>, Alexey Melnikov <alexey.melnikov@isode.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 13:44:13 -0000

>    Barry> internally, and, therefore, has no interoperability
>    Barry> requirements.  As best I can tell, the issue here is to let
>
> It does.  It's an RFC1918-type use, and for the same reason we had to
> document those networks, we have to document this URI.
> This document prevents someone else from creating "about:" scheme which
> is NOT internal.

Oh, yes: to be clear here... I am NOT suggesting that we shouldn't
register the URI scheme.  I'm only saying that the registration
doesn't require a great deal of standards-track documentation.  A
short Informational doc should do.

Barry

v2.23.0 | Report a Bug | By Email