IETF Logo Mail Archive

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

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Tue, 09 September 2014 21:20 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 CADED1A8549 for <dmm@ietfa.amsl.com>; Tue, 9 Sep 2014 14:20:46 -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 w_zTbgOSVdE1 for <dmm@ietfa.amsl.com>; Tue, 9 Sep 2014 14:20:41 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3FE91A0380 for <dmm@ietf.org>; Tue, 9 Sep 2014 14:20:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1919; q=dns/txt; s=iport; t=1410297639; x=1411507239; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=XyMVBudL04nktoVRqBzYuJsxH6gy3WwKCSZaAreNiK0=; b=GN5IvLcHfc1/KN7YjV4sQA4oBwUnqVL2c82caf+8vzycFLQHlP1k8pnL EPqMbgkjZUzA7tw7KSF2VFJ/IAcHeCNdGVfbq7Kn8gzqRVOWu5nKO3T0N LlUV9faa1tKDgQ/LyNSae1r3/feTLfuAPz/PhBy+WAzcXZC8R7L0oy9Jo 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiYFAFduD1StJV2Y/2dsb2JhbABZgw1TVwTKJodMAYENFniEBAIEOj8SAQgOKEIlAgQBDQUJiCUDEQ29LQEXjSCCLQeETAWGGosnizKVLoNhbAGBR4EHAQEB
X-IronPort-AV: E=Sophos;i="5.04,493,1406592000"; d="scan'208";a="353966701"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP; 09 Sep 2014 21:20:39 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s89LKcem018054 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Sep 2014 21:20:38 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.21]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0195.001; Tue, 9 Sep 2014 16:20:37 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Charlie Perkins <charles.perkins@earthlink.net>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] regarding the re-chartering..
Thread-Index: AQHPzHPmFTJi/s504kOP81QcxzozOA==
Date: Tue, 09 Sep 2014 21:20:37 +0000
Message-ID: <D034B8C3.1627CC%sgundave@cisco.com>
In-Reply-To: <540F62DA.906@earthlink.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.217]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E2D526A96488EC4785F6215B54DA6E1E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/7KPQoQ_9IsWZ_ePivuoh6OIRUCQ
Cc: Vijay Devarapalli <dvijay@rocketmail.com>
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 21:20:47 -0000

Hi Charlie,

This is good. Thanks.


1.) If EUI-48 and EUI-64 addresses are derived of a 48-bit IEEE 802.2
address, why do we need to two sub-types ? Why not have just one sub-type
for mac based identifiers ?

2.) Sub type value (1) is currently used. Its currently overloaded for
IMSI-NAI (3GPP specs) and generic NAI based identifiers. Given the
definition of new sub-types, we need some text explaining the motivation

3.) Proposed Sub-type value of (2) for IPv6 address. What exactly is this
? Are these CGA-based IPv6 addresses ?




                     New Mobile Node Identifier Types

               +-----------------+------------------------+
               | Identifier Type | Identifier Type Number |
               +-----------------+------------------------+
               | IPv6 Address    | 2                      |
               |                 |                        |
               | IMSI            | 3                      |
               |                 |                        |
               | P-TMSI          | 4                      |
               |                 |                        |
               | EUI-48 address  | 5                      |
               |                 |                        |
               | EUI-64 address  | 6                      |
               |                 |                        |
               | GUTI            | 7                      |
               +-----------------+------------------------+







Regards
Sri
PS: Good to see Vijay back


On 9/9/14 1:28 PM, "Charlie Perkins" <charles.perkins@earthlink.net> wrote:

>
>Hello folks,
>
>Here's the last Internet Draft that we did, long ago expired:
>http://www.ietf.org/archive/id/draft-perkins-mext-4283mnids-01.txt
>
>I'll resubmit it with a few updates as a personal draft to dmm.
>
>Regards,
>Charlie P.

v2.23.0 | Report a Bug | By Email