Re: [Sidrops] 6486 bis

On Wed, Jul 1, 2020 at 11:07 AM Job Snijders <job@ntt.net> wrote:
>
> Dear all,
>
> Its been a week since the interim and I think it is important to have a
> draft uploaded into the IETF system so that the process towards
> publication formally starts. There are RPKI implementers who tell me
> that they are waiting for an RFC to be published before making changes
> to their software. Not optimal.
>

apologies, I didn't note that there was some discussion off-list by
the author folk.. I believe they are aiming to send to the system end
of week or perhaps (because holiday) early next week.

if it's beyond next wed the author(s) should put out a 'expect text
DD/MM/YYYY' please.

> Stephen Kent - if it is of any help to you, I'm happy to help navigate
> the IETF datatracker and XML goo. I don't like XML either, but I do know
> some of the magic incantations to make the computer happy. I think there
> are other people on this email list that would be happy to help too.
>
> I vaguely recall there being some text or xml being hosted at Randy's
> git server, but I don't seem to be able to connect to that server, which
> means for now I can't continue the implementation report because there
> is no text to look at.
>
> This process is blocked, please help.
>
> Kind regards,
>
> Job
>
> On Thu, May 21, 2020 at 11:51:55AM -0400, Stephen Kent wrote:
> > It seems the list prefers a KISS approach to the issue of multiple CRLs in a
> > manifest. So, absent any additional suggestions, I'll plan to post a revised
> > version of 6486 with the version 4 text that I posted to the list last week.
> >
> > Thanks,
> >
> > Steve
> >
>
> > _______________________________________________
> > Sidrops mailing list
> > Sidrops@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidrops
>
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops