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

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Wed, 10 September 2014 15:11 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 75C131A03F5 for <dmm@ietfa.amsl.com>; Wed, 10 Sep 2014 08:11:54 -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 wFQ6q3DkMfK3 for <dmm@ietfa.amsl.com>; Wed, 10 Sep 2014 08:11:52 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A366D1A8725 for <dmm@ietf.org>; Wed, 10 Sep 2014 08:11:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4011; q=dns/txt; s=iport; t=1410361912; x=1411571512; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Y2jN6Y2XLJFhLRLHtLyImmDgYPPYmFIhrxbvrhc9rjo=; b=Zbpa85C+My+Whp61rDwS6qQn3EUy3abO6AH+evZhtwnb9zCJCnCuxvUT f/zbISCFt2lMgmf1SMt2Yjwpx1aJXEjePm9+n/EjO4c9+YUKtSnJX9jdX r+/nOYezCQnm9rUm/kbFQwSv2uqyurqbPGJVz7vZYpWex6IwMVlq7IVJJ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFAJZpEFStJA2D/2dsb2JhbABZgw1TVwTKNAqHTAGBEBZ4hAMBAQEEAQEBawsMBgEIEQQBASguCxQJCAIEAQ0FCYglAxENvioBF40gggIrBwaERgWGGoRghkeLMpUug2FsAYFHgQcBAQE
X-IronPort-AV: E=Sophos;i="5.04,499,1406592000"; d="scan'208";a="354111209"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-5.cisco.com with ESMTP; 10 Sep 2014 15:11:52 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s8AFBp7N014000 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 10 Sep 2014 15:11:51 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.21]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Wed, 10 Sep 2014 10:11:51 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Marco Liebsch <Marco.Liebsch@neclab.eu>, Charlie Perkins <charles.perkins@earthlink.net>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] regarding the re-chartering..
Thread-Index: AQHPzQmMFTJi/s504kOP81QcxzozOA==
Date: Wed, 10 Sep 2014 15:11:50 +0000
Message-ID: <D035B45D.162A1A%sgundave@cisco.com>
In-Reply-To: <69756203DDDDE64E987BC4F70B71A26D91A58AC3@DAPHNIS.office.hd>
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="iso-8859-1"
Content-ID: <323F35006034C84DB6FE99D14D76D906@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/35nGFVzbCaLbH4jv4LNNT7FfBys
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: Wed, 10 Sep 2014 15:11:54 -0000

Yes. Currently, the MNID is if the nai format and is overloaded. The MNID
in 3GPP specs is the IMSI-NAI (IMSI@REALM), its based on the IMSI. Ex:
"<IMSI>@epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org²

We also have MAC48@REALM;

We also have approaches to transform MAC to Pseudo IMSI, and then carry
IMSI-NAI as the MN-ID.


So, we need unique sub-types for each of the types/sources.

MN-Id based on IMSI, MSISDN, IMEI, MAC ..

Also, do we need to distinguish between IMSI and IMSI-NAI ?

Sri



On 9/10/14 6:29 AM, "Marco Liebsch" <Marco.Liebsch@neclab.eu> wrote:

>It seems the MNID is somehow overloaded to carry both, node-specific IDs,
>e.g. MAC, as well as subscriber IDs, which is the IMSI.
>There may be value in adding the IMEI to the list of possible types of
>node-specific IDs.
>
>marco
>
>>-----Original Message-----
>>From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Sri Gundavelli
>>(sgundave)
>>Sent: Dienstag, 9. September 2014 23:30
>>To: Sri Gundavelli (sgundave); Charlie Perkins; dmm@ietf.org
>>Cc: Vijay Devarapalli
>>Subject: Re: [DMM] regarding the re-chartering..
>>
>>Two more comments.
>>
>>
>>
>>4.) I'd also use sub-type value of (2) for IMSI. Just to align with the
>>sub-types
>>defined for MN Id defined for ICMP. I suspect there are some
>>implementations
>>already using sub-type (2). Please see the other thread.
>>
>>
>>5.) For each of the sub-types, we need text including examples and some
>>explanation on how they are used.
>>
>>
>>Sri
>>
>>
>>
>>On 9/9/14 2:20 PM, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
>>wrote:
>>
>>>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.
>>>
>>>_______________________________________________
>>>dmm mailing list
>>>dmm@ietf.org
>>>https://www.ietf.org/mailman/listinfo/dmm
>>
>>_______________________________________________
>>dmm mailing list
>>dmm@ietf.org
>>https://www.ietf.org/mailman/listinfo/dmm