IEEE Std 1722-2011 pdf download – IEEE Standard for Layer 2 Transport Protocol for Time-Sensitive Applications in Bridged Local Area Networks.
3. Terms, definitions, and notation For the purposes of this document, the following terms and definitions apply. The IEEE Standards Dictionary: Glossary of Terms & Definitions should be consulted for terms not defined in this clause. 5 3.1 Conformance levels Several keywords are used to differentiate between different levels of requirements and optionally, as follows: may: Indicates a course of action permissible within the limits of the standard with no implied preference (“may” means “is permitted to”). shall: Indicates mandatory requirements strictly to be followed in order to conform to the standard and from which no deviation is permitted (“shall” means “is required to”). should: An indication that among several possibilities, one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of action is deprecated but not prohibited (“should” means “is recommended to”). 3.2 Definitions Audio/Video Transport Protocol (AVTP): The protocol defined by IEEE Std 1722-2011. As an adjective, it indicates that the modified noun is specified in or interpreted in the context of this standard. audio/video bridging (AVB) bridge: A bridge that implements IEEE Std 802.1Q TM -2005 as amended by the Stream Reservation Protocol (SRP), Forwarding and Queuing Enhancements for Time Sensitive Streams (FQTSS), and implements the generalized Precision Time Protocol (gPTP). Audio/Video Transport Protocol (AVTP) stream: An AVTP stream is between one Talker and one or more Listeners. Audio/Video Transport Protocol (AVTP) gateway: A device that transports AVTP audio/video streams between an audio/video bridging (AVB) network and another type of media, for example, an IEEE 1394 bus.
3.3 Reserved fields Any field within a data structure that is defined in this specification as reserved is reserved for future standardization. All reserved fields specified in this standard shall be set to a value of zero (0) on transmit. All reserved fields specified in this standard shall be ignored on receive. 3.4 Numerical values Decimal, hexadecimal, and binary numbers are used within this document. For clarity, decimal numbers are generally used to represent counts, hexadecimal numbers are used to represent addresses, and binary numbers are used to describe bit patterns within binary fields. Decimal numbers are represented in their usual 0, 1, 2, … format. Hexadecimal numbers are represented by a string of one or more hexadecimal (0 to 9 and A to F) digits followed by the subscript 16. Binary numbers are represented by a string of one or more binary (0,1) digits in left to right order where the left-most bit is the most significant bit and the right-most bit is the least significant bit, followed by the subscript 2. Thus, the decimal number “26” may also be represented as “1A 16 ” or “11010 2 .” These notational conventions have one exception: MAC addresses and IEEE Organizationally Unique Identifier (OUI)/IEEE Extended Unique Identifier (EUI) values are represented as strings of 8 bit hexadecimal numbers separated by hyphens and without a subscript as, for example, “01-80-C2-00-00-15” or “AA-55-11.”