IETF Logo Mail Archive

[sfc] Adopting draft-mirsky-sfc-pmamm

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 24 May 2019 18:17 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1CE4120150 for <sfc@ietfa.amsl.com>; Fri, 24 May 2019 11:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 d0bM9iDe4_JZ for <sfc@ietfa.amsl.com>; Fri, 24 May 2019 11:17:55 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEC391201BB for <sfc@ietf.org>; Fri, 24 May 2019 11:17:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 459ZNZ5f9jzXxYG; Fri, 24 May 2019 11:17:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1558721870; bh=x0lxDgtVxMzMN+9OmoiS9cqXGgXWPMzt9MmBziChx7E=; h=Subject:To:References:From:Date:In-Reply-To:From; b=CQFvYfuJ+ZWTJODVs/3bUhh1LWoxI+qO3GOWgiIpJ1WMveloEMHT0H2mqdaXEFGgv V2Z6rnpfL06hF30Mg72El2nMOAaoeSwryugDbO/BQPAcpZ29MgiqxxmLkKOZefvGmK afK7Qv5zFjOv726bkRGg2VrukhAyoNh2Kw800rxs=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 459ZNZ21HXzFq4H; Fri, 24 May 2019 11:17:50 -0700 (PDT)
To: Greg Mirsky <gregimirsky@gmail.com>, Service Function Chaining IETF list <sfc@ietf.org>
References: <CA+RyBmXFfeoPd5jTqfvG7RAxgDxQePmuV4j4VuvVC1-H=p5OZA@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <b2c4ca07-e012-72b7-476c-2ca17c3f9748@joelhalpern.com>
Date: Fri, 24 May 2019 14:17:49 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <CA+RyBmXFfeoPd5jTqfvG7RAxgDxQePmuV4j4VuvVC1-H=p5OZA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/VFb-_k2gDlxMzuiHAOALNji9gHk>
Subject: [sfc] Adopting draft-mirsky-sfc-pmamm
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 24 May 2019 18:17:57 -0000

This email starts the adoption call for draft-mirsky-sfc-pmamm 
(https://datatracker.ietf.org/doc/draft-mirsky-sfc-pmamm/).

Please speak up if you support or oppose adopting this document as a 
working group document.  Please provide reasons for that view.
Silence will not be considered consent.

The adoption call will end CoB 10 June 2019.

Yours,
Joel (and Jim

On 5/20/19 1:58 PM, Greg Mirsky wrote:
> Dear Joel and Jim,
> authors ofdraft-mirsky-sfc-pmamm believe that the draft, that defines 
> how the Alternate Marking (RFC 8321) technique can be used in SFC NSH, 
> is stable, and ready for the working group adoption. Much appreciate 
> your consideration to start the WG AP.
> 
> Best regards,
> Greg

v2.23.0 | Report a Bug | By Email