IEEE Std 1609.3-2010 pdf download – IEEE Standard for Wireless Access in Vehicular Environments (WAVE)- Network Systems Corrigendum 2: Miscellaneous Corrections.
8. WAVE information formats 8.1 General Change the second paragraph to reflect the correct reference as shown below. Over-the-air formats shall adhere to the following conventions, compatible with IEEE Std 802.11and IEEE Std 802.11p. 8.1.2 Management ID and Content Descriptor Change the text to reflect the IEEE Std 802.11 terminology convention and the correct reference as shown below. The Management ID is used by WAVE in the IEEE 802.11 Vendor Specific Action frame and Vendor Specific Information Element information element to indicate the management entity sourcing the management information. Management ID is passed across the MLMEX SAP via primitives specified in IEEE Std 1609.4. See IEEE Std 1609.120 for specification of Management ID values. For the case of WSAs, Management ID has a value of 3 indicating “1609.3.” In this case (i.e., for 1609.3 management messages), the first octet of the associated vendor-specific content is an 8-bit Content Descriptor, which is coded as shown in Table 3.
8.2.3.6.5 RCPI Threshold Change the text to reflect the correct reference as shown below. If present, the RCPI Threshold indicates the recommended minimum received WSA signal value in dBm, 0 to –110, below which the service should be ignored by a recipient. It has a length of 1 octet, coded as RCPI in IEEE Std 802.11k-2008. 8.2.4 Channel Info 8.2.4.2 Operating Class Change the text to reflect the correct reference as shown below. Operating Class is one octet as specified in IEEE Std 802.11, IEEE Std 802.11p, and IEEE P802.11REVmb, and it allows the following Channel Number to identify a specific channel uniquely in the context of a country. 8.2.5 WAVE Routing Advertisement 8.2.5.3 Router Lifetime Change the text to reflect the correct reference as shown below. Router Lifetime is 16 bits and indicates the duration for which the Default Gateway and associated information is valid. It is coded and interpreted as specified in IETF RFC 244861.