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

Hi Jan,

Sorry for late response. Thanks a lot for your following information.

Could you or anybody else provide me some protocol specification for the pfsync?

Xiaohu

> -----邮件原件-----
> 发件人: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] 代表 Jan
> Melen
> 发送时间: 2009年11月15日 22:38
> 收件人: <mohamed.boucadair@orange-ftgroup.com>
> 抄送: behave@ietf.org
> 主题: 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