RFC 7645 on The Keying and Authentication for Routing Protocol (KARP) IS-IS Security Analysis

rfc-editor@rfc-editor.org Fri, 25 September 2015 21:42 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE9C81A884B for <ietf-announce@ietfa.amsl.com>; Fri, 25 Sep 2015 14:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 XmoxdVVv6Yum for <ietf-announce@ietfa.amsl.com>; Fri, 25 Sep 2015 14:42:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 6D00D1A8848 for <ietf-announce@ietf.org>; Fri, 25 Sep 2015 14:42:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2014D187E26; Fri, 25 Sep 2015 14:41:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7645 on The Keying and Authentication for Routing Protocol (KARP) IS-IS Security Analysis
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150925214151.2014D187E26@rfc-editor.org>
Date: Fri, 25 Sep 2015 14:41:51 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/NbBbydXMEf9ogOlspvz9Sp_NxSI>
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2015 21:42:52 -0000

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

        
        RFC 7645

        Title:      The Keying and Authentication for 
                    Routing Protocol (KARP) IS-IS Security Analysis 
        Author:     U. Chunduri,
                    A. Tian,
                    W. Lu
        Status:     Informational
        Stream:     IETF
        Date:       September 2015
        Mailbox:    uma.chunduri@ericsson.com, 
                    albert.tian@ericsson.com, 
                    wenhu.lu@ericsson.com
        Pages:      12
        Characters: 28986
        Updates/Obsoletes/SeeAlso:   None

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

        URL:        https://www.rfc-editor.org/info/rfc7645

        DOI:        http://dx.doi.org/10.17487/RFC7645

This document analyzes the current state of the Intermediate System to
Intermediate System (IS-IS) protocol according to the requirements
set forth in "Keying and Authentication for Routing Protocols (KARP)
Design Guidelines" (RFC 6518) for both manual and automated key 
management protocols.


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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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