RE : Issue 74: RFC 3576 behavior

["MORAND Lionel RD-CORE-ISS" <lionel.morand@francetelecom.com>]

Is there any "send-location" attribute defined in the current draft?

For me, there is nothing in the COA "instructing" the client to sed the location. I think that the COA procedure is a way to retrieve once again location information received in a previous Access-Request (e.g. to check if the previous location is still up-to-date). 

The COA here just means "send a new access-Request". If during the previous exchange the NAS has provided the location info, it is likely that the NAS will provide it once again. But there is no way to mandate it through the COA request.

Therefore, the following text:
   "The COA message may instruct the
   access network to generate an Authorize-Only Access-Request (Access-
   Request with Service-Type set to "Authorize-Only") in which case the
   NAS MUST include the location infromation in this Access-Request if 
   it included the location information is previous Access-Requests. "

Should be modified to remove the "MUST"



-----Message d'origine-----
De : owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] De la part de Bernard Aboba
Envoyé : mercredi 9 novembre 2005 23:45
À : radiusext@ops.ietf.org
Objet : Re: Issue 74: RFC 3576 behavior


I think there is still an issue here.

You need to be very clear about the meaning of the "Send-Location" attribute 
when put in various messages by the server.  For example, if sent in an 
Access-Challenge, does this mean "send location in the next Access-Request", 
  or does it mean "send location in every RADIUS Access-Request in this 
session", or does it mean "send location in Access-Request and 
Accounting-Request messages."

I ask because this will determine the behavior of the RADIUS client when a 
"Send-Location" attribute is sent in an Access-Accept.  If it means "send 
location in the next Access-Request" then the client will do that, and only 
that.  You should not expect location in an Access-Request sent as the 
result of a CoA-Request, *unless* that CoA-Request contains a 
"Send-Location" attribute.

----------------------------------------------------------------------------------------------------------
hi all,

with issue #74 bernard raised a question with regard to the usage of rfc 3576. avi proposed text is:

"
We need to change the paragraph from:

The COA message may instruct the
   access network to generate an Authorize-Only Access-Request (Access-
   Request with Service-Type set to "Authorize-Only") in which case the
   NAS MUST include the location infromation in this Access-Request.

to:
The COA message may instruct the
   access network to generate an Authorize-Only Access-Request (Access-
   Request with Service-Type set to "Authorize-Only") in which case the
   NAS MUST include the location infromation in this Access-Request if it included the location information is previous Access-Requests. "

i would like to ask whether this issue can be closed now?

ciao
hannes



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

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