![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Ohta san, ISP talking with you intend to charge whether sender, reciever or both ? I guess some ISP would not like to start multicast service, even if subscriber request it. They might sometimes say as an excuse what you heard. I think there are a lot of way to make a special charge for special service without resource reservation protocol as you think, even if you say "It is not scalable way" :) Masataka Ohta wrote: > > I've heard that ISPs, which were expecting to receive special charge > for multicast service, are now bitterly recognizing one aspect of the > relationship that, even if multicast is free, customers do not bother > to use multicast if they pay flat rate to receive any amount of unicast > traffic >
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.