draft-iab-liaison-guidelines-00.txt   draft-iab-liaison-guidelines-01.txt 
Network Working Group L. Andersson Network Working Group L. Andersson
Internet-Draft Acreo AB Internet-Draft Acreo AB
Expires: April 16, 2006 October 13, 2005 Expires: July 27, 2006 January 23, 2006
Guidelines for Acting as an IETF Liaison to Another Organization Guidelines for Acting as an IETF Liaison to Another Organization
draft-iab-liaison-guidelines-00.txt draft-iab-liaison-guidelines-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 33 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 16, 2006. This Internet-Draft will expire on July 27, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
Whenever IETF decides to enter into a liaison relationhsip with Whenever IETF decides to enter into a liaison relationship with
another organization, e.g. a Standards Development Organization, a another organization, such as a Standards Development Organization
consortium, or an industrial forum, a liaison manger is appointed. (SDO), a consortium, or an industrial forum, a liaison manager is
The procedures used by the IAB to establish and maintain liaison appointed. The procedures used by the IAB to establish and maintain
relationships between the IETF and other organizations are described liaison relationships between the IETF and other organizations are
in RFC 4052 [RFC4052]. This document give guidelines on described in RFC 4052 [RFC4052]. This document gives guidelines on
expectations, tasks, responsibilities and mandate of the liaisons expectations, tasks, responsibilities and mandate of the liaison
managers. managers.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. IETF liaisons . . . . . . . . . . . . . . . . . . . . . . . . 4 2. IETF Liaison Relationships . . . . . . . . . . . . . . . . . . 4
2.1. Related documents . . . . . . . . . . . . . . . . . . . . 4 2.1. Related documents . . . . . . . . . . . . . . . . . . . . 4
2.2. Written information . . . . . . . . . . . . . . . . . . . 4 2.2. Written information . . . . . . . . . . . . . . . . . . . 4
2.3. A person acting as liaison . . . . . . . . . . . . . . . . 5 2.3. A Person Acting As a Liaison Manager . . . . . . . . . . . 5
2.4. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 2.4. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
3. Liaison Guidelines . . . . . . . . . . . . . . . . . . . . . . 6 3. Liaison Guidelines . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Expectations . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Expectations . . . . . . . . . . . . . . . . . . . . . . . 6
3.2. Responsibilities . . . . . . . . . . . . . . . . . . . . . 7 3.2. Responsibilities . . . . . . . . . . . . . . . . . . . . . 7
3.3. Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.3. Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4. Mandate . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.4. Mandate . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.4.1. Speaking for the IETF . . . . . . . . . . . . . . . . 9 3.4.1. Speaking for the IETF . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 3.5. Relationship management . . . . . . . . . . . . . . . . . 9
5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 11 3.5.1. IETF consensus process on liaison statements . . . . . 9
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 3.5.2. Incoming Liaison Statements . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.5.3. Ambigous incoming Liaison Statements . . . . . . . . . 10
7.1. Normative References . . . . . . . . . . . . . . . . . . . 13 3.5.4. Liaison managers representing other SDOs . . . . . . . 10
7.2. Informative References . . . . . . . . . . . . . . . . . . 13 4. Security Considerations . . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . . . 15 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . . 15
7.2. Informative References . . . . . . . . . . . . . . . . . . 15
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . . . . 17
1. Introduction 1. Introduction
IETF has extensive communication with other organizations on issues The IETF communicates extensively with other organizations on issues
telating to the development of standards for the Internet. Part of relating to the development of Internet standards. Part of this
this is in written form, known as "liaison statements" sent between communication occurs in written form, known as "liaison statements".
the organizations. Part is done by appointing a person to be In order to ensure the delivery of liaison statements, as well as to
responsible for the relationship with the other organization, a enable other forms of communication, the IETF appoints a liaison
liaison manager. We normally speak of such a person as "the liaison" manager to be responsible for the relationship with the other
from the IETF to this other organization. organization. We normally speak of such a person as "the liaison"
from the IETF to the other organization.
The organizations IETF establish liaison relationships with comes The organizations IETF establishes liaison relationships with include
from various categories, such as Standards Developing Organization Standards Developing Organizations (SDOs) such as ITU-T or IEEE 802,
(SDO), e.g. the ITU-T or IEEE 802, consortium, and industrial forum. consortia, and industrial forums such as Global Grid Forum. Usually
Global Grid Forum is an example of the latter. Usually the IETF IETF liaisons are concerned with groups that develop standards and
liaisons are concerned with groups that develop standards and technical specifications.
technical specifications, and many types of groups do so.
Whenever IETF decides to enter into a liaison relationship a liaison Whenever the IETF decides to enter into a liaison relationship, a
manager is appointed. The procedures used by the IAB to establish liaison manager is appointed. The procedures used by the IAB to
and maintain liaison relationships between the IETF and other establish and maintain liaison relationships between the IETF and
organizations are described in RFC 4052 [RFC4052]. other organizations are described in RFC 4052 [RFC4052].
The role of the liaison manager has become more and important to the The role of the liaison manager has grown in importance to the IETF.
IETF. This document therefore, in addition to what is specified in This document supplements [RFC4052] by providing guidelines for
RFC 4052, gives some guidelines for liaison managers and liaison liaison managers and liaison representatives to other organizations.
representatives to another organization.
2. IETF liaisons 2. IETF Liaison Relationships
A goal for IETF is to develop standards for the Internet. These A major goal of the IETF is to develop standards for the Internet,
standards are intended to make interoperable implementations for the enabling the development of interoperable implementations. In order
Internet possible. Developing Internet standards is an actvity that to develop Internet standards, it is sometimes necessary for the IETF
makes communication with and agreements between IETF and other to communicate with other organizations which develop standards for
organizations necessary. Other organizations may develop standards other types of networks, for Internet applications or for
for other types of networks, applications running over the Internet technologies that the Internet uses.
and/or technologies that the Internet uses.
Sometimes the IETF and other organizations consider it mutually Sometimes the IETF and other organizations consider it mutually
beneficial to have certain rules governing such a relationship. The beneficial to have certain rules governing the relationship. The
organizations then enter into a "liaison relationship". On a high organizations then enter into a "liaison relationship". At a high
level it can be said that both sides agree to undertake certain level, both sides agree to undertake certain responsibilities with
responsibilities towards each other. The most basic liaison respect to each other. The most basic liaison responsibility is to
responsibility is to communicate information as necessary and to communicate information as necessary, and to respond to requests from
respond to requests for information from organizations participating liaison organizations.
in the liasion relationship.
2.1. Related documents 2.1. Related documents
The IETF liaison process is specified in an number of documents, RFC The IETF liaison process is specified in several documents. RFC 4052
4052 specifies how the IAB mamage the IETF liaison relationship, RFC [RFC4052] specifies how the IAB manages the IETF liaison
4053 [rfc4053] specifies how liaison statements should be treated. relationship; RFC 4053 [RFC4053] specifies how liaison statements
RFC 3356 [rfc3356] describes the collaboration between the IETF and should be treated; RFC 3356 [RFC3356] describes the collaboration
ITU-T. between the IETF and ITU-T.
2.2. Written information 2.2. Written information
A large amount of information may be exchanged between the IETF and Extensive communication may occur between the IETF and the
the organizations it has a liaison relationships with. This organizations it has liaison relationships with. Much of this
information is sent in a liaison statement and typically contains information is sent in liaison statements and typically contains
plans, new developments and time schedules that one of the parties plans, new developments and time schedules that one party believes
believe that the other should be aware of. A typical example is that that the other party should be aware of.
one of the organizations that the IETF has a liasion relationship
with needs to reference IETF documents as part of its document
publication activity. The liaison statement the IETF receive would
then ask us to have an RFC number ready in time. The response IETF
sent could either include that RFC number or explain why it is not
possible to have it available within the time requested.
The requests for quick action on RFCs by other organizations than ITU For example, when a liaison organization needs to reference an IETF
have not typically come as liaison statements - e.g. from 3GPP/PP2 Internet-Draft within a specification that is under development, a
and OMA, they've come as a monthly-updated list of the document liaison statement is often sent to the IETF requesting that an RFC
dependencies and dates-required. The liaison manager is expected to number be assigned within the required timeframe. In response, the
follow this and interact and convey the requests via the AD's IETF can provide the RFC number or explain why it is not possible to
requests for expedited publication citing the table (or email when provide this within the timeframe requested.
needed).
2.3. A person acting as liaison Requests for expedited action on RFCs by organizations other than
ITU-T have not typically come in the form of liaison statements. For
example, 3GPP/PP2 and OMA provide the IETF with an updated list of
dependencies on a monthly basis, indicating what documents are needed
and the required timeframe. The liaison manager tracks the
dependency list and conveys the request for expedited publication to
the appropriate AD.
Whenever the IETF enteres in to a liaison relationship with another 2.3. A Person Acting As a Liaison Manager
organization a liaison manager is appointed. In day to day talk we
refer to this person "the IETF liaison" to this other organization.
This document gives guidelines on expecations, tasks and
responsibilities for such a person.
All decisions on IETF liaison relationships, e.g. whether we should Whenever the IETF enters into a liaison relationship with another
have a liaison realtionship with a certain organization or not, is organization, a liaison manager (often referred to as "the IETF
the responsibility of the IAB. This is also true for appointing liaison") is appointed. This document describes the expectations,
liaison managers or liaison representatives. tasks and responsibilities of the liaison manager.
Decisions on IETF liaison relationships are the responsibility of the
IAB. This includes whether the IETF should have a liaison
relationship with a particular organization or not. The IAB is also
responsible for appointing both liaison managers and liaison
representatives.
In some cases, it may be necessary to have more than one person In some cases, it may be necessary to have more than one person
working with the liaison realtionship with a given organization. For handling the liaison relationship with a given organization. For
example, it may be the case that the technical scope of the liaison example, the time commitment required may be too substantial, or the
relationship is to varied, or that the time committement is more than technical scope of the liaison relationship may be too broad to be
would be reasonable for a single person. handled by a single individual.
In such cases we might appoint a liaison representative, a person In such cases the IAB may appoint a liaison representative to manage
appointed to manage one certain aspect of the liaison relationship one aspect of the liaison relationship between the IETF and the other
between IETF and the other organization. organization.
2.4. Terminology 2.4. Terminology
A terminology for managing the IETF relationship procedures are found Terminology relating to IETF liaison procedures is found in
in RFC 4052, definitons given here is intended to be the delta valid [RFC4052]. Terms defined below are valid for this document only.
for this document only.
Liaison manager - Liaison manager
a person appointed to manage an IETF liaison relationship with A person appointed to manage an IETF liaison relationship with
another organization. another organization.
Liaison representative - Liaison representative
a person appointed to manage a certain (sub-)aspect of an IETF A person appointed to manage a certain (sub-)aspect of an IETF
liaison relationship with another organization. Since it is only the liaison relationship with another organization. Since it is only the
scale of the responsibilities, mandate and tesks that is different scale of the responsibilities, mandate and tasks that is different,
the rest of this document only explicitly mentioning the liaison the rest of this document only explicitly mentions liaison managers.
managers.
IETF consensus
RFC 2026 [RFC2026] and RFC 2418 [RFC2418] discuss the IETF consensus
process. In this document the term "IETF consensus" is used to
indicate either consensus of the IETF as an organization, an Area
within IETF or a working group. There the term "IETF consensus"
needs to be interpreted in the context in which it is used.
3. Liaison Guidelines 3. Liaison Guidelines
Since the liaison relationship is by definition intended to be mutual Since liaison relationships are intended to be mutually beneficial,
beneficial, the IETF liaison to another organization must act as a the IETF liaison to another organization must act as a bi-directional
bi-directional communication link between the IETF and the other communication link between the IETF and the other organization.
organization. While this is self evident it, is also evident that Since the liaison manager has been appointed by the IETF, the liaison
since the liasion manager has been appointed by the IETF that there manager is accountable to the IETF.
are certain expectations from the IETF.
RFC 4052 lists some tasks and expectations on liaison managers, the RFC 4052 lists some of the tasks and expectations relating to liaison
intention in this document is discuss this in some more detail and at managers. This document provides more detailed discussion and
the same time focus more on how to execute the role as liaison describes how the role is executed.
manager.
3.1. Expectations 3.1. Expectations
There are certain expectations placed on liaison managers appointed There are certain expectations placed on liaison managers appointed
by the IETF. Examples of these expectations are listed below. by the IETF. Examples of these expectations are listed below.
Comptence Competence
A person appointed to act as a liaison manager on behalf of the IETF A person appointed to act as a liaison manager on behalf of the IETF
is expected to have a thorough technical knowledge and understanding is expected to have a thorough technical understanding of the key
of the key issues in the subject area. That is, the liaison manager issues in the subject area, as well as an understanding of the
is expected to have a thorough understanding of the stakeholder concerns important to stakeholders in both organizations.
issues from both organizations.
An IETF liaison manager needs to have knowledge of the IETF's An IETF liaison manager needs to have knowledge of the IETF's
consensus process in general and on the consesus work on the key consensus process in general, as well as the consensus process(es)
issues for the specific liaison relationship in particular. applying to the key issues within the liaison relationship.
The technical comptence of the liaision manager is important, but it The technical competence of the liaison manager is important, but the
should be understood the essence of the liaison manager role is essence of the liaison manager role is management of the liaison
giving attention to managing the rules agreed upon. While the process according to the rules that have been agreed upon. In the
liaison manager is managing the liaison relationship, the liasion liaison manager role, the liaison manager acts as a representative of
mananger is not an independent IETF technologist with respect to the the IETF and not an independent voice with respect to topics of
topics that are the focus of the liaision relationship. Rather, the discussion in the liaison relationship. The liaison manager must
liaison manager must represent documented IETF consensus in his or therefore be careful to distinguish their own views from documented
her dealings with the liasied organization. IETF consensus in his or her dealings with the liaison organization.
Perspective Perspective
Liaison relationships are designed for the mutual benefit of the Liaison relationships are designed for the mutual benefit of the
organisations participating in the liasion. As such, swift organizations participating in the liaison. As such, swift
information flow in both directions is a firm requirement. It is information flow in both directions is a firm requirement. The role
nevertheless expected that an IETF liaison manager in everthing that of an IETF liaison manager is to promote the interests of the IETF
relates to the subject matter of the liaison relationship promotes with respect to all topics within the scope of the liaison
the interests of the IETF. A liaison managers needs to approach the relationship. Since the liaison manager "wears an IETF hat", it is
tasks of the liaison relationship wearing an IETF hat. It is NOT the NOT the task of a liaison manager to promote the interests of the
tasks of a liaison manager to promote the interests of the liaised liaised organization within the IETF.
organization within the IETF.
Distance Distance
When appointing an appropriate person to manage a liasion When appointing an appropriate person to manage a liaison
relationship the IAB needs to take into account any conflicts of relationship, the IAB needs to take into account any conflicts of
interest that the individual being considered might have. IAB will interest that the individual being considered might have. Before a
not appoint a person to liaison manger if there is strong conflict of person is appointed to manage a liaison relationship he or she will
interests. Examples of such conflict of interest includes industry be asked to explicitly state any conflicts of interest. The IAB will
or organization leadership positions in the liaised organizations. not appoint a person to a liaison manager position if there is a
strong conflict of interest. For example, an individual with an
Before a person is appointed to manage a liaison relationship he or industry or organizational leadership position in an organization
she will be asked to explicitly state any conflicts of interest. would typically not be suitable for appointment as an IETF liaison to
that organization.
Commitment and opportunity Commitment and opportunity
A liaison needs to be committed to and have the opportunity to solve A liaison manager needs to be committed to addressing the issues
the issues for which the liaison relationship has been created. This relevant to the liaison relationship. To handle the job properly, it
also includes having time allocated to spend on the task. is necessary for the liaison be able to allocate sufficient time to
the task.
Timeliness Timeliness
One key factor when acting as a liaison is to make the IETF aware of It is expected that a liaison manger will make the IETF aware of new
the new development in the subject area in a timely fashion. developments in the subject area in a timely fashion.
3.2. Responsibilities 3.2. Responsibilities
The key responsibility of the liaison manager is to make sure that The liaison manager provides information to the IETF community in
the information flow between the IETF and the liaised organization is order to enable the IETF to make decisions based on the best possible
as effective as possible. information. Information communicated by the IETF liaison to the
liased organization is based on IETF consensus. The liaison manager
works with the liaised organization to ensure that communication is
clear. As part of this, the liaison manager must clearly
differentiate their own independent positions from those which
represent IETF consensus.
Information brought to the IETF will be used so that the IETF may It is the responsibility of the liaison manager to ensure that the
take decisions and actions based on the best possible information. liaised organization provides its requirements to the IETF and that
Information from the IETF is based on IETF consensus. The liaison the IETF consensus is clearly understood. This is particularly
manager does not develop independent positions different from the important in situations where the IETF and the liased organization
IETF consensus, though the liaison manager works with the other differ substantially in their positions. In this situation the
organization on ways to ensure that the communication is clear; that liaison manager needs to facilitate prompt communication so that the
the other organization gets it requirements to the IETF, that the IETF the the liased organization can stay in close communication.
IETF consensus is clear. If differences are strong between the IETF
and the other organization, the relevant IETF and other organization
leadership need to be in touch; the liaison manager needs to
facilitate this communication quickly.
From a more formal point of view the liaison managers are responsible The liaison managers are responsible for clearly and correctly
for a clear and correct communication of the IETF consensus position communicating the IETF consensus position to the liased organization.
to the liaised organization. This includes, when specifically This includes, when specifically instructed, to carry any messages
instructed, to carry any messages from the IETF to the peer from the IETF to the peer organization. Generally, these
organization. Generally, these communications "represent the IETF", communications "represent the IETF", and therefore due care and
and therefore due care and consensus must be applied in their consensus must be applied in their construction.
construction.
The liaison managers are responsible that any relevant information The liaison managers are responsible for ensuring that relevant
originating from the liaised organization, or other information and information originating from the liaised organization, or other
comes to the attention of the liaison manager, reaches the correct information coming to the attention of the liaison manager, reaches
destination, in a timely and correct fashion, within the IETF. the correct destination within the IETF, in a timely and correct way.
3.3. Tasks 3.3. Tasks
The list below are examples of tasks that a liaison manager could be Examples of tasks performed by the liaison manager are provided
required to perform. Depending on the nature of liaised organization below. Depending on the nature of liaised organization the task may
the task may vary in frequence and relative importance, vary in frequency and relative importance.
1. Attend relevant meetings, mailing lists and conference calls of 1. Attend relevant meetings and participate in conference calls and
the liaised organization as needed and report back to the mailing lists within the liased organization. Report back to the
appropriate part of the IETF on any developments that is of IETF on the developments of interest.
interest for the IETF.
2. A liaison manager is encouraged to work through delegation, 2. A liaison manager is encouraged to communicate; sometimes this
sometimes this involves holding frequent update meetings with a involves holding frequent update meetings with a team of IETFers
team of IETFers involved in the liaised organization and other involved in the liaised organization and other interested parties
interested parties within the IETF, e.g. working group chairs and within the IETF, e.g. working group chairs and ADs. A
ADs. A significant result of of holding such meetings is an significant result of holding such meetings is an increased
increased understanding, and eventually IETF support, for the understanding, and eventually IETF support, for the other
other organizations goals. organizations goals.
3. Prepare updates as this is requested by the IETF side. The 3. Prepare updates as requested. The target for these updates
target of these updates (e.g., the IAB, an AD, a WG) will (e.g., the IAB, an AD, a WG) will typically be identified upon
generally be identified upon establishment of the liaison establishment of the liaison relationship and/or the appointment
relationship and/or the appointment of the liaison manager. of the liaison manager.
4. Oversee delivery of liaison statements addressed to the IETF, 4. Oversee delivery of liaison statements addressed to the IETF.
ensuring that they reach the appropriate destination within the This includes ensuring that liaison statements are delivered to
IETF, and ensure that relevant responses from the IETF are the appropriate destination within the IETF, as well as
created and sent in a timely fashion. sheparding the timely creation of responses by the IETF.
5. Work with the liaised organization to ensure that the IETF's 5. Work with the liaised organization to ensure that the IETF's
liaison statements are appropriately directed and responded to in liaison statements are appropriately directed and responded to in
a timely fashion. This could e.g. be accomplished by building an a timely fashion. To accomplish this, the liaison needs to build
informal contact network for exchanging relevant information. a contact network.
6. Communicate and coordinate with other IETF liaison managers where 6. Communicate and coordinate with other IETF liaison managers where
concerned technical activities of two or more organizations that the activities of two or more liaised organizations overlap.
the IETF has a liaison relationship with overlap.
7. Based on the IETF consensus position be part of preparation of
IETF liaison statements.
8. Once the IETF has decided that a liaison statement should be sent 7. Assist with the preparation of IETF liaison statements based on
the liasion manager should be part of the preparation of the IETF consensus.
liaison statement. The liaison manager should do this based on
the IETF consensus position and the information he or she has
about the liaised organisation.
9. Liaison mangers and liaison representaives shall report to the 8. Liaison mangers and liaison representatives shall report to the
IETF on status of the liaison relationship and keep track of IETF on the status of the liaison relationship and keep track of
outstanding issues on behalf of the IETF. The frequency of the outstanding issues on behalf of the IETF. The frequency of the
reports and the recipients of the reports within the IETF will be reports and the recipients of the reports within the IETF will be
decide when the liaison relationship is set up and may be changed decided when the liaison relationship is set up and may be
at any time by an IAB decision. Status report and issue tracking changed at any time by an IAB decision. IAB or other parties
shall be done by means of the IETF liaison managment system." within the IETF may probe for liaison reports as needed or at
reegular intervals.
3.4. Mandate 3.4. Mandate
The mandate for IETF liaison managers is strictly limited, it In Section Section 3.2 and in Section Section 3.3, tasks and
comprises only conveying IETF consensus to the liased organization. responsibilities are listed which enable the IETF to obtain the
In Section 3.3 and in Section 3.2 a number of tasks and information to correctly interact with the liased organizations and
responsibilites is listed. There are at least two important aspects to develop and clearly communicate IETF consensus.
of the tasks and responsibilities. Carried out carefully they will
supply the IETF with the information need to correctly interact with
other organizations. The other, equally important, aspect is that
the tasks and responsibilites will help the liaison manager
understand the IETF consensus and build a basis on which is possible
to execute the mandate.
The liaison manager MUST NOT on his or her own initiative send The mandate for IETF liaison managers is strictly limited to
liaison statements to a liaised organization on behalf of IETF, its conveying IETF consensus to the liaised organization. The liaison
areas and working groups. Liaison statements are only sent following manager MUST NOT on their own initiative, send liaison statements to
the process specified in RFC 4052. Liaison statements are only sent a liaised organization on behalf of IETF, its areas and working
on the initiative of the IETF chair, the IAB chair, IETF Area groups. Liaison statements are only sent following the process
Directors or IETF working group chairs. specified in [RFC4052]. Liaison statements are only sent on the
initiative of the IETF chair, the IAB chair, IETF Area Directors or
IETF working group chairs.
3.4.1. Speaking for the IETF 3.4.1. Speaking for the IETF
IETF does work on the rough consensus basis, which means that the The IETF functions based on rough consensus, which means that the
right to speak for the IETF is not in any way delegated. However, right to speak for the IETF cannot be delegated. The liaison manager
the liaison manager has the task to speak for the IETF on the subject speaks on behalf of the IETF on the subject matter of the liaison,
matter of the liaison, but only after making sure that the IETF but only after making sure that the IETF consensus is understood.
consensus is understood. Some guidelines in understanding the IETF Some guidelines for understanding IETF consensus are provided above;
consensus are given above, but the most important aspect is a close however, the most important requirement is close and detailed
and detailed coordination and consultation with the IETF side in the coordination/consultation with the IETF community.
liaison relationship.
3.5. Relationship management
Liaison managers will be involved in activities for which they are
not directly responsible, but that might greatly benefit from their
expertise. Some of these activities are outlined below.
3.5.1. IETF consensus process on liaison statements
Liaison statements and other messages sent to a liaised organization
should be based on rough consensus within IETF or one of its working
groups or areas. Though the liaison manager is not responsible for
determining consensus, it is important that the liaison manager
participate in the process and makes his/her expertise and knowledge
available.
How consensus is arrived at may vary according to the circumstnaces.
Some issues are new and in these cases an open discussion on a
mailing list should be undertaken. For some issues consensus has
already been arrived at and in these cases the liaison statement can
be written and sent (such as by a working group chair), possibly
involving the liaison manager
3.5.2. Incoming Liaison Statements
When the IETF receives a liaison statement or other communication
from an organization with which it has an liaison relationship, the
IETF is committed to providing a timely response. This means that
IETF will respond within the time requested, and provide information
as accurately as possible. This commitment has been one of the key
discussion points in the past, such as within the (g)mpls change
process [I-D.andersson-rtg-gmpls-change].
This commitment does not mean that the IETF will uncritically accept
the content in the incoming liaison statement. To the extent the
liaison contains requirements on IETF technology or protocols they
will be taken into consideration based on their technical merit.
3.5.3. Ambigous incoming Liaison Statements
Sometimes the IETF, IETF areas or IETF working groups receives
liaison statements from a liaised organisation that is sent to the
wrong destination. At other times the liaision statement is sent to
working groups that is not chartered to do the work that the liaison
statement addresses. In some cases it might be the situation that no
working group is chartered to do the work.
In such cases the liaison manager should assist in finding the
appropriate recipient within the IETF that might respond to the
incoming liaison statement. Sometimes this might require that the
intended response is made available for review on one of the IETF
mailing lists.
3.5.4. Liaison managers representing other SDOs
Liased organizations may appoint a person to act as a liaison manager
for "their side" of the relationship. This is the person that will
speak for the other organization within the IETF. The other
organization needs to make this person known to the IETF. This
person might request a slot on a working group agenda to discuss
developments and plans of the liaised organization.
The mandate of liaison managers from other organizations are
recognized by the IETF to the extent needed to understand the
information received from the liaison manager. In all other respects
he/she participates in IETF activities under the same conditions and
rules as any other IETF participant.
IETF liaison managers should work to include the liaison manager from
the liaised organization within their contact network.
4. Security Considerations 4. Security Considerations
Because the interaction on protocols with other standards-making This document does not specify any protocol or "bits on the wire".
organizations often concerns security aspects, though this document However, since interaction with other standards-making organizations
does not specify any protocol or "bits on the wire", getting the often relates to security, the liaison manager can assist with
liaison manager role right does improve the development of secure security related issues, resulting in improved security for Internet
protocols for the Internet. protocols.
5. IANA considerations 5. IANA considerations
There are no requests to the IANA herein. Note that the liaison There are no requests to the IANA herein. Note that the liaison
manager very often has to understand and bridge questions regarding manager very often has to understand and bridge questions regarding
IETF namespace. IETF namespace.
6. Acknowledgements 6. Acknowledgements
This document was developed as part of a conversation regarding the This document was developed as part of a conversation regarding the
requirements on IETF liaison managers and representatives. Several requirements on IETF liaison managers and representatives. Several
IAB memebers have significantly contributed to the document. Also, IAB members have significantly contributed to the document. Also,
the document has been improved thanks to suggestions and review from the document has been improved thanks to suggestions and review from
Allison Mankin, Dave Meyer and Leslie Daigle. Allison Mankin, Dave Meyer and Leslie Daigle.
A special thanks to Bernard Aboba who apart from drawing on his
experience as a liaison manager has made many useful comments on the
subjet matter, also have spent time on correcting language and
grammar.
Members of the IAB at the time of approval of this document were: Members of the IAB at the time of approval of this document were:
Bernard Aboba Bernard Aboba
Loa Andersson Loa Andersson
Brian Carpenter Brian Carpenter
Leslie Daigle Leslie Daigle
Patrik Falstrom Patrik Falstrom
Bob Hinden Bob Hinden
Kurtis Lindqvist Kurtis Lindqvist
David Meyer David Meyer
Pekka Nikander Pekka Nikander
Eric Rescorla Eric Rescorla
Pete Resnick Pete Resnick
Jonathan Rosenberg Jonathan Rosenberg
Lixia Zhang Lixia Zhang
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2418] Bradner, S., "IETF Working Group Guidelines and
Procedures", BCP 25, RFC 2418, September 1998.
[RFC4052] Daigle, L. and Internet Architecture Board, "IAB Processes [RFC4052] Daigle, L. and Internet Architecture Board, "IAB Processes
for Management of IETF Liaison Relationships", BCP 102, for Management of IETF Liaison Relationships", BCP 102,
RFC 4052, April 2005. RFC 4052, April 2005.
7.2. Informative References 7.2. Informative References
[I-D.andersson-rtg-gmpls-change]
Andersson, L., "MPLS and GMPLS Change Process",
draft-andersson-rtg-gmpls-change-02 (work in progress),
December 2005.
[RFC3356] Fishman, G. and S. Bradner, "Internet Engineering Task [RFC3356] Fishman, G. and S. Bradner, "Internet Engineering Task
Force and International Telecommunication Union - Force and International Telecommunication Union -
Telecommunications Standardization Sector Collaboration Telecommunications Standardization Sector Collaboration
Guidelines", RFC 3356, August 2002. Guidelines", RFC 3356, August 2002.
[RFC4053] Trowbridge, S., Bradner, S., and F. Baker, "Procedures for [RFC4053] Trowbridge, S., Bradner, S., and F. Baker, "Procedures for
Handling Liaison Statements to and from the IETF", Handling Liaison Statements to and from the IETF",
BCP 103, RFC 4053, April 2005. BCP 103, RFC 4053, April 2005.
Author's Address Author's Address
skipping to change at page 15, line 41 skipping to change at page 17, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 63 change blocks. 
249 lines changed or deleted 330 lines changed or added

This html diff was produced by rfcdiff 1.28, available from http://www.levkowetz.com/ietf/tools/rfcdiff/