IETF Logo Mail Archive

Re: [sfc] Call for WG adoption of draft-merged-sfc-architecture-02

Sharon <sbarkai@gmail.com> Wed, 27 August 2014 02:22 UTC

Return-Path: <sbarkai@gmail.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CE931A0376 for <sfc@ietfa.amsl.com>; Tue, 26 Aug 2014 19:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BbYsha_ALije for <sfc@ietfa.amsl.com>; Tue, 26 Aug 2014 19:22:48 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D6A81A0363 for <sfc@ietf.org>; Tue, 26 Aug 2014 19:22:48 -0700 (PDT)
Received: by mail-qg0-f43.google.com with SMTP id a108so15635349qge.16 for <sfc@ietf.org>; Tue, 26 Aug 2014 19:22:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=b5NFDZ3Lguyw4/qn68c8FSYz7awfWJsyRYuFsqBShvY=; b=vWAeoDxSRL9Y8ixiPnpQYBVUMSiFXXqF52STapyET43JYUsGBescIm93lrd1vnFd/1 Jz+YBLrfzYY2y2EF0x46mU72FnY/wqHeOzpq1JLLCJD5mmYr6iwq/mZdb/bxpXHK8ajt z88TPx2l2EcgJ1WmtMVA7dYyWiBJ0VoOzb/v2tB4ir8Mh1qe7ZBZ6q6g9WwpmUh9F9jf 0wa46AHTWOqoa+2FjtE/b8nwGBH6BO14QMx5M7xESciORCu1Wd1Ynvg3FmidLOvEQRuc ciNgurEKvS8p/vsmjRVxnGbT8WoHuTr9Hx/rU//ZQm69m/lQHDYBn2RGPXinTatJkUBG pecg==
X-Received: by 10.229.84.133 with SMTP id j5mr51806672qcl.14.1409106167614; Tue, 26 Aug 2014 19:22:47 -0700 (PDT)
Received: from [192.168.1.102] (108-214-96-27.lightspeed.sntcca.sbcglobal.net. [108.214.96.27]) by mx.google.com with ESMTPSA id v1sm15154846qat.17.2014.08.26.19.22.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Aug 2014 19:22:47 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-CA93392C-524D-4E63-B3D5-3E1C572306A3"
Mime-Version: 1.0 (1.0)
From: Sharon <sbarkai@gmail.com>
X-Mailer: iPhone Mail (11D257)
In-Reply-To: <D021EA69.33AE5%jguichar@cisco.com>
Date: Tue, 26 Aug 2014 19:22:45 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <308400DD-B6EA-46AE-ACFD-6F9A60702D6C@gmail.com>
References: <D021EA69.33AE5%jguichar@cisco.com>
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/eejq8PddOQq2LurtEcYJq9zm8gM
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] Call for WG adoption of draft-merged-sfc-architecture-02
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Aug 2014 02:22:50 -0000

Support 

--szb

> On Aug 26, 2014, at 4:40 AM, "Jim Guichard (jguichar)" <jguichar@cisco.com> wrote:
> 
> Greetings WG:
> 
> This message begins a two week call for WG adoption of draft-merged-sfc-architecture-02 [http://datatracker.ietf.org/doc/draft-merged-sfc-architecture/] ending September 9th 2014.
> 
> Please respond to the SFC mailing list with any statements of approval or disapproval.
> 
> As always, please note:
> This is not WG Last Call. The document is not final, and the WG is expected to modify the document’s content until there is WG consensus that the content is solid. Therefore, please don’t oppose adoption just because you want to see changes to its content.
> If you have objections to adoption of the document, please state your reasons why, and explain what it would take to address your concerns.
> If you have issues with the content, by all means raise those issues and we can begin a dialog about how best to address them.
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc

v2.23.0 | Report a Bug | By Email