IEEE 1722.1 Agenda 20190123 AVBTP-DECC@LISTSERV.IEEE.ORG Meeting time is 9AM Pacific (GMT -8) In advance of joining the meeting, please review the Essential Patent Claims Announcement https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.pdf The policies and procedures for this group can be found here: http://grouper.ieee.org/groups/1722/1/web/P1722_1_WG_PP.pdf Online Zoom Meeting address for this week: https://zoom.us/j/2268818568 One tap mobile +14086380968,,2268818568# US (San Jose) +16699006833,,2268818568# US (San Jose) Dial by your location +1 408 638 0968 US (San Jose) +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 226 881 8568 Find your local number: https://zoom.us/u/cMjKFMQnr IMPORTANT - Voting for New IEEE 1722.1 Officers: Please reply to the request on the reflector (thread "IMPORTANT - Voting for New IEEE 1722.1 Officers") to be listed as a voting member to nominate and to vote. Nominations close by end of day January 31. Self nominations close by end of day February 14. Note to all: For those attending ISE-2019 (February 5-8) in Amsterdam there will be an informal meeting on Thursday afternoon (Feb 7) after the Avnu Alliance joint MWG/TWG meeting. The address is The Hilton Amsterdam, Apolloaan 138, 1077 BG Amsterdam. New topics for discussion: Proposal from Chris Calmejane Thread: Entities enumeration with lots of devices (and how to reduce required traffic / reduce enumeration time) Discussions (and proposals) on how to improve the standard regarding entities enumeration, especially when the network has a lot of them. The objectives being how to reduce the required traffic between a controller and the entities, and the overall enumeration time. Please see the thread on this started by Chris on Thursday. Proposal from Jeff Koftinoff Jeff would like to see controller driven ACMP. This would allow a controller to be able to pass requests between talkers and listeners that have their control connections on different VLANs or subnets, preventing them from communicating directly when we use 1722.1 over IP. There is a way this can be hacked now, but a more elegant solution is desired. Continuing review of the status of the documents being prepared to pass to the editors. These are the ones still in progress: A. Clarification of the existing standard. 05. ACMP : STREAMING_WAIT discussion on clarifying details on which flags are used in Connect Tx and Connect Rx commands 8.2.1.17 bit 13 needs clarification! what is intended use and what does it mean "Connection has saved state (used in Get State only) 06. ACMP/ AEM : Connection and acquired/locked state 07. ACMP : Various clarifications of the fields of the ACMP messages B. Change existing standard. 08. AEM : ACQUIRE_ENTITY command 09. AEM : Sequence id for unsolicited notification messages 10. ACMP : List of connected listeners maintained by the talker 11. ACMP : ACMP and MAAP 13. AEM : Sample rate conversion 14. ACMP : Fast Connect 15. ACMP : Controller Connect sequence D. Extend the existing standard in 1722.1-REV 21. AEM : GET_COUNTERS 22. AEM : List of unsolicited notifications 23. AEM : Extend GET_STREAM_INFO