IETF Logo Mail Archive

Re: [Ianaplan] making ARPA explicit (Re: draft-ietf-ianaplan-icg-response-02 working group lastcall)

Andrei Robachevsky <andrei.robachevsky@gmail.com> Sun, 09 November 2014 07:04 UTC

Return-Path: <andrei.robachevsky@gmail.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 404391A19EF for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 23:04:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CqABDevSMGdT for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 23:04:44 -0800 (PST)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72A0D1A19EB for <ianaplan@ietf.org>; Sat, 8 Nov 2014 23:04:44 -0800 (PST)
Received: by mail-pd0-f180.google.com with SMTP id ft15so5786364pdb.25 for <ianaplan@ietf.org>; Sat, 08 Nov 2014 23:04:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=DFDuyYxxYXLjlk63T1a6F43ASzjEg84iV9id3vBBIuc=; b=TiEnKkUvJoZoALR9517VpygxhhzBnR9cdUQTSKwZGoisqsjSYeviVM9fRyRM7jWWD3 pNmEwA7AX8a2RegDgrbGVfm56hDa74F293gEJlvmURFXkbLzPAjiFZqzRBUvxNPfb3mM aSz678Jozp14eP/a1KKApTXvSX66JMa46Jw8MOGgnrvSy3mqxhb7RYw1hLxZh+SdlXTm smFcGZIrSGBCwH2tMbB/E/Muzbs9Fq+tPemEL2xJQwcTqu2B/2/oL93ZpjypKKBItib8 zl4ukOEhbFBO0/JsJkkpZtTYDlxs30tL5vMjPK1Q1E74f8LZ599OfbjQ/fq0DuP3LY/X qHtg==
X-Received: by 10.66.184.47 with SMTP id er15mr23464087pac.5.1415516683643; Sat, 08 Nov 2014 23:04:43 -0800 (PST)
Received: from dhcp-8f8f.meeting.ietf.org (dhcp-8f8f.meeting.ietf.org. [31.133.143.143]) by mx.google.com with ESMTPSA id gm11sm13052586pbd.63.2014.11.08.23.04.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Nov 2014 23:04:42 -0800 (PST)
Message-ID: <545F1206.6020207@gmail.com>
Date: Sun, 09 Nov 2014 08:04:38 +0100
From: Andrei Robachevsky <andrei.robachevsky@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: JFC Morfin <jefsey@jefsey.com>, Olaf Kolkman <kolkman@isoc.org>, "ianaplan@ietf.org" <ianaplan@ietf.org>
References: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca> <830AC04C-6020-4E42-AAC2-A0D3AF5E3B02@isoc.org> <545E88E1.50609@gmail.com> <545ec489.c59c420a.72cd.3864SMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <545ec489.c59c420a.72cd.3864SMTPIN_ADDED_MISSING@mx.google.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="oWc9UNFTf5hKV6hWAqAUnKcfOVOaAWxSJ"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/xDZmhDq5ObFUzhWfi-u2B_jVPpg
Subject: Re: [Ianaplan] making ARPA explicit (Re: draft-ietf-ianaplan-icg-response-02 working group lastcall)
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Nov 2014 07:04:46 -0000

JFC Morfin wrote on 09/11/14 01:31:
> At 22:19 08/11/2014, Andrei Robachevsky wrote:
>> My question here, when we say .ARPA domain, do we mean the whole
>> sub-tree? Do we need to mention that here explicitly?
> 
> Why do you want to change anything? All this is already agreed and
> signed by ARPA, NTIA, ICANN and IAB.

We are not saying anything new in this section, neither do we change
things. It is just documenting what "protocol parameters registries"
mean. A reference to BCP52 would be appropriate, IMO (it is in the draft
already, but in a slightly different context).

Andrei

v2.23.0 | Report a Bug | By Email