[mif] Comments on draft-ietf-mif-mpvd-id-01

Steven Barth <cyrus@openwrt.org> Wed, 22 July 2015 07:11 UTC

Return-Path: <cyrus@openwrt.org>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 101D11ACE2E for <mif@ietfa.amsl.com>; Wed, 22 Jul 2015 00:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level:
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=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 AaaorOewsPqU for <mif@ietfa.amsl.com>; Wed, 22 Jul 2015 00:11:37 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74C921ACE26 for <mif@ietf.org>; Wed, 22 Jul 2015 00:11:37 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1ZHoBj-0000So-9i with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) for mif@ietf.org; Wed, 22 Jul 2015 09:11:35 +0200
From: Steven Barth <cyrus@openwrt.org>
To: mif@ietf.org
Message-ID: <55AF4226.8010803@openwrt.org>
Date: Wed, 22 Jul 2015 09:11:34 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.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/_3Ur0jJB-WKo_vK316q3Qo3EFvc>
Subject: [mif] Comments on draft-ietf-mif-mpvd-id-01
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 22 Jul 2015 07:11:39 -0000

Hello everyone,

below a few comments for the MPVD ID draft.


3 I'm unsure about the id-length field. It seems entirely redundant for e.g.
DHCP(v6) purposes and even considering e.g. RAs it is redundant for half of
the given id-types. Should this be type-specfic instead?


3 I'm unsure if cross references to the draft that in turn references this
one are wise, also wrt. informative / normative reference sections.


3 id-type
Encoding and / or allowed lengths are entirely unclear for most types you declare.
Are they supposed to be strings, BE integers, ...? How big are they supposed to be?
Shall I be able to use 16, 32 or maybe even 24bit numbers for representing the OID?

0x04: RFC 4282 specifies the assignment of NAI Realms to be tied to domain names,
so this type seems mostly redundant since you alreay have FQDN.

0x06: This looks overly specific to me. Why not have a generic (unicast) prefix type,
so people could also use their RIPE / ARIN / ... assigned UC addresses? E.g. prefix
length followed by arbitrary length ipv6 prefix.



4 What if I want to use this outside a configuration protocol?

4 Undefined reference to "PVD container option"

In general 4 seems awkward / misplaced here, since you are defining an abstract identifier.



Cheers,

Steven