Re: [Dots] I-D Action: draft-ietf-dots-signal-channel-29.txt
"Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com> Wed, 27 February 2019 07:02 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 11C6C12F19D for <dots@ietfa.amsl.com>; Tue, 26 Feb 2019 23:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 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_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 w5RhRzqRNi0S for <dots@ietfa.amsl.com>; Tue, 26 Feb 2019 23:02:13 -0800 (PST)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9BCC128B01 for <dots@ietf.org>; Tue, 26 Feb 2019 23:02:12 -0800 (PST)
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=1551250468; h=From: To:CC: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-exchange-diagnostics: x-microsoft-antispam-prvs:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-ms-exchange-senderadcheck: x-microsoft-antispam-message-info:Content-Type: Content-Transfer-Encoding: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-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=i9DIWZMdc68skmFNXjWkO908KoiZDQ36t/IljX nArHU=; b=pC/+nn/K6daP4UwjzSyp4lNsTbfaZWRyiw4zA+KW xywVLdR2LMrxV9D7/S4qEL4jPMcE61HVKXrISZnVEsP5kmeXhg l0enjulcJe9Lv9Mje53lj1rB9W8hEgO3jNB43hD+JuvA1Vub61 wCKw2qR2sKHRdoTVJZ00Tz9hSAGcov8=
Received: from DNVEXAPP1N05.corpzone.internalzone.com (unknown [10.44.48.89]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 6336_40f7_31d8d591_0254_4daf_a636_b1028b5544f4; Tue, 26 Feb 2019 23:54:27 -0700
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; Tue, 26 Feb 2019 23:56:27 -0700
Received: from DNVO365EDGE1.corpzone.internalzone.com (10.44.176.66) by DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 26 Feb 2019 23:56:27 -0700
Received: from NAM02-CY1-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; Tue, 26 Feb 2019 23:56:26 -0700
Received: from BYAPR16MB2790.namprd16.prod.outlook.com (20.178.233.91) by BYAPR16MB2614.namprd16.prod.outlook.com (20.177.227.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.18; Wed, 27 Feb 2019 06:56:26 +0000
Received: from BYAPR16MB2790.namprd16.prod.outlook.com ([fe80::9c48:452b:e39c:ef39]) by BYAPR16MB2790.namprd16.prod.outlook.com ([fe80::9c48:452b:e39c:ef39%2]) with mapi id 15.20.1643.022; Wed, 27 Feb 2019 06:56:26 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
CC: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-signal-channel-29.txt
Thread-Index: AQHUysO2BSyTdnM0Qka7k+Ykw8xjSaXr/0pggAY1FWCAAQcR8A==
Date: Wed, 27 Feb 2019 06:56:25 +0000
Message-ID: <BYAPR16MB2790E0DAA102D11B54ED23D4EA740@BYAPR16MB2790.namprd16.prod.outlook.com>
References: <155084937056.5323.18401033305053602209@ietfa.amsl.com> <DM6PR16MB27941968A6A96F37C8A64E32EA7F0@DM6PR16MB2794.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302EA25825@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302EA25825@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.2.0.6
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com;
x-originating-ip: [103.245.47.20]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 22087120-ea7e-43a9-e3f5-08d69c80b12b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:BYAPR16MB2614;
x-ms-traffictypediagnostic: BYAPR16MB2614:
x-ms-exchange-purlcount: 5
x-microsoft-exchange-diagnostics: 1;BYAPR16MB2614;23:l2McF8BISg/+aTPDWvxPezaC08vowK0Z2vur15UUF5+yZa8pZURSBph+vqF4m9M6599jZRYTJaJhZXDb/RrEjKmNk+nNdNynMIrgN//ibeEwRDeCYFR//8Aj4g1j2z80xfEeEuNr4KzDT/oZ6QWuhjyXE6uk5wPUEC4tsPrQoGEF6kvEXWheaTSNMplzTc0pQCd4e0Q8sd6FL8Vvn7hYr+bx595iWO7gC1bbDIuwzvKzSAZXKLeZczuZfR/M6NU6cjx0TzRAZDv5FMyneAZDx5/upt48pPwUD4HxtCaTSlK0VJx4hn5OBBtisJAHVUkWvALa78zUYjqToIsZo/D0dVOIqoHIw8G731TjcxANYXLkK462xqinY/LkwvgAH2Tzq4zs2TJGUNJmaaABYuc17CtZew6t6S5S0Zs7lql08BUcfnszmuTVw1u/sAbw7mcHsEmm11fpz/+P9EiDtiuTB1zKQA+6q0pKSPT4Nk8oVy6E4bWg8NdAqywsQUVCOF7ReeZAbQosGHFfTMR7Jg/YYhBKyjwVfD2uTlmkLoP8rWeH/6WKLZPxNhvEnYCAG8U2WERDNOGgUVdU77khQHThD0sTPgIf3RADinhmUQuFU/GzAhNmmh9Ows0FlH9s7lhCkImNOY5NaCdiFDKNxc/bLxDg5D4lHn0Xy4R8ZrV3abC+eAvu4wVJPfcSI7nAiECt7vy+BuYKrwDt7GhU9d4/zJ/aGcUjiutJ7mzds22f+Qq5i2fFsRRKHDdcf22ZYfux2p6ZZPOl8k91K1rIDQAJ10NlFrU1Gt5yW2Sh/3Kn5WsvRpL4si8tu5sCJcD6Z5GM+ts03wuN13TbZyVbHmd6B4OE17F7Q1tFdnpP2qC/rYNavStPHQazBZl9xvAgk2ZfxM5LwUwgXdiOUC5oPxtL9X9Nne9HyaV/5dkaeryyYby9KxdQWNQ6nw08eB6cnkpbOGlMyeSmThF72ugQn8LxlkNx8vqIAH1DLFbQzQAXOkvenb+zr5UeeEWDzgQV+H9ZwTvzepz/BL9EncrlPmQxBOorSlFCKZ3n9nPXLP6FYLv+Tu4GvA0gwHE41T2RozIPL1XfmYNX+WxDmuPtv5B/rfjixAzQDTujJ7/EbN01zOUZh0/nbsVOCAYnx4vup5BfMUq7cKvZG4hUkJNm3MZwpUkHPA2TqlAFosoZ/WxSHEWLV27s3bqoOjm9g1vr4vyVWqCJhBT+6IQ+STrow9i1h4jXn/5LqfUndJXQlg1PmoFN85NGBT9KeWPq6ZjdN2tzWAtqOurhlwwziCJJubWab07QHu4gTeCQAb1puSFhAtSasP3vzk6rrEY0+7d6KFEZen/LizvNzhBpIYRGj+9NwCIcfSTldSemqxQ8ed7NtjPMGvdu8S2FO2qt4/FaAgWDsSHnwYyybAfYlSYbuTlEwdASN+Mhl0CohCrRNdIyxU7TiZ4yg9/ygnWS9tajQ+Lg7GTpdCXqVAY3HCw3K4JmoQ==
x-microsoft-antispam-prvs: <BYAPR16MB2614048CE4BA828F0748BE03EA740@BYAPR16MB2614.namprd16.prod.outlook.com>
x-forefront-prvs: 0961DF5286
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(366004)(136003)(346002)(396003)(39860400002)(13464003)(32952001)(189003)(199004)(53936002)(66574012)(5024004)(6306002)(256004)(9686003)(68736007)(52536013)(229853002)(25786009)(66066001)(8936002)(5640700003)(55016002)(99286004)(6436002)(478600001)(14454004)(966005)(71190400001)(72206003)(71200400001)(26005)(5660300002)(2501003)(4326008)(7696005)(33656002)(53546011)(102836004)(76176011)(3846002)(6116002)(6506007)(6916009)(186003)(14444005)(476003)(106356001)(2351001)(11346002)(446003)(316002)(486006)(80792005)(305945005)(81166006)(74316002)(7736002)(105586002)(81156014)(8676002)(86362001)(2906002)(97736004)(6246003)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR16MB2614; H:BYAPR16MB2790.namprd16.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: HR4rum2vSnUPs6+4s2/7mYxtq0XNUy631SZFycftRkZpLhEkiBUqElwYC4p3apPWAx+Vu3NRdrY0VeXoz+j6EZkfjfrjrZGLT3sHhzrqC8aEsVUbkzK+2Lny//7cmH3Zf2Nd0r3Sydcoy6k0QzBr6sA0AC0g+Sh5CEbfuUiD2HrnU0RMFg4iOwteWfb41gU2DskCBfJI/ilu5MxDexnXwgxC3dP15U4XXpFUhEHqh8NsKUe3MW06oIe5djklC4jBVp9RQ4+wM1pT6mb9zOGoClxJkaP0T6LR76JT/JHzovW1Z1sl/ot0sgfajhKpUAwux/J7u43UP9GI1+KTu6CSb1uXi/gxlpuiaxgDOL1xFCS8RfFuuBnxG8BKSPjMnWpLSd2LkWCYYYdEXNoGMTYRQE7pO1d1SGS3g6im46p4ZSU=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 22087120-ea7e-43a9-e3f5-08d69c80b12b
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2019 06:56:26.0103 (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-Transport-CrossTenantHeadersStamped: BYAPR16MB2614
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Level:
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0.1
X-NAI-Spam-Version: 2.3.0.9418 : core <6491> : inlines <7024> : streams <1814228> : uri <2802937>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/Q_a25Y_wX0VHAOFaGr321u6HdZA>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-signal-channel-29.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: Wed, 27 Feb 2019 07:02:15 -0000
Hi Med, Please see inline > -----Original Message----- > From: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com> > Sent: Tuesday, February 26, 2019 8:42 PM > To: Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@McAfee.com> > Cc: dots@ietf.org > Subject: RE: [Dots] I-D Action: draft-ietf-dots-signal-channel-29.txt > > > > Hi Tiru, > > Please see inline. > > Cheers, > Med > > > -----Message d'origine----- > > De : Dots [mailto:dots-bounces@ietf.org] De la part de Konda, > > Tirumaleswar Reddy Envoyé : vendredi 22 février 2019 17:20 À : > > dots@ietf.org; i-d-announce@ietf.org Objet : Re: [Dots] I-D Action: > > draft-ietf-dots-signal-channel-29.txt > > > > Hi Med, > > > > Couple of Nits: > > > > 1) > > OLD: > > Likewise, 'sid' value is > > monotonically increased by the DOTS client for each configuration > > session, attackers replaying configuration requests with lower numeric > > 'sid' values will be rejected by the DOTS server if it maintains a > > higher numeric 'sid' value for this DOTS client. > > > > NEW: > > Likewise, 'sid' value is > > monotonically increased by the DOTS client for each configuration > > request, attackers replaying configuration requests with lower numeric > > 'sid' values will be rejected by the DOTS server if it maintains a > > higher numeric 'sid' value for this DOTS client. > > > > [Med] OK for s/session/request. > > > 2) > > Define 'idle' time (i.e. when no attack traffic is present). > > [Med] This one is not needed, IMHO. We do already have the following in the > draft: > > The same or distinct configuration sets may be used during times when > ^^^^^^^^^^ > a mitigation is active ('mitigating-config') and when no mitigation > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > ^^^^ > is active ('idle-config'). This is particularly useful for DOTS > ^^^^^^^^^^^^^^^^^ The above lines do not define the term 'idle'. We just have to append "(i.e. when no attack traffic is present)" to 'idle' time. Cheers, -Tiru > servers that might want to reduce heartbeat frequency or cease > heartbeat exchanges when an active DOTS client has not requested > mitigation. If distinct configurations are used, DOTS agents MUST > follow the appropriate configuration set as a function of the > mitigation activity (e.g., if no mitigation request is active, 'idle- > config'-related values must be followed). Additionally, DOTS agents > MUST automatically switch to the other configuration upon a change in > the mitigation activity (e.g., if an attack mitigation is launched > after an 'idle' time, the DOTS agent switches from 'idle-config' to > 'mitigating-config'-related values). > > > > > -Tiru > > > > > -----Original Message----- > > > From: Dots <dots-bounces@ietf.org> On Behalf Of > > > internet-drafts@ietf.org > > > Sent: Friday, February 22, 2019 9:00 PM > > > To: i-d-announce@ietf.org > > > Cc: dots@ietf.org > > > Subject: [Dots] I-D Action: draft-ietf-dots-signal-channel-29.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. > > > > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > directories. > > > This draft is a work item of the DDoS Open Threat Signaling WG of the IETF. > > > > > > Title : Distributed Denial-of-Service Open Threat > > Signaling (DOTS) > > > Signal Channel Specification > > > Authors : Tirumaleswar Reddy > > > Mohamed Boucadair > > > Prashanth Patil > > > Andrew Mortensen > > > Nik Teague > > > Filename : draft-ietf-dots-signal-channel-29.txt > > > Pages : 99 > > > Date : 2019-02-22 > > > > > > Abstract: > > > This document specifies the DOTS signal channel, a protocol for > > > signaling the need for protection against Distributed Denial-of- > > > Service (DDoS) attacks to a server capable of enabling network > > > traffic mitigation on behalf of the requesting client. > > > > > > A companion document defines the DOTS data channel, a separate > > > reliable communication layer for DOTS management and configuration > > > purposes. > > > > > > Editorial Note (To be removed by RFC Editor) > > > > > > Please update these statements within the document with the RFC > > > number to be assigned to this document: > > > > > > o "This version of this YANG module is part of RFC XXXX;" > > > > > > o "RFC XXXX: Distributed Denial-of-Service Open Threat Signaling > > > (DOTS) Signal Channel Specification"; > > > > > > o "| [RFCXXXX] |" > > > > > > o reference: RFC XXXX > > > > > > Please update this statement with the RFC number to be assigned to > > > the following documents: > > > > > > o "RFC YYYY: Distributed Denial-of-Service Open Threat Signaling > > > (DOTS) Data Channel Specification (used to be I-D.ietf-dots-data- > > > channel) > > > > > > Please update TBD/TBD1/TBD2 statements with the assignments made by > > > IANA to DOTS Signal Channel Protocol. > > > > > > Also, please update the "revision" date of the YANG modules. > > > > > > > > > The IETF datatracker status page for this draft is: > > > https://datatracker.ietf.org/doc/draft-ietf-dots-signal-channel/ > > > > > > There are also htmlized versions available at: > > > https://tools.ietf.org/html/draft-ietf-dots-signal-channel-29 > > > https://datatracker.ietf.org/doc/html/draft-ietf-dots-signal-channel > > > -29 > > > > > > A diff from the previous version is available at: > > > https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-signal-channel-29 > > > > > > > > > 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. > > > > > > Internet-Drafts are also available by anonymous FTP at: > > > ftp://ftp.ietf.org/internet-drafts/ > > > > > > _______________________________________________ > > > 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] I-D Action: draft-ietf-dots-signal-channel… internet-drafts
- Re: [Dots] I-D Action: draft-ietf-dots-signal-cha… Konda, Tirumaleswar Reddy
- Re: [Dots] I-D Action: draft-ietf-dots-signal-cha… mohamed.boucadair
- Re: [Dots] I-D Action: draft-ietf-dots-signal-cha… Konda, Tirumaleswar Reddy
- Re: [Dots] I-D Action: draft-ietf-dots-signal-cha… mohamed.boucadair
- Re: [Dots] I-D Action: draft-ietf-dots-signal-cha… Konda, Tirumaleswar Reddy