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/[email protected]/
[cooperation-wg] publication of data about legacy resources
- Previous message (by thread): [cooperation-wg] publication of data about legacy resources
- Next message (by thread): [cooperation-wg] publication of data about legacy resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Seun Ojedeji
seun.ojedeji at gmail.com
Mon Sep 22 11:11:44 CEST 2014
On Mon, Sep 22, 2014 at 9:44 AM, Roland Perry < roland at internetpolicyagency.com> wrote: > > >Indeed. But it is not up to the RIRs or anyone else who contributes > money to (part) fund IANA to define what services IANA provides. At least > >not yet. Maybe that'll change if/when the DoC contract goes away. > > The only service IANA needs to provide here is updating a very small > number of entries comprising the /8 allocation records, when the need > arises. > I think the point here is that IANA no longer assign to orgs(and somewhat transferred initial legacy spaces maintenance to RIR) and since they now only assign to RIRs the records already reflects the relevant assignments. If there is any regular update that is required, it will/should be at the RIR level because there is apparently no major changes that will happen at /8 level. [1] > Also note I'm not suggesting the records for 51/8 are still out of date, > or need any maintenance. > > Nor am I suggesting that the same ideas be applied to legacy blocks > smaller than a /8, because that doesn't seem to me to be anything to do > with "IANA oversight". > This seem to negate your call for IANA to update its records; because i think your scenario above would have been a good example. Nevertheless, i also agree that "how IANA maintain whois record is definitely not within the IANA oversight scope" but rather an operation/policy issue. (though it doesn't hurt discussing it for all its worth) Regards 1. Speaking about who maintains legacy spaces, it may be good to note that its been raised by region members why its not "just" to maintain legacy spaces with paying members money. > -- > Roland Perry > > -- ------------------------------------------------------------------------ *Seun Ojedeji,Federal University Oye-Ekitiweb: http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> Mobile: +2348035233535**alt email: <http://goog_1872880453>seun.ojedeji at fuoye.edu.ng <seun.ojedeji at fuoye.edu.ng>* The key to understanding is humility - my view ! -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/cooperation-wg/attachments/20140922/4fb2bdff/attachment.html>
- Previous message (by thread): [cooperation-wg] publication of data about legacy resources
- Next message (by thread): [cooperation-wg] publication of data about legacy resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]