Skip to main content

3GPP2-IETF Standardization Collaboration
RFC 3131

Document Type RFC - Informational (June 2001)
Authors Scott O. Bradner , Mike McPheters , Gerry Flynn , Pat R. Calhoun , Henry Cuschieri , Steve Dennett , Mark Lipford
Last updated 2013-03-02
RFC stream Legacy stream
Formats
IESG Responsible AD (None)
Send notices to (None)
RFC 3131
Network Working Group                                         S. Bradner
Request for Comments: 3131                            Harvard University
Category: Informational                                       P. Calhoun
                                                  Sun Microsystems, Inc.
                                                            H. Cuschieri
                                                                     TIA
                                                              S. Dennett
                                                                Motorola
                                                                G. Flynn
                                                        Verizon Wireless
                                                              M. Lipford
                                                              Sprint PCS
                                                            M. McPheters
                                                     Lucent Technologies
                                                               June 2001

                3GPP2-IETF Standardization Collaboration

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

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

Abstract

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

1. Conventions used in this document

   This document uses significant terminology that is specialized to
   IETF, 3GPP2, or their areas of work.  See appendix A for definitions
   of acronyms.  The organizational definitions can be found in their
   respective web-sites.

2. Introduction

   This document contains a set of principles and guidelines that serves
   as the basis for establishing the collaboration between 3GPP2 and
   IETF, with the objective of securing timely development of technical
   specification that facilitate maximum interoperability with existing
   (fixed and mobile) Internet systems, devices, and protocols.

Bradner, et al.              Informational                      [Page 1]
RFC 3131        3GPP2-IETF Standardization Collaboration       June 2001

   Each organization will operate according to their own rules and
   procedures including rules governing IPR policy, specification
   elaboration, approval and maintenance.

3. Reasons For Collaboration

3.1 3GPP2 use of IETF Internet Standards

   In the further development of 3GPP2 specifications, the benefit of
   adopting Internet specifications has been identified.

   The preferred 3GPP2 approach is to use the Internet standards
   unchanged, if feasible.  In any case, 3GPP2 has no intention to
   duplicate work performed in IETF.

   However, while this document recognizes the importance of 3GPP2
   interoperability with the existing Internet and hence the use of IETF
   standards, 3GPP2 recognizes that additions or modifications might be
   needed in order to make the IETF internet specification fulfill the
   needs of 3GPP2.  In such cases, 3GPP2 will take its concerns directly
   to the appropriate IETF working groups for resolution, or to an
   appropriate Area Director if no appropriate working group can be
   found.

3.2 IETF access to 3GPP2 Wireless expertise

   The technical work in 3GPP2 is organized in Technical Specification
   Groups TSGs each with their area of responsibilities.  TSG-A and
   TSG-C are responsible for the Radio Access networks based on CDMA and
   thus the experts in the areas of the characteristics of the physical
   transport.  TSG-N is responsible for the Mobility Management and
   other core network protocol and functionalities.  TSG-P is
   responsible for data services and applications.  TSG-S is responsible
   for the service and system aspects including the overall
   architecture, security and O&M aspects.  Contacts for the TSGs can be
   found on the 3GPP2 web-site www.3gpp2.org.

4. Document Sharing

   Both 3GPP2 and IETF encourage the sharing of draft documents that are
   of mutual interest.

   3GPP2 working documents are available on its official web-site, and
   are grouped according to the meeting.  These documents can be found
   on the 3GPP2 ftp server, which is open to anyone, at
   ftp://ftp.3gpp2.org.  3GPP2 specifications, those that have completed
   the 15-day Steering Committee review, can be found at:

