Re: [Dots] I-D Action: draft-ietf-dots-rfc8782-bis-00.txt

[Jon Shallow <[e-mail]>]

Hi Kaname,

Well spotted!

I agree that 

           leaf attack-status {
             type iana-signal:attack-status;
             description
               "Indicates the status of an attack as seen by the
                DOTS client.";
           }
Should be moved up to just after (in the yang definition [e-mail])
       leaf trigger-mitigation {
         type boolean;
         default "true";
         description
           "If set to 'false', DDoS mitigation will not be
            triggered unless the DOTS signal channel
            session is lost.";
       }

And will get corrected.

Regards

Jon

> -----Original Message-----
> From: Dots [mailto: [e-mail]] On Behalf Of kaname nishizuka
> Sent: 24 August 2020 08:28
> To: Valery Smyslov; [e-mail]
> Subject: Re: [Dots] I-D Action: draft-ietf-dots-rfc8782-bis-00.txt
> 
> Hi Med, all.
> 
> `attack-status` is now under server-to-client-only in RFC8782 bis, but I just
> want to clarify whether it's correct.
> 
> In 4.4.3, it is said:
>     The 'attack-status' parameter is a mandatory attribute when
>     performing an efficacy update.  The various possible values contained
>     in the 'attack-status' parameter are described in Table 4.
>              +-----------+-------------------------------------+
>              | Parameter | Description                         |
>              |     Value |                                     |
>              +===========+=====================================+
>              |         1 | The DOTS client determines that it  |
>              |           | is still under attack.              |
>              +-----------+-------------------------------------+
>              |         2 | The DOTS client determines that the |
>              |           | attack is successfully mitigated    |
>              |           | (e.g., attack traffic is not seen). |
>              +-----------+-------------------------------------+
> 
>                  Table 4: Values of 'attack-status' Parameter
> 
> 
> regards,
> Kaname Nishizuka
> 
> 
> On 2020/08/19 16:06, Valery Smyslov wrote:
> > Hi,
> >
> > according to the roadmap we discussed for the replacement
> > of RFC 8782, we are going to request yangdoctors
> > and opsdir reviews for the just adopted draft to double check
> > that all the changes in YANG module are fine with them.
> > We are going to issue WGLC shortly after the reviews are complete.
> >
> > Regards,
> > Frank & Valery.
> >
> >> 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         : Mohamed Boucadair
> >>                            Jon Shallow
> >>                            Tirumaleswar Reddy.K
> >> 	Filename        : draft-ietf-dots-rfc8782-bis-00.txt
> >> 	Pages           : 119
> >> 	Date            : 2020-08-18
> >>
> >> Abstract:
> >>     This document specifies the Distributed Denial-of-Service Open Threat
> >>     Signaling (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.
> >>
> >>     This document obsoletes RFC 8782.
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-dots-rfc8782-bis/
> >>
> >> There are also htmlized versions available at:
> >> https://tools.ietf.org/html/draft-ietf-dots-rfc8782-bis-00
> >> https://datatracker.ietf.org/doc/html/draft-ietf-dots-rfc8782-bis-00
> >>
> >>
> >> 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
> >> [e-mail]
> >> https://www.ietf.org/mailman/listinfo/dots
> > _______________________________________________
> > Dots mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/dots
> 
> _______________________________________________
> Dots mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dots