If we care about 'immutability', put it in a notarized hash chain... I am actually serious.
RFCs are digital objects thus potentially have infinite affordances. The email address is merely a means of contacting someone. So a contextual reader could easily provide a means of click on author, connect to them via data tracker.
Alternatively, could have a set of forwarding addresses, rfc822@xxxxxxxxxxxxxxxxxxx.
We have that for drafts. Challenge for rfcs would be visibility. It might even exist already. How would I find it?
On Mon, Mar 31, 2025 at 12:29 PM Donald Eastlake <d3e3e3@xxxxxxxxx> wrote:
I believe that the immutability of RFCs is one of their greatest
strengths. But there is no problem with adding annotations to the meta
data. So the original author information should always be there but
making any updates to the information for an author easily accessible
is fine.
Thanks,
Donald
===============================
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
2386 Panoramic Circle, Apopka, FL 32703 USA
d3e3e3@xxxxxxxxx
On Mon, Mar 31, 2025 at 8:22 AM Q Misell
<q=40as207960.net@xxxxxxxxxxxxxx> wrote:
>
> 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.
>
> Q
> ________________________________
>
> 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.
