From fecframe-bounces@ietf.org Thu May 10 21:10:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmJeK-0008Ca-MT; Thu, 10 May 2007 21:10:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmJeJ-0008CP-9t for fecframe@ietf.org; Thu, 10 May 2007 21:10:23 -0400 Received: from nz-out-0506.google.com ([64.233.162.229]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmJeJ-00025m-0d for fecframe@ietf.org; Thu, 10 May 2007 21:10:23 -0400 Received: by nz-out-0506.google.com with SMTP id z6so889975nzd for ; Thu, 10 May 2007 18:10:22 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=jGPySlaCHtQz6atnPCjQXT+1YojMCmsWKcZaos86ps14C6W0nP0d0v7IW8noBUScqZzlupEIBTw8vmSG6ejP522G6t8CmWIIcIwD+ALvxelBJY3WoczvE/NDtKehsR6Drmh304QA2UlF2Yug4A200q9wrnYA5AlboghiXsY8URg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=T7R8dD1xkbSXzjtOsTA1m+UOpeFTbepybsGvVsMc3GrauYCVhHQSfuajJ7KW5C/E46/JFM54avEtDupbtycNq6Juw2PiDAEtEbVolI24DpHpOjl7GNGjwWxfZ77Zdq4FPVlpTFUcK7hEOLBlTrpDn4ZquDmT/UzmtNMTCPn57wY= Received: by 10.114.53.1 with SMTP id b1mr752162waa.1178845822336; Thu, 10 May 2007 18:10:22 -0700 (PDT) Received: by 10.114.132.13 with HTTP; Thu, 10 May 2007 18:10:22 -0700 (PDT) Message-ID: <38c19b540705101810y30c29b9dkff8a1f02c8a95a7@mail.gmail.com> Date: Thu, 10 May 2007 18:10:22 -0700 From: "Greg Shepherd" To: fecframe@ietf.org, rmt@ietf.org, mmusic@ietf.org, avt@ietf.org In-Reply-To: <38c19b540704121450k611cfa11ic3ff20deee967849@mail.gmail.com> MIME-Version: 1.0 References: <38c19b540704121450k611cfa11ic3ff20deee967849@mail.gmail.com> X-Spam-Score: 0.6 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Cc: Subject: [Fecframe] Re: Request For FEC Schemes X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1195623974==" Errors-To: fecframe-bounces@ietf.org --===============1195623974== Content-Type: multipart/alternative; boundary="----=_Part_117884_24314310.1178845822263" ------=_Part_117884_24314310.1178845822263 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline All, On 4/12/07, Greg Shepherd wrote: > > Greetings, > > From the 68th IETF meeting in Prague, the FECFrame working group came away > with some action items which we need to get to in order stay on track with > our milestones: > > 1) Streaming Content Delivery Protocol > Define specific protocol elements for signalling the use of FEC > SDP, in particular, requires coordination with mmusic, avt and rmt > - thus the current distribution. > Call for volunteers to participate as the part of a Design Team. So far we've had two step forward willing to work on the team. This doesn't include Mark (opt-out assigned) or the chairs. Last call. 2) Call for FEC Schemes: > > Like the RMT FEC Building Block, we should define the requirements > that FECFRAME FEC Schemes should meet; > Data elements that must be defined > Procedures that must be defined > Format for FEC Scheme specifications No reponse here. Perhaps we need to expand out request outside of the above groups. Greg If you're interested enough to be on this list, and/or interested enough to > attend the WG meetings, then you must be interested enough to see this > through to functional result - please step-up. > > Thanks, > Greg > > ------=_Part_117884_24314310.1178845822263 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline All,

On 4/12/07, Greg Shepherd <gjshep@gmail.com > wrote:
Greetings,

From the 68th IETF meeting in Prague, the FECFrame working group came away with some action items which we need to get to in order stay on track with our milestones:

1) Streaming Content Delivery Protocol
       Define specific protocol elements for signalling the use of FEC
       SDP, in particular, requires coordination with mmusic, avt and rmt - thus the current distribution.
       Call for volunteers to participate as the part of a Design Team.

