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

[kaname nishizuka <[e-mail]>]

Hi Med,

thanks.
The presentation slide is now on the site of meeting materials.

It might be better for the discussion at the Friday meeting if you could look at it beforehand.

regards,
Kaname

On 2019/11/18 21:59, [e-mail] wrote:
> Hi Kaname,
>
> Thank you for the feedback. I added an issue for this: https://github.com/boucadair/draft-dots-telemetry/issues/1
>
> An alternative approach would be to define a distinct contain for configuration-related data under the telemetry.
>
> Looking forward reading your Hackathon report.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : Dots [mailto:[e-mail]] De la part de kaname nishizuka
>> Envoyé : samedi 16 novembre 2019 04:29
>> À : BOUCADAIR Mohamed TGI/OLN; [e-mail]
>> Objet : Re: [Dots] TR: New Version Notification for draft-reddy-dots-
>> telemetry-04.txt
>>
>> 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, [e-mail] 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:[e-mail]] De la part de
>>>>> [e-mail]
>>>>> Envoyé : mercredi 23 octobre 2019 13:25
>>>>> À : kaname nishizuka; [e-mail]
>>>>> 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:[e-mail]]
>>>>>> Envoyé : mercredi 23 octobre 2019 11:07
>>>>>> À : BOUCADAIR Mohamed TGI/OLN; [e-mail]
>>>>>> 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, [e-mail] 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 : [e-mail] [mailto:[e-mail]]
>>>>>>>> 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
>>>>>>> [e-mail]
>>>>>>> https://www.ietf.org/mailman/listinfo/dots
>>>>> _______________________________________________
>>>>> Dots mailing list
>>>>> [e-mail]
>>>>> https://www.ietf.org/mailman/listinfo/dots
>>> _______________________________________________
>>> Dots mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/dots
>> _______________________________________________
>> Dots mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/dots