Re: [ippm] Section 6 - draft-fz-ippm-alt-mark-deployment-01

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Wed, 27 September 2023 09:05 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 59423C13AE53; Wed, 27 Sep 2023 02:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xQTP10yCP5bm; Wed, 27 Sep 2023 02:05:50 -0700 (PDT)
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 2DF4CC151542; Wed, 27 Sep 2023 02:05:50 -0700 (PDT)
Received: from frapeml500008.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4RwVzf5Sfqz6K8rH; Wed, 27 Sep 2023 17:04:30 +0800 (CST)
Received: from frapeml500006.china.huawei.com (7.182.85.219) by frapeml500008.china.huawei.com (7.182.85.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Wed, 27 Sep 2023 11:05:47 +0200
Received: from frapeml500006.china.huawei.com ([7.182.85.219]) by frapeml500006.china.huawei.com ([7.182.85.219]) with mapi id 15.01.2507.031; Wed, 27 Sep 2023 11:05:47 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: "Thomas.Graf@swisscom.com" <Thomas.Graf@swisscom.com>, "ippm@ietf.org" <ippm@ietf.org>, "draft-fz-ippm-alt-mark-deployment.authors@ietf.org" <draft-fz-ippm-alt-mark-deployment.authors@ietf.org>
CC: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: Section 6 - draft-fz-ippm-alt-mark-deployment-01
Thread-Index: AdnvorM7OAaThpJqSiCXHe8g9y5AaABdhS4g
Date: Wed, 27 Sep 2023 09:05:46 +0000
Message-ID: <9e02d54e02274236adf48960f53e1346@huawei.com>
References: <b04df19096e446ab99b51303517f7315@swisscom.com>
In-Reply-To: <b04df19096e446ab99b51303517f7315@swisscom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.146.1]
Content-Type: multipart/alternative; boundary="_000_9e02d54e02274236adf48960f53e1346huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/XOYHP-sKJCw4AEuMj8V7lLtkgAo>
Subject: Re: [ippm] Section 6 - draft-fz-ippm-alt-mark-deployment-01
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
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, 27 Sep 2023 09:05:55 -0000

Hi Thomas,
Thank you for the feedback.
I think your proposal to extend Section 6 makes sense. The use of IPFIX and YANG Push for data export and collection was only mentioned in the current version, therefore, it is very good to include more details on that. I will incorporate your proposed text in the next revision.

Comments are always welcome.

Best Regards,

Giuseppe

From: Thomas.Graf@swisscom.com <Thomas.Graf@swisscom.com>
Sent: Monday, September 25, 2023 1:23 PM
To: ippm@ietf.org; Giuseppe Fioccola <giuseppe.fioccola@huawei.com>; draft-fz-ippm-alt-mark-deployment.authors@ietf.org
Cc: opsawg@ietf.org
Subject: Section 6 - draft-fz-ippm-alt-mark-deployment-01

Dear draft-fz-ippm-alt-mark-deployment authors, Dear IPPM working group,

First of all I think draft-fz-ippm-alt-mark-deployment is a valuable document describing the deployment of Alternat Marking.

I have reviewed https://datatracker.ietf.org/doc/draft-fz-ippm-alt-mark-deployment/ the Network Telemetry aspect described in Section 6 and wrote a proposal for -01 as following:

https://raw.githubusercontent.com/network-analytics/draft-fz-ippm-alt-mark-deployment/main/draft-fz-ippm-alt-mark-deployment-01.txt
https://raw.githubusercontent.com/network-analytics/draft-fz-ippm-alt-mark-deployment/main/draft-fz-ippm-alt-mark-deployment-01.xml

The new section describes how the export could be performed with existing IPFIX entities where decomposition is performed at the data collection and what needs to be consider for new IPFIX entities. I also described the publication with YANG push and what needs to be considered in terms of subscription, data publication and modeling.

Here the current diff: https://author-tools.ietf.org/diff?url_1=https://www.ietf.org/archive/id/draft-fz-ippm-alt-mark-deployment-00.txt&url_2=https://raw.githubusercontent.com/network-analytics/draft-fz-ippm-alt-mark-deployment/main/draft-fz-ippm-alt-mark-deployment-01.txt

I hope this makes sense and is helpful for the community. Feedback and comments welcome.

Best wishes
Thomas