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/[email protected]/
[ipv6-wg] Free GUA space for community projects [CfP/RFC] (was: Minutes from the IPv6 WG @ RIPE 83)
- Previous message (by thread): [ipv6-wg] Free GUA space for community projects [CfP/RFC] (was: Minutes from the IPv6 WG @ RIPE 83)
- Next message (by thread): [ipv6-wg] Free GUA space for community projects [CfP/RFC] (was: Minutes from the IPv6 WG @ RIPE 83)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Vasilenko Eduard
vasilenko.eduard at huawei.com
Wed Dec 22 09:33:40 CET 2021
3. use proper source based routing on the ISP routers -> see homenet WG. a) homenet is not available on real products b) if a particular resource is in the walled garden of one Carrier (access from other carriers are filtered), then source routing would not help, proper source address should be chosen first on the host. Only NPT resolves this situation now. c) homenet did not try to resolve ND problems of proper withdrawal for stale prefixes. If uplink to one carrier would be lost - it does not discuss how it would be informed to the hosts on the first hop. Hence, no - solution 3 does not exist. Ed/ -----Original Message----- From: Gert Doering [mailto:gert at space.net] Sent: Wednesday, December 22, 2021 11:18 AM To: Vasilenko Eduard <vasilenko.eduard at huawei.com> Cc: Leo Vegoda <leo at vegoda.org>; Marco Hogewoning <marcoh at ripe.net>; ipv6-wg at ripe.net Subject: Re: [ipv6-wg] Free GUA space for community projects [CfP/RFC] (was: Minutes from the IPv6 WG @ RIPE 83) Hi, On Wed, Dec 22, 2021 at 08:09:59AM +0000, Vasilenko Eduard via ipv6-wg wrote: > Almost any business (even small) would like to have Internet resiliency in the form of redundant connections through the different Carriers. > Then hosts should have PA addresses from different carriers. > > Hosts are not capable to choose properly which one address to choose for the particular flow. > If the address of Carrier 1 would be used as the source for the packet going to Carrier2 then Carrier2 would drop the packet as a result of spoofing protection (uRPF check). > > If the connection to the carrier is lost then the respective PA address should be withdrawn (by the way, not resolved problem in IETF). > > There are only 2 currently available solutions for Internet connections resiliency: > 1. Request PI from RIR. Then the Internet table would be the size of all businesses in the world. > 2. Use ULA internally and NPT (prefix translation to proper PA) on the CPEs connecting to the Carrier. 3. use proper source based routing on the ISP routers -> see homenet WG. Of course NAT is good (https://www.youtube.com/watch?v=v26BAlfWBm8) but not really needed here. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
- Previous message (by thread): [ipv6-wg] Free GUA space for community projects [CfP/RFC] (was: Minutes from the IPv6 WG @ RIPE 83)
- Next message (by thread): [ipv6-wg] Free GUA space for community projects [CfP/RFC] (was: Minutes from the IPv6 WG @ RIPE 83)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]