Bang-path routing

[Alan DeKok <aland@deployingradius.com>]

  To follow up on a separate item:

Bernard Aboba wrote:
> ... For example,  the initial  
> EAP-Response/Identity could have included NAI source-routing which was
> subsequently stripped off.  For example, the EAP-Response/Identity
> might have been deployingradius.com!aland@example.com; by the time
> this arrives at the RADIUS server, the example.com proxy will have
> transformed it into aland@deployingradius.com within the User-Name
> Attribute,

  The problem is that this isn't common practice.  The existing roaming
providers don't do this.  Many AAA servers don't do this.

  Where did this text come from?  Why is it there?

  I've discussed this && the i18n issues with roaming providers && AAA
implementors.  They all agree that the existing text in 4282 relating to
i18n and bang-path routing is wrong.  They are starting to see other
standards rely on the "RFC4282" behavior, and it's causing them
problems.  There's a big push to come up with fixes.

  Alan DeKok.

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