Re: [wellknown-uri-review] Request for well-known URI: ni

Eran Hammer <eran@hueniverse.com> Wed, 09 May 2012 07:33 UTC

Return-Path: <eran@hueniverse.com>
X-Original-To: wellknown-uri-review@ietfa.amsl.com
Delivered-To: wellknown-uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85CE321F85A4 for <wellknown-uri-review@ietfa.amsl.com>; Wed, 9 May 2012 00:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level:
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599]
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 wi+Uhjk+TB3C for <wellknown-uri-review@ietfa.amsl.com>; Wed, 9 May 2012 00:33:43 -0700 (PDT)
Received: from p3plex2out04.prod.phx3.secureserver.net (p3plex2out04.prod.phx3.secureserver.net [184.168.131.18]) by ietfa.amsl.com (Postfix) with ESMTP id 0009921F8597 for <wellknown-uri-review@ietf.org>; Wed, 9 May 2012 00:33:39 -0700 (PDT)
Received: from P3PWEX2HT002.ex2.secureserver.net ([184.168.131.10]) by p3plex2out04.prod.phx3.secureserver.net with bizsmtp id 7jZf1j0010Dcg9U01jZf4j; Wed, 09 May 2012 00:33:39 -0700
Received: from P3PWEX2MB008.ex2.secureserver.net ([169.254.8.88]) by P3PWEX2HT002.ex2.secureserver.net ([184.168.131.10]) with mapi id 14.02.0247.003; Wed, 9 May 2012 00:33:39 -0700
From: Eran Hammer <eran@hueniverse.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "wellknown-uri-review@ietf.org" <wellknown-uri-review@ietf.org>
Thread-Topic: [wellknown-uri-review] Request for well-known URI: ni
Thread-Index: AQHNK6BPvPj546IKd06LIsQpg2SuXpbBEuww
Date: Wed, 09 May 2012 07:33:39 +0000
Message-ID: <0CBAEB56DDB3A140BA8E8C124C04ECA201024B3B@P3PWEX2MB008.ex2.secureserver.net>
References: <4FA69E55.5020501@cs.tcd.ie>
In-Reply-To: <4FA69E55.5020501@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.74.213.174]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [wellknown-uri-review] Request for well-known URI: ni
X-BeenThere: wellknown-uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Well-Known URI review list <wellknown-uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wellknown-uri-review>
List-Post: <mailto:wellknown-uri-review@ietf.org>
List-Help: <mailto:wellknown-uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 07:33:43 -0000

I have reviewed the request to register the 'ni' well-known URI prefix (in my capacity as designated expert for the Well-Known URI registry).  I have found no issues with the request and will inform IANA upon IESG approval of the document.

EH



> -----Original Message-----
> From: wellknown-uri-review-bounces@ietf.org [mailto:wellknown-uri-
> review-bounces@ietf.org] On Behalf Of Stephen Farrell
> Sent: Sunday, May 06, 2012 8:53 AM
> To: wellknown-uri-review@ietf.org
> Subject: [wellknown-uri-review] Request for well-known URI: ni
> 
> 
> Hi,
> 
> Please see the request, in the formally specified format below. The draft [1]
> now includes the 30x requirement at a SHOULD level.
> 
> Thanks,
> Stephen.
> 
>    URI suffix: ni
> 
>    Change controller: IETF
> 
>    Specification document(s): draft-farrell-decade-06 [1]
> 
>    Related information: None
> 
> 
> [1] http://tools.ietf.org/html/draft-farrell-decade-ni
> _______________________________________________
> wellknown-uri-review mailing list
> wellknown-uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/wellknown-uri-review