Re: [Dots] Last Call: <draft-ietf-dots-data-channel-27.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification) to Proposed Standard

Barry Raveendran Greene <bgreene@senki.org> Wed, 27 February 2019 16:52 UTC

Return-Path: <bgreene@senki.org>
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 231711310C4; Wed, 27 Feb 2019 08:52:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 hlyGiOENkJgf; Wed, 27 Feb 2019 08:52:36 -0800 (PST)
Received: from smtp70.ord1d.emailsrvr.com (smtp70.ord1d.emailsrvr.com [184.106.54.70]) (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 C6FE7131092; Wed, 27 Feb 2019 08:52:32 -0800 (PST)
Received: from smtp17.relay.ord1d.emailsrvr.com (localhost [127.0.0.1]) by smtp17.relay.ord1d.emailsrvr.com (SMTP Server) with ESMTP id 22BAF20251; Wed, 27 Feb 2019 11:52:32 -0500 (EST)
X-Auth-ID: bgreene@senki.org
Received: by smtp17.relay.ord1d.emailsrvr.com (Authenticated sender: bgreene-AT-senki.org) with ESMTPSA id 67D3C2025D; Wed, 27 Feb 2019 11:52:31 -0500 (EST)
X-Sender-Id: bgreene@senki.org
Received: from [10.0.0.116] (c-73-92-124-43.hsd1.ca.comcast.net [73.92.124.43]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:25 (trex/5.7.12); Wed, 27 Feb 2019 11:52:32 -0500
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Barry Raveendran Greene <bgreene@senki.org>
X-Mailer: iPad Mail (16D57)
In-Reply-To: <155127802240.13985.12710692781572812550.idtracker@ietfa.amsl.com>
Date: Wed, 27 Feb 2019 08:52:30 -0800
Cc: IETF-Announce <ietf-announce@ietf.org>, Roman Danyliw <rdd@cert.org>, dots-chairs@ietf.org, kaduk@mit.edu, dots@ietf.org, draft-ietf-dots-data-channel@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDD3AF39-BFAB-49DB-A25A-87D6A3A2C1AA@senki.org>
References: <155127802240.13985.12710692781572812550.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/xIf--cjMSYYW2vDOZFihYs8NZpY>
Subject: Re: [Dots] Last Call: <draft-ietf-dots-data-channel-27.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification) to Proposed Standard
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, 27 Feb 2019 16:52:43 -0000

Do we have working implementations to validate the movement to a proposed standard? Does it work?

> On Feb 27, 2019, at 06:33, The IESG <iesg-secretary@ietf.org> wrote:
> 
> 
> The IESG has received a request from the DDoS Open Threat Signaling WG (dots)
> to consider the following document: - 'Distributed Denial-of-Service Open
> Threat Signaling (DOTS) Data
>   Channel Specification'
>  <draft-ietf-dots-data-channel-27.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2019-03-13. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the beginning of
> the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>   The document specifies a Distributed Denial-of-Service Open Threat
>   Signaling (DOTS) data channel used for bulk exchange of data that
>   cannot easily or appropriately communicated through the DOTS signal
>   channel under attack conditions.
> 
>   This is a companion document to the DOTS signal channel
>   specification.
> 
> Editorial Note (To be removed by RFC Editor)
> 
>   Please update these statements within the document with the RFC
>   number to be assigned to this document:
> 
>   o  "This version of this YANG module is part of RFC XXXX;"
> 
>   o  "RFC XXXX: Distributed Denial-of-Service Open Threat Signaling
>      (DOTS) Data Channel Specification";
> 
>   o  reference: RFC XXXX
> 
>   Please update the "revision" date of the YANG module.
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-dots-data-channel/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-dots-data-channel/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> 
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots