IETF Logo Mail Archive

Re: RFC 6437 on IPv6 Flow Label Specification

Bob Hinden <bob.hinden@gmail.com> Wed, 02 November 2011 14:10 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 A31D811E80D8 for <ipv6@ietfa.amsl.com>; Wed, 2 Nov 2011 07:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level:
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=1.027, 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 J+FrdXP-+-Ji for <ipv6@ietfa.amsl.com>; Wed, 2 Nov 2011 07:10:50 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E470211E80CA for <ipv6@ietf.org>; Wed, 2 Nov 2011 07:10:49 -0700 (PDT)
Received: by vws5 with SMTP id 5so205541vws.31 for <ipv6@ietf.org>; Wed, 02 Nov 2011 07:10:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=/3ouEx0bBQSd+ridIqkOkOsySkpoPHo3vAkHJX29DxY=; b=D5YmUkU9wi8MgMAyX2+uu+3F8+2SeF3FjEdXVA4aloXufb18OBmm9uo6Q3LJwoR7W1 yMa7cdoCBdij7wid1zU24VlRA+wvvFU682DUZVpTlwZS6BofdOUNkJsES54L/mwTUJt2 tPZm/DWlsmRyU1CbkTIDIXKmuT+OKAKvVRrds=
Received: by 10.68.72.33 with SMTP id a1mr5133725pbv.44.1320243041400; Wed, 02 Nov 2011 07:10:41 -0700 (PDT)
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 a4sm813719pbd.7.2011.11.02.07.10.39 (version=SSLv3 cipher=OTHER); Wed, 02 Nov 2011 07:10:40 -0700 (PDT)
Subject: Re: RFC 6437 on IPv6 Flow Label Specification
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4EB0A4D3.1070002@gmail.com>
Date: Wed, 02 Nov 2011 07:10:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <22A8860A-1055-483C-83C3-93556A75DDA8@gmail.com>
References: <4EB0A4D3.1070002@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: 6man <ipv6@ietf.org>, Bob Hinden <bob.hinden@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: Wed, 02 Nov 2011 14:10:50 -0000

Brian,

I agree this is a good idea.  <draft-ietf-6man-node-req-bis-11.txt> is recently entered AUTH48 so this may be possible.  I doubt we are going to update node-requirements again for a while, so it would be good to do it now.

The first step is to see if anyone on the list disagrees with this approach.  Comments?

I have asked the authors to propose text to the ipv6 list.

Bob

On Nov 1, 2011, at 7:02 PM, Brian E Carpenter wrote:

> Hi,
> 
> The new flow label proposed standard is here, as well as
> the rationale document (RFC 6436) and the ECMP/LAG proposed
> standard (RFC 6438).
> 
> This document formally updates RFC 2460 and says that every IPv6
> source SHOULD set the flow label value accordingly.
> 
> Maybe we can include this in draft-ietf-6man-node-req-ter when
> it comes.
> 
>   Brian
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email