RE: Capabilities negotiation problem statement

[Bernard Aboba <aboba@internaut.com>]

> I think the only issues that may not be addressed by the Mandatory bit
> (which, BTW, does not yet have WG consensus) that may require some
> additional text would be proxy chain and roaming consortium scenarios.
> If the Mandatory bit is hop-by-hop, then a Proxy Considerations section

Mandatory attributes are end-to-end in Diameter, so I assume they would be 
end-to-end in RADIUS too.  It's only Diameter application negotiation that 
is hop-by-hop. 


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