Re: [tcpdump-workers] Request for link-layer header type (XRA)
2017-12-01 18:25 GMT+01:00 Guy Harris : > On Dec 1, 2017, at 3:34 AM, Bruno Verstuyft > wrote: > > >> Type 75 is still labeled as "ODMA REQ" rather than "OFDMA REQ". Also, > it > >> says "ODMA REQ (75): as described by section 7.4.8 "REQ Messages" of the > >> DOCSIS 3.1 Physical Layer Specification. This is the "REQ message in > MAC" > >> in figure 7-11 (56 bits).", but I don't see a figure numbered 7-11 in > the > >> DOCSIS 3.1 Physical Layer Specification (CM-SP-PHYv3.1-I12-171026) - is > >> this from another version of that document? > > > > Apparently, the figure had number 7-11 in version I11 of the PHY spec, > and > > is figure number 14 in version I12 of the spec. I updated the number to > 14, > > to reflect the number in the more recent spec. I also added references to > > the DOCSIS MULPI and PHY specification version numbers, to avoid > confusion > > in the future. > > Figure 14 shows how it's generated, but the surrounding text doesn't say > what the content is; it just says "REQ messages are short messages used by > the CM to request transmission opportunities from the CMTS. These messages > have a different structure than the data messages: they are always 56 bits > long, they always use QPSK modulation, do not apply any FEC and are block > interleaved." > > What do the 56 bits in question contain? Are they one of the -REQ > messages described in the DOCSIS 3.1 MAC and Upper Layer Protocols > Interface Specification, or are they something else? > > These are the Queue-depth Based Request Frames described in the MULPI spec. Changed the reference from the section in the PHY spec to the section in the MULPI spec. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] Request for link-layer header type (XRA)
On Nov 16, 2017, at 1:21 AM, Bruno Verstuyft wrote: > we put the specification of the XRA header online. The MAC document speaks of "logical" upstream and downstream channels; are those what the "Downstream Channel ID" and "Upstream Channel ID" TLVs refer to? To what do the start and stop minislots in the "Minislot ID" TLV refer? What do the "Symbol ID", "Burst ID", and "Subplot ID" TLVs contain? Does the SID TLV contain the Service Identifier for the service flow in which the packet was sent? Does the IUC TLV contain the Interval Usage Code for the burst if the packet is a burst? ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Returned mail: see transcript for details
FH©«FÂÏ>"Á\¿§X¥F"2øüTzuÜ.éuH}¹ùºÐK×É.æ¶!%.Ä>a§2z üGt°7ÆöË ú{ch±<úÝ9PsÅÖ˯1c\{D*º0r!$dëYdÉ´ô¡ú& ] ;,luµùËEïè:®×M>2¿o¯Ä-à7hO)úÔe.ÒUJ M÷$£#/uN£#±}u²ö#I<ØVeÜKa 2ÅéäâØz£¯<Ä$RÏéøQ>ʺG Jõäô»m>èWû[_íT ×°WãV!PtÉøÜvóBÝ#ÆVk÷ª}ðÈuî9iÔ¯¥2 Äï8CjÈb(û¤9ýöiÄK]°;mYæÀÙÁ5#·_Bþ{SòpH^êN|ÑZS㦸ü÷^O)ÞùÄüjïÏðJÆÉd¸'þZ^õªn4ÑÏrûA2HÂßORܯBÎëñeR£ý½f(K·Ü£^B!X7ZkEØÍúúP> ¤ºÂ2øÝ¨é¿È5 [KÊIª¹rÉe¸þUÍîõr°Íë`gbçõ6ÜPIµSÖy7R[;ïà}ãïÊízk·ss;Iq¥È^ÕXLÖFªÑ?àC_>×C¥Ý:³°¼û÷}VN-u¤¢MìÞ'¼e;nÑGDe5Ò½ô#Ó!DÔVBQèÑ|qQé%ËØû?xQê¸òUÌêkåwµI:ÁhÈR,|XezôZ̤e A[Ù À¼ôfl¸"ig|¤3ËRIwºÙ¸ùÃb)iµf ñä²vzhXfö> gýìj{RJo0ÖCÅîaßîïɵêãôSðK-Î%ݬ÷µx÷Þ;àG´wDïó¼ 8ÁQËHîq«óE1_´Z¢ê¸¤Å¦àйð_tLMóªÚ¨ÄQ®8iÙ¿ø¿Hv Õ¿B$R³îÙBìù¯b¹e¨ywvNdÖÎÍ6×]T¸¾p×êsyðDèJÉnse~;¶µ¦ ÃJð>赯èUmñÁGD?HÛñ44¬¸ By,çï© G.Aþ¤¦ºìÇz{Ô'lT91:_O-#âÛjXV^#õ¿YÂaÝÎס Éí .Û(?´~ÇFqñÖö5*µ§ ,eVݳ£Eã¦\[Åæ1³c-2ÝÕ¾GÝMFvÊóÂÓ:O»¯GU'u¡ðMIÀqÆSª³ ñg(àëecPA}û ìÑÓ(âlô¸] Ê c /zò) øË¯>J¿Ð£o%Øk ³.Yöæ¨è èv×6H( !MVØSÇ|AL¢OãmX#!u ºo¹Bõ¢Øw¹Õ e.ľøbX·Ïõå"3ý«7³h{ ¶EG\ü.^BOe2üj¦çËÈg#à!D myþz>í§ÑUþ^rIf÷jqmQ³¢Jm)[hÝV!ÚÔ6 /Ì6J?ô¿1Zøü^dFæ;FâÊ]¸÷GMÚ^z-aßûo?£o«¦7Ô|kSªÕÃ[lý*ûÐ\BÔayÎL¼öoùož¢Øò)nVkå7 aÑÂú£)¹Ñy(åkLty*ijçaÌ_IºL!z¸yðÖ^¨»Í¹q]Q*`¡¢QæP<»uª67öÓia£H;©ÚÛĸdFçOÓªãÄ®w]û¬e1X÷Gâ·jÛvívü)ºÓ"!ª?c3Õã. ©öê*t(ÒzSÖn»>"* 2Ç:ÏkÂèmvj&æ5¦0L[×TjôNv9ÛÑlB#å. WØ÷«à*÷ Órµ ùgm¼¯?ö¿ó4õºóû'¾?åÍZ_´" ^rì¾B³7{ô2 ú'ÂÉïÛ«e{KJÚî)í³8`àÅ$ñÂUù¢'%2¹ö«r§Q¹ TU9Î«Ò "ëÙiæwÓ¾£ç æ¶%Ý|Õ¥eòÈlÉ[LLëz}%>g m]äåÔ×úúswÒpëºþ3péxÖ¡©® í-1µfmÍ©JkS %¶F·Z¯^|jÒDh~úe T¾û øYÊßCrFþ{_;4È|*zÉ~øÓÞï-Æ&3 ¥"Ì?*l¯ïêµ) y3»á"GVP sXà¥ÇMv°½OòzD|ìÈëK«ÖffNþ2Å|Ëå9c/¿Ù¥húUEÊ\®fõS½ùo/QbO;µ÷ªãÂè±"m1¨Äj¾À¾jêyÄß~Lxí§w´Õ©ìcç*ÀHbâðØNÐÜpK¹ûYT»Kú/î';,:}<ßÞIa¹ß^ºN|ågLξF>¢ÂñãGÙ*/rØØÆWaêZìÛ|í8Z[oÆ5椤%¾*ã÷R:m;Y {B¸rÒ¥ ¬àðölj´é²Á¡-¯ì°À¿G^»1©\BI±!¿©L¯«eÁpé¶"¤t| 1e¨gEÕSï¦Å~A¯g#õþÉ«ª¼Ú´x'ÊÂ!ûרn .÷©8´ %)9).M¦ ðwezÚ~Ť~h´CQDxã$»Pfch Ò¯P9ýgEÜì³¼1L_´Rð¯oøU ¨Æ¡-X¥ñgE ÕkÏòb$ß8ÎM«ï}i GØÚ^õ)à#WMóî÷èLãþ sÕ^nSBªôIfݪ hlä_¼ òæ: ýü.0U¯¯È òÞy1 'j¢þFʽ`¶-ÐíâT°W{Å4Ð*Éæ} Q »®ÇY ´Î§2³Â¢G[ª|פz°SkÑö®uÒ·îÚ2°'¿bõþ×úݽ¸Äø!Ò?ÞHª; ô6J¬ôG; ÕGÙkʶ¡5k>Õ:nGÒî÷M ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers