Menu ▾ ▴

#22 Ensure identifiable stream packet source

Revision-26
needs-review
Stefan Schlichting
MDPWS (1) Streaming (2)
7 days ago
2016-11-21
abesting
No

MDPWS stream packets should containt a mandatory "From" header field to ensure resolving its origin (currently, it's optional). The source IP address might not suffice to do that (multiple devices per machine).

Discussion

  • Martin

    Martin - 2016-11-21
    • Milestone: Beta06 --> 201601 - SDC Spec
     

  • Stefan Schlichting

    Stefan Schlichting - 2017-05-18
    • Added as IEEE Comment: --> False
    • Must be Satisfied: --> False
    • Line: -->
    • Page: -->
    • Milestone: 201601 - SDC Spec --> 201708 - SDC
     

  • Björn Andersen

    Björn Andersen - 2021-10-08

    Ticket moved from /p/opensdc/tickets/324/

    Can't be converted:

    • _added_as_ieee_comment: False
    • _must_be_satisfied: False
    • _line:
    • _page:
     

  • Stefan Schlichting

    Stefan Schlichting - 7 days ago
    • Owner: Anonymous --> Stefan Schlichting
     

  • Stefan Schlichting

    Stefan Schlichting - 7 days ago
    • status: unread --> needs-review
    • Milestone: 201708 - SDC --> Revision-26
     

  • Stefan Schlichting

    Stefan Schlichting - 7 days ago

    Converted the unnumbered wsa:From recommendation into a SHOULD requirement and added source-identification rationale.

    R0072: A STREAM source SHOULD include a wsa:From SOAP header block that identifies the STREAM source in each SOAP-over-UDP multicast STREAM MESSAGE.

    NOTE 2—The InstanceId attribute of the AppSequence element has HOSTED SERVICE scope and therefore cannot reliably distinguish different STREAM sources. The source IP address can also be insufficient when multiple DEVICEs or SERVICES share a host. Including wsa:From supports source identification, filtering, diagnostics, and correlation by STREAM sinks

     
Auth0 Logo