[karp] Document Action: 'Operations Model for Router Keying' to Informational RFC (draft-ietf-karp-ops-model-10.txt)

The IESG <iesg-secretary@ietf.org> Thu, 16 January 2014 14:53 UTC

Return-Path: <iesg-secretary@ietf.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 631F21AE3E4; Thu, 16 Jan 2014 06:53:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 0IcFmycl7tu4; Thu, 16 Jan 2014 06:53:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C3041AE41E; Thu, 16 Jan 2014 06:53:22 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140116145322.1924.100.idtracker@ietfa.amsl.com>
Date: Thu, 16 Jan 2014 06:53:22 -0800
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: 'Operations Model for Router Keying' to Informational RFC (draft-ietf-karp-ops-model-10.txt)
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 16 Jan 2014 14:53:26 -0000

The IESG has approved the following document:
- 'Operations Model for Router Keying'
  (draft-ietf-karp-ops-model-10.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-ops-model/




Technical Summary

   The IETF is engaged in an effort to analyze security of routing
   protocol authentication according to design guidelines discussed in
   RFC 6518.  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.

Working Group Summary

  The need for this document is clearly indicated in order to meet the
  KARP charter. There has been little controversy.

Document Quality

  This document has had the benefit of review from many members of the
  Security Area as well as the Routing Area. This document received
  substantial review from individuals participating in the KARP WG, and
  there is a clear consensus to progress it. . The WGLC was also
  advertised to the OPSEC WG, and at least one key review was made by a
  member of that group. Since the document discusses operational
  security, this was critical in confirming the quality of the document.


Personnel
  Brian Weis is the Document Shepherd. 
  Stewart Bryant is the Responsible  Area Director.

RFC Editor Note

 == Outdated reference: draft-ietf-karp-design-guide has been published as
     RFC 6518 - please change

  == Outdated reference: A later version (-02) exists of
     draft-liu-ospfv3-automated-keying-req-01 - please change to latest

  -- Obsolete informational reference (is this intentional?): RFC 2385
     (Obsoleted by RFC 5925) - this was intended