Attendees & Representation
LF Staff:
Community:
| Name | Organization | |
|---|---|---|
| AT&T | x | |
| Deutsche Telekom | x | |
| Deutsche Telekom | x | |
| Ericsson | x | |
| KDDI | x | |
@Masaharu Hattori | KDDI | x |
| Nokia | x | |
| Orange | x | |
| SingTel | x | |
| Telefonica | x | |
| Telefonica | x | |
| Vodafone | x | |
| CableLabs | x | |
| GSMA | x | |
| Telefonica | x | |
| Telefonica | x | |
| TIM | x |
Agenda
The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF. |
- Discuss Issue #171 on how to simplify the existing Device Object definition so that it is fully supported by all implementations and/or provide mechanisms to make it interoperable and usable by developers.
Minutes
Work in progress - Bear with me
AOB
N/A
Action items
- Jesús Peña García-Oliva Create meeting notes in CAMARA Confluence and link them in #171
- Jesús Peña García-Oliva Document simplification proposal for next meta-release in #171
- Jesús Peña García-Oliva Include in #171 the agreed deadline (end of next week - 31/05) to provide feedback on the simplification proposal
- Jesús Peña García-Oliva As per request of fabrizio moggio , include a comment in #171 pointing reviewers to existing CAMARA API Specs already delegating to the information associated to the access_token
- Jesús Peña García-Oliva Make a text proposal for the API specs, aimed at the API consumer, on how the access_token delegation mechanism would work