Re: [Dots] TR: New Version Notification for draft-reddy-dots-telemetry-04.txt

kaname nishizuka <kaname@nttv6.jp> Sat, 16 November 2019 03:28 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 817511200A4 for <dots@ietfa.amsl.com>; Fri, 15 Nov 2019 19:28:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-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 tYKOA6q_Yt49 for <dots@ietfa.amsl.com>; Fri, 15 Nov 2019 19:28:48 -0800 (PST)
Received: from guri.nttv6.jp (guri.nttv6.jp [IPv6:2402:c800:ff06:136::140]) by ietfa.amsl.com (Postfix) with ESMTP id 164121200B1 for <dots@ietf.org>; Fri, 15 Nov 2019 19:28:47 -0800 (PST)
Received: from z.nttv6.jp (z.nttv6.jp [IPv6:2402:c800:ff06:6::f]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id 2407C25F6B8; Sat, 16 Nov 2019 12:28:45 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nttv6.jp; s=20180820; t=1573874925; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GQXD+1OENa8lvi8gN2N6meAbETElbtaDsq9H3hNlIxE=; b=qfZgxKj3tGy2jUKCkfUSxrD2KvYun5DamhFXF/g5iqM4HSXtVNPA91Hl4zHpfOD0GMReTt L785b461Kp9VGub33UyW36Zxtc7LVfNP8YhbnTJyS4BvGKJewtH0crQq/TBR65RR9JAVAi h7yQbFSreNG9RdJDg850Bi2nDQVPupA=
Received: from dhcp-868e.meeting.ietf.org (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 9F6F5759062; Sat, 16 Nov 2019 12:28:44 +0900 (JST)
From: kaname nishizuka <kaname@nttv6.jp>
To: mohamed.boucadair@orange.com, "dots@ietf.org" <dots@ietf.org>
References: <157139119677.3853.16590465405127507911.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B9330313410DA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <317486f6-fbd7-2811-a58c-c5a826fb9e5e@nttv6.jp> <787AE7BB302AE849A7480A190F8B9330313445B0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <787AE7BB302AE849A7480A190F8B93303135F2E7@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <c51a0b31-03b2-8234-648d-83ac77976e46@nttv6.jp>
Message-ID: <11b795d5-bb12-9f3e-b01b-9c95d36e4275@nttv6.jp>
Date: Sat, 16 Nov 2019 12:28:42 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <c51a0b31-03b2-8234-648d-83ac77976e46@nttv6.jp>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Authentication-Results: guri.nttv6.jp; spf=pass smtp.mailfrom=kaname@nttv6.jp
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/0-ABU62Y64D86I5IDKdBVAcBGQw>
Subject: Re: [Dots] TR: New Version Notification for draft-reddy-dots-telemetry-04.txt
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: Sat, 16 Nov 2019 03:28:52 -0000

Hi Med, all,

I've just arrived at the hackathon venue.

To start with, I'd like to suggest one change to the current pre-migation spec.

 From yang module on page 19, in "telemetry" tree (with URI-path "telemetry"):
here is the configuration part.
           +--rw telemetry* [cuid tcid]
              +--rw cuid                     string
              +--rw cdid?                    string
              +--rw tcid                     uint32
              +--rw telemetry-config
              |  +--rw low-percentile?    percentile
              |  +--rw mid-percentile?    percentile
              |  +--rw high-percentile?   percentile
              |  +--rw unit-config* [unit]
              |     +--rw unit      unit
              |     +--rw status?   boolean
Capacity things will be also a part of configuration. (it would work with tcid)
However, attack-detail is *NOT* a configuration.

How about separating these resources like this,
URI-path "telemetry-config":
     telemetry-config and capacity things
URI-path "telemetry":
     periodical traffic/connection metric and attack-detail (if exist)


regards,
Kaname


On 2019/11/08 20:16, kaname nishizuka wrote:
> Hi Med,
>
> Thanks! I'll look into and use it.
>
> kaname
>
> On 2019/11/08 16:58, mohamed.boucadair@orange.com wrote:
>> Hi Kaname,
>>
>> Apologies for the delay to have this done.
>>
>> The draft notes the following:
>>
>>        Notes: (1) Check naming conflict to ease CBOR mapping (e.g, low-
>>        percentile is defined as yang:gauge64, list, or container).
>>        Distinct names may be considered.
>>
>> Although this is not an issue in YANG, I updated some YANG attribute names to avoid cbor naming conflicts. The updated YANG module is available at: https://github.com/boucadair/draft-dots-telemetry/blob/master/draft-reddy-dots-telemetry-04.txt
>>
>> Please find below the mapping table. An online version is also available at: https://github.com/boucadair/draft-dots-telemetry/blob/master/mapping-table.txt.
>>
>> +----------------------+-------------+------+---------------+--------+
>>     | Parameter Name       | YANG        | CBOR | CBOR Major | JSON   |
>>     |                      | Type        | Key  |    Type &     | Type   |
>>     |                      |             |      | Information |        |
>> +----------------------+-------------+------+---------------+--------+
>>     | ietf-dots-signal-cha |             |      | |        |
>>     | nnel:telemetry       | container   |0x8008| 5 map | Object |
>>     | tcid                 | uint32      |0x8009| 0 unsigned | Number |
>>     | telemetry-config     | container   |0x800A| 5 map | Object |
>>     | low-percentile       | decimal64   |0x800B| 6 tag 4 |        |
>>     |                      |             |      |  [-2, integer]| String |
>>     | mid-percentile       | decimal64   |0x800C| 6 tag 4 |        |
>>     |                      |             |      |  [-2, integer]| String |
>>     | high-percentile      | decimal64   |0x800D| 6 tag 4 |        |
>>     |                      |             |      |  [-2, integer]| String |
>>     | unit-config          | list        |0x800E| 4 array | Array  |
>>     | unit                 | enumeration |0x800F| 0 unsigned | String |
>>     | status               | boolean     |0x8010| 7 bits 20 | False  |
>>     |                      |             |      | 7 bits 21 | True   |
>>     | total-pipe-capability| list        |0x8011| 4 array | Array  |
>>     | pipe                 | uint64      |0x8012| 0 unsigned | String |
>>     | pre-mitigation       | list        |0x8013| 4 array | Array  |
>>     | telemetry-id         | uint32      |0x8014| 0 unsigned | Number |
>>     | total-traffic-       |             |      | |        |
>>     |    normal-baseline   | list        |0x8015| 4 array | Array  |
>>     | low-percentile-g     | yang:gauge64|0x8016| 0 unsigned | String |
>>     | mid-percentile-g     | yang:gauge64|0x8017| 0 unsigned | String |
>>     | high-percentile-g    | yang:gauge64|0x8018| 0 unsigned | String |
>>     | peak-g               | yang:gauge64|0x8019| 0 unsigned | String |
>>     | total-attack-traffic | list        |0x801A| 4 array | Array  |
>>     | total-traffic        | list        |0x801B| 4 array | Array  |
>>     | total-connection-    |             |      | |        |
>>     |        capacity      | list        |0x801C| 4 array | Array  |
>>     | connection           | uint64      |0x801D| 0 unsigned | String |
>>     | connection-client    | uint64      |0x801E| 0 unsigned | String |
>>     | embryonic            | uint64      |0x801F| 0 unsigned | String |
>>     | embryonic-client     | uint64      |0x8020| 0 unsigned | String |
>>     | connection-ps        | uint64      |0x8021| 0 unsigned | String |
>>     | connection-client-ps | uint64      |0x8022| 0 unsigned | String |
>>     | request-ps           | uint64      |0x8023| 0 unsigned | String |
>>     | request-client-ps    | uint64      |0x8024| 0 unsigned | String |
>>     | partial-request-ps   | uint64      |0x8025| 0 unsigned | String |
>>     | mitigation-start     | uint64      |0x8026| 0 unsigned | String |
>>     | partial-request-     |             |      | |        |
>>     |        client-ps     | uint64      |0x8027| 0 unsigned | String |
>>     | total-attack-        |             |      | |        |
>>     |        connection    | container   |0x8028| 5 map | Object |
>>     | low-percentile-l     | list        |0x8029| 4 array | Array  |
>>     | mid-percentile-l     | list        |0x802A| 4 array | Array  |
>>     | high-percentile-l    | list        |0x802B| 4 array | Array  |
>>     | peak                 | list        |0x802C| 4 array | Array  |
>>     | attack-detail        | container   |0x802D| 5 map | Object |
>>     | vendor-id            | uint32      |0x802E| 0 unsigned | Number |
>>     | attack-id            | string      |0x802F| 3 text string | String |
>>     | attack-name          | string      |0x8030| 3 text string | String |
>>     | attack-severity      | enumeration |0x8031| 0 unsigned | String |
>>     | start-time           | uint64      |0x8032| 0 unsigned | String |
>>     | end-time             | uint64      |0x8033| 0 unsigned | String |
>>     | source-count         | container   |0x8034| 5 map | Object |
>>     | top-talker           | container   |0x8035| 5 map | Object |
>>     | spoofed-status       | boolean     |0x8036| 7 bits 20 | False  |
>>     |                      |             |      | 7 bits 21 | True   |
>>     | low-percentile-c     | container   |0x8037| 5 map | Object |
>>     | mid-percentile-c     | container   |0x8038| 5 map | Object |
>>     | high-percentile-c    | container   |0x8039| 5 map | Object |
>>     | peak-c               | container   |0x803A| 5 map | Object |
>> +----------------------+-------------+------+---------------+--------+
>>
>> Cheers,
>> Med
>>
>>> -----Message d'origine-----
>>> De : Dots [mailto:dots-bounces@ietf.org] De la part de
>>> mohamed.boucadair@orange.com
>>> Envoyé : mercredi 23 octobre 2019 13:25
>>> À : kaname nishizuka; dots@ietf.org
>>> Objet : Re: [Dots] TR: New Version Notification for draft-reddy-dots-
>>> telemetry-04.txt
>>>
>>> Hi Kaname,
>>>
>>> Thank you for sharing the feedback.
>>>
>>> We will prepare an initial version of the mapping table that we will put on
>>> the github. That table will be integrated in the next iteration of the
>>> draft.
>>>
>>> Cheers,
>>> Med
>>>
>>>> -----Message d'origine-----
>>>> De : kaname nishizuka [mailto:kaname@nttv6.jp]
>>>> Envoyé : mercredi 23 octobre 2019 11:07
>>>> À : BOUCADAIR Mohamed TGI/OLN; dots@ietf.org
>>>> Objet : Re: [Dots] TR: New Version Notification for draft-reddy-dots-
>>>> telemetry-04.txt
>>>>
>>>> Hi Med, all,
>>>>
>>>> I'm planning to implement dots telemetry features into go-dots.
>>>> Though it would evolve, ifan initial version of yang/cbor mapping was
>>>> defined, it helps me a lot.
>>>>
>>>> thanks,
>>>> Kaname
>>>>
>>>>
>>>> On 2019/10/18 18:38, mohamed.boucadair@orange.com wrote:
>>>>> Hi all,
>>>>>
>>>>> Although we are waiting for a call for adoption for this draft, we made
>>>> some changes which you can track with the diff provided below.
>>>>> Cheers,
>>>>> Med
>>>>>
>>>>>> -----Message d'origine-----
>>>>>> De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>>>>> Envoyé : vendredi 18 octobre 2019 11:33
>>>>>> À : chenmeiling; BOUCADAIR Mohamed TGI/OLN; Meiling Chen; Tirumaleswar
>>>>>> Reddy; Ehud Doron; Reddy K
>>>>>> Objet : New Version Notification for draft-reddy-dots-telemetry-04.txt
>>>>>>
>>>>>>
>>>>>> A new version of I-D, draft-reddy-dots-telemetry-04.txt
>>>>>> has been successfully submitted by Mohamed Boucadair and posted to the
>>>>>> IETF repository.
>>>>>>
>>>>>> Name:        draft-reddy-dots-telemetry
>>>>>> Revision:    04
>>>>>> Title:        Distributed Denial-of-Service Open Threat Signaling
>>> (DOTS)
>>>>>> Telemetry
>>>>>> Document date:    2019-10-18
>>>>>> Group:        Individual Submission
>>>>>> Pages:        41
>>>>>> URL: https://www.ietf.org/internet-drafts/draft-reddy-dots-
>>>>>> telemetry-04.txt
>>>>>> Status: https://datatracker.ietf.org/doc/draft-reddy-dots-
>>>>>> telemetry/
>>>>>> Htmlized: https://tools.ietf.org/html/draft-reddy-dots-
>>> telemetry-
>>>> 04
>>>>>> Htmlized: https://datatracker.ietf.org/doc/html/draft-reddy-
>>> dots-
>>>>>> telemetry
>>>>>> Diff: https://www.ietf.org/rfcdiff?url2=draft-reddy-dots-
>>>>>> telemetry-04
>>>>>>
>>>>>> Abstract:
>>>>>>      This document aims to enrich DOTS signal channel protocol with
>>>>>>      various telemetry attributes allowing optimal DDoS attack
>>>> mitigation.
>>>>>>      This document specifies the normal traffic baseline and attack
>>>>>>      traffic telemetry attributes a DOTS client can convey to its DOTS
>>>>>>      server in the mitigation request, the mitigation status telemetry
>>>>>>      attributes a DOTS server can communicate to a DOTS client, and the
>>>>>>      mitigation efficacy telemetry attributes a DOTS client can
>>>>>>      communicate to a DOTS server.  The telemetry attributes can assist
>>>>>>      the mitigator to choose the DDoS mitigation techniques and perform
>>>>>>      optimal DDoS attack mitigation.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Please note that it may take a couple of minutes from the time of
>>>>>> submission
>>>>>> until the htmlized version and diff are available at tools.ietf.org.
>>>>>>
>>>>>> The IETF Secretariat
>>>>> _______________________________________________
>>>>> Dots mailing list
>>>>> Dots@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/dots
>>> _______________________________________________
>>> Dots mailing list
>>> Dots@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dots
>
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots