Re: [v6ops] Thoughts on draft-yourtchenko-ra-dhcpv6-comparison

Owen DeLong <owen@delong.com> Mon, 16 December 2013 23:47 UTC

Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C081ADE87 for <v6ops@ietfa.amsl.com>; Mon, 16 Dec 2013 15:47:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level:
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
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 ZkurMJi-Eay9 for <v6ops@ietfa.amsl.com>; Mon, 16 Dec 2013 15:47:42 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 7D83C1ADF7F for <v6ops@ietf.org>; Mon, 16 Dec 2013 15:47:41 -0800 (PST)
Received: from [IPv6:2620::930:0:ca2a:14ff:fe3e:d024] ([IPv6:2620:0:930:0:ca2a:14ff:fe3e:d024]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id rBGNiwdc013816 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 16 Dec 2013 15:44:58 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com rBGNiwdc013816
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1387237498; bh=AW6EAf6skcbab2C3w0GvPRzA5MY=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=ESAzvS0I4MpY2DuKGx72EnhXtRliIz/03cVNZJf26SZdzeYagm/PMY6O8k5WIcu8B iSq4fBjJIQ8DzJOQLLt6XH1goJNZtHhg6MZ8SeU7ZPtgUbA19bGy3f1K8rSkvAwOkZ m90GC7G3cfArQ22ZTzfeucNzzHAYKDVRV5tCv0WA=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <904EFC8A-7B13-4F1A-B538-A6605E635C3D@employees.org>
Date: Mon, 16 Dec 2013 15:44:51 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F979825F-A6E2-4D81-9C92-C868B4B2F29C@delong.com>
References: <CAKD1Yr0evKjEEvErq3T=nU6_joat8duseraJJDZ4OHPK9NGWDA@mail.gmail.com> <D1A3AA08-F644-4C43-87DA-06028A781166@nominum.com> <CAKD1Yr3J_MYjxmifP7j--2xcR6mOhSbUnPGQjX0G4+AxhJqFpQ@mail.gmail.com> <94433006-8AF6-45ED-B247-03EC1B397356@employees.org> <FC156001-06A1-47CD-AB06-BABA7E6C4EFA@delong.com> <904EFC8A-7B13-4F1A-B538-A6605E635C3D@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1822)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [IPv6:2620:0:930::200:2]); Mon, 16 Dec 2013 15:44:58 -0800 (PST)
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Thoughts on draft-yourtchenko-ra-dhcpv6-comparison
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Dec 2013 23:47:44 -0000

On Dec 16, 2013, at 13:46 , Ole Troan <otroan@employees.org> wrote:

> Owen,
> 
>>>>> Second: some of the text you have now deals with link-layer performance. However, I think that since these are configuration protocols, the attributes that are important are primarily semantics, not performance or implementation.
>>>> 
>>>> Lorenzo, this is kind of a puzzling position to take.   There are lots of ways to do things with really nice semantics that fall on their face for performance reasons.   So I think performance questions are in scope.
>>>> 
>>>> Oh, of course - in general, they are. But here the protocols used are so similar that there is little substantive difference in performance.
>>> 
>>> could you expand on that?
>>> I see the scaling properties on a multicast capable link very different between the two.
>>> take a multicast capable link with 10K nodes on it, where power has just come back.
>>> a few hundred RS/RA messages, at least 40K DHCPv6 messages.
>> 
>> I'm trying to think of a multi-user network technology still in use today where 40,000 packets over a couple of minutes time is likely to be a significant load and I'm failing to come up with one.
> 
> indeed, I wasn't thinking of link-congestion, but processing time. on the DHCP server and the first-hop switches and routers.
> do you agree that RS/RA and DHCP scales quite differently in this scenario?

Meh... I think most modern DHCP servers could actually take that kind of load without too much problem. In any real world scenario, 10,000 hosts that are all DHCP clients on the same segment isn't all that likely. However, even if we forego that reality for a moment, they won't likely be homogeneous which means that they will take different amounts of time to get to where they want to make their DHCP requests. Can we agree that the spread would be at least 45 seconds and more likely somewhere in the neighborhood of 120 seconds from the time of the first host requesting to the last?

If so, then you're talking about 40,000 packets (10,000 requests) over 45 seconds = <1,000 PPS. If your switch and/or DHCP server can't handle 1,000 PPS from 10,000 nodes, I'm mystified as to how you expect that network to work when the power hasn't failed recently.

I think in terms of the switch, there are a number of problems that are more impactful than DHCP that would prevent me from attempting to put 10K nodes on a single network segment.

So, yes, I suppose, technically, there is a valid argument that the scaling properties of RA and DHCP are different. However, I think it's kind of the networking equivalent of Zeno's paradox... At some point you have to just accept that close enough is close enough and splitting the hair any further is pointless. I think this goes beyond that point.

> (then we can argue later if the differences matter or not).
> 

I guess I'll concede that there is a theoretical difference, but I remain unconvinced of an actual difference. I'm pretty sure that the theoretical difference doesn't really matter.

To know whether the actual one did or not, I'd have to see an example where it might.

Owen