[iesg-secretary@ietf.org: Last Call: <draft-ietf-trill-p2mp-bfd-06.txt> (TRILL Support of Point to Multipoint BFD) to Proposed Standard]

Jeffrey Haas <jhaas@pfrc.org> Tue, 19 December 2017 15:40 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 CEB50129C6D for <rtg-bfd@ietfa.amsl.com>; Tue, 19 Dec 2017 07:40:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Ui7YmiVsEcLP for <rtg-bfd@ietfa.amsl.com>; Tue, 19 Dec 2017 07:40:19 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 30DDE1241F3 for <rtg-bfd@ietf.org>; Tue, 19 Dec 2017 07:40:19 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id AB20B1E35A; Tue, 19 Dec 2017 10:44:22 -0500 (EST)
Date: Tue, 19 Dec 2017 10:44:22 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: rtg-bfd@ietf.org
Subject: [iesg-secretary@ietf.org: Last Call: <draft-ietf-trill-p2mp-bfd-06.txt> (TRILL Support of Point to Multipoint BFD) to Proposed Standard]
Message-ID: <20171219154422.GG8708@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/ESst7sYqw03k9-0Q-ITpjYeDMxU>
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: Tue, 19 Dec 2017 15:40:21 -0000

Working Group,

This likely could use BFD eyes upon it, especially given our current WGLC on
the multipoint documents.

-- Jeff

----- Forwarded message from The IESG <iesg-secretary@ietf.org> -----

Date: Mon, 18 Dec 2017 13:56:36 -0800
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: trill-chairs@ietf.org, draft-ietf-trill-p2mp-bfd@ietf.org, trill@ietf.org, shares@ndzh.com, akatlas@gmail.com
Subject: Last Call: <draft-ietf-trill-p2mp-bfd-06.txt> (TRILL Support of Point to Multipoint BFD) to Proposed Standard


The IESG has received a request from the Transparent Interconnection of Lots
of Links WG (trill) to consider the following document: - 'TRILL Support of
Point to Multipoint BFD'
  <draft-ietf-trill-p2mp-bfd-06.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-01-08. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   Point to multipoint (P2MP) BFD is designed to verify multipoint
   connectivity.  This document specifies the support of P2MP BFD in
   TRILL.  Similar to TRILL point-to-point BFD, BFD Control packets in
   TRILL P2MP BFD are transmitted using RBridge Channel message. This
   document updates RFC 7175 and RFC 7177.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-trill-p2mp-bfd/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-trill-p2mp-bfd/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    draft-ietf-bfd-multipoint-active-tail: BFD Multipoint Active Tails. (None - IETF stream)



----- End forwarded message -----