IETF Logo Mail Archive

Re: [Idr] 6PE-Alt draft

Francois Le Faucheur IMAP <flefauch@cisco.com> Thu, 31 January 2008 17:06 UTC

Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKcrW-0007Mc-ER; Thu, 31 Jan 2008 12:06:06 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKcrV-0007IW-0m for idr@ietf.org; Thu, 31 Jan 2008 12:06:05 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JKcrU-0001Ir-6t for idr@ietf.org; Thu, 31 Jan 2008 12:06:04 -0500
X-IronPort-AV: E=Sophos;i="4.25,286,1199660400"; d="scan'208,217";a="4533718"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 31 Jan 2008 18:06:03 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m0VH63cb023581; Thu, 31 Jan 2008 18:06:03 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m0VH61Ep027299; Thu, 31 Jan 2008 17:06:03 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 31 Jan 2008 18:06:01 +0100
Received: from [10.0.0.61] ([10.61.81.79]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 31 Jan 2008 18:06:00 +0100
In-Reply-To: <BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl> <77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com> <77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com> <BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <8BDF3D48-B388-44A9-A245-64DC68FD6BAC@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [Idr] 6PE-Alt draft
Date: Thu, 31 Jan 2008 18:05:54 +0100
To: Jan Novak <jjjnovak@hotmail.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 31 Jan 2008 17:06:00.0840 (UTC) FILETIME=[8DF9F880:01C8642B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7248; t=1201799163; x=1202663163; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=flefauch@cisco.com; z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco. com> |Subject:=20Re=3A=20[Idr]=206PE-Alt=20draft |Sender:=20; bh=PHbKn+fQd3MBg5Y6NNCE1lwH+zDiFYjAx2Vw/MijUkg=; b=w7RXOrwY2TRTr0YujqInXfa43kHDwAwH/YjonmYCwoVs9YyNRQReC1Frrh isN96ZwVNzPtfRqTgQk9MmJ23R2lOBokvsk2jM96L3I23PgAO+T2XslyrIlc b5F2asBFJ4;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Cc: idr@ietf.org, Francois Le Faucheur IMAP <flefauch@cisco.com>, Ooms Dirk <dirk@onesparrow.com>
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0831285961=="
Errors-To: idr-bounces@ietf.org

Hi Jan,

There are two documents that relate to transport of IPv6 over an IPv4  
MPLS core:
	* RFC4659 (6VPE): IPv6 VPNS over (say) IPv4 MPLS
	* RFC4798 (6PE): IPv6 over IPv4 MPLS

The quote below is from the 6PE RFC (ie WITHOUT VPN/VRF). It does not  
apply to the 6VPE.

Francois

On 31 Jan 2008, at 18:00, Jan Novak wrote:

>
>
>
> Hi Vishwas,
>
> I believe you refer to this part of 6PE spec:
>
>    The label bound by MP-BGP to the IPv6 prefix indicates to the  
> egress
>    6PE Router that the packet is an IPv6 packet.  This label  
> advertised
>    by the egress 6PE Router with MP-BGP MAY be an arbitrary label  
> value,
>    which identifies an IPv6 routing context or outgoing interface to
>    send the packet to, or MAY be the IPv6 Explicit Null Label.  An
>    ingress 6PE Router MUST be able to accept any such advertised  
> label.
>
> I don't know what is the envisaged use of Explicit Null here - but  
> I would think
> it is for some other purposes since to deliver the packet to the  
> VPN this is
> still needed "identifies an IPv6 routing context or outgoing  
> interface to".
>
> Jan
>
>
>
>
> _________________________________________________________________
> Share what Santa brought you
> https://www.mycooluncool.com


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email