Actually, I have a small dilemma regarding the offset words (the last 4 bytes):
Does it make more sense to define an enum (0..7) instead of ASCII symbols? I noticed that VLC project defines RDS blocks (internally) using an enum, starting from 0: #define V4L2_RDS_BLOCK_A 0 #define V4L2_RDS_BLOCK_B 1 #define V4L2_RDS_BLOCK_C 2 #define V4L2_RDS_BLOCK_D 3 #define V4L2_RDS_BLOCK_C_ALT 4 #define V4L2_RDS_BLOCK_INVALID 7 Should we do the same? We would also have to add the missing #define RDS_BLOCK_E 5 On Tue, Sep 13, 2016 at 7:20 PM, Guy Harris <g...@alum.mit.edu> wrote: > On Sep 4, 2016, at 6:43 AM, Jonathan Brucker <jonathan.bru...@gmail.com> > wrote: > >> I am posting to request a value for DLT_RDS and LINKTYPE_RDS. >> >> Radio Data System (RDS) is a communications protocol standard >> published in 1992 for embedding small amounts of digital information >> in conventional FM radio broadcasts. >> >> The standard is also known as Radio Broadcast Data System (RBDS) in the US. >> >> References and Specifications: > > IEC 62106 Edition 3.0 (2015-03) "Specification of the radio data system (RDS) > for VHF/FM sound broadcasting in the frequency range from 87,5 MHz to 108,0 > MHz", and earlier versions thereof. > >> The Offset Symbols are ASCII characters representing the detected >> syndromes for the corresponding Information Words, and are used in >> the interpretation of Information Words, as per RDS standard. > > OK, so in this format the offset words are given as ASCII characters rather > than as the bit sequences. > > I've assigned a value of 265 for LINKTYPE_RDS and DLT_RDS, and added an entry > for it in http://www.tcpdump.org/linktypes.html; the update to that page > probably won't appear immediately, but it should show up in 24 hours or so. _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
