Skip to content

nefd/udmd: #2152 follow-ups (29.591 notification shape, udmd-first upgrade order, JSON Pointer leading zeros) #2154

Closed

Description

@parlakisik

From R42's review of #2152 (Closes #2133):

  1. Notification shape. nefd sends T8-shaped notifications, including the new cancellation indication, to Nnef_EventExposure (TS 29.591) subscribers too. This is pre-existing for all notifications. Nnef_EventExposure subscribers should get the TS 29.591 NefEventExposureNotif shape, so route each subscription by the API it was created on.
  2. Upgrade order. A new nefd talking to an older udmd fails every refresh with 400, because the older udmd doesn't accept add /reportingOptions/expiry, and the legs then lapse. Document the order (upgrade udmd before nefd) in the release notes and the upgrade docs. Optionally, fall back to replacing the whole /reportingOptions when a 400 names the path.
  3. Nit. udmd's JSON Pointer handling accepts an array index with leading zeros (RFC 6901 §4 forbids them). Refuse it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions