Return-Path: X-Sieve: cmu-sieve 2.0 Return-Path: Received: (from majordom@localhost) by ece.cmu.edu (8.11.0/8.10.2) id h0HJkrr10068 for ips-outgoing; Fri, 17 Jan 2003 14:46:53 -0500 (EST) X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f Received: from mxic2.corp.emc.com (mxic2.corp.emc.com [128.221.31.40]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h0HJkoW10060 for ; Fri, 17 Jan 2003 14:46:50 -0500 (EST) Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Fri, 17 Jan 2003 14:46:40 -0500 Message-ID: <277DD60FB639D511AC0400B0D068B71E0564C7B1@corpmx14.us.dg.com> From: Black_David@emc.com To: nramas@windows.microsoft.com, ips@ece.cmu.edu Subject: RE: HeaderDigest, DataDigest, etc Date: Fri, 17 Jan 2003 14:45:48 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2BE61.089B0F00" Sender: owner-ips@ece.cmu.edu Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C2BE61.089B0F00 Content-Type: text/plain; charset="iso-8859-1" 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. Thanks, --David -----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 ------_=_NextPart_001_01C2BE61.089B0F00 Content-Type: text/html; charset="iso-8859-1" Message
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.
 
Thanks,
--David
-----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
------_=_NextPart_001_01C2BE61.089B0F00--