[Hipsec] RFC 6253 on Host Identity Protocol Certificates

rfc-editor@rfc-editor.org Thu, 26 May 2011 16:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28AB7E0728; Thu, 26 May 2011 09:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.35
X-Spam-Level:
X-Spam-Status: No, score=-102.35 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1yw89rBWAH52; Thu, 26 May 2011 09:35:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id A43C2E0707; Thu, 26 May 2011 09:35:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 26084E0750; Thu, 26 May 2011 09:35:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110526163559.26084E0750@rfc-editor.org>
Date: Thu, 26 May 2011 09:35:59 -0700
Cc: hipsec@ietf.org, rfc-editor@rfc-editor.org
Subject: [Hipsec] RFC 6253 on Host Identity Protocol Certificates
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2011 16:36:00 -0000

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

        
        RFC 6253

        Title:      Host Identity Protocol Certificates 
        Author:     T. Heer, S. Varjonen
        Status:     Experimental
        Stream:     IETF
        Date:       May 2011
        Mailbox:    heer@cs.rwth-aachen.de, 
                    samu.varjonen@hiit.fi
        Pages:      12
        Characters: 24079
        Updates:    RFC5201

        I-D Tag:    draft-ietf-hip-cert-12.txt

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

The Certificate (CERT) parameter is a container for digital
certificates.  It is used for carrying these certificates in Host
Identity Protocol (HIP) control packets.  This document specifies the
CERT parameter and the error signaling in case of a failed
verification.  Additionally, this document specifies the
representations of Host Identity Tags in X.509 version 3 (v3) and
Simple Public Key Infrastructure (SPKI) certificates.

The concrete use of certificates, including how certificates are
obtained, requested, and which actions are taken upon successful or
failed verification, is specific to the scenario in which the
certificates are used.  Hence, the definition of these scenario-
specific aspects is left to the documents that use the CERT
parameter.

This document updates RFC 5201.  This document defines an 
Experimental Protocol for the Internet community.

This document is a product of the Host Identity Protocol Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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/rfcsearch.html.
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