Re: [Sidrops] About the use of manifests (follow-up from Apr Interim meeting)

On Mon, May 4, 2020 at 8:07 AM Stephen Kent
<stkent=40verizon.net@dmarc.ietf.org> wrote:
>
> Job,
> > On Sun, May 03, 2020 at 03:56:22PM -0400, Stephen Kent wrote:
> >> Yes, Section 6 of RFC 6486.
> >>
> >> I believe that most of the changes will arise in 6.2, 6.3, 6.4, 6.5, and
> >> 6.6.
> > The current draft (draft-spaghetti-sidrops-rpki-manifest-validation-00)
> > replaces Section 6 entirely. I don't know if that aligns with IETF
> > etiquette and it has to be done paragraph by paragraph, but I hope this
> > helps clarify our thinking.
>
> I'll see what my co-authors think, but I'm more of an angle hair past
> guy myself :-)

did you mean 'angel hair pasta' ? :) (which I agree, far better than
that gross fat worm pasta... but...)

>
> I think most of 6.1 is OK and I plan to reuse most of it in the rev. The
> ambiguity arises in the discussion of what an RP SHOULD/MUST do when an
> object is missing or in error, which is what the latter parts of Section
> 6 address.

i think this was the meat of the previous discussion:
  "originally we left a lot of wiggle room, because <reasons>"

and today/now:
  "uhm, leaving this much wiggle room was ... oops! folk would REALLY
like to understand
   the tradeoffs in a succinct manner (that does not require phd in
pkix) and some better
   guidelines on what they should set as default behavior that
can/will set a base security/safety
   level for their deployment."

which I think is the goal of job's draft? I understood from previous
email conversations on
the WG list that the previous author set was happy to suggest
improvements but had no time/$$
for the full edit job?

Is there now time/$$ for the editoring to happen?
(maybe I'm confused, which totally could be the case)

-chris
(off reading current draft:
https://tools.ietf.org/id/draft-spaghetti-sidrops-rpki-manifest-validation-00.txt)
>
> Steve
>
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops