draft-iab-rfc3356bis-00.txt   draft-iab-rfc3356bis-01.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
Expires: October 9, 2012 April 5, 2012 S. Bradner, Ed.
Harvard University
Expires: October 19, 2012 April 19, 2012
Internet Engineering Task Force and International Internet Engineering Task Force and International
Telecommunication Union - Telecommunications Standardization Telecommunication Union - Telecommunications Standardization
Sector Collaboration Guidelines Sector Collaboration Guidelines
draft-iab-rfc3356bis-00 draft-iab-rfc3356bis-01
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
text with ITU-T Supplement 3 to the ITU-T A-Series text with ITU-T Supplement 3 to the ITU-T A-Series
Recommendations. Recommendations.
Note: This was approved by ITU-T TSAG on xx July 2012 as a Note: This was approved by ITU-T TSAG on xx July 2012 as a
Supplement to the ITU-T A-Series of Recommendations (will be Supplement to the ITU-T A-Series of Recommendations (will be
numbered as A-Series Supplement 3). numbered as A-Series Supplement 3).
skipping to change at page 3, line 11 skipping to change at page 3, line 11
document must include Simplified BSD License text as described document must include Simplified BSD License text as described
in Section 4.e of the Trust Legal Provisions and are provided in Section 4.e of the Trust Legal Provisions and are provided
without warranty as described in the Simplified BSD License. without warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Scope..........................................................4 1. Scope..........................................................4
2. Introduction...................................................4 2. Introduction...................................................4
3. Guidance on Collaboration......................................5 3. Guidance on Collaboration......................................5
3.1. How to Interact on ITU-T or IETF Work Items...............5 3.1. How to Interact on ITU-T or IETF Work Items...............5
3.1.1. How the ITU-T is informed about Existing IETF Work Items 3.1.1. How the ITU-T is informed about Existing IETF Work
............................................................5 Items.......................................................5
3.1.2. How the ITU-T is informed about proposed new IETF work 3.1.2. How the ITU-T is informed about proposed new IETF work
items.......................................................6 items.......................................................5
3.1.3. How the IETF is informed about ITU-T Work Items......6 3.1.3. How the IETF is informed about ITU-T Work Items......6
3.2. Representation............................................7 3.2. Representation............................................6
3.2.1. IETF Recognition at ITU-T............................7 3.2.1. IETF Recognition at ITU-T............................6
Experts and representatives from the IETF that are chosen by
IETF leadership may participate in ITU-T meetings as ISOC
delegates. The ISOC focal point will facilitate registration
and verification of these people, as appropriate............6
3.2.2. ITU-T Recognition at ISOC/IETF.......................7 3.2.2. ITU-T Recognition at ISOC/IETF.......................7
3.2.3. Communication Contacts...............................7 3.2.3. Communication Contacts...............................7
3.2.4. Communication........................................8 3.2.4. Communication........................................8
3.2.5. Mailing Lists........................................8 3.2.5. Mailing Lists........................................8
3.3. Document Sharing..........................................9 3.3. Document Sharing..........................................9
3.3.1. IETF to ITU-T........................................9 3.3.1. IETF to ITU-T........................................9
3.3.2. ITU-T to IETF.......................................10 3.3.2. ITU-T to IETF.......................................10
3.3.3. ITU-T & IETF........................................10 3.3.3. ITU-T & IETF........................................10
3.4. Simple Cross Referencing.................................11 3.4. Simple Cross Referencing.................................11
3.5. Preliminary Work Efforts.................................11 3.5. Preliminary Work Efforts.................................11
3.6. Additional Items.........................................11 3.6. Additional Items.........................................11
3.6.1. Useful Information to ITU-T participations on the IETF11 3.6.1. IETF Information that may be of use to ITU-T
3.6.2. Current ITU-T information can be found on the ITU participations.............................................11
website: (includes contacts, organization, Recommendations for 3.6.2. ITU-T Information that may be useful to IETF
purchase, mailing list info, etc.).........................12 participants...............................................12
4. Security Considerations.......................................13 4. Security Considerations.......................................13
5. IANA Considerations...........................................13 5. IANA Considerations...........................................13
6. References....................................................13 6. Acknowledgements..............................................13
6.1. Normative References.....................................13 7. References....................................................13
6.2. Non-normative References.................................14 7.1. Normative References.....................................13
7. Acknowledgements..............................................14 7.2. Informative References...................................14
8. Changes since RFC3356.........................................14 8. Changes since RFC3356.........................................15
9. Authors' Addresses............................................15 9. Authors' Addresses............................................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. Scope 1. Scope
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 ITU-T and the collaboration on standards development between the ITU-T and the
Internet Society (ISOC) / Internet Engineering Task Force Internet Society (ISOC) -- Internet Engineering Task Force
(IETF). (IETF).
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. Questions worked on mostly through meetings led by rapporteurs. Questions
are generally grouped within Working Parties (WPs) led by a WP are generally grouped within Working Parties (WPs) led by a WP
Chairman. Working Parties report to a parent Study Group led by chairman. Working Parties report to a parent Study Group led by
a SG Chairman. Work may also be conducted in ITU-T focus groups a SG chairman. Work may also be conducted in ITU-T focus groups
(see 3.5. ) (see 3.5)
2. Introduction 2. Introduction
The telecommunication industry is faced with an explosion in growth The telecommunication industry is faced with an explosion in growth
of the Internet and other IP (Internet Protocol) based networks. of the Internet and other IP (Internet Protocol) based networks.
Operators, manufacturers and software/application providers alike are Operators, manufacturers and software/application providers alike
reconsidering their business directions and Standards Development are reconsidering their business directions and Standards
Organizations and Forums and Consortia are facing an immense Development Organizations and forums and consortia are facing an
challenge to address this situation. 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 This document provides guidelines for communication between the IETF
based networks. There are many topics of interest to ITU-T and the ITU-T concerning topics of common interest. Early
Study Groups in the IP area that should be investigated (e.g., identification of these topics will allow for constructive efforts
signaling, routing, security, numbering & addressing, integrated between the two organizations.
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.
The current level of cooperation between the ITU-T and the IETF The current level of cooperation between the ITU-T and the IETF
should be built upon to ensure that the competence and experience of should be built upon to ensure that the competence and experience of
each organization is brought to bear in the most effective manner and each organization is brought to bear in the most effective manner
in collaboration with the other. This document provides guidelines and in collaboration with the other. This document provides
for collaboration between the ITU-T and the IETF. guidelines for collaboration between the ITU-T and the IETF.
3. Guidance on Collaboration 3. Guidance on Collaboration
This section builds on existing collaborative processes and details This section builds on existing collaborative processes and details
some of the more important guidance points that each organization some of the more important guidance points that each organization
should be aware of for effective collaboration. should be aware of for effective collaboration.
3.1. How to Interact on ITU-T or IETF Work Items 3.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-
related should evaluate the relationship with topics defined in related should evaluate the relationship with topics defined in
the IETF. Current IETF Working Groups and their charters (IETF the IETF. Current IETF Working Groups and their charters (IETF
definition of the scope of work) are listed in the IETF archives definition of the scope of work) are listed in the IETF archives
(see section 3.5). (see section 3.5).
A Study Group may decide that development of a Recommendation on A study group may decide that development of a Recommendation on
a particular topic may benefit from collaboration with the IETF. a particular topic may benefit from collaboration with the IETF.
The Study Group should identify this collaboration in its work The study group should identify this collaboration in its work
plan (specifically in that of each Question involved), plan (specifically in that of each Question involved),
describing the goal of the collaboration and its expected describing the goal of the collaboration and its expected
outcome. outcome.
An IETF Working Group should also evaluate and identify areas of An IETF Working Group should also evaluate and identify areas of
relationship with the ITU-T and document the collaboration with relationship with the ITU-T and document the collaboration with
the ITU-T Study Group in its charter. The following sections the ITU-T study group in its charter. The following sections
outline a process that can be used to enable each group to be outline a process that can be used to enable each group to be
informed about the other's new work items. informed about the other's new work items.
3.1.1. How the ITU-T is informed about Existing IETF Work Items 3.1.1. How the ITU-T is informed about Existing IETF Work Items
The responsibility is on individual Study Groups to review the The responsibility is on individual study groups to review the
current IETF Working Groups to determine if there are any topics of current IETF Working Groups to determine if there are any topics of
mutual interest. Should a Study Group believe that there is an mutual interest. Should a study group believe that there is an
opportunity for collaboration on a topic of mutual interest, it opportunity for collaboration on a topic of mutual interest, it
should contact both the IETF Working Group Chair and the Area should contact both the IETF Working Group Chair and the Area
Director(s) responsible. This may be accompanied by a formal liaison Director(s) responsible. This may be accompanied by a formal liaison
statement (see 3.2.4. ). statement (see 3.2.4).
3.1.2. How the ITU-T is informed about proposed new IETF work items 3.1.2. How the ITU-T is informed about proposed new IETF work items
The IETF maintains a mailing list for the distribution of proposed The IETF maintains a mailing list for the distribution of proposed
new work items among standards development organizations. Many such new work items among standards development organizations. Many such
items can be identified in proposed Birds of a Feather (BoF) items can be identified in proposed Birds of a Feather (BoF)
sessions, as well as draft charters for working groups. The IETF sessions, as well as draft charters for working groups. The IETF
forwards all such draft charters for all new and revised Working forwards all such draft charters for all new and revised Working
Groups and Birds Of a Feather session announcements to the IETF Groups and Birds Of a Feather session announcements to the IETF
NewWork mailing list. An ITU-T mail mailing list is subscribed to NewWork mailing list. An ITU-T mailing list is subscribed to this
this list. Leadership of Study Groups may subscribe to this ITU-T list. Leadership of study groups may subscribe to this ITU-T mailing
mailing list, which is maintained by the TSB. Members of the SG- list, which is maintained by the TSB. Members of the SG-specific
specific listname may include the SG Chairman, SG Vice Chairmen, listname may include the SG chairman, SG vice-chairmen, working
Working Party Chairmen, concerned Rapporteurs, other experts party chairmen, concerned rapporteurs, other experts designated by
designated by the SG and the SG Counselor. This will enable the SGs the SG and the SG Counselor. This will enable the SGs to monitor
to monitor the new work items for possible overlap or interest to the new work items for possible overlap or interest to their study
their Study Group. It is expected that this mailing list will see a group. It is expected that this mailing list will see a few
few messages per month. 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 is two weeks. As a result, the mailing list
should be consistently monitored. should be consistently monitored.
3.1.3. How the IETF is informed about ITU-T Work Items 3.1.3. How the IETF is informed about ITU-T Work Items
The ITU-T accepts new areas of work through the creation or update of The ITU-T accepts new areas of work through the creation or update
Questions. In addition, the ITU-T work programme is documented in of Questions. In addition, the ITU-T work programme is documented
the Questions of each Study Group. These can be found on the ITU-T in the Questions of each study group. These can be found on the
web site. ITU-T web site.
Study Groups should send updates to the IETF NewWork mailing list as study groups should send updates to the IETF NewWork mailing list as
new Questions are created, terms of reference for Questions are new Questions are created, terms of reference for Questions are
updated, or otherwise when there is reason to believe that a updated, or otherwise when there is reason to believe that a
particular effort might be of interest to the IETF. Area Directors particular effort might be of interest to the IETF. Area Directors
or WG Chairs should provide comments through liaison statements or or WG Chairs should provide comments through liaison statements or
direct email to the relevant SG Chairman in cases of possible overlap direct email to the relevant SG chairman in cases of possible
or interest. overlap or interest.
3.2. Representation 3.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 3.2.1). Conversely, ITU-T 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 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 of the ITU-T (see 3.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.
3.2.1. IETF Recognition at ITU-T 3.2.1. 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 may participate in ITU-T meetings as ISOC delegates. The leadership may participate in ITU-T meetings as ISOC delegates. The
ISOC focal point will facilitate registration and verification of ISOC focal point will facilitate registration and verification of
these people, as appropriate. these people, as appropriate.
3.2.2. ITU-T Recognition at ISOC/IETF 3.2.2. 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 other working group are given equal weight with opinions expressed by other working
participants. group participants.
3.2.3. Communication Contacts 3.2.3. Communication Contacts
To foster ongoing communication between the ITU-T and IETF, it is To foster ongoing communication between the ITU-T and IETF, it is
important to identify and establish contact points within each important to identify and establish contact points within each
organization. Contact points may include: organization. Contact points may include:
1. ITU-T Study Group Chairman and IETF Area Director 1. ITU-T Study Group and IETF Area Director
An IETF Area Director is the individual responsible for An IETF Area Director is the individual responsible for
overseeing a major focus of activity with a scope similar to overseeing a major focus of activity with a scope similar to
that of an ITU-T Study Group Chairman. These positions are that of an ITU-T study group chairman. These positions are
both relatively long-term (of several years) and offer the both relatively long-term (of several years) and offer the
stability of contact points between the two organizations for stability of contact points between the two organizations for
a given topic. a given topic.
2. ITU-T Rapporteur and IETF Working Group Chair 2. ITU-T Rapporteur and IETF Working Group Chair
An IETF Working Group Chair is an individual who is assigned An IETF Working Group Chair is an individual who is assigned
to lead the work on a specific task within one particular Area to lead the work on a specific task within one particular Area
with a scope similar to that of an ITU-T Rapporteur. These with a scope similar to that of an ITU-T rapporteur. These
positions are working positions (of a year or more) that positions are working positions (of a year or more) that
typically end when the work on a specific topic ends. typically end when the work on a specific topic ends.
Collaboration here is very beneficial to ensure the actual Collaboration here is very beneficial to ensure the actual
work gets done. work gets done.
3. Other Contact Points 3. Other Contact Points
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. the same individual.
Note that the current IETF Area Directors and Working Group Note that the current IETF Area Directors and Working Group
Chairs can be found in the IETF Working Group charters. The Chairs can be found in the IETF Working Group charters. The
current ITU-T Study Group Chairmen and Rapporteurs are listed on current ITU-T study group chairmen and rapporteurs are listed on
the ITU-T web page. the ITU-T web page.
3.2.4. Communication 3.2.4. Communication
Informal communication between contact points and experts of both Informal communication between contact points and experts of both
organizations is encouraged. However, note that formal communication organizations is encouraged. However, note that formal
from an ITU-T Study Group, Working Party or Rapporteur to an communication from an ITU-T study group, working party or rapporteur
associated IETF contact point must be explicitly approved and group to an associated IETF contact point must be explicitly
identified as coming from the Study Group, Working Party or approved and identified as coming from the study group, working
Rapporteur Group, respectively. Formal liaison statements from the party or rapporteur group, respectively. Formal liaison statements
ITU-T to the IETF are transmitted according to the procedures from the ITU-T to the IETF are transmitted according to the
described in [2]. These liaison statements are placed by the IETF procedures described in [2]. These liaison statements are placed by
onto a liaison statements web page at the IETF onto a liaison statements web page at
https://datatracker.ietf.org/liaison/. An individual at the IETF is https://datatracker.ietf.org/liaison/. An individual at the IETF is
assigned responsibility for dealing with each liaison statement that assigned responsibility for dealing with each liaison statement that
is received. The name and contact information of the responsible is received. The name and contact information of the responsible
person and any applicable deadline is listed with the links to the person and any applicable deadline is listed with the links to the
liaison statement on this web page. liaison statement on this web page.
Formal liaison statements from the IAB, the IETF, an IETF Working Formal liaison statements from the IAB, the IETF, an IETF Working
Group or or Area to the ITU-T are generated, approved, and Group or or Area to the ITU-T are generated, approved, and
transmitted according to the procedures described in [2]. Formal transmitted according to the procedures described in [2]. Formal
communication is intended to allow the sharing of positions between communication is intended to allow the sharing of positions between
the IETF and the ITU-T outside of actual documents (as described in the IETF and the ITU-T outside of actual documents (as described in
3.3). This covers such things as comments on documents and requests 3.3). This covers such things as comments on documents and requests
for input. for input.
3.2.5. Mailing Lists 3.2.5. Mailing Lists
All IETF Working Groups and all ITU-T Study Group Questions have All IETF Working Groups and all ITU-T study group Questions have
associated mailing lists. associated mailing lists.
In the IETF, the mailing list is the primary vehicle for discussion In the IETF, the mailing list is the primary vehicle for discussion
and decision-making. It is recommended that the ITU-T experts and decision-making. It is recommended that the ITU-T experts
interested in particular IETF Working Group topics subscribe to and interested in particular IETF Working Group topics subscribe to and
participate in these lists. IETF WG mailing lists are open to all participate in these lists. IETF WG mailing lists are open to all
subscribers. The IETF Working Group mailing list subscription and subscribers. The IETF Working Group mailing list subscription and
archive information are noted in each Working Group's charter. In archive information are noted in each Working Group's charter. In
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 can Working Parties and other topics within study groups (more detail
be found on the ITU website). These mailing lists are typically used can be found on the ITU website). These mailing lists are typically
for ITU-T correspondence, including technical discussion, meeting used for ITU-T correspondence, including technical discussion,
logistics, reports, etc. Note that individual subscribers to this meeting logistics, reports, etc. Note that individual subscribers
list must be affiliated with an ITU-T member or associate (at this to this list must be affiliated with an ITU-T member or associate
time, there is no blanket inclusion of all IETF participants as (at this time, there is no blanket inclusion of all IETF
members, however, as a member, the ISOC focal point can facilitate participants as members, however, as a member, the ISOC focal point
access by IETF technical experts, liaison representatives, or liaison can facilitate access by IETF technical experts, liaison
managers). Any IETF participant may subscribe to ITU-T focus group representatives, or liaison managers). Any IETF participant may
email lists. subscribe to ITU-T focus group email lists.
3.3. Document Sharing 3.3. 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 can groups. Initially proposed concepts and specifications typically
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 ITU- including the details of the specification) on both the IETF and
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 the Recommendations, Internet-Drafts or RFCs may also be sent between
organizations as described below. the organizations as described below.
Internet-Drafts are available on the IETF web site. The ITU-T can Internet-Drafts are available on the IETF web site. The ITU-T can
make selected ITU-T documents at any stage of development available make selected ITU-T documents at any stage of development available
to IETF by attaching them to a formal liaison statement. Although a to IETF by attaching them to a formal liaison statement. Although a
communication can point to a URL where a non-ASCII document (e.g., communication can point to a URL where a non-ASCII document (e.g.,
Word) can be downloaded, attachments in proprietary formats to an Word) can be downloaded, attachments in proprietary formats to an
IETF mailing list are discouraged. It should also be recognized that IETF mailing list are discouraged. It should also be recognized
the official version of all IETF documents are in ASCII. that the official version of all IETF documents are in ASCII.
3.3.1. IETF to ITU-T 3.3.1. IETF to ITU-T
IETF documents (e.g., Internet-Drafts) or URLs of those documents are IETF documents (e.g., Internet-Drafts) or URLs of those documents
most commonly transmitted to ITU-T Study Groups as liaison statements are most commonly transmitted to ITU-T study groups as liaison
(see [2]), but exceptionally can be submitted to a Study Group as a statements (see [2]), but exceptionally can be submitted to a study
Contribution from ISOC. In order to ensure that the IETF has group as a Contribution from ISOC. In order to ensure that the IETF
properly authorized this, the IETF Working Group must agree that the has properly authorized this, the IETF Working Group must agree that
specific drafts are of mutual interest, that there is a benefit in the specific drafts are of mutual interest, that there is a benefit
forwarding them to the ITU-T for review, comment and potential use in forwarding them to the ITU-T for review, comment and potential
and that the document status is accurately represented in the cover use and that the document status is accurately represented in the
letter. Once agreed, the appropriate Area Directors would review the cover letter. Once agreed, the appropriate Area Directors would
Working Group request and give approval. The contributions would review the Working Group request and give approval. The rules of
then be forwarded (with the noted approval) to the TSB for the IETF Trust are followed in these circumstances[3]. The
circulation as a Study Group Contribution (see 3.2.4). The rules of contributions would then be forwarded (with the noted approval) to
the IETF Trust are followed in these circumstances[RFC5378]. the TSB for circulation as a study group Contribution (see 3.2.4).
Note that material submitted to the ITU-T as an ISOC contribution is
governed by ITU-T intellectual property rules for contributions. Any
such contribution will be made only after receiving necessary
approval of owners of the work in question. In other circumstances,
a liaison statement may be appropriate. See RFC5378 and
Recommendation ITU-T A.1 for more information.
3.3.2. ITU-T to IETF 3.3.2. ITU-T to IETF
A Study Group or Working Party may send texts of draft new or revised A study group or Working Party may send texts of draft new or
Recommendations, clearly indicating their status, to the IETF as revised Recommendations, clearly indicating their status, to the
contributions in the form of liaison statements or Internet Drafts. IETF as contributions in the form of liaison statements or Internet-
Internet Drafts are IETF temporary documents that expire six months Drafts. Internet-Drafts are IETF temporary documents that expire
after being published. The Study Group or Working Party must decide six months after being published. The study group or Working Party
that there is a benefit in forwarding them to the IETF for review, must decide that there is a benefit in forwarding them to the IETF
comment and potential use. Terms of reference for Rapporteur Group for review, comment and potential use. Terms of reference for
meetings may authorize Rapporteur Groups to send working documents, rapporteur group meetings may authorize rapporteur groups to send
in the form of Internet Drafts, to the IETF. working documents, in the form of Internet-Drafts, to the IETF.
If the Study Group or Working Party elects to transmit the text as an If the study group or working party elects to transmit the text as
Internet-Draft, the document editor would be instructed to prepare an Internet-Draft, the document editor would be instructed to
the contribution in Internet Draft format (in ASCII and optionally prepare the contribution in Internet-Draft format (in ASCII and
postscript format as per [RFC2223]) and upload it via optionally postscript format as per [9]) and upload it via
https://datatracker.ietf.org/idst/upload.cgi. Alternatively, the https://datatracker.ietf.org/idst/upload.cgi. Material submitted as
Study Group, Working Party or Rapporteur Group could attach the text an Internet-Draft or intended for inclusion in an Internet-Draft or
to a formal liaison statement. RFC is governed by the rules set forth in RFCs 5378, 3979, and 4879.
[3,4,5] Alternatively, the study group, Working Party or rapporteur
group could attach the text to a formal liaison statement.
Both the Rapporteur and the Document Editor should be identified as Both the rapporteur and the Document Editor should be identified as
contacts in the contribution. The document should also clearly contacts in the contribution. The document should also clearly
indicate the state of development in a particular ITU-T Study Group. indicate the state of development in a particular ITU-T study group.
Note that liaison statements are made publicly available on the IETF Note that liaison statements and their attachments sent to the IETF
web site. are made publicly available on the IETF web site.
3.3.3. ITU-T & IETF 3.3.3. ITU-T & IETF
It is envisaged that the processes of 3.3.1 & 3.3.2 will often be It is envisaged that the processes of 3.3.1 & 3.3.2 will often be
used simultaneously by both an IETF Working Group and an ITU-T Study used simultaneously by both an IETF Working Group and an ITU-T study
Group to collaborate on a topic of mutual interest. group to collaborate on a topic of mutual interest.
It is also envisaged that the outcome of the collaboration will be It is also envisaged that the outcome of the collaboration will be
the documentation in full by one body and its referencing by the the documentation in full by one body and its referencing by the
other (see section 3.4 for details). That is, common or joint text other (see section 3.4 for details). That is, common or joint text
is discouraged because of the current differences in procedures for is discouraged because of the current differences in procedures for
document approval and revision. Where complementary work is being document approval and revision. Where complementary work is being
undertaken in both organizations that will result in Recommendations undertaken in both organizations that will result in Recommendations
or RFCs, due allowance should be given to the differing perspectives, or RFCs, due allowance should be given to the differing
working methods, and procedures of the two organizations. That is, perspectives, working methods, and procedures of the two
each organization should understand the other organization's organizations. That is, each organization should understand the
procedures and strive to respect them in the collaboration. other organization's procedures and strive to respect them in the
collaboration.
3.4. Simple Cross Referencing 3.4. Simple Cross Referencing
ITU-T Recommendation A.5 describes the process for including Recommendation ITU-T A.5 describes the process for including
references to documents of other organizations in ITU-T references to documents of other organizations in ITU-T
Recommendations. Information specific to referencing IETF RFCs is Recommendations. Information specific to referencing IETF RFCs is
found at http://www.itu.int/dms_pub/itu- found at http:// itu.int/dms_pub/itu-
t/oth/3E/01/T3E010000010001MSWE.doc. t/oth/3E/01/T3E010000010001MSWE.doc.
IETF RFC2026, specifically section 7.1.1, describes the process for RFC 2026, specifically section 7.1.1, describes the process for
referencing other open standards (like ITU-T Recommendations) in IETF referencing other open standards (like ITU-T Recommendations) in
RFCs. IETF RFCs.
3.5. Preliminary Work Efforts 3.5. Preliminary Work Efforts
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 a potential new work areas prior to the official start of work in a
Study Group or creation of an IETF working group. 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 described in ITU-T Recommendation 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 the division of groups are frequently created in new work areas where the division
work across various ITU-T Study Groups and other standards of work across various ITU-T study groups and other standards
development organizations is not yet clear. IETF participants who are development organizations is not yet clear. IETF participants who
not members or associates of ITU-T may participate fully in the work are not members or associates of ITU-T may participate fully in the
of ITU-T focus groups. work of ITU-T focus groups.
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 RFC5434. 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. These sessions group stage may be discussed in BOF sessions. 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.
3.6. Additional Items 3.6. Additional Items
3.6.1. Useful Information to ITU-T participations on the IETF 3.6.1. IETF Information that may be of use to ITU-T participations
Information on IETF procedures may be found in the documents and URLs
below. Note that RFCs do not change after they are published.
Rather they are either obsoleted or updated by other RFCs. Such
updates are tracked in the rfc-index.txt file indicated below.
RFC 2028 - The Organizations involved in the IETF Standards Process,
October 1996.
The Tao of the IETF - A Novice's Guide to the Internet Engineering
Task Force, http://www.ietf.org/tao.html.
RFC 3935 - A Mission Statement for the IETF, October 2004
RFC2026 - The Internet Standards Process Revision 3, October 1996
http://www.ietf.org/rfc/rfc2026.txt
RFC2418 - IETF Working Group Guidelines and Procedures, September
1998
http://www.ietf.org/rfc/rfc2418.txt
RFC5434 - Considerations for Having a Successful Birds-of-a-Feather Information on IETF procedures may be found in the documents in the
(BOF) Session, February 2009 informative references, and URLs below. Note that RFCs do not
http://www.rfc-editor.org/rfc/rfc5434.txt change after they are published. Rather they are either obsoleted
or updated by other RFCs. Such updates are tracked in the rfc-
index.txt file.
Current list and status of all IETF RFCs: Current list and status of all IETF RFCs:
ftp://ftp.ietf.org/rfc/rfc-index.txt ftp://ftp.ietf.org/rfc/rfc-index.txt
Current list and description of all IETF Internet Drafts: Current list and description of all IETF Internet-Drafts:
ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt
Current list of IETF Working Groups and their Charters: (includes Current list of IETF Working Groups and their Charters: (includes
Area Directors and Chair contacts, Mailing list information, etc.) Area Directors and Chair contacts, Mailing list information, etc.)
http://www.ietf.org/dyn/wg/charter.html http://www.ietf.org/dyn/wg/charter.html
Current list of registered BOFs Current list of registered BOFs
http://trac.tools.ietf.org/bof/trac/ http://trac.tools.ietf.org/bof/trac/
RFC Editor pages about publishing RFCs, including available tools and RFC Editor pages about publishing RFCs, including available tools
lots of guidance: and lots of guidance:
http://www.rfc-editor.org/pubprocess.html http://www.rfc-editor.org/pubprocess.html
Current list of liaison statements: Current list of liaison statements:
https://datatracker.ietf.org/liaison/ https://datatracker.ietf.org/liaison/
IETF Intellectual Property Rights Policy and Notices: IETF Intellectual Property Rights Policy and Notices:
http://www.ietf.org/ipr/ http://www.ietf.org/ipr/
3.6.2. Current ITU-T information can be found on the ITU website: The Tao of the IETF - A Novice's Guide to the Internet Engineering
(includes contacts, organization, Recommendations for purchase, Task Force, http://www.ietf.org/tao.html
mailing list info, etc.)
ITU-T Main page: http://www.itu.int/ITU-T 3.6.2. ITU-T Information that may be useful to IETF participants
Information about the ITU-T can be found in the informative
references and at the URLs below.
ITU-T Main page: http://itu.int/ITU-T
List of all ITU-T Recommendations: List of all ITU-T Recommendations:
http://www.itu.int/itu-t/recommendations/index.aspx http://itu.int/itu-t/recommendations/index.aspx
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://www.itu.int/ITU-T/studygroups/comNN/index.asp http://itu.int/ITU-T/studygroups/comNN/index.asp
Intellectual Property policies, forms and databases: Intellectual Property policies, forms and databases:
http://www.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://www.itu.int/en/ITU-T/focusgroups/Pages/default.aspx http://itu.int/en/ITU-T/focusgroups/Pages/default.aspx
ITU-T operational matters including:
Recommendation A.1 - Study Group work methods
Recommendation A.2 - Preparation of written contributions
Recommendation A.4 - Communication process between ITU-T and
forums and consortia
Recommendation A.5 - Include reference to documents of other
organizations in ITU-T Recs
Recommendation A.7 - Focus groups: Working methods and procedures
Recommendation A.8 - Alternative Approval Process for
Recommendations
http://www.itu.int/itu-t/recommendations/index.aspx?ser=A
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
http://www.itu.int/publ/T-RES/en http://itu.int/publ/T-RES/en
Authors Guide for drafting ITU-T Recommendations: Authors Guide for drafting ITU-T Recommendations:
http://www.itu.int/dms_pub/itu- http://itu.int/dms_pub/itu-t/oth/0A/0F/T0A0F0000040003MSWE.docx
t/oth/0A/0F/T0A0F0000040003MSWE.docxh
Templates for contributions and liaison statements: Templates for contributions and liaison statements:
http://www.itu.int/ITU-T/studygroups/templates/index.html http://itu.int/ITU-T/studygroups/templates/index.html
4. Security Considerations 4. Security Considerations
Documents that describe cooperation procedures, like this one Documents that describe cooperation procedures, like this one
does, have no direct Internet security implications. does, have no direct Internet security implications.
5. IANA Considerations 5. IANA Considerations
No new IANA considerations. No new IANA considerations.
6. References 6. Acknowledgements
6.1. Normative References This document is based on the text from RFCs 2436 and 3356 and
benefited greatly from discussions during the January 2012 ITU-T
Telecommunication Standardization Advisory Group (TSAG) meeting.
7. References
7.1. Normative References
[1] Daigle, L, Ed. "IAB Processes for Management of IETF Liaison [1] Daigle, L, Ed. "IAB Processes for Management of IETF Liaison
Relationships", RFC 4052, BCP 102, April 2005. Relationships", RFC 4052, BCP 102, April 2005.
[2] Trowbridge, S, Bradner, S, and Baker, F, "Procedures for [2] Trowbridge, S, Bradner, S, and Baker, F, "Procedures for
Handling Liaison Statements to and from the IETF", RFC4053, BCP Handling Liaison Statements to and from the IETF", RFC 4053,
103, April 2005. BCP 103, April 2005.
6.2. Informative References [3] Bradner, J. Ed., Contreras, J., Ed., "Rights Contributors
Provide to the IETF Trust", RFC-5378, BCP 78, November, 2008.
[3] Bradner. S, "The Internet Standards Process -- Revision 3", BCP [4] Bradner, S., Ed., "Intellectual Property Rights in IETF
9, RFC 2026, October 1996. Technology", RFC 3979, BCP 79, March 2005.
[4] Postel, J. and J. Reynolds, "Instructions to RFC Authors", RFC [5] Narten, T., "Clarifications of the Third Party Disclosure
Procedure in RFC 4879", BCP 79, April 2007.
[6] International Telecommunications Union, "Communication process
between ITU-T and Forums and Consortia", Recommendation ITU-T
A.4, 2008.
[7] International Telecommunications Union, "Generic procedures
for including references to documents of other organizations
in ITU-T Recommendations", Recommendation ITU-T A.5, 2008.
7.2. Informative References
[8] Bradner. S, "The Internet Standards Process -- Revision 3",
BCP 9, RFC 2026, October 1996.
[9] Postel, J. and J. Reynolds, "Instructions to RFC Authors", RFC
2223, October 1997. 2223, October 1997.
[5] Brett, R., Bradner, S. and G. Parsons, "Collaboration between [10] Brett, R., Bradner, S. and G. Parsons, "Collaboration between
ISOC/IETF and ITU-T", RFC 2436, October 1998. ISOC/IETF and ITU-T", RFC 2436, October 1998.
[6] Fishman, G and Bradner, S, "Internet Engineering Task Force and [11] Fishman, G. and Bradner, S., "Internet Engineering Task Force
International Telecommunication Union - Telecommunications and International Telecommunication Union - Telecommunications
Standardization Sector Collaboration Guidelines", RFC 3356, Standardization Sector Collaboration Guidelines", RFC 3356,
August 2002. August 2002.
7. Acknowledgements [12] Hovey, R., Bradner, S., "The Organizations involved in the
IETF Standards Process, October 1996", RFC 2028, October,
1996.
This document is based on the text from RFCs 2436 and 3356 and [13] Bradner, S., "IETF Working Group Guidelines and Procedures",
benefited greatly from discussions during the January 2012 ITU-T TSAG RFC-2418, September 1998.
meeting.
[14] Narten, T., "Considerations for Having a Successful Birds-of-
a-Feather (BOF) Session", RFC-5434, February 2009.
[15] Alvestrand, H., "A Mission Statement for the IETF", BCP-95
(also RFC-3935), October 2004.
[16] International Telecommunications Union, "Work Methods for
study groups of the ITU Telecommunications Standard Sector
(ITU-T)", Recommendation ITU-T A.1, 2008.
[17] International Telecommunications Union, "Presentation of
Contributions to the ITU-T", Recommendation ITU-T A.2, 2008.
[18] International Telecommunications Union, "Focus groups: Working
methods and procedures", Recommendation ITU-T A.7, 2008.
[19] International Telecommunications Union, "Alternative approval
process for new and revised ITU-T Recommendations",
Recommendation ITU-T A.8, 2008.
8. Changes since RFC3356 8. Changes since RFC3356
Authorization of liaison managers and liaison representatives from Authorization of liaison managers and liaison representatives from
IETF to ITU-T are updated per current IETF procedures documented in IETF to ITU-T are updated per current IETF procedures documented in
[1]. [1].
Transmission of formal liaison statements between ITU-T and IETF are Transmission of formal liaison statements between ITU-T and IETF are
updated per current IETF procedures documented in [2]. updated per current IETF procedures documented in [2].
skipping to change at page 15, line 9 skipping to change at page 15, line 25
groups and IETF BOFs. ITU-T focus group participation is not limited groups and IETF BOFs. ITU-T focus group participation is not limited
to ITU-T members. to ITU-T members.
Obsolete URLs in RFC3356 from both the ITU-T and IETF web sites are Obsolete URLs in RFC3356 from both the ITU-T and IETF web sites are
updated. updated.
9. Authors' Addresses 9. Authors' Addresses
Steve Trowbridge Steve Trowbridge
Alcatel-Lucent Alcatel-Lucent
5280 Centennial Trail
Boulder, CO 80303-1262 USA
Phone: +1 720 945 6885
Email: steve.trowbridge@alcatel-lucent.com Email: steve.trowbridge@alcatel-lucent.com
Eliot Lear Eliot Lear
Cisco Systems GmbH Cisco Systems GmbH
Richtistrasse 7 Richtistrasse 7
8304 Wallisellen 8304 Wallisellen
Switzerland Switzerland
Phone: +41 44 878 9200 Phone: +41 44 878 9200
Email: lear@cisco.com Email: lear@cisco.com
Scott Bradner
Harvard University
29 Oxford St.
Cambridge, MA 02138
Phone: +1 617 495 3864
Email: sob@harvard.edu
 End of changes. 80 change blocks. 
224 lines changed or deleted 249 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/