IETF Logo Mail Archive

[dnsext] CDS RRTYPE review - Comments period end Mar 29th

Roy Arends <roy@nominet.org.uk> Tue, 08 March 2011 19:32 UTC

Return-Path: <roy@nominet.org.uk>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 22A093A692C for <dnsext@core3.amsl.com>; Tue, 8 Mar 2011 11:32:14 -0800 (PST)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ij5bCDbN5zRS for <dnsext@core3.amsl.com>; Tue, 8 Mar 2011 11:32:13 -0800 (PST)
Received: from mx1.knowthenet.org.uk (mx1.knowthenet.org.uk [213.248.199.2]) by core3.amsl.com (Postfix) with ESMTP id 793FC3A67F2 for <dnsext@ietf.org>; Tue, 8 Mar 2011 11:32:11 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:Subject: Thread-Topic:Thread-Index:Date:Message-ID:In-Reply-To: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:Content-Type:Content-ID: Content-Transfer-Encoding:MIME-Version; b=xHMHFfIylT1c2/LV7BHu3J96m8Zjulgm86HsilWLdCbKFV7vQW07bvdj 15q50IErI9yH6mb9YfkM5/6WT3qUROSrsgkgvj+qTfHFEq+8PMJd1+pwp /FuCkBGR48Sk+ij;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=roy@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1299612808; x=1331148808; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Roy=20Arends=20<roy@nominet.org.uk>|Subject:=20C DS=20RRTYPE=20review=20-=20Comments=20period=20end=20Mar =2029th|Date:=20Tue,=208=20Mar=202011=2019:33:22=20+0000 |Message-ID:=20<C99C3502.72B1%roy@nominet.org.uk>|To:=20" dnsext@ietf.org"=20<dnsext@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<2c2ea216-8403-4a6b-ac5d-907d281eb5a5> |In-Reply-To:=20<20101115231159.GA697@shinkuro.com>; bh=a01EQq0TXxUJFN0mtXsekFXNEns6ts1iguRbznnfz8g=; b=j/42GQxRpe+JWE6919hVbx+8J7ol+VlJXXd2cLnb+zPUPzj2f7hIJK2D bhKKOMO7myjM0RUGEesRMCLT+Nx3PiUiaQF6d6mbzzc/GxZz42sW6/76O 3HBeyUZYRPBhZkL;
X-IronPort-AV: E=Sophos;i="4.62,285,1297036800"; d="scan'208";a="31416164"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx3.nominet.org.uk with ESMTP; 08 Mar 2011 19:33:25 +0000
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%19]) with mapi; Tue, 8 Mar 2011 19:33:24 +0000
From: Roy Arends <roy@nominet.org.uk>
To: "dnsext@ietf.org" <dnsext@ietf.org>
Thread-Topic: CDS RRTYPE review - Comments period end Mar 29th
Thread-Index: AQHL3cewrDa2/M5NO0iO/nIAjhSWZw==
Date: Tue, 08 Mar 2011 19:33:22 +0000
Message-ID: <C99C3502.72B1%roy@nominet.org.uk>
In-Reply-To: <20101115231159.GA697@shinkuro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2c2ea216-8403-4a6b-ac5d-907d281eb5a5>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dnsext] CDS RRTYPE review - Comments period end Mar 29th
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 19:32:14 -0000

Dear Colleagues,

Below is a resubmission of a completed template requesting a new
RRTYPE assignment under the procedures of RFC5395.

This message starts a 3 weeks period for an expert-review of the DNS
RRTYPE parameter allocation for URI specified in
http://tools.ietf.org/id/draft-barwood-dnsop-ds-publish-01.txt

If you have any new comments regarding this request that have not yet
being made, please post them here before Mar 29th 18:00 UTC.

Kind Regards,
Roy Arends

--begin 5395 template URI--

   A.    Submission Date: 15 November 2010

   B.    Submission Type:
         [X] New RRTYPE
         [ ] Modification to existing RRTYPE

   C.    Contact Information for submitter:
            Name: George Barwood
            Email Address: george.barwood@blueyonder.co.uk
            International telephone number: +44 1452 722670
            Other contact handles: N/A

   D.    Motivation for the new RRTYPE application?

         To allow a copy of the DS RRset [RFC4034] to be published
         in the child zone, which is used to update the parent DS RRset.
         It is expected that this will allow the rollover of a key signing
         key to be automated.

   E.    Description of the proposed RR type.

         The format is identical to the DS record.
         However there is no special processing for servers/resolvers.

   F.    What existing RRTYPE or RRTYPEs come closest to filling that
         need and why are they unsatisfactory?

         None.

   G.    What mnemonic is requested for the new RRTYPE (optional)?

         CDS to stand for "Child DS".

   H.    Does the requested RRTYPE make use of any existing IANA
         Registry or require the creation of a new IANA sub-registry in
         DNS Parameters?

         It uses the same registries as the DS record.

   I.    Does the proposal require/expect any changes in DNS
         servers/resolvers that prevent the new type from being
         processed as an unknown RRTYPE (see [RFC3597])?

         No.

   J.    Comments:
         An RFC describing in detail how the CDS RRset may be used
         to update the parent DS RRset is anticipated. The current draft
         is draft-barwood-dnsop-ds-publish-01.

--end 5395 template URI--

v2.23.0 | Report a Bug | By Email