clarification section 4.1

[mglt]

4.1. UAS Remote Identifiers Problem Space

"""
The data communication of using Broadcast RID faces extreme
challenges due to the limitation of the demanding support for

"""
I think that removing "The data communication of using" makes the message clearer.

"""
message. The Basic RID message has a maximum payload of 25 bytes and
the maximum size allocated by ASTM for the RID is 20 bytes and only 3
bytes are left unused. currently, the authentication maximum payload
is defined to be 201 bytes.

"""

The text is not clear to me. The Basic RID message is expected to carry the RID, so I expect its size to be greater the RID. This seems fine with the RID with a maximum size of 20 bytes versus the message being of up to to 25 bytes.
I would consider that the remaining unused bytes could be up to 5. The text mentions 3 bytes are left unused, but it is unclear to me to which these 3 bytes belong to the message of the RID and whether this information is related to the previous numbers. I believe some clarifying text needs to be provided.

[ShuaiZhao]

4.1. UAS Remote Identifiers Problem Space

"""
The data communication of using Broadcast RID faces extreme
challenges due to the limitation of the demanding support for

"""
I think that removing "The data communication of using" makes the message clearer.

@mglt How about we say "The Broadcast RID data exchange faces extreme challenges due to...." or you prefer your suggested version?

"""
message. The Basic RID message has a maximum payload of 25 bytes and
the maximum size allocated by ASTM for the RID is 20 bytes and only 3
bytes are left unused. currently, the authentication maximum payload
is defined to be 201 bytes.

"""

The text is not clear to me. The Basic RID message is expected to carry the RID, so I expect its size to be greater the RID. This seems fine with the RID with a maximum size of 20 bytes versus the message being of up to to 25 bytes.
I would consider that the remaining unused bytes could be up to 5. The text mentions 3 bytes are left unused, but it is unclear to me to which these 3 bytes belong to the message of the RID and whether this information is related to the previous numbers. I believe some clarifying text needs to be provided.

@mglt F3411-19 defined Basic ID has 20 bytes UAS ID message + 1 byte header for UA ID info + 3 bytes reserved for others play around. Are those the details you suggest we should add as background info?

[mglt]

The modified sentence is fine to me.

Your wording is clarifying. I understand the F3411-19 defines the Basic RID which is composed of a 20 byte UAS ID message field, a 1 byte UA ID info field and an additional 3 bytes (unspecified ?) or left for additional usages.
I think that is sufficient, I am however wondering why the size of the Basic RID is mentioned to be a maximum size of 25 bytes

[cardsw]

How long the payload is depends on which of many nested layers you are considering. The most commonly cited length of ASTM F3411 Broadcast RID message payloads is 25 bytes, including a 4 bit Message Type and 4 bit Version. The Basic ID message has a 4 bit ID Type, 4 bit UA Type, 20 byte UAS ID and 3 reserved bytes. F3411 Authentication messages can be "paged" (segmented), for up to 201 bytes of auth. data, the first of which is the Specific Auth. Method (SAM) type. Perhaps we should just lay that out, succinctly, somewhere early in -arch, presumably Section 4.1?

[ShuaiZhao]

> Editor-note 7: To be more specific about the RID message header and payload structure, such as 1) list different type of BRID messages defined in ASTM F3411, 2) how many bytes for each filed.

[mglt]

The text proposed by @cradsw is clear on how we have 25 byte message with a 20 byte RID.

[ShuaiZhao]

implemented as following:

The Broadcast RID data exchange faces extreme challenges due to the limitation of the demanding support for Bluetooth. The ASTM {{F3411-19}} defines the basic RID message which is expected to contain certain RID data and the Authentication message. The Basic RID message has a maximum payload of 25 bytes and only 3 reserved bytes are left unused. currently, the authentication maximum payload is defined to be 201 bytes.