RFC 2436 on ISOC/IETF - ITU-T Collaboration
RFC Editor <rfc-ed@ISI.EDU> Thu, 15 October 1998 23:05 UTC
Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id TAA26000 for ietf-123-outbound.10@ietf.org; Thu, 15 Oct 1998 19:05:03 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA25548 for <all-ietf@ietf.org>; Thu, 15 Oct 1998 18:44:18 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id PAA20670; Thu, 15 Oct 1998 15:44:19 -0700 (PDT)
Message-Id: <199810152244.PAA20670@tnt.isi.edu>
To: IETF-Announce:;
Subject: RFC 2436 on ISOC/IETF - ITU-T Collaboration
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 15 Oct 1998 15:44:19 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2436: Title: Collaboration between ISOC/IETF and ITU-T Author(s): R. Brett, S. Bradner, G. Parsons Status: Informational Date: October 1998 Mailbox: rfbrett@nortel.ca, sob@harvard.edu, Glenn.Parsons@Nortel.ca Pages: 14 Characters: 31154 Updates/Obsoletes/See Also: None I-D Tag: draft-itu-isoc-00.txt URL: ftp://ftp.isi.edu/in-notes/rfc2436.This This document describes the collaboration process between the ITU-T and ISOC/IETF. The process was documented by ITU-T at its TSAG (Telecommunication Standardization Advisory Group) meeting in September 1998. All participants of this meeting (including Study Group chairmen and the ISOC Vice President for Standards) assisted in the creation of this document. Subsequently, it was sent to all ITU-T Study Groups and ISOC/IETF to ensure that everyone was aware of the process. Feedback is requested by the next meeting of TSAG in April 1999. This document is identical to the document produced by TSAG. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Alegre Ramos USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 2436 on ISOC/IETF - ITU-T Collaboration RFC Editor