Re: [pkix] New Version Notification for draft-seantek-certfrag-00.txt

Sean Leonard <dev+ietf@seantek.com> Sun, 26 October 2014 15:36 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B93DE1A890F; Sun, 26 Oct 2014 08:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] 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 CrjRf-pWqC-R; Sun, 26 Oct 2014 08:36:50 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 961681A0081; Sun, 26 Oct 2014 08:36:50 -0700 (PDT)
Received: from [192.168.123.7] (unknown [23.240.242.6]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7B10D509B5; Sun, 26 Oct 2014 11:36:49 -0400 (EDT)
Message-ID: <544D14C8.4070604@seantek.com>
Date: Sun, 26 Oct 2014 08:35:36 -0700
From: Sean Leonard <dev+ietf@seantek.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: pkix@ietf.org, saag@ietf.org
References: <540E0A56.7060301@seantek.com>
In-Reply-To: <540E0A56.7060301@seantek.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pkix/hO-beoaW5U0JrpJcFKfoS23uvS0
Subject: Re: [pkix] New Version Notification for draft-seantek-certfrag-00.txt
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Oct 2014 15:36:53 -0000

Just wanted to follow up on this request for feedback/review for 
draft-seantek-certfrag, which defines fragment identifiers for certificates.

This is a short draft (just four pages--and the fourth page is just the 
author info). If you read it and don't find any issues, please let me 
know as well.

Thanks,

Sean

On 9/8/2014 12:58 PM, Sean Leonard wrote:

Hello PKIX and SAAG lists:

Based on discussions had at IETF 90, I have written up a new 
Internet-Draft to define URI fragment identifiers for certificates. The 
proposal is very simple, as there are only a limited number of 
well-defined PKIX certificate parts.

This text is a spinoff of draft-seantek-certspec, since the fragment 
definitions depend on the media type (application/pkix-cert), not on the 
URI scheme or other parts.

Feedback is appreciated.

Sean

*************************

A new version of I-D, draft-seantek-certfrag-00.txt
has been successfully submitted by Sean Leonard and posted to the
IETF repository.

Name:        draft-seantek-certfrag
Revision:    00
Title:        URI Fragment Identifiers for the application/pkix-cert 
Media Type
Document date:    2014-09-08
Group:        Individual Submission
Pages:        4
URL: http://www.ietf.org/internet-drafts/draft-seantek-certfrag-00.txt
Status: https://datatracker.ietf.org/doc/draft-seantek-certfrag/
Htmlized: http://tools.ietf.org/html/draft-seantek-certfrag-00


Abstract:
    This memo describes Uniform Resource Identifier (URI) fragment
    identifiers for PKIX certificates, which are identified with the
    Internet media type application/pkix-cert.




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.

The IETF Secretariat