Re: [FECFRAME-PROTO] A new informational draft on fec grouping issues

"Ali Begen (abegen)" <abegen@cisco.com> Wed, 13 February 2008 15:45 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 E7A693A6FA0; Wed, 13 Feb 2008 07:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.946
X-Spam-Level:
X-Spam-Status: No, score=-1.946 tagged_above=-999 required=5 tests=[AWL=-3.309, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_12=0.6, J_CHICKENPOX_13=0.6, J_CHICKENPOX_15=0.6, 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 P8Ty61j2Wy9F; Wed, 13 Feb 2008 07:45:06 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56C2328C86E; Wed, 13 Feb 2008 07:44:58 -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 20BEF3A6F97 for <fecframe-proto@core3.amsl.com>; Wed, 13 Feb 2008 07:44:57 -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 28Mla2gBNqp0 for <fecframe-proto@core3.amsl.com>; Wed, 13 Feb 2008 07:44:54 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 64EF928C882 for <fecframe-proto@ietf.org>; Wed, 13 Feb 2008 07:44:01 -0800 (PST)
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 13 Feb 2008 07:45:24 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m1DFjORH018825 for <fecframe-proto@ietf.org>; Wed, 13 Feb 2008 07:45:24 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m1DFjOPp003186 for <fecframe-proto@ietf.org>; Wed, 13 Feb 2008 15:45:24 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); Wed, 13 Feb 2008 07:45:24 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C86E57.723788CA"
Date: Wed, 13 Feb 2008 07:45:20 -0800
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540683D31A@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <15B86BC7352F864BB53A47B540C089B604ECA404@xmb-rtp-20b.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: Achturhr2vPK5a3xQa6iuOp60OoAJgAAX5EwAABMybAAIffIEAAEU0gA
References: <04CAD96D4C5A3D48B1919248A8FE0D540683CFC5@xmb-sjc-215.amer.cisco.com> <15B86BC7352F864BB53A47B540C089B604ECA404@xmb-rtp-20b.amer.cisco.com>
From: "Ali Begen (abegen)" <abegen@cisco.com>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>, fecframe-proto@ietf.org
X-OriginalArrivalTime: 13 Feb 2008 15:45:24.0159 (UTC) FILETIME=[7275C4F0:01C86E57]
Authentication-Results: sj-dkim-4; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 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>
Sender: fecframe-proto-bounces@ietf.org
Errors-To: fecframe-proto-bounces@ietf.org

Hi Rajiv,

Thanks for reading the draft. For other who have not started reading,
pls see the updated version (attached).

I asked someone without any FEC background to comment on the draft
(seems that we will have the same issue in MMUSIC). So, I expanded the
intro part and make clarifications about what we meant with
prioritization, additivity, etc.

Thanks again,
-acbegen

> -----Original Message-----
> From: Rajiv Asati (rajiva) 
> Sent: Wednesday, February 13, 2008 5:36 AM
> To: Ali Begen (abegen); 'fecframe-proto@ietf.org'
> Subject: RE: [FECFRAME-PROTO] A new informational draft on 
> fec grouping issues
> 
> 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