[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: Review of draft-ietf-geopriv-radius-lo-04.txt
> > A simple solution would be that a NAS that knows both the NAS and
> > user location always sends both (when sending location information).
> > (I don't think we need more fine-grained capability negotiation
> > for this.)
> I agree that this would work and also agree that capability
> negotiation is
> not needed. However, I thought that the idea was not to send
> any location
> data by default.
location is not sent by default.
the aspect is similar to the civic vs. geospatial discussion. you could
send both, if you have it. sometimes you just don't have civic and
geospatial location information (depending on the deployment).
> to unsubscribe send a message to email@example.com 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 firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.