draft-iab-rfc3356bis-02.txt   draft-iab-rfc3356bis-03.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 4, 2012 Expires: December 4, 2012 June 11, 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-02 draft-iab-rfc3356bis-03
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 20 skipping to change at page 3, line 20
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. IETF Recognition at ITU-T............................7
Experts and representatives from the IETF that are chosen by Experts and representatives from the IETF that are chosen by
IETF leadership may participate in ITU-T meetings as ISOC IETF leadership normally participate in ITU-T meetings as ISOC
delegates. The ISOC focal point will facilitate registration delegates. The ISOC focal point will facilitate registration
and verification of these people, as appropriate............7 and verification of these people, as appropriate............7
2.2.2. ITU-T Recognition at ISOC/IETF.......................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 Liaisons from the IETF to ITU-T....9 2.5.1. Contributions and Liaison Statements from the IETF to
2.5.2. Conributions and liaisons form the ITU-T to IETF....10 ITU-T.......................................................9
2.5.2. Contributions and Liaison Statements from the ITU-T to
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
2.8. Additional Items.........................................11 2.8. Additional Items.........................................11
2.8.1. IETF Information that may be of use to ITU-T 2.8.1. IETF Information that may be of use to ITU-T
participations.............................................11 participations.............................................11
2.8.2. ITU-T Information that may be useful to IETF 2.8.2. ITU-T Information that may be useful to IETF
participants...............................................12 participants...............................................12
3. Security Considerations.......................................13 3. Security Considerations.......................................13
4. IANA Considerations...........................................13 4. IANA Considerations...........................................13
skipping to change at page 4, line 22 skipping to change at page 4, line 22
1. Introduction & Scope 1. Introduction & 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 International collaboration on standards development between the International
Telecommunication Union - Telecommunication Standardization Sector Telecommunication Union - Telecommunication Standardization Sector
(ITU-T) and the Internet Society (ISOC) -- Internet Engineering Task (ITU-T) and the Internet Society (ISOC) -- Internet Engineering Task
Force (IETF). Early identification of topics of mutual interest Force (IETF). Early identification of topics of mutual interest
will allow for constructive efforts between the two organizations. will allow for constructive efforts between the two organizations.
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
generally grouped within Working Parties (WPs) led by a WP 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 (SG)
a SG chairman. Work may also be conducted in ITU-T focus groups led by a SG chairman. Work may also be conducted in ITU-T focus
(see Section 2.5) groups (see Section 2.5)
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 Chair and IETF Area Director 1. ITU-T Study Group Chair 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. 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 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.
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-
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 2.8.1). (see Section 2.8.1).
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 ITU-T study group in its charter.
The following sections outline a process that can be used to The following sections outline a process that can be used to
enable each group to be informed about the other's new work enable each group to be informed about the other's new work
items. items.
2.1.1. How the ITU-T is informed about Existing IETF Work Items 2.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. Working group charters and active Internet-Drafts
opportunity for collaboration on a topic of mutual interest, it can be found on the IETF web site (http://datatracker.ietf.org/wg/).
should contact both the IETF Working Group Chair and the Area If a study group identifies a common area of work, the study group
Director(s) responsible. This may be accompanied by a formal liaison leadership should contact both the IETF working group chair and the
statement (see 3.2.4). area director(s) responsible. This may be accompanied by a formal
liaison statement (see 2.3).
2.1.2. How the IETF is informed about Existing ITU-T Work Items 2.1.2. How the IETF is informed about Existing ITU-T Work Items
The IETF through its representatives will review current work of The IETF through its representatives will review current work of
various study groups from time to time. Each ITU-T study group's various study groups from time to time. Each ITU-T study group's
web pages on the ITU-T web site contain its current list of web pages on the ITU-T web site contain its current list of
Questions as well as its current work programme. When a common area Questions as well as its current work programme. When an area or
of work is identified, the matter is referred to appropriate Working working group identifies a common area of work, the matter is
Group chairs and Area Directors, where they may consider sending a referred to appropriate working group chairs and area directors,
liaison statement to the appropriate study group. where they may consider sending a liaison statement to the
appropriate study group.
2.1.3. How the ITU-T is informed about proposed new IETF work items 2.1.3. 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 new-
NewWork mailing list. An ITU-T mailing list is subscribed to this work mailing list. An ITU-T mailing list is subscribed to this
list. Leadership of study groups may subscribe to this ITU-T mailing list. Leadership of study groups may subscribe to this ITU-T mailing
list, which is maintained by the Telecommunication Standardization list, which is maintained by the Telecommunication Standardization
Bureau (TSB). Members of the SG-specific listname may include the Bureau (TSB). Members of the SG-specific listname may include the
SG chairman, SG vice-chairmen, working party chairmen, concerned SG chairman, SG vice-chairmen, working party chairmen, concerned
rapporteurs, other experts designated by the SG and the SG rapporteurs, other experts designated by the SG and the SG
Counsellor. This will enable the SGs to monitor the new work items Counsellor. This will enable the SGs to monitor the new work items
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 is two weeks. As a result, the mailing list
should be consistently monitored. 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 should send updates to the IETF NewWork mailing list as Study groups send updates to the IETF new-work mailing list as new
new Questions are contemplated or created, terms of reference for Questions are first drafted or created, terms of reference for
Questions are contemplated or updated, or otherwise when there is Questions are first drafted or updated, or otherwise when there is
reason to believe that a particular effort might be of interest to reason to believe that a particular effort might be of interest to
the IETF. Area Directors or WG Chairs should provide comments the IETF. Area directors or WG chairs should provide comments
through liaison statements or direct email to the relevant SG through liaison statements or direct email to the relevant SG
chairman in cases of possible overlap or interest. chairman in cases of possible overlap or interest.
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
skipping to change at page 7, line 43 skipping to change at page 7, line 45
2.2.1. IETF Recognition at ITU-T 2.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 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.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 any other working are given equal weight with opinions expressed by any other working
group participant. group participant.
2.3. Communication outside of Meetings 2.3. Communication outside of Meetings
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 organizations is encouraged. However, note that formal
communication from an ITU-T study group, working party or rapporteur communication from an ITU-T study group, working party or rapporteur
group to an associated IETF contact point must be explicitly group to an associated IETF contact point must be explicitly
skipping to change at page 8, line 24 skipping to change at page 8, line 26
party or rapporteur group, respectively. Formal liaison statements party or rapporteur group, respectively. Formal liaison statements
from the ITU-T to the IETF are transmitted according to the from the ITU-T to the IETF are transmitted according to the
procedures described in [2]. These liaison statements are placed by procedures described in [2]. These liaison statements are placed by
the IETF 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 IESG, the IETF, an IETF
Group or Area to the ITU-T are generated, approved, and transmitted working group or Area to the ITU-T are generated, approved, and
according to the procedures described in [2] and [15]. Formal transmitted according to the procedures described in [2] and [15].
communication is intended to allow the sharing of positions between Formal communication is intended to allow the sharing of positions
the IETF and the ITU-T outside of actual documents (as described in between the IETF and the ITU-T outside of actual documents (as
2.5.1). This covers such things as comments on documents and described in 2.5.1). This covers such things as comments on
requests for input. documents and requests for input.
2.4. Mailing Lists 2.4. 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 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
skipping to change at page 9, line 25 skipping to change at page 9, line 27
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
the 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 IETF mailing list are discouraged. It should also be recognized
that the official version of all IETF documents are in ASCII. that the official versions of all IETF documents are in ASCII.
2.5.1. Contributions and Liaison Statements from the IETF to ITU-T 2.5.1. Contributions and Liaison Statements from the IETF to ITU-T
IETF documents (e.g., Internet-Drafts) or URLs of those documents IETF documents (e.g., Internet-Drafts) or URLs of those documents
are most commonly transmitted to ITU-T study groups as liaison are most commonly transmitted to ITU-T study groups as liaison
statements (see [2]), but exceptionally can be submitted to a study statements (see [2]), but exceptionally can be submitted to a study
group as a Contribution from ISOC. In order to ensure that the IETF group as a Contribution from ISOC. In order to ensure that the IETF
has properly authorized this, the IETF Working Group must agree that has properly authorized this, the IETF working group must agree that
the specific drafts are of mutual interest, that there is a benefit the specific drafts are of mutual interest, that there is a benefit
in forwarding them to the ITU-T for review, comment and potential in forwarding them to the ITU-T for review, comment and potential
use and that the document status is accurately represented in the use and that the document status is accurately represented in the
cover letter. Once agreed, the appropriate Area Directors would cover letter. Once agreed, the appropriate area directors would
review the Working Group request and give approval. The rules of review the working group request and give approval. The rules of
the IETF Trust are followed in these circumstances[3]. The the IETF Trust are followed in these circumstances[3]. The
contributions would then be forwarded (with the noted approval) to contributions would then be forwarded (with the noted approval) to
the TSB for circulation as a study group Contribution (see 2.2). the TSB for circulation as a study group Contribution (see 2.2).
Note that material submitted to the ITU-T as an ISOC Contribution is Note that material submitted to the ITU-T as an ISOC Contribution is
governed by Section 3.1.5 of Recommendation ITU-T A.1. Any such governed by Section 3.1.5 of Recommendation ITU-T A.1. Any such
contribution will be made only after receiving necessary approval of contribution will be made only after receiving necessary approval of
owners of the work in question. In other circumstances, a liaison owners of the work in question. In other circumstances, a liaison
statement may be appropriate. See RFC5378 and Recommendation ITU-T statement may be appropriate. See RFC 5378 and Recommendation ITU-T
A.1 for more information. A.1 for more information.[3, 15]
2.5.2. Contributions and Liaison Statements from the ITU-T to IETF 2.5.2. Contributions and Liaison Statements from the ITU-T to IETF
An ITU-T study group or working party may send texts of draft new or An ITU-T study group or working party may send texts of draft new or
revised Recommendations, clearly indicating their status, to the revised Recommendations, clearly indicating their status, to the
IETF as contributions in the form of liaison statements or Internet- IETF as contributions in the form of liaison statements or Internet-
Drafts. Internet-Drafts are IETF temporary documents that expire Drafts. Internet-Drafts are IETF temporary documents that expire
six months after being published. The study group or working party six months after being published. The study group or working party
must decide that there is a benefit in forwarding them to the IETF must decide that there is a benefit in forwarding them to the IETF
for review, comment and potential use. Terms of reference for for review, comment and potential use. Terms of reference for
rapporteur group meetings may authorize rapporteur groups to send rapporteur group meetings may authorize rapporteur groups to send
working documents, 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 If the study group or working party elects to transmit the text as
an Internet-Draft, the document editor would be instructed to an Internet-Draft, the document editor would be instructed to
prepare the contribution in Internet-Draft format (in ASCII and prepare the contribution in Internet-Draft format (in ASCII and
optionally postscript format as per [8]) and upload it via optionally postscript format as per [8]) and upload it via
https://datatracker.ietf.org/idst/upload.cgi. Material submitted as https://datatracker.ietf.org/idst/upload.cgi. Material submitted as
an Internet-Draft or intended for inclusion in an Internet-Draft or an Internet-Draft or intended for inclusion in an Internet-Draft or
RFC is governed by the rules set forth in RFCs 5378, 3979, and 4879. 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 [4,5] Alternatively, the study group, working party or rapporteur
group could attach the text to a formal liaison statement. 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 and their attachments sent to the IETF Note that liaison statements and their attachments sent to the IETF
are made publicly available on the IETF web site. are made publicly available on the IETF web site.
2.5.3. ITU-T & IETF 2.5.3. ITU-T & IETF
It is envisaged that the processes of 2.5.1 & 2.5.2 will often be It is envisaged that the processes of 2.5.1 & 2.5.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 2.4 for details). That is, common or joint text other (see section 2.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 or RFCs, due allowance should be given to the differing
perspectives, working methods, and procedures of the two perspectives, working methods, and procedures of the two
organizations. That is, each organization should understand the organizations. That is, each organization should understand the
other organization's procedures and strive to respect them in the other organization's procedures and strive to respect them in the
collaboration. collaboration.
2.6. Simple Cross Referencing 2.6. Simple Cross Referencing
Recommendation ITU-T 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. Recommendation ITU-T A.5 also addresses the sit uation where a study group Recommendations. Recommendation ITU-T A.5 also addresses the
or working party decides to incorporate the text of another organization into the text of a situation where a study group or working party decides to
Recommendation, rather than referencing it . Information specific to referencing incorporate the text of another organization into the text of a
IETF RFCs is found at http:// itu.int/dms_pub/itu- Recommendation, rather than referencing it. Information specific to
t/oth/3E/01/T3E010000010001MSWE.doc. referencing IETF RFCs is found at http://itu.int/ITU-T/go/ref-ietf-
isoc.
RFC 2026, specifically section 6.1.1, describes the process for RFC 2026 Section 6.1.1, describes the process for referencing other
referencing other open standards (like ITU-T Recommendations) in open standards (like ITU-T Recommendations) in IETF RFCs.[7]
IETF RFCs.
2.7. Preliminary Work Efforts 2.7. 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 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 from a country that is a member of 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. 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
Information on IETF procedures may be found in the documents in the Information on IETF procedures may be found in the documents in the
informative references, and URLs below. Note that RFCs do not informative references, and URLs below. Note that RFCs do not
change after they are published. Rather they are either obsoleted change after they are published. Rather they are either obsoleted
or updated by other RFCs. Such updates are tracked in the rfc- or updated by other RFCs. Such updates are tracked in the rfc-
index.txt file. 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 RFC Editor pages about publishing RFCs, including available tools
and 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:
skipping to change at page 13, line 6 skipping to change at page 13, line 6
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
http://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://itu.int/dms_pub/itu-t/oth/0A/0F/T0A0F0000040003MSWE.docx http://itu.int/ITU-T/go/author-guide
Templates for contributions and liaison statements: Templates for contributions and liaison statements:
http://itu.int/ITU-T/studygroups/templates/index.html http://itu.int/ITU-T/studygroups/templates/index.html
3. Security Considerations 3. 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.
4. IANA Considerations 4. IANA Considerations
skipping to change at page 13, line 38 skipping to change at page 13, line 38
6.1. Normative References 6.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", RFC 4053, Handling Liaison Statements to and from the IETF", RFC 4053,
BCP 103, April 2005. BCP 103, April 2005.
[3] Bradner, J. Ed., Contreras, J., Ed., "Rights Contributors [3] Bradner, J. Ed., Contreras, J., Ed., "Rights Contributors
Provide to the IETF Trust", RFC-5378, BCP 78, November, 2008. Provide to the IETF Trust", RFC 5378, BCP 78, November, 2008.
[4] Bradner, S., Ed., "Intellectual Property Rights in IETF [4] Bradner, S., Ed., "Intellectual Property Rights in IETF
Technology", RFC 3979, BCP 79, March 2005. Technology", RFC 3979, BCP 79, March 2005.
[5] Narten, T., "Clarifications of the Third Party Disclosure [5] Narten, T., "Clarifications of the Third Party Disclosure
Procedure in RFC 4879", BCP 79, April 2007. Procedure in RFC 4879", BCP 79, April 2007.
[6] International Telecommunication Union, "Generic procedures for [6] International Telecommunication Union, "Generic procedures for
including references to documents of other organizations in including references to documents of other organizations in
ITU-T Recommendations", Recommendation ITU-T A.5, 2008. ITU-T Recommendations", Recommendation ITU-T A.5, 2008.
skipping to change at page 14, line 29 skipping to change at page 14, line 29
August 2002. August 2002.
[11] Hovey, R., Bradner, S., "The Organizations involved in the [11] Hovey, R., Bradner, S., "The Organizations involved in the
IETF Standards Process, October 1996", RFC 2028, October, IETF Standards Process, October 1996", RFC 2028, October,
1996. 1996.
[12] Bradner, S., "IETF Working Group Guidelines and Procedures", [12] Bradner, S., "IETF Working Group Guidelines and Procedures",
RFC-2418, September 1998. RFC-2418, September 1998.
[13] Narten, T., "Considerations for Having a Successful Birds-of- [13] Narten, T., "Considerations for Having a Successful Birds-of-
a-Feather (BOF) Session", RFC-5434, February 2009. a-Feather (BOF) Session", RFC 5434, February 2009.
[14] Alvestrand, H., "A Mission Statement for the IETF", BCP-95 [14] Alvestrand, H., "A Mission Statement for the IETF", BCP 95
(also RFC-3935), October 2004. (also RFC 3935), October 2004.
[15] International Telecommunications Union, "Work Methods for [15] International Telecommunications Union, "Work Methods for
study groups of the ITU Telecommunication Standardization study groups of the ITU Telecommunication Standardization
Sector (ITU-T)", Recommendation ITU-T A.1, 2008. Sector (ITU-T)", Recommendation ITU-T A.1, 2008.
[16] International Telecommunications Union, "Presentation of [16] International Telecommunications Union, "Presentation of
Contributions to the ITU-T", Recommendation ITU-T A.2, 2008. Contributions to the ITU-T", Recommendation ITU-T A.2, 2008.
[17] International Telecommunications Union, "Focus groups: Working [17] International Telecommunications Union, "Focus groups: Working
methods and procedures", Recommendation ITU-T A.7, 2008. methods and procedures", Recommendation ITU-T A.7, 2008.
 End of changes. 41 change blocks. 
80 lines changed or deleted 84 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/