This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/

[ipv6-wg] Its that time of the year...

Previous message (by thread): [ipv6-wg] Its that time of the year...
Next message (by thread): [ipv6-wg] New on RIPE Labs: How to Build and Market IPv6-only Services

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Yannis Nikolopoulos dez at otenet.gr
Mon Dec 2 17:34:19 CET 2019

Hi Jan,

On 12/1/19 9:16 PM, Jan Zorz - Go6 wrote:
> On 29/11/2019 11:47, Yannis Nikolopoulos wrote:
>> A few years back we gave LW4o6 a go. In the end, it did not work out 
>> very well. 
> 
> I think that you might be much happier with MAP-E as it is stateless and 
> keeps NAT at the right place (CPE).

I think so too. If CPE issues do not arise, we're hoping that the BR 
performance will be satisfying.

> No matter how hard you try, at the end of the day LW4o6 is still 
> stateful mechanism.
> Please, keep us in sync how the deployment is going.
> 
> Just out of curiosity - how many ports per CPE did you configure?

1008 ports

> Cheers, Jan

cheers,
Yannis

Previous message (by thread): [ipv6-wg] Its that time of the year...
Next message (by thread): [ipv6-wg] New on RIPE Labs: How to Build and Market IPv6-only Services

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]