IETF Logo Mail Archive

Re: [Dots] Signal / Data / Alias / Filter Implementation

"Jon Shallow" <supjps-ietf@jpshallow.com> Thu, 03 August 2017 13:05 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 222FD131FCA for <dots@ietfa.amsl.com>; Thu, 3 Aug 2017 06:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 Fw9goRF2gV9C for <dots@ietfa.amsl.com>; Thu, 3 Aug 2017 06:05:33 -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 11B34131EF8 for <dots@ietf.org>; Thu, 3 Aug 2017 06:05:33 -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 1ddFoh-0000OR-KX for ietf-supjps-dots@ietf.org; Thu, 03 Aug 2017 14:05:31 +0100
From: Jon Shallow <supjps-ietf@jpshallow.com>
To: dots@ietf.org
References: <035401d30b77$fb3a1da0$f1ae58e0$@jpshallow.com> <DM5PR16MB1788C9F8E53F0F39A9B3AE70EAB10@DM5PR16MB1788.namprd16.prod.outlook.com> <042c01d30c30$93ad0670$bb071350$@jpshallow.com> <DM5PR16MB178860DB65938F50187AAC2AEAB10@DM5PR16MB1788.namprd16.prod.outlook.com> <044b01d30c37$034e3cf0$09eab6d0$@jpshallow.com> <DM5PR16MB178821B08674C1C6F2E0E2F3EAB10@DM5PR16MB1788.namprd16.prod.outlook.com> <047301d30c3d$63dd9240$2b98b6c0$@jpshallow.com> <CCAF3E58-5337-422C-83F8-7ED27EFD9498@arbor.net>
In-Reply-To: <CCAF3E58-5337-422C-83F8-7ED27EFD9498@arbor.net>
Date: Thu, 03 Aug 2017 14:05:33 +0100
Message-ID: <04ce01d30c59$30d42af0$927c80d0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-gb
Thread-Index: AQI4Xj59hXHis+FNi2tfJtTtHlSsOQLJsfx7AdboHUsCSD9NFAKHk78aAQdihigBh1dFEwGUUmLFoTtZ5/A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/IeTNV7bnvKygU2_PXSt3aIGB7lk>
Subject: Re: [Dots] Signal / Data / Alias / Filter Implementation
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, 03 Aug 2017 13:05:34 -0000

>From Roland Dobbins
Sent: 03 August 2017 13:58

> On 3 Aug 2017, at 16:46, Jon Shallow wrote:

> >  to cover the source-*, icmp types and fragmentation as optional 
> > (and
> > hint) entries to handle any future work in Telemetry etc.

> It already should do so.

True if using ietf-access-control-list over data channel

Not true if using ietf-dots-signal over signal channel.

This extra functionality  is not available over the signal channel.

Regards

Jon

v2.23.0 | Report a Bug | By Email