Re: [multrans] Comments on draft-jaclee-behave-v4v6-mcast-ps-01
彭军 Lightning Peng <Lightning-Peng@huawei.com> Tue, 12 April 2011 07:42 UTC
Return-Path: <Lightning-Peng@huawei.com>
X-Original-To: multrans@ietfc.amsl.com
Delivered-To: multrans@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 788A1E077B for <multrans@ietfc.amsl.com>; Tue, 12 Apr 2011 00:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.995
X-Spam-Level:
X-Spam-Status: No, score=-0.995 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zg1WLCem5upr for <multrans@ietfc.amsl.com>; Tue, 12 Apr 2011 00:42:51 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by ietfc.amsl.com (Postfix) with ESMTP id 5142DE06D7 for <multrans@ietf.org>; Tue, 12 Apr 2011 00:42:51 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LJJ005AM41106@szxga04-in.huawei.com> for multrans@ietf.org; Tue, 12 Apr 2011 15:41:25 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LJJ00603410NC@szxga04-in.huawei.com> for multrans@ietf.org; Tue, 12 Apr 2011 15:41:25 +0800 (CST)
Received: from p65294x ([10.70.39.142]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LJJ0024140VDZ@szxml04-in.huawei.com> for multrans@ietf.org; Tue, 12 Apr 2011 15:41:24 +0800 (CST)
Date: Tue, 12 Apr 2011 15:41:19 +0800
From: 彭军 Lightning Peng <Lightning-Peng@huawei.com>
In-reply-to: <01ef01cbf4d5$06aa0c10$13fe2430$@com>
To: tom111.taylor@bell.net
Message-id: <000c01cbf8e5$036ee6b0$0a4cb410$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="gb2312"
Content-language: en-us
Content-transfer-encoding: 7bit
Thread-index: Acv0xuCoN1TPnVNIT0qUjvRQZEJ7kAADiFTgAQNeYaA=
References: <01ef01cbf4d5$06aa0c10$13fe2430$@com>
Cc: multrans@ietf.org
Subject: Re: [multrans] Comments on draft-jaclee-behave-v4v6-mcast-ps-01
X-BeenThere: multrans@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discuss the work of IPv4-IPv6 multicast." <multrans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multrans>, <mailto:multrans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multrans>
List-Post: <mailto:multrans@ietf.org>
List-Help: <mailto:multrans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multrans>, <mailto:multrans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Apr 2011 07:42:52 -0000
The use cases in 3.4. Mono-Stack Multicast Delivery Infrastructure just involve Translation Cases and Traversal Cases, but I think another case in draft-tsou-v6ops-multicast-transition-v6only-01 should be included. In order to have good performance of 4.1 Fast Zapping, either Translation function or Traversal function is avoided in draft-tsou-v6ops-multicast-transition-v6only-01. Best Regards! Lightning Peng Phone: +86 755 28978851 Mobile: +86 15989362410 -----Original Message----- From: Tom Taylor [mailto:tom111.taylor@bell.net] Sent: Wednesday, April 06, 2011 6:55 PM To: Lee, Yiu Cc: christian.jacquenet@orange-ftgroup.com; BOUCADAIR Mohamed OLNC/NAD/TIP; Jacni Qin; Tina TSOU Subject: Re: Comments on draft-jaclee-behave-v4v6-mcast-ps-01 I'll mention that I have many purely editorial comments at the micro level (e.g., better ways to say some things in English, spelling out of acronyms and abbreviations on first use). Christian, you can advise me on the form in which you want to see this: as an XML file, by marked-up text, or whatever. My primary concern is that the current organization lacks focus because it considers the delivery infrastructures without separating the concerns posed by source and group address acquisition, interworking and forwarding of control messages, and distribution of content. In addition, requirements seem to be scattered through the document rather than grouped in one place. Just looking at the table of contents, I have these proposals: a) Instead of 2. Discussion, you should have 2. Service Requirements. This is the part the operator owns. b) 4.1 Fast Zapping, 4.5 SLA Considerations, 4.6 Load Balancing, and 4.7 Bandwidth Consumption should all be moved into the Service Requirements section. If there is material there that belongs in later sections it can be extracted and moved. c) Section 4 should be organized into three subsections: -- Group and Source Discovery Considerations -- Control Signalling and Multicast Tree Computation -- Content Distribution The benefit of doing this is that features common to the various use cases may emerge where they do not at present because grouping everything together makes every case seem to be unique. d) Within these subsections, the implications of the different use cases should be explored. That probably means grabbing some of the content from Section 3. Tom
- [multrans] Comments on draft-jaclee-behave-v4v6-m… Tom Taylor
- Re: [multrans] Comments on draft-jaclee-behave-v4… 彭军 Lightning Peng
- Re: [multrans] Comments on draft-jaclee-behave-v4… Jacni Qin
- [multrans] FW: Comments on draft-jaclee-behave-v4… Lightning Peng(Jun)
- Re: [multrans] Proposed organization of requireme… christian.jacquenet
- Re: [multrans] Proposed organization of requireme… Jacni Qin
- Re: [multrans] Proposed organization of requireme… Tina Tsou
- Re: [multrans] Proposed organization of requireme… Tina Tsou
- Re: [multrans] Proposed organization of requireme… Jacni Qin
- Re: [multrans] Proposed organization of requireme… Tina Tsou