Re: [Hipsec] I-D Action: draft-ietf-hip-rfc6253-bis-05.txt

Samu Varjonen <samu.varjonen@helsinki.fi> Tue, 03 November 2015 09:55 UTC

Return-Path: <samu.varjonen@helsinki.fi>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E79511B316E for <hipsec@ietfa.amsl.com>; Tue, 3 Nov 2015 01:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 IHYf5qsQGynI for <hipsec@ietfa.amsl.com>; Tue, 3 Nov 2015 01:55:14 -0800 (PST)
Received: from smtp-rs1-vallila2.fe.helsinki.fi (smtp-rs1-vallila2.fe.helsinki.fi [128.214.173.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 788641B316D for <hipsec@ietf.org>; Tue, 3 Nov 2015 01:55:14 -0800 (PST)
Received: from [128.214.10.115] (hpf-7.cs.helsinki.fi [128.214.10.115]) (authenticated bits=0) by smtp-rs1.it.helsinki.fi (8.14.4/8.14.4) with ESMTP id tA39tBEj008290 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <hipsec@ietf.org>; Tue, 3 Nov 2015 11:55:12 +0200
To: hipsec@ietf.org
References: <20151103095132.25799.90450.idtracker@ietfa.amsl.com>
From: Samu Varjonen <samu.varjonen@helsinki.fi>
Message-ID: <5638847F.5090504@helsinki.fi>
Date: Tue, 3 Nov 2015 11:55:11 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151103095132.25799.90450.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/hipsec/qaqS-usBBCwf9tp0W25fZL9t5Xk>
Subject: Re: [Hipsec] I-D Action: draft-ietf-hip-rfc6253-bis-05.txt
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 03 Nov 2015 09:55:18 -0000

Hi all,

I removed the SPKI and addressed other nits from the earlier version.

-Samu Varjonen

On 03/11/15 11:51, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Host Identity Protocol Working Group of the IETF.
>
>          Title           : Host Identity Protocol Certificates
>          Authors         : Tobias Heer
>                            Samu Varjonen
> 	Filename        : draft-ietf-hip-rfc6253-bis-05.txt
> 	Pages           : 10
> 	Date            : 2015-11-03
>
> Abstract:
>     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
>     certificate 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).
>
>     The concrete use cases of certificates, including how certificates
>     are obtained, requested, and which actions are taken upon successful
>     or failed verification, are 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 extends RFC7401 and obsoletes RFC6253.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-hip-rfc6253-bis/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-hip-rfc6253-bis-05
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-rfc6253-bis-05
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec