RFC 8177 on YANG Data Model for Key Chains

rfc-editor@rfc-editor.org Fri, 16 June 2017 00:21 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A49281267BB; Thu, 15 Jun 2017 17:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 8g1P2uecTtG8; Thu, 15 Jun 2017 17:21:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C4651294E7; Thu, 15 Jun 2017 17:21:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7A99CB814B8; Thu, 15 Jun 2017 17:21:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8177 on YANG Data Model for Key Chains
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtgwg@ietf.org
Message-Id: <20170616002125.7A99CB814B8@rfc-editor.org>
Date: Thu, 15 Jun 2017 17:21:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/RRZghcD3KcHXuiTikOQf_yW0BOk>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jun 2017 00:21:42 -0000

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

        
        RFC 8177

        Title:      YANG Data Model for Key Chains 
        Author:     A. Lindem, Ed.,
                    Y. Qu,
                    D. Yeung,
                    I. Chen,
                    J. Zhang
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2017
        Mailbox:    acee@cisco.com,
                    yingzhen.qu@huawei.com,
                    derek@arrcus.com,
                    Ing-Wher_Chen@jabil.com,
                    zzhang@juniper.net
        Pages:      25
        Characters: 46205
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-yang-key-chain-24.txt

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

        DOI:        10.17487/RFC8177

This document describes the key chain YANG data model.  Key chains
are commonly used for routing protocol authentication and other
applications requiring symmetric keys.  A key chain is a list
containing one or more elements containing a Key ID, key string,
send/accept lifetimes, and the associated authentication or
encryption algorithm.  By properly overlapping the send and accept
lifetimes of multiple key chain elements, key strings and algorithms
may be gracefully updated.  By representing them in a YANG data
model, key distribution can be automated.

This document is a product of the Routing Area Working Group Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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/retrieve/bulk

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