IETF Logo Mail Archive

Re: [Dots] WGLC Signal: mid=123 then overlapping mid=122

"Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com> Mon, 06 August 2018 08: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 92849127598 for <dots@ietfa.amsl.com>; Mon, 6 Aug 2018 01:11:34 -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 OHEjWgxvMctE for <dots@ietfa.amsl.com>; Mon, 6 Aug 2018 01:11:32 -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 7626A129619 for <dots@ietf.org>; Mon, 6 Aug 2018 01:11:31 -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=1533543094; 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:authentication-results: 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: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=MVDdfnpkjjdLur4qWsbXbnMOkC8Rxiu73anukh /8Bc4=; b=WtLOjOL8YlnKQ58J8rJGFcznv9H6fX/b9ah+BZQB gwDD7A4XjwFYAjRqM+3et2WbusRwIV9zN6x4s/u6kMQ4+LHJHp HJAkuC8ZQMB1JtupowbWDyKtbbzC2XlGJuiPGEVNyfioV65fC8 sdWbMI6SabS2trlpk7LpPaLTBPuI7o4=
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 0979_3774_f9bda227_0fc2_438e_9fc7_e9de91234276; Mon, 06 Aug 2018 03:11:33 -0500
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.1347.2; Mon, 6 Aug 2018 02:11:23 -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.1347.2 via Frontend Transport; Mon, 6 Aug 2018 02:11:23 -0600
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (10.44.176.240) by edge.mcafee.com (10.44.176.74) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 6 Aug 2018 02:11:22 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1603.namprd16.prod.outlook.com (10.172.208.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1017.15; Mon, 6 Aug 2018 08:11:22 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::ede9:2a31:940:db6c]) by BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::ede9:2a31:940:db6c%11]) with mapi id 15.20.1017.019; Mon, 6 Aug 2018 08:11:22 +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] WGLC Signal: mid=123 then overlapping mid=122
Thread-Index: AdQr6majIfwWOMkbRY6FrlC5ZlsRJAAGczgwAFWwpgAAAFvLMA==
Date: Mon, 06 Aug 2018 08:11:22 +0000
Message-ID: <BN6PR16MB1425CAAC2CBB3632DE54BEFEEA200@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <05de01d42bea$66b4bed0$341e3c70$@jpshallow.com> <BN6PR16MB1425F9B6326B79073BD73710EA200@BN6PR16MB1425.namprd16.prod.outlook.com> <070401d42d5a$f62651c0$e272f540$@jpshallow.com>
In-Reply-To: <070401d42d5a$f62651c0$e272f540$@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.300.84
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com;
x-originating-ip: [185.221.69.46]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1603; 6:bqB8fO3L3NoRjwYuNYWeLc96j7RQyTpX0jXcXFXDGitRkYyMOWbZUUf+vyC3mLmlkaQMOUG4Nco1LOfD8s2hwziL5ns3+94P3F+TxdZ01JiU8hdtDBITp4SabRhnqSzcP6p1rATL0IIHnRGs7DdCNQA4JlegY15PhcJYiZuJwIvltpPD/jPiDx5iwnCRHhJcwXk6xMm4D5/feWIOHcISnGX593cJxQ5v/ojoelb85r4hLPUXP138ttzjmD4rnCPRzB1sXQj1alW7K3IKParyUoiZLi3xP/PBjrcj7/2uWvdJwzXfqHNj50vLM8uJp8lT2GsPGvv1aIsByd9G9yS9UsXOqhTxLbtTW/Kl3Zl4L0DRfcsY82QSIQq8JH6bj1JcXkm4wT3NvcKGa6DBuug4r16yZscrs/CicZJfF8AG92dgVhmqTEopApuhUxWimu898RUtIan1xKto5Wv5Swsg9A==; 5:oVzRgXNZ6gNTVEcAiYhegvrO0AOBaixaBXH+e1E6VqDIuZY0z+iPq9HZGmDULGsgXvKpQw5qKOs5zslG4PXFhXkYV30hk2uxgaFBS+OEhuTqUVjZAYYNLGToqOqHpJpMODC+F6wPEeTZtIO9HsIEqz4iDd/wRjU9HF/x4K/DlBM=; 7:ieQgC8G9XIfkHi7WojHiRjN3i56IkyGGB6QF1pt9wdsMtr4nJoue5DFmlxbrNplojBpqMdmRPfza7rDTq+bgcC+FibqPdrH99MZMxcdwYkcpmLVt4ErSJVo6+00VYUb9ZIniibjzqnPV8zMfoPIDUenCYQ6UqIQaKBddmw7tknasJWLdufLpt45qNydCBQCoJ0YbMu2O55+kkgUw5ev/MlEHtpiZeIUoy/CM78A4IZP8wMVtIeUx7uTmTcMDbEnm
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 00143a12-59d8-41aa-0b4f-08d5fb74326c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1603;
x-ms-traffictypediagnostic: BN6PR16MB1603:
x-microsoft-antispam-prvs: <BN6PR16MB16030B96631233486523AF16EA200@BN6PR16MB1603.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155)(123452027830198);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231311)(944501410)(52105095)(3002001)(10201501046)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:BN6PR16MB1603; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1603;
x-forefront-prvs: 07562C22DA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39850400004)(346002)(376002)(366004)(136003)(32952001)(189003)(199004)(2906002)(81166006)(2501003)(14444005)(256004)(106356001)(5024004)(105586002)(2900100001)(5250100002)(9686003)(229853002)(6436002)(478600001)(6246003)(53936002)(7696005)(6306002)(55016002)(54896002)(8676002)(81156014)(236005)(76176011)(8936002)(33656002)(7736002)(14454004)(97736004)(72206003)(74316002)(66066001)(68736007)(25786009)(80792005)(6506007)(446003)(19609705001)(102836004)(11346002)(186003)(26005)(110136005)(5660300001)(476003)(53546011)(86362001)(486006)(6116002)(3846002)(316002)(790700001)(99286004)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1603; H:BN6PR16MB1425.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-microsoft-antispam-message-info: 1X1w7HvVEwyegAFwx+7dTOvCPdCyKnEQTONi1N/qHFM9ViB5W7MmMnglr5+JmOlUKkzwkkBZy5v0iMFcL2Mq2wzymBwD02J+I4MNm9mrpbLGuZa51PHMit2rK95d6OZKtcP04MW9OzEx8oeMa+cDJ+/6vL9JwTjonwRLIfGYQMsJfUzRR1PcLbvBI8wPI2WyNnfcBK1T3O70wPMmgR9srrvnRb2xx/gHIpmldO6CAX3xrNawaUeQjEDHr22CadnFTBguvixUUBSqKZ2TFgyYtjVBxQ5zCHoeKuTExnDRLFBrcL188VUmwtPFZSZWDFEs9nlCygq4+6W93/FZhKXm76ndWM953VvchBpvol6MlQI=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN6PR16MB1425CAAC2CBB3632DE54BEFEEA200BN6PR16MB1425namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 00143a12-59d8-41aa-0b4f-08d5fb74326c
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Aug 2018 08:11:22.3012 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1603
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 <6344> : inlines <6797> : streams <1794695> : uri <2684692>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/Kf3E6cZOpPX_jCWUD8ehOMBg0hw>
Subject: Re: [Dots] WGLC Signal: mid=123 then overlapping mid=122
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.27
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, 06 Aug 2018 08:11:34 -0000

