Re: [Dots] I-D Action: draft-ietf-dots-data-channel-16.txt

Hi all, 

This version integrates the comments raised during the last month: 
- fix some nits in the examples
- add a sentence to make clear which information is included in a put refresh request
- use the same name for reporting fragment capabilities for both IPv4 and IPv6. 

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:dots-bounces@ietf.org] De la part de internet-
> drafts@ietf.org
> Envoyé : vendredi 18 mai 2018 10:25
> À : i-d-announce@ietf.org
> Cc : dots@ietf.org
> Objet : [Dots] I-D Action: draft-ietf-dots-data-channel-16.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) Data Channel Specification
>         Authors         : Tirumaleswar Reddy
>                           Mohamed Boucadair
>                           Kaname Nishizuka
>                           Liang Xia
>                           Prashanth Patil
>                           Andrew Mortensen
>                           Nik Teague
> 	Filename        : draft-ietf-dots-data-channel-16.txt
> 	Pages           : 59
> 	Date            : 2018-05-18
> 
> 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 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 these statements with the RFC number to be assigned to
>    the following documents:
> 
>    o  "RFC YYYY: Distributed Denial-of-Service Open Threat Signaling
>       (DOTS) Signal Channel Specification" (used to be
>       [I-D.ietf-dots-signal-channel])
> 
>    o  "RFC ZZZZ: Network Access Control List (ACL) YANG Data Model"
>       (used to be [I-D.ietf-netmod-acl-model])
> 
>    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-data-channel/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dots-data-channel-16
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-data-channel-16
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-data-channel-16
> 
> 
> 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/
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots