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

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Wed, 29 May 2019 10:09 UTC

Return-Path: <giuseppe.fioccola@huawei.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 BBA6612015C for <sfc@ietfa.amsl.com>; Wed, 29 May 2019 03:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 Du5oOXd10tvy for <sfc@ietfa.amsl.com>; Wed, 29 May 2019 03:09:19 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 E53C012012C for <sfc@ietf.org>; Wed, 29 May 2019 03:09:18 -0700 (PDT)
Received: from lhreml705-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 4CECDD5FE1BB63B7A410; Wed, 29 May 2019 11:09:17 +0100 (IST)
Received: from lhreml507-mbb.china.huawei.com ([10.201.109.48]) by lhreml705-cah.china.huawei.com ([10.201.108.46]) with mapi id 14.03.0415.000; Wed, 29 May 2019 11:09:13 +0100
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Greg Mirsky <gregimirsky@gmail.com>, Service Function Chaining IETF list <sfc@ietf.org>
CC: Cociglio Mauro <mauro.cociglio@telecomitalia.it>
Thread-Topic: [sfc] Adopting draft-mirsky-sfc-pmamm
Thread-Index: AQHVEl0ZnM9TV0Qg+kqw/EML0fBO96aB5XIw
Date: Wed, 29 May 2019 10:09:13 +0000
Message-ID: <E92F9C7E59A8854E8BED73140B879B4E01273CE1@lhreml507-mbb>
References: <CA+RyBmXFfeoPd5jTqfvG7RAxgDxQePmuV4j4VuvVC1-H=p5OZA@mail.gmail.com> <b2c4ca07-e012-72b7-476c-2ca17c3f9748@joelhalpern.com>
In-Reply-To: <b2c4ca07-e012-72b7-476c-2ca17c3f9748@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.204.62.190]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/B7-oTMvjsk0blqIzA5STwGyX2qo>
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: Wed, 29 May 2019 10:09:21 -0000

Dear Joel, Jim and All,
I support the adoption of the this draft as co-author. The application of the alternate marking method to SFC NSH was also mentioned in RFC 8321 and enables efficient OAM Performance Measurements as expected in the SFC OAM draft.

Best Regards,

Giuseppe


-----Original Message-----
From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Joel M. Halpern
Sent: Friday, May 24, 2019 8:18 PM
To: Greg Mirsky <gregimirsky@gmail.com>; Service Function Chaining IETF list <sfc@ietf.org>
Subject: [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