IETF Logo Mail Archive

Re: [DNSOP] New Version Notification for draft-gersch-dnsop-revdns-cidr-00.txt

Ray Bellis <Ray.Bellis@nominet.org.uk> Fri, 30 March 2012 10:19 UTC

Return-Path: <Ray.Bellis@nominet.org.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 A6E3A21F894B for <dnsop@ietfa.amsl.com>; Fri, 30 Mar 2012 03:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.25
X-Spam-Level:
X-Spam-Status: No, score=-10.25 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d+-aEM6PZPtS for <dnsop@ietfa.amsl.com>; Fri, 30 Mar 2012 03:19:46 -0700 (PDT)
Received: from mx4.nominet.org.uk (mx4.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 6762021F891A for <dnsop@ietf.org>; Fri, 30 Mar 2012 03:19:46 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: 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=kY5Szk2TOQFN3dRJ8HfdZAjFtSLiPWcD5WIHaL0NN9qpYW02ns+RSWuI HYx9M2oHaKVKgLiAC7nc/cIuVUcg1d67RTwMZV3MVkoQMGNVdUjbNDDLa H2LtbhD7Y5JQUnU;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1333102786; x=1364638786; 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:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[DNSOP]=20New=20Version=20Notification =20for=0D=0A=09draft-gersch-dnsop-revdns-cidr-00.txt |Date:=20Fri,=2030=20Mar=202012=2010:19:43=20+0000 |Message-ID:=20<2C012FE1-A40D-473F-89D8-52673182A581@nomi net.org.uk>|To:=20=3D?utf-8?B?T25kxZllaiBTdXLDvQ=3D=3D? =3D=20<ondrej.sury@nic.cz>|CC:=20"dnsop@ietf.org"=20<dnso p@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20base64|Content-ID:=20<b7237 213-0a12-41a3-81bc-33e7ab8a1afe>|In-Reply-To:=20<E2FDD0E1 -9C08-43C4-967E-1AE9102D817E@nic.cz>|References:=20<20120 217000918.22307.43753.idtracker@ietfa.amsl.com>=0D=0A=20< 2D04DB88-9570-4DE3-A796-F4F07AF5EF74@secure64.com>=0D=0A =20<017101ccefd5$51790560$f46b1020$@lampo@eurid.eu>=0D=0A =20<C21F43CF-9CA9-4A40-A7CC-463C5139F362@secure64.com>=0D =0A=20<E2FDD0E1-9C08-43C4-967E-1AE9102D817E@nic.cz>; bh=N4SUXNnRuOcgDnkZn0bg3OS+0yMYmmjPr6NVOp55pnI=; b=xaakfYE1iQJ4fB1hFJxZNyHVS4eS4F8HjRGzNYYJoVbulGXb11GpaUH0 KBPfyYUf21WUf+Yii6eITyc7aUft2sC4ofO/7Or6Z//q5uD0bp7LdBwlG u4fHu3DRiZaGraU;
X-IronPort-AV: E=Sophos;i="4.75,343,1330905600"; d="scan'208";a="32260397"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 30 Mar 2012 11:19:45 +0100
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; Fri, 30 Mar 2012 11:19:44 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Ondřej Surý <ondrej.sury@nic.cz>
Thread-Topic: [DNSOP] New Version Notification for draft-gersch-dnsop-revdns-cidr-00.txt
Thread-Index: AQHNDl02iNxAl6YiKkK0tj1P/kJikZaCj8GA
Date: Fri, 30 Mar 2012 10:19:43 +0000
Message-ID: <2C012FE1-A40D-473F-89D8-52673182A581@nominet.org.uk>
References: <20120217000918.22307.43753.idtracker@ietfa.amsl.com> <2D04DB88-9570-4DE3-A796-F4F07AF5EF74@secure64.com> <017101ccefd5$51790560$f46b1020$@lampo@eurid.eu> <C21F43CF-9CA9-4A40-A7CC-463C5139F362@secure64.com> <E2FDD0E1-9C08-43C4-967E-1AE9102D817E@nic.cz>
In-Reply-To: <E2FDD0E1-9C08-43C4-967E-1AE9102D817E@nic.cz>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="utf-8"
Content-ID: <b7237213-0a12-41a3-81bc-33e7ab8a1afe>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-gersch-dnsop-revdns-cidr-00.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, 30 Mar 2012 10:19:47 -0000

On 30 Mar 2012, at 12:09, Ondřej Surý wrote:

> Hi Joseph,
> 
> since I am not sure if you understood my point (I am not sure if I was able
> to understand it myself :), I am summarizing it to the mailing list.
> 
> I like the direction of your work, but I miss a way how to put more stuff under
> the named prefix.
> 
> I would like you to update RFC2317 together with your document, so the end
> customers don't have two distinct trees in their DNS infrastructure.

+1

> F.e. if I have 1.0.m.82.129.in-addr.arpa prefix in the DNS and I have delegate
> it to the customer, how do I put my PTRs in?  The block owner would still have
> to delegate another "dummy" prefix with CNAMEs and you have to handle it in
> separate zone.
> 
> BTW one more observation.  Since you don't have to do any zone cuts in the binary
> part, why not merge them into just one label?  E.g. something like 10.m.82.129.in-addr.arpa or 10001101.m.82.129.in-addr.arpa.

With the current scheme it's possible to delegate longer prefixes, and this is a necessary feature.

The stuff Dan was saying about two alternate representations concerns me, though.  As written, by default:

  192.168.64/18 is 1.0.m.168.192

but

  192.168.64/24 is 64.168.192

which is not a sub-domain of the enclosing /18 representation.

This way lies dragons, I think...

Ray

v2.23.0 | Report a Bug | By Email