IETF Logo Mail Archive

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

Sumandra Majee <S.Majee@F5.com> Tue, 26 August 2014 18:25 UTC

Return-Path: <S.Majee@f5.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 1584B1A00F9 for <sfc@ietfa.amsl.com>; Tue, 26 Aug 2014 11:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.668
X-Spam-Level:
X-Spam-Status: No, score=-7.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 r0ow83e8TaiY for <sfc@ietfa.amsl.com>; Tue, 26 Aug 2014 11:25:26 -0700 (PDT)
Received: from mail.f5.com (mail.f5.com [208.85.209.139]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8CC01A0097 for <sfc@ietf.org>; Tue, 26 Aug 2014 11:25:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=f5.com; i=@f5.com; q=dns/txt; s=seattle; t=1409077526; x=1440613526; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=6xbqSldw4CoXUS/Cqy/THEJV1g+10TkMMXSP/uPpjho=; b=MMqTRbVC/czyy4Lgn8j/9zL9f/ELtLWhH67Fl2RHEAbuPBQEcEr0UAER b4drTxW6zsJqZ8g1m5HsAuB37uQl4npbKAecb59XtbuUURAEKvvEWw+4P SjQ4F53AoEWPhOUvHfCbxzzt/4XC7OeduCZDtR5ppUMNmUjQ7Kt/XPSux M=;
X-IronPort-AV: E=Sophos;i="5.04,405,1406592000"; d="scan'208,217";a="127462170"
X-IPAS-Result: AssEAOjP/FPAqArr/2dsb2JhbABbgkeBGVeyV5gigTghAQmHTQGBLXeEBAEBAQMBAQEaUQsQAgEIBA4tBycLFAMOAgQOBYhPv0AXj0gEB4MvgR0FlU+IUpcSbIJPAQEB
Received: from oracle-apps.f5net.com (HELO exchmail.f5net.com) ([192.168.10.235]) by mail.f5.com with ESMTP/TLS/AES128-SHA; 26 Aug 2014 18:25:26 +0000
Received: from SEAEMBX01.olympus.F5Net.com ([fe80::3440:4256:38f6:d3a0]) by SEAECAS04.olympus.F5Net.com ([::1]) with mapi id 14.03.0181.006; Tue, 26 Aug 2014 11:25:26 -0700
From: Sumandra Majee <S.Majee@F5.com>
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>
Thread-Topic: [sfc] Call for WG adoption of draft-merged-sfc-architecture-02
Thread-Index: AQHPwVsajjT4O/XlBUWhy0sus5Gcrw==
Date: Tue, 26 Aug 2014 18:25:25 +0000
Message-ID: <3A9E5A05-79B1-41E1-875C-C466E496A711@F5.com>
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:
Content-Type: multipart/alternative; boundary="_000_3A9E5A0579B141E1875CC466E496A711F5com_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/X99QtzxjJGT6dJjwmzEIJ7Gdb3Q
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: Tue, 26 Aug 2014 18:25:29 -0000

Support

Sent from my iPhone

On Aug 26, 2014, at 4:41 AM, "Jim Guichard (jguichar)" <jguichar@cisco.com<mailto: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:

  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.

_______________________________________________
sfc mailing list
sfc@ietf.org<mailto:sfc@ietf.org>
https://www.ietf.org/mailman/listinfo/sfc

v2.23.0 | Report a Bug | By Email