Fwd: New Version Notification for draft-ietf-bess-mvpn-fast-failover-03.txt

Greg Mirsky <gregimirsky@gmail.com> Fri, 04 May 2018 17:42 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 8D3AA126FDC; Fri, 4 May 2018 10:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 7XAt4YYPDFmL; Fri, 4 May 2018 10:42:27 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 EF3EC12422F; Fri, 4 May 2018 10:42:26 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id y14-v6so31697804lfy.12; Fri, 04 May 2018 10:42:26 -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=ypl5WITBz2+MbDy3fE1jmEqc4Qdw0IjU8huUJ6E1z4g=; b=YKaDJCCbTAH9xf3mzQ/RrBiEajUoL1xUF77VmbccIKDlLLdeaIbbPLyvV+VTlvRGjI hcMPJpuRFIBcERhZYIntDut6Klu6QlcI1nPNKl23r3BNXJJzHUX33mm40QxkuE0pHqvw lG1+QzjOXMuNsG2sWgDSzgxEaC0WwkwCmGHYu7AA6SpupYyDWRt47q4VXfGG6kzt2YVo Cs9LxhT6Q4s2Wd5HgX/oS9bSebwTzCMlfsJcbDOuLj8/QwEXDJn0WDon7iFYdmEDcTnj /0rDQrnrfIxP6HEE6jwQgfvaVmnDeH6n45ezrRmTtEdH1kN+IbFtEijV+hB5RZ+JGz+d P3LQ==
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=ypl5WITBz2+MbDy3fE1jmEqc4Qdw0IjU8huUJ6E1z4g=; b=cKNQAHAh4PU53zn31pL6oUAgJzUVI0bM4/vtKnX7ugo558eT+LCMXZYap2Ypty/kNN eJZZh8k+652qiTYZ/X0U48qN3TgM2hlLDfmPCSIhK/ArVNWB05z0Zfk1KAUr4RDjjXnw 8CwjCY6aVFfcGeeUnsfKHYNYKNqtYxvH3c6ToiwfqRRaj8kW76cDjOmzlbp5x2f0G4p/ 4zuysi35UsUbk2sj5uGVIbzHApc8xJN+0C8C5Sp/aFm9tvxWwAIGhuK/r5MPaYmSu5a9 LxjdeLc0odaBxIr1DlVXzi/WC87dL8OXSb2mrKve+AnVQVjAUK7T5nYCOCxxeNshWvYv jSLw==
X-Gm-Message-State: ALQs6tDJzquOVpXEqWwiwxb91hllM/PxR5kfDclLvOw1Vi7uJ5bUH3I6 zotGxWo/JGHnjMpANuCFO/JRjlP0Oe/WbaZtU0s=
X-Google-Smtp-Source: AB8JxZoJ5oBelqHLCeKqz2txI4kCuwVgt6PfxDKBTX18cXLDsH1iNVATeRFMSjD3b40iKyC6Nmb39mdbVfucp+gzB4Y=
X-Received: by 2002:a19:d853:: with SMTP id p80-v6mr4847208lfg.36.1525455744240; Fri, 04 May 2018 10:42:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.133.13 with HTTP; Fri, 4 May 2018 10:42:23 -0700 (PDT)
In-Reply-To: <152544745742.11693.18095019632093905418.idtracker@ietfa.amsl.com>
References: <152544745742.11693.18095019632093905418.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 04 May 2018 10:42:23 -0700
Message-ID: <CA+RyBmXq-iSFEHW6T1uWCTe1zWavQPLcYMixyUDj8GsW-CORKw@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-ietf-bess-mvpn-fast-failover-03.txt
To: BESS <bess@ietf.org>, rtg-bfd@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c1928e056b64d76c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/wQOhY6p9L3Z7f29VpNx_yRsCTZg>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
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, 04 May 2018 17:42:29 -0000

Dear All,
the new version clarifies the use of the BGP-BFD Attribute by PE
advertising BFD Discriminator of p2mp BFD session.
Appreciate your consideration. Always welcome comments, questions, and
suggestions.

Regards,
Greg

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Fri, May 4, 2018 at 8:24 AM
Subject: New Version Notification for
draft-ietf-bess-mvpn-fast-failover-03.txt
To: Gregory Mirsky <gregimirsky@gmail.com>, Thomas Morin <
thomas.morin@orange-ftgroup.com>, Robert Kebler <rkebler@juniper.net>



A new version of I-D, draft-ietf-bess-mvpn-fast-failover-03.txt
has been successfully submitted by Greg Mirsky and posted to the
IETF repository.

Name:           draft-ietf-bess-mvpn-fast-failover
Revision:       03
Title:          Multicast VPN fast upstream failover
Document date:  2018-05-04
Group:          bess
Pages:          19
URL:            https://www.ietf.org/internet-drafts/draft-ietf-bess-mvpn-
fast-failover-03.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-fast-
failover/
Htmlized:       https://tools.ietf.org/html/draft-ietf-bess-mvpn-fast-
failover-03
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-bess-mvpn-
fast-failover
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-mvpn-
fast-failover-03

Abstract:
   This document defines multicast VPN extensions and procedures that
   allow fast failover for upstream failures, by allowing downstream PEs
   to take into account the status of Provider-Tunnels (P-tunnels) when
   selecting the upstream PE for a VPN multicast flow, and extending BGP
   MVPN routing so that a C-multicast route can be advertised toward a
   standby upstream PE.



Hello,
greatly appreciate your help submitting this draft. I'm a new co-author and
the automated process is not that good with newbies.
Thank you for your help.

Regards,
Greg

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