Re: [Dots] Barry Leiba's No Objection on draft-ietf-dots-server-discovery-14: (with COMMENT)

[Barry Leiba <[e-mail]>]

Perfect; thanks again, Med.

Barry

On Thu, Oct 29, 2020 at 9:30 AM <[e-mail]> wrote:
>
> Re-,
>
> Sure. Please check the update at: https://tinyurl.com/dots-discovery-iesg
>
> Thank you.
>
> Cheers,
> Med
>
> > -----Message d'origine-----
> > De : Barry Leiba [mailto:[e-mail]]
> > Envoyé : jeudi 29 octobre 2020 14:08
> > À : BOUCADAIR Mohamed TGI/OLN <[e-mail]>
> > Cc : The IESG <[e-mail]>; draft-ietf-dots-server-
> > [e-mail]; [e-mail]; [e-mail]; Valery
> > Smyslov <[e-mail]>
> > Objet : Re: Barry Leiba's No Objection on draft-ietf-dots-server-
> > discovery-14: (with COMMENT)
> >
> > Hi, Med, and many thanks for making the changes and addressing my
> > comments.
> >
> > > > Overall discussion question (but not at blocking DISCUSS level):
> > > > Does it make sense for DOTS clients to proactively discover
> > > > appropriate DOTS servers *before* a DDoS attack hits, to avoid
> > the
> > > > issue of discovery being blocked by the attack that the client
> > is
> > > > trying to report?  Should this document discuss that?
> > >
> > > [Med] This is already covered in the text as the discovery is
> > > triggered by new network attachments (which includes
> > bootstrapping).
> > > The discovery information is thus available independently of the
> > attack conditions.
> >
> > Indeed, so the list at the end of Section 4 implies, and that ought
> > to be enough.
> >
> > Still, may I ask for one more minor change, which I think makes it
> > just a tad more explicit?  In the lead-in to the list:
> >
> > OLD
> >    The discovery method is reiterated by a DOTS agent upon the
> > following
> >    events:
> >
> > NEW
> >    The discovery method is performed upon attachment to a network,
> > and is
> >    reiterated by a DOTS agent upon the following events:
> >
> > END
> >
> > > I understand the references in the terminology section may suggest
> > > that knowledge is required. To avoid that, the terminology section
> > is
> > > updated to list the terms used in the document.
> >
> > I looked at the update, and that works for me; thanks!
> >
> > Barry
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>