Chapter 4. NISP and Configuration Management Process

20. The NISP is updated^[3] at least once a year to account for standards and profile evolution. Updates to the NISP are handled through a "Requests for Change Proposal" (RFCP) process. RFCPs are identified by stakeholders (users, C3 Board and its sub structure, SMEs, the IP CaT, and nations) and are formally submitted to the IP CaT. The IP CaT will then review the submissions either at the next scheduled meeting or via collaboration tools. After the RFCPs are considered, they may be passed to SMEs within the C3 Board sub structure or "owners" of the technology area for detailed technical review. Based on that technology review, the RFCP will be formally added to the next available version of the NISP or returned to the originator for further details or rejected. The NISP database will be immediately updated.

21. RFCPs deemed urgent are handled in an expedited manner, outside the normal meeting schedule of the IP CAT with a reply to the RFCP originator within two weeks.

22. As technology is made available, the NISP development and submission of RFCP will be automated. The ultimate goal of incorporating advanced technology will be to shorten the time required for coordination of NISP updates and reduce the effort required to produce the NISP.

23. The NISP with updates is submitted to the C3 Board in the first quarter of each year after internal review by the IP CaT. The version under review is a snapshot in time of the status of standards and profiles.

24. The database of standards and profiles maintained by the IP CaT is the definitive source of the currents status of standards and profiles. The database will be updated as soon as the RFCP has been approved by the C3 Board.