IETF Logo Mail Archive

Re: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server

"Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com> Wed, 05 September 2018 10:38 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 C7A62130DC5 for <dots@ietfa.amsl.com>; Wed, 5 Sep 2018 03:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level:
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 e-uP6sanS5_F for <dots@ietfa.amsl.com>; Wed, 5 Sep 2018 03:38:04 -0700 (PDT)
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 86A7C124BE5 for <dots@ietf.org>; Wed, 5 Sep 2018 03:38:04 -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=1536143895; h=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:x-originating-ip: x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-ms-exchange-senderadcheck:x-exchange-antispam-report-cfa-test: x-forefront-prvs:x-forefront-antispam-report: received-spf:authentication-results:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: 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-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=1KxZTys9VKX4J8e+AMx8yuVdZWFvwda6+9AoEM c4BmE=; b=BW7APkUhUuLuB8PfobX5/43wu8rASM1ETDalM4Ta FcBE+sAnP8NX528lmhhRgbjtYeE0NOSoEXwTfl0D3tMhCFpPwt 45ZZ01JMlil8i+mECFLX3EYvC1gpDqlYosdUYvoypKXgPpyf5R p0ztkp5CT7a3ZiemEcZZ5ZcX7dE5xNc=
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 18cf_7b78_9c9c8dd5_0e16_4127_b692_0a567089094b; Wed, 05 Sep 2018 05:38:14 -0500
Received: from DNVEXUSR1N08.corpzone.internalzone.com (10.44.48.81) by DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 5 Sep 2018 04:37:56 -0600
Received: from DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) by DNVEXUSR1N08.corpzone.internalzone.com (10.44.48.81) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 5 Sep 2018 04:37:55 -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.1347.2 via Frontend Transport; Wed, 5 Sep 2018 04:37:55 -0600
Received: from NAM02-SN1-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.1347.2; Wed, 5 Sep 2018 04:37:53 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1474.namprd16.prod.outlook.com (10.172.207.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1101.18; Wed, 5 Sep 2018 10:37:51 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::a14e:458f:4a71:ef35]) by BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::a14e:458f:4a71:ef35%6]) with mapi id 15.20.1101.016; Wed, 5 Sep 2018 10:37:51 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: Jon Shallow <supjps-ietf@jpshallow.com>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server
Thread-Index: AdRFAu54VN0AjTquSDWy2o8cWBv6OwAAL20g
Date: Wed, 05 Sep 2018 10:37:51 +0000
Message-ID: <BN6PR16MB14255336A8BCE46C9BBAD404EA020@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <006401d44502$eedc4090$cc94c1b0$@jpshallow.com>
In-Reply-To: <006401d44502$eedc4090$cc94c1b0$@jpshallow.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.0.500.52
dlp-reaction: no-action
x-originating-ip: [103.245.47.20]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1474; 6:sg52fmWzPvDKUExZeLqfb/2RCii+FMrBrcU8dYUB27HQug6iBm8JkvPAviPzLwIR5iLrl/kVyLznDKsup/bZCJH9+UN9rwkfL0nFKBjeVs2zUAGhlL5xUWaXSd2QcgPVVeCBrkyg8mWUNbmVgTURUT2RCv6yRtMMoJ0PrxSZNMLLOZ7H9rz62dWaoewl/g0OVECrT9tGzeEF0CIIYw6B7fIEA0sYkbSAbmYqIf/ya5YigEp0NU+cPhouVloXEMlO7EMH5DgHuWqz0FEMOJp2979DxOiQ8FCV93VshlVKUrAvPWLSTcDMpzL3iZ9w64sYT1jd5xo1LRQlx7uOApODt04Blvq2fe6euFkNOaaDHUv0UVo8R2dpFnSP9eAFrHStBxs2FC7d46E/BVsAswwVrgREGuUMOV6CQhLCNxuuhFWs3nwUDwWTasE8s8/JpQU1XFPqOs1XwhnB4TOqM17Thg==; 5:W3Ld/jXVfQYxyrbnejXJ0C3+AHJs17fvkuUMezLijXPsR+dVdq3Jb7TGodDGxH26B6Eo+vKRMcqeB3Fgt/mi1FOzThF53tbusJCSF/1NXuXbA5Ztb+NFhfVnrgOq7KIvK3XNe+rg6VaE+ewXtVW4epM0w8dkYNt1jDRE0qkAP+M=; 7:8h5M8a7UgZDrn5XomDqrxzsL+HlMVN7CfBdWvAKvqtRma/9kxbxRNL5OgXiCzZtPEfz7RR7+v76Feb72m/jMAE21e+ZX3JRNBY5IRSGYdXLQ/uHscpiCMe9SBaXJjiwg+zXt7HKN1lxlBQHtlsDiEH+4oJK29OeBz0xV+bFd1NjMqOgfptjJ87fWk+JAUMwKqyEDOWodB8RePZJwkU3vuS6jChvbaIk2F13M75x2ly34DEPvx88wKCAMHA9geyul
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 034179ac-1f4d-453b-d087-08d6131ba1a5
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1474;
x-ms-traffictypediagnostic: BN6PR16MB1474:
x-microsoft-antispam-prvs: <BN6PR16MB1474F40845EDDCB67C8DE907EA020@BN6PR16MB1474.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(103651359005742)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(3231344)(944501410)(52105095)(10201501046)(149027)(150027)(6041310)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(201708071742011)(7699016); SRVR:BN6PR16MB1474; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1474;
x-forefront-prvs: 078693968A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(136003)(39860400002)(366004)(396003)(199004)(189003)(32952001)(53936002)(68736007)(74316002)(476003)(8936002)(5024004)(14444005)(256004)(186003)(6346003)(446003)(11346002)(26005)(102836004)(80792005)(229853002)(6506007)(53546011)(6436002)(97736004)(6246003)(9686003)(8676002)(478600001)(19609705001)(25786009)(54896002)(6306002)(55016002)(72206003)(66066001)(86362001)(14454004)(110136005)(5660300001)(2900100001)(7696005)(2906002)(316002)(81166006)(81156014)(99286004)(5250100002)(6116002)(3846002)(106356001)(790700001)(76176011)(105586002)(33656002)(2501003)(7736002)(486006)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1474; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com;
x-microsoft-antispam-message-info: 8EFyX6xWzC8Ywxy3U16OgrMWnqj+J6FdXtuo3e0+3yJWwjcsCfsvk5rYdomILK4a7SYUA6OgMTH52JyCAhBIMG5tiHULEICehsfg8KHxb9BNtBdoNQB5a/4yJFWIdJJQJMJGHZeyeL7j2M47aC6Q1Njp7wcEpbykSWMGpRltw3SaLe9nAwgV59gGT5kaEcPrh8CYLDtlL2rxV4K6Gt8npwn6ScYP5nrjSHLySkyzg+dY8OMy8x1fJhTqDDg7xqdRm913Yh9wtaIeuHIK02LQZeSSwxaXq74n85IG3fm9vnKIvr2yt6wKJKUBsgSyq9UGWmThQ06ukMBJfJLAB2rKMN/QxmgUwk0YHRdU59BwAoM=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN6PR16MB14255336A8BCE46C9BBAD404EA020BN6PR16MB1425namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 034179ac-1f4d-453b-d087-08d6131ba1a5
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Sep 2018 10:37:51.4515 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1474
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 <6366> : inlines <6854> : streams <1797558> : uri <2703496>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/947OgCJTX4bhfdTG4aQvd8XsR7g>
Subject: Re: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server
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, 05 Sep 2018 10:38:07 -0000

Manual configuration creates conflicts with the DOTS protocols (just like the conflicts network devices would face if configured using both SDN and manual configuration) and I guess should be avoided.

-Tiru

From: Dots <dots-bounces@ietf.org> On Behalf Of Jon Shallow
Sent: Wednesday, September 5, 2018 3:57 PM
To: dots@ietf.org
Subject: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server


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


________________________________
Hi There,

When there is a manual configuration on the DOTS server of an alias by an operator, not created by the DOTS client, what should happen if the DOTS client tries to delete the alias?

The DOTS client will see the alias in a GET request for all aliases (as it is entitled to use it)

Returning a 404 (Not Found) could be confusing

Returning a 204 (No Content) is not right as it has not been deleted per se.

Should the alias in the GET response be marked as permanent (or some equivalent)?

The same is true for ACLs

Regards

Jon

v2.23.0 | Report a Bug | By Email