Re: [Idr] 6PE-Alt draft

"Vishwas Manral" <vishwas.ietf@gmail.com> Thu, 31 January 2008 14:31 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 1JKaRy-000566-Rf; Thu, 31 Jan 2008 09:31:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKaRv-0004zI-M6 for idr@ietf.org; Thu, 31 Jan 2008 09:31:31 -0500
Received: from wr-out-0506.google.com ([64.233.184.229]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKaRt-0006qS-EX for idr@ietf.org; Thu, 31 Jan 2008 09:31:31 -0500
Received: by wr-out-0506.google.com with SMTP id 50so749196wri.25 for <idr@ietf.org>; Thu, 31 Jan 2008 06:31:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=kWeJ2l/STxMartXRrRJzMki+IHPsSdt4IvkUt0HWko0=; b=fq7ZihD39EGpk6GFM1g4OkKYNqCt1E6th6WwBTRkIFgH40asRbEZprjqZ1aHTjzR1XUQx+afOR+UdBWd9esLSY2W/huf6HWaIJ25T1A8R/VpLcULflvYyxjUZKhPgOZVFaiHbqmq3jGp7C+X/UPreuSh0NzOsuJw1vLZ3X9CEGk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZDYHzr23O0k6xon6MvoASiruIqIH83G6sd6cbPlACX17lWOR0lxgRVFKp33SwLAK55R0WvYGYe7ils8joBWqtsSBAPCxu2Yj/wX5HvGyoMmtRHc7ra3ah83ctjMQfddDBgfktYVR5rsCMwYQPQWG8BFmLQOTP/p7kz3mhHK+lpA=
Received: by 10.142.139.19 with SMTP id m19mr1190394wfd.7.1201789887309; Thu, 31 Jan 2008 06:31:27 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Thu, 31 Jan 2008 06:31:27 -0800 (PST)
Message-ID: <77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
Date: Thu, 31 Jan 2008 06:31:27 -0800
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Jan Novak <jjjnovak@hotmail.com>
Subject: Re: [Idr] 6PE-Alt draft
In-Reply-To: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: idr@ietf.org
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>
Errors-To: idr-bounces@ietf.org

Hi Jan,

You may be missing the scope of the document. There is a discussion in
the v6ops group too which .

The idea is simple. We do not need to define a new AFI/ SAFI
combination to achieve the 6PE functionality. We can just use the
meaning implied in the IPv6 Explicit NULL label. The 6PE RFC does talk
about allowing signaling for the Explicit NULL label in which case the
dataplane functionality becomes just the same, but in 6PE even that is
signaled using BGP extensions defined in RFC3107.

Thanks,
Vishwas

On Jan 31, 2008 2:14 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
>
>
> Hi,
>
> Just out of curiosity - lets say you have two IPv4 VPNs with
> overlapping set of Pes and both of them want to provide 6PE
> service.
> When the explicit-null encapsulated packets from two different
> VPNs (but same PE) arrive to the other side PE - how do you
> decide which is which - e.g. which packet should be shipped to
> which VPN ??
>
> Jan
>
>
> _________________________________________________________________
> Telly addicts unite!
> http://www.searchgamesbox.com/tvtown.shtml

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