Mirja Kühlewind's Discuss on draft-ietf-bfd-seamless-base-09: (with DISCUSS)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Tue, 03 May 2016 09:35 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: rtg-bfd@ietf.org
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A0B8812D1B6; Tue, 3 May 2016 02:35:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kuehlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
Subject: Mirja Kühlewind's Discuss on draft-ietf-bfd-seamless-base-09: (with DISCUSS)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160503093512.7446.68991.idtracker@ietfa.amsl.com>
Date: Tue, 03 May 2016 02:35:12 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/PpI4A1aRvs3JBBKRiPfde3BaVDQ>
Cc: rtg-bfd@ietf.org, draft-ietf-bfd-seamless-base@ietf.org, bfd-chairs@ietf.org
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2016 09:35:12 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-bfd-seamless-base-09: 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-bfd-seamless-base/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

As S-BFD has no initiation process anymore it is not guarenteed that the
receiver/responder actually exists. That means that packets could float
(uncontrolled) in the network or even outside of the adminstrative domain
(e.g. due to configuration mistakes). From my point of view this document
should recommend/require two things:

1) A maximum number of S-BFD packet that is allow to be send without
getting a response (maybe leading to a local error report).

2) Egress filtering at the adminstrative border of the domain that uses
S-BFD to make sure that no S-BFD packets leave the domain.