IETF Logo Mail Archive

Re: [sidr] Last Call: <draft-ietf-sidr-rfc6490-bis-04.txt> (Resource Public Key Infrastructure (RPKI) Trust Anchor Locator) to Proposed Standard

Rob Austein <sra@hactrn.net> Mon, 03 August 2015 20:42 UTC

Return-Path: <sra@hactrn.net>
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 20DAD1B311A; Mon, 3 Aug 2015 13:42:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.11
X-Spam-Level:
X-Spam-Status: No, score=-0.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, J_CHICKENPOX_71=0.6, J_CHICKENPOX_81=0.6, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 yNYAi2YtWKCt; Mon, 3 Aug 2015 13:42:42 -0700 (PDT)
Received: from adrilankha.hactrn.net (adrilankha.hactrn.net [147.28.0.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EB471B3123; Mon, 3 Aug 2015 13:42:42 -0700 (PDT)
Received: from minas-ithil.hactrn.net (c-24-34-34-101.hsd1.ma.comcast.net [24.34.34.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nargothrond.hactrn.net", Issuer "Grunchweather Associates" (verified OK)) by adrilankha.hactrn.net (Postfix) with ESMTPS id EDF1CB805; Mon, 3 Aug 2015 20:42:40 +0000 (UTC)
Received: from minas-ithil.hactrn.net (localhost [IPv6:::1]) by minas-ithil.hactrn.net (Postfix) with ESMTP id BEECF19E9585; Mon, 3 Aug 2015 16:42:23 -0400 (EDT)
Date: Mon, 03 Aug 2015 16:42:23 -0400
From: Rob Austein <sra@hactrn.net>
To: sidr@ietf.org, ietf@ietf.org
In-Reply-To: <19AFB4E0-C337-4E81-83C7-087F7E1CA4B9@tislabs.com>
References: <20150709134637.7120.70507.idtracker@ietfa.amsl.com> <55A5E727.7020605@bbn.com> <55B97546.3060200@bbn.com> <20150730155133.D18C719D848A@minas-ithil.hactrn.net> <19AFB4E0-C337-4E81-83C7-087F7E1CA4B9@tislabs.com>
User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <20150803204223.BEECF19E9585@minas-ithil.hactrn.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/VuE7AlawmGyg1qveMAXC6VI4XDU>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-rfc6490-bis-04.txt> (Resource Public Key Infrastructure (RPKI) Trust Anchor Locator) to Proposed Standard
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 03 Aug 2015 20:42:43 -0000

At Mon, 3 Aug 2015 16:16:22 -0400, Sandra Murphy wrote:
> 
> On Jul 30, 2015, at 11:51 AM, Rob Austein <sra@hactrn.net> wrote:
> > 
> > I prefer Richard's option 2 (allow but do not require linebreaks),
> > which is what RFC 6490 RP implementations had to support anyway.
> 
> Richard?s option 2 allows insertion of line breaks in a TAL.
> 
> Should we add a ?Relying parties MUST ignore line breaks/whitespace? as well?

Writer being allowed to insert whitespace rather strongly implies that
reader must cope with said whitespace, so seem unnecessary, but if
saying this explicitly makes people feel better, sure, whatever.

> Richard?s message agrees that everyone?s relying party code he?s
> looked at does that anyway.

Yep.

v2.23.0 | Report a Bug | By Email