[mpls] progressing draft-ietf-mpls-bfd-directed
<N.Leymann@telekom.de> Fri, 17 February 2017 14:42 UTC
Return-Path: <prvs=214f39329=N.Leymann@telekom.de>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2783129AAC for <mpls@ietfa.amsl.com>; Fri, 17 Feb 2017 06:42:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level:
X-Spam-Status: No, score=-4.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 SwyP7T72DtVj for <mpls@ietfa.amsl.com>; Fri, 17 Feb 2017 06:42:28 -0800 (PST)
Received: from MAILOUT31.telekom.de (MAILOUT31.telekom.de [80.149.113.193]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3242C129AA3 for <mpls@ietf.org>; Fri, 17 Feb 2017 06:42:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1487342548; x=1518878548; h=from:to:subject:date:message-id:mime-version; bh=Ja5DYlhyH12oO+3WtrPVAiUXYT9h/L7+DS8Tta0doS8=; b=zornROmhBI2w6blCo5HHVFJjt/28AfmOQqT8W5aoGvSWi4IF+R+YhX8U NuON7+5iM/ZBnq1NYQ/tU4H/AJxKlVSKX6jXe2wHSDOFK/Pn1twjevUym Sz6uW+uiZX3G2kWvTgShQui9Gry269daa3wUuKtZVVv8k898RQBSPtBBA SLNJBIOczELgEMEWvjxWANDLYnHth6Bj8Eos7pfQNRqYV5Hzi/IvuKbmb nW+gg248i7Obx2ZcBIdQRTiExl1guNtJR544NT4gDonW1cEi25278YB3B URRfUYPQaS02LcWarURpBw1SewW4HEzCMmdUvWT6Uy5a/Kz2t8HkOWCDf g==;
Received: from q4de8ssaz61.gppng.telekom.de ([10.206.166.200]) by MAILOUT31.telekom.de with ESMTP/TLS/DHE-RSA-AES128-SHA; 17 Feb 2017 15:42:15 +0100
X-IronPort-AV: E=Sophos;i="5.35,172,1484002800"; d="scan'208,217";a="1128877996"
Received: from he105662.emea1.cds.t-internal.com ([10.169.119.58]) by q4de8ssazdv.gppng.telekom.de with ESMTP/TLS/AES256-SHA; 17 Feb 2017 15:42:13 +0100
Received: from HE105662.EMEA1.cds.t-internal.com (10.169.119.58) by HE105662.emea1.cds.t-internal.com (10.169.119.58) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 17 Feb 2017 15:42:12 +0100
Received: from HE105662.EMEA1.cds.t-internal.com ([fe80::442c:834e:c489:d2c4]) by HE105662.emea1.cds.t-internal.com ([fe80::442c:834e:c489:d2c4%26]) with mapi id 15.00.1263.000; Fri, 17 Feb 2017 15:42:12 +0100
From: N.Leymann@telekom.de
To: mpls@ietf.org
Thread-Topic: progressing draft-ietf-mpls-bfd-directed
Thread-Index: AdKJLAYldfAMlcZ2SRu00wgjwaizcw==
Date: Fri, 17 Feb 2017 14:42:12 +0000
Message-ID: <03af7847dc014c688abfa283fdf05711@HE105662.emea1.cds.t-internal.com>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.213.71.39]
Content-Type: multipart/alternative; boundary="_000_03af7847dc014c688abfa283fdf05711HE105662emea1cdstintern_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/ppTSymuLAk6C5grdjvhbY3GHHu4>
Subject: [mpls] progressing draft-ietf-mpls-bfd-directed
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 14:42:30 -0000
Hi, I have closed the WG last call for the old version draft-ietf-mpls-bfd-directed. There is a new version available which addresses the concerns raised during the 2nd Last Call. The plan to progress the draft is the following: - Do a shepherd review and update the draft if necessary - Issue a new working group last call - QA review - Shepherd write up and publication I hope this solves the open issues we had in the past. regards Nic