draft-iab-rfc3356bis-03.txt   draft-iab-rfc3356bis-04.txt 
Internet Architecture Board (IAB) S. Trowbridge, Ed. Internet Architecture Board (IAB) S. Trowbridge, Ed.
Internet-Draft Alcatel-Lucent Internet-Draft Alcatel-Lucent
Obsoletes: 3356 E. Lear, Ed. Obsoletes: 3356 E. Lear, Ed.
Intended status: Informational Cisco Systems Intended status: Informational Cisco Systems
G. Fishman, Ed. G. Fishman, Ed.
Pearlfisher International Pearlfisher International
S. Bradner, Ed. S. Bradner, Ed.
Harvard University Harvard University
Expires: December 4, 2012 June 11, 2012 Expires: December 18, 2012 June 19, 2012
Internet Engineering Task Force and International Internet Engineering Task Force and International
Telecommunication Union - Telecommunication Standardization Telecommunication Union - Telecommunication Standardization
Sector Collaboration Guidelines Sector Collaboration Guidelines
draft-iab-rfc3356bis-03 draft-iab-rfc3356bis-04
Abstract Abstract
This document provides guidance to aid in the understanding of This document provides guidance to aid in the understanding of
collaboration on standards development between the International collaboration on standards development between the International
Telecommunication Union -- Telecommunication Standardization Telecommunication Union -- Telecommunication Standardization
Sector (ITU-T) and the Internet Society (ISOC) -- Internet Sector (ITU-T) and the Internet Society (ISOC) -- Internet
Engineering Task Force (IETF). It is an update of and obsoletes Engineering Task Force (IETF). It is an update of and obsoletes
RFC 3356. The updates reflect changes in the IETF and ITU-T RFC 3356. The updates reflect changes in the IETF and ITU-T
since RFC 3356 was written. The bulk of this document is common since RFC 3356 was written. The bulk of this document is common
skipping to change at page 3, line 18 skipping to change at page 3, line 18
2. Guidance on Collaboration......................................5 2. Guidance on Collaboration......................................5
2.1. How to Interact on ITU-T or IETF Work Items...............5 2.1. How to Interact on ITU-T or IETF Work Items...............5
2.1.1. How the ITU-T is informed about Existing IETF Work 2.1.1. How the ITU-T is informed about Existing IETF Work
Items.......................................................6 Items.......................................................6
2.1.2. How the IETF is informed about Existing ITU-T Work 2.1.2. How the IETF is informed about Existing ITU-T Work
Items.......................................................6 Items.......................................................6
2.1.3. How the ITU-T is informed about proposed new IETF work 2.1.3. How the ITU-T is informed about proposed new IETF work
items.......................................................6 items.......................................................6
2.1.4. How the IETF is informed about ITU-T Work Items......7 2.1.4. How the IETF is informed about ITU-T Work Items......7
2.2. Representation............................................7 2.2. Representation............................................7
2.2.1. IETF Recognition at ITU-T............................7 2.2.1. ITU-T Recognition at ISOC/IETF.......................7
Experts and representatives from the IETF that are chosen by
IETF leadership normally participate in ITU-T meetings as ISOC
delegates. The ISOC focal point will facilitate registration
and verification of these people, as appropriate............7
2.2.2. ITU-T Recognition at ISOC/IETF.......................7
2.3. Communication outside of Meetings.........................8 2.3. Communication outside of Meetings.........................8
2.4. Mailing Lists.............................................8 2.4. Mailing Lists.............................................8
2.5. Document Sharing..........................................9 2.5. Document Sharing..........................................9
2.5.1. Contributions and Liaison Statements from the IETF to 2.5.1. Contributions and Liaison Statements from the IETF to
ITU-T.......................................................9 ITU-T.......................................................9
2.5.2. Contributions and Liaison Statements from the ITU-T to 2.5.2. Contributions and Liaison Statements from the ITU-T to
IETF.......................................................10 IETF.......................................................10
2.5.3. ITU-T & IETF........................................10 2.5.3. ITU-T & IETF........................................10
2.6. Simple Cross Referencing.................................11 2.6. Simple Cross Referencing.................................11
2.7. Preliminary Work Efforts.................................11 2.7. Preliminary Work Efforts.................................11
skipping to change at page 4, line 15 skipping to change at page 4, line 15
[The following note to be removed upon publication as an RFC] [The following note to be removed upon publication as an RFC]
Editors' Note: Editors' Note:
This Informational Internet-Draft is intended for publication as an This Informational Internet-Draft is intended for publication as an
RFC with the IAB stream, and is subject to the publication process RFC with the IAB stream, and is subject to the publication process
described in RFC 4845. described in RFC 4845.
1. Introduction & Scope 1. Introduction & Scope
This document provides guidance to aid in the understanding of This document provides non-normative guidance to aid in the
collaboration on standards development between the International understanding of collaboration on standards development between the
Telecommunication Union - Telecommunication Standardization Sector International Telecommunication Union - Telecommunication
(ITU-T) and the Internet Society (ISOC) -- Internet Engineering Task Standardization Sector (ITU-T) and the Internet Society (ISOC) --
Force (IETF). Early identification of topics of mutual interest Internet Engineering Task Force (IETF). Early identification of
will allow for constructive efforts between the two organizations. topics of mutual interest will allow for constructive efforts
between the two organizations based on mutual respect.
In the IETF, work is done in working groups (WG), mostly through In the IETF, work is done in working groups (WG), mostly through
open, public mailing lists rather than face-to-face meetings. open, public mailing lists rather than face-to-face meetings.
WGs are organized into Areas, each Area being managed by two co- WGs are organized into Areas, each Area being managed by two co-
area directors. Collectively, the area directors comprise the area directors. Collectively, the area directors comprise the
Internet Engineering Steering Group (IESG). Internet Engineering Steering Group (IESG).
In the ITU-T, work is defined by study questions which are In the ITU-T, work is defined by study questions which are
worked on mostly through meetings led by rapporteurs (these are worked on mostly through meetings led by rapporteurs (these are
sometimes called "Rapporteur's Group" meetings). Questions are sometimes called "Rapporteur's Group" meetings). Questions are
skipping to change at page 5, line 21 skipping to change at page 5, line 23
It may be beneficial to establish additional contact points It may be beneficial to establish additional contact points
for specific topics of mutual interest. These contact points for specific topics of mutual interest. These contact points
should be established early in the work effort, and in some should be established early in the work effort, and in some
cases the contact point identified by each organization may be cases the contact point identified by each organization may be
the same individual. In addition, the ITU-T has an additional the same individual. In addition, the ITU-T has an additional
level of management, the working party chair. From time to level of management, the working party chair. From time to
time it may be beneficial for this person to exchange views time it may be beneficial for this person to exchange views
with IETF working group chairs and area directors. with IETF working group chairs and area directors.
Note that the current IETF area directors and working group Note that the current list of IETF area directors and working
chairs can be found in the IETF working group charters. The group chairs can be found in the IETF working group charters.
current ITU-T study group chairmen and rapporteurs are listed on The current ITU-T study group chairmen and rapporteurs are
the ITU-T web page. listed on the ITU-T web page.
2. Guidance on Collaboration 2. Guidance on Collaboration
This section describes how the existing processes within the IETF This section describes how the existing processes within the IETF
and ITU-T may be utilized to enable collaboration between the and ITU-T may be utilized to enable collaboration between the
organizations. organizations.
2.1. How to Interact on ITU-T or IETF Work Items 2.1. How to Interact on ITU-T or IETF Work Items
Study groups that have identified work topics that are IP- Study groups that have identified work topics that are IP-
skipping to change at page 7, line 8 skipping to change at page 7, line 12
for possible overlap or interest to their study group. It is for possible overlap or interest to their study group. It is
expected that this mailing list will see a few messages per month. expected that this mailing list will see a few messages per month.
Each SG chairman, or designated representative, may provide comments Each SG chairman, or designated representative, may provide comments
on these charters by responding to the IESG mailing list at on these charters by responding to the IESG mailing list at
iesg@ietf.org clearly indicating their ITU-T position and the nature iesg@ietf.org clearly indicating their ITU-T position and the nature
of their concern. Plain-text email is preferred on the IESG mailing of their concern. Plain-text email is preferred on the IESG mailing
list. list.
It should be noted that the IETF turnaround time for new working It should be noted that the IETF turnaround time for new working
group charters is two weeks. As a result, the mailing list group charters can be as short as two weeks. As a result, the
should be consistently monitored. mailing list should be consistently monitored.
2.1.4. How the IETF is informed about ITU-T Work Items 2.1.4. How the IETF is informed about ITU-T Work Items
The ITU-T accepts new areas of work through the creation or update The ITU-T accepts new areas of work through the creation or update
of Questions and these can be found on the ITU-T Study Group web of Questions and these can be found on the ITU-T Study Group web
pages. In addition, the ITU-T work programme is documented on each pages. In addition, the ITU-T work programme is documented on each
ITU-T study group's web page on the ITU-T web site. ITU-T study group's web page on the ITU-T web site.
Study groups send updates to the IETF new-work mailing list as new Study groups send updates to the IETF new-work mailing list as new
Questions are first drafted or created, terms of reference for Questions are first drafted or created, terms of reference for
skipping to change at page 7, line 36 skipping to change at page 7, line 40
2.2. Representation 2.2. Representation
ISOC, including its standards body IETF, is a Sector Member of the ISOC, including its standards body IETF, is a Sector Member of the
ITU-T. As a result, ISOC delegates are therefore afforded the same ITU-T. As a result, ISOC delegates are therefore afforded the same
rights as other ITU-T Sector Members (see 2.2.1). Conversely, ITU-T rights as other ITU-T Sector Members (see 2.2.1). Conversely, ITU-T
delegates may participate in the work of the IETF as representatives delegates may participate in the work of the IETF as representatives
of the ITU-T (see 2.2.2). To promote collaboration it is useful to of the ITU-T (see 2.2.2). To promote collaboration it is useful to
facilitate communication between the organizations as further facilitate communication between the organizations as further
described below. described below.
2.2.1. IETF Recognition at ITU-T IETF Recognition at ITU-T
Experts and representatives from the IETF that are chosen by IETF Experts and representatives from the IETF that are chosen by IETF
leadership normally participate in ITU-T meetings as ISOC delegates. leadership normally participate in ITU-T meetings as ISOC delegates.
The ISOC focal point will facilitate registration and verification The ISOC focal point will facilitate registration and verification
of these people, as appropriate. of these people, as appropriate.
2.2.2. ITU-T Recognition at ISOC/IETF 2.2.1. ITU-T Recognition at ISOC/IETF
ITU-T study group chairmen can authorize one or more members to ITU-T study group chairmen can authorize one or more members to
attend an IETF meeting as an official ITU-T delegate speaking attend an IETF meeting as an official ITU-T delegate speaking
authoritatively on behalf of the activities of the study group (or a authoritatively on behalf of the activities of the study group (or a
particular rapporteur group). The study group chairman sends the particular rapporteur group). The study group chairman sends the
ITU-T list of delegates by email to the working group chair, with a 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, copy to the area directors, and also to the study group. Note that,
according to IETF process, opinions expressed by any such delegate according to IETF process, opinions expressed by any such delegate
are given equal weight with opinions expressed by any other working are given equal weight with opinions expressed by any other working
group participant. group participant.
skipping to change at page 9, line 7 skipping to change at page 9, line 10
the ITU-T, the TSB has set up formal mailing lists for Questions, the ITU-T, the TSB has set up formal mailing lists for Questions,
working parties and other topics within study groups (more detail working parties and other topics within study groups (more detail
can be found on the ITU-T website). These mailing lists are can be found on the ITU-T website). These mailing lists are
typically used for ITU-T correspondence, including technical typically used for ITU-T correspondence, including technical
discussion, meeting logistics, reports, etc. Note that individual discussion, meeting logistics, reports, etc. Note that individual
subscribers to this list must be affiliated with an ITU-T member or subscribers to this list must be affiliated with an ITU-T member or
associate (at this time, there is no blanket inclusion of all IETF associate (at this time, there is no blanket inclusion of all IETF
participants as members, however, as a member, the ISOC focal point participants as members, however, as a member, the ISOC focal point
can facilitate access by IETF technical experts, liaison can facilitate access by IETF technical experts, liaison
representatives, or liaison managers). IETF participants may representatives, or liaison managers). IETF participants may
subscribe to ITU-T focus group email lists if they are from a subscribe to ITU-T focus group email lists if they are citizens of
country that is a member of ITU-T. countries that are members of the ITU-T.
2.5. Document Sharing 2.5. Document Sharing
During the course of ITU-T and IETF collaboration it is important to During the course of ITU-T and IETF collaboration it is important to
share working drafts and documents among the technical working share working drafts and documents among the technical working
groups. Initially proposed concepts and specifications typically groups. Initially proposed concepts and specifications typically
can be circulated by email (often just repeating the concept and not can be circulated by email (often just repeating the concept and not
including the details of the specification) on both the IETF and including the details of the specification) on both the IETF and
ITU-T mailing lists. In addition, working texts (or URLs) of draft ITU-T mailing lists. In addition, working texts (or URLs) of draft
Recommendations, Internet-Drafts or RFCs may also be sent between Recommendations, Internet-Drafts or RFCs may also be sent between
skipping to change at page 11, line 31 skipping to change at page 11, line 31
Both ITU-T and IETF provide mechanisms for early discussion of Both ITU-T and IETF provide mechanisms for early discussion of
potential new work areas prior to the official start of work in an potential new work areas prior to the official start of work in an
ITU-T study group or creation of an IETF working group. ITU-T study group or creation of an IETF working group.
Objectives, methods and procedures for the creation and operation of Objectives, methods and procedures for the creation and operation of
ITU-T focus groups are defined in Recommendation ITU-T A.7. Focus ITU-T focus groups are defined in Recommendation ITU-T A.7. Focus
groups are frequently created in new work areas where there is a groups are frequently created in new work areas where there is a
need for deliverables to be produced on a specific topic within a need for deliverables to be produced on a specific topic within a
short timeframe. IETF participants who are not members or associates short timeframe. IETF participants who are not members or associates
of ITU-T may participate fully in the work of ITU-T focus groups if of ITU-T may participate fully in the work of ITU-T focus groups if
they are from a country that is a member of ITU-T. they are citizens of countries that are members of the ITU-T.
In the IETF, guidance for Birds Of a Feather (BoF) sessions is In the IETF, guidance for Birds Of a Feather (BoF) sessions is
provided in RFC 5434. Efforts that have not yet reached the working provided in RFC 5434. Efforts that have not yet reached the working
group stage may be discussed in BOF sessions.[13] These sessions group stage may be discussed in BOF sessions.[13] These sessions
typically gauge interest in pursuing creation of working groups. In typically gauge interest in pursuing creation of working groups. In
some cases, these discussions continue on mailing lists. some cases, these discussions continue on mailing lists.
2.8. Additional Items 2.8. Additional Items
2.8.1. IETF Information that may be of use to ITU-T participations 2.8.1. IETF Information that may be of use to ITU-T participations
skipping to change at page 12, line 36 skipping to change at page 12, line 36
Task Force, http://www.ietf.org/tao.html Task Force, http://www.ietf.org/tao.html
2.8.2. ITU-T Information that may be useful to IETF participants 2.8.2. ITU-T Information that may be useful to IETF participants
Information about the ITU-T can be found in the informative Information about the ITU-T can be found in the informative
references and at the URLs below. references and at the URLs below.
ITU-T Main page: http://itu.int/ITU-T ITU-T Main page: http://itu.int/ITU-T
List of all ITU-T Recommendations: List of all ITU-T Recommendations:
http://itu.int/itu-t/recommendations/index.aspx http://itu.int/itu-t/recommendations/
ITU-T Study Group main page for Study Group NN (where NN is the 2- ITU-T Study Group main page for Study Group NN (where NN is the 2-
digit SG number): digit SG number):
http://itu.int/ITU-T/studygroups/comNN/index.asp http://itu.int/ITU-T/studygroups/comNN/
Intellectual Property policies, forms and databases: Intellectual Property policies, forms and databases:
http://itu.int/en/ITU-T/ipr/Pages/default.aspx http://itu.int/en/ITU-T/ipr/Pages/default.aspx
Current list of active ITU-T focus Groups Current list of active ITU-T focus Groups
http://itu.int/en/ITU-T/focusgroups/Pages/default.aspx http://itu.int/en/ITU-T/focusgroups/Pages/default.aspx
ITU-T Procedures including: ITU-T Procedures including:
Resolution 1 - Rules of Procedure for ITU-T Resolution 1 - Rules of Procedure for ITU-T
Resolution 2 - Study Group responsibility and mandates Resolution 2 - Study Group responsibility and mandates
 End of changes. 12 change blocks. 
27 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/