Re: Working Group last call for adding RFC6437 Flow Label support to Node Requirements bis document

Tim Chown <tjc@ecs.soton.ac.uk> Fri, 11 November 2011 20:07 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 2479521F85DB for <ipv6@ietfa.amsl.com>; Fri, 11 Nov 2011 12:07:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 IAmLrb1sGkbF for <ipv6@ietfa.amsl.com>; Fri, 11 Nov 2011 12:07:33 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id F237F21F87D3 for <ipv6@ietf.org>; Fri, 11 Nov 2011 12:07:32 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id pABK7Hs9014087; Fri, 11 Nov 2011 20:07:17 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk pABK7Hs9014087
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1321042037; bh=gZANnrsEc4hMOSxaNw03aN5o/LI=; h=Subject:Mime-Version:From:In-Reply-To:Date:Cc:References:To; b=BO+rH6qIsc0rTveJSFgG0EPDpsLLVSigfHGFpNSshdJBnyvoqMxIfLM+PHUydhIj+ lEOW1WLXQmbzPAwa9KpymHxLZT8WP+VklA2c6Dae7w8dqbhQFi0HYfQVTpVihx2aPO aQvfwpEcFKf4zOyBCJc2klkvE6Su0MLZMZa8uR08=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id nAAK7H0543743651OX ret-id none; Fri, 11 Nov 2011 20:07:17 +0000
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id pABK698v002168 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 Nov 2011 20:07:02 GMT
Subject: Re: Working Group last call for adding RFC6437 Flow Label support to Node Requirements bis document
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset="us-ascii"
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAA1335D-191B-4C55-A1B4-5D3F951C68F7@castlepoint.net>
Date: Fri, 11 Nov 2011 20:07:01 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|fb418a899c92787cccf76ebe9a1af9acnAAK7H03tjc|ecs.soton.ac.uk|3E19C111-2EAA-4A73-A602-75D6853A4777@ecs.soton.ac.uk>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com> <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.com> <4EBC2BB9.4030308@gmail.com> <CAA1335D-191B-4C55-A1B4-5D3F951C68F7@castlepoint.net> <3E19C111-2EAA-4A73-A602-75D6853A4777@ecs.soton.ac.uk>
To: Shane Amante <shane@castlepoint.net>
X-Mailer: Apple Mail (2.1251.1)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=nAAK7H054374365100; tid=nAAK7H0543743651OX; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: pABK7Hs9014087
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Haberman <brian@innovationslab.net>, 6man Mailing List <ipv6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
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: Fri, 11 Nov 2011 20:07:34 -0000

Agree.

On 11 Nov 2011, at 04:13, Shane Amante wrote:

> 
> On Nov 10, 2011, at 12:53 PM, Brian E Carpenter wrote:
>> I support this change.
> 
> +1.
> 
> -shane
> 
> 
> 
>> Regards
>>  Brian Carpenter
>> 
>> On 2011-11-11 06:00, Bob Hinden wrote:
>>> This email starts a one week 6MAN Working Group last call for adding text and a reference to RFC6437 "IPv6 Flow Label Specification" to the Node Requirements bis document current in AUTH48 state.  The document is currently on hold in the RFC Editor waiting for resolution of this issue.  
>>> 
>>> The proposed text, first sent to the ipv6@ietf.org mailing list on November 2, 2011 (included below), is:
>>> 
>>>> 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. "
>>> 
>>> The chairs have discussed this with the Internet Area Directors and they recommended this course of action.  This topic is also on the agenda for the 6man session at the Taipei IETF.
>>> 
>>> Substantive comments and statements of support for taking this action should be sent to the mailing list.  This last call will end on November 17, 2011.
>>> 
>>> Regards,
>>> Bob Hinden & Brian Haberman
>>> 
>>> 
>>> Begin forwarded message:
>>> 
>>>> From: <john.loughney@nokia.com>
>>>> Date: November 2, 2011 7:50:35 PM PDT
>>>> To: <ipv6@ietf.org>
>>>> Subject: Flow Label support in the Node Requirements bis document
>>>> 
>>>> 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. "
>>>> 
>>>> I'd like to ask the wg the following:
>>>> 
>>>> 1) Is the above text acceptable?
>>>> 2) Do you support adding the text? If no, please suggest text, unless you do not support adding
>>>>   Flow label support at all (please say so).
>>>> 
>>>> John
>>>> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org
>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>> 
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>> 
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------