idnits 2.17.1 draft-ietf-ngtrans-bia-05.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 3338 5 Title: Dual Stack Hosts Using "Bump-in-the-API" (BIA) 6 Author(s): S. Lee, M-K. Shin, Y-J. Kim, E. Nordmark, 7 A. Durand 8 Status: Experimental 9 Date: October 2002 10 Mailbox: syl@pec.etri.re.kr, mkshin@pec.etri.re.kr, 11 yjkim@pec.etri.re.kr, Alain.Durand@sun.com, 12 erik.nordmark@sun.com 13 Pages: 16 14 Characters: 34480 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-ngtrans-bia-05.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3338.txt 21 This document specifies a mechanism of dual stack hosts using a 22 technique called "Bump-in-the-API"(BIA) which allows for the hosts to 23 communicate with other IPv6 hosts using existing IPv4 applications. 24 The goal of this mechanism is the same as that of the 25 Bump-in-the-stack mechanism, but this mechanism provides the 26 translation method between the IPv4 APIs and IPv6 APIs. Thus, the 27 goal is simply achieved without IP header translation. 29 This document is a product of the Next Generation Transition Working 30 Group of the IETF. 32 This memo defines an Experimental Protocol for the Internet community. 33 It does not specify an Internet standard of any kind. Discussion and 34 suggestions for improvement are requested. Distribution of this memo 35 is unlimited. 37 This announcement is sent to the IETF list and the RFC-DIST list. 38 Requests to be added to or deleted from the IETF distribution list 39 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 40 added to or deleted from the RFC-DIST distribution list should 41 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 43 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 44 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 45 help: ways_to_get_rfcs. For example: 47 To: rfc-info@RFC-EDITOR.ORG 48 Subject: getting rfcs 50 help: ways_to_get_rfcs 52 Requests for special distribution should be addressed to either the 53 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 54 specifically noted otherwise on the RFC itself, all RFCs are for 55 unlimited distribution.echo 56 Submissions for Requests for Comments should be sent to 57 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 58 Authors, for further information.