Reverse DNS in IPv6 for Internet Service Providers
RFC 8501
Revision differences
Document history
Date | By | Action |
---|---|---|
2019-08-19
|
Gunter Van de Velde | Closed request for Telechat review by OPSDIR with state 'Overtaken by Events' |
2019-08-19
|
Gunter Van de Velde | Assignment of request for Telechat review by OPSDIR to Susan Hares was marked no-response |
2018-11-28
|
(System) | Received changes through RFC Editor sync (created alias RFC 8501, changed abstract to 'In IPv4, Internet Service Providers (ISPs) commonly provide IN-ADDR.ARPA information for … Received changes through RFC Editor sync (created alias RFC 8501, changed abstract to 'In IPv4, Internet Service Providers (ISPs) commonly provide IN-ADDR.ARPA information for their customers by prepopulating the zone with one PTR record for every available address. This practice does not scale in IPv6. This document analyzes different approaches and considerations for ISPs in managing the IP6.ARPA zone.', changed pages to 15, changed standardization level to Informational, changed state to RFC, added RFC published event at 2018-11-28, changed IESG state to RFC Published) |
2018-11-28
|
(System) | RFC published |