Hi again,

Please read this version, as it attempts to roll up everything I've
seen that's in scope. There's not much point in commenting on what you
didn't like about version 01, because those are exactly the things
that I've changed.

I request the chairs to consider an adoption call for this version,
even though there are two very explicit open issues in the text.
(I'm biased on both of them.)

Rgds
   Brian
-------- Forwarded Message --------
Subject: I-D Action: draft-carpenter-rswg-authoring-ethics-04.txt
Date: Tue, 09 Jun 2026 01:00:53 -0700
From: [email protected]
Reply-To: [email protected]
To: [email protected]

Internet-Draft draft-carpenter-rswg-authoring-ethics-04.txt is now available.

   Title:   Guidelines for Assignment of RFC Authorship
   Author:  Brian E. Carpenter
   Name:    draft-carpenter-rswg-authoring-ethics-04.txt
   Pages:   14
   Dates:   2026-06-09

Abstract:

   This document describes ethical guidelines for assigning authorship
   in RFC documents, including guidelines for the use of artificial
   intelligence during document preparation, and for inclusion of
   material from other documents.  It also discusses the related issues
   of acknowledgements, editors and contributors.  The various RFC
   streams are expected to apply these guidelines, and possibly define
   their own variations, which will have priority.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-carpenter-rswg-authoring-ethics/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-carpenter-rswg-authoring-ethics-04.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-carpenter-rswg-authoring-ethics-04

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
I-D-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

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

Reply via email to