Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge Routers (6PE)' to Proposed Standard

Yakov Rekhter <yakov@juniper.net> Sun, 27 August 2006 16:44 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GHNkH-0007LX-2K; Sun, 27 Aug 2006 12:44:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GHNkF-0007Ic-3E; Sun, 27 Aug 2006 12:44:23 -0400
Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GHNkC-0007pZ-N9; Sun, 27 Aug 2006 12:44:23 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id k7RGiI1Z092585; Sun, 27 Aug 2006 09:44:18 -0700 (PDT) (envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k7RGiIg53535; Sun, 27 Aug 2006 09:44:18 -0700 (PDT) (envelope-from yakov@juniper.net)
Message-Id: <200608271644.k7RGiIg53535@merlot.juniper.net>
To: David Ward <dward@cisco.com>
Subject: Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge Routers (6PE)' to Proposed Standard
In-Reply-To: Your message of "Fri, 25 Aug 2006 17:43:04 CDT." <C114E728.809F7%dward@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <39284.1156697058.1@juniper.net>
Date: Sun, 27 Aug 2006 09:44:18 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: idr@ietf.org, Bill Fenner <fenner@research.att.com>, "Durand, Alain" <Alain_Durand@cable.comcast.com>, IESG <iesg@ietf.org>, softwires@ietf.org, "Mark Townsley (townsley)" <townsley@cisco.com>, Sam Hartman <hartmans-ietf@mit.edu>
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

Dave,

> Yakov -
> 
> Please note that we have to solve the scenarios that include tunnel
> encapsulation aka non-MPLS deployments. 

By "non-MPLS deployment" do you mean that the tunnels can not be LSPs,
or do you mean that there should be no MPLS at all, even at the edges
(PEs) ?

> Therefore, the AF/SAF needs some reinterpretation.

You still did not answer my question. Namely, which of the AFI/SAFIs 
currently defined by IETF need "some reinterpretation" ?

Yakov. 

> 
> 
> Thanks
> 
> -DWard
> 
> 
> On 8/25/06 3:17 PM, "Yakov Rekhter" <yakov@juniper.net> wrote:
> 
> > Dave,
> > 
> >> Yakov, Bill -
> >> 
> >> Since we allow the route to an X-prefix to have a Y-address as its next ho
p,
> >> we still need an SOFTWIRE|IDR document to specify  how to do that.  For th
e
> >> cases where (a) X is  VPN-IPv4 and Y  is IPv4,  (b) X is  VPN-IPv6 and Y  
is
> >> IPv4, (c)  X is VPN-IPv6 and  Y is IPv6, we  have legacy solutions in
> >> deployment which could easily remain valid.
> > 
> > We also have "legacy solutions" for the cases where (d) X is IPv6
> > and Y is IPv4, (e) X is L2VPN and Y is IPv4, (f) X is L2VPN and Y
> > is IPv6, (g) X is RT and Y is IPv4, (h) X is RT and Y is IPv6, ...
> >   
> >> In addition, we need to handle the  "X is VPN-IPv4 and Y is IPv6" case,
> > 
> > See e-mail from Ron Bonica on this.
> > 
> >> as  well as the case where X is IPv4 and Y is IPv6 and the case
> >> where X is IPv6 and Y is IPv4.
> > 
> > X is IPv6 and Y is IPv4 is done (6PE).
> > 
> > The only item from your list above for which the IETF does not have
> > a solution is the case where X is IPv4 and Y is IPv6. With this in
> > mind, why would not the softwires WG take the existing 6PE as the
> > base and modify it to cover the case where X is IPv4 and Y is IPv6 ?
> > 
> >> The necessary document being proposed
> >> needs at least the following components:
> >> 
> >> - A reinterpretation of IPv4 AFI/SAFI  and IPv6 AFI/SAFI which allows the 
NH
> >>   to  be of  a  different  AF than  the  NLRI.
> > 
> > Since the interpretation of MP_REACH/MP_UNREACH depends on a combination
> > of AFI/SAFI, and since IPv4 or IPv6 only define AFI, which of the
> > currently defined SAFIs need the reinterpretation ?
> > 
> > Yakov.

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