yahoo-eng-team team mailing list archive

[Alexandra Settle <a.settle@xxxxxxxxxxx>]

Moved to the neutron repo :)

** Also affects: neutron
   Importance: Undecided
       Status: New

** Changed in: openstack-manuals
       Status: In Progress => Won't Fix

** Changed in: neutron
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1656378

Title:
  Networking Guide uses RFC1918 IPv4 ranges instead of RFC5737

Status in neutron:
  Confirmed
Status in openstack-manuals:
  Won't Fix

Bug description:
  ***UPDATE***

  An etherpad for tracking the required changes can be found here:

  https://etherpad.openstack.org/p/non-compliant-ip-subnets

  ************

  Hi! I was reading the guide on the "Get me a network" bits, and I
  realized that the whole manual is using the wrong address ranges.

  RFC5737 defines three ranges for use in documentation:

  3.  Documentation Address Blocks

     The blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2),
     and 203.0.113.0/24 (TEST-NET-3) are provided for use in
     documentation.

  These are non-routable addresses, even privately, and the RFC is
  specifically provided to avoid problems like overlap (If everyone uses
  the 10.x ranges because that's what's in the manuals, we end up with
  even more overlap than usual).

  https://tools.ietf.org/rfc/rfc5737.txt

  It's worth noting that the manual _is_ compliant with RFC3848, which
  defines the IPv6 documentation range as 2001:db8::/32.

  -----------------------------------
  Release: 0.9 on 2017-01-12 12:47
  SHA: 03c62feaf3779cc3b0491f83bcb5eb2dd3442e2a
  Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/networking-guide/source/config-auto-allocation.rst
  URL: http://docs.openstack.org/newton/networking-guide/config-auto-allocation.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1656378/+subscriptions