You're viewing an archived page. It is no longer being updated.
Wednesday, 14 May, 14:00-15:30
Working Group Chairs: Nigel Titley, Ulf Klieber
Scribe: Nigel Titley
See presentation
All issues are now tracked in github (although this was noted to be not necessarily useful to people who were not familiar with Github)
Code base is open and in github
All releases are now made to a release candidate before going to production
The via: attribute has been added to autnum
Member resources are covered by abuse-c:
Roughly 33% of IPv4 and 44% of IPv6 PI space is covered by abuse-c:
Single Sign On (SSO) has been introduced which will allow the introduction of more features and services such as authenticated queries.
Pending route authorisation gives a hierachical authorisation process.
Documentation has been improved and is now linked to the version number
Hot node in Stockholm is now up and running and accepting queries (load balanced with Amsterdam)
aut-num now has a mandatory status ('ASSIGNED', 'LEGACY', 'OTHER') (automatically added)
All inetnum legacy objects have been set to status: LEGACY
sponsoring-org: has been added to end user objects
Deprecate "referral-by:"
New flag to request personal data. Should this go ahead?
Only block person objects when limits reached (rather than everything)
Internationalisation? What business/syntax rules should we apply?
Replace changed: with created: and last-updated: attributed.
Stats show that 27.4% of changed: dates don't match the actual data.
Improved dummification algorithm removing slightly less data and standardised
Improved user experience
Review of all error messages (does anyone parse them?)
History query to show deleted data
(it was noted that this potentially allowed the full history of an address block which one speaker thought may be a problem)
Role object no longer considered personal data (remove personal data)
Convert irt: object to role: object (and deprecate the irt: object)
Change syntax of role: to match organisation: (remove limitations on name (for example))
Allow change of person: and role: names (no legal issues)
Authenticated queries will allow unlimited access to personal data (for example)
Full re-implementation of auto cleanup including clusters of data
Deprecating object editors by using business rules to lock down appropriate fixed object parts
Server side as-set expansion (client performance improvement)
See above
See presentation
WHOIS is being replaced by WEIRDS for a number of reasons including a limited data model, no internationalisation, no authentication, no redirection and insecure.
WEIRDS covers names and numbers and uses the RDAP protocol over HTTP and HTTPS
It covers a limited number of objects. Contact should be made with the WEIRDS-WG to get additional objects added.
See presentation
The basic issue is that people do not understand the concept of a maintainer.
It would be better to group persons under a role associated with an org and use it as a maintainer.
This integrates better into SSO.
Review of Abuse Contact Stuff