Task Description

Task name :

Continue development on MRN documentation, considering inputs from IALA Secretariat, other committees, or others as needed

Leading committee and working group owning the task: ARM WG 2
Tasks associated (*leading) :
Task Leader : LeeAnne Gordon
Task Number : ARM-7.1.7
Standards : S1070 Information Services
Topic area : S1070.1 Data models and data encoding
Task Description :
Objectives of the task :

Review and revise MRN Guidelines and Recommendation as needed, publishing edition 2.0 and continuing development throughout the work plan

Expected outcome :

Revised Guideline

Compelling need :
Strategic Alignment :
Scope :
Cybersecurity related :

No

Brief and concise description of the work : to be undertaken and programme mile-stones (where appropriate).
Expected numbers of sessions for completion :
453 Session 17 453 Session 18 453 Session 19 453 Session 20 453 Session 21 453 Session 22 453 Session 23
v v v v v v v

Meaning of symbols for sessions :

v + x > <
Scheduled Progressed Not progressed Finalised On hold
Committee notes : Origins :
Approved by Council (Council session/Date) : 0
Notes from the council :
Status (Text) :
Status (Color) :
On track
Remarks :

History of the task :

2024-11-18 14:47:18

2024-11-19 10:37:42

ARM19, The Task Group discussed four input papers on MRN from DTEC and VTS. Both Committees expressed concerns with elements of the MRN documentation. During discussions, there were concerns that members of the other Committees may be misinterpreting the MRN documents, or misunderstanding IALA’s two-fold role with MRN. IALA has the role of prescribing procedures for adoption of MRN within its remit, which is covered in IALA Guideline G1143. As the owner of MRN, IALA also has the responsibility to allocate MRN namespaces to other interested parties, and to prescribe procedures for requesting those. This responsibility is documented in IALA Guideline G1164. The Task Group noted that there may be an overall lack of awareness and familiarity with MRN across IALA Committees, which may result in the misinterpretations and misunderstandings. In this case, better awareness of MRN is needed. In addition, the input from the DTEC Committee included a path of action for an IMO Submission on MRN. The Task Group supported the proposed plan of action, but agreed further work should be done by a cross-Committee Intersessional Work Group. The Task Group concluded that intersessional work is warranted, and outlined some suggestions to inform and scop this intersessional work. A Liaison Note to PAP and all committees was created, to identify participants to work intersessionally, and to request use-cases and other information for intersessional discussions.

2024-11-19 10:37:42

ARM19, The Task Group discussed four input papers on MRN from DTEC and VTS. Both Committees expressed concerns with elements of the MRN documentation. During discussions, there were concerns that members of the other Committees may be misinterpreting the MRN documents, or misunderstanding IALA’s two-fold role with MRN. IALA has the role of prescribing procedures for adoption of MRN within its remit, which is covered in IALA Guideline G1143. As the owner of MRN, IALA also has the responsibility to allocate MRN namespaces to other interested parties, and to prescribe procedures for requesting those. This responsibility is documented in IALA Guideline G1164. The Task Group noted that there may be an overall lack of awareness and familiarity with MRN across IALA Committees, which may result in the misinterpretations and misunderstandings. In this case, better awareness of MRN is needed. In addition, the input from the DTEC Committee included a path of action for an IMO Submission on MRN. The Task Group supported the proposed plan of action, but agreed further work should be done by a cross-Committee Intersessional Work Group. The Task Group concluded that intersessional work is warranted, and outlined some suggestions to inform and scop this intersessional work. A Liaison Note to PAP and all committees was created, to identify participants to work intersessionally, and to request use-cases and other information for intersessional discussions.

2024-11-19 10:38:05

2024-11-19 10:38:05