Re: [ippm] RFC8321bis and RFC8889bis: draft-02
Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Wed, 23 February 2022 10:43 UTC
Return-Path: <giuseppe.fioccola@huawei.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29A763A0A48; Wed, 23 Feb 2022 02:43:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 C9Z4fqXEA5OW; Wed, 23 Feb 2022 02:43:48 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F6F63A0A36; Wed, 23 Feb 2022 02:43:48 -0800 (PST)
Received: from fraeml711-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4K3XZp0Ndyz6890h; Wed, 23 Feb 2022 18:38:58 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml711-chm.china.huawei.com (10.206.15.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Wed, 23 Feb 2022 11:43:45 +0100
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.2308.021; Wed, 23 Feb 2022 11:43:44 +0100
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Giuseppe Fioccola <giuseppe.fioccola=40huawei.com@dmarc.ietf.org>, Martin Duke <martin.h.duke@gmail.com>, IETF IPPM WG <ippm@ietf.org>
CC: "draft-fioccola-rfc8321bis.all@ietf.org" <draft-fioccola-rfc8321bis.all@ietf.org>, "draft-fioccola-rfc8889bis.all@ietf.org" <draft-fioccola-rfc8889bis.all@ietf.org>
Thread-Topic: RFC8321bis and RFC8889bis: draft-02
Thread-Index: AdgkATgXIMY0zCqzTny6KOgRPKluEwEmo+1Q
Date: Wed, 23 Feb 2022 10:43:44 +0000
Message-ID: <bf1e9f55e4324c3c93584a24083fc1fc@huawei.com>
References: <fc96f6e4ec6347dfa72c2e6ccdf87313@huawei.com>
In-Reply-To: <fc96f6e4ec6347dfa72c2e6ccdf87313@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.219.177]
Content-Type: multipart/alternative; boundary="_000_bf1e9f55e4324c3c93584a24083fc1fchuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/JcKXMDP3JHZBrfMDcnp0vKG02Rg>
Subject: Re: [ippm] RFC8321bis and RFC8889bis: draft-02
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2022 10:43:53 -0000
Dear Martin, As promised, I just published revision -03 of RFC8321bis. I also updated RFC8889bis accordingly. All the modifications are recorded in the Changes Log. I think we can now take it through IETF Last Call. Regards, Giuseppe (on behalf of co-authors) From: ippm <ippm-bounces@ietf.org> On Behalf Of Giuseppe Fioccola Sent: Thursday, February 17, 2022 2:24 PM To: Martin Duke <martin.h.duke@gmail.com>; IETF IPPM WG <ippm@ietf.org> Cc: draft-fioccola-rfc8321bis.all@ietf.org; draft-fioccola-rfc8889bis.all@ietf.org Subject: [ippm] RFC8321bis and RFC8889bis: draft-02 Hi Martin, All, Please note that I just submitted new revisions of both RFC8321bis and RFC8889bis. I tried to address the latest comments. I plan to submit revision -03 of RFC8321bis early next week for the IETF Last Call. https://datatracker.ietf.org/doc/draft-fioccola-rfc8321bis/ https://datatracker.ietf.org/doc/draft-fioccola-rfc8889bis/ Reviews and suggestions will be welcome. Regards, Giuseppe
- [ippm] RFC8321bis and RFC8889bis: draft-02 Giuseppe Fioccola
- Re: [ippm] RFC8321bis and RFC8889bis: draft-02 Giuseppe Fioccola