[Standards] dialback refactoring

Peter Saint-Andre stpeter at stpeter.im
Thu Jun 25 17:29:18 UTC 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/24/09 11:22 PM, Ralph Meijer wrote:
> On Wed, Jun 24, 2009 at 08:16:00PM -0600, Peter Saint-Andre wrote:
>> On 6/24/09 2:49 PM, Ralph Meijer wrote:
>>> On Wed, 2009-06-24 at 14:16 -0600, Peter Saint-Andre wrote:
>> [..]
>>
>>> Yeah, that seems ok, although I would probably keep 'Server' instead of
>>> 'Host' and 'Receiving Server' to keep in sync with RFC 3920 and
>>> XEP-0185. 
>> OK. So:
>>
>> - - Sending Domain
>> - - Accepting Domain
>> - - Originating Server
>> - - Receiving Server
>> - - Authoritative Server
> 
> Yeah.

I think I prefer SENDER DOMAIN and TARGET DOMAIN for the first two.

>>> To make it more real, make sure the hosts have different
>>> hostnames (duck.example.org, swan.example.org and elephant.example.com)
>>> from the domains (example.org, example.com). Maybe also show the
>>> associated DNS records (SRV and A).
>> I have DNS records and IP addresses in version 0.3 of the spec, so it
>> would be fairly straightforward to port those over. I agree that they
>> are helpful.
> 
> OK
> 
>> Looking more closely, I would pair them up as follows:
>>
>> DB authoritative-host-unknown = stanza remote-server-not-found (sent
>> from receiving server to originating server if the authoritative server
>> does not service the domain asserted by the originating server)
>>
>> DB host-unknown = stanza item-not-found
>>
>> DB remote-connection-failed = recipient-unavailable
>>
>> DB remote-server-timeout = stanza remote-server-timeout
> 
> That seems a proper mapping indeed.

Super.

>> Correct. I ran out of time to do that (in fact I don't remember how I
>> generated those since openssl doesn't support HMAC-SHA256, but I'll
>> figure it out again).
> 
> If not, I can show how to do it in Python or do it for you.

I simply don't remember how to do it -- I've done it before but that was
a while ago. :)

>>> I expect the title for example 13 to be from the other perspective.
>> So "Authoritative Server Receives Verification Request"?
> 
> Yeah.

I'll check all the example captions.

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

iEYEARECAAYFAkpDs+4ACgkQNL8k5A2w/vyMCQCfU29FvW8CoioR0DJuyYfMfTib
f3IAn1uHwfrjpHxMNPnZrm+Uo6fxdR/O
=bLy1
-----END PGP SIGNATURE-----



More information about the Standards mailing list