View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010383 | Part 82: UAFX Networking [sg.Networking] | Spec | public | 2025-06-25 07:40 | 2025-07-16 14:03 |
| Reporter | Jan Murzyn | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Target Version | NextMaintenance | ||||
| Summary | 0010383: Don't mandate existence of the PriorityMappingTable methods by specification. | ||||
| Description | In Part 82, clause 6.5.4 there is a text: "The referenced PriorityMappingTableType instance shall include the AddPriorityMappingEntry and DeletePriorityMappingEntry Methods." During the F2F meeting in Esslingen it was decided to change the shall to should. By doing so, the methods won't be mandatory anymore, until the Conformance Unit is added which will explicitly mandate them. This should not happen before the behaviour of the methods is clarified in Part 22 and prototyping is completed. | ||||
| Tags | No tags attached. | ||||
| related to | 0010384 | assigned | Thomas Enzinger | 10000-022: Base Network Model | Clarify behaviour of PriorityMappingTable Methods. |
| related to | 0010385 | new | Part 84: UAFX Profiles | Restructure Conformance Units around PriorityMappingTable Methods. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-25 07:40 | Jan Murzyn | New Issue | |
| 2025-06-25 09:43 | Jan Murzyn | Note Added: 0023035 | |
| 2025-07-16 12:10 | Bob Lattimer | Relationship added | related to 0010385 |
| 2025-07-16 12:32 | Bob Lattimer | Relationship added | related to 0010384 |
| 2025-07-16 14:03 | Paul Hunkar | Target Version | => NextMaintenance |
