IETF Logo Mail Archive

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

Sam Aldrin <aldrin.ietf@gmail.com> Tue, 26 August 2014 22:26 UTC

Return-Path: <aldrin.ietf@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 7B3A51A00EC for <sfc@ietfa.amsl.com>; Tue, 26 Aug 2014 15:26:29 -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 uEkWhNMVfVMl for <sfc@ietfa.amsl.com>; Tue, 26 Aug 2014 15:26:28 -0700 (PDT)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 040751A0118 for <sfc@ietf.org>; Tue, 26 Aug 2014 15:26:27 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id fp1so23579837pdb.13 for <sfc@ietf.org>; Tue, 26 Aug 2014 15:26:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=FQwtCZYUcSgoHw8hk9OioIv8eJLH+CxSKbdCaBJPlEs=; b=dj4LsfhppYxn3BMrhiYrasM4SXbUWNat76VeDoalbqhJmICJAqVITTT4rBw9GC5SVQ /lKdnfjhfzTi24RCb4XQ/cTorpzStuWGkM88pLlM5Qs64DuOAOtQQo/OdBzaJ5EQhwOl 7Bt+tUrLsz0mlNt7tcOJXlPdGN75pz4eSZ8HH9P/vlHMhM6tf/VhlmzlBeqbSSTIzXbb Cv/zkcylLTbWXjph+QI2BkWC7AbKmdfDiug0+aWZBB89Rq5HmGtWqz3LGUa6WIm6EO9K Xzq8fCC+jP9oPxcFsK95A0sE0AktJPmYDoGNI4lC0ADJhx4NxkRgFHpdKi5TauodMbvs IEQw==
X-Received: by 10.66.222.132 with SMTP id qm4mr16991283pac.140.1409091987693; Tue, 26 Aug 2014 15:26:27 -0700 (PDT)
Received: from [10.94.182.211] (mobile-166-171-251-186.mycingular.net. [166.171.251.186]) by mx.google.com with ESMTPSA id td4sm4332923pbc.36.2014.08.26.15.26.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Aug 2014 15:26:26 -0700 (PDT)
References: <D021EA69.33AE5%jguichar@cisco.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <D021EA69.33AE5%jguichar@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-A08ACC4D-8349-4115-8A24-82BAA67CC981"
Content-Transfer-Encoding: 7bit
Message-Id: <872C5C6A-7A30-4685-97B2-04274F553807@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Sam Aldrin <aldrin.ietf@gmail.com>
Date: Tue, 26 Aug 2014 15:26:24 -0700
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/X-5b0V9RnlJJPqpym_hVtaiblLY
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 22:26:29 -0000

Support adoption of this version as WG doc.

Cheers
Sam

Sent from my iPhone

> 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