[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]

To: "charliep at computer.org" <charliep at computer.org>
Subject: Re: [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]
From: "Laganier, Julien" <julienl at qualcomm.com>
Date: Tue, 20 Oct 2009 09:45:42 -0700
Accept-language: en-US
Acceptlanguage: en-US
Cc: mext <mext at ietf.org>
Delivered-to: mext at core3.amsl.com
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl at qualcomm.com; q=dns/txt; s=qcdkim; t=1256057147; x=1287593147; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Laganier,=20Julien"=20<julienl at qualcomm.com> |To:=20"charliep at computer.org"=20<charliep at computer.org> |CC:=20mext=20<mext at ietf.org>|Date:=20Tue,=2020=20Oct=202 009=2009:45:42=20-0700|Subject:=20RE:=20[MEXT]=20[Fwd:=20 New=20Version=09Notification=09for=0D=0A=09draft-perkins- mext-4283mnids-00]|Thread-Topic:=20[MEXT]=20[Fwd:=20New =20Version=09Notification=09for=0D=0A=09draft-perkins-mex t-4283mnids-00]|Thread-Index:=20AcpRo0m1fOv30TRxRTeyL3dv+ REZLQAAHNag|Message-ID:=20<BF345F63074F8040B58C00A186FCA5 7F1C648C9FA9 at NALASEXMB04.na.qualcomm.com>|References:=20< 4ADCCCE3.1010506 at computer.org>=0D=0A=09<BF345F63074F8040B 58C00A186FCA57F1C648C9F9E at NALASEXMB04.na.qualcomm.com>=0D =0A=20<4ADDE6AB.9000301 at computer.org>|In-Reply-To:=20<4AD DE6AB.9000301 at computer.org>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5777"=3B=20a=3D"25673518"; bh=ADMwG8z94jBeEuipg0N+Sx+06cXXiDw32mueoPj8qTM=; b=wx04plgSYPX9ziMNFN4avqhJJYiHboMwP1WY9YBaka3XtL7nWlSAbpIw flogXb7eR+NaG+XKH5E7xhIfwZyAqIm9rPEUZe10SAM34FbazJgggsSxR 8/MaaBtQmro9EJ2RvXqTiv2ZAC4XQWN4nE5aOWFPwdJROK+6jM44U6UFz c=;
In-reply-to: <4ADDE6AB.9000301 at computer.org>
List-archive: <http://www.ietf.org/mail-archive/web/mext>
List-help: <mailto:mext-request@ietf.org?subject=help>
List-id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-post: <mailto:mext@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
References: <4ADCCCE3.1010506 at computer.org> <BF345F63074F8040B58C00A186FCA57F1C648C9F9E at NALASEXMB04.na.qualcomm.com> <4ADDE6AB.9000301 at computer.org>
Thread-index: AcpRo0m1fOv30TRxRTeyL3dv+REZLQAAHNag
Thread-topic: [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]

The IANA considerations of RFC 4283 states:

   In addition, IANA has created a new namespace for the subtype field
   of the Mobile Node Identifier option.  The currently allocated values
   are as follows:

   NAI (defined in [RFC4282]).

   New values for this namespace can be allocated using Standards Action
   [RFC2434].
 
So I do not see what restriction made encoding the IMSI as an NAI the only choice available. If 3GPP had wanted to encode an MNID subtype to encode the IMSI, they could have get it allocated via the appropriate channel.
 
As to the lack of pressure on the MNID subtype registry, it is not IMHO a reason to reserve values before a clear requirement has been expressed, which doesn't seem to be the case yet. Until then...

--julien

