
From jabley@hopcount.ca  Thu Jun  2 03:03:59 2011
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3000DE076E for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 03:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.975
X-Spam-Level: 
X-Spam-Status: No, score=-101.975 tagged_above=-999 required=5 tests=[AWL=-0.576, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, J_CHICKENPOX_44=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6MrDzykj5om for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 03:03:51 -0700 (PDT)
Received: from monster.hopcount.ca (monster.hopcount.ca [IPv6:2001:4900:1:392:213:20ff:fe1b:3bfe]) by ietfa.amsl.com (Postfix) with ESMTP id B04D5E0782 for <dnsop@ietf.org>; Thu,  2 Jun 2011 03:02:53 -0700 (PDT)
Received: from [196.200.216.217] (helo=wifi-216-217.mtg.afnog.org) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1QS4jh-0001Aw-4i for dnsop@ietf.org; Thu, 02 Jun 2011 10:02:51 +0000
From: Joe Abley <jabley@hopcount.ca>
Content-Type: multipart/mixed; boundary=Apple-Mail-41-136749060
Date: Thu, 2 Jun 2011 13:02:27 +0300
Message-Id: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>
To: IETF DNSOP WG <dnsop@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-SA-Exim-Connect-IP: 196.200.216.217
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
Subject: [DNSOP] watching for signature expiration in zones you don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 10:03:59 -0000

--Apple-Mail-41-136749060
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi all,

I've been poking about a bit in other signed zones looking for impending =
signature expirations. I've been doing this mainly because we sign a lot =
of zones and have had at least one accident in the past, but this also =
seems like something that is worth knowing if you're the operator of a =
validator and you want to be able to prepare for impending signature =
expiration in zones that are otherwise going to cause you helpdesk =
problems.

See attached script for an example of what I have been doing.

I have realised, however, that I can't tell whether a signature that is =
(say) going to expire in under three days is a cause for concern, or =
whether it's normal operations and something I should expect to be =
replaced as part of normal operations.

This boils down to there being no way for a zone operator to publish =
their normal signature replacement policy in a way that I can obtain in =
a simple way. Sometimes that information is present in a DPS, but often =
there is no DPS to be found, sometimes there's a DPS but it doesn't =
contain that level of detail, and in any case this is all far too manual =
for an automated check script.

Is there perhaps value in finding a mechanism by which zone operators =
can publish information in their zones which gives guidance as to what =
the normal limits for signature expiration ought to be?

  $ORIGIN HOPCOUNT.CA.
  @ RRSIGPOLICY DNSKEY <min planned remaining signature validity> <max =
planned remaining signature validity>
  @ RRSIGPOLICY SOA ....

or something?



Joe

wifi-216-217:~]% ./sigexpire.sh
2011-06-01 15:30:41 UTC ---------- right now =
-----------------------------
2011-06-02 15:30:41 UTC ---------- 1 day from now =
------------------------
2011-06-03 15:30:41 UTC ---------- 2 days from now =
-----------------------
2011-06-03 18:25:33 UTC signature over COM. DNSKEY expires
2011-06-04 15:30:41 UTC ---------- 3 days from now =
-----------------------
2011-06-04 18:02:19 UTC signature over VIP.ICANN.ORG. DNSKEY expires
2011-06-04 18:02:19 UTC signature over VIP.ICANN.ORG. DNSKEY expires
2011-06-05 15:30:41 UTC ---------- 4 days from now =
-----------------------
2011-06-05 16:00:23 UTC signature over GOV. DNSKEY expires
2011-06-06 04:00:23 UTC signature over GOV. SOA expires
2011-06-06 15:30:41 UTC ---------- 5 days from now =
-----------------------
2011-06-06 16:38:57 UTC signature over NET. DNSKEY expires
2011-06-06 19:28:05 UTC signature over EDU. DNSKEY expires
2011-06-07 06:21:17 UTC signature over DK. DNSKEY expires
2011-06-07 08:00:01 UTC signature over EU. DNSKEY expires
2011-06-07 08:00:01 UTC signature over EU. DNSKEY expires
2011-06-07 08:00:01 UTC signature over EU. DNSKEY expires
2011-06-07 09:09:09 UTC signature over CH. DNSKEY expires
2011-06-07 09:09:09 UTC signature over LI. DNSKEY expires
2011-06-07 15:30:41 UTC ---------- 6 days from now =
-----------------------
2011-06-08 00:00:00 UTC signature over . SOA expires
2011-06-08 00:00:00 UTC signature over ARPA. SOA expires
2011-06-08 06:00:00 UTC signature over DE. SOA expires
2011-06-08 09:00:00 UTC signature over BR. SOA expires
2011-06-08 09:02:13 UTC signature over EU. SOA expires
2011-06-08 09:02:13 UTC signature over EU. SOA expires
2011-06-08 09:16:26 UTC signature over VIP.ICANN.ORG. SOA expires
2011-06-08 11:23:03 UTC signature over BE. DNSKEY expires
2011-06-08 14:34:51 UTC signature over XN--DEBA0AD. DNSKEY expires
2011-06-08 14:38:20 UTC signature over XN--0ZWM56D. SOA expires
2011-06-08 14:38:54 UTC signature over IANA.ORG. SOA expires
2011-06-08 14:38:54 UTC signature over IP6-SERVERS.ARPA. DNSKEY expires
2011-06-08 14:38:54 UTC signature over XN--G6W251D. DNSKEY expires
2011-06-08 14:50:18 UTC signature over ICANN.ORG. SOA expires
2011-06-08 14:57:44 UTC signature over IP6.ARPA. DNSKEY expires
2011-06-08 14:59:29 UTC signature over XN--9T4B11YI5A. SOA expires
2011-06-08 15:12:05 UTC signature over URI.ARPA. SOA expires
2011-06-08 15:14:51 UTC signature over COM. SOA expires
2011-06-08 15:15:06 UTC signature over EDU. SOA expires
2011-06-08 15:18:24 UTC signature over NET. SOA expires
2011-06-08 15:23:13 UTC signature over XN--ZCKZAH. SOA expires
2011-06-08 15:30:41 UTC ---------- 7 days from now =
-----------------------
2011-06-08 15:40:41 UTC signature over IN-ADDR-SERVERS.ARPA. SOA expires
2011-06-08 16:02:53 UTC signature over IN-ADDR.ARPA. SOA expires
2011-06-08 16:02:53 UTC signature over XN--HLCJ6AYA9ESC7A. SOA expires
2011-06-08 16:22:55 UTC signature over XN--HGBK6AJ7F53BBA. DNSKEY =
expires
2011-06-08 17:12:02 UTC signature over URI.ARPA. DNSKEY expires
2011-06-08 17:47:06 UTC signature over URN.ARPA. SOA expires
2011-06-08 18:26:30 UTC signature over DK. SOA expires
2011-06-08 18:29:41 UTC signature over XN--JXALPDLP. DNSKEY expires
2011-06-08 18:46:03 UTC signature over IRIS.ARPA. SOA expires
2011-06-08 19:07:26 UTC signature over URN.ARPA. DNSKEY expires
2011-06-08 19:58:19 UTC signature over IANA.ORG. DNSKEY expires
2011-06-08 20:14:20 UTC signature over IN-ADDR-SERVERS.ARPA. DNSKEY =
expires
2011-06-08 20:19:01 UTC signature over XN--KGBECHTV. SOA expires
2011-06-08 20:23:40 UTC signature over XN--DEBA0AD. SOA expires
2011-06-08 21:00:28 UTC signature over XN--11B5BS3A9AJ6G. SOA expires
2011-06-08 21:23:22 UTC signature over XN--JXALPDLP. SOA expires
2011-06-08 21:28:57 UTC signature over IP6.ARPA. SOA expires
2011-06-08 21:52:46 UTC signature over XN--11B5BS3A9AJ6G. DNSKEY expires
2011-06-08 22:06:53 UTC signature over IRIS.ARPA. DNSKEY expires
2011-06-08 22:26:09 UTC signature over XN--ZCKZAH. DNSKEY expires
2011-06-08 23:54:38 UTC signature over ICANN.ORG. DNSKEY expires
2011-06-08 23:58:18 UTC signature over XN--KGBECHTV. DNSKEY expires
2011-06-08 23:59:30 UTC signature over XN--80AKHBYKNJ4F. SOA expires
2011-06-09 00:24:19 UTC signature over IN-ADDR.ARPA. DNSKEY expires
2011-06-09 00:24:19 UTC signature over XN--HLCJ6AYA9ESC7A. DNSKEY =
expires
2011-06-09 00:32:02 UTC signature over IP6-SERVERS.ARPA. SOA expires
2011-06-09 00:32:02 UTC signature over XN--G6W251D. SOA expires
2011-06-09 01:25:10 UTC signature over XN--80AKHBYKNJ4F. DNSKEY expires
2011-06-09 01:28:57 UTC signature over XN--0ZWM56D. DNSKEY expires
2011-06-09 01:44:31 UTC signature over XN--9T4B11YI5A. DNSKEY expires
2011-06-09 02:16:57 UTC signature over XN--HGBK6AJ7F53BBA. SOA expires
2011-06-09 04:47:12 UTC signature over MUSEUM. DNSKEY expires
2011-06-09 04:47:12 UTC signature over MUSEUM. DNSKEY expires
2011-06-09 05:53:12 UTC signature over CAT. DNSKEY expires
2011-06-09 15:30:42 UTC ---------- 8 days from now =
-----------------------
2011-06-10 09:00:00 UTC signature over BR. DNSKEY expires
2011-06-10 15:30:42 UTC ---------- 9 days from now =
-----------------------
2011-06-11 09:01:45 UTC signature over BE. SOA expires
2011-06-11 20:02:44 UTC signature over SE. DNSKEY expires
2011-06-12 17:32:10 UTC signature over CZ. DNSKEY expires
2011-06-13 04:02:44 UTC signature over SE. DNSKEY expires
2011-06-13 04:18:16 UTC signature over CZ. DNSKEY expires
2011-06-13 09:43:58 UTC signature over CZ. SOA expires
2011-06-14 04:35:53 UTC signature over LU. DNSKEY expires
2011-06-14 08:20:20 UTC signature over FI. DNSKEY expires
2011-06-14 10:39:30 UTC signature over SE. SOA expires
2011-06-14 17:10:30 UTC signature over LU. SOA expires
2011-06-14 23:18:40 UTC signature over NL. DNSKEY expires
2011-06-14 23:59:59 UTC signature over . DNSKEY expires
2011-06-14 23:59:59 UTC signature over ARPA. DNSKEY expires
2011-06-15 04:48:19 UTC signature over UK. SOA expires
2011-06-15 06:53:11 UTC signature over CAT. SOA expires
2011-06-15 10:48:19 UTC signature over UK. DNSKEY expires
2011-06-15 11:47:13 UTC signature over MUSEUM. SOA expires
2011-06-15 15:45:48 UTC signature over ASIA. DNSKEY expires
2011-06-15 15:45:48 UTC signature over ASIA. DNSKEY expires
2011-06-15 15:46:29 UTC signature over ME. DNSKEY expires
2011-06-15 15:46:29 UTC signature over ME. DNSKEY expires
2011-06-15 15:47:16 UTC signature over AG. DNSKEY expires
2011-06-15 15:47:16 UTC signature over AG. DNSKEY expires
2011-06-15 15:49:25 UTC signature over INFO. DNSKEY expires
2011-06-15 15:49:25 UTC signature over INFO. DNSKEY expires
2011-06-15 15:56:25 UTC signature over ORG. DNSKEY expires
2011-06-15 15:56:25 UTC signature over ORG. DNSKEY expires
2011-06-15 16:05:05 UTC signature over IN. DNSKEY expires
2011-06-15 16:05:05 UTC signature over IN. DNSKEY expires
2011-06-15 16:30:31 UTC signature over BZ. DNSKEY expires
2011-06-15 16:30:31 UTC signature over BZ. DNSKEY expires
2011-06-15 16:36:33 UTC signature over VC. DNSKEY expires
2011-06-15 16:36:33 UTC signature over VC. DNSKEY expires
2011-06-15 17:12:20 UTC signature over HN. DNSKEY expires
2011-06-15 17:12:20 UTC signature over HN. DNSKEY expires
2011-06-15 18:36:55 UTC signature over MN. DNSKEY expires
2011-06-15 18:36:55 UTC signature over MN. DNSKEY expires
2011-06-15 20:15:17 UTC signature over FI. SOA expires
2011-06-15 21:51:38 UTC signature over SC. DNSKEY expires
2011-06-15 21:51:38 UTC signature over SC. DNSKEY expires
2011-06-15 23:32:32 UTC signature over LC. DNSKEY expires
2011-06-15 23:32:32 UTC signature over LC. DNSKEY expires
2011-06-15 23:54:39 UTC signature over NL. SOA expires
2011-06-16 02:13:38 UTC signature over GI. DNSKEY expires
2011-06-16 02:13:38 UTC signature over GI. DNSKEY expires
2011-06-16 12:00:00 UTC signature over DE. DNSKEY expires
2011-06-18 03:44:21 UTC signature over AM. DNSKEY expires
2011-06-18 03:44:21 UTC signature over AM. DNSKEY expires
2011-06-21 20:13:06 UTC signature over LI. DNSKEY expires
2011-06-21 22:31:39 UTC signature over CH. DNSKEY expires
2011-06-22 08:34:51 UTC signature over LC. SOA expires
2011-06-22 11:27:43 UTC signature over SC. SOA expires
2011-06-22 11:56:35 UTC signature over VC. SOA expires
2011-06-22 14:06:18 UTC signature over MN. SOA expires
2011-06-22 14:28:51 UTC signature over HN. SOA expires
2011-06-22 14:55:24 UTC signature over BZ. SOA expires
2011-06-22 14:58:49 UTC signature over GI. SOA expires
2011-06-22 15:11:25 UTC signature over AG. SOA expires
2011-06-22 15:15:57 UTC signature over IN. SOA expires
2011-06-22 15:17:51 UTC signature over ASIA. SOA expires
2011-06-22 15:18:25 UTC signature over ME. SOA expires
2011-06-22 15:18:32 UTC signature over INFO. SOA expires
2011-06-22 15:21:45 UTC signature over ORG. SOA expires
2011-06-22 18:42:09 UTC signature over LA. SOA expires
2011-06-24 00:21:43 UTC signature over BIZ. DNSKEY expires
2011-06-24 00:21:43 UTC signature over BIZ. DNSKEY expires
2011-06-24 00:21:43 UTC signature over BIZ. DNSKEY expires
2011-06-24 02:08:36 UTC signature over US. DNSKEY expires
2011-06-24 02:08:36 UTC signature over US. DNSKEY expires
2011-06-24 13:00:00 UTC signature over CO. DNSKEY expires
2011-06-24 13:00:00 UTC signature over CO. DNSKEY expires
2011-06-24 13:00:00 UTC signature over CO. DNSKEY expires
2011-06-24 13:45:59 UTC signature over LA. DNSKEY expires
2011-06-25 10:17:03 UTC signature over XN--FZC2C9E2C. SOA expires
2011-06-25 10:17:38 UTC signature over XN--XKC2AL3HYE2A. SOA expires
2011-06-25 19:59:45 UTC signature over LA. DNSKEY expires
2011-06-26 18:41:02 UTC signature over TH. DNSKEY expires
2011-06-26 18:41:02 UTC signature over TH. DNSKEY expires
2011-06-26 18:41:02 UTC signature over TH. SOA expires
2011-06-27 17:45:03 UTC signature over JP. DNSKEY expires
2011-06-27 17:45:03 UTC signature over JP. SOA expires
2011-06-28 06:04:02 UTC signature over NA. DNSKEY expires
2011-06-28 06:04:02 UTC signature over NA. DNSKEY expires
2011-06-28 09:06:45 UTC signature over BE. DNSKEY expires
2011-06-28 09:06:45 UTC signature over BE. DNSKEY expires
2011-06-28 09:06:45 UTC signature over BE. DNSKEY expires
2011-06-29 05:46:24 UTC signature over AC. DNSKEY expires
2011-06-29 05:46:24 UTC signature over AC. DNSKEY expires
2011-06-29 05:46:24 UTC signature over AC. SOA expires
2011-06-29 05:46:24 UTC signature over IO. DNSKEY expires
2011-06-29 05:46:24 UTC signature over IO. DNSKEY expires
2011-06-29 05:46:24 UTC signature over IO. SOA expires
2011-06-29 05:46:24 UTC signature over SH. DNSKEY expires
2011-06-29 05:46:24 UTC signature over SH. DNSKEY expires
2011-06-29 05:46:24 UTC signature over SH. SOA expires
2011-06-29 05:46:24 UTC signature over TM. DNSKEY expires
2011-06-29 05:46:24 UTC signature over TM. DNSKEY expires
2011-06-29 05:46:24 UTC signature over TM. SOA expires
2011-06-30 10:29:51 UTC signature over LK. SOA expires
2011-07-01 03:01:01 UTC signature over PR. DNSKEY expires
2011-07-01 03:01:01 UTC signature over PR. DNSKEY expires
2011-07-01 03:17:05 UTC signature over NU. DNSKEY expires
2011-07-01 04:30:04 UTC signature over HOPCOUNT.CA. DNSKEY expires
2011-07-01 04:30:04 UTC signature over HOPCOUNT.CA. DNSKEY expires
2011-07-01 04:30:04 UTC signature over HOPCOUNT.CA. SOA expires
2011-07-01 06:01:01 UTC signature over PR. SOA expires
2011-07-01 06:04:01 UTC signature over NA. SOA expires
2011-07-01 06:17:05 UTC signature over NU. SOA expires
2011-07-01 07:00:07 UTC signature over PT. SOA expires
2011-07-01 07:53:19 UTC signature over AUTOMAGIC.ORG. DNSKEY expires
2011-07-01 07:53:19 UTC signature over AUTOMAGIC.ORG. DNSKEY expires
2011-07-01 07:53:19 UTC signature over AUTOMAGIC.ORG. SOA expires
2011-07-01 08:00:11 UTC signature over BG. SOA expires
2011-07-01 08:45:04 UTC signature over AM. SOA expires
2011-07-01 10:00:19 UTC signature over E164.ARPA. DNSKEY expires
2011-07-01 10:00:19 UTC signature over E164.ARPA. SOA expires
2011-07-01 12:00:05 UTC signature over PT. DNSKEY expires
2011-07-01 12:00:05 UTC signature over PT. DNSKEY expires
2011-07-01 12:12:12 UTC signature over GR. DNSKEY expires
2011-07-01 12:12:12 UTC signature over GR. DNSKEY expires
2011-07-01 12:12:12 UTC signature over GR. SOA expires
2011-07-01 13:00:13 UTC signature over BG. DNSKEY expires
2011-07-01 13:00:13 UTC signature over BG. DNSKEY expires
2011-07-01 13:34:40 UTC signature over CH. SOA expires
2011-07-01 13:59:07 UTC signature over LI. SOA expires
2011-07-01 15:14:32 UTC signature over BIZ. SOA expires
2011-07-01 15:14:50 UTC signature over CO. SOA expires
2011-07-01 15:19:33 UTC signature over US. SOA expires
2011-07-16 13:30:20 UTC signature over CL. SOA expires
2011-07-16 13:30:21 UTC signature over CL. DNSKEY expires
2011-07-29 12:16:31 UTC signature over FR. DNSKEY expires
2011-07-29 12:16:31 UTC signature over FR. DNSKEY expires
2011-07-29 12:17:36 UTC signature over PM. DNSKEY expires
2011-07-29 12:17:36 UTC signature over PM. DNSKEY expires
2011-07-29 12:17:36 UTC signature over PM. SOA expires
2011-07-29 12:17:37 UTC signature over RE. DNSKEY expires
2011-07-29 12:17:37 UTC signature over RE. DNSKEY expires
2011-07-29 12:17:37 UTC signature over TF. DNSKEY expires
2011-07-29 12:17:37 UTC signature over TF. DNSKEY expires
2011-07-29 12:17:37 UTC signature over TF. SOA expires
2011-07-29 12:17:39 UTC signature over WF. DNSKEY expires
2011-07-29 12:17:39 UTC signature over WF. DNSKEY expires
2011-07-29 12:17:39 UTC signature over WF. SOA expires
2011-07-29 12:17:39 UTC signature over YT. DNSKEY expires
2011-07-29 12:17:39 UTC signature over YT. DNSKEY expires
2011-07-29 12:17:39 UTC signature over YT. SOA expires
2011-07-30 06:29:31 UTC signature over JP. DNSKEY expires
2011-07-31 05:00:04 UTC signature over RE. SOA expires
2011-07-31 09:00:06 UTC signature over FR. SOA expires
2011-08-11 14:37:10 UTC signature over CL. DNSKEY expires
2011-08-15 00:00:00 UTC signature over LK. DNSKEY expires
2011-08-15 00:00:00 UTC signature over LK. DNSKEY expires
2011-08-15 00:00:00 UTC signature over XN--FZC2C9E2C. DNSKEY expires
2011-08-15 00:00:00 UTC signature over XN--FZC2C9E2C. DNSKEY expires
2011-08-15 00:00:00 UTC signature over XN--XKC2AL3HYE2A. DNSKEY expires
2011-08-15 00:00:00 UTC signature over XN--XKC2AL3HYE2A. DNSKEY expires
2011-08-28 13:06:23 UTC signature over MY. DNSKEY expires
2011-08-28 13:06:23 UTC signature over MY. DNSKEY expires
2011-08-30 05:06:22 UTC signature over MY. SOA expires
2011-12-31 23:59:59 UTC signature over KG. DNSKEY expires
2011-12-31 23:59:59 UTC signature over KG. DNSKEY expires
2011-12-31 23:59:59 UTC signature over KG. SOA expires
[wifi-216-217:~]%


--Apple-Mail-41-136749060
Content-Disposition: attachment;
	filename=sigexpire.sh
Content-Type: application/octet-stream;
	name="sigexpire.sh"
Content-Transfer-Encoding: 7bit

#!/bin/sh
#
# Report on when SOA and DNSKEY signatures for various zones expire.

# how many days in the future we categorise
days=10

# giant pipeline begins! how exciting.

# zones to check (don't worry about duplicates)
(
  # the root zone
  echo "."

  # TLD zones and ARPA children from xfr.cjr.dns.icann.org and
  # xfr.lax.dns.icann.org
  for xfr in xfr.cjr.dns.icann.org xfr.lax.dns.icann.org; do
    for zone in arpa. .; do
      dig @${xfr} ${zone} axfr  2>/dev/null | \
        awk '/[[:space:]]+IN[[:space:]]+NS[[:space:]]+/ { print $1;} '
    done
  done

  # jabley zones
  echo "automagic.org"
  echo "hopcount.ca"

  # icann zones
  echo "iana.org"
  echo "icann.org"
  echo "vip.icann.org"
) | \
  awk '/\.$/ { print toupper($0); }
    /[a-zA-Z0-9]$/ { print toupper($0) "."; }' | \
  sort | \
  uniq | (
    while read zone; do
      signed=""
      for rrset in SOA DNSKEY; do
        dig ${zone} ${rrset} +dnssec +noall +answer | \
          awk '($4 == "RRSIG") { print; } {}' | \
          while read rrsig; do
            expiry=$(echo "${rrsig}" | awk '{ print $9; }')
            echo "${expiry} ${zone} ${rrset}"
          done
      done
    done

    for d in $(jot ${days} 0); do
      echo "$(date -u -v+${d}d +%Y%m%d%H%M%S) ${d} --"
    done
  ) | \
    sort -n | \
    awk -v days=${days} '
     function prettydate(sigtime) {
       return sprintf("%s-%s-%s %s:%s:%s UTC", \
         substr(sigtime, 1, 4), \
         substr(sigtime, 5, 2), \
         substr(sigtime, 7, 2), \
         substr(sigtime, 9, 2), \
         substr(sigtime, 11, 2), \
         substr(sigtime, 13, 2));
     }

     function rep(s, n) {
       rep_s = "";
       for (rep_i = 0; rep_i < n; rep_i++)
         rep_s = rep_s s;
       return rep_s;
     }

     function marksection(s) {
       return sprintf("%s %s %s", rep("-", 10), s, rep("-", 38 - length(s)));
     }

     {
        expiry = $1;
        zone = $2;
        rrset = $3;

        if (rrset == "--") {
          if (zone == 0) {
            printf "%s %s\n", prettydate(expiry), marksection("right now");
          } else {
            printf "%s %s\n", \
              prettydate(expiry), \
              marksection(zone " day" (zone == 1 ? "" : "s") " from now");
          }
        } else {
          printf "%s signature over %s %s expires\n", \
            prettydate(expiry), zone, rrset;
        }
        sigs++;
      }'


--Apple-Mail-41-136749060--

From joao@bondis.org  Thu Jun  2 03:18:04 2011
Return-Path: <joao@bondis.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98553E0751 for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 03:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.777
X-Spam-Level: 
X-Spam-Status: No, score=-0.777 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_34=0.6, J_CHICKENPOX_44=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Ma0J5AwoGWL for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 03:18:03 -0700 (PDT)
Received: from smtp1.bondis.org (voyager.c-l-i.net [194.176.119.229]) by ietfa.amsl.com (Postfix) with ESMTP id 625F6E0738 for <dnsop@ietf.org>; Thu,  2 Jun 2011 03:17:44 -0700 (PDT)
Received: from [192.168.2.36] (82.158.254.126.dyn.user.ono.com [82.158.254.126]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.bondis.org (Postfix) with ESMTPSA id 14DE31AB301; Thu,  2 Jun 2011 10:17:42 +0000 (UTC)
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>
In-Reply-To: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
Message-Id: <F3F4A1E6-649A-47FB-8863-161C0B3B32B1@bondis.org>
Content-Transfer-Encoding: quoted-printable
From: =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
Date: Thu, 2 Jun 2011 12:17:42 +0200
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1084)
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 10:18:04 -0000

at first glance it might look useful, but this is the kind of info that =
tends to go stale and then what do you do when there is a mismatch?
Would you invalidate a still-valid signature if it doesn't conform to =
policy in case someone else is signing the zone other than the =
authorised party?
Would you send mail to the zone admin? (and knowing the people on this =
list, that would be a lot email on top of that admin) :)

Shouldn't this sort of admin work be done by the admin, either =
internally or by outsourcing to some other organisation?

Joao

On 2 Jun 2011, at 12:02, Joe Abley wrote:

