IETF Logo Mail Archive

Re: [Dots] New Version Notification for draft-ietf-dots-requirements-16.txt

Benjamin Kaduk <kaduk@mit.edu> Wed, 24 October 2018 03:28 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 137F0128CFD for <dots@ietfa.amsl.com>; Tue, 23 Oct 2018 20:28:14 -0700 (PDT)
X-Quarantine-ID: <7_BUftuJwqJN>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char 9C hex): Received: ...s kaduk@ATHENA.MIT.EDU)\n\t\234by outgoing.mit[...]
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 7_BUftuJwqJN for <dots@ietfa.amsl.com>; Tue, 23 Oct 2018 20:28:12 -0700 (PDT)
Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) (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 16A50130DD8 for <dots@ietf.org>; Tue, 23 Oct 2018 20:28:11 -0700 (PDT)
X-AuditID: 1209190e-111ff70000002651-2c-5bcfe6ca5e55
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 1F.6C.09809.AC6EFCB5; Tue, 23 Oct 2018 23:28:10 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-1.mit.edu (8.14.7/8.9.2) with ESMTP id w9O3S9ci028275; Tue, 23 Oct 2018 23:28:09 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) �by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id w9O3S5Ka028804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 23 Oct 2018 23:28:07 -0400
Date: Tue, 23 Oct 2018 22:28:04 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: mohamed.boucadair@orange.com
Cc: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, "Mortensen, Andrew" <Andrew.Mortensen@netscout.com>, dots <dots@ietf.org>
Message-ID: <20181024032804.GU45914@kduck.kaduk.org>
References: <154023914707.13766.12718384264915087037.idtracker@ietfa.amsl.com> <C16759A2-824F-40F6-88DC-81BAC88AC566@netscout.com> <BN6PR16MB14252CF0618E3D6AED857DECEAF50@BN6PR16MB1425.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302E019E49@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302E019E49@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFKsWRmVeSWpSXmKPExsUixCmqrHvq2flog9+HjS0+9P9mtFj75gir xeG3T9ktfh88z+bA4rFkyU8mj+bND1k8HjSwerQ8O8kWwBLFZZOSmpNZllqkb5fAlfHz9Cqm guM8Ff/OzmZpYFzK1cXIySEhYCLRu3wHSxcjF4eQwBomicNHjkI5Gxkl3uybyATh3GWS2HRo EztIC4uAqsS3Na/YQGw2ARWJhu7LzCC2iICCxL62frBuZoGFjBKn1h8ESwgL+EpsWT4HrJkX aN/fxatYIaauZ5LY+WMbG0RCUOLkzCcsIDazgI7Ezq13gOIcQLa0xPJ/HBBheYnmrbPBZnIK JEn0PP4FZosKKEvs7TvEPoFRcBaSSbOQTJqFMGkWkkkLGFlWMcqm5Fbp5iZm5hSnJusWJyfm 5aUW6Rrr5WaW6KWmlG5iBEeAJN8OxkkN3ocYBTgYlXh4D9SejxZiTSwrrsw9xCjJwaQkynv1 MFCILyk/pTIjsTgjvqg0J7X4EKMEB7OSCK+yBlCONyWxsiq1KB8mJc3BoiTOO6FlcbSQQHpi SWp2ampBahFMVoaDQ0mCNxQY6UKCRanpqRVpmTklCGkmDk6Q4TxAw3NAaniLCxJzizPTIfKn GI05fn3/O52Z40tT5wxmIZa8/LxUKXGIcQIgpRmleXDTQElMInt/zStGcaDnhHmjngJV8QAT INy8V0CrmIBWXVc/A7KqJBEhJdXA2P84/d6PX/lMy//YrzSxY6lTfN0y75JYV1IHj+Ysvv4D uXceK3mYBzanZ1z2Lg9KLtTnDN2fs1SLKXbStYMvdxarGWoHtC9Lmq2l6HXvKMN7g48JrH4v p/VLz/mxrO34cyers7E6PR4XmDfk/JY5zvffaP8eRWcHrdSPBxzOiDXWLUsv7tuixFKckWio xVxUnAgAdbIyAj0DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/FRMCTbo5I4p3Bpqv24QCX9QpAUY>
Subject: Re: [Dots] New Version Notification for draft-ietf-dots-requirements-16.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, 24 Oct 2018 03:28:14 -0000

On Tue, Oct 23, 2018 at 12:28:00PM +0000, mohamed.boucadair@orange.com wrote:
> Hi Tiru,
> 
> Also, the data-channel will be updated to make use of accept- and drop-list.
> 
> Please see inline.
> 
> Cheers,
> Med
> 
> De : Dots [mailto:dots-bounces@ietf.org] De la part de Konda, Tirumaleswar Reddy
> Envoyé : mardi 23 octobre 2018 11:20
> À : Mortensen, Andrew; dots; Benjamin Kaduk
> Objet : Re: [Dots] New Version Notification for draft-ietf-dots-requirements-16.txt
> 
> Based on the updated DOTS requirements, following changes are required to DOTS protocol drafts:
> 
> [1] In the updated requirement GEN-001, version number to distinguish protocol revisions is removed.  Remove "Uri-Path: "v1.0"" from the DOTS signal channel specification. We have already introduced
> comprehension-mandatory and comprehension-required parameters in DOTS signal channel protocol to accommodate future protocol extensions and backward compatibility.
> 
> [Med] Yes.
> 
> [2]
> CIDR notation is not used for IPv4 prefix in https://tools.ietf.org/html/rfc6991, updated SIG-008 requirement does not refer to CIDR notation; will remove the following line from the DOTS signal and data channel drafts :
> "Prefixes are represented using Classless Inter-Domain Routing (CIDR) notation [RFC4632]."
> 
> [Med] We are using cidr notation (even if 4632 is not explicitly cited in 6991).

CIDR notation is still generally a good thing; my comment on
dots-requirements was just that we have no *protocol-level* requirement to
use it.  I wasn't trying to say that we should stop using it.

-Ben

v2.23.0 | Report a Bug | By Email