-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/30/09 2:50 PM, Fabio Forno wrote: > On Thu, Apr 30, 2009 at 10:16 PM, Fabio Forno <[email protected]> wrote: >> I've just a problem with the business rules, specifically these ones >> >> # TLS compression and stream compression SHOULD NOT be used simultaneously. >> # If both TLS (whether including TLS compression or not) and stream >> compression are used, then TLS MUST be negotiated first, followed by >> negotiation of stream compression. >> >> The above business rules don't forbid but discourage to fall back to >> stream compression after TLS has been established but no compression >> has been activated. I see no harm in telling that stream compression >> MAY be offered after TLS if TLS doesn't succeed in activating >> compression (so far we haven't been able to to it with any server) > > Just had an IM coversation with Dave about that. I completely misread > the rules skipping the word "TLS *compression*" in the first rule, so > the rules work, sorry. > > There only one possible improvement in the second rule, which better > clarifies when using stream compression: Stream compression MAY be > offered after TLS negotiation if TLS compression fails (it sounds more > as a recipe for users)
That wording is better. Thanks! Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn/aSUACgkQNL8k5A2w/vzNMQCcCFEa55/6XlgWA+GkEE5ymFKa ZVkAnikOvz24iY7Bz5bloHm2F5P5BYCp =tA21 -----END PGP SIGNATURE-----
