Re: [TLS] I-D ACTION:draft-ietf-tls-rfc2246-bis-11.txt

Hello all,

A couple of question and comments:

Sec. 6 says "If a TLS implementation receives a record type it does not
understand, it SHOULD just ignore it."

If such a record is received after the parties have started encrypting the  
records, should it try to decrypt the data, or should the implementation  
throw the record away immediately?

Sec A.5 specifically forbids the negotiation of 40 bit export ciphers.

Does this also apply to the 56 bit export ciphers that was defined just  
before the export restrictions were eased? My reading of the document  
indicates "Yes". But should not also the single DES suites (e.g.  
TLS_RSA_WITH_DES_CBC_SHA) and perhaps also IDEA also be phased out in a  
similar manner?

About compatibility: Back in August/September 2004 Opera Software  
performed a test where we released a Technology Preview version of Opera  
with TLS 1.1 and TLS Extensions enabled. During this test our users  
identified more than 120 services (including major banks) that did not  
interoperate with a client using either TLS 1.1 or TLS Extensions, or  
both. I have so far not been able to find out what is causing the problem.

Is it within the scope of this draft to discuss how to handle this  
situation? We did, after all, have similar problems when TLS 1.0 was  
introduced.

-- 
Sincerely,
Yngve N. Pettersen

********************************************************************
Senior Developer		             Email: yngve@opera.com
Opera Software ASA                   http://www.opera.com/
Phone:  +47 24 16 42 60              Fax:    +47 24 16 40 01
********************************************************************

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls