RE: New draft submission - Chargeable User Identity

[<john.loughney@nokia.com>]

Hi all,

Just to follow-on to David. This is what is defined in the Diameter CCA,
and is used by 3GPP for charging.  If there are additional values that
would be useful to add, it would be consistent with the Diameter
CC application to add more.

If we could align the proposed draft with the Diameter CC app, that
would be great.

thanks,
John

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org
> [mailto:owner-radiusext@ops.ietf.org]On Behalf Of ext David Mariblanca
> (ML/EEM)
> Sent: 13 September, 2004 12:16
> To: 'Adrangi, Farid'; Bernard Aboba
> Cc: Nelson, David; Avi Lior; jouni.korhonen@teliasonera.com;
> radiusext@ops.ietf.org; sami.ala-luukko@teliasonera.com
> Subject: RE: New draft submission - Chargeable User Identity
> 
> 
> 
> Hi Farid and others,
> for these purposes, in 3GPP it's used the Subscription-Id AVP 
> from the Diameter Credit Control application. It is a grouped 
> AVP with these values:
> 
>    END_USER_E164                   0  
>      The identifier is in international E.164 format (e.g. MSISDN), 
>      according to the ITU-T E.164 numbering plan as defined in [E164] 
>      and [CE164]. 
>                 
>    END_USER_IMSI                   1  
>        The identifier is in international IMSI format, 
> according to the 
>      ITU-T E.212 numbering plan as defined in [E121] and [CE121].  
>              
>    END_USER_SIP_URI                2  
>      The identifier is in the form of a SIP URI as defined in [SIP].  
>                          
>    END_USER_NAI                    3  
>      The identifier is in the form of a Network Access Identifier as 
>      defined in [NAI].  
>              
>    END_USER_PRIVATE                4   
>      The Identifier is a credit-control server private identifier. 
> 
> If an attribute for a similar purpose is to be created for 
> RADIUS, shouldn't it be a mapping from this one ?
> 
> BR,
> David.
> 
> -----Original Message-----
> From: owner-radiusext@ops.ietf.org
> [mailto:owner-radiusext@ops.ietf.org]On Behalf Of Adrangi, Farid
> Sent: viernes, 10 de septiembre de 2004 19:02
> To: Bernard Aboba
> Cc: Nelson, David; Avi Lior; jouni.korhonen@teliasonera.com;
> radiusext@ops.ietf.org; sami.ala-luukko@teliasonera.com
> Subject: RE: New draft submission - Chargeable User Identity
> 
> 
> Yes, that is the intent.  The VSA uses the same string format as
> described in the IETF draft, and it is temporary until we get 
> a standard
> attribute from IETF.  Several GSMA vendors have already 
> implemented and
> tested the VSA for EAP-SIM trial - and they are ready to 
> replace it with
> the IETF standard attribute for the deployment.  So, getting the
> standard attribute from IETF sometime this year would be 
> great!  BTW, as
> you already know, GSAM has sent an LS on this to IETF.  
> 
> I also copied Sami Ala-luukko on this thread as well.
> 
> BR,
> Farid
> 
> 
> > -----Original Message-----
> > From: Bernard Aboba [mailto:aboba@internaut.com] 
> > Sent: Friday, September 10, 2004 9:43 AM
> > To: Adrangi, Farid
> > Cc: Nelson, David; Avi Lior; jouni.korhonen@teliasonera.com; 
> > radiusext@ops.ietf.org
> > Subject: Re: New draft submission - Chargeable User Identity
> > 
> > 
> > BTW, I noticed that the GSMA roaming spec includes VSAs for 
> chargeable
> > userID as well as location.  Is the GSMA prepared to adopt an IETF
> > standard attribute spec for chargeable userID instead, 
> assuming it is
> > completed within their time frame?  What is that time frame?
> > 
> > 
> > On Fri, 10 Sep 2004, Adrangi, Farid wrote:
> > 
> > > Hi,
> > > I would like to submit 00 version of a draft to RADEXT WG.  
> > Here is the
> > > url to the draft:
> > >
> > > 
> > http://mng.ctgisp.com/IETF/RADIUSEXT/draft-adrangi-radius-char
> geable-user-id-00.txt
> >
> > I also attached a copy to this mail.
> >
> > BR,
> > Farid
> >
> >
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
> 

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>