Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id h0HM3gS19028
	for ips-outgoing; Fri, 17 Jan 2003 17:03:42 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from lion.ninthwonder.com (lion.ninthwonder.com [151.199.66.147])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h0HM3eW19024
	for <ips@ece.cmu.edu>; Fri, 17 Jan 2003 17:03:40 -0500 (EST)
Received: by lion.ninthwonder.com (Postfix, from userid 1021)
	id D7D4D3070A; Fri, 17 Jan 2003 17:03:27 -0500 (EST)
Date: Fri, 17 Jan 2003 13:58:52 -0800 (PST)
From: Bill Studenmund <wrstuden@wasabisystems.com>
X-X-Sender:  <wrstuden@candlekeep.home-net.internetconnect.net>
To: <Black_David@emc.com>
Cc: <nramas@windows.microsoft.com>, <ips@ece.cmu.edu>
Subject: RE: HeaderDigest, DataDigest, etc
In-Reply-To: <277DD60FB639D511AC0400B0D068B71E0564C7B1@corpmx14.us.dg.com>
Message-ID: <Pine.NEB.4.33.0301171356360.501-100000@candlekeep.home-net.internetconnect.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

On Fri, 17 Jan 2003 Black_David@emc.com wrote:

> Yes in both cases, as the "also offer" requirements are triggered
> by the extension algorithm - they don't apply if no extension algorithm
> is offered.

Would our whole thread about AuthMethods apply here too (I think it does
but want to make sure)? i.e. the concern is for a shipped-default that has
had no administrative intervention, and that if an admin chooses to only
enable a private or public algorithm it is fine to offer/accept only that
algorithm?

Take care,

Bill

> -----Original Message-----
> From: Lakshmi Ramasubramanian [mailto:nramas@windows.microsoft.com]
> Sent: Friday, January 17, 2003 1:59 PM
> To: ips@ece.cmu.edu
> Subject: HeaderDigest, DataDigest, etc
>
>
> According to the spec, if an initiator offers private\public extension(s)
> for Header\Data Digest, it MUST also offer CRC32C and None. But if
> the initiator requires digest can it offer CRC32C only (And NOT offer None)?
>
> This way it can ensure that it talks only to those targets that support
> digest.
>
> Does the same hold for AuthMethod also - I mean can the initiator offer only
> CHAP for AuthMethod (And NOT offer none)?
>
> thanks!
>  -lakshmi
>
>

