Re: [multrans] How does the receiver initially acquire the <Source, Group> address pair?
Tom Taylor <tom111.taylor@bell.net> Tue, 03 May 2011 15:02 UTC
Return-Path: <tom111.taylor@bell.net>
X-Original-To: multrans@ietfa.amsl.com
Delivered-To: multrans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id 8F36FE0837 for <multrans@ietfa.amsl.com>;
Tue, 3 May 2011 08:02:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.774
X-Spam-Level:
X-Spam-Status: No, score=-100.774 tagged_above=-999 required=5 tests=[AWL=1.022,
BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U--MJoeXVTxy for
<multrans@ietfa.amsl.com>; Tue, 3 May 2011 08:02:26 -0700 (PDT)
Received: from blu0-omc4-s2.blu0.hotmail.com (blu0-omc4-s2.blu0.hotmail.com
[65.55.111.141]) by ietfa.amsl.com (Postfix) with ESMTP id E7FF0E0830 for
<multrans@ietf.org>; Tue, 3 May 2011 08:02:25 -0700 (PDT)
Received: from BLU0-SMTP31 ([65.55.111.135]) by blu0-omc4-s2.blu0.hotmail.com
with Microsoft SMTPSVC(6.0.3790.4675); Tue, 3 May 2011 08:02:20 -0700
X-Originating-IP: [64.231.151.226]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP319EEE5E21FBEB757CB417D89E0@phx.gbl>
Received: from [192.168.2.17] ([64.231.151.226]) by BLU0-SMTP31.phx.gbl over
TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);
Tue, 3 May 2011 08:02:20 -0700
Date: Tue, 3 May 2011 11:02:22 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB;
rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
References: <C9E4B05B.DA5C%yiu_lee@cable.comcast.com>
In-Reply-To: <C9E4B05B.DA5C%yiu_lee@cable.comcast.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 May 2011 15:02:20.0569 (UTC)
FILETIME=[19E57890:01CC09A3]
Cc: "multrans@ietf.org" <multrans@ietf.org>
Subject: Re: [multrans] How does the receiver initially acquire the <Source,
Group> address pair?
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, 03 May 2011 15:02:26 -0000
Thanks a lot. This makes sense, and maybe it takes address acquisition off the table as an issue, except to note that translation is needed if the versions of the source and receiver are different. I distinguish that offline translation step from any further translation needed for the control signalling when the network version doesn't match the receiver version. On 02/05/2011 7:10 PM, Lee, Yiu wrote: > In our case, the mapping is regional base and static. It is provisioned > out-of-band to the receivers. > > On 5/2/11 2:36 PM, "Tom Taylor"<tom111.taylor@bell.net> wrote: > >> I am thinking of the IPTV case. >> >> I need help in understanding how receiver address acquisition works in >> the absence of v4/v6 transition issues. I assume the receiver gets the >> address pair from some sort of signalling exchange with a network node >> (please verify), but would this node be located in the core network >> serving the receiver or hang off the backbone network beyond that (which >> is where I assume the sources lie)? >> >> Of course, in some cases the addresses could be configured by management >> action. >> >> Tom Taylor >> _______________________________________________ >> multrans mailing list >> multrans@ietf.org >> https://www.ietf.org/mailman/listinfo/multrans > > >