fix: add more explanations in BoF requests

ietf/templates/doc/bofreq/bofreq_template.md

@@ -15,9 +15,19 @@ Fill in the details below. Keep items in the order they appear here.
    - Chair Conflicts: TBD
    - Technology Overlap: TBD
    - Key Participant Conflict: TBD
+
+## Information for IAB/IESG
+To allow evaluation of your proposal, please include the following items:
+
+- Any protocols or practices that already exist in this space:
+- Which (if any) modifications to existing protocols or practices are required:
+- Which (if any) entirely new protocols or practices are required:
+- Open source projects (if any) implementing this work:
+
 ## Agenda
    - Items, drafts, speakers, timing
    - Or a URL
+
 ## Links to the mailing list, draft charter if any, relevant Internet-Drafts, etc.
    - Mailing List: https://www.ietf.org/mailman/listinfo/example
    - Draft charter: https://datatracker.ietf.org/doc/charter-ietf-EXAMPLE/

ietf/templates/doc/bofreq/new_bofreq.html

@@ -5,12 +5,16 @@
 {% block content %}
     {% origin %}
     <h1>Start a new BOF Request</h1>
+    <p>
+        The IAB will also attempt to provide BoF Shepherds as described in their document on the subject only on request from the IESG. If you feel that your BoF would benefit from an IAB BoF Shepherd, please discuss this with your Area Director.
+    </p>
     <p>
         Choose a short descriptive title for your request. Take time to choose a good initial title - it will be used to make the filename for your request's content. The title can be changed later, but the filename will not change.
     </p>
     <p>
         For example, a request with a title of "A new important bit" will be saved as <code>bofreq-{{ user.person.last_name|xslugify|slice:"64" }}-a-new-important-bit-00.md</code>.
     </p>
+    <p>All the items in the template MUST be filed in.</p>
     <form class="upload-content form-horizontal"
           method="post"
           enctype="multipart/form-data">