Inline [TR1]

From: Jon Shallow <supjps-ietf@jpshallow.com>
Sent: Monday, August 6, 2018 1:26 PM
To: Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@McAfee.com>; dots@ietf.org
Subject: RE: [Dots] WGLC Signal: mid=123 then overlapping mid=122


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


________________________________
Hi Tiru,

Please see inline Jon>

Regards

Jon

From: Dots [mailto: dots-bounces@ietf.org<mailto:dots-bounces@ietf.org>] On Behalf Of Konda, Tirumaleswar Reddy
Sent: 06 August 2018 04:08
To: Jon Shallow; dots@ietf.org<mailto:dots@ietf.org>
Subject: Re: [Dots] WGLC Signal: mid=123 then overlapping mid=122

Hi Jon,

Please see inline [TR]

From: Dots <dots-bounces@ietf.org<mailto:dots-bounces@ietf.org>> On Behalf Of Jon Shallow
Sent: Saturday, August 4, 2018 5:28 PM
To: dots@ietf.org<mailto:dots@ietf.org>
Subject: [Dots] WGLC Signal: mid=123 then overlapping mid=122


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


________________________________
Hi there,

What happens when we receive mid=123, followed by mid=122 that overlaps mid=123?

Do we put mid=122 into an active-but-terminating state?
- state 5 is not really correct here as per the description

[TR] In the previous threads we have already discussed to add new conflict-status for conflicting mitigation requests from the same DOTS client (e.g. conflict-status MSB set to 1 means conflict from different DOTS clients, MSB set to 0 means conflict from the same DOTS client).
Jon> I may have blinked, but do not recall this particular discussion about using MSB and therefor needs to get into the draft.  An alternative is to have a different variable for same/different DOTS client.

[TR1] Both options look okay, I like the MSB approach ☺

-Tiru

The mitigation request with mid=122 will be rejected with 4.09 conflict. I don’t get your comment, why put mid=122 into active-but-terminating state ?
Jon> This potential option of what to return was written before we focused in on the single case for active-but-terminating.

Do we return 4.09 conflict with an appropriate (perhaps new) conflict-status ?

[TR] Yes

- my preference, but this is not said anywhere I can find

[TR] we will update the draft.
Jon> Thanks

- should conflict-scope also include the ‘mid’ in the list (YANG)?

[TR] Yes, including mid can help troubleshooting.
Jon> Please include it in the draft.
~Jon

Do we return 4.00 (bad request)?

[TR] No.

-Tiru

- I do not really like this one as there is no indication as to why – especially of there was an out of sequence packet arrival at the DOTS server.

Regards

Jon

v2.23.0 | Report a Bug | By Email