Re: [DNSOP] Prefixed name spaces and DANE client TLSA
Tony Finch <dot@dotat.at> Wed, 13 January 2016 10:24 UTC
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8321A037E for <dnsop@ietfa.amsl.com>; Wed, 13 Jan 2016 02:24:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyytoZSkXT4l for <dnsop@ietfa.amsl.com>; Wed, 13 Jan 2016 02:24:37 -0800 (PST)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [131.111.8.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD6531A1A33 for <dnsop@ietf.org>; Wed, 13 Jan 2016 02:24:36 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:58842) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1aJIbP-000xVJ-iT (Exim 4.86_36-e07b163) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 13 Jan 2016 10:24:31 +0000
Received: from fanf2 by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1aJIbP-0001Gr-Kv (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 13 Jan 2016 10:24:31 +0000
Date: Wed, 13 Jan 2016 10:24:31 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: John Levine <johnl@taugh.com>
In-Reply-To: <20160113055505.54822.qmail@ary.lan>
Message-ID: <alpine.LSU.2.00.1601131015380.8365@hermes-2.csi.cam.ac.uk>
References: <20160113055505.54822.qmail@ary.lan>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/MPcTKCDXlUYkfcRTjRKjyzOBuuc>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Prefixed name spaces and DANE client TLSA
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2016 10:24:38 -0000
John Levine <johnl@taugh.com> wrote: > > What's peculiar is the names. The previous proposal was to look up a > TLSA at _smtp.outbound.example.com, then somone noted that _smtp is > for servers, so they want to look up the newly invented name > _smtp-client.outbound.example.com. If you have a client for some > other service, you make up a name. (Read the draft if this seems like > an implausible summary.) This naming scheme is a bad idea because it looks very similar to XMPP SRV records but has confusingly different semantics. _xmpp-client refers to an XMPP server endpoint for use by clients. _xmpp-server refers to an XMPP server endpoint for use by other servers. _submission refers to SMTP-like server endpoints for use by clients. _smtp-client is proposed to refer to SMTP client initiators. More generally this promises to clutter up the service identifier namespace with identifiers for clients, which are not services. I like the idea of taking the server's service labels and prefixing them with _client. Tony. -- f.anthony.n.finch <dot@dotat.at> http://dotat.at/ Thames, Dover, Wight: Northwest backing southwest 5 to 7, perhaps gale 8 later. Moderate or rough. Showers, becoming thundery later. Good, occasionally poor later.
- Re: [DNSOP] Prefixed name spaces and DANE client … George Michaelson
- [DNSOP] Prefixed name spaces and DANE client TLSA John Levine
- Re: [DNSOP] Prefixed name spaces and DANE client … Shane Kerr
- Re: [DNSOP] Prefixed name spaces and DANE client … Tony Finch
- Re: [DNSOP] Prefixed name spaces and DANE client … Shumon Huque
- Re: [DNSOP] Prefixed name spaces and DANE client … John R Levine
- Re: [DNSOP] Prefixed name spaces and DANE client … Ray Bellis
- Re: [DNSOP] Prefixed name spaces and DANE client … John Levine
- Re: [DNSOP] Prefixed name spaces and DANE client … Ray Bellis
- Re: [DNSOP] Prefixed name spaces and DANE client … John Levine
- Re: [DNSOP] Prefixed name spaces and DANE client … Ray Bellis
- Re: [DNSOP] Prefixed name spaces and DANE client … Shumon Huque
- Re: [DNSOP] Prefixed name spaces and DANE client … Tim Wicinski
- Re: [DNSOP] Prefixed name spaces and DANE client … John R Levine
- Re: [DNSOP] Prefixed name spaces and DANE client … John R Levine
- Re: [DNSOP] Prefixed name spaces and DANE client … Shane Kerr
- Re: [DNSOP] Prefixed name spaces and DANE client … Rob Austein
- Re: [DNSOP] Prefixed name spaces and DANE client … John Levine
- Re: [DNSOP] Prefixed name spaces and DANE client … Shumon Huque
- Re: [DNSOP] Prefixed name spaces and DANE client … Shumon Huque
- Re: [DNSOP] Prefixed name spaces and DANE client … John R Levine
- [DNSOP] Client/server vs. other models (was: Pref… Shane Kerr
- Re: [DNSOP] Prefixed name spaces and DANE client … James Cloos
- Re: [DNSOP] Prefixed name spaces and DANE client … John Levine