From fecframe-bounces@ietf.org Mon May 5 13:24:18 2008 Return-Path: X-Original-To: fecframe-archive@megatron.ietf.org Delivered-To: ietfarch-fecframe-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF6813A6C38; Mon, 5 May 2008 13:24:18 -0700 (PDT) X-Original-To: fecframe@core3.amsl.com Delivered-To: fecframe@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D502A3A6AC1 for ; Mon, 5 May 2008 13:24:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.298 X-Spam-Level: X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5Gm9WGGB7LY for ; Mon, 5 May 2008 13:24:17 -0700 (PDT) Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 0057E3A6C38 for ; Mon, 5 May 2008 13:24:16 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.27,439,1204531200"; d="scan'208,217";a="25344309" Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-5.cisco.com with ESMTP; 05 May 2008 13:24:15 -0700 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m45KOFtx013865; Mon, 5 May 2008 13:24:15 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m45KOFG2021397; Mon, 5 May 2008 20:24:15 GMT Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 5 May 2008 13:24:15 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 5 May 2008 13:24:47 -0700 Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540703C85B@xmb-sjc-215.amer.cisco.com> In-Reply-To: <241bc2150804241715m76941a23o3aad26ebda431e6e@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft document for clarifying use cases of framework document Thread-Index: AcimaW7hUFPcSnhsQ0KIITwZrV2JRQIhGvyA References: <241bc2150804241715m76941a23o3aad26ebda431e6e@mail.gmail.com> From: "Ali Begen (abegen)" To: =?iso-8859-2?Q?Ula=BA_C=2E_Kozat?= , "Greg Shepherd" , "Marshall Eubanks" X-OriginalArrivalTime: 05 May 2008 20:24:15.0659 (UTC) FILETIME=[FD158FB0:01C8AEED] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3529; t=1210019055; x=1210883055; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=abegen@cisco.com; z=From:=20=22Ali=20Begen=20(abegen)=22=20 |Subject:=20RE=3A=20draft=20document=20for=20clarifying=20u se=20cases=20of=20framework=20document |Sender:=20; bh=VTrmvp4ezqkL6eXMgKWO4qhkoUDGl2rdfmKxjzBo0lQ=; b=eEPWEpAfGZFYF0e82RUvF2RofEgYM3WkcR7rMe2WXPIV4U4cpbIaQ5hWCa iQ1YylovlApuYb1fW+BzoVjOpI+mBHd2eW/NzVsMWF+tU5s2aVSXEASq6nBA UP9TQShJAK; Authentication-Results: sj-dkim-2; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); Cc: fecframe@ietf.org Subject: Re: [Fecframe] draft document for clarifying use cases of framework document X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0027473311==" Sender: fecframe-bounces@ietf.org Errors-To: fecframe-bounces@ietf.org This is a multi-part message in MIME format. --===============0027473311== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8AEED.FCE49A58" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8AEED.FCE49A58 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Any comments at all? Do you agree that this document will be useful or = think it won't be needed? =20 -acbegen ________________________________ From: Ula=BA C. Kozat [mailto:ulas.kozat@gmail.com]=20 Sent: Thursday, April 24, 2008 5:15 PM To: Greg Shepherd; Marshall Eubanks Cc: Ali Begen (abegen); fecframe@ietf.org Subject: draft document for clarifying use cases of framework document =09 =09 Hi Greg and Marshall, =09 We had a brief meeting with Ali today to discuss various issues some = related to the FECFRAME. We think it is a good idea to generate a new = document based on the framework document and explain some parts in more = detail (e.g., how we utilize different fields specified in the framework = as optional and/or required in different scenarios). We want to pay = particular attention to the scenarios where multiple source flows are = protected together by one or multiple repair flows. =09 I am cc-ing to the fecframe list in case people have suggestions or = concerns before we jump into generating such a draft. =09 Ulas =09 =09 =09 ------_=_NextPart_001_01C8AEED.FCE49A58 Content-Type: text/html; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable
Any comments at all? Do you agree that this = document will=20 be useful or think it won't be needed?
 
-acbegen

From: Ula=BA C. Kozat=20 [mailto:ulas.kozat@gmail.com]
Sent: Thursday, April 24, = 2008 5:15=20 PM
To: Greg Shepherd; Marshall Eubanks
Cc: Ali = Begen=20 (abegen); fecframe@ietf.org
Subject: draft document for = clarifying=20 use cases of framework document

Hi Greg and Marshall,

