Re: [Dots] Close of WGLC for Requirements Draft

"Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com> Mon, 18 June 2018 07:04 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 B032B130DE6 for <dots@ietfa.amsl.com>; Mon, 18 Jun 2018 00:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.81
X-Spam-Level:
X-Spam-Status: No, score=-3.81 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_ABOUTYOU=0.5, 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 oN9DdT12pFLv for <dots@ietfa.amsl.com>; Mon, 18 Jun 2018 00:04:34 -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 5180C127598 for <dots@ietf.org>; Mon, 18 Jun 2018 00:04:33 -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=1529305477; 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-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=oXXmzFLCGgCEmJQxsV0oEQeRZ6PL74qe9zheFS MVZ5Y=; b=ebnano2yCnHNxiHG3kq9MMayZraAnkz6mPQqRDsL dp2SkK/3R6HqLXuZfVddzkxaJoKj3i6HJG4DzZnOPxs22GS/wv XqMRmH/3HW3h/NGeTYkx/UnT1md/K21AJ8HM+ZTqO5DgX7Li2E hcXxL/3wIhQVMRTMBTcce7qfvoX7cvs=
Received: from DNVEXAPP1N04.corpzone.internalzone.com (unknown [10.44.48.88]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 7f16_9430_c3cb1f25_5e34_4b57_82dc_02ee586f2275; Mon, 18 Jun 2018 02:04:37 -0500
Received: from DNVEXUSR1N08.corpzone.internalzone.com (10.44.48.81) by DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 18 Jun 2018 01:04:26 -0600
Received: from DNVEXUSR1N10.corpzone.internalzone.com (10.44.48.83) by DNVEXUSR1N08.corpzone.internalzone.com (10.44.48.81) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 18 Jun 2018 01:04:26 -0600
Received: from DNVO365EDGE1.corpzone.internalzone.com (10.44.176.66) by DNVEXUSR1N10.corpzone.internalzone.com (10.44.48.83) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Mon, 18 Jun 2018 01:04:25 -0600
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.1347.2; Mon, 18 Jun 2018 01:04:24 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1522.namprd16.prod.outlook.com (10.172.208.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.863.14; Mon, 18 Jun 2018 07:04:22 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::1561:ac68:679c:204e]) by BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::1561:ac68:679c:204e%2]) with mapi id 15.20.0863.016; Mon, 18 Jun 2018 07:04:22 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Tobias Gondrom <tobias.gondrom@gondrom.org>, "dots@ietf.org" <dots@ietf.org>
CC: 'Roman Danyliw' <rdd@cert.org>
Thread-Topic: [Dots] Close of WGLC for Requirements Draft
Thread-Index: AdP50ZtalkXGKdzwSuivtFip3vbzCwJHN88wABkEoIAAGE7OEAACSRXQAMVmvsA=
Date: Mon, 18 Jun 2018 07:04:22 +0000
Message-ID: <BN6PR16MB14257BCDA6FC7BAE6CDD1748EA710@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <02a601d3f9d2$aa115f70$fe341e50$@gondrom.org> <787AE7BB302AE849A7480A190F8B93302DF356BF@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <030401d40352$8f3ba780$adb2f680$@gondrom.org> <BN6PR16MB142525D498236C50D6BD1D05EA7D0@BN6PR16MB1425.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302DF44497@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302DF44497@OPEXCLILMA3.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.0.300.84
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com;
x-originating-ip: [134.191.232.93]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1522; 7:TqWYSWoLC/UZghGr/yajZKa4KrDdwh0fKrXeA7QVWL8C6B7/ZPYW31XtG4NAAOzGisk81dmoun82ZsMeDGAytlRzCti3FS8sIpc8/G+b+ZjIqpoxKu32d9L+cGEGs879ikq95kg6xEW8chq7tsfYrmAepNzR3p/JX5DtasZNIYqkW0e9XJfX74Fhti27aQPNkE2NROCdIz+XON9ybQ+4QQ+sHgsAlBnRpbLW4oBAaCAGNNliPDmwc3w7w4HKj0Rg
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 26f06648-b606-4274-aa76-08d5d4e9b826
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(711020)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1522;
x-ms-traffictypediagnostic: BN6PR16MB1522:
x-microsoft-antispam-prvs: <BN6PR16MB1522F47AD7A428813BDC9E4AEA710@BN6PR16MB1522.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(120809045254105)(18271650672692)(21748063052155)(123452027830198);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123562045)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:BN6PR16MB1522; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1522;
x-forefront-prvs: 0707248B64
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39850400004)(346002)(376002)(366004)(39380400002)(85644002)(189003)(199004)(32952001)(52564003)(105586002)(6246003)(236005)(110136005)(7696005)(76176011)(25786009)(9686003)(72206003)(53936002)(86362001)(4326008)(7736002)(33656002)(81166006)(3660700001)(966005)(8676002)(106356001)(316002)(2906002)(478600001)(229853002)(14454004)(81156014)(3280700002)(8936002)(606006)(3846002)(68736007)(66066001)(93886005)(97736004)(80792005)(790700001)(5890100001)(2501003)(476003)(6436002)(5250100002)(11346002)(74316002)(5660300001)(99286004)(486006)(6306002)(54896002)(55016002)(2900100001)(26005)(102836004)(186003)(446003)(59450400001)(6506007)(53546011)(6116002)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1522; 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: dmUHpLj4pb6dqp8EqqPEY6POLe4v/Big2veT/eK8Qp6A+2TLUvU6upoRmw5GpvaLY3ipksteUK/YLzo0WolOlWZ3GGq2a41b/wWtIbiqKS/vQ3234kDWzTptzc6+fxU7oq6cH6IFIbDuhekZzUlimv+b7jUGB7rshMa+FOpxYMjzkNX8FD82Ns/kdyYRuICFDlHln367iW6DfWu/bkuF8w==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN6PR16MB14257BCDA6FC7BAE6CDD1748EA710BN6PR16MB1425namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 26f06648-b606-4274-aa76-08d5d4e9b826
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jun 2018 07:04:22.4152 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1522
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 <6309> : inlines <6702> : streams <1790018> : uri <2660091>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/q6czvYHdhhWFwvMJHgnvOMWNnow>
Subject: Re: [Dots] Close of WGLC for Requirements Draft
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.26
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, 18 Jun 2018 07:04:38 -0000

