[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RADEXT charter, Take 8
> Bernard wrote:
> > - SIP support. RADIUS is currently used for SIP authentication,
> > authorization and accounting. Standardization of these attributes
> > will enable improved interoperability.
> I'd like to add something about compatibility with existing
> IETF RFCs on HTTP Digest on this...
> Also, add something about compatibility. I think the functionality
> of Diameter SIP is bigger than in RADIUS SIP, so maybe a note
> about not necessarily being able to translate from Diameter to
> RADIUS in all cases is appropriate.
> So I would prefer seeing a "Diameter Translation Considerations"
> section in the RADIUS SIP extension, for instance. I'll volunteer
This is already on my list for version -02 of the HTTP Digest draft.
> Bernard wrote:
> > * All drafts will need to undergo review prior to acceptance as WG work
> > items, which includes demonstration that the drafts are backward
> > compatible with RADIUS RFCs and are compatible with equivalent
> > facilities in Diameter. Given the backwards compatibility issues, no
> > document including sub-attributes will be considered for publication as
> > an RFC before the RADIUS design guidelines and RADIUS/Diameter
> > translation work items are completed, analyzing the issues in
> > a comprehensive way.
> I think this approach to subattributes makes sense.
If this does not translate into 'string attributes must not be structured',
I can live with it. You know my opinion about this.
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.