From fd3ce4f61c305a0f936a825a8cadf9be5d8d0bae Mon Sep 17 00:00:00 2001 From: chenxing Date: Fri, 19 May 2017 09:50:33 +0000 Subject: [PATCH] [networking] RFC 5737 compliance: service subnets Replace non-compliant subnets in: intro-nat.rst Change-Id: I0033d5da4cdb2fb210dd21e3ecbacdb568da7604 Partial-Bug: #1656378 --- doc/networking-guide/source/intro-nat.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/networking-guide/source/intro-nat.rst b/doc/networking-guide/source/intro-nat.rst index 081c59edfe..d700a1d746 100644 --- a/doc/networking-guide/source/intro-nat.rst +++ b/doc/networking-guide/source/intro-nat.rst @@ -27,12 +27,12 @@ address of the sender in IP packets. SNAT is commonly used to enable hosts with *private addresses* to communicate with servers on the public Internet. -`RFC 1918 `_ +`RFC 5737 `_ reserves the following three subnets as private addresses: -* ``10.0.0.0/8`` -* ``172.16.0.0/12`` -* ``192.168.0.0/16`` +* ``192.0.2.0/24`` +* ``198.51.100.0/24`` +* ``203.0.113.0/24`` These IP addresses are not publicly routable, meaning that a host on the public Internet can not send an IP packet to any of these addresses. Private IP