Re: [BEHAVE] draft-xu-behave-nat-state-sync-00

Dean Cheng <Chengd@huawei.com> Mon, 23 November 2009 19:19 UTC

Return-Path: <Chengd@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 5C1213A69EA for <behave@core3.amsl.com>; Mon, 23 Nov 2009 11:19:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 KHhd17XPUkm8 for <behave@core3.amsl.com>; Mon, 23 Nov 2009 11:19:43 -0800 (PST)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 3F00B3A69E9 for <behave@ietf.org>; Mon, 23 Nov 2009 11:19:43 -0800 (PST)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KTK00B3GTOQ1M@usaga04-in.huawei.com> for behave@ietf.org; Mon, 23 Nov 2009 13:19:38 -0600 (CST)
Received: from DeanChengSC ([10.193.34.162]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KTK00BXOTOMRC@usaga04-in.huawei.com> for behave@ietf.org; Mon, 23 Nov 2009 13:19:38 -0600 (CST)
Date: Mon, 23 Nov 2009 11:19:34 -0800
From: Dean Cheng <Chengd@huawei.com>
In-reply-to: <42867872-BDDE-42BA-ABF9-4953CEC92B9C@nomadiclab.com>
To: 'Jan Melen' <jan.melen@nomadiclab.com>, mohamed.boucadair@orange-ftgroup.com
Message-id: <993A3A4FF0FC43A5ACC2846F61546B47@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: quoted-printable
Thread-index: AcpmAg5WgN1jvmXqTCu+F4FHeO8JSAGb3NIw
References: <4AFCBC87.20009@gmail.com> <21422_1258094445_4AFCFF6D_21422_40641_1_94C682931C08B048B7A8645303FDC9F307914E625D@PUEXCB1B.nanterre.francetelecom.fr> <42867872-BDDE-42BA-ABF9-4953CEC92B9C@nomadiclab.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] draft-xu-behave-nat-state-sync-00
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: Mon, 23 Nov 2009 19:19:51 -0000

Hi Jan,

Do you know whether there exists a protocol specification
for pfsync somewhere so we can take a look?

Thanks
Dean

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of
> Jan Melen
> Sent: Sunday, November 15, 2009 6:38 AM
> To: <mohamed.boucadair@orange-ftgroup.com>
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] draft-xu-behave-nat-state-sync-00
> 
> Hi all,
> 
> If we are planning to standardize something should we also take a look
> at existing open source solutions that are not based on SCSP such as
> OpenBSD pfsync
> http://www.openbsd.org/cgi-bin/man.cgi?query=pfsync&sektion=4
>    which is used pretty widely at least in the BSD community for nat(/
> fw) state synchronization?
> 
>    Regards,
>      Jan
> 
> On Nov 13, 2009, at 8:40 AM, <mohamed.boucadair@orange-ftgroup.com>
> <mohamed.boucadair@orange-ftgroup.com
>  > wrote:
> 
> >
> > Dear all,
> >
> > I guess that the question should be asked priori to yours:
> >
> > Do we let vendors define their proprietary solutions or does the
> > IETF define a solution based on standardised protocols to achieve
> > reliable state synchronisation?
> >
> > From a service provider perspective, I'd like to see a solution with
> > IETF stamp so as to be included in our RFPs/analysis. Vendors are
> > then free to propose more reliable solutions, if any, compared to
> > the one standardised by IETF.
> >
> > Cheers,
> > Med
> >
> >
> > -----Message d'origine-----
> > De : behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la
> > part de Brian E Carpenter
> > Envoyé : vendredi 13 novembre 2009 02:55
> > À : behave@ietf.org
> > Objet : [BEHAVE] draft-xu-behave-nat-state-sync-00
> >
> > My question about this draft is whether there is available code and
> > implementation experience with SCSP, which was defined in 1998.
> >
> > If there isn't code and experience, since it is a quite complex
> > design, I would be a bit worried.
> >
> > On the other hand, I believe that something of the complexity of
> > SCSP is absolutely required to provide reliable synchronisation.
> > There is no simple, lightweight way to do this reliably.
> >
> >   Brian
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> >
> > *********************************
> > This message and any attachments (the "message") are confidential
> > and intended solely for the addressees.
> > Any unauthorised use or dissemination is prohibited.
> > Messages are susceptible to alteration.
> > France Telecom Group shall not be liable for the message if altered,
> > changed or falsified.
> > If you are not the intended addressee of this message, please cancel
> > it immediately and inform the sender.
> > ********************************
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave