draft-ietf-behave-v4v6-bih-08.txt   draft-ietf-behave-v4v6-bih-09.txt 
Behave WG B. Huang Behave WG B. Huang
Internet-Draft H. Deng Internet-Draft H. Deng
Obsoletes: 3338, 2767 China Mobile Obsoletes: 3338, 2767 China Mobile
(if approved) T. Savolainen (if approved) T. Savolainen
Intended status: Standards Track Nokia Intended status: Standards Track Nokia
Expires: June 25, 2012 December 23, 2011 Expires: July 19, 2012 January 16, 2012
Dual Stack Hosts Using "Bump-in-the-Host" (BIH) Dual Stack Hosts Using "Bump-in-the-Host" (BIH)
draft-ietf-behave-v4v6-bih-08 draft-ietf-behave-v4v6-bih-09
Abstract Abstract
Bump-In-the-Host (BIH) is a host-based IPv4 to IPv6 protocol Bump-In-the-Host (BIH) is a host-based IPv4 to IPv6 protocol
translation mechanism that allows a class of IPv4-only applications translation mechanism that allows a class of IPv4-only applications
that work through NATs to communicate with IPv6-only peers. The host that work through NATs to communicate with IPv6-only peers. The host
on which applications are running may be connected to IPv6-only or on which applications are running may be connected to IPv6-only or
dual-stack access networks. BIH hides IPv6 and makes the IPv4-only dual-stack access networks. BIH hides IPv6 and makes the IPv4-only
applications think they are talking with IPv4 peers by local applications think they are talking with IPv4 peers by local
synthesis of IPv4 addresses. This document obsoletes RFC 2767 and synthesis of IPv4 addresses. This document obsoletes RFC 2767 and
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 25, 2012. This Internet-Draft will expire on July 19, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 5, line 23 skipping to change at page 5, line 23
DNS synthesis DNS synthesis
DNS, A record, synthesis is a process where A type of DNS record DNS, A record, synthesis is a process where A type of DNS record
is created by Extension Name Resolver to contain synthetic IPv4 is created by Extension Name Resolver to contain synthetic IPv4
address. address.
Real IPv4 address Real IPv4 address
An IPv4 address of a remote node a host has learned, for example, An IPv4 address of a remote node a host has learned, for example,
from DNS response to an A query. Real IPv4 address is opposite to from DNS response to an A query.
synthetic IPv4 address.
Real IPv6 address Real IPv6 address
An IPv6 address of a remote node a host has learned, for example, An IPv6 address of a remote node a host has learned, for example,
from DNS response to an AAAA query. from DNS response to an AAAA query.
Synthetic IPv4 address Synthetic IPv4 address
An IPv4 address that has meaning only inside a host and that is An IPv4 address that has meaning only inside a host and that is
used to provide IPv4 representation of remote node's real IPv6 used to provide IPv4 representation of remote node's real IPv6
skipping to change at page 9, line 8 skipping to change at page 9, line 8
getaddrinfo()) that will resolve both A and AAAA records. This getaddrinfo()) that will resolve both A and AAAA records. This
implementation alternative is name resolution protocol agnostic, and implementation alternative is name resolution protocol agnostic, and
hence supports techniques such as "hosts-file", NetBIOS, mDNS, and hence supports techniques such as "hosts-file", NetBIOS, mDNS, and
anything else the underlying operating system uses. anything else the underlying operating system uses.
In the case of the network layer implementation alternative, the ENR In the case of the network layer implementation alternative, the ENR
intercepts the A query and creates an additional AAAA query with intercepts the A query and creates an additional AAAA query with
similar content. The ENR will then collect replies to both A and similar content. The ENR will then collect replies to both A and
AAAA queries and, depending on results, either return an A reply AAAA queries and, depending on results, either return an A reply
unmodified or synthesize a new A reply. If no reply for A query is unmodified or synthesize a new A reply. If no reply for A query is
received after 300 ms since reception of positive AAAA response, the received after ENR implementation specific timeout, after reception
ENR MAY choose to proceed as if there were only AAAA record available of positive AAAA response, the ENR MAY choose to proceed as if there
for the destination. were only AAAA record available for the destination.
The network layer implementation alternative will only be able to The network layer implementation alternative will only be able to
catch applications' name resolution requests that result in actual catch applications' name resolution requests that result in actual
DNS queries, hence is more limited when compared to the socket API DNS queries, hence is more limited when compared to the socket API
layer implementation alternative. Hence the socket API layer layer implementation alternative. Hence the socket API layer
alternative is RECOMMENDED. alternative is RECOMMENDED.
In either implementation alternative, if DNS A record reply contains In either implementation alternative, if DNS A record reply contains
non-excluded real IPv4 addresses the ENR MUST NOT synthesize IPv4 non-excluded real IPv4 addresses the ENR MUST NOT synthesize IPv4
addresses. addresses.
 End of changes. 6 change blocks. 
9 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/