IETF Logo Mail Archive

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

marcelo bagnulo braun <marcelo@it.uc3m.es> Fri, 13 November 2009 02:28 UTC

Return-Path: <marcelo@it.uc3m.es>
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 C4EBC28C172 for <behave@core3.amsl.com>; Thu, 12 Nov 2009 18:28:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.492
X-Spam-Level:
X-Spam-Status: No, score=-6.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ik5M4QQkkpDs for <behave@core3.amsl.com>; Thu, 12 Nov 2009 18:28:15 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id C34E228C15A for <behave@ietf.org>; Thu, 12 Nov 2009 18:28:15 -0800 (PST)
Received: from host-17-49.meeting.ietf.org (host-17-49.meeting.ietf.org [133.93.17.49]) by smtp03.uc3m.es (Postfix) with ESMTP id BF5FB81BA; Fri, 13 Nov 2009 03:28:41 +0100 (CET)
Message-ID: <4AFCC458.9040603@it.uc3m.es>
Date: Fri, 13 Nov 2009 03:28:40 +0100
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Dean Cheng <Chengd@huawei.com>
References: <4AFCBC87.20009@gmail.com> <C1463B96FBAB4A59B7B279C43BDCE778@china.huawei.com>
In-Reply-To: <C1463B96FBAB4A59B7B279C43BDCE778@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.0.0.1038-17004.003
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:28:16 -0000

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?

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
>
>

v2.8.7 | Report a Bug | By Email