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

Kevin Glavin <Kevin.Glavin@riverbed.com> Tue, 26 August 2014 18:46 UTC

Return-Path: <Kevin.Glavin@riverbed.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 3F0271A0089 for <sfc@ietfa.amsl.com>; Tue, 26 Aug 2014 11:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level:
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.668, 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 Y5Kgb07bLuwK for <sfc@ietfa.amsl.com>; Tue, 26 Aug 2014 11:46:29 -0700 (PDT)
Received: from smtp1.riverbed.com (incomingmail.riverbed.com [208.70.196.45]) by ietfa.amsl.com (Postfix) with ESMTP id B02F71A0079 for <sfc@ietf.org>; Tue, 26 Aug 2014 11:46:29 -0700 (PDT)
Received: from unknown (HELO 365EXCH-HUB-P3.nbttech.com) ([10.16.4.1]) by smtp1.riverbed.com with ESMTP; 26 Aug 2014 11:46:29 -0700
Received: from SFO1EXC-MBXP14.nbttech.com ([fe80::48a3:fcd6:284c:af72]) by 365EXCH-HUB-P3.nbttech.com ([::1]) with mapi id 14.03.0195.001; Tue, 26 Aug 2014 11:46:29 -0700
From: Kevin Glavin <Kevin.Glavin@riverbed.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] Call for WG adoption of draft-merged-sfc-architecture-02
Thread-Index: AQHPwV4LrKFwlbPq2EakRGFWvH7bzw==
Date: Tue, 26 Aug 2014 18:46:28 +0000
Message-ID: <D02223D2.2B7AA%kevin.glavin@riverbed.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.16.205.250]
Content-Type: multipart/alternative; boundary="_000_D02223D22B7AAkevinglavinriverbedcom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/vrHtmVAjX5flbukQm6yb4DMbGj4
Cc: "Jim Guichard (jguichar)" <jguichar@cisco.com>
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 18:46:33 -0000

I support the adoption of this version of merged architecture.

Kevin


From: "Jim Guichard (jguichar)" <jguichar@cisco.com<mailto:jguichar@cisco.com>>
Date: Tuesday, August 26, 2014 4:40 AM
To: "sfc@ietf.org<mailto:sfc@ietf.org>" <sfc@ietf.org<mailto: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.