Last Call: <draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat-00.txt> (IPv6 Multihoming without Network Address Translation) to Informational RFC

The IESG <> Tue, 07 June 2011 19:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3E97411E823F; Tue, 7 Jun 2011 12:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GYYSthtMTeCS; Tue, 7 Jun 2011 12:41:01 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id BC13511E81E3; Tue, 7 Jun 2011 12:41:01 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat-00.txt> (IPv6 Multihoming without Network Address Translation) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 3.55
Message-ID: <>
Date: Tue, 07 Jun 2011 12:41:01 -0700
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 07 Jun 2011 19:41:02 -0000

The IESG has received a request from the IPv6 Operations WG (v6ops) to
consider the following document:
- 'IPv6 Multihoming without Network Address Translation'
  <draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat-00.txt> as an
Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2011-06-21. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


Network Address and Port Translation (NAPT) works well for conserving
global addresses and addressing multihoming requirements, because an
IPv4 NAPT router implements three functions: source address
selection, next-hop resolution and optionally DNS resolution.  For
IPv6 hosts one approach could be the use of IPv6 NAT.  However, NAT
should be avoided, if at all possible, to permit transparent host-to-
host connectivity.  In this document, we analyze the use cases of
multihoming.  We also describe functional requirements for
multihoming without the use of NAT in IPv6 for hosts and small IPv6
networks that would otherwise be unable to meet minimum IPv6
allocation criteria.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.