a question about the USP requirement

[believe209]

I am a developer of Calix and I am now integrating obuspa in our router device.

When I am studying the requirement ( link : https://usp.technology/specification/03-index-discovery.html#r-dis.1a) , I get a little uncertain about below:

R-DIS.1a: The Agent MUST decode all received options as strings (provisioning code, wait interval, and interval multiplier are not decoded as numeric fields).

Does it mean the sub options 25,26,27,28 and 29 in both DHCPv4 125 and DHCPv6 17 option are all coded as an ascii string? For example, the value of Device.LocalAgent.Controller.{i}.USPNotifRetryMinimumWaitInterval should be a string type “12345” other than an integer type 12345.

3.3.1 DHCP Options for Controller Discovery 

Encapsulated Option	DHCPv4 Option 125	DHCPv6 Option 17	Parameter in the Device:2 Data Model [38]
URL or FQDN of the Controller	25	25	Dependent on MTP
Provisioning code	26	26	Device.LocalAgent.Controller.{i}.ProvisioningCode
USP retry minimum wait interval	27	27	Device.LocalAgent.Controller.{i}.USPNotifRetryMinimumWaitInterval
USP retry interval multiplier	28	28	Device.LocalAgent.Controller.{i}.USPNotifRetryIntervalMultiplier
Endpoint ID of the Controller	29	29	Device.LocalAgent.Controller.{i}.EndpointID

[timspets]

This is an original requirement, I would need to verify (I assume) that it is sent over DHCP in ascii.

All USP communication is a string , does that answer the other question?

If you still need further assistance, please either put in a JIRA ticket in BUS or try the USP questions on slack (wider audience)

[believe209]

what's the result of verify whether the sub options 25,26,27,28 and 29 is sent over DHCP in ascii ? @timspets

[timspets]

Hi - please ask the question here, will be easier to reply in detail

https://broadband-forum.slack.com/archives/C017V6HCYMN