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

"Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com> Fri, 02 August 2019 11:10 UTC

Return-Path: <tirumaleswarreddy_konda@mcafee.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 C9C26120096 for <dots@ietfa.amsl.com>; Fri, 2 Aug 2019 04:10:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.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 39D2mvzz_W8K for <dots@ietfa.amsl.com>; Fri, 2 Aug 2019 04:10:56 -0700 (PDT)
Received: from us-smtp-delivery-210.mimecast.com (us-smtp-delivery-210.mimecast.com [216.205.24.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29FF81200DB for <dots@ietf.org>; Fri, 2 Aug 2019 04:10:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=mimecast20190606; t=1564744255; h=from:from: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:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4Iu6RO6kmecYPxOxluQGhR0Hc9FMlJkmitHK79H2x8A=; b=E//ODQv8oJgHghXMw4uqz81VRylA/rfpyx2ZpOlB4j6fwXWCCnT7kJ/iyQc8u8+bMmY0lH ha5dw45ZCgdMLGSJwfft2YM3lmj52N4Wh9pf6auW/+0xy6EJ4SHKw7KVCloOj93+i2fSLA /vBLq05hoAIcvlNm0I7Qlp3eCDVehRs=
Received: from MIVWSMAILOUT1.mcafee.com (mivwsmailout1.mcafee.com [161.69.47.167]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-105-dbwxbfuZP6OTF4BMkGCccg-1; Fri, 02 Aug 2019 07:10:50 -0400
Received: from DNVEXAPP1N06.corpzone.internalzone.com (DNVEXAPP1N06.corpzone.internalzone.com [10.44.48.90]) by MIVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 0502_6ac1_3a4d69be_4a3f_442a_b4f0_b10aa9abb843; Fri, 02 Aug 2019 07:11:30 -0400
Received: from DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 2 Aug 2019 05:10:37 -0600
Received: from DNVO365EDGE1.corpzone.internalzone.com (10.44.176.66) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 2 Aug 2019 05:10:37 -0600
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (10.44.176.240) by edge.mcafee.com (10.44.176.66) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 2 Aug 2019 05:10:32 -0600
Received: from DM5PR16MB1705.namprd16.prod.outlook.com (10.172.44.147) by DM5PR16MB1371.namprd16.prod.outlook.com (10.173.210.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.13; Fri, 2 Aug 2019 11:10:31 +0000
Received: from DM5PR16MB1705.namprd16.prod.outlook.com ([fe80::6c22:21e:7528:3dc5]) by DM5PR16MB1705.namprd16.prod.outlook.com ([fe80::6c22:21e:7528:3dc5%6]) with mapi id 15.20.2136.010; Fri, 2 Aug 2019 11:10:31 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, H Y <yuuhei.hayashi@gmail.com>
CC: tirumal reddy <kondtir@gmail.com>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] Fwd: New Version Notification for draft-reddy-dots-telemetry-00.txt
Thread-Index: AQHVMzSMCPbrTboVdUKfxcuyXDvZxqbYNT+AgAGVHKCAAAbagIAAAf6QgAAE3gCAAAhfgP///5jQgA27AICAAD/vgA==
Date: Fri, 2 Aug 2019 11:10:31 +0000
Message-ID: <DM5PR16MB170543EFE7B366D14F8EE015EAD90@DM5PR16MB1705.namprd16.prod.outlook.com>
References: <156233245922.21720.2303446065970922340.idtracker@ietfa.amsl.com> <CAFpG3gcgpJRyLSoLkOMuUWY8pZrBPDCCz6-sc8A=1KW3GMpm+g@mail.gmail.com> <CAA8pjUPY+GDGxNhqDCWsh-6aGnYoOL+A5pGaE=2BaE5j8rY41g@mail.gmail.com> <DM5PR16MB17051F8C7697FE7DAF88AEC4EAC60@DM5PR16MB1705.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B9330312E739F@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <DM5PR16MB17050D182A4BE8C3B7EFDC3EEAC60@DM5PR16MB1705.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B9330312E73FA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAA8pjUPe8rf6m2xy2S+JzhTN+xMm_9f3+OaBAsAnY7aV43g11A@mail.gmail.com> <DM5PR16MB17055E4630A2413CB7D212DBEAC60@DM5PR16MB1705.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B9330312FB914@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B9330312FB914@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.3.0.17
dlp-reaction: no-action
x-originating-ip: [49.37.202.60]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 236b0159-03d2-4565-bf0a-08d7173a08a2
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM5PR16MB1371;
x-ms-traffictypediagnostic: DM5PR16MB1371:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <DM5PR16MB1371813DFF2C34C910ABA605EAD90@DM5PR16MB1371.namprd16.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 011787B9DD
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(4636009)(136003)(346002)(39850400004)(376002)(366004)(396003)(199004)(189003)(32952001)(52314003)(53754006)(13464003)(51914003)(229853002)(305945005)(8676002)(5660300002)(30864003)(81166006)(81156014)(7736002)(8936002)(15650500001)(66556008)(76116006)(64756008)(66446008)(71190400001)(66946007)(66476007)(86362001)(52536014)(71200400001)(102836004)(2501003)(66066001)(7696005)(80792005)(76176011)(6506007)(186003)(53546011)(68736007)(26005)(99286004)(33656002)(316002)(6116002)(3846002)(486006)(446003)(11346002)(476003)(5024004)(14444005)(256004)(55016002)(6246003)(74316002)(6436002)(110136005)(2906002)(4326008)(9686003)(478600001)(66574012)(53936002)(6306002)(54906003)(14454004)(25786009)(966005)(85282002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR16MB1371; H:DM5PR16MB1705.namprd16.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: W/y8jCJs7LQMgLXGaY1Z1oBKzZ/cplseYrzxN1hjVAZb1BLDQVrC+6wlZjZ1RX30A3StlKLNIklio81j7YdrHo2hh48A0N0O+/+wEzmf9SMdHZSDHCsJx0r0iFZK/2yLkJqJI8HMrqf3YWfeYSd8O+OGEEWmRcZGt9A6/1yE/c8jeAoW6qGtrT/xEEQAzrnBkeZsr1N0pUgiO59ftxJBryn3vqBB4vKWz4g1e5o7xXrN4w8+BrYxU5QVGEmti1b4d98VPg/GCQMuAMKkgC+v31nB7GpfCO/WAHe/yFRdaryHoAT5U+UKTKf6pNMm3AN6kFKkPpw+p06myx/baO0M/tRfudQ5/+fd9x1LoTOdqADNy9qZQ8YLlk6JVt66e5PjLhfu6wSSINUC8aCcq5GGV25UYlXHWSHMV2C0ftiYBrI=
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 236b0159-03d2-4565-bf0a-08d7173a08a2
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Aug 2019 11:10:31.4988 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: TirumaleswarReddy_Konda@McAfee.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR16MB1371
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Level:
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0.2
X-NAI-Spam-Version: 2.3.0.9418 : core <6603> : inlines <7130> : streams <1829138> : uri <2876874>
X-MC-Unique: dbwxbfuZP6OTF4BMkGCccg-1
X-Mimecast-Spam-Score: 0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/yjI38wMKnuZyhlF2DywBQf1nhnY>
Subject: Re: [Dots] Fwd: New Version Notification for draft-reddy-dots-telemetry-00.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: Fri, 02 Aug 2019 11:11:00 -0000

> -----Original Message-----
> From: mohamed.boucadair@orange.com
> <mohamed.boucadair@orange.com>;
> Sent: Friday, August 2, 2019 12:36 PM
> To: Konda, Tirumaleswar Reddy
> <TirumaleswarReddy_Konda@McAfee.com>;; H Y
> <yuuhei.hayashi@gmail.com>;
> Cc: tirumal reddy <kondtir@gmail.com>;; dots@ietf.org
> Subject: RE: [Dots] Fwd: New Version Notification for draft-reddy-dots-
> telemetry-00.txt
> 
> This email originated from outside of the organization. Do not click links or
> open attachments unless you recognize the sender and know the content is
> safe.
> 
> Hi Tiru,
> 
> These questions are valid ones when it comes to decide which mitigation
> actions to apply. Nevertheless, the source information is part of the
> characterization of an attack at given time. This does not mean that we
> necessarily rely on it to mitigate, but this is not excluded either.

The use of this top-talkers attribute and it's use to black-list traffic (or mitigation) needs to be clearly articulated. It can potentially adversely impact the mitigated resource service 
to spoofed top-taker IP addresses. 

-Tiru

> 
> The source information can be included in the notification use case already
> described by Kaname in this thread, or if the mitigator is enforcing policies
> based on the source information (because of a local knowledge of an attack)
> but reaches a limit, it can delegate the policy to a L3 orchestrator (Yuhei case).
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Konda, Tirumaleswar Reddy
> > [mailto:TirumaleswarReddy_Konda@McAfee.com]
> > Envoyé : mercredi 24 juillet 2019 15:35 À : H Y; BOUCADAIR Mohamed
> > TGI/OLN Cc : tirumal reddy; dots@ietf.org Objet : RE: [Dots] Fwd: New
> > Version Notification for draft-reddy-dots- telemetry-00.txt
> >
> > Hi Yuhei,
> >
> > What is stopping the attacker to frequently change the IP address
> > (especially with IPv6) ?
> > What kind of attack traffic is generated by the top talkers and what
> > happens if the top talkers are spoofed IP addresses (e.g.
> > amplification
> > attack) ?
> >
> > Cheers,
> > -Tiru
> >
> > > -----Original Message-----
> > > From: H Y <yuuhei.hayashi@gmail.com>;
> > > Sent: Wednesday, July 24, 2019 6:57 PM
> > > To: Mohamed Boucadair <mohamed.boucadair@orange.com>;
> > > Cc: Konda, Tirumaleswar Reddy
> <TirumaleswarReddy_Konda@McAfee.com>;;
> > > tirumal reddy <kondtir@gmail.com>;; dots@ietf.org
> > > Subject: Re: [Dots] Fwd: New Version Notification for
> > > draft-reddy-dots- telemetry-00.txt
> > >
> > >
> > >
> > > Hi Med,
> > >
> > > > [Med] Yes. My point is if one has to return a list of top-talkers
> > > > in
> > terms of
> > > pps, another list of top-talkers in terms of second_criteria, or
> > > other information relying on source-prefix dedicated attributes will
> > > be needed because this cannot be inferred from the current
> > > source-prefix
> > attribute.
> > > [hayashi] +1. This top-talker information is helpful for the
> > orchestrator to
> > > decide which attack traffic should be blocked preferentially in network.
> > The
> > > criteria information is also needed.
> > >
> > > Thanks,
> > > Yuhei
> > >
> > > 2019年7月24日(水) 8:56 <mohamed.boucadair@orange.com>;:
> > > >
> > > > Re-,
> > > >
> > > > Please see inline.
> > > >
> > > > Cheers,
> > > > Med
> > > >
> > > > > -----Message d'origine-----
> > > > > De : Konda, Tirumaleswar Reddy
> > > > > [mailto:TirumaleswarReddy_Konda@McAfee.com]
> > > > > Envoyé : mercredi 24 juillet 2019 14:45 À : BOUCADAIR Mohamed
> > > > > TGI/OLN; H Y; tirumal reddy Cc : dots@ietf.org Objet : RE:
> > > > > [Dots]
> > > > > Fwd: New Version Notification for draft-reddy-dots-
> > > > > telemetry-00.txt
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: mohamed.boucadair@orange.com
> > > <mohamed.boucadair@orange.com>;
> > > > > > Sent: Wednesday, July 24, 2019 6:02 PM
> > > > > > To: Konda, Tirumaleswar Reddy
> > > > > > <TirumaleswarReddy_Konda@McAfee.com>;; H Y
> > > > > > <yuuhei.hayashi@gmail.com>;; tirumal reddy <kondtir@gmail.com>;
> > > > > > Cc: dots@ietf.org
> > > > > > Subject: RE: [Dots] Fwd: New Version Notification for
> > > > > > draft-reddy-dots- telemetry-00.txt
> > > > > >
> > > > > > This email originated from outside of the organization. Do not
> > > > > > click
> > > > > links or
> > > > > > open attachments unless you recognize the sender and know the
> > > > > > content is safe.
> > > > > >
> > > > > > Hi Tiru,
> > > > > >
> > > > > > That’s true...but fragmentation is a general issue each time
> > > > > > we need to supply more telemetry information in the signal channel.
> > > > > > As already
> > > > > noted in
> > > > > > the draft, we will need to figure out when it is better to
> > > > > > provide some telemetry information using data channel.
> > > > >
> > > > > Yes, normal traffic baseline attributes can be conveyed in the
> > > > > DOTS data channel and traffic from top talkers can also be
> > > > > blocked/rate-limited using the DOTS data channel during peace time.
> > > > >
> > > > > >
> > > > > > BTW, "top talker" can already be supplied using source-prefix
> > attribute.
> > > > > > Whether top-talker needs to be defined as a separated
> > > > > > attribute, but structured as a list of source-prefixes is a
> > > > > > design details (if the WG
> > > > > agrees to
> > > > > > include it in the telemetry information).
> > > > >
> > > > > Source-prefix is already a list/array.
> > > >
> > > > [Med] Yes. My point is if one has to return a list of top-talkers
> > > > in
> > terms of
> > > pps, another list of top-talkers in terms of second_criteria, or
> > > other information relying on source-prefix dedicated attributes will
> > > be needed because this cannot be inferred from the current
> > > source-prefix
> > attribute.
> > > >
> > > > >
> > > > > >
> > > > > > Anyway, let's continue collecting candidate telemetry
> > > > > > information and
> > > > > then
> > > > > > make a selection in a second phase.
> > > > >
> > > > > Sure.
> > > > >
> > > > > Cheers,
> > > > > -Tiru
> > > > >
> > > > > >
> > > > > > Cheers,
> > > > > > Med
> > > > > >
> > > > > > > -----Message d'origine-----
> > > > > > > De : Dots [mailto:dots-bounces@ietf.org] De la part de
> > > > > > > Konda, Tirumaleswar Reddy Envoyé : mercredi 24 juillet 2019
> > > > > > > 14:18 À : H Y; tirumal reddy Cc : dots@ietf.org Objet : Re:
> > > > > > > [Dots] Fwd: New Version Notification for draft-reddy-dots-
> > > > > > > telemetry-00.txt
> > > > > > >
> > > > > > > Hi Yuhei,
> > > > > > >
> > > > > > > Thanks for the support. The problem is fragmentation of the
> > > > > > > DOTS telemetry message, DOTS Telemetry is sent over the DOTS
> > > > > > > signal channel using UDP and the message size cannot exceed
> PMTU.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > -Tiru
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Dots <dots-bounces@ietf.org>; On Behalf Of H Y
> > > > > > > > Sent: Tuesday, July 23, 2019 5:28 PM
> > > > > > > > To: tirumal reddy <kondtir@gmail.com>;
> > > > > > > > Cc: dots@ietf.org
> > > > > > > > Subject: Re: [Dots] Fwd: New Version Notification for
> > > > > > > > draft-reddy-dots- telemetry-00.txt
> > > > > > > >
> > > > > > > > This email originated from outside of the organization. Do
> > > > > > > > not click
> > > > > > > links or
> > > > > > > > open attachments unless you recognize the sender and know
> > > > > > > > the content is safe.
> > > > > > > >
> > > > > > > > Hi Tiru,
> > > > > > > >
> > > > > > > > I read the draft and I also support this draft.
> > > > > > > > Sending detail information about attack traffic helps my
> > > > > > > > dms offload
> > > > > > > scenario
> > > > > > > > because the orchestrator can decide what to do based on
> > > > > > > > the detail information.
> > > > > > > >
> > > > > > > > IMO, "top talker" attribute defined in my previous draft
> > > > > > > > is also
> > > > > > > feasible to
> > > > > > > > send and effective to mitigate attack correctly.
> > > > > > > > https://datatracker.ietf.org/doc/draft-h-dots-mitigation-o
> > > > > > > > fflo
> > > > > > > > ad-
> > > > > > > expansion/
> > > > > > > > What do you think about including the top talker attribute
> > > > > > > > to the
> > > > > > > telemetry?
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Yuhei
> > > > > > > >
> > > > > > > > 2019年7月5日(金) 9:21 tirumal reddy <kondtir@gmail.com>;:
> > > > > > > > >
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > https://tools.ietf.org/html/draft-reddy-dots-telemetry-0
> > > > > > > > > 0
> > > > > > > > > aims to
> > > > > > > enrich
> > > > > > > > DOTS protocols 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.
> > > > > > > > >
> > > > > > > > > Comments, suggestions, and questions are more than
> welcome.
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > > -Tiru
> > > > > > > > >
> > > > > > > > > ---------- Forwarded message ---------
> > > > > > > > > From: <internet-drafts@ietf.org>;
> > > > > > > > > Date: Fri, 5 Jul 2019 at 18:44
> > > > > > > > > Subject: New Version Notification for
> > > > > > > > > draft-reddy-dots-telemetry-00.txt
> > > > > > > > > To: Tirumaleswar Reddy <kondtir@gmail.com>;, Ehud Doron
> > > > > > > > > <ehudd@radware.com>;, Mohamed Boucadair
> > > > > > > > <mohamed.boucadair@orange.com>;
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > A new version of I-D, draft-reddy-dots-telemetry-00.txt
> > > > > > > > > has been successfully submitted by Tirumaleswar Reddy
> > > > > > > > > and posted to the IETF repository.
> > > > > > > > >
> > > > > > > > > Name:           draft-reddy-dots-telemetry
> > > > > > > > > Revision:       00
> > > > > > > > > Title:          Distributed Denial-of-Service Open Threat
> > > > > Signaling
> > > > > > > (DOTS)
> > > > > > > > Telemetry
> > > > > > > > > Document date:  2019-07-05
> > > > > > > > > Group:          Individual Submission
> > > > > > > > > Pages:          13
> > > > > > > > > URL:            https://www.ietf.org/internet-drafts/draft-
> > reddy-
> > > > > dots-
> > > > > > > > telemetry-00.txt
> > > > > > > > > Status:         https://datatracker.ietf.org/doc/draft-
> > reddy-dots-
> > > > > > > telemetry/
> > > > > > > > > Htmlized:       https://tools.ietf.org/html/draft-reddy-
> > dots-
> > > > > > > telemetry-00
> > > > > > > > > Htmlized:       https://datatracker.ietf.org/doc/html/draft-
> > reddy-
> > > > > > > dots-
> > > > > > > > telemetry
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > 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
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > ----------------------------------
> > > > > > > > Yuuhei HAYASHI
> > > > > > > > 08065300884
> > > > > > > > yuuhei.hayashi@gmail.com
> > > > > > > > iehuuy_0220@docomo.ne.jp
> > > > > > > > ----------------------------------
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > 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
> > >
> > >
> > >
> > > --
> > > ----------------------------------
> > > Yuuhei HAYASHI
> > > 08065300884
> > > yuuhei.hayashi@gmail.com
> > > iehuuy_0220@docomo.ne.jp
> > > ----------------------------------