[Standards] dialback refactoring

Peter Saint-Andre stpeter at stpeter.im
Thu Jun 25 17:43:27 UTC 2009

Hash: SHA1

On 6/25/09 11:42 AM, Ralph Meijer wrote:
> On Thu, 2009-06-25 at 19:09 +0200, Philipp Hancke wrote:
>> Ralph Meijer wrote:
>> [snip]
>>>> Ralph, do you have further feedback?
>>> I think you removed the confusing switching of roles of the servers
>>> between sections, per my request. I.e. you switched the hosts in two
>> Well, now the point of view switches between sections, in 2.1.1 the
>> sending server is example.org, in 2.1.2 it is xmpp.example.com; the
>> same applies to 2.2.
>> I am not sure if that is better... but it is not worse either.
> Personally, I rather have the point of view change. I makes all the
> examples in the spec cater to one goal: establishing a connection from
> one server to another. 


> Somewhere near the end (or maybe all the way in
> the beginning) we can remark that for traffic in the other direction,
> the whole shebang needs to be repeated with the roles of the domains
> reversed.

Yes, version 0.3 has text like that:


As mentioned, Server Dialback results in weak identity verification in
one direction only (in the foregoing text, verification of the
Originating Server by the Receiving Server). In order to proceed with
bi-directional communication so that the Receiving Server can send XML
stanzas to the Originating Server, the Receiving Server MUST now also
initiate a dialback negotiation with the Originating Server (i.e.,
assume the role of an originating server in a new dialback negotiation).



- --
Peter Saint-Andre

Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the Standards mailing list