Re: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles

"Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com> Fri, 26 July 2019 08:44 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 BE0291202DA for <dots@ietfa.amsl.com>; Fri, 26 Jul 2019 01:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level:
X-Spam-Status: No, score=-2.398 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, 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 nsQmWLe131VB for <dots@ietfa.amsl.com>; Fri, 26 Jul 2019 01:44: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 7C7F81202DE for <dots@ietf.org>; Fri, 26 Jul 2019 01:44:56 -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=1564130728; 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-Threshold: X-NAI-Spam-Score:X-NAI-Spam-Version; bh=l Sr3po6FUxplTlb2qiFW64vWGe2XB55uuu/rPb0lHD g=; b=JYsVk3falogfCAaMNPV0pVuTCEl02j3n3uCmzgrG+3BS Hq8imnPXQVjj+5mQVhDNaccLqgrLDqLkr4Ep1r0XtG9JfZWfuT +viDNz4nL7OH4Q6XxYkkVmT8nYZz62NwF5YcneIuV4JSb2lYEI 79v24C4gdKkkw2/OtP8FkGl3QhQ=
Received: from MIVWSMAILOUT1.mcafee.com (mivwsmailout1.mcafee.com [161.69.47.167]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-273-0jexgmMnO-2eU2JFv4LafQ-1; Fri, 26 Jul 2019 04:44:48 -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 2184_94d2_d780be0c_2b36_451e_9068_ab780c42d1bb; Fri, 26 Jul 2019 04:45:26 -0400
Received: from DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 26 Jul 2019 02:44:42 -0600
Received: from DNVO365EDGE1.corpzone.internalzone.com (10.44.176.66) by DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 26 Jul 2019 02:44:42 -0600
Received: from NAM01-BN3-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, 26 Jul 2019 02:44:40 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cXrT3Hjru/AqrNdovaVviLB76sP0/YKbqUWDjbjb+POQ+4hH/5oMBDjpdgY6B+mIrxfyAXP69OWc8VpI3p+wDt0HbhX0/M/Ao8bIO+1E2H426anEEEx2n7HPdXoKQH8yaEflkS/v+PGBrUkFHe5GkHZvws7zY4eF7sUPh8Q7XFcIMpIW8XDg2t7qgTplToryZh+418WtfiYKJn6KPZJq5V5PECy2GVTEMwZnRaFHq/tyBwKy3pR6+hVY0gNx7DECEk42eAtdB4i3GK15eHu0fk+drheKZLE0UN8cllxFC/7D1ZZhnbXRWVzoyhOCTmm3/jOLvY5mlaeseTS8tfAQew==
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=lSr3po6FUxplTlb2qiFW64vWGe2XB55uuu/rPb0lHDg=; b=LcG3qPKS3xM2UtWzQOahNqNVnWvtM1aELQpWIy7HcPq0iRnKwgwPaEj1/TIuub9sDqPIiAM5peTOZKvaZFV/tHLWUN1Qg5zDPzbnDd0QL9j92P8rYUHoospkQ2VqOesOhAcydVS3K4Z1Kjn0bzF7eBpjprDEwwEOCK5N6hpJKoWs8nao3PTwxTTZDjljLnMvPnpPKL/TQ1p9plCORyL4TE3wP1RT8TelpWpvGetWmN4gQWTfg4hEmriHmAmm1lXvfjkIubuYqvDy4IewzeprP7arsYBt351pStqjSqLfVD7gMDO2S2uy3uHWEWOo5qdrw60kn4hhwH9NBSIlw2CRhg==
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 DM5PR16MB1451.namprd16.prod.outlook.com (10.173.212.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.14; Fri, 26 Jul 2019 08:44:39 +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.2115.005; Fri, 26 Jul 2019 08:44:39 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Valery Smyslov <smyslov.ietf@gmail.com>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles
Thread-Index: AdVC85i4bFch/Zy8RxyBqvTQ1hxRMAADwJ6AAB/YkwAAAtugEA==
Date: Fri, 26 Jul 2019 08:44:39 +0000
Message-ID: <DM5PR16MB17050CF9AF89A83E5425C4A5EAC00@DM5PR16MB1705.namprd16.prod.outlook.com>
References: <787AE7BB302AE849A7480A190F8B9330312E88FA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <01db01d54302$9bef3b40$d3cdb1c0$@gmail.com> <787AE7BB302AE849A7480A190F8B9330312E9380@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B9330312E9380@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: [103.245.47.20]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6c81488c-041f-4b45-f758-08d711a57f4e
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM5PR16MB1451;
x-ms-traffictypediagnostic: DM5PR16MB1451:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <DM5PR16MB1451245E2B71BE4F01D6ABEFEAC00@DM5PR16MB1451.namprd16.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01106E96F6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(396003)(136003)(346002)(366004)(39860400002)(32952001)(189003)(199004)(110136005)(26005)(5660300002)(71200400001)(71190400001)(14454004)(790700001)(54896002)(6306002)(6116002)(3846002)(2906002)(86362001)(186003)(66446008)(64756008)(66556008)(66476007)(229853002)(76176011)(66066001)(53546011)(99286004)(25786009)(6506007)(52536014)(8676002)(81166006)(81156014)(33656002)(606006)(102836004)(2501003)(55016002)(80792005)(966005)(478600001)(8936002)(6246003)(5024004)(256004)(316002)(7696005)(7736002)(74316002)(236005)(66946007)(9686003)(76116006)(53936002)(486006)(11346002)(446003)(68736007)(476003)(6436002)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR16MB1451; H:DM5PR16MB1705.namprd16.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: qbJc7Ld1cfPEkQoXk9qOAcEB165nNdQRk/LgGUkrMprBlT7FMlmdramMRb6Nz9UU6NkmVk/rJPTVG8TmMCXXmy4qVvg82sWMiFZW9nz4Q/yIqliOZBUHb1UqlHyalCzE7oLYMCVWwN5XWWvaVqFh27QM4228B4Wdz9DCHhIKiOewXC1vdj+rZopBOhH1UXWFhxEXtWdnb/BiygDsitT8pWQPRIDA7z8kxK0eayqU3Al3Btwl7TV8kVyHnh6k4FKDbhGu1b9EWmMLgqxT/rTsq6J2Ecg2xUV9j6iK0z8KmgXiVSpytxE4OTAOihzVnAtc/6O735bhxRmzzdFs67n9uP28THmp9+FkJR9TLfE3DSotMB+VGb8D+ywilLauVRh6+vNS5/yGH1WzQTnMeRKx53XvlqHMOGD/SJKJ7HCDoKI=
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6c81488c-041f-4b45-f758-08d711a57f4e
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2019 08:44:39.7420 (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: DM5PR16MB1451
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0
X-NAI-Spam-Version: 2.3.0.9418 : core <6598> : inlines <7127> : streams <1828459> : uri <2872927>
X-MC-Unique: 0jexgmMnO-2eU2JFv4LafQ-1
X-Mimecast-Spam-Score: 0
Content-Type: multipart/alternative; boundary="_000_DM5PR16MB17050CF9AF89A83E5425C4A5EAC00DM5PR16MB1705namp_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/6ppZ4bKd9TdiIuTWmYaKYrocfU4>
Subject: Re: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles
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, 26 Jul 2019 08:45:00 -0000

I don’t see any such terminology used in other specifications like https://tools.ietf.org/html/rfc8071. Why do we need “Call Home” prefix even after the text clarifies the roles clearly ?
If we go with this change all the figures needs to modified, and these terms need to be defined before being used.

Cheers,
-Tiru

From: Dots <dots-bounces@ietf.org> On Behalf Of mohamed.boucadair@orange.com
Sent: Friday, July 26, 2019 12:46 PM
To: Valery Smyslov <smyslov.ietf@gmail.com>; dots@ietf.org
Subject: Re: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles


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

________________________________
Hi Valery,


We didn’t consider the use of new terms because we thought this may be interpreted as if we are defining new DOTS roles (which we don’t).



The text uses “in the call home scenario” to make that distinction in some places, but I understand this may not be sufficient.



I’m OK to go with “Call Home DOTS *”. I updated the terminology section with the following:



   DOTS agents involved in the DOTS Call Home adhere to the DOTS roles

   as defined in [RFC8612].  For clarity, this document uses "Call Home

   DOTS client" (or "Call Home DOTS server") to refer to a DOTS client

   (or DOTS server) deployed in a Call Home scenario.



and changed the text when it makes sense. The full diff is available at:



https://github.com/boucadair/dots-call-home/blob/master/wdiff%20draft-ietf-dots-signal-call-home-04.txt%20draft-ietf-dots-signal-call-home-05.pdf



candidate -05: https://github.com/boucadair/dots-call-home/blob/master/draft-ietf-dots-signal-call-home-05.txt



Please let us know if this is better.



Thank you.



Cheers,

Med

De : Valery Smyslov [mailto:smyslov.ietf@gmail.com]
Envoyé : jeudi 25 juillet 2019 18:04
À : BOUCADAIR Mohamed TGI/OLN; dots@ietf.org<mailto:dots@ietf.org>
Objet : RE: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles

Hi Med,

thank you for adding this section, it really helps.
However, I was asking for more - did you consider
changing the terminology in such a way, that
Call Home use case is not mixed with basic DOTS use case?

For example, calling entities not just DOTS Client and DOTS
Server, but say Call Home DOTS Client and Call Home DOTS Server?
(actually I don't like these ad hoc names, probably you can invent better term)..

Regards,
Valery.


From: Dots <dots-bounces@ietf.org<mailto:dots-bounces@ietf.org>> On Behalf Of mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>
Sent: Thursday, July 25, 2019 5:17 PM
To: dots@ietf.org<mailto:dots@ietf.org>
Subject: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles

Re-,

There was a comment raised during the meeting asking to further clarify the role of the various DOTS agent in the call home. We added an new section to address this comment: https://tools.ietf.org/html/draft-ietf-dots-signal-call-home-04#section-1.4

Cheers,
Med