Re: [mpls] mpls vs IPv6

Erblichs <erblichs@earthlink.net> Thu, 30 September 2004 22:17 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08250; Thu, 30 Sep 2004 18:17:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CD9My-0005Rp-Ho; Thu, 30 Sep 2004 18:25:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD8us-0000MJ-Sl; Thu, 30 Sep 2004 17:56:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD8oC-00067Y-FZ for mpls@megatron.ietf.org; Thu, 30 Sep 2004 17:49:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05548 for <mpls@ietf.org>; Thu, 30 Sep 2004 17:49:49 -0400 (EDT)
Received: from pop-a065c28.pas.sa.earthlink.net ([207.217.121.205]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CD8wV-0004uC-Jv for mpls@ietf.org; Thu, 30 Sep 2004 17:58:29 -0400
Received: from user-2ivfl39.dialup.mindspring.com ([165.247.212.105] helo=earthlink.net) by pop-a065c28.pas.sa.earthlink.net with esmtp (Exim 3.33 #1) id 1CD8o1-0003ey-00; Thu, 30 Sep 2004 14:49:41 -0700
Message-ID: <415C7FBB.5EB8490B@earthlink.net>
Date: Thu, 30 Sep 2004 14:50:51 -0700
From: Erblichs <erblichs@earthlink.net>
X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Piotr Marecki <p.marecki@swiat.pl>
Subject: Re: [mpls] mpls vs IPv6
References: <Pine.GSO.4.58.0409281121560.26661@ural2> <008401c4a637$13a8d3e0$0202a8c0@tdcinternet.pl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.0 (++++)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org
X-Spam-Score: 4.0 (++++)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: 7bit

This is abit of simplification, but should suffice..

IPv6 is the next generation protocol of IPv4 to move beyond
32 bit addressing.

IPv4 and IPv6 are end-system(ES), intermediate-system(IS), intermediate
system, end sytem protocols that are destination based protocols.
Note: ES is aka a host and IS is aka to a router.

MPLS is a IS-IS protocol that is source based, based on labels
being used for routing when entering a MPLS domain by a edge
router and only being removed when exiting the MPLS domain
at the exiting MPLS edge router.

At the entering MPLS edge router, the same mechanisms apply
as a VLAN tagged frame, to translate to the correct MPLS label
based on a number of factors, one of them could be the incoming
port.

Thus, MPLS requres IPv4 and/or IPv6 to be properly routed, but
IPv4/IPv6 does not need MPLS.

Hopefully this helps...

Mitchell Erblich
---------------------------



Piotr Marecki wrote:
> 
> Halo ,
> 
> IPv6 is related to MPLS in the same way as IPv4 ( i.e it is another network
> protocol transported on top of MPLS ). In that sense IPv6 is
> used with MPLS but not instead of. Please note that the IPv6 flow label has
> dissimiliar meaning than MPLS label and shall be used to diffrentiatate
> flows along with source and destination address ( see RFC3697 ) .
> 
> regards
> 
> Piotr Marecki
> 
> ----- Original Message -----
> From: "Jung Janos" <jj306@hszk.bme.hu>
> To: <mpls@ietf.org>
> Sent: Tuesday, September 28, 2004 11:22 AM
> Subject: [mpls] mpls vs IPv6
> 
> > Hi!
> >
> > I have to make some performance mesurement, with
> > IPv6, IPv4, mpls, but first i must find out,
> > if it has a sense.
> >
> > With MPLS I can create MPLS VPNs, QoS can (really?) be
> > granted to packet flows, and routing is more faster.
> >
> > IPv6 has the "Flow label" field wich makes routing faster
> > and has less header overhead than ipv4 (or mpls+ipv4)
> > And i think flow label could have the same use as
> > the mpls label value...
> >
> > How is MPLS to IPv6 related?
> >
> > Are they technologies that have nothing to do with each other?
> >
> > Or MPLS can bring new functionalities to IPv6 networks (like to IPv4), and
> > so mpls+ipv6 would have a sense?
> > And if so, what are the benefits?
> >
> > Or:
> >
> > IPv6 has all what mpls+ipv4 has (separeted flows to support qos
> > VPNs faster routing) and so mpls would have no further use?
> >
> > In the new IPV6 era what role will mpls play?
> >
> > thanks for the answers!
> > and sorry for the bad english
> >
> > regards
> > JJ.
> > (student)
> >
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@lists.ietf.org
> > https://www1.ietf.org/mailman/listinfo/mpls
> >
> 
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls