Re: [dd] DBOUND scope

[George Michaelson <[e-mail]>]

Maybe a divide-and-conquer issue here is how to specify zone-cut and
policy limits to zone cut(s) -because right now every mechanism I
imagine comes with its own set of issues.

I wouldn't preclude this being a future information type inside an
extensible model of DELEG, but I would think there is a bit of work,
problem-statement class before diving in.

In that sense, a DELEG charted could be prepared to say something
about future extensible models. And thus, NOT out-of-scope (in the
future)

-G

On Wed, Mar 20, 2024 at 9:05 AM Peter Thomassen <[e-mail]> wrote:
>
>
>
> On 3/19/24 12:53, Ben Schwartz wrote:
> > I saw a few concerns in Zulip today about whether the DBOUND-like work is addressable by /any/ technical solution.  I think it is.  Additionally, I think:
> >
> > * We should use DELEG to solve it.
>
> ... at least for parent-side claims.
>
> I have little hope that there's a way to express child-asserted domain boundaries through delegations (because they are asserted by the parent).
>
> So, I think that any effort in this direction (be it now or in the future) should declare child-asserted domain boundaries *out of scope*.
>
> Peter