[karp] RFC 7211 on Operations Model for Router Keying

rfc-editor@rfc-editor.org Tue, 17 June 2014 23:26 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC2201A0089; Tue, 17 Jun 2014 16:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level:
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 G3CMxoUW9Tqm; Tue, 17 Jun 2014 16:26:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 854DC1A001B; Tue, 17 Jun 2014 16:26:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4279D18000E; Tue, 17 Jun 2014 16:25:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140617232521.4279D18000E@rfc-editor.org>
Date: Tue, 17 Jun 2014 16:25:21 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/tmCcH-U4SYRPRaDLrb8ETE5wJ0Y
Cc: drafts-update-ref@iana.org, karp@ietf.org, rfc-editor@rfc-editor.org
Subject: [karp] RFC 7211 on Operations Model for Router Keying
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 17 Jun 2014 23:26:36 -0000

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

        
        RFC 7211

        Title:      Operations Model for Router Keying 
        Author:     S. Hartman, D. Zhang
        Status:     Informational
        Stream:     IETF
        Date:       June 2014
        Mailbox:    hartmans-ietf@mit.edu, 
                    zhangdacheng@huawei.com
        Pages:      18
        Characters: 47824
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-karp-ops-model-10.txt

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

The IETF is engaged in an effort to analyze the security of routing
protocol authentication according to design guidelines discussed in
RFC 6518, "Keying and Authentication for Routing Protocols 
(KARP)Design Guidelines".  Developing an operational and management model
for routing protocol security that works with all the routing
protocols will be critical to the deployability of these efforts.
This document gives recommendations to operators and implementors
regarding management and operation of router authentication.  These
recommendations will also assist protocol designers in understanding
management issues they will face.

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/search
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