RFC 3131 on 3GPP2-IETF Standardization Collaboration

RFC Editor <rfc-ed@ISI.EDU> Thu, 28 June 2001 16:31 UTC

Message-Id: <200106281618.f5SGIbG14757@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3131 on 3GPP2-IETF Standardization Collaboration
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 28 Jun 2001 09:18:36 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 3131

        Title:	    3GPP2-IETF Standardization Collaboration
        Author(s):  S. Bradner, P. Calhoun, H. Cuschieri, S. Dennett,
                    G. Flynn, M. Lipford, M. McPheters
        Status:     Informational
	Date:       June 2001
        Mailbox:    sob@harvard.edu, pcalhoun@eng.sun.com,
                    hcuschie@tia.eia.org, S.Dennett@motorola.com,
                    gerry.flynn@verizonwireless.com,
                    Mlipfo01@sprintspectrum.com,
                    mjmcpheters@lucent.com  
        Pages:      8
        Characters: 13643
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-bradner-3gpp2-collaboration-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3131.txt


This document describes the standardization collaboration between
3GPP2 and IETF.

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 Sandy Ginoza
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.

ftp://ftp.isi.edu/in-notes/rfc3131.txt"><ftp://ftp.isi.edu/in-notes/rfc3131.txt>

RFC 3131 on 3GPP2-IETF Standardization Collaborat… RFC Editor