Re: [sidr] Last Call: (BGPsec Operational Considerations) to Best Current Practice

2016-12-17 Thread Job Snijders
Hi all, This following paragraph looks somewhat awkward to me. TEXT: An edge site which does not provide transit and trusts its upstream(s) SHOULD only originate a signed prefix announcement and need not validate received announcements. COMMENT: If you are multihomed and receive

Re: [sidr] [Sidrops] [Technical Errata Reported] RFC6487 (6854)

2022-05-10 Thread Job Snijders
Hi, Earlier versions of RFC 6487 contained slightly more verbose guidance: https://datatracker.ietf.org/doc/html/draft-ietf-sidr-res-certs-18#section-4.9.1 """ 4.9.1. Basic Constraints The Basic Constraints extension identifies whether the Subject of the certificate is a CA and the

Re: [sidr] [Sidrops] [Technical Errata Reported] RFC8416 (7080)

2022-08-22 Thread Job Snijders
Hi all, On Mon, 22 Aug 2022 at 10:29, Tim Bruijnzeels wrote: > Hi Warren, all, > > I (co-author) agree that this was an oversight. I have no objections to > the change. > > However.. I haven't checked, but beware that current implementations might > fail to parse the file if a "comment" member

Re: [sidr] [Sidrops] [Technical Errata Reported] RFC8416 (7080)

2022-08-22 Thread Job Snijders
Hi all, On Mon, 22 Aug 2022 at 10:29, Tim Bruijnzeels wrote: > Hi Warren, all, > > I (co-author) agree that this was an oversight. I have no objections to > the change. > > However.. I haven't checked, but beware that current implementations might > fail to parse the file if a "comment" member

Re: [sidr] [Technical Errata Reported] RFC6482 (7079)

2022-08-10 Thread Job Snijders
horizations (ROAs)". > > -- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid7079 > > -- > Type: Technical > Reported by: Job Snijders > > Section: 4

Re: [sidr] [Technical Errata Reported] RFC8182 (7239)

2022-12-08 Thread Job Snijders
In response to Russ: On Thu, Dec 08, 2022 at 10:20:54AM -0500, Russ Housley wrote: > RFC 5280 defines the SAI extension, and it says: > >This profile defines one access method to be used when the subject is >a CA and one access method to be used when the subject is an end >entity.

Re: [sidr] [IANA #1266244] [Errata Verified] RFC8182 (7239)

2023-02-09 Thread Job Snijders
gt; > "The RPKI Repository Delta Protocol (RRDP)". > > > > -- > > You may review the report below and at: > > https://www.rfc-editor.org/errata/eid7239 > > > > ------ > > Status: Verified > > Type: Technical > >

Re: [sidr] [Sidrops] [Technical Errata Reported] RFC6482 (7525)

2023-05-31 Thread Job Snijders
Dear John, I think the report is correct, and it seems we already resolved it in the -bis effort: https://www.ietf.org/archive/id/draft-ietf-sidrops-rfc6482bis-03.html Section 4.3.1 of the -bis contains the same sentence the errata report proposed “The addresses field represents prefixes as a