[Dots] DOTS Telemetry: Interop Clarification #3
mohamed.boucadair@orange.com Thu, 25 June 2020 19:31 UTC
Return-Path: <mohamed.boucadair@orange.com>
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 2978C3A0FE8 for <dots@ietfa.amsl.com>; Thu, 25 Jun 2020 12:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 FCwKu7MTEKT2 for <dots@ietfa.amsl.com>; Thu, 25 Jun 2020 12:31:36 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 224A83A0FE7 for <dots@ietf.org>; Thu, 25 Jun 2020 12:31:36 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 49t99y3gGzzFq15; Thu, 25 Jun 2020 21:31:34 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1593113494; bh=Cj89lTnlGtjuvn1BqZZuI+o//D+22HGKWHbL8V7GX6Q=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=dIEGbVNZS7aQ1GlmuHf0u8hHR19GagsO4WcXbfAO3Vd7aYy4TPRfZxzT1mKM2+Dqu URyq7myeRTyZMFFLDhd17W4Xa7u2LwLWMYimgsldR2dFgY5ZqODLPykcGu9r6W+w9U yxo90IDlvyHavuQeeqIxmbp3QgcTCGpO4NDET6YqzFKppCbeASDDhEaAczj/QiWHWS W9WAsy81XPZK0dcCPSkdtE5aGimuWsMRbOTAzTNg0MNjozjRmEePc88doJxAi9KZTk IbTGdD68JI2XCfmiD9yNRrqvFmsmvtJtRzLuJU7vExGYRMPP9SkMz2LoFxRrpSAwSu A2XnAUmJDJM1g==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.107]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 49t99y2lvfzCqkV; Thu, 25 Jun 2020 21:31:34 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: kaname nishizuka <kaname@nttv6.jp>
CC: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: DOTS Telemetry: Interop Clarification #3
Thread-Index: AdZLJzstzanwENMBRvG6m9wslEq8bA==
Date: Thu, 25 Jun 2020 19:31:33 +0000
Message-ID: <27464_1593113494_5EF4FB96_27464_425_1_787AE7BB302AE849A7480A190F8B9330314E7645@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B9330314E7645OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/Es8Mkl02JrxaDesoEC85P-mlWgA>
Subject: [Dots] DOTS Telemetry: Interop Clarification #3
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 25 Jun 2020 19:31:38 -0000
Re-, You reported the following in the interim : == 3."DOTS agents MUST NOT include 'attack-name' attribute except if the corresponding attack mapping details were not shared with the peer DOTS agent". But how can the DOTS server know they're shared or not? === This is implementation-specific. The DOTS server may record which version of the mapping table it shared with a DOTS client. Do you think that we need to include such details in the spec? or do you have mind something else? Thanks. Cheers, Med _________________________________________________________________________________________________________________________ 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.
- [Dots] DOTS Telemetry: Interop Clarification #3 mohamed.boucadair
- Re: [Dots] DOTS Telemetry: Interop Clarification … kaname nishizuka
- Re: [Dots] DOTS Telemetry: Interop Clarification … Konda, Tirumaleswar Reddy
- Re: [Dots] DOTS Telemetry: Interop Clarification … mohamed.boucadair
- Re: [Dots] DOTS Telemetry: Interop Clarification … Konda, Tirumaleswar Reddy
- Re: [Dots] DOTS Telemetry: Interop Clarification … mohamed.boucadair
- Re: [Dots] DOTS Telemetry: Interop Clarification … Konda, Tirumaleswar Reddy
- Re: [Dots] DOTS Telemetry: Interop Clarification … mohamed.boucadair
- Re: [Dots] DOTS Telemetry: Interop Clarification … Jon Shallow
- Re: [Dots] DOTS Telemetry: Interop Clarification … mohamed.boucadair
- Re: [Dots] DOTS Telemetry: Interop Clarification … Jon Shallow
- Re: [Dots] DOTS Telemetry: Interop Clarification … mohamed.boucadair