Re: [BEHAVE] Whether or not need to distinguish the primary and the backup NAT boxes?

xuxiaohu 41208 <xuxh@huawei.com> Fri, 26 March 2010 09:30 UTC

Return-Path: <xuxh@huawei.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BEB383A69A0 for <behave@core3.amsl.com>; Fri, 26 Mar 2010 02:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.5
X-Spam-Level: ****
X-Spam-Status: No, score=4.5 tagged_above=-999 required=5 tests=[AWL=-1.524, BAYES_50=0.001, CN_BODY_35=0.339, DNS_FROM_OPENWHOIS=1.13, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y9YrtTQw9PeT for <behave@core3.amsl.com>; Fri, 26 Mar 2010 02:30:06 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 98F093A676A for <behave@ietf.org>; Fri, 26 Mar 2010 02:30:06 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZV00N7TUEJ54@szxga03-in.huawei.com> for behave@ietf.org; Fri, 26 Mar 2010 17:30:19 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KZV00H9BUEJWT@szxga03-in.huawei.com> for behave@ietf.org; Fri, 26 Mar 2010 17:30:19 +0800 (CST)
Received: from [172.24.1.6] (Forwarded-For: [130.129.26.82]) by szxmc04-in.huawei.com (mshttpd); Fri, 26 Mar 2010 02:30:19 -0700
Date: Fri, 26 Mar 2010 02:30:19 -0700
From: xuxiaohu 41208 <xuxh@huawei.com>
In-reply-to: <20100326.173947.112558575.miyakawa@nttv6.jp>
To: Shin Miyakawa <miyakawa@nttv6.jp>
Message-id: <fdcfed4452b1.52b1fdcfed44@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug 8 2006)
Content-type: text/plain; charset="gb2312"
Content-language: zh-CN
Content-transfer-encoding: quoted-printable
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
References: <fe6da9184f48.4f48fe6da918@huawei.com> <20100326.074608.71140248.miyakawa@nttv6.jp> <fe8ceafa3104.3104fe8ceafa@huawei.com> <20100326.173947.112558575.miyakawa@nttv6.jp>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Whether or not need to distinguish the primary and the backup NAT boxes?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 09:30:07 -0000

Hi Shin,

----- 原邮件 -----
发件人: Shin Miyakawa <miyakawa@nttv6.jp>
日期: 星期五, 三月 26日, 2010 上午1:40
主题: Re: [BEHAVE] Whether or not need to distinguish the primary and the backup NAT boxes?
收件人: xuxh@huawei.com
抄送: behave@ietf.org

> Xuxiaohu,
> 
> > Yes, the administrators can use them in that way. However, IMHO, 
> it is still better to assure the traffic of a given session 
> traverse the identical NAT box in normal case.
> 
> Usually one ISP network is big enough to have mutiple EBGP routers 
> to have
> redundancy, then, packets go through a box A and their responses
> return through the box B other than A.

Symmetric path usage is beneficial in some cases, e.g., traffic monitoring.

> So that's the reason why I said at the mic that it depends on the 
> network design.
> 
> Also, I think that "Cold Stand-by" means that the stand-by box is 
> just 
> "sleeping" usually. Even if you think "normal case" is for small 

No, the standby box is not sleeping, you can deploy redundancy and load-balancing together, just like what VRRP does for multiple VRRP groups. For more details, please see the load-balancing section of draft-xu-behave-stateful-nat-standby.

BR,
Xiaohu

> size of 
> Enterprise or so, it sounds like waste of investiment.
> We should be noticed that "running parallelly" often means "load 
> balancing" too.


 
> Best wishes,
> 
> Shin Miyakawa
>