RE: I believe that AS2 is now ready to be submitted to IETF as a RFC...

in draft-ietf-ediint-as2-14.txt, section 7.4.3:
 
For signed messages, the algorith used to calculate the
MIC MUST be the same as the algorithm that was used on the
message that was signed.
 
Then if the message is signed, the signed-receipt-micalg parameter is
not taken into account;
But the draft continues with:
 
If the message is not signed, then
the SHA-1 algorithm should be used.
 
So the signed-receipt-micalg parameter is never taken into account ?
(And there's no way of requesting a MD5 MIC for an unsigned message).
 
 
 
 

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Rik Drummond
Sent: 7 janvier, 2004 01:45
To: [email protected]
Subject: RE: I believe that AS2 is now ready to be submitted to IETF as
a RFC...


thanks... any more?

-----Original Message-----
From: Shan Harter [mailto:[email protected]] 
Sent: Wednesday, January 07, 2004 12:29 AM
To: 'Rik Drummond'; [email protected]
Subject: RE: I believe that AS2 is now ready to be submitted to IETF as
a RFC...


Perhaps a clarification for the following?
 
1. "AS2-Version: 1.1 - Designates those implementations which support
Compression as defined by RFC 3274."
 
2. The draft draft-ietf-ediint-as2-14.txt does not reference
draft-ietf-ediint-compression-03.txt. 
 
3. draft-ietf-ediint-compression-03.txt does not reference RFC 3274.
 
4. draft-ietf-ediint-as2-14.txt does reference RFC 3274 for compression.
 
 

-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Rik Drummond
Sent: Tuesday, January 06, 2004 10:26 PM
To: [email protected]
Subject: I believe that AS2 is now ready to be submitted to IETF as a
RFC...


.. are there any more comments on it before we do a last call on this
list?
 
Rik Drummond, Chair EDIINT WG