AW: Do we have consensus on the Digest Auth draft issues?

"Beck01, Wolfgang" <BeckW@t-systems.com> Thu, 11 August 2005 14:59 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Thu, 11 Aug 2005 15:00:02 +0000
Message-Id: <97A461F3EE5284469E41ED3728202F41121E32@S4DE9JSAAMW.ost.t-com.de>
From: "Beck01, Wolfgang" <BeckW@t-systems.com>
To: radiusext@ops.ietf.org
Cc: dnelson@enterasys.com, aboba@internaut.com
Subject: AW: Do we have consensus on the Digest Auth draft issues?
Date: Thu, 11 Aug 2005 16:59:53 +0200
MIME-Version: 1.0
Content-Type: text/plain

Bernard wrote:
> Dave wrote:
> > The substantive issue with the draft-ietf-radext-diget-auth-03.txt 
> > seems to be how to deal with Diameter interoperability of the two 
> > different sources of nonce.  The general sense of the room at IETF-63 
> > seemed to be that the Digest Auth draft needed to support both modes, 
> > and that the companion Diameter draft would need to follow suit.  This 
> > places the Diameter compatibility action item with the Diameter 
> > document.
> >
> > Does the WG at large agree?  Please reply.
> 
> Personally, I agree.  But then again, I was the person who 
> first suggested moving the  Diameter compatibility section to 
> the Diameter document :)
> 
> > Assuming that we do agree, then what action item doe we have w.r.t. 
> > the Diameter document?
> 
> I think the implication is that the Diameter document (which 
> has been in simulaneous WG last call with Digest) needs to 
> own the compatibility section.
> 

I am preparing a -04 version of the draft correcting a few nits
-- like the text/table mismatch discovered by Hideo Morishita --
and without the Diameter migration section. I have asked Miguel
Garcia whether he could add the client-side nonce generation mode
and the RADIUS/Diameter migration section into
draft-ietf-diameter-sip-app. If there are no new issues with -03,
I will submit -04 tomorrow.

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