Re: [MBONED] draft-zhou-mboned-multrans-path-optimization

"Lee, Yiu" <Yiu_Lee@Cable.Comcast.com> Fri, 23 March 2012 02:42 UTC

Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5474321E8051 for <mboned@ietfa.amsl.com>; Thu, 22 Mar 2012 19:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.191
X-Spam-Level:
X-Spam-Status: No, score=-101.191 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGvb59PTFUoz for <mboned@ietfa.amsl.com>; Thu, 22 Mar 2012 19:42:32 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id C8C9C21E804A for <mboned@ietf.org>; Thu, 22 Mar 2012 19:42:32 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP id C7WM3M1.10584199; Thu, 22 Mar 2012 20:30:28 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%17]) with mapi id 14.01.0355.002; Thu, 22 Mar 2012 22:42:27 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>, Stig Venaas <stig@venaas.com>
Thread-Topic: [MBONED] draft-zhou-mboned-multrans-path-optimization
Thread-Index: AQHNCJ6VUXcFpF5c4keKvP0Eg0a/ng==
Date: Fri, 23 Mar 2012 02:42:26 +0000
Message-ID: <CB915AE8.1E5F6%yiu_lee@cable.comcast.com>
In-Reply-To: <A6A061BEE5DDC94A9692D9D81AF776DF1BDBE219@szxeml527-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.14.0.111121
x-originating-ip: [24.40.55.70]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3415300945_1079568"
MIME-Version: 1.0
Cc: "mboned@ietf.org" <mboned@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [MBONED] draft-zhou-mboned-multrans-path-optimization
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 02:42:33 -0000

You can't do that right? If I have a v4 receiver connected to the v6-only
network, the v4 receiver has to receive stream from the S4 source. Or you
suggest the access network will statefully convert the v6 group address to
v4 group address?
 

On 3/22/12 10:31 PM, "Zhouqian (Cathy)" <cathy.zhou@huawei.com> wrote:

>Hi Yiu,
>This solution is not only for transition, it also covers the pure v6 case.
>About the content stream, there will be only one stream received by MTR
>because MTR makes comparison.
>If the path metric of v4 source> path metric of v6 source, the MTR will
>choose the path of v6 source. Otherwise, it will choose v4 source.
>If the v4 metric=v6 metric, it will choose one of them.
>
>Best Regards,
>Cathy ZHOU
>
>
>-----Original Message-----
>From: Lee, Yiu [mailto:Yiu_Lee@Cable.Comcast.com]
>Sent: Friday, March 23, 2012 10:07 AM
>To: Zhouqian (Cathy); Stig Venaas
>Cc: mboned@ietf.org; Ronald Bonica
>Subject: Re: [MBONED] draft-zhou-mboned-multrans-path-optimization
>
>Hi Cathy,
>
>I am a little confused. Since MTR is for transitioning, why will it
>connect to the S6 in the first place? Besides, say you have two types of
>receivers (v4 and v6) connected to the v6-only network. At any given time,
>there are v4 and v6 receivers watching TV. In this setup, you will have to
>stream the content twice anyway because the group address will be
>different for native-v6 (v6 source) and v4-embedded v6 (v4 source). Did I
>get this wrong?
>
>Thanks,
>Yiu
>
>
>On 3/22/12 9:50 PM, "Zhouqian (Cathy)" <cathy.zhou@huawei.com> wrote:
>
>>There are two cases in Figure 1. One is v6 network connecting to both v4
>>and v6 sources via MTR, which is in higher priority and is the main case
>>of this document.