Re: [Int-area] Call for adoption of draft-carpenter-flow-label-balancing-02
joel jaeggli <joelja@bogus.com> Fri, 21 December 2012 02:38 UTC
Return-Path: <joelja@bogus.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B072A21F888F for <int-area@ietfa.amsl.com>; Thu, 20 Dec 2012 18:38:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 OJTTPuGOUI9g for <int-area@ietfa.amsl.com>; Thu, 20 Dec 2012 18:38:35 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id D2F8C21F884B for <int-area@ietf.org>; Thu, 20 Dec 2012 18:38:35 -0800 (PST)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qBL2bbdn080645 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 21 Dec 2012 02:37:38 GMT (envelope-from joelja@bogus.com)
Message-ID: <50D3CB6C.9040708@bogus.com>
Date: Thu, 20 Dec 2012 18:37:32 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:18.0) Gecko/20121128 Thunderbird/18.0
MIME-Version: 1.0
To: "Liubing (Leo)" <leo.liubing@huawei.com>
References: <50D0657B.8090302@ericsson.com> <8AE0F17B87264D4CAC7DE0AA6C406F453CCFF776@szxeml509-mbx>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453CCFF776@szxeml509-mbx>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 21 Dec 2012 02:37:38 +0000 (UTC)
Cc: Julien Laganier <julien.ietf@gmail.com>, Internet Area <int-area@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Int-area] Call for adoption of draft-carpenter-flow-label-balancing-02
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 02:38:36 -0000
On 12/20/12 5:38 PM, Liubing (Leo) wrote: > I'm in favor of it. It's a good use case of flow label for L3/4 load balancing RFC 6437 did not go nearly far enough in my opinion make the flow label suitable for this application. The fact of the matter is if I attempted to use the flow label today as part of a load balancing scheme it would provide zero additional entropy, and what's more I still have to look at the upper layer header. Furthermore the document proposes the use of flow label across muliple flows as a common "session key" across multiple flows which I personally feel is inconsistent with the notion of a flow, is certainly embedding upper layer (notionally above the l4 header) session information in the layer-3 header and suffers from the exposures described in section 6 of 6437 and making no attempt to ameliorate them. > Thanks > > B.R. > Bing > >> -----Original Message----- >> From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On >> Behalf Of Suresh Krishnan >> Sent: Tuesday, December 18, 2012 8:46 PM >> To: Internet Area >> Cc: Julien Laganier; Ralph Droms >> Subject: [Int-area] Call for adoption of >> draft-carpenter-flow-label-balancing-02 >> >> Hi all, >> This draft has been presented at intarea face to face meetings and has >> received a bit of discussion. It has been difficult to gauge whether the >> wg is interested in this work or not. This call is being initiated to >> determine whether there is WG consensus towards adoption of >> draft-carpenter-flow-label-balancing-02 as an intarea WG draft. Please >> state whether or not you're in favor of the adoption by replying to this >> email. If you are not in favor, please also state your objections in >> your response. This adoption call will complete on 2013-01-04. >> >> Regards >> Suresh & Julien >> >> >> _______________________________________________ >> Int-area mailing list >> Int-area@ietf.org >> https://www.ietf.org/mailman/listinfo/int-area > _______________________________________________ > Int-area mailing list > Int-area@ietf.org > https://www.ietf.org/mailman/listinfo/int-area >
- [Int-area] Call for adoption of draft-carpenter-f… Suresh Krishnan
- Re: [Int-area] Call for adoption of draft-carpent… George, Wes
- Re: [Int-area] Call for adoption of draft-carpent… Liubing (Leo)
- Re: [Int-area] Call for adoption of draft-carpent… joel jaeggli
- Re: [Int-area] Call for adoption of draft-carpent… Brian E Carpenter
- Re: [Int-area] Call for adoption of draft-carpent… Warren Kumari
- [Int-area] Call for adoption of draft-carpenter-f… Qiong
- Re: [Int-area] Call for adoption of draft-carpent… Yao
- Re: [Int-area] Call for adoption of draft-carpent… Bob Hinden
- Re: [Int-area] Call for adoption of draft-carpent… Hosnieh Rafiee
- Re: [Int-area] Call for adoption of draft-carpent… Diego R. Lopez
- Re: [Int-area] Call for adoption of draft-carpent… Linda Dunbar