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

Bob Hinden <bob.hinden@gmail.com> Thu, 10 November 2011 17:00 UTC

Return-Path: <bob.hinden@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 672F221F8B5C for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 09:00:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.061
X-Spam-Level:
X-Spam-Status: No, score=-103.061 tagged_above=-999 required=5 tests=[AWL=0.538, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 duYoZfmazHiR for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 09:00:17 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 74A1D21F8B5E for <ipv6@ietf.org>; Thu, 10 Nov 2011 09:00:16 -0800 (PST)
Received: by eyg24 with SMTP id 24so3030592eyg.31 for <ipv6@ietf.org>; Thu, 10 Nov 2011 09:00:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=A1Qqyhk+1vxgBbcD7LPhDWR86jHNhe11jsWrHYnIj4g=; b=fYY8WWK4LTDQL2T3xNslPz8IXZsvfAWeLZzKWCbYuQKvKzZbVoofdqg8GzqPSxpt0v 24dW1sCzPaHXSxfyXcBzMcyRZBGiVCOBWibOiIcSUGsxvayKtLvtvwJCjcRmceeuhdN3 JUhddUhkYaNpK88ELjWJ2cdmgiovWK+7/YrhU=
Received: by 10.68.7.132 with SMTP id j4mr16518481pba.11.1320944414690; Thu, 10 Nov 2011 09:00:14 -0800 (PST)
Received: from [10.0.0.25] (c-24-130-227-241.hsd1.ca.comcast.net. [24.130.227.241]) by mx.google.com with ESMTPS id p10sm22759220pbd.15.2011.11.10.09.00.12 (version=SSLv3 cipher=OTHER); Thu, 10 Nov 2011 09:00:13 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Working Group last call for adding RFC6437 Flow Label support to Node Requirements bis document
From: Bob Hinden <bob.hinden@gmail.com>
Date: Thu, 10 Nov 2011 09:00:10 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.com>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
To: 6man Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>, 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: Thu, 10 Nov 2011 17:00:18 -0000

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
> --------------------------------------------------------------------