[Lsr] Roman Danyliw's Discuss on draft-ietf-isis-segment-routing-extensions-24: (with DISCUSS and COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Wed, 15 May 2019 19:17 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: lsr@ietf.org
Delivered-To: lsr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F1B12001B; Wed, 15 May 2019 12:17:55 -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-isis-segment-routing-extensions@ietf.org, Christian Hopps <chopps@chopps.org>, Uma Chunduri <uma.chunduri@huawei.com>, aretana.ietf@gmail.com, lsr-chairs@ietf.org, uma.chunduri@huawei.com, lsr@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <155794787548.30479.12106710565768543060.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 12:17:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/grOBfxlWS5IMSQlOdqBc4qTH9k0>
Subject: [Lsr] Roman Danyliw's Discuss on draft-ietf-isis-segment-routing-extensions-24: (with DISCUSS and COMMENT)
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 19:17:56 -0000
Roman Danyliw has entered the following ballot position for draft-ietf-isis-segment-routing-extensions-24: 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: https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I need a bit of help understanding how to read the Security Considerations text – threats are identified but how they are mitigated seems implicit. The text, “In general the same types of attacks … However, the latter will be more difficult to detect …”, alludes to a similar threat without a reference and seems to suggest it will be worse in the deployed environment of this extension. The next paragraph, “Existing security extensions … [RFC5304] and [RFC5310] apply …” states that [RFC5304] and [RFC5310] also apply. What does apply mean here – should they be used? Do they mitigate what’s described in the previous paragraph? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Section 2.3. Typo. s/advertsied/advertised/
- [Lsr] Roman Danyliw's Discuss on draft-ietf-isis-… Roman Danyliw via Datatracker
- Re: [Lsr] Roman Danyliw's Discuss on draft-ietf-i… Les Ginsberg (ginsberg)
- Re: [Lsr] Roman Danyliw's Discuss on draft-ietf-i… Roman Danyliw