[Teas] Roman Danyliw's No Objection on draft-ietf-teas-yang-te-types-10: (with COMMENT)

Roman Danyliw via Datatracker <noreply@ietf.org> Thu, 22 August 2019 02:44 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: teas@ietf.org
Delivered-To: teas@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E32CB120019; Wed, 21 Aug 2019 19:44:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-teas-yang-te-types@ietf.org, Lou Berger <lberger@labn.net>, teas-chairs@ietf.org, lberger@labn.net, teas@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <156644187592.25712.14344476423196091642.idtracker@ietfa.amsl.com>
Date: Wed, 21 Aug 2019 19:44:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/9C3hRD3imFBVB6w5qtPS1zmRxc8>
Subject: [Teas] Roman Danyliw's No Objection on draft-ietf-teas-yang-te-types-10: (with COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2019 02:44:36 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-teas-yang-te-types-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-types/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I concur with Ben Kaduk and Mirja Kühlewind comments about the utility of
additional context for the model.

Section 7.  Other models will import this one, and specific security
considerations will have to be written for them.  Nevertheless, the general
caution provided here could be a bit more specific perhaps on the order of:

-- Per “Write operations (e.g., edit-config) to these data nodes without proper
protection can have a negative effect on network operations”, doesn’t seem to
adequately cover security/privacy issues such as misrouting of traffic for
eavesdropping/inspection, circumventing existing defenses, modification or
replay; and business operation issues such as increased transit bills due to
inappropriate/malicious configuration.

-- Per “The access to such data nodes may be considered sensitive or vulnerable
in some network environments” doesn’t explain the rationale such as that
revealing detailed information about network configuration could exploited in
future attacks.