Re: [Sidrops] WGLC: draft-ietf-sidrops-https-tal-03

Hi Job, all,

First off: I will be offline for the coming two weeks until 2 July, so don’t take lack of responses from me personally ;) I realise this not convenient during last call but other co-authors can comment as well of course.

> On 10 Jun 2018, at 11:25, Job Snijders <job@instituut.net> wrote:
> 
> On Fri, Jun 08, 2018 at 09:45:10AM -0400, Chris Morrow wrote:
>> The authors of: draft-ietf-sidrops-https-tal-03 would like the WG to
>> consider a WGLC of their document, 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."
>> 
>> Please have a read through the document and send along
>> comments/questions/additions/subtractions so the authors can amend if
>> required with the intent to move this document along the proper path
>> in short order.
> 
> Read. I support publication.
> 
> Nits:
> 
> 1/ "one of more" should perhaps be "one or more”?

ack

> 
> 2/  OLD: "However, a MITM can perform withhold or replay attacks
> targeting a Relying Party and keep the Relying Party from learning about
> an update CA certificate."
> 
> PERHAPS: "However, a MITM attack can be performed to prevent the Relying
> Party from learning about an updated CA certificate.”
> 

I am okay with your text, but the ‘OLD’ text is more explicit about how the MITM can affect the RP. This text was mostly stolen from the delta protocol:
https://tools.ietf.org/html/rfc8182#section-4.3

And that went through some revisions in the IESG.

I don’t have strong feelings either way as long as it’s clear to readers.

Kind regards,

Tim

> Kind regards,
> 
> Job
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
> 

Re: [Sidrops] WGLC: draft-ietf-sidrops-https-tal-03 - ENDS 22 June 2018