Re: [mif] Comments about default route and draft-ietf-mif-dhcpv6-route-option-02

Ted Lemon <Ted.Lemon@nominum.com> Tue, 02 August 2011 15:43 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 226AF11E807B for <mif@ietfa.amsl.com>; Tue, 2 Aug 2011 08:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.478
X-Spam-Level:
X-Spam-Status: No, score=-106.478 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wtS7pPfgqqJs for <mif@ietfa.amsl.com>; Tue, 2 Aug 2011 08:43:38 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 349D421F84BF for <mif@ietf.org>; Tue, 2 Aug 2011 08:43:32 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKTjgbJliKxmpHiNkUAcS4OmjI7TWF5d+0@postini.com; Tue, 02 Aug 2011 08:43:42 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 922741B819A for <mif@ietf.org>; Tue, 2 Aug 2011 08:43:31 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D0A1819005D; Tue, 2 Aug 2011 08:43:29 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0289.001; Tue, 2 Aug 2011 08:43:24 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
Thread-Topic: [mif] Comments about default route and draft-ietf-mif-dhcpv6-route-option-02
Thread-Index: AQHMUSf8EeUO6S0EmUqrEB5G+j+sPZUKJTwAgAADngA=
Date: Tue, 02 Aug 2011 15:43:23 +0000
Message-ID: <1185116F-C8B3-4EF2-AEAA-CE6B71E9EAA9@nominum.com>
References: <4E38162B.1040507@gmail.com> <4E381812.7040802@viagenie.ca>
In-Reply-To: <4E381812.7040802@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.162.214.218]
Content-Type: multipart/alternative; boundary="_000_1185116FC8B34EF2AEAACE6B71E9EAA9nominumcom_"
MIME-Version: 1.0
Cc: "<mif@ietf.org>" <mif@ietf.org>
Subject: Re: [mif] Comments about default route and draft-ietf-mif-dhcpv6-route-option-02
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 02 Aug 2011 15:43:39 -0000

On Aug 2, 2011, at 11:30 AM, Marc Blanchet wrote:
I don't agree with your assessment of waste of memory and bandwidth.
This usage of bandwidth is completly noise compared to a single http request on the wire.

Calling this a bandwidth issue is kind of a misnomer.   This is really an issue of space in the DHCPv6 packet.   It's a UDP packet, of limited size, and it's not completely unreasonable to want to save 9 bytes in it.

Having said that, I find this argument unconvincing, for the simple reason that when you count the additional overhead of sending two options, you've already lost four of those nine bytes.

The other argument is about lifetimes.   But DHCP already has lifetimes; if this is unclear in the draft, perhaps the draft needs to be made more clear.   I haven't read it with this question in mind (indeed, I haven't read it in over a year) so I can at least imagine that this is a valid criticism, but if it is an accurate criticism, it is valid not only for the default route, but for all other routes as well, and so it needs to be addressed in the current draft.