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

Hi Barry,

> -----Original Message-----
> From: Barry Raveendran Greene [mailto:bgreene@senki.org]
> Sent: Wednesday, February 27, 2019 11:53 AM
> To: ietf@ietf.org
> 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
> 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
> 
> 
> Do we have working implementations to validate the movement to a
> proposed standard? Does it work?

Yes.  There are two implementations [1] (from NTT and NCC Group) of this data channel specification. These implementations did an interop at IETF 102 [2] and IETF 103 [3] which improved the current specification.

Regards,
Roman

[1] https://trac.ietf.org/trac/dots
[2] https://datatracker.ietf.org/meeting/102/materials/slides-102-dots-ietf-102-hackathon-interop-report-00
[3] https://datatracker.ietf.org/meeting/103/materials/slides-103-dots-interop-report-from-ietf-103-hackathon-00 

> > 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