IETF Logo Mail Archive

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

Steven Barth <cyrus@openwrt.org> Wed, 22 July 2015 07:45 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 484E21AD0B1 for <mif@ietfa.amsl.com>; Wed, 22 Jul 2015 00:45:03 -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 m4I-WJqXIrk0 for <mif@ietfa.amsl.com>; Wed, 22 Jul 2015 00:45:01 -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 7BB761ACE2C for <mif@ietf.org>; Wed, 22 Jul 2015 00:45:01 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1ZHoi3-0001aP-49 with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) for mif@ietf.org; Wed, 22 Jul 2015 09:44:59 +0200
To: mif@ietf.org
References: <55AF4226.8010803@openwrt.org>
From: Steven Barth <cyrus@openwrt.org>
Message-ID: <55AF49FA.4020605@openwrt.org>
Date: Wed, 22 Jul 2015 09:44:58 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55AF4226.8010803@openwrt.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mif/AcnuKKPXIDzMcXp1ZNVSYjuDY7c>
Subject: Re: [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:45:03 -0000

> 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?
Actually strike that, I should not review this early in the morning.
Anyway it makes sense to allow for future id-types to be
skippable, still may be debatable whether it should be depending on if
the configuration or whatever protocol actually requires it.

v2.23.0 | Report a Bug | By Email