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 : UDP support #163

Open
JanneKiiskila opened this issue Apr 5, 2018 · 17 comments
Open

Feature request : UDP support #163

JanneKiiskila opened this issue Apr 5, 2018 · 17 comments

Comments

@JanneKiiskila
Copy link
Contributor

JanneKiiskila commented Apr 5, 2018

As part of ARMmbed/mbed-os#6545 investigations we come to the conclusion that we have a test gap - the TLS connections are not tested with UDP (with the exception of Mbed Cloud Client) - so as such it would be really good to have both TCP and UDP as options for the TLS example.

Could it be added? It should be preferably an option you can configure from the mbed_app.json file.

What target(s) are you using? Target: Client reference boards, typically K64F, K66F,
What toolchain(s) are you using? Toolchain: GCC-ARM, ARM C 6.
What version of Mbed OS are you using (tag or sha)? cdc2d45e05622f375d222b1920a9df148c5acbab, master, Mbed OS 5.15.x and Mbed OS 6.x
It would help if you could also specify the versions of any tools you are using? N/A, varies according to Mbed OS release used.
How can we reproduce your issue: See description (new feature request).

@everhardt
Copy link

What would be especially great, is if that DTLS example could also include CoAP.

The only existing DTLS+CoAP implementations I can find are in nanostack and mbed-cloud-client, but both are too heavily entangled with other code (about IPv6 mesh networks and LwM2M respectively) for me to distill a clean DTLS+CoAP example out of it.

@simonbutcher
Copy link
Contributor

The purpose of these samples are to demonstrate the technology and use of the API. Testing is covered elsewhere.

@JanneKiiskila - Do you just want a DTLS system test for an Mbed OS board? If so, that's something else which we're already working on, and is nothing to do with this sample code.

cc: @mazimkhan

@ciarmcom
Copy link
Member

@JanneKiiskila thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.
What target(s) are you using?
What toolchain(s) are you using?
What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?
How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

@ciarmcom
Copy link
Member

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

1 similar comment
@ciarmcom
Copy link
Member

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@JanneKiiskila
Copy link
Contributor Author

@adbridge - seems to be me the BOT is teasing me for no reason, the ticket was updated.

@ciarmcom
Copy link
Member

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

9 similar comments
@ciarmcom
Copy link
Member

ciarmcom commented Nov 4, 2020

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Nov 9, 2020

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Dec 5, 2020

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@JanneKiiskila it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTOSM-3116

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

4 participants