diff --git a/doc/todo/add_maxextensionlength_to_git-annex-config/comment_6_9ff852c12549985f6e88bd2316a69def._comment b/doc/todo/add_maxextensionlength_to_git-annex-config/comment_6_9ff852c12549985f6e88bd2316a69def._comment
new file mode 100644
index 0000000000..26d2a042d6
--- /dev/null
+++ b/doc/todo/add_maxextensionlength_to_git-annex-config/comment_6_9ff852c12549985f6e88bd2316a69def._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="(partial) filenames in keys"
+ date="2021-07-13T15:13:27Z"
+ content="""
+WOM and URL keys [[already contain|backends]] filenames or parts of filenames.  Docs warn that too-long keys might cause issues on Windows, but also that 512 and 384 length hashes already have that problem.  So it seems that permitting larger `maxextensionlength` should not add new issues?
+"""]]