IETF Logo Mail Archive

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

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Thu, 01 May 2014 22:20 UTC

Return-Path: <rajiva@cisco.com>
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 CA6301A0948; Thu, 1 May 2014 15:20:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 v6a3X7n5ZGhr; Thu, 1 May 2014 15:20:22 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 5837D1A06DB; Thu, 1 May 2014 15:20:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1520; q=dns/txt; s=iport; t=1398982820; x=1400192420; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=k4S/nS0HaDlaEU0x2uJcZ98uVGbisT63Zg6f8W/d8qc=; b=LUJJBZHVxCSUVfdN0YGrobWgpYPJzdaPKsFuSCFYWOZSvOzAJbI8mO/+ FsGk4OfA7KwRtL1vwzBIZ4PMTQ6+4yQIIyFp/4UNuTZrdxbSBGSCs6o25 Sexfi0uYS1jihnH8nGaRfQ9Hrtw2qFLPp9OmJjvNKMYmxzWVcRbFkECmR I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFACTIYlOtJA2D/2dsb2JhbABagwZPvXOHPoEUFnSCJQEBAQMBAQEBawsFCwIBCBguJwslAgQOBYg5CA3JaBeOUgeDJIEVBIlMj2OBPJEygzM
X-IronPort-AV: E=Sophos;i="4.97,967,1389744000"; d="scan'208";a="321837749"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-3.cisco.com with ESMTP; 01 May 2014 22:20:20 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s41MKJO7032112 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 1 May 2014 22:20:19 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.41]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Thu, 1 May 2014 17:20:19 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Simon Perreault <simon@per.reau.lt>
Thread-Topic: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
Thread-Index: AQHPZYHVKyuQb1xSnUicpDemuoOtD5ssTA69
Date: Thu, 01 May 2014 22:20:19 +0000
Message-ID: <A88E5272-6E81-420B-977A-DE8CF21E8829@cisco.com>
References: <CF875D2F.1951A9%rajiva@cisco.com>,<5362B83F.4020808@per.reau.lt>
In-Reply-To: <5362B83F.4020808@per.reau.lt>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/CZoViCCzlQ9xSYnsApr4DoohyZw
Cc: "mpls@ietf.org" <mpls@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, 6man WG <ipv6@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 22:20:23 -0000

Hi Simon,

Ditto. This is what I was about to suggest for Q#1. Thanks. 

I wish there was something like that for ospfv3, isis, rip, BGP etc. too. 

Cheers,
Rajiv

> On May 1, 2014, at 5:10 PM, "Simon Perreault" <simon@per.reau.lt> wrote:
> 
> Le 2014-05-01 02:08, Rajiv Asati (rajiva) a écrit :
>> The answer to Q#1 will help MPLS WG to decide the proper handling of
>> v4-mapped v6 addresses in LDPv6 draft section 7 1st para.
>> http://tools.ietf.org/html/draft-ietf-mpls-ldp-ipv6-12#section-7 *
> 
> Rajiv,
> 
> In addition to what the others have said, to provide very precise
> guidance, I think this text in your draft...
> 
>   An LSR MUST NOT allocate and MUST NOT advertise FEC-Label bindings
>   for link-local IPv6 address, and ignore such bindings, if ever
>   received. An LSR MUST treat the IPv4-mapped IPv6 address, defined in
>   section 2.5.5.2 of [RFC4291], the same as that of a global IPv6
>   address and not mix it with the 'corresponding' IPv4 address.
> 
> ...should be changed to:
> 
>   An LSR MUST NOT allocate and MUST NOT advertise FEC-Label bindings
>   for link-local or IPv4-mapped IPv6 address, and ignore such
>   bindings, if ever received.
> 
> Simon
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email