[karp] RFC 6952 on Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide

rfc-editor@rfc-editor.org Fri, 24 May 2013 23:22 UTC

Return-Path: <wwwrun@rfc-editor.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 20E2F21F95EC; Fri, 24 May 2013 16:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.411
X-Spam-Level:
X-Spam-Status: No, score=-102.411 tagged_above=-999 required=5 tests=[AWL=0.189, 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 F3B1ExhAq4sQ; Fri, 24 May 2013 16:22:01 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 5A10A21F95E9; Fri, 24 May 2013 16:22:01 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7E5FB62113; Fri, 24 May 2013 16:21:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130524232119.7E5FB62113@rfc-editor.org>
Date: Fri, 24 May 2013 16:21:19 -0700 (PDT)
Cc: karp@ietf.org, rfc-editor@rfc-editor.org
Subject: [karp] RFC 6952 on Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Fri, 24 May 2013 23:22:02 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6952

        Title:      Analysis of BGP, LDP, PCEP, 
                    and MSDP Issues According to the 
                    Keying and Authentication for Routing Protocols 
                    (KARP) Design Guide 
        Author:     M. Jethanandani, K. Patel,
                    L. Zheng
        Status:     Informational
        Stream:     IETF
        Date:       May 2013
        Mailbox:    mjethanandani@gmail.com, 
                    keyupate@cisco.com, 
                    vero.zheng@huawei.com
        Pages:      17
        Characters: 37969
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-karp-routing-tcp-analysis-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6952.txt

This document analyzes TCP-based routing protocols, the Border
Gateway Protocol (BGP), the Label Distribution Protocol (LDP), the
Path Computation Element Communication Protocol (PCEP), and the
Multicast Source Distribution Protocol (MSDP), according to
guidelines set forth in Section 4.2 of "Keying and Authentication 
for Routing Protocols Design Guidelines", RFC 6518.

This document is a product of the Keying and Authentication for Routing Protocols Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC