IETF Logo Mail Archive

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

Ron Parker <Ron_Parker@affirmednetworks.com> Tue, 26 August 2014 21:56 UTC

Return-Path: <Ron_Parker@affirmednetworks.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 201401A0115 for <sfc@ietfa.amsl.com>; Tue, 26 Aug 2014 14:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 NkOZQWvwWt8R for <sfc@ietfa.amsl.com>; Tue, 26 Aug 2014 14:56:48 -0700 (PDT)
Received: from relay.emg-ca-1.securemail.intermedia.net (relay.emg-ca-1.securemail.intermedia.net [64.78.56.32]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 737841A00E1 for <sfc@ietf.org>; Tue, 26 Aug 2014 14:56:48 -0700 (PDT)
Received: from emg-ca-1-2 (localhost [127.0.0.1]) by emg-ca-1-2.localdomain (Postfix) with ESMTP id D898D53E64; Tue, 26 Aug 2014 14:55:28 -0700 (PDT)
MIME-Version: 1.0
x-echoworx-emg-received: Tue, 26 Aug 2014 14:55:28.863 -0700
x-echoworx-msg-id: 4813615a-7e2d-4b49-a4a9-ff1c49691680
x-echoworx-action: delivered
Received: from localhost ([127.0.0.1]) by emg-ca-1-2 (JAMES SMTP Server 2.3.2) with SMTP ID 223; Tue, 26 Aug 2014 14:55:28 -0700 (PDT)
Received: from HUB021-CA-6.exch021.domain.local (unknown [10.254.4.92]) by emg-ca-1-2.localdomain (Postfix) with ESMTP id BC3BB53E64; Tue, 26 Aug 2014 14:55:28 -0700 (PDT)
Received: from MBX021-W3-CA-2.exch021.domain.local ([10.254.4.78]) by HUB021-CA-6.exch021.domain.local ([10.254.4.92]) with mapi id 14.03.0174.001; Tue, 26 Aug 2014 14:56:47 -0700
From: Ron Parker <Ron_Parker@affirmednetworks.com>
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Call for WG adoption of draft-merged-sfc-architecture-02
Thread-Index: AQHPwSKarKFwlbPq2EakRGFWvH7bz5vjbuRg
Date: Tue, 26 Aug 2014 21:56:47 +0000
Message-ID: <CDF2F015F4429F458815ED2A6C2B6B0B1A90A9BA@MBX021-W3-CA-2.exch021.domain.local>
References: <D021EA69.33AE5%jguichar@cisco.com>
In-Reply-To: <D021EA69.33AE5%jguichar@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [50.203.66.100]
x-source-routing-agent: Processed
Content-Type: multipart/alternative; boundary="_000_CDF2F015F4429F458815ED2A6C2B6B0B1A90A9BAMBX021W3CA2exch_"
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/zc11XR1LmQGI1oOc__y3Jac3Rsk
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: Tue, 26 Aug 2014 21:56:50 -0000

Support.

   Ron

From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Jim Guichard (jguichar)
Sent: Tuesday, August 26, 2014 7:41 AM
To: sfc@ietf.org
Subject: [sfc] Call for WG adoption of draft-merged-sfc-architecture-02

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:

  1.  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.
  2.  If you have objections to adoption of the document, please state your reasons why, and explain what it would take to address your concerns.
  3.  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.

v2.23.0 | Report a Bug | By Email