Thanks Med for the clarification.

-Tiru

From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
Sent: Thursday, June 14, 2018 11:57 AM
To: Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@McAfee.com>; Tobias Gondrom <tobias.gondrom@gondrom.org>; dots@ietf.org
Cc: 'Roman Danyliw' <rdd@cert.org>
Subject: RE: [Dots] Close of WGLC for Requirements Draft


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


________________________________
Hi Tiru,

An early yang doctors review can be requested, but this is not required.

I recall a discussion I had with Benoit Claise (for another draft) who was the Ops AD:
https://mailarchive.ietf.org/arch/msg/opsawg/H5GvTsu6Vxl91glTRiACfAMWDhA

His conclusion works with s/OPSAWG/DOTS as well :

==
Bottom line: if the OPSAWG chairs believe this document is ready, it can
progress to IETF LC now.
==

Cheers,
Med

De : Konda, Tirumaleswar Reddy [mailto:TirumaleswarReddy_Konda@McAfee.com]
Envoyé : jeudi 14 juin 2018 09:48
À : Tobias Gondrom; BOUCADAIR Mohamed IMT/OLN; dots@ietf.org<mailto:dots@ietf.org>
Cc : 'Roman Danyliw'
Objet : RE: [Dots] Close of WGLC for Requirements Draft

Hi Tobias,

YANG doctors review is required for the signal channel draft after the WGLC is complete (please see https://datatracker.ietf.org/group/yangdoctors/about/).

Cheers,
-Tiru

From: Dots [mailto:dots-bounces@ietf.org] On Behalf Of Tobias Gondrom
Sent: Thursday, June 14, 2018 1:40 AM
To: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>; dots@ietf.org<mailto:dots@ietf.org>
Cc: 'Roman Danyliw' <rdd@cert.org<mailto:rdd@cert.org>>
Subject: Re: [Dots] Close of WGLC for Requirements Draft


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


________________________________
Hi guys,

As far as I could see the signal draft WGLC can be closed and the raised points have been addressed.
(one caveat: I am still combing through the some left 10% of the email threads for the signal draft to check whether I missed something, so if I did, please let me know by raising it…)

As I understand that we had some further implementation works going on since IETF101, I would like to reconfirm the question towards the implementation and hackathon teams whether they found any further deviations or lack of clarity in the last few weeks since IETF101?
If not, then I think we are ready to go. I would appreciate a last “thumbs up” or any raise issues if they encountered any in the last weeks.

Thank a lot and best regards, Tobias



From: Dots <dots-bounces@ietf.org<mailto:dots-bounces@ietf.org>> On Behalf Of mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>
Sent: Wednesday, June 13, 2018 10:15 AM
To: Tobias Gondrom <tobias.gondrom@gondrom.org<mailto:tobias.gondrom@gondrom.org>>; dots@ietf.org<mailto:dots@ietf.org>
Cc: 'Roman Danyliw' <rdd@cert.org<mailto:rdd@cert.org>>
Subject: Re: [Dots] Close of WGLC for Requirements Draft

Hi Tobias,

Can you please update us about your conclusions with regards to the WGLC of signal channel?

Thank you.

Cheers,
Med

De : Dots [mailto:dots-bounces@ietf.org] De la part de Tobias Gondrom
Envoyé : vendredi 1 juin 2018 20:02
À : dots@ietf.org<mailto:dots@ietf.org>
Cc : 'Roman Danyliw'
Objet : [Dots] Close of WGLC for Requirements Draft

Dear DOTS WG team,

Thanks for your discussion and patience.
As announced a month ago, the WGLC for the requirements document is now closed.

From reading through all the emails on the mailing-list it appears to me that all open issues have been addressed so far. In case I have missed something, please let me know.

Next step will be for the ID shepherd (Frank XiaLiang was so kind to volunteer for the work task) and the chairs to prepare a shepherd document and submit the document to the IESG for LC.

Thanks and best regards, Tobias


Ps.: over the weekend, I will also review the status for the other WG documents and come back to you on that beginning of next week.