IRTF Code of Conduct
draft-perkins-irtf-code-of-conduct-08
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2025-03-18
|
(System) | Received changes through RFC Editor sync (changed state to RFC, created became rfc relationship between draft-perkins-irtf-code-of-conduct and RFC 9775, changed IRTF state to Published … Received changes through RFC Editor sync (changed state to RFC, created became rfc relationship between draft-perkins-irtf-code-of-conduct and RFC 9775, changed IRTF state to Published RFC) |
|
|
2025-03-17
|
08 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
|
2025-03-16
|
08 | (System) | RFC Editor state changed to AUTH48 |
|
2025-02-24
|
08 | (System) | IANA Action state changed to No IANA Actions from In Progress |
|
2025-02-22
|
08 | Colin Perkins | Tag IESG Review Completed set. |
|
2025-02-21
|
08 | (System) | RFC Editor state changed to EDIT |
|
2025-02-21
|
08 | (System) | IANA Action state changed to In Progress |
|
2025-02-21
|
08 | Colin Perkins | IRTF state changed to Sent to the RFC Editor from Waiting for IRTF Chair |
|
2025-02-21
|
08 | Colin Perkins | Sent request for publication to the RFC Editor |
|
2025-02-20
|
08 | Liz Flynn | IRTF state changed to Waiting for IRTF Chair::IESG Review Completed from In IESG Review |
|
2025-02-13
|
08 | Amanda Baber | IANA has reviewed draft-perkins-irtf-code-of-conduct-08 and has the following comments: We understand that this document doesn't require any registry actions. While it's often helpful for a … IANA has reviewed draft-perkins-irtf-code-of-conduct-08 and has the following comments: We understand that this document doesn't require any registry actions. While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object. |
|
2025-02-13
|
08 | (System) | IANA Review state changed to IANA OK - No Actions Needed |
|
2025-02-05
|
08 | Colin Perkins | IRTF state changed to In IESG Review from Waiting for IRTF Chair |
|
2025-02-05
|
08 | Colin Perkins | IETF conflict review initiated - see conflict-review-perkins-irtf-code-of-conduct |
|
2025-02-02
|
08 | Colin Perkins | New version available: draft-perkins-irtf-code-of-conduct-08.txt |
|
2025-02-02
|
08 | Colin Perkins | New version approved |
|
2025-02-02
|
08 | (System) | Request for posting confirmation emailed to previous authors: Colin Perkins |
|
2025-02-02
|
08 | Colin Perkins | Uploaded new revision |
|
2025-01-28
|
07 | Colin Perkins | IRTF state changed to Waiting for IRTF Chair from In IRSG Poll |
|
2025-01-28
|
07 | Colin Perkins | Closed "IRSG Approve" ballot |
|
2025-01-28
|
07 | Mirja Kühlewind | [Ballot comment] Thanks for this document. It's important to have this written down! Thanks for addressing my previous comments! |
|
2025-01-28
|
07 | Mirja Kühlewind | Ballot comment text updated for Mirja Kühlewind |
|
2025-01-26
|
07 | Allison Mankin | [Ballot comment] Just adding, this was very carefully developed and reviewed under Colin's editing. Really ready for publication, which is why there are so many … [Ballot comment] Just adding, this was very carefully developed and reviewed under Colin's editing. Really ready for publication, which is why there are so many yeses. Many issues were discussed during IRSG meetings early on, |
|
2025-01-26
|
07 | Allison Mankin | Ballot comment text updated for Allison Mankin |
|
2025-01-25
|
07 | Jana Iyengar | [Ballot comment] Thank you for the discussions and the changes. I'm good with this doc now. |
|
2025-01-25
|
07 | Jana Iyengar | [Ballot Position Update] Position for Jana Iyengar has been changed to Yes from Not Ready |
|
2025-01-21
|
07 | Carsten Bormann | [Ballot comment] This is a very good result. I still have two comments that may or may not be ignored: ## Minor > The IRTF … [Ballot comment] This is a very good result. I still have two comments that may or may not be ignored: ## Minor > The IRTF sometimes organises meetings or activities that co-locate with events organised by others. These meetings or activities may need to follow the anti-harassment policy of the hosting event, which may differ from that of the IRTF. In such cases, the organisers of the IRTF meeting or activity should check with the IRTF Chair to confirm that the policy is acceptable and it should be made clear to participants what policy applies. Really? This seems to deserve an RFC 6919 keyword of "MUST (BUT WE KNOW YOU WON'T)". (Of course we won't colocate with a venue that already is known to have problems in this area.) ## Editorial > They should be generous, give credit to others where it is due, and recognise that understanding advances through collaborative research efforts of many, rather than for the glory of a few. I need to read the sentence about three times to recognize that "understanding advances" is not about "understanding advances". |
|
2025-01-21
|
07 | Carsten Bormann | [Ballot Position Update] New position, Yes, has been recorded for Carsten Bormann |
|
2025-01-20
|
07 | Colin Perkins | New version available: draft-perkins-irtf-code-of-conduct-07.txt |
|
2025-01-20
|
07 | Colin Perkins | New version approved |
|
2025-01-20
|
07 | (System) | Request for posting confirmation emailed to previous authors: Colin Perkins |
|
2025-01-20
|
07 | Colin Perkins | Uploaded new revision |
|
2025-01-15
|
06 | Ari Keränen | [Ballot Position Update] Position for Ari Keränen has been changed to Yes from No Objection |
|
2024-11-22
|
06 | Colin Perkins | New version available: draft-perkins-irtf-code-of-conduct-06.txt |
|
2024-11-22
|
06 | Colin Perkins | New version approved |
|
2024-11-22
|
06 | (System) | Request for posting confirmation emailed to previous authors: Colin Perkins |
|
2024-11-22
|
06 | Colin Perkins | Uploaded new revision |
|
2024-11-04
|
05 | Laurent Ciavaglia | [Ballot comment] A few editorial comments. Not sure if appropriate to share them here/now. Section 2. Rationale: the rationale for having a IRTF specific code … [Ballot comment] A few editorial comments. Not sure if appropriate to share them here/now. Section 2. Rationale: the rationale for having a IRTF specific code of conduct could be enhanced and make more explicit what differences between IRTF and IETF will translate in differences in the respective codes of conduct. Section 3. Conduct: it is not fully clear who/What "the IRTF" is (IRSG, IRTF Chair, RGs, all...) and how to separate participants from "the IRTF": are participants also part of "the IRTF" or not. For harassment, why is "sexual" cited primarily and only. Other forms of harassment could be considered or generalized e.g. physical, moral, verbal or non-verbal, behavioral... Section 4. Language and Imagery: s/IRTP/IRTF (end of first paragraph). The section mixes different aspects not fully in-line with the title of the section. Maybe consider organizing or splitting into different sub-sections e.g. on accessibility of communication (support), on language barriers, understanding and attitude to overcome and communicate effectively with respectful and constructive behavior, on compliance of language and imagery... Section 5. Academic Integrity: suggest changing section title to "Research Integrity". I think the content applies broadly beyond the academic context (but maybe I am missing a nuance here). Section 6. Research Ethics: I think the RFC editor would catch this one: no need to capitalize "Institutional Review Board, Research Ethics Committee". Section 7. Participation and Accessibility: if still possible to change the content, I would encourage "the IRTF" to be more assertive in expressing preference or support towards open forum, and considering the preferred, default mode for research groups, and that closed or limited fora must be justified and are exceptions. |
|
2024-11-04
|
05 | Laurent Ciavaglia | [Ballot Position Update] New position, Yes, has been recorded for Laurent Ciavaglia |
|
2024-11-04
|
05 | Jana Iyengar | [Ballot comment] Just one, and I see that Mirja has raised it already, but I would call for it to be a correction: the para … [Ballot comment] Just one, and I see that Mirja has raised it already, but I would call for it to be a correction: the para on uncredited use of AI tools seems overly restrictive. In particular, I suspect people use it as a tool, similar to any other, for writing and editing, and as such, asking for it to be credited seems unnecessary. IMO, as it stands, this recommendation is very likely to be ignored, so I would recommend removing it. Do we really care how text -- or even a research idea -- is generated as long as it is defensible and makes sense? |
|
2024-11-04
|
05 | Jana Iyengar | [Ballot Position Update] New position, Not Ready, has been recorded for Jana Iyengar |
|
2024-11-04
|
05 | Mirja Kühlewind | [Ballot comment] Thanks for this document. It's important to have this written down! I have two small comments: 1) In Section 3 it says concerns … [Ballot comment] Thanks for this document. It's important to have this written down! I have two small comments: 1) In Section 3 it says concerns should "be raised with the Chair of the Internet Architecture Board". I think this should say "be raised with the Internet Architecture Board" to clarify that it is the whole IAB handling these concerns. 2) I would like to note that the section on use of automated systems in section 5 is more restrictive than other policies I know of. Usually these policies say that use of such tools only have to be acknowledges if it was a significant contribution. E.g. using such a system for spell checking or creating a first version of some text that then is largely and manually revised is okay without attribution. |
|
2024-11-04
|
05 | Mirja Kühlewind | [Ballot Position Update] New position, Yes, has been recorded for Mirja Kühlewind |
|
2024-11-03
|
05 | Colin Perkins | Added to session: IETF-121: irtfopen Mon-1730 |
|
2024-11-03
|
05 | Rodney Van Meter | [Ballot Position Update] New position, Yes, has been recorded for Rodney Van Meter |
|
2024-11-03
|
05 | Jérôme François | [Ballot Position Update] New position, Yes, has been recorded for Jérôme François |
|
2024-11-02
|
05 | Alexey Melnikov | [Ballot Position Update] New position, Yes, has been recorded for Alexey Melnikov |
|
2024-11-02
|
05 | Shivan Sahib | [Ballot comment] Fixed a minor typo: https://github.com/irtf-chair/code-of-coduct/pull/4 |
|
2024-11-02
|
05 | Shivan Sahib | Ballot comment text updated for Shivan Sahib |
|
2024-11-02
|
05 | Shivan Sahib | [Ballot Position Update] New position, Yes, has been recorded for Shivan Sahib |
|
2024-11-02
|
05 | Dirk KUTSCHER | [Ballot Position Update] New position, Yes, has been recorded for Dirk KUTSCHER |
|
2024-11-02
|
05 | Lars Eggert | [Ballot Position Update] New position, Yes, has been recorded for Lars Eggert |
|
2024-11-01
|
05 | Allison Mankin | [Ballot Position Update] New position, Yes, has been recorded for Allison Mankin |
|
2024-11-01
|
05 | Nick Sullivan | [Ballot Position Update] New position, Yes, has been recorded for Nick Sullivan |
|
2024-11-01
|
05 | Kurtis Heimerl | [Ballot Position Update] New position, Yes, has been recorded for Kurtis Heimerl |
|
2024-11-01
|
05 | Stanislav Smyshlyaev | [Ballot Position Update] New position, Yes, has been recorded for Stanislav Smyshlyaev |
|
2024-10-31
|
05 | Stephen Farrell | [Ballot Position Update] New position, Yes, has been recorded for Stephen Farrell |
|
2024-10-30
|
05 | Eve Schooler | [Ballot Position Update] New position, Yes, has been recorded for Eve Schooler |
|
2024-10-29
|
05 | Jianfei(Jeffrey) HE | [Ballot comment] Thank you for this draft. All good except for a typo "IRTP" in Section 4. |
|
2024-10-29
|
05 | Jianfei(Jeffrey) HE | [Ballot Position Update] New position, Yes, has been recorded for Jianfei(Jeffrey) HE |
|
2024-10-29
|
05 | Wojciech Kozlowski | [Ballot comment] Thank you for this! I think this is helpful in fostering a more inclusive and supportive culture. I guess the following is a … [Ballot comment] Thank you for this! I think this is helpful in fostering a more inclusive and supportive culture. I guess the following is a typo that would be caught during editorial, but I thought I'd point it out. In Sec. 4 Language and Imagery, the last sentence concludes with "...IRTP participants should treat those doing so with grace and understanding." Is IRTP a typo? Based on the context I'd expect IRTF. |
|
2024-10-29
|
05 | Wojciech Kozlowski | [Ballot Position Update] New position, Yes, has been recorded for Wojciech Kozlowski |
|
2024-10-29
|
05 | Marie-Jose Montpetit | [Ballot Position Update] New position, Yes, has been recorded for Marie-Jose Montpetit |
|
2024-10-23
|
05 | Alvaro Retana | [Ballot Position Update] New position, Yes, has been recorded for Alvaro Retana |
|
2024-10-21
|
05 | Melinda Shore | [Ballot Position Update] New position, Yes, has been recorded for Melinda Shore |
|
2024-10-13
|
05 | Brian Trammell | [Ballot Position Update] New position, Yes, has been recorded for Brian Trammell |
|
2024-10-10
|
05 | Sofia Celi | [Ballot comment] Thank you for this! |
|
2024-10-10
|
05 | Sofia Celi | [Ballot Position Update] New position, Yes, has been recorded for Sofia Celi |
|
2024-10-09
|
05 | Reese Enghardt | [Ballot comment] Thank you for this document, I think it's a great addition to the existing Anti-Harassment procedures. One editorial nit in Section 5: "They … [Ballot comment] Thank you for this document, I think it's a great addition to the existing Anti-Harassment procedures. One editorial nit in Section 5: "They should be generous, give credit to others where it is due, and recognise that understanding advances through collaborative research efforts of many, rather than for the glory of a few." Should it be "rather than through the glory of a few"? Otherwise I'm not sure what "understanding advances for the glory of a few" means. |
|
2024-10-09
|
05 | Reese Enghardt | [Ballot Position Update] New position, Yes, has been recorded for Reese Enghardt |
|
2024-10-09
|
05 | Mat Ford | [Ballot Position Update] New position, Yes, has been recorded for Mat Ford |
|
2024-10-08
|
05 | Lixia Zhang | [Ballot Position Update] New position, Yes, has been recorded for Lixia Zhang |
|
2024-10-08
|
05 | Ari Keränen | [Ballot comment] Small typo ("IRTP") in Sec 4: [...] and IRTP participants should treat those doing so with grace and understanding |
|
2024-10-08
|
05 | Ari Keränen | [Ballot Position Update] New position, No Objection, has been recorded for Ari Keränen |
|
2024-10-08
|
05 | Ignacio Castro | [Ballot Position Update] New position, Yes, has been recorded for Ignacio Castro |
|
2024-10-08
|
05 | David Oran | [Ballot Position Update] New position, Yes, has been recorded for David Oran |
|
2024-10-08
|
05 | Colin Perkins | [Ballot Position Update] New position, Yes, has been recorded for Colin Perkins |
|
2024-10-08
|
05 | Colin Perkins | IRTF state changed to In IRSG Poll from In RG Last Call |
|
2024-10-08
|
05 | Colin Perkins | Created IRSG Ballot |
|
2024-09-22
|
05 | Colin Perkins | New version available: draft-perkins-irtf-code-of-conduct-05.txt |
|
2024-09-22
|
05 | Colin Perkins | New version approved |
|
2024-09-22
|
05 | (System) | Request for posting confirmation emailed to previous authors: Colin Perkins |
|
2024-09-22
|
05 | Colin Perkins | Uploaded new revision |
|
2024-08-28
|
04 | Colin Perkins | Notification list changed to irsg@irtf.org, ietf@trammell.ch from irsg@irtf.org because the document shepherd was set |
|
2024-08-28
|
04 | Colin Perkins | Document shepherd changed to Brian Trammell |
|
2024-08-28
|
04 | Colin Perkins | Intended Status changed to Informational from None |
|
2024-08-28
|
04 | Colin Perkins | Changed consensus to Yes from Unknown |
|
2024-08-28
|
04 | Colin Perkins | IRTF state changed to In RG Last Call |
|
2024-08-28
|
04 | Colin Perkins | Notification list changed to irsg@irtf.org from irsg@irtf.org |
|
2024-08-28
|
04 | Colin Perkins | Changed group to IRTF Open Meeting (IRTFOPEN) |
|
2024-08-27
|
04 | Colin Perkins | Stream changed to IRTF from None |
|
2024-08-22
|
04 | Colin Perkins | New version available: draft-perkins-irtf-code-of-conduct-04.txt |
|
2024-08-22
|
04 | Colin Perkins | New version approved |
|
2024-08-22
|
04 | (System) | Request for posting confirmation emailed to previous authors: Colin Perkins |
|
2024-08-22
|
04 | Colin Perkins | Uploaded new revision |
|
2024-07-07
|
03 | Colin Perkins | New version available: draft-perkins-irtf-code-of-conduct-03.txt |
|
2024-07-07
|
03 | Colin Perkins | New version approved |
|
2024-07-07
|
03 | (System) | Request for posting confirmation emailed to previous authors: Colin Perkins |
|
2024-07-07
|
03 | Colin Perkins | Uploaded new revision |
|
2024-04-28
|
02 | Colin Perkins | New version available: draft-perkins-irtf-code-of-conduct-02.txt |
|
2024-04-28
|
02 | Colin Perkins | New version approved |
|
2024-04-28
|
02 | (System) | Request for posting confirmation emailed to previous authors: Colin Perkins |
|
2024-04-28
|
02 | Colin Perkins | Uploaded new revision |
|
2024-03-04
|
01 | Colin Perkins | New version available: draft-perkins-irtf-code-of-conduct-01.txt |
|
2024-03-04
|
01 | Colin Perkins | New version approved |
|
2024-03-04
|
01 | (System) | Request for posting confirmation emailed to previous authors: Colin Perkins |
|
2024-03-04
|
01 | Colin Perkins | Uploaded new revision |
|
2023-10-23
|
00 | Colin Perkins | New version available: draft-perkins-irtf-code-of-conduct-00.txt |
|
2023-10-23
|
00 | Colin Perkins | New version approved |
|
2023-10-23
|
00 | Colin Perkins | Request for posting confirmation emailed to submitter and authors: Colin Perkins |
|
2023-10-23
|
00 | Colin Perkins | Uploaded new revision |