2024-08-09 Network Access Management - Meeting Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: 

Community: @Christopher Aubut @Randy Levensalor @Justin Pace 

Agenda

• Antitrust Policy

• Review of previous meeting minutes

• Overall Topics

• Regular Topics

  • Closed PRs and Issues

  • Open Pull Requests

  • New Issues

  • Open Issues

• Any Other Topics

Minutes

Review of previous meeting minutes

• Previous meeting minutes: N/A

  • no comments

Overall topics

• Target: Agree / approve the PR for r1.1, plan next steps until final release (PR due on August 26th)

• Current status: 

  • #18 Scope of NetworkAccessManagement for Fall24 CAMARA release

Closed PRs and Issues

• PR #1 Update README.md

• #2 CODEOWNERS file contains errors

• PR #3 fix: removes trailing substitution marker from mailing list contact

• #4 Add linting for Camara rules

• PR #5 Add linting for OpenAPI and Camara guidelines

• PR #6 Change Sub Project name in Readme

• PR #7 chore: adds initial proposal from the backlog working group

• #8 Add yamllint and spectral config files

• PR #9 Adding config files for spectral and yamllint

• #10 Missing additional linting files

• PR #11 Moving the linting fixes from init to new PR

• #20 ICM pass for corrections

• PR #21 Updating mandatory ICM tex

• #22 Add Ben Hepworth as maintaner so he can review PRs

• PR #23 Add benhepworth as maintainer so he can review PRs

Open Pull Requests

• PR #17 Create release v0.1.0

New Issues

• #12 Add HATEOAS links

• #13 Clarity on fine-grained and role-based scope format

• #14 Remove CPE to remove network specific terms

• #18 Scope of NetworkAccessManagement for Fall24 CAMARA release

• #19 Commonalities pass for corrections

Issues 

• N/A

Review scope and time plan for Release Candidate

• #18 Scope of NetworkAccessManagement for Fall24 CAMARA release

  • #19 Commonalities pass for corrections

    • The following areas are known to be needing a review:

      • Add use cases / user stories.

      • Update return codes.

      • Add test files.

      • Review other notes from @Justin Pace 

Any other topics

• @Randy Levensalor There is language regarding omitting the device using three-legged auth.  @Christopher Aubut mentioned this API has a default default mode that does the same.  Need to review for alignment with commonalities / ICM.

• @Christopher Aubut Review Commonalities and DeviceIdentifier to look for overlap with NAM.

  • Charter and CableLabs are looking at expanding the scope of this API, so any overlap with other CAMARA APIs should be considered. 

• @Randy Levensalor Optional endpoints should be split into different OpenAPI spec files.  All endpoints in a file should be implemented.

• @Christopher Aubut It was mentioned on yesterday's Backlog call that the notion of API Families is going away calling into question if NAM fits as part of Home Devices any more.

  • From the Backlog call:

    • API may be split into multiple endpoint files aligning with previous comment from @Randy Levensalor.

    • Endpoints may share or be split into multiple repos with different CODEOWNERS / MAINTAINERS.

    • The same meeting should be used for all endpoints, which is not currently done with Home Devices QoD.

Action items 

• @Christopher Aubut will work on Commonalities pass for release.

• Open an issue for splitting the endpoints into different files were appropriate.

• Open issue for default device alignment with Commonalities.