Sent from mobile, sorry for terse
>> IMO this draft should include the normative SID files for the initial
>> registry contents.
Generating such a document should not be a big problem. It should not be the
core-Sid document — splitting this off is the right way to handle it.
Andy Bierman wrote:
>> I don't understand why it matters where we publish the work, as long as
we
>> do.
>>
>>
> I don't understand where the SID files are for the modules in the initial
> registry (sec. 6.4.4).
> Is that for another WG to create the SID files and
On Sun, Sep 10, 2023 at 11:59 AM Michael Richardson
wrote:
>
> Andy Bierman wrote:
> > I do not have time to do another full review of this draft.
> > These are high-level comments.
>
> > ## document scope is too large
>
> > The draft should be split into 2 or 3 drafts.
>
>
Andy Bierman wrote:
> I do not have time to do another full review of this draft.
> These are high-level comments.
> ## document scope is too large
> The draft should be split into 2 or 3 drafts.
> 1) SID File Definition
> 2a) SID Management Procedures
> 2b)
