<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>

<!--
     ASCII to XML transformation by Invisible Worlds, Inc.
     http://invisible.net/
     Last transformation: 03-Feb-1999, 02:08:21

     Cannonical version of this document is at:
     http://info.internet.isi.edu/in-notes/rfc/files/rfc2031.txt

     Implementors should verify all content with
     cannonical version.  Failure to do so may result in
     protocol failures.
-->

<rfc number="2031"
     category="info">
<front>
<title abbrev="IETF-ISOC Relationship">IETF-ISOC relationship</title>
<author initials="E." surname="Huizer" fullname="Erik Huizer">
<organization>SURFnet ExpertiseCentrum bv</organization>
<address>
<postal>
<street>P.O. Box 19115</street>
<street>3501 DC  Utrecht</street>
<street>The</street>
<country>Netherlands</country>
</postal>
<phone>+31 302 305 305</phone>
<facsimile>+31 302 305 329</facsimile>
<email>Erik.Huizer@sec.nl</email>
</address>
</author>
<date month="October" year="1996"/>
<area>General</area>
<keyword>Internet Engineering Task Force</keyword>
<keyword>Internet Society</keyword>
<abstract>
<t>
   This memo summarises the issues on IETF - ISOC relationships as the
   have been discussed by the Poised Working Group. The purpose of the
   document is to gauge consensus on these issues. And to allow further
   discussions where necessary.
</t>
</abstract>
</front>
<middle>
<section title="Main boundary condition">
<t>
   The IETF remains responsible for the development and quality of the
   Internet Standards. The ISOC will aid the IETF by facilitating legal
   and organizational issues as described below. Apart from the roles
   described below, the IETF and ISOC acknowledge that the ISOC has no
   influence whatsoever on the Internet Standards process, the Internet
   Standards or their technical content.
</t>
<t>
   All subgroups in the IETF and ISOC that have an official role in the
   standards process should be either:
<list>
<t>
   - open to anyone (like Working Groups); or
</t>
<t>
   - have a well documented restricted membership in which the
     voting members are elected or nominated through an open process.
</t></list>
</t>
<t>
   The latter means that within the IETF the IAB and the IESG need to be
   formed through a nomination process that is acceptable to the IETF
   community and that gives all IETF participants an equal chance to be
   candidate for a position in either of these bodies. For the ISOC this
   means that the Board of Trustees should be elected by the ISOC
   individual membership, where all individual members have an equal
   vote and all individual members have an equal opportunity to stand as
   a candidate for a position on the Board of Trustees.
</t>
<t>
   ISOC will, like the IETF use public discussion and consensus building
   processes when it wants to develop new policies or regulations that
   may influence the role of ISOC in the Internet or the Internet
   Technical work. ISOC will always put work related to Internet
   standards, Internet technical issues or Internet operations up for
   discussion in the IETF through the IETF Internet-drafts publication
   process.
</t>
</section>
<section title="The legal umbrella">
<t>
   To avoid the fact that the IETF has to construct its own legal
   structure to protect the standards and the standards process, ISOC
   should provide a legal umbrella. The legal umbrella will at least
   cover:
<list>
<t>
   - legal insurance for all IETF officers (IAB, IESG, Nomcom and WG
      chairs);
</t>
<t>
   - legal protection of the RFC series of documents; In such a way
     that these documents can be freely (i.e. no restrictions
     financially or otherwise) distributed, copied etc. but cannot
     be altered or misused. And that the right to change the document
     lies with the IETF.
</t>
<t>
   - legal protection in case of Intellectual property rights disputes
     over Internet Standards or parts thereof.
</t></list>
</t>
</section>
<section title="The standards process role">
<t>
   ISOC will assist the standards process by
<list>
<t>
     - appointing the nomcom chair
</t>
<t>
     - approving IAB candidates
</t>
<t>
     - reviewing and approving the documents that describe the standards
       process (i.e. the formal Poised documents).
</t>
<t>
     - acting as the last resort in the appeals process
</t></list>
</t>
</section>
<section title="Security considerations">
<t>
   By involving ISOC into specific parts of the Standards process, the
   IETF has no longer absolute control. It can be argued that this is a
   breach of security. It is therefore necessary to make sure that the
   ISOC involvement is restricted to well defined and understood parts,
   at well defined and understood boundary conditions. The Poised WG
   attempts to define these, and they are summarised in this document.
</t>
<t>
   There are three alternatives:
<list>
<t>
   - Do nothing and ignore the increasing responsibility and growth; the
     risk here is that the IETF either becomes insignificant, or will be
     suffocated by US law suits.
</t>
<t>
   - The IETF does everything itself; this keeps the IETf in control,
     but it would distract enormously from the technical work the IETF
     is trying to get done.
</t>
<t>
   - The IETF finds another organization than ISOC to take on the role
     described above. But why would another organization be better than
     ISOC?
</t></list>
</t>
<t>
   All in all a certain risk seems unavoidable, and a relationship with
   ISOC, under the restrictions and boundary conditions as have been
   described above, seems more like an opportunity for the IETF than
   like a risk.
</t>
</section>
<section title="Acknowledgement and disclaimer">
<t>
   The author is chair of the Poised 95 WG. The author has tried to
   summarise e-mail and face to face discussions in the WG. All the good
   ideas in this paper are the result of the WG, all the mistakes and
   errors are probably due to the author or his lack of command of the
   American language as well as the American legal system.
</t>
<t>
   The author is a member of the Internet Society.
</t>
</section>
</middle>
</rfc>
