IETF Logo Mail Archive

Re: [DMM] regarding the re-chartering..

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Tue, 09 September 2014 18:09 UTC

Return-Path: <sgundave@cisco.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E01A61A0659 for <dmm@ietfa.amsl.com>; Tue, 9 Sep 2014 11:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.153
X-Spam-Level:
X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 elL8FUBhPGlw for <dmm@ietfa.amsl.com>; Tue, 9 Sep 2014 11:09:48 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CE7F1A0489 for <dmm@ietf.org>; Tue, 9 Sep 2014 11:09:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1193; q=dns/txt; s=iport; t=1410286188; x=1411495788; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=MGyta18CckrjpBUB8YVB4zscWh5W5kVuwNb3VKyaE6E=; b=L7XFS4KWjhfl0EhyyDWQmY2aq2yM2ZfMRKT51o/fg5beZ6GJUeFnPEB+ inh4TGsn+Nby1Z9ve7WNarPq4xPwdpqQq93XbjgEsTMB3+CQCJT4WhHSd P7s8gCGw7UhKXEo4KjHik6D2++u1O+zA8xRLYEkJw/NRF4FqUxflZYIan I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiYFAJVBD1StJA2B/2dsb2JhbABZgw1TVwTKKIdKAYENFniEAwEBAQMBfg0BCBhgJQIEARIJiDEIDb0eARePVIRMBZFBizKVLoNhbAGBR4EHAQEB
X-IronPort-AV: E=Sophos;i="5.04,492,1406592000"; d="scan'208";a="353852403"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-8.cisco.com with ESMTP; 09 Sep 2014 18:09:47 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s89I9lMp025215 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Sep 2014 18:09:47 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.21]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Tue, 9 Sep 2014 13:09:47 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, "pierrick.seite@orange.com" <pierrick.seite@orange.com>, Charlie Perkins <charles.perkins@earthlink.net>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] regarding the re-chartering..
Thread-Index: AQHPzFk9FTJi/s504kOP81QcxzozOA==
Date: Tue, 09 Sep 2014 18:09:46 +0000
Message-ID: <D0348F3E.16271E%sgundave@cisco.com>
In-Reply-To: <540F3B69.7030109@ericsson.com>
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.217]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <A9E093A2D7D5D84AB26817029C71AF08@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/aUSMff_o0MFVsMIDqZwdHhBr0Co
Subject: Re: [DMM] regarding the re-chartering..
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 18:09:50 -0000

Hi Suresh,

Thanks. That makes sense. Now, I remember that spec/update.

The option name conflict and my search not finding 4283 references threw
me off. Thanks.


> No comments on that one :-)


:)


Regards
Sri




On 9/9/14 10:39 AM, "Suresh Krishnan" <suresh.krishnan@ericsson.com> wrote:

>Hi Sri,
>
>On 09/09/2014 10:11 AM, Sri Gundavelli (sgundave) wrote:
>> This is bit strange. Some thing changed in the IANA Mobile Node
>> Identifier pages.  I assumed the MN Id was defined in RFC4283. How come
>> I see a definition in 5271 as well.
>>
>>
>> Confused. Jouni / Brian ­ Any ideas ? Unless, I've been smoking Š
>
>No comments on that one :-). There are indeed two definitions of the
>MNID types.
>
>The one you originally saw is for the mobility option and is available
>in the mobility parameters registry
>
>http://www.iana.org/assignments/mobility-parameters/mobility-parameters.xh
>tml#mobility-parameters-5
>
>The second one you saw is for the *ND option* to carry MNID from the
>ICMPv6 parameters registry
>
>http://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#
>icmpv6-parameters-5
>
>Thanks
>Suresh
>

v2.23.0 | Report a Bug | By Email