> Hi all,
>=20
> I've been poking about a bit in other signed zones looking for =
impending signature expirations. I've been doing this mainly because we =
sign a lot of zones and have had at least one accident in the past, but =
this also seems like something that is worth knowing if you're the =
operator of a validator and you want to be able to prepare for impending =
signature expiration in zones that are otherwise going to cause you =
helpdesk problems.
>=20
> See attached script for an example of what I have been doing.
>=20
> I have realised, however, that I can't tell whether a signature that =
is (say) going to expire in under three days is a cause for concern, or =
whether it's normal operations and something I should expect to be =
replaced as part of normal operations.
>=20
> This boils down to there being no way for a zone operator to publish =
their normal signature replacement policy in a way that I can obtain in =
a simple way. Sometimes that information is present in a DPS, but often =
there is no DPS to be found, sometimes there's a DPS but it doesn't =
contain that level of detail, and in any case this is all far too manual =
for an automated check script.
>=20
> Is there perhaps value in finding a mechanism by which zone operators =
can publish information in their zones which gives guidance as to what =
the normal limits for signature expiration ought to be?
>=20
>  $ORIGIN HOPCOUNT.CA.
>  @ RRSIGPOLICY DNSKEY <min planned remaining signature validity> <max =
planned remaining signature validity>
>  @ RRSIGPOLICY SOA ....
>=20
> or something?
>=20
>=20
>=20
> Joe
>=20
> wifi-216-217:~]% ./sigexpire.sh
> 2011-06-01 15:30:41 UTC ---------- right now =
-----------------------------
> 2011-06-02 15:30:41 UTC ---------- 1 day from now =
------------------------
> 2011-06-03 15:30:41 UTC ---------- 2 days from now =
-----------------------
> 2011-06-03 18:25:33 UTC signature over COM. DNSKEY expires
> 2011-06-04 15:30:41 UTC ---------- 3 days from now =
-----------------------
> 2011-06-04 18:02:19 UTC signature over VIP.ICANN.ORG. DNSKEY expires
> 2011-06-04 18:02:19 UTC signature over VIP.ICANN.ORG. DNSKEY expires
> 2011-06-05 15:30:41 UTC ---------- 4 days from now =
-----------------------
> 2011-06-05 16:00:23 UTC signature over GOV. DNSKEY expires
> 2011-06-06 04:00:23 UTC signature over GOV. SOA expires
> 2011-06-06 15:30:41 UTC ---------- 5 days from now =
-----------------------
> 2011-06-06 16:38:57 UTC signature over NET. DNSKEY expires
> 2011-06-06 19:28:05 UTC signature over EDU. DNSKEY expires
> 2011-06-07 06:21:17 UTC signature over DK. DNSKEY expires
> 2011-06-07 08:00:01 UTC signature over EU. DNSKEY expires
> 2011-06-07 08:00:01 UTC signature over EU. DNSKEY expires
> 2011-06-07 08:00:01 UTC signature over EU. DNSKEY expires
> 2011-06-07 09:09:09 UTC signature over CH. DNSKEY expires
> 2011-06-07 09:09:09 UTC signature over LI. DNSKEY expires
> 2011-06-07 15:30:41 UTC ---------- 6 days from now =
-----------------------
> 2011-06-08 00:00:00 UTC signature over . SOA expires
> 2011-06-08 00:00:00 UTC signature over ARPA. SOA expires
> 2011-06-08 06:00:00 UTC signature over DE. SOA expires
> 2011-06-08 09:00:00 UTC signature over BR. SOA expires
> 2011-06-08 09:02:13 UTC signature over EU. SOA expires
> 2011-06-08 09:02:13 UTC signature over EU. SOA expires
> 2011-06-08 09:16:26 UTC signature over VIP.ICANN.ORG. SOA expires
> 2011-06-08 11:23:03 UTC signature over BE. DNSKEY expires
> 2011-06-08 14:34:51 UTC signature over XN--DEBA0AD. DNSKEY expires
> 2011-06-08 14:38:20 UTC signature over XN--0ZWM56D. SOA expires
> 2011-06-08 14:38:54 UTC signature over IANA.ORG. SOA expires
> 2011-06-08 14:38:54 UTC signature over IP6-SERVERS.ARPA. DNSKEY =
expires
> 2011-06-08 14:38:54 UTC signature over XN--G6W251D. DNSKEY expires
> 2011-06-08 14:50:18 UTC signature over ICANN.ORG. SOA expires
> 2011-06-08 14:57:44 UTC signature over IP6.ARPA. DNSKEY expires
> 2011-06-08 14:59:29 UTC signature over XN--9T4B11YI5A. SOA expires
> 2011-06-08 15:12:05 UTC signature over URI.ARPA. SOA expires
> 2011-06-08 15:14:51 UTC signature over COM. SOA expires
> 2011-06-08 15:15:06 UTC signature over EDU. SOA expires
> 2011-06-08 15:18:24 UTC signature over NET. SOA expires
> 2011-06-08 15:23:13 UTC signature over XN--ZCKZAH. SOA expires
> 2011-06-08 15:30:41 UTC ---------- 7 days from now =
-----------------------
> 2011-06-08 15:40:41 UTC signature over IN-ADDR-SERVERS.ARPA. SOA =
expires
> 2011-06-08 16:02:53 UTC signature over IN-ADDR.ARPA. SOA expires
> 2011-06-08 16:02:53 UTC signature over XN--HLCJ6AYA9ESC7A. SOA expires
> 2011-06-08 16:22:55 UTC signature over XN--HGBK6AJ7F53BBA. DNSKEY =
expires
> 2011-06-08 17:12:02 UTC signature over URI.ARPA. DNSKEY expires
> 2011-06-08 17:47:06 UTC signature over URN.ARPA. SOA expires
> 2011-06-08 18:26:30 UTC signature over DK. SOA expires
> 2011-06-08 18:29:41 UTC signature over XN--JXALPDLP. DNSKEY expires
> 2011-06-08 18:46:03 UTC signature over IRIS.ARPA. SOA expires
> 2011-06-08 19:07:26 UTC signature over URN.ARPA. DNSKEY expires
> 2011-06-08 19:58:19 UTC signature over IANA.ORG. DNSKEY expires
> 2011-06-08 20:14:20 UTC signature over IN-ADDR-SERVERS.ARPA. DNSKEY =
expires
> 2011-06-08 20:19:01 UTC signature over XN--KGBECHTV. SOA expires
> 2011-06-08 20:23:40 UTC signature over XN--DEBA0AD. SOA expires
> 2011-06-08 21:00:28 UTC signature over XN--11B5BS3A9AJ6G. SOA expires
> 2011-06-08 21:23:22 UTC signature over XN--JXALPDLP. SOA expires
> 2011-06-08 21:28:57 UTC signature over IP6.ARPA. SOA expires
> 2011-06-08 21:52:46 UTC signature over XN--11B5BS3A9AJ6G. DNSKEY =
expires
> 2011-06-08 22:06:53 UTC signature over IRIS.ARPA. DNSKEY expires
> 2011-06-08 22:26:09 UTC signature over XN--ZCKZAH. DNSKEY expires
> 2011-06-08 23:54:38 UTC signature over ICANN.ORG. DNSKEY expires
> 2011-06-08 23:58:18 UTC signature over XN--KGBECHTV. DNSKEY expires
> 2011-06-08 23:59:30 UTC signature over XN--80AKHBYKNJ4F. SOA expires
> 2011-06-09 00:24:19 UTC signature over IN-ADDR.ARPA. DNSKEY expires
> 2011-06-09 00:24:19 UTC signature over XN--HLCJ6AYA9ESC7A. DNSKEY =
expires
> 2011-06-09 00:32:02 UTC signature over IP6-SERVERS.ARPA. SOA expires
> 2011-06-09 00:32:02 UTC signature over XN--G6W251D. SOA expires
> 2011-06-09 01:25:10 UTC signature over XN--80AKHBYKNJ4F. DNSKEY =
expires
> 2011-06-09 01:28:57 UTC signature over XN--0ZWM56D. DNSKEY expires
> 2011-06-09 01:44:31 UTC signature over XN--9T4B11YI5A. DNSKEY expires
> 2011-06-09 02:16:57 UTC signature over XN--HGBK6AJ7F53BBA. SOA expires
> 2011-06-09 04:47:12 UTC signature over MUSEUM. DNSKEY expires
> 2011-06-09 04:47:12 UTC signature over MUSEUM. DNSKEY expires
> 2011-06-09 05:53:12 UTC signature over CAT. DNSKEY expires
> 2011-06-09 15:30:42 UTC ---------- 8 days from now =
-----------------------
> 2011-06-10 09:00:00 UTC signature over BR. DNSKEY expires
> 2011-06-10 15:30:42 UTC ---------- 9 days from now =
-----------------------
> 2011-06-11 09:01:45 UTC signature over BE. SOA expires
> 2011-06-11 20:02:44 UTC signature over SE. DNSKEY expires
> 2011-06-12 17:32:10 UTC signature over CZ. DNSKEY expires
> 2011-06-13 04:02:44 UTC signature over SE. DNSKEY expires
> 2011-06-13 04:18:16 UTC signature over CZ. DNSKEY expires
> 2011-06-13 09:43:58 UTC signature over CZ. SOA expires
> 2011-06-14 04:35:53 UTC signature over LU. DNSKEY expires
> 2011-06-14 08:20:20 UTC signature over FI. DNSKEY expires
> 2011-06-14 10:39:30 UTC signature over SE. SOA expires
> 2011-06-14 17:10:30 UTC signature over LU. SOA expires
> 2011-06-14 23:18:40 UTC signature over NL. DNSKEY expires
> 2011-06-14 23:59:59 UTC signature over . DNSKEY expires
> 2011-06-14 23:59:59 UTC signature over ARPA. DNSKEY expires
> 2011-06-15 04:48:19 UTC signature over UK. SOA expires
> 2011-06-15 06:53:11 UTC signature over CAT. SOA expires
> 2011-06-15 10:48:19 UTC signature over UK. DNSKEY expires
> 2011-06-15 11:47:13 UTC signature over MUSEUM. SOA expires
> 2011-06-15 15:45:48 UTC signature over ASIA. DNSKEY expires
> 2011-06-15 15:45:48 UTC signature over ASIA. DNSKEY expires
> 2011-06-15 15:46:29 UTC signature over ME. DNSKEY expires
> 2011-06-15 15:46:29 UTC signature over ME. DNSKEY expires
> 2011-06-15 15:47:16 UTC signature over AG. DNSKEY expires
> 2011-06-15 15:47:16 UTC signature over AG. DNSKEY expires
> 2011-06-15 15:49:25 UTC signature over INFO. DNSKEY expires
> 2011-06-15 15:49:25 UTC signature over INFO. DNSKEY expires
> 2011-06-15 15:56:25 UTC signature over ORG. DNSKEY expires
> 2011-06-15 15:56:25 UTC signature over ORG. DNSKEY expires
> 2011-06-15 16:05:05 UTC signature over IN. DNSKEY expires
> 2011-06-15 16:05:05 UTC signature over IN. DNSKEY expires
> 2011-06-15 16:30:31 UTC signature over BZ. DNSKEY expires
> 2011-06-15 16:30:31 UTC signature over BZ. DNSKEY expires
> 2011-06-15 16:36:33 UTC signature over VC. DNSKEY expires
> 2011-06-15 16:36:33 UTC signature over VC. DNSKEY expires
> 2011-06-15 17:12:20 UTC signature over HN. DNSKEY expires
> 2011-06-15 17:12:20 UTC signature over HN. DNSKEY expires
> 2011-06-15 18:36:55 UTC signature over MN. DNSKEY expires
> 2011-06-15 18:36:55 UTC signature over MN. DNSKEY expires
> 2011-06-15 20:15:17 UTC signature over FI. SOA expires
> 2011-06-15 21:51:38 UTC signature over SC. DNSKEY expires
> 2011-06-15 21:51:38 UTC signature over SC. DNSKEY expires
> 2011-06-15 23:32:32 UTC signature over LC. DNSKEY expires
> 2011-06-15 23:32:32 UTC signature over LC. DNSKEY expires
> 2011-06-15 23:54:39 UTC signature over NL. SOA expires
> 2011-06-16 02:13:38 UTC signature over GI. DNSKEY expires
> 2011-06-16 02:13:38 UTC signature over GI. DNSKEY expires
> 2011-06-16 12:00:00 UTC signature over DE. DNSKEY expires
> 2011-06-18 03:44:21 UTC signature over AM. DNSKEY expires
> 2011-06-18 03:44:21 UTC signature over AM. DNSKEY expires
> 2011-06-21 20:13:06 UTC signature over LI. DNSKEY expires
> 2011-06-21 22:31:39 UTC signature over CH. DNSKEY expires
> 2011-06-22 08:34:51 UTC signature over LC. SOA expires
> 2011-06-22 11:27:43 UTC signature over SC. SOA expires
> 2011-06-22 11:56:35 UTC signature over VC. SOA expires
> 2011-06-22 14:06:18 UTC signature over MN. SOA expires
> 2011-06-22 14:28:51 UTC signature over HN. SOA expires
> 2011-06-22 14:55:24 UTC signature over BZ. SOA expires
> 2011-06-22 14:58:49 UTC signature over GI. SOA expires
> 2011-06-22 15:11:25 UTC signature over AG. SOA expires
> 2011-06-22 15:15:57 UTC signature over IN. SOA expires
> 2011-06-22 15:17:51 UTC signature over ASIA. SOA expires
> 2011-06-22 15:18:25 UTC signature over ME. SOA expires
> 2011-06-22 15:18:32 UTC signature over INFO. SOA expires
> 2011-06-22 15:21:45 UTC signature over ORG. SOA expires
> 2011-06-22 18:42:09 UTC signature over LA. SOA expires
> 2011-06-24 00:21:43 UTC signature over BIZ. DNSKEY expires
> 2011-06-24 00:21:43 UTC signature over BIZ. DNSKEY expires
> 2011-06-24 00:21:43 UTC signature over BIZ. DNSKEY expires
> 2011-06-24 02:08:36 UTC signature over US. DNSKEY expires
> 2011-06-24 02:08:36 UTC signature over US. DNSKEY expires
> 2011-06-24 13:00:00 UTC signature over CO. DNSKEY expires
> 2011-06-24 13:00:00 UTC signature over CO. DNSKEY expires
> 2011-06-24 13:00:00 UTC signature over CO. DNSKEY expires
> 2011-06-24 13:45:59 UTC signature over LA. DNSKEY expires
> 2011-06-25 10:17:03 UTC signature over XN--FZC2C9E2C. SOA expires
> 2011-06-25 10:17:38 UTC signature over XN--XKC2AL3HYE2A. SOA expires
> 2011-06-25 19:59:45 UTC signature over LA. DNSKEY expires
> 2011-06-26 18:41:02 UTC signature over TH. DNSKEY expires
> 2011-06-26 18:41:02 UTC signature over TH. DNSKEY expires
> 2011-06-26 18:41:02 UTC signature over TH. SOA expires
> 2011-06-27 17:45:03 UTC signature over JP. DNSKEY expires
> 2011-06-27 17:45:03 UTC signature over JP. SOA expires
> 2011-06-28 06:04:02 UTC signature over NA. DNSKEY expires
> 2011-06-28 06:04:02 UTC signature over NA. DNSKEY expires
> 2011-06-28 09:06:45 UTC signature over BE. DNSKEY expires
> 2011-06-28 09:06:45 UTC signature over BE. DNSKEY expires
> 2011-06-28 09:06:45 UTC signature over BE. DNSKEY expires
> 2011-06-29 05:46:24 UTC signature over AC. DNSKEY expires
> 2011-06-29 05:46:24 UTC signature over AC. DNSKEY expires
> 2011-06-29 05:46:24 UTC signature over AC. SOA expires
> 2011-06-29 05:46:24 UTC signature over IO. DNSKEY expires
> 2011-06-29 05:46:24 UTC signature over IO. DNSKEY expires
> 2011-06-29 05:46:24 UTC signature over IO. SOA expires
> 2011-06-29 05:46:24 UTC signature over SH. DNSKEY expires
> 2011-06-29 05:46:24 UTC signature over SH. DNSKEY expires
> 2011-06-29 05:46:24 UTC signature over SH. SOA expires
> 2011-06-29 05:46:24 UTC signature over TM. DNSKEY expires
> 2011-06-29 05:46:24 UTC signature over TM. DNSKEY expires
> 2011-06-29 05:46:24 UTC signature over TM. SOA expires
> 2011-06-30 10:29:51 UTC signature over LK. SOA expires
> 2011-07-01 03:01:01 UTC signature over PR. DNSKEY expires
> 2011-07-01 03:01:01 UTC signature over PR. DNSKEY expires
> 2011-07-01 03:17:05 UTC signature over NU. DNSKEY expires
> 2011-07-01 04:30:04 UTC signature over HOPCOUNT.CA. DNSKEY expires
> 2011-07-01 04:30:04 UTC signature over HOPCOUNT.CA. DNSKEY expires
> 2011-07-01 04:30:04 UTC signature over HOPCOUNT.CA. SOA expires
> 2011-07-01 06:01:01 UTC signature over PR. SOA expires
> 2011-07-01 06:04:01 UTC signature over NA. SOA expires
> 2011-07-01 06:17:05 UTC signature over NU. SOA expires
> 2011-07-01 07:00:07 UTC signature over PT. SOA expires
> 2011-07-01 07:53:19 UTC signature over AUTOMAGIC.ORG. DNSKEY expires
> 2011-07-01 07:53:19 UTC signature over AUTOMAGIC.ORG. DNSKEY expires
> 2011-07-01 07:53:19 UTC signature over AUTOMAGIC.ORG. SOA expires
> 2011-07-01 08:00:11 UTC signature over BG. SOA expires
> 2011-07-01 08:45:04 UTC signature over AM. SOA expires
> 2011-07-01 10:00:19 UTC signature over E164.ARPA. DNSKEY expires
> 2011-07-01 10:00:19 UTC signature over E164.ARPA. SOA expires
> 2011-07-01 12:00:05 UTC signature over PT. DNSKEY expires
> 2011-07-01 12:00:05 UTC signature over PT. DNSKEY expires
> 2011-07-01 12:12:12 UTC signature over GR. DNSKEY expires
> 2011-07-01 12:12:12 UTC signature over GR. DNSKEY expires
> 2011-07-01 12:12:12 UTC signature over GR. SOA expires
> 2011-07-01 13:00:13 UTC signature over BG. DNSKEY expires
> 2011-07-01 13:00:13 UTC signature over BG. DNSKEY expires
> 2011-07-01 13:34:40 UTC signature over CH. SOA expires
> 2011-07-01 13:59:07 UTC signature over LI. SOA expires
> 2011-07-01 15:14:32 UTC signature over BIZ. SOA expires
> 2011-07-01 15:14:50 UTC signature over CO. SOA expires
> 2011-07-01 15:19:33 UTC signature over US. SOA expires
> 2011-07-16 13:30:20 UTC signature over CL. SOA expires
> 2011-07-16 13:30:21 UTC signature over CL. DNSKEY expires
> 2011-07-29 12:16:31 UTC signature over FR. DNSKEY expires
> 2011-07-29 12:16:31 UTC signature over FR. DNSKEY expires
> 2011-07-29 12:17:36 UTC signature over PM. DNSKEY expires
> 2011-07-29 12:17:36 UTC signature over PM. DNSKEY expires
> 2011-07-29 12:17:36 UTC signature over PM. SOA expires
> 2011-07-29 12:17:37 UTC signature over RE. DNSKEY expires
> 2011-07-29 12:17:37 UTC signature over RE. DNSKEY expires
> 2011-07-29 12:17:37 UTC signature over TF. DNSKEY expires
> 2011-07-29 12:17:37 UTC signature over TF. DNSKEY expires
> 2011-07-29 12:17:37 UTC signature over TF. SOA expires
> 2011-07-29 12:17:39 UTC signature over WF. DNSKEY expires
> 2011-07-29 12:17:39 UTC signature over WF. DNSKEY expires
> 2011-07-29 12:17:39 UTC signature over WF. SOA expires
> 2011-07-29 12:17:39 UTC signature over YT. DNSKEY expires
> 2011-07-29 12:17:39 UTC signature over YT. DNSKEY expires
> 2011-07-29 12:17:39 UTC signature over YT. SOA expires
> 2011-07-30 06:29:31 UTC signature over JP. DNSKEY expires
> 2011-07-31 05:00:04 UTC signature over RE. SOA expires
> 2011-07-31 09:00:06 UTC signature over FR. SOA expires
> 2011-08-11 14:37:10 UTC signature over CL. DNSKEY expires
> 2011-08-15 00:00:00 UTC signature over LK. DNSKEY expires
> 2011-08-15 00:00:00 UTC signature over LK. DNSKEY expires
> 2011-08-15 00:00:00 UTC signature over XN--FZC2C9E2C. DNSKEY expires
> 2011-08-15 00:00:00 UTC signature over XN--FZC2C9E2C. DNSKEY expires
> 2011-08-15 00:00:00 UTC signature over XN--XKC2AL3HYE2A. DNSKEY =
expires
> 2011-08-15 00:00:00 UTC signature over XN--XKC2AL3HYE2A. DNSKEY =
expires
> 2011-08-28 13:06:23 UTC signature over MY. DNSKEY expires
> 2011-08-28 13:06:23 UTC signature over MY. DNSKEY expires
> 2011-08-30 05:06:22 UTC signature over MY. SOA expires
> 2011-12-31 23:59:59 UTC signature over KG. DNSKEY expires
> 2011-12-31 23:59:59 UTC signature over KG. DNSKEY expires
> 2011-12-31 23:59:59 UTC signature over KG. SOA expires
> [wifi-216-217:~]%
>=20
> <sigexpire.sh>_______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From jabley@hopcount.ca  Thu Jun  2 03:22:45 2011
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2C01E06E1 for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 03:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdiQ57zJzO5b for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 03:22:44 -0700 (PDT)
Received: from monster.hopcount.ca (monster.hopcount.ca [IPv6:2001:4900:1:392:213:20ff:fe1b:3bfe]) by ietfa.amsl.com (Postfix) with ESMTP id CD9BBE076A for <dnsop@ietf.org>; Thu,  2 Jun 2011 03:22:25 -0700 (PDT)
Received: from [41.221.50.13] (helo=[10.10.0.146]) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1QS52j-0001pY-VC; Thu, 02 Jun 2011 10:22:22 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <F3F4A1E6-649A-47FB-8863-161C0B3B32B1@bondis.org>
Date: Thu, 2 Jun 2011 13:22:16 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C4DD6B9-F6A8-4B79-83EA-E2A2AEB9F071@hopcount.ca>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <F3F4A1E6-649A-47FB-8863-161C0B3B32B1@bondis.org>
To: =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
X-Mailer: Apple Mail (2.1084)
X-SA-Exim-Connect-IP: 41.221.50.13
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 10:22:45 -0000

On 2011-06-02, at 13:17, Jo=E3o Damas wrote:

> at first glance it might look useful, but this is the kind of info =
that tends to go stale and then what do you do when there is a mismatch?

I guess you flag it for manual investigation. The alternative is that =
you don't really know when a situation is actually bad until the =
signature expires, and it'd be nice to have some early warning.

I could maintain a manual table of what "bad" means for particular zones =
based on observation, but that seems even more likely to become stale.

> Would you invalidate a still-valid signature if it doesn't conform to =
policy in case someone else is signing the zone other than the =
authorised party?

Nope, but (especially in these early days of deployment) perhaps it =
might merit a note to an administrator, or a heads-up to a public list.

> Would you send mail to the zone admin? (and knowing the people on this =
list, that would be a lot email on top of that admin) :)
>=20
> Shouldn't this sort of admin work be done by the admin, either =
internally or by outsourcing to some other organisation?

I guess my point is that unless you're the person involved in signing a =
particular zone, telling when there's a signature expiration problem =
looming is not easy.


Joe=

