Re: [POSH] Comments/questions on draft-miller-posh-00

[Philipp Hancke <[e-mail]>]

Am 27.07.2013 19:22, schrieb Peter Saint-Andre:
[...]
>> Similarly, I can't see anything obviously wrong with letting the
>> application handshake complete, then performing the POSH
>> operations before deciding the application connection is not
>> suitable and should be terminated before being used.  Is the MUST
>> in this section mandating the order of operations necessary for
>> some other reason?
>
> As mentioned above, the MUST here is perhaps a bit silly because it's
> so obvious. I think there is a better way to word it...

While implementing this I found another reason why this MUST doesn't work.

In XMPP we want DNA to have the ability to multiplex several domain 
pairs, with multiple remote domains.

However, at the time of the TLS handshake we only know a single remote 
domain (taken from the stream's from).

At any later time, the remote end may use this <db:result/> stuff to add 
another remote domain. This might trigger the POSH dance and clearly 
happens after the TLS handshake is done.

I would suggest removing this MUST.