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

"Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com> Mon, 22 July 2019 14:11 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 5326412029F for <dots@ietfa.amsl.com>; Mon, 22 Jul 2019 07:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.388
X-Spam-Level:
X-Spam-Status: No, score=-2.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" 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 KSoCntw8leWN for <dots@ietfa.amsl.com>; Mon, 22 Jul 2019 07:11:45 -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 0AE14120059 for <dots@ietf.org>; Mon, 22 Jul 2019 07:11:44 -0700 (PDT)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1563804025; h=ARC-Seal: ARC-Message-Signature:ARC-Authentication-Results: From:To:Subject:Thread-Topic:Thread-Index: Date:Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-ms-exchange-purlcount:x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-ms-exchange-senderadcheck: x-microsoft-antispam-message-info:Content-Type: MIME-Version:X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-CrossTenant-mailboxtype: X-MS-Exchange-CrossTenant-userprincipalname: X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Level: X-NAI-Spam-Threshold:X-NAI-Spam-Score:X-NAI-Spam-Version; bh=PcsX9erSZB0nfGOLDD2RWbT8wgyCfnlOZQs6ZD r4ufA=; b=ESa1QQBFqw+1r8qhf05k2BRukwfEChzQJg1uOWLP 37QL3dcvL5xMdKyLUAgGEtCqd6vmNcuIY9cz5LK84Ms5KmcWWd Qcq6xkbNpsvRGo7QABJTA7kupFe+iz6YTeMQuw/XPr7xOIAl+b ykbzqwXYnrDYmZtxpXbr/r76O6rzN2U=
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-207-JtdDDm_DMNu7R78rA2NCaQ-1; Mon, 22 Jul 2019 10:11:38 -0400
Received: from DNVEXAPP1N05.corpzone.internalzone.com (DNVEXAPP1N05.corpzone.internalzone.com [10.44.48.89]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 298c_389c_02153e77_4af9_4eb1_93ba_e4e8c2ebbb7f; Mon, 22 Jul 2019 08:00:24 -0600
Received: from DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) by DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 22 Jul 2019 08:11:32 -0600
Received: from DNVO365EDGE2.corpzone.internalzone.com (10.44.176.74) by DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 22 Jul 2019 08:11:32 -0600
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (10.44.176.242) by edge.mcafee.com (10.44.176.74) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 22 Jul 2019 08:11:30 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gyJ64vgMUUZiDWAvk/zvcXcGqLR2QSuUDa4MtuBkJ6rlI/qxMRdO7CxrEj6yEccc8qE3+TRLZCx6K+Cyt2b3bwOgcPBaYgfluDw4PjqScgC6oNu3hptGBBQJ74vXaWfmGXKxVc/IuH5AUSA0RbdvwzT+vUQ6TfqWji4RB68tN6KqQIdL2cmGk4h9SuCl0mPAflO+QWWb30IGf2b0nRirohLFX0Ki67U38ezihCXMhEH3aO5dfmxnEmwyf20CWuIJnrEHuaykpmwQ0LOiK2fhw5EDTK20jPkR66VvZ4otus77jAz1zroOXtFWgSTov5h8jTV7R6IlTtT2J8errwAtgA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PcsX9erSZB0nfGOLDD2RWbT8wgyCfnlOZQs6ZDr4ufA=; b=YPYVNfQulqSsePcEjGqX+VNc3WJBYzEWKytoBRoT002Z7YG4HObYUUTiK7OnAfss12Qrjyts6xVhFHIsRU/Na+RKfNFMY8o7NX3Np03OF2HL21URi7ccMbE+gzk97Y/dQMmLOFrvAe6qly0cqk7Np46PjfRkdHHt37HwahJcVyLjM8hflKqiVZ0lkAGW+f4MHOxKb5RvPz6ZjVEvCEeJ6UR86rqa6k0UvgmBmJ2wE22BROkDPW/6Unl5ykkY5GDFXPt4uPUfz5JkWIJir2J25dIOwt0vvsbVQUXEaWyqRZeDAq0XL4x2oBWkd5cbAm5tc1YCW/878KU9NFFGnize7A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=mcafee.com;dmarc=pass action=none header.from=mcafee.com;dkim=pass header.d=mcafee.com;arc=none
Received: from DM5PR16MB1705.namprd16.prod.outlook.com (10.172.44.147) by DM5SPR00MB242.namprd16.prod.outlook.com (10.168.120.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.16; Mon, 22 Jul 2019 14:11:29 +0000
Received: from DM5PR16MB1705.namprd16.prod.outlook.com ([fe80::570:2208:75c2:5f17]) by DM5PR16MB1705.namprd16.prod.outlook.com ([fe80::570:2208:75c2:5f17%8]) with mapi id 15.20.2094.013; Mon, 22 Jul 2019 14:11:29 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: kaname nishizuka <kaname@nttv6.jp>, 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: AQHVMzSMCPbrTboVdUKfxcuyXDvZxqbWuDsAgAAPDoA=
Date: Mon, 22 Jul 2019 14:11:29 +0000
Message-ID: <DM5PR16MB17054921F8CC3C2C90CB6A4BEAC40@DM5PR16MB1705.namprd16.prod.outlook.com>
References: <156233245922.21720.2303446065970922340.idtracker@ietfa.amsl.com> <CAFpG3gcgpJRyLSoLkOMuUWY8pZrBPDCCz6-sc8A=1KW3GMpm+g@mail.gmail.com> <9401a258-5a32-b612-450b-10d3452777ac@nttv6.jp>
In-Reply-To: <9401a258-5a32-b612-450b-10d3452777ac@nttv6.jp>
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.16
dlp-reaction: no-action
x-originating-ip: [49.37.200.50]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3b1c683f-c027-4b51-664f-08d70eae7e22
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM5SPR00MB242;
x-ms-traffictypediagnostic: DM5SPR00MB242:
x-ms-exchange-purlcount: 8
x-microsoft-antispam-prvs: <DM5SPR00MB2422DECD054E149860ECB1FEAC40@DM5SPR00MB242.namprd16.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01068D0A20
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(39860400002)(376002)(346002)(396003)(53754006)(32952001)(199004)(22974007)(189003)(99286004)(33656002)(66066001)(14454004)(2420400007)(15650500001)(9686003)(236005)(54896002)(81156014)(186003)(81166006)(6306002)(6436002)(606006)(74316002)(110136005)(53936002)(53386004)(7696005)(53546011)(76176011)(6506007)(102836004)(55016002)(316002)(6246003)(486006)(8936002)(26005)(8676002)(476003)(478600001)(11346002)(6116002)(790700001)(68736007)(3846002)(5024004)(256004)(2906002)(7736002)(966005)(14444005)(446003)(25786009)(76116006)(66946007)(2501003)(66476007)(66556008)(66446008)(64756008)(66574012)(71200400001)(71190400001)(7110500001)(229853002)(80792005)(5660300002)(86362001)(52536014)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5SPR00MB242; 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: CyC9PmDp5el2LSsSt2SmcyzXhDyRJ+9HbLpielAkPA+I0BLnDFXYjUgc0BIDTj9tsXnrhux0vwDUv0Ctdqbvba00Mu/LQGqXjyUQ1C3jkJPYueidHSSTDJXdi69ykG+rfdYZoDb8unF/+bh7u4nRl9WiHAbOJFeN8srxtkp6plPmsdVJpzV5RL4nneOea8qdV5knu+b3lHQsKXa5EfMmPbTLfqsuZpKKlAXaJIobNv0Tn3SUl1GritJQyvOXnA4HxVceqIdF3RtmgYAqF8hZphChSqTSWIGwIKGeNjTHMH7Ov0hSaitX/L91U0Ji0j8P3NB9u62X+qe2ZuCpZ+M6qJYHSTaSpBzcdWuuT6Tahsd9XHQgYsOKVVd3dpn9+qrZaKTXxF561c7pumuv2X9nLyC83QdLfFTx71lfZuoOWEk=
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3b1c683f-c027-4b51-664f-08d70eae7e22
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jul 2019 14:11:29.8375 (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: DM5SPR00MB242
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 <6595> : inlines <7122> : streams <1828098> : uri <2870845>
X-MC-Unique: JtdDDm_DMNu7R78rA2NCaQ-1
X-Mimecast-Spam-Score: 0
Content-Type: multipart/alternative; boundary="_000_DM5PR16MB17054921F8CC3C2C90CB6A4BEAC40DM5PR16MB1705namp_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/4T7-CMjte-eeEW_g7a0A2yMtzw4>
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: Mon, 22 Jul 2019 14:11:48 -0000

Thanks Kaname for the support. I did not get the comment. what type of pre-mitigation DOTS telemetry attributes can be signaled from the DOTS server to the DOTS client ?
And How will the DOTS server know the pre-mitigation DOTS telemetry attributes relevant or associated with a DOTS client ?

Cheers,
-Tiru

From: Dots <dots-bounces@ietf.org>; On Behalf Of kaname nishizuka
Sent: Monday, July 22, 2019 6:44 PM
To: tirumal reddy <kondtir@gmail.com>;; dots@ietf.org
Subject: Re: [Dots] Fwd: New Version Notification for draft-reddy-dots-telemetry-00.txt


CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.

________________________________
I support this draft.

I'd like to mention about the telemetry attributes from a DOTS server to a DOTS client.
Currently, several transit ISPs are providing DDoS detection and protection services.
In such a service, they send a DDoS detection notification via e-mail when they noticed that their customer is under attack.
The mail includes the telemetry information such as 4.1.5. Attack Details.
This info can be used for further decision of protection strategy by the customer's security operators.
I think it should be covered by the DOTS telemetry specification.

One suggestion to the draft:
Pre-mitigation DOTS Telemetry Attributes can also be signaled from the DOTS server to the DOTS client.

thanks,
Kaname


On 2019/07/05 22:20, tirumal reddy wrote:
Hi all,

https://tools.ietf.org/html/draft-reddy-dots-telemetry-00 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<mailto: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<mailto:kondtir@gmail.com>>, Ehud Doron <ehudd@radware.com<mailto:ehudd@radware.com>>, Mohamed Boucadair <mohamed.boucadair@orange.com<mailto: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<http://tools.ietf.org>.

The IETF Secretariat



_______________________________________________

Dots mailing list

Dots@ietf.org<mailto:Dots@ietf.org>

https://www.ietf.org/mailman/listinfo/dots