[Sidrops] Mirja Kühlewind's Discuss on draft-ietf-sidrops-lta-use-cases-05: (with DISCUSS)

Mirja Kühlewind via Datatracker <noreply@ietf.org> Mon, 29 April 2019 13:47 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CFD14120365; Mon, 29 Apr 2019 06:47:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-sidrops-lta-use-cases@ietf.org, Chris Morrow <morrowc@ops-netman.net>, sidrops-chairs@ietf.org, morrowc@ops-netman.net, sidrops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
Message-ID: <155654565583.15899.253597532069368895.idtracker@ietfa.amsl.com>
Date: Mon, 29 Apr 2019 06:47:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/OBvONtCLpjDeKkOg5f7sEpYl4-4>
Subject: [Sidrops] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ie?= =?utf-8?q?tf-sidrops-lta-use-cases-05=3A_=28with_DISCUSS=29?=
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2019 13:47:43 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-sidrops-lta-use-cases-05: Discuss

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:


1) I’m not sure I really understand the following use case..? Also is
“re-routing to acceptable content” actually a use case we want to endorse in an
RFC? "Alice is responsible for the trusted routing for a large
   organization, commercial or geo-political, in which management
   requests routing engineering to redirect their competitors' prefixes
   to socially acceptable data.

 2) This sentence in the security considerations section uses normative
 language without having the respective disclaimer in the document:
“Hence they MUST be implemented to assure the
   local constraint.”
However, I also don’t understand what such a normative statement is supposed to
say. I’m not sure if local trust actors are the only solution to the stated use
case/problems; if that’s what the sentence tries to say, I disagree, however,
in any case it doesn’t seem to make sense to use normative wording here.

 3) Also, this sentence in the security consideration section, needs probably
 more explanation:
   “Authentication of modification 'recipes' will be needed.”
   What is “will be needed” supposed to mean? How can this be achieved? What
   happens if it’s not implemented?