Re: [Idr] 6PE-Alt draft

"Vishwas Manral" <vishwas.ietf@gmail.com> Thu, 31 January 2008 17:32 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 1JKdGf-0007Tn-1v; Thu, 31 Jan 2008 12:32:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKdGe-0007TY-1b for idr@ietf.org; Thu, 31 Jan 2008 12:32:04 -0500
Received: from wr-out-0506.google.com ([64.233.184.231]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKdGd-0002mh-LT for idr@ietf.org; Thu, 31 Jan 2008 12:32:04 -0500
Received: by wr-out-0506.google.com with SMTP id 50so890195wri.25 for <idr@ietf.org>; Thu, 31 Jan 2008 09:32:03 -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=qyHJmKd+h8yHEIZqV/rC7ldQbNbGC77s4VKqV25TKKE=; b=HmROfZ973W6JlxZW24momYi6L5ymvbHGKHpHjrNbOokR9oTsJ1BW1KEb7IYik5mTnpQh5XOxEIMbywWgl+lnksTs39OePgjrR/BZoigdbngz1iAOG5xp/HPiNvBtptGie5y8/hajaQJUIvuS8yEx4S6uUz/1LlHlBwQu5hDBHZ8=
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=P2i3wiGw3Uqwz3dWCh2NDFkpiNF+dSlCdOX/rCI6gR1JBGCHfFNEA0Usp2X3j6uluES/UMb/YTLsbNnMd0znsyyK4zChCdW4AW/jRaeOO/b5LDizlj23WHofz7ds/n5cYZfQKH8rnFcL67PzqlTQtIs4Xc+2lVHa8ku+r/o1OG4=
Received: by 10.142.215.5 with SMTP id n5mr1347755wfg.140.1201800721966; Thu, 31 Jan 2008 09:32:01 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Thu, 31 Jan 2008 09:32:01 -0800 (PST)
Message-ID: <77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
Date: Thu, 31 Jan 2008 09:32:01 -0800
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Jan Novak <jjjnovak@hotmail.com>
Subject: Re: [Idr] 6PE-Alt draft
In-Reply-To: <BAY120-W1856D92C0C10B950241B43D8370@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> <77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com> <77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com> <BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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>
Errors-To: idr-bounces@ietf.org

Hi Jan,

Unlike in BGP MPLS IP VPN, the label does not tell any interface as we
finally look up the only routing table the IPv6 routing table. We do
not have the VRF concept here. That is the reason we do not need any
presignaled label. The 6PE draft mentions why we need the top label
very clearly.

However they have wrongly decided to signal a label with each route
instead of just using the IPv6 Explicit NULL label.

Thanks,
Vishwas

On Jan 31, 2008 9:00 AM, Jan Novak <jjjnovak@hotmail.com> 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