Re: [DNSOP] DLVs and ITAR
Mark Andrews <marka@isc.org> Fri, 11 September 2009 23:00 UTC
Return-Path: <marka@isc.org>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAAA03A681E for <dnsop@core3.amsl.com>; Fri, 11 Sep 2009 16:00:52 -0700 (PDT)
X-Quarantine-ID: <92c4bZY+aiTE>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Cc"
X-Spam-Flag: NO
X-Spam-Score: -2.419
X-Spam-Level:
X-Spam-Status: No, score=-2.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 92c4bZY+aiTE for <dnsop@core3.amsl.com>; Fri, 11 Sep 2009 16:00:51 -0700 (PDT)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id 82E643A6804 for <dnsop@ietf.org>; Fri, 11 Sep 2009 16:00:51 -0700 (PDT)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id B29A0E6023; Fri, 11 Sep 2009 23:01:27 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id n8BN1MOB009397; Sat, 12 Sep 2009 09:01:24 +1000 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200909112301.n8BN1MOB009397@drugs.dv.isc.org>
To: Jim Reid <jim@rfc1035.com>
From: Mark Andrews <marka@isc.org>
References: <alpine.LFD.1.10.0909081307090.9233@newtla.xelerance.com> <68F05A6E-256D-4C61-B03D-82E9E949349F@virtualized.org> <a06240800c6cc563a4381@[10.31.200.192]> <4AE266E3-E9ED-48D4-BEEE-41FB5A547392@virtualized.org> <a06240801c6cc67e5678b@[10.31.200.192]> <F6A9960F-44A8-4B97-A353-10B3578BA08E@virtualized.org> <a0624080ac6ceff5a54fd@[10.31.200.192]> <A4DC1D4D-3CC5-4BB7-A724-72BEBD0EA321@virtualized.org> <alpine.LFD.1.10.0909101705260.28494@newtla.xelerance.com> <58B0810F-29BD-4897-8E5A-46030F3417BD@rfc1035.com> <20090911094858.GA19094@nic.fr> <196D62EA-0561-431A-879D-21F8AE4520AB@rfc1035.com> <alpine.LFD.1.10.0909110923200.28830@newtla.xelerance.com> <68AE4775-CE61-47F1-9267-B08E60587741@rfc1035.com>
In-reply-to: Your message of "Fri, 11 Sep 2009 18:20:20 +0100." <68AE4775-CE61-47F1-9267-B08E60587741@rfc1035.com>
Date: Sat, 12 Sep 2009 09:01:22 +1000
Sender: marka@isc.org
Cc: IETF DNSOP WG <dnsop@ietf.org>, iana@iana.org
Subject: Re: [DNSOP] DLVs and ITAR
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 11 Sep 2009 23:00:52 -0000
I see no need for any TLD to check that ISC has picked up records from the ITAR for the DLV registry. What I do see is a need to formalise the timing parameters involved an ensure that all parties involved are aware of them. That way if a party is too slow or if a party is too fast we know who to blame. At the moment there is wishy washy language which doesn't help anyone do the right thing IANA still has not provided timing guidance. IANA can you please specifiy a maximum polling interval on this page and inform the TLD's using ITAR of what it is. A minimum polling interval would also be useful but is not crucial. https://itar.iana.org/instructions/ As a reminder, the trust anchor repository is temporary. It will be decommissioned once the root zone is signed. Any software configured to use it should be configured to continue to work when this event happens. You should also ensure you have procedures in place to keep the trust anchors up to date as the ITAR will regularly add and remove keys. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
- [DNSOP] .PR servfails due to wrong key in DLV Paul Wouters
- [DNSOP] Key Management and Provisioningl was Re: … Edward Lewis
- Re: [DNSOP] Key Management and Provisioningl was … Paul Wouters
- Re: [DNSOP] Key Management and Provisioningl was … Edward Lewis
- Re: [DNSOP] Key Management and Provisioningl was … bmanning
- Re: [DNSOP] Key Management and Provisioningl was … David Conrad
- Re: [DNSOP] Key Management and Provisioningl was … Edward Lewis
- Re: [DNSOP] Key Management and Provisioningl was … Paul Wouters
- Re: [DNSOP] Key Management and Provisioningl was … David Conrad
- Re: [DNSOP] Key Management and Provisioningl was … Edward Lewis
- [DNSOP] provisioning and OT&E for the signed root Jim Reid
- Re: [DNSOP] provisioning and OT&E for the signed … Edward Lewis
- Re: [DNSOP] Key Management and Provisioningl was … David Conrad
- Re: [DNSOP] Key Management and Provisioningl was … Edward Lewis
- Re: [DNSOP] Key Management and Provisioningl was … David Conrad
- Re: [DNSOP] Key Management and Provisioningl was … Paul Wouters
- [DNSOP] DLVs and ITAR Jim Reid
- Re: [DNSOP] DLVs and ITAR Stephane Bortzmeyer
- Re: [DNSOP] DLVs and ITAR Jim Reid
- Re: [DNSOP] DLVs and ITAR Paul Wouters
- Re: [DNSOP] DLVs and ITAR Jim Reid
- Re: [DNSOP] DLVs and ITAR Mark Andrews
- Re: [DNSOP] DLVs and ITAR Kim Davies
- Re: [DNSOP] DLVs and ITAR Kim Davies
- Re: [DNSOP] DLVs and ITAR Mark Andrews
- Re: [DNSOP] DLVs and ITAR Mark Andrews
- Re: [DNSOP] DLVs and ITAR Kim Davies
- Re: [DNSOP] DLVs and ITAR joao damas
- Re: [DNSOP] DLVs and ITAR Kim Davies
- Re: [DNSOP] DLVs and ITAR David Blacka
- Re: [DNSOP] DLVs and ITAR Thierry Moreau
- Re: [DNSOP] DLVs and ITAR Edward Lewis
- Re: [DNSOP] DLVs and ITAR Mark Andrews
- Re: [DNSOP] DLVs and ITAR Holger Zuleger
- Re: [DNSOP] DLVs and ITAR Mark Andrews
- Re: [DNSOP] DLVs and ITAR Mark Andrews
- Re: [DNSOP] Key Management and Provisioningl was … Roy Arends
- Re: [DNSOP] Key Management and Provisioningl was … joao damas
- Re: [DNSOP] Key Management and Provisioningl was … Roy Arends
- Re: [DNSOP] Key Management and Provisioningl was … joao damas
- Re: [DNSOP] Key Management and Provisioningl was … Roy Arends
- Re: [DNSOP] Key Management and Provisioningl was … joao damas
- Re: [DNSOP] Key Management and Provisioningl was … Joe Abley
- Re: [DNSOP] Key Management and Provisioningl was … Florian Weimer
- Re: [DNSOP] Key Management and Provisioningl was … Roy Arends
- Re: [DNSOP] Key Management and Provisioningl was … Florian Weimer
- Re: [DNSOP] Key Management and Provisioningl was … Mark Andrews
- Re: [DNSOP] Key Management and Provisioningl was … Stephane Bortzmeyer
- Re: [DNSOP] Key Management and Provisioningl was … David Conrad
- Re: [DNSOP] Key Management and Provisioningl was … Mark Andrews
- Re: [DNSOP] Key Management and Provisioningl was … Stephane Bortzmeyer
- Re: [DNSOP] Key Management and Provisioningl was … David Conrad
- Re: [DNSOP] Key Management and Provisioningl was … Mark Andrews
- Re: [DNSOP] Key Management and Provisioningl was … Roy Arends
- Re: [DNSOP] Key Management and Provisioningl was … Mark Andrews
- Re: [DNSOP] Key Management and Provisioningl was … Edward Lewis
- Re: [DNSOP] Key Management and Provisioningl was … Mark Andrews
- Re: [DNSOP] Key Management and Provisioningl was … Mark Andrews
- Re: [DNSOP] Key Management and Provisioningl was … Mark Andrews
- Re: [DNSOP] Key Management and Provisioningl was … Chris Thompson
- Re: [DNSOP] Key Management and Provisioningl was … Kim Davies
- Re: [DNSOP] Key Management and Provisioningl was … Mark Andrews
- Re: [DNSOP] Key Management and Provisioningl was … Kim Davies
- Re: [DNSOP] Key Management and Provisioningl was … Mark Andrews
- Re: [DNSOP] Key Management and Provisioningl was … Michael Graff
- Re: [DNSOP] Key Management and Provisioningl was … Chris Thompson
- Re: [DNSOP] Key Management and Provisioningl was … Michael Graff
- Re: [DNSOP] Key Management and Provisioningl was … Chris Thompson
- Re: [DNSOP] Key Management and Provisioningl was … Edward Lewis
- Re: [DNSOP] Key Management and Provisioningl was … Mark Andrews
- Re: [DNSOP] .PR servfails due to wrong key in DLV David Conrad
- Re: [DNSOP] .PR servfails due to wrong key in DLV Stephane Bortzmeyer
- Re: [DNSOP] .PR servfails due to wrong key in DLV Mark Andrews