BCP 111, RFC 4841 on RFC 4181 Update to Recognize the IETF Trust
rfc-editor@rfc-editor.org Tue, 27 March 2007 20:22 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWIB7-0003uf-5j; Tue, 27 Mar 2007 16:22:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWIB5-0003rW-Oy for ietf-announce@ietf.org; Tue, 27 Mar 2007 16:21:59 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWIB4-00029m-BJ for ietf-announce@ietf.org; Tue, 27 Mar 2007 16:21:59 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l2RKLvIu026053; Tue, 27 Mar 2007 12:21:57 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l2RKLvtS026052; Tue, 27 Mar 2007 13:21:57 -0700
Date: Tue, 27 Mar 2007 13:21:57 -0700
Message-Id: <200703272021.l2RKLvtS026052@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: rfc-editor@rfc-editor.org
Subject: BCP 111, RFC 4841 on RFC 4181 Update to Recognize the IETF Trust
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
BCP 111
RFC 4841
Title: RFC 4181 Update to Recognize
the IETF Trust
Author: C. Heard, Ed.
Status: Best Current Practice
Date: March 2007
Mailbox: heard@pobox.com
Pages: 3
Characters: 4414
Updates: 4841
SeeAlso: BCP 111
I-D Tag: draft-heard-rfc4181-update-00.txt
URL: http://www.rfc-editor.org/rfc/rfc4841.txt
This document updates RFC 4181, "Guidelines for Authors and Reviewers
of MIB Documents", to recognize the creation of the IETF Trust. This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
ddress in either the outermost or
innermost IP header and MAY provide a configuration option
for specifying which is to be checked. If there is no
configuration option provided, an implementation SHOULD
check the peer source address contained in the outermost
header (as is the practice of most of today's implementations).
In section 5.1.3.12, please make the following change:
OLD:
A summary of the logic flow for peer certificate validation regarding
the EKU extension follows:
NEW:
Conforming IKE implementations are not required to support EKU.
If a critical EKU extension appears in a certificate and EKU is
not supported by the implementation, then RFC 3280 requires that
the certificate be rejected. Implementations that do support EKU
MUST support the following logic for certificate validation:
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce