NENA ISSUE SUBMISSION & CHARTER FORM - NENA-ADM-003
Instructions for NENA ISSUE SUBMISSION FORM:
Originator to complete the top table and e-mail the form to the NENA Committee Resource Manager
(CRM). Go to https://www.nena.org/?page=nenastaff to determine contact information.
NOTE: Some fields on this form will be used to populate the Charter if this Issue is accepted and
assigned by the DSC.
To Be Completed by the Originator
Please provide input for all fields
Short title (what the Issue may easily be referred to by)
“Should” is the appropriate term for a requirement that has exceptions.
Originator Name
Brian Rosen
Originator Organization
Neustar
Originator Email
brian.rosen@neustar.biz
Originator Phone
724 382 1051
Date Submitted:
4/10/13
Description of Problem or Opportunity (Provide detailed and clear information):
In the boilerplate, we use “shall”, “must” and “required” to indicate mandatory items. The
current text uses “should”, “may”, “desirable” and “preferable” for what it calls
“recommendations”. It is not clear what a “recommendation” is. Is it a normative
conditional, or an informative helpful suggestion? In some SDOs, there are instructions for
“should” which often make it “must except under these conditions”, meaning the text must
clearly state when it is acceptable to have an alternative.
When too many alternatives are included for any kind of normative requirement, it makes it
harder to word a non-normative statement with the same level of emphasis. Could we
consider choosing one of “must” or “shall” and leaving the other for editorial comments? I
would prefer “must”, but could live with “shall”.
Of course we could choose to adopt RFC2119, which has the huge advantage that it labels
the words unambiguously (upper case).
Expected Outcome/Proposed Solution (Provide detailed and clear information):
Change in boilerplate. Here is my suggested rewrite:
The terms “must”, “must not”, “required” and “not required” are normative, mandatory requirements.
“Should” and “should not” are conditional normative requirements, and the exception conditions must be
stated clearly. “May” is a normative option. Words such as “desirable” and “preferable” are informational
recommendations.
To be even more explicit, and closer to RFC2119, I would rewrite to:
The terms “must”, “must not”, “required, “not required”, “should”, “should not” and “may” have specific
normative meaning in this document:
“must” or “required” means that the statement is an absolute requirement of the standard
“must not” or “not required” means that the statement is an absolute prohibition of the standard
Page 1 of 4
NENA ISSUE SUBMISSION & CHARTER FORM - NENA-ADM-003
“should” means that the statement is a requirement except under specific conditions, which are explicitly
stated in the standard.
“should not” is a prohibition except under specific conditions, that are explicitly stated in the standard.
“may” is a true optional requirement
Words such as “desirable” or “preferable” are non-normative suggestions.
To be Completed by NENA DSC
Issue Number
20130410
Date Assigned by DSC
04/30/2013
Referred To - Who will receive the Issue?:
If applicable, which NENA Committee will own this Issue?
☐ Accessibility ☐ Agency Systems ☐ Core Services ☐ Interconnection & Security ☐ NGTPC
☐ PSAP Operations ☐ Public Education & PSAP Training
Or specify the internal NENA owner of this Issue: Development Steering Council ADM Review Group
********************************************************************************************
Or specify which external entity it was referred to:
☐ APCO ☐ ATIS-ESIF ☐ ATIS-PTSC ☐ ATIS-WTSC ☐ IEEE ☐ IETF ☐ NFPA
OTHER ___________________________________________________________
Working Group Assigned To
(If applicable)
DSC Advisors/ADM Working Group
Estimated/Requested
Completion Date
Actual Completion Date
(to be completed later)
Resolution: (a brief explanation of how the Issue was resolved for closure)
Page 2 of 4
NENA ISSUE SUBMISSION & CHARTER FORM - NENA-ADM-003
CHARTER TO PERFORM WORK ASSOCIATED WITH THIS ISSUE
To Be Completed by the DSC and the Assigned WG
Assigned Committee & Working Group (should be based on the name
used in the Issue Submission form, and include the Parent Committee
name.)
CHARTER APPROVED BY DSC 7/28/2015
Issue Number
(from above)
Date WG Created
(if it is a new WG)
20130410
Ongoing
DSC Advisors/ADM Working Group
Goal/Objective/Deliverable (Describe each goal/objective/deliverable and provide detailed and clear
information, based on the accepted Issue.)
#1 goal/objective/deliverable: review RFC 2119 and determine its applicability
#2 goal/objective/deliverable: revise template language as desired
#3 goal/objective/deliverable: determine implementation needs – what happens with old documents
Importance (Rank each goal/objective/deliverable as Essential, Important, or Desirable as follows;
 Essential – required for something else to succeed
 Important – helpful toward the success of another work effort
 Desirable – asset for other reasons
#1 goal/objective/deliverable is ranked: Essential
#2 goal/objective/deliverable is ranked: Desireable
#3 goal/objective/deliverable is ranked: Essential Contingent upon implementation of #2
Schedule (Considering the Estimated Completion Date for the Issue, establish when each goal/objective/deliverable
should be met or accomplished, and provide detailed and clear information, based on the accepted Issue.
If applicable, list any intermediate schedule milestones, e.g., “Outline complete”, “First draft complete”.)
#1 goal/objective/deliverable: July 31, 2015
#2 goal/objective/deliverable: August 4, 2015
#3 goal/objective/deliverable: August 4, 2015
Dependencies (Identify all known dependencies for achieving success, e.g., completion of work in other committees or
other organizations outside of NENA.)
Completion of #3 is dependent upon completion of #2
Chair(s) (Who will serve as the Chair(s) for the group performing this work? Provide name, phone and email.)
Currently, Delaine Arnold or Tom Breen
Editor(s) (Who will serve as the Editor(s) for the group performing this work? Provide name, phone and email.)
Currently, Delaine Arnold or Tom Breen
Participating Organizations (Identify all outside organizations that will be needed for success of the identified
goals/objectives/deliverables, e.g., APCO, ATIS, NEIM, IHIS, etc.)
Subject Matter Expertise Needed (Identify the types of SMEs needed to achieve success.)
Page 3 of 4
NENA ISSUE SUBMISSION & CHARTER FORM - NENA-ADM-003
CHARTER TO PERFORM WORK ASSOCIATED WITH THIS ISSUE
To Be Completed by the DSC and the Assigned WG
Required Resources (Identify the types of non-human resources needed to achieve success, e.g., list server, web site, etc.)
Initial Work Schedule Plan (Identify the initial call & meeting schedule, e.g., every Tuesday at 10am EASTERN.)
Status Reporting Schedule (The Charter serves as the guiding document to drive work activities toward established
goals. Additionally, it serves as a tool to ensure timely status reports to the DSC throughout the work interval. Depending
on the nature of the work, and its impact on other work, the timing of status reports may differ among WG activities.
This field is to be used by the DSC to establish the timing of WG status reports to the DSC or designated Project Mgr(s).)
Measurement (How will each goal/objective/deliverable be evaluated? Use quantitative and/or qualitative measures
which are descriptive of the measurement criteria)
#1 goal/objective/deliverable: ______________________________________________________________
#2 goal/objective/deliverable: ______________________________________________________________
Other?
Page 4 of 4