I think this problem is already solved in RFC 5549.

RFC 5549 specifies the procedures for creating a route with IPv4 or VPN-IPv4 NLRI and an IPv6 next hop, which should provide both 4PE and 4vPE functionality.

Your proposal seems to differ, in that it puts the v6 next hop address in the NLRI, rather than in the next hop field. I don't think it makes much sense to put the next hop address in the NLRI, as that would then require a special set of rules for bestpath selection.

On 3/8/2016 10:37 PM, [email protected] wrote:
Hello all,

I update my draft. 4PE is introduced in this doc to meet the gap pointed out in RFC7439. 4PE routers in IPv6-only MPLS network can use MP-BGP extended in this doc to connect IPv4-only islands.. Your comments are very appreciated.

------------------------------------------------------------------------
[email protected]

    *From:* internet-drafts <mailto:[email protected]>
    *Date:* 2016-03-09 09:54
    *To:* Zhenqiang Li <mailto:[email protected]>
    *Subject:* New Version Notification for draft-li-bess-4pe-01.txt
    A new version of I-D, draft-li-bess-4pe-01.txt
    has been successfully submitted by Zhenqiang Li and posted to the
    IETF repository.
    Name: draft-li-bess-4pe
    Revision: 01
    Title: Connecting IPv4 Islands over IPv6 MPLS Using IPv4 Provider
    Edge Routers (4PE)
    Document date: 2016-03-08
    Group: Individual Submission
    Pages: 9
    URL: https://www.ietf.org/internet-drafts/draft-li-bess-4pe-01.txt
    Status: https://datatracker.ietf.org/doc/draft-li-bess-4pe/
    Htmlized: https://tools.ietf.org/html/draft-li-bess-4pe-01
    Diff: https://www.ietf.org/rfcdiff?url2=draft-li-bess-4pe-01
    Abstract:
       This document explains how to interconnect IPv4 islands over a
       Multiprotocol Label Switching (MPLS)-enabled IPv6-only core.  This
       approach relies on IPv4 Provider Edge routers (4PE), which are Dual
       Stacks in order to connect to IPv4 islands and to the MPLS
    core.  The
       4PE routers exchange the IPv4 reachability information
    transparently
       over the core using the Multiprotocol Border Gateway Protocol (MP-
       BGP).  MP-BGP is extended to do this.  A new Subsequence Address
       Family Identifier (SAFI) with corresponding new format Network
    Layer
       Reachability Information (NLRI), is introduced.  The BGP Next Hop
       field is used to convey the IPv4 address of the 4PE router, a field
       is added in Network Layer Reachability Information (NLRI) to convey
       the IPv6 address of the 4PE router, so that dynamically established
       IPv6-signaled MPLS Label Switched Paths (LSPs) can be used without
       explicit tunnel configuration.
    Please note that it may take a couple of minutes from the time of
    submission
    until the htmlized version and diff are available at tools.ietf.org.
    The IETF Secretariat



_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess

_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess

Reply via email to