Subject: Re: [AAA-WG]: Re: Issue 424: Record-Route AVP in Responses

From: David Mitton <[email-masked]>
Date: Sat, 04 Oct 2003 17:19:15 -0400

On 9/30/2003 06:52 PM +0300, Jari Arkko wrote:
><snip>...

I've edited these changes in to 13c, but will pass editing against the 
Identities issue until we work it out.

Dave.

>>Updates for NASREQ -13b:
>>o  Section 9.2: Remove the following list item:
>>    "4. Route-Record AVPs (in the proper order)"
>>o  Section 9.2: Remove the following bullet:
>>    "The Route-Record AVPs MUST be added to the Diameter message, in
>>    the same order they were present in the request.  The gateway's
>>    position in the forwarding should be properly recorded."
>>o  Section 9.2: Replace the bullet
>>    "The response's Origin-Host information is created from the    FQDN 
>> of the source IP address of the RADIUS message."
>>    with
>>    "The response's Origin-Host information is created from the FQDN
>>    of the source IP address of the RADIUS message. The same FQDN
>>    is also stored to a Route-Record AVP."
>>o  Section 10.1: Update AVP occurrence table to specify that
>>    AAA message can have zero or more Route-Record AVPs.
>
>Ok.
>
>>A couple of related editorials/typos:
>>o  Section 9.3.3: Replace
>>    "...lookup on the source address and NAS-IP-Address
>>    attributes..."
>>    with
>>    "...lookup on the source address and NAS-IPv6-Address attribute..."
>>o  Section 9.3.3: Add to end of last paragraph
>>
>>    "...other action is taken."
>>    (seems this was chopped off at some point)
>
>Ok.
>
>--Jari
>
>
>
>