Charles E. Perkins
> 
> Hello Julien,
> 
> Your comment actually applies to every type of
> identifier.  Even MAC addresses could be written
> as NAIs:
> 	AB_CD_EF_00_11_22 at ieeeMACaddresses.org
> Or:
> 	MAC_ADDRESS_AB_CD_EF_00_11_22 at HomeAgent.org
> depending on preferneces for AAA administration.
> 
> I'd give 5 to 1 odds that the use of NAI as you
> mentioned by 3GPP and others was predicated on
> the restriction that it was the only choice
> available.
>
> It seems to me that, going into the future, we
> can do better.  And there is absolutely no pressure
> evident today on the MNID type registry.
> 
> Nearer term, I think the availability of appropriate
> MNID types might be valuable for the work that is
> ongoing for an alternate security mechanism for
> MIPv6.
> 
> Regards,
> Charlie P.
> 
> 
> 
> Laganier, Julien wrote:
> > Hello Charlie,
> >
> > Two comments on this draft:
> >
> > I'm wondering how useful it is to reserve a MNID type to encode a
> 3GPP IMSI [1] given that EAP-AKA [RFC4187] and the 3GPP Numbering,
> addressing and identification specification [TS23.003] already define
> means of encoding the IMSI as an NAI.
> >
> > Also, w.r.t. P-TMSI and GUTI, 1) it's unclear to me whether these
> identifiers are going to be used to identify a MN with its HA or LMA,
> and 2) if it's going to be used, why not let 3GPP define in [TS23.003]
> their own mapping of P-TMSI, GUTI, or whatever identifier they're using,
> into a NAI?
> >
> > Best,
> >
> > --julien
> >
> > [RFC4187]  Extensible Authentication Protocol Method for 3rd
> Generation
> >            Authentication and Key Agreement (EAP-AKA)
> > [TS23.003] 3rd Generation Partnership Project, "3GPP Technical
> >            Specification 23.003: Technical Specification Group Core
> >            Network and Terminals; Numbering, addressing and
> identification"
> >
> > Charles E. Perkins wrote:
> >>
> >> Hello folks,
> >>
> >> This is a very simple draft, but could make a significant
> >> difference in ease of standardization.  Anyway it would
> >> avoid the need to shoehorn every possible type of identifier
> >> into a new substructure for the MN-NAI.
> >>
> >> Any comments will be appreciated.
> >>
> >> Regards,
> >> Charlie P.
> >>
> >>
> >>
> >> -------- Original Message --------
> >> Subject: New Version Notification for draft-perkins-mext-4283mnids-
> 00
> >> Date: Mon, 19 Oct 2009 13:20:49 -0700 (PDT)
> >> From: IETF I-D Submission Tool <idsubmission at ietf.org>
> >> To: charliep at computer.org
> >> CC: vijay at wichorus.com
> >>
> >>
> >> A new version of I-D, draft-perkins-mext-4283mnids-00.txt has been
> >> successfuly submitted by Charles Perkins and posted to the IETF
> >> repository.
> >>
> >> Filename:	 draft-perkins-mext-4283mnids
> >> Revision:	 00
> >> Title:		 MN Identifier Types for RFC 4283 Mobile Node
> >> Identifier Option
> >> Creation_date:	 2009-10-19
> >> WG ID:		 Independent Submission
> >> Number_of_pages: 8
> >>
> >> Abstract:
> >> Additional Identifier Types are proposed for use with the Mobile
> Node
> >> Identifier Option for MIPv6 (RFC 4283).
> >>
> >>
> >>
> >>
> >> The IETF Secretariat.
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> MEXT mailing list
> >> MEXT at ietf.org
> >> https://www.ietf.org/mailman/listinfo/mext
> > _______________________________________________
> > MEXT mailing list
> > MEXT at ietf.org
> > https://www.ietf.org/mailman/listinfo/mext
> >
> >
> 
> _______________________________________________
> MEXT mailing list
> MEXT at ietf.org
> https://www.ietf.org/mailman/listinfo/mext

Follow-Ups:
- Re: [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]
  - From: Charles E. Perkins

References:
- [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]
  - From: Charles E. Perkins
- Re: [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]
  - From: Laganier, Julien
- Re: [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]
  - From: Charles E. Perkins

Prev by Date: Re: [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]
Next by Date: Re: [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]
Previous by thread: Re: [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]
Next by thread: Re: [MEXT] [Fwd: New Version Notification for draft-perkins-mext-4283mnids-00]
Index(es):
- Date
- Thread