[PATCH] NAN: Send synchronized service SSI also in SDA Service Info

Paul Hu paulhu at google.com
Mon Nov 16 23:25:36 PST 2026


Hi Andrei,

> The spec says (4.1.3):
> "[..]
> The service_specific_info from the Publish command are put into **either**
> the Service Info field of the SDA or the Service Info field of the SDEA.
> (Note that, due to the size limit of the Service Info field of the SDA, if
> the service_specific_info is longer than 255 bytes, the Service Info field
> of the SDEA should be used)
> [..]
> "
> I think *either* wording implies that only one option shall be used. It may
> also confuse the receiver side how to interpret and report both SSI fields.
> If it's needed for legacy devices support that don't parse SSI out of SDEA,
> I would put it only in SDA instead (if the SSI is short enough).

Thanks for the review. Agreed -- duplicating the SSI in both the SDA and the
SDEA goes against the "either ... or" wording and could be ambiguous for
receivers.

Following your suggestion, v2 changes synchronized NAN services to carry SSI
of up to 255 octets only in the SDA Service Info field by default, and to use
the SDEA Service Info field when the SSI exceeds 255 octets.

There is also one case where a <= 255-octet SSI still needs to be carried in
the SDEA instead of the SDA: protocols (such as NAN Pairing discovery using
Service Protocol Type = Generic with sub-attribute TLVs per Section 9.6.1)
where the peer requires the SDEA Service Info wrapper (WFA OUI + Service
Protocol Type) and ignores the SDA. To support that without duplicating the
SSI across both attributes, v2 adds an opt-in ssi_in_sdea parameter (still
putting the SSI in only one of SDA or SDEA).

I have sent [PATCH v2] ("NAN: Send synchronized service SSI in SDA by
default") to the list.

Thanks,
Paul



More information about the Hostap mailing list