[BEHAVE] Comments on draft-chen-behave-rsnat-01
Dave Thaler <dthaler@microsoft.com> Thu, 23 July 2009 01:26 UTC
Return-Path: <dthaler@microsoft.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 73EAC3A6C94 for <behave@core3.amsl.com>; Wed, 22 Jul 2009 18:26:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.079
X-Spam-Level:
X-Spam-Status: No, score=-10.079 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 IIYniOllRWoH for <behave@core3.amsl.com>; Wed, 22 Jul 2009 18:26:13 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id A387E3A6C8D for <behave@ietf.org>; Wed, 22 Jul 2009 18:26:13 -0700 (PDT)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.99.4; Wed, 22 Jul 2009 18:23:55 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) with Microsoft SMTP Server id 14.0.621.7; Wed, 22 Jul 2009 18:23:55 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.210]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Wed, 22 Jul 2009 18:23:54 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: "phdgang@gmail.com" <phdgang@gmail.com>, "denghui02@gmail.com" <denghui02@gmail.com>, "zhouboyj@chinamobile.com" <zhouboyj@chinamobile.com>, "xmw@csnet1.cs.tsinghua.edu.cn" <xmw@csnet1.cs.tsinghua.edu.cn>, "songlinjian@csnet1.cs.tsinghua.edu.cn" <songlinjian@csnet1.cs.tsinghua.edu.cn>, "cuiyong@tsinghua.edu.cn" <cuiyong@tsinghua.edu.cn>
Thread-Topic: [BEHAVE] Comments on draft-chen-behave-rsnat-01
Thread-Index: AQHKCzQ+FS7iBkzQ/UuOi2QiEaylOg==
Date: Thu, 23 Jul 2009 01:23:50 +0000
Message-ID: <E4561B14EE2A3E4E9D478EBFB5416E1B134874@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B126E28@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B126E28@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Behave WG <behave@ietf.org>
Subject: [BEHAVE] Comments on draft-chen-behave-rsnat-01
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: Thu, 23 Jul 2009 01:26:14 -0000
This draft seems to be tackling the same problem as draft-xu-behave-stateful-nat-standby-00 except using slightly different protocols. Terminology Chen et al. Xu ------------ -------- User Network internal realm Service Network external realm Protocols Function Chen et al. Xu --------------------- -------------- ------------------- Liveness detection BGP KEEPALIVE VRRP over VPLS State synchronization new BGP option SCSP Routing preferences BGP priority More/less specifics I also have a bunch of editorial-only comments which I will send directly to the authors. -Dave > -----Original Message----- > From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On > Behalf Of Dave Thaler > Sent: Tuesday, July 21, 2009 7:28 PM > To: xuxh@huawei.com > Cc: Behave WG > Subject: [BEHAVE] Comments on draft-xu-behave-stateful-nat-standby-00 > > This document is now much more clear than > draft-xu-behave-lsn-standby-00 was, thanks! > > I mostly just have some more editorial nits, which I > will send directly to you. I only have one technical comment... > > Section 4.2 states: > > > To preserve the established sessions during the failover, in > > addition to keeping the internal addresses for the external hosts > > unchanged, the external addresses for the internal hosts should also > > keep unchanged. How to meet the first requirement will not be > > reiterated since it is the same as that for the cold standby > > mechanism. To meet the second requirement, NAT routers in a > > redundancy group should be configured with an identical external > > address pool and they should assign the same external address for > > the same internal host. > > It's not just the same address that a stateful NAT has to assign, > it also has to assign the same external port. So the state > synchronization protocol also has to exchange port mapping > information. In Section 7 you suggest using SCSP (RFC 2334), which > would require you to specify the record format (see section B.2.2) > which would need to include both addresses and ports, and perhaps > other information as well. > > -Dave > _______________________________________________ > Behave mailing list > Behave@ietf.org > https://www.ietf.org/mailman/listinfo/behave