search

NEAT-project / neat

A New, Evolutive API and Transport-Layer Architecture for the Internet
https://www.neat-project.org/
BSD 3-Clause "New" or "Revised" License
66 stars 19 forks source link

Feature request: support for setting/obtaining SCTP PPID #343

Open dreibh opened 7 years ago

dreibh commented 7 years ago

It is currently not possible to set/obtain SCTP PPID when using SCTP transport. It would be useful to have an option for setting/getting the PPID.

weinrank commented 7 years ago

Will you implement it?

marceloleitner commented 6 years ago

I can give it a try.

marceloleitner commented 6 years ago

Should we really implement this? Asking because we will have to have the counterparts for all other transports, and currently one can just prepend the PPID to the message itself and it should work.

tuexen commented 6 years ago

I think this can only be implemented for SCTP. So if you are trying to set this on a non-SCTP transport, it could report a non-fatal error. If you are using neat for an application especially using SCTP, it might be useful... So for example, if you are using neat to implement Diameter/TCP or Diameter/SCTP it would be useful, if in the case of Diameter/SCTP the corresponding PPID would be used.

marceloleitner commented 6 years ago

What do you mean with 'non-fatal error'? If it is for logging an error but move on as if nothing had happened, it may lead to application issues if the receiver side try to validate it, I suppose.

tuexen commented 6 years ago

Rethinking... If a different transport is chosen, the application should not be notified.