IETF Logo Mail Archive

Re: [BEHAVE] proprietary implementation v.s standardised protocols//re: draft-xu-behave-nat-state-sync-00

Christian Huitema <huitema@microsoft.com> Fri, 27 November 2009 03:32 UTC

Return-Path: <huitema@microsoft.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 5CD8D3A67C1 for <behave@core3.amsl.com>; Thu, 26 Nov 2009 19:32:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 l4N2BlGhjxa3 for <behave@core3.amsl.com>; Thu, 26 Nov 2009 19:32:02 -0800 (PST)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id B2DC93A63D3 for <behave@ietf.org>; Thu, 26 Nov 2009 19:32:02 -0800 (PST)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 26 Nov 2009 19:32:21 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.0.639.20; Thu, 26 Nov 2009 19:31:56 -0800
Received: from TK5EX14MBXW652.wingroup.windeploy.ntdev.microsoft.com ([169.254.2.203]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Thu, 26 Nov 2009 19:31:56 -0800
From: Christian Huitema <huitema@microsoft.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>, "Joel M. Halpern" <jmh@joelhalpern.com>
Thread-Topic: [BEHAVE] proprietary implementation v.s standardised protocols//re: draft-xu-behave-nat-state-sync-00
Thread-Index: AQHKbjs9CvO333pib0GTWk+Eqsnlf5FIgZsAgAAC9gCAAAT1gIAAvZGA
Date: Fri, 27 Nov 2009 03:31:21 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA211EDA5F@TK5EX14MBXW652.wingroup.windeploy.ntdev.microsoft.com>
References: <004301ca6e3b$304eb1f0$d40c6f0a@china.huawei.com> <4B0E315A.1070104@it.uc3m.es> <4B0E33D6.8090902@joelhalpern.com> <4B0E37FF.4050103@it.uc3m.es>
In-Reply-To: <4B0E37FF.4050103@it.uc3m.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] proprietary implementation v.s standardised protocols//re: 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, 27 Nov 2009 03:32:03 -0000

> The reason for doing that is that as you mention, there is a vlaue in 
> allowing multiple boxes from multiple vendors to be used in synch i.e. 
> interoperability.

And the way to resolve that is to make sure that there are at least two vendors interested in developing a standard solution before starting the work. Clearly, Huawei is interested. Is there another major vendor on board?

-- Christian Huitema

v2.8.7 | Report a Bug | By Email