Re: [Dots] I-D Action: draft-ietf-dots-signal-channel-23.txt

Hi all, 

This version follows the recommendations from the core WG: 
* Move Hop-Limit text to a separate I-D: I-D.boucadair-core-hop-limit.
* Abandon the use of 3.00, but use 5.03 instead. 

The good news is that these changes are straightforward and do not hold publication because I-D.boucadair-core-hop-limit is not a normative reference. 

We also updated the text to reflect the recent publication of RFC8446 (TLS 1.3). Changes are tweaked to be aligned with the discussion with Benjamin (thanks). 

Chairs, the token is yours now :)

Cheers,
Med

> -----Message d'origine-----
> De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de
> internet-drafts@ietf.org
> Envoyé : vendredi 17 août 2018 14:19
> À : i-d-announce@ietf.org
> Cc : dots@ietf.org
> Objet : I-D Action: draft-ietf-dots-signal-channel-23.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.
> 
>         Title           : Distributed Denial-of-Service Open Threat Signaling
> (DOTS) Signal Channel Specification
>         Authors         : Tirumaleswar Reddy
>                           Mohamed Boucadair
>                           Prashanth Patil
>                           Andrew Mortensen
>                           Nik Teague
> 	Filename        : draft-ietf-dots-signal-channel-23.txt
> 	Pages           : 87
> 	Date            : 2018-08-17
> 
> Abstract:
>    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.
> 
>    A companion document defines the DOTS data channel, a separate
>    reliable communication layer for DOTS management and configuration
>    purposes.
> 
> 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) Signal Channel Specification";
> 
>    o  "| [RFCXXXX] |"
> 
>    o  reference: RFC XXXX
> 
>    Please update TBD statements with the port number to be assigned to
>    DOTS Signal Channel Protocol.
> 
>    Also, please update the "revision" date of the YANG module.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dots-signal-channel/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dots-signal-channel-23
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-signal-channel-23
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-signal-channel-23
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt