Re: [Geopriv] The 's' in HELD
Tim Thome <tthome@kyocera-wireless.com> Mon, 05 May 2008 13:54 UTC
Return-Path: <geopriv-bounces@ietf.org>
X-Original-To: geopriv-archive@megatron.ietf.org
Delivered-To: ietfarch-geopriv-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A99828C198; Mon, 5 May 2008 06:54:26 -0700 (PDT)
X-Original-To: geopriv@core3.amsl.com
Delivered-To: geopriv@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B83303A6AA5 for <geopriv@core3.amsl.com>; Wed, 30 Apr 2008 11:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level:
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
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 tmPAEKdGbf7b for <geopriv@core3.amsl.com>; Wed, 30 Apr 2008 11:26:56 -0700 (PDT)
Received: from lanai.intra.kyocera-wireless.com (lanai.kyocera-wireless.com [206.169.67.134]) by core3.amsl.com (Postfix) with ESMTP id 536473A6A53 for <geopriv@ietf.org>; Wed, 30 Apr 2008 11:26:52 -0700 (PDT)
Received: from [192.168.1.100] (ktrcdev.intra.kyocera-wireless.com [172.20.16.211]) by lanai.intra.kyocera-wireless.com (8.13.7+Sun/8.12.3) with ESMTP id m3UIQirf011636; Wed, 30 Apr 2008 11:26:44 -0700 (PDT)
Message-ID: <4818B9DF.20402@kyocera-wireless.com>
Date: Wed, 30 Apr 2008 11:26:39 -0700
From: Tim Thome <tthome@kyocera-wireless.com>
Organization: Kyocera Wireless Corporation
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Richard Barnes <rbarnes@bbn.com>
References: <E51D5B15BFDEFD448F90BDD17D41CFF10441BD76@AHQEX1.andrew.com> <4818B2F8.6090506@bbn.com>
In-Reply-To: <4818B2F8.6090506@bbn.com>
X-Mailman-Approved-At: Mon, 05 May 2008 06:54:26 -0700
Cc: GEOPRIV <geopriv@ietf.org>, Mary Barnes <mary.barnes@nortel.com>, "Thomson, Martin" <Martin.Thomson@andrew.com>
Subject: Re: [Geopriv] The 's' in HELD
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: geopriv-bounces@ietf.org
Errors-To: geopriv-bounces@ietf.org
Richard raises a good point, as devices may have requirements for emergency contexts... including support for devices that do not have a business relationship with the network access and/or service provider. Should this context be handled separately? Thanks! Tim Richard Barnes wrote: > Is TLS really used for every HELD transaction, as opposed to being > available for every transaction? This seems to be a deviation from the > normal pattern for Internet protocols to have a base protocol without > TLS and an (mandatory) option to use TLS as desired. More importantly, > it seems like TLS might be undesirable in some circumstances, e.g., > emergency calling. > > Is there a reason for this extra-strong requirement? > > --RB > > > > Thomson, Martin wrote: > >> I missed this in the changes for -06. Please forgive my ignorance, but >> I wasn't there at -71 and it appears that only the conclusion was >> captured, not the rationale. The minutes focus on whether there should >> be a URI scheme or not, but make what seems (to me) to be a logical >> leap: >> >> Question: Does this HELD: scheme require TLS? Ans: Yes. Then >> it needs >> to be a HELDS: scheme. >> >> I don't believe that the letter 's' addresses "concerns over referential >> integrity" as stated by the held-06 change-log. So can anyone justify >> the above statement? Is there some IETF guideline I don't know of that >> states that URI schemes for protocols that use TLS have an extra 's'? >> >> Cheers, >> Martin >> >> ------------------------------------------------------------------------------------------------ >> This message is for the designated recipient only and may >> contain privileged, proprietary, or otherwise private information. >> If you have received it in error, please notify the sender >> immediately and delete the original. Any unauthorized use of >> this email is prohibited. >> ------------------------------------------------------------------------------------------------ >> [mf2] >> >> >> -- Tim Thome - <mailto:tthome@kyocera-wireless.com> Senior Staff Engineer Technology Development Kyocera Wireless Corp. San Diego, CA _______________________________________________ Geopriv mailing list Geopriv@ietf.org https://www.ietf.org/mailman/listinfo/geopriv
- [Geopriv] The 's' in HELD Thomson, Martin
- Re: [Geopriv] The 's' in HELD Eric Rescorla
- Re: [Geopriv] The 's' in HELD Randall Gellens
- Re: [Geopriv] The 's' in HELD Richard Barnes
- Re: [Geopriv] The 's' in HELD Richard Barnes
- Re: [Geopriv] The 's' in HELD Mary Barnes
- Re: [Geopriv] The 's' in HELD Richard Barnes
- Re: [Geopriv] The 's' in HELD Thomson, Martin
- Re: [Geopriv] The 's' in HELD Tim Thome
- Re: [Geopriv] The 's' in HELD Winterbottom, James