idnits 2.17.1 draft-3gpp-collaboration-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 224 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. ** There are 23 instances of lines with control characters in the document. == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 7 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft K. Rosenbrock 2 15 November 2000 3GPP PCG Chair 3 Expires: May 2001 R. Sanmugam 4 Ericsson 5 S. Bradner 6 Harvard University 7 J. Klensin 8 AT&T 9 3GPP-IETF Standardization Collaboration 10 draft-3gpp-collaboration-00.txt 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with all 15 provisions of Section 10 of RFC2026 [1]. 16 This memo provides information for the Internet community. Distribution 17 of this memo is unlimited. 19 Internet-Drafts are working documents of the Internet Engineering Task 20 Force (IETF), its areas, and its working groups. Note that other groups 21 may also distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet- Drafts as reference material 25 or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 1. Abstract 35 This document describes the standardization collaboration between 36 3GPP and IETF. 38 2. Conventions used in this document 40 This document uses significant terminology that is specialized to IETF, 41 3GPP, or their areas of work. See appendix A for definitions of 42 acronyms. The organizational definitions can be found in their 43 respective web-sites. 45 3. Introduction 47 This document contains a set of principles and guidelines that serves 48 as the basis for establishing the collaboration between 3GPP and IETF, 49 with the objective of securing timely development of technical 50 specification that facilitate maximum interoperability with existing 51 (fixed and mobile) Internet systems, devices, and protocols. 53 Each organization will operate according to their own rules and 54 procedures including rules governing IPR policy, specification 55 elaboration, approval and maintenance. 57 4. Reasons For Collaboration 59 4.1 3GPP use of IETF Internet Standards 61 In the further development of 3GPP specifications, the benefit of 62 adopting Internet specifications has been identified. 64 The preferred 3GPP approach is to use the Internet standards unchanged, 65 if feasible. In any case, 3GPP has no intention to duplicate work 66 performed in IETF. 68 However, while this document recognizes the importance of 3GPP 69 interoperability with the existing Internet and hence the use of IETF 70 standards, 3GPP recognizes that additions or modifications might be 71 needed in order to make the IETF internet specification fulfil the 72 needs of 3GPP. 4.2 IETF access to 3GPP Wireless expertise 74 The technical work in 3GPP is organized in Technical Specification 75 Groups TSGs each with their area of responsibilities. TSG-RAN and 76 TSG-GERAN are responsible for the Radio Access networks based on UTRAN 77 and GERAN and thus the experts in the areas of the characteristics of 78 the physical transport. TSG CN is responsible for the Mobility 79 Management and other core network protocol and functionalities. TSG-T 80 is responsible for Terminal aspects and applications. TSG-SA is 81 responsible for the service and system aspects including the overall 82 architecture, security and O&M aspects. Contacts for the TSGs can be 83 found on the 3GPP web-site www.3gpp.org. 85 5. Document Sharing 87 Both 3GPP and IETF encourage the sharing of draft documents that are of 88 mutual interest. 90 3GPP documents are available on its official web-site 91 (http://WWW.3GPP.ORG/) and is open to anyone. IETF documents, including 92 preliminary working documents ("Internet Drafts") are available on its 93 web-site (http://www.ietf.org/ and various shadow sites. 95 IETF representatives can obtain information about the 3GPP document and 96 web-site structures by contacting the relevant 3GPP contact points 97 indicated at the 3GPP web-site www.3gpp.org. 99 3GPP representatives can obtain information about the IETF document and 100 web-site structures by contacting the relevant IETF contact points ? 101 the Area Directors indicated at the IETF web- site www.ietf.org . 103 6. Communication 105 Whenever possible, informal communication at working level is 106 encouraged. The vast majority of the technical discussions and 107 decision making in both IETF and 3GPP is done over mailing lists. Both 108 3GPP and IETF web sites contain information concerning the associated 109 mailing lists. 111 It is recommended that interested individuals subscribe to and 112 participate in these lists. 114 When deemed necessary, formal communication between 3GPP and IETF is 115 also permitted. Relevant IETF Area Directors and 3GPP technical 116 leadership are encouraged and authorized to facilitate such 117 communications when needed. 119 7. Rapporteurs/coordinators 121 7.1 IETF coordination support in 3GPP 123 An IETF rapporteur function is established in 3GPP TSG-SA. 125 The individual(s) appointed to undertake the responsibility of this 126 function should be the initial contact point in 3GPP for matters 127 pertaining to the 3GPP-IETF cooperation. Of course, the chairman of 128 TSG-SA can always be contacted. 130 The 3GPP-IETF rapporteur function, therefore, is expected to work with 131 the concerned working groups and TSGs and support the interaction 132 between 3GPP and IETF. 134 7.2 3GPP Liaison in IETF 136 The preferred way for organizations to work with IETF is through the 137 working groups. However, IETF has a limited number of liaison 138 relationships with other organizations when conditions warrant the 139 appointment of a specific person. 141 The appointment of a specific person in IESG to function as a "3GPP 142 liaison" is proposed. 144 The role of the 3GPP Liaison is to act as an initial contact point in 145 IETF for administrative aspects of this collaboration that cannot 146 easily be handled in other ways (e.g., at a technical 147 level by interactions with IETF Working Groups or Area Directors). It 148 is agreed that the role does not carry the expectation of attendance at 149 3GPP meetings or participation in 3GPP administrative processes and 150 anticipated that all liaison efforts assigned to this individual will 151 be carried out by electronic mail. It is understood that the liaison 152 will not have the ability to make exceptions to, or special provisions 153 for, IETF policies and procedures. 155 8. Participation 157 In order to assist the information flow between the organizations, IETF 158 can on per case basis appoint a rapporteur to participate and represent 159 IETF at 3GPP technical meetings. 161 IETF meetings are open to any interested individuals. 163 3GPP partners (OPs, MRPs) or individual members can participate in any 164 of the IETF meetings, in accordance with the existing IETF procedures. 166 9. Security Considerations 167 This type of non-protocol document does not directly affect the security 168 of the Internet. 169 10. References 171 [1] Bradner, S., "The Internet Standards Process -- Revision 3", 172 BCP 9, RFC 2026, October 1996. 174 11. Authors' Addresses 176 Karl Heinz Rosenbrock 177 ETSI 178 06921 Sophia Antipolis 179 CEDEX Phone: +33 492 94 4212 180 France Email: rosenbrock@etsi.fr 182 Appendix A: Acronyms 184 Glossary Of Acronyms: 186 3GPP Third Generation Partnership Project 187 BCP Best Current Practice 188 IAB Internet Architecture Board 189 IESG Internet Engineering Steering Group 190 IETF Internet Engineering Task Force 191 IPR Intellectual Property rights 192 MRP Market Representation Partner 193 OP Organizational Partner 194 O&M Operation and Maintenance 195 PCG Project coordination Group 196 RFC Request for Comments 198 TSG Technical Specification Group 199 TSG-SA TSG Services and systems aspects 200 TSG-CN TSG Core Network 201 TSG-RAN TSG Radio Access Network 202 TSG-GERAN TSG GSM Radio Access Network 203 TSG-T TSG Terminals 204 UTRAN Universal Terrestrial Radio Access Network 205 WWW World Wide Web