Re: AD review of draft-ietf-6man-flow-update

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 21 June 2011 13:48 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B583C11E80C1 for <ipv6@ietfa.amsl.com>; Tue, 21 Jun 2011 06:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.487
X-Spam-Level:
X-Spam-Status: No, score=-103.487 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 gwllqm+WBeUP for <ipv6@ietfa.amsl.com>; Tue, 21 Jun 2011 06:48:28 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id F161711E80AC for <ipv6@ietf.org>; Tue, 21 Jun 2011 06:48:27 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2086657fxm.31 for <ipv6@ietf.org>; Tue, 21 Jun 2011 06:48:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BIjRoNSn5KR2nQlx8Mn8EEWGNT8NofiHoumE7bmqKsc=; b=xT16fuF32R7ege5PP70rmfXgiA8g6eel0diZz7HaRfz7ngqyxfpmEw8siiXRLRkzIp 1vSOMKzQYwO7jgODY6R3m95X/xqy2zyDy9tvHPd9+osLxYdJJXGrYRAVeF9/1dcMxobr kXzubhy7i1nIjrUc90a0jbQHRFagbDPQVGHtk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=HBBNsu43v2HXx/Qcv9pHfaB5dBUISyu3C1CMNzKyENT2j+LKAv1zvxK7qGDXJH/8nF 062QijGiHeak5KMU3j0qy1xR8Lw73afYHL/nIyz1rcaopDEwr1stywtZN49RsSl16neH ulcvY8IhfqT5Hj3zFH8YvIJUE/tHg/uvpLzGY=
Received: by 10.223.59.146 with SMTP id l18mr130489fah.58.1308664106779; Tue, 21 Jun 2011 06:48:26 -0700 (PDT)
Received: from [10.255.25.96] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id 11sm3411169fax.36.2011.06.21.06.48.24 (version=SSLv3 cipher=OTHER); Tue, 21 Jun 2011 06:48:25 -0700 (PDT)
Message-ID: <4E00A123.6000209@gmail.com>
Date: Wed, 22 Jun 2011 01:48:19 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: AD review of draft-ietf-6man-flow-update
References: <023C12B3-CBC6-4406-82FE-ED7707ACE7A6@gmail.com>
In-Reply-To: <023C12B3-CBC6-4406-82FE-ED7707ACE7A6@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 13:48:28 -0000

Ran,

On 2011-06-22 01:03, RJ Atkinson wrote:
> Earlier, Brian Carpenter wrote:
>> I'd have to trawl the archive to find all the arguments,
>> but the main issue was that any attempt to include semantics
>> in the bits of the flow label leads to complexity that
>> probably can't be handled at line speed in a scaleable way.
> 
> That claim presumes that a typical IPv6 router is using CPU-based
> packet forwarding.  I believe that assumption to be incorrect.
> (By the way, this assumption underlies a lot of the discussion
> on the IPv6 list.  Those of us who build ("have built", in my own 
> case) real routers try to speak up about this from time to time,
> apparently without having much impact on WG thinking.
> 
> I believe that most deployed IPv6 routers are using ASIC-based
> or FPGA-based forwarding of IPv6 packets.  NP-based forwarding
> is not uncommon, but is probably less common.  An advantage
> of NP-based forwarding engines or FPGA-based forwarding engines
> is that new capabilities can be added on the fly.  While some
> deployed ASIC-based forwarding engines are programmable, most 
> IPv6-capable ASIC forwarding engines are not programmable.
> 
> Even the really low-cost consumer electronics routers that 
> support IPv6 generally do so via commodity silicon packet 
> processors offered by a range of different merchant silicon 
> firms based in various countries (example: Broadcom).
> 
> Since the majority of the lifespan of IPv6 is well into the 
> future, and deployment today remains pretty small today,
> compared with say 3 years from now, re-allocating those 4 bits 
> seems entirely possible to me.

Anything's possible. I was trying to summarise what I recall
from the discussions that led to the WG consensus.

> 
>> Also 16 bits might make it too easy for a malicious party
>> to predict flow label values.
> 
> That makes no mathematical sense to me.
> 
> To the extent 16 bits is problematic, 20 bits also would be
> problematic.  So that argument also does not make sense to me.
> Even if someone has formal maths behind that claim, which so far
> I haven't seen claimed on the IPv6 WG list, Moore's Law would
> defeat any claim that 20 bits is adequate within ~5 years.

Sure, we are talking about the difference between a brute force
attack with a million choices vs 65k choices; not a strong argument,
of course.

   Brian