From fecframe-bounces@ietf.org Fri Jun 02 09:37:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm9q4-0006u9-Rd; Fri, 02 Jun 2006 09:37:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm9q3-0006rd-94 for fecframe@ietf.org; Fri, 02 Jun 2006 09:37:19 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fm9Lc-0003Wk-Bp for fecframe@ietf.org; Fri, 02 Jun 2006 09:05:52 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fm9EA-0003mK-Ig for fecframe@ietf.org; Fri, 02 Jun 2006 08:58: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 id 4642434 for fecframe@ietf.org; Fri, 02 Jun 2006 08:58:05 -0400 Mime-Version: 1.0 (Apple Message framework v750) References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <077B4C9F-10EB-47A6-A3D0-B5836D5102F8@multicasttech.com> Content-Transfer-Encoding: 7bit From: Marshall Eubanks Date: Fri, 2 Jun 2006 08:53:56 -0400 To: fecframe@ietf.org X-Mailer: Apple Mail (2.750) X-Spam-Score: -2.2 (--) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Subject: [Fecframe] Fwd: Internet-Drafts Submission Cutoff Dates for the 66th IETF Meeting in Montreal, Quebec, Canada 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 Hello; It's that time again ! Note the deadlines for document submissions. If you have items you want to discuss in Montreal, please send them to the chairs. Regards Marshall Eubanks Begin forwarded message: > From: ietf-secretariat@ietf.org > Date: June 2, 2006 12:00:01 AM EDT > To: ietf-announce@ietf.org > Subject: Internet-Drafts Submission Cutoff Dates for the 66th IETF > Meeting in Montreal, Quebec, Canada > > > There are two (2) Internet-Draft cutoff dates for the 66th > IETF Meeting in Montreal, Quebec, Canada: > > June 19th: Cutoff Date for Initial (i.e., version -00) > Internet-Draft Submissions > > All initial Internet-Drafts (version -00) must be submitted by Monday, > June 19th at 9:00 AM ET. As always, all initial submissions with a > filename beginning with "draft-ietf" must be approved by the > appropriate WG Chair before they can be processed or announced. The > Secretariat would appreciate receiving WG Chair approval by Monday, > June 12th at 9:00 AM ET. > > June 26th: Cutoff Date for Revised (i.e., version -01 and higher) > Internet-Draft Submissions > > All revised Internet-Drafts (version -01 and higher) must be submitted > by Monday, June 26th at 9:00 AM ET. > > Initial and revised Internet-Drafts received after their respective > cutoff dates will not be made available in the Internet-Drafts > directory or announced until on or after Monday, July 10th at 9:00 > AM ET, when Internet-Draft posting resumes. Please do not wait until > the last minute to submit. > > Thank you for your understanding and cooperation. If you have any > questions or concerns, then please send a message to > internet-drafts@ietf.org. > > The IETF Secretariat > > FYI: The Internet-Draft cutoff dates as well as other significant > dates > for the 66th IETF Meeting can be found at http://www.ietf.org/ > meetings/cutoff_dates_66.html. > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Fri Jun 02 11:51:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmBw9-00026S-N0; Fri, 02 Jun 2006 11:51:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmBw8-00026K-M6 for fecframe@ietf.org; Fri, 02 Jun 2006 11:51: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 1FmBw5-00053k-Eo for fecframe@ietf.org; Fri, 02 Jun 2006 11:51: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 id 4642715 for fecframe@ietf.org; Fri, 02 Jun 2006 11:51:36 -0400 Mime-Version: 1.0 (Apple Message framework v750) References: <44804282.1070905@isoc.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Marshall Eubanks Date: Fri, 2 Jun 2006 11:48:57 -0400 To: fecframe@ietf.org X-Mailer: Apple Mail (2.750) X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Subject: [Fecframe] Fwd: IETF 2008 - 2010 Meeting Calendar Adopted 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 Just FYI. Marshall Begin forwarded message: > From: Ray Pelletier > Date: June 2, 2006 9:52:02 AM EDT > To: IETF Discussion > Subject: IETF 2008 - 2010 Meeting Calendar Adopted > Reply-To: iad@ietf.org > > The IAOC has formally adopted an IETF Meeting Calendar for 2008 - > 2010. Thanks for your feedback during its development. > > The calendar also includes targeted regions for each meeting for > planning purposes. These regions are provisional and dependent > upon many variables, including qualified venue availability, > financial risk and an appropriate Host arrangement, and thus are > subject to change. > > A process for sending expressions of interest to host a meeting is > under development and will be separately announced. > > The calendar can be found at: http://www.ietf.org/meetings/0mtg- > sites.txt > > BTW - only 38 days before IETF 66 in the City of Festivals, > Montreal. Register and book your hotels at: http://www.ietf.org/ > meetings/IETF-66.html > > Thanks again, > > Ray Pelletier > IAD > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Tue Jun 06 11:22:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FndNu-0005Zp-LI; Tue, 06 Jun 2006 11:22:22 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FndNt-0005Zk-H3 for fecframe@ietf.org; Tue, 06 Jun 2006 11:22: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 1FndNs-0005xP-C8 for fecframe@ietf.org; Tue, 06 Jun 2006 11:22: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 id 4651634 for fecframe@ietf.org; Tue, 06 Jun 2006 11:21:57 -0400 Mime-Version: 1.0 (Apple Message framework v750) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: fecframe@ietf.org From: Marshall Eubanks Date: Tue, 6 Jun 2006 11:22:18 -0400 X-Mailer: Apple Mail (2.750) X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Subject: [Fecframe] Presentation at Montreal 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 Wearing my member hat, I would like to submit to present on the two new SMPTE documents from the SMPTE Technology Committee N26 on File Management and Networking Technology on transport layer FEC. 10 Minutes should suffice. These documents will enter their equivalent of last call (their ballot process) tomorrow, and I think that the WG should be aware of this effort. Regards Marshall _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Tue Jun 06 13:17:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnfBf-00040X-8u; Tue, 06 Jun 2006 13:17:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnfBd-00040S-Aw for fecframe@ietf.org; Tue, 06 Jun 2006 13:17:49 -0400 Received: from nf-out-0910.google.com ([64.233.182.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnfBc-0002tD-1X for fecframe@ietf.org; Tue, 06 Jun 2006 13:17:49 -0400 Received: by nf-out-0910.google.com with SMTP id l37so1770858nfc for ; Tue, 06 Jun 2006 10:17:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lpEaNSJCNAcsmfxV2LyVCnGCu6kGpQKYrL1oxlinOncv9gmODt9WHUrTN5s0bvIOHtzjnvBZP8IFk4V1NHG5Menau2ljFXNySZxv8AsZOWnfdDmpcqtPW8rKQIIL5wPkO5sLM53aANb8NKnmuXN0AjmYg2pClHiPrpcqk3qj9sU= Received: by 10.48.12.8 with SMTP id 8mr5509557nfl; Tue, 06 Jun 2006 10:17:46 -0700 (PDT) Received: by 10.49.2.15 with HTTP; Tue, 6 Jun 2006 10:17:39 -0700 (PDT) Message-ID: <38c19b540606061017i7d6e257bn282c670eb2cd613@mail.gmail.com> Date: Tue, 6 Jun 2006 10:17:39 -0700 From: "Greg Shepherd" To: "Marshall Eubanks" Subject: Re: [Fecframe] Presentation at Montreal In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: fecframe@ietf.org 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 Thanks Marshall. You're on the agenda. Greg On 6/6/06, Marshall Eubanks wrote: > Wearing my member hat, I would like to submit to present on the > two new SMPTE documents from the SMPTE Technology Committee N26 on > File Management and Networking Technology > on transport layer FEC. 10 Minutes should suffice. > > These documents will enter their equivalent of last call (their > ballot process) tomorrow, and I think that the > WG should be aware of this effort. > > Regards > Marshall > > > _______________________________________________ > 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 Tue Jun 06 13:20:00 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnfDk-0004DP-SQ; Tue, 06 Jun 2006 13:20:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnfDj-0004DK-Uj for fecframe@ietf.org; Tue, 06 Jun 2006 13:19:59 -0400 Received: from nf-out-0910.google.com ([64.233.182.191]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnfDj-00033s-CA for fecframe@ietf.org; Tue, 06 Jun 2006 13:19:59 -0400 Received: by nf-out-0910.google.com with SMTP id m18so1752182nfc for ; Tue, 06 Jun 2006 10:19:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NKPGZrVjsBoZHFiMdIP/8JO8Pa9U+jBwvFuK9VLZ+E0i4y9YzE06YL/kB5wJNFQvDMgTz/63xuspDoND+DLj2woojJfShUFk8xa3BppjnQB3AXAneEPXnJBhxOZhQ708oizktjpJisMFxxXBUn0QPTQHMRqNUrFYzbkc6jjS9Ao= Received: by 10.48.210.19 with SMTP id i19mr4369039nfg; Tue, 06 Jun 2006 10:19:56 -0700 (PDT) Received: by 10.49.2.15 with HTTP; Tue, 6 Jun 2006 10:19:56 -0700 (PDT) Message-ID: <38c19b540606061019i790698eem412265778673ec87@mail.gmail.com> Date: Tue, 6 Jun 2006 10:19:56 -0700 From: "Greg Shepherd" To: "Mark Watson" Subject: Re: [Fecframe] Re: WG Action: FEC Framework (fecframe) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Spam-Score: 0.0 (/) X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665 Cc: fecframe@ietf.org 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 Mark, How is this effort progressing? Will you have this submitted for Montreal? Thanks, Greg On 5/7/06, Mark Watson wrote: > Greg, all, > > Ok, we can get started! > > The first agenda item I'd suggest is a discussion on requirements for > the framework and I'd certainly be happy to provide some input on this > in the form of an Internet Draft. > > To this end, here are some suggestions for requirement items (in outline > form - they would each need fleshing out a bit). Please let me know your > comments, and then the first draft can include the results of some > initial discussion: > > Terminology > ----------- > > "FEC Framework" - the thing we are designing - a general framework > which, when combined with an "FEC scheme" and an application protocol > which supports some minimal FEC framework-related requirements (which we > shall define) produces a complete protocol for FEC protection of that > application. > > "Media protocol" (good term?) - the protocol used for the data stream > being protected - e.g. RTP > > "Transport protocol" - the protocol used for transport of the data > stream being protected - e.g., UDP > > "Application protocol" - control protocols used to establish & modify > the media stream - e.g. RTSP > > "Source block" - the group of media packets which are to be FEC > protected as a single block > > "Protection amount" - the relative increase in data sent due to the use > of FEC > > "SHALL" requirements: > --------------------- > > Req-01: The FEC Framework shall support of a wide range of FEC codes, > using the abstractions of the FEC Building Block defined in RMT > (including short and long block FEC codes, systematic and non-systematic > codes) > > Req-02: The FEC Framework shall support variable source block sizes, > including real-time variation of source block size between blocks within > a stream > > Req-03: The FEC Framework shall support variable protection amounts, > including real-time variation of protection amount between blocks within > a stream > > Req-04: The FEC Framework shall be independent of the media protocols > (provided that media protocol uses one of the supported transport > protocols) and codecs > > Req-05: The FEC Framework shall place minimal requirements on the > application protocols > > Req-06: The FEC Framework shall support variable media data rates > > Req-07: The FEC Framework shall support variable media packet sizes > > Req-08: The FEC Framework shall provide support of combined protection > of multiple packet flows > > Req-09: The FEC Framework shall provide support of multiple transport > protocols for the media protocols (UDP, DCCP, others ?) > > Req-10: The FEC Framework shall provide support for definition of > backwards-compatible FEC protocols (i.e. where the source packets are > not modified in any way) > > Req-11: The FEC Framework shall provide support for different media > protocols (RTP, MIKEY, others ?) > > "SHOULD" requirements: > --------------------- > > Req-12: The FEC Framework should be constructed such that the FEC > streaming protocol defined by 3GPP in TS26.346 is a valid > instantiation/use-case (term?) of the FEC Framework > > Regards, > > Mark Watson > > -----Original Message----- > From: Greg Shepherd [mailto:gjshep@gmail.com] > Sent: Friday, May 05, 2006 7:33 AM > To: fecframe@ietf.org > Subject: [Fecframe] Re: WG Action: FEC Framework (fecframe) > > Hello, > > Okay it's official and the clock is now ticking - two clocks actually. > One obviously is our own Milestone clock which sets our first goal of > having "Working Group consensus on requirements and their > prioritization for the FEC protocol framework" by Nov 06. This means > we only have the upcoming July meeting before our first Milestone and > should have a solid requirements draft by the November meeting. > > We should certainly have our first real WG meeting in Montreal to get > working on the reqs. The 2nd clock gives us one month to prepare for > our July meeting agenda. > > Please let this message serve as a call for agenda items for Montreal > in July. I'll follow this up with an agenda outline. > > Thanks, > Greg > > On 5/2/06, IESG Secretary wrote: > > A new IETF working group has been formed in the Transport Area. For > > additional information, please contact the Area Directors or the WG > Chairs. > > > > +++ > > > > FEC Framework (fecframe) > > ========================= > > > > Current Status: Active Working Group > > > > Chairs: > > Greg Shepherd (gjshep@gmail.com) > > Marshall Eubanks (tme@multicasttech.com) > > > > Transport Area Director(s): > > Magnus Westerlund (magnus.westerlund@ericsson.com) > > Lars Eggert (lars.eggert@netlab.nec.de) > > > > Transport Area Advisor: > > Magnus Westerlund (magnus.westerlund@ericsson.com) > > > > General Discussion: fecframe@ietf.org > > To Subscribe: https://www1.ietf.org/mailman/listinfo/fecframe > > Archive: > http://www1.ietf.org/mail-archive/web/fecframe/current/index.html > > > > Description: > > > > The object of this group is to develop specifications for using > forward > > error correction (FEC) codes with applications in the Internet to > > provide protection against packet loss. The group will develop a > > protocol framework for application of FEC codes to arbitrary packet > > flows over unreliable transport protocols over both IP multicast and > > unicast. The application of the FEC codec on an aggregate of multiple > > packet flows may be investigated and considered to be included in the > > solution. > > > > The FECFrame working group will use the building block approach (RFC > > 3269), especially the FEC Building Block (RFC 3452), developed by the > > RMT working group. The FEC Building Block was developed to ensure that > > the RMT framework developed can support multiple FEC codes and > maintain > > independence between FEC codes and protocols based on the framework. > The > > FECFrame WG may develop new FEC schemes if necessary to provide > > substantial performance gains for the intended applications. However > > the acceptance of any FEC scheme will require multiple, prior, > detailed > > reviews of the FEC code by independent experts from both the IETF and > > the broader community, since it is likely that the IETF working group > > will not include a large enough number of suitable experts in its > > working set. If these reviews are positive, then Working Group > > acceptance of an FEC scheme work item still needs the approval of the > > responsible Area > > Director. > > > > A primary objective of this framework is to support FEC for real-time > > media applications using RTP over UDP, such as on demand streaming and > > audio/video broadcast. Other potential usages of the framework may be > > brought to the working group for consideration during the development > of > > the requirements, to enable future support of those usages. The group > > will coordinate closely with the AVT and MMUSIC working groups to > ensure > > that the streaming use-case is fully specified both in terms of > > interactions with RTP/RTCP and application layer signalling. The group > > will also coordinate with the DCCP working group, at least to consider > > that transport protocol's role in streaming media. The interactions of > > the framework with existing and used security mechanisms must also be > > considered. > > > > The group will work with the RMT working group to ensure that the FEC > > Building Block defined in RMT supports both the RMT use-cases (object > > delivery over multicast) and the more general FEC protection of > > flow(s) over unreliable unicast and multicast transport. > > > > Specification of hybrid schemes involving both retransmission and > > forward error correction is out of scope of the group. > > > > MILESTONES: > > > > Nov 06 - Working Group consensus on requirements and their > > prioritization for the FEC protocol framework > > Mar 07 - Completed selection of solution to develop and mature > > Nov 07 - FEC Streaming Framework submitted as Proposed Standard > > Nov 07 - FEC framework requirements submitted as Informational > > Mar 08 - Usage of FEC framework with RTP submitted as Proposed > Standard > > Mar 08 - FEC framework signalling specification submitted as Proposed > > Standard > > Mar 08 - Discuss re-chartering > > > > _______________________________________________ > 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 Jun 08 13:55:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoOjW-0000bg-Vo; Thu, 08 Jun 2006 13:55:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoOjW-0000bb-O1 for fecframe@ietf.org; Thu, 08 Jun 2006 13:55:50 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FoOjV-0005v5-Gt for fecframe@ietf.org; Thu, 08 Jun 2006 13:55:50 -0400 Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP id 4657542 for fecframe@ietf.org; Thu, 08 Jun 2006 13:55:17 -0400 Mime-Version: 1.0 (Apple Message framework v750) References: <44884D4D.70405@isoc.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <8B63A4C5-9BC9-4AD5-81D4-4BC34D0D5D29@multicasttech.com> Content-Transfer-Encoding: 7bit From: Marshall Eubanks Date: Thu, 8 Jun 2006 13:55:46 -0400 To: fecframe@ietf.org X-Mailer: Apple Mail (2.750) X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Subject: [Fecframe] Fwd: IETF 67 in San Diego 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 FYI Begin forwarded message: > From: Ray Pelletier > Date: June 8, 2006 12:16:13 PM EDT > To: IETF Discussion > Subject: IETF 67 in San Diego > > The IETF is pleased to announce its selection of San Diego, > California, USA and the Sheraton San Diego Hotel & Marina as the > site of IETF 67 being held November 5 - 10, 2006. > > As we celebrate IETF's 20th year we return to the city where IETF > 01 (with 21 attendees) was held, as well as IETFs' 9, 23, 49, and > 60. The Sheraton has added another 18,000 sq ft of meeting space > for us to use. > > Note Well: There are other conferences being held in San Diego so > we encourage you to reserve your hotel rooms right away. > > We have arrangements on Harbor Island with: > > Sheraton San Diego Hotel & Marina for 770 rooms and 50 rooms at the > Hilton San Diego Airport/Marina, both properties with free Internet > in the rooms. More information can be found at: http:// > www.ietf.org/meetings/hotels_67.html > > Registration for San Diego will open July 12th. > > We are looking forward to San Diego in November, but until then we > will see you in Montreal in 31 days! > > And speaking of Montreal, Early Bird registration with its $550 > registration fee expires at 1600 GMT on 30 June! If you have not > registered yet, delay no longer! http://www.ietf.org/meetings/ > IETF-66.html > > Ray Pelletier > IETF Administrative Director > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Sun Jun 11 23:42:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FpdJx-0007cy-FF; Sun, 11 Jun 2006 23:42:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FpdJw-0007cp-Ee for fecframe@ietf.org; Sun, 11 Jun 2006 23:42:32 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FpdJv-0001Ni-8a for fecframe@ietf.org; Sun, 11 Jun 2006 23:42:32 -0400 Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP id 4666342 for fecframe@ietf.org; Sun, 11 Jun 2006 23:41:45 -0400 Mime-Version: 1.0 (Apple Message framework v750) References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Marshall Eubanks Date: Sun, 11 Jun 2006 23:42:26 -0400 To: fecframe@ietf.org X-Mailer: Apple Mail (2.750) X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Subject: [Fecframe] Fwd: FECFRAME - Requested session has been scheduled for IETF 66 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 FYI, in Greg's absence. Anyone who would like speak needs to let us know. Regards Marshall Begin forwarded message: > From: IETF Secretariat > Date: June 11, 2006 2:53:28 PM EDT > To: gjshep@gmail.com > Cc: tme@multicasttech.com, magnus.westerlund@ericsson.com, > lars.eggert@netlab.nec.de, session-request@ietf.org > Subject: FECFRAME - Requested session has been scheduled for IETF 66 > > Dear Greg Shepherd, > > The sessions that you have requested have been scheduled. > Below is the scheduled session information followed by > the information of sessions that you have requested. > > FECFRAME Session 1 (2 hours) > Tuesday, Afternoon Session II 1520-1720 > Room Name: Room 519B > ---------------------------------------------- > > > > Requested Information: > > > --------------------------------------------------------- > Working Group Name: fecframe > Area Name: Transport Area > Session Requester: Greg Shepherd > > Number of Sessions: 1 > Length of Session(s): 2 hours > > > Number of Attendees: 50 > Conflicts to Avoid: > First Priority: rmt avt mboned ippm ips behave nfsv4 pmtud rddp > tcpm tsvwg midcom nsis rohc rserpool > > Special Requests: > Please avoid all other TSV WG meetings and BOFs, if possible > --------------------------------------------------------- > > _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Mon Jun 19 08:31:32 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsIui-000464-F0; Mon, 19 Jun 2006 08:31:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsIuh-00045z-Gj for fecframe@ietf.org; Mon, 19 Jun 2006 08:31:31 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsIug-0002hZ-97 for fecframe@ietf.org; Mon, 19 Jun 2006 08:31:31 -0400 Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP id 4702041 for fecframe@ietf.org; Mon, 19 Jun 2006 08:31:25 -0400 Mime-Version: 1.0 (Apple Message framework v750) References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <10C74034-A934-4320-BE98-F7488464B2EB@multicasttech.com> Content-Transfer-Encoding: 7bit From: Marshall Eubanks Date: Mon, 19 Jun 2006 08:31:28 -0400 To: fecframe@ietf.org X-Mailer: Apple Mail (2.750) X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Subject: [Fecframe] Fwd: Internet-Drafts Submission Cutoff Dates for the 66th IETF Meeting in Montreal, Quebec, Canada 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 that the deadline for new drafts is TODAY. Regards Marshall Begin forwarded message: > From: ietf-secretariat@ietf.org > Date: June 16, 2006 12:00:01 AM EDT > To: ietf-announce@ietf.org > Subject: Internet-Drafts Submission Cutoff Dates for the 66th IETF > Meeting in Montreal, Quebec, Canada > > > There are two (2) Internet-Draft cutoff dates for the 66th > IETF Meeting in Montreal, Quebec, Canada: > > June 19th: Cutoff Date for Initial (i.e., version -00) > Internet-Draft Submissions > > All initial Internet-Drafts (version -00) must be submitted by Monday, > June 19th at 9:00 AM ET. As always, all initial submissions with a > filename beginning with "draft-ietf" must be approved by the > appropriate WG Chair before they can be processed or announced. The > Secretariat would appreciate receiving WG Chair approval by Monday, > June 12th at 9:00 AM ET. > > June 26th: Cutoff Date for Revised (i.e., version -01 and higher) > Internet-Draft Submissions > > All revised Internet-Drafts (version -01 and higher) must be submitted > by Monday, June 26th at 9:00 AM ET. > > Initial and revised Internet-Drafts received after their respective > cutoff dates will not be made available in the Internet-Drafts > directory or announced until on or after Monday, July 10th at 9:00 > AM ET, when Internet-Draft posting resumes. Please do not wait until > the last minute to submit. > > Thank you for your understanding and cooperation. If you have any > questions or concerns, then please send a message to > internet-drafts@ietf.org. > > The IETF Secretariat > > FYI: The Internet-Draft cutoff dates as well as other significant > dates > for the 66th IETF Meeting can be found at http://www.ietf.org/ > meetings/cutoff_dates_66.html. > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Thu Jun 22 13:39:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtT9O-0006eV-4d; Thu, 22 Jun 2006 13:39:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtT9M-0006eN-S8 for fecframe@ietf.org; Thu, 22 Jun 2006 13:39:28 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtT9L-0002d2-L6 for fecframe@ietf.org; Thu, 22 Jun 2006 13:39:28 -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 4710768 for fecframe@ietf.org; Thu, 22 Jun 2006 13:39:09 -0400 Mime-Version: 1.0 (Apple Message framework v750) References: <449AD3BC.8030004@zurich.ibm.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <290057D1-F4A1-4F51-93F4-96D461667678@multicasttech.com> Content-Transfer-Encoding: 7bit From: Marshall Eubanks Date: Thu, 22 Jun 2006 13:39:24 -0400 To: fecframe@ietf.org X-Mailer: Apple Mail (2.750) X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Subject: [Fecframe] Fwd: [Fwd: Montreal agenda still in flux] 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 Well @ Begin forwarded message: > From: Brian E Carpenter > Date: June 22, 2006 1:30:36 PM EDT > To: IETF discussion list > Subject: [Fwd: Montreal agenda still in flux] > > > > -------- Original Message -------- > Subject: Montreal agenda still in flux > Date: Thu, 22 Jun 2006 13:26:51 -0400 > From: IETF Chair > To: IETF Announcement list > > Please be aware that there are still a few unresolved clashes, > and the Secretariat is working on this, so (as always) please do > not be surprised if there are some more agenda changes. Obviously > we attempt to minimize late changes, but they are likely to > continue for several more days. > > For the latest agenda, please check this URL: > > https://datatracker.ietf.org/public/meeting_agenda_html.cgi? > meeting_num=66 > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce > > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Thu Jun 22 19:48:56 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtYuu-0003IV-4S; Thu, 22 Jun 2006 19:48:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtYus-00039p-U1 for fecframe@ietf.org; Thu, 22 Jun 2006 19:48:54 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtYus-0002SE-SY for fecframe@ietf.org; Thu, 22 Jun 2006 19:48:54 -0400 Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FtYrz-0002Gk-7a for fecframe@ietf.org; Thu, 22 Jun 2006 19:45:59 -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 4711372 for fecframe@ietf.org; Thu, 22 Jun 2006 19:45:35 -0400 Mime-Version: 1.0 (Apple Message framework v750) Content-Transfer-Encoding: 7bit Message-Id: <105B30A0-2015-43BA-8BA4-13CC4DEE9E8F@multicasttech.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: fecframe@ietf.org From: Marshall Eubanks Date: Thu, 22 Jun 2006 19:45:53 -0400 X-Mailer: Apple Mail (2.750) X-Spam-Score: -2.4 (--) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Subject: [Fecframe] FECFRAME requirements Draft 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 Since this is taking a little time getting through the Secretariat, I thought I would host it : http://www.multicasttech.com/papers/draft-ietf-fecframe-req-00.html or http://www.multicasttech.com/papers/draft-ietf-fecframe-req-00.txt Regards Marshall _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe