2023-12-13 - sp-connectivity Minutes

Owned by Casey Cain
Last updated: Jan 25, 2024 by Kevin Smith
2 min read

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff:

Community:

Name

Organisation

Attendance

Name

Organisation

Attendance

@Mahesh Chapalamadugu

ย Verizon Wireless, 5GFF (Chair)

x

@Syed Rehman

ย Verizon Wireless

x

@Kevin Smithย 

Vodafone (Minutes)

x

Santhi Dharmapalan

ย Verizon Wireless

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.

  • Action Items Review

  • General Topics

    • ย Pull requests

  • Any Other Topics

Minutes

Action items review

  • Mahesh Chapalamadugu ย to mail the mailing list with call details and update time on GitHub 13 Dec 2023ย  DONE
    Mahesh Chapalamadugu ย to align the Connectivity Insights API spec with commonalities guidelines. 17 Jan 2024ย 
    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ย 
    Kevin Smith to add Connectivity Insights to LF CAMARA Wiki as a sub-project 13 Dec 2023ย  DONE

General topics

  • Pull requests

  • 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. Jan 17, 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. Jan 10, 2024ย 10 Jan 2024ย