Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS

Gert Doering <gert@space.net> Thu, 01 May 2014 08:59 UTC

Return-Path: <gert@Space.Net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 548FA1A88E4 for <v6ops@ietfa.amsl.com>; Thu, 1 May 2014 01:59:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g90T7t_tkFUZ for <v6ops@ietfa.amsl.com>; Thu, 1 May 2014 01:59:42 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) by ietfa.amsl.com (Postfix) with ESMTP id 9BCD71A88E1 for <v6ops@ietf.org>; Thu, 1 May 2014 01:59:42 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 9810E62A49 for <v6ops@ietf.org>; Thu, 1 May 2014 10:59:39 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 5F6D562A3B for <v6ops@ietf.org>; Thu, 1 May 2014 10:59:39 +0200 (CEST)
Received: (qmail 66840 invoked by uid 1007); 1 May 2014 10:59:39 +0200
Date: Thu, 01 May 2014 10:59:39 +0200
From: Gert Doering <gert@space.net>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
Message-ID: <20140501085939.GG43641@Space.Net>
References: <CF875D2F.1951A9%rajiva@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CF875D2F.1951A9%rajiva@cisco.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/YQHsFhmV_jPq4MzGkLSd6AmH8Bc
Cc: "mpls@ietf.org" <mpls@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2014 08:59:45 -0000

Hi,

On Thu, May 01, 2014 at 06:08:51AM +0000, Rajiv Asati (rajiva) wrote:
> We need your guidance on handling v4-mapped v6 addresses (section 2.5.5.2
> of [RFC4291]). 
> 
> 1. Should/Would they appear in IPv6 routing table?

"Yes and no".  It depends on the context - if the packet comes in and has
an IPv6 header, address lookup happens via the IPv6 routing table.  If 
a packet comes in with an IPv4 header, address lookup happens via the
IPv4 routing table.  

So, IPv4 should never "bleed over" to the IPv6 routing table, but if 
you happen to receive an IPv6 packet with a destination IPv6 address
in it's header of ::ffff:1.2.3.4, you'd either drop it right away,
or use the IPv6 routing table to find the destination.

The router itself should never ever source packets with a v4-mapped
destination address in the packet (see below).

> 2. Should an IPv6 packet with ::FFFF:127.0.0.0  be forwarded or dropped or
> treated as a loopback packet, if ever received?

Dropped.  v4-mapped is an internal representation of an IPv4 address
recevied on an ipv6 socket, and should never ever appear in packets on
the wire.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279