[mif] Domain name issue in draft-stenberg-mif-mpvd-dns

Ray Bellis <ray@bellis.me.uk> Tue, 15 March 2016 10:26 UTC

Return-Path: <ray@bellis.me.uk>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4AB5B12D972; Tue, 15 Mar 2016 03:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id x8XJGuA4Zurx; Tue, 15 Mar 2016 03:26:44 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net []) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAF2A12D936; Tue, 15 Mar 2016 03:26:40 -0700 (PDT)
Received: from [] (port=51090 helo=rays-mbp.local) by hydrogen.portfast.net ([]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1afmBS-00018i-84 (Exim 4.72) (return-path <ray@bellis.me.uk>); Tue, 15 Mar 2016 10:26:38 +0000
To: mif@ietf.org, draft-stenberg-mif-mpvd-dns@ietf.org
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <56E7E35D.6040108@bellis.me.uk>
Date: Tue, 15 Mar 2016 10:26:37 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mif/1vAJcV4riP5Q7zwuwSlUHqEi81U>
X-Mailman-Approved-At: Tue, 15 Mar 2016 03:30:51 -0700
Subject: [mif] Domain name issue in draft-stenberg-mif-mpvd-dns
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mif/>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2016 10:26:46 -0000

Looking at section 3 of this draft, I have a problem with the
specification where it says that for e.g. a /64 the DNS lookup should be
for _pvd., and likewise the
/80 example (with 12 leading zeros).

Taking the /80 example, it would be impossible given this specification
to distinguish between a /80 where the bits between 64 and 80 were all
zeros and the corresponding /64 - they would both end up at the same
point in the ip6.arpa hierarchy.

In my opinion (and I do have some prior art in this space, see RFC 7216)
the "_pvd" label must be at the point in the ip6.arpa that presents the
same level as the prefix being queried for.  Any leading zeros below
that point (i.e. to the left in the domain name) MUST be omitted.

Hence in the /80 case, it would be _pvd.<20 labels>.ip6.arpa and in the
/64 case it would be _pvd.<16 labels>.ip6.arpa