On Wed, 3 Jan 2007, Andrew Sullivan wrote: > Dear colleagues, > > On Wed, Jan 03, 2007 at 03:50:01PM -0500, [EMAIL PROTECTED] wrote: > > > Title : Considerations for the use of DNS Reverse Mapping > > Author(s) : D. Senie, A. Sullivan > > Filename : draft-ietf-dnsop-reverse-mapping-considerations-01.txt > > Pages : 10 > > Date : 2007-1-3 > > This version of the draft is our attempt to address all the comments > we received on the list and in San Diego about the -00 draft. The > text that I originally proposed on the list for issue 10 has been > mostly replaced by that which emerged from Ed Lewis's discussion of > the issue. I hope it is better this way. > > Any comments are, as always, welcome. Thanks very much.
>RIRs may delegate address space to Local Internet Registries (LIRs), >who may perform further delegation. Reverse mapping only works if >all the intermediate delegations are correctly maintained. As a >result, RIRs find they cannot enforce policies requiring reverse >mappings, because they sometimes do not have any relationship with >the intermediate party on whom some end-point reverse mapping >depends. It may be supposed that IPv6 will make this "reachover >problem" worse, because of the likelihood of longer delegation chains >in IPv6. I agree that RIR's cannot enforce policies requiring reverse mapping on end users or maybe even endpoint ISP's but they could and in some cases do have policies related to reverse delegations on the direct relationship's they have with LIR's. The RIPE NCC strongly encourage LIR's to insert the data for reverse delegation. This is mentioned in the following policy: http://www.ripe.net/ripe/docs/rev-del.html The RIPE NCC will also be soon kicking off a project to check delegations from RIPE>LIR's in the reverse tree. You can see the details here. http://www.ripe.net/ripe/draft-documents/dns-lameness.html I think similar work is being undertaken in APNIC which I'm sure George may be able to comment on. I think the fact that policies can and do exist to encourage reverse delegations should be mentioned in this draft. -- Brett Carr RIPE Network Coordination Centre Manager -- DNS Services Group Singel 258 Amsterdam NL GPG Key fingerprint = F20D B2A7 C91D E370 44CF F244 B6A1 EF48 E743 F7D8 _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www1.ietf.org/mailman/listinfo/dnsop
