IETF Logo Mail Archive

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

Dean Cheng <Chengd@huawei.com> Fri, 13 November 2009 02:52 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 937973A68D6 for <behave@core3.amsl.com>; Thu, 12 Nov 2009 18:52:09 -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 G-IrG6dECg6C for <behave@core3.amsl.com>; Thu, 12 Nov 2009 18:52:08 -0800 (PST)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id CCF573A6984 for <behave@ietf.org>; Thu, 12 Nov 2009 18:52:08 -0800 (PST)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KT100K0W1BPX1@usaga03-in.huawei.com> for behave@ietf.org; Thu, 12 Nov 2009 20:52:38 -0600 (CST)
Received: from DeanChengSC (host-128-154.meeting.ietf.org [133.93.128.154]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KT100L671BN2Q@usaga03-in.huawei.com> for behave@ietf.org; Thu, 12 Nov 2009 20:52:37 -0600 (CST)
Date: Thu, 12 Nov 2009 18:52:31 -0800
From: Dean Cheng <Chengd@huawei.com>
In-reply-to: <4AFCC458.9040603@it.uc3m.es>
To: 'marcelo bagnulo braun' <marcelo@it.uc3m.es>
Message-id: <AD50D1D768684036949610716E34FCFA@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: AcpkCT3uWZ5idpJ3RjmUfc2a3M/b2QAAt+GA
References: <4AFCBC87.20009@gmail.com> <C1463B96FBAB4A59B7B279C43BDCE778@china.huawei.com> <4AFCC458.9040603@it.uc3m.es>
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: Fri, 13 Nov 2009 02:52:09 -0000

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of
> marcelo bagnulo braun
> Sent: Thursday, November 12, 2009 6:29 PM
> To: Dean Cheng
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] draft-xu-behave-nat-state-sync-00
> 
> Dean Cheng escribió:
> > Brian,
> >
> >
> >> -----Original Message-----
> >> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
Behalf
> >>
> > Of
> >
> >> Brian E Carpenter
> >> Sent: Thursday, November 12, 2009 5:55 PM
> >> To: behave@ietf.org
> >> Subject: [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.
> >>
> >
> > I don't know personally whether there is any available code, but
> > RFC2335 and RFC2443 documented two separate applications using SCSP,
> > although also about 10 years ago.
> >
> 
> Right and the question is: are there any implementations of the SCSP
> protocol?
> 

I don’t know any at this time.

Dean 

> Regards, marcelo
> 
> > However, SCSP (as mentioned in my presentation) itself heavily
> > "borrowed" link-state based algorithm and mechanisms from OSPF/ISIS
> > (also defined in 90's or earlier) that have been widely deployed since.
> >
> >
> >> 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.
> >>
> >
> > Totally agreed.
> >
> > Dean
> >
> >
> >>     Brian
> >>
> >> _______________________________________________
> >> 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
> >
> >
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

v2.23.0 | Report a Bug | By Email