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

Thomas.Graf@swisscom.com Mon, 25 September 2023 11:23 UTC

Return-Path: <Thomas.Graf@swisscom.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 5821FC15198F; Mon, 25 Sep 2023 04:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 P-ltiF9HWArq; Mon, 25 Sep 2023 04:23:52 -0700 (PDT)
Received: from mail.swisscom.com (mailout110.swisscom.com [138.188.166.110]) (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 24D46C15198E; Mon, 25 Sep 2023 04:23:47 -0700 (PDT)
Received: by mail.swisscom.com; Mon, 25 Sep 2023 13:23:30 +0200
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="----=_Part_543898_1502627048.1695641010134"
X-Mailer: Totemo_TrustMail_(Notification)
From: Thomas.Graf@swisscom.com
To: ippm@ietf.org, giuseppe.fioccola@huawei.com, draft-fz-ippm-alt-mark-deployment.authors@ietf.org
CC: opsawg@ietf.org
Thread-Topic: Section 6 - draft-fz-ippm-alt-mark-deployment-01
Thread-Index: AdnvorM7OAaThpJqSiCXHe8g9y5AaA==
Date: Mon, 25 Sep 2023 11:23:27 +0000
Message-ID: <b04df19096e446ab99b51303517f7315@swisscom.com>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_ActionId=946f09c7-8772-4e1e-8ac9-08c6207207e4; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_ContentBits=0; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Enabled=true; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Method=Standard; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Name=C2 Internal; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SetDate=2023-09-25T11:13:25Z; MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SiteId=364e5b87-c1c7-420d-9bee-c35d19b557a1;
x-originating-ip: [138.188.161.184]
X-CFilter-Loop: Reflected
X-Trustmail: processed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/f5oyNWL0eGwOMXEkSLbBpIJMaPg>
Subject: [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: Mon, 25 Sep 2023 11:23:56 -0000

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