From fanf2@hermes.cam.ac.uk  Thu Jun  2 04:47:06 2011
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9050EE0703 for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 04:47:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dS0YJK0hGEFH for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 04:47:05 -0700 (PDT)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3B12CE06EC for <dnsop@ietf.org>; Thu,  2 Jun 2011 04:47:05 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:34584) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1QS6Mh-0006Qq-S7 (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 02 Jun 2011 12:47:03 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1QS6Mh-0003Ad-Mc (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 02 Jun 2011 12:47:03 +0100
Date: Thu, 2 Jun 2011 12:47:03 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>
Message-ID: <alpine.LSU.2.00.1106021234310.19557@hermes-2.csi.cam.ac.uk>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="1870870024-388293401-1307015223=:19557"
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 11:47:06 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1870870024-388293401-1307015223=:19557
Content-Type: TEXT/PLAIN; charset=ISO-8859-15
Content-Transfer-Encoding: QUOTED-PRINTABLE

Joe Abley <jabley@hopcount.ca> wrote:
>
> Is there perhaps value in finding a mechanism by which zone operators
> can publish information in their zones which gives guidance as to what
> the normal limits for signature expiration ought to be?

Sounds like a good idea. I agree with Jo=E3o that you need to take care not
to confuse the current rrsig expiration semantics. So I think the right
thing to publish is the next planned signature refresh time. (Which
amounts to the same thing but the terminology is clearer.)

Tony.
--=20
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Rockall, Malin, Hebrides: South 5 to 7, occasionally gale 8 at first in
Rockall and Malin, veering west or northwest 4 or 5, then backing southwest=
 5
or 6 later. Rough or very rough. Occasional rain. Moderate or good,
occasionally poor.
--1870870024-388293401-1307015223=:19557--

From Ed.Lewis@neustar.biz  Thu Jun  2 06:43:00 2011
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD737E0692 for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 06:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.517
X-Spam-Level: 
X-Spam-Status: No, score=-106.517 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mfj8XC68iCp6 for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 06:43:00 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 11EA5E065B for <dnsop@ietf.org>; Thu,  2 Jun 2011 06:42:59 -0700 (PDT)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p52DgvOc059488; Thu, 2 Jun 2011 09:42:57 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.204.168] by Work-Laptop-2.local (PGP Universal service); Thu, 02 Jun 2011 09:42:58 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Thu, 02 Jun 2011 09:42:58 -0400
Mime-Version: 1.0
Message-Id: <a06240802ca0d3aec24d4@[10.31.204.168]>
In-Reply-To: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>
Date: Thu, 2 Jun 2011 09:36:30 -0400
To: IETF DNSOP WG <dnsop@ietf.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: ed.lewis@neustar.biz
Subject: Re: [DNSOP] watching for signature expiration in zones you don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 13:43:01 -0000

At 13:02 +0300 6/2/11, Joe Abley wrote:

>I have realised, however, that I can't tell whether a signature that is
>(say) going to expire in under three days is a cause for concern, or
>whether it's normal operations and something I should expect to be
>replaced as part of normal operations.

Once upon a time a DNS set up had two NS records and the two IP 
addresses were neighbors.  I was sitting next to the admin of the 
zone and mentioned this to him.  He said "but you don't know..." how 
he had set up the zone to avoid the problem I thought I detected.  It 
turns out, what I "didn't know" didn't really solve the problem but 
the moral is that with all the tricks available to admins these days, 
it's nearly impossible to poke at port 53 and make an accurate 
diagnosis and recommendation.  (You can detect symptoms, but not a 
reason.)

I also repeated this lesson writing lame server detection software 
years ago.  Again, you can find symptoms but can't really diagnose or 
prescribe fixes.

So, I would bet that about all you can do is list when signatures are 
to expire (in the future) and list signatures that expire and notify 
the admins.  Except for the expired ones, there's not much you can 
say definitively to the admin.  More remote monitoring and reporting 
symptoms is good, trying to diagnose and offer fixes is likely to 
drive you crazy (unless you like false positives).

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

Now, don't say I'm always complaining.
Wait, that's a complaint, isn't it?

From fanf2@hermes.cam.ac.uk  Thu Jun  2 06:53:20 2011
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 962E9E076A for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 06:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YXspUAIXiEun for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 06:53:19 -0700 (PDT)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by ietfa.amsl.com (Postfix) with ESMTP id 899E4E0692 for <dnsop@ietf.org>; Thu,  2 Jun 2011 06:53:18 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:43916) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:fanf2) id 1QS8Ks-0003h8-WN (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 02 Jun 2011 14:53:18 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1QS8Ks-0002aI-0o (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 02 Jun 2011 14:53:18 +0100
Date: Thu, 2 Jun 2011 14:53:18 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Edward Lewis <Ed.Lewis@neustar.biz>
In-Reply-To: <a06240802ca0d3aec24d4@[10.31.204.168]>
Message-ID: <alpine.LSU.2.00.1106021449270.19557@hermes-2.csi.cam.ac.uk>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <a06240802ca0d3aec24d4@[10.31.204.168]>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 13:53:20 -0000

Edward Lewis <Ed.Lewis@neustar.biz> wrote:
> At 13:02 +0300 6/2/11, Joe Abley wrote:
>
> > I have realised, however, that I can't tell whether a signature that is
> > (say) going to expire in under three days is a cause for concern, or
> > whether it's normal operations and something I should expect to be
> > replaced as part of normal operations.
>
> So, I would bet that about all you can do is list when signatures are to
> expire (in the future) and list signatures that expire and notify the admins.
> Except for the expired ones, there's not much you can say definitively to the
> admin.  More remote monitoring and reporting symptoms is good, trying to
> diagnose and offer fixes is likely to drive you crazy (unless you like false
> positives).

It's possibly useful to know the ratio of the intervals between the
inception time and now, and now and the expiry time. Also the relation
between the now/expiry interval and the relevant TTLs and zone refresh and
expiry intervals.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Rockall, Malin, Hebrides: South 5 to 7, occasionally gale 8 at first in
Rockall and Malin, veering west or northwest 4 or 5, then backing southwest 5
or 6 later. Rough or very rough. Occasional rain. Moderate or good,
occasionally poor.

From jim@rfc1035.com  Thu Jun  2 07:02:29 2011
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 037A2E065B for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 07:02:29 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id owd4IM3Pg3K0 for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 07:02:28 -0700 (PDT)
Received: from hutch.rfc1035.com (hutch.rfc1035.com [195.54.233.70]) by ietfa.amsl.com (Postfix) with ESMTP id 1B904E06C2 for <dnsop@ietf.org>; Thu,  2 Jun 2011 07:02:28 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jim) by hutch.rfc1035.com (Postfix) with ESMTPSA id A266E15420A1; Thu,  2 Jun 2011 15:02:23 +0100 (BST)
Message-Id: <D22C9921-0224-45D3-B897-BA64882F2ADB@rfc1035.com>
From: Jim Reid <jim@rfc1035.com>
To: Tony Finch <dot@dotat.at>
In-Reply-To: <alpine.LSU.2.00.1106021449270.19557@hermes-2.csi.cam.ac.uk>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 2 Jun 2011 15:02:23 +0100
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <a06240802ca0d3aec24d4@[10.31.204.168]> <alpine.LSU.2.00.1106021449270.19557@hermes-2.csi.cam.ac.uk>
X-Mailer: Apple Mail (2.936)
Cc: IETF DNSOP WG <dnsop@ietf.org>, Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 14:02:29 -0000

On 2 Jun 2011, at 14:53, Tony Finch wrote:

> It's possibly useful to know the ratio of the intervals between the
> inception time and now, and now and the expiry time. Also the relation
> between the now/expiry interval and the relevant TTLs and zone  
> refresh and
> expiry intervals.

How does this differ from the metadata that's in the zone's RRSIG and  
SOA records?

From fanf2@hermes.cam.ac.uk  Thu Jun  2 07:24:08 2011
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3CC8E078C for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 07:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AuI8Bao75+NP for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 07:24:07 -0700 (PDT)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by ietfa.amsl.com (Postfix) with ESMTP id BB5C8E0786 for <dnsop@ietf.org>; Thu,  2 Jun 2011 07:24:07 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:48447) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:fanf2) id 1QS8of-0002Iv-Z5 (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 02 Jun 2011 15:24:05 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1QS8of-0006cw-Rp (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 02 Jun 2011 15:24:05 +0100
Date: Thu, 2 Jun 2011 15:24:05 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Jim Reid <jim@rfc1035.com>
In-Reply-To: <D22C9921-0224-45D3-B897-BA64882F2ADB@rfc1035.com>
Message-ID: <alpine.LSU.2.00.1106021518570.19557@hermes-2.csi.cam.ac.uk>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <a06240802ca0d3aec24d4@[10.31.204.168]> <alpine.LSU.2.00.1106021449270.19557@hermes-2.csi.cam.ac.uk> <D22C9921-0224-45D3-B897-BA64882F2ADB@rfc1035.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: IETF DNSOP WG <dnsop@ietf.org>, Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 14:24:08 -0000

Jim Reid <jim@rfc1035.com> wrote:
> On 2 Jun 2011, at 14:53, Tony Finch wrote:
>
> > It's possibly useful to know the ratio of the intervals between the
> > inception time and now, and now and the expiry time. Also the relation
> > between the now/expiry interval and the relevant TTLs and zone refresh and
> > expiry intervals.
>
> How does this differ from the metadata that's in the zone's RRSIG and SOA
> records?

Joe's script doesn't display that metadata. It might help you decide if
you should worry about signatures that are due to expire soon, more than
just the interval between now and the expiry time.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Rockall, Malin, Hebrides: South 5 to 7, occasionally gale 8 at first in
Rockall and Malin, veering west or northwest 4 or 5, then backing southwest 5
or 6 later. Rough or very rough. Occasional rain. Moderate or good,
occasionally poor.

From jim@rfc1035.com  Thu Jun  2 08:11:40 2011
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10EF7E06AF for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 08:11:40 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bK5XJ+q7YkjS for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 08:11:39 -0700 (PDT)
Received: from hutch.rfc1035.com (hutch.rfc1035.com [195.54.233.70]) by ietfa.amsl.com (Postfix) with ESMTP id 685E9E0699 for <dnsop@ietf.org>; Thu,  2 Jun 2011 08:11:39 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jim) by hutch.rfc1035.com (Postfix) with ESMTPSA id C74EE15420A1; Thu,  2 Jun 2011 16:11:37 +0100 (BST)
Message-Id: <C8588887-F3B0-4973-A80C-4BE7AD69E46C@rfc1035.com>
From: Jim Reid <jim@rfc1035.com>
To: Tony Finch <dot@dotat.at>
In-Reply-To: <alpine.LSU.2.00.1106021518570.19557@hermes-2.csi.cam.ac.uk>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 2 Jun 2011 16:11:37 +0100
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <a06240802ca0d3aec24d4@[10.31.204.168]> <alpine.LSU.2.00.1106021449270.19557@hermes-2.csi.cam.ac.uk> <D22C9921-0224-45D3-B897-BA64882F2ADB@rfc1035.com> <alpine.LSU.2.00.1106021518570.19557@hermes-2.csi.cam.ac.uk>
X-Mailer: Apple Mail (2.936)
Cc: IETF DNSOP WG <dnsop@ietf.org>, Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 15:11:40 -0000

On 2 Jun 2011, at 15:24, Tony Finch wrote:

>> How does this differ from the metadata that's in the zone's RRSIG  
>> and SOA
>> records?
>
> Joe's script doesn't display that metadata. It might help you decide  
> if
> you should worry about signatures that are due to expire soon, more  
> than
> just the interval between now and the expiry time.

Ah. I thought you were talking about Joe's idea rather than the script  
he used to illustrat that.

From richard.lamb@icann.org  Thu Jun  2 08:23:36 2011
Return-Path: <richard.lamb@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE1C2E06AF for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 08:23:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FkkaorBKnvCc for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 08:23:35 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id 03E92E067F for <dnsop@ietf.org>; Thu,  2 Jun 2011 08:23:35 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Thu, 2 Jun 2011 08:23:34 -0700
From: Richard Lamb <richard.lamb@icann.org>
To: Joe Abley <jabley@hopcount.ca>, =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
Date: Thu, 2 Jun 2011 08:23:38 -0700
Thread-Topic: [DNSOP] watching for signature expiration in zones you don't sign
Thread-Index: AcwhDx3M5yc28INqSgGDvZTs0pA8BQAKIRrQ
Message-ID: <05B243F724B2284986522B6ACD0504D7F84FF26D9F@EXVPMBX100-1.exc.icann.org>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <F3F4A1E6-649A-47FB-8863-161C0B3B32B1@bondis.org> <5C4DD6B9-F6A8-4B79-83EA-E2A2AEB9F071@hopcount.ca>
In-Reply-To: <5C4DD6B9-F6A8-4B79-83EA-E2A2AEB9F071@hopcount.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't	sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 15:23:36 -0000

I still think, stale or not, having some idea of what the zone's policy is =
regarding signature updates would be useful.  I've been running signature e=
xpiry monitoring scripts for a few years and having some idea of what is "o=
k" for a zone would be very helpful - particularly those zones that have a =
policy of not refreshing signatures a day or two before expiry (e.g. red on=
es on http://www.dnssek.info/ )- which I would normally consider a concern =
and start firing off warning emails.

-Rick

> -----Original Message-----
> From: dnsop-bounces@ietf.org [mailto:dnsop-bounces@ietf.org] On Behalf Of=
 Joe Abley
> Sent: Thursday, June 02, 2011 3:22 AM
> To: Jo=E3o Damas
> Cc: IETF DNSOP WG
> Subject: Re: [DNSOP] watching for signature expiration in zones you don't=
 sign
>=20
>=20
> On 2011-06-02, at 13:17, Jo=E3o Damas wrote:
>=20
> > at first glance it might look useful, but this is the kind of info that=
 tends to go stale and then
> what do you do when there is a mismatch?
>=20
> I guess you flag it for manual investigation. The alternative is that you=
 don't really know when a
> situation is actually bad until the signature expires, and it'd be nice t=
o have some early warning.
>=20
> I could maintain a manual table of what "bad" means for particular zones =
based on observation, but
> that seems even more likely to become stale.
>=20
> > Would you invalidate a still-valid signature if it doesn't conform to p=
olicy in case someone else is
> signing the zone other than the authorised party?
>=20
> Nope, but (especially in these early days of deployment) perhaps it might=
 merit a note to an
> administrator, or a heads-up to a public list.
>=20
> > Would you send mail to the zone admin? (and knowing the people on this =
list, that would be a lot
> email on top of that admin) :)
> >
> > Shouldn't this sort of admin work be done by the admin, either internal=
ly or by outsourcing to some
> other organisation?
>=20
> I guess my point is that unless you're the person involved in signing a p=
articular zone, telling when
> there's a signature expiration problem looming is not easy.
>=20
>=20
> Joe
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

From paul.hoffman@vpnc.org  Thu Jun  2 08:43:34 2011
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB0FE07D8 for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 08:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b4B2w2ElhguP for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 08:43:34 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7D917E07CC for <dnsop@ietf.org>; Thu,  2 Jun 2011 08:43:33 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p52FhRqe017004 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Jun 2011 08:43:28 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>
Date: Thu, 2 Jun 2011 08:43:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <82D178F5-6EED-44C7-85EB-22A949BD46AF@vpnc.org>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1084)
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 15:43:34 -0000

Another thought is to simply keep a detailed history and watch the =
replacements. For each zone, you should be able to determine what their =
normal renewal buffer is. You would only need to be concerned about =
those that get too close to the edge from their normal operations.

--Paul Hoffman=

From ogud@ogud.com  Thu Jun  2 08:44:03 2011
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8996E07EB for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 08:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q9ojoGpC9o+j for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 08:44:02 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 1C0E2E07DA for <dnsop@ietf.org>; Thu,  2 Jun 2011 08:44:01 -0700 (PDT)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p52Fhx6r060410 for <dnsop@ietf.org>; Thu, 2 Jun 2011 11:43:59 -0400 (EDT) (envelope-from ogud@ogud.com)
Message-ID: <4DE7AFB8.6070106@ogud.com>
Date: Thu, 02 Jun 2011 11:43:52 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: dnsop@ietf.org
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>	<F3F4A1E6-649A-47FB-8863-161C0B3B32B1@bondis.org>	<5C4DD6B9-F6A8-4B79-83EA-E2A2AEB9F071@hopcount.ca> <05B243F724B2284986522B6ACD0504D7F84FF26D9F@EXVPMBX100-1.exc.icann.org>
In-Reply-To: <05B243F724B2284986522B6ACD0504D7F84FF26D9F@EXVPMBX100-1.exc.icann.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Subject: Re: [DNSOP] watching for signature expiration in zones you	don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 15:44:03 -0000

On 02/06/2011 11:23 AM, Richard Lamb wrote:
> I still think, stale or not, having some idea of what the zone's policy is regarding signature updates would be useful.  I've been running signature expiry monitoring scripts for a few years and having some idea of what is "ok" for a zone would be very helpful - particularly those zones that have a policy of not refreshing signatures a day or two before expiry (e.g. red ones on http://www.dnssek.info/ )- which I would normally consider a concern and start firing off warning emails.
>

Strictly speaking from a protocol point of view any signature that 
expires before (zone expiry + RR TTL) is a potential validation failure.
Any Signature that expires before corresponding TTL is a likely 
validation failure if there is a non DNSSEC validating cache in the path.

Any Signature that has expired is bad.

The issue is that many zone owners do not
a) Do not know how long it takes to distribute their modified zone to 
all the servers in the NS set. (frequent assumption is 0 seconds)
b) Forget about the possible impact of zone expiry when secondary server 
can not reach distribution server.
c) Forget about maximum TTL in zone

	Olafur


> -Rick
>
>> -----Original Message-----
>> From: dnsop-bounces@ietf.org [mailto:dnsop-bounces@ietf.org] On Behalf Of Joe Abley
>> Sent: Thursday, June 02, 2011 3:22 AM
>> To: João Damas
>> Cc: IETF DNSOP WG
>> Subject: Re: [DNSOP] watching for signature expiration in zones you don't sign
>>
>>
>> On 2011-06-02, at 13:17, João Damas wrote:
>>
>>> at first glance it might look useful, but this is the kind of info that tends to go stale and then
>> what do you do when there is a mismatch?
>>
>> I guess you flag it for manual investigation. The alternative is that you don't really know when a
>> situation is actually bad until the signature expires, and it'd be nice to have some early warning.
>>
>> I could maintain a manual table of what "bad" means for particular zones based on observation, but
>> that seems even more likely to become stale.
>>
>>> Would you invalidate a still-valid signature if it doesn't conform to policy in case someone else is
>> signing the zone other than the authorised party?
>>
>> Nope, but (especially in these early days of deployment) perhaps it might merit a note to an
>> administrator, or a heads-up to a public list.
>>
>>> Would you send mail to the zone admin? (and knowing the people on this list, that would be a lot
>> email on top of that admin) :)
>>>
>>> Shouldn't this sort of admin work be done by the admin, either internally or by outsourcing to some
>> other organisation?
>>
>> I guess my point is that unless you're the person involved in signing a particular zone, telling when
>> there's a signature expiration problem looming is not easy.
>>
>>
>> Joe
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>
>


From Ed.Lewis@neustar.biz  Thu Jun  2 09:23:00 2011
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51DB6E06FD for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 09:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.522
X-Spam-Level: 
X-Spam-Status: No, score=-106.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1datR7j5lWTp for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 09:22:58 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 43D4AE06CC for <dnsop@ietf.org>; Thu,  2 Jun 2011 09:22:58 -0700 (PDT)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p52GMrWY060694; Thu, 2 Jun 2011 12:22:54 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.204.168] by Work-Laptop-2.local (PGP Universal service); Thu, 02 Jun 2011 12:22:55 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Thu, 02 Jun 2011 12:22:55 -0400
Mime-Version: 1.0
Message-Id: <a06240802ca0d637ec710@[10.31.204.168]>
In-Reply-To: <4DE7AFB8.6070106@ogud.com>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <F3F4A1E6-649A-47FB-8863-161C0B3B32B1@bondis.org> <5C4DD6B9-F6A8-4B79-83EA-E2A2AEB9F071@hopcount.ca> <05B243F724B2284986522B6ACD0504D7F84FF26D9F@EXVPMBX100-1.exc.icann.org> <4DE7AFB8.6070106@ogud.com>
Date: Thu, 2 Jun 2011 12:22:42 -0400
To: Olafur Gudmundsson <ogud@ogud.com>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] watching for signature expiration in zones you	don't sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 16:23:00 -0000

Time is a pain in the neck.  Conversations over the meaning of timers 
and time fields have gone on for a long time.

Keep in mind the difference between absolute (or wall clock) time and 
relative time.  The latter is even stickier because the time may be 
relative to an event that is local and not even zone-wide.

What timers are used to do is to govern different, often orthogonal 
operations and events in the DNS system.  The TTL is there to govern 
freshness of cached records in a server.  The SOA timers are there to 
govern the freshness of a copy of a zone in a slave server. 
Authority (only) servers have no notion of time and we've made 
strides to keep it that way.  (At least in the protocol.)

DNSSEC came along with absolute time.  That is a novelty of the 
extensions.  The time was used to do two things - protect the 
cryptographic relevance of the signature and to limit the impact of 
replay attempts.

Along the way many have confused the meaning of the timers.  TTL 
trimming to the signature expiration is one abuse, arguably one that 
makes sense.  In the purity of the protocol it doesn't but given 
operational realities that there may be a forced downstream validator 
that needs this trimming to be done.

At 11:43 -0400 6/2/11, Olafur Gudmundsson wrote:

>Strictly speaking from a protocol point of view any signature that expires
>before (zone expiry + RR TTL) is a potential validation failure.

The signature expiration is in absolute time.  Zone expiry (and 
refresh/retry) is a relative time.  TTL is also a relative time.

Whether the signature expiration time will arrive before the 
expiration of the zone or the cache entry is a question relative to 
the time you ask.

The base time for, say zone expiry, is relative to the slave server 
and is not revealed via the protocol.  And it is server specific, not 
zone specific!

So - there's no way to determine if "any signature ... expires 
before" zone expiry or RR TTL.

>Any Signature that expires before corresponding TTL is a likely validation
>failure if there is a non DNSSEC validating cache in the path.

What do you mean by "in the path"?

There's no protocol error in shipping an expired signature.  It's up 
to the receiver to decide if that matters.  We stopped requiring zone 
loading to check signatures like 10 years ago.

>Any Signature that has expired is bad.

http://tools.ietf.org/html/draft-wijngaards-dnsop-trust-history-02 
says differently.

>The issue is that many zone owners do not

>a) Do not know how long it takes to distribute their modified zone to all
>the servers in the NS set. (frequent assumption is 0 seconds)

>b) Forget about the possible impact of zone expiry when secondary server
>can not reach distribution server.

>c) Forget about maximum TTL in zone

I'm not sure where you are going here - but C isn't a problem in 
caches that do TTL trimming.   A & B aren't limited to being DNSSEC 
issues.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

Now, don't say I'm always complaining.
Wait, that's a complaint, isn't it?

From richard.lamb@icann.org  Thu Jun  2 10:41:20 2011
Return-Path: <richard.lamb@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 567A2E06FB for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 10:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2iSbhd68fWBq for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 10:41:19 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id B8550E0693 for <dnsop@ietf.org>; Thu,  2 Jun 2011 10:41:19 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Thu, 2 Jun 2011 10:41:19 -0700
From: Richard Lamb <richard.lamb@icann.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Joe Abley <jabley@hopcount.ca>
Date: Thu, 2 Jun 2011 10:41:25 -0700
Thread-Topic: [DNSOP] watching for signature expiration in zones you don't sign
Thread-Index: AcwhO+bd8g5y7k70QP+7iHeXW26NMAAEEtrw
Message-ID: <05B243F724B2284986522B6ACD0504D7F84FF26E8A@EXVPMBX100-1.exc.icann.org>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <82D178F5-6EED-44C7-85EB-22A949BD46AF@vpnc.org>
In-Reply-To: <82D178F5-6EED-44C7-85EB-22A949BD46AF@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't	sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 17:41:20 -0000

Good point. Make it adaptive.

> -----Original Message-----
> From: dnsop-bounces@ietf.org [mailto:dnsop-bounces@ietf.org] On Behalf Of=
 Paul Hoffman
> Sent: Thursday, June 02, 2011 8:43 AM
> To: Joe Abley
> Cc: IETF DNSOP WG
> Subject: Re: [DNSOP] watching for signature expiration in zones you don't=
 sign
>=20
> Another thought is to simply keep a detailed history and watch the replac=
ements. For each zone, you
> should be able to determine what their normal renewal buffer is. You woul=
d only need to be concerned
> about those that get too close to the edge from their normal operations.
>=20
> --Paul Hoffman
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

