IETF Logo Mail Archive

Re: https at ietf.org

Pranesh Prakash <pranesh@cis-india.org> Thu, 07 November 2013 23:29 UTC

Return-Path: <pranesh@cis-india.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDC3E21F9FC7 for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 15:29:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KEZtp6Mfxfz6 for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 15:29:10 -0800 (PST)
Received: from mail.cis-india.org (mail.cis-india.org [202.190.125.68]) by ietfa.amsl.com (Postfix) with ESMTP id AA66E21E8188 for <ietf@ietf.org>; Thu, 7 Nov 2013 15:28:57 -0800 (PST)
Received: from [192.168.1.210] (172-0-8-35.lightspeed.wlfrct.sbcglobal.net [172.0.8.35]) by mail.cis-india.org (Postfix) with ESMTPSA id 67DBDA7E8FD; Thu, 7 Nov 2013 23:28:55 +0000 (UTC)
Message-ID: <527C2233.3030605@cis-india.org>
Date: Thu, 07 Nov 2013 18:28:51 -0500
From: Pranesh Prakash <pranesh@cis-india.org>
Organization: Centre for Internet and Society
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>, Eric Burger <eburger@standardstrack.com>
Subject: Re: https at ietf.org
References: <CAHBU6ivbrk=NXgd4_5Upik+8H0AbHRy3kJnN=8fcK+Bz3pOV9Q@mail.gmail.com> <alpine.LRH.2.01.1311051733570.4200@egate.xpasc.com> <01P0FR4HDQNG00004G@mauve.mrochek.com> <CAHBU6ivZS33r4HHbCC391Ug9fMtZkJ3nojEeeqH5L+0+o3ZqGQ@mail.gmail.com> <01P0FU0CS96Q00004G@mauve.mrochek.com> <26C6A672-A5D2-44C4-B343-9CCE5E388348@standardstrack.com> <CAKHUCzzzT-0p89uT62zrxGqF1XACG+Ok7hNLcuTaDad7R7eCTQ@mail.gmail.com>
In-Reply-To: <CAKHUCzzzT-0p89uT62zrxGqF1XACG+Ok7hNLcuTaDad7R7eCTQ@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="RMQrqXwcdmqdmjMcokxKaxRumvQ6s5dlS"
Cc: IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 07 Nov 2013 23:29:14 -0000

Dave Cridland [2013-11-06 06:39]:
> Requiring HTTPS, particularly with reasonable cipher suites, might restrict
> use of from certain jurisdictions.

Could we have more concrete examples, please?  Would these be because of
export restrictions?[1]  For instance, are there any jurisdictions from
where users have to disable the HTTPS by default option in Gmail?

 [1]: http://www.cryptolaw.org/

v2.23.0 | Report a Bug | By Email