The Navelink Developer forum held on the 25th of May 2023 lifted the updates of the G1128 schemas, the implementation of MIR (Maritime Identity Registry) version 1.2.0 in the internal environment, and Navelink’s recommendation to submit functional email addresses as contact information within the Service Registry. Mikael Olofsson, Navelink’s Head of Concept, also held a How-to presentation about certificate management and the creating and signing of keys using Navelink. 


Update of G1128 Service Documentation Schemas to Version 1.3 

There is a difference between the earlier and the updated version of the G1128 schemas that came into effect in September 2022. The discussion during Developer forum surrounded whether Navelink should keep supporting version 1.0 as the minimal version or only use 1.3 as the minimal version. The question was discussed whether there are reasons for supporting the older version. For now, Navelink supports both versions. One of the differences between the two versions is that within version 1.0 the service instance XML contains the field ‘URL’ while in version 1.3 the same field is called ‘endpoint’. Navelink users are encouraged to control how a complete removal of the name ‘URL’ would affect their implementations of the G1128 schemas. The JSON part in response from Get Instance and Search Instance is unchanged and continues to name the field ‘endpointUri”. 


Implementation of MIR Version 1.2.0 in the Internal Environment 

Since the previous Developer forum, MIR version 1.2.0 has been implemented in the internal environment. Official releases will be awaited before implementing the updated version in the DEV, TEST and PROD environments, which is expected to occur after the summer. The main impact on functionality is the removed API operation to create a private key on the Navelink server. The rationale is to avoid transit of private keys on internet. The solution that remains is to create the private key in a local browser or in your own computer environment (manually or by tool). The public part is then sent to Navelink for signing and storage (CSR=Certificate Signing Request).  


Navelink Recommends Using Functional Email Addresses as Contact Information in the Service Registry 

The majority of Navelink users have submitted functional emails as their organization’s contact information in the Service Registry. There are still a few users who have submitted their private email addresses for this purpose. Navelink urges the use of functional emails as contact information in the Service Registry to ensure that reports and feedback on the services reach the organization, as well as for the sake of protecting personal information.  

As for the Identity Registry, where the emails are used as login, the current use of personal accounts will be kept, in order to comply with authority regulations and standards. Since the personal accounts are protected by login, the aspect of security is dealt with.  


Route Exchange with S-421 in ECDIS  

Navigation, Communication, Search and Rescue (NCSR) is a subcommittee under the International Maritime Organization (IMO). Recently, the committee has granted approval to the proposal put forth by the Swedish Maritime Administration (SMA) regarding the mandatory implementation of route exchange using S-421. In terms of incorporating route exchange through S-421 into Electronic Chart Display and Information Systems, ECDIS, it is planned to be recommended starting from 2024 and mandated by 2029. 

Per Löfbom from SMA emphasizes that route sharing serves as a fundamental aspect of numerous upcoming maritime services. Additionally, Löfbom highlights the significance of SECOM (Security Communication) as an integral component of these endeavors. Moving forward, SMA’s primary focus revolves around two ongoing projects related to route exchange: 

  1. Upgrading the Vessel Traffic Service (VTS) system to meet the necessary requirements for Sea Traffic Management (STM) functionality. 
  1. Providing Navigational Assistance from Shore (NAS) and implementing S-421 for route sharing purposes for vessels approaching Gothenburg. 

SMA will use Navelink, which adheres to SECOM standards, as the platform for publishing these services. 


Navelink’s First How-To Presentation 

Mikael Olofsson, the Head of Concept at Navelink, held a How-to presentation about certificate management and how to create keys and get them signed. Navelink welcomes your feedback on the concept of How-to presentations as well as your input on which topics you would like How-to presentations about. 

You can study the complete How-to guide here.


Navelink’s next Developer forum will be held on the 22nd of June 2023.  


Author: Milena Dalinaros