Known Problems


- downloading a LORDN-log more than once a minute will return http result 
  code 500 instead of 429 with content 'Too frequent download rate, try 
  again in 1 minute'



Release notes

2016-07-01
----------

- DNL, SMDRL, LORDN: return HTPP 401 instead of 500 when source ip not in whitelist


2014-12-18
----------

- Sunrise List : fix for missing labels of marks of type "protected by
  treaty or statute" and "court validated"

2014-08-29
----------

- LORDN processing : LORDN files will be accepted after the end of the 
  sunrise and claims periods.

2014-07-11
----------

- integration of OT&E with TMCH OT&E

2014-07-04
----------

- fix duplicate rows in sunrise list

2014-06-20
----------

- fix Contact link when logged in as registry.
- Update format of CNIS lookup keys to latest version of technical spec.

2014-06-13
----------

- Add Cache-Control header.
- Eliminate possible delay in publication of DNL file.

2014-06-03
----------

- Implement LORDN resultcode 3617 based on
  http://newgtlds.icann.org/en/about/trademark-clearinghouse/scsvcs/
  db-registrar-certified-latest.csv.
- LORDN resultcode 4602 : use 
  http://www.iana.org/assignments/registrar-ids/registrar-ids-1.csv
  as list of registrar IDs instead of token file.

2014-05-02
----------

- Support for the new LORDN resultcode 3619 and change to resultcode 
  3605 as described in draft-lozano-tmch-func-spec-09.

2014-04-18
----------

- Support for Qualified Launch Program Periods as described in 
  draft-lozano-tmch-func-spec-09.
  Support for the new LORDN resultcode 3619 and the change to resultcode 
  3605 is not yet included.

2014-02-28
----------

- Do not create NORDN messages for LORDN lines that are duplicates 
  (resultcodes 3602 and 3603).

2014-02-21
----------

- Allow CIDR blocks in TMDB service settings used for whitelisting.
  This is a per-TLD and per-registrar setting that has to be enabled via
  the service desk.
- Use the latest POC_email set by the ICANN token file instead of the one 
  that was active at time of registration in the password reset procedure.

2014-01-24 
---------- 

- Validate that a LORDN file with the same <LORDN creation datetime> of a
  previously received LORDN file contains the same information of the 
  previously received LORDN file before responding with the LORDN 
  transaction identifier. 

  The rationale for the change is the following: in the OTE, we found 
  LORDN files that by mistake contain the <LORDN creation datetime> of a 
  previous file, the new file will not be processed because the identifier 
  is the same of a previous file.

  The new algorithm is as follows : 
  after receiving a syntactically valid LORDN file with a 
  <LORDN creation datetime> of a previously received LORDN file:
  - If the previously received LORDN file was uploaded with a different 
    type (sunrise or claims), send an HTTP/400 with the following message 
    in the HTTP Entity-body: 
      "A LORDN file with this <LORDN creation datetime> was already 
      uploaded with type [type]" 
  - If the previously received LORDN file was uploaded with a different 
    number of lines, send an HTTP/400 with the following message 
    in the HTTP Entity-body: 
      "A LORDN file with this <LORDN creation datetime> was already 
      uploaded with a different number of lines" 
  - If the contents of the data lines is different after sorting the lines 
    alphabetically, send an HTTP/400 with the following message in the 
    HTTP Entity-body: 
      "A LORDN file with this <LORDN creation datetime> was already 
      uploaded with different data" 
  - If the contents of the LORDN files is the same, send the LORDN 
    transaction identifier. 

  This change will be reflected in the new version of 
  draft-lozano-tmch-func-spec.

2013-12-06
----------

- Allow registrars to access the OT&E DNL service
- Allow registries to access the OT&E CNIS service
- Add 'release notes' page to public web site
- LORDN service : return an error when the TLD in the upload url does not 
  match the TLD linked to the service user that was used to connect to the
  service
- DNL service : fix time format for labels that are inserted for the first 
  time in the list

2013-11-15
----------

- Use the <LORDN creation datetime> element of the LORDN file as a unique
  client-side identifier as in v07 of the technical specification.
- The validation of the IANA ID within the LORDN file in the OTE has been 
  removed.
- Align the LORDN processing with v08 of the technical specification : 
  remove checks for error codes 4604 and 4605 and add 3616.

2013-10-25
----------

- allow Sunrise LORDN entry without "application-datetime" but with comma
  at the end
- allow empty LORDN files (with only the 2 header lines)

2013-10-18
----------

- support for abused labels
- fix for cnis url : .xls added
- LORDN processing : match SMD revocation against SMDRL insertion time
  rather then the real revocation date

2013-09-27
----------

- use datetime of first insertion in SMDRL insertion-datetime field
- use datetime of first insertion or datetime of re-insertion in DNL
  insertion-datetime field
- check 'recent-dnl-insertion' against dnl at time of application or
  registration

2013-09-18
----------

- fix for SQL error in registration of registrars

2013-09-13
----------

- support 'recent-dnl-insertion' in LORDN
- fix date formats in DNL and SMDRL
- fix sunrise & claims start & end date related checks in LORDN processing

2013-09-09
----------

- convert test tld's to lowercase

2013-09-06
----------

- use noreply@marksdb.org instead of noreply@trademark-clearinghouse.com as
  from address in emails

2013-09-05
----------

- claims support : DNL and CNIS
- fix for problem registering uppercase (test)-tld's
- fix for LORDN processing where error 3609 was returned instead of 3613
- allow TMCH provider ID up to 5 digits in smd-id field of LORDN
- return 429 instead of 403 on Too many requests for LORDN-LOG download
- return correct http result codes for LORDN upload and LORDN-LOG download