We had a brief meeting with = Ali today=20 to discuss various issues some related to the FECFRAME. We think it is = a good=20 idea to generate a new document based on the framework document and = explain=20 some parts in more detail (e.g., how we utilize different fields = specified in=20 the framework as optional and/or required in different scenarios). We = want to=20 pay particular attention to the scenarios where multiple source flows = are=20 protected together by one or multiple repair flows.

I am cc-ing = to the=20 fecframe list in case people have suggestions or concerns before we = jump into=20 generating such a = draft.

Ulas


------_=_NextPart_001_01C8AEED.FCE49A58-- --===============0027473311== 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://www.ietf.org/mailman/listinfo/fecframe --===============0027473311==-- From fecframe-bounces@ietf.org Thu May 8 09:37:30 2008 Return-Path: X-Original-To: fecframe-archive@megatron.ietf.org Delivered-To: ietfarch-fecframe-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC1E83A724A; Thu, 8 May 2008 09:37:12 -0700 (PDT) X-Original-To: fecframe@core3.amsl.com Delivered-To: fecframe@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C160E3A6D92 for ; Thu, 8 May 2008 09:36:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5a9BqyxDENG5 for ; Thu, 8 May 2008 09:36:43 -0700 (PDT) Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id B1D8528C8A4 for ; Thu, 8 May 2008 09:30:29 -0700 (PDT) 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 11310481 for fecframe@ietf.org; Thu, 08 May 2008 12:30:28 -0400 Message-Id: <32E20416-1303-404A-92A4-A29EA80D55F2@multicasttech.com> From: Marshall Eubanks To: fecframe@ietf.org Mime-Version: 1.0 (Apple Message framework v919.2) Date: Thu, 8 May 2008 12:30:27 -0400 References: <4822E190.8080007@cisco.com> X-Mailer: Apple Mail (2.919.2) Subject: [Fecframe] Fwd: [TICTOC] The tools page X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: fecframe-bounces@ietf.org Errors-To: fecframe-bounces@ietf.org Since I also know that some people in Fecframe are not that familiar with the process here, I thought that Stewart's message might be useful here too. http://tools.ietf.org/wg/fecframe/ Regards Marshall Begin forwarded message: > From: Stewart Bryant > Date: May 8, 2008 7:18:40 AM EDT > To: "tictoc@ietf.org" > Subject: [TICTOC] The tools page > Reply-To: stbryant@cisco.com > > Since I know that a number of people following TICTOC are not familiar > with the IETF process, can I draw your attention to the TICTOC web > page > maintained by the IETF Tools group. > > http://tools.ietf.org/wg/tictoc/ > > From here you can get to pretty well everything that relates to the > TICTOC WG. > > When you come to write drafts you cannot call them > draft-ietf-tictoc-etc-etc until they are accepted by the WG as a work > item. However if you call them draft-yourname-tictoc-etc-etc the tool > will gather them up in the list at the bottom making it easy for > people > to see the set of drafts that relate to our work. > > Stewart > > > > > > > > _______________________________________________ > TICTOC mailing list > TICTOC@ietf.org > https://www.ietf.org/mailman/listinfo/tictoc _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Thu May 8 13:13:13 2008 Return-Path: X-Original-To: fecframe-archive@megatron.ietf.org Delivered-To: ietfarch-fecframe-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E99E3A6E07; Thu, 8 May 2008 13:13:13 -0700 (PDT) X-Original-To: fecframe@core3.amsl.com Delivered-To: fecframe@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 511753A6E05 for ; Thu, 8 May 2008 13:13:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tYQKn3IjCDjf for ; Thu, 8 May 2008 13:13:11 -0700 (PDT) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by core3.amsl.com (Postfix) with ESMTP id 441C93A66B4 for ; Thu, 8 May 2008 13:13:11 -0700 (PDT) Received: by an-out-0708.google.com with SMTP id d18so567280and.122 for ; Thu, 08 May 2008 13:13:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=j2j5H4HgMOr5ifsR5fyL2g3RoWBlfKUKpxhriCPJJAA=; b=QlmVo/Km46k+Ssn8TZRFaCJn3jO2EHHc52ylZThEC+GuQnPHpARX9g0i35mmV9vyvZhG5gT2LBDyZthePtuX437KkOM7hs+wpByEY9CWO7Bl6/4bHJv4Nq1oSM5E7rE2SjPBZHIvUCIMnQaVj0Cghp3re2f5PLLRIXM6rqYhU/4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JIQ0bOzIvAuy/qgQG1Zy4IzR1PfG8Kx0oJSwMj5A/gWYb5pXKPvykpmxv9P66ZuK7eRtGISrlVMrIYBD2Ur4zMPpWvEku7nvzrK7EwCkmjZVbBXr33G5kWyqD7qUqDbk8xW7h0ycoMJWAwxXz+hPDmdSSE2uuJatAU8rZP6E2VQ= Received: by 10.101.69.6 with SMTP id w6mr4979614ank.63.1210277588925; Thu, 08 May 2008 13:13:08 -0700 (PDT) Received: by 10.100.125.10 with HTTP; Thu, 8 May 2008 13:13:08 -0700 (PDT) Message-ID: <38c19b540805081313yb630d8aj3a9d21cc90f4b59e@mail.gmail.com> Date: Thu, 8 May 2008 13:13:08 -0700 From: "Greg Shepherd" To: "Ali Begen (abegen)" In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540703C85B@xmb-sjc-215.amer.cisco.com> MIME-Version: 1.0 Content-Disposition: inline References: <241bc2150804241715m76941a23o3aad26ebda431e6e@mail.gmail.com> <04CAD96D4C5A3D48B1919248A8FE0D540703C85B@xmb-sjc-215.amer.cisco.com> Cc: fecframe@ietf.org Subject: Re: [Fecframe] draft document for clarifying use cases of framework document X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Sender: fecframe-bounces@ietf.org Errors-To: fecframe-bounces@ietf.org Well, there were a couple of group participants I would have expected to shout "yes", but nothing but crickets here... If you do pursue this document I think an important part (or maybe another doc?) would be a scheme template. Greg 2008/5/5 Ali Begen (abegen) : > > > Any comments at all? Do you agree that this document will be useful or th= ink > it won't be needed? > > -acbegen > > > ________________________________ > From: Ula=BA C. Kozat [mailto:ulas.kozat@gmail.com] > Sent: Thursday, April 24, 2008 5:15 PM > To: Greg Shepherd; Marshall Eubanks > Cc: Ali Begen (abegen); fecframe@ietf.org > Subject: draft document for clarifying use cases of framework document > > > > Hi Greg and Marshall, > > We had a brief meeting with Ali today to discuss various issues some rela= ted > to the FECFRAME. We think it is a good idea to generate a new document ba= sed > on the framework document and explain some parts in more detail (e.g., how > we utilize different fields specified in the framework as optional and/or > required in different scenarios). We want to pay particular attention to = the > scenarios where multiple source flows are protected together by one or > multiple repair flows. > > I am cc-ing to the fecframe list in case people have suggestions or conce= rns > before we jump into generating such a draft. > > Ulas > > > _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Thu May 8 14:53:47 2008 Return-Path: X-Original-To: fecframe-archive@megatron.ietf.org Delivered-To: ietfarch-fecframe-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F71E3A6E4F; Thu, 8 May 2008 14:53:47 -0700 (PDT) X-Original-To: fecframe@core3.amsl.com Delivered-To: fecframe@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C66C528C2C8 for ; Thu, 8 May 2008 14:53:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2VeSSMJXURWh for ; Thu, 8 May 2008 14:53:45 -0700 (PDT) Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id C568F3A6A3D for ; Thu, 8 May 2008 14:53:45 -0700 (PDT) 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 11312829; Thu, 08 May 2008 17:53:43 -0400 Message-Id: From: Marshall Eubanks To: "Greg Shepherd" In-Reply-To: <38c19b540805081313yb630d8aj3a9d21cc90f4b59e@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v919.2) Date: Thu, 8 May 2008 17:53:38 -0400 References: <241bc2150804241715m76941a23o3aad26ebda431e6e@mail.gmail.com> <04CAD96D4C5A3D48B1919248A8FE0D540703C85B@xmb-sjc-215.amer.cisco.com> <38c19b540805081313yb630d8aj3a9d21cc90f4b59e@mail.gmail.com> X-Mailer: Apple Mail (2.919.2) Cc: fecframe@ietf.org Subject: Re: [Fecframe] draft document for clarifying use cases of framework document X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: fecframe-bounces@ietf.org Errors-To: fecframe-bounces@ietf.org SnVzdCBhcyBhIGdyb3VwIG1lbWJlciwgY291bnQgbWUgYXMgYSArMSBoZXJlLgoKKFllcywgSSB0 aGluayB0aGF0IHRoaXMgZG9jdW1lbnQgd291bGQgYmUgdXNlZnVsIGFuZCBuZWNlc3NhcnkpLgoK UmVnYXJkcwpNYXJzaGFsbAoKT24gTWF5IDgsIDIwMDgsIGF0IDQ6MTMgUE0sIEdyZWcgU2hlcGhl cmQgd3JvdGU6Cgo+IFdlbGwsIHRoZXJlIHdlcmUgYSBjb3VwbGUgb2YgZ3JvdXAgcGFydGljaXBh bnRzIEkgd291bGQgaGF2ZSBleHBlY3RlZAo+IHRvIHNob3V0ICJ5ZXMiLCBidXQgbm90aGluZyBi dXQgY3JpY2tldHMgaGVyZS4uLiBJZiB5b3UgZG8gcHVyc3VlIHRoaXMKPiBkb2N1bWVudCBJIHRo aW5rIGFuIGltcG9ydGFudCBwYXJ0IChvciBtYXliZSBhbm90aGVyIGRvYz8pIHdvdWxkIGJlIGEK PiBzY2hlbWUgdGVtcGxhdGUuCj4KPiBHcmVnCj4KPiAyMDA4LzUvNSBBbGkgQmVnZW4gKGFiZWdl bikgPGFiZWdlbkBjaXNjby5jb20+Ogo+Pgo+Pgo+PiBBbnkgY29tbWVudHMgYXQgYWxsPyBEbyB5 b3UgYWdyZWUgdGhhdCB0aGlzIGRvY3VtZW50IHdpbGwgYmUgdXNlZnVsICAKPj4gb3IgdGhpbmsK Pj4gaXQgd29uJ3QgYmUgbmVlZGVkPwo+Pgo+PiAtYWNiZWdlbgo+Pgo+Pgo+PiBfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXwo+PiBGcm9tOiBVbGHFnyBDLiBLb3phdCBbbWFpbHRvOnVs YXMua296YXRAZ21haWwuY29tXQo+PiBTZW50OiBUaHVyc2RheSwgQXByaWwgMjQsIDIwMDggNTox NSBQTQo+PiBUbzogR3JlZyBTaGVwaGVyZDsgTWFyc2hhbGwgRXViYW5rcwo+PiBDYzogQWxpIEJl Z2VuIChhYmVnZW4pOyBmZWNmcmFtZUBpZXRmLm9yZwo+PiBTdWJqZWN0OiBkcmFmdCBkb2N1bWVu dCBmb3IgY2xhcmlmeWluZyB1c2UgY2FzZXMgb2YgZnJhbWV3b3JrICAKPj4gZG9jdW1lbnQKPj4K Pj4KPj4KPj4gSGkgR3JlZyBhbmQgTWFyc2hhbGwsCj4+Cj4+IFdlIGhhZCBhIGJyaWVmIG1lZXRp bmcgd2l0aCBBbGkgdG9kYXkgdG8gZGlzY3VzcyB2YXJpb3VzIGlzc3VlcyAgCj4+IHNvbWUgcmVs YXRlZAo+PiB0byB0aGUgRkVDRlJBTUUuIFdlIHRoaW5rIGl0IGlzIGEgZ29vZCBpZGVhIHRvIGdl bmVyYXRlIGEgbmV3ICAKPj4gZG9jdW1lbnQgYmFzZWQKPj4gb24gdGhlIGZyYW1ld29yayBkb2N1 bWVudCBhbmQgZXhwbGFpbiBzb21lIHBhcnRzIGluIG1vcmUgZGV0YWlsICAKPj4gKGUuZy4sIGhv dwo+PiB3ZSB1dGlsaXplIGRpZmZlcmVudCBmaWVsZHMgc3BlY2lmaWVkIGluIHRoZSBmcmFtZXdv cmsgYXMgb3B0aW9uYWwgIAo+PiBhbmQvb3IKPj4gcmVxdWlyZWQgaW4gZGlmZmVyZW50IHNjZW5h cmlvcykuIFdlIHdhbnQgdG8gcGF5IHBhcnRpY3VsYXIgIAo+PiBhdHRlbnRpb24gdG8gdGhlCj4+ IHNjZW5hcmlvcyB3aGVyZSBtdWx0aXBsZSBzb3VyY2UgZmxvd3MgYXJlIHByb3RlY3RlZCB0b2dl dGhlciBieSBvbmUgIAo+PiBvcgo+PiBtdWx0aXBsZSByZXBhaXIgZmxvd3MuCj4+Cj4+IEkgYW0g Y2MtaW5nIHRvIHRoZSBmZWNmcmFtZSBsaXN0IGluIGNhc2UgcGVvcGxlIGhhdmUgc3VnZ2VzdGlv bnMgb3IgIAo+PiBjb25jZXJucwo+PiBiZWZvcmUgd2UganVtcCBpbnRvIGdlbmVyYXRpbmcgc3Vj aCBhIGRyYWZ0Lgo+Pgo+PiBVbGFzCj4+Cj4+Cj4+CgpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXwpGZWNmcmFtZSBtYWlsaW5nIGxpc3QKRmVjZnJhbWVAaWV0 Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9mZWNmcmFtZQo= From fecframe-bounces@ietf.org Mon May 26 08:07:45 2008 Return-Path: X-Original-To: fecframe-archive@megatron.ietf.org Delivered-To: ietfarch-fecframe-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 743963A69B8; Mon, 26 May 2008 08:07:45 -0700 (PDT) X-Original-To: fecframe@core3.amsl.com Delivered-To: fecframe@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D8E0F3A68A5 for ; Mon, 26 May 2008 08:07:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.462 X-Spam-Level: X-Spam-Status: No, score=-103.462 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gtdgpdSHnLPx for ; Mon, 26 May 2008 08:07:38 -0700 (PDT) Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 5AA043A69B8 for ; Mon, 26 May 2008 08:07:38 -0700 (PDT) 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 11519326 for fecframe@ietf.org; Mon, 26 May 2008 11:07:41 -0400 Message-Id: From: Marshall Eubanks To: fecframe@ietf.org Mime-Version: 1.0 (Apple Message framework v919.2) Date: Mon, 26 May 2008 11:07:16 -0400 X-Mailer: Apple Mail (2.919.2) Subject: [Fecframe] WG Adoption of draft-asati-fecframe-config-signaling X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: fecframe-bounces@ietf.org Errors-To: fecframe-bounces@ietf.org We would like to judge acceptance by the list on the adoption of http://tools.ietf.org/html/draft-asati-fecframe-config-signaling-00 by the WG. There was consensus in the room for doing this in Philadelphia, so I think that 1 week would be sufficient for this. So, please comment on this draft and specifically on whether or not it should be adopted by the group by next Monday, June 2nd, Noon EDT. Regards Marshall _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Wed May 28 22:57:56 2008 Return-Path: X-Original-To: fecframe-archive@megatron.ietf.org Delivered-To: ietfarch-fecframe-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CDF528C1AA; Wed, 28 May 2008 22:57:56 -0700 (PDT) X-Original-To: fecframe@core3.amsl.com Delivered-To: fecframe@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 322633A68A6 for ; Wed, 28 May 2008 22:57:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.4 X-Spam-Level: X-Spam-Status: No, score=-3.4 tagged_above=-999 required=5 tests=[J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYPe5h3tnsS5 for ; Wed, 28 May 2008 22:57:54 -0700 (PDT) Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id E762F28C1D8 for ; Wed, 28 May 2008 22:57:53 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.27,560,1204520400"; d="scan'208";a="9510556" Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 29 May 2008 01:57:53 -0400 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4T5vqDB025671 for ; Thu, 29 May 2008 01:57:52 -0400 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4T5vqjn004670 for ; Thu, 29 May 2008 05:57:52 GMT Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 29 May 2008 01:57:52 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 29 May 2008 01:56:14 -0400 Message-ID: <15B86BC7352F864BB53A47B540C089B6058C65C6@xmb-rtp-20b.amer.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Fecframe Digest, Vol 28, Issue 3 Thread-Index: AciyBub1ypp5wneaR46IjMffeJ2+lAAV0mBw References: From: "Rajiv Asati (rajiva)" To: X-OriginalArrivalTime: 29 May 2008 05:57:52.0653 (UTC) FILETIME=[EEB653D0:01C8C150] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5710; t=1212040672; x=1212904672; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rajiva@cisco.com; z=From:=20=22Rajiv=20Asati=20(rajiva)=22=20 |Subject:=20RE=3A=20Fecframe=20Digest,=20Vol=2028,=20Issue= 203 |Sender:=20 |To:=20; bh=cmK+4lqIFByIo932Eb2Bss3hg6XvNmrFxRvL+mIt9ws=; b=I99CmVlswJixfsnns4177MEc/FDy8UGI+M5TM1Y+KLuvQj2ud+kAbILuAH mNTSwgQIl0Hkd2tdLpPihpD+0Ue6NjPwUWLseACfbdQtvkzmWX6Fg41mQsY5 0unTEdd0CR; Authentication-Results: rtp-dkim-1; header.From=rajiva@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); Subject: Re: [Fecframe] Fecframe Digest, Vol 28, Issue 3 X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: fecframe-bounces@ietf.org Errors-To: fecframe-bounces@ietf.org +1 in support. Cheers, Rajiv > -----Original Message----- > From: fecframe-bounces@ietf.org > [mailto:fecframe-bounces@ietf.org] On Behalf Of > fecframe-request@ietf.org > Sent: Friday, May 09, 2008 3:00 PM > To: fecframe@ietf.org > Subject: Fecframe Digest, Vol 28, Issue 3 > > Send Fecframe mailing list submissions to > fecframe@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/fecframe > or, via email, send a message with subject or body 'help' to > fecframe-request@ietf.org > > You can reach the person managing the list at > fecframe-owner@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Fecframe digest..." > > > Today's Topics: > > 1. Re: draft document for clarifying use cases of framework > document (Greg Shepherd) > 2. Re: draft document for clarifying use cases of framework > document (Marshall Eubanks) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 8 May 2008 13:13:08 -0700 > From: "Greg Shepherd" > Subject: Re: [Fecframe] draft document for clarifying use cases of > framework document > To: "Ali Begen (abegen)" > Cc: fecframe@ietf.org > Message-ID: > <38c19b540805081313yb630d8aj3a9d21cc90f4b59e@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-2 > > Well, there were a couple of group participants I would have expected > to shout "yes", but nothing but crickets here... If you do pursue this > document I think an important part (or maybe another doc?) would be a > scheme template. > > Greg > > 2008/5/5 Ali Begen (abegen) : > > > > > > Any comments at all? Do you agree that this document will > be useful or think > > it won't be needed? > > > > -acbegen > > > > > > ________________________________ > > From: Ula? C. Kozat [mailto:ulas.kozat@gmail.com] > > Sent: Thursday, April 24, 2008 5:15 PM > > To: Greg Shepherd; Marshall Eubanks > > Cc: Ali Begen (abegen); fecframe@ietf.org > > Subject: draft document for clarifying use cases of > framework document > > > > > > > > Hi Greg and Marshall, > > > > We had a brief meeting with Ali today to discuss various > issues some related > > to the FECFRAME. We think it is a good idea to generate a > new document based > > on the framework document and explain some parts in more > detail (e.g., how > > we utilize different fields specified in the framework as > optional and/or > > required in different scenarios). We want to pay particular > attention to the > > scenarios where multiple source flows are protected > together by one or > > multiple repair flows. > > > > I am cc-ing to the fecframe list in case people have > suggestions or concerns > > before we jump into generating such a draft. > > > > Ulas > > > > > > > > ------------------------------ > > Message: 2 > Date: Thu, 8 May 2008 17:53:38 -0400 > From: Marshall Eubanks > Subject: Re: [Fecframe] draft document for clarifying use cases of > framework document > To: "Greg Shepherd" > Cc: fecframe@ietf.org > Message-ID: > Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes > > Just as a group member, count me as a +1 here. > > (Yes, I think that this document would be useful and necessary). > > Regards > Marshall > > On May 8, 2008, at 4:13 PM, Greg Shepherd wrote: > > > Well, there were a couple of group participants I would > have expected > > to shout "yes", but nothing but crickets here... If you do > pursue this > > document I think an important part (or maybe another doc?) > would be a > > scheme template. > > > > Greg > > > > 2008/5/5 Ali Begen (abegen) : > >> > >> > >> Any comments at all? Do you agree that this document will > be useful > >> or think > >> it won't be needed? > >> > >> -acbegen > >> > >> > >> ________________________________ > >> From: Ula? C. Kozat [mailto:ulas.kozat@gmail.com] > >> Sent: Thursday, April 24, 2008 5:15 PM > >> To: Greg Shepherd; Marshall Eubanks > >> Cc: Ali Begen (abegen); fecframe@ietf.org > >> Subject: draft document for clarifying use cases of framework > >> document > >> > >> > >> > >> Hi Greg and Marshall, > >> > >> We had a brief meeting with Ali today to discuss various issues > >> some related > >> to the FECFRAME. We think it is a good idea to generate a new > >> document based > >> on the framework document and explain some parts in more detail > >> (e.g., how > >> we utilize different fields specified in the framework as > optional > >> and/or > >> required in different scenarios). We want to pay particular > >> attention to the > >> scenarios where multiple source flows are protected > together by one > >> or > >> multiple repair flows. > >> > >> I am cc-ing to the fecframe list in case people have > suggestions or > >> concerns > >> before we jump into generating such a draft. > >> > >> Ulas > >> > >> > >> > > > > ------------------------------ > > _______________________________________________ > Fecframe mailing list > Fecframe@ietf.org > https://www.ietf.org/mailman/listinfo/fecframe > > > End of Fecframe Digest, Vol 28, Issue 3 > *************************************** > _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www.ietf.org/mailman/listinfo/fecframe From fecframe-bounces@ietf.org Thu May 29 06:46:25 2008 Return-Path: X-Original-To: fecframe-archive@megatron.ietf.org Delivered-To: ietfarch-fecframe-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 200973A6B89; Thu, 29 May 2008 06:46:25 -0700 (PDT) X-Original-To: fecframe@core3.amsl.com Delivered-To: fecframe@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90BE03A6B89 for ; Thu, 29 May 2008 06:46:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_53=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v3LWb-OQz7ek for ; Thu, 29 May 2008 06:46:18 -0700 (PDT) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by core3.amsl.com (Postfix) with ESMTP id DB6CA3A6C04 for ; Thu, 29 May 2008 06:45:50 -0700 (PDT) Received: by an-out-0708.google.com with SMTP id d18so126595and.122 for ; Thu, 29 May 2008 06:45:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=QhRcdQzfqeusFLKEx3T5LsXwk8ptcgJRoUtky+eWDJo=; b=uHlkR3HZZawx59XZqAxq555Ziqokgao3su/6QXr7bFF0CjyDHTKzTN/Tkv49YAUtiqSQCFNlg/ZgsRPESL9mEBCxfMkspDaD7cgqzb3fRa1ztq3QfFokLa2zKU8YvW0OgX4oTZlS+6V6BzgSqRtANC+yI5leJtFXGM59qOBlDY8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pD1zrgqHdQ1sEL2vv+xeOfEHJdGV5rw+qFzk60cHhubvPwCLO+VD/Vv78rDDrDGYs/AD7dEaLZ6O6DJN3TlxXDRuSBU7+OXgd2ENEdEg3xf8b4Mm/t4/3FpGq5x+bt6GRwt0tD0pjKh4vxJXGOsbt3ms/Gf8a8Ot6kdmw2cS4BM= Received: by 10.100.33.4 with SMTP id g4mr6403498ang.128.1212068749738; Thu, 29 May 2008 06:45:49 -0700 (PDT) Received: by 10.100.112.16 with HTTP; Thu, 29 May 2008 06:45:49 -0700 (PDT) Message-ID: <38c19b540805290645h7efca529re318bf2d619f0c0@mail.gmail.com> Date: Thu, 29 May 2008 06:45:49 -0700 From: "Greg Shepherd" To: "Rajiv Asati (rajiva)" In-Reply-To: <15B86BC7352F864BB53A47B540C089B6058C65C6@xmb-rtp-20b.amer.cisco.com> MIME-Version: 1.0 Content-Disposition: inline References: <15B86BC7352F864BB53A47B540C089B6058C65C6@xmb-rtp-20b.amer.cisco.com> Cc: fecframe@ietf.org Subject: Re: [Fecframe] Fecframe Digest, Vol 28, Issue 3 X-BeenThere: fecframe@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of FEC Framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: fecframe-bounces@ietf.org Errors-To: fecframe-bounces@ietf.org I agree... We need more feedback please. Anyone else agree or not? Thanks, Greg On Wed, May 28, 2008 at 10:56 PM, Rajiv Asati (rajiva) wrote: > > +1 in support. > > Cheers, > Rajiv > >> -----Original Message----- >> From: fecframe-bounces@ietf.org >> [mailto:fecframe-bounces@ietf.org] On Behalf Of >> fecframe-request@ietf.org >> Sent: Friday, May 09, 2008 3:00 PM >> To: fecframe@ietf.org >> Subject: Fecframe Digest, Vol 28, Issue 3 >> >> Send Fecframe mailing list submissions to >> fecframe@ietf.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://www.ietf.org/mailman/listinfo/fecframe >> or, via email, send a message with subject or body 'help' to >> fecframe-request@ietf.org >> >> You can reach the person managing the list at >> fecframe-owner@ietf.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Fecframe digest..." >> >> >> Today's Topics: >> >> 1. Re: draft document for clarifying use cases of framework >> document (Greg Shepherd) >> 2. Re: draft document for clarifying use cases of framework >> document (Marshall Eubanks) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 8 May 2008 13:13:08 -0700 >> From: "Greg Shepherd" >> Subject: Re: [Fecframe] draft document for clarifying use cases of >> framework document >> To: "Ali Begen (abegen)" >> Cc: fecframe@ietf.org >> Message-ID: >> <38c19b540805081313yb630d8aj3a9d21cc90f4b59e@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-2 >> >> Well, there were a couple of group participants I would have expected >> to shout "yes", but nothing but crickets here... If you do pursue this >> document I think an important part (or maybe another doc?) would be a >> scheme template. >> >> Greg >> >> 2008/5/5 Ali Begen (abegen) : >> > >> > >> > Any comments at all? Do you agree that this document will >> be useful or think >> > it won't be needed? >> > >> > -acbegen >> > >> > >> > ________________________________ >> > From: Ula? C. Kozat [mailto:ulas.kozat@gmail.com] >> > Sent: Thursday, April 24, 2008 5:15 PM >> > To: Greg Shepherd; Marshall Eubanks >> > Cc: Ali Begen (abegen); fecframe@ietf.org >> > Subject: draft document for clarifying use cases of >> framework document >> > >> > >> > >> > Hi Greg and Marshall, >> > >> > We had a brief meeting with Ali today to discuss various >> issues some related >> > to the FECFRAME. We think it is a good idea to generate a >> new document based >> > on the framework document and explain some parts in more >> detail (e.g., how >> > we utilize different fields specified in the framework as >> optional and/or >> > required in different scenarios). We want to pay particular >> attention to the >> > scenarios where multiple source flows are protected >> together by one or >> > multiple repair flows. >> > >> > I am cc-ing to the fecframe list in case people have >> suggestions or concerns >> > before we jump into generating such a draft. >> > >> > Ulas >> > >> > >> > >> >> ------------------------------ >> >> Message: 2 >> Date: Thu, 8 May 2008 17:53:38 -0400 >> From: Marshall Eubanks >> Subject: Re: [Fecframe] draft document for clarifying use cases of >> framework document >> To: "Greg Shepherd" >> Cc: fecframe@ietf.org >> Message-ID: >> Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes >> >> Just as a group member, count me as a +1 here. >> >> (Yes, I think that this document would be useful and necessary). >> >> Regards >> Marshall >> >> On May 8, 2008, at 4:13 PM, Greg Shepherd wrote: >> >> > Well, there were a couple of group participants I would >> have expected >> > to shout "yes", but nothing but crickets here... If you do >> pursue this >> > document I think an important part (or maybe another doc?) >> would be a >> > scheme template. >> > >> > Greg >> > >> > 2008/5/5 Ali Begen (abegen) : >> >> >> >> >> >> Any comments at all? Do you agree that this document will >> be useful >> >> or think >> >> it won't be needed? >> >> >> >> -acbegen >> >> >> >> >> >> ________________________________ >> >> From: Ula? C. Kozat [mailto:ulas.kozat@gmail.com] >> >> Sent: Thursday, April 24, 2008 5:15 PM >> >> To: Greg Shepherd; Marshall Eubanks >> >> Cc: Ali Begen (abegen); fecframe@ietf.org >> >> Subject: draft document for clarifying use cases of framework >> >> document >> >> >> >> >> >> >> >> Hi Greg and Marshall, >> >> >> >> We had a brief meeting with Ali today to discuss various issues >> >> some related >> >> to the FECFRAME. We think it is a good idea to generate a new >> >> document based >> >> on the framework document and explain some parts in more detail >> >> (e.g., how >> >> we utilize different fields specified in the framework as >> optional >> >> and/or >> >> required in different scenarios). We want to pay particular >> >> attention to the >> >> scenarios where multiple source flows are protected >> together by one >> >> or >> >> multiple repair flows. >> >> >> >> I am cc-ing to the fecframe list in case people have >> suggestions or >> >> concerns >> >> before we jump into generating such a draft. >> >> >> >> Ulas >> >> >> >> >> >> >> >> >> >> ------------------------------ >> >> _______________________________________________ >> Fecframe mailing list >> Fecframe@ietf.org >> https://www.ietf.org/mailman/listinfo/fecframe >> >> >> End of Fecframe Digest, Vol 28, Issue 3 >> *************************************** >> > _______________________________________________ > Fecframe mailing list > Fecframe@ietf.org > https://www.ietf.org/mailman/listinfo/fecframe > _______________________________________________ Fecframe mailing list Fecframe@ietf.org https://www.ietf.org/mailman/listinfo/fecframe