[Standards-JIG] Re: proto-JEP: Proposed Stream FeatureImprovements
JD Conley
jd.conley at coversant.net
Tue Aug 22 16:52:59 CDT 2006
I hit send a little too quickly..
Also, why should future compression be TLS based? It is very handy to,
for example, require TLS before authentication but only allow
compression after authentication.
-----Original Message-----
From: standards-jig-bounces at jabber.org
[mailto:standards-jig-bounces at jabber.org] On Behalf Of JD Conley
Sent: Tuesday, August 22, 2006 2:49 PM
To: Jabber protocol discussion list
Subject: RE: [Standards-JIG] Re: proto-JEP: Proposed Stream
FeatureImprovements
Use case: Server administrator specifies that IM sessions are only
allowed over a compressed channel for certain users. So, the server
doesn't send the client the session or resource bind features until
after compression is negotiated.
Also, why should future compression be TLS based? It is very handy to,
for example, require TLS before authentication but only allow
compression
-----Original Message-----
From: standards-jig-bounces at jabber.org
[mailto:standards-jig-bounces at jabber.org] On Behalf Of Dave Cridland
Sent: Tuesday, August 22, 2006 2:15 PM
To: Justin Karneges
Cc: Jabber protocol discussion list
Subject: Re: [Standards-JIG] Re: proto-JEP: Proposed Stream
FeatureImprovements
On Tue Aug 22 20:27:51 2006, Justin Karneges wrote:
> On Tuesday 22 August 2006 09:18, Dave Cridland wrote:
> > For compression, no stream restart is needed - you just have to
> > ensure that both sides know when the compression layer kicks in.
>
> But then new features can't be made available as a result of
> negotiating compression.
>
>
Can you come up with a use-case for that? I can't think of one myself,
unless it's a new stream feature that's inherent in the compression
algorithm. None of our existing compression algorithms have any, and
future compression ought to be TLS based, so realistically the features
would belong in the TLS layer.
Dave.
--
Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at jabber.org
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
More information about the Standards-JIG
mailing list