idnits 2.17.1 draft-ietf-v6ops-3gpp-cases-03.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 3574 5 Title: Transition Scenarios for 3GPP Networks 6 Author(s): J. Soininen, Ed. 7 Status: Informational 8 Date: August 2003 9 Mailbox: jonne.soininen@nokia.com 10 Pages: 12 11 Characters: 23359 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-ietf-v6ops-3gpp-cases-03.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3574.txt 18 This document describes different scenarios in Third Generation 19 Partnership Project (3GPP) defined packet network, i.e., General 20 Packet Radio Service (GPRS) that would need IP version 6 and IP 21 version 4 transition. The focus of this document is on the scenarios 22 where the User Equipment (UE) connects to nodes in other networks, 23 e.g., in the Internet. GPRS network internal transition scenarios, 24 i.e., between different GPRS elements in the network, are out of 25 scope. The purpose of the document is to list the scenarios for 26 further discussion and study. 28 This document is a product of the IPv6 Operations Working Group of the 29 IETF. 31 This memo provides information for the Internet community. It does 32 not specify an Internet standard of any kind. Distribution of this 33 memo is unlimited. 35 This announcement is sent to the IETF list and the RFC-DIST list. 36 Requests to be added to or deleted from the IETF distribution list 37 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 38 added to or deleted from the RFC-DIST distribution list should 39 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 41 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 42 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 43 help: ways_to_get_rfcs. For example: 45 To: rfc-info@RFC-EDITOR.ORG 46 Subject: getting rfcs 48 help: ways_to_get_rfcs 50 Requests for special distribution should be addressed to either the 51 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 52 specifically noted otherwise on the RFC itself, all RFCs are for 53 unlimited distribution.echo 54 Submissions for Requests for Comments should be sent to 55 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 56 Authors, for further information.