IETF Logo Mail Archive

Re: https at ietf.org

Joe Abley <jabley@hopcount.ca> Mon, 25 November 2013 15:44 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62AC51ADF63 for <ietf@ietfa.amsl.com>; Mon, 25 Nov 2013 07:44:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.001
X-Spam-Level:
X-Spam-Status: No, score=-4.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1_xnwyS5sPNJ for <ietf@ietfa.amsl.com>; Mon, 25 Nov 2013 07:44:49 -0800 (PST)
Received: from mail-qe0-x235.google.com (mail-qe0-x235.google.com [IPv6:2607:f8b0:400d:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 595241ADF61 for <ietf@ietf.org>; Mon, 25 Nov 2013 07:44:49 -0800 (PST)
Received: by mail-qe0-f53.google.com with SMTP id nc12so2474807qeb.40 for <ietf@ietf.org>; Mon, 25 Nov 2013 07:44:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=QmyaURIql8Rn3oGRITg9OETQY69fsKOEMRRP4/xLkmw=; b=QHNVUyyRAfSVd2B2BRUOL/wSZuuuLnvCpENtQRvQldCabSu1vgJAphw9XQFHGN1k7W J/rEgNYPT8CuTAokcfbn0vZM8QAVr8nYrgijNO5cZq8scPqYHPQ/1Ie3JwzKpiPJPRxH Ma4YUM4oOkfiFNImudN2vEfg2SKqh8tyJpmhE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=QmyaURIql8Rn3oGRITg9OETQY69fsKOEMRRP4/xLkmw=; b=ToUKJjWVo1CezFF+S33mncCj0NXbdiMAKKTyCwkygBBzxpfWlU0rNuvEQkvGvc981K t6LUY97nXVxPFz5YwQdiQPuGMJQPg4yPkg5znhf2scnly3KUCYWzjBwTNwX6O8on2DUn dfw/2C6qOoGprW2v2gztzUcF1GGzMkTYO+0t/MUj9bkqZ7lQd0R2O2pViz03ZU7XvtOT K2mjzopXIa6xnnwCuoNENwcnwypqJuOLFnTbdqtwMMKedbE3TviEVlf0JOU45WZh7qjs JF5OxrgiTRn/xE1pM0M+cMshOwvwVYhPxgtQAYLA/HeZv8mmGWmnJ63zxkSQjuFKurFt ItWg==
X-Gm-Message-State: ALoCoQnNS/Lf/56cbHvrua+2RzY+EpBGeDgtSooRdoQSbx3fEGrdhrRsQKOx1R6IEINnrcfJMvTc
X-Received: by 10.49.50.38 with SMTP id z6mr47501554qen.30.1385394289354; Mon, 25 Nov 2013 07:44:49 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:e15f:b548:8134:aa24? ([2001:4900:1042:1:e15f:b548:8134:aa24]) by mx.google.com with ESMTPSA id h2sm76962772qaf.10.2013.11.25.07.44.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 25 Nov 2013 07:44:48 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_569A681C-10B6-426A-8B2C-F6F380F91856"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Subject: Re: https at ietf.org
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <E760A0D0-57E1-44F5-AF0C-32F87E4C55FF@nominum.com>
Date: Mon, 25 Nov 2013 10:44:46 -0500
Message-Id: <90334355-B4AA-4975-AEF9-7ECEB123B4A3@hopcount.ca>
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> <527C2233.3030605@cis-india.org> <CAKHUCzzcNros1=O=D1zkEU1n+XdRcdYdgK2Hkik=AvxbuUJX3w@mail.gmail.com> <731D4B97-BC19-4AC8-BEF6-DA702073069A@standardstrack.com> <A1F7405B-CD8D-4DB8-9817-71F29AE14266@hopcount.ca> <E760A0D0-57E1-44F5-AF0C-32F87E4C55FF@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1822)
Cc: IETF-Discussion Discussion <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 25 Nov 2013 15:44:51 -0000

On 2013-11-25, at 10:42, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Nov 25, 2013, at 10:38 AM, Joe Abley <jabley@hopcount.ca> wrote:
>> Isn't this at least part of the motivation behind DANE?
>> 
>> (I realise DANE requires moving parts in the client and signatures in the published zone, but it seems odd that it hasn't been mentioned.)
> 
> Is the DNSSEC root key secure against National Security Letters?

I don't know. Sounds like a good question to ask ICANN.


Joe

v2.23.0 | Report a Bug | By Email