IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 13 November 2009 04:12 UTC

Return-Path: <brian.e.carpenter@gmail.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 33E313A682A for <behave@core3.amsl.com>; Thu, 12 Nov 2009 20:12:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level:
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[AWL=0.105, 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 4TnjbfsmR7Fe for <behave@core3.amsl.com>; Thu, 12 Nov 2009 20:12:37 -0800 (PST)
Received: from mail-gx0-f228.google.com (mail-gx0-f228.google.com [209.85.217.228]) by core3.amsl.com (Postfix) with ESMTP id D0C783A67F3 for <behave@ietf.org>; Thu, 12 Nov 2009 20:12:36 -0800 (PST)
Received: by gxk28 with SMTP id 28so910816gxk.9 for <behave@ietf.org>; Thu, 12 Nov 2009 20:13:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=odX9gTTHIbPM6h6ugEZmdabQlIRF0WLhPMyu449lViw=; b=NyAQuDgEprBFFcPke1G/E+5h9+6i+efqdOUrr2mg2F4mhETlYEMICML9mwTjfLsuBX Ge8wDz/rT8G126KlhXe8kKvsYWMuTqpNnHjWDYgKhGWERu8BxkJ6eCw+eUCROwiKI7xp vArGwqwgoWSwubFNe86tz9/+DZdoETtX/sP/Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=xOPZmMzALP6UV5nyrA+01orbi3SJrxaP7pW/0EOXz4q8mN3n1wbRpeFfW+ELo6a5vt xhFjc/cyu3M7iClIbdtp/G2nUmRmQEsqlDGXIECvtZjNI2ySj0NVpmts2ugC6dCUKxjA N4jWTukGNimZyRqDFH3DRBTqQWk/X3X0KCD34=
Received: by 10.151.16.24 with SMTP id t24mr6828144ybi.151.1258085573030; Thu, 12 Nov 2009 20:12:53 -0800 (PST)
Received: from ?133.93.16.203? (host-16-203.meeting.ietf.org [133.93.16.203]) by mx.google.com with ESMTPS id 15sm1630475gxk.4.2009.11.12.20.12.51 (version=SSLv3 cipher=RC4-MD5); Thu, 12 Nov 2009 20:12:52 -0800 (PST)
Message-ID: <4AFCDCBD.8090403@gmail.com>
Date: Fri, 13 Nov 2009 17:12:45 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
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="UTF-8"
Content-Transfer-Encoding: 7bit
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 04:12:39 -0000

It seems there was SCSP code in BSD some years ago, as part of the
ATM support:

http://www.freebsd.org/releases/3.0R/notes.html

Also for Linux, it seems to be tied to ATM:

http://www.digipedia.pl/man/doc/view/scspd.8.html

I also found an MSc thesis discussing SCSP in SunOS 5.6.

Regards
   Brian

On 2009-11-13 15:25, Dean Cheng wrote:
> 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.
> 
> 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
> 
>

v2.23.0 | Report a Bug | By Email