24315 METR |
Submit Comment Traceability Tables: |
ID | Description | Discussion | Links |
---|---|---|---|
N-2 |
Every role is implemented as a system or…
|
||
N-3 |
Each system needs a system manager
|
derived from:
SP-17 Some regions might wish to have a system…
|
|
N-4 |
Explain that the regulator role includes…
|
derived from:
SP-19 The role model should add a role between…
|
|
N-5 |
The concept of modes does not really app…
|
derived from:
SP-22 The concept of modes does not seem to ap…
|
|
N-6 |
The ConOps should reference ISO/IEC/IEEE…
|
derived from:
SP-25 The ConOps should reference ISO/IEC/IEEE…
|
|
N-7 |
The preferred implementation is that the…
|
derived from:
SP-44 The preferred implementation is that the…
|
|
N-8 |
The preferred implementation is that a u…
|
derived from:
SP-45 The preferred implementation is that a u…
|
|
N-9 |
The use of mainstream data distribution …
|
derived from:
SP-52 The ConOps should be written to allow fo…
SP-75 The term "C-ITS data source" should perh…
|
|
N-10 |
Automated discovery is a likely possibil…
|
derived from:
SP-53 The ConOps should mention that automated…
|
|
N-11 |
The preferred implementation is that rea…
|
derived from:
SP-55 To the extent that C-ITS data is exchang…
|
|
N-12 |
When showing multiplicity in diagrams ot…
|
derived from:
SP-63 When showing multiplicity in diagrams ot…
|
|
N-13 |
Remove the rule types from the state mac…
|
derived from:
SP-65 Remove the rule types from the state mac…
|
|
N-14 |
When discussing planned rules, indicate …
|
derived from:
SP-67 When discussing planned rules, indicate …
|
|
N-15 |
Change "C-ITS data source" to "dynamic d…
|
derived from:
SP-75 The term "C-ITS data source" should perh…
|
|
N-16 |
ConOps should explain that the dissemina…
|
derived from:
SP-76 The ConOps should describe why we are di…
|
|
N-17 |
The ConOps should explain that proposed …
|
derived from:
SP-77 The ConOps should provide a brief mentio…
|
|
N-18 |
The ConOps should discuss the legal aspe…
|
derived from:
SP-79 What is the legal standing of C-ITS data…
|
|
N-19 |
The ConOps should explain that the rule …
|
derived from:
SP-80 The ConOps should explain that the rule …
|
|
N-20 |
The ConOps should describe a process by …
|
derived from:
SP-87 The ConOps should describe a process by …
|
|
N-21 |
The ConOps should include a scenario tha…
|
derived from:
SP-92 The ConOps should probably stay agnostic…
|
|
N-22 |
The operational scenarios should provide…
|
derived from:
SP-118 The operational scenarios should provide…
|
|
N-23 |
Identification and responding to dynamic…
|
derived from:
SP-127 Identification and responding to dynamic…
|
|
N-1 |
METR will result in some operational cha…
|
derived from:
SP-163 For the foreseeable future, METR should …
|
|
N-24 |
Jurisdictional entities might require su…
|
derived from:
SP-189 Some jurisdictional entities might requi…
SP-199 Some jurisdictions might adopt regulatio…
|
|
N-25 |
Jurisdictional entities might require tr…
|
derived from:
SP-189 Some jurisdictional entities might requi…
SP-199 Some jurisdictions might adopt regulatio…
|
|
N-26 |
A ConOps document only defines "what" is…
|
derived from:
SP-191 The METR ConOps will only define "what" …
|
|
N-27 |
The ConOps should mention the relevance …
|
derived from:
SP-196 The information provided by METR is safe…
|