Re: When the IETF can discuss drafts seriously?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

>As a relative newcomer to IETF, I can perhaps give two (hopefully
>positive) suggestions (sorry, none of which is technical):
>
>(1) From taking a very quick look at your drafts, it may be helpful to
>have three sections at the top of the drafts that answer these 3
>questions (before you describe the new protocols):
>   i) What is the problem that the draft is solving?
>   ii) Why the problem cannot be cleanly solved with existing
>protocols/technology (which would normally be much cheaper than
>designing a new protocol)?
>   iii) How does the new protocol/technology solves the problem?
>
>I.e. I think that you need to first convince the community that there is
>a problem to be solved, before they will invest their time looking at a
>solution.

Also, I think the Introduction section of the draft should answer (at
least on a high-level) the 3 questions above, so that people don¹t have to
read through the draft just to figure out the answers.

Regards,

Christer





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]