Mirja Kühlewind's No Objection on draft-ietf-bfd-seamless-ip-04: (with COMMENT)
"Mirja Kuehlewind" <ietf@kuehlewind.net> Tue, 03 May 2016 09:46 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 3175612D6B2; Tue, 3 May 2016 02:46:26 -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 No Objection on draft-ietf-bfd-seamless-ip-04: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160503094626.7542.81246.idtracker@ietfa.amsl.com>
Date: Tue, 03 May 2016 02:46:26 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/Yj26G4-QX9_Gv8IitwSukIVrF3w>
Cc: rtg-bfd@ietf.org, bfd-chairs@ietf.org, draft-ietf-bfd-seamless-ip@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:46:28 -0000
Mirja Kühlewind has entered the following ballot position for draft-ietf-bfd-seamless-ip-04: 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-bfd-seamless-ip/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- This part is unclear to me: "It is, however, possible for an SBFDInitiator to carefully set "your discriminator" and TTL fields to perform a continuity test towards a target, but to a transit network node and not to the target itself. [...] This also requires S-BFD control packets not be dropped by the responder node due to TTL expiry. Thus implementations on the responder MUST allow received S-BFD control packets taking TTL expiry exception path to reach corresponding reflector BFD session." You basically perform a traceroute with (S-)BFD, right? Why do you need the last sentence? Wouldn't it be okay, if the packet get dropped by the responder, to simply re-send with a higher TTL?
- Mirja Kühlewind's No Objection on draft-ietf-bfd-… Mirja Kuehlewind
- Re: Mirja Kühlewind's No Objection on draft-ietf-… Carlos Pignataro (cpignata)