Re: [Dots] 答复: Protocol Action: 'Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification' to Proposed Standard (draft-ietf-dots-signal-channel-41.txt)

"Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com> Wed, 08 January 2020 07:39 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 9B272120105 for <dots@ietfa.amsl.com>; Tue, 7 Jan 2020 23:39:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, 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=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 gFq2O_qAS0QL for <dots@ietfa.amsl.com>; Tue, 7 Jan 2020 23:39:12 -0800 (PST)
Received: from us-smtp-delivery-140.mimecast.com (us-smtp-delivery-140.mimecast.com [216.205.24.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CBD312007C for <dots@ietf.org>; Tue, 7 Jan 2020 23:39:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=mimecast20190606; t=1578469150; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Rhgt2xWF5EO7CxIlm9TcXsVr/ltCZnvwgdw+imB6p7s=; b=CMcJMxLMqtrqSJyCCHUNyePlhZMOlg2NnVb2gMN4M5eANhnYd+7qpmuoyUlS8qj3PZy/y8 6ELnh8tWdtSGM7I7PXcezQSl5lU4BpQylb1JLYCE/Tc1rh9giBw5usxSzWpAA/QWAIyNMJ Wr2a66WeOVvSF33lgy1etkjg00yozr8=
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (mail-dm6nam10lp2107.outbound.protection.outlook.com [104.47.58.107]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-69-PnKvOeHpODG_44ll5lwFRw-1; Wed, 08 Jan 2020 02:39:06 -0500
Received: from CY4PR1601MB1254.namprd16.prod.outlook.com (10.172.118.12) by CY4PR1601MB1317.namprd16.prod.outlook.com (10.172.116.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2623.9; Wed, 8 Jan 2020 07:39:02 +0000
Received: from CY4PR1601MB1254.namprd16.prod.outlook.com ([fe80::a50e:f380:4d5e:71ea]) by CY4PR1601MB1254.namprd16.prod.outlook.com ([fe80::a50e:f380:4d5e:71ea%6]) with mapi id 15.20.2602.016; Wed, 8 Jan 2020 07:39:02 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: "Xialiang (Frank, Network Standard & Patent Dept)" <frank.xialiang@huawei.com>, Benjamin Kaduk <kaduk@mit.edu>, "draft-ietf-dots-signal-channel@ietf.org" <draft-ietf-dots-signal-channel@ietf.org>
CC: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] 答复: Protocol Action: 'Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification' to Proposed Standard (draft-ietf-dots-signal-channel-41.txt)
Thread-Index: AQHVxfBEJd+OwZDNZE6eh3aTU1MhHafgYLcw
Date: Wed, 08 Jan 2020 07:39:02 +0000
Message-ID: <CY4PR1601MB125459D95C8724B66E76A3F1EA3E0@CY4PR1601MB1254.namprd16.prod.outlook.com>
References: <157841700862.20985.14116369579091975153.idtracker@ietfa.amsl.com> <20200107171727.GW57294@kduck.mit.edu> <C02846B1344F344EB4FAA6FA7AF481F13EB58021@dggemm511-mbx.china.huawei.com>
In-Reply-To: <C02846B1344F344EB4FAA6FA7AF481F13EB58021@dggemm511-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.4.0.45
dlp-reaction: no-action
x-originating-ip: [49.37.206.28]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 184e8660-df64-4769-7d67-08d7940dd535
x-ms-traffictypediagnostic: CY4PR1601MB1317:
x-microsoft-antispam-prvs: <CY4PR1601MB13171A225C88CCC578B1E505EA3E0@CY4PR1601MB1317.namprd16.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 02760F0D1C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(39860400002)(396003)(376002)(136003)(366004)(32952001)(13464003)(189003)(199004)(86362001)(6506007)(53546011)(7696005)(52536014)(5660300002)(64756008)(66476007)(186003)(66556008)(66446008)(66946007)(26005)(76116006)(71200400001)(2906002)(224303003)(9686003)(316002)(55016002)(110136005)(81166006)(81156014)(66574012)(966005)(478600001)(4326008)(33656002)(8936002)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR1601MB1317; H:CY4PR1601MB1254.namprd16.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 8jdYI6+LQf/4KLSoyYrMDasyXvNfoSWyKVArmvDYrgSmq8xEPxrqKkKpTXtXIwOQJ/zQlEAz+77igOblGEbOHxcpIechcC2c/psdcPAQzv/Yk8OgcH7rmEZSST1ajrsDgn8JY/yk+Gt7evZz6RmYUBRStYdc6L7Ld6kj5gQvJwELIRrjNXMKE39KOJFPhnBIcSvALE4ui+inuapFVPegDCwMMP/U2wFGUV9dg9ODitSIGd2w32wv/t5Wb/ZcH44TMqOLkp2b04l8myNw/gKMffOu0mjSE3seun91qgvR2wnZjgzmOHXxuQUUZQNRVa1fPDJ/E7BOlnsdvV5/MWMtgbb+Dw7gWC9wmYCbds4RE2bMBP8zGX5u1JDgE4EVdjxMO1XtKIpmsBzihpgF1Yqys5aImbeMTDw8w7WrhLpTzCU8p15Im+T/5aZOAIMIW1719Adio3p4cpqUYNveDky8vDFRTr6R5HJIQv0PbDR73onVFQYI+/GiPLHG626ALmgu0+Nm2GfgrL+/AHxppRTsa+F1QAlj4LwSxtP8P+oVhh+ZXmilF1aa+6eBeVqUbiLRz7OmuhuAlTBmyBhGG6zUFA==
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: mcafee.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 184e8660-df64-4769-7d67-08d7940dd535
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jan 2020 07:39:02.7563 (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: QJb9ckcmxrytZX0mHqcas1aINFhulZAgl8U/TA0gxJ0WUVls2EEbTGJZZ1Pdb0Y6sbx2yhPQLQGVFJdnRQ+doK9utON5J4J2Z5VbtrgcTRnHiHjoRKrZ1VRxcrhxeZw8
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1601MB1317
X-MC-Unique: PnKvOeHpODG_44ll5lwFRw-1
X-Mimecast-Spam-Score: 0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/iZpS4lAOxbB-wP8GEfJfeJNErbo>
Subject: Re: [Dots] 答复: Protocol Action: 'Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification' to Proposed Standard (draft-ietf-dots-signal-channel-41.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, 08 Jan 2020 07:39:15 -0000

Glad to see the document progressed and all the effort from the WG paid off. 

Cheers,
-Tiru

> -----Original Message-----
> From: Dots <dots-bounces@ietf.org> On Behalf Of Xialiang (Frank, Network
> Standard & Patent Dept)
> Sent: Wednesday, January 8, 2020 12:23 PM
> To: Benjamin Kaduk <kaduk@mit.edu>; draft-ietf-dots-signal-
> channel@ietf.org
> Cc: dots@ietf.org
> Subject: [Dots] 答复: Protocol Action: 'Distributed Denial-of-Service Open
> Threat Signaling (DOTS) Signal Channel Specification' to Proposed Standard
> (draft-ietf-dots-signal-channel-41.txt)
> 
> CAUTION: External email. Do not click links or open attachments unless you
> recognize the sender and know the content is safe.
> 
> Good news, thanks all for the hard work to get this done.
> 
> -----邮件原件-----
> 发件人: Dots [mailto:dots-bounces@ietf.org] 代表 Benjamin Kaduk
> 发送时间: 2020年1月8日 1:17
> 收件人: draft-ietf-dots-signal-channel@ietf.org
> 抄送: dots@ietf.org
> 主题: Re: [Dots] Protocol Action: 'Distributed Denial-of-Service Open Threat
> Signaling (DOTS) Signal Channel Specification' to Proposed Standard (draft-
> ietf-dots-signal-channel-41.txt)
> 
> Thank you for all your hard work to get this document approved; I'm happy
> with where we ended up (even if I'm not happy that it took so long)!
> 
> -Ben
> 
> On Tue, Jan 07, 2020 at 09:10:08AM -0800, The IESG wrote:
> > The IESG has approved the following document:
> > - 'Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal
> >    Channel Specification'
> >   (draft-ietf-dots-signal-channel-41.txt) as Proposed Standard
> >
> > This document is the product of the DDoS Open Threat Signaling Working
> Group.
> >
> > The IESG contact persons are Benjamin Kaduk and Roman Danyliw.
> >
> > A URL of this Internet Draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-dots-signal-channel/
> >
> >
> >
> >
> > Technical Summary
> >
> >     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.
> >
> >     This is a companion document to the DOTS data channel specification.
> >
> > Working Group Summary
> >
> >     This draft has been extensively reviewed and discussed within the
> >     working group by mailing list and github.  The latest document is
> >     well written and reaches a broad consensus in WG.
> >
> > Document Quality
> >
> >    The co-authors are from some of the leading vendors and operators in
> >    DDoS protection industry with extensive experience with the related
> >    technologies and implementations; they are also the core authors of
> >    the DOTS requirements WG drafts, which guarantees consistency
> between
> >    the core DOTS protocol documents.  Until now, there are three demo
> >    implementations for it (open source go-dots from NTT and two
> >    proprietary demos from NCC and Huawei), and several rounds of interop
> >    tests during IETF hackathon activities. All the technical issues
> >    identified by these demos and the finished tests have been addressed
> >    and reflected into the latest draft, which are very helpful for the
> >    completeness and quality improvement of the draft.
> >
> >    IANA port number expert review is ongoing; the expert is seeking
> >    additional justification that a dedicated port is needed, which has
> >    been provided by the document authors.
> >
> > Personnel
> >
> >     The document shepherd is Liang Xia. The responsible Area Director is
> >     Benjamin Kaduk.
> 
> _______________________________________________
> 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