IEEE 1722.1 Agenda 20190313 AVBTP-DECC@LISTSERV.IEEE.ORG AVBTP@LISTSERV.IEEE.ORG NOTE North American Time CHANGE Meeting time is 9AM Pacific Daylight Time (GMT -7) 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 Since all work and voting on the PAR needs to be completed by the end of the extension, we need members to start submitting specific proposals please. P1722.1 REV1 can be found here: https://development.standards.ieee.org/get-file/P1722.1.pdf?t=88000800003 The criteria for the revisions and additions to 1722.1 are to maintain interoperability with existing systems. The PAR lists the following areas where work is to be done: * generalized Precision Time Protocol (IEEE 802.1AS-2011 and IEEE P802.1AS-REV) * Egress shapers (IEEE 802.1Q-2014 Clause 34, IEEE P802.1Qbv and IEEE P802.1Qbu) * Parameterized SRP (IEEE P802.1Qcc) * Redundant networks (IEEE P802.1CB and IEEE P802.1AS-REV) * Ingress Policing (IEEE P802.1Qci) I believe that anything proposed must fit within one of the above categories. To meet schedule we should be gathering proposals now so that there is time for discussion and refinement. I know the Avnu Milan group has a redundancy scheme that has elements that would fit well in 1722.1, and that group also had some challenges that have not been resolved by the IEEE Std 1722.1-2013/Cor. 1-2018. The problems should be defined and a discussion started on how to provide a way to address them either within the existing standard, or in the rev. I think keeping this weekly meeting at 20 minutes or less is sufficient for the moment, but as we get proposals there is going to be a need for extended discussions. I still do not have an answer on the archive for the reflector or for an approved use of Slack or something like it. thanks Richard ________________________________________________________________________ To unsubscribe from the AVBTP-DECC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=AVBTP-DECC&A=1 NOTICE: This email may contain confidential information. Please see https://meyersound.com/legal/#email/ for our complete policy. To unsubscribe from the AVBTP-DECC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=AVBTP-DECC&A=1 Hi Richard I can’t make it to today’s call please send out meeting notes. My update: corrigendum is complete and will be released March 15 for purchase from IEEE. I have a git branch in 1722.1-rev where i am still in progress updating formatting and front matter etc. next step will be enabling change bars to show comparisons between the base document and proposed changes .