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

requestedtalist needs to be added to GetDeviceStateResponse #2

Open
dthaler opened this issue Nov 8, 2018 · 2 comments
Open

requestedtalist needs to be added to GetDeviceStateResponse #2

dthaler opened this issue Nov 8, 2018 · 2 comments

Comments

@dthaler
Copy link
Collaborator

dthaler commented Nov 8, 2018

Per hackathon report at IETF 103

@dthaler
Copy link
Collaborator Author

dthaler commented Mar 24, 2019

Need to define the actual syntax. As a strawman, I would propose it be placed immediately under the "tee" node, and have a value with the same syntax as "talist", i.e.,

"tee": {

"requestedtalist": [
{
"taid": "",
"taname": "" // optional
}
]
}

@dthaler
Copy link
Collaborator Author

dthaler commented Mar 24, 2019

Actually in implementing it, I realize the strawman above is likely not sufficient, since there's two cases:
(a) The device has the TA binary and just needs the metadata, and
(b) The device needs both the TA binary and the metadata

It seems the message should have a way to specify which is the case, to avoid wasting resources transferring a TA binary the device already has. Perhaps another field in parallel with taid and taname, e.g., "havebinary": true/false, which if absent, defaults to false?

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

No branches or pull requests

1 participant