Minutes interim-2020-dots-01: Thu 06:00
minutes-interim-2020-dots-01-202006250600-00
Meeting Minutes | DDoS Open Threat Signaling (dots) WG | |
---|---|---|
Date and time | 2020-06-25 06:00 | |
Title | Minutes interim-2020-dots-01: Thu 06:00 | |
State | Active | |
Other versions | plain text | |
Last updated | 2020-06-29 |
minutes-interim-2020-dots-01-202006250600-00
DOTS WG Virtual Interim Meeting Thursday 25 June 2020 6:00-7:00 UTC WebEx: https://ietf.webex.com/ietf/j.php?MTID=m583b7d2e85e9bc229e902d12aabbaa41 Jabber: xmpp:dots@jabber.ietf.org?join Etherpad: https://etherpad.ietf.org:9009/p/notes-ietf-interim-2020-dots-01-dots?useMonospaceFont=true Slides: https://datatracker.ietf.org/meeting/interim-2020-dots-01/session/dots Jabber scribe: Valery Smyslov Note Taker: Wei Pan Agenda: 1. Administrivia and agenda bashing - 5 min (Chairs) Chairs introduce the current status of drafts. 2. Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry status update (draft-ietf-dots-telemetry-08) - 25 min (Med, Tiru) Med: Suggest to use comprehension-optional attributes, thus the key values will consume 3 bytes, the proposal for the value range is 128-255. Valery: No objection, suggest to discuss this on the mailing list. Tiru: Telemetry is optional, if using comprehension-required then the DOTS server needs to understand all the attributes. Take this to the mailing list. Chair: Raise this issue on the mailing list. Tiru: Support to exchange the map of attack-id and attack-name on the data channel. Tiru: Do we need to use BLOCK 3 and BLOCK 4 more often because of the poor connections caused by attacks? Jon: I think so. Med: I agree with Jon. It's not mandatory. Chair: Should request YANG doctors' review and Ask the OPS AD to review this draft. Encourage the operators to review. 3. Multi-homing Deployment Considerations for Distributed-Denial-of-Service Open Threat Signaling (DOTS) status update (draft-ietf-dots-multihoming-04) - 5 min (Med, Tiru) Med: Need more reviews and feedback. Suggest to consider WGLC in Sept 2020. 4. Use Cases for DDoS Open Threat Signaling (DOTS) Telemetry (draft-hayashi-dots-telemetry-use-cases-00) - 5 min (Yuhei) Options on how to move forward with this draft: Opt 1. Require WG adoption after addressing comments from WG. Opt 2. Add a high-level use case description to the Telemetry draft. (e.g. Appendix) Tiru: We should adopt this draft. Prefer option 1. Frank: Suggest option 2. Valery: For the implementers option 2 would be better, but if the draft is too long to read then option 1 is better. Tiru: This is a draft of examples of how to using telemetry. Chairs: discuss this further on the mailing list. 5. A method for dots server deployment (draft-chen-dots-server-hierarchical-deployment-02) - 5 min (Meiling) Meiling: Ask for how to move forward with this draft. Frank: Suggest to clarify the objectives and discuss on the mailing list. Meiling: The objective is to make recommandations for DOTS agents deployment. Frank: Feel like that this draft can be combinded into other drafts. I don't see the needs of such a separate document. Getting more discussions on the mailing list will be helpful. Charis: Suggest to discuss on the mailing list.