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/address-policy-wg@ripe.net/
[address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
- Previous message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
- Next message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Garry Glendown
garry at nethinks.com
Wed Apr 15 19:26:04 CEST 2009
Peter Koch wrote: > The new assignment is not intended to serve as a supplement to RFC 1918 > address space. It is intentionally left open here whether similar > considerations would suggest an additional assignment in v6 space, as well. Why would you not want to use RFC1918's IPs in documentation? Everybody inclined enough to read documentation will probably know those addresses at a glance ... instead, you want to throw a new set of IPs on the market that nobody knows, nobody cares for, most likely nobody will use and that have no real benefit as far as documentation goes ... (at least none I'd see). Heck, I've never known that 192.0.2/24 is reserved for test purposes ... or that there are "test domains" ... but maybe I'm just ignorant ... ;) (not that saving that /24 would mitigate the dawning IPv4 shortage ...) -garry
- Previous message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
- Next message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]