From fecframe-bounces@ietf.org Wed Jan 10 11:17:41 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4g8z-0008QQ-T1; Wed, 10 Jan 2007 11:17:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4g8x-0008O7-LZ
	for fecframe@ietf.org; Wed, 10 Jan 2007 11:17:39 -0500
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4g8w-0006Np-Ct
	for fecframe@ietf.org; Wed, 10 Jan 2007 11:17:39 -0500
Received: by ug-out-1314.google.com with SMTP id a2so151677ugf
	for <fecframe@ietf.org>; Wed, 10 Jan 2007 08:17:37 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=asRXgB7epmoLIJdQ0QsQ9KR9khE0gp7lTnIYTeMLBykL1BMbuSpoEfe1vfMmSTgm9PXCz5eHZmjBOY4dGybu/D48++Sh/l4dXL6grglhyrIPkA4EyMH/5cNisVWgxtMmRrrAPzgD44XyoATFAZ+bmzEszka7yNMmr6RNZh7doVo=
Received: by 10.78.178.5 with SMTP id a5mr132944huf.1168445856519;
	Wed, 10 Jan 2007 08:17:36 -0800 (PST)
Received: by 10.78.120.17 with HTTP; Wed, 10 Jan 2007 08:17:36 -0800 (PST)
Message-ID: <38c19b540701100817n847d4aewc74423d519826f84@mail.gmail.com>
Date: Wed, 10 Jan 2007 08:17:36 -0800
From: "Greg Shepherd" <gjshep@gmail.com>
To: fecframe@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: [Fecframe] Prep for Prague
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of FEC Framework <fecframe.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/fecframe>,
	<mailto:fecframe-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/fecframe>
List-Post: <mailto:fecframe@ietf.org>
List-Help: <mailto:fecframe-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/fecframe>,
	<mailto:fecframe-request@ietf.org?subject=subscribe>
Errors-To: fecframe-bounces@ietf.org

It's time once again to shedule our WG slot for the next meeting, and
develop an agenda. As usual the traffic on this list was blistering -
made even more torrent from the holidays. ;-)

Please send any agenda items too me and/or the list and I'll accumulate.

Some important dates below:

- Cut-off date for requesting a Working Group session and for preliminary
BOF proposals to ADs: Monday, January 15 at 17:00 ET (22:00 UTC/GMT).
-- Cut-off date for requests to schedule BoFs: Monday, February 5 at 17:00
ET (22:00 UTC/GMT).
-- Preliminary agenda published for comment: Friday, February 9 by
midnight ET.
-- Cut-off date for requests to reschedule a session: Wednesday, February
21 at 09:00 ET (14:00 UTC/GMT).
-- Final schedule published: Monday, February 26 before midnight ET.
-- Draft Working Group agendas due: Wednesday, March 7 at 17:00 ET (22:00
UTC/GMT).
-- Revised Working Group agendas due: Monday, March 12 at 12:00 ET (16:00
UTC/GMT), upload using IETF Meeting Materials Management Tool

Thanks,
Greg

_______________________________________________
Fecframe mailing list
Fecframe@ietf.org
https://www1.ietf.org/mailman/listinfo/fecframe



From fecframe-bounces@ietf.org Sun Jan 21 22:28:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H8pr8-0002DZ-A6; Sun, 21 Jan 2007 22:28:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H8pr7-0002DU-Ml
	for fecframe@ietf.org; Sun, 21 Jan 2007 22:28:25 -0500
Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H8pr6-00007G-Dj
	for fecframe@ietf.org; Sun, 21 Jan 2007 22:28:25 -0500
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 6106820; Sun, 21 Jan 2007 22:28:21 -0500
In-Reply-To: <52E27EC4-E2BB-4A28-8272-72A35E956169@multicasttech.com>
References: <38c19b540612071735q552e205el38ecad46aeb8b3cb@mail.gmail.com>
	<26EBB276-A3BB-4727-9000-B11FF3D9CC9D@stewe.org>
	<48405AC9-C9CB-4279-A94B-3FF8003A9D96@digitalfountain.com>
	<38c19b540612071937kc7aa1d1x6da67d9897bc4691@mail.gmail.com>
	<52E27EC4-E2BB-4A28-8272-72A35E956169@multicasttech.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9722828D-0320-4D80-A95A-4DECD54D036D@multicasttech.com>
