IETF Logo Mail Archive

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

"Ali Begen (abegen)" <abegen@cisco.com> Tue, 12 February 2008 21:02 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 8B4D328C5C8; Tue, 12 Feb 2008 13:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.105
X-Spam-Level:
X-Spam-Status: No, score=-3.105 tagged_above=-999 required=5 tests=[AWL=-2.668, 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 KMvZQcfVwlsM; Tue, 12 Feb 2008 13:02:33 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB07C28C4E9; Tue, 12 Feb 2008 13:02:32 -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 6D30628C524 for <fecframe-proto@core3.amsl.com>; Tue, 12 Feb 2008 13:02:32 -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 BZRR9JtL5cHU for <fecframe-proto@core3.amsl.com>; Tue, 12 Feb 2008 13:02:30 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 11BD728C4BC for <fecframe-proto@ietf.org>; Tue, 12 Feb 2008 13:02:30 -0800 (PST)
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 12 Feb 2008 13:03:54 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m1CL3smv023682 for <fecframe-proto@ietf.org>; Tue, 12 Feb 2008 13:03:54 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1CL3nJe014492 for <fecframe-proto@ietf.org>; Tue, 12 Feb 2008 21:03:54 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Feb 2008 13:03:49 -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_01C86DBA.C3BAF19F"
Date: Tue, 12 Feb 2008 13:03:46 -0800
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540683CF88@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: A new informational draft on fec grouping issues
thread-index: Achturhr2vPK5a3xQa6iuOp60OoAJg==
From: "Ali Begen (abegen)" <abegen@cisco.com>
To: fecframe-proto@ietf.org
X-OriginalArrivalTime: 12 Feb 2008 21:03:49.0914 (UTC) FILETIME=[C3F6DFA0:01C86DBA]
Authentication-Results: sj-dkim-1; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Subject: [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 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

v2.23.0 | Report a Bug | By Email