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

Cyrus Daboo <cyrus@daboo.name> Wed, 23 June 2010 19:20 UTC

Return-Path: <cyrus@daboo.name>
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 64C483A6B01 for <ietf@core3.amsl.com>; Wed, 23 Jun 2010 12:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level:
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[AWL=-1.555, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396]
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 PUzBMumfGRn6 for <ietf@core3.amsl.com>; Wed, 23 Jun 2010 12:20:37 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id 454EA3A6AFC for <ietf@ietf.org>; Wed, 23 Jun 2010 12:20:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id F40F617C739D0; Wed, 23 Jun 2010 15:20:44 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b24WXy0JPIH9; Wed, 23 Jun 2010 15:20:44 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id A6D6817C739C9; Wed, 23 Jun 2010 15:20:43 -0400 (EDT)
Date: Wed, 23 Jun 2010 15:20:40 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Patrik Fältström <paf@cisco.com>, Cullen Jennings <fluffy@cisco.com>
Subject: Re: Last Call: draft-daboo-srv-caldav (Use of SRV records for locating CalDAV and CardDAV services) to Proposed Standard
Message-ID: <923C2AD1F5768D40D940E71A@caldav.corp.apple.com>
In-Reply-To: <29086_1277189668_o5M6sRJn006182_307E2698-A9DF-4198-8FEF-C5DE7EE270DB@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>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size="1346"
Cc: 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 19:20:40 -0000

Hi Patrik,

--On June 22, 2010 8:54:22 AM +0200 Patrik Fältström <paf@cisco.com> 
wrote:

> I have together with Olaf Kolkman suggested a new RR type that I call URI
> that work similarly to what is described in this draft (regarding the
> owner of the RRSET), but a URI in the RDATA. It has been posted to the
> namedroppers list a few times...but maybe that has been wrong. Maybe Apps
> Area should have been notified about the work a bit more...
>
> Cyrus has asked a few questions about it, and maybe it is me that have
> not reached out to the Caldav people enough? I have tried to push it
> through via the DNS people in the IETF, but there have not been enough
> traction.

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.

-- 
Cyrus Daboo