draft-iab-liaison-guidelines-02.txt   draft-iab-liaison-guidelines-03.txt 
Network Working Group L. Andersson Network Working Group L. Andersson (Ed)
Internet-Draft Acreo AB Internet-Draft IAB
Expires: September 7, 2006 March 6, 2006 Expires: November 4, 2006 May 3, 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-02.txt draft-iab-liaison-guidelines-03.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 September 7, 2006. This Internet-Draft will expire on November 4, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
Whenever IETF decides to enter into a liaison relationship with Whenever IETF decides to enter into a liaison relationship with
another organization, such as a Standards Development Organization another organization, such as a Standards Development Organization
(SDO), a consortium, or an industrial forum, a liaison manager is (SDO), a consortium, or an industrial forum, a liaison manager is
skipping to change at page 2, line 17 skipping to change at page 2, line 17
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 Liaison Relationships . . . . . . . . . . . . . . . . . . 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 a Liaison Manager . . . . . . . . . . . 5 2.3. Liaison Managers and Liaison Representatives . . . . . . . 5
2.4. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 2.4. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
3. Liaison Guidelines . . . . . . . . . . . . . . . . . . . . . . 6 3. Liaison Guidelines . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Expectations . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Expectations . . . . . . . . . . . . . . . . . . . . . . . 7
3.2. Responsibilities . . . . . . . . . . . . . . . . . . . . . 7 3.2. Responsibilities . . . . . . . . . . . . . . . . . . . . . 8
3.3. Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.3. Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.4. Mandate . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.4. Mandate . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4.1. Speaking for the IETF . . . . . . . . . . . . . . . . 9 3.4.1. Speaking for the IETF . . . . . . . . . . . . . . . . 10
3.5. Relationship management . . . . . . . . . . . . . . . . . 9 3.5. Relationship management . . . . . . . . . . . . . . . . . 10
3.5.1. IETF consensus process on liaison statements . . . . . 9 3.5.1. IETF consensus process on liaison statements . . . . . 10
3.5.2. Incoming Liaison Statements . . . . . . . . . . . . . 10 3.5.2. Incoming Liaison Statements . . . . . . . . . . . . . 11
3.5.3. Ambiguous incoming Liaison Statements . . . . . . . . 10 3.5.3. Ambiguous incoming Liaison Statements . . . . . . . . 11
3.5.4. Liaison managers representing other SDOs . . . . . . . 10 3.5.4. Liaison managers representing other SDOs . . . . . . . 11
4. Security Considerations . . . . . . . . . . . . . . . . . . . 12 4. Security Considerations . . . . . . . . . . . . . . . . . . . 13
5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 13 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 14
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.1. Normative References . . . . . . . . . . . . . . . . . . . 15 7.1. Normative References . . . . . . . . . . . . . . . . . . . 16
7.2. Informative References . . . . . . . . . . . . . . . . . . 15 7.2. Informative References . . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 17 Intellectual Property and Copyright Statements . . . . . . . . . . 18
1. Introduction 1. Introduction
The IETF communicates extensively with other organizations on issues The IETF communicates extensively with other organizations on issues
relating to the development of Internet standards. Part of this relating to the development of Internet standards. Part of this
communication occurs in written form, known as "liaison statements". communication occurs in written form, known as "liaison statements".
In order to ensure the delivery of liaison statements, as well as to In order to ensure the delivery of liaison statements, as well as to
enable other forms of communication, the IETF appoints a liaison enable other forms of communication, the IETF appoints a liaison
manager to be responsible for the relationship with the other manager to be responsible for the relationship with the other
organization. We normally speak of such a person as "the liaison" organization. We normally speak of such a person as "the liaison"
from the IETF to the other organization. from the IETF to the other organization.
The organizations IETF establishes liaison relationships with include The organizations IETF establishes liaison relationships with include
Standards Developing Organizations (SDOs) such as ITU-T or IEEE 802, Standards Developing Organizations (SDOs) such as ITU-T or IEEE 802,
consortia, and industrial forums such as Global Grid Forum. Usually consortia such as W3C, and industrial forums such as Global Grid
IETF liaisons are concerned with groups that develop standards and Forum. Usually IETF liaisons are concerned with groups that develop
technical specifications. standards and technical specifications.
Whenever the IETF decides to enter into a liaison relationship, a Whenever the IETF decides to enter into a liaison relationship, a
liaison manager is appointed. The procedures used by the IAB to liaison manager is appointed. The procedures used by the IAB to
establish and maintain liaison relationships between the IETF and establish and maintain liaison relationships between the IETF and
other organizations are described in RFC 4052 [RFC4052]. other organizations are described in RFC 4052 [RFC4052].
The role of the liaison manager has grown in importance to the IETF. The role of the liaison manager has grown in importance to the IETF.
This document supplements [RFC4052] by providing guidelines for This document supplements [RFC4052] by providing guidelines for
liaison managers and liaison representatives to other organizations. liaison managers and liaison representatives to other organizations.
skipping to change at page 4, line 27 skipping to change at page 4, line 27
level, both sides agree to undertake certain responsibilities with level, both sides agree to undertake certain responsibilities with
respect to each other. The most basic liaison responsibility is to respect to each other. The most basic liaison responsibility is to
communicate information as necessary, and to respond to requests from communicate information as necessary, and to respond to requests from
liaison organizations. liaison organizations.
2.1. Related documents 2.1. Related documents
The IETF liaison process is specified in several documents. RFC 4052 The IETF liaison process is specified in several documents. RFC 4052
[RFC4052] specifies how the IAB manages the IETF liaison [RFC4052] specifies how the IAB manages the IETF liaison
relationship; RFC 4053 [RFC4053] specifies how liaison statements relationship; RFC 4053 [RFC4053] specifies how liaison statements
should be treated; RFC 3356 [RFC3356] describes the collaboration should be treated. Organization-specific agreements and documents
between the IETF and ITU-T. may also be generated in some cases, e.g., RFC 3356 [RFC3356]
describes the collaboration between the IETF and ITU-T, RFC 3113
[RFC3113] describes the relationship with 3GPP, and RFC 3131
[RFC3131]describes the one with 3GPP2.
2.2. Written information 2.2. Written information
Extensive communication may occur between the IETF and the Extensive communication may occur between the IETF and the
organizations it has liaison relationships with. Much of this organizations it has liaison relationships with. Much of this
information is sent in liaison statements and typically contains information is sent in liaison statements and typically contains
plans, new developments and time schedules that one party believes plans, new developments and time schedules that one party believes
that the other party should be aware of. that the other party should be aware of.
For example, when a liaison organization needs to reference an IETF For example, when a liaison organization needs to reference an IETF
Internet-Draft within a specification that is under development, a Internet-Draft within a specification that is under development, a
liaison statement is often sent to the IETF requesting that an RFC liaison statement is often sent to the IETF requesting that an RFC
number be assigned within the required timeframe. In response, the number be assigned within the required timeframe. In response, the
IETF can provide the RFC number or explain why it is not possible to IETF can provide the RFC number or explain why it is not possible to
provide this within the timeframe requested. provide this within the timeframe requested.
Requests for expedited action on RFCs by organizations other than Requests for expedited action on RFCs by organizations other than
ITU-T have not typically come in the form of liaison statements. For 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 example, 3GPP/3GPP2 and OMA provide the IETF with an updated list of
dependencies on a monthly basis, indicating what documents are needed dependencies on a monthly basis, indicating what documents are needed
and the required timeframe. The liaison manager tracks the and the required timeframe. The liaison manager tracks the
dependency list and conveys the request for expedited publication to dependency list and conveys the request for expedited publication to
the appropriate AD. the appropriate AD.
2.3. A Person Acting As a Liaison Manager 2.3. Liaison Managers and Liaison Representatives
Whenever the IETF enters into a liaison relationship with another Whenever the IETF enters into a liaison relationship with another
organization, a liaison manager (often referred to as "the IETF organization, a liaison manager (often referred to as "the IETF
liaison") is appointed. This document describes the expectations, liaison") is appointed. This document describes the expectations,
tasks and responsibilities of the liaison manager. tasks and responsibilities of the liaison manager.
Decisions on IETF liaison relationships are the responsibility of the Decisions on IETF liaison relationships are the responsibility of the
IAB. This includes whether the IETF should have a liaison IAB. This includes whether the IETF should have a liaison
relationship with a particular organization or not. The IAB is also relationship with a particular organization or not. The IAB is also
responsible for appointing both liaison managers and liaison responsible for appointing both liaison managers and liaison
representatives. 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
handling the liaison relationship with a given organization. For handling the liaison relationship with a given organization. For
example, the time commitment required may be too substantial, or the example, the time commitment required may be too substantial, or the
technical scope of the liaison relationship may be too broad to be technical scope of the liaison relationship may be too broad to be
handled by a single individual. handled by a single individual.
In such cases the IAB may appoint a liaison representative to manage In such cases the IAB may appoint one or more liaison representatives
one aspect of the liaison relationship between the IETF and the other to supplement the work of the liaison manager by managing different
aspects of the liaison relationship between the IETF and the other
organization. organization.
2.4. Terminology 2.4. Terminology
Terminology relating to IETF liaison procedures is found in Terminology relating to IETF liaison procedures is found in
[RFC4052]. Terms defined below are valid for this document only. [RFC4052]. Terms defined below are valid 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
skipping to change at page 6, line 11 skipping to change at page 7, line 11
indicate either consensus of the IETF as an organization, an Area indicate either consensus of the IETF as an organization, an Area
within IETF or a working group. There the term "IETF consensus" within IETF or a working group. There the term "IETF consensus"
needs to be interpreted in the context in which it is used. needs to be interpreted in the context in which it is used.
3. Liaison Guidelines 3. Liaison Guidelines
Since liaison relationships are intended to be mutually beneficial, Since liaison relationships are intended to be mutually beneficial,
the IETF liaison to another organization must act as a bi-directional the IETF liaison to another organization must act as a bi-directional
communication link between the IETF and the other organization. communication link between the IETF and the other organization.
Since the liaison manager has been appointed by the IETF, the liaison Since the liaison manager has been appointed by the IETF, the liaison
manager is accountable to the IETF. manager needs to be responsive to the needs and aims of the IETF.
RFC 4052 lists some of the tasks and expectations relating to liaison RFC 4052 lists some of the tasks and expectations relating to liaison
managers. This document provides more detailed discussion and managers. This document provides more detailed discussion and
describes how the role is executed. describes how the role is executed.
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.
skipping to change at page 7, line 35 skipping to change at page 8, line 35
Timeliness Timeliness
It is expected that a liaison manger will make the IETF aware of new It is expected that a liaison manger will make the IETF aware of new
developments in the subject area in a timely fashion. developments in the subject area in a timely fashion.
3.2. Responsibilities 3.2. Responsibilities
The liaison manager provides information to the IETF community in The liaison manager provides information to the IETF community in
order to enable the IETF to make decisions based on the best possible order to enable the IETF to make decisions based on the best possible
information. Information communicated by the IETF liaison to the information. Information communicated by the IETF liaison to the
liased organization is based on IETF consensus. The liaison manager liaised organization is based on IETF consensus. The liaison manager
works with the liaised organization to ensure that communication is works with the liaised organization to ensure that communication is
clear. As part of this, the liaison manager must clearly clear. As part of this, the liaison manager must clearly
differentiate their own independent positions from those which differentiate their own independent positions from those which
represent IETF consensus. represent IETF consensus.
It is the responsibility of the liaison manager to ensure that the It is the responsibility of the liaison manager to ensure that the
liaised organization provides its requirements to the IETF and that liaised organization provides its requirements to the IETF and that
the IETF consensus is clearly understood. This is particularly the IETF consensus is clearly understood. This is particularly
important in situations where the IETF and the liased organization important in situations where the IETF and the liaised organization
differ substantially in their positions. In this situation the differ substantially in their positions. In this situation the
liaison manager needs to facilitate prompt communication so that the liaison manager needs to facilitate prompt communication so that the
IETF and the liased organization can stay in close communication. IETF and the liaised organization can stay in close communication.
The liaison managers are responsible for clearly and correctly The liaison managers are responsible for clearly and correctly
communicating the IETF consensus position to the liased organization. communicating the IETF consensus position to the liaised
This includes, when specifically instructed, to carry any messages organization. This includes, when specifically instructed, to carry
from the IETF to the peer organization. Generally, these any messages from the IETF to the peer organization. Generally,
communications "represent the IETF", and therefore due care and these communications "represent the IETF", and therefore due care and
consensus must be applied in their construction. consensus must be applied in their construction.
The liaison managers are responsible for ensuring that relevant The liaison managers are responsible for ensuring that relevant
information originating from the liaised organization, or other information originating from the liaised organization, or other
information coming to the attention of the liaison manager, reaches information coming to the attention of the liaison manager, reaches
the correct destination within the IETF, in a timely and correct way. the correct destination within the IETF, in a timely and correct way.
3.3. Tasks 3.3. Tasks
Examples of tasks performed by the liaison manager are provided Examples of tasks performed by the liaison manager are provided
below. Depending on the nature of liaised organization the task may below. Depending on the nature of liaised organization the task may
vary in frequency and relative importance. vary in frequency and relative importance.
1. Attend relevant meetings and participate in conference calls and 1. Attend relevant meetings and participate in conference calls and
mailing lists within the liased organization. Report back to the mailing lists within the liaised organization. Report back to
IETF on the developments of interest. the IETF on the developments of interest.
2. A liaison manager is encouraged to communicate; sometimes this 2. A liaison manager is encouraged to communicate; sometimes this
involves holding frequent update meetings with a team of IETFers involves holding frequent update meetings with a team of IETFers
involved in the liaised organization and other interested parties involved in the liaised organization and other interested parties
within the IETF, e.g. working group chairs and ADs. A within the IETF, e.g. working group chairs and ADs. A
significant result of holding such meetings is an increased significant result of holding such meetings is an increased
understanding, and eventually IETF support, for the other understanding, and eventually IETF support, for the other
organizations goals. organizations goals.
3. Prepare updates as requested. The target for these updates 3. Prepare updates as requested. The target for these updates
(e.g., the IAB, an AD, a WG) will typically be identified upon (e.g., the IAB, an AD, a WG) will typically be identified upon
establishment of the liaison relationship and/or the appointment establishment of the liaison 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.
This includes ensuring that liaison statements are delivered to This includes ensuring that liaison statements are delivered to
the appropriate destination within the IETF, as well as the appropriate destination within the IETF, as well as
sheparding the timely creation of responses by the IETF. shepherding 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. To accomplish this, the liaison needs to build a timely fashion. To accomplish this, the liaison needs to build
a contact network. a contact network.
6. Communicate and coordinate with other IETF liaison managers where 6. Communicate and coordinate with other IETF liaison managers where
the activities of two or more liaised organizations overlap. the activities of two or more liaised organizations overlap.
7. Assist with the preparation of IETF liaison statements based on 7. Assist with the preparation of IETF liaison statements based on
IETF consensus. IETF consensus.
8. Liaison mangers and liaison representatives shall report to the 8. Liaison mangers and liaison representatives will have to report
IETF on the status of the liaison relationship and keep track of to the IETF on the status of the liaison relationship and keep
outstanding issues on behalf of the IETF. The frequency of the track of outstanding issues on behalf of the IETF. The frequency
reports and the recipients of the reports within the IETF will be of the reports and the recipients of the reports within the IETF
decided when the liaison relationship is set up and may be will be decided when the liaison relationship is set up and may
changed at any time by an IAB decision. IAB or other parties be changed at any time by an IAB decision. IAB or other parties
within the IETF may probe for liaison reports as needed or at within the IETF may probe for liaison reports as needed or at
reegular intervals. reegular intervals.
3.4. Mandate 3.4. Mandate
In Section 3.2 and in Section 3.3, tasks and responsibilities are In Section 3.2 and in Section 3.3, tasks and responsibilities are
listed which enable the IETF to obtain the information to correctly listed which enable the IETF to obtain the information to correctly
interact with the liased organizations and to develop and clearly interact with the liaised organizations and to develop and clearly
communicate IETF consensus. communicate IETF consensus.
The mandate for IETF liaison managers is strictly limited to The mandate for IETF liaison managers is strictly limited to
conveying IETF consensus to the liaised organization. The liaison conveying IETF consensus to the liaised organization. The liaison
manager MUST NOT on their own initiative, send liaison statements to manager MUST NOT on their own initiative, send liaison statements to
a liaised organization on behalf of IETF, its areas and working a liaised organization on behalf of IETF, or any of its areas and
groups. Liaison statements are only sent following the process working groups. Liaison statements are only sent following the
specified in [RFC4052]. Liaison statements are only sent on the process specified in [RFC4052]. Liaison statements are only sent on
initiative of the IETF chair, the IAB chair, IETF Area Directors or the initiative of the IETF chair, the IAB chair, IETF Area Directors
IETF working group chairs. or IETF working group chairs.
3.4.1. Speaking for the IETF 3.4.1. Speaking for the IETF
The IETF functions based on rough consensus, which means that the The IETF functions based on rough consensus, which means that the
right to speak for the IETF cannot be delegated. The liaison manager right to speak for the IETF cannot be delegated. The liaison manager
speaks on behalf of the IETF on the subject matter of the liaison, speaks on behalf of the IETF on the subject matter of the liaison,
but only after making sure that the IETF consensus is understood. but only after making sure that the IETF consensus is understood.
Some guidelines for understanding IETF consensus are provided above; Some guidelines for understanding IETF consensus are provided above;
however, the most important requirement is close and detailed however, the most important requirement is close and detailed
coordination/consultation with the IETF community. coordination/consultation with the IETF community.
skipping to change at page 10, line 20 skipping to change at page 11, line 20
of facts (e.g., to inform the liaised organization that an IETF Last of facts (e.g., to inform the liaised organization that an IETF Last
Call had started on a document they had previously expressed interest Call had started on a document they had previously expressed interest
in) and in these cases the liaison statement can be written and sent in) and in these cases the liaison statement can be written and sent
(such as by a working group chair), possibly involving the liaison (such as by a working group chair), possibly involving the liaison
manager. manager.
3.5.2. Incoming Liaison Statements 3.5.2. Incoming Liaison Statements
When the IETF receives a liaison statement or other communication When the IETF receives a liaison statement or other communication
from an organization with which it has an liaison relationship that from an organization with which it has an liaison relationship that
includes a request for a response to the communnication, the IETF is includes a request for a response to the communication, the IETF is
committed to providing a timely response. This means that IETF will committed to providing a timely response. This means that IETF will
respond within the time requested, and provide information as respond within the time requested, and provide information as
accurately as possible. This commitment has been one of the key accurately as possible. This commitment has been one of the key
discussion points in the past, such as within the (g)mpls change discussion points in the past, such as within the (g)mpls change
process [I-D.andersson-rtg-gmpls-change]. process [I-D.andersson-rtg-gmpls-change].
This commitment does not mean that the IETF will uncritically accept This commitment does not mean that the IETF will uncritically accept
the content in the incoming liaison statement. To the extent the the content in the incoming liaison statement. To the extent the
liaison contains requirements on IETF technology or protocols they liaison contains requirements on IETF technology or protocols they
will be taken into consideration based on their technical merit. will be taken into consideration based on their technical merit.
3.5.3. Ambiguous incoming Liaison Statements 3.5.3. Ambiguous incoming Liaison Statements
Sometimes the IETF, an IETF area or an IETF working group receives Sometimes the IETF, an IETF area or an IETF working group receives
liaison statements from a liaised organisation that is sent to the liaison statements from a liaised organization that is sent to the
wrong destination. At other times the liaison statement is sent to wrong destination. At other times the liaison statement is sent to
working groups that are not chartered to do the work that the liaison working groups that are not chartered to do the work that the liaison
statement addresses. In some cases it might be the situation that no statement addresses. In some cases it might be the situation that no
working group is chartered to do the work. working group is chartered to do the work.
In such cases the liaison manager should assist in finding the In such cases the liaison manager should assist in finding the
appropriate recipient within the IETF that might respond to the appropriate recipient within the IETF that might respond to the
incoming liaison statement. Sometimes this might require that the incoming liaison statement. Sometimes this might require that the
intended response is made available for review on one of the IETF intended response is made available for review on one of the IETF
mailing lists. mailing lists.
3.5.4. Liaison managers representing other SDOs 3.5.4. Liaison managers representing other SDOs
Liased organizations may appoint a person to act as a liaison manager Liaised organizations may appoint a person to act as a liaison
for "their side" of the relationship. This is the person that will manager for "their side" of the relationship. This is the person
speak authoritatively, within the IETF, 0n the activities performed that will speak authoritatively, within the IETF, on the activities
by the other organization. The other organization needs to make this performed by the other organization. The other organization needs to
person known to the IETF. This person might request a slot on a make this person known to the IETF. This person might request a slot
working group agenda to discuss developments and plans of the liaised on a working group agenda to discuss developments and plans of the
organization. liaised organization.
The mandate of liaison managers from other organizations are The mandates of liaison managers from other organizations are
recognized by the IETF to the extent needed to understand the recognized by the IETF to the extent needed to understand the
information received from the liaison manager. In all other respects information received from the liaison manager. In all other respects
he/she participates in IETF activities under the same conditions and he/she participates in IETF activities under the same conditions and
rules as any other IETF participant. rules as any other IETF participant.
Note that, according to IETF process [RFC3356], opinions expressed by Note that, according to IETF process [RFC3356], opinions expressed by
any such liaison manager are given equal weight with opinions any such liaison manager are given equal weight with opinions
expressed by other working group participants. expressed by other working group participants.
IETF liaison managers should work to include the liaison manager from IETF liaison managers should work to include the liaison manager from
skipping to change at page 13, line 8 skipping to change at page 14, line 8
This document does not specify any protocol or "bits on the wire". This document does not specify any protocol or "bits on the wire".
However, since interaction with other standards-making organizations However, since interaction with other standards-making organizations
often relates to security, the liaison manager can assist with often relates to security, the liaison manager can assist with
security related issues, resulting in improved security for Internet security related issues, resulting in improved security for Internet
protocols. 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 convey questions regarding
IETF namespace. IETF namespaces managed by IANA.
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 members 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 A special thanks to Bernard Aboba who apart from drawing on his
experience as a liaison manager has made many useful comments on the experience as a liaison manager has made many useful comments on the
subjet matter, also has spent time on correcting language and subject matter, also has spent time on correcting language and
grammar. 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 Elwyn Davies
Bob Hinden Kevin Fall
Olaf Kolkman
Kurtis Lindqvist Kurtis Lindqvist
David Meyer David Meyer
Pekka Nikander Dave Oran
Eric Rescorla Eric Rescorla
Pete Resnick Dave Thaler
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 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 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
skipping to change at page 15, line 29 skipping to change at page 16, line 29
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] [I-D.andersson-rtg-gmpls-change]
Andersson, L., "MPLS and GMPLS Change Process", Andersson, L., "MPLS and GMPLS Change Process",
draft-andersson-rtg-gmpls-change-02 (work in progress), draft-andersson-rtg-gmpls-change-02 (work in progress),
December 2005. December 2005.
[RFC3113] Rosenbrock, K., Sanmugam, R., Bradner, S., and J. Klensin,
"3GPP-IETF Standardization Collaboration", RFC 3113,
June 2001.
[RFC3131] Bradner, S., Calhoun, P., Cuschieri, H., Dennett, S.,
Flynn, G., Lipford, M., and M. McPheters, "3GPP2-IETF
Standardization Collaboration", RFC 3131, June 2001.
[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
Loa Andersson Loa Andersson
Acreo AB IAB
Email: loa@pi.se Email: loa@pi.se
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
 End of changes. 31 change blocks. 
76 lines changed or deleted 88 lines changed or added

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