Re: Last Call: draft-daboo-srv-caldav (Use of SRV records for locating CalDAV and CardDAV services) to Proposed Standard

Patrik Fältström <paf@cisco.com> Wed, 23 June 2010 20:07 UTC

Return-Path: <paf@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AEB028C0DD for <ietf@core3.amsl.com>; Wed, 23 Jun 2010 13:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.839
X-Spam-Level:
X-Spam-Status: No, score=-9.839 tagged_above=-999 required=5 tests=[AWL=0.460, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ByUqcAop4qWL for <ietf@core3.amsl.com>; Wed, 23 Jun 2010 13:07:39 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 0A11C3A69D0 for <ietf@ietf.org>; Wed, 23 Jun 2010 13:07:38 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-Files: PGP.sig : 186
X-IronPort-AV: E=Sophos; i="4.53,468,1272844800"; d="sig'?scan'208"; a="124740637"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 23 Jun 2010 20:07:46 +0000
Received: from dhcp-10-61-107-181.cisco.com (dhcp-10-61-107-181.cisco.com [10.61.107.181]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o5NK7jCv003978; Wed, 23 Jun 2010 20:07:46 GMT
Subject: Re: Last Call: draft-daboo-srv-caldav (Use of SRV records for locating CalDAV and CardDAV services) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Apple-Mail-227-516237757"
From: Patrik Fältström <paf@cisco.com>
In-Reply-To: <923C2AD1F5768D40D940E71A@caldav.corp.apple.com>
Date: Wed, 23 Jun 2010 22:07:44 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <856941CB-7C17-4919-9B4B-CBD3FF135C19@cisco.com>
References: <20100618155119.133353A6A8F@core3.amsl.com> <50BC2CEC-9EF6-4A0E-886F-6140552913F1@cisco.com> <29086_1277189668_o5M6sRJn006182_307E2698-A9DF-4198-8FEF-C5DE7EE270DB@cisco.com> <923C2AD1F5768D40D940E71A@caldav.corp.apple.com>
To: Cyrus Daboo <cyrus@daboo.name>
X-Pgp-Agent: GPGMail 1.2.3
X-Mailer: Apple Mail (2.1081)
Cc: Cullen Jennings <fluffy@cisco.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 20:07:40 -0000

On 23 jun 2010, at 21.20, Cyrus Daboo wrote:

> I did chat with a few server implementors about this and the feeling was SRV + .well-known is a good solution that can quickly be deployed. Some points:
> 
> 1) SRV's are very deployable today - a new RR will be harder to deploy.
> 
> 2) There is a push to support SRV's with other protocols (e.g. draft-daboo-srv-email for IMAP, POP3, and Submission) so from an operational standpoint its likely to be more common.
> 
> 3) .well-known is useful in the absence of any DNS records. i.e. if no SRV/URI were available, a client can still try auto-discovery by attempting an HTTP connection to the host (derived from user input) and the .well-known path.

Hmm...regarding the new RR, the only thing I can think of today is the need for some changes in the provisioning system from which one create the DNS zones. I do not know of any DNS code today that can not handle "unknown" DNS RR Types, but maybe I am wrong? I am though confused over (1) as this is 2010 and not 1998.

Regarding (3), I think it is sad people move redirects and lookups and functionality to be on top of HTTP instead of IP. And I do not understand "in the absence of DNS"...that is an interesting situation ;-) Specifically to use that as the foundation for the architecture to use for calendaring, that is -- I hope -- one of the more fundamental applications on the Internet.

A new version of my draft I promised today, but due to this security consideration discussion, it is now delayed yet another day.

And yes, I will do the job of releasing a new version although there will continue to not be any interest of using it. :-)

Or maybe I should just push it through, although for calendaring draft-daboo-srv-caldav will be used. Hmm... I do not want to be problematic here.

   Patrik