RFC 8263 on Group Domain of Interpretation (GDOI) GROUPKEY-PUSH Acknowledgement Message
rfc-editor@rfc-editor.org Fri, 01 December 2017 05:22 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 429D5127241 for <ietf-announce@ietfa.amsl.com>; Thu, 30 Nov 2017 21:22:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 sx_2FlM_4JA0 for <ietf-announce@ietfa.amsl.com>; Thu, 30 Nov 2017 21:22:28 -0800 (PST)
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 C308E1243F6 for <ietf-announce@ietf.org>; Thu, 30 Nov 2017 21:22:28 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C5FCEB8126C; Thu, 30 Nov 2017 21:22:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8263 on Group Domain of Interpretation (GDOI) GROUPKEY-PUSH Acknowledgement Message
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
Content-type: text/plain; charset="UTF-8"
Message-Id: <20171201052215.C5FCEB8126C@rfc-editor.org>
Date: Thu, 30 Nov 2017 21:22:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Am8XER9e_-GivZwBW-1evnp3b9c>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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, 01 Dec 2017 05:22:30 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8263
Title: Group Domain of Interpretation (GDOI)
GROUPKEY-PUSH Acknowledgement Message
Author: B. Weis,
U. Mangla,
T. Karl,
N. Maheshwari
Status: Standards Track
Stream: IETF
Date: November 2017
Mailbox: bew@cisco.com,
umangla@juniper.net,
thomas.karl@telekom.de,
nileshm@gmail.com
Pages: 17
Characters: 36745
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-weis-gdoi-rekey-ack-07.txt
URL: https://www.rfc-editor.org/info/rfc8263
DOI: 10.17487/RFC8263
The Group Domain of Interpretation (GDOI) includes the ability of a
Group Controller/Key Server (GCKS) to provide a set of current Group
Member (GM) devices with additional security associations (e.g., to
rekey expiring security associations). This memo adds the ability of
a GCKS to request that the GM devices return an acknowledgement of
receipt of its rekey message and specifies the acknowledgement
method.
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