Re: [netext] Fwd: AD Evaluation : draft-ietf-netext-update-notifications

Brian Haberman <brian@innovationslab.net> Thu, 15 August 2013 13:11 UTC

Return-Path: <brian@innovationslab.net>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 807F821E8087 for <netext@ietfa.amsl.com>; Thu, 15 Aug 2013 06:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 9+7emQ++tTOa for <netext@ietfa.amsl.com>; Thu, 15 Aug 2013 06:11:22 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 541D021E811F for <netext@ietf.org>; Thu, 15 Aug 2013 06:11:22 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 295C6880FA; Thu, 15 Aug 2013 06:11:22 -0700 (PDT)
Received: from 102526207.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id D5CA6130003; Thu, 15 Aug 2013 06:11:21 -0700 (PDT)
Message-ID: <520CD378.8070205@innovationslab.net>
Date: Thu, 15 Aug 2013 09:11:20 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
References: <24C0F3E22276D9438D6F366EB89FAEA8103FDA1B@xmb-aln-x03.cisco.com>
In-Reply-To: <24C0F3E22276D9438D6F366EB89FAEA8103FDA1B@xmb-aln-x03.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "netext@ietf.org" <netext@ietf.org>
Subject: Re: [netext] Fwd: AD Evaluation : draft-ietf-netext-update-notifications
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 13:11:27 -0000

Hi Sri,

On 8/15/13 2:09 AM, Sri Gundavelli (sgundave) wrote:
>
> 3. - I would like to see some more guidance given to IANA on where the new
> registries should be placed in their protocol hierarchy.
>
> On cross checking, this seemed OK. But, may be we mis-understood the
> comment.
>

I just want the document to be explicit that IANA actions 3 and 4 will 
create registries under the "Mobile IPv6 Parameters" registry 
(https://www.iana.org/assignments/mobility-parameters/mobility-parameters.xhtml).

Regards,
Brian