[dnsext] TALINK RRTYPE review. Start of three week comment period
roy@nominet.org.uk Wed, 22 July 2009 12:53 UTC
Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 250B13A685E; Wed, 22 Jul 2009 05:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level:
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_UK=1.749, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
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 2YtpATsTWsa4; Wed, 22 Jul 2009 05:53:56 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id F37AC3A6821; Wed, 22 Jul 2009 05:53:28 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1MTbDN-000FMV-I8 for namedroppers-data0@psg.com; Wed, 22 Jul 2009 12:46:33 +0000
Received: from [213.248.199.24] (helo=mx4.nominet.org.uk) by psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from <roy@nominet.org.uk>) id 1MTbDH-000FLx-V8 for namedroppers@ops.ietf.org; Wed, 22 Jul 2009 12:46:31 +0000
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Subject:To:X-Mailer:Message-ID: From:Date:X-MIMETrack:MIME-Version:Content-type; b=wHZjdyu3fdgcFN320D+WIUzFmdbEwMjTNqgFTrJYUPCIEN7bWRxNYipH 0t/fF3p7fhYzvxBOgXaGf/sp+L+w29JDqKdMzgRDncZKKgPBUZQyMdUWy YCZ1/lxOpMh0rE7;
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=1248266788; x=1279802788; 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@nominet.org.uk|Subject:=20TALINK=20RRTYPE=20 review.=20Start=20of=20three=20week=20comment=20period |Date:=20Wed,=2022=20Jul=202009=2014:46:21=20+0200 |Message-ID:=20<OF1621B157.6C4A78F9-ON802575FB.0043EF31-C 12575FB.004628F6@nominet.org.uk>|To:=20namedroppers@ops.i etf.org|MIME-Version:=201.0; bh=PPjkwr3rJphRNqmimDR125sxhK9Xe8M/AdECT6cb5sU=; b=pDZB6ycm1+ISLPtvK0NHZMqOVhgP2Tpifq/1ry9KW49S4ylx/E1v23oA RkECRxUycT9ccYpHm9Yp+MWlnxGDRC4mlumj+LzyylVQPkeog6k/wjjO6 vYOnUaPsB2L3rC/;
X-IronPort-AV: E=Sophos;i="4.43,247,1246834800"; d="scan'208";a="11645914"
Received: from notes1.nominet.org.uk ([213.248.197.128]) by mx4.nominet.org.uk with ESMTP; 22 Jul 2009 13:46:23 +0100
Subject: [dnsext] TALINK RRTYPE review. Start of three week comment period
To: namedroppers@ops.ietf.org
X-Mailer: Lotus Notes Build V85_M2_08202008 August 20, 2008
Message-ID: <OF1621B157.6C4A78F9-ON802575FB.0043EF31-C12575FB.004628F6@nominet.org.uk>
From: roy@nominet.org.uk
Date: Wed, 22 Jul 2009 14:46:21 +0200
X-MIMETrack: Serialize by Router on notes1/Nominet(Release 7.0.1FP1 | May 25, 2006) at 22/07/2009 01:46:24 PM
MIME-Version: 1.0
Content-type: text/plain; charset="US-ASCII"
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
Dear colleagues, I have been assigned with the task of coordinating an expert-review of the DNS RRTYPE parameter allocation for TALINK, present in http://tools.ietf.org/html/draft-wijngaards-dnsop-trust-history-00 . Attached is a completed template requesting an RRTYPE assignment under the procedures of draft-ietf-dnsext-2929bis. This request will be evaluated by expert review. This mail initiates a three week comment period on the RRTYPE request. If you have comments on the request, please post them to this list. Kind regards, Roy Arends --- Template from http://tools.ietf.org/html/rfc5395 DNS RRTYPE PARAMETER ALLOCATION TEMPLATE A. Submission Date: 30, June 2009 B. Submission Type: [X] New RRTYPE [ ] Modification to existing RRTYPE C. Contact Information for submitter: Name: Wouter Wijngaards Email Address: wouter@nlnetlabs.nl International telephone number: +31 20 888 4551 Other contact handles: - (Note: This information will be publicly posted.) D. Motivation for the new RRTYPE application? Please keep this part at a high level to inform the Expert and reviewers about uses of the RRTYPE. Remember most reviewers will be DNS experts that may have limited knowledge of your application space. A double linked list of names that contain specific DNSKEY data at those names. The type is to be used by applications that maintain trust anchors for DNS validators. The DNSKEY data is used to rollover trust anchors to the current key. Therefore they must know the start and end of the list, and be able to move forwards and backwards through the list. E. Description of the proposed RR type. This description can be provided in-line in the template, as an attachment, or with a publicly available URL: The RR is a data type, can be handled as an RFC3597 unknown record. No additional section processing. The rdata is two domain names, presentation format is the two domain names, wireformat the two domain names in uncompressed form. The type is used to link domain names. TALINK _start_ _end_ for the list head and TALINK _prev_ _next_ for linking the elements. To end the list, the root label '.' is used to denote the endpoints. Thus, the root can be the list head, but not a list element. This is fine, saves space and is less complex than other solutions for flagging list endpoints or an empty list. F. What existing RRTYPE or RRTYPEs come closest to filling that need and why are they unsatisfactory? RP has two domain names but it means 'Responsible Person'. MINFO has two domain names but means 'Machine Information'. These types are compressed, which is nice. The PTR type is the right concept, but has only one domain name in its rdata, and I need two. If I use two PTRs then the validator cannot distinguish the previous and next pointer, because the ordering of RRs in an RRset is not fixed. Another alternative is using PTR records at _start, _end, _prev and _next prefixes for disambiguation. Prefixes limit the domains that can be used because of the max domain name length. This is the alternative I would consider if this application is denied. G. What mnemonic is requested for the new RRTYPE (optional)? Note: This can be left blank and the mnemonic decided after the template is accepted. TALINK (Trust Anchor LINK). 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? If so, please indicate which registry is to be used or created. If a new sub-registry is needed, specify the allocation policy for it and its initial contents. Also include what the modification procedures will be. No. 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 changes. J. Comments: - -- to unsubscribe send a message to namedroppers-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://ops.ietf.org/lists/namedroppers/>
- [dnsext] TALINK RRTYPE review. Start of three wee… roy
- Re: [dnsext] TALINK RRTYPE review. Start of three… Edward Lewis
- Re: [dnsext] TALINK RRTYPE review. Start of three… W.C.A. Wijngaards
- Re: [dnsext] TALINK RRTYPE review. Start of three… Mark Andrews
- Re: [dnsext] TALINK RRTYPE review. Start of three… Jeffrey A. Williams
- Re: [dnsext] TALINK RRTYPE review. Start of three… Mark Andrews
- Fwd: [dnsext] TALINK RRTYPE review. Start of thre… bert hubert
- Re: Fwd: [dnsext] TALINK RRTYPE review. Start of … Alex Bligh
- Re: [dnsext] TALINK RRTYPE review. Start of three… W.C.A. Wijngaards
- Re: Fwd: [dnsext] TALINK RRTYPE review. Start of … W.C.A. Wijngaards
- Re: Fwd: [dnsext] TALINK RRTYPE review. Start of … bert hubert
- Re: Fwd: [dnsext] TALINK RRTYPE review. Start of … Olafur Gudmundsson
- Re: [dnsext] TALINK RRTYPE review. Start of three… Andrew Sullivan