OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (EMERGENCY-38) add a route hint to CAP messages


     [ https://issues.oasis-open.org/browse/EMERGENCY-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomer Petel updated EMERGENCY-38:
---------------------------------

    Proposal: 
Add an element called: <route> 
Every server that handles the CAP message along the way will append its "stamp" to the route.
Of course, this could break a signature, so it may not be a good idea if the message is signed by the originator, unless the originator is able to exclude the <route> element from the signature.

  was:Add an element called: <route> Every server that handles the CAP message along the way will append its "stamp" to the route Of course, this will break the signature so it may not be a good idea if the message is signed by the originator, unless the originator is able to exclude the route parameter from the signature.


> add a route hint to CAP messages
> --------------------------------
>
>                 Key: EMERGENCY-38
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-38
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>            Reporter: Tomer Petel
>
> Many times when troubleshooting or auditing, it is useful to know the route or path that the CAP message took. Assumption here is that the system is using its own custom transport protocol, and the wrapper of the CAP message is unknown. in a complex network it may be useful to know the path for optimizations and load balancing



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]