IETF Logo Mail Archive

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

"mikebianc@aol.com" <mikebianc@aol.com> Tue, 16 September 2014 21:49 UTC

Return-Path: <mikebianc@aol.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 9FEF41A6F0E for <sfc@ietfa.amsl.com>; Tue, 16 Sep 2014 14:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.13
X-Spam-Level:
X-Spam-Status: No, score=0.13 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652, 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 XfgNa5JFrn0x for <sfc@ietfa.amsl.com>; Tue, 16 Sep 2014 14:49:35 -0700 (PDT)
Received: from omr-m07.mx.aol.com (omr-m07.mx.aol.com [64.12.143.81]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 950C11A03BE for <sfc@ietf.org>; Tue, 16 Sep 2014 14:49:35 -0700 (PDT)
Received: from mtaout-aan02.mx.aol.com (mtaout-aan02.mx.aol.com [172.27.19.78]) by omr-m07.mx.aol.com (Outbound Mail Relay) with ESMTP id 6FB057009438E; Tue, 16 Sep 2014 17:49:34 -0400 (EDT)
Received: from mgs-aam01.mail.aol.com (mgs-aam01.mail.aol.com [64.12.250.54]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mtaout-aan02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 39AB73800009B; Tue, 16 Sep 2014 17:49:34 -0400 (EDT)
Date: Tue, 16 Sep 2014 17:49:34 -0400
From: "mikebianc@aol.com" <mikebianc@aol.com>
To: jguichar@cisco.com, sfc@ietf.org
Message-ID: <243854349.5104.1410904174086.JavaMail.tomcat@mgs-aam01.mail.aol.com>
In-Reply-To: <D021EA69.33AE5%jguichar@cisco.com>
References: <D021EA69.33AE5%jguichar@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_5103_1340227276.1410904174086"
X-Originating-IP: 10.181.180.123, 10.181.180.123
X-Mailer: Alto
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1410904174; bh=lXS19Oa8jBZtqWTR/W/vyMnel9Da9fv1c949avOmA4k=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=tznMmQqCg8s1iseifR1ny4E/2KqkM2YbXOryPgcUKZVR/GOFaI52nI3hgd+DfxNuC TAOGVnLytqjXMFD9i3xIJxnv7+t9nHTpdFVl7RKVQteJufbO/MunomU0sfXp0Yftro VBS/6P9guKgyPV6PNQOWF7emlMmGBkncKh4nobOc=
x-aol-sid: 3039ac1b134e5418b06e4aaa
X-AOL-IP: 64.12.250.54
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/AucEf-Ma5FxXBT5OeRrYRwnE2Ek
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, 16 Sep 2014 21:49:37 -0000

support adoption as well.





From: jguichar@cisco.com<jguichar@cisco.com>
To: sfc@ietf.org<sfc@ietf.org>
Sent: Tuesday, August 26, 2014
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:

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.

v2.23.0 | Report a Bug | By Email