[magma] Fw: New Version Notification for draft-dizhou-pim-umf-problem-statement-00

zhoudi <zhoudi@h3c.com> Thu, 19 August 2010 07:01 UTC

Return-Path: <zhoudi@h3c.com>
X-Original-To: magma@core3.amsl.com
Delivered-To: magma@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05C073A68DD; Thu, 19 Aug 2010 00:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.884
X-Spam-Level:
X-Spam-Status: No, score=0.884 tagged_above=-999 required=5 tests=[AWL=1.379, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 86OIhYEEkDDs; Thu, 19 Aug 2010 00:01:47 -0700 (PDT)
Received: from huawei-3com.com (unknown [60.191.123.50]) by core3.amsl.com (Postfix) with ESMTP id 361DC3A67E5; Thu, 19 Aug 2010 00:01:40 -0700 (PDT)
Received: from huawei-3com.com (localhost [127.0.0.1]) by h3cml01-in.huawei-3com.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0L7E00ERW0GHBJ@h3cml01-in.huawei-3com.com>; Thu, 19 Aug 2010 14:53:05 +0800 (CST)
Received: from H3CHUB01-EX.srv.huawei-3com.com ([10.63.16.181]) by h3cml01-in.huawei-3com.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPS id <0L7E007C80GHID@h3cml01-in.huawei-3com.com>; Thu, 19 Aug 2010 14:53:05 +0800 (CST)
Received: from h3cedge01-ex.h3c.com (172.25.12.73) by H3CHUB01-EX.srv.huawei-3com.com (10.63.16.181) with Microsoft SMTP Server (TLS) id 14.0.689.0; Thu, 19 Aug 2010 14:53:04 +0800
Received: from h3cimss01-ss (172.25.12.100) by h3cedge01-ex.h3c.com (172.25.12.73) with Microsoft SMTP Server id 14.0.689.0; Thu, 19 Aug 2010 15:15:31 +0800
Received: from unknown (HELO z00782a) ([10.55.72.60]) by smtp2.h3c.com with ESMTP; Thu, 19 Aug 2010 14:52:58 +0800
Date: Thu, 19 Aug 2010 14:52:44 +0800
From: zhoudi <zhoudi@h3c.com>
To: Indranil Bhattacharya <myselfindranil@gmail.com>, Greg Shepherd <gjshep@gmail.com>, pim@ietf.org, mboned@ietf.org, multimob@ietf.org, magma@ietf.org
Message-id: <009201cb3f6b$206dd2f0$240a0164@h3c.huawei3com.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
X-TM-IMSS-Message-ID: <1b39a62a00150849@h3c.com>
X-Mailman-Approved-At: Thu, 19 Aug 2010 03:53:24 -0700
Cc: young@h3c.com, Hui Deng <denghui@chinamobile.com>
Subject: [magma] Fw: New Version Notification for draft-dizhou-pim-umf-problem-statement-00
X-BeenThere: magma@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast and Anycast Group Membership <magma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/magma>
List-Post: <mailto:magma@ietf.org>
List-Help: <mailto:magma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Aug 2010 07:01:48 -0000

Hi,
     According to your advice, I newly submitted the problem-statement for the problem of 
Unnecessary Multicast Flooding between sources and PIM FHRs.
http://datatracker.ietf.org/doc/draft-dizhou-pim-umf-problem-statement/
     Welcome to  comment on the problem and  bring forward solutions.

     Thanks and Regards.
     ZhouDi    


Subject: New Version Notification for draft-dizhou-pim-umf-problem-statement-00


> 
> A new version of I-D, draft-dizhou-pim-umf-problem-statement-00.txt has been successfully submitted by Di Zhou and posted to the IETF repository.
> 
> Filename: draft-dizhou-pim-umf-problem-statement
> Revision: 00
> Title: Unnecessary Multicast Flooding Problem Statement
> Creation_date: 2010-08-17
> WG ID: Independent Submission
> Number_of_pages: 15
> 
> Abstract:
> This document describes the unnecessary multicast stream flooding
> problem in the link layer switches between multicast source and PIM
> First Hop Router (FHR).  The IGMP-Snooping Switch will forward
> multicast streams to router ports, and the PIM FHR must receive all
> multicast streams even if there is no request from receiver.  This
> often leads to waste of switchs' cache and link bandwidth when the
> multicast streams are not actually required.  This document details
> the problem and defines design goals for a generic mechanism to
> restrain the unnecessary multicast stream flooding.
>                                                                                  
> 
> 
> The IETF Secretariat.
> 
> 
>