Re: [RADIATOR] dictionary entries for Ascend conflict with IANA assigned ones

2011-06-10 Thread Heikki Vatiainen
On 06/07/2011 08:09 PM, Heikki Vatiainen wrote: > On 06/06/2011 07:27 PM, Bruno Tiago Rodrigues wrote: Hello Bruno and others, [about attributes 119-123 and possible others too] >> I was wondering if this could be fixed (or at least documented) on the >> next releases. > I'll check about adding

Re: [RADIATOR] dictionary entries for Ascend conflict with IANA assigned ones

2011-06-07 Thread Heikki Vatiainen
On 06/06/2011 07:27 PM, Bruno Tiago Rodrigues wrote: > The standard radiator dictionary file specifies at least a pair of > invalid entries sharing the same ID. > Apparently, Ascend defines a set of attributes on the global (IANA > assigned) range. > > ATTRIBUTEX-Ascend-FCP-Parameter

Re: [RADIATOR] dictionary entries for Ascend conflict with IANA assigned ones

2011-06-06 Thread Alan Buxey
Hi, Grrr. ascend dictionaries stomp all over IANA space - attributes 126-132 are also munged up (used by IANA assign Operator-Name space stuff - which we in eduroam would like to use widely) alan ___ radiator mailing list radiator@open.com.au http://www

[RADIATOR] dictionary entries for Ascend conflict with IANA assigned ones

2011-06-06 Thread Bruno Tiago Rodrigues
Dear all The standard radiator dictionary file specifies at least a pair of invalid entries sharing the same ID. Apparently, Ascend defines a set of attributes on the globalĀ  (IANA assigned) range. ATTRIBUTEX-Ascend-FCP-Parameter119string - conflicts with Digest-Domain ATTRIBU