Re: [secdir] Secdir review of draft-hollenbeck-rfc4930bis-02

"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 15 July 2009 22:12 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 806823A6B66; Wed, 15 Jul 2009 15:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e48UEN2BhTtV; Wed, 15 Jul 2009 15:12:19 -0700 (PDT)
Received: from osprey.verisign.com (osprey.verisign.com [216.168.239.75]) by core3.amsl.com (Postfix) with ESMTP id 1D04D3A6B45; Wed, 15 Jul 2009 15:12:19 -0700 (PDT)
Received: from dul1wnexcn03.vcorp.ad.vrsn.com (dul1wnexcn03.vcorp.ad.vrsn.com [10.170.12.113]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id n6FLxLQq011765; Wed, 15 Jul 2009 17:59:21 -0400
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 15 Jul 2009 23:11:36 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 15 Jul 2009 18:11:35 -0400
Message-ID: <046F43A8D79C794FA4733814869CDF0702B8DE91@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <20090715200807.GS1274@Sun.COM>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [secdir] Secdir review of draft-hollenbeck-rfc4930bis-02
Thread-Index: AcoFjJFe9m81ua2hS/CYixixcSOlzgADJChQ
References: <046F43A8D79C794FA4733814869CDF07025CD275@dul1wnexmb01.vcorp.ad.vrsn.com> <20090715173502.GO1274@Sun.COM> <046F43A8D79C794FA4733814869CDF0702B8DE7A@dul1wnexmb01.vcorp.ad.vrsn.com> <20090715200807.GS1274@Sun.COM>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Nicolas Williams <Nicolas.Williams@sun.com>
X-OriginalArrivalTime: 15 Jul 2009 22:11:36.0144 (UTC) FILETIME=[38049500:01CA0599]
Cc: secdir@ietf.org, iesg@ietf.org
Subject: Re: [secdir] Secdir review of draft-hollenbeck-rfc4930bis-02
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 22:12:20 -0000

> -----Original Message-----
> From: Nicolas Williams [mailto:Nicolas.Williams@sun.com] 
> Sent: Wednesday, July 15, 2009 4:08 PM
> To: Hollenbeck, Scott
> Cc: Sandy Murphy; catherine.meadows@nrl.navy.mil; 
> iesg@ietf.org; secdir@ietf.org
> Subject: Re: [secdir] Secdir review of draft-hollenbeck-rfc4930bis-02
> 
> On Wed, Jul 15, 2009 at 03:44:04PM -0400, Hollenbeck, Scott wrote:
> > > -----Original Message-----
> > > From: Nicolas Williams [mailto:Nicolas.Williams@sun.com]
> > > Sent: Wednesday, July 15, 2009 1:35 PM
> > > To: Hollenbeck, Scott
> > > Cc: Sandy Murphy; catherine.meadows@nrl.navy.mil; iesg@ietf.org; 
> > > secdir@ietf.org
> > > Subject: Re: [secdir] Secdir review of 
> > > draft-hollenbeck-rfc4930bis-02
> > > 
> > > On Tue, Jul 14, 2009 at 08:08:32PM -0400, Hollenbeck, Scott wrote:
> > > > Doesn't TLS provide protections for this issue?
> > > 
> > > Provided you authenticate the server, yes.
> > 
> > Good, because server authentication is a requirement specified in 
> > section 9 of 4934bis.
> 
> And provided we're talking about a two-party, client-server 
> type of application.  Specifically, that the username and 
> cleartext password are not being sent to more than one party 
> and never in cleartext.

That's exactly how it works right now.

-Scott-