Re: [dhcwg] draft-despres-intarea-4rd comments
Rémi Després <remi.despres@free.fr> Fri, 01 April 2011 07:39 UTC
Return-Path: <remi.despres@free.fr>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E7BA3A6AF8 for <dhcwg@core3.amsl.com>; Fri, 1 Apr 2011 00:39:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
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 myBXDCXHSwoT for <dhcwg@core3.amsl.com>; Fri, 1 Apr 2011 00:39:43 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.1]) by core3.amsl.com (Postfix) with ESMTP id 299F03A6BEC for <dhcwg@ietf.org>; Fri, 1 Apr 2011 00:39:43 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2118.sfr.fr (SMTP Server) with ESMTP id 4077E7000090; Fri, 1 Apr 2011 09:41:22 +0200 (CEST)
Received: from dhcp-45cd.meeting.ietf.org (dhcp-45cd.meeting.ietf.org [130.129.69.205]) by msfrf2118.sfr.fr (SMTP Server) with ESMTP id BE8BA700008B; Fri, 1 Apr 2011 09:41:21 +0200 (CEST)
X-SFR-UUID: 20110401074121780.BE8BA700008B@msfrf2118.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="iso-8859-1"
From: Rémi Després <remi.despres@free.fr>
In-Reply-To: <4D9495E0.5030404@gmail.com>
Date: Fri, 01 Apr 2011 09:41:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD783472-1F76-4748-9173-4E972CDF80DA@free.fr>
References: <4D9495E0.5030404@gmail.com>
To: Tomasz Mrugalski <tomasz.mrugalski@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: DHC WG <dhcwg@ietf.org>, draft-despres-intarea-4rd@tools.ietf.org
Subject: Re: [dhcwg] draft-despres-intarea-4rd comments
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2011 07:39:44 -0000
Hi Tomasz, Comments in line. Le 31 mars 2011 à 16:55, Tomasz Mrugalski a écrit : > I have partially read the draft (mostly the parts related to DHCPv6) and > would like to provide my comments. I may have additional comments as I > finish proper reading throughout the draft. > > First, I'm sorry if my comments may seem a bit harsh, but the currently > proposed option format is catastrophic. It is basically several > suboptions stuffed together with suboption-like type and length coded on > nibbles, rather than usual 2 byte fields, with some suboptions being > optional. These parameters should clearly be defined as separate options > (possibly grouped together as suboptions within an option for clarity). Thanks for expressing a view, this was the goal of this presentation. No catastrophy ahead, there is enough time make proposal that reach consensus in the WG. > Defined that way, it would be much easier to parse/build such options by > involved entities. I will also be less problematic to support by > implementations that also definition of custom options. Luckily, that > can be fixed quite easily. Hopefully, there are no (or very limited) > implementations, so redoing the option layout should be no problem. No implementation I heard of includes the DHCPv6 part of the draft. > There are no usual DHCPv6 Server or Client Behavior sections. Although > not strictly required, they are very convienient for vendors that are > looking for clean list of requirements that they must meet to claim spec > conformance. > > There is no mention of DHCPv6 related problems in Security > Considerations section whatsoever. This should be analysed a bit and > commented in the text (possibly briefly if there are no new issues here, > with just pointers to existing RFCs). No 4rd specific security concern about dhcpv6 ahd been identified, and RFC 5969 on 6rd has no such mention. Yet, if you have a particular suggestion, why not? > Also, I have a procedural recommendation. I happen to have worked on > DHCPv6 option for another IPv4-IPv6 coexistence architecture. The actual > architecture and the DHCPv6 operation were specified in separate, but > closely related documents. It worked really well, because discussed > problems and review groups are mostly orthogonal. They could also > possibly follow separate adoption paths (or perhaps not, but that is > something that should be possibly considered). Doing it earlier might have been more complex than needed, but doing it for a later version does make sense to me. A volunteer for te DHCPv6 draft will be welcome (I am clearly not an expert of this WG). > Remi asked for DHC experts to provide help with this. I'm not sure if I > qualify to that distinction, but I'm happily volunteering for work on > this. I will coordinate with Remi and other authors how they would like > to organize the work. > Hope that helps, IMHO, it does, thank you. Regards, RD > Tomek Mrugalski > ISC
- [dhcwg] draft-despres-intarea-4rd comments Tomasz Mrugalski
- Re: [dhcwg] draft-despres-intarea-4rd comments Rémi Després
- Re: [dhcwg] draft-despres-intarea-4rd comments Tomasz Mrugalski