Re: [FECFRAME-PROTO] A new informational draft on fec grouping issues
"Rajiv Asati (rajiva)" <rajiva@cisco.com> Wed, 13 February 2008 13:35 UTC
Return-Path: <fecframe-proto-bounces@ietf.org>
X-Original-To: ietfarch-fecframe-proto-archive@core3.amsl.com
Delivered-To: ietfarch-fecframe-proto-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B1E828C7AC; Wed, 13 Feb 2008 05:35:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.616
X-Spam-Level:
X-Spam-Status: No, score=-2.616 tagged_above=-999 required=5 tests=[AWL=-2.179, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.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 SBm8ECwri6Kw; Wed, 13 Feb 2008 05:35:37 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D87A728C7A7; Wed, 13 Feb 2008 05:35:37 -0800 (PST)
X-Original-To: fecframe-proto@core3.amsl.com
Delivered-To: fecframe-proto@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78D5928C7B9 for <fecframe-proto@core3.amsl.com>; Wed, 13 Feb 2008 05:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 wReUMfZTevTz for <fecframe-proto@core3.amsl.com>; Wed, 13 Feb 2008 05:35:35 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 6711F28C7AC for <fecframe-proto@ietf.org>; Wed, 13 Feb 2008 05:35:35 -0800 (PST)
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 13 Feb 2008 08:36:56 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m1DDauAQ010631 for <fecframe-proto@ietf.org>; Wed, 13 Feb 2008 08:36:56 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m1DDaiQb005659 for <fecframe-proto@ietf.org>; Wed, 13 Feb 2008 13:36:56 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 13 Feb 2008 08:36:51 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 13 Feb 2008 08:36:10 -0500
Message-ID: <15B86BC7352F864BB53A47B540C089B604ECA404@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540683CFC5@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [FECFRAME-PROTO] A new informational draft on fec grouping issues
Thread-Index: Achturhr2vPK5a3xQa6iuOp60OoAJgAAX5EwAABMybAAIffIEA==
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "Ali Begen (abegen)" <abegen@cisco.com>, fecframe-proto@ietf.org
X-OriginalArrivalTime: 13 Feb 2008 13:36:51.0707 (UTC) FILETIME=[7D7AFCB0:01C86E45]
Authentication-Results: rtp-dkim-2; header.From=rajiva@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
Subject: Re: [FECFRAME-PROTO] A new informational draft on fec grouping issues
X-BeenThere: fecframe-proto@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Fecframe protocol design team <fecframe-proto.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/fecframe-proto>, <mailto:fecframe-proto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/fecframe-proto>
List-Post: <mailto:fecframe-proto@ietf.org>
List-Help: <mailto:fecframe-proto-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/fecframe-proto>, <mailto:fecframe-proto-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: fecframe-proto-bounces@ietf.org
Errors-To: fecframe-proto-bounces@ietf.org
Hi Ali, That's fine. I just got to see the draft. Looks fine to me. Cheers, Rajiv > -----Original Message----- > From: Ali Begen (abegen) > Sent: Tuesday, February 12, 2008 4:28 PM > To: Rajiv Asati (rajiva); 'fecframe-proto@ietf.org' > Subject: RE: [FECFRAME-PROTO] A new informational draft on > fec grouping issues > > This is just for describing the problem and showing some > alternative solutions. It does not have to become anything. > That's why, it is intended to be informational. > > If MMUSIC agrees to adopt one of the solutions described here > or comes up with a new one, then of course we should work on > that draft together, which should be in the cateogry of > "proposed standard." > > However, note that MMUSIC WG should approve what needs to be > done here. And, that's why we need to tell them about our problems. > > -acbegen > > > -----Original Message----- > > From: Rajiv Asati (rajiva) > > Sent: Tuesday, February 12, 2008 1:17 PM > > To: Ali Begen (abegen); fecframe-proto@ietf.org > > Subject: RE: [FECFRAME-PROTO] A new informational draft on > > fec grouping issues > > > > Hi Ali, > > > > We (the protocol team) should all collaborate to jointly > > author the new draft, if/when it needs to be produced. > > > > Also, why should it be the informational draft? > > > > Cheers, > > Rajiv > > > > > -----Original Message----- > > > From: fecframe-proto-bounces@ietf.org > > > [mailto:fecframe-proto-bounces@ietf.org] On Behalf Of Ali Begen > > > (abegen) > > > Sent: Tuesday, February 12, 2008 4:04 PM > > > To: fecframe-proto@ietf.org > > > Subject: [FECFRAME-PROTO] A new informational draft on > fec grouping > > > issues > > > > > > Hi everyone, > > > > > > So far, we could not ignite a discussion in the MMUSIC WG > regarding > > > the FEC grouping issues. So, it was suggested that I > would write an > > > informational draft, describe the problems and propose some > > > alternative solutions. So, that is what I did. > > > > > > I am attaching the draft for your review. Note that this > has to be > > > submitted by Monday. So any comments within this week > > (before Friday) > > > would be appreciated. It is important that we convey our issues > > > appropriately. So, please take a few minutes to review the > > document. > > > It is very short, and should not take much time. > > > > > > Thanks, > > > -acbegen > > > > > > _______________________________________________ FECFRAME-PROTO mailing list FECFRAME-PROTO@ietf.org http://www.ietf.org/mailman/listinfo/fecframe-proto
- [FECFRAME-PROTO] A new informational draft on fec… Ali Begen (abegen)
- Re: [FECFRAME-PROTO] A new informational draft on… Rajiv Asati (rajiva)
- Re: [FECFRAME-PROTO] A new informational draft on… Ali Begen (abegen)
- Re: [FECFRAME-PROTO] A new informational draft on… Rajiv Asati (rajiva)
- Re: [FECFRAME-PROTO] A new informational draft on… Ali Begen (abegen)
- Re: [FECFRAME-PROTO] A new informational draft on… Rajiv Asati (rajiva)
- Re: [FECFRAME-PROTO] A new informational draft on… Mark Watson
- Re: [FECFRAME-PROTO] A new informational draft on… Ali Begen (abegen)
- Re: [FECFRAME-PROTO] A new informational draft on… Mark Watson
- Re: [FECFRAME-PROTO] A new informational draft on… Rajiv Asati (rajiva)
- Re: [FECFRAME-PROTO] A new informational draft on… Rajiv Asati (rajiva)