IETF Logo Mail Archive

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

sthaug@nethelp.no Thu, 01 May 2014 07:12 UTC

Return-Path: <sthaug@nethelp.no>
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 6FA8F1A0A25 for <v6ops@ietfa.amsl.com>; Thu, 1 May 2014 00:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=unavailable
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 MHxfjoYjZLWZ for <v6ops@ietfa.amsl.com>; Thu, 1 May 2014 00:12:50 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 0048A1A0A24 for <v6ops@ietf.org>; Thu, 1 May 2014 00:12:45 -0700 (PDT)
Received: (qmail 66636 invoked from network); 1 May 2014 07:12:42 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 1 May 2014 07:12:42 -0000
Date: Thu, 01 May 2014 09:12:42 +0200
Message-Id: <20140501.091242.74687867.sthaug@nethelp.no>
To: swmike@swm.pp.se
From: sthaug@nethelp.no
In-Reply-To: <alpine.DEB.2.02.1405010836220.29282@uplift.swm.pp.se>
References: <CF875D2F.1951A9%rajiva@cisco.com> <alpine.DEB.2.02.1405010836220.29282@uplift.swm.pp.se>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/iChJzko3rHPeFWiQNjwgfU1MlrE
Cc: mpls@ietf.org, v6ops@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 07:12:52 -0000

> http://tools.ietf.org/html/draft-itojun-v6ops-v4mapped-harmful-02
> 
> I realise this draft seems to have died, but I would never expect to see 
> packets with these addresses on the wire or in the routing table and if 
> they're there, I would want hosts/routers to drop them. Not doing this 
> seems to me it would open to all kinds of unwanted consequences when it 
> comes to filtering etc.

On the wire, definitely no. In the routing tables - ::ffff:127.0.0.0
is not expected, but other IPv4-mapped IPv6 address are possible, for
instance if you use 6VPE.

Steinar Haug, AS 2116

v2.23.0 | Report a Bug | By Email