IETF Logo Mail Archive

Re: [Dots] use of restconf for the data channel?

"Clark, Gilbert J. (GRC-LCA0)" <gilbert.j.clark@nasa.gov> Wed, 22 February 2017 05:56 UTC

Return-Path: <gilbert.j.clark@nasa.gov>
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 8FDA8129619 for <dots@ietfa.amsl.com>; Tue, 21 Feb 2017 21:56:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nasa.gov
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 X03jVmUhB2Ve for <dots@ietfa.amsl.com>; Tue, 21 Feb 2017 21:56:14 -0800 (PST)
Received: from ndjsvnpf101.ndc.nasa.gov (NDJSVNPF101.ndc.nasa.gov [198.117.1.151]) (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 2B2C912961D for <dots@ietf.org>; Tue, 21 Feb 2017 21:56:14 -0800 (PST)
X-Comment: SPF check N/A for local connections - client-ip=198.117.1.198; helo=ndjsppt104.ndc.nasa.gov; envelope-from=gilbert.j.clark@nasa.gov; receiver=dots@ietf.org
DKIM-Filter: OpenDKIM Filter v2.11.0 ndjsvnpf101.ndc.nasa.gov C80C840000B4
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nasa.gov; s=letsgomars; t=1487742972; bh=3Eh1uJTmxECk4JFR+x68fiI8gVqNxg0O06o6PLxij4U=; h=From:To:Subject:Date:References:In-Reply-To:From; b=CSWtHGUZ3HbhEcry6yFYftlTLxEVr3nPc0FLMPaYwh0t8jwlGUXvyUW89CAF2H22l 6YK1XK+gUFl5UNGyehfNrAQw78RdPpvslXWuDwt0vGzInGkQJfmdABAfYARSqdbI11 fDpx4pXyIMIqDLuOLGYWqLsXgINoGLMiGy8xYsOIwMX/2tzj6g0MjJopQsYdlwexbP Oi5vw90SR0V6sSEyLEEHopPyP3lnt/Bk8XBcLMAYsw+f95aOgtC8j11rAJrHz3FLa6 HXNbHTj4Mp97N+Czjzid1SC1dry3PwbhepBiNOIz021KCGL6Jk9Ny6FkKJtepWE+Vg L5ciFoY7sBEAQ==
Received: from ndjsppt104.ndc.nasa.gov (ndjsppt104.ndc.nasa.gov [198.117.1.198]) by ndjsvnpf101.ndc.nasa.gov (Postfix) with ESMTP id C80C840000B4; Tue, 21 Feb 2017 23:56:12 -0600 (CST)
Received: from pps.filterd (ndjsppt104.ndc.nasa.gov [127.0.0.1]) by ndjsppt104.ndc.nasa.gov (8.16.0.20/8.16.0.20) with SMTP id v1M5kM9C001085; Tue, 21 Feb 2017 23:56:12 -0600
Received: from ndjscht109.ndc.nasa.gov (ndjscht109-pub.ndc.nasa.gov [198.117.1.209]) by ndjsppt104.ndc.nasa.gov with ESMTP id 28s1es0gsr-1; Tue, 21 Feb 2017 23:56:12 -0600
Received: from NDJSMBX201.ndc.nasa.gov ([169.254.4.228]) by NDJSCHT109.ndc.nasa.gov ([198.117.1.179]) with mapi id 14.03.0319.002; Tue, 21 Feb 2017 23:56:12 -0600
From: "Clark, Gilbert J. (GRC-LCA0)" <gilbert.j.clark@nasa.gov>
To: "Roman D. Danyliw" <rdd@cert.org>, "Mortensen, Andrew" <amortensen@arbor.net>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: use of restconf for the data channel?
Thread-Index: AQHShUvelq2Fax0X1U+DAQQ/dairhqFqKpDAgApPffE=
Date: Wed, 22 Feb 2017 05:56:11 +0000
Message-ID: <5AE9F2D3F5799545818A4795DA145E7103BC588B@NDJSMBX201.ndc.nasa.gov>
References: <6AE56175-DBE7-4CD9-BA4E-5DCA88E901D8@arbor.net>, <359EC4B99E040048A7131E0F4E113AFC0104F01D17@marathon>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC0104F01D17@marathon>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [75.118.191.143]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-22_03:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/3k-Td50UeZj5EOXbRz4my95hObs>
Subject: Re: [Dots] use of restconf for the data channel?
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: Wed, 22 Feb 2017 05:56:15 -0000

Hi:

My strongest objection to both NETCONF and RESTCONF were in the context of their consideration for use in the signal channel.

I wouldn't personally vote to see NETCONF, specifically, used in either channel.  NETCONF can involve substantial implementation complexity to support capabilities that, in the case of DOTS, seem to me to be of marginal utility at best.

The use of RESTCONF seems a little more reasonable to me here since many of those implementation requirements are relaxed.  

I will note that adoption of RESTCONF will inflict a 100+ page not-yet-RFC as (additional) required reading for anyone who wishes to implement a DOTS data channel from scratch.  Also, note that the use of RESTCONF would introduce a dependency on something that is still in development, and that therefore most likely hasn't yet been very well tested and / or may be subject to change.

Just offering some clarification on my original opinion(s), for what that's worth.

-Gilbert
_________________________________
From: Dots [dots-bounces@ietf.org] on behalf of Roman D. Danyliw [rdd@cert.org]
Sent: Wednesday, February 15, 2017 9:51 AM
To: Mortensen, Andrew; dots@ietf.org
Subject: Re: [Dots] use of restconf for the data channel?

> Subject: [Dots] use of restconf for the data channel?
> [snip]
>
> Since RESTCONF is now a concrete proposal, it seems
> worthwhile continuing the debate ahead of the interim
> meeting.  Are there specific concerns in the WG
> regarding the use ...

This discussion topic is one we need to resolve.  We can start here on the list but I'll also add a slot to the interim meeting to continue the conversation.

Roman

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

v2.23.0 | Report a Bug | By Email