diff --git a/draft-knodel-nomcom-gender-representation b/draft-knodel-nomcom-gender-representation
new file mode 100644
index 0000000..8a372d2
--- /dev/null
+++ b/draft-knodel-nomcom-gender-representation
@@ -0,0 +1,83 @@
+---
+title: "Gender Representation in the IETF Nominating Committees"
+abbrev: "nomcom-gender-representation"
+category: info
+
+docname: draft-knodel-nomcom-gender-representation
+submissiontype: IETF
+number:
+date:
+consensus: true
+v: 3
+area: GENART
+workgroup: 
+keyword:
+ - gender
+venue:
+  group: 
+  type: 
+  mail: 
+  arch: 
+  github: mallory/nomcom-gender-representation
+  latest: 
+
+author:
+ -
+    fullname: Mallory Knodel
+    organization: Center for Democracy and Technology
+    email: mknodel@cdt.org
+
+normative:
+
+informative:
+
+  RFC8713:
+  RFC9389:
+  Vervoe:
+    target: https://vervoe.com/gender-discrimination-in-hiring-practices/
+    title: Gender Discrimination in Hiring Practices
+    author:
+      org: Vervo
+    date: 2022
+
+--- abstract
+
+This document extends the existing limit on nomcom representation by company in order to improve gender diversity by ensuring that not all voting members of the IETF Nominating Committee (nomcom) belong to the same gender.
+
+--- middle
+
+# Introduction
+
+The literature supports the claims that lack of gender diversity in hiring teams reinforce under representation of gender minorities in leadership positions and that lack of gender diversity in leadership perpetuates gender discrimination [Vervoe].
+
+# Gender Representation in the IETF Nomcom
+
+The IETF considers influence and weaknesses in nomcom selection in [RFC8713]. Likewise, gender diversity in IETF leadership should be considered a community strengthening exercise insofar as gender diversity has been shown to lead to more productivity, creativity and reinforces a culture of respect and value for all participants. If we consider the nomcom as a "team", it will itself benefit from having more gender diversity among its voting members.
+
+To address gender representation in the IETF nomcom, we need only ensure that all voting members are not of the same gender. All attempts to ensure gender representation in the nomcom should include:
+    a. increase participation in the community from women and non-binary individuals so that the eligible pool is more gender diverse.
+    b. encourage eligible women and non-binary members of the community to accept selection to the nomcom.
+
+While the IETF does not routinely confirm the gender of volunteers, we have committed to improving gender diversity in the community by way of measuring it and identifying concrete steps to mitigate imbalance.
+
+# Suggested Remedy
+
+The “two-per-organisation limit” can easily be extended to ensure a nomcom consisting of no more than n-1 members from any one gender (where n is the number of available volunteer slots), requiring skips for the nth slot until a gender minority volunteer is chosen.
+
+This assumes that for any given pool therein contains at least one gender minority volunteer.
+
+This short remedy might update [RFC8713].
+
+# Security Considerations
+
+There are no security considerations for this document.
+
+# IANA Considerations
+
+This document has no IANA actions.
+
+--- back
+
+# Acknowledgments
+
+Thanks to Martin Thompson and Suresh Krishnan for informed initial thoughts on bringing this idea to the community.
diff --git a/draft-todo-yourname-protocol.md b/draft-todo-yourname-protocol.md
deleted file mode 100644
index fa51372..0000000
--- a/draft-todo-yourname-protocol.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-###
-# Internet-Draft Markdown Template
-#
-# Rename this file from draft-todo-yourname-protocol.md to get started.
-# Draft name format is "draft-<yourname>-<workgroup>-<name>.md".
-#
-# For initial setup, you only need to edit the first block of fields.
-# Only "title" needs to be changed; delete "abbrev" if your title is short.
-# Any other content can be edited, but be careful not to introduce errors.
-# Some fields will be set automatically during setup if they are unchanged.
-#
-# Don't include "-00" or "-latest" in the filename.
-# Labels in the form draft-<yourname>-<workgroup>-<name>-latest are used by
-# the tools to refer to the current version; see "docname" for example.
-#
-# This template uses kramdown-rfc: https://github.com/cabo/kramdown-rfc
-# You can replace the entire file if you prefer a different format.
-# Change the file extension to match the format (.xml for XML, etc...)
-#
-###
-title: "TODO - Your title"
-abbrev: "TODO - Abbreviation"
-category: info
-
-docname: draft-todo-yourname-protocol-latest
-submissiontype: IETF  # also: "independent", "editorial", "IAB", or "IRTF"
-number:
-date:
-consensus: true
-v: 3
-area: AREA
-workgroup: WG Working Group
-keyword:
- - next generation
- - unicorn
- - sparkling distributed ledger
-venue:
-  group: WG
-  type: Working Group
-  mail: WG@example.com
-  arch: https://example.com/WG
-  github: USER/REPO
-  latest: https://example.com/LATEST
-
-author:
- -
-    fullname: Your Name Here
-    organization: Your Organization Here
-    email: your.email@example.com
-
-normative:
-
-informative:
-
-
---- abstract
-
-TODO Abstract
-
-
---- middle
-
-# Introduction
-
-TODO Introduction
-
-
-# Conventions and Definitions
-
-{::boilerplate bcp14-tagged}
-
-
-# Security Considerations
-
-TODO Security
-
-
-# IANA Considerations
-
-This document has no IANA actions.
-
-
---- back
-
-# Acknowledgments
-{:numbered="false"}
-
-TODO acknowledge.