Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
dreibh opened this issue Jul 15, 2017 · 6 comments
Open

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

dreibh opened this issue Jul 15, 2017 · 6 comments

Comments

@dreibh
Copy link
Contributor

dreibh commented Jul 15, 2017

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
Copy link
Member

Will you implement it?

@marceloleitner
Copy link

I can give it a try.

@marceloleitner
Copy link

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
Copy link
Contributor

tuexen commented Mar 18, 2018

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
Copy link

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
Copy link
Contributor

tuexen commented Mar 19, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants