Re: [caldav] draft-desruisseaux-caldav-sched-09 / question concerning Security

Julian Reschke <julian.reschke@gmx.de> Mon, 07 February 2011 11:25 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BEF83A6DD1 for <caldav@core3.amsl.com>; Mon, 7 Feb 2011 03:25:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 nxvwJ38dBj85 for <caldav@core3.amsl.com>; Mon, 7 Feb 2011 03:25:56 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 2D4C53A6DD0 for <caldav@ietf.org>; Mon, 7 Feb 2011 03:25:55 -0800 (PST)
Received: (qmail invoked by alias); 07 Feb 2011 11:25:58 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.134]) [217.91.35.233] by mail.gmx.net (mp027) with SMTP; 07 Feb 2011 12:25:58 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/eaCgZ3Wne0JhW4TeKb8bhcDXgD5zQixoe53Mhgr 1iAKJZtifomqxN
Message-ID: <4D4FD6C3.8030206@gmx.de>
Date: Mon, 07 Feb 2011 12:25:55 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
References: <alpine.DEB.2.00.1102071123510.18675@softronics.hoeneisen.ch>
In-Reply-To: <alpine.DEB.2.00.1102071123510.18675@softronics.hoeneisen.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: draft-desruisseaux-caldav-sched@tools.ietf.org, caldav@ietf.org
Subject: Re: [caldav] draft-desruisseaux-caldav-sched-09 / question concerning Security
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2011 11:25:57 -0000

On 07.02.2011 11:56, Bernie Hoeneisen wrote:
> Dear authors of draft-desruisseaux-caldav-sched
>
> I was going through draft-desruisseaux-caldav-sched and came across
> something rather confusing:
>
> - In the Security Considerations of draft-desruisseaux-caldav-sched, the
> following is specified:
>
> "Servers and clients MUST use an HTTP connection protected with
> TLS as defined in [RFC2818] for all scheduling transactions."
>
> - RFC 2818 requires:
>
> "2.4. URI Format
> HTTP/TLS is differentiated from HTTP URIs by using the 'https'
> protocol identifier in place of the 'http' protocol identifier."
>
> - However, in the IANA Considerations section 16.1 (only) "http" is
> requested for IANA registration:
>
> "Applicable protocol: http"
>
>
> This appears rather contradictionary to me. Can you please enlight me
> regarding this matter? I assume that some correction (or at least
> clarification) is needed in draft-desruisseaux-caldav-sched.
> ...

Although the spec requires use of HTTPS, the base protocol is still 
"http". There is no separate header field registry for "https" (and that 
would really be bad).

BR, Julian