IETF Logo Mail Archive

Re: [Dots] Alignment with architecture document

"Teague, Nik" <nteague@verisign.com> Thu, 21 July 2016 15:02 UTC

Return-Path: <nteague@verisign.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 037C812D739 for <dots@ietfa.amsl.com>; Thu, 21 Jul 2016 08:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign-com.20150623.gappssmtp.com
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 pmCcIlSnVUvJ for <dots@ietfa.amsl.com>; Thu, 21 Jul 2016 08:02:37 -0700 (PDT)
Received: from mail-qt0-x261.google.com (mail-qt0-x261.google.com [IPv6:2607:f8b0:400d:c0d::261]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 519EA12D67B for <dots@ietf.org>; Thu, 21 Jul 2016 08:02:36 -0700 (PDT)
Received: by mail-qt0-x261.google.com with SMTP id w38so5437463qtb.2 for <dots@ietf.org>; Thu, 21 Jul 2016 08:02:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :accept-language:content-language:user-agent:content-id :content-transfer-encoding:mime-version; bh=N4NrjUl/TezRlBwsCarbbS6wGfJ97eBR6l5k6RVloqM=; b=nvomXmS+R+FScC9m2T5A0ScxiZNJaBDuzE7LXjXvvdBqA5DHH0hjKX2LnLiUT7I6Vb SEDa+IcbqK62m2SZP/vKabKjqc5jO2om+WcPw+6p2mKC1mNYh+SQwUxS1g320mOoGns1 XczIRDjl941ljkpOvO2OAV+CuZ74EH7Mx6r7+wC4bsRnYP2+lTuJ3Xd6qpsYRxNRdkgg U/b8YU829YrjYO1B/qPNCVUCB032gn1gHbCABGcK3RubCy1G+Wl3mVhLNESiX9mucuit wzjTpyuT2HddCZOZI6MeEEDTIw/4JWDqgM/xESM/aT4DYxtH2CYHySVPSAlo7vOO6rs6 svoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:accept-language:content-language:user-agent:content-id :content-transfer-encoding:mime-version; bh=N4NrjUl/TezRlBwsCarbbS6wGfJ97eBR6l5k6RVloqM=; b=N3Wj+pdKqodzTXBpuBitc7Mp8Ux+Vwtvvof/Fw2BAx46vnfXUkywWBKe0bRLtsAUBc Q79B9ObLcx4URnqJkZxm8U59TlGT7SgSkDjCzJXAt2v6IDcSVC6bTCDsnCne2oX4dDeF erktR6jxvSu0pzdfOwV08HR/njuwVVPVdQ24EpDLHNYpe4O/SkmK4Mc5zfrLkf2ELACh eH7h3/cwQ/NFV4Mba53zv+/dYhzG0gMiYggkFYqjZpZMLBaSxV1syf3Ek0Cb09gXE5rD W8Hp3rfAWJd6aO6Gt9S4ubPpUZLNHytMp/2WP5+yi400tUXgMVh0d0N1Wv8gtt3H8/6S XA4A==
X-Gm-Message-State: ALyK8tKJeSjtMOVsiGdi60AcaE67BZ9LW3XkX7YQV73DKOGbupGzKZob67MS+dfsNc3XAI+M06vZOUYTDCHS0l6RhTuO+N5p
X-Received: by 10.55.155.22 with SMTP id d22mr70782411qke.103.1469113355641; Thu, 21 Jul 2016 08:02:35 -0700 (PDT)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id d141sm1321822qkc.1.2016.07.21.08.02.35 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 21 Jul 2016 08:02:35 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id u6LF2ZLW023755 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 21 Jul 2016 11:02:35 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 21 Jul 2016 11:02:34 -0400
From: "Teague, Nik" <nteague@verisign.com>
To: "Roman D. Danyliw" <rdd@cert.org>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] Alignment with architecture document
Thread-Index: AQHR42Dpstvji5VhRRW6cZRJEraRiw==
Date: Thu, 21 Jul 2016 15:02:34 +0000
Message-ID: <ADE40F13-A2BF-40EC-8252-6C5C7431166B@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.160212
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0D45DD8554D9E04F99FE59760B64C015@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/1NQ5xP5KVO0MN00VlYlV8GvCMbE>
Subject: Re: [Dots] Alignment with architecture document
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 21 Jul 2016 15:02:44 -0000

On 21/07/2016 10:39, "Dots on behalf of Roman D. Danyliw" <dots-bounces@ietf.org on behalf of rdd@cert.org> wrote:


>(2) The protocol draft [4] does not express messaging in terms of the components (i.e., DOTS server, client or gateway) or interfaces (i.e., signal and data channels) described in [1].
>
>The lack of alignment in [4] is the finding that is most interesting for me.  Does this draft [4] suggest we need new components or interfaces in the architecture? New use cases?

IMHO - No

I’m struggling to see the relevance here - And I’d be happy if someone could elaborate and explain what it is I’m missing.

Slide 2 of <https://www.ietf.org/proceedings/96/slides/slides-96-dots-2.pdf> shows routers sending flow (I presume, marked in red) to a DOTS client also labeled ‘flow analysis’ - I get that - what I don’t understand is the further red line between the DOTS client and server - why would the flow analyser then forward this to the controller (the DOTS server)?

Wouldn’t the DOTS client just speak DOTS to the DOTS server for those particular red lines?

>
>Regards,
>Roman 
>
>[1] draft-ietf-dots-architecture-00
>[2] draft-reddy-dots-transport-05
>[3] draft-francois-dots-ipv6-signal-option-00
>[4] draft-fu-dots-ipfix-extension-01
>[5] draft-nishizuka-dots-inter-domain-mechanism-01

v2.23.0 | Report a Bug | By Email