Re: [Sidrops] I-D Action: draft-ietf-sidrops-https-tal-06.txt

Tim Bruijnzeels <> Wed, 23 January 2019 09:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DEA55130E78 for <>; Wed, 23 Jan 2019 01:16:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Status: No, score=-7.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JWcto1aksn8K for <>; Wed, 23 Jan 2019 01:16:56 -0800 (PST)
Received: from ( [IPv6:2a04:b900::1:0:0:10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 74146130E62 for <>; Wed, 23 Jan 2019 01:16:56 -0800 (PST)
Received: from [IPv6:2a04:b900::1:24d3:bc8d:c6c0:da53] (unknown [IPv6:2a04:b900:0:1:24d3:bc8d:c6c0:da53]) by (Postfix) with ESMTPSA id 2F8F61E2BD; Wed, 23 Jan 2019 10:16:54 +0100 (CET)
Authentication-Results:; dmarc=pass (p=none dis=none)
Authentication-Results:; spf=pass
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=default; t=1548235014; bh=PHdwDbpltVkYMMWT+/sjSkfPrBExvZ+PaIwRtlnSMfE=; h=Subject:From:In-Reply-To:Date:References:To; b=T59XEgdsgmh8cUjaMyh0byu0GtT1sddDRw1ixtgANS6qshA/aD/n59/y8AZdHG6ZS c7lkZnpjUaJNkEPR6IX315O8hqY7FGXk1CwIghzfgFODejImtToifzwo+Qk6OwD1xn wV3qP2kfDxl6/XmHE6fQa8/A+erEADwp9Cpk//Ek=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Tim Bruijnzeels <>
In-Reply-To: <>
Date: Wed, 23 Jan 2019 10:16:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: SIDR Operations WG <>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-https-tal-06.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 23 Jan 2019 09:16:59 -0000

Dear WG,

This version address the comments made after the unclosed last call for -05.

* There is now no blank line between the comments and the URIs.
* Relying Parties MUST now do TLS verification (from SHOULD) and text that was there arguing that unsafe transport is not a huge issue when there is object security has been removed.
* Job Snijders is acknowledged for suggesting the comments section.

Please have a look and speak up if you see any remaining issues. This should have been a simple change, but we're talking about this for almost a year now. If I get no comments by the end of next week, then I will try asking for last call once again, but I hope to avoid having to make a version -07.


> On 23 Jan 2019, at 10:11, wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the SIDR Operations WG of the IETF.
>        Title           : Resource Public Key Infrastructure (RPKI) Trust Anchor Locator
>        Authors         : Geoff Huston
>                          Samuel Weiler
>                          George Michaelson
>                          Stephen Kent
>                          Tim Bruijnzeels
> 	Filename        : draft-ietf-sidrops-https-tal-06.txt
> 	Pages           : 10
> 	Date            : 2019-01-23
> Abstract:
>   This document defines a Trust Anchor Locator (TAL) for the Resource
>   Public Key Infrastructure (RPKI).  TALs allow Relying Parties in the
>   RPKI to download the current Trust Anchor (TA) CA certificate from
>   one or more locations, and verify that the key of this self-signed
>   certificate matches the key on the TAL.  Thus, Relying Parties can be
>   configured with TA keys, but allow these TAs to change the content of
>   their CA certificate.  In particular it allows TAs to change the set
>   of Internet Number Resources included in the RFC3779 extension of
>   their certificate.
>   This document obsoletes the previous definition of Trust Anchor
>   Locators in RFC 7730 by adding support for HTTPS URIs.
> The IETF datatracker status page for this draft is:
> There are also htmlized versions available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> Sidrops mailing list