From drc@virtualized.org  Thu Jun  2 12:28:53 2011
Return-Path: <drc@virtualized.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01FBCE0888 for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 12:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id STjMsnzn2f8T for <dnsop@ietfa.amsl.com>; Thu,  2 Jun 2011 12:28:52 -0700 (PDT)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by ietfa.amsl.com (Postfix) with ESMTP id 961E9E06D7 for <dnsop@ietf.org>; Thu,  2 Jun 2011 12:28:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virtualized.org (Postfix) with ESMTP id 13236137785D; Thu,  2 Jun 2011 12:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at virtualized.org
Received: from virtualized.org ([127.0.0.1]) by localhost (trantor.virtualized.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gcgjD4PFT5Av; Thu,  2 Jun 2011 12:28:49 -0700 (PDT)
Received: from [10.0.1.2] (cpe-66-91-109-17.hawaii.res.rr.com [66.91.109.17]) by virtualized.org (Postfix) with ESMTP id C93D41377837; Thu,  2 Jun 2011 12:28:48 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: David Conrad <drc@virtualized.org>
In-Reply-To: <05B243F724B2284986522B6ACD0504D7F84FF26D9F@EXVPMBX100-1.exc.icann.org>
Date: Thu, 2 Jun 2011 09:28:45 -1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <AF6FF43C-A684-452C-A756-ECBD1BA83D09@virtualized.org>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <F3F4A1E6-649A-47FB-8863-161C0B3B32B1@bondis.org> <5C4DD6B9-F6A8-4B79-83EA-E2A2AEB9F071@hopcount.ca> <05B243F724B2284986522B6ACD0504D7F84FF26D9F@EXVPMBX100-1.exc.icann.org>
To: Richard Lamb <richard.lamb@icann.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't	sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 02 Jun 2011 19:28:53 -0000

On Jun 2, 2011, at 5:23 AM, Richard Lamb wrote:
> I still think, stale or not, having some idea of what the zone's =
policy is regarding signature updates would be useful. =20

I'll admit a vague, unsubstantiated feeling of ill-ease about this.  =
Would publishing this policy provide information of benefit to potential =
attackers?

On the other hand, pragmatically speaking, I suspect signature =
expiration will be causing more damage to the DNS than potential =
attackers...

Regards,
-drc


From marc.lampo@eurid.eu  Fri Jun  3 00:14:06 2011
Return-Path: <marc.lampo@eurid.eu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFDABE06AD for <dnsop@ietfa.amsl.com>; Fri,  3 Jun 2011 00:14:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.501
X-Spam-Level: 
X-Spam-Status: No, score=-8.501 tagged_above=-999 required=5 tests=[AWL=0.649,  BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kTppoFIwS3CG for <dnsop@ietfa.amsl.com>; Fri,  3 Jun 2011 00:14:05 -0700 (PDT)
Received: from barra.eurid.eu (mx.eurid.eu [212.190.206.103]) by ietfa.amsl.com (Postfix) with ESMTP id 79AF2E06C1 for <dnsop@ietf.org>; Fri,  3 Jun 2011 00:14:04 -0700 (PDT)
X-ASG-Debug-ID: 1307085242-036949163976200001-lPZdTi
Received: from zimbra.eurid.eu (zcs-master.vt.eurid.eu [10.19.100.121]) by barra.eurid.eu with ESMTP id Jonupb4FwDBXsF31; Fri, 03 Jun 2011 09:14:02 +0200 (CEST)
X-Barracuda-Envelope-From: marc.lampo@eurid.eu
X-ASG-Whitelist: Client
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.eurid.eu (Postfix) with ESMTP id D026DE408D; Fri,  3 Jun 2011 09:05:05 +0200 (CEST)
X-Virus-Scanned: amavisd-new at techmail.eurid.eu
Received: from zimbra.eurid.eu ([127.0.0.1]) by localhost (zimbra.eurid.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c6bX307-uAjE; Fri,  3 Jun 2011 09:05:05 +0200 (CEST)
Received: from zimbra.eurid.eu (zimbra.eurid.eu [10.19.100.120]) by zimbra.eurid.eu (Postfix) with ESMTP id B07C9E406A; Fri,  3 Jun 2011 09:05:05 +0200 (CEST)
From: "Marc Lampo" <marc.lampo@eurid.eu>
To: "'Paul Hoffman'" <paul.hoffman@vpnc.org>, "'Joe Abley'" <jabley@hopcount.ca>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <82D178F5-6EED-44C7-85EB-22A949BD46AF@vpnc.org>
In-Reply-To: <82D178F5-6EED-44C7-85EB-22A949BD46AF@vpnc.org>
Date: Fri, 3 Jun 2011 09:05:05 +0200 (CEST)
X-ASG-Orig-Subj: RE: [DNSOP] watching for signature expiration in zones you don't	sign
Message-ID: <00b401cc21bd$d096a190$71c3e4b0$@lampo@eurid.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraConnectorForOutlook/5.0.3064.18)
Thread-Index: AcwhO9D+IhketBKqShOU3tgekH5+twAgZ2kg
Content-Language: en-za
X-Originating-IP: [172.20.1.130]
X-Barracuda-Connect: zcs-master.vt.eurid.eu[10.19.100.121]
X-Barracuda-Start-Time: 1307085242
X-Barracuda-URL: http://172.20.1.190:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at eurid.eu
Cc: 'IETF DNSOP WG' <dnsop@ietf.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't	sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 03 Jun 2011 07:14:07 -0000

Which is basically what we, EURid for .eu, do.
Example : DNSKEY "operations" and usage during the month of may

domain "eu." on 2011-05-01
 serial : 1003539565
 ksks   : 61179 DS
 zsks   : 19700, 57368 RRSIG
domain "eu." on 2011-05-03
 signing with keyid 19700
 serial : 1003545434
 ksks   : 61179 DS
 zsks   : 19700 RRSIG, 57368 RRSIG
domain "eu." on 2011-05-12
 no longer signing with keyid 57368
 serial : 1003578276
 ksks   : 61179 DS
 zsks   : 19700 RRSIG, 57368
domain "eu." on 2011-05-20
 zsk 57368 - removed DNSKEY from zone
 serial : 1003606818
 ksks   : 61179 DS
 zsks   : 19700 RRSIG
domain "eu." on 2011-05-24
 zsk 34553 - added DNSKEY to zone
 serial : 1003620223
 ksks   : 61179 DS
 zsks   : 19700 RRSIG, 34553
domain "eu." on 2011-05-31
 signing with keyid 34553
 serial : 1003644472
 ksks   : 61179 DS
 zsks   : 19700 RRSIG, 34553 RRSIG

In addition :
On the network management server, scripts were added that do check
validity of published signatures.
Getting "too close" to end-of-validity is one of the triggers to send
alerts.

Kind regards,

Marc Lampo
Security Officer
EURid

-----Original Message-----
From: Paul Hoffman [mailto:paul.hoffman@vpnc.org] 
Sent: 02 June 2011 05:43 PM
To: Joe Abley
Cc: IETF DNSOP WG
Subject: Re: [DNSOP] watching for signature expiration in zones you don't
sign

Another thought is to simply keep a detailed history and watch the
replacements. For each zone, you should be able to determine what their
normal renewal buffer is. You would only need to be concerned about those
that get too close to the edge from their normal operations.

--Paul Hoffman

From marc.lampo@eurid.eu  Fri Jun  3 00:28:33 2011
Return-Path: <marc.lampo@eurid.eu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8F8E0665 for <dnsop@ietfa.amsl.com>; Fri,  3 Jun 2011 00:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.513
X-Spam-Level: 
X-Spam-Status: No, score=-8.513 tagged_above=-999 required=5 tests=[AWL=0.337,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MSGID_MULTIPLE_AT=1.449,  RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RXNoJbvH5Evf for <dnsop@ietfa.amsl.com>; Fri,  3 Jun 2011 00:28:32 -0700 (PDT)
Received: from barra.eurid.eu (mx.eurid.eu [212.190.206.103]) by ietfa.amsl.com (Postfix) with ESMTP id 29AA8E0662 for <dnsop@ietf.org>; Fri,  3 Jun 2011 00:28:31 -0700 (PDT)
X-ASG-Debug-ID: 1307086110-0369491639762d0001-lPZdTi
Received: from zimbra.eurid.eu (zcs-master.vt.eurid.eu [10.19.100.121]) by barra.eurid.eu with ESMTP id WotvmXIehP72Nuv3; Fri, 03 Jun 2011 09:28:30 +0200 (CEST)
X-Barracuda-Envelope-From: marc.lampo@eurid.eu
X-ASG-Whitelist: Client
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.eurid.eu (Postfix) with ESMTP id 342AAE408C; Fri,  3 Jun 2011 09:19:34 +0200 (CEST)
X-Virus-Scanned: amavisd-new at techmail.eurid.eu
Received: from zimbra.eurid.eu ([127.0.0.1]) by localhost (zimbra.eurid.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pC09HWruX1JU; Fri,  3 Jun 2011 09:19:34 +0200 (CEST)
Received: from zimbra.eurid.eu (zimbra.eurid.eu [10.19.100.120]) by zimbra.eurid.eu (Postfix) with ESMTP id 16AC3E4075; Fri,  3 Jun 2011 09:19:34 +0200 (CEST)
From: "Marc Lampo" <marc.lampo@eurid.eu>
To: "'Richard Lamb'" <richard.lamb@icann.org>, "'Joe Abley'" <jabley@hopcount.ca>, =?iso-8859-1?Q?'Jo=E3o_Damas'?= <joao@bondis.org>
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca>	<F3F4A1E6-649A-47FB-8863-161C0B3B32B1@bondis.org>	<5C4DD6B9-F6A8-4B79-83EA-E2A2AEB9F071@hopcount.ca> <05B243F724B2284986522B6ACD0504D7F84FF26D9F@EXVPMBX100-1.exc.icann.org>
In-Reply-To: <05B243F724B2284986522B6ACD0504D7F84FF26D9F@EXVPMBX100-1.exc.icann.org>
Date: Fri, 3 Jun 2011 09:19:34 +0200 (CEST)
X-ASG-Orig-Subj: RE: [DNSOP] watching for signature expiration in zones you	don't	sign
Message-ID: <00b901cc21bf$d63269c0$82973d40$@lampo@eurid.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Mailer: Microsoft Office Outlook 12.0
X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraConnectorForOutlook/5.0.3064.18)
Thread-Index: AcwhOQuyN1DgIUFzT1OTNsPjWfWuZAAhOJRg
Content-Language: en-za
X-Originating-IP: [172.20.1.130]
X-Barracuda-Connect: zcs-master.vt.eurid.eu[10.19.100.121]
X-Barracuda-Start-Time: 1307086110
X-Barracuda-URL: http://172.20.1.190:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at eurid.eu
Cc: 'IETF DNSOP WG' <dnsop@ietf.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you	don't	sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 03 Jun 2011 07:28:33 -0000

Hello,

And thanks for the reference to this website.

While I do agree that having signatures "close to end-of-validity time"
might be a reason for concern
 - in most cases I observed with our own registrars,
   getting "too close" usually leads to "no longer valid" signatures -
there is however absolutely no problem if the signatures are regenerated
before actually reaching that end-of-validity time.

(and though .eu shows "red" in this website,
 I can assure the community we got the re-signing well under control
 and also monitored by network management scripts).


On the other hand, I would be concerned with signatures that remain valid
"very" long !
They show up "green", but actually have a very long period of time
during which "replay attacks" are potentially possible !
Some malicious person might grab present data,
with presently valid signatures,
and - as long as that signature remains valid -
that capture data might be reused !
(the associated DNSKEY must/should remain in the zone
 to allow for validation of that signature)

This begin said :
(at least) one of the tld's that are green in the website,
sends signatures that remain valid till the last second of the present
year,
(and did not even, as far as I can see, any ZSK roll-over at all).
Now *that* would be a reason to flag them "red", in my opinion.

(and yes, I did send the colleague admins emails about this;
 and no, no response ...)


Kind regards,

Marc Lampo
Security Officer
EURid

-----Original Message-----
From: Richard Lamb [mailto:richard.lamb@icann.org]
Sent: 02 June 2011 05:24 PM
To: Joe Abley; João Damas
Cc: IETF DNSOP WG
Subject: Re: [DNSOP] watching for signature expiration in zones you don't
sign

I still think, stale or not, having some idea of what the zone's policy is
regarding signature updates would be useful.  I've been running signature
expiry monitoring scripts for a few years and having some idea of what is
"ok" for a zone would be very helpful - particularly those zones that have
a policy of not refreshing signatures a day or two before expiry (e.g. red
ones on http://www.dnssek.info/ )- which I would normally consider a
concern and start firing off warning emails.

-Rick

> -----Original Message-----
> From: dnsop-bounces@ietf.org [mailto:dnsop-bounces@ietf.org] On Behalf
Of Joe Abley
> Sent: Thursday, June 02, 2011 3:22 AM
> To: João Damas
> Cc: IETF DNSOP WG
> Subject: Re: [DNSOP] watching for signature expiration in zones you
don't sign
>
>
> On 2011-06-02, at 13:17, João Damas wrote:
>
> > at first glance it might look useful, but this is the kind of info
that tends to go stale and then
> what do you do when there is a mismatch?
>
> I guess you flag it for manual investigation. The alternative is that
you don't really know when a
> situation is actually bad until the signature expires, and it'd be nice
to have some early warning.
>
> I could maintain a manual table of what "bad" means for particular zones
based on observation, but
> that seems even more likely to become stale.
>
> > Would you invalidate a still-valid signature if it doesn't conform to
policy in case someone else is
> signing the zone other than the authorised party?
>
> Nope, but (especially in these early days of deployment) perhaps it
might merit a note to an
> administrator, or a heads-up to a public list.
>
> > Would you send mail to the zone admin? (and knowing the people on this
list, that would be a lot
> email on top of that admin) :)
> >
> > Shouldn't this sort of admin work be done by the admin, either
internally or by outsourcing to some
> other organisation?
>
> I guess my point is that unless you're the person involved in signing a
particular zone, telling when
> there's a signature expiration problem looming is not easy.
>
>
> Joe
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From joao@bondis.org  Fri Jun  3 02:03:34 2011
Return-Path: <joao@bondis.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5653E0701 for <dnsop@ietfa.amsl.com>; Fri,  3 Jun 2011 02:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.077
X-Spam-Level: 
X-Spam-Status: No, score=-1.077 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5JlPHUO0fRGP for <dnsop@ietfa.amsl.com>; Fri,  3 Jun 2011 02:03:34 -0700 (PDT)
Received: from smtp1.bondis.org (voyager.c-l-i.net [194.176.119.229]) by ietfa.amsl.com (Postfix) with ESMTP id 18BABE06F1 for <dnsop@ietf.org>; Fri,  3 Jun 2011 02:03:33 -0700 (PDT)
Received: from [192.168.2.36] (82.158.254.126.dyn.user.ono.com [82.158.254.126]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.bondis.org (Postfix) with ESMTPSA id DE52A1AB301; Fri,  3 Jun 2011 09:03:29 +0000 (UTC)
References: <FF1F118A-F5A8-4C62-8840-72BEE131BF9A@hopcount.ca> <F3F4A1E6-649A-47FB-8863-161C0B3B32B1@bondis.org> <5C4DD6B9-F6A8-4B79-83EA-E2A2AEB9F071@hopcount.ca> <05B243F724B2284986522B6ACD0504D7F84FF26D9F@EXVPMBX100-1.exc.icann.org> <AF6FF43C-A684-452C-A756-ECBD1BA83D09@virtualized.org>
In-Reply-To: <AF6FF43C-A684-452C-A756-ECBD1BA83D09@virtualized.org>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
Message-Id: <FEF86626-FAEA-481D-A0E3-A8931D121F05@bondis.org>
Content-Transfer-Encoding: quoted-printable
From: =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
Date: Fri, 3 Jun 2011 11:03:29 +0200
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF DNSOP WG <dnsop@ietf.org>, Richard Lamb <richard.lamb@icann.org>
Subject: Re: [DNSOP] watching for signature expiration in zones you don't	sign
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 03 Jun 2011 09:03:34 -0000

So far, experience tells us exactly that. I am afraid it will continue =
to do so

Joao

On 2 Jun 2011, at 21:28, David Conrad wrote:

> On Jun 2, 2011, at 5:23 AM, Richard Lamb wrote:
>=20
> On the other hand, pragmatically speaking, I suspect signature =
expiration will be causing more damage to the DNS than potential =
attackers...


From george.barwood@blueyonder.co.uk  Sun Jun 12 12:51:02 2011
Return-Path: <george.barwood@blueyonder.co.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30D5E11E813D for <dnsop@ietfa.amsl.com>; Sun, 12 Jun 2011 12:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.754
X-Spam-Level: *
X-Spam-Status: No, score=1.754 tagged_above=-999 required=5 tests=[BAYES_50=0.001, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SSjjjY7ItOgt for <dnsop@ietfa.amsl.com>; Sun, 12 Jun 2011 12:51:01 -0700 (PDT)
Received: from mtaout01-winn.ispmail.ntl.com (mtaout01-winn.ispmail.ntl.com [81.103.221.47]) by ietfa.amsl.com (Postfix) with ESMTP id 40E6D11E814A for <dnsop@ietf.org>; Sun, 12 Jun 2011 12:51:00 -0700 (PDT)
Received: from know-smtpout-4.server.virginmedia.net ([62.254.123.3]) by mtaout01-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20110612195054.LHCB10265.mtaout01-winn.ispmail.ntl.com@know-smtpout-4.server.virginmedia.net> for <dnsop@ietf.org>; Sun, 12 Jun 2011 20:50:54 +0100
Received: from [82.46.65.24] (helo=GeorgeLaptop) by know-smtpout-4.server.virginmedia.net with smtp (Exim 4.63) (envelope-from <george.barwood@blueyonder.co.uk>) id 1QVqgQ-0004zG-Gy for dnsop@ietf.org; Sun, 12 Jun 2011 20:50:54 +0100
Message-ID: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local>
From: "George Barwood" <george.barwood@blueyonder.co.uk>
To: <dnsop@ietf.org>
Date: Sun, 12 Jun 2011 20:50:49 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6090
X-Cloudmark-Analysis: v=1.1 cv=JvdXmxIgLJv2/GthKqHpGJEEHukvLcvELVXUanXFreg= c=1 sm=0 a=Zu9n7L20B7YA:10 a=3NElcqgl2aoA:10 a=8nJEP1OIZ-IA:10 a=48vgC7mUAAAA:8 a=POUOnRNkwuW_6xFtDLEA:9 a=wPNLvfGTeEIA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Subject: [DNSOP] CDS RRtype - automated KSK rollover
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sun, 12 Jun 2011 19:51:02 -0000

SSBoYXZlIHVwZGF0ZWQgdGhlIGRyYWZ0DQoNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQt
YmFyd29vZC1kbnNvcC1kcy1wdWJsaXNoLTAyLnR4dA0KDQpJIGhhdmUgYWRkZWQgYW4gYXBwZW5k
aXggd2l0aCBhbiBleGFtcGxlciBLU0sgcm9sbG92ZXIsIGFuZCBtYWRlDQp2YXJpb3VzIGdlbmVy
YWxseSBtaW5vciBjaGFuZ2VzLg0KDQpJQU5BIGhhdmUgbm93IGFzc2lnbmVkIHR5cGUgY29kZSA1
OSBmb3IgdGhlIENEUyBSUnR5cGUuDQoNCkknZCBsaWtlIHRvIHJlcXVlc3QgdGhhdCB0aGUgV0cg
YWRvcHQgdGhpcyBkb2N1bWVudC4NCg0KR2Vvcmdl


From sa.morris7@googlemail.com  Mon Jun 13 10:22:44 2011
Return-Path: <sa.morris7@googlemail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9F4D11E8183 for <dnsop@ietfa.amsl.com>; Mon, 13 Jun 2011 10:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bd9rzFnZ7wjR for <dnsop@ietfa.amsl.com>; Mon, 13 Jun 2011 10:22:44 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id A456511E818C for <dnsop@ietf.org>; Mon, 13 Jun 2011 10:22:43 -0700 (PDT)
Received: by wwk4 with SMTP id 4so2791775wwk.1 for <dnsop@ietf.org>; Mon, 13 Jun 2011 10:22:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:x-enigmail-version:content-type:content-transfer-encoding; bh=vJHg4/7u1xN+q9b2RxSb8dGt50uCIpDQ+XpLOBz820A=; b=T7Z+BDMBMfih+AT8te/mbjZ0LGOyScC98gufkFz6jcAysyZ9x+lk1kLqRQAW3evhsg Ej0z9Fyz2vIA7O6Sd6iajQC0UMH4cepjUPWMw3uk3FJeiRaoYQbvyE3+TlN3P4Vc/aWt 4RJgY6Xtj2txaoZCDCvIM+D5zDPCmQk6j9xf8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; b=no5MFVY8Wdstnfp9ZSoMLanwGM6kjV7/e5/FHNBf7VVU7nQfPo8fP2K2AxBx1onvrZ D/PwuvTqRcwtLhvMAsayGrZGmwj8fRE1SJsyV+7qZz3PAhSmJY+1r7YjTGkJh3Z5afWR JkdDtD2i73pabrGQ0tGn/DlTazk/4SkAYwkA0=
Received: by 10.227.205.14 with SMTP id fo14mr5331158wbb.79.1307985762439; Mon, 13 Jun 2011 10:22:42 -0700 (PDT)
Received: from stephen-morriss-macbook-pro.local ([217.155.47.50]) by mx.google.com with ESMTPS id gb6sm4375704wbb.0.2011.06.13.10.22.40 (version=SSLv3 cipher=OTHER); Mon, 13 Jun 2011 10:22:41 -0700 (PDT)
Message-ID: <4DF6475F.6030407@googlemail.com>
Date: Mon, 13 Jun 2011 18:22:39 +0100
From: Stephen Morris <sa.morris7@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: dnsop@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 13 Jun 2011 17:22:45 -0000

Dear DNSOP WG,

This is to initiate a working group last call (WGLC) on

      "DNSSEC Policy & Practice Statement Framework"
       draft-ietf-dnsop-dnssec-dps-framework-04.txt

Owing to the length of the document, the WGLC will last for three weeks
instead of the usual two, and will therefore end on

             Monday, 4 July 2011, 23:59 UTC

The IETF tools site gives easy access to the current and previous
versions, as well as differences and the like, at:

http://tools.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework-04

The document is aimed at a status of "Informational".

Please review the document and send any comments you may have to the
list.  If you have no comments but support (or do not support) the
document being published, please send that information to the list.

The document is subject to the normal five reviewer threshold.

    Stephen and Peter
     DNSOP co-chairs

From jakob@kirei.se  Tue Jun 14 08:39:11 2011
Return-Path: <jakob@kirei.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C71711E815F for <dnsop@ietfa.amsl.com>; Tue, 14 Jun 2011 08:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Dt9ALCnF7pw for <dnsop@ietfa.amsl.com>; Tue, 14 Jun 2011 08:39:10 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [IPv6:2001:67c:394:15::9]) by ietfa.amsl.com (Postfix) with ESMTP id D381F11E80B4 for <dnsop@ietf.org>; Tue, 14 Jun 2011 08:39:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:subject:mime-version:content-type:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer; bh=hDXfcqzS7xIeMnitkV5eFbgt/wXHbPWyQv7yxnZSNVY=; b=g8qVM84/wMuo14r1fPr1liG2Sh91lvvSeUSrgxJflJ6/soOIa46g1tdqY2u9LJ1rXVSWnrqJo+7EE BV4zKXPPx56KIbDSMkP4yo8m8DUwFBOKY6W8m+EdjFFf+JSMXXPUdqIOD7iaWy234xuPqKghttpnw9 AV4YftyZDtR9mWIY=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Tue, 14 Jun 2011 17:39:06 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jakob Schlyter <jakob@kirei.se>
In-Reply-To: <4DF6475F.6030407@googlemail.com>
Date: Tue, 14 Jun 2011 17:39:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9DE011E-F73D-4A4A-8A2B-5F4539D36F08@kirei.se>
References: <4DF6475F.6030407@googlemail.com>
To: Stephen Morris <sa.morris7@googlemail.com>
X-Mailer: Apple Mail (2.1084)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Jun 2011 15:39:11 -0000

I have read this draft, have no further comments and support it being =
published as Informational.

	jakob


From richard.lamb@icann.org  Tue Jun 14 08:59:43 2011
Return-Path: <richard.lamb@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6691211E80A6 for <dnsop@ietfa.amsl.com>; Tue, 14 Jun 2011 08:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KPbksmcgNUWc for <dnsop@ietfa.amsl.com>; Tue, 14 Jun 2011 08:59:43 -0700 (PDT)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id EDE6511E80A4 for <dnsop@ietf.org>; Tue, 14 Jun 2011 08:59:42 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Tue, 14 Jun 2011 08:59:42 -0700
From: Richard Lamb <richard.lamb@icann.org>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Date: Tue, 14 Jun 2011 08:59:45 -0700
Thread-Topic: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
Thread-Index: Acwp7pKjOlBh3d9xQ2uFkSTvZCF9cwAvKlFg
Message-ID: <05B243F724B2284986522B6ACD0504D7F850570B96@EXVPMBX100-1.exc.icann.org>
References: <4DF6475F.6030407@googlemail.com>
In-Reply-To: <4DF6475F.6030407@googlemail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Stephen Morris <sa.morris7@googlemail.com>
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Jun 2011 15:59:43 -0000

I've reviewed it and have nothing to add. I find it very useful and support=
 it being published as Informational.

-Rick


> -----Original Message-----
> From: dnsop-bounces@ietf.org [mailto:dnsop-bounces@ietf.org] On Behalf Of=
 Stephen Morris
> Sent: Monday, June 13, 2011 10:23 AM
> To: dnsop@ietf.org
> Subject: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
>=20
> Dear DNSOP WG,
>=20
> This is to initiate a working group last call (WGLC) on
>=20
>       "DNSSEC Policy & Practice Statement Framework"
>        draft-ietf-dnsop-dnssec-dps-framework-04.txt
>=20
> Owing to the length of the document, the WGLC will last for three weeks
> instead of the usual two, and will therefore end on
>=20
>              Monday, 4 July 2011, 23:59 UTC
>=20
> The IETF tools site gives easy access to the current and previous
> versions, as well as differences and the like, at:
>=20
> http://tools.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework-04
>=20
> The document is aimed at a status of "Informational".
>=20
> Please review the document and send any comments you may have to the
> list.  If you have no comments but support (or do not support) the
> document being published, please send that information to the list.
>=20
> The document is subject to the normal five reviewer threshold.
>=20
>     Stephen and Peter
>      DNSOP co-chairs
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

From mehmet@icann.org  Tue Jun 14 10:16:04 2011
Return-Path: <mehmet@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF0DD11E80B4 for <dnsop@ietfa.amsl.com>; Tue, 14 Jun 2011 10:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBBan0JnfDNI for <dnsop@ietfa.amsl.com>; Tue, 14 Jun 2011 10:16:04 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id F364011E8078 for <dnsop@ietf.org>; Tue, 14 Jun 2011 10:16:03 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Tue, 14 Jun 2011 10:16:03 -0700
From: Mehmet Akcin <mehmet@icann.org>
To: Stephen Morris <sa.morris7@googlemail.com>
Date: Tue, 14 Jun 2011 10:15:57 -0700
Thread-Topic: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
Thread-Index: Acwqtr0DXXlA5yLbRfCHLajcyMB4ng==
Message-ID: <0032B7CA-059F-4C24-955A-6579FD5AF275@icann.org>
References: <4DF6475F.6030407@googlemail.com>
In-Reply-To: <4DF6475F.6030407@googlemail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-pgp-agent: GPGMail 1.3.3
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Jun 2011 17:16:05 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've read and support informal draft-ietf-dnsop-dnssec-dps-framework-04.

mehmet

On Jun 13, 2011, at 8:22 PM, Stephen Morris wrote:

> Dear DNSOP WG,
>=20
> This is to initiate a working group last call (WGLC) on
>=20
>      "DNSSEC Policy & Practice Statement Framework"
>       draft-ietf-dnsop-dnssec-dps-framework-04.txt
>=20
> Owing to the length of the document, the WGLC will last for three weeks
> instead of the usual two, and will therefore end on
>=20
>             Monday, 4 July 2011, 23:59 UTC
>=20
> The IETF tools site gives easy access to the current and previous
> versions, as well as differences and the like, at:
>=20
> http://tools.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework-04
>=20
> The document is aimed at a status of "Informational".
>=20
> Please review the document and send any comments you may have to the
> list.  If you have no comments but support (or do not support) the
> document being published, please send that information to the list.
>=20
> The document is subject to the normal five reviewer threshold.
>=20
>    Stephen and Peter
>     DNSOP co-chairs
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.12 (Darwin)

iQIcBAEBAgAGBQJN95dRAAoJEOdd3QW5I0J0lJ4QAJDSjxaondB+XgL8a5l/HZzG
gsA3kduKdsJ1tBWWr+rtbs0pTiZbwoEP72v2Wgz2F82vl2ejIJfp71X0KhQBKlQg
rw9lzStb49vx+ADL0WDQ3kk4vMutnlSGzh5JHWkHuz/gYCeNrxiGVAY87ULm+7kO
DVkdYPphYqmP1siznQU8XV4eoGLj6Cl9dkB6lelVZthIpruxmh2VEGhWNTFPlJhN
BlFIcr+0ttsJVGfw3skE9GhsrVd4wa6vW92TlHRnV5B5iRedgBx1MmN/ZPoGajbz
5weRioHy39b8dFQK1XX+83IsNrwqq7fwHs54h2+rPr5eosm0oKzMxYKfwMSMwDcG
k4RAynkEEBm+PVlTeOzoW+2ThDFfPS2snrbuliCw8QtGt5Rqb84SWPGrAwGwyHvR
hIDKUkOLF1XfAyiRl6y4wDjfpcWRkd6Z75lFM8EworLDPvcSxxdYPwo+5Wk3H45M
ACxAnO+8dehrNGJ5cLl/YBOZVic3UMKHqWPidulLCX9zX1aLGZXVvqXQMJ6Bv46L
8jjAL7+KCT1ghFAOyTgOGCoLA5TfUPW+ipDDu6I2kVjgzDsqqu0dO+PlF3y6htJn
b8okkWoSQofhqL4RcGPfaF/D6NnfxNAr5YnqBhUputFE2UHuEVP+ovabjtEA2LSC
ZitMZzbZ92sj3nRvpwUE
=3DHpfd
-----END PGP SIGNATURE-----

From sebastian@nzrs.net.nz  Wed Jun 15 22:01:04 2011
Return-Path: <sebastian@nzrs.net.nz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F35C11E812B for <dnsop@ietfa.amsl.com>; Wed, 15 Jun 2011 22:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level: 
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SmM3QO-pleVa for <dnsop@ietfa.amsl.com>; Wed, 15 Jun 2011 22:01:03 -0700 (PDT)
Received: from srsomail.nzrs.net.nz (srsomail.nzrs.net.nz [202.46.183.22]) by ietfa.amsl.com (Postfix) with ESMTP id ACF8711E8116 for <dnsop@ietf.org>; Wed, 15 Jun 2011 22:01:03 -0700 (PDT)
Received: from localhost (srsomail.office.nzrs.net.nz [202.46.183.22]) by srsomail.nzrs.net.nz (Postfix) with ESMTP id 32CCA2CE005 for <dnsop@ietf.org>; Thu, 16 Jun 2011 17:01:06 +1200 (NZST)
Received: from srsomail.nzrs.net.nz ([202.46.183.22]) by localhost (srsomail.office.nzrs.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WnEe3L9f+Ka7 for <dnsop@ietf.org>; Thu, 16 Jun 2011 17:01:06 +1200 (NZST)
Received: from [192.168.22.190] (unknown [202.46.183.35]) (Authenticated sender: sebastian) by srsomail.nzrs.net.nz (Postfix) with ESMTPSA id C66E42DBBDC for <dnsop@ietf.org>; Thu, 16 Jun 2011 17:01:05 +1200 (NZST)
Message-ID: <4DF98E0C.4030909@nzrs.net.nz>
Date: Thu, 16 Jun 2011 17:01:00 +1200
From: Sebastian Castro <sebastian@nzrs.net.nz>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
CC: dnsop@ietf.org
References: <4DF6475F.6030407@googlemail.com>
In-Reply-To: <4DF6475F.6030407@googlemail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 16 Jun 2011 05:01:04 -0000

On 06/14/2011 05:22 AM, Stephen Morris wrote:

I've read this document (and previous versions), I have no further
comments and support its publication as Informational

-- 
Sebastian Castro
DNS Specialist
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 495 2337
mobile: +64 21 400535

From matthijs@nlnetlabs.nl  Thu Jun 16 23:37:59 2011
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BD8311E808F for <dnsop@ietfa.amsl.com>; Thu, 16 Jun 2011 23:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V0634mCKrs03 for <dnsop@ietfa.amsl.com>; Thu, 16 Jun 2011 23:37:58 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6189E11E8083 for <dnsop@ietf.org>; Thu, 16 Jun 2011 23:37:58 -0700 (PDT)
Received: from [192.168.1.13] (ip123-112-174-82.adsl2.static.versatel.nl [82.174.112.123]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p5H6bpsQ040668 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 17 Jun 2011 08:37:51 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4DFAF63F.7070408@nlnetlabs.nl>
Date: Fri, 17 Jun 2011 08:37:51 +0200
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: dnsop@ietf.org
References: <4DF6475F.6030407@googlemail.com>
In-Reply-To: <4DF6475F.6030407@googlemail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Fri, 17 Jun 2011 08:37:51 +0200 (CEST)
Cc: Stephen Morris <sa.morris7@googlemail.com>
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 17 Jun 2011 06:37:59 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have read it and have one comment:

I would have expect that section 4.6. on Zone Signing would have a
subcomponent on Signing Scheme. Such a subcomponent would address the
number of keys used for signing and what roles (zsk, ksk) they fulfill.

I would like to see this addition and I support its publication as
Informational.

Best regards,

Matthijs


On 06/13/2011 07:22 PM, Stephen Morris wrote:
> Dear DNSOP WG,
> 
> This is to initiate a working group last call (WGLC) on
> 
>       "DNSSEC Policy & Practice Statement Framework"
>        draft-ietf-dnsop-dnssec-dps-framework-04.txt
> 
> Owing to the length of the document, the WGLC will last for three weeks
> instead of the usual two, and will therefore end on
> 
>              Monday, 4 July 2011, 23:59 UTC
> 
> The IETF tools site gives easy access to the current and previous
> versions, as well as differences and the like, at:
> 
> http://tools.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework-04
> 
> The document is aimed at a status of "Informational".
> 
> Please review the document and send any comments you may have to the
> list.  If you have no comments but support (or do not support) the
> document being published, please send that information to the list.
> 
> The document is subject to the normal five reviewer threshold.
> 
>     Stephen and Peter
>      DNSOP co-chairs
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJN+vY/AAoJEA8yVCPsQCW5UdUH/3VhFdnQ0e5GAz54yXevBuMY
FwLWeB1o6MvhRxbQH3PCsonU5cPCgkq/HaCt57QLwbcqmaCHjYCmPfhTA1qd7kmM
eODA2QQrJWEfKQowk8eVhm+une1qsG9R8Wo0CVYldkayL2BeQyT8KqKkHvsmAvLb
miq9v1UrFhs2S6wnnykS+AbQoetjUJo1ntwBnHmVKFjwrmxiUkiorCf8bjzdPITe
qSUvrW/gwFPd4HO412h++0U/X4jEv7x9+HhfW7ctgzA+Cjvy5evWbEJ2EbDfe7e5
hc0eJk/Oa5pf+sLVpvHBD5imJ9hY4GjHBK/rH+gKnJBfK64lFkREokmQ3YDzkAQ=
=Ht6p
-----END PGP SIGNATURE-----

From fredrik@kirei.se  Fri Jun 17 07:57:20 2011
Return-Path: <fredrik@kirei.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A78841F0C5F for <dnsop@ietfa.amsl.com>; Fri, 17 Jun 2011 07:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.699
X-Spam-Level: 
X-Spam-Status: No, score=0.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E392Y9AUqnwX for <dnsop@ietfa.amsl.com>; Fri, 17 Jun 2011 07:57:19 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [IPv6:2001:67c:394:15::9]) by ietfa.amsl.com (Postfix) with ESMTP id C70B91F0C5D for <dnsop@ietf.org>; Fri, 17 Jun 2011 07:57:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:references:in-reply-to:mime-version:content-transfer-encoding: content-type:message-id:cc:x-mailer:from:subject:date:to; bh=m/dtwLo7NPQNdIzfOlmfCQy+/ZUDFWvmTTHbWgqgm/k=; b=KyHayw3xGheskw7O39hnrofRz4eHAP608lxpYfw8Y72e6AadjDwGVZevQz69XanOgMeCX8kGPDmnE GRDF+t94utF//RQcNIRBBDci77/BlogrURWtXjWU53yFOU8oUhfmJRHCctTjepE7z5RVq1PtYiaH9p rcTGEIqTp2ZPZXQg=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Fri, 17 Jun 2011 16:57:11 +0200 (CEST)
References: <4DF6475F.6030407@googlemail.com> <4DFAF63F.7070408@nlnetlabs.nl>
In-Reply-To: <4DFAF63F.7070408@nlnetlabs.nl>
Mime-Version: 1.0 (iPad Mail 8J3)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-1--697055228
Message-Id: <5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se>
X-Mailer: iPad Mail (8J3)
From: Fredrik Ljunggren <fredrik@kirei.se>
Date: Fri, 17 Jun 2011 07:56:55 -0700
To: Matthijs Mekking <matthijs@NLnetLabs.nl>, "dnsop@ietf.org" <dnsop@ietf.org>
Cc: Stephen Morris <sa.morris7@googlemail.com>
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 17 Jun 2011 14:57:20 -0000

--Apple-Mail-1--697055228
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Matthjis,

thank you for reviewing the document. The intention is to cover those aspect=
s you mention (key separation, number of keys and roll-over scheme) in secti=
ons 6.4, 6.5 and 6.6. It is also intended that a drafter of a DPS may put a r=
ationale, explaining why a particular scheme has been choosen, directly in t=
he main component (6).

For this reason, I'm concerned that a new component may overlap with those a=
lready existing. However, I do agree that the intentions described above are=
 not very clear (section 4.6.4 - 4.6.6 of the document), and could be explai=
ned in more detail. Would that fulfil your purpose, or did I misunderstand y=
ou?

 -- Fredrik Ljunggren


On 16 jun 2011, at 23:37, Matthijs Mekking <matthijs@NLnetLabs.nl> wrote:

> I have read it and have one comment:
>=20
> I would have expect that section 4.6. on Zone Signing would have a
> subcomponent on Signing Scheme. Such a subcomponent would address the
> number of keys used for signing and what roles (zsk, ksk) they fulfill.
>=20
> I would like to see this addition and I support its publication as
> Informational.
>=20
> Best regards,
>=20
> Matthijs
>=20
>=20
> On 06/13/2011 07:22 PM, Stephen Morris wrote:
>> Dear DNSOP WG,
>>=20
>> This is to initiate a working group last call (WGLC) on
>>=20
>>      "DNSSEC Policy & Practice Statement Framework"
>>       draft-ietf-dnsop-dnssec-dps-framework-04.txt
>>=20
>> Owing to the length of the document, the WGLC will last for three weeks
>> instead of the usual two, and will therefore end on
>>=20
>>             Monday, 4 July 2011, 23:59 UTC
>>=20
>> The IETF tools site gives easy access to the current and previous
>> versions, as well as differences and the like, at:
>>=20
>> http://tools.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework-04
>>=20
>> The document is aimed at a status of "Informational".
>>=20
>> Please review the document and send any comments you may have to the
>> list.  If you have no comments but support (or do not support) the
>> document being published, please send that information to the list.
>>=20
>> The document is subject to the normal five reviewer threshold.
>>=20
>>    Stephen and Peter
>>     DNSOP co-chairs
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop

--Apple-Mail-1--697055228
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><body bgcolor=3D"#FFFFFF"><div>Matthjis,</div><div><br></div><div>than=
k you for reviewing the document. The intention is to cover those aspects yo=
u mention (key separation, number of keys and roll-over scheme) in sections 6=
.4, 6.5 and 6.6. It is also intended that a drafter of a DPS may put a ratio=
nale, explaining why a particular scheme has been choosen, directly in the m=
ain component (6).</div><div><br></div><div>For this reason, I'm concerned t=
hat a new component may overlap with those already existing. However, I do a=
gree that the intentions described above are not very clear (section 4.6.4 -=
 4.6.6 of the document), and could be explained in more detail. Would that f=
ulfil your purpose, or did I misunderstand you?</div><div><br></div><div>&nb=
sp;-- Fredrik Ljunggren</div><div><br></div><div><br>On 16 jun 2011, at 23:3=
7, Matthijs Mekking &lt;<a href=3D"mailto:matthijs@NLnetLabs.nl">matthijs@NL=
netLabs.nl</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><span>I hav=
e read it and have one comment:</span><br><span></span><br><span>I would hav=
e expect that section 4.6. on Zone Signing would have a</span><br><span>subc=
omponent on Signing Scheme. Such a subcomponent would address the</span><br>=
<span>number of keys used for signing and what roles (zsk, ksk) they fulfill=
.</span><br><span></span><br><span>I would like to see this addition and I s=
upport its publication as</span><br><span>Informational.</span><br><span></s=
pan><br><span>Best regards,</span><br><span></span><br><span>Matthijs</span>=
<br><span></span><br><span></span><br><span>On 06/13/2011 07:22 PM, Stephen M=
orris wrote:</span><br><blockquote type=3D"cite"><span>Dear DNSOP WG,</span>=
<br></blockquote><blockquote type=3D"cite"><span></span><br></blockquote><bl=
ockquote type=3D"cite"><span>This is to initiate a working group last call (=
WGLC) on</span><br></blockquote><blockquote type=3D"cite"><span></span><br><=
/blockquote><blockquote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"=
DNSSEC Policy &amp; Practice Statement Framework"</span><br></blockquote><bl=
ockquote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf=
-dnsop-dnssec-dps-framework-04.txt</span><br></blockquote><blockquote type=3D=
"cite"><span></span><br></blockquote><blockquote type=3D"cite"><span>Owing t=
o the length of the document, the WGLC will last for three weeks</span><br><=
/blockquote><blockquote type=3D"cite"><span>instead of the usual two, and wi=
ll therefore end on</span><br></blockquote><blockquote type=3D"cite"><span><=
/span><br></blockquote><blockquote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"x-apple-data-=
detectors://2" x-apple-data-detectors=3D"true">Monday, 4 July 2011, 23:59 UT=
C</a></span><br></blockquote><blockquote type=3D"cite"><span></span><br></bl=
ockquote><blockquote type=3D"cite"><span>The IETF tools site gives easy acce=
ss to the current and previous</span><br></blockquote><blockquote type=3D"ci=
te"><span>versions, as well as differences and the like, at:</span><br></blo=
ckquote><blockquote type=3D"cite"><span></span><br></blockquote><blockquote t=
ype=3D"cite"><span><a href=3D"http://tools.ietf.org/html/draft-ietf-dnsop-dn=
ssec-dps-framework-04" x-apple-data-detectors=3D"true"><a href=3D"http://too=
ls.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework-04">http://tools.ietf=
.org/html/draft-ietf-dnsop-dnssec-dps-framework-04</a></a></span><br></block=
quote><blockquote type=3D"cite"><span></span><br></blockquote><blockquote ty=
pe=3D"cite"><span>The document is aimed at a status of "Informational".</spa=
n><br></blockquote><blockquote type=3D"cite"><span></span><br></blockquote><=
blockquote type=3D"cite"><span>Please review the document and send any comme=
nts you may have to the</span><br></blockquote><blockquote type=3D"cite"><sp=
an>list. &nbsp;If you have no comments but support (or do not support) the</=
span><br></blockquote><blockquote type=3D"cite"><span>document being publish=
ed, please send that information to the list.</span><br></blockquote><blockq=
uote type=3D"cite"><span></span><br></blockquote><blockquote type=3D"cite"><=
span>The document is subject to the normal five reviewer threshold.</span><b=
r></blockquote><blockquote type=3D"cite"><span></span><br></blockquote><bloc=
kquote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;Stephen and Peter</span><br></=
blockquote><blockquote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;DNSOP co=
-chairs</span><br></blockquote><blockquote type=3D"cite"><span>_____________=
__________________________________</span><br></blockquote><blockquote type=3D=
"cite"><span>DNSOP mailing list</span><br></blockquote><blockquote type=3D"c=
ite"><span><a href=3D"mailto:DNSOP@ietf.org" x-apple-data-detectors=3D"true"=
><a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a></a></span><br></blockq=
uote><blockquote type=3D"cite"><span><a href=3D"https://www.ietf.org/mailman=
/listinfo/dnsop" x-apple-data-detectors=3D"true"><a href=3D"https://www.ietf=
.org/mailman/listinfo/dnsop">https://www.ietf.org/mailman/listinfo/dnsop</a>=
</a></span></blockquote></blockquote><div></div></body></html>=

--Apple-Mail-1--697055228--

From ogud@ogud.com  Fri Jun 17 13:31:51 2011
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29E8E21F8499 for <dnsop@ietfa.amsl.com>; Fri, 17 Jun 2011 13:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.499
X-Spam-Level: 
X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K+T1yzHZO8Gw for <dnsop@ietfa.amsl.com>; Fri, 17 Jun 2011 13:31:49 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 4D82221F8496 for <dnsop@ietf.org>; Fri, 17 Jun 2011 13:31:48 -0700 (PDT)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p5HKVkmB005461 for <dnsop@ietf.org>; Fri, 17 Jun 2011 16:31:47 -0400 (EDT) (envelope-from ogud@ogud.com)
Message-ID: <4DFBB9AF.4040207@ogud.com>
Date: Fri, 17 Jun 2011 16:31:43 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: dnsop@ietf.org
References: <4DF6475F.6030407@googlemail.com>
In-Reply-To: <4DF6475F.6030407@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 17 Jun 2011 20:31:51 -0000

On 13/06/2011 1:22 PM, Stephen Morris wrote:
> Dear DNSOP WG,
>
> This is to initiate a working group last call (WGLC) on
>
>        "DNSSEC Policy&  Practice Statement Framework"
>         draft-ietf-dnsop-dnssec-dps-framework-04.txt
>
> Owing to the length of the document, the WGLC will last for three weeks
> instead of the usual two, and will therefore end on
>
>               Monday, 4 July 2011, 23:59 UTC
>
> The IETF tools site gives easy access to the current and previous
> versions, as well as differences and the like, at:
>
> http://tools.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework-04
>
> The document is aimed at a status of "Informational".
>
> Please review the document and send any comments you may have to the
> list.  If you have no comments but support (or do not support) the
> document being published, please send that information to the list.
>
> The document is subject to the normal five reviewer threshold.
>

I have reviewed this document and support its publication.

Few nits and questions below:

a) DP and DSP should be included in the Definitions section 2, even 
though the abbreviations are are defined in section 1.2
Alternatively spell out in section 3.1. and 3.2 titles what DP and DPS are.

b) The document for all practical purposes is about the process until a 
zone has been signed/resigned. There is almost no discussion about the 
operation of the signed zone is this intentional or an omission ?
(the exceptions are the key rollover sections 4.5.4+5)

c) Section 4.6.9 should not limit itself to TTL's to types it should 
cover all types in the zone as the Maximum TTL in the zone impacts how 
fast keys can be added/removed from DNSKEY set.

d) Section 4.6.8 does not indicate what the purpose of this test is.
I think the purpose is to prevent bad data from showing up in the DNS.

f) There needs to be section (4.6.x) for zones that use NSEC3 as to the 
policy for changing NSEC3 parameters as this is similar to a ZSK roll-over.


