Re: [Dots] New Version Notification for draft-chen-dots-server-hierarchical-deployment-00.txt

"Meiling Chen" <chenmeiling@chinamobile.com> Wed, 17 July 2019 08:30 UTC

Return-Path: <chenmeiling@chinamobile.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38D00120221 for <dots@ietfa.amsl.com>; Wed, 17 Jul 2019 01:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uUOdmvDtsHCJ for <dots@ietfa.amsl.com>; Wed, 17 Jul 2019 01:30:43 -0700 (PDT)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 5190E12021B for <dots@ietf.org>; Wed, 17 Jul 2019 01:30:40 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.11]) by rmmx-syy-dmz-app09-12009 (RichMail) with SMTP id 2ee95d2edca3961-84c47; Wed, 17 Jul 2019 16:30:28 +0800 (CST)
X-RM-TRANSID: 2ee95d2edca3961-84c47
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[10.2.51.70]) by rmsmtp-syy-appsvr06-12006 (RichMail) with SMTP id 2ee65d2edca3b7b-9d778; Wed, 17 Jul 2019 16:30:28 +0800 (CST)
X-RM-TRANSID: 2ee65d2edca3b7b-9d778
Date: Wed, 17 Jul 2019 16:30:30 +0800
From: "Meiling Chen" <chenmeiling@chinamobile.com>
To: mohamed.boucadair <mohamed.boucadair@orange.com>, dots <dots@ietf.org>
References: <156246539991.3273.3216673143517865297.idtracker@ietfa.amsl.com>, <2019070916342639919923@chinamobile.com>, <787AE7BB302AE849A7480A190F8B93302EAE5D7E@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.9.115[cn]
Mime-Version: 1.0
Message-ID: <201907171630300752479@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart630165737448_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/gMvdjsfN-_RmVGY5rKRBPEaPwsM>
Subject: Re: [Dots] New Version Notification for draft-chen-dots-server-hierarchical-deployment-00.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2019 08:30:46 -0000

Hi med,
Thank you for your suggestion.
next version will more details about the interfaces and deployment considerations
but I don't get your point about interaction with flow collectors? what's your mean of flow collectors? is it clean equipment(mitigator)?

Best Regards,
Meiling Chen 
From: mohamed.boucadair@orange.com
Date: 2019-07-16 16:26
To: Meiling Chen; dots
Subject: RE: [Dots] New Version Notification for draft-chen-dots-server-hierarchical-deployment-00.txt
Hi Meiling, 
 
Thank for initiating this work.
 
It would be interesting to add more details about the various interfaces involved in the deployment schemes (e.g. recursive signaling). This would help assessing whether current DOTS signals are sufficient or not. 
 
Also, it would helpful if you can elaborate further on deployment considerations (and how) to meet some of the requirements you identified, for example:
 
“   o  DOTS server has the ability to know the address of attack target
      belong to which mitigator“
 
The document may include a discussion about:
* redundancy/backup considerations (with or without DOTS gateways).
* interaction with flow collectors
 
Thank you. 
 
Cheers,  
Med
 
De : Dots [mailto:dots-bounces@ietf.org] De la part de Meiling Chen
Envoyé : mardi 9 juillet 2019 10:34
à : dots
Objet : Re: [Dots] New Version Notification for draft-chen-dots-server-hierarchical-deployment-00.txt
 
Hi all,
I have submited a draft which some thoughts and suggestions on dots server deployment are given, 
・         Consider how to deploy between operators and within operators.
・         URL:https://datatracker.ietf..org/doc/draft-chen-dots-server-hierarchical-deployment/
Reading and Comments are more than welcome.
 
Best Regards,
Meiling Chen 
From: internet-drafts
Date: 2019-07-07 10:09
To: Li Su; chenmeiling; Jin Peng; Meiling Chen
Subject: New Version Notification for draft-chen-dots-server-hierarchical-deployment-00.txt
 
A new version of I-D, draft-chen-dots-server-hierarchical-deployment-00.txt
has been successfully submitted by Meiling Chen and posted to the
IETF repository.
 
Name: draft-chen-dots-server-hierarchical-deployment
Revision: 00
Title: A method for dots server deployment
Document date: 2019-07-06
Group: Individual Submission
Pages: 8
URL:            https://www.ietf.org/internet-drafts/draft-chen-dots-server-hierarchical-deployment-00.txt
Status:         https://datatracker.ietf.org/doc/draft-chen-dots-server-hierarchical-deployment/
Htmlized:       https://tools.ietf.org/html/draft-chen-dots-server-hierarchical-deployment-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-chen-dots-server-hierarchical-deployment
 
 
Abstract:
   As DOTS is used for DDoS Mitigation signaling, In practice, there are
   different deployment scenarios for DOTS agents deployment depending
   on the network deployment mode.  This document made an accommandation
   for DOTS Server deployment which may be Suitable for ISP.  The goal
   is to provide some guidance for DOTS agents deployment.
 
                                                                                  
 
 
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.
 
The IETF Secretariat