eap Mailing List: issue 375 (Was: Re: review of netsel-05)

[Jari Arkko (jari.arkko]

But latest PANA document (ietf-pana-pana) no longer
has ISP-Information or NAP-Information, so I think
further developments have changed the situation
again. Here's the edit:

Remove text:

   The PANA protocol [I-D.ietf-pana-pana] has a mechanism to advertise
   and select "ISPs" through the exchange of the ISP-Information AVP in
   its initial exchange.

Change text

   The use of other network identifiers
   than domain names is also possible, for instance the PANA protocol
   uses an a free form string and an SMI Network Management Private
   Enterprise Code [I-D.ietf-pana-pana], or Mobile Network Codes
   embedded in NAIs as specified in 3GPP.

=>

   The use of other network identifiers
   than domain names is also possible.

And remove the reference too.

Jari

Bari, Farooq kirjoitti:
> Regarding 375, I am attaching Ohba san's email on eap reflector from
> last year that requested to disregard his previous email. So this issue
> seems to be resolved.
>
>  
> Farooq Bari
>  
> farooq.bari [at] att.com
> +1 425 580 5526
>  
>  
>   

>   
>> -----Original Message-----
>> From: Bernard Aboba [mailto:bernard_aboba [at] hotmail.com] 
>> Sent: Wednesday, February 21, 2007 9:47 AM
>> To: eap [at] frascone.com
>> Subject: Re: [eap] review of netsel-05
>>
>> I have resolved issues 330, 331, 332, 334, 335 and 336 as 
>> fixed in NETSEL-05.  I am assuming that 333 will be resolved in -06.
>>
>> That still leaves Issues 374, 375, 376, 377, and 378 open.
>>
>> Can the submitters of those issues look over the document and 
>> post whether their concerns have been resolved?
>>
>> The document is available for inspection here:
>> http://www.ietf.org/internet-drafts/draft-ietf-eap-netsel-prob
>> lem-05.txt
>>
>>     
>>> Jari Arkko said:
>>>       
>>> First, there are some open issues in the issue tracker. I consider 
>>> issues 330-336 now mostly closed, based on the revisions in the new 
>>> drafts. Thanks. For issue 333 there is one small remaining 
>>>       
>> thing, noted 
>>     
>>> below.
>>>
>>> What is the situation with the other issues? They have been made for 
>>> previous revisions, have they been resolved in -05?
>>>
>>> I also re-read the document and noticed two small editorial issues, 
>>> also noted below.
>>>
>>> But otherwise I think the document is ready. Ship it!
>>>
>>> Parts remaining from issue 333:
>>>
>>>       
>>>>    Section 4 gives the conclusions
>>>>    and some suggestions on how to proceed for the rest.
>>>>         
>>> This should be: "Section 4 presents our conclusions."
>>>
>>> Editorial:
>>>
>>>       
>>>>    discussion of the limitations of certain classes of solution,
>>>>         
>>> s/solution/solutions/
>>>
>>>
>>>       
>>>> The solution ...
>>>>         
>>> Multiple occurrences of this. I think the draft should not 
>>>       
>> assume that 
>>     
>>> we have a single solution in this space.
>>> Therefore, we should typically write "Solutions should 
>>>       
>> satisfy ... " as 
>>     
>>> opposed to "The solution should satisfy ..."
>>>       
>> _________________________________________________________________
>> To unsubscribe or modify your subscription options, please visit:
>> http://lists.frascone.com/mailman/listinfo/eap
>>
>> Arhives: http://lists.frascone.com/pipermail/eap
>>
>>     
>> ------------------------------------------------------------------------
>>
>> _________________________________________________________________
>> To unsubscribe or modify your subscription options, please visit:
>> http://lists.frascone.com/mailman/listinfo/eap
>>
>> Arhives: http://lists.frascone.com/pipermail/eap