So far we've had two step forward willing to work on the team. This doesn't include Mark (opt-out assigned) or the chairs. Last call. 

2) Call for FEC Schemes:

     Like the RMT FEC Building Block, we should define the requirements that FECFRAME FEC Schemes should meet;
          Data elements that must be defined
          Procedures that must be defined
          Format for FEC Scheme specifications

No reponse here. Perhaps we need to expand out request outside of the above groups.

Greg

If you're interested enough to be on this list, and/or interested enough to attend the WG meetings, then you must be interested enough to see this through to functional result - please step-up.

Thanks,
Greg


------=_Part_117884_24314310.1178845822263-- --===============1195623974== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe --===============1195623974==-- From fecframe-bounces@ietf.org Thu May 10 22:06:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmKWM-0000Ho-AL; Thu, 10 May 2007 22:06:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmKWK-0000Gq-V4; Thu, 10 May 2007 22:06:12 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmKWJ-00085B-NH; Thu, 10 May 2007 22:06:12 -0400 Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 6588098; Thu, 10 May 2007 22:06:11 -0400 In-Reply-To: <38c19b540705101810y30c29b9dkff8a1f02c8a95a7@mail.gmail.com> References: <38c19b540704121450k611cfa11ic3ff20deee967849@mail.gmail.com> <38c19b540705101810y30c29b9dkff8a1f02c8a95a7@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <8823D258-B4A5-4393-A334-94EA605F5F05@multicasttech.com> Content-Transfer-Encoding: 7bit From: Marshall Eubanks Subject: Re: [Fecframe] Re: Request For FEC Schemes Date: Thu, 10 May 2007 22:06:04 -0400 To: "Greg Shepherd" X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.5 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Cc: mmusic@ietf.org, fecframe@ietf.org, Reliable Multicast Transport Transport X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: fecframe-bounces@ietf.org The curse of cross posting : Hello; I am going to the VSF Meeting in Austin next week - http://www.videoservicesforum.org/upcoming_events/2007-05_MtgSeries- AustinTX.shtml Mark Watson should be there are well; hopefully we can drum up some interest. Regards Marshall On May 10, 2007, at 9:10 PM, Greg Shepherd wrote: > All, > > On 4/12/07, Greg Shepherd wrote: Greetings, > > From the 68th IETF meeting in Prague, the FECFrame working group > came away with some action items which we need to get to in order > stay on track with our milestones: > > 1) Streaming Content Delivery Protocol > Define specific protocol elements for signalling the use of FEC > SDP, in particular, requires coordination with mmusic, avt > and rmt - thus the current distribution. > Call for volunteers to participate as the part of a Design > Team. > > So far we've had two step forward willing to work on the team. This > doesn't include Mark (opt-out assigned) or the chairs. Last call. > > 2) Call for FEC Schemes: > > Like the RMT FEC Building Block, we should define the > requirements that FECFRAME FEC Schemes should meet; > Data elements that must be defined > Procedures that must be defined > Format for FEC Scheme specifications > > No reponse here. Perhaps we need to expand out request outside of > the above groups. > > Greg > > If you're interested enough to be on this list, and/or interested > enough to attend the WG meetings, then you must be interested > enough to see this through to functional result - please step-up. > > Thanks, > Greg > > > _______________________________________________ > Fecframe mailing list > Fecframe@ietf.org > https://www1.ietf.org/mailman/listinfo/fecframe _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Thu May 17 11:28:45 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HohuH-000348-H3; Thu, 17 May 2007 11:28:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HohuG-00033S-FH for fecframe@ietf.org; Thu, 17 May 2007 11:28:44 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HohuG-0004k9-1H for fecframe@ietf.org; Thu, 17 May 2007 11:28:44 -0400 Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 6621626 for fecframe@ietf.org; Thu, 17 May 2007 11:28:43 -0400 Mime-Version: 1.0 (Apple Message framework v752.3) References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Marshall Eubanks Date: Thu, 17 May 2007 11:28:34 -0400 To: fecframe@ietf.org X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.5 (/) X-Scan-Signature: bc102ac530ba955ef81f1f75b8bebe44 Subject: [Fecframe] Fwd: 69th IETF - Working Group/BOF Scheduling X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: fecframe-bounces@ietf.org Note the deadlines. Begin forwarded message: > From: IETF Agenda > Date: May 17, 2007 10:50:02 AM EDT > To: wgchairs@ietf.org, bofchairs@ietf.org, irsg@isi.edu > Subject: 69th IETF - Working Group/BOF Scheduling > > ----------------------------------------------------------------- > 69th IETF - Chicago, IL USA > Meeting Dates: July 22-27, 2007 > ----------------------------------------------------------------- > > We are accepting scheduling requests for all Working Groups and BOFs > starting today, Monday, April 23, 2007. The milestones and > deadlines for > scheduling-related activities are as follows: > > -- Cut-off date for requesting a Working Group session and for > preliminary BOF proposals to ADs: Monday, May 21 at 17:00 ET (21:00 > UTC/GMT). > -- Cut-off date for requests to schedule BoFs: Monday, June 11 at > 17:00 ET > (21:00 UTC/GMT). > -- Preliminary agenda published for comment: Friday, June 15 by > midnight > ET. > -- Cut-off date for requests to reschedule a session: Wednesday, > June 27 > at 09:00 ET (13:00 UTC/GMT). > -- Final agenda published: Monday, July 2 before midnight ET. > -- Draft Working Group agendas due: Wednesday, July 11 at 17:00 ET > (21:00 > UTC/GMT). > -- Revised Working Group agendas due: Monday, July 16 at 12:00 ET > (16:00 > UTC/GMT), upload using IETF Meeting Materials Management Tool > > Submitting Requests for Working Group and BOF Sessions > > Please submit requests to schedule your Working Group sessions > using the > "IETF Meeting Session Request Tool," a Web-based tool for > submitting all > of the information that the Secretariat requires to schedule your > sessions. > > The URL for the tool is: > > https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi > > Instructions for using the tool are available at: > > http://www.ietf.org/instructions/session_request_tool_instruction.html > > Please send requests to schedule your BOF sessions to agenda@ietf.org. > Please include the acronym of your BOF in the subject line of the > message, > and include all of the information specified in item (4) of > "Requesting > Meeting Sessions at IETF Meetings" in the body. (This document is > included below.) > > Submitting Session Agendas > > For the convenience of meeting attendees, we ask that you submit the > agendas for your Working Group sessions as early as possible. Draft > Working Group agendas are due Wednesday, July 11 by 17:00 ET (21:00 > UTC/GMT). Revised Working Group agendas are due no later than Monday, > July 16 at 12:00 ET (16:00 UTC/GMT). The proposed agenda for a BOF > session should be submitted along with your request for a session. > Please > be sure to copy your Area Director on that message. > > Please submit the agendas for your Working Group sessions using the > "IETF > Meeting Materials Management Tool," a Web-based tool for making your > meeting agenda, minutes, and presentation slides available to the > community before, during, and after an IETF meeting. If you are a BOF > chair, then you may use the tool to submit a revised agenda as well as > other materials for your BOF once the BOF has been approved. > > The URL for the tool is: > > https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi > > Additional information about this tool is available at: > > http://www.ietf.org/instructions/meeting_materials_tool.html > > Agendas submitted via the tool will be available to the public on the > "IETF Meeting Materials" Web page as soon as they are submitted. > > The URL for the "IETF 69 Meeting Materials" Web page is: > > https://datatracker.ietf.org/public/meeting_materials.cgi? > meeting_num=69 > > If you are a Working Group chair, then you already have accounts on > the > "IETF Meeting Session Request Tool" and the "IETF Meeting Materials > Management Tool." The same User ID and password will work for both > tools. > If you are a BOF chair who is not also a Working Group chair, > then you > will be given an account on the "IETF Meeting Materials Management > Tool" > when your BOF has been approved. If you require assistance in using > either tool, or wish to report a bug, then please send a message to: > ietf-action@ietf.org. > =============================================================== > For your convenience, comprehensive information on requesting meeting > sessions at IETF 69 is presented below: > > 1. Requests to schedule Working Group sessions should be submitted > using > the "IETF Meeting Session Request Tool," a Web-based tool for > submitting > all of the information required by the Secretariat to schedule your > sessions. The URL for the tool is: > > https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi > > Instructions for using the tool are available at: > > http://www.ietf.org/instructions/session_request_tool_instruction.html > > If you require an account on this tool, or assistance in using it, > then > please send a message to ietf-action@ietf.org. If you are unable > to use > the tool, then you may send your request via e-mail to > agenda@ietf.org, > with a copy to the appropriate Area Director(s). > > Requests to schedule BOF sessions must be sent to agenda@ietf.org > with a > copy to the appropriate Area Director(s). > > When submitting a Working Group or BOF session request by e-mail, > please > include the Working Group or BOF acronym in the Subject line. > > 2. BOFs will NOT be scheduled unless the Area Director(s) approved > request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, CHAIR > (S) > NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL > DESCRIPTION, and the information requested in (4) below. (Please > read the > BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt before > requesting a session for a BOF.) > > 3. A Working Group may request either one or two sessions. If your > Working Group requires more than two sessions, then your request > must be > approved by an Area Director. Additional sessions will be > assigned, based > on availability, after Wednesday, June 27 at 09:00 ET (13:00 UTC/ > GMT), the > cut-off date for requests to reschedule a session. > > 4. You MUST provide the following information before a Working > Group or > BOF session will be scheduled: > > a. Working Group or BOF full name with acronym in brackets: > > b. AREA under which Working Group or BOF appears: > > c. CONFLICTS you wish to avoid, please be as specific as possible: > > d. Expected Attendance (figures from the 68th IETF meeting are > included at the end of this message): > > e. Special requests: > > f. Number of sessions: > > g. Length of session: > - 1 hour > - 2 hours > - 2 1/2 hours > > For more information on scheduling Working Group and BOF sessions, > please > refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and > Procedures" > (http://www.ietf.org/rfc/rfc2418.txt). > =============================================================== > For your convenience please find here a list of the IETF Area > Directors > with their e-mail addresses: > > IETF Chair > Russ Housley > > Applications Area (app) > Lisa Dusseault > Chris Newman > > Internet Area (int) > Jari Arkko > Mark Townsley > > Operations & Management Area (ops) > Ronald Bonica > Dan Romascanu > > Real-time Applications and Infrastructure Area (rai) > Cullen Jennings > Jon Peterson > > Routing Area (rtg) > Ross Callon > David Ward > > Security Area (sec) > Sam Hartman > William Polk > > Transport Area (tsv) > Lars Eggert > Magnus Westerlund > =========================================================== > 68th IETF Meeting Attendance Number > > 16ng 119 > 16ng (2nd session) 46 > 6lowpan 57 > adslmib 8 > ancp 33 > apparea 74 > autoconf 53 > avt 80 > avt (2nd session) 62 > behave 43 > bfd 65 > bliss 171 > bmwg 29 > btns 51 > calsify 18 > capwap 39 > ccamp 109 > ccamp (2nd session) 94 > dccp 37 > dhc 61 > dime 26 > dkim 46 > dna 14 > dnsext 89 > dnsop 107 > eai 59 > ecrit 91 > emu 48 > enum 106 > fecframe 22 > forces 28 > fsm 41 > geopriv 84 > hiprg NI > hokey 96 > idr 69 > ifare 60 > intarea 250 > ipdvb 18 > ipfix NI > ippm 40 > ipr 30 > isis 34 > isms 36 > keyprov 42 > krb-wg 27 > krb-wg (2nd session) 30 > l1vpn 51 > l2vpn 114 > l3vpn 106 > lemonade 28 > lemonade (2nd session) 24 > ltans 28 > manet 104 > mboned 57 > mediactrl 48 > mip4 48 > mip6 140 > mipshop 123 > mipshop (2nd session) 94 > mmusic 128 > mobopts 59 > monami6 115 > mpls 114 > nea 55 > nemo 135 > netconf 50 > netlmm 129 > nfsv4 NI > nmrg 32 > nsis 53 > ntp 28 > opsares 101 > opsarea (2nd session) 65 > ospf 83 > p2psip 183 > pana 30 > pce 77 > pcn 74 > pim 49 > pkix 48 > pwe3 103 > radext 23 > rmt 25 > rtgarea 196 > rptsec 154 > saag 74 > sasl 29 > sava 156 > sidr 77 > sieve 20 > simple 90 > sip 154 > sip (2nd session) 160 > sipping 177 > sipping (2nd session) 134 > smime 22 > softwire 59 > speermint 122 > tcpm 46 > tictoc 113 > tls 53 > trill 48 > tsvarea 110 > tsvwg 88 > tsvwg (2nd session) 65 > v6ops 141 > xcon 82 > _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Wed May 23 13:05:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HquH4-0001fu-Jb; Wed, 23 May 2007 13:05:22 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HquH3-0001fp-IC for fecframe@ietf.org; Wed, 23 May 2007 13:05:21 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HquH3-0008L2-B0 for fecframe@ietf.org; Wed, 23 May 2007 13:05:21 -0400 Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 6642528 for fecframe@ietf.org; Wed, 23 May 2007 13:05:21 -0400 Mime-Version: 1.0 (Apple Message framework v752.3) References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1A624E11-CE65-465F-BE1C-0A8E24591CA5@multicasttech.com> Content-Transfer-Encoding: 7bit From: Marshall Eubanks Date: Wed, 23 May 2007 13:05:19 -0400 To: fecframe@ietf.org X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Subject: [Fecframe] Fwd: 69th IETF - DRAFT Meeting Agenda for Review X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: fecframe-bounces@ietf.org We thought that given the state of work a meeting would not be necessary. If people feel otherwise, please speak up ASAP. Regards Marshall Begin forwarded message: > From: IETF Agenda > Date: May 23, 2007 11:55:54 AM EDT > To: wgchairs@ietf.org, bofchairs@ietf.org, irsg@isi.edu, iesg@ietf.org > Subject: 69th IETF - DRAFT Meeting Agenda for Review > > Dear ALL: > > The DRAFT agenda for the 69th IETF Meeting can be found at: > https://datatracker.ietf.org/public/meeting_agenda_html.cgi? > meeting_num=69. > Please note that the agenda is in draft form and is subject to change. > > We would like to ask you to review the Draft Agenda and send your > comments to agenda@ietf.org. We shall be working on your comments > until > the Final Agenda is published which is on Monday, July 2nd) > (Important Meeting Dates can be found at > http://www.ietf.org/meetings/69-IETF.html). > > We would really appreciate your inputs or suggestions on the draft > agenda and shall try to accommodate your priorities if possible. > > IETF Secretariat > > +++ > > The milestones and deadlines for scheduling-related activities are as > follows: > > -- Cut-off date for requesting a Working Group session and for > preliminary BOF proposals to ADs: Monday, May 21 at 17:00 ET (21:00 > UTC/GMT). > -- Cut-off date for requests to schedule BoFs: Monday, June 11 at > 17:00 ET > (21:00 UTC/GMT). > -- Preliminary agenda published for comment: Friday, June 15 by > midnight > ET. > -- Cut-off date for requests to reschedule a session: Wednesday, > June 27 > at 09:00 ET (13:00 UTC/GMT). > -- Final agenda published: Monday, July 2 before midnight ET. > -- Draft Working Group agendas due: Wednesday, July 11 at 17:00 ET > (21:00 > UTC/GMT). > -- Revised Working Group agendas due: Monday, July 16 at 12:00 ET > (16:00 > UTC/GMT), upload using IETF Meeting Materials Management Tool > _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe