IETF Logo Mail Archive

Re: [Dots] Availability of a DOTS public test server

Benjamin Kaduk <kaduk@mit.edu> Sun, 08 December 2019 19:40 UTC

Return-Path: <kaduk@mit.edu>
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 AC6701200B1 for <dots@ietfa.amsl.com>; Sun, 8 Dec 2019 11:40:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 wZCEoJ36L-SF for <dots@ietfa.amsl.com>; Sun, 8 Dec 2019 11:40:21 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D614B12007C for <dots@ietf.org>; Sun, 8 Dec 2019 11:40:20 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id xB8JeFce000588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 8 Dec 2019 14:40:18 -0500
Date: Sun, 08 Dec 2019 11:40:15 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Jon Shallow <supjps-ietf@jpshallow.com>
Cc: dots@ietf.org
Message-ID: <20191208194015.GB13890@kduck.mit.edu>
References: <046101d5aab2$ae791890$0b6b49b0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <046101d5aab2$ae791890$0b6b49b0$@jpshallow.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/XJtYNOqQcwH8pzQ_A-Puqe3BwBc>
Subject: Re: [Dots] Availability of a DOTS public test server
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: Sun, 08 Dec 2019 19:40:23 -0000

Hi Jon,

That is very cool to see -- thank you!

-Ben

On Wed, Dec 04, 2019 at 02:54:08PM -0000, Jon Shallow wrote:
> Hi there,
> 
>  
> 
> This is to confirm that I have a DOTS server that can be publically accessed
> for testing.
> 
>  
> 
> The current versions of the drafts that are supported are:-
> 
>  
> 
> draft-ietf-dots-signal-channel-39
> 
> draft-ietf-dots-data-channel-31
> 
> draft-ietf-core-hop-limit-07
> 
> draft-ietf-dots-signal-filter-control-02
> 
> draft-ietf-dots-signal-call-home-07
> 
>  
> 
> with the following caveats
> 
>  
> 
> application/dots+cbor has not yet been defined, so currently using 60
> (application/cbor)
> 
>  
> 
> For signal-filter-control, CBOR Key 52 is used to not clash with
> signal-channel CBOR keys.
> 
>  
> 
> The DOTS server (signal) is available at dotsserver.ddos-secure.net port
> 4646 (both UDP and TCP)
> 
> The DOTS server (data) is available at dotsserver.ddos-secure.net port 443
> (both UDP and TCP) (SNI required)
> 
> The Call Home DOTS client is available at dotsserver.ddos-secure.net port
> 4647 (both UDP and TCP)
> 
>  
> 
> To access using PKI, Certificates are the same as used by godots and are
> available from https://github.com/nttdots/go-dots/tree/master/certs.
> 
> To access the DOTS server, you need to use client-cert.pem and
> client-key.pem
> 
> To access the Call Home DOTS client, you need to use server-cert.pem and
> server-key.pem.
> 
>  
> 
> Alternatively, using PSK, the Pre-Shared Key is 12345678  and the DOTS
> client Identity must be client.example.server.com .
> 
>  
> 
> It is possible to set the configuration up as a DOTS gateway, but your DOTS
> server needs to be pre-configured so that traffic can be gatewayed to it, as
> well as use a different client key that has a different common name (but
> created from the same godots CA) so traffic can be differentiated from that
> using client-cert.pem which access the DOTS server only.
> 
>  
> 
> The local DOTS server will accept mitigation requests for 1.1.1.69,
> 1.1.1.71, 1.1.2.0/24 and 2001:db8:6401::/96.
> 
>  
> 
> Diagnostic messages should be self-explanatory as to what the (perceived)
> issue is.
> 
>  
> 
> It is possible that there may be brief outages whenever the s/w is updated.
> 
>  
> 
> Regards
> 
>  
> 
> Jon
> 

> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots

v2.23.0 | Report a Bug | By Email