Bradner, et al.              Informational                      [Page 2]
RFC 3131        3GPP2-IETF Standardization Collaboration       June 2001

      http://www.3gpp2.org/Public_html/Specs/index.cfm

   IETF documents, including preliminary working documents ("Internet
   Drafts") are available on its web-site (http://www.ietf.org/) and
   various shadow sites.

   IETF representatives can obtain information about the 3GPP2 document
   and web-site structures by contacting the relevant 3GPP2 contact
   points indicated at the 3GPP2 web-site (www.3gpp2.org).

   3GPP2 representatives can obtain information about the IETF document
   and web-site structures by contacting the relevant IETF contact
   points, which are the Area Directors indicated at the IETF web-site
   (www.ietf.org).

5. Communication

   Whenever possible, informal communication at working level is
   encouraged.

   The vast majority of the technical discussions and decision making at
   IETF is done over mailing lists.  It is recommended that interested
   individuals subscribe to and participate in these lists.

   3GPP2 mailing lists, however, are not open to the general public.  It
   is recommended that work of mutual interest be discussed on the
   relevant IETF mailing lists.

   When deemed necessary, formal communication between 3GPP2 and IETF is
   also permitted.  Relevant IETF Area Directors and 3GPP2 technical
   leadership are encouraged and authorized to facilitate such
   communications when needed.

6. Rapporteurs/coordinators

6.1 IETF coordination support in 3GPP2

   An IETF rapporteur function is established in 3GPP2 Steering
   Committee.

   The individual(s) appointed to undertake the responsibility of this
   function should be the initial contact point in 3GPP2 for matters
   pertaining to the 3GPP2-IETF cooperation.  Of course, the chairman of
   Steering Committee can always be contacted.

   The 3GPP2-IETF rapporteur function, therefore, is expected to work
   with the concerned working groups and TSGs and support the
   interaction between 3GPP2 and IETF.

Bradner, et al.              Informational                      [Page 3]
RFC 3131        3GPP2-IETF Standardization Collaboration       June 2001

6.2 3GPP2 Liaison in IETF

   The preferred way for organizations to work with IETF is through the
   working groups.  However, IETF has a limited number of liaison
   relationships with other organizations when conditions warrant the
   appointment of a specific person.

   The appointment of a specific person in IESG to function as a "3GPP2
   liaison" is proposed.

   The role of the 3GPP2 Liaison is to act as an initial contact point
   in IETF for administrative aspects of this collaboration that cannot
   easily be handled in other ways (e.g., at a technical level by
   interactions with IETF Working Groups or Area Directors).  It is
   agreed that the role does not carry the expectation of attendance at
   3GPP2 meetings or participation in 3GPP2 administrative processes and
   anticipated that all liaison efforts assigned to this individual will
   be carried out by electronic mail.  It is understood that the liaison
   will not have the ability to make exceptions to, or special
   provisions for, IETF policies and procedures.

7. Participation

   In order to assist the information flow between the organizations,
   IETF can on a per case basis appoint an observer to participate and
   represent IETF at 3GPP2 technical meetings.

   IETF meetings are open to any interested individuals.

   3GPP2 partners (OPs, MRPs) or individual members can participate in
   any of the IETF meetings, in accordance with the existing IETF
   procedures.

   3GPP2 meetings are also open to any interested individual, however
   such individuals do not have voting privileges.  The meeting schedule
   can be found on the 3GPP2 web site.

8. Security Considerations

   This type of non-protocol document does not directly affect the
   security of the Internet.

9. Acknowldegement

   This memo took guidance from and borrowed text from RFC 3113.[4]

Bradner, et al.              Informational                      [Page 4]
RFC 3131        3GPP2-IETF Standardization Collaboration       June 2001

10. References

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

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

   [3] Bradner, S., "IETF Working Group Guidelines and Procedures", BCP
       25, RFC 2418, September 1998.

   [4] Rosenbrock, K., Sanmugam, R., Bradner, S. and J. Klensin, "3GPP-
       IETF Standardization Collaboration", RFC 3113, June 2001.

10. Authors' Addresses

   Scott O. Bradner
   Harvard University
   Holyoke Center, Room 813
   1350 Mass. Ave.
   Cambridge, MA  02138
   USA

   Phone: +1 617-495-3864
   EMail: sob@harvard.edu

   Pat R. Calhoun
   Network and Security Research Center, Sun Laboratories
   Sun Microsystems, Inc.
   15 Network Circle
   Menlo Park, California, 94025
   USA

   Phone: +1 650-786-7733
   Fax:   +1 650-786-6445
   EMail: pcalhoun@eng.sun.com

   Henry Cuschieri
   TIA
   2500 Wilson Boulevard
   Arlington, VA 22201

   Phone: +1 703-907-7497
   Fax:   +1 703-907-7728
   EMail: hcuschie@tia.eia.org

Bradner, et al.              Informational                      [Page 5]
RFC 3131        3GPP2-IETF Standardization Collaboration       June 2001

   Steve Dennett
   Motorola/3GPP2 Chair
   1900 W. Winchester Road
   Libertyville, IL 60048

   Phone: +1 847-523-6868
   Fax:   +1 847-523-0375
   EMail: S.Dennett@motorola.com

   Gerry Flynn
   Verizon Wireless
   180 Washington Valley Road
   Bedminster, NJ  07921

   Phone: +1 908-306-4154
   Fax:   +1 908-306-7731
   EMail: gerry.flynn@verizonwireless.com

   Mark Lipford
   Sprint PCS
   15405 College Boulevard
   Lenexa, KS 66219

   Phone: +1 913-890-4248
   Fax +1 913-890-4291
   Email: Mlipfo01@sprintspectrum.com

   Mike McPheters
   Lucent Technologies
   263 Shuman Blvd
   Naperville, IL  60566

   Phone: +1 630-713-4182
   Fax:   +1 630-713-4182
   EMail: mjmcpheters@lucent.com

Bradner, et al.              Informational                      [Page 6]
RFC 3131        3GPP2-IETF Standardization Collaboration       June 2001

Appendix A:  Acronyms

Glossary Of Acronyms:

   3GPP2           Third Generation Partnership Project 2
   BCP             Best Current Practice
   CDMA            Code Division Multiple Access
   IAB             Internet Architecture Board
   IESG            Internet Engineering Steering Group
   IETF            Internet Engineering Task Force
   IPR             Intellectual Property rights
   OP              Organizational Partner
   O&M             Operation and Maintenance
   RFC             Request for Comments
   SC              3GPP2 Steering Committee
   TSG             Technical Specification Group
   TSG-A           TSG A-Interface System
   TSG-C           TSG CDMA2000 Air Interface
   TSG-P           TSG Wireless Packet Data Interworking
   TSG-N           TSG ANSI-41/WIN
   TSG-S           TSG Service And System Aspects
   WWW             World Wide Web

Bradner, et al.              Informational                      [Page 7]
RFC 3131        3GPP2-IETF Standardization Collaboration       June 2001

Full Copyright Statement

   Copyright (C) The Internet Society (2001).  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.

Bradner, et al.              Informational                      [Page 8]