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

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 01 May 2014 06:59 UTC

Return-Path: <swmike@swm.pp.se>
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 472AD1A0A27; Wed, 30 Apr 2014 23:59:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.602
X-Spam-Level:
X-Spam-Status: No, score=-4.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 k07gSmZUr0tY; Wed, 30 Apr 2014 23:59:25 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by ietfa.amsl.com (Postfix) with ESMTP id 14EA51A0A17; Wed, 30 Apr 2014 23:59:25 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 8B4FCA6; Thu, 1 May 2014 08:59:22 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1398927562; bh=8xqZPIWyBXZqp6CTGwV0Pcox1VFGEELHcpcDyoP4C6o=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=y0mdbxSSvD+nRQBAoYSpkaZ6yRxzHjDS5vmaEe/Mhw4WWxMKaBn43953IW2wzLa6h jL1kokdz7ISR24CwYn1LEx3puCia6sYgb8PzLCy0I1MQHa+1hIcyv8WKVxwvwjzDai AsEaanXlo9009qbDj0kfNDEJ+xJgta+lxRRHEucU=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7DB4CA5; Thu, 1 May 2014 08:59:22 +0200 (CEST)
Date: Thu, 01 May 2014 08:59:22 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Hesham Soliman <hesham@elevatemobile.com>
In-Reply-To: <CF882A16.4EA36%hesham@elevatemobile.com>
Message-ID: <alpine.DEB.2.02.1405010856540.29282@uplift.swm.pp.se>
References: <CF875D2F.1951A9%rajiva@cisco.com> <alpine.DEB.2.02.1405010836220.29282@uplift.swm.pp.se> <CF882A16.4EA36%hesham@elevatemobile.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-478116969-1398927562=:29282"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/C84UyWyzUu2KXFnZ4SegBrWv0s4
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 06:59:27 -0000

On Thu, 1 May 2014, Hesham Soliman wrote:

>> or in the routing table
>
> => That¹s a different story. I don¹t think there is anything banning this,
> not least due to the fact that it is an implementation issue. If that
> entry points to an IPv4 tunnel it should be fine. So it is possible to
> implement a tunnel that way inside the host/router and nothing to stop
> someone from doing unless I missed an RFC.

Let me qualify my statement that I don't want to see it outside the box, 
ie in routes it's sending to anyone else. If it's in the internal RIB I 
have no problem with it, if it starts being announced in IGP and BGP then 
I think it's a bigger issue.

>> and if
>> they're there, I would want hosts/routers to drop them.
>
> => Is that behaviour documented somewhere? Also, you¹re mixing them
> appearing on the wire with an internal implementation issue.

If this is documented somewhere, I am not aware, but I am definitely not 
the right person to ask about what might be in what RFC.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se