Re: [apps-discuss] AppsDir review of draft-saintandre-urn-example

"Murray S. Kucherawy" <superuser@gmail.com> Sat, 30 March 2013 17:43 UTC

Return-Path: <superuser@gmail.com>
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 A7B0021F875C; Sat, 30 Mar 2013 10:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.318
X-Spam-Level:
X-Spam-Status: No, score=-3.318 tagged_above=-999 required=5 tests=[AWL=0.280, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 4MU9GAH+0yFK; Sat, 30 Mar 2013 10:43:29 -0700 (PDT)
Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by ietfa.amsl.com (Postfix) with ESMTP id B2B7D21F8749; Sat, 30 Mar 2013 10:43:28 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id a12so1191280wgh.9 for <multiple recipients>; Sat, 30 Mar 2013 10:43:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=JdEb+Wj+abgchNg18US16IJQ2zScKb84k1FOifYij6k=; b=zhnjbpoYQKpXVkfhAtl6iCMgzNJF57W+hIZSo267TnfGtERTCLx15U1/Im7FjCHOVm GVXE6cRF6FUVLNil3H2GNYKHcp5pcGrLd3lI69j5105LHfKIsGgHUcMczzYono4H2AF9 vhRrKbejCQibVFUomiUu+qpqDpmh5abivP+1rfWZMbRf8JkNHoOCero2B1a4/Ee7icdd dfSdkeYlxqami2bNcXmTdqFsy9MVS51t0Ly2Xq6TE6mbr9KDUr5/qachvFW1dFHzhCgz vjCvBWZrcLNzBVyEFFF9EMLY5s5F18phncAFcHybjUoYCEFecwoQV/XMC3hh70a4Gh7/ BoJg==
MIME-Version: 1.0
X-Received: by 10.180.94.133 with SMTP id dc5mr3433346wib.1.1364665407922; Sat, 30 Mar 2013 10:43:27 -0700 (PDT)
Received: by 10.180.13.71 with HTTP; Sat, 30 Mar 2013 10:43:27 -0700 (PDT)
In-Reply-To: <CAC4RtVA8WsP+OBq0Nc-Cu_XLraS6KQ4MO6YG_j5nJs3c15aV9A@mail.gmail.com>
References: <CAL0qLwbEgtAVbY-DK3O_e3qcKXTHdJAgeC4P86VK5sK7Wn06sQ@mail.gmail.com> <5156641B.70302@stpeter.im> <CAC4RtVA8WsP+OBq0Nc-Cu_XLraS6KQ4MO6YG_j5nJs3c15aV9A@mail.gmail.com>
Date: Sat, 30 Mar 2013 10:43:27 -0700
Message-ID: <CAL0qLwafA-jUuGO8zuZVbXzOdRa2wbWNQNiZtem8JJL63DrSrQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary="f46d04462e66e0695304d927ec0e"
Cc: IETF Apps Discuss <apps-discuss@ietf.org>, The IESG <iesg@ietf.org>, draft-saintandre-urn-example.all@tools.ietf.org
Subject: Re: [apps-discuss] AppsDir review of draft-saintandre-urn-example
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: Sat, 30 Mar 2013 17:43:29 -0000

I thought it could be useful to show an example namespace that isn't
strings, or that this is done in more than just the domain namespace.  It's
not mandatory; I did say "might".


On Sat, Mar 30, 2013 at 8:20 AM, Barry Leiba <barryleiba@computer.org>wrote:

> > Would it be
> > appropriate to add a sentence about that? For example, under Community
> > Considerations:
> >
> >   Naturally, authorities for particular namespaces (say, the 'xmpp'
> > NID) might want
> >   to define their own sub-spaces for examples (say,
> > urn:xmpp:example:*); however,
> >   such policies are outside the scope of this document.
>
> I'll stick that in as an RFC Editor note now.
>
> >> In Section 1, you might also make reference to the RFC that
> >> reserves some of the IP address space for examples.  It might be
> >> RFC2606 or some other; apologies for not digging up the reference
> >> myself, but I'm sending this from a place with no net access.
> >
> > Sure, that would be RFC 5737.
>
> Why?  It already says this:
>
>    Therefore this document registers
>    a formal namespace identifier of "example", similar to "example.com"
>    and other domain names [RFC2606].
>
> What's the reason for *also* mentioning 5737?  The point is already
> made, isn't it?
>
> Barry
>