Re: [MBONED] [multrans] New Version Notification for draft-tsou-multrans-addr-acquisition-00.txt for the 2nd item "Multicast Source Discovery" of the interim meeting

[Tom Taylor <[e-mail]>]

I'm happy to drop the second paragraph. It was there because I was 
trying to guess at your intentions for the scope.

On 27/12/2011 3:45 PM, Ronald Bonica wrote:
> Hi Tom,
>
> Response inline.....
>
>> [PTT] As I see it, the wording you are looking for is this:
>>
>> "To request a program instance that has been selected by the user, the
>> receiver must signal the corresponding multicast group address and,
>> depending on the deployment, unicast source address. In the IPTV case,
>> it acquires these addresses from an electronic program guide supplied
>> by
>> the provider. During the transition from IPv4 to IPv6, it may happen
>> that the IP version supported by the source network differs from that
>> supported by the receiver. As a result, if the receiver and/or the
>> electronic program guide is unchanged, the receiver will be unable to
>> find addresses it recognizes and can use for signalling in the
>> electornic program guide.
>
> Yes, this is a good approximation.
>
>>
>> "In cases other than IPTV, the receiver may receive the addresses it
>> needs for signalling in a SAP (Session Announcement Protocol, RFCxxxx)
>> announcement or directly through session-level signalling. For purposes
>> of the analysis in this document the SAP announcement is the equivalent
>> of the electronic program guide, since both are essentially a matter of
>> acquisition of static data prior to the actual usage of that data. The
>> strategy for dealing with the transition issues presented by
>> session-level signalling may differ because of the latter's more
>> dynamic
>> nature."
>>>
>
> I'm not sure what this paragraph adds.
>
>
>                                Ron
>
>