Browse Prior Art Database

IETF-ISOC relationship (RFC2031)

IP.com Disclosure Number: IPCOM000002585D
Original Publication Date: 1996-Oct-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 4 page(s) / 8K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

E. Huizer: AUTHOR

Abstract

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.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 36% of the total text.

Network Working Group E. Huizer

Request for Comments: 2031 SURFnet ExpertiseCentrum bv

Category: Informational October 1996

IETF-ISOC relationship

Status of this Memo

This memo provides information for the Internet community. This memo

does not specify an Internet standard of any kind. Distribution of

this memo is unlimited.

Abstract

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.

Introduction

The Internet Engineering Task Force (IETF) is the body that is

responsible for the development and maintenance of the Internet

Standards. Traditionally the IETF is a volunteer organization. The

driving force is dedicated high quality engineers from all over the

world. In a structure of working groups these engineers exchange

ideas and experience, and through discussion (both by e-mail and face

to face) they strive to get rough consensus. The engineers then work

on building running code to put the consensus to the test and evolve

it into an Internet Standard.

The growth of the Internet has also led to a growth of the IETF. More

and more people, organizations and companies rely on Internet

Standards. The growth of responsibility as well as amount of

participants has forced the IETF to more and more structure its

processes. Non technical issues, such as legal issues, liaison issues

etc., have become an undesirable but a seemingly unavoidable part of

the IETF organization. To address these issues the IETF established

the Poised95 working group. The working group is now trying to

structure and document the IETF processes in such a way as to keep

the maximum flexibility and freedom for the engineers in the IETF to

work in the way the IETF has always been most successful, and to

honour the IETF credo: "Rough consensus and running code".

One of the more obvious recommendations that came out of the Poised

WG was to move all non technical issues that can be moved safely, to

another related organization. The Poised WG finds that the Internet

Society (ISOC) is the obvious choice for this task. A straw poll at

the open plenary session of the IETF in december 1995 in Dallas

clearly confirmed this notion.

However, since this is an issue that is crucial to the functioning of

the IETF as a whole it is necessary to get a broad (rather than a

rough) consensus on this issue. At the same time it is necessary to

clearly indicate the extend of the relationship between the IETF and

ISOC. So both the IETF participants and the ISOC board of trustees

get a clear picture on the division of responsibilities.

The details of the Poised WG recommendations on the IETF - ISOC

relationships can be found in the appro...