RE: [FECFRAME-PROTO] Protocol Design Team Meeting, Jan 29th
"Rajiv Asati (rajiva)" <rajiva@cisco.com> Mon, 28 January 2008 16:26 UTC
Return-path: <fecframe-proto-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJWoP-0005Jr-JQ; Mon, 28 Jan 2008 11:26:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJWoO-0005Jl-LQ for fecframe-proto@ietf.org; Mon, 28 Jan 2008 11:26:20 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJWoO-0000UK-6g for fecframe-proto@ietf.org; Mon, 28 Jan 2008 11:26:20 -0500
X-IronPort-AV: E=Sophos;i="4.25,260,1199682000"; d="scan'208";a="84737547"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 28 Jan 2008 11:26:18 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m0SGQGJc030217; Mon, 28 Jan 2008 11:26:16 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m0SGQ1Vt027230; Mon, 28 Jan 2008 16:26:16 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); Mon, 28 Jan 2008 11:26:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [FECFRAME-PROTO] Protocol Design Team Meeting, Jan 29th
Date: Mon, 28 Jan 2008 11:25:34 -0500
Message-ID: <15B86BC7352F864BB53A47B540C089B604CF0AE4@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <C3C26D94.224AA%mark@digitalfountain.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [FECFRAME-PROTO] Protocol Design Team Meeting, Jan 29th
Thread-Index: AchhS8s4CdduIs0/EdyecQAX8sJN9gAfn/OQ
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Mark Watson <mark@digitalfountain.com>, Greg Shepherd <gjshep@gmail.com>, fecframe-proto@ietf.org
X-OriginalArrivalTime: 28 Jan 2008 16:26:16.0099 (UTC) FILETIME=[81521F30:01C861CA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3058; t=1201537576; x=1202401576; c=relaxed/simple; s=rtpdkim2001; 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<rajiva@cisco.com > |Subject:=20RE=3A=20[FECFRAME-PROTO]=20Protocol=20Design=20 Team=20Meeting,=20Jan=2029th |Sender:=20 |To:=20=22Mark=20Watson=22=20<mark@digitalfountain.com>,=0A =20=20=20=20=20=20=20=20=22Greg=20Shepherd=22=20<gjshep@gmai l.com>,=20<fecframe-proto@ietf.org>; bh=FfvHD2HobqU3+aXj2gYxw2rfcGnJrjt0b5HHpfmMxcI=; b=kWe6SS/vkqcBg6EIOmqsu+of27gy1S9+gfV+DRPovur4Zv5kgcnCc7Jqar 5tEckZMZezQOwzW1Oeo2TD8YdfKg6qP1JW6x4/M9A/u1NKIgvRB0RhynUwVa cv4et3A7d5;
Authentication-Results: rtp-dkim-2; header.From=rajiva@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc:
X-BeenThere: fecframe-proto@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Fecframe protocol design team <fecframe-proto.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/fecframe-proto>, <mailto:fecframe-proto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/fecframe-proto>
List-Post: <mailto:fecframe-proto@ietf.org>
List-Help: <mailto:fecframe-proto-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/fecframe-proto>, <mailto:fecframe-proto-request@ietf.org?subject=subscribe>
Errors-To: fecframe-proto-bounces@ietf.org
Hi Mark, Could you please send the draft in .txt format? The .xml seems to have errors. Cheers, Rajiv > -----Original Message----- > From: Mark Watson [mailto:mark@digitalfountain.com] > Sent: Sunday, January 27, 2008 8:19 PM > To: Greg Shepherd; fecframe-proto@ietf.org > Subject: Re: [FECFRAME-PROTO] Protocol Design Team Meeting, Jan 29th > > All, > > I will be at the meeting Tuesday. I looked at the notes from the IETF > meeting and started with updates to the Framework draft. It > turned out there > were not too many: > - address the communication of FEC Configuration Information > to the sender > as well as to the receiver > - relax requirement for systematic codes (I think, actually, > it already got > relaxed, because I could not find it) > - reduce width of some of the ASCII art > > The first point is something we should discuss further on Tuesday - > particularly whether there is information which only the > sender needs which > is not presently described as part of the FEC Framework Configuration > Information. I introduced the possibility for scheme-specific > information > needed only by the sender - we should discuss whether there > is any such > information which is independent of the FEC scheme. > > Also raised at the meeting was the question of feedback > information. We > should discuss whether there is anything generic which could > usefully be > introduced into the framework for this or whether it should > just be left to > CDPs. > > A revised draft is attached - we can continue work on this at > the meeting. > > See you on Tuesday. > > ...Mark > > > > On 1/23/08 3:03 PM, "Greg Shepherd" <gjshep@gmail.com> wrote: > > > I have a conference room reserved on the cisco SJ campus, > building 16. > > I'll need to meet everyone in the lobby of building 16 when you > > arrive. Please try to arrive on or before 9am so that we may get > > things rolling right away. We'll have to move to a different room at > > noon, so we can grab lunch on the way over. The afternoon room will > > have a TelePresence conference established with Rajiv in RTP. > > > > Bldg 16 is located here: > > > > > http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=109496 039069852425144. > > > 00000112df60cca861566&ll=37.409233,-121.926204&spn=0.004994,0. > 009248&t=h&z=17& > > om=0 > > > > My cell number is: > > > > 541-915-4989 > > > > Can everyone planning on being there in person please confirm so I > > know who to expect, thanks. We also have a conference phone reserved > > in the room so anyone wishing to dial-in should contact me > in advance > > and I'll send you the dial-in details. > > > > Thank you, > > Greg > > > > _______________________________________________ > > FECFRAME-PROTO mailing list > > FECFRAME-PROTO@ietf.org > > https://www1.ietf.org/mailman/listinfo/fecframe-proto > > > > _______________________________________________ FECFRAME-PROTO mailing list FECFRAME-PROTO@ietf.org https://www1.ietf.org/mailman/listinfo/fecframe-proto
- [FECFRAME-PROTO] Protocol Design Team Meeting, Ja… Greg Shepherd
- RE: [FECFRAME-PROTO] Protocol Design Team Meeting… Ali Begen (abegen)
- Re: [FECFRAME-PROTO] Protocol Design Team Meeting… Ulas Kozat
- Re: [FECFRAME-PROTO] Protocol Design Team Meeting… Marshall Eubanks
- Re: [FECFRAME-PROTO] Protocol Design Team Meeting… Greg Shepherd
- Re: [FECFRAME-PROTO] Protocol Design Team Meeting… Mark Watson
- Re: [FECFRAME-PROTO] Protocol Design Team Meeting… Marshall Eubanks
- RE: [FECFRAME-PROTO] Protocol Design Team Meeting… Rajiv Asati (rajiva)
- Re: [FECFRAME-PROTO] Protocol Design Team Meeting… Greg Shepherd