RE: Secdir last call review of draft-ietf-dots-signal-channel-30

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Stephen, 

FWIW, a new version that integrates your comments is available online. The diff can be tracked at:
https://tools.ietf.org/rfcdiff?url2=draft-ietf-dots-signal-channel-31.txt 

Please let me know if you have further comments. 

Thank you.

Cheers,
Med

> -----Message d'origine-----
> De : Stephen Farrell [mailto:stephen.farrell@xxxxxxxxx]
> Envoyé : vendredi 15 mars 2019 11:20
> À : BOUCADAIR Mohamed TGI/OLN; secdir@xxxxxxxx
> Cc : draft-ietf-dots-signal-channel.all@xxxxxxxx; ietf@xxxxxxxx;
> dots@xxxxxxxx
> Objet : Re: Secdir last call review of draft-ietf-dots-signal-channel-30
> 
> 
> Hiya,
> 
> On 15/03/2019 06:47, mohamed.boucadair@xxxxxxxxxx wrote:
> >> ISTM that all clients can get information
> >> about how an attack is being seen at other clients, isn't that
> >> right?
> > [Med] No. A client can only get information that is bound to it.
> Where does the spec say that? I don't recall the term "bound"
> used that way but may have missed it.
> 
> And it still seems a bit hard to enforce. If two clients (one
> ok, one zombied) ask the same server/network how many packets
> targetted at 10.0.0/24 were dropped won't they get the same
> answer? (Assuming both clients are within that /24.)
> 
> Thanks,
> S.




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux