search

ietf-teep / teep-over-http

HTTP Transport for TEEP
2 stars 5 forks source link

RequestPolicyCheck API and multiple TAMs #32

Closed dthaler closed 3 years ago

dthaler commented 3 years ago

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 commented 3 years ago

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

dthaler commented 3 years ago

Fixed in draft -10