On a 4PE node the connectivity is like this:
v4 peering <— BGP (v4 NLRI with v4 NH) —> 4PE —— MPLS v6 ————— 4PE <— BGP (v4
NLRI with v4 NH) —> v4 peering
<— BGP (v4 NLRI with v6 NH) —>
From: "EXT li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>"
<li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>>
Date: Tuesday 3 May 2016 at 08:31
To: Wim Henderickx
<wim.henderi...@alcatel-lucent.com<mailto:wim.henderi...@alcatel-lucent.com>>,
"thomas.morin" <thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>>, bess
<bess@ietf.org<mailto:bess@ietf.org>>
Subject: Re: Re: [bess] Do 4PE routers need both IPv4 and IPv6 next hop
information?
Don't you need a IPv4 next hop to populate the IPv4 routing table in the 4PE
router?
________________________________
li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>
From: Henderickx, Wim (Nokia - BE)<mailto:wim.henderi...@nokia.com>
Date: 2016-04-29 00:17
To: li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>;
thomas.morin<mailto:thomas.mo...@orange.com>; bess<mailto:bess@ietf.org>
Subject: Re: [bess] Do 4PE routers need both IPv4 and IPv6 next hop information?
To support a v6 MPLS network we just need a v6 Next-hop for V4 prefixes as
described in RFC5549
From: BESS <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> on behalf of
"li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>"
<li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>>
Date: Tuesday 26 April 2016 at 01:58
To: "thomas.morin" <thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>>,
bess <bess@ietf.org<mailto:bess@ietf.org>>
Subject: [bess] Do 4PE routers need both IPv4 and IPv6 next hop information?
Hi, Everyone,
As talked in IETF 95 meeting in Buenos Aires, and suggested by our Chairs, I
want to know your opinion, especially the experts from the vendors, about 4PE
routers.
Do 4PE routers need both IPv4 and IPv6 next hop information to install their
IPv4 and IPv6 routing tables when they receive IPv4 routes from other 4PE
routers? Or they only need IPv6 next hop information?
Since RFC5549 can only convey IPv4 or IPv6 next hop for IPv4 routes, but not
both, I submit draft draft-li-bess-4pe to solve this problem. 4PE I think is a
scenario for my draft. Any other scenarioes that need both IPv4 and IPv6 next
hops?
For your reference, RFC5549 is here,
https://www.rfc-editor.org/rfc/rfc5549.txt, draft-li-bess-4pe is here,
https://www.ietf.org/id/draft-li-bess-4pe-01.txt<https://www.ietf.org/id/draft-li-bess-4pe-01.txt,>
Thank you very much
________________________________
li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>
From: Thomas Morin<mailto:thomas.mo...@orange.com>
Date: 2016-04-13 20:47
To: li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>;
bess<mailto:bess@ietf.org>
Subject: Re: [bess] minutes of our IETF 95 meeting
Hi,
I've updated the minutes.
Thanks for the precision.
Beyond this minute adjustment, I understand that the key thing you need to
clarify is what is missing or problematic in RFC5549.
Thank you,
-Thomas
2016-04-13, li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>:
for draft-li-bess-4pe-01:
Please add my response to comments from Keyur and Wim: 4PE routers need IPv4
next hop information to install their IPv4 routing table.
Thanks and Best Regards,
________________________________
li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>
From: Thomas Morin<mailto:thomas.mo...@orange.com>
Date: 2016-04-08 05:44
To: BESS<mailto:bess@ietf.org>
Subject: [bess] minutes of our IETF 95 meeting
Hi everyone,
We have just posted draft minutes for today's meeting.
You can read them at
https://www.ietf.org/proceedings/95/minutes/minutes-95-bess
Please send any comments you may have on these minutes.
Many many thanks to Gunter for his minute taking!
-Thomas/Martin
_______________________________________________
BESS mailing list
BESS@ietf.org<mailto:BESS@ietf.org>
https://www.ietf.org/mailman/listinfo/bess
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
