Page Comparison

...

• Pull requests

  • Open:

    • #7 Update CAMARA Connectivity Insights API.yaml fixes #6

    Merged since last call:

    • #3 initial upload of Connectivity Insights YAML
    • #4 call schedule
    • #5 update maintainers
• Issues

  • Open:

    • #6 API basepath should be human-readable: This is awaiting confirmation from Herbert that his requested changes are reflected

    • #9 Performance metric definitions do not match those of the QoD API: Agreement to adopt the QoD schema.

• Discussions

  • Discussion on whether we need for port identification at both Device and Application port side

    Agreed we would need this for Connectivity Insights between a given device and application server.
    The device IPv4 address and public port can be sent by the API consumer, but we will not need to user the private port (pre-NAT) in the API. The schema definitions will be reused from QoD.

• AOB
  • none

Action items

•  Mahesh Chapalamadugu Mahesh Chapalamadugu  to align the Connectivity Insights API spec with commonalities guidelines. 17 Jan 2024 17 Jan 2024
•  Kevin Smith Kevin Smith  to clarify if a need for consent (or a check for consent-needed) is determined by the sub-project or other body in CAMARA. 10 Jan 2024 10 Jan 2024