Project

General

Profile

Actions

Feature #5647

open

cfg: separate PFCP Node ID from PFCP local address

Added by neels about 1 month ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
08/17/2022
Due date:
% Done:

0%

Spec Reference:

Description

The PFCP protocol features a Node ID, which can be used to uniquely identify
PFCP endpoints across different interfaces. The Node ID can be a fully-qualified
domain name (FQDN), or IP address. Currently, osmo-hnbgw has no support for
using an FQDN as Node ID, and requires the 'local-addr' to be configured, which
it uses as Node ID.

Instead, we should separate the concepts of which local interface to use from the Node ID sent in-band.
pfcp_endpoint.h already has separate fields in osmo_pfcp_endpoint_cfg for local_addr and local_node_id, but osmo-hnbgw only features a pfcp / local-addr config option.

osmo-hnbgw is the first PFCP CPF implementation. Since other CPF may be added in the future, it would make sense to implement the PFCP endpoint configuration bits into libosmo-pfcp, including a FQDN node id set separately from the local-addr, and then use that in osmo-hnbgw.

(Similar to how osmo-msc, osmo-bsc and osmo-hnbgw use mgcp_client_vty_init() from libosmo-mgcp-client.)


Checklist

  • implement common CPF client VTY config, #5648
  • use CPF client VTY config in osmo-hnbgw
  • update doc/manual/chapters/running.adoc

Related issues

Related to libosmo-pfcp - Feature #5648: implement common PFCP CPF client VTY configNew08/17/2022

Actions
Actions #1

Updated by neels about 1 month ago

  • Related to Feature #5648: implement common PFCP CPF client VTY config added
Actions #2

Updated by neels about 1 month ago

  • Checklist item implement common CPF client VTY config, #5648 added
  • Checklist item use CPF client VTY config in osmo-hnbgw added
  • Checklist item update doc/manual/chapters/running.adoc added
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)