Questions:

c)  should the DPS have a section describing if/when/how a zone (i.e. 
the one covered by the DPS) goes to unsigned?

d) Should the DPS have a section describing the zone's policy as how to 
perform an algorithm rollover ?
what I'm in particular looking for is in particular how long the zone 
expects to be signed by both algorithms.

	Olafur
	




From fredrik@kirei.se  Sun Jun 19 09:22:14 2011
Return-Path: <fredrik@kirei.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC2F711E80DD for <dnsop@ietfa.amsl.com>; Sun, 19 Jun 2011 09:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.698, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DUezd0DYHEKl for <dnsop@ietfa.amsl.com>; Sun, 19 Jun 2011 09:22:14 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [IPv6:2001:67c:394:15::9]) by ietfa.amsl.com (Postfix) with ESMTP id 9924411E809C for <dnsop@ietf.org>; Sun, 19 Jun 2011 09:22:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:content-type:mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to:x-mailer; bh=Bq1RKyok09qRKWbqCvq3LpXFVmBun7N/3bRkSOIOXkM=; b=coBY9TYUYV+Auv+K8mpM9h83NofXl7TRICV3EeBU4CR9tvAdcbjDHopfbxoZMJcFL5uWcEuj6eQ5G uN0M+lVsMuIwxtgOZ7CR139s6kgQtCMQMRW3NyzZmcXYo9mkno88k42fJdE4dO7YGJ69d9eFHepAWF 3tJHnM4OaefHgFqQ=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Sun, 19 Jun 2011 18:22:07 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fredrik Ljunggren <fredrik@kirei.se>
In-Reply-To: <4DFBB9AF.4040207@ogud.com>
Date: Sun, 19 Jun 2011 09:22:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B250FDB-509C-4D83-91DA-53E5B1333895@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFBB9AF.4040207@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>, dnsop@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sun, 19 Jun 2011 16:22:15 -0000

On 2011-06-17, at 13:31, Olafur Gudmundsson wrote:

> Few nits and questions below:
>=20
> a) DP and DSP should be included in the Definitions section 2, even =
though the abbreviations are are defined in section 1.2
> Alternatively spell out in section 3.1. and 3.2 titles what DP and DPS =
are.

Makes perfect sense. I prefer spelling it out in the section headers to =
keep the document from growing even further.


> b) The document for all practical purposes is about the process until =
a zone has been signed/resigned. There is almost no discussion about the =
operation of the signed zone is this intentional or an omission ?
> (the exceptions are the key rollover sections 4.5.4+5)

The document is intended to cover all security-related aspects and =
topics (including operational) which is impacted by the introduction =
DNSSEC in a zone. So in this context, technical operation of the signed =
zone is covered in the key-rollover sections (6.4, 6.5), in the =
signing/re-signing section (6.6) and the verification of the data to be =
signed (6.7, 6.8). =46rom a business-operational perspective, =
contingency and disaster-recovery planning is covered in 4.5 and 4.6. =
For key management life-cycle operations (such as generation of new keys =
and possibly also distribution, backup and destruction), should be =
covered in sections 5.1 and 5.3.

Are other aspects to operations which you think should be included in =
the document? (Or do you think the scope is too narrow?)


> c) Section 4.6.9 should not limit itself to TTL's to types it should =
cover all types in the zone as the Maximum TTL in the zone impacts how =
fast keys can be added/removed from DNSKEY set.

Good point, you are absolutely right. SOA expire and negative caching is =
also part of the equation.


> d) Section 4.6.8 does not indicate what the purpose of this test is.
> I think the purpose is to prevent bad data from showing up in the DNS.

Yes. It currently reads:

   This subsection addresses the controls around the verification of the
   resource records in order to validate and authenticate the data to be
   signed.

Should we clarify in that? Suggestions?


> f) There needs to be section (4.6.x) for zones that use NSEC3 as to =
the policy for changing NSEC3 parameters as this is similar to a ZSK =
roll-over.

The intention is to have this in 6.2. But I see that there are no =
mentions of policy for changing of NSEC3-parameters in 4.6.2 of the =
draft. I'm thinking of adding a sentence to the text in 4.6.2 instead of =
creating a new subsection?


> Questions:
>=20
> c)  should the DPS have a section describing if/when/how a zone (i.e. =
the one covered by the DPS) goes to unsigned?

There has been discussions about this among the authors, but so far =
we've agreed on that such procedure is a DR-procedure and may be =
described in 4.5.


> d) Should the DPS have a section describing the zone's policy as how =
to perform an algorithm rollover ?
> what I'm in particular looking for is in particular how long the zone =
expects to be signed by both algorithms.

I'm thinking that whatever forces a zone to change the algorithm is an =
unexpected event which has many dependencies to unknown factors (such as =
resolver implementations, new algorithms .. ), which is really hard to =
plan ahead for in such detail.

Although, the emergency case (where a algorithm has been fundamentally =
broken) should be covered in 4.5.3 (Entity private key compromise =
procedures).


-- Fredrik=20





From matthijs@nlnetlabs.nl  Mon Jun 20 01:01:00 2011
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81F1221F8454 for <dnsop@ietfa.amsl.com>; Mon, 20 Jun 2011 01:01:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pj0BpsixwKF3 for <dnsop@ietfa.amsl.com>; Mon, 20 Jun 2011 01:00:59 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0813421F8477 for <dnsop@ietf.org>; Mon, 20 Jun 2011 01:00:58 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:219:d1ff:feb1:85e8] (zoidberg.nlnetlabs.nl [IPv6:2001:7b8:206:1:219:d1ff:feb1:85e8]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p5K80rcW047603; Mon, 20 Jun 2011 10:00:54 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4DFEFE35.4050200@nlnetlabs.nl>
Date: Mon, 20 Jun 2011 10:00:53 +0200
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Fredrik Ljunggren <fredrik@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFAF63F.7070408@nlnetlabs.nl> <5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se>
In-Reply-To: <5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Mon, 20 Jun 2011 10:00:54 +0200 (CEST)
Cc: "dnsop@ietf.org" <dnsop@ietf.org>, Stephen Morris <sa.morris7@googlemail.com>
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Jun 2011 08:01:00 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Fredrik,

On 06/17/2011 04:56 PM, Fredrik Ljunggren wrote:
> Matthjis,
> 
> thank you for reviewing the document. The intention is to cover those
> aspects you mention (key separation, number of keys and roll-over
> scheme) in sections 6.4, 6.5 and 6.6. It is also intended that a drafter
> of a DPS may put a rationale, explaining why a particular scheme has
> been choosen, directly in the main component (6).

I think you mean sections 4.6.4, 4.6.5 and 4.6.6. Those sections
(especially the first two) cover ZSK specific rollover and KSK specific
roll-over schemes and are relevant in case a zone is subject to a
KSK/ZSK Split Signing Scheme.

However, if a zone is subject to a Single Type Signing Scheme, different
roll-over schemes are relevant.

The main component of 4.6 already says:

   This component covers all aspects of zone signing, including the
   cryptographic specification surrounding the Key Signing Key and Zone
   Signing Key, *signing scheme* and methodology for key roll-over and
   the actual zone signing.

I think 4.6.4 and 4.6.5 cover methodology for key roll-over. I miss a
section that says "Signing Scheme: This subcomponent describes which
signing scheme is in use."


Best regards,

Matthijs



> 
> For this reason, I'm concerned that a new component may overlap with
> those already existing. However, I do agree that the intentions
> described above are not very clear (section 4.6.4 - 4.6.6 of the
> document), and could be explained in more detail. Would that fulfil your
> purpose, or did I misunderstand you?
> 
>  -- Fredrik Ljunggren
> 
> 
> On 16 jun 2011, at 23:37, Matthijs Mekking <matthijs@NLnetLabs.nl
> <mailto:matthijs@NLnetLabs.nl>> wrote:
> 
>> I have read it and have one comment:
>>
>> I would have expect that section 4.6. on Zone Signing would have a
>> subcomponent on Signing Scheme. Such a subcomponent would address the
>> number of keys used for signing and what roles (zsk, ksk) they fulfill.
>>
>> I would like to see this addition and I support its publication as
>> Informational.
>>
>> Best regards,
>>
>> Matthijs
>>
>>
>> On 06/13/2011 07:22 PM, Stephen Morris wrote:
>>> Dear DNSOP WG,
>>>
>>> This is to initiate a working group last call (WGLC) on
>>>
>>>      "DNSSEC Policy & Practice Statement Framework"
>>>       draft-ietf-dnsop-dnssec-dps-framework-04.txt
>>>
>>> Owing to the length of the document, the WGLC will last for three weeks
>>> instead of the usual two, and will therefore end on
>>>
>>>             Monday, 4 July 2011, 23:59 UTC <x-apple-data-detectors://2>
>>>
>>> The IETF tools site gives easy access to the current and previous
>>> versions, as well as differences and the like, at:
>>>
>>> <http://tools.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework-04>http://tools.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework-04
>>>
>>> The document is aimed at a status of "Informational".
>>>
>>> Please review the document and send any comments you may have to the
>>> list.  If you have no comments but support (or do not support) the
>>> document being published, please send that information to the list.
>>>
>>> The document is subject to the normal five reviewer threshold.
>>>
>>>    Stephen and Peter
>>>     DNSOP co-chairs
>>> _______________________________________________
>>> DNSOP mailing list
>>> <mailto:DNSOP@ietf.org>DNSOP@ietf.org <mailto:DNSOP@ietf.org>
>>> <https://www.ietf.org/mailman/listinfo/dnsop>https://www.ietf.org/mailman/listinfo/dnsop
> 
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJN/v41AAoJEA8yVCPsQCW5MAkIAL93MT6fcSBVNVWEMNUbHdaz
8yjwd+LFVva2T0Q8gsT1naop/Gv8d6xR+47zESEm25y2FZgW+7yYkqOkQhmZ4Vrb
QnheXSL0o5fObglnOxV+7PHK4fX8EuCsxHyZ1dEqf5Q/SNX45rLaaYqF7WyCY9dZ
RsOaDRTb5q2t7EmvFL5C09qn9yzNo65N+AvHjZhLdsMQ4pDhfNRxH83zRK0Sqg/M
NaMMejUk6dWykYAHb8cC03NQOM7Pmw88synFcaIL7sNoZ+Np2jgMbxpKd9w1MG7n
NHOKeZQfdN6uLPtodcfwF7qMsIuDBK7a/cFG+ryyjNKGbiEoBCrzs4lb/b/w5iU=
=QCfl
-----END PGP SIGNATURE-----

From sa.morris7@googlemail.com  Mon Jun 20 02:52:19 2011
Return-Path: <sa.morris7@googlemail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 089D011E80A9 for <dnsop@ietfa.amsl.com>; Mon, 20 Jun 2011 02:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TSF6juIv+WNd for <dnsop@ietfa.amsl.com>; Mon, 20 Jun 2011 02:52:18 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B67D411E8095 for <dnsop@ietf.org>; Mon, 20 Jun 2011 02:52:17 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1037973wyj.31 for <dnsop@ietf.org>; Mon, 20 Jun 2011 02:52:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:x-enigmail-version:content-type:content-transfer-encoding; bh=f4tOuP9KoZWGGVYGZgD/we6GodC3DOa4g4ToaaIsb8w=; b=nbWc8JStv8mzZXSflT2sAYJHrdrRmUeBe8APf2NcRnHqynrSM+ffc6X2g1/gVJNjF6 CU/4Gd0+x/hHi4fAceFhj1h12MbNz6zRb2BbN4uisqL8wMKBJdM/dUQ2kVb0ydQulW0W JHFxkZepH1HdbeqGeDDegUGS8NI2BsaJVekGw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; b=sPEP24jjqcDYYiRoMkqADnInX0qJ+Ud1ZkTR/2ZKrOH5OAue9EjsY3+mP0EB1ur9/0 +KRWUGRjvvZYNZlJg7yEMguCQo66Fc6i+t88TLxI2JBS9Dk6ePJvb6kcNdj0tLOJnyJi +bZpO8vxd8UY9vJjGLB1MTz1fo6ySzz3oKYdM=
Received: by 10.217.6.197 with SMTP id y47mr1810303wes.55.1308563536745; Mon, 20 Jun 2011 02:52:16 -0700 (PDT)
Received: from stephen-morriss-macbook-pro.local ([217.155.47.50]) by mx.google.com with ESMTPS id ei4sm3044997wbb.9.2011.06.20.02.52.14 (version=SSLv3 cipher=OTHER); Mon, 20 Jun 2011 02:52:15 -0700 (PDT)
Message-ID: <4DFF184D.9080304@googlemail.com>
Date: Mon, 20 Jun 2011 10:52:13 +0100
From: Stephen Morris <sa.morris7@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: dnsop@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [DNSOP] Fwd: Nomcom 2011-12: Call for Volunteers
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Jun 2011 09:52:19 -0000

Any volunteers for this important function?

Stephen


--------------------------------------------
Subject: Nomcom 2011-12: Call for Volunteers
Date: Fri, 10 Jun 2011 19:56:06 -0700 (PDT)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>

The IETF nominating committee process for 2011-12 has begun. The IETF
nominating committee appoints folks to fill the open slots on the
IAOC, the IAB, and the IESG. The 10 nominating committee members are
selected randomly from a pool of volunteers. The more volunteers, the
better the chance we have of choosing a random yet representative
cross section of the IETF population.  The details of the nomcom
process can be found in RFC 3777.

To be eligible, volunteers for the nomcom need to have attended 3 of
the past 5 IETF meetings as of the time this announcement goes out
(i.e. IETF76-IETF80). If you qualify, and are not seeking appointment
to any of the open positions this nomcom will be filling, please
consider volunteering.

The list of people and posts whose terms end with the March 2012 IETF
meeting, and thus the positions for which the nominating committee is
responsible, are as follows:

IAB
===

Bernard Aboba
Hannes Tschofenig
Andrei Robachevsky
Olaf Kolkman
Spencer Dawkins
Ross Callon

IAOC
====

Marshall Eubanks

IESG
====

Peter Saint-Andre (Applications)
Jari Arkko (Internet)
Dan Romascanu (Operations & Management)
Gonzalo Camarillo (RAI)
Stewart Bryant (Routing)
Sean Turner (Security)
David Harrington (Transport)


The primary activity for this nomcom will begin during IETF-81 in
Quebec City and should be completed by January 2012. The nomcom will
be collecting requirements from the community, as well as talking to
candidates and to community members about candidates. There will be
regularly scheduled conference calls to ensure progress. Thus, being a
nomcom member does require some time commitment.

Please volunteer by sending an email to me before
11:59 pm EDT July 10, 2011 as follows:

To: suresh.krishnan@ericsson.com
Subject: Nomcom 2011-12 Volunteer

Please include the following information in the body of the mail:

Full Name:  // As you enter in the IETF Registration Form,
             // First/Given name followed by Last/Family Name

Current Primary Affiliation: // typically what goes in the Company
                              // field in the IETF Registration Form

Email Address(es): // all email addresses used to Register for the
                    // past 5 IETF meetings
		   // Please designate a Preferred email address for
                    // contact if there is more than one email address

Telephone number:  // With country code (for confirmation if selected)

Please expect an email response from me within 3 business days stating
whether or not you are qualified.  If you do not receive a response in
this timeframe, please re-send your email with the tag "RESEND:" added
to the subject line.

If you are not yet sure you would like to volunteer, please consider
that nomcom members play a very important role in shaping the
leadership of the IETF.  Ensuring the leadership of the IETF is fair
and balanced and comprised of those who can lead the IETF in the right
direction is an important responsibility that rests on the IETF
participants at large. Volunteering for the nomcom is a good way of
contributing in that direction.

I will be publishing a more detailed target timetable, as well as
details of the randomness seeds to be used for the RFC 3797 selection
process within the next few days.

Thank you in advance for your participation.

Suresh Krishnan
Nomcom Chair 2011-2012
Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


From scott.rose@nist.gov  Mon Jun 20 04:32:44 2011
Return-Path: <scott.rose@nist.gov>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95B1B11E810C for <dnsop@ietfa.amsl.com>; Mon, 20 Jun 2011 04:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gIfc28ckigvR for <dnsop@ietfa.amsl.com>; Mon, 20 Jun 2011 04:32:43 -0700 (PDT)
Received: from smtp.nist.gov (rimp1.nist.gov [129.6.16.226]) by ietfa.amsl.com (Postfix) with ESMTP id 8634E11E807E for <dnsop@ietf.org>; Mon, 20 Jun 2011 04:32:43 -0700 (PDT)
Received: from 107-140.antd.nist.gov (107-140.antd.nist.gov [129.6.140.107]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id p5KBWXdJ014361 for <dnsop@ietf.org>; Mon, 20 Jun 2011 07:32:33 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Scott Rose <scott.rose@nist.gov>
In-Reply-To: <4DFBB9AF.4040207@ogud.com>
Date: Mon, 20 Jun 2011 07:32:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <19E9EB73-3702-4149-9789-E96B7EC4B2E8@nist.gov>
References: <4DF6475F.6030407@googlemail.com> <4DFBB9AF.4040207@ogud.com>
To: dnsop WG <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: scott.rose@nist.gov
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Jun 2011 11:32:44 -0000

I have read previous versions of the draft, and skimmed this one looking =
at the changes.  I agree that the document is (almost) ready to go.

On Jun 17, 2011, at 4:31 PM, Olafur Gudmundsson wrote:

>=20
> Questions:
>=20
> c)  should the DPS have a section describing if/when/how a zone (i.e.=20=

> the one covered by the DPS) goes to unsigned?
>=20

I agree, adding this will improve the doc.

> d) Should the DPS have a section describing the zone's policy as how =
to=20
> perform an algorithm rollover ?
> what I'm in particular looking for is in particular how long the zone=20=

> expects to be signed by both algorithms.
>=20

There might be a variety of reasons that a zone may want to roll the =
algorithm(s) in use and that reason may dictate the length of time both =
algorithms are used.  So I don't think it's the best idea. =20

Scott


> 	Olafur
> =09
>=20
>=20
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Scott Rose
NIST
scottr@nist.gov
+1 301-975-8439
Google Voice: +1 571-249-3671
http://www.dnsops.gov/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From ogud@ogud.com  Mon Jun 20 08:20:20 2011
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53FD421F84A0 for <dnsop@ietfa.amsl.com>; Mon, 20 Jun 2011 08:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.539
X-Spam-Level: 
X-Spam-Status: No, score=-106.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Lce8-vxMNfr for <dnsop@ietfa.amsl.com>; Mon, 20 Jun 2011 08:20:18 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 476F021F85F7 for <dnsop@ietf.org>; Mon, 20 Jun 2011 08:20:14 -0700 (PDT)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p5KFKCSj026743; Mon, 20 Jun 2011 11:20:12 -0400 (EDT) (envelope-from ogud@ogud.com)
Message-ID: <4DFF652A.9020304@ogud.com>
Date: Mon, 20 Jun 2011 11:20:10 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Fredrik Ljunggren <fredrik@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFBB9AF.4040207@ogud.com> <8B250FDB-509C-4D83-91DA-53E5B1333895@kirei.se>
In-Reply-To: <8B250FDB-509C-4D83-91DA-53E5B1333895@kirei.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Jun 2011 15:20:20 -0000

Fredrik,

On 19/06/2011 12:22 PM, Fredrik Ljunggren wrote:
>
> On 2011-06-17, at 13:31, Olafur Gudmundsson wrote:
>
>> Few nits and questions below:
>>
>> a) DP and DSP should be included in the Definitions section 2, even though the abbreviations are are defined in section 1.2
>> Alternatively spell out in section 3.1. and 3.2 titles what DP and DPS are.
>
> Makes perfect sense. I prefer spelling it out in the section headers to keep the document from growing even further.
>

Good

>
>> b) The document for all practical purposes is about the process until a zone has been signed/resigned. There is almost no discussion about the operation of the signed zone is this intentional or an omission ?
>> (the exceptions are the key rollover sections 4.5.4+5)
>
> The document is intended to cover all security-related aspects and topics (including operational) which is impacted by the introduction DNSSEC in a zone. So in this context, technical operation of the signed zone is covered in the key-rollover sections (6.4, 6.5), in the signing/re-signing section (6.6) and the verification of the data to be signed (6.7, 6.8). From a business-operational perspective, contingency and disaster-recovery planning is covered in 4.5 and 4.6. For key management life-cycle operations (such as generation of new keys and possibly also distribution, backup and destruction), should be covered in sections 5.1 and 5.3.
>
> Are other aspects to operations which you think should be included in the document? (Or do you think the scope is too narrow?)
>

I think the document needs to be clearer as to what is NOT covered in a 
DSP.

It is fine for the document to say that it only covers: (in section 1.3)
"As to DNS operational aspects of the zone, Normal DNS operation is 
outside the scope of this document but best DNS operational practices 
are expected".
(as this is a product of the dnsop WG you need to say that or some 
readers may have expectations as how to set up name-servers).

Having said that does the document need to spell out how to recover if 
the signing infrastructure fails?

>
>> c) Section 4.6.9 should not limit itself to TTL's to types it should cover all types in the zone as the Maximum TTL in the zone impacts how fast keys can be added/removed from DNSKEY set.
>
> Good point, you are absolutely right. SOA expire and negative caching is also part of the equation.
>
>
>> d) Section 4.6.8 does not indicate what the purpose of this test is.
>> I think the purpose is to prevent bad data from showing up in the DNS.
>
> Yes. It currently reads:
>
>     This subsection addresses the controls around the verification of the
>     resource records in order to validate and authenticate the data to be
>     signed.
>
> Should we clarify in that? Suggestions?
>

What I want to know is, how does a failure in the signing system, show up?
1) updates to be blocked i.e. zone will stop processing updates.
2) New versions of zone will not show up on schedule
3) bad data will be published but will be replaced as soon as possible?
4) something else.

as this may affect Service level agreements having this spelled out is a 
good thing.

>
>> f) There needs to be section (4.6.x) for zones that use NSEC3 as to the policy for changing NSEC3 parameters as this is similar to a ZSK roll-over.
>
> The intention is to have this in 6.2. But I see that there are no mentions of policy for changing of NSEC3-parameters in 4.6.2 of the draft. I'm thinking of adding a sentence to the text in 4.6.2 instead of creating a new subsection?
>

That is fine,

>
>> Questions:
>>
>> c)  should the DPS have a section describing if/when/how a zone (i.e. the one covered by the DPS) goes to unsigned?
>
> There has been discussions about this among the authors, but so far we've agreed on that such procedure is a DR-procedure and may be described in 4.5.

I agree this frequently is a Disaster Recovery, but this may also be a 
policy decision.
In particular for a tld. having DS removed is estimated to take 2 days, 
flushing the DS takes another day, DNSKEY may still trusted by resolvers 
for the DNSKEY TTL.
Thus in the case of loss of zone signing the DS must be removed 3 days + 
DNSKEY TTL before the first signature in the zone expires.

If the zone is going to bring up a new signing system (with new keys) is 
the zone going be dual signed until old keys are flushed from the system.

>
>
>> d) Should the DPS have a section describing the zone's policy as how to perform an algorithm rollover ?
>> what I'm in particular looking for is in particular how long the zone expects to be signed by both algorithms.
>
> I'm thinking that whatever forces a zone to change the algorithm is an unexpected event which has many dependencies to unknown factors (such as resolver implementations, new algorithms .. ), which is really hard to plan ahead for in such detail.

Still does not cover if/how long the zone is going to be dual signed.

As to the planning for algorithm rollover.

The DSP may say
     "before any algorithm rollover a new DSP will be published x months 
before the event"
or   "in case of introduction of new algorithm in the zone the zone will 
be dual signed for x days"
or   "zone will NEVER roll algorithm only go to longer keys"
or   "zone will change from NSEC3 to NSEC 6 months after x% of the zone 
has DS records"

Algorithm rollover is the scariest part of DNSSEC operation,
>
> Although, the emergency case (where a algorithm has been fundamentally broken) should be covered in 4.5.3 (Entity private key compromise procedures).
>

I think there are two different cases, that need to be covered, key 
compromised and algorithm compromised.

The first one is important the second one is not a big deal as
DNSSEC is only one of many security systems that will be affected and 
slow and deliberate process in this case is better for everyone than 
quick over-reaction.

Thus the document should focus on the first case, by recommending that 
the zone publish a time-line for algorithm rollover and include a 
policy as how long the zone is going to be dual-signed.

	Olafur

From matthijs@nlnetlabs.nl  Wed Jun 22 08:22:09 2011
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B97211E80B8 for <dnsop@ietfa.amsl.com>; Wed, 22 Jun 2011 08:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vvcJZooQQ3pN for <dnsop@ietfa.amsl.com>; Wed, 22 Jun 2011 08:22:08 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 884C511E812B for <dnsop@ietf.org>; Wed, 22 Jun 2011 08:22:07 -0700 (PDT)
Received: from [192.168.1.13] (ip123-112-174-82.adsl2.static.versatel.nl [82.174.112.123]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p5MFM1fr008124 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Wed, 22 Jun 2011 17:22:02 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4E020899.1000805@nlnetlabs.nl>
Date: Wed, 22 Jun 2011 17:22:01 +0200
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: "'IETF DNSOP WG'" <dnsop@ietf.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Wed, 22 Jun 2011 17:22:02 +0200 (CEST)
Subject: [DNSOP] Fwd: New Version Notification for	draft-mekking-dnsop-dnssec-key-timing-bis-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Jun 2011 15:22:09 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

FYI,

I posted a new version of my key-timing-bis document.
Changes are:
- - It saw a first line of review.
- - Lots of style changes
- - More detailed explanation of Key States Unraveled
- - Introduced the idea of Key Rollover Stages.

rfcdiff:

http://tools.ietf.org/rfcdiff?url2=draft-mekking-dnsop-dnssec-key-timing-bis-01.txt

Best regards,

Matthijs


- -------- Original Message --------
Subject: New Version Notification for
draft-mekking-dnsop-dnssec-key-timing-bis-01.txt
Date: Wed, 22 Jun 2011 06:54:33 -0700
From: internet-drafts@ietf.org
To: matthijs@nlnetlabs.nl
CC: matthijs@nlnetlabs.nl

A new version of I-D, draft-mekking-dnsop-dnssec-key-timing-bis-01.txt
has been successfully submitted by Willem Matthijs Mekking and posted to
the IETF repository.

Filename:	 draft-mekking-dnsop-dnssec-key-timing-bis
Revision:	 01
Title:		 DNSSEC Key Timing Considerations Follow-Up
Creation date:	 2011-06-22
WG ID:		 Individual Submission
Number of pages: 45

Abstract:
   This document describes issues surrounding the timing of events
   related to DNSSEC policy.  It presents timelines for various key
   rollovers and DNSSEC policy changes regarding the key signing scheme.
   It explicitly identifies the relationships between the various
   parameters affecting the rollover process.

   This document updates [draft-ietf-dnsop-dnssec-key-timing] [MM: If
   approved] as it covers timelines for key rollovers in more detail and
   it covers additional key rollover scenarios, including algorithm
   rollover and single type key rollovers.





The IETF Secretariat

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOAgiZAAoJEA8yVCPsQCW5AgwIAIcFrPTxDgA9MnKgRbt/Yk/w
MWnRUSpC/whbFSLOTjk14wQS0kDfQYmeqzqyW34oWMeK0sGcxY9etezhDq9oSRMy
oZyCGfeDsvqpMCzJWPBpjxEPQ9lpMZT7XQoR/L/SJZNP1SYtBfxIsw639vyZz3I2
/rzU+vqHJsNmWmmOySG3TpNdbjJtsQGSFgyghiOMznvKfdSzbaLs/LOMuxZcJUQo
NWHZKBUOfdr/tM4fQ+tBSi1A4cx9Tzy9M/v0sNOHklwWVcDY4ZwEbBBEnalcmFAs
+PR2kjCq5vW0rcZDu83Uto/+zuiX9qowHrXKFMWDZYoDMU1S3v9mkWc68cYxkDs=
=fWIN
-----END PGP SIGNATURE-----

From fredrik@kirei.se  Wed Jun 22 10:51:19 2011
Return-Path: <fredrik@kirei.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9935228003 for <dnsop@ietfa.amsl.com>; Wed, 22 Jun 2011 10:51:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.349
X-Spam-Level: 
X-Spam-Status: No, score=-0.349 tagged_above=-999 required=5 tests=[AWL=0.349,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dNS0InJYM2QO for <dnsop@ietfa.amsl.com>; Wed, 22 Jun 2011 10:51:19 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [IPv6:2001:67c:394:15::9]) by ietfa.amsl.com (Postfix) with ESMTP id CFD8221F855D for <dnsop@ietf.org>; Wed, 22 Jun 2011 10:51:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:content-type:mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to:x-mailer; bh=XTnVVfVjvJ1AsIfNVyRuXpGmSXaH31/Crxg0eIOQwTA=; b=BRgDf8Cv6TOqBgn4DqKud0/qcpUZPPXVukucsIM9Lyo45aEdxjKzcfwDbr5xuTvCXM1vf4O2EWGzV T0Se0W/A81uw7b0HqmBM2XVhpHSVEFsscqDsPDCZgSYJiCPUbwL7u4+9qnq7W+MnQ2KGcXWWRVFthr zJa7IAgyqo/Zdzto=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Wed, 22 Jun 2011 19:51:14 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fredrik Ljunggren <fredrik@kirei.se>
In-Reply-To: <4DFEFE35.4050200@nlnetlabs.nl>
Date: Wed, 22 Jun 2011 10:51:09 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <65672F13-A23B-4C00-9F9A-4DD63DBA73D5@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFAF63F.7070408@nlnetlabs.nl> <5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se> <4DFEFE35.4050200@nlnetlabs.nl>
To: Matthijs Mekking <matthijs@NLnetLabs.nl>, dnsop@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Jun 2011 17:51:19 -0000

On 2011-06-20, at 01:00, Matthijs Mekking wrote:

> I think you mean sections 4.6.4, 4.6.5 and 4.6.6. Those sections
> (especially the first two) cover ZSK specific rollover and KSK =
specific
> roll-over schemes and are relevant in case a zone is subject to a
> KSK/ZSK Split Signing Scheme.
>=20
> However, if a zone is subject to a Single Type Signing Scheme, =
different
> roll-over schemes are relevant.
>=20
> The main component of 4.6 already says:
>=20
>   This component covers all aspects of zone signing, including the
>   cryptographic specification surrounding the Key Signing Key and Zone
>   Signing Key, *signing scheme* and methodology for key roll-over and
>   the actual zone signing.
>=20
> I think 4.6.4 and 4.6.5 cover methodology for key roll-over. I miss a
> section that says "Signing Scheme: This subcomponent describes which
> signing scheme is in use."

I think we may have different conceptions of what a "signing scheme" is =
(which may call for clarification of that in the definitions section).

For me, signing scheme is the signature life-time and re-signing =
frequency, paired with the key roll-over schedule. What exactly is it =
you are missing? What would a drafter put in the "signing scheme" =
section which does not fit into any of the other subsections?

-- Fredrik


From fredrik@kirei.se  Wed Jun 22 11:32:40 2011
Return-Path: <fredrik@kirei.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26C7511E809C for <dnsop@ietfa.amsl.com>; Wed, 22 Jun 2011 11:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.465
X-Spam-Level: 
X-Spam-Status: No, score=-0.465 tagged_above=-999 required=5 tests=[AWL=0.233,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kO+aOBqPTcm6 for <dnsop@ietfa.amsl.com>; Wed, 22 Jun 2011 11:32:36 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [IPv6:2001:67c:394:15::9]) by ietfa.amsl.com (Postfix) with ESMTP id 68C7111E8099 for <dnsop@ietf.org>; Wed, 22 Jun 2011 11:32:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:content-type:mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to:x-mailer; bh=GbejXyLNrFmRqRp74lYe3p9IK3EKlve1/E0akqTDg9M=; b=wNBevDAkY1vpzpzk0wfOyofHc6N4UeA/gqtdPypryqTQNdAlKi2en+i+F0wCKOtEkBIpGPq3HGNWk TYW1yc6mZWB9poz2Mf2zS1bi8Q9YxeD3Uvdz8YTzNEplFOGHrjES6abvgSn2vU7j18Xo6D8+fCcVSB mQlHUa3iguww0QDA=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Wed, 22 Jun 2011 20:32:30 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fredrik Ljunggren <fredrik@kirei.se>
In-Reply-To: <4DFF652A.9020304@ogud.com>
Date: Wed, 22 Jun 2011 11:32:24 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <85FE718C-2580-4A1F-9C7B-6BB784A6ED99@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFBB9AF.4040207@ogud.com> <8B250FDB-509C-4D83-91DA-53E5B1333895@kirei.se> <4DFF652A.9020304@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>, dnsop@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Jun 2011 18:32:40 -0000

On 2011-06-20, at 08:20, Olafur Gudmundsson wrote:

>> Are other aspects to operations which you think should be included in =
the document? (Or do you think the scope is too narrow?)
>>=20
>=20
> I think the document needs to be clearer as to what is NOT covered in =
a DSP.
>=20
> It is fine for the document to say that it only covers: (in section =
1.3)
> "As to DNS operational aspects of the zone, Normal DNS operation is =
outside the scope of this document but best DNS operational practices =
are expected".
> (as this is a product of the dnsop WG you need to say that or some =
readers may have expectations as how to set up name-servers).
>=20
> Having said that does the document need to spell out how to recover if =
the signing infrastructure fails?

I'm fine with clarifying the scope. Although, I strongly believe we =
should try real hard to not give recommendations as how to run a zone in =
the DPS framework document:

1.2.  Purpose

   The purpose of this document is twofold.  Firstly, the document aims
   to explain the concept of a DNSSEC Policy (DP) and a DNSSEC Practice
   Statement (DPS), and describe the relationship between a DP and a
   DPS.  Second, this document aims to present a framework to encourage
   and assist writers of Policies and Practice Statements in creating
   heterogenous and comparable documents.  In particular, the framework
   identifies the elements that should be considered in formulating a
   DP/DPS.  It does not, however, define a particular Policy or Practice
   Statement, not does it seek to provide legal advice or
   recommendations as to the contents.

>> Yes. It currently reads:
>>=20
>>    This subsection addresses the controls around the verification of =
the
>>    resource records in order to validate and authenticate the data to =
be
>>    signed.
>>=20
>> Should we clarify in that? Suggestions?
>=20
> What I want to know is, how does a failure in the signing system, show =
up?
> 1) updates to be blocked i.e. zone will stop processing updates.
> 2) New versions of zone will not show up on schedule
> 3) bad data will be published but will be replaced as soon as =
possible?
> 4) something else.
>=20
> as this may affect Service level agreements having this spelled out is =
a good thing.

Doesn't this belong in section 4.5.2 (Corrupted computing resources, =
software, and/or data) of a DPS - described in section 4.4.5 in the =
framework document?

>>> Questions:
>>>=20
>>> c)  should the DPS have a section describing if/when/how a zone =
(i.e. the one covered by the DPS) goes to unsigned?
>>=20
>> There has been discussions about this among the authors, but so far =
we've agreed on that such procedure is a DR-procedure and may be =
described in 4.5.
>=20
> I agree this frequently is a Disaster Recovery, but this may also be a =
policy decision.
> In particular for a tld. having DS removed is estimated to take 2 =
days, flushing the DS takes another day, DNSKEY may still trusted by =
resolvers for the DNSKEY TTL.
> Thus in the case of loss of zone signing the DS must be removed 3 days =
+ DNSKEY TTL before the first signature in the zone expires.
>=20
> If the zone is going to bring up a new signing system (with new keys) =
is the zone going be dual signed until old keys are flushed from the =
system.

The intention is that this is to be covered in the same sections as =
mentioned above (4.4.5 in the framework document). That is where a TLD =
(or other zone operator) would spell out the policy for recovering from =
a lost or compromised key.


>>> d) Should the DPS have a section describing the zone's policy as how =
to perform an algorithm rollover ?
>>> what I'm in particular looking for is in particular how long the =
zone expects to be signed by both algorithms.
>>=20
>> I'm thinking that whatever forces a zone to change the algorithm is =
an unexpected event which has many dependencies to unknown factors (such =
as resolver implementations, new algorithms .. ), which is really hard =
to plan ahead for in such detail.
>=20
> Still does not cover if/how long the zone is going to be dual signed.
>=20
> As to the planning for algorithm rollover.
>=20
> The DSP may say
>    "before any algorithm rollover a new DSP will be published x months =
before the event"
> or   "in case of introduction of new algorithm in the zone the zone =
will be dual signed for x days"
> or   "zone will NEVER roll algorithm only go to longer keys"
> or   "zone will change from NSEC3 to NSEC 6 months after x% of the =
zone has DS records"
>=20
> Algorithm rollover is the scariest part of DNSSEC operation,

Ok, I see what you mean. Good point. I'm thinking maybe clarifying on =
this under "Key lengths and algorithms" (and possibly also under =
"Authenticated denial of existence"), or do you think we should create a =
new subsection for it?


>> Although, the emergency case (where a algorithm has been =
fundamentally broken) should be covered in 4.5.3 (Entity private key =
compromise procedures).
>=20
> I think there are two different cases, that need to be covered, key =
compromised and algorithm compromised.
>=20
> The first one is important the second one is not a big deal as
> DNSSEC is only one of many security systems that will be affected and =
slow and deliberate process in this case is better for everyone than =
quick over-reaction.
>=20
> Thus the document should focus on the first case, by recommending that =
the zone publish a time-line for algorithm rollover and include a policy =
as how long the zone is going to be dual-signed.

Agreed. Although I think it may be worth mentioning the case of =
algorithm compromise under "Entity private key compromise procedures". =
Planning for that case may reduce the risk of quick over-reaction.

- f


From paul@xelerance.com  Wed Jun 22 13:25:39 2011
Return-Path: <paul@xelerance.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23BC411E8152; Wed, 22 Jun 2011 13:25:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rjR-D4tDDjDf; Wed, 22 Jun 2011 13:25:37 -0700 (PDT)
Received: from newtla.xelerance.com (newtla.xelerance.com [193.110.157.143]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA1511E8157; Wed, 22 Jun 2011 13:25:25 -0700 (PDT)
Received: from newtla.xelerance.com (newtla.xelerance.com [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by newtla.xelerance.com (Postfix) with ESMTP id 08EE5C661; Wed, 22 Jun 2011 16:25:23 -0400 (EDT)
Date: Wed, 22 Jun 2011 16:25:22 -0400 (EDT)
From: Paul Wouters <paul@xelerance.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
In-Reply-To: <AANLkTinwihQa4qO1a8o=j82Csx6qMgyTGFmS+ccsbvrD@mail.gmail.com>
Message-ID: <alpine.LFD.1.10.1106221608190.30438@newtla.xelerance.com>
References: <AANLkTik4MeDWDRxXLkPd8k6HPVeKY9_7p4FQWzyXwvFD@mail.gmail.com> <201010041437.o94EbTHT029454@fs4113.wdf.sap.corp> <AANLkTinwihQa4qO1a8o=j82Csx6qMgyTGFmS+ccsbvrD@mail.gmail.com>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: dnsop@ietf.org, tls@ietf.org
Subject: Re: [DNSOP] [TLS] [pkix] Cert Enumeration and Key Assurance With DNSSEC
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Jun 2011 20:25:39 -0000

On Mon, 4 Oct 2010, Phillip Hallam-Baker wrote:

> 2) Sanction CAs that issue unauthorized certificates

What would you say a valid sanction would be for a CA that issues a bad
certificate for 10 major websites like Mozilla and Yahoo?

What should the sanction be for a CA whose reseller's subCAs issues such
bad certificates?

What would the sanctions be for non-FQDN EV certs issued?

What would the current total sanction be for Comodo, a player who has
someone as honourable as you working for them based on last year's events
plus EV violations detected via the SSL observatory data?

How could an external party review the set of unknown serials revoked by
Comodo to determine the kind/amount of sanction?

Would Comodo's "licencse" have been revoked, or would the sanctions have
been limited by money? If so, would the money be in absolute value or
percantage of profit/turnover?

What would or could Comodo have done differently if such a sanction had
been applied?




There is really only one sanction everyone can determine by themselves
to apply to any CA, the decision to trust them more or less then
themselves. If the latter, DNSSEC with DANE is an excellent choice. Feel
free to interpret DANE as each TLS owner's "sanction".

Paul

From matthijs@nlnetlabs.nl  Thu Jun 23 02:21:56 2011
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4E711E80C5 for <dnsop@ietfa.amsl.com>; Thu, 23 Jun 2011 02:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S-N74Nd3hZs8 for <dnsop@ietfa.amsl.com>; Thu, 23 Jun 2011 02:21:54 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4731C11E80BB for <dnsop@ietf.org>; Thu, 23 Jun 2011 02:21:53 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:219:d1ff:feb1:85e8] (zoidberg.nlnetlabs.nl [IPv6:2001:7b8:206:1:219:d1ff:feb1:85e8]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p5N9Losu005815; Thu, 23 Jun 2011 11:21:50 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4E0305AE.10009@nlnetlabs.nl>
Date: Thu, 23 Jun 2011 11:21:50 +0200
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Fredrik Ljunggren <fredrik@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFAF63F.7070408@nlnetlabs.nl>	<5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se>	<4DFEFE35.4050200@nlnetlabs.nl> <65672F13-A23B-4C00-9F9A-4DD63DBA73D5@kirei.se>
In-Reply-To: <65672F13-A23B-4C00-9F9A-4DD63DBA73D5@kirei.se>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Thu, 23 Jun 2011 11:21:50 +0200 (CEST)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 23 Jun 2011 09:21:56 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/22/2011 07:51 PM, Fredrik Ljunggren wrote:
> 
> On 2011-06-20, at 01:00, Matthijs Mekking wrote:
> 
>> I think you mean sections 4.6.4, 4.6.5 and 4.6.6. Those sections 
>> (especially the first two) cover ZSK specific rollover and KSK
>> specific roll-over schemes and are relevant in case a zone is
>> subject to a KSK/ZSK Split Signing Scheme.
>> 
>> However, if a zone is subject to a Single Type Signing Scheme,
>> different roll-over schemes are relevant.
>> 
>> The main component of 4.6 already says:
>> 
>> This component covers all aspects of zone signing, including the 
>> cryptographic specification surrounding the Key Signing Key and
>> Zone Signing Key, *signing scheme* and methodology for key
>> roll-over and the actual zone signing.
>> 
>> I think 4.6.4 and 4.6.5 cover methodology for key roll-over. I miss
>> a section that says "Signing Scheme: This subcomponent describes
>> which signing scheme is in use."
> 
> I think we may have different conceptions of what a "signing scheme"
> is (which may call for clarification of that in the definitions
> section).
> 
> For me, signing scheme is the signature life-time and re-signing
> frequency, paired with the key roll-over schedule. What exactly is it
> you are missing? What would a drafter put in the "signing scheme"
> section which does not fit into any of the other subsections?

Basically it comes to this: It is not clear to me in what component I
can describe whether:
- - I am going to use a ZSK/KSK split signing scheme (where I have two
keys for signing, one to sign the DNSKEY RRset and another to sign the
rest), or
- - I am going to use a Single Type Signing Scheme (where I have one key
that signs all).

The two different methods I call signing scheme.

If I am going to use ZSK/KSK Split, there is a component that covers
ZSK(-only) roll-over and there is a component that covers KSK(-only)
roll-over.

If I am going to use a Single Type Signing Scheme, where do I describe
the roll-over schedule for that key.

Best regards,

Matthijs

> -- Fredrik
> 
> _______________________________________________ DNSOP mailing list 
> DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOAwWuAAoJEA8yVCPsQCW5HhkIALfUd8igclOaZ4gOU6kFp4sC
iTyOrRauqvkt5deCrZc2XiSu3Nl13Dn1DrLA2XrkXoR0A5ABXm9uWjmATaQZOjbn
p3zgc0o0oWGhfExR3g4fsaGdBmW4a8thfr5G/zVKp1SQ9fXhJvSDiAbnR37i/1d1
4cSZl/E+z6TKaVgMpnURUeGVoeNcfdu0Eltupc+TKeGxpcrdBbhwyFzSx4W9lFOe
fowDGnsi0bqsvqfLb2HqrHxj7j7iKxGT3p4HwwTNYoxULZVK1phfbGiwI2PTlxD3
s0yO27wrl/d+a8VQLSczKfoJkpQo+uFBraSxokuteDMa4l8xlX8eFnGoCNH3nGM=
=yKU3
-----END PGP SIGNATURE-----

From fredrik@kirei.se  Thu Jun 23 09:51:50 2011
Return-Path: <fredrik@kirei.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8476F11E8141 for <dnsop@ietfa.amsl.com>; Thu, 23 Jun 2011 09:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.523
X-Spam-Level: 
X-Spam-Status: No, score=-0.523 tagged_above=-999 required=5 tests=[AWL=0.175,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xc00p-fhs5dY for <dnsop@ietfa.amsl.com>; Thu, 23 Jun 2011 09:51:49 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [IPv6:2001:67c:394:15::9]) by ietfa.amsl.com (Postfix) with ESMTP id 9B7BC11E811A for <dnsop@ietf.org>; Thu, 23 Jun 2011 09:51:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:content-type:mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to:x-mailer; bh=gt/0Y19FEkvaheuW8Cqmmoda4PVVYm9C9T3w323B+EQ=; b=vJA8nADj/CclF/W++qJszmpo70X7Q8tE6Kj5Xm2EPqQ5EUQhDFtxhSIy8v4DmNAFJhYTBUij8Fh3Z FXjzCDXEJWAVheo2gMtWCLC0wNxa4FJUfc3qXJVfoDYILIiB9IGA6op6j+u/n9qdMGC94+1ltMz9St XPz4kcA76+P3WdXQ=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Thu, 23 Jun 2011 18:51:44 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fredrik Ljunggren <fredrik@kirei.se>
In-Reply-To: <4E0305AE.10009@nlnetlabs.nl>
Date: Thu, 23 Jun 2011 09:51:40 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1586A958-90DB-47DA-977E-B0DDB1AAC5BB@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFAF63F.7070408@nlnetlabs.nl>	<5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se>	<4DFEFE35.4050200@nlnetlabs.nl> <65672F13-A23B-4C00-9F9A-4DD63DBA73D5@kirei.se> <4E0305AE.10009@nlnetlabs.nl>
To: Matthijs Mekking <matthijs@NLnetLabs.nl>, dnsop@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 23 Jun 2011 16:51:50 -0000

On 2011-06-23, at 02:21, Matthijs Mekking wrote:

> The two different methods I call signing scheme.

Ok! I follow you.

> If I am going to use a Single Type Signing Scheme, where do I describe
> the roll-over schedule for that key.

A KSK is a DNSKEY with the SEP bit set. And for validation to work with =
a single key, that key has to have the SEP bit set. So I would suggest =
roll-overs in a single-key zone to be described under KSK roll-over.

And you do have a point that this should be spelled out in the DPS =
framework document. Although, I'm a bit reluctant to having a whole new =
section for this, but would rather see it included in the existing =
sections.=20

What do you think about adding some descriptive text to the section "Key =
lengths and algorithms", to include split/single key signing there? And =
using the existing subsections as relevant for roll-overs?

-- Fredrik


From cet1@hermes.cam.ac.uk  Thu Jun 23 10:51:18 2011
Return-Path: <cet1@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A700411E8184 for <dnsop@ietfa.amsl.com>; Thu, 23 Jun 2011 10:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sCa0bfQNtfr1 for <dnsop@ietfa.amsl.com>; Thu, 23 Jun 2011 10:51:15 -0700 (PDT)
Received: from ppsw-52.csi.cam.ac.uk (ppsw-52.csi.cam.ac.uk [131.111.8.152]) by ietfa.amsl.com (Postfix) with ESMTP id EB1E011E817E for <dnsop@ietf.org>; Thu, 23 Jun 2011 10:51:14 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:50226) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:cet1) id 1QZo3a-0004is-Fl (Exim 4.72) (return-path <cet1@hermes.cam.ac.uk>); Thu, 23 Jun 2011 18:51:10 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:cet1) id 1QZo3a-0001Ja-SF (Exim 4.67) (return-path <cet1@hermes.cam.ac.uk>); Thu, 23 Jun 2011 18:51:10 +0100
Received: from [131.111.11.47] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.4); 23 Jun 2011 18:51:10 +0100
Date: 23 Jun 2011 18:51:10 +0100
From: Chris Thompson <cet1@cam.ac.uk>
To: Fredrik Ljunggren <fredrik@kirei.se>
Message-ID: <Prayer.1.3.4.1106231851100.14389@hermes-2.csi.cam.ac.uk>
In-Reply-To: <1586A958-90DB-47DA-977E-B0DDB1AAC5BB@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFAF63F.7070408@nlnetlabs.nl> <5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se> <4DFEFE35.4050200@nlnetlabs.nl> <65672F13-A23B-4C00-9F9A-4DD63DBA73D5@kirei.se> <4E0305AE.10009@nlnetlabs.nl> <1586A958-90DB-47DA-977E-B0DDB1AAC5BB@kirei.se>
X-Mailer: Prayer v1.3.4
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Chris Thompson <cet1@hermes.cam.ac.uk>
Cc: dnsop@ietf.org, Matthijs Mekking <matthijs@NLnetLabs.nl>
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cet1@cam.ac.uk
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: <http://www.ietf.org/mail-archive/web/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: Thu, 23 Jun 2011 17:51:27 -0000

