Re: [xmpp] Barry Leiba's No Objection on draft-ietf-xmpp-posh-04: (with COMMENT)

Peter Saint-Andre <> Tue, 04 August 2015 03:17 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id DD6711B33F6 for <>; Mon, 3 Aug 2015 20:17:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fi8dqr_-w_jw for <>; Mon, 3 Aug 2015 20:17:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 519A41B33F2 for <>; Mon, 3 Aug 2015 20:17:23 -0700 (PDT)
Received: by igr7 with SMTP id 7so66638844igr.0 for <>; Mon, 03 Aug 2015 20:17:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=dtZdk+Qe+mxUIKcjbTCIncC0PtVgvtCNayS+Vut09+g=; b=a5gtzsnwPHZ314qcHu2nEyOT+hti8TD9rj9XOuXTgdy9jccAEmJBMybg761Sq1g4Zx RGvht0tvJ6aSD/1s4tmhW3BaQibjaDtwh8K6qi3J4KKkDQQO5YNxw78pasrO5DNsJmB1 pwsvU2S72/gDWwk8B7UR8pFvkqxlymhgAb7TJQ2/dcPixTUaPshbvRL+HjugWK3CsGVc ph66teNBxsNRcMMouq1ILxbCyQ1K8roGU2Z2bBJfggmWys5X8i3akw2u+eNj5oedidIh eU77eu/XC7HQ/aLW/jySC+M0psa/khjzLrBY6egH7Jw42AnKyWS/zfBmguos/kS620qq tiJA==
X-Gm-Message-State: ALoCoQkCup0R2KM7KlNmcIpWTLL9TIoRpSdncdu0FBpRoqY4zoNGx4v+2rTLwigSTvLVMJBfALFx
X-Received: by with SMTP id lp9mr1364689igb.56.1438658242659; Mon, 03 Aug 2015 20:17:22 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id d8sm470390igl.19.2015. (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Aug 2015 20:17:21 -0700 (PDT)
References: <> <> <> <> <> <> <>
Mime-Version: 1.0 (1.0)
In-Reply-To: <>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
X-Mailer: iPhone Mail (12H143)
From: Peter Saint-Andre <>
Date: Mon, 03 Aug 2015 21:17:19 -0600
To: Mark Nottingham <>
Archived-At: <>
Cc: "" <>, "" <>, "" <>, "" <>, Barry Leiba <>, "" <>, The IESG <>
Subject: Re: [xmpp] Barry Leiba's No Objection on draft-ietf-xmpp-posh-04: (with COMMENT)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 04 Aug 2015 03:17:25 -0000

Hi Mark, thanks for sharing your perspective. I'll give it more thought tomorrow. 


Sent from mobile, might be terse 

> On Aug 3, 2015, at 6:10 PM, Mark Nottingham <> wrote:
> Hi Peter,
> As I discussed with Barry, I don't have any strong guidance here; I agree that his approach is probably the way I'd go with if I designed it myself, but I agree it's highly dependent on the situation. With my DE hat on, I'm neutral on this. 
> Cheers,
>> On 4 Aug 2015, at 9:31 am, Peter Saint-Andre - &yet <> wrote:
>> Adding Mark to this thread, with pointers to get him up to speed...
>> On 7/31/15 7:50 PM, Barry Leiba wrote:
>>>>> If you like, it could even do POSH service names and POSH format
>>>>> names, and specify ".well-known/posh/<servicename>/<formatname>",
>>>> Currently it's the <servicename> field that we're most interested in.
>>> Right... and that's what I'm suggesting an FCFS registry for.  You
>>> register "posh" in .well-known, and you create your own FCFS registry
>>> for service names, and if you don't care about the format as a
>>> separate thing, you just register "spice.json" (and so on) in your
>>> FCFS registry.  That way, Mark doesn't get involved in approving
>>> "posh.x" and "posh.y" and "posh.z", when Mark has no idea of what to
>>> say about posh service names (or seedy ones, for that matter).
>>>> Perhaps it makes sense to talk about it again with Mark?
>>> Sounds like a plan.
>> Hi Mark,
>> During IESG review of draft-ietf-xmpp-posh, Barry raised a question about the .well-known registration, which you and Matt Miller and I talked about ages ago. Here are some relevant readings:
>> Barry's proposed approach is more elegant. However, my feeling is that POSH is essentially a one-off workaround for use in XMPP until DNSSEC and DANE are more widely deployed. Although we've tried to design it in such a way that it *could* be used by other application protocols, I doubt that folks in those communities will use POSH unless Matt and I start actively promoting it (and even that is only a necessary condition, not a sufficent one). Because I don't think that we'll see additional .well-known registrations related to POSH, setting up a separate POSH registry to supplement a "posh" entry in the well-known URIs registry feels like overkill to me given the burden on IANA (I'm not a fan of one-entry registries).
>> That said, people have been wrong before about the popularity of technologies defined in RFCs and it's possible that POSH could become more popular, in which case I'd lean more strongly toward the approach that Barry has outlined.
>> As the designated expert for the well-known URIs registry, do you have any suggestions or preferences on how to proceed?
>> Thanks!
>> Peter
> --
> Mark Nottingham