Re: [Dots] Reminder -- WGLC on draft-ietf-dots-data-channel-18

["Konda, Tirumaleswar Reddy" <[e-mail]>]

Got it, will update draft.

Cheers,
-Tiru

From: Kathleen Moriarty <[e-mail]>
Sent: Monday, August 27, 2018 7:55 PM
To: Konda, Tirumaleswar Reddy <[e-mail]>
Cc: Roman Danyliw <[e-mail]>; [e-mail]
Subject: Re: [Dots] Reminder -- WGLC on draft-ietf-dots-data-channel-18


CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.


________________________________
Hi Tirumaleswar,
Sent from my mobile device

On Aug 25, 2018, at 10:56 AM, Konda, Tirumaleswar Reddy <[e-mail]<mailto:[e-mail]>> wrote:
Hi Kathleen,

Security vendors already provide feeds of malicious domain names and IP addresses to black-list traffic (e.g. block botnets) and provide reputation scores for white-listing and grey-listing for content inspection. I don’t think sharing the attacker details with the DOTS server over a secure communication channel to black-list traffic has any privacy implications.


Yes, as I had said in my review, the controls cover the consideration.  What I was suggesting is that the consideration is mentioned in terms of privacy.  This matters more in some regions (Germany) than others.  I suspect if it’s not added now, it’s likely to be requested when the draft goes through IESG review.  I’m just trying to save you time later.

Best regards,
Kathleen


Cheers,
-Tiru

From: Dots <[e-mail]<mailto:[e-mail]>> On Behalf Of Kathleen Moriarty
Sent: Saturday, August 25, 2018 1:23 AM
To: Roman Danyliw <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>
Subject: Re: [Dots] Reminder -- WGLC on draft-ietf-dots-data-channel-18


CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.


________________________________
I did a quick read, sorry I didn't have time for a closer review and noticed the following:

Section 3.5:

   This

   behavior is required for topology hiding purposes but also to

   minimizing potential conflicts that may arise if overlapping

   information is used in distinct DOTS domains (e.g., private IPv4

   addresses, non globally unique aliases).
s/minimizing/minimize/

Then in the Security Considerations (Privacy)...

I don't see any explicit privacy considerations and am thinking IP address/host information of attackers could be sensitive as they often indicate compromised systems.  The compromise may extend further than the use of the system in a DDoS attack and there could also be reputation considerations.

The controls already listed are the most that can be applied considering the protocols, so thank you for that.

Best regards,
Kathleen

On Tue, Aug 21, 2018 at 6:03 PM, Roman Danyliw <[e-mail]<mailto:[e-mail]>> wrote:
Hello!

The WGLC on draft-ietf-dots-data-channel ends Tuesday, August 27.  Please provide input on the mailing list by this deadline.

Roman

> -----Original Message-----
> From: Dots [mailto:[e-mail]<mailto:[e-mail]>] On Behalf Of Roman Danyliw
> Sent: Friday, August 10, 2018 4:30 PM
> To: [e-mail]<mailto:[e-mail]>
> Subject: [Dots] WGLC on draft-ietf-dots-data-channel-18
>
> Hello!
>
> Consistent with our discussion at the Montreal meeting, we are starting a
> working group last call (WGLC) for the DOTS Data Channel draft:
>
> DOTS Data Channel Specification
> draft-ietf-dots-data-channel-18
> https://tools.ietf.org/html/draft-ietf-dots-data-channel-18
>
> Please send comments to the DOTS mailing list -- feedback on remaining
> issues or needed changes; as well as endorsements that this draft is ready.
>
> This WGLC will end on August 27, 2018.
>
> Thanks,
> Roman
>
> _______________________________________________
> Dots mailing list
> [e-mail]<mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/dots

_______________________________________________
Dots mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/dots



--

Best regards,
Kathleen