Hi Roman, Eliot, and Lars,

Roman - Regarding Eliot's concern:

>> 6) Because this document obsoletes RFCs 3683 and 3934 and updates RFCs 2418 
>> and 9245, please review the reported errata and confirm whether they have 
>> been addressed in this document or are not relevant:
>> 
>> * RFC 2418 (https://www.rfc-editor.org/errata/rfc2418)
>> * RFC 3934 (https://www.rfc-editor.org/errata/rfc3934)
> 
> The first one is not an issue.  However, the second erratum against RFC 3934 
> raises a question:
> 
> Does this become its own BCP or does it merge with another, such as BCP 83?  
> I don't think this is part of BCP 25, however, because moderation is only one 
> aspect of working group management.  And this document goes well beyond what 
> RFC3683 did.

We would agree that this draft would go well with BCP 83. However, we wanted to 
get AD input first.

Thoughts?
Sarah Tarrant
RFC Production Center

> On Feb 11, 2026, at 10:38 AM, Lars Eggert <[email protected]> wrote:
> 
> Hi,
> 
> agree with everything Eliot said (and which I cut from this response).
> 
> On Feb 11, 2026, at 18:33, Eliot Lear <[email protected]> wrote:
>>> 7) Would you like to participate in the RPC Pilot Test for editing in 
>>> kramdown-rfc?
>>> If so, please let us know and provide a self-contained kramdown-rfc file. 
>>> For more
>>> information about this experiment, see:
>>> https://www.rfc-editor.org/rpc/wiki/doku.php?id=pilot_test_kramdown_rfc.
>> If Lars is game, so am I.  You can find the current kramdown at 
>> https://github.com/larseggert/draft-ietf-modpod-group-processes/blob/main/draft-ietf-modpod-group-processes.md.
> 
> Yes!
> 
>>> 8) Would you like to participate in the RPC Pilot Test for completing 
>>> AUTH48 in 
>>> GitHub? If so, please let us know. For more information about this 
>>> experiment, 
>>> see:
>>> https://www.rfc-editor.org/rpc/wiki/doku.php?id=rpc-github-phase-0-pilot-test.
>> I will leave this to Lars to answer.
> 
> Yes!
> 
> Thanks,
> Lars
> 
> 

-- 
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to