[no subject]

["Adrangi, Farid" <farid.adrangi@intel.com>]

Thanks Bernrad.  As I recall the Liason that we sent from WFA to IETF
contained the following:

1) Access network location information 
      - covered by combined adrangi and jones draft soon to be submitted
to GeoPriv WG.  GeoPriv chairs are expecting this draft.
2) Access network Bandwidth parameters
      - covered by combined adrangi and black/congdon draft which is
currently being discussed on the mailing list.  Will submit a new
version by the end this month
3) billing class of Service
      - I believe "IP address type" attribute in the "lan attribute
extension" draft covers this.  At least, this was the case when we
discussed this in WFA sometime ago!
4) There are a couple of other security key related attributes which are
not covered by any drafts -- to best of my understanding.

BR,
Farid



      

> -----Original Message-----
> From: Bernard Aboba [mailto:aboba@internaut.com] 
> Sent: Monday, June 21, 2004 8:54 PM
> To: Adrangi, Farid
> Cc: radiusext@ops.ietf.org
> Subject: RE: RADEXT Agenda, Take One
> 
> 
> > I think we should add
> > 
> http://www.ietf.org/internet-drafts/draft-adrangi-radius-attri
> butes-exte
> > nsion-00.txt to the agenda as well.
> 
> Done.
> 
> > I believe WFA radius requirements
> > are captured in a different document (in Excel spreadsheet 
> format) --
> > and that document does not propose any format/syntax for these
> > attributes.
> 
> I wasn't sure whether the Excel spreadsheet was a public 
> document or not.
> In any case, the reference was put in as a placeholder.  We 
> have a liaison
> request from the WFA relating to those attributes, so I'm anticipating
> that a draft will be submitted defining them.
> 
> Or am I missing something?
> 

--
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/>