Description: Section 2: Destination List - isn't that a source route? If not, what's different? If so, why not say so? Does it include the IDs through which the message has already been routed or not? Later, (in 5.1.1) I
find out that the earlier IDs are dropped, saying that here would be good. And also say that its not just Node-IDs, but also Resource-IDs, that wasn't clear 1st time.
Notes: Suggest "A list of node and resource IDs indicating nodes through which a message is to b routed, in strict order. A single Node-ID or a Resource-ID is a trivial form of destination list. When multiple Node-IDs are specified (no more than one Resource-ID is permitted, and it MUST be the last entry) a Destination List is a loose source route.
From: Stephen Farrell
Description: Section 2: Destination List - isn't that a source route? If not, what's different? If so, why not say so? Does it include the IDs through which the message has already been routed or not? Later, (in 5.1.1) I find out that the earlier IDs are dropped, saying that here would be good. And also say that its not just Node-IDs, but also Resource-IDs, that wasn't clear 1st time.
Notes: Suggest "A list of node and resource IDs indicating nodes through which a message is to b routed, in strict order. A single Node-ID or a Resource-ID is a trivial form of destination list. When multiple Node-IDs are specified (no more than one Resource-ID is permitted, and it MUST be the last entry) a Destination List is a loose source route.