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

[Tim Bruijnzeels <[e-mail]>]

Hi,


> On 12 Oct 2018, at 08:53, George Michaelson <[e-mail]> wrote:
> 
> We need to deploy processes for TAL and repository fetch and
> synchronisation which can move to CDN. As it stands, the design of the
> repository fetch systems is heading to single points of failure
> because Rsync is a very poor fit for anycast distribution (no
> commercial entities I know of are offering it as a service, where all
> of them offer HTTP(S) as a matter of course)
> 
> Please can we close on this draft, because its the simple, obvious
> change to permit the TAL to be formally distributed by scaleable
> mechanisms, and helps point a way out of what I feel is a major
> operational design flaw.
> 
> The comments section has potential for people who are trapped behind
> legal disclaimer issues. I understand some of you feel paying
> attention to this is wrong, but it does not (to my mind) directly harm
> the overall intend of the proposal to adopt HTTP(S) as a
> carrier/transport to the data.

I doubt very much that this will address the issues that ARIN sees, but one can hope.

But I see value in having comments when handling test TALs, and when TA key rolls become a thing (update on this coming in a few days). Having some comments as a hint to what / which key this TAL is about is helpful - I do not like guessing this from URIs or file names. This is mainly serving RP software developers in deciding which TALs to bundle, and people doing research. I understand that normal operators will most likely never see the TAL.

On the other side, I do not see any clear harm. Ignoring a bunch of lines starting with ‘#’ is trivial and RP software needs to be updated anyway to handle the ‘https’ case.

All this being said, I do not want this to block progress on the main effort here which is to include https on TALs.

Tim


> 
> (speaking as a co-author)
> 
> -George
> On Fri, Oct 12, 2018 at 12:33 AM Job Snijders <[e-mail]> wrote:
>> 
>> Hi,
>> 
>> The comment character will *maybe* help unblock some distribution issues that some are facing in the North American region.
>> 
>> Kind regards,
>> 
>> Job
>> 
>> On Thu, Oct 11, 2018 at 19:59 Tim Bruijnzeels <[e-mail]> wrote:
>>> 
>>> Dear WG,
>>> 
>>> I asked for last call on a previous version of this document back in April, but it got stuck somehow
>>> 
>>> However, this version -05 now includes an optional comments section at the start of the TAL file, which was suggested to me off list. The idea is that this section can be used to provide some additional information to operators.
>>> 
>>> I want to ask the WG to consider first. If there are no major concerns then I will ask the co-chairs to initiate last call.
>>> 
>>> Kind regards,
>>> 
>>> Tim
>>> 
>>> 
>>> 
>>> 
>>>> On 11 Oct 2018, at 12:49, [e-mail] 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-05.txt
>>>>     Pages           : 10
>>>>     Date            : 2018-10-11
>>>> 
>>>> Abstract:
>>>> This document defines a Trust Anchor Locator (TAL) for the Resource
>>>> Public Key Infrastructure (RPKI).  This document obsoletes RFC 7730
>>>> by adding support for HTTPS URIs in a TAL.
>>>> 
>>>> 
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-ietf-sidrops-https-tal/
>>>> 
>>>> There are also htmlized versions available at:
>>>> https://tools.ietf.org/html/draft-ietf-sidrops-https-tal-05
>>>> https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-https-tal-05
>>>> 
>>>> A diff from the previous version is available at:
>>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-https-tal-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/
>>>> 
>>>> _______________________________________________
>>>> Sidrops mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/sidrops
>>> 
>>> _______________________________________________
>>> Sidrops mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/sidrops
>> 
>> _______________________________________________
>> Sidrops mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/sidrops
> 
> _______________________________________________
> Sidrops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sidrops