IETF Logo Mail Archive

Re: [DNSOP] AD sponsoring draft-cheshire-sudn-ipv4only-dot-arpa

Philip Homburg <pch-dnsop-3@u-1.phicoh.com> Thu, 05 July 2018 10:05 UTC

Return-Path: <pch-bCE2691D2@u-1.phicoh.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 9D237130E3F for <dnsop@ietfa.amsl.com>; Thu, 5 Jul 2018 03:05:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FfcGpp4XgT2i for <dnsop@ietfa.amsl.com>; Thu, 5 Jul 2018 03:05:52 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62FCE130E24 for <dnsop@ietf.org>; Thu, 5 Jul 2018 03:05:52 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1fb194-0000FpC; Thu, 5 Jul 2018 12:05:50 +0200
Message-Id: <m1fb194-0000FpC@stereo.hq.phicoh.net>
To: dnsop@ietf.org
From: Philip Homburg <pch-dnsop-3@u-1.phicoh.com>
Sender: pch-bCE2691D2@u-1.phicoh.com
In-reply-to: Your message of "Wed, 4 Jul 2018 16:26:06 -0400 ." <CAHw9_iK605yw--xE0NutaF=r+MfmmT2cBj9eNnSOh4Swkx=_QQ@mail.gmail.com>
Date: Thu, 05 Jul 2018 12:05:49 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/VGE4LbPe3ZCgoXB_eG6mVVAFFbE>
Subject: Re: [DNSOP] AD sponsoring draft-cheshire-sudn-ipv4only-dot-arpa
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.26
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: <https://mailarchive.ietf.org/arch/browse/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, 05 Jul 2018 10:05:55 -0000

>draft-cheshire-sudn-ipv4only-dot-arpa document

Section 7.1:
"Name resolution APIs and libraries MUST recognize 'ipv4only.arpa' as
"special and MUST give it special treatment. 

It seems to me that it is going way to far to require all DNS software to
implement support for a hack that abuses DNS for configuration management of
a rather poor IPv4 transition technology.

I think the more obvious approach is to formally deprecate RFC 7050 and
require nodes that need to do NAT64 address synthesis use one of the other
methods for obtaining the NAT64 prefix.

The only part of the draft that makes sense to me is to make ipv4only.arpa
an insecure delegation. 

Any other problems are better solved by deprecating RFC 7050.

v2.23.0 | Report a Bug | By Email