50 likes | 76 Views
NAT444 Operational Concerns. The Bad and the Ugly. Why NAT444?. Either operators are masochistic or “the alternative is worse” (or both) Changing CPE can lead to $$ or customer churn v4 only end devices (CE for example). What is worse than NAT444?.
E N D
NAT444 Operational Concerns • The Bad and the Ugly
Why NAT444? • Either operators are masochistic or “the alternative is worse” (or both) • Changing CPE can lead to $$ or customer churn • v4 only end devices (CE for example)
What is worse than NAT444? • NAT444 with conflicting address space on both sides of the CPE • While some parts of 1918 space are “default” use for NAT devices, the whole space is at risk for conflict • Front-line call centres’ will find trouble-shooting this “challenging.”
What are the alternatives? • Avoid NAT444 - trust us, we’d REALLY like to, without breaking our business • Deploy NAT444 using 1918 space and roll the dice • Deploy NAT444 with re-useable address space that is not a space recommended by vendors and other documentation as being available to use (and used by default, etc.)
Mitigating Factors • Size of space is “flexible” so long as it is reasonable. • For some a /8 is too small (so there would be parallel NAT444 clouds) • For all a /16 is probably too small • Somewhere in-between is correct • The space is “re-useable” but reserved for NAT-based service providers. When (not if) customers use it, they will have to do so manually, and that is easier to deal with • The space has a time horizon that is based around CPE fleet turnover.