On Jun 23 2011, Fredrik Ljunggren wrote:

>A KSK is a DNSKEY with the SEP bit set. And for validation to work with
>a single key, that key has to have the SEP bit set.

Shome mishtake, shurely? There are zones around that have only one DNSKEY,
without the SEP bit, and they validate just fine. To take two examples at
random: "nu" and "co.uk".

"nu" had its 15 minutes of fame when it failed to get included in
dlv.isc.org when ISC were importing the ITAR, just because the SEP bit
was missing. I seem to recall that ISC had to make special arrangements
to fix that.

"co.uk", and the other sub-zones of "uk" managed by Nominet, are more
recent examples.

-- 
Chris Thompson               University of Cambridge Computing Service,
Email: cet1@ucs.cam.ac.uk    New Museums Site, Cambridge CB2 3QH,
Phone: +44 1223 334715       United Kingdom.

From Ed.Lewis@neustar.biz  Thu Jun 23 11:25:15 2011
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 914509E805D for <dnsop@ietfa.amsl.com>; Thu, 23 Jun 2011 11:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.283
X-Spam-Level: 
X-Spam-Status: No, score=-106.283 tagged_above=-999 required=5 tests=[AWL=0.316, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XaPs0qPRSfbj for <dnsop@ietfa.amsl.com>; Thu, 23 Jun 2011 11:25:15 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id BC1919E805B for <dnsop@ietf.org>; Thu, 23 Jun 2011 11:25:14 -0700 (PDT)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p5NIPBbp019031; Thu, 23 Jun 2011 14:25:12 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.204.119] by Work-Laptop-2.local (PGP Universal service); Thu, 23 Jun 2011 14:25:12 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Thu, 23 Jun 2011 14:25:12 -0400
Mime-Version: 1.0
Message-Id: <a06240800ca29326fff37@[10.31.204.119]>
In-Reply-To: <1586A958-90DB-47DA-977E-B0DDB1AAC5BB@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFAF63F.7070408@nlnetlabs.nl> <5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se> <4DFEFE35.4050200@nlnetlabs.nl> <65672F13-A23B-4C00-9F9A-4DD63DBA73D5@kirei.se> <4E0305AE.10009@nlnetlabs.nl> <1586A958-90DB-47DA-977E-B0DDB1AAC5BB@kirei.se>
Date: Thu, 23 Jun 2011 14:17:35 -0400
To: Fredrik Ljunggren <fredrik@kirei.se>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: dnsop@ietf.org, Matthijs Mekking <matthijs@NLnetLabs.nl>
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 23 Jun 2011 18:25:15 -0000

At 9:51 -0700 6/23/11, Fredrik Ljunggren wrote:

>A KSK is a DNSKEY with the SEP bit set. And for validation to work with a
>single key, that key has to have the SEP bit set. So I would suggest
>roll-overs in a single-key zone to be described under KSK roll-over.

SEP != KSK.

In the protocol, there is no distinction between KSK and ZSK.  The 
SEP bit signals the intent of the zone administrator to distribute 
this key to other parties to develop a chain of trust.

What is known as a KSK is a key that signs only other keys in the 
DNSKEY set and is (in the vast majority of cases) intended to be 
distributed to another party, for example, in a DS record to the 
parent zone.

A zone may use one key to sign everything (Common Signing Key is a 
designation I like) and have it be marked with the SEP bit.

The SEP bit is not a factor in validation.  It's a factor in key 
management tools.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

I'm overly entertained.

From matthijs@nlnetlabs.nl  Fri Jun 24 01:41:18 2011
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD0E821F84D8 for <dnsop@ietfa.amsl.com>; Fri, 24 Jun 2011 01:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xVz0e3GiCupD for <dnsop@ietfa.amsl.com>; Fri, 24 Jun 2011 01:41:17 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E15521F84D6 for <dnsop@ietf.org>; Fri, 24 Jun 2011 01:41:16 -0700 (PDT)
Received: from [192.168.1.13] (ip123-112-174-82.adsl2.static.versatel.nl [82.174.112.123]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p5O8fD12072288 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 24 Jun 2011 10:41:14 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4E044DA9.9040806@nlnetlabs.nl>
Date: Fri, 24 Jun 2011 10:41:13 +0200
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Fredrik Ljunggren <fredrik@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFAF63F.7070408@nlnetlabs.nl>	<5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se>	<4DFEFE35.4050200@nlnetlabs.nl> <65672F13-A23B-4C00-9F9A-4DD63DBA73D5@kirei.se> <4E0305AE.10009@nlnetlabs.nl> <1586A958-90DB-47DA-977E-B0DDB1AAC5BB@kirei.se>
In-Reply-To: <1586A958-90DB-47DA-977E-B0DDB1AAC5BB@kirei.se>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Fri, 24 Jun 2011 10:41:14 +0200 (CEST)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 24 Jun 2011 08:41:18 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Fredik,

As others already pointed out. A key with the SEP bit set is not
necessarily a KSK.

I like to see Key Signing (KS) and Zone Signing (ZS) as a role of a key.
A key can than have one or both of these roles. The document focuses too
much on the situation where those roles are divided between different
keys (aka a KSK/ZSK split). Therefore, it might be difficult to fit in
the Single Type Signing Scheme into the framework.

I propose the following changes:

- --------------------------------------------------------------------------

Section 2 Definitions:

Key Roll Over - A operational process of DNSSEC to change one of the
keys currently used for signing.

Section 4.4.5. Compromise and Disaster Recovery:

Bullet point 2:
The recovery procedures used ... is re-established, whether one of the
keys requires a roll-over, how to assess the damage and carry out the
root cause analysis.

Bullet point 3:
The recovery procedures used if one of the keys is compromised.  These
procedures describe how ...

Section 4.6.1. Key lengths, algorithms and roles

This subcomponent describes whether the keys are used as Key Signing
Key, Zone Singing Key or both. It describes the key generation algorithm
and the key length used to create the keys.

Merge 4.6.4 and 4.6.5: Key Roll-over

This subcomponent explains the roll-over scheme per key. Roll-overs vary
depending on the roles of the key (e.g. does the key act as a Key
Signing Key, Zone Singing Key or both).

- --------------------------------------------------------------------------

I think these are fairly small changes and makes a Single Type Signing
Scheme fit more into the framework.

Best regards.

Matthijs

PS: Perhaps the Flags Field (to SEP or not to SEP) should also be
covered. I think it would fit in Section 4.6.1.



On 06/23/2011 06:51 PM, Fredrik Ljunggren wrote:
> 
> On 2011-06-23, at 02:21, Matthijs Mekking wrote:
> 
>> The two different methods I call signing scheme.
> 
> Ok! I follow you.
> 
>> If I am going to use a Single Type Signing Scheme, where do I
>> describe the roll-over schedule for that key.
> 
> A KSK is a DNSKEY with the SEP bit set. And for validation to work
> with a single key, that key has to have the SEP bit set. So I would
> suggest roll-overs in a single-key zone to be described under KSK
> roll-over.
> 
> And you do have a point that this should be spelled out in the DPS
> framework document. Although, I'm a bit reluctant to having a whole
> new section for this, but would rather see it included in the
> existing sections.
> 
> What do you think about adding some descriptive text to the section
> "Key lengths and algorithms", to include split/single key signing
> there? And using the existing subsections as relevant for
> roll-overs?
> 
> -- Fredrik
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOBE2pAAoJEA8yVCPsQCW5hJYIAIQ5ELccaM7vupiisVI+n9DF
15QJ8fXB81Ql4si2GSqeNIdVUmVt0Vb+OPagGAXfnEKt3O/Cj4ARuGKvRrNQJNUH
uy1n8dRyx5MkaW1hqruBywS68Pmra9OYn1Mbi5TJTKBjTl9oHwPCrR1gnZmtFLFf
ZqeZnQM/z+K6mkGGfxt4WdIQyzIjkTAN6atEi7f7Mfv6qJH3Gbc4PG6bLudkBQG+
uofyJUg6U0tGJDyGq7T0IMW9YyYAjavUzQKqdgVv5JMozrszzc8LMTBca4zGwDvB
wZUaFJFcrh8phJ5hwjv7Ymf02jis4I1u885tGjqrgZ8NE0/9+aj6QwNlT384SPw=
=VtNH
-----END PGP SIGNATURE-----

From fredrik@kirei.se  Fri Jun 24 14:27:49 2011
Return-Path: <fredrik@kirei.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0D3311E8164 for <dnsop@ietfa.amsl.com>; Fri, 24 Jun 2011 14:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.558
X-Spam-Level: 
X-Spam-Status: No, score=-0.558 tagged_above=-999 required=5 tests=[AWL=0.140,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rqBVU40ZAOgk for <dnsop@ietfa.amsl.com>; Fri, 24 Jun 2011 14:27:46 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [IPv6:2001:67c:394:15::9]) by ietfa.amsl.com (Postfix) with ESMTP id D8C7D11E810C for <dnsop@ietf.org>; Fri, 24 Jun 2011 14:27:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:content-type:mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to:x-mailer; bh=5pwAqp8aRsuFMlyNJCxY/6QEmoh+zJN+cTWCtmZZFu4=; b=xTOKu/N+CSUvDjhrUE5P/iWB6B6YC1vpVkw/fWmXNHyyCix7ZqG1LKfO43/kDyb6va8pObV2FkO4w 4189HIW9sk//cIeC71uUHenrLCtEGjGegGyy/KsP0Qz5VA+uavwkjm/G17cXb+q076dKcr1LEHWWBE AI5NLQGi5NTSlRaU=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Fri, 24 Jun 2011 23:27:40 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fredrik Ljunggren <fredrik@kirei.se>
In-Reply-To: <4E044DA9.9040806@nlnetlabs.nl>
Date: Fri, 24 Jun 2011 14:27:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E7E6286-ADC6-4420-8233-C3A8D4A56DF2@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFAF63F.7070408@nlnetlabs.nl>	<5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se>	<4DFEFE35.4050200@nlnetlabs.nl> <65672F13-A23B-4C00-9F9A-4DD63DBA73D5@kirei.se> <4E0305AE.10009@nlnetlabs.nl> <1586A958-90DB-47DA-977E-B0DDB1AAC5BB@kirei.se> <4E044DA9.9040806@nlnetlabs.nl>
To: Matthijs Mekking <matthijs@NLnetLabs.nl>, dnsop@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 24 Jun 2011 21:27:49 -0000

On 2011-06-24, at 01:41, Matthijs Mekking wrote:

> I like to see Key Signing (KS) and Zone Signing (ZS) as a role of a =
key.

Agreed, although I prefer the term "key type" rather than "role", as =
"role" may be confused the controls surrounding personnel and "trusted =
roles".

> I propose the following changes:

I like the idea of merging the subsections covering key roll-overs.=20

> I think these are fairly small changes and makes a Single Type Signing
> Scheme fit more into the framework.

I agree with the only remark to as calling it key types, rather than =
roles. If there are no objections I'll incorporate these and Olafur's =
suggested changes shortly and submit a -05 version of the draft.

-- Fredrik


From matthijs@nlnetlabs.nl  Mon Jun 27 13:40:29 2011
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A169211E817F for <dnsop@ietfa.amsl.com>; Mon, 27 Jun 2011 13:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KA8U4UNY9zC9 for <dnsop@ietfa.amsl.com>; Mon, 27 Jun 2011 13:40:28 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EE19C11E817D for <dnsop@ietf.org>; Mon, 27 Jun 2011 13:40:27 -0700 (PDT)
Received: from [192.168.1.8] (ip123-112-174-82.adsl2.static.versatel.nl [82.174.112.123]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p5RKeKQJ077072; Mon, 27 Jun 2011 22:40:20 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4E08EAB4.6090708@nlnetlabs.nl>
Date: Mon, 27 Jun 2011 22:40:20 +0200
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: Fredrik Ljunggren <fredrik@kirei.se>
References: <4DF6475F.6030407@googlemail.com> <4DFAF63F.7070408@nlnetlabs.nl>	<5DF2FF72-C755-4A6A-ABA1-89372D19FE87@kirei.se>	<4DFEFE35.4050200@nlnetlabs.nl> <65672F13-A23B-4C00-9F9A-4DD63DBA73D5@kirei.se> <4E0305AE.10009@nlnetlabs.nl> <1586A958-90DB-47DA-977E-B0DDB1AAC5BB@kirei.se> <4E044DA9.9040806@nlnetlabs.nl> <0E7E6286-ADC6-4420-8233-C3A8D4A56DF2@kirei.se>
In-Reply-To: <0E7E6286-ADC6-4420-8233-C3A8D4A56DF2@kirei.se>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Mon, 27 Jun 2011 22:40:23 +0200 (CEST)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 27 Jun 2011 20:40:29 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Fredrik,

On 06/24/2011 11:27 PM, Fredrik Ljunggren wrote:
> 
> On 2011-06-24, at 01:41, Matthijs Mekking wrote:
> 
>> I like to see Key Signing (KS) and Zone Signing (ZS) as a role of a
>> key.
> 
> Agreed, although I prefer the term "key type" rather than "role", as
> "role" may be confused the controls surrounding personnel and
> "trusted roles".

That's fine with me.

Best regards,

Matthijs

> 
>> I propose the following changes:
> 
> I like the idea of merging the subsections covering key roll-overs.
> 
>> I think these are fairly small changes and makes a Single Type
>> Signing Scheme fit more into the framework.
> 
> I agree with the only remark to as calling it key types, rather than
> roles. If there are no objections I'll incorporate these and Olafur's
> suggested changes shortly and submit a -05 version of the draft.
> 
> -- Fredrik
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOCOqzAAoJEA8yVCPsQCW5l/oIANKXFmJ6IS7gTbPEua/kgSna
iDGfWJ8mflwxqzSEwswayyhwihy0LtsPCUqREvYC/nUQwYC+M04aSWOTg9Mfit0X
NzlpiUlqnw84N5eh7vW7s14Na9zj1gW93EnA1utHFTM2LwWdKCAw/icsZ7eWxZjN
6CcuKjJRx+YRobD3+asDJA4ExEJE4z6nE1GknAA4OzkJ0iOfBLYtTfKxjF6wPSZQ
XmaqNr3L1nJzlBIgvPxbE0vXmAelwCGNzX/22bivzcp0MC1Xt14hZL0yKSLWe74+
UXdbsI57e4d91tN4gVErG19kXFHyd2RX8re/MK+9RDhZygywdrYhdzUJZLpdShM=
=a4Lf
-----END PGP SIGNATURE-----

From sa.morris7@googlemail.com  Thu Jun 30 07:32:15 2011
Return-Path: <sa.morris7@googlemail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C516C11E817A for <dnsop@ietfa.amsl.com>; Thu, 30 Jun 2011 07:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id swaKMgrSnh6j for <dnsop@ietfa.amsl.com>; Thu, 30 Jun 2011 07:32:15 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id D0F1D11E8075 for <dnsop@ietf.org>; Thu, 30 Jun 2011 07:32:14 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1824264wyj.31 for <dnsop@ietf.org>; Thu, 30 Jun 2011 07:32:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=ddXgipTdC1/H6Co1ixciLRJuM8lsJ3W3QjjQ3a+JfVo=; b=Bx3i02HHZG+n78o8Q0X7N6hxy1eGCadhjMXJFLGk6sVKzoEn3GCLdqSYyqHtf/znyk 1jc75GRncY6TUOLXlUo+0hE1ziIiUCWxSbDblVD0rxdkCs7CByhmlXFgCcsVRVX14fPw PND4/hYHj9nCgIBQnZNEibHUAvg5CjRw2z0TA=
Received: by 10.227.55.74 with SMTP id t10mr1903295wbg.91.1309444333824; Thu, 30 Jun 2011 07:32:13 -0700 (PDT)
Received: from stephen-morriss-macbook-pro.local ([217.155.47.50]) by mx.google.com with ESMTPS id et5sm1671158wbb.50.2011.06.30.07.32.11 (version=SSLv3 cipher=OTHER); Thu, 30 Jun 2011 07:32:12 -0700 (PDT)
Message-ID: <4E0C88EA.8050909@googlemail.com>
Date: Thu, 30 Jun 2011 15:32:10 +0100
From: Stephen Morris <sa.morris7@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: dnsop@ietf.org
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local>
In-Reply-To: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 30 Jun 2011 14:32:15 -0000

On 12/06/2011 20:50, George Barwood wrote:
> I have updated the draft
> 
> http://www.ietf.org/id/draft-barwood-dnsop-ds-publish-02.txt
> 
> I have added an appendix with an exampler KSK rollover, and made
> various generally minor changes.
> 
> IANA have now assigned type code 59 for the CDS RRtype.
> 
> I'd like to request that the WG adopt this document.

Before calling for adoption of this draft or any other similar proposal,
I think we should step back a minute and take a look at the context.

There was quite a discussion on the subject of "automatic update of DS
records" in this mailing list during February and March last year (the
thread started by Tony Finch at at
http://www.ietf.org/mail-archive/web/dnsop/current/msg08079.html).
Early on in the discussion, Ed Lewis said:

"My concern - if the IETF produces a solution for transferring DS
records in-band to the DNS protocol we will repeat a mistake made in
pushing EPP to Full Standard. Pushing EPP to Full Standard is in itself
a true accomplishment and there is no controversy, the process was
followed faithfully. The problem is, once it was Full Standard it was
found to not be applicable to the general population that it was
designed to serve. The protocol works and is interoperable; the
requirements didn't grow as the use cases grew."

I agree with Ed and think that we before adopting a solution, we
should step back and ask some basic questions such as:

1. Is there a problem?
2. If so, do we agree on the nature of the problem?
3. If we agree, is the IETF (and in particular, DNSOP) the place to
develop a solution?

Last year's discussion thread covered a number of issues: at the risk of
missing ones and losing some of the nuances of the discussion, the ones
that stood out when I reviewed it were:

* Do we need to automatically update DS records?
Current manual procedures were cited as being error-prone (i.e. people
are less likely to notice a mistake in cutting and pasting a DS record
into a web form than doing the same with an NS record), and there was
the suggestion that DS records are likely to need more frequent updating
than NS records.

* Who is the target audience?
Should the operator/registrant-registrar-registry ecosystem be the
primary or only target audience or should this approach focus on other
parent/child relationships?

* How should we update DS records?
There was some discussion as to whether the update channel should be
from child zone to parent zone, or whether the update should go through
the registrant->registrar->registry path (or variation thereof). With
the latter, EPP was suggested.

* If we automatically update DS records, why not NS records?
Delegations are frequently broken - if we have a mechanism for
automatically updating DS records, can we use the same mechanism to
update NS records as well?

* What sort of security issues will arise?
If you use an in-band (i.e. DNS) solution to transfer information from
the child to the parent, how does it cope if the child zone has been
compromised?

* What sort of out-of-band communication should exist between parent and
child zones?
It was felt that some form of non-DNS communication needs to exist
between the operators of the parent and child zones to handle initial
zone configuration and to resolve emergencies and the like.

* Does this raise any issues with regards to transferring secure domains
between registrars?
The problems associated with these types of transfers have been
discussed to great extent elsewhere, but they may have a bearing on the
solution.

So it seems to me that the first step would be to write a draft that
defines the problem and the requirements for a solution. (The
requirements should include real-world requirements, e.g. how do we
assess the potential bypassing of a registrar in changing registry
data?) Solutions can then be measured against that.

Does this sound a reasonable way for the WG to proceed?

Stephen

From Antoin.Verschuren@sidn.nl  Thu Jun 30 07:40:54 2011
Return-Path: <Antoin.Verschuren@sidn.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 983FA11E807F for <dnsop@ietfa.amsl.com>; Thu, 30 Jun 2011 07:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.504
X-Spam-Level: 
X-Spam-Status: No, score=-4.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V8d629DKecja for <dnsop@ietfa.amsl.com>; Thu, 30 Jun 2011 07:40:52 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [94.198.152.69]) by ietfa.amsl.com (Postfix) with ESMTP id 7791A21F85C1 for <dnsop@ietf.org>; Thu, 30 Jun 2011 07:40:52 -0700 (PDT)
Received: from KAHUBCAS1.SIDN.local ([192.168.2.41]) by ede1-kamx.sidn.nl  with ESMTP id p5UEekN1030425 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=CAFAIL) for <dnsop@ietf.org>; Thu, 30 Jun 2011 16:40:46 +0200
Received: from [192.168.129.125] (192.168.129.125) by KAHUBCAS1.SIDN.local (192.168.2.41) with Microsoft SMTP Server (TLS) id 14.1.289.1; Thu, 30 Jun 2011 16:40:46 +0200
Message-ID: <4E0C8B43.2030409@sidn.nl>
Date: Thu, 30 Jun 2011 16:42:11 +0200
From: Antoin Verschuren <antoin.verschuren@sidn.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: <dnsop@ietf.org>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local> <4E0C88EA.8050909@googlemail.com>
In-Reply-To: <4E0C88EA.8050909@googlemail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [192.168.129.125]
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 30 Jun 2011 14:40:54 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 30-06-11 16:32, Stephen Morris wrote:

> 
> * Does this raise any issues with regards to transferring secure domains
> between registrars?

There isn't any issue transfering secure domains between registrars.
There might only be an issue transfering domains between dns-operators.

- -- 
Antoin Verschuren

Technical Policy Advisor SIDN
Utrechtseweg 310, PO Box 5022, 6802 EA Arnhem, The Netherlands

P: +31 26 3525500  F: +31 26 3525505  M: +31 6 23368970
mailto:antoin.verschuren@sidn.nl  xmpp:antoin@jabber.sidn.nl
http://www.sidn.nl/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJODItDAAoJEDqHrM883AgnnzQH/0XMZoOEhKgxUHwUfAzHaMBL
JaexqlbDobBNzzzvlHBSV1IRN4u3z68J2GJrQM7cxH3RSQqGawKOP8r+qBYLc/7T
ArRSt4uityASjUnMzX3gow61SJ2hcWEjnN6MVcUc3HQvlkX7qoEAwgIVMQv78X4Y
8cvEl8UH+9tSvoOxLbNXvaMczsEWSoJAu6ekvG4hjiPZbVmhPV3cyA2KPbVYufXq
IwO7GyFBFdsmPcnQyQjppxuWlFn+l6PDYvNjW9JjYSBThphi00dcIsaCvcRFQe1Z
ERltzrSOHdgfFKJ9dKAJfOqDEYx1ZwCrh7xI1mzwbPQ3Zn+ye99jIij47/IM7Xc=
=K8VA
-----END PGP SIGNATURE-----

