Re: [sidr] I-D Action: draft-ietf-sidr-rfc6490-bis-04.txt

Richard Hansen <rhansen@bbn.com> Fri, 22 May 2015 22:28 UTC

Return-Path: <rhansen@bbn.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE0D1A897E for <sidr@ietfa.amsl.com>; Fri, 22 May 2015 15:28:34 -0700 (PDT)
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 saDWCsGqYyM3 for <sidr@ietfa.amsl.com>; Fri, 22 May 2015 15:28:32 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1AFE1A891B for <sidr@ietf.org>; Fri, 22 May 2015 15:28:03 -0700 (PDT)
Received: from socket.bbn.com ([192.1.120.102]:48143) by smtp.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <rhansen@bbn.com>) id 1YvvQ3-0006gO-RP; Fri, 22 May 2015 18:27:55 -0400
X-Submitted: to socket.bbn.com (Postfix) with ESMTPSA id 95BC140058
Message-ID: <555FAD6B.7030902@bbn.com>
Date: Fri, 22 May 2015 18:27:55 -0400
From: Richard Hansen <rhansen@bbn.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: gih@apnic.net, weiler@tislabs.com, ggm@apnic.net, Stephen Kent <kent@bbn.com>
References: <20150515051010.31959.9930.idtracker@ietfa.amsl.com>
In-Reply-To: <20150515051010.31959.9930.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/BE3dsey3_Rem771CgA7yq2q23oY>
Cc: sidr@ietf.org
Subject: Re: [sidr] I-D Action: draft-ietf-sidr-rfc6490-bis-04.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 May 2015 22:28:34 -0000

Hi Geoff, Sam, George, and Steve,

I spotted a bug in this draft:  Section 2.1 refers to Base64 encoding,
defined in RFC4648 Section 4.  RFC4648 Section 3.1 says:

   Implementations MUST NOT add line feeds to base-encoded data unless
   the specification referring to this document explicitly directs base
   encoders to add line feeds after a specific number of characters.

Section 2.1 doesn't say anything about adding newlines to the Base64
string, yet the example in Section 2.3 contains embedded newlines every
57 characters.

Rather than fix the example in Section 2.3 to conform to the current
Section 2.1, I think it would be better to permit newlines in the Base64
data:

      3)  a subjectPublicKeyInfo [RFC5280] in DER format [X.509],
          encoded in Base64 (see Section 4 of [RFC4648]).  To avoid
          long lines, a <CRLF> or <LF> line break MAY be inserted into
          the Base64 encoded string every 40 or more characters.

The choice of 40 is arbitrary; I just didn't want an implementation to
be ridiculous and add a newline after only one or a few characters.

I wouldn't mind changing it to "MUST be inserted every 40 to 76
characters" to make it possible to write a parser with fixed-length line
buffers.

(I also spotted a few typos, sent off-list.)

-Richard


On 2015-05-15 01:10, 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 Secure Inter-Domain Routing Working Group of the IETF.
> 
>         Title           : Resource Public Key Infrastructure (RPKI) Trust Anchor Locator
>         Authors         : Geoff Huston
>                           Samuel Weiler
>                           George Michaelson
>                           Stephen Kent
> 	Filename        : draft-ietf-sidr-rfc6490-bis-04.txt
> 	Pages           : 9
> 	Date            : 2015-05-14
> 
> Abstract:
>    This document defines a Trust Anchor Locator (TAL) for the Resource
>    Public Key Infrastructure (RPKI).  This document obsoletes RFC6490 by
>    adding support for multiple URIs in a TAL.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sidr-rfc6490-bis/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-sidr-rfc6490-bis-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-sidr-rfc6490-bis-04
> 
> 
> 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/
> 
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>