IETF Logo Mail Archive

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

<mohamed.boucadair@orange-ftgroup.com> Fri, 13 November 2009 06:40 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.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 937033A68F1 for <behave@core3.amsl.com>; Thu, 12 Nov 2009 22:40:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.13
X-Spam-Level:
X-Spam-Status: No, score=-2.13 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 WIH7RETyqC5z for <behave@core3.amsl.com>; Thu, 12 Nov 2009 22:40:17 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by core3.amsl.com (Postfix) with ESMTP id 8DE833A697E for <behave@ietf.org>; Thu, 12 Nov 2009 22:40:15 -0800 (PST)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id 232183B4291; Fri, 13 Nov 2009 07:40:45 +0100 (CET)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id 0D73218004D; Fri, 13 Nov 2009 07:40:45 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Fri, 13 Nov 2009 07:40:45 +0100
From: mohamed.boucadair@orange-ftgroup.com
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "behave@ietf.org" <behave@ietf.org>
Date: Fri, 13 Nov 2009 07:40:44 +0100
Thread-Topic: [BEHAVE] draft-xu-behave-nat-state-sync-00
Thread-Index: AcpkBGV5WQWd75kNQhedwrf/iaLaiwAJkStA
Message-ID: <21422_1258094445_4AFCFF6D_21422_40641_1_94C682931C08B048B7A8645303FDC9F307914E625D@PUEXCB1B.nanterre.francetelecom.fr>
References: <4AFCBC87.20009@gmail.com>
In-Reply-To: <4AFCBC87.20009@gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2009.11.13.45124
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 06:40:19 -0000

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

v2.23.0 | Report a Bug | By Email