[ppml] Staff Comments Regarding Policy Proposal 2006-3
Owen DeLong
owen at delong.com
Fri Oct 6 12:21:28 EDT 2006
- Previous message: [ppml] Staff Comments Regarding Policy Proposal 2006-3
- Next message: [ppml] Staff Comments Regarding Policy Proposal 2006-3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I think this is a much better approach and I would support a policy bringing ARIN templates and whois data in line with this approach. Owen > RIPE supports a "mnt-routes:" attribute in their "inetnum" > objects > which refers > to a maintainer in the routing registry who is allowed to create route > objects > which are covered by the given address space. Note that > RIPE does not put AS information in the inetnum objects themselves. > One could envision an attribute similar to mnt-routes in the ARIN > address > registry which would refer to a maintainer in the ARIN IRR who is > allowed to create > routes in the IRR covered by that address space. This avoids > duplicate > information in both the address and routing registries and would > support > existing RPSL based configuration tools. > > -Larry Blunk > Merit > > _______________________________________________ > PPML mailing list > PPML at arin.net > http://lists.arin.net/mailman/listinfo/ppml -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.arin.net/pipermail/ppml/attachments/20061006/00a3cffa/attachment.bin
- Previous message: [ppml] Staff Comments Regarding Policy Proposal 2006-3
- Next message: [ppml] Staff Comments Regarding Policy Proposal 2006-3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the PPML mailing list