Re: [IPsec] #117: Hash and URL interop

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 25 November 2009 16:21 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 399233A6AC5 for <ipsec@core3.amsl.com>; Wed, 25 Nov 2009 08:21:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
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 EzUr3QIhzM2n for <ipsec@core3.amsl.com>; Wed, 25 Nov 2009 08:21:17 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 8F57C3A6AB4 for <ipsec@ietf.org>; Wed, 25 Nov 2009 08:21:17 -0800 (PST)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id nAPGL1Qi071247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 Nov 2009 09:21:02 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624081fc73309acb6c5@[10.20.30.158]>
In-Reply-To: <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDF88E016D@il-ex01.ad.checkpoint.com>
References: <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDA1213EA9@il-ex01.ad.checkpoint.com> <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDF88DFFE1@il-ex01.ad.checkpoint.com> <p06240863c731d54f3a70@[10.20.30.158]> <EA6311DE-97C3-4633-AAD2-C6C82946D162@checkpoint.com> <19213.13970.105797.850084@fireball.kivinen.iki.fi> <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDF88E016D@il-ex01.ad.checkpoint.com>
Date: Wed, 25 Nov 2009 08:20:59 -0800
To: Yaron Sheffer <yaronf@checkpoint.com>, Tero Kivinen <kivinen@iki.fi>, Yoav Nir <ynir@checkpoint.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: IPsecme WG <ipsec@ietf.org>
Subject: Re: [IPsec] #117: Hash and URL interop
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Nov 2009 16:21:18 -0000

At 4:44 PM +0200 11/25/09, Yaron Sheffer wrote:
>Can you live with:
>
>Implementations MUST support HTTP. The behavior of other URL methods is not currently specified, so such methods SHOULD NOT be used in the absence of a Standards Track document defining them.

No. There is no technical or interop reason for the SHOULD NOT. Everyone MUST support HTTP and the rest is up to them. If someone later specifies how to do FTP or whatever, that is fine.

--Paul Hoffman, Director
--VPN Consortium