[DNSOP] update on draft-jabley-dnssec-trust-anchor

"Joe Abley" <jabley@hopcount.ca> Sat, 31 October 2015 20:50 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB5E1A9071 for <dnsop@ietfa.amsl.com>; Sat, 31 Oct 2015 13:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] 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 b3gZqTbjSdCh for <dnsop@ietfa.amsl.com>; Sat, 31 Oct 2015 13:50:27 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB3CE1B2DFC for <dnsop@ietf.org>; Sat, 31 Oct 2015 13:50:27 -0700 (PDT)
Received: by iodd200 with SMTP id d200so111047594iod.0 for <dnsop@ietf.org>; Sat, 31 Oct 2015 13:50:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:to:cc:subject:date:message-id:mime-version:content-type; bh=3WJ5Znt+D5qWQpNIRog0SnSMeb8uAUB55SjG5DWk4tY=; b=UN+9fcOw6BJ8g3t7ZLawb0jCHKZlXi1CTRnfinMJl5P3OWmzkEyDGjk1bpbNRJgFSX T9YBEFBXj0He/LHqipPSXII59r8cpYYHLijIH0EZD9dK9GArrkJG4tA1gAughr6ZpG1Y GZ3BIXSsAOvlfZxBtMLXXR/dP6SqyUaPrxapc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-type; bh=3WJ5Znt+D5qWQpNIRog0SnSMeb8uAUB55SjG5DWk4tY=; b=G7tmJHuTlzoGiVLg+gIJ8AAiLpfCLpLZilIBUdFdSqXnG1hPPh9mnXtaIhlsj896rj 6B2vuZT9nIhPBO+eJa4eivLl/NduCOiq+Iwt98Yj6yN1xY74TuzbmHGzOKSu89xNY9Ik JU5Dxy6LcN7/QmKXeaCv8+CMHMPF976mm3fsDjM8yBgwRoMXsC4ztb+zf073zwCDwSpU qY2MAmOM+WFV/I7JAFuZsIEiVls8AG4cLnojDqeHYGmVDrSfM3nLUQFc50mp17acqCMf MPTaR4bDH/vQa7odh3qBKFi529/uMr8JfycHETZ8WlI8D5fobgzcKEn+8AA/Av7Kjjid vPNA==
X-Gm-Message-State: ALoCoQk9VV0IB8pYxsw6c6Xb1jr99LojdoSZ7LLj3BP4Y20v9lVG7sO0BpgEWKdUuW7fwSSNRCLE
X-Received: by 10.107.137.66 with SMTP id l63mr15913411iod.112.1446324626739; Sat, 31 Oct 2015 13:50:26 -0700 (PDT)
Received: from [199.212.90.113] (24-212-157-244.cable.teksavvy.com. [24.212.157.244]) by smtp.gmail.com with ESMTPSA id rs2sm3194406igb.9.2015.10.31.13.50.26 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 31 Oct 2015 13:50:26 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
To: dnsop WG <dnsop@ietf.org>
Date: Sat, 31 Oct 2015 16:50:26 -0400
Message-ID: <846193F8-1A47-4D21-97A4-DAF306920417@hopcount.ca>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.2r5141)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/x7JhFbsgmYoSDp0-nqIbQQ7CrLY>
Cc: Nevil Brownlee <rfc-ise@rfc-editor.org>
Subject: [DNSOP] update on draft-jabley-dnssec-trust-anchor
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2015 20:50:29 -0000

Hi,

Just a clarification to the wg, since I think my earlier note on this 
was buried in some long thread -- the authors of 
draft-jabley-dnssec-trust-anchor have taken it to the ISE and it has 
been accepted as a draft on the independent stream.

The next step in the process is for some people to review it. Please 
feel free to do that and send your opinions to rfc-ise@rfc-editor.org, 
ideally cc'ing the authors (directly or via this list) so that we know 
what is happening.

If there are changes proposed as part of the review we will follow up 
with edits and submit them, per the usual process.

Thanks all,


Joe