Timeline with dates and status
Below is the timeline with scheduled dates for activities and milestones in the project. The timeline will be updated when an activity is completed or changes occur. The dates are tentative and may be adjusted if necessary.
|April 26, 2017||The proposed changes to the data model were presented at the registrar seminar, and published on Norid’s web.||Done|
|May 11, 2017||
Email was sent to the registrars with information about changes in data model. The deadline for submitting comments to the changes was set to 31 May 2017.
|June 2017||Norid reviewed all received comments to see if these would result in any adjustments of the thought changes.
We received a few comments, which were thoroughly discussed and evaluated. The conclusion was that none of the comments resulted in any changes. However, it was decided that the abuse contact should not be introduced. The changes in the data model will otherwise be as stated in the proposed changes.
|June 28, 2017||Information about adopted new data model and the process for the introduction of the data model is published. Registrars are informed by email and web.||Done|
|August – October 2017||The changes are documented, implemented and tested internally by Norid.||Done|
|Mid October 2017||Strategy for forced data conversion is determined and describing information is published.||Done|
|October 2017||Updated interface documentation for the new data model is published.||
Done (minor changes may come)
|November 1, 2017||
A new test system running the new data model is offered to the registrars. The new test system will be configured with a copy of the current test database. The current test system is kept and will offer the old data model.
The service addresses for the new test system are listed below:
|November 30, 2017||A change in the data model has been decided. It will be a requirement that all technical contacts for delegations and name servers are role contacts. Relevant interface documentation is updated.||Done|
|December 5, 2017||A detailed description (in English) of the changes are published, see Datamodell-revidert-en-v2.pdf||Done|
|November 2, 2017 – January 8, 2018||Data conversion period in the new test system. The registrars are given the chance to update their data objects to match new data model. The new test system will need to support both new and old data models to support those updates. Registrars are given a deadline for January 8, 2018 to update their data. Data objects that are not updated within the deadline will be forcibly converted.||Done|
|January 9, 2018||
Forced data conversion in the new test system. Norid performs a forced data conversion on the remaining data objects in the new test system which do not conform to the new data model. This includes deleting all relationships and fax numbers, and organizational objects that are used for delegations are merged with their legal-c object.
Note: From now on, the new test system only supports the new data model.
|November 2, 2017 – March 5, 2018||Registrars should adapt their own systems to the new data model and test against the new test system.||Ongoing|
|March 6, 2018||The new data model is put into production.|
|March 6, 2018 – April 24, 2018||Data conversion period in the production system. The registrars are given the chance to update their data objects to match new data model. The production system will need to support both new and old data models to support those updates. Registrars are given a deadline for April 24, 2018 to update their data. Data objects that are not updated within the deadline will be forcibly converted.|
|April 25, 2018||Forced data conversion in the production system. Norid performs a forced data conversion for remaining data objects in the production system that violates new data model. This includes deleting all relationships and fax numbers, and organizational objects that are used for delegations are merged with their legal-c object. From now on, the production system only supports new data model.|
|April 25, 2018 and beyond||The production system is running with the new data model. The project monitors the result and performs corrections if necessary.|
|May 2018||The project ends.|