From ogud@ogud.com  Thu Jun 30 09:30:44 2011
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5CD711E8239 for <dnsop@ietfa.amsl.com>; Thu, 30 Jun 2011 09:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.979
X-Spam-Level: 
X-Spam-Status: No, score=-105.979 tagged_above=-999 required=5 tests=[AWL=0.620, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4CkeGRwMT0hX for <dnsop@ietfa.amsl.com>; Thu, 30 Jun 2011 09:30:44 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id AF28B11E823E for <dnsop@ietf.org>; Thu, 30 Jun 2011 09:30:43 -0700 (PDT)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p5UGUfbV077607 for <dnsop@ietf.org>; Thu, 30 Jun 2011 12:30:41 -0400 (EDT) (envelope-from ogud@ogud.com)
Message-ID: <4E0CA4AD.4020703@ogud.com>
Date: Thu, 30 Jun 2011 12:30:37 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: dnsop@ietf.org
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local> <4E0C88EA.8050909@googlemail.com>
In-Reply-To: <4E0C88EA.8050909@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 30 Jun 2011 16:30:44 -0000

On 30/06/2011 10:32 AM, Stephen Morris wrote:
> On 12/06/2011 20:50, George Barwood wrote:
>> I have updated the draft
>>
>> http://www.ietf.org/id/draft-barwood-dnsop-ds-publish-02.txt
.....
> I agree with Ed and think that we before adopting a solution, we
> should step back and ask some basic questions such as:
>
> 1. Is there a problem?

Yes there is a problem

> 2. If so, do we agree on the nature of the problem?

The overall issue is that child knows what KSK's it wants to use,
but the parent publishes what that as DS, getting the information from 
the child to the parent is the problem.

There are multiple possible paths for the information:

EPP: Only works when there is a EPP path from the child to the	parent 
but natural in the RRR (Registry/Registrar/Registrant) world when the 
DNS operator has access to the Registrar.
Note in the RRR world the parent can be either Registry or Registrar.

Dynamic update: only works if parent is willing to GRANT child the right 
to update the DS set.

Web interface: child needs login credentials

Vendor supplied solution: if a distributed organization uses single 
solution DNS vendor that product can perform this work w/o any 
standardization.

Parent scans DNSKEY: does not work for all possible KSK rollovers i.e. 
algorithm removal, and if the parent scans at the wrong time, there 
might be validation error due to timing.

Child sends via email: needs authentication, scaling issues

Child publishes in zone what it wants parent to publish: GB proposal

	
> 3. If we agree, is the IETF (and in particular, DNSOP) the place to
> develop a solution?
>

Not sure there is a "proper" home for this work anywhere right now nor a 
wrong place, dnsop is probably a better place for now as the possible 
output of this process are BCP's as how to do things for each of the 
possible channels.

> Last year's discussion thread covered a number of issues: at the risk of
> missing ones and losing some of the nuances of the discussion, the ones
> that stood out when I reviewed it were:
>
> * Do we need to automatically update DS records?
> Current manual procedures were cited as being error-prone (i.e. people
> are less likely to notice a mistake in cutting and pasting a DS record
> into a web form than doing the same with an NS record), and there was
> the suggestion that DS records are likely to need more frequent updating
> than NS records.

It would be nice, and make the system more robust. FWIW I think NS can 
be automatically maintained after we have DNSSEC by having the parent 
copy what the child publishes.
So maybe we should be having a different discussion:
Does DNSSEC obsolete updating NS and DS information via EPP/Web/Email ?
In the ICANN version of the RRR the path from can quite easily be:
DNS Operator --> Registrant --> Reseller --> Registrar --> Registry
how many of these links are automated ?
does it make sense for all of them to be involved ?

>
> * Who is the target audience?
> Should the operator/registrant-registrar-registry ecosystem be the
> primary or only target audience or should this approach focus on other
> parent/child relationships?
>

I have many burns on my body from using the RRR word incorrectly, and 
many people do not have the full model of roles and responsibilities for 
each role.
my suggestion is to describe the process between parent and child
and then map the process onto the different operating models.

> * How should we update DS records?
> There was some discussion as to whether the update channel should be
> from child zone to parent zone, or whether the update should go through
> the registrant->registrar->registry path (or variation thereof). With
> the latter, EPP was suggested.
>

As I explained above there is NO one solution

> * If we automatically update DS records, why not NS records?
> Delegations are frequently broken - if we have a mechanism for
> automatically updating DS records, can we use the same mechanism to
> update NS records as well?

yes and the discussion should be about consistency of information in 
parent and child with the child as the source.

>
> * What sort of security issues will arise?
> If you use an in-band (i.e. DNS) solution to transfer information from
> the child to the parent, how does it cope if the child zone has been
> compromised?

Is this any worse than if the web account is compromised?
Account is reset, information submitted via account overwrites what is 
in the DNS.
I propose that DNSSEC be the precondition.

>
> * What sort of out-of-band communication should exist between parent and
> child zones?
> It was felt that some form of non-DNS communication needs to exist
> between the operators of the parent and child zones to handle initial
> zone configuration and to resolve emergencies and the like.

No one solution fits all possible.
But in general initial configuration MUST take place outside DNS.

>
> * Does this raise any issues with regards to transferring secure domains
> between registrars?
> The problems associated with these types of transfers have been
> discussed to great extent elsewhere, but they may have a bearing on the
> solution.

Not an issue at all with registrar transfer, if you on the other hand
had said DNS Operators
then in general parent zone must be able to merge two DS sets before the 
transfer and after transfer to switch only the DS for the new operator.

>
> So it seems to me that the first step would be to write a draft that
> defines the problem and the requirements for a solution. (The
> requirements should include real-world requirements, e.g. how do we
> assess the potential bypassing of a registrar in changing registry
> data?) Solutions can then be measured against that.

Do I read this statement you want a requirements that only support the 
RRR model ?

>
> Does this sound a reasonable way for the WG to proceed?
>

Yes,

Olafur

From sa.morris7@googlemail.com  Thu Jun 30 09:56:44 2011
Return-Path: <sa.morris7@googlemail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52F1C11E8092 for <dnsop@ietfa.amsl.com>; Thu, 30 Jun 2011 09:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HUdi4fwgNog5 for <dnsop@ietfa.amsl.com>; Thu, 30 Jun 2011 09:56:43 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 741DD11E807A for <dnsop@ietf.org>; Thu, 30 Jun 2011 09:56:43 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1931302wyj.31 for <dnsop@ietf.org>; Thu, 30 Jun 2011 09:56:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=OOney/pSiZaahyq7LW1ZXVuRdQOlIDkP/PvadOIkJqM=; b=usb0FX5qnPbEHIgEMI5Ek+LzIrZM6y/c5iywGnWfyhL2RaudFIYubg6sNyl350ROoy 79mKyDo7m18/1PfIvijCpjJvsbv23rLE7piGAYw7fLmwzGauVrON6zQPkkNu7eaCHAkL SSL1PvAHxL8Qcu41QNWSTrDbKkFe5pBLxJ6z0=
Received: by 10.227.206.21 with SMTP id fs21mr2080692wbb.40.1309453002525; Thu, 30 Jun 2011 09:56:42 -0700 (PDT)
Received: from stephen-morriss-macbook-pro.local ([217.155.47.50]) by mx.google.com with ESMTPS id b13sm1760587wbh.41.2011.06.30.09.56.41 (version=SSLv3 cipher=OTHER); Thu, 30 Jun 2011 09:56:41 -0700 (PDT)
Message-ID: <4E0CAAC8.8070407@googlemail.com>
Date: Thu, 30 Jun 2011 17:56:40 +0100
From: Stephen Morris <sa.morris7@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local>	<4E0C88EA.8050909@googlemail.com> <4E0CA4AD.4020703@ogud.com>
In-Reply-To: <4E0CA4AD.4020703@ogud.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 30 Jun 2011 16:56:44 -0000

On 30/06/2011 17:30, Olafur Gudmundsson wrote:
>> So it seems to me that the first step would be to write a draft that
>> defines the problem and the requirements for a solution. (The
>> requirements should include real-world requirements, e.g. how do we
>> assess the potential bypassing of a registrar in changing registry
>> data?) Solutions can then be measured against that.
> 
> Do I read this statement you want a requirements that only support the
> RRR model ?

No.  It was only an example and not intended to restrict the scope of
the requirements in any way.

Stephen

From george.barwood@blueyonder.co.uk  Thu Jun 30 15:34:31 2011
Return-Path: <george.barwood@blueyonder.co.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A15811E8258 for <dnsop@ietfa.amsl.com>; Thu, 30 Jun 2011 15:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.846
X-Spam-Level: 
X-Spam-Status: No, score=-0.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id afzsqk4ZQ6hf for <dnsop@ietfa.amsl.com>; Thu, 30 Jun 2011 15:34:30 -0700 (PDT)
Received: from mtaout01-winn.ispmail.ntl.com (mtaout01-winn.ispmail.ntl.com [81.103.221.47]) by ietfa.amsl.com (Postfix) with ESMTP id E236B11E807E for <dnsop@ietf.org>; Thu, 30 Jun 2011 15:34:29 -0700 (PDT)
Received: from know-smtpout-4.server.virginmedia.net ([62.254.123.4]) by mtaout01-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20110630223426.FMWH10265.mtaout01-winn.ispmail.ntl.com@know-smtpout-4.server.virginmedia.net>; Thu, 30 Jun 2011 23:34:26 +0100
Received: from [82.46.65.24] (helo=GeorgeLaptop) by know-smtpout-4.server.virginmedia.net with smtp (Exim 4.63) (envelope-from <george.barwood@blueyonder.co.uk>) id 1QcPoX-000551-Pn; Thu, 30 Jun 2011 23:34:25 +0100
Message-ID: <95A982B76E864EB795A5B322A50EAD32@local>
From: "George Barwood" <george.barwood@blueyonder.co.uk>
To: "Stephen Morris" <sa.morris7@googlemail.com>, <dnsop@ietf.org>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local> <4E0C88EA.8050909@googlemail.com>
Date: Thu, 30 Jun 2011 23:33:57 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Cloudmark-Analysis: v=1.1 cv=R50lirqlHffDPPkwUlkuVa99MrvKdVWo//yz83qex8g= c=1 sm=0 a=NvRijEmkbiIA:10 a=3NElcqgl2aoA:10 a=8nJEP1OIZ-IA:10 a=mK_AVkanAAAA:8 a=48vgC7mUAAAA:8 a=iy3s7R6rU_hPtDWIKRoA:9 a=Kc96OwhYI445KohxvmQA:7 a=wPNLvfGTeEIA:10 a=f7E4GzFmBzwA:10 a=A2SeYfKJtcwA:10 a=MwQNKhUfhccA:10 a=9xyTavCNlvEA:10 a=lZB815dzVvQA:10 a=YqmONFQEAOCt3lpj:21 a=z6NEcZrDdE32_hyV:21 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 30 Jun 2011 22:34:31 -0000

LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJTdGVwaGVuIE1vcnJpcyIgPHNh
Lm1vcnJpczdAZ29vZ2xlbWFpbC5jb20+DQpUbzogPGRuc29wQGlldGYub3JnPg0KU2VudDogVGh1
cnNkYXksIEp1bmUgMzAsIDIwMTEgMzozMiBQTQ0KU3ViamVjdDogUmU6IFtETlNPUF0gQ0RTIFJS
dHlwZSAtIGF1dG9tYXRlZCBLU0sgcm9sbG92ZXINCg0KDQo+IE9uIDEyLzA2LzIwMTEgMjA6NTAs
IEdlb3JnZSBCYXJ3b29kIHdyb3RlOg0KPj4gSSBoYXZlIHVwZGF0ZWQgdGhlIGRyYWZ0DQo+PiAN
Cj4+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtYmFyd29vZC1kbnNvcC1kcy1wdWJsaXNo
LTAyLnR4dA0KPj4gDQo+PiBJIGhhdmUgYWRkZWQgYW4gYXBwZW5kaXggd2l0aCBhbiBleGFtcGxl
ciBLU0sgcm9sbG92ZXIsIGFuZCBtYWRlDQo+PiB2YXJpb3VzIGdlbmVyYWxseSBtaW5vciBjaGFu
Z2VzLg0KPj4gDQo+PiBJQU5BIGhhdmUgbm93IGFzc2lnbmVkIHR5cGUgY29kZSA1OSBmb3IgdGhl
IENEUyBSUnR5cGUuDQo+PiANCj4+IEknZCBsaWtlIHRvIHJlcXVlc3QgdGhhdCB0aGUgV0cgYWRv
cHQgdGhpcyBkb2N1bWVudC4NCj4gDQo+IEJlZm9yZSBjYWxsaW5nIGZvciBhZG9wdGlvbiBvZiB0
aGlzIGRyYWZ0IG9yIGFueSBvdGhlciBzaW1pbGFyIHByb3Bvc2FsLA0KPiBJIHRoaW5rIHdlIHNo
b3VsZCBzdGVwIGJhY2sgYSBtaW51dGUgYW5kIHRha2UgYSBsb29rIGF0IHRoZSBjb250ZXh0Lg0K
PiANCj4gVGhlcmUgd2FzIHF1aXRlIGEgZGlzY3Vzc2lvbiBvbiB0aGUgc3ViamVjdCBvZiAiYXV0
b21hdGljIHVwZGF0ZSBvZiBEUw0KPiByZWNvcmRzIiBpbiB0aGlzIG1haWxpbmcgbGlzdCBkdXJp
bmcgRmVicnVhcnkgYW5kIE1hcmNoIGxhc3QgeWVhciAodGhlDQo+IHRocmVhZCBzdGFydGVkIGJ5
IFRvbnkgRmluY2ggYXQgYXQNCj4gaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2Vi
L2Ruc29wL2N1cnJlbnQvbXNnMDgwNzkuaHRtbCkuDQoNCkknZCBsaWtlIHRvIGFsc28gcmVmZXJl
bmNlIHRoaXMgdGhyZWFkDQoNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9k
bnNvcC9jdXJyZW50L21zZzA4NDI0Lmh0bWwNCg0Kd2hpY2ggcmVmZXJlbmNlcyBhbiBlYXJsaWVy
IHJlcXVpcmVtZW50cyBkb2N1bWVudCBmcm9tIDIwMDQsIHRoYXQgaXMNCg0KaHR0cDovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1kbnNvcC1rZXktcm9sbG92ZXItcmVxdWlyZW1lbnRz
LTAyDQoNCkkgdGhpbmsgdGhhdCByZXF1aXJlbWVudHMgZG9jdW1lbnQgaXMgcmVhc29uYWJseSBj
bGVhciwgYW5kIEkgdGhpbmsgdGhlIGVhcmxpZXIgdGhyZWFkDQppbmRpY2F0ZXMgYSByZWFzb25h
YmxlIGNvbnNlbnN1cyB0byBtb3ZlIGZvcndhcmQgd2l0aCBzYXRpc2Z5aW5nIHRoZSByZXF1aXJl
bWVudHMuDQoNCj4gRWFybHkgb24gaW4gdGhlIGRpc2N1c3Npb24sIEVkIExld2lzIHNhaWQ6DQo+
IA0KPiAiTXkgY29uY2VybiAtIGlmIHRoZSBJRVRGIHByb2R1Y2VzIGEgc29sdXRpb24gZm9yIHRy
YW5zZmVycmluZyBEUw0KPiByZWNvcmRzIGluLWJhbmQgdG8gdGhlIEROUyBwcm90b2NvbCB3ZSB3
aWxsIHJlcGVhdCBhIG1pc3Rha2UgbWFkZSBpbg0KPiBwdXNoaW5nIEVQUCB0byBGdWxsIFN0YW5k
YXJkLiBQdXNoaW5nIEVQUCB0byBGdWxsIFN0YW5kYXJkIGlzIGluIGl0c2VsZg0KPiBhIHRydWUg
YWNjb21wbGlzaG1lbnQgYW5kIHRoZXJlIGlzIG5vIGNvbnRyb3ZlcnN5LCB0aGUgcHJvY2VzcyB3
YXMNCj4gZm9sbG93ZWQgZmFpdGhmdWxseS4gVGhlIHByb2JsZW0gaXMsIG9uY2UgaXQgd2FzIEZ1
bGwgU3RhbmRhcmQgaXQgd2FzDQo+IGZvdW5kIHRvIG5vdCBiZSBhcHBsaWNhYmxlIHRvIHRoZSBn
ZW5lcmFsIHBvcHVsYXRpb24gdGhhdCBpdCB3YXMNCj4gZGVzaWduZWQgdG8gc2VydmUuIFRoZSBw
cm90b2NvbCB3b3JrcyBhbmQgaXMgaW50ZXJvcGVyYWJsZTsgdGhlDQo+IHJlcXVpcmVtZW50cyBk
aWRuJ3QgZ3JvdyBhcyB0aGUgdXNlIGNhc2VzIGdyZXcuIg0KPiANCj4gSSBhZ3JlZSB3aXRoIEVk
IGFuZCB0aGluayB0aGF0IHdlIGJlZm9yZSBhZG9wdGluZyBhIHNvbHV0aW9uLCB3ZQ0KPiBzaG91
bGQgc3RlcCBiYWNrIGFuZCBhc2sgc29tZSBiYXNpYyBxdWVzdGlvbnMgc3VjaCBhczoNCj4gDQo+
IDEuIElzIHRoZXJlIGEgcHJvYmxlbT8NCj4gMi4gSWYgc28sIGRvIHdlIGFncmVlIG9uIHRoZSBu
YXR1cmUgb2YgdGhlIHByb2JsZW0/DQo+IDMuIElmIHdlIGFncmVlLCBpcyB0aGUgSUVURiAoYW5k
IGluIHBhcnRpY3VsYXIsIEROU09QKSB0aGUgcGxhY2UgdG8NCj4gZGV2ZWxvcCBhIHNvbHV0aW9u
Pw0KPiANCj4gTGFzdCB5ZWFyJ3MgZGlzY3Vzc2lvbiB0aHJlYWQgY292ZXJlZCBhIG51bWJlciBv
ZiBpc3N1ZXM6IGF0IHRoZSByaXNrIG9mDQo+IG1pc3Npbmcgb25lcyBhbmQgbG9zaW5nIHNvbWUg
b2YgdGhlIG51YW5jZXMgb2YgdGhlIGRpc2N1c3Npb24sIHRoZSBvbmVzDQo+IHRoYXQgc3Rvb2Qg
b3V0IHdoZW4gSSByZXZpZXdlZCBpdCB3ZXJlOg0KPiANCj4gKiBEbyB3ZSBuZWVkIHRvIGF1dG9t
YXRpY2FsbHkgdXBkYXRlIERTIHJlY29yZHM/DQo+IEN1cnJlbnQgbWFudWFsIHByb2NlZHVyZXMg
d2VyZSBjaXRlZCBhcyBiZWluZyBlcnJvci1wcm9uZSAoaS5lLiBwZW9wbGUNCj4gYXJlIGxlc3Mg
bGlrZWx5IHRvIG5vdGljZSBhIG1pc3Rha2UgaW4gY3V0dGluZyBhbmQgcGFzdGluZyBhIERTIHJl
Y29yZA0KPiBpbnRvIGEgd2ViIGZvcm0gdGhhbiBkb2luZyB0aGUgc2FtZSB3aXRoIGFuIE5TIHJl
Y29yZCksIGFuZCB0aGVyZSB3YXMNCj4gdGhlIHN1Z2dlc3Rpb24gdGhhdCBEUyByZWNvcmRzIGFy
ZSBsaWtlbHkgdG8gbmVlZCBtb3JlIGZyZXF1ZW50IHVwZGF0aW5nDQo+IHRoYW4gTlMgcmVjb3Jk
cy4NCj4gDQo+ICogV2hvIGlzIHRoZSB0YXJnZXQgYXVkaWVuY2U/DQo+IFNob3VsZCB0aGUgb3Bl
cmF0b3IvcmVnaXN0cmFudC1yZWdpc3RyYXItcmVnaXN0cnkgZWNvc3lzdGVtIGJlIHRoZQ0KPiBw
cmltYXJ5IG9yIG9ubHkgdGFyZ2V0IGF1ZGllbmNlIG9yIHNob3VsZCB0aGlzIGFwcHJvYWNoIGZv
Y3VzIG9uIG90aGVyDQo+IHBhcmVudC9jaGlsZCByZWxhdGlvbnNoaXBzPw0KDQpJIGJlbGlldmUg
aXQncyBiZXN0IHRvIGxlYXZlIG91dCBkaXNjdXNzaW9uIG9mIHJlZ2lzdHJhcnMgZXRjLCBiZWNh
dXNlIEkgdGhpbmsgdGhlIHByb2JsZW0NCmNhbiBiZSBwcm9wZXJseSBzb2x2ZWQgYW5kIHN0YW5k
YXJkaXNlZCBpbiBhIGdlbmVyYWxpc2VkIHBhcmVudC9jaGlsZCBtb2RlbC4NCj4gDQo+ICogSG93
IHNob3VsZCB3ZSB1cGRhdGUgRFMgcmVjb3Jkcz8NCj4gVGhlcmUgd2FzIHNvbWUgZGlzY3Vzc2lv
biBhcyB0byB3aGV0aGVyIHRoZSB1cGRhdGUgY2hhbm5lbCBzaG91bGQgYmUNCj4gZnJvbSBjaGls
ZCB6b25lIHRvIHBhcmVudCB6b25lLCBvciB3aGV0aGVyIHRoZSB1cGRhdGUgc2hvdWxkIGdvIHRo
cm91Z2gNCj4gdGhlIHJlZ2lzdHJhbnQtPnJlZ2lzdHJhci0+cmVnaXN0cnkgcGF0aCAob3IgdmFy
aWF0aW9uIHRoZXJlb2YpLiBXaXRoDQo+IHRoZSBsYXR0ZXIsIEVQUCB3YXMgc3VnZ2VzdGVkLg0K
PiANCj4gKiBJZiB3ZSBhdXRvbWF0aWNhbGx5IHVwZGF0ZSBEUyByZWNvcmRzLCB3aHkgbm90IE5T
IHJlY29yZHM/DQo+IERlbGVnYXRpb25zIGFyZSBmcmVxdWVudGx5IGJyb2tlbiAtIGlmIHdlIGhh
dmUgYSBtZWNoYW5pc20gZm9yDQo+IGF1dG9tYXRpY2FsbHkgdXBkYXRpbmcgRFMgcmVjb3Jkcywg
Y2FuIHdlIHVzZSB0aGUgc2FtZSBtZWNoYW5pc20gdG8NCj4gdXBkYXRlIE5TIHJlY29yZHMgYXMg
d2VsbD8NCj4gDQo+ICogV2hhdCBzb3J0IG9mIHNlY3VyaXR5IGlzc3VlcyB3aWxsIGFyaXNlPw0K
PiBJZiB5b3UgdXNlIGFuIGluLWJhbmQgKGkuZS4gRE5TKSBzb2x1dGlvbiB0byB0cmFuc2ZlciBp
bmZvcm1hdGlvbiBmcm9tDQo+IHRoZSBjaGlsZCB0byB0aGUgcGFyZW50LCBob3cgZG9lcyBpdCBj
b3BlIGlmIHRoZSBjaGlsZCB6b25lIGhhcyBiZWVuDQo+IGNvbXByb21pc2VkPw0KDQpXZWxsIGlm
IHRoZSBjaGlsZCB6b25lICggdGhlIHNlY3JldCBrZXlzLCBJIGFzc3VtZSB5b3UgbWVhbikgYXJl
IGNvbXByb21pc2VkIHRoZW4gYWxsDQpzZWN1cml0eSBpcyBsb3N0IGluIGFueSBjYXNlLCBhbmQg
SSdtIG5vdCBzdXJlIG11Y2ggbW9yZSBjYW4gYmUgc2FpZC4NCk1heWJlIEknbSBtaXNzaW5nIHNv
bWUgc3VidGxldHkgaGVyZS4NCiANCj4gKiBXaGF0IHNvcnQgb2Ygb3V0LW9mLWJhbmQgY29tbXVu
aWNhdGlvbiBzaG91bGQgZXhpc3QgYmV0d2VlbiBwYXJlbnQgYW5kDQo+IGNoaWxkIHpvbmVzPw0K
PiBJdCB3YXMgZmVsdCB0aGF0IHNvbWUgZm9ybSBvZiBub24tRE5TIGNvbW11bmljYXRpb24gbmVl
ZHMgdG8gZXhpc3QNCj4gYmV0d2VlbiB0aGUgb3BlcmF0b3JzIG9mIHRoZSBwYXJlbnQgYW5kIGNo
aWxkIHpvbmVzIHRvIGhhbmRsZSBpbml0aWFsDQo+IHpvbmUgY29uZmlndXJhdGlvbiBhbmQgdG8g
cmVzb2x2ZSBlbWVyZ2VuY2llcyBhbmQgdGhlIGxpa2UuDQoNClRoYXQncyB0cnVlLiBJbiBnZW5l
cmFsIGl0J3MgbmVjZXNzYXJ5IHRvIGhhdmUgYW4gb3V0LW9mLWJhbmQgYm9vdHN0cmFwDQptZWNo
YW5pc20gZm9yIGluaXRpYWwgY29uZmlndXJhdGlvbiBhbmQgZm9yIHJlc2V0IGlmIHRoZSBjaGls
ZCBwcml2YXRlIGtleXMgYXJlIGxvc3QuDQpUaGF0IHNhaWQsIGl0IG1heSBiZSBwb3NzaWJsZSB0
byBoYXZlICJpbnNlY3VyZS9vcHBvcnR1bmlzdGljIiBhdXRvLWNvbmZpZ3VyYXRpb24gDQppbiBz
aXR1YXRpb25zIHdoZXJlIHRoZSBjaGlsZCBoYXMgcmVzcG9uc2liaWxpdHkgdG8gdmVyaWZ5IHRo
ZSBwYXJlbnQgZGF0YS4NCkkgbGVhdmUgdGhhdCBvcGVuIGluIHRoZSBkcmFmdCBieSBzYXlpbmcg
aXQgaXMgcGFyZW50IHBvbGljeSA6DQoNCiAgSWYgdGhlIHJlc3VsdCBpcyBpbnNlY3VyZSwgZXh0
cmEgY2hlY2tzIE1BWSBiZSBwZXJmb3JtZWQNCiAgYWNjb3JkaW5nIHRvIHRoZSBwYXJlbnQgem9u
ZSBwb2xpY3kuDQoNCj4gKiBEb2VzIHRoaXMgcmFpc2UgYW55IGlzc3VlcyB3aXRoIHJlZ2FyZHMg
dG8gdHJhbnNmZXJyaW5nIHNlY3VyZSBkb21haW5zDQo+IGJldHdlZW4gcmVnaXN0cmFycz8NCj4g
VGhlIHByb2JsZW1zIGFzc29jaWF0ZWQgd2l0aCB0aGVzZSB0eXBlcyBvZiB0cmFuc2ZlcnMgaGF2
ZSBiZWVuDQo+IGRpc2N1c3NlZCB0byBncmVhdCBleHRlbnQgZWxzZXdoZXJlLCBidXQgdGhleSBt
YXkgaGF2ZSBhIGJlYXJpbmcgb24gdGhlDQo+IHNvbHV0aW9uLg0KDQpJIHRoaW5rIHRoYXQgaXMg
YSBkaXN0aW5jdCBpc3N1ZSwgYWx0aG91Z2ggYSBnZW5lcmFsIGluLWJhbmQgbWVjaGFuaXNtIHRv
IHVwZGF0ZQ0KdGhlIHBhcmVudCBEUyBSUnNldCBtYXkgd2VsbCBiZSB1c2VmdWwgaW4gdGhhdCBz
aXR1YXRpb24uIEluIHRoZSBkcmFmdCBJIGZvY3VzDQptYWlubHkgb24ga2V5IHJvbGxvdmVyLCBi
dXQgYWxnb3JpdGhtIHJvbGxvdmVyIGlzIG9mIGNvdXJzZSBhbHNvIGNvdmVyZWQsIGFuZA0KYW55
IG90aGVyIHNpdHVhdGlvbnMgdGhhdCByZXF1aXJlIGNoYW5nZXMgdG8gdGhlIHBhcmVudCBEUyBS
UnNldC4NCiANCj4gU28gaXQgc2VlbXMgdG8gbWUgdGhhdCB0aGUgZmlyc3Qgc3RlcCB3b3VsZCBi
ZSB0byB3cml0ZSBhIGRyYWZ0IHRoYXQNCj4gZGVmaW5lcyB0aGUgcHJvYmxlbSBhbmQgdGhlIHJl
cXVpcmVtZW50cyBmb3IgYSBzb2x1dGlvbi4gKFRoZQ0KPiByZXF1aXJlbWVudHMgc2hvdWxkIGlu
Y2x1ZGUgcmVhbC13b3JsZCByZXF1aXJlbWVudHMsIGUuZy4gaG93IGRvIHdlDQo+IGFzc2VzcyB0
aGUgcG90ZW50aWFsIGJ5cGFzc2luZyBvZiBhIHJlZ2lzdHJhciBpbiBjaGFuZ2luZyByZWdpc3Ry
eQ0KPiBkYXRhPykgU29sdXRpb25zIGNhbiB0aGVuIGJlIG1lYXN1cmVkIGFnYWluc3QgdGhhdC4N
Cg0KPiBEb2VzIHRoaXMgc291bmQgYSByZWFzb25hYmxlIHdheSBmb3IgdGhlIFdHIHRvIHByb2Nl
ZWQ/DQoNCklzIHRoZSBlYXJsaWVyIHJlcXVpcmVtZW50cyBkcmFmdCBmcm9tIDIwMDUgKGxpbmtl
ZCBhYm92ZSkgc3Vic3RhbnRpYWxseSBpbmNvbXBsZXRlIGluIHNvbWUgd2F5Pw0KSSB0aGluayB0
aGF0IHdvdWxkIGJlIGEgcmVhc29uYWJsZSBiYXNpcyB0byBtZWFzdXJlLCBJIHdvdWxkIGNsYWlt
IHRoYXQgdGhlIENEUw0KcmVjb3JkIGlzIGNhcGFibGUgb2Ygc2F0aXNmeWluZyB0aGUgcmVxdWly
ZW1lbnRzIGV4cHJlc3NlZCB0aGVyZSBpbiBhIG5hdHVyYWwgd2F5LiANCkkgYWxzbyB0aGluayB0
aGUgcmVxdWlyZW1lbnQgaXMgYWN0dWFsbHkgZmFpcmx5IGNsZWFyIC0gd2hlbiBpbXBsZW1lbnRp
bmcgS1NLIHJvbGxvdmVyLA0KeW91IHJlYWNoIGEgcG9pbnQgd2hlcmUgaXQncyBjbGVhciB0aGF0
IHNvbWV0aGluZyBpcyBuZWVkZWQgKCBvdGhlciB0aGFuIGFza2luZw0KdGhlIG9wZXJhdG9yIHRv
IHN0YXJ0IGN1dHRpbmcgYW5kIHBhc3RpbmcgLyBpbnRlcmZhY2luZyB3aXRoIHNvbWUgb3V0LW9m
LWJhbmQgc3lzdGVtIC8gd2hhdGV2ZXIpLg0KSSBkb3VidCBhbm90aGVyIGN5Y2xlIG9mIHJlcXVp
cmVtZW50cyB3b3VsZCBiZSBwcm9kdWN0aXZlIC0gd2UgbWlnaHQgYmUgaGVyZSBhZ2FpbiBpbiA2
IHllYXJzIHRpbWUhDQoNCktpbmQgcmVnYXJkcywNCkdlb3JnZQ0KIA0KPiBTdGVwaGVuDQo+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IEROU09QIG1h
aWxpbmcgbGlzdA0KPiBETlNPUEBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2Ruc29w

