APNIC Whois Upgrade Update
•
0 j'aime•597 vues
Presentation by Anna Mulingbayan at APNIC 44 on Wednesday, 13 September 2017
Recommandé
Recommandé
Contenu connexe
Similaire à APNIC Whois Upgrade Update
Similaire à APNIC Whois Upgrade Update (20)
Plus de APNIC
Plus de APNIC (20)
Dernier
Dernier (20)
APNIC Whois Upgrade Update
- 1. APNIC Whois Upgrade Anna Mulingbayan anna@apnic.net
- 2. Latest whois upgrade • Organization object • Last-modified attribute 2
- 3. Organization object • What is an organization object? – New object type in whois that is used to represent an APNIC account holder’s company name and contact information – An account holder’s delegation from APNIC are linked to their organization object – This allows an organisation’s resources to be determined easily in whois • For example, whois.apnic.net -i org <Unique org ID> -T inetnum, inet6num, aut-num • How are organization objects created? – Existing APNIC account holders confirm or update their organization details in MyAPNIC – New accounts will get organization object details when they receive IP addresses or AS numbers • Where we are now? – Timeline of the implementation 3
- 4. Where are we now ? 4 5 Jun 2017 Announcement of the upgrade 26 Jun 2016 Whois v4 upgrade installed 9 Aug 2017 Organization objects inserted in whois after Members have confirmed or updated organization details Sep 2017 Request remaining Members to review their organization details 12 Jul 2017 Direct emails to authorized Member contacts 31 Aug 2017 3000 org objects created, that is, over 42% of APNIC Members have updated their organization details
- 5. Actions required by Members • Account contacts are asked to either review or update organization details via MyAPNIC from 12 July 2017 5
- 6. Actions required by Members • Contacts who log in to MyAPNIC will see the organization details update on the landing page 6
- 7. Need more information or support? • Please contact the APNIC Helpdesk – https://www.apnic.net/helpdesk • FAQ is available at: – https://www.apnic.net/get-ip/faqs/organization-object/ 7
- 8. Last-modified attribute • What is the “last-modified:” attribute? – A new attribute replacing the existing “changed:” attribute – Stores the time when the whois object was last updated – The value is set by the server when an update occurs • Why use “last-modified:”? – For accuracy of date and time stamp when changes are made for an individual record in the whois 8
- 9. Last-modified attribute implementation • Phase 1 – Whois objects that include “changed:” will still be accepted and clients will receive a warning about its coming deprecation – Any “changed:” attributes in updates will be removed and “last- modified:” will be added – The “changed:” attribute will be ignored when the object is deleted to avoid errors 9
- 10. Last-modified attribute implementation • Phase 2 – Objects that include “changed:” will be rejected 10
Notes de l'éditeur
- Background of the
- Point 2 start with Existing APNIC acount holders
- If asked say that we already discuss with NIR for any possible impact
- - Open or suspended accounts missing from this list because their contacts either don’t have access to MyAPNIC or permission to make this update – 515 members in this category - If members in this list due to MyAPNIC permission problems it was thought best to contact separately
- - Open or suspended accounts missing from this list because their contacts either don’t have access to MyAPNIC or permission to make this update – 515 members in this category - If members in this list due to MyAPNIC permission problems it was thought best to contact separately
- Members who do not have access to MyAPNIC Those who haven’t confirmed their org details yet 40% of members has now org object - Users to confirm or update before allowing them to do other things within MyAPNIC There are 145 users who do not have access to this page We have sent mail outs to 500 members who did not have access in MyAPNIC because MyAPNIC is the only way to create org-object – security reasons for this These details are generated based on our internal record
- Convey info about this affects their use of whois
- Reason behind taking this 2-phase approach: - Reduced impact on NIRS (questions we have is will their systems accept these objects after implementation changes, can their users perform queries?) -> Discussion for NIR w/s at APNIC 44 - Reduced impacts on members (for example those whom have their own scripts etc) - Reduced downtime since it will only be during the regular maintenance windows when moving to each phase