Re: [Dots] [Nmop] Request for a solt at Nmop IETF119 [Extended YANG Data Model for DOTS]
Linzhe Li <lilz@zgclab.edu.cn> Wed, 06 March 2024 06:35 UTC
Return-Path: <lilz@zgclab.edu.cn>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AED9DC14CE2C; Tue, 5 Mar 2024 22:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.397
X-Spam-Level:
X-Spam-Status: No, score=-0.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_RPBL=1.31, 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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=zgclab.edu.cn
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 RbCDWIps_-Dp; Tue, 5 Mar 2024 22:35:45 -0800 (PST)
Received: from azure-sdnproxy.icoremail.net (azure-sdnproxy.icoremail.net [52.237.72.81]) by ietfa.amsl.com (Postfix) with ESMTP id 60813C14F5E4; Tue, 5 Mar 2024 22:35:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zgclab.edu.cn; s=dkim; h=Received:Date:From:To:Cc:Subject: In-Reply-To:References:Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID; bh=46OjLW2JU7KsZeko2pCiF7wAg4uWrajhwfjx NHgx7BU=; b=ljrtFoVSQdbNkL7jhhbSaKY9KQnuE4CQ3yLqPF8E7sgxOr8H099r TKi3inAQ3UT6tuq5LtAB8Z2LMdQVB6OIlirAHreLZjD8TTiX/7M/dCnaUcM5fdzR W0XtOYzPOhbbHqS1y4zK1m6L98W0ZNxd9hGR2vxvXPedTkZf49p6Iic=
Received: from lilz$zgclab.edu.cn ( [58.206.206.207] ) by ajax-webmail-web4 (Coremail) ; Wed, 6 Mar 2024 14:35:39 +0800 (GMT+08:00)
X-Originating-IP: [58.206.206.207]
Date: Wed, 06 Mar 2024 14:35:39 +0800
X-CM-HeaderCharset: UTF-8
From: Linzhe Li <lilz@zgclab.edu.cn>
To: nmop@ietf.org
Cc: "dots@ietf.org" <dots@ietf.org>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version 2023.2-cmXT5 build 20230915(bf90896b) Copyright (c) 2002-2024 www.mailtech.cn mispb-4df55a87-4b50-4a66-85a0-70f79cb6c8b5-tsinghua.edu.cn
In-Reply-To: <DU2PR02MB1016030ABE6679F374007E0C488222@DU2PR02MB10160.eurprd02.prod.outlook.com>
References: <6d1dc816.12938.18e0c33780e.Coremail.lilz@zgclab.edu.cn> <DU2PR02MB1016030ABE6679F374007E0C488222@DU2PR02MB10160.eurprd02.prod.outlook.com>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-ID: <209d5067.144a0.18e12798e14.Coremail.lilz@zgclab.edu.cn>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: ywQGZQDHT5C7DuhlfrrOAw--.65147W
X-CM-SenderInfo: holo6qx2jfztveohv3gofq/1tbiAQEICGXnpDlEdgAGsr
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/H7d8Qqk6MWUvw5nX6sgGYB0Mtgg>
Subject: Re: [Dots] [Nmop] Request for a solt at Nmop IETF119 [Extended YANG Data Model for DOTS]
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2024 06:35:49 -0000
Hi Med, Thanks for your comments. We will make the following main updates: * Use cases to make the problem clearer. * We've taken DOTS telemetry into account, and we found there is stll some other information worth considering in the data model. We will make this point more clearly. * Explain the source of the extension parameters to prove that our assumptions about the client are feasible. Looking forward to have a further talk with you at the hackathon. Best regards, Linzhe -----原始邮件----- 发件人: mohamed.boucadair@orange.com 发送时间: 2024-03-05 19:42:51 (星期二) 收件人: 李林哲 <lilz@zgclab.edu.cn>, "nmop@ietf.org" <nmop@ietf.org> 抄送: "dots@ietf.org" <dots@ietf.org> 主题: RE: [Nmop] Request for a solt at Nmop IETF119 [Extended YANG Data Model for DOTS] Hi Linzhe, (ccing DOTS) Recorded your request at https://github.com/ietf-wg-nmop/IETF-Meetings/blob/main/119/requested-slots.md. However, I don’t expect a slot to be allocated for this item. FWIW, you may find some quick comments at: pdf: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2024/draft-cui-dots-extended-yang-01-rev%20Med.pdf doc: https://github.com/boucadair/IETF-Drafts-Reviews/edit/master/2024/draft-cui-dots-extended-yang-01-rev%20Med.doc The main comment I have is that the Problem to be Solved is not clear enough and seems to not take into account the recent work about DOTS telemetry. I found it useful in the past to have a DOTS use case document with the flow to illustrate the intended functionality. You may inspire from RFC 9387. Some assumptions about the client capabilities in the draft should also be better clarified (e.g., supplying mitigation strategies). There are some issues with the modules themselves, but that’s not important at this stage. These can be fixed once the overall problem is clarified. Hope this helps. Looking forward to have more information from the hackathon. Cheers, Med De : Nmop <nmop-bounces@ietf.org> De la part de ??? Envoyé : mardi 5 mars 2024 02:21 À : nmop@ietf.org Objet : [Nmop] Request for a solt at Nmop IETF119 [Extended YANG Data Model for DOTS] Hi all, I would like to request a slot to present the draft about extended YANG model of DOTS (DDoS Open Threat Signaling).In the process of deploying dots, we identified some problems and proposed preliminary solutions We are designing and deploying a collaborative mitigation framework for DDoS attacks. And we noticed DOTS and tried to use it to complete the transmission of important data in the collaborative mitigation framework. However, we and operators, security equipment manufacturers, discovered that both the data channel and signaling channel of DOTS lacked some important data models. This will seriously affect the response speed and mitigation effectiveness of collaborative mitigation parties. Therefore, we proposed a draft to describe the data model that DOTS needs to add. It is worth mentioning that we will demonstrate the expanded prototype system at HACKAHTON and explain the benefits of the expanded data model. Request Information: Title: Extended YANG Data Model for DOTS Draft: https://datatracker.ietf.org/doc/draft-cui-dots-extended-yang/ Presenter: Linzhe Li Duration: 10 minutes Best regards, Linzhe ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
- Re: [Dots] [Nmop] Request for a solt at Nmop IETF… mohamed.boucadair
- Re: [Dots] [Nmop] Request for a solt at Nmop IETF… Linzhe Li