[pim] Fwd: New Version Notification for draft-mirsky-pim-bfd-p2mp-use-case-02.txt
Greg Mirsky <gregimirsky@gmail.com> Thu, 28 June 2018 00:24 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F81A130E4A; Wed, 27 Jun 2018 17:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, 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 nx4nzCQKYxOe; Wed, 27 Jun 2018 17:24:41 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 9D8F5130E54; Wed, 27 Jun 2018 17:24:40 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id l12-v6so3029396lja.1; Wed, 27 Jun 2018 17:24:40 -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; bh=9V5VRyW8c+JP/0e9RqXYN1u2TomzatgRgENh9Sgva6M=; b=YGtutqWdjDHWoWMRDRQGrz/jnZ9+CGFoqn2BK6+QGut/I87Q4TGPGaydPgTCa1JOng MZA542suYhEVY6Grd3bElGUjdMAkKAHiVnG8+bFYqdckn08dnGGx0AfU4yMD4eYl4H6C Jk4iKukYnIBMOxEKGIEtV1KhtKnF0MHtwJq/bZov4Fk14R7Ecv29gXik/DBk0HtyTq5d xHtXfOXHLrWgmTbWTdmhjcCbnO8VVUhjnuuczaKXqq9Jxo8M1CHOd/DmCbTR59jVB3lQ qlu3/OqUjxAKhuasrtzFK1kv2O7dndgA1xHjSEkf+ATTsE3EFLaq/1Fn7JwnQqBcQL1E O9Fg==
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; bh=9V5VRyW8c+JP/0e9RqXYN1u2TomzatgRgENh9Sgva6M=; b=gwJRy8U+1wtceQeV+qyersyYO/rXINAE9UtUNE1FWu5stBMIgGSIf1EuRrtyjR7OZd 2qMCDqtA+ZiwF/hPTUwxWEh00mwkHrairXUXC+x03oaVK2YfdItzHdykxxyMyG/osDPN xLd8/XoJgECRa6PSjgb05Y2uv6aphRjjr7J4X4lY9F6y6al0NY5xagErVC0G0XZe6uZ8 MeWBJOdWMT06TTHU0yAVwoAu0mvWNeCspU1ArSPNIb4zqIHkAAi0to9quzXI+QxVRD5n +JSJEvfBvPUaNPNY/RZYordfe8lnm8XiL18Qe/utZtC9ZjyOUNPTQnVmHwCj3ED6GnES veTw==
X-Gm-Message-State: APt69E2dr5hR3bFY93jFnmnqQY9U7Da5VgeKHym/Dc5aI0sh/rFTLuZF qBle5/ZQDOkX6srHegnl/Ac0nn7mtFNZl4zjZ4c=
X-Google-Smtp-Source: ADUXVKKh8sQfO2a5sUaRtIo+dWEArxPmuiP6iQI6jJWbNR0+Rtdmelml9Bv+qgVcyvTuN2aH/fARIN/ILg1cumJEDyc=
X-Received: by 2002:a2e:534e:: with SMTP id t14-v6mr5248937ljd.73.1530145478507; Wed, 27 Jun 2018 17:24:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a2e:6e08:0:0:0:0:0 with HTTP; Wed, 27 Jun 2018 17:24:37 -0700 (PDT)
In-Reply-To: <153014505217.15447.15073934942116107591.idtracker@ietfa.amsl.com>
References: <153014505217.15447.15073934942116107591.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 27 Jun 2018 17:24:37 -0700
Message-ID: <CA+RyBmXm-QaAVVy+wHq3fwMwjwyeVKY+2jc_n47bVme5D3gMEQ@mail.gmail.com>
To: pim-chairs@ietf.org, pim@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b38479056fa8c129"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/_3EDZ2eg4gLx7Zy321qqNgLKSZI>
Subject: [pim] Fwd: New Version Notification for draft-mirsky-pim-bfd-p2mp-use-case-02.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2018 00:24:44 -0000
Dear All, many thanks to Stig Venaas and Mankamana Mishra for many helpful comments and great discussion. We've expanded the scope of the document to explore applicability of p2mp BFD to cases beyond DR and BDR monitoring by PIM-SM routers on a shared-media link. And, as Stig have suggested, specified that a tail removes the monitored PIM-SM neighbor (head of p2mp BFD session) it detects the latter had failed. Welcome your questions, comments, suggestions. Regards, Greg ---------- Forwarded message ---------- From: <internet-drafts@ietf.org> Date: Wed, Jun 27, 2018 at 5:17 PM Subject: New Version Notification for draft-mirsky-pim-bfd-p2mp-use-case-02.txt To: Gregory Mirsky <gregimirsky@gmail.com>, Ji Xiaoli <ji.xiaoli@zte.com.cn> A new version of I-D, draft-mirsky-pim-bfd-p2mp-use-case-02.txt has been successfully submitted by Greg Mirsky and posted to the IETF repository. Name: draft-mirsky-pim-bfd-p2mp-use-case Revision: 02 Title: Bidirectional Forwarding Detection (BFD) for Multi-point Networks and Protocol Independent Multicast - Sparse Mode (PIM-SM) Use Case Document date: 2018-06-27 Group: Individual Submission Pages: 6 URL: https://www.ietf.org/internet-drafts/draft-mirsky-pim-bfd- p2mp-use-case-02.txt Status: https://datatracker.ietf.org/doc/draft-mirsky-pim-bfd-p2mp- use-case/ Htmlized: https://tools.ietf.org/html/draft-mirsky-pim-bfd-p2mp-use- case-02 Htmlized: https://datatracker.ietf.org/doc/html/draft-mirsky-pim-bfd- p2mp-use-case Diff: https://www.ietf.org/rfcdiff?url2=draft-mirsky-pim-bfd- p2mp-use-case-02 Abstract: This document discusses the use of Bidirectional Forwarding Detection (BFD) for multi-point networks to provide nodes that participate in Protocol Independent Multicast - Sparse Mode (PIM-SM) with the sub- second convergence. Optional extension to PIM-SM Hello, as specified in RFC 7761, to bootstrap point-to-multipoint BFD session. also defined in this document. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat