RE: HeaderDigest, DataDigest, etc

["Julian Satran" <satran@haifasphere.co.il>]

Yes I have added a similar statement to the digest part. No new+none
without CRC32C by default.

Regards,
Julo


-----Original Message-----
From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu] On Behalf Of
Bill Studenmund
Sent: 17 January, 2003 23:59
To: Black_David@emc.com
Cc: nramas@windows.microsoft.com; ips@ece.cmu.edu
Subject: RE: HeaderDigest, DataDigest, etc


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