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

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Thu, 15 August 2013 14:30 UTC

Return-Path: <sgundave@cisco.com>
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 AF66311E8152 for <netext@ietfa.amsl.com>; Thu, 15 Aug 2013 07:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 ts62Akj4wlON for <netext@ietfa.amsl.com>; Thu, 15 Aug 2013 07:29:59 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id E7AEE21F9E34 for <netext@ietf.org>; Thu, 15 Aug 2013 07:29:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=769; q=dns/txt; s=iport; t=1376576996; x=1377786596; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=TFez49fJkWrXZIhDEMEUPkj7ZqN5Y6JTkfO7RbiwbhA=; b=QRVP4VINkWukavy+y3/qSC6yKiYkbxZihvc8ZUGCYN7x6Yt4ylgZ64mO EZAPl9w2ZEylvp+jT3iFPY6G1mWwybkZC17pG2cocKjKU7jfuNznC64ZA LnxHF/XEpWOo51AiW9iNdGy/VUMICsOalhPXR0Oxu7QNoqi79eobl4O+P g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AowFAD7lDFKtJV2b/2dsb2JhbABbgwY1UIJSvECBIRZ0giQBAQEEOj0CEgEIGAoUQiUCBA4FCIgIDLlwBJAfMQeDG3cDqTaDG4Iq
X-IronPort-AV: E=Sophos;i="4.89,885,1367971200"; d="scan'208";a="247503818"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-1.cisco.com with ESMTP; 15 Aug 2013 14:29:55 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r7FETt3Y022075 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 15 Aug 2013 14:29:55 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.31]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Thu, 15 Aug 2013 09:29:55 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Brian Haberman <brian@innovationslab.net>
Thread-Topic: [netext] Fwd: AD Evaluation : draft-ietf-netext-update-notifications
Thread-Index: AQHOmcPoM004WIq4m06Xy+Z7Qbs27Q==
Date: Thu, 15 Aug 2013 14:29:54 +0000
Message-ID: <24C0F3E22276D9438D6F366EB89FAEA8103FE03E@xmb-aln-x03.cisco.com>
In-Reply-To: <520CD378.8070205@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.32.246.210]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <95087A373B17ED43BC31EDCFAD2CB6E8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 14:30:08 -0000

Hi Brian,

Thanks for the clarification. That will make IANA related text complete.
We will make that change.

Regards
Sri


On 8/15/13 6:11 AM, "Brian Haberman" <brian@innovationslab.net> wrote:

>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
>