RE: AW: Comments on draft-ietf-radext-digest-auth-06.txt (fwd)
"Nelson, David" <dnelson@enterasys.com> Thu, 17 November 2005 15:42 UTC
Envelope-to: radiusext-data@psg.com
Delivery-date: Thu, 17 Nov 2005 15:43:12 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: AW: Comments on draft-ietf-radext-digest-auth-06.txt (fwd)
Date: Thu, 17 Nov 2005 10:42:37 -0500
Message-ID: <3CFB564E055A594B82C4FE89D215656006B6C1@MABOSEVS2.ets.enterasys.com>
Thread-Topic: AW: Comments on draft-ietf-radext-digest-auth-06.txt (fwd)
Thread-Index: AcXrfYfWdJtxgE5oTrW5mts/bJdxwQADv0og
From: "Nelson, David" <dnelson@enterasys.com>
To: Lou Berger <lberger@movaz.com>, "Beck01, Wolfgang" <BeckW@t-systems.com>, Bernard Aboba <aboba@internaut.com>
Cc: radiusext@ops.ietf.org
> The WG charter states: > > > >- SIP support. RADIUS is currently used for SIP authentication, > >authorization and accounting. Standardization of these attributes > >will enable improved interoperability. > > > >This document will be upwards compatible with the Diameter SIP > >application, and conform to existing IETF RFCs on HTTP Digest, > >including RFC 2617, 3261, and 3310. > > It seems clear that the digest-auth draft covers the objectives of > the second paragraph. But the first paragraph seems broader than > this and suggesting covering the full scope of "SIP authentication, > authorization and accounting". (Presumably as defined in the, albeit > informational, requirements RFC.) Is there any intent or interest in > covering the remaining requirements? > > I can contribute to this if there is interest, and being a newbie in > this area, would welcome happily collaborate with anyone else who may > be interested. Creating RADIUS features that exceed the comparable features in Diameter would be a problem. That's not the intent of RADEXT. Everything in RADEXT WG work items needs to be upwards compatible to a corresponding feature in Diameter, or contain that Diameter compatibility in the RADEXT document. If these are requirements that you see as not being addressed in the Diameter SIP Application, then I don't see how we could (or should) address them in RADIUS (alone). -- 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/>
- RE: AW: Comments on draft-ietf-radext-digest-auth… Nelson, David
- AW: Comments on draft-ietf-radext-digest-auth-06.… Beck01, Wolfgang