Re: Flow Label support in the Node Requirements bis document
Brian Haberman <brian@innovationslab.net> Thu, 10 November 2011 21:25 UTC
Return-Path: <brian@innovationslab.net>
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 1CBD221F8A35 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 13:25:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.932
X-Spam-Level:
X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8OTifc-X7ZTK for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 13:25:49 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 80DF421F8A58 for <ipv6@ietf.org>; Thu, 10 Nov 2011 13:25:49 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 017B788244 for <ipv6@ietf.org>; Thu, 10 Nov 2011 13:25:49 -0800 (PST)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 9CE391368145 for <ipv6@ietf.org>; Thu, 10 Nov 2011 13:25:48 -0800 (PST)
Message-ID: <4EBC415B.3080701@innovationslab.net>
Date: Thu, 10 Nov 2011 16:25:47 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Flow Label support in the Node Requirements bis document
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
In-Reply-To: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Thu, 10 Nov 2011 21:25:50 -0000
I agree that an update should be done prior to publishing the Node Requirements draft, but I have some issues with the language (not the intent) proposed below... On 11/2/11 10:50 PM, john.loughney@nokia.com wrote: > Hi all, > > There has been some discussions whether or not we should add support for the Flow Label in > Soon to be RFC 6434<draft-ietf-6man-node-req-bis-11.txt> As a straw man proposal, if we add > Support, I would suggest the following text: > > All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification, > defines the IPv6 Flow Label. Specifically: > > "Forwarding nodes such as routers and load distributors MUST NOT > depend only on Flow Label values being uniformly distributed. " > > "It is therefore RECOMMENDED that source hosts support the flow > label by setting the flow label field for all packets of a given flow to the > same value chosen from an approximation to a discrete uniform distribution. " First, I propose that the text be added to section 5.1, which discusses the specifications that must be supported at the IPv6 layer. Second, I would modify the text proposed to clean up the introductory component as follows: All nodes SHOULD support the setting and use of the IPv6 Flow Label field as defined in the IPv6 Flow Label specification [RFC6437]. Forwarding nodes such as routers and load distributors MUST NOT depend only on Flow Label values being uniformly distributed. It is RECOMMENDED that source hosts support the flow label by setting the Flow Label field for all packets of a given flow to the same value chosen from an approximation to a discrete uniform distribution. Regards, Brian (who is not wearing any hats at this time)
- Flow Label support in the Node Requirements bis d… john.loughney
- Re: Flow Label support in the Node Requirements b… Brian E Carpenter
- RE: Flow Label support in the Node Requirements b… Sheng Jiang
- Re: Flow Label support in the Node Requirements b… John Leslie
- Re: Flow Label support in the Node Requirements b… Thomas Narten
- Re: Flow Label support in the Node Requirements b… John Leslie
- Re: Flow Label support in the Node Requirements b… Shane Amante
- Re: Flow Label support in the Node Requirements b… t.petch
- Working Group last call for adding RFC6437 Flow L… Bob Hinden
- Re: Working Group last call for adding RFC6437 Fl… Brian E Carpenter
- Re: Flow Label support in the Node Requirements b… Brian Haberman
- Re: Working Group last call for adding RFC6437 Fl… Shane Amante
- Re: Working Group last call for adding RFC6437 Fl… Tim Chown
- RE: Working Group last call for adding RFC6437 Fl… George, Wes
- Re: Working Group last call for adding RFC6437 Fl… Bob Hinden
- Re: Working Group last call for adding RFC6437 Fl… Jari Arkko