Re: [DNSOP] WGLC: "Considerations for the use of DNS Reverse Mapping"

Andrew Sullivan <ajs@commandprompt.com> Mon, 28 April 2008 22:01 UTC

Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: dnsop-archive@optimus.ietf.org
Delivered-To: ietfarch-dnsop-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05F813A6AB5; Mon, 28 Apr 2008 15:01:32 -0700 (PDT)
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 47E8F3A6C8C for <dnsop@core3.amsl.com>; Mon, 28 Apr 2008 15:01:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.991
X-Spam-Level:
X-Spam-Status: No, score=-0.991 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311]
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 R3klLw758GBY for <dnsop@core3.amsl.com>; Mon, 28 Apr 2008 15:01:29 -0700 (PDT)
Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by core3.amsl.com (Postfix) with ESMTP id 95B593A6AB5 for <dnsop@ietf.org>; Mon, 28 Apr 2008 15:01:29 -0700 (PDT)
Received: from commandprompt.com (227-54-222-209.mycybernet.net [209.222.54.227]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m3SM2AXN025574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Mon, 28 Apr 2008 15:02:13 -0700
Date: Mon, 28 Apr 2008 18:01:29 -0400
From: Andrew Sullivan <ajs@commandprompt.com>
To: dnsop@ietf.org
Message-ID: <20080428220128.GC3445@commandprompt.com>
References: <20080314034500.GE7553@x27.adm.denic.de> <20080326142252.GA11184@nic.fr> <20080329191803.GA362@commandprompt.com> <47EEA725.2060807@ca.afilias.info> <m2lk3ujqz2.wl%Jinmei_Tatuya@isc.org> <20080404023428.GA1040@commandprompt.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20080404023428.GA1040@commandprompt.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Mon, 28 Apr 2008 15:02:14 -0700 (PDT)
Subject: Re: [DNSOP] WGLC: "Considerations for the use of DNS Reverse Mapping"
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/pipermail/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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org

Dear colleagues,

On Thu, Apr 03, 2008 at 10:34:29PM -0400, Andrew Sullivan wrote:
> On Thu, Apr 03, 2008 at 07:25:53PM -0700, JINMEI Tatuya / 神明達哉 wrote:

> > address.  So, it's not "in use within a range, and referenced in a
> > forward mapping".  Does this mean this address is not covered by the
> > above sentence of Section 4.2?

[. . .]

> > still covered by this sentence, but the following sentence seems to
> > indicate the opposite.
> 
> Sorry, I see the problem now with my response.  No, the temporary
> address does not need to have a reverse mapping, for exactly the same
> reason that it does not need a forward one.
> 
> I will attempt to come up with a sentence that makes this clearer,
> given that it obviously isn't so far.

I have attempted to address this problem by changing the text from

   Unless there are strong counter-considerations, such as a high
   probability of forcing large numbers of queries to use TCP, IP
   addresses in use within a range and referenced in a forward mapping
   should have a reverse mapping.

to

   Unless there are strong counter-considerations, such as a high
   probability of forcing large numbers of queries to use TCP, IP
   addresses both in use within a range, and referenced in a forward
   mapping, should have a reverse mapping.

Does this address the concern?

I put this into the tracker as issue 21.

Best regards,

A

-- 
Andrew Sullivan
ajs@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop