Re: [netext] Adopt I-D draft-valmikam-eap-attributes-wifi-epc-integration as WG document?

[Rajeev Koodli <[e-mail]>]

Hi,


On 4/26/12 8:30 AM, "jouni korhonen" <[e-mail]> wrote:

>> 
>> I believe since the EAP attributes registry is the same, the same attributes
>> should also be applicable to EAP-SIM/AKA/AKA'.
> 
> The registry is the same, sure. What I mean, is that RFC5448 also needs
> to be reference since it is specifically mentioned in the draft. Just
> nitpicking..
> 

No problem, will reference RFC5448.


>> 
>> I think the attribute definition should be PS, no?
> 
> No.. furthermore, the IANA registry for EAP-SIM/AKA/AKA' attributes
> is specification required, which means any publicly available document
> fulfills the requirement for a specification. Even a vendor product
> spec would suffice. Personally, I rather have an RFC than something else..
> 

Agree we need an RFC to capture this so that PMIP6 can benefit in trusted
WiFi deployments. 

-Rajeev


>>> 
>>> o Should the draft state it updates RFC5448?
>>> 
>> 
>> I do not believe it needs to. I will consult Jari on this.
> 
> Ack.
> 
> - JOuni
> 
> 
>> 
>> -Rajeev
>> 
>> 
>> 
>>> - Jouni
>>> 
>>> 
>>> 
>>> On Apr 20, 2012, at 10:20 PM, <[e-mail]>
>>> <[e-mail]> wrote:
>>> 
>>>> 
>>>> Hello,
>>>> 
>>>> I have not heard any negative views on adopting this I-D.
>>>> I do believe that this I-D provides a good solution to the problem of
>>>> indicating APN choice (in 3GPP networks) or handover indication (general
>>>> applicability) to the MAG via EAP signaling.
>>>> 
>>>> Hence it makes sense to adopt this I-D as a WG document and progress it as
>>>> a Proposed Standard.
>>>> 
>>>> I believe APN selection and Handover indication attributes within EAP
>>>> messages are useful. I am not yet convinced about the multiple APN
>>>> connectivity attribute. Hence I would recommend publishing this I-D as a
>>>> WG doc with the scope limited to these two attributes.
>>>> 
>>>> I-D Authors, please go ahead and publish the I-D as a Netext WG doc.
>>>> 
>>>> 
>>>> -Raj
>>>> 
>>>> <Please note that I will be acting as the sole responsible chair w.r.t
>>>> this I-D> 
>>>> 
>>>> On 4/2/12 3:15 PM, "Patil Basavaraj (Nokia-CIC/Dallas)"
>>>> <[e-mail]> wrote:
>>>> 
>>>>> 
>>>>> Hello,
>>>>> 
>>>>> At IETF83 the WG discussed the I-D :
>>>>> draft-valmikam-eap-attributes-wifi-epc-integration (EAP Attributes
>>>>> for WiFi - EPC Integration)
>>>>> 
>>>>> This I-D proposes the use of EAP attributes as a means of signaling to
>>>>> the MAG by an MN the parameters such as:
>>>>> 1. Choice of APN
>>>>> 2. Handover indication
>>>>> 3. Multiple APN connectivity
>>>>> 
>>>>> These attributes are relevant in the context of an MN connecting via a
>>>>> WiFi network to the 3GPP evolved packet core (EPC).
>>>>> 
>>>>> The discussion in the WG favored using EAP attributes for parameters
>>>>> (1) and (2) above. The multiple APN connectivity problem is harder to
>>>>> solve. 
>>>>> 
>>>>> Question to the WG members:
>>>>> Should we adopt I-D draft-valmikam-eap-attributes-wifi-epc-integration
>>>>> as a Netext WG document with the intent of standardizing the following
>>>>> two attributes only : (1) Choice of APN and (2) Handover indication, to be
>>>>> carried in EAP signaling at the time of network access authentication?
>>>>> 
>>>>> Please respond to the ML (or to me privately) if you favor the adoption
>>>>> of this I-D or are opposed to it.
>>>>> 
>>>>> Adopt I-D: draft-valmikam-eap-attributes-wifi-epc-integration:
>>>>> 
>>>>> Yes [  ]
>>>>> 
>>>>> No  [  ]
>>>>> 
>>>>> -Basavaraj
>>>>> 
>>>>> ----------------------------------------------------
>>>>> 
>>>>> Abstract
>>>>> 
>>>>> With WiFi beginning to establishing itself as a trusted access
>>>>> network for service providers, it has become important to provide
>>>>> functions commonly available in 3G and 4G networks in WiFi access
>>>>> networks.  Such functions include Access Point Name (APN) Selection,
>>>>> multiple Packet Data Network (PDN) connections and seamless mobility
>>>>> between WiFi and 3G/4G networks.
>>>>> 
>>>>> EAP/AKA (and EAP/AKA') is standardized by 3GPP as the access
>>>>> authentication protocol for trusted access networks.  This IETF
>>>>> specification is required for mobile devices to access the 3GPP
>>>>> Evolved Packet Core (EPC) networks.  This document defines a few new
>>>>> EAP attributes and procedures to provide the above-mentioned
>>>>> functions in trusted WiFi access networks.
>>>>> 
>>>>> 
>>>> 
>>>> _______________________________________________
>>>> netext mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/netext
>>> 
>>> _______________________________________________
>>> netext mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/netext
>> 
>