{"type":"rich","version":"1.0","author_name":"npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet","author_url":"https://nostr.ae/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-11-19\n📝 Original message:On Tue, Nov 19, 2013 at 8:53 AM, Drak \u003cdrak at zikula.org\u003e wrote:\n\u003e It's quite normal for standards bodies to allocate numbers when in draft\n\u003e status. If they don't pass, they don't pass - they are clearly labelled\n\u003e DRAFTs.\n\u003e\n\u003e +1 on having things in a github repository. Much better for collaboration,\n\nThe IETF makes a clear distinction between individual proposals and\ndocuments which have been accepted by a working group. The former are\nnamed after their authors.  Work is not assigned a number until it is\ncomplete.\n\nI believe it is important to distinguish complete work that people\nshould be implementing from things which are incomplete,  and even\nmore important to distinguish the work of single parties.\n\nOtherwise you're going to get crap like BIP90: \"Increase the supply of\nBitcoins to 210 million\" being confused as an earnest proposal\nsupported by many that has traction."}