Fwd: New Version Notification for draft-mirsky-pim-bfd-p2mp-use-case-02.txt

Greg Mirsky <gregimirsky@gmail.com> Thu, 28 June 2018 20:29 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 533D21310A0; Thu, 28 Jun 2018 13:29:17 -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 FAYB6s6xLH3h; Thu, 28 Jun 2018 13:29:15 -0700 (PDT)
Received: from mail-lj1-x242.google.com (mail-lj1-x242.google.com [IPv6:2a00:1450:4864:20::242]) (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 D2BCB1292F1; Thu, 28 Jun 2018 13:29:14 -0700 (PDT)
Received: by mail-lj1-x242.google.com with SMTP id o26-v6so5526188ljg.3; Thu, 28 Jun 2018 13:29:14 -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=iCkBa8YwZjf2vStEN7ELJFWll+iZWIzs0fhxGnG08VQ=; b=l5fxlQXnDkmuCqYcoAr/H2utQOgylvwSY5tHF6isnKOJ8CnmUuaHuBvnfEO7Qlt0lx RNUgaCj0NVLl3NNkGEafULkWdeHWW8QSLX7IkwaQzDxEhPL6y21ZSq0WUxCtaJUUy/gp sRxIEzMu50xr2BgPrl4xY7pUuvbuDY3w6Jans5w9xPUnbMrzQr89zZ3JmcU7nBGXI3uk VB78VveIjWFM7z6eFZE3mCvbRDIqT/KtoNQI1AqLQBXTvv5zBZctRrK1FLHd35xgQaAb O0W3OQGZGwP9X3rWlO6+N4IumGf8Ak5SCh38LIgBDIhotgI7et9Pa+Z7oXfPIWgqKAHM 3ChA==
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=iCkBa8YwZjf2vStEN7ELJFWll+iZWIzs0fhxGnG08VQ=; b=UlQCUi8new6EsFYLUct40RxHHCEAUdzmTvEIh7D/Z4AE7CxMEzWsVDm/+Y0QgiD67S GGiGcYSyPRHEJsewVL6fK7sU6Y/W6kwKSPXb7wc8te3jq4WLdEQY083cJ8OcrTSuM/XL /cXcoPtcziq/DnldvwWRgbU9M1QvPeTEVut0DgHXPfalBA8K7lVnahXdflCWU47nIOut kWuoierEnBifXqoJHTKrhS+GNkv6uyAUsQaOu+P6XT3r4traEdok8gM8R3OTmLX2g7OP PbY2/wspiVE1Zua1cKpF5oQ6pK5c+2rsQNRc5dhnaXDPEDEyVa2Rpndn4M0BgfcMuRo/ i/2g==
X-Gm-Message-State: APt69E0M56cyioA5KZyF90gGdRQyKQzXoVXm4i/1vTMLHtzDKwLSX6Nh StQTRh8RcRD6Y9/4RyRi6cTimf00UsFYFuy/U5Y=
X-Google-Smtp-Source: AAOMgpfWqVssWS0bhDxI3DjXBuHCO2CjFCuK8NacaskK9KzxwaPhob/0AFptpGkat/hbm7t6d5D/NOTqkxxKSHcB4rg=
X-Received: by 2002:a2e:87da:: with SMTP id v26-v6mr7741228ljj.69.1530217752708; Thu, 28 Jun 2018 13:29:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a2e:6e08:0:0:0:0:0 with HTTP; Thu, 28 Jun 2018 13:29:12 -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: Thu, 28 Jun 2018 13:29:12 -0700
Message-ID: <CA+RyBmWCcz2=N7r8xqEJPYgK-d0bSt7cOJ9e3AUZC73ai7NGVA@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-mirsky-pim-bfd-p2mp-use-case-02.txt
To: RTGWG <rtgwg@ietf.org>, Service Function Chaining IETF list <sfc@ietf.org>, NVO3 <nvo3@ietf.org>, BIER WG <bier@ietf.org>, int-area@ietf.org, detnet@ietf.org
Content-Type: multipart/alternative; boundary="00000000000094523b056fb995b7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/1adBFUVkf-MfBuV0oB9Tu8vpyes>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2018 20:29:18 -0000

Dear All,
I hope that this new draft will be of interest to those working on
overlay encapsulations. Appreciate your comments, questions, and
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>om>, 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