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

[Roman Danyliw <[e-mail]>]

Hi Tiru!

Do you want to roll this clarifying change into a quick -24?

Roman

> -----Original Message-----
> From: Dots [mailto:[e-mail]] On Behalf Of Konda,
> Tirumaleswar Reddy
> Sent: Saturday, August 18, 2018 10:18 AM
> To: [e-mail]; [e-mail]
> Subject: Re: [Dots] I-D Action: draft-ietf-dots-signal-channel-23.txt
> 
> Minor change:
> 
> If PSK is used, (EC)DHE key exchange is required to provide perfect forward
> secrecy.
> 
> OLD:
>    o  Raw public keys [RFC7250] or PSK handshake [RFC4279] which reduces
>       the size of the ServerHello, and can be used by DOTS agents that
>       cannot obtain certificates.
> 
> NEW:
> 
>    o  Raw public keys [RFC7250] or PSK handshake with (EC)DHE key exchange
> [RFC4279] which reduces
>       the size of the ServerHello, and can be used by DOTS agents that
>       cannot obtain certificates.
> 
> -Tiru
> 
> > -----Original Message-----
> > From: Dots <[e-mail]> On Behalf Of
> > [e-mail]
> > Sent: Friday, August 17, 2018 5:58 PM
> > To: [e-mail]
> > Subject: 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:[e-mail]] De la part
> > > de [e-mail] Envoyé : vendredi 17 août 2018 14:19 À :
> > > [e-mail] Cc : [e-mail] 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
> > > -2
> > > 3
> > >
> > > 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
> > > [e-mail]
> > > 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
> >
> > _______________________________________________
> > Dots mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/dots
> _______________________________________________
> Dots mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dots