idnits 2.17.1 draft-fishman-2436bis-02.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3356 5 Title: Internet Engineering Task Force and International 6 Telecommunication Union - Telecommunications 7 Standardization Sector Collaboration Guidelines 8 Author(s): G. Fishman, S. Bradner 9 Status: Informational 10 Date: August 2002 11 Mailbox: garyfishman@lucent.com, sob@Harvard.edu 12 Pages: 12 13 Characters: 27068 14 Obsoletes: 2436 16 I-D Tag: draft-fishman-2436bis-02.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3356.txt 20 This document provides guidance to aid in the understanding of 21 collaboration on standards development between the International 22 Telecommunication Union -- Telecommunication Standardization Sector 23 (ITU-T) and the Internet Society (ISOC) / Internet Engineering Task 24 Force (IETF). It is an update of and obsoletes RFC 2436. The 25 updates reflect changes in the IETF and ITU-T since RFC 2436 was 26 written. The bulk of this document is common text with ITU-T 27 Supplement 3 to the ITU-T A-Series Recommendations. 29 Note: This was approved by ITU-T TSAG on 30 November 2001 as a 30 Supplement to the ITU-T A-Series of Recommendations (will be numbered 31 as A-Series Supplement 3). 33 This memo provides information for the Internet community. It does 34 not specify an Internet standard of any kind. Distribution of this 35 memo is unlimited. 37 This announcement is sent to the IETF list and the RFC-DIST list. 38 Requests to be added to or deleted from the IETF distribution list 39 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 40 added to or deleted from the RFC-DIST distribution list should 41 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 43 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 44 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 45 help: ways_to_get_rfcs. For example: 47 To: rfc-info@RFC-EDITOR.ORG 48 Subject: getting rfcs 50 help: ways_to_get_rfcs 52 Requests for special distribution should be addressed to either the 53 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 54 specifically noted otherwise on the RFC itself, all RFCs are for 55 unlimited distribution.echo 56 Submissions for Requests for Comments should be sent to 57 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 58 Authors, for further information.