📄 rfc3356.txt
字号:
Network Working Group G. Fishman
Request for Comments: 3356 Bell Laboratories
Obsoletes: 2436 S. Bradner
Category: Informational Harvard University
August 2002
Internet Engineering Task Force and International
Telecommunication Union - Telecommunications
Standardization Sector Collaboration Guidelines
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract
This document provides guidance to aid in the understanding of
collaboration on standards development between the International
Telecommunication Union -- Telecommunication Standardization Sector
(ITU-T) and the Internet Society (ISOC) / Internet Engineering Task
Force (IETF). It is an update of and obsoletes RFC 2436. The
updates reflect changes in the IETF and ITU-T since RFC 2436 was
written. The bulk of this document is common text with ITU-T
Supplement 3 to the ITU-T A-Series Recommendations.
Note: This was approved by ITU-T TSAG on 30 November 2001 as a
Supplement to the ITU-T A-Series of Recommendations (will be numbered
as A-Series Supplement 3).
Table of Contents
1. Scope...........................................................2
2. Introduction ...................................................2
3. Guidance on collaboration.......................................3
3.1 How to interact on ITU-T or IETF work items.....................3
3.2 Representation..................................................4
3.3 Document sharing................................................7
3.4 Simple cross referencing........................................8
3.5 Additional items................................................8
4. Security Considerations........................................10
5. Non-normative references.......................................10
6. Acknowledgements...............................................10
Fishman Informational [Page 1]
RFC 3356 IETF and ITU-T Collaboration Guidelines August 2002
7. Changes since RFC 2436.........................................10
8. Author's addresses.............................................11
9. Full Copyright Statement.......................................12
1. Scope
This document provides guidance to aid in the understanding of
collaboration on standards development between the ITU-T and the
Internet Society (ISOC) / Internet Engineering Task Force (IETF).
In the IETF, work is done in Working Groups (WG), mostly through
open, public mailing lists rather than face-to-face meetings. WGs
are organized into Areas, each Area being managed by two co-Area
Directors. Collectively, the Area Directors comprise the Internet
Engineering Steering Group (IESG).
In the ITU-T, work is defined by study Questions which are worked on
mostly through meetings led by Rapporteurs. Questions are generally
grouped within Working Parties (WPs) led by a WP Chairman. Working
Parties report to a parent Study Group led by a SG Chairman.
2. Introduction
The telecommunication industry is faced with an explosion in growth
of the Internet and other IP (Internet Protocol) based networks.
Operators, manufacturers and software/application providers alike are
reconsidering their business directions and Standards Development
Organizations and Forums and Consortia are facing an immense
challenge to address this situation.
These challenges were considered by TSAG in September 1998 and IETF
shortly thereafter, when it was initially recognized that the ITU-T
and ISOC/IETF were already collaborating in a number of areas, and
that this collaboration must be strengthened within the context of
changes in work emphasis and direction within the ITU-T on studies
related to IP based networks.
For example, many Study Groups already address aspects of IP based
networks. There are many topics of interest to ITU-T Study Groups in
the IP area that should be investigated (e.g., signaling, routing,
security, numbering & addressing, integrated management, performance,
IP - telecom interworking, access). Since many of these topics are
also being investigated by the IETF, there is a requirement for close
collaboration.
Fishman Informational [Page 2]
RFC 3356 IETF and ITU-T Collaboration Guidelines August 2002
The current level of cooperation between the ITU-T and the IETF
should be built upon to ensure that the competence and experience of
each organization is brought to bear in the most effective manner and
in collaboration with the other. This document provides guidelines
for collaboration between the ITU-T and the IETF.
3. Guidance on Collaboration
This section builds on existing collaborative processes and details
some of the more important guidance points that each organization
should be aware of for effective collaboration.
3.1 How to Interact on ITU-T or IETF Work Items
Study Groups that have identified work topics that are IP-related
should evaluate the relationship with topics defined in the IETF.
Current IETF Working Groups and their charters (IETF definition of
the scope of work) are listed in the IETF archives (see section 3.5).
A Study Group may decide that development of a Recommendation on a
particular topic may benefit from collaboration with the IETF. The
Study Group should identify this collaboration in its work plan
(specifically in that of each Question involved), describing the goal
of the collaboration and its expected outcome.
An IETF Working Group should also evaluate and identify areas of
relationship with the ITU-T and document the collaboration with the
ITU-T Study Group in its charter. The following sections outline a
process that can be used to enable each group to learn about the
other's new work items.
3.1.1 How the ITU-T Learns About Existing IETF Work Items
The responsibility is on individual Study Groups to review the
current IETF Working Groups to determine if there are any topics of
mutual interest. Should a Study Group believe that there is an
opportunity for collaboration on a topic of mutual interest, it
should contact both the IETF Working Group Chair and the Area
Director(s) responsible.
3.1.2 How the ITU-T learns about proposed new IETF work items
The IETF maintains a mailing list for the distribution of proposed
new work items among standards development organizations. The IETF
forwards draft charters for all new and revised Working Groups and
Birds Of a Feather session announcements to the IETF NewWork mailing
list. An ITU-T mail exploder is subscribed to this list. It is
recommended that each Study Group subscribe to this ITU-T exploder,
Fishman Informational [Page 3]
RFC 3356 IETF and ITU-T Collaboration Guidelines August 2002
which is maintained by the TSB. Members of the SG-specific listname
may include the SG Chairman, SG Vice Chairmen, Working Party
Chairmen, concerned Rapporteurs, other experts designated by the SG
and the SG Counselor. This will enable the SGs to monitor the new
work items for possible overlap or interest to their Study Group. It
is expected that this mailing list will see a few messages per month.
Each SG Chairman, or designated representative, may provide comments
on these charters by responding to the IESG mailing list at
iesg@ietf.org clearly indicating their ITU-T position and the nature
of their concern. Plain-text email is preferred on the IESG mailing
list.
It should be noted that the IETF turnaround time for new Working
Group charters is two weeks. As a result, the mailing list should be
consistently monitored.
3.1.3 How the IETF Learns About ITU-T Work Items
The ITU-T work programme is documented in the Questions of each Study
Group. These can be found on the ITU-T web site.
Study Groups should send updates to the IETF NewWork mailing list as
they occur. Area Directors or WG Chairs should provide comments to
the relevant SG Chairman in cases of possible overlap or interest.
3.2 Representation
ISOC, including its standards body IETF, is a Sector Member of the
ITU-T. As a result, ISOC delegates are therefore afforded the same
rights as other ITU-T Sector Members (see 3.2.1). Conversely, ITU-T
delegates may participate in the work of the IETF as representatives
of the ITU-T (see 3.2.2). To promote collaboration it is useful to
facilitate communication between the organizations as further
described below.
3.2.1 IETF Recognition at ITU-T
Participants from the IETF may participate in ITU-T meetings as ISOC
delegates if the appropriate IETF Working Group (or Area) has
approved their attendance. This approval will be communicated to the
TSB in the form of a registration for a particular ITU-T meeting by
the IAB Chair.
3.2.2 ITU-T Recognition at ISOC/IETF
ITU-T Study Group Chairmen can authorize one or more members to
attend an IETF meeting as an official ITU-T delegate speaking
authoritatively on behalf of the activities of the Study Group (or a
Fishman Informational [Page 4]
RFC 3356 IETF and ITU-T Collaboration Guidelines August 2002
particular Rapporteur Group). The Study Group Chairman sends the
ITU-T list of delegates by email to the Working Group chair, with a
copy to the Area Directors, and also to the Study Group. Note that,
according to IETF process, opinions expressed by any such delegate
are given equal weight with opinions expressed by other working group
participants.
3.2.3 Communication Contacts
To foster ongoing communication between the ITU-T and IETF, it is
important to identify and establish contact points within each
organization. Contact points may include:
1) ITU-T Study Group Chairman and IETF Area Director
An IETF Area Director is the individual responsible for overseeing
a major focus of activity with a scope similar to that of an ITU-T
Study Group Chairman. These positions are both relatively long-
term (of several years) and offer the stability of contact points
between the two organizations for a given topic.
2) ITU-T Rapporteur and IETF Working Group Chair
An IETF Working Group Chair is an individual who is assigned to
lead the work on a specific task within one particular Area with a
scope similar to that of an ITU-T Rapporteur. These positions are
working positions (of a year or more) that typically end when the
work on a specific topic ends. Collaboration here is very
beneficial to ensure the actual work gets done.
3) Other Contact Points
It may be beneficial to establish additional contact points for
specific topics of mutual interest. These contact points should
be established early in the work effort, and in some cases the
contact point identified by each organization may be the same
individual.
Note that the current IETF Area Directors and Working Group Chairs
can be found in the IETF Working Group charters. The current ITU-T
Study Group Chairmen and Rapporteurs are listed on the ITU-T web
page.
3.2.4 Communication
Informal communication between contact points and experts of both
organizations is encouraged. However, note that formal communication
from an ITU-T Study Group, Working Party or Rapporteur to an
Fishman Informational [Page 5]
RFC 3356 IETF and ITU-T Collaboration Guidelines August 2002
associated IETF contact point must be explicitly approved and
identified as coming from the Study Group, Working Party or
Rapporteur Group, respectively. Formal communication from the ITU-T
to the IETF should be addressed to the appropriate Working Group
Chairs and Area Directors with a copy to the email address
"statements@ietf.org." These communications are placed by the IETF
onto a liaison statements web page at
http://www.ietf.org/IESG/liaison.html. An individual at the IETF is
assigned responsibility for dealing with each communication that is
received. The name and contact information of the responsible person
is listed with the links to the communications on this web page.
Conversely, formal communication from an IETF Working Group or Area
Director must also be explicitly approved and identified before
forwarding to any ITU-T contact. This approval is indicated in IETF
communication by copying the appropriate Working Group Chairs and
Area Directors. Formal communication is intended to allow the
sharing of positions between the IETF and the ITU-T outside of actual
documents (as described in 3.3). This would cover such things as
comments on documents and requests for input. The approved
communication is simply emailed from one body contact to another (the
appropriate mailing lists, as described in 3.2.5 may be copied).
3.2.5 Mailing Lists
All IETF Working Groups and all ITU-T Study Group Questions have
associated mailing lists.
In the IETF, the mailing list is the primary vehicle for discussion
and decision-making. It is recommended that the ITU-T experts
interested in particular IETF Working Group topics subscribe to and
participate in these lists. IETF WG mailing lists are open to all
subscribers. The IETF Working Group mailing list subscription and
archive information are noted in each Working Group's charter. In
the ITU-T, the TSB has set up formal mailing lists for Questions,
Working Parties and other topics within Study Groups (more detail can
be found on the ITU website). These mailing lists are typically used
for discussion of ITU-T contributions. Note that individual
subscribers to this list must be affiliated with an ITU-T member (at
this time, there is no blanket inclusion of all IETF participants as
members, however, as a member, ISOC may designate representatives to
subscribe). Alternatively, ITU-T members operate personal mailing
lists on various topics with no restrictions on membership (e.g.,
IETF participants are welcome).
Fishman Informational [Page 6]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -