Re: [Dots] DOTS Telemetry: Interop Clarification #3
kaname nishizuka <kaname@nttv6.jp> Fri, 26 June 2020 01:51 UTC
Return-Path: <kaname@nttv6.jp>
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 AC5853A10E0 for <dots@ietfa.amsl.com>; Thu, 25 Jun 2020 18:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nttv6.jp
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 eQAgVhSToUhf for <dots@ietfa.amsl.com>; Thu, 25 Jun 2020 18:51:02 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [115.69.228.140]) by ietfa.amsl.com (Postfix) with ESMTP id C99DB3A10DF for <dots@ietf.org>; Thu, 25 Jun 2020 18:51:01 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [192.168.8.15]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id A759B25F6BB; Fri, 26 Jun 2020 10:50:59 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nttv6.jp; s=20180820; t=1593136259; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=mSAtOmtpbh1syrpupH+EYSELxb4MKF4BCtXdr7cEsp8=; b=YHPAILymdNtr5feIvuDO5h2yo0UPaiqq1W/KdudArzGrqJdY/aNDVtdRg2jNwCkF8Hu4A/ C/O0oI3ptIb4YDUwXcmFeN3mxG+fzgruW0tIdH6ncERRN2qwQdyUFJTNeK0cRRRRlUfDGZ LmTnQsZhqYbiAQloTp5beDTwFbusLeY=
Received: from UG023-kaname.local (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 81F6D75900F; Fri, 26 Jun 2020 10:50:59 +0900 (JST)
To: mohamed.boucadair@orange.com
Cc: "dots@ietf.org" <dots@ietf.org>
References: <27464_1593113494_5EF4FB96_27464_425_1_787AE7BB302AE849A7480A190F8B9330314E7645@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: kaname nishizuka <kaname@nttv6.jp>
Message-ID: <fa1f7938-17cf-a80d-5bad-37ef08c495e8@nttv6.jp>
Date: Fri, 26 Jun 2020 10:50:59 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <27464_1593113494_5EF4FB96_27464_425_1_787AE7BB302AE849A7480A190F8B9330314E7645@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------D8E0FFD65E1C62FE71100757"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/Zq8RbOjWvNImasoMTHHeUt8gHCk>
Subject: Re: [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: Fri, 26 Jun 2020 01:51:07 -0000
Hi Med, Yes, it's implementation-specific. I didn't intend to suggest a text here, but wanted to hear ideas on how others might handle it. regards, kaname On 2020/06/26 4:31, mohamed.boucadair@orange.com wrote: > > 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