Re: [Bier] Feedback on draft-hu-bier-bfd-02

Greg Mirsky <gregimirsky@gmail.com> Thu, 08 November 2018 05:18 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADE7B126CB6; Wed, 7 Nov 2018 21:18:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level:
X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1c-u_ysGhf7I; Wed, 7 Nov 2018 21:18:39 -0800 (PST)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7040127332; Wed, 7 Nov 2018 21:18:38 -0800 (PST)
Received: by mail-lj1-x231.google.com with SMTP id e5-v6so12728039lja.4; Wed, 07 Nov 2018 21:18:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6w/e2aNMmGuXcvLIXsTEw1S2B2L7NYTAMbi9xaXjBD8=; b=u4B9nOjqrVbNfFmKKgXnIWmDiBUWPVv0Bf9b2A6Bmbat7cXF8huexR8dyLYKjKzQ58 cn9Bv58tRyOpYuIH1y1w93gUnDZCbn8FprhJoOzPjYkOm8EG0EhXfg1qO80Vq2NYidNa obVtSWFU+mmef6l6evFucp1GcsQW2DdMfd1Nm7khGsbCM/W9Nm8qDORM2xYUfHnR8PiV t8BXxZyUZaG8bDZ8kncf1vm6geZlXtkLEwYklB/R4xemsngJTO/mfRT5gI9iKKUaAdrA OTsvhkQh82DFlS7SfKUCWxTn6KckMvInw2newVNdY4u+c4abCIhNY1ourjlLdVX5q+rd 82gA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6w/e2aNMmGuXcvLIXsTEw1S2B2L7NYTAMbi9xaXjBD8=; b=VxYoB41bbVHDqzGLlNjZC0x7ErEHLNwrMeElSl8gO2QTRMC4zzTouASXWsOSh7UTKG FVu5ywZOns/JD0pl2HDWkc8h5l0UN6fdYTcLqkHl5VaeyeNxgPFy4l5vmEFP9vKvKnnN PW5rONh5Zux9IHx1dVv2BUTSPixr5DMxf7zL/ctKpYsMtwmfdic0MzMsHYf+J6UIyG37 EsR1zyCix0uoe48Fak2cJTJHzYkWK8L3iM7l5Cl+ckIla4mKHuJTpos8j4YlMmaZwC8Y 37yWPz5X3zIB1aTEfho2VjdTYX2EY+wWtu4d2WtCtU+WrGfWQlH1dOk/zYl+XTRfCtqK CO2A==
X-Gm-Message-State: AGRZ1gKvt5+t4MG7SnTaV5wZva0KNNtw5aKphNciv0Ov4XW/HTOQRP5W 4TRy2K3hCxEhExb+WpHx2ZfXwr1CFDgkd8tkM14=
X-Google-Smtp-Source: AJdET5ce9b6cXwlOUF3N/MCaYYl6m8YrBuETGqc+UET9UuKTsZEOi0VLWgLhoChdpY9DGmHHaiX0R4Lr3ck5ZzqKTKI=
X-Received: by 2002:a2e:7d15:: with SMTP id y21-v6mr1593261ljc.77.1541654316473; Wed, 07 Nov 2018 21:18:36 -0800 (PST)
MIME-Version: 1.0
References: <CE547BEC-C580-4CC6-8B9B-CB22EE07E948@cisco.com> <201811081227199234176@zte.com.cn>
In-Reply-To: <201811081227199234176@zte.com.cn>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 08 Nov 2018 12:18:27 +0700
Message-ID: <CA+RyBmV54zYMpq-+H66CxC_8XriAZmYt02tK3y_oo_mU1hj6-A@mail.gmail.com>
To: hu.fangwei@zte.com.cn
Cc: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, draft-hu-bier-bfd@ietf.org, BIER WG <bier@ietf.org>, bfd@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e66b1c057a205d51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/BaHQtW2MSoqd4FiMxq5Gv8n6s3Y>
Subject: Re: [Bier] Feedback on draft-hu-bier-bfd-02
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2018 05:18:42 -0000

Hi Reshad,
thank you for taking the time to review and sharing your comments, much
appreciated. I'll add to answers by Fangwei, please find them in-line
tagged GIM>>.

Regards,
Greg

On Thu, Nov 8, 2018 at 11:27 AM <hu.fangwei@zte.com.cn> wrote:

> Hi, Rahman
>
> Thanks for your comments.
>
> Plese see inline marked with[hfw].
>
>
> >Hi,
>
>
>
> >I just took a quick look at the draft:
>
> >1.Section 1, 2nd paragraph mentions “…detect unicast failures..”, I
> believe this  should be unidirectional?
>
> [hfw] Agree, the BFD multipoint document only defines the unidirectional
> deteck from header to one or more tails.
>
GIM>> Great catch, thank you. Will fix in the next version.

> >2.Section 1, 3rd paragraph says that active-tail is for further study.
> So when a tail detects a failure, how will the head be notified?  If the
> head does not have to be notified, what action is taken?
>
> [hfw] Ok. Actually, we are considering the active-tails solution. It  will
> be added in the next version.
>
GIM>> Our plan is to use BFD for Multipoint Network with Active Tail
specfication as the base for this mode. Since tails in p2mp BFD are in the
Demand mode the head only can query all tail and/or the particular tail
using the Poll sequence (referred as multicast and unicast Poll). Depending
on the type of the failure, the head may recieve or not the BFD control
message with Final flag set. Absence of the response in combination with
the content of the Diag field must be used to draw the conclusion on
liveleness of the path from the head to the particular tail. From here the
head may use BIER Ping to localize the defect and switch to using the
alternative path through the BIER domain by using different transient BFRs.

>
> Regards
>
> Fangwei.
> *发件人:*ReshadRahman(rrahman) <rrahman@cisco.com>
> *收件人:*draft-hu-bier-bfd@ietf.org <draft-hu-bier-bfd@ietf.org>;
> *抄送人:*bier@ietf.org <bier@ietf.org>;bfd@ietf.org <bfd@ietf.org>;
> *日 期 :*2018年11月08日 11:56
> *主 题 :**Feedback on draft-hu-bier-bfd-02*
>
> Hi,
>
>
>
> I just took a quick look at the draft:
>
>    1.
>
>    Section 1, 2nd paragraph mentions “…detect unicast failures..”, I
>    believe this  should be unidirectional?
>    2.
>
>    Section 1, 3rd paragraph says that active-tail is for further study.
>    So when a tail detects a failure, how will the head be notified?  If the
>    head does not have to be notified, what action is taken?
>
>
>
> Regards,
>
> Reshad.
>
>
>