Hi Q,
Quite often, particularly if you are new to the process, the IAB (iab@xxxxxxx) will offer to assign a shepherd to help for BOFs, but then, I’m not sure whether you really want/need a BOF at all.
What you are trying do may be complex within the IETF organization because RFCs are treated somewhat separately to the IETF (e.g., the IRTF, IAB, and ISE also publish RFCs as well as the IETF).
Hence my suggestion would be to perhaps email either the RSWG (RFC Series Working Group) directly, or perhaps just the RSWG chairs (https://datatracker.ietf.org/group/rswg/about/) and ask them for
advice on how best to approach this and what the best path forward might be. There may be some existing work that this could already dovetail into.
If RSWG or the RSWG chairs suggest that a BOF is perhaps the right way forward, then you could put in a placeholder BOF request here,
https://datatracker.ietf.org/doc/bof-requests/new/, under the GEN area, which would mean that it would flag up to the IESG’s radar at the appropriate time. If you do that, then I would also suggest
dropping Roman an email (as GEN AD) to let him know (perhaps even in advance of submitting the BOF request).
Kind regards,
Rob
From: Q Misell <q=40as207960.net@xxxxxxxxxxxxxx>
Date: Monday, 31 March 2025 at 13:22
To: ietf@xxxxxxxx <ietf@xxxxxxxx>
Subject: Re: sob@xxxxxxxxxxx is not long for the world
To dig up an old conversation, the relevance of such a BoF crossed my mind yesterday.
It probably happens less often than email addresses being deleted, but people change names. You're probably familiar with this happening when someone gets married, but there are other times.
It is common for trans people to change their name, and having to recall or see their old name (commonly called a deadname) can be a traumatic experience for us. We currently accept RFCs to be unchanging documents,
but I think in some cases there should be room to update the author's metadata on the RFC.
I would like to organise a BoF to discuss updating the rules on changing RFCs, and would appreciate some input from people who have organised a BoF before.
Any statements contained in this email are personal to the author and are not necessarily the statements of the company unless specifically stated. AS207960 Cyfyngedig, having a registered
office at 13 Pen-y-lan Terrace, Caerdydd, Cymru, CF23 9EU, trading as Glauca Digital, is a company registered in Wales under №
12417574, LEI 875500FXNCJPAPF3PD10. ICO register №:
ZA782876. UK VAT №: GB378323867. EU VAT №: EU372013983. Turkish VAT №: 0861333524. South Korean VAT №: 522-80-03080. AS207960 Ewrop OÜ, having a registered office at Lääne-Viru maakond, Tapa vald, Porkuni küla, Lossi tn 1, 46001, trading as Glauca Digital,
is a company registered in Estonia under № 16755226. Estonian VAT №: EE102625532. Glauca Digital and the Glauca logo are registered trademarks in the UK, under № UK00003718474 and № UK00003718468, respectively.
|
