[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE : [RADIUS location attributes] support of a location identifier in location-information attribute
I precise that it would be not necessary to define the exact format of the information contained in the Location-Info field. By manual configuration, the sender will know how to fill this field and the receiver will know how to process the received information. I insist on the fact that such a mechanism would be useful between a NAS and a RADIUS server from the same administrative domain if the RADIUS client was not able to provide explicit location information, that is likely to be frequent ;)
> -----Message d'origine-----
> De : Tschofenig Hannes [mailto:firstname.lastname@example.org]
> Envoyé : lundi 18 avril 2005 12:22
> À : MORAND Lionel RD-CORE-ISS; email@example.com
> Cc : firstname.lastname@example.org
> Objet : AW: [RADIUS location attributes] support of a
> location identifier in location-information attribute
> hi lionel,
> i remember that you have proposed this feature already once.
> is someone else in favor of this approach?
> i don't want to add new functionality based the opinion of a
> few individuals only (particularly if the functionality is
> not really necessary).
> > -----Ursprüngliche Nachricht-----
> > Von: MORAND Lionel RD-CORE-ISS
> > [mailto:email@example.com]
> > Gesendet: Montag, 18. April 2005 10:34
> > An: Tschofenig Hannes; firstname.lastname@example.org
> > Cc: email@example.com
> > Betreff: [RADIUS location attributes] support of a location
> > identifier in location-information attribute
> > Hi Hannes,
> > The actuel design of the location-information attribute
> > allows to convey
> > location objects as defined by GEOPRIV, either civic or geospatial
> > location information.
> > I agree that this fulfil the GEOPRIV requirements but what
> about some
> > "location ID" that could be sent to the AAA server to
> > retrieve location
> > info? I mean that the location info attribute may convey
> > either explicit
> > ("self-explicit") location information or any identifier if
> there is a
> > mean for the receiver to extract explicit information from
> > this ID, such
> > as the CellID in GSM.
> > Moreover, it could be seen as a complement of the global design:
> > 1)if the NAS is not able to provide an explicit location,
> the NAS can
> > provide the local RADIUS server with the location ID (any identifier
> > related to the access network) in the location-information
> > 2)the local RADIUS server performs the mapping between
> identifier and
> > location;
> > 3)the local server inserts the extracted information in a new
> > location-information attribute in the Access-Request sent to
> > the remote
> > RADIUS server.
> > It is therefore proposed to allocate a new code value (2),
> defined for
> > location identifiers carried in location-information attributes.
> > Lionel
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.