rfc3356.txt

RFC 的详细文档！


RFC 3356        IETF and ITU-T Collaboration Guidelines      August 2002


3.3 Document Sharing

   During the course of ITU-T and IETF collaboration it is important to
   share working drafts and documents among the technical working
   groups.  Initially proposed concepts and specifications typically can
   be circulated by email (often just repeating the concept and not
   including the details of the specification) on both the IETF and
   ITU-T mailing lists.  In addition, working texts (or URLs) of draft
   Recommendations, Internet Drafts or RFCs may also be sent between the
   organizations as described below.

   Internet Drafts are available on the IETF web site.  The ITU-T can
   make selected ITU-T documents available in a common FTP area on the
   ITU-T web site.  Although a communication can point to a URL where a
   non-ASCII document (e.g., Word) can be downloaded, Word attachments
   to an IETF mailing list are discouraged.  It should also be
   recognized that the official version of all IETF documents are in
   ASCII.

3.3.1 IETF to ITU-T

   IETF documents (e.g., Internet Drafts) can be submitted to a Study
   Group as a Contribution from ISOC.  In order to ensure that the IETF
   has properly authorized this, the IETF Working Group must agree that
   the specific drafts are of mutual interest, that there is a benefit
   in forwarding them to the ITU-T for review, comment and potential use
   and that the document status is accurately represented in the cover
   letter.  Once agreed, the appropriate Area Directors would review the
   Working Group request and give approval.  The contributions would
   then be forwarded (with the noted approval) to the TSB for
   circulation as a Study Group Contribution (see 3.2.4).

3.3.2 ITU-T to IETF

   A Study Group or Working Party may send texts of draft new or revised
   Recommendations, clearly indicating their status, to the IETF as
   contributions in the form of Internet Drafts.  Internet Drafts are
   IETF temporary documents that expire six months after being
   published.  The Study Group or Working Party must decide that there
   is a benefit in forwarding them to the IETF for review, comment and
   potential use.  Terms of reference for Rapporteur Group meetings may
   authorize Rapporteur Groups to send working documents, in the form of
   Internet Drafts, to the IETF.

   In these cases, the document editor would be instructed to prepare
   the contribution in Internet Draft format (in ASCII and optionally
   postscript format as per [RFC2223]) and submit it to the Internet
   Draft editor (email [e-mail]).  Alternatively, the



Fishman                      Informational                      [Page 7]

RFC 3356        IETF and ITU-T Collaboration Guidelines      August 2002


   Study Group, Working Party or Rapporteur Group could agree to post
   the document on a web site and merely document its existence with a
   short Internet Draft that contains a summary and the document URL.
   The URL can point to a Word document as long as it is publicly
   available and with the understanding that it will not be eligible for
   publication as an RFC in that format.

   Both the Rapporteur and the Document Editor should be identified as
   contacts in the contribution.  The contribution must also clearly
   indicate that the Internet Draft is a working document of a
   particular ITU-T Study Group.

3.3.3 ITU-T & IETF

   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
   Group to collaborate on a topic of mutual interest.

   It is also envisaged that the outcome of the collaboration will be
   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
   is discouraged because of the current differences in procedures for
   document approval and revision.  Where complementary work is being
   undertaken in both organizations that will result in Recommendations
   or RFCs, due allowance should be given to the differing perspectives,
   working methods, and procedures of the two organizations.  That is,
   each organization should understand the other organization's
   procedures and strive to respect them in the collaboration.

3.4 Simple Cross Referencing

   ITU-T Recommendation A.5 describes the process for including
   references to documents of other organizations in ITU-T
   Recommendations.  Information specific to referencing IETF RFCs is
   found at http://www.itu.int/itudoc/itu-t/sdo/ref-a.5/isocietf.html.

   IETF RFC2026, specifically section 7.1.1, describes the process for
   referencing other open standards (like ITU-T Recommendations) in IETF
   RFCs.

3.5  Additional Items

3.5.1 Several URLs to IETF procedures are provided here for information:

   RFC2223  - Instructions to RFC Authors, October 1997
      http://www.ietf.org/rfc/rfc2223.txt





Fishman                      Informational                      [Page 8]

RFC 3356        IETF and ITU-T Collaboration Guidelines      August 2002


   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

   Current list and status of all IETF RFCs:
      ftp://ftp.ietf.org/rfc/rfc-index.txt

   Current list and description of all IETF Internet Drafts:
      ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt

   Current list of IETF Working Groups and their Charters: (includes
      Area Directors and Chair contacts, Mailing list information, etc.)
      http://www.ietf.org/html.charters/wg-dir.html

   RFC Editor pages about publishing RFCs:
      http://www.rfc-editor.org/howtopub.html

   Current list of liaison statements:
      http://www.ietf.org/IESG/liaison.html

   IETF Intellectual Property Rights Notices:
      http://www.ietf.org/ipr.html

3.5.2 Current ITU-T information can be found on the ITU website:
      (includes contacts, organization, Recommendations for purchase,
      mailing list info, etc.)

   ITU-T Main page: http://www.itu.int/ITU-T

   List of all ITU-T Recommendations:
      http://www.itu.int/publibase/itu-t/

   ITU-T Study Group main page for Study Group NN (where NN is the
      2-digit SG number):
      http://www.itu.int/ITU-T/studygroups/comNN/index.html

   ITU-T Special Study Group on IMT-2000 and beyond:
      http://www.itu.int/ITU-T/studygroups/ssg/index.html

   Intellectual Property policies, forms and databases:
      http://www.itu.int/ITU-T/dbase/patent/index.html








Fishman                      Informational                      [Page 9]

RFC 3356        IETF and ITU-T Collaboration Guidelines      August 2002


   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.8 - Alternative Approval Process for
      Recommendations: http://www.itu.int/itudoc/itu-t/rec/A

   ITU T Procedures including:
      Resolution 1 - Rules of Procedure for ITU-T
      Resolution 2 - Study Group responsibility and mandates
      http://www.itu.int/itudoc/itu-t/wtsa-res/index.html

   Authors Guide for drafting ITU-T Recommendations:
      http://www.itu.int/itudoc/itu-t/guide/64657.html

   Templates for contributions:
      http://www.itu.int/itudoc/itu-t/com2/template/w2000tem/index.html

4. Security Considerations

   Documents that describe cooperation procedures, like this one does,
   have no direct Internet security implications.

5. Non-normative references

   [RFC2026] Bradner. S, " The Internet Standards Process -- Revision
             3", BCP 9, RFC 2026, October 1996.

   [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors",
             RFC 2223, October 1997.

   [RFC2436] Brett, R., Bradner, S. and G. Parsons, "Collaboration
             between ISOC/IETF and ITU-T", RFC 2436, October 1998.

6. Acknowledgements

   This document is based on the text from RFC 2436 and benefited
   greatly from discussions during the November 2001 ITU-T TSAG meeting.

7. Changes since RFC 2436

   The wording has been cleaned up in a number of places, a few
   additional references have been provided, and the details of the
   cooperation process have been modified slightly.




Fishman                      Informational                     [Page 10]

RFC 3356        IETF and ITU-T Collaboration Guidelines      August 2002


   Sec 3.2.1 - Registration for IETF representatives to ITU-T meetings
      is now done by IAB Chair instead of the ISOC VP for Standards.
   Sec 3.2.2 - Notice of ITU-T delegates to IETF Working Group meetings
      is now sent to the Working Group chairs and appropriate Area
      Directors instead of the ISOC VP for Standards.
   Sec 3.2.4 - Official communications from the ITU-T to the IETF now
      are sent to the appropriate Working Group Chairs and Area
      Directors with a copy to the email address "[e-mail]"
      instead of to the ISOC VP for Standards.  A description of the new
      IETF liaison statements web page was added.  Official approval of
      messages from the IETF to the ITU-T is now indicated by having the
      appropriate Working Group Chairs and Area Directors copied on the
      message.
   Sec 3.3 - A description of the new ITU-T common FTP area was added.
   Sec 3.3.1 - The appropriate Area Directors now review documents to be
      sent to the ITU-T instead of the ISOC VP for Standards.
   Annex A was removed as unneeded.

8. Author's addresses

   Gary Fishman
   Bell Laboratories
   101 Crawfords Corner Road
   Room 4D-605B
   Holmdel, NJ 07733-3030
   USA
   [phone]
   EMail: [e-mail]


   Scott Bradner
   Harvard University
   29 Oxford St.
   Cambridge MA 02138
   USA
   [phone]
   EMail: [e-mail]














Fishman                      Informational                     [Page 11]

RFC 3356        IETF and ITU-T Collaboration Guidelines      August 2002


9.  Full Copyright Statement

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Fishman                      Informational                     [Page 12]