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

Yaron Sheffer <yaronf@checkpoint.com> Tue, 24 November 2009 17:10 UTC

From: Yaron Sheffer <yaronf@checkpoint.com>
To: IPsecme WG <ipsec@ietf.org>
Date: Tue, 24 Nov 2009 19:09:24 +0200
Thread-Topic: #117: Hash and URL interop
Thread-Index: AcpY7LaHo4XNYlksQG2848du6xjjCQUOh/4Q
Message-ID: <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDF88DFFE1@il-ex01.ad.checkpoint.com>
References: <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDA1213EA9@il-ex01.ad.checkpoint.com>
In-Reply-To: <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDA1213EA9@il-ex01.ad.checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F9A6D26EB51614FBF9F81C0DA4CFEC801BDF88DFFE1ilex01adche_"
MIME-Version: 1.0
Subject: Re: [IPsec] #117: Hash and URL interop
Precedence: list

Resending. There may be value in other URL methods, just maybe, but OTOH they would confuse developers and add security issues.

________________________________
From: ipsec-bounces@ietf.org [mailto:ipsec-bounces@ietf.org] On Behalf Of Yaron Sheffer
Sent: Friday, October 30, 2009 1:18
To: IPsecme WG
Subject: [IPsec] #117: Hash and URL interop

To improve interoperability, allow only the "http" URL method. The current text (end of sec. 3.6) implies that any method is allowed, although HTTP MUST be supported.

Scanned by Check Point Total Security Gateway.

[IPsec] #117: Hash and URL interop Yaron Sheffer
[IPsec] #117: Hash and URL interop Tero Kivinen
Re: [IPsec] #117: Hash and URL interop Yaron Sheffer
Re: [IPsec] #117: Hash and URL interop Paul Hoffman
Re: [IPsec] #117: Hash and URL interop Yoav Nir
Re: [IPsec] #117: Hash and URL interop Tero Kivinen
Re: [IPsec] #117: Hash and URL interop Tero Kivinen
Re: [IPsec] #117: Hash and URL interop Yaron Sheffer
Re: [IPsec] #117: Hash and URL interop Tero Kivinen
Re: [IPsec] #117: Hash and URL interop Scott C Moonen
Re: [IPsec] #117: Hash and URL interop Paul Hoffman