| 2017-01-13 18:34:34 |
Clint Byrum |
bug |
|
|
added bug |
| 2017-01-16 11:02:30 |
John Davidge |
openstack-manuals: status |
New |
Confirmed |
|
| 2017-01-16 11:02:43 |
John Davidge |
openstack-manuals: importance |
Undecided |
High |
|
| 2017-01-17 16:14:57 |
Alexandra Settle |
openstack-manuals: assignee |
|
John Davidge (john-davidge) |
|
| 2017-01-17 16:20:40 |
Alexandra Settle |
openstack-manuals: status |
Confirmed |
In Progress |
|
| 2017-02-01 10:11:24 |
kavitha h r |
openstack-manuals: status |
In Progress |
Fix Committed |
|
| 2017-02-01 14:59:50 |
John Davidge |
openstack-manuals: status |
Fix Committed |
In Progress |
|
| 2017-02-03 13:57:09 |
John Davidge |
description |
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 |
***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 |
|
| 2017-02-07 10:44:46 |
John Davidge |
openstack-manuals: milestone |
|
ocata |
|
| 2017-03-02 16:13:04 |
OpenStack Infra |
openstack-manuals: assignee |
John Davidge (john-davidge) |
caoyuan (cao-yuan) |
|
| 2017-03-03 11:56:06 |
OpenStack Infra |
openstack-manuals: assignee |
caoyuan (cao-yuan) |
John Davidge (john-davidge) |
|
| 2017-03-03 16:02:39 |
OpenStack Infra |
openstack-manuals: assignee |
John Davidge (john-davidge) |
caoyuan (cao-yuan) |
|
| 2017-04-05 13:20:23 |
OpenStack Infra |
openstack-manuals: assignee |
caoyuan (cao-yuan) |
John Davidge (john-davidge) |
|
| 2017-05-18 14:12:09 |
Brian Haley |
bug |
|
|
added subscriber Brian Haley |
| 2017-05-18 23:06:04 |
Akihiro Motoki |
openstack-manuals: assignee |
John Davidge (john-davidge) |
Akihiro Motoki (amotoki) |
|
| 2017-05-19 09:51:22 |
OpenStack Infra |
openstack-manuals: assignee |
Akihiro Motoki (amotoki) |
Chason (chen-xing) |
|
| 2017-05-19 13:16:35 |
Akihiro Motoki |
openstack-manuals: assignee |
Chason (chen-xing) |
Akihiro Motoki (amotoki) |
|
| 2017-05-23 16:37:31 |
OpenStack Infra |
openstack-manuals: assignee |
Akihiro Motoki (amotoki) |
Chason (chen-xing) |
|
| 2017-09-12 22:02:28 |
Alexandra Settle |
bug task added |
|
neutron |
|
| 2017-09-12 22:02:45 |
Alexandra Settle |
openstack-manuals: status |
In Progress |
Won't Fix |
|
| 2017-09-12 22:02:51 |
Alexandra Settle |
neutron: status |
New |
Confirmed |
|
| 2017-09-12 22:03:38 |
Akihiro Motoki |
tags |
networking-guide |
doc |
|
| 2017-09-12 22:03:51 |
Akihiro Motoki |
neutron: assignee |
|
Akihiro Motoki (amotoki) |
|
| 2017-09-12 22:03:56 |
Akihiro Motoki |
neutron: importance |
Undecided |
High |
|
| 2019-03-05 01:05:20 |
André Luis Penteado |
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 |
***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 RFC3849, 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 |
|
| 2019-03-05 01:07:48 |
André Luis Penteado |
bug |
|
|
added subscriber André Luis Penteado |
| 2024-02-14 15:54:41 |
Brian Haley |
neutron: importance |
High |
Low |
|