Content-Transfer-Encoding: 7bit
From: Marshall Eubanks <tme@multicasttech.com>
Subject: Re: WG Adoption of draft-watson-fecframe-framework-00.txt - was Re:
	[Fecframe] Next steps..
Date: Sun, 21 Jan 2007 22:28:16 -0500
To: Marshall Eubanks <tme@multicasttech.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: fecframe@ietf.org
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of FEC Framework <fecframe.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/fecframe>,
	<mailto:fecframe-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/fecframe>
List-Post: <mailto:fecframe@ietf.org>
List-Help: <mailto:fecframe-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/fecframe>,
	<mailto:fecframe-request@ietf.org?subject=subscribe>
Errors-To: fecframe-bounces@ietf.org

This comment period having long expired, I declare consensus to adopt  
this document as a WG draft.

Mark, could you please send this in to the Secretariat as an ietf- 
fecframe draft ?

Regards
Marshall

On Dec 8, 2006, at 7:27 PM, Marshall Eubanks wrote:

> My feeling is that there was consensus at the meeting to adopt  
> draft-watson-fecframe-framework-00.txt
> as a working group document. This needs to be ratified by the list.
>
> This is a mini call for comments on this matter, which will expire  
> 5 PM PST Friday Dec 15.
>
> If you agree, and especially if you disagree,
> please speak up. Of course, comments on the document text are also  
> appropriate and welcomed.
>
> Regards
> Marshall Eubanks
>
>
> On Dec 7, 2006, at 10:37 PM, Greg Shepherd wrote:
>
>> On 12/7/06, Mark Watson <mark@digitalfountain.com> wrote:
>>> I agree - just because there isn't a single formal term doesn't mean
>>> we can't agree that the document is 'frozen' - so long as we all
>>> understand what that actually means, which is just that it will form
>>> the basis of our work and we don't see any need now for further  
>>> changes.
>>
>> Agreed. I suppose I was imagining a official "frozen" status would  
>> let
>> it live in draft form without expiration. Other than that I see  
>> little
>> benefit
>>
>>> I think you need to qualify that hum on draft-watson-fecframe-
>>> framework-00.txt was to adopt *as a working group document*.
>>
>> Yes, thanks!
>>
>> Greg
>>
>>> ...Mark
>>>
>>> On Dec 7, 2006, at 5:57 PM, Stephan Wenger wrote:
>>>
>>> > I'm happy with the requirements and have therefore no problem to
>>> > consider the draft "frozen".  Couldn't care less how to express
>>> > that formally.
>>> > Regards,
>>> > Stephan
>>> >
>>> > On Dec 7, 2006, at 5:35 PM, Greg Shepherd wrote:
>>> >
>>> >> Greetings,
>>> >>
>>> >> We have two list items from the San Diego meeting, and this  
>>> year is
>>> >> about gone...
>>> >>
>>> >> It was suggested that we hold off on last-call for
>>> >> draft-fecframe-req-01.txt to leave us flexibility as we learn  
>>> going
>>> >> forward. Someone mentioned considering a freeze-call.
>>> >>
>>> >> A search of ietf.org for freeze call brings up only five  
>>> references;
>>> >> one from our last minutes and the other four from ROHC. The  
>>> IETF-ID
>>> >> tracker has 17 choices for Document State - two of them being  
>>> Last
>>> >> Call Requested, and In Last Call - but no mention of freeze-call.
>>> >>
>>> >> But I suppose we can still get consensus here on the list for  
>>> the req
>>> >> draft itself. From there we can decide if there is really such a
>>> >> thing
>>> >> as a freeze-call, what it buys us, and whether it fits.
>>> >>
>>> >> So, please - read and respond.
>>> >>
>>> >> Next, draft-watson-fecframe-framework-00.txt was presented and
>>> >> received a humming acceptance for adoption.
>>> >>
>>> >> Again, read and respond please.
>>> >>
>>> >> 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
>>>
>>>
>>
>> _______________________________________________
>> 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


_______________________________________________
Fecframe mailing list
Fecframe@ietf.org
https://www1.ietf.org/mailman/listinfo/fecframe



