[Standards] Council Minutes 2019-07-10

Florian Schmaus flo at geekplace.eu
Fri Jul 19 11:52:00 UTC 2019


On 17.07.19 15:57, Tedd Sterr wrote:
> *3b) PR #796 - XEP-0368: clarify what happens when a `.` target is
> published* - https://github.com/xsf/xeps/pull/796
> Jonas: +1
> Link: +1 (definitely!)
> Georg: +1 (this is just a clarification of RFC 2782)
> Dave: [pending]
> Kev: [pending]

This PR adds the following to XEP-0368: SRV records for XMPP over TLS

"""
If the <tt>_xmpps-client</tt> (or <tt>_xmpps-server</tt>) target is set
to <tt>.</tt> (dot), this indicates as per &rfc2782; that the service is
not provided for the given domain. In this context, this means that
Direct TLS is not supported. In this case, the initiating party SHOULD
look up <tt>_xmpp-client</tt> (or <tt>_xmpp-server</tt>) records. The
initiating party MUST NOT perform A/AAAA fallback as per &rfc6120;
(since the service provider has already indicated that the SRV protocol
is supported).
"""

I am not sure about the last sentence, especially,

"""
The initiating party MUST NOT perform A/AAAA fallback as per &rfc6120;
(since the service provider has already indicated that the SRV protocol
is supported).
"""

This assumes that SRV RRs come with a contract stating that if you add
one for a service then you also add SRV RRs for all other possible
provided services. Is that contract written down somewhere? If not, I'd
rather not start adding this semantic on top of SRV RRs in some remote
place like a XEP.

- Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 614 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20190719/e463bf97/attachment-0001.sig>


More information about the Standards mailing list