[Dots] Availability of DOTS Server
"Jon Shallow" <supjps-ietf@jpshallow.com> Thu, 02 November 2017 14:08 UTC
Return-Path: <supjps-ietf@jpshallow.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 5415413F893 for <dots@ietfa.amsl.com>; Thu, 2 Nov 2017 07:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, SPF_PASS=-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 JGaRWEMNfaJ3 for <dots@ietfa.amsl.com>; Thu, 2 Nov 2017 07:08:14 -0700 (PDT)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (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 D26C513F884 for <dots@ietf.org>; Thu, 2 Nov 2017 07:08:13 -0700 (PDT)
Received: from [127.0.0.1] (helo=N01332) by mail.jpshallow.com with smtps (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from <jon.shallow@jpshallow.com>) id 1eAGAG-0007K4-C5 for ietf-supjps-dots@ietf.org; Thu, 02 Nov 2017 14:08:12 +0000
From: Jon Shallow <supjps-ietf@jpshallow.com>
To: dots@ietf.org
Date: Thu, 02 Nov 2017 14:08:12 -0000
Message-ID: <05e701d353e4$052ab450$0f801cf0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_05E8_01D353E4.052B5090"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdNT5AOFWju5GZ2ZR+C6vVHgMupOHQ==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/PDpXpb7g1NIvedlrkVGN3TMRJOQ>
Subject: [Dots] Availability of DOTS Server
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.22
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, 02 Nov 2017 14:08:16 -0000
As mentioned at the last DOTS Virtual Meeting, I would aim to get a DOTS server up and running to test against. It has taken a bit longer than I said - so apologies for that. The DOTS server is hosted at dotsserver.ddos-secure.net , listening on ports 5684 and 4646 for CoAP over both DTLS and TLS. The data channel is not currently available, but should be shortly. At present, you can come in from any IP address, but need to use the Client and CA certificates that provided as part of the nttdots project for authentication (https://github.com/nttdots/go-dots/tree/master/certs) . It is on my ToDo list to use a different set of certificates. Thanks to nttdots for making the current set of certificates available. The DOTS server will accept mitigation requests for 1.1.1.69, 1.1.1.71, and 1.1.2.0/24 It is possible the server may go down briefly - when we update the s/w - but should be for no more than a minute. The server supports signal draft -06, as well as the changes so far in https://github.com/dotswg/dots-signal-channel/blob/master/draft-ietf-dots-si gnal-channel-07.txt. You should get back CoAP diagnostic messages saying what is failing for troubleshooting at both ends. I have logging enabled at my end. We also have a working DOTS client which can be pointed to an external DOTS server for testing - we need a client cert + key for that. Some of the DOTS gateway "glue" is in place. Regards Jon
- [Dots] Availability of DOTS Server Jon Shallow