AW: Comments on draft-ietf-radext-digest-auth-06.txt (fwd)

"Beck01, Wolfgang" <BeckW@t-systems.com> Thu, 17 November 2005 09:06 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Thu, 17 Nov 2005 09:30:56 +0000
Message-Id: <97A461F3EE5284469E41ED3728202F41121EEC@S4DE9JSAAMW.ost.t-com.de>
From: "Beck01, Wolfgang" <BeckW@t-systems.com>
To: radiusext@ops.ietf.org
Cc: lberger@movaz.com
Subject: AW: Comments on draft-ietf-radext-digest-auth-06.txt (fwd)
Date: Thu, 17 Nov 2005 10:06:49 +0100
MIME-Version: 1.0
Content-Type: text/plain

Lou wrote:

> Bernard, (Wolfgang),
> 
> [..] 
> 1.  It seems to me that both the SIP and Diameter drafts 
> don't fully support 
> the requirements laid out in RFC 3702.  Also, neither draft 
> references this RFC. I found this really surprising.  What is the relationship of 
> the drafts to the RFC?  Is there any intention/desire to have 
> the drafts fully support it?  
draft-ietf-radext-digest-auth tries to be useful for other protocols than SIP, too.
It's a building block, not a complete AAA framework.

Wolfgang

--
T-Systems
Next Generation IP Services and Systems
+49 6151 937 2863
Am Kavalleriesand 3
64295 Darmstadt
Germany 

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