Page History

...

• Parses the JSON response to extract all configuration parameters.

• Updates TR-181 parameters by invoking tr181 set commands for each relevant RFC value.

• tr181 set uses RFC API which in turn calls the tr69hotif API to store these environment variables and TR-181 parameters.

...

5. tr181 Set and RFC API

• The tr181 set commands internally call the RFC API to perform parameter get/set operations.

• The RFC API communicates with the local HTTP server running within tr69hostif using HTTP GET or POSTrequests.

• tr69hostif uses the below files for storing the configuration:

  /opt/secure/RFC/rfcVariable.ini	RFC environment variables	Contains environment-level variables derived from RFC config
  /opt/secure/RFC/tr181store.ini	RFC namespace TR-181 parameters	Contains TR-181 parameters managed within the RFC namespace
  /opt/secure/RFC/bootstrap.ini	Bootstrap TR-181 parameters	Contains TR-181 parameters with the bsUpdate attribute
  Profile-specific storage	Non-RFC TR-181 parameters	Managed by respective profile handlers with their own storage mechanism

  
  

...

56. tr69hostif Request Routing

• The tr69hostif component routes incoming parameter requests based on their namespace or attributes:

  bsUpdate attribute present	Bootstrap handlers	Handles bootstrap get/set requests
  RFC namespace	RFC handlers	Manages parameters controlled by RFC
  Other (non-RFC) parameters	Profile handlers	Routed to profile-specific get/set implementations

...

7. mTLS support

• RDKE expects xconf connections to be secure. This expects RFC to use MTLS by default.
• Support to add MTLS to RDKM xconf server is under investigation.
• Until then, we are disabling MTLS support by not enabling rdkcertselector
  • mTLS is enabled in the RFC code when the macro LIBRDKCERTSELECTOR is defined.

...