One document matched: draft-carpenter-whats-an-author-00.xml

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<!-- You want a table of contents -->
<?rfc symrefs="yes"?>
<!-- Use symbolic labels for references -->
<?rfc sortrefs="yes"?>
<!-- This sorts the references -->
<?rfc iprnotified="no" ?>
<!-- Change to "yes" if someone has disclosed IPR for the draft -->
<?rfc compact="yes"?>
<!-- This defines the specific filename and version number of your draft (and inserts the appropriate IETF boilerplate -->
<rfc category="info" docName="draft-carpenter-whats-an-author-00" ipr="trust200902">
  <front>
    <title abbrev="What's an Author?">What is an Author of an IETF Stream Draft?</title>

    <author fullname="Brian Carpenter" initials="B. E." surname="Carpenter">
      <organization abbrev="Univ. of Auckland"/>

      <address>
        <postal>
          <street>Department of Computer Science</street>
          <street>University of Auckland</street>
          <street>PB 92019</street>
          <city>Auckland</city>
          <region/>
          <code>1142</code>
          <country>New Zealand</country>
        </postal>
        <email>brian.e.carpenter@gmail.com</email>
      </address>
    </author>


 

    <date day="24" month="April" year="2015"/>

    <abstract>
      <t>This draft suggests guidelines for assigning authorship in IETF Internet-Drafts.
      It also discusses the related issues of named contributors and
      acknowledgements. </t>
    </abstract>
  </front>

  <middle>
<section anchor="intro" title="Introduction and Scope">
<t>
The question sometimes comes up of who should be listed as the author(s)
of a draft, who should be listed as contributors, and what acknowledgements
are appropriate. The guidelines below are aimed at Internet-Drafts in the IETF
publication stream <xref target="RFC5741"/>.
They are intended to be compatible with the RFC Editor's style guide 
<xref target="RFC7322"/> and with the RFC Editor's authorship policies. </t>

<t>This draft has been written purely to aid discussion and is not expected to be published
as an RFC.</t>
</section>
<section title="Authors">
<t>Authors are people who have made a substantial creative contribution to the document.
Normally this means writing text or drawing diagrams. Occasionally, with the consent
of the other authors, it means making some other substantial creative contribution to
the document, for example by writing a software implementation as part of the design process.
</t><t>
People who did not make any such substantial contribution should not be listed
as authors. In normal circumstances, people should not be listed as authors without
their explicit permission.
</t><t>
The practical impact is that the authors will be listed as such on the front page if
the document becomes an RFC, and in public bibliographies.
</t>
</section>
<section title="Contributors">
<t>Contributors are people who made smaller creative contributions to the document
than the authors.
</t><t>
People who did not make any such contribution should not be listed as contributors.
People should not normally be listed as contributors without their explicit permission.
</t><t>
The dividing line between contributors and authors is a matter of judgement and cannot
be rigidly defined. However, the RFC Editor's policy is to query any document that has
more than five listed authors. Any list of more than five authors will need to be
negotiated if the document is approved for publication as an RFC.
</t>
</section>
<section title="Editors">
<t>
When a document has a large number of contributors and potential authors, it may
be appropriate to designate one or two people as "Editors" and list all the others
as contributors. The editors will indeed do the actual work of editing the document
on behalf of the community.
The practical impact of this is that the editors will be listed
as such on the front page if the document becomes an RFC, and in public bibliographies.
</t>
</section>
<section title="List of Acknowledgements">
<t>
Acknowledgements should be given to people who have made significant creative
contributions smaller than those from the authors and contributors, or to people
who have made useful comments, provided critical reviews, or otherwise contributed
significantly to the development of the document. Acknowledgements may also be given
to people or organizations that have given material support and assistance, but
this should not include the authors' regular employers.
</t><t>
An acknowledgement does not signify that the person acknowledged agrees with the
document. In general, people who do not wish to be listed as an author or a
contributor, but have in fact made a significant contribution, should be given
an acknowledgement.
</t>
</section>
<section title="Intellectual Property Rights">
<t>
None of the above affects intellectual property rights. 
Copyright in IETF documents is governed by BCP 78 <xref target="RFC5378"/> and its predecessors,
the IETF Trust's Legal Provisions, and applicable national and international law.
</t><t>
The word "contributor" used in this draft does not mean the same thing as the word
"Contributor" used in BCP 79 <xref target="RFC3979"/>, which is broader. That BCP should be consulted by
anyone concerned about the IETF requirement for disclosure of intellectual
property rights. </t>

</section>

    <section anchor="security" title="Security Considerations">
      <t>None, really. </t>
    </section>
    
    <section anchor="IANA" title="IANA Considerations">
      <t>This memo includes no request to IANA.</t>
    </section>

    <section anchor="ack" title="Acknowledgements">
 
      <t>Valuable comments were received from
      TBD.
      </t>

    </section>

    <section anchor="changes" title="Change log">
      <t>draft-carpenter-whats-an-author-00, 2015-04-24: original version. </t>
     
    </section>
  </middle>

  <back>
 
    <references title="Informative References">
      
      <?rfc include='reference.RFC.7322'?>
      <?rfc include='reference.RFC.5378'?>
      <?rfc include='reference.RFC.3979'?>
      <?rfc include='reference.RFC.5741'?>
      

    </references>
    
 
    
  </back>
</rfc>