Re: The ecosystem is moving

Ted Lemon <> Sat, 14 May 2016 17:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5AE2912D189 for <>; Sat, 14 May 2016 10:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qH6IvsbM4DNR for <>; Sat, 14 May 2016 10:28:08 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4010:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2C62C12D180 for <>; Sat, 14 May 2016 10:28:08 -0700 (PDT)
Received: by with SMTP id ww9so28730286lbc.2 for <>; Sat, 14 May 2016 10:28:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PDuHmCdYJhgIl4BmsuUYTTP/fHXZHFhpD5RvuJhs9VE=; b=h/fZlv+4Sv91sZh3QE/g72lZoEZE9IBNFJ2bGmzmxB6QorZ50yL1/auOZCubFRLYDZ XSUf8lWVQV3tta7hAtoD3gSuDOVgAFFo5p49kqhizFsUuqNEIcQi0QBjeaSsCeX3lHdS Myp2xJihJArgiUZOGlbIc9GVrFkYyqZbMGNPUNyUVWvwkuDXgVZkm2Cm3FaGqJeOwjAI R1qAHfsc+V5maogeOJCLCLA25GlHNkpGtS9o2B7TxDR/eU2319HoV/ZgGHzANtxNlvY6 5Plnwbf/3TEsCbe4Tw1xV0DNVZKApPHJkO2bsYiP3XEOtGBYbLYUY9MgmrYZRntorwuc 0DOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PDuHmCdYJhgIl4BmsuUYTTP/fHXZHFhpD5RvuJhs9VE=; b=e3WIV8CiyqrDqQChavSjJp/r2JfvK73eHmuurzOP2xD8WQ05l1BA6EvUYPE5fyyL+h mlFPuZBF7dHjiB3FVkgHmFFVzklDypAM4r4zs+j0ZuYED95mCsOgIoQNRYtFVW5PJzSA OzkKL/KMMfnQCyU/WVvyaCwZaGCiQngolI2ztsR6ij0IMIFVOr2A31qJ42sx+1ltNEYw yJG6Xkhn1aHhgancKqviymb5X85UGpXmcpdZJ00Hgu5MhUqOc+W4h+qTKz0vpqkZ85ZE B4ABI6NMv/bGmiKUnhalUmNQgeqq2CdgqJ+NUR633CGRxGTxrLByfddlEI63PUboi6/O DdlQ==
X-Gm-Message-State: AOPr4FUehLt+2H9qy6weaktckSsLWgaqiDOk7nozi4t+NfD6p76m7tKa9zN8FoPJEHN+XCqEKhpW0ZFy6sPmkw==
X-Received: by with SMTP id xp9mr8527168lbb.133.1463246886346; Sat, 14 May 2016 10:28:06 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Sat, 14 May 2016 10:27:26 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <> <>
From: Ted Lemon <>
Date: Sat, 14 May 2016 13:27:26 -0400
Message-ID: <>
Subject: Re: The ecosystem is moving
Content-Type: multipart/alternative; boundary=001a11c26b2ae13c700532d0b6f3
Archived-At: <>
Cc: " Discussion" <>, Phillip Hallam-Baker <>, Paul Wouters <>, Dave Crocker <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 14 May 2016 17:28:10 -0000

I suspect that a lot of these problems simply have to do with the fact that
Jabber isn't very mainstream, and so there are a lot of implementations out
there with not enough miles on them to have smoothed out some of the
significant interop problems.

On Sat, May 14, 2016 at 1:00 PM, <> wrote:

> > XMPP does not have ongoing problems with interop. Quite the opposite -
> the
> > community is extremely positively engaged with the standards process at
> the
> > XSF, and interoperability issues are detected fast, treated seriously,
> and
> > fixed quickly. If they occur due to specifications being unclear, the
> spec
> > is fixed.
> > Every server I'm aware of, with the exception of Google's XMPP S2S
> service
> > (still operating but fundamentally broken) has supported at least the
> > baseline of "XMPP" for years.
> Dave, all due respect, but this doesn't match my IETF experience, which
> lines
> up with Martin's and Ted's pretty closely. Every time a meeting rolls
> around I
> have to fight to get jabber chat working.
> The BA meeting was better than usual. I fired up Psi, which despite being
> crappy I am forced to use for work because Adium won't talk to the
> corporate
> jabber server for some reason. Finding the two accounts I had set up
> previously
> were both dead, I started the hunt for a functioning public server. (I
> tried a
> private server once, but never succeeded in getting it going.)
> After trying various server names from a list that obviously hadn't been
> updated in years, I found one that responded but wouldn't configure
> properly in
> Psi. So I switched to Adium, where it worked.
> But the real test is whether or not you can join one of the IETF group
> chats. I
> tried, and it worked. (My past experience has been that this has about a
> 50-50
> shot of working, and when it doesn't work there's absolutely no indication
> of
> what's wrong.)
> So after maybe an hour of fiddling I once again had a working setup,
> albeit one
> where I have to have use two different clients to connect to different
> servers.
> As these things go, this counts as s significant success.
> Now, I have no doubt that I'm missing some sooper seecret sauce, have bad
> google-fu, should not be using a Mac because reasons, or whatever. But
> that's
> beside the point. As abjectly incompetent as I undoubtedly am with jabber,
> I
> doubt very very much that I rise to the level of incompetence of the
> average
> user setting up IM for the first time.
> And perhaps all these problems are not "interoperability issues", by your
> definition of that term. But the bottom line is that the reasons why
> something
> is a PITA don't change the fact that it's a PITA.
>                                 Ned