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.

Sign up for GitHub

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

Jump to bottom

RequestPolicyCheck API and multiple TAMs #32

Closed
dthaler opened this issue Jan 8, 2021 · 2 comments · Fixed by #33
Closed

RequestPolicyCheck API and multiple TAMs #32

dthaler opened this issue Jan 8, 2021 · 2 comments · Fixed by #33
Assignees
@tireddy2
Labels
ready to close Authors believe this issue has been addressed

Comments

@dthaler
Copy link
Collaborator

dthaler commented Jan 8, 2021

As shown in Figure 1 of the TEEP architecture doc, a TEEP Agent may need to talk to multiple TAMs (e.g., one to get a TA, and a second one to get personalization data).

The TEEP-over-HTTP spec currently says:

The TEEP/HTTP Client informs the TEEP Agent by invoking an appropriate "RequestPolicyCheck" API.
The TEEP Agent will either (a) pass no data back, (b) pass back a TAM URI to connect to, or (c) pass back a message buffer and TAM URI to send it to.

The question is if the API can only pass back "a" TAM URI, then how does it conduct policy checks with multiple TAMs?
@dthaler
Copy link
Collaborator Author

dthaler commented Jan 8, 2021

This will also affect the TEEP protocol spec once https://github.com/ietf-teep/teep-protocol/pull/87/files is merged.

This was referenced Feb 18, 2021
Closed
Merged
@dthaler dthaler reopened this Feb 20, 2021
@dthaler dthaler added fixed in editors copy Fixed in github awaiting I-D submission and removed have proposed text labels Feb 20, 2021
@dthaler
Copy link
Collaborator Author

dthaler commented Feb 22, 2021

Fixed in draft -10

@dthaler dthaler added ready to close Authors believe this issue has been addressed and removed fixed in editors copy Fixed in github awaiting I-D submission labels Feb 22, 2021
@tireddy2 tireddy2 closed this as completed Mar 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tireddy2 tireddy2

Labels
ready to close Authors believe this issue has been addressed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Handle multiple TAMs with RequestPolicyCheck API ietf-teep/teep-over-http
2 participants
@dthaler @tireddy2