IETF Logo Mail Archive

Re: [sfc] Adopting draft-mirsky-sfc-pmamm

<xiao.min2@zte.com.cn> Sat, 25 May 2019 02:06 UTC

Return-Path: <xiao.min2@zte.com.cn>
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 56CF9120323 for <sfc@ietfa.amsl.com>; Fri, 24 May 2019 19:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 w4LvCPhEuQDp for <sfc@ietfa.amsl.com>; Fri, 24 May 2019 19:06:24 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 DCAD1120319 for <sfc@ietf.org>; Fri, 24 May 2019 19:06:23 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id DBBF873E887EEDA3F906; Sat, 25 May 2019 10:06:21 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse-fl2.zte.com.cn with SMTP id x4P26G6D008991; Sat, 25 May 2019 10:06:16 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid201; Sat, 25 May 2019 10:06:16 +0800 (CST)
Date: Sat, 25 May 2019 10:06:16 +0800
X-Zmail-TransId: 2afd5ce8a31868d4c065
X-Mailer: Zmail v1.0
Message-ID: <201905251006164923129@zte.com.cn>
In-Reply-To: <b2c4ca07-e012-72b7-476c-2ca17c3f9748@joelhalpern.com>
References: CA+RyBmXFfeoPd5jTqfvG7RAxgDxQePmuV4j4VuvVC1-H=p5OZA@mail.gmail.com, b2c4ca07-e012-72b7-476c-2ca17c3f9748@joelhalpern.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: jmh@joelhalpern.com
Cc: gregimirsky@gmail.com, sfc@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn x4P26G6D008991
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/IS_3Iv4daHlUupIsIC6_PcKq2Bw>
Subject: Re: [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: Sat, 25 May 2019 02:06:25 -0000

Hi SFC WG,






I support the adoption.


This document falls within the SFC charter on OAM work, and it provides a very useful tool on SFC performance monitoring.






Thanks,


Xiao Min










原始邮件



发件人：JoelM.Halpern <jmh@joelhalpern.com>
收件人：Greg Mirsky <gregimirsky@gmail.com>;Service Function Chaining IETF list <sfc@ietf.org>;
日 期 ：2019年05月25日 02:16
主 题 ：[sfc] Adopting draft-mirsky-sfc-pmamm


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

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

v2.23.0 | Report a Bug | By Email