On Feb 7, 2018, at 8:47 PM, Khaled Omar <eng.khaled.omar@xxxxxxxxxxx> wrote:
If there is interest, you will have heard from those who are interested. If you haven't heard from anyone, it's safe to assume that there is no interest. This can be really discouraging. But it's actually good to get to the point where this happens, because then you can regroup and learn from the experience. The first question to ask yourself is, why do you want to publish these documents? That is, what core problem for Khaled Omar do these drafts solve? Be brutally honest. If the document hasn't gotten significant interest, the reason is that it's solving a problem you want to solve, not a problem that everyone wants to solve. So where is the gap? Write down a list of all the reasons it would be good for you if your document were published as an RFC. Include reasons that have to do with your reputation, with your desire to be heard, etc. Write down the technical reasons too. But alongside the technical reasons, write down the list of documents that already attempt to solve the same problem in different ways. Are any of them RFCs? Have any of them seen adoption by hardware or software vendors? How much would it cost to switch to doing what you are proposing? Also think about how many people you want to read these documents, and how much time it will take them to read and understand them, and how much their time is worth in your favorite currency, whatever it happens to be. This kind of thinking probably won't help you to get more interest in your current documents, but it will help you to learn from experience and produce documents that have more chance of attracting interest in the IETF. |