[karp] Document Action: 'Analysis of BGP, LDP, PCEP and MSDP Issues According to KARP Design Guide' to Informational RFC (draft-ietf-karp-routing-tcp-analysis-07.txt)
The IESG <iesg-secretary@ietf.org> Tue, 09 April 2013 14:15 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC59C21F913E for <karp@ietfa.amsl.com>; Tue, 9 Apr 2013 07:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.536
X-Spam-Level:
X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oSEeCx8j8gPi; Tue, 9 Apr 2013 07:15:12 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ABAB321F8E63; Tue, 9 Apr 2013 07:15:11 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IANA <drafts-approval@icann.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.43.p4
X-IETF-Draft-string: draft-ietf-karp-routing-tcp-analysis
X-IETF-Draft-revision: 07
Message-ID: <20130409141511.4475.23650.idtracker@ietfa.amsl.com>
Date: Tue, 09 Apr 2013 07:15:11 -0700
Cc: karp mailing list <karp@ietf.org>, karp chair <karp-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [karp] Document Action: 'Analysis of BGP, LDP, PCEP and MSDP Issues According to KARP Design Guide' to Informational RFC (draft-ietf-karp-routing-tcp-analysis-07.txt)
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: noreply@ietf.org
List-Id: Discussion list for key management for routing and transport protocols <karp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/karp>, <mailto:karp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/karp>
List-Post: <mailto:karp@ietf.org>
List-Help: <mailto:karp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/karp>, <mailto:karp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 14:15:13 -0000
The IESG has approved the following document: - 'Analysis of BGP, LDP, PCEP and MSDP Issues According to KARP Design Guide' (draft-ietf-karp-routing-tcp-analysis-07.txt) as Informational RFC This document is the product of the Keying and Authentication for Routing Protocols Working Group. The IESG contact persons are Stewart Bryant and Adrian Farrel. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis/ Technical Summary This document analyzes TCP based routing protocols, Border Gateway Protocol (BGP) [RFC4271], Label Distribution Protocol (LDP) [RFC5036], Path Computation Element Protocol (PCEP) [RFC5440], and Multicast Source Distribution Protocol (MSDP) [RFC3618] according to guidelines set forth in section 4.2 of Keying and Authentication for Routing Protocols Design Guidelines [RFC6518]. Working Group Summary The working group was happy with this document. Joe Touch expressed concerns about the descriptions of TCP-MD5 and TCP-AO. All the specific concerns he raised have been addressed, but his comments suggest that he may have additional unspecified concerns. Document Quality This document has been reviewed by the Working Group and by the chairs. It does a good job laying out both the common issues across the protocols it analyses, and the protocol specific issues. The level of detail is appropriate to the working group goals as laid out in the charter and the guidelines document. Personnel Joel Halpern is the document shepherd. Stewart Bryant is the responsible Area Director. RFC Editor Note The rather terse and "non-standard" IANA section should be interpreted as "This document makes no IANA requests, and the RFC Editor may consider deleting this section on publication of this document as a RFC." Please move reference RFC6863 to the normative section.