IETF Logo Mail Archive

Re: Genart last call review of draft-ietf-bfd-multipoint-active-tail-09

Greg Mirsky <gregimirsky@gmail.com> Fri, 29 June 2018 16:45 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D10D8130DDB; Fri, 29 Jun 2018 09:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 g6QhoYdQedc8; Fri, 29 Jun 2018 09:45:05 -0700 (PDT)
Received: from mail-lj1-x243.google.com (mail-lj1-x243.google.com [IPv6:2a00:1450:4864:20::243]) (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 A6622130DC1; Fri, 29 Jun 2018 09:45:04 -0700 (PDT)
Received: by mail-lj1-x243.google.com with SMTP id g3-v6so7808788ljk.12; Fri, 29 Jun 2018 09:45:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nVQthTZQtL+xu0QekldhZC4wZUacHAaZ6IkirqGrxRU=; b=HKuKjVqhRsdMBkXlO6rS+W9SUIKGSxFbE8IHDKEyOQbQEVqXvIE890urvuIt7w9fis 56kHRjq7a9nlyaZgCt0hhJVOtUvrPzSRGLcMAMty9nLtaz0mp3ZEIvUcGn4Jj0qGFLku gEaMxPFoHnZDhfyb+9FK/xJkErRC3X/v4Cy5MqYNmN5jawaBrkL5uAXRA3XVVeOuytGB 61IEHYPrXp+ZlhnvhlQPGcaA/Ape8bsHPOELw0kvIOkVgi6FvtlmyPAp8uyG+qLvFodC HbOOwOlF4A7yJGuOJ3P+1LsynaU5oammY8CZX3Dva3fVuCSXdR4GbE7Du0B7wbqhKtwi fBtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nVQthTZQtL+xu0QekldhZC4wZUacHAaZ6IkirqGrxRU=; b=hqS/jldP8C5elX/CsoZiGD79rJ9hsbBjovCiodcGH60RofQboj8XvBFm2m0xWAcGiC NdkI0ly3efsO/7ctTAJEPdlUKWcuQbbFip/WhlhhML4+nOGlbWzEi07TCKYO6mwgf3cd N5XUcjZQe4F9gAVL91KyYUUgDmCGxm0RC9fIbY68cZjQ/HxTWIoVujgq071RNKXdOMur a0zfkP2QHaxgwNCjO+FAstnwBtWuOi1QrofBk3FJikkQjPAKGZaXfW2vhK79wQa+ubfm toJ3d1q+FO+1RgyaFFPPT+i/3TyZft3CrAWD76oP9v42giA3nYFIEhvpSulEVzSkpHyf bpDA==
X-Gm-Message-State: APt69E19euwgIefKnF4thJfwBF2Jym9swc67a4QIbGLdtRpD90GrTThv tsbdh+ez9As4A7f0Cmfah2NSEKRgpElg56v/TEg=
X-Google-Smtp-Source: ADUXVKKeAxTNJ/mqG2LL910/cMNcRRLRWM4ak9g8c4J4eKiGIv0nP5Jawx5isFAxRJs15x4/BHmLac1/FhPj6iFWj30=
X-Received: by 2002:a2e:c52:: with SMTP id o18-v6mr10527714ljd.72.1530290702758; Fri, 29 Jun 2018 09:45:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a2e:6e08:0:0:0:0:0 with HTTP; Fri, 29 Jun 2018 09:45:02 -0700 (PDT)
In-Reply-To: <153021423641.18488.4659084638238812446@ietfa.amsl.com>
References: <153021423641.18488.4659084638238812446@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 29 Jun 2018 09:45:02 -0700
Message-ID: <CA+RyBmU_zRdtSTbogU_4As-YLhhM9OYKWSSgN190cSwLkLzwCQ@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-bfd-multipoint-active-tail-09
To: Linda Dunbar <Linda.dunbar@huawei.com>
Cc: gen-art@ietf.org, rtg-bfd@ietf.org, IETF list <ietf@ietf.org>, draft-ietf-bfd-multipoint-active-tail.all@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bdb75c056fca91db"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/z0RNAWZuvP36qfSJkBdc42r-BBg>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
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: Fri, 29 Jun 2018 16:45:07 -0000

Hi Linda,
thank you for the review and your kind words, much appreciated.

If an end-point during the p2mp BFD session never responded to the head's
multicast poll it is unknown to the head and cannot be reported as
"inactive tail". I can imagine that if the head has been given the list of
the tails, then the unresponsive end-point can be reported as "inactive
tails".

Regards,
Greg

On Thu, Jun 28, 2018 at 12:30 PM, Linda Dunbar <Linda.dunbar@huawei.com>
wrote:

> Reviewer: Linda Dunbar
> Review result: Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-bfd-multipoint-active-tail-??
> Reviewer: Linda Dunbar
> Review Date: 2018-06-28
> IETF LC End Date: 2018-06-18
> IESG Telechat date: 2018-07-05
>
> Summary: clear writing of the procedure.
>
> Major issues: None
>
> Minor issues: None
>
> Nits/editorial comments:
>
> Are End points that not responding considered "Inactive Tails"?  Does the
> HeadEnd report the "Inactive Tails"?
>
> Linda Dunbar
>
>
>

v2.23.0 | Report a Bug | By Email