P2PRGInternet Research Task Force (IRTF) S. KameiInternet-DraftRequest for Comments: 6875 NTT CommunicationsIntended status:Category: Informational T. MomoseExpires: April 18, 2013ISSN: 2070-1721 Cisco Systems T. Inoue T. Nishitani NTT CommunicationsOctober 15, 2012 ALTO-LikeFebruary 2013 The P2P Network Experiment Council's Activities and Experiments with Application-Layer Traffic Optimization (ALTO) inP2P Network Experiment Council draft-kamei-p2p-experiments-japan-09Japan Abstract This documentintroducesdescribes experimentstothat clarify howALTO-likean approach similar to Application-Layer Traffic Optimization (ALTO) was effectiveto reducein reducing networktraffic madetraffic. These experiments were performed in Japan byathe P2P Network Experiment Council inJapanan attempt to harmonizeP2Ppeer-to-peer (P2P) technology withthenetwork infrastructure.AndBased on what was learned from these experiments, thisalsodocument provides some suggestions that might be useful for the ALTO architecturelearned through our experiments. Especially, experimentand especially forapplication independent ALTO-likeapplication-independent ALTO- like server operation. Status ofthisThis Memo ThisInternet-Draftdocument issubmitted in full conformance withnot an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Research Task Force (IRTF). The IRTF publishes theprovisionsresults ofBCP 78Internet-related research andBCP 79. Internet-Drafts are working documentsdevelopment activities. These results might not be suitable for deployment. This RFC represents the individual opinion(s) of one or more members of the Peer-to-Peer Research Group of the InternetEngineeringResearch Task Force(IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid(IRTF). Documents approved for publication by the IRSG are not amaximumcandidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status ofsix monthsthis document, any errata, and how to provide feedback on it may beupdated, replaced, or obsoleted by other documentsobtained atany time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on April 18, 2013.http://www.rfc-editor.org/info/rfc6875. Copyright Notice Copyright (c)20122013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Background in Japan . . . . . . . . . . . . . . . . . . . . .34 2.1. P2PtrafficTraffic . . . . . . . . . . . . . . . . . . . . . . .34 2.2. Impact onnetwork infrastructureNetwork Infrastructure . . . . . . . . . . . . . 4 2.3.The objectOverview of the P2P Network Experiment Council . . . . . ..5 3.The objectObjectives of the P2P Network Experiment Council . . . . . . .. . 56 4.The detailsDetails of theexperimentsExperiment . . . . . . . . . . . . . . . . . . 7 4.1. Dummy Node . . . . . . . . . . . . . . . . . . . . . . . . 7 5. HintServer ('08)Servers . . . . . . . . . . . . . . . . . . . . . . . .8. 9 6. High-Level Trial Results . . . . . . . . . . . . . . . . . . . 13 6.1. Peer Selection with P2P . . . . . . . . . . . . . . . . . 13 6.2. Peer Selection with the Hint Server . . . . . . . . . . . 13 7. Considerations . . . . . . . . . . . . . . . . . . . . . . . . 14 7.1. NextstepsSteps . . . . . . . . . . . . . . . . . . . . . . . . 14 7.2. Feedback to the ALTO WG . . . . . . . . . . . . . . . . .. .15 7.2.1. HierarchicalarchitectureArchitecture for ALTOserversServers . . . . . . 15 7.2.2. MeasurementmechanismMechanism . . . . . . . . . . . . . . . . 15 8. Security Considerations . . . . . . . . . . . . . . . . . . . 16 9.IANA Considerations .Acknowledgments . . . . . . . . . . . . . . . . . . . .16 10. Acknowledgments. . . 16 10. Informative References . . . . . . . . . . . . . . . . . . . . 1611. Informative References . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 171. Introduction An overlay network, which is used by P2P and other applications, offers the advantage of allowing flexibleprovisionprovisioning of services while hiding thelower layerlower-layer network. Thedownsidedisadvantage is that inefficientroutes are often taken inrouting without considering thelower IP network, therebylower-layer network may cause increasing the network load. Several proposals have been made to build an overlay network that takes into accountofthe information about thelower layer network.lower-layer network [1][2][2]. Since the management of the Internet is highly distributed, it is difficult to implement suchproposalsproposals, and thus to optimize anetworknetwork, without the cooperation of network providers. Recently, the controversy between the overlay network and the network providers about network resource wastefulness has been rekindled. Under these circumstances, some researchers have studiedoverlayoverlay- network control technology that takes into accountofthe network topology information obtained from network providers. Oneof the activities concerningresearch effort regarding this issuehas been madewere experiments planned and performed by the P2P Network Experiment Council in Japan.We planned some experiments in the council.This document reports on these experiments and the issuesaddressed andthey addressed. These experimentsbeing made by the council. This experiment madewere performed from 2007 to 2008, because P2P traffichad reduced due to rivision ofdecreased after Japanese copyright lawin Japan. Andwas revised. While more recently, the dominant trafficis HTTP based flash streamingin Japan,U.S,the United States, andso on. However, P2Pelsewhere has been HTTP-based flash streaming, a large amount of trafficremainsinlargeAsia (outside Japan) is still P2P traffic, likePPStreaming, in Asia (except Japan)[3],P2P streaming [3], and P2P technology is veryuserfuluseful in such arealtimereal-time streaming area. Our experience in this experiment might be useful for ALTO architecture, especially forapplication independentapplication-independent andmultimulti- application ALTO-like server operations. We suggest that a generic measurement mechanism is important because each application has differentmechanism andmechanism, which makes itisdifficult to comparethetheir effectiveness. This document is a product of the P2PRG.Research Group (RG). The views in this document were considered controversial by the P2PRGRG, but the RG reached a consensus that the document should still be published. 2. Background in Japan 2.1. P2PtrafficTraffic As of 2008, theworldworld's most popular P2Pfile sharingfile-sharing application,Bittorrent, isn'tBitTorrent, was not widely deployed in Japan. Instead, otherJapan specific filefile- sharing P2P applications specific to Japan, such as Winny[4],[4] and Share [5],and so on,stilloccupyaccount for 40% of the Internet traffic inJapanJapan, even though many those P2P users were arrested for sharing illegal files with these P2Papps.applications. Each P2Pfile sharingfile-sharing application has a unique protocol and noneof themhave a large marketshareshare, therefore making it hard toeffectively control.control them effectively. 2.2. Impact onnetwork infrastructureNetwork Infrastructure Oneof theadvantage of using P2P technology for content delivery is that peers exchange content directly among themselves without server bottleneck. This reduces the load on servers. Also, P2P applications can reduce upstream traffic from an origin content server. Thisreducereduces server cost dramatically. It is also known that server cost could be reduced with P2P technology. However, the story is quite different for network providers. From the viewpoint of network providers, the traffic that content servers generate has shifted to the edge network and the amount of traffic has not necessarily been reducedwithby using P2P technology for reducing server cost. Another problem for network providers is thatanextremely inefficient routing may be selectedhas been raised. It isbecause overlay network systems are configured without any regard to the structure of thelower layerlower-layer network or network geometry. In some cases, the total amount of traffic on the Internet used to be limited by the capacity of servers. For those cases, P2P technology can improve the scalability ofservers , howeverservers; however, it may exhaust network resources. Moreover, using P2P applications remarkably increases the volume of traffic peruser remarkably.user. Faced with an increase in the load on network infrastructure, network providers are compelled to take actions to overcome the sudden increase in facilities'cost.costs. Representative actions include placing content ininternet exchangesInternet Exchanges (IXs) or data centers, introducing bandwidth control, and raisingtheaccess fees [6].However, currentAs mentioned above, the dominant trafficis HTTP based flash streamingcurrently in Japan,U.S,the US, andso on.elsewhere, is HTTP-based flash streaming. However,P2Pa large amount of trafficremainsinlargeAsia (outside Japan) is P2P traffic, likePPStreaming, in Asia (except Japan)[3],P2P Streaming [3], and P2P technology is veryuserfuluseful in sucha realtime streaming area.real-time streaming. The increase in traffic arising from such a shift may be a great threat to the network. 2.3.The objectOverview of the P2P Network Experiment Council In order to reduce Internet traffic and encourage legitimate use of P2P technologies, in 2006 the Japanese governmentled to establishestablished a new council called the P2P Network ExperimentCouncilCouncil, in conjunction with commercial P2P application vendors andISPs in 2006. Then theISPs. The councilhad started to developdeveloped regulations that includeseveralguidelines suchlike anas giving advance notice torestrict bandwidth toheavytraffic users.users before restricting their bandwidth. In accordance with the regulations, some ISPs introduced solutions that reduce traffic caused by P2Pfile sharingfile-sharing applications.Besides this activity,In addition, thecouncil alsocouncil, along with ISPs, carriers, contents providers, and P2P system vendors, looked for new ways to control traffic by commercial P2Papplications with ISPs, carriers, contents providers and P2P system vendors.applications. In this work, the councilhadperformed experiments that introduced an ALTO-like system and observed how the traffic was reducedby redirectingwhen it was redirected to proper peers on the real Internet in Japan. In our experiment, the council deployed hint servers, which are described insection 4.Section 5. Hint servershaverun a protocolofferingthat offers networkdistancedistances to peers,which isand these distances are disclosed to P2P application vendors. Using hintserver,servers, P2P application vendors can introduce ALTO concepts easilytointo their P2P distribution systems. Because the protocolprovided ofused by hintserversservers, as defined by the council, is independentonof specific P2P application vendors likeBittorrent, the council defines theBitTorrent. The protocolto be able to use any P2P application vendors. Itneeds to gather network information from ISPsto offerso it can provide network distance topeers, howeverpeers. However, many ISPs disliketo disclosedisclosing such information to others. Therefore, hint servers are designed to offer little information aboutISPs'an ISP's network architecture to P2P application vendors. To monitor the traffic of peers, the council also deployed a dummy node, whichareis described insection 3.1. ThisSection 4.1. The remainder of this memodescribes theprovides an overview of the experiments. 3.The objectObjectives of the P2P Network Experiment Council The Japanese Ministry of Internal Affairs andCommunications Japan,Communications, which has jurisdiction over information and communication systems in Japan, held meetings of an advisory panel on network neutralityfromin 2006toand 2007 in order to study issues related tonext generationnext-generation networks, such as how to ensure fairness in the use of networks and how to define fairness in the cost burden. The panel took an interest in P2P technology as a solution to the impending traffic saturation in the backbone network resulting from the rapid expansion of broadband access in Japan, and it formed a "Working Group on the P2P Network", which carried out an intensive study of P2P networks. TheWorking Groupworking group reported that itiswould be necessary to undertake the following four activities, which are intended to encourage the government to adopt relevant policies [7]: o Formulate guidelines on P2P file-delivery applications to beself-imposedself- imposed by theindustry on P2P file delivery applications,industry. o Promote feasibility tests of P2Pnetworks,networks. o Study the current state of traffic control and promote the sharing ofinformation,information. o Hold working group meetingsonabout traffic control. The first two proposals led to the establishment of the P2P Network ExperimentCouncilCouncil, supported by the Japanese Ministry of Internal Affairs and CommunicationsJapan [8].[8] [9]. The Council, with membership from P2P delivery providers, content holders, and network providers, began a variety of delivery experiments, which were expected to strengthen cooperative control between different layers. In contrast toP4P,P4P (Proactive Network Provider Participation for P2P), which takes a relatively top-down approach of adopting an architecture based on a proposal from a university, the Council is characterized by its bottom-up approach. The aim of establishing the Councilhas beenwas described asfollows.follows (translated from [10]). The rapid growth of broadband access enables content deliverysystemsystems to deliver high-quality and high-volume videos securely and efficiently. Although P2P technology is an effective technology for this requirement, it still has some issues to be coped with. Therefore, the "P2P Network Experiment Council" was established with the support of the Japanese Ministry of Internal Affairs andCommunicationsCommunications, with its secretariat set up within the Foundation for MultiMedia Communications(FMMC)(FMMC), in order to formulate guidelines for providers and conduct feasibility tests so that users can receive video delivery services safely. The activities of the P2P Network Experiment Council can be classified into two categories. The first isactivities to formulateformulating guidelines forthe promotion ofpromoting the commercial use of P2P technology. These guidelines will enable users to use P2P technologysafely,safely and will give providersto haveclear rules they must observe. Theothersecond is feasibilityteststesting of P2P technology.The next sectionSection 4 describesmainlyexperiments conductedfromin 2007toand 2008. 4.The detailsDetails of theexperimentsExperiment Thecouncil has alreadyCouncil investigated data offered by the members of the Council and learned that the server cost could be reducedwithby using P2P technology forcontents delivering by investigating data offered by the members of the council.content delivery. For example, the databrought byfrom the vendorsshows as follows: 90% of trafficshowed the following: Traffic was reduced by 90% withUG LiveUGLive byUtagoe Inc [9].Utagoe, Inc. [11]. Thecostscost of delivering to tens ofthousandthousands of subscribers was reducedto 1/5by 80% with BBbroadcast with TV Bank Corp.[10][12] On the other hand, these reduced server costs mayaffecthave affected the network load. One of the goals of our experiments was to visualize theimpactsimpact and propose an architecture to reduce network load caused by these new technologies. In order to visualize the reduction of network cost, wehad to modelizemodeled P2P applications and a multi-ISP environment.It willThis model was also needed for visualizing the effectiveness of the ALTO-like approach. 4.1. Dummy Node As mentionedbefore,above, while the effect ofdeliveryusing P2P technologyon reducingto reduce the traffic and the load on servers is wellknown,known; however, traffic behavior in the inter-ISP area is not known. In Japan,there isthe ISPs and IXes cooperated to create a backbone traffic reportcooperated with ISPs and IXes [11].[13]. However,this measurement requires to capturethe measurements gathered for that report required capturing packets onsubscribers linesubscribers' lines in order toknowdetermine the enduser's activity.users' activities. It is not realistic to measure the behavior of P2P applications at user terminals connected to the Internet because that would require a large-scale arrangement for measurement, such as usingDeep Packet Inspectiondeep packet inspection (DPI) on aggregated lines. To solve these problems, we put several nodes called 'dummy nodes' in the ISP's networks. The dummy nodes emulate an end user's PCandrunning P2Papplications are running on the nodes.applications. Every P2P node provided by participating vendors in the experiment was configured so it always contacted the hint server. By introducing dummynodes,nodes and measuring the traffic on them, wecanwere able to observe and evaluate how much the P2P applicationshaveaffectednetworks by measuringthetraffic on dummy nodes.networks. Since this method can't measure every subscriber's traffic, the accuracywould beis less than other methods.But this makeHowever, using dummy nodes makes it possible to adapt to situations in which many different P2P applications coexist on a network. Wecan say this isdecided that using dummy nodes was suitable for these experiments. A dummy nodeconsistsconsisted of an Intel PCserver, Linux(CentOS), VMWareserver running Linux (CentOS), VMWare, and Windows XPworkson VMWare. With this configuration, all packets can be captured without anyimpacts toimpact on the behavior of the network,nodes and application behaviors. And it enablenodes, or applications. Also, this configuration enabled us to use different P2P applications forwindowsWindows and evaluate them generally. To see behaviors of the node, incoming and outgoing packets are captured on Linux because everypackets arepacket is transmitted through it.InTo see flow information in these experiments, we capturedsource/destination address,the source and destination addresses, port number, amount oftraffictraffic, andstart/end time to see flow information.start and end times. We placed 60Dummydummy nodesare puton access networksthat are closest subscriberof 40 different ISPs. They were placed as close as possible to the subscriber indifferent 40 ISP networks.each network. +----------------------+ |+--------------------+| ||+------------------+|| ||| P2P Application ||| |||WindowsXPWindows XP ||| ||| +--+ ||| ||+--------|N |------+|| || VMware |e | || |+---------|t |-------+| | Linux |IF| capture| +----------| |--------+ +--+Dummy nodesFigure11: Dummy node 5. HintServer ('08) InServers Since fiber to the home (FTTH) has rapidly spread all over Japan,bottleneckbottlenecks in IP networks have been shifting from access networks to backbone networks andequipments,equipment, such as bandwidth between ISPs and capacity inIXs, since FTTH has rapidly spread all over Japan.IXs. Under these circumstances, the Council proposedaless restrictive and more flexible cooperation between ISPs than existent P4P experiments[12].[14]. The proposed method consists of the following elements: (1) P2P clients, (2) P2P control servers, and (3) a hintserver:server (specifically, a peer selection hintserver. (1)server). P2P clients and(2)control servers are existingsystemssystems, but whether(2) exists depends on each application. (3)the P2P control servers exist is application dependent. The hint server is a server that provides a hintas to thefor peer selectionof a peer,and plays a role equivalent to that of the ALTOServer.server. Note that this proposal was based on results of experiments using dummy nodes. The results showed that it was possible to reduce unnecessary traffic that flows across the boundaries of geographical districts or ISPsthroughby providing information about the physical network to P2P applications. When a peer joins the network, it registers its location information (IP address) and supplementary information (line speed, etc.)with&# 12288;thewith the hint server. The hint servercalculatecalculates the network distance between peers (P2Pclient)clients) based on network topology information obtained from the ISP and generates a priority table for peer selection. The hint server returns the table to the peer. If all informationcan be made publicly,is public, the above procedure can producea result which is close to overall optimization.results that are nearly optimal. However, some information held by ISPscanis oftenbeconfidential.Besides,Also, in some cases, the volume of calculation required to process all information can be excessive. To avoid these problems,itthe plan isplannedto conduct experiments with a limited set of functions, analyzeexperimentsthe results, and gradually expand the scope of optimization. A control mechanism that makes use of all possible information is difficult not only technically but alsodifficulties to achievebecause it requires coordination among providers. Inconsiderationlight of these difficulties, the council has been limiting the implementation and experiments to thefollowing scope since 2006.technical scope. Figure 2 shows an outline of the hint server. +---------+ GetLocation +-------------GeoIP DB Server---------+ | | +-----------+ | +----------+ +-----------+ | | |--|IP Address |-->| | GeoIP DB ||Quagga etc|BGP daemon | | | | +-----------+ | +----------+ +-----------+ | | | | +-------------+ +----------------+ | | | +-----------+ | | District | | Routing | | | |--|AS Code: |---| |informationInformation ||information(DGP)||Information(BGP)| | | | |Regional | | | | | | | |P2P Peers| |Information| | | Range of | |AS Code(origin) | | | or | +-----------+ | | IPaddressAddresses| | | | || Contro|Control | | +-------------+ +----------------+ | | Server | +-------------------------------------+ | | | ^ | | PeerSelection v | | | +-----------+ +--------------------------------------+ | |--|IP Address |-->| +--Priority Node Selection System--+ | | | | List | | | | | | | +-----------+ | | Peercandidate rankingCandidate Ranking | | | | +-----------+ | | | | | |--| Ranking |-->| +----------------------------------+ | | | +-----------+ +--------------------------------------+ +---------+Peer selection hint serverFigure22: Hint server for peer selection The network information used by the hint server is not information solicited from individual ISPs but is theASAutonomous System (AS) number and district information, which are more or lessalready public.public already. Routing tables are not generated. Instead, peers within the same ISP or the same district are selected with higher priority in order to confine traffic to within the same ISP or the same district. When the hint server receives an IP address, it returns its attribute information, in order to confine the traffic toachievewithin theabove.nearer ISP or district. A peer can selecta peeranother based on the returned information. This operation is called GetLocation. However, in preparation for the time when it becomes necessary to hide topology information, an interface is provided through which a priority order is returned in response to an input of a list of candidate peers. This operation is called PeerSelection. Although the target node is selected based on the criterion that it is within the same ISP or the same district, this type of selection is not very effective if the number of participating peers is small. Table 1 showsratiothe percentage of peers within the same AS or the same prefecture calculated from the distribution ofASsASes and prefectures in the IP address space from one-day data on a Winny network.+--------------------+--------++--------------------+------------+ | Conditions |ratioPercentage |+--------------------+--------++--------------------+------------+ | AS matches | 6.70% | | Prefecture matches | 12.76% | | Both match | 2.09% | | Neither match | 78.45% |+--------------------+--------++--------------------+------------+ Table 1: AS and prefecture distributionsSince,Because, in addition to the above, thepresence/absencepresence or absence of content affects theresult, the control of selecting aresults, controlling peer selection within the same district may be inadequate. Therefore, it is necessary to introduce the weight of a continuous quantity that reflects the physical distance or the AS path length as an indicator of the proximity of the areas involved. In consideration ofthe above,this, the following two measures are usedfor the evaluation ofto evaluate the proximitybetweenof peers in a hint server. o AS path length (distance between ISPs) AS path length is calculated from BGP full routes. Since a full routing table retrieved at an ISP can show only a best path, it may not get an accurate length if the AS hop count of both ISPs is too large. To avoid this, we usemultipleBGP information received from different ISPs and combine them. Based on this concept, we used BGP routinginformation'sinformation offered by three ISPs operated by big telecommunication couriers and made a topology tree.Then it enablesThen, we were able to calculate the shortest path betweengiventwo given ASes. o Geographical distance Distances between peers are measured using the physical distanceof prefectural capitals that target peers belong to. The distancebetweenprefecturalthe capitalsis usedof the prefectures tocalculate physical distance.which the peers belong. Distances between prefectural capitals are sorted into ascending order, and then into bands, with weights 1 to 15 assigned to them so thatthere are a more or less equaleach band contains roughly the same number of "capitalpairs" in each band.pairs". If either oftheir locationthe peer's locations is indefinite, the distance is equal to15 and,15; if they are in the same prefecture, the distance is equal to 0. Evaluation of distances between peers showed that the distribution of distances was almost uniform when distances between peers are normalized. This result suggests that using normalized distances expands the area where the control by aHint Serverhint server is effective. The geographical distance isonlyused only when the AS path length issame.the same between some candidates. An example of the request and the response follows. o Request POST /PeerSelection HTTP/1.1 Host: ServerName User-Agent: ClientName Content-Type: text/plain; charset=utf-8 v=Version number [application=Application identifier] ip=IP address of physical interface port=Port number of physical interface [nat={no|upnp|unknown}] [nat_ip=Global IP address using UPnP] [nat_port= Global port number using UPnP][trans_id=transcation[trans_id=transaction ID] [pt=Flag of port type] [ub=upload bandwidth] [db=download bandwidth] o Response HTTP/1.1 200 OK Date: Timestamp Content-Type: text/plain; charset=utf-8 Cache-control: max-age=max age Connection: close v=Version number ttl=ttl server=hint server name ... trans_id=transaction ID pt=Flag of port type client_ip=Peer IP address observed from server client_port=Peer port number observed from server numpeers=number ofrespond peerresponding peers n=[src address] dst address / cost / option 6. High-Level Trial Results 6.1. Peer Selection with P2P Table 2 shows the result of the analysis of communication in a node of an ISPinstalledin Tokyo, as an example of measurement results. In these twoexperimentsexperiments, weevaluateevaluated different P2Papplications, in 1stapplications. In the first experiment, the P2P topologyiswas generated by a treealgorithm, andalgorithm; in2ndthe second experiment, itiswas generated by a mesh algorithm. Bothof them resultresulted in similar performance. +-----------------------------------------+------------+------------+ | Conditions | Experiment | Experiment | | | 1 | 2 | +-----------------------------------------+------------+------------+ |*PeersPeers selected within the same ISP | 22% | 29% | |*Peers| | | | Peers selected within the same district | 19% | 23% | |district| | | |*PeersPeers selected within the same district | 5% | 7% | |districtand the same ISP | | | +-----------------------------------------+------------+------------+ Table 2: Percentage of communication within the same ISPThe tableTable 2 shows that the probability of communication with peers in the same ISP is proportional to thenumber ofpopulation size and the share of the ISP in each district. The data show that peers were selected at random. Note that the vendor of a P2P application used in these experimentsexplaineddemonstrated that the mechanismof selectionfor selecting a peer using network information can be implemented. However, peer selection is normally based on past information because users often cannot actually perceive the effect of using network information. 6.2. Peer Selection with the Hint Server The main objective of these experiments was to verify theoperationsoperation of the hint server and P2P applications. The distances between a dummy node and a peer were obtained from data on the dummy nodes. An examination of the distances between a dummy node and a peer revealed that the mean value of distance after the hint server was introduced was reduced by 10% and that the 95th percentile was reduced by 5%. The results show that introducing a hint server can reduce the network loadsbythat result from P2P applications. 7. Considerations We clarifiedfollowings throughoutthe following during our experiments. 1. Dispersed dummy nodes canfigure outdetermine the behavior of peers and traffic between inter-ISPnetworks, which peers are selected bynetworks and can determine the peer that eachpeer. Therefore itpeer selects. Therefore, this result provesthatthe importance ofpeer selectionthe peer-selection control mechanism that is proposedinby ALTO. 2. Using ourpeer selectionpeer-selection control mechanism, called hintserver, could achieveservers, can result in significant differences.Our hint serverHint servers can lead each peer to selectnearera closer peer. 3. Theresult of10% reduction of network cost is notsatisfying effectsatisfactory for ISPs, but the controllabilityforof P2Papplicationisapplications is the most important point. WhentheyISPs apply this mechanismforto their realISP network,networks, they will set a very large cost for the most expensive network link. In the experimentalresult of peer selectionresults for peer-selection control,itthe selection is smaller in intra-ISP traffic than in other experiments[13][15]. We thinkthat itthis is because there aresmallerfewer peers in each area of traffic control. When there are many peers in one ISP, it is easy to select peers in the same ISP. However, when there aresmallfewer peers in one ISP, it is difficult to select peers in the same ISP. Inthe situation ofour experiments,there are many ISPsmost of the ISPs had many peersbelonging, andin their networks, i.e., thereare relatively smallerwere a small number of ISPs that had few peersexistinsame ISP.their networks. Moreover, we didn't force P2P vendors to limit their implementationpolicy, thereforepolicy; therefore, wecan observeobserved differences in how eachimplementations weighimplementation weighs the information from the hint servers.Especially,Specifically, in P2P applications when a treeoverlaytopologyP2P applications, suchis used, the hint-server mechanism is veryeffective,effective; on the other hand,inwhen a meshoverlay system,topology is used, it less effective. 7.1. Nextsteps RecentSteps In recent research, we've changedtheto an ALTO-based communication protocoltoon hint serversto ALTO basedbecauseitthe requirements of ALTO are documented in RFC 6708 [16] and the ALTO protocol isnearly standardized.a work in progress [17]. In our implementation,PIDsprotocol identifiers (PIDs) and thevalue ofcost value are mapped to ISPsubnets,subnets and to ISPdistancedistance, respectively. We also implement services for compatibility required by ALTO such asService Capability andMapServices. But theServices and Endpoint Cost Service. The Endpoint Cost Service (defined in [17]) is mainly used because of backward compatibilityofwith our experiments. We are alsostudystudying a hierarchical structure of hintserver structure,servers, in order to controlintraffic at a coarseinter-ISPslevel (in inter-ISP areas) andin detail intra-ISP.at a finer level (in intra-ISP areas). It is also effective for limiting thearea ofareas where informationdisclose.is disclosed. 7.2. Feedback to the ALTO WG This section describes what the authors learnedwithfrom these experimentswouldthat might be usefulforto the ALTO WG. 7.2.1. HierarchicalarchitectureArchitecture for ALTOserversServers In our experiments, we present the possibility of traffic control amongmulti-ISPsmultiple ISPs andmulti-P2Pmultiple P2P applications using an ALTO mechanism.On the other hand, weWe found several problemsin ISP operationswhen ISPs try toadaptadopt the mechanism. One is the granularity of network information fromcouncilCouncil members. Among inter-ISParea,areas, it is relatively easy totreathandle information for publicpurposepurposes by using BGP fullroute.routes. On the other hand, among the intra-ISParea,areas, it may be difficult to disclose the private information of each ISP.[14] proposeKiesel [18] proposes somemodificationmodifications for the ALTO protocol in order to hide ISP information. We propose hierarchical structures. From the viewpoint of cooperation between ISPs, fine-grained information is not necessarilyrequired and moreoverrequired. Moreover, it is difficult to exchange the fine-grained information between ISPs. Considering this situation,the authors usewe used only coarse-grained information to control backbone traffic inthis experiments, thoughthese experiments; however, in the future, there may be a demandoffor controlling traffic within an ISP using fine-grainedinformation may arise in future. Therefore it led us that introducinginformation. Therefore, we decided to introduce hierarchicalstructurestructures into ALTOis necessaryin order to cope with both situations. Actually,to adaptadopting a hierarchical control mechanismwhich includethat includes the following two steps will be useful. oIn the first step,First, use coarse-grained information about whole the networkis usedto select ISPs. oNext,Second, use fine-grained information within the ISPis usedto select a peer. 7.2.2. MeasurementmechanismMechanisms Inthethese experiments, there were two difficulties asfollows:follows. o Evaluating the effect of introducing a hint server wasdifficult, sincedifficult because the P2P applications had their own measurement mechanisms. o How to treat the priorityordersorder of peers suggested by a hint server could not be predetermined for P2P applications. From these experiences, the authors consider that clarifying the requirements about measurement mechanisms for P2P applicationsareis necessaryalsoin ALTO. 8. Security Considerations This document does not propose any kind of protocol,practicepractice, or standard. 9.IANA Considerations No need to describe any request regarding number assignment. 10.AcknowledgmentsThanksThe P2P Network Experiment Council was established thanks to strong support byMIC (Ministrythe Japanese Ministry of Internal Affairs andCommunications of Japanese government), the council was established.Communications. These experiments were performedunderwith cooperation among the P2P Network Experiment Councilmembers, andmembers. DREAMBOATco.,ltd., BitmediaCo., Ltd., Bitmedia, Inc., Utagoe, Inc.,Utagoe. Inc.and Toyama IX have especially supported the analyses of the experiments. The authors appreciate Tohru Asami, HiroshiEsakiEsaki, and TatsuyaYamshitaYamashita for their constructive comments.And theThe authors would also like to thank Martin Stiemerling, StefanoPrevidiPrevidi, and VijayK.GurbaniK. Gurbani forthetheir comments on this document.11.10. Informative References [1]R.Kawahara, E.K.Lua, M.Uchida, S.Kamei, H.Yoshino,Kawahara, R., Lua, E., Uchida, M., Kamei, S., and H. Yoshino, "On the Quality of Triangle Inequality Violation Aware Routing Overlay Architecture", INFOCOM2009:2009, pages 2761-2765. [2]Z.Li,Li, Z. and P. Mohapatra, "QRON: QoS-aware routing in overlay networks", IEEEJOURNAL ON SELECTED AREAS IN COMMUNICATIONS, VOL.Journal on Selected Areas in Communications, Vol. 22,NO.No. 1,JANUARYJanuary 2004. [3]Sandvine Corp,Sandvine, Inc., "Global Internet Phenomena Report:1H2H 2012", September 2012, <http://www.sandvine.com/news/global_broadband_trends.asp>. [4]"Winny on Wikipedia", <http://en.wikipedia.org/wiki/Winny>.Wikipedia, "Winny", July 2012, <http://en.wikipedia.org/w/ index.php?title=Winny&oldid=500744660>. [5] Wikipedia, "Shareon Wikipedia", <http://en.wikipedia.org/wiki/Share_(P2P)>.(P2P)", January 2013, <http://en.wikipedia.org/w/index.php?title=Share_(P2P)& oldid=532999898>. [6] Taniwaki, Y., "Broadband Competition Policy in Japan", March 2008,<http://www.smartireland.jp/en/forum/may-2009/>.<http://unpan1.un.org/intradoc/groups/public/ documents/apcity/unpan040329.pdf>. [7] Ministry of Internal Affairs and Communications, "Disclosure of the Report`Working'Working Group on P2PNetworks'", http://www.soumu.go.jp/menu_news/s-news/2007/070629_11.html, 2007Networks'" (inJapanese).Japanese), 2007, <http://www.soumu.go.jp/menu_news/s-news/2007/070629_11.html>. [8] The Foundation for MultiMedia Communications, "The P2P Network ExperimentCouncil", http://www.fmmc.or.jp/P2P/about.htm, 2007Council" (inJapanese).Japanese), 2007, <http://www.fmmc.or.jp/P2P/about.htm>. [9]Utagoe Inc., "UGLive technology introduction", http://www.utagoe.com/en/technology/grid/live/index.html, March, 2011.Ministry of Internal Affairs and Communications, "P2P Network Experiment Council Symposium to Be Held", February 2008, <http://www.soumu.go.jp/main_sosiki/joho_tsusin/eng/Releases/ Telecommunications/news080201_1.html>. [10]TVBank,The Foundation for MultiMedia Communications, "The Aim of P2P Network Experiment Council" (in Japanese), 2007, <http://www.fmmc.or.jp/p2p_web/aim.html>. [11] Shudo, K., "A Review of ALM Software in Practical Use", IRTF SAMRG (Scalable Adaptive Multicast Research Group) meeting, Proceedings of IETF 76, November 2009, <http://www.ietf.org/proceedings/76/slides/SAMRG-6.pdf>. [12] TV Bank Corp., "Live Deliveryusing `BB Broadcast'AchievingUsing 'BB Broadcast' Achieved a 96% Saving inTraffic!", http:.wwww.tv-bank.com/jp/20081031.html, 2008Traffic!" (inJapanese). [11]Japanese), October 2008, <http://www.tv-bank.com/jp/20081031.html>. [13] Cho, K., Fukuda, K., Esaki, H., and A. Kato, "The Impact and Implications of the Growth in Residential User-to-User Traffic",SIGCOMM2006, pp207-218, Pisa, Italy,SIGCOMM '06, pages 207-218, September 2006.[12] Open P4P, "P4P Field Tests: Yale-Pando-Verizon", http://www.openp4p.net/front/, 2009. [13] "RFC5632: Comcast's[14] Xie, H., Yang, R., Krishnamurthy, A., Liu, Y., and A. Silberscatz, "P4P: Provider Portal for Applications", SIGCOMM '08, pages 351-362, 2008, <http://www.cs.yale.edu/homes/yry/ projects/p4p/p4p-sigcomm08.pdf>. [15] Griffiths, C., Livingood, J., Popkin, L., Woundy, R., and Y. Yang, "Comcast's ISP Experiences in a Proactive Network Provider Participation for P2P (P4P) Technical Trial", RFC 5632, September 2009.[14][16] Kiesel, S., Previdi, S., Stiemerling, M., Woundy, R., and Y. Yang, "Application-Layer Traffic Optimization (ALTO) Requirements", RFC 6708, September 2012. [17] Alimi, R., Ed., Penno, R., Ed., and Y. Yang, Ed., "ALTOH12,draft-kiesel-alto-h12-02 (workProtocol", Work inprogress)",Progress, September 2012. [18] Kiesel, S. and M. Stiemerling, "ALTO H12", Work in Progress, March 2010. Authors' Addresses Satoshi Kamei NTT Communications Corporation Granpark Tower17F,16F, 3-4-1 Shibaura Minato-ku, Tokyo 108-8118JPJapan Phone: +81-50-3812-4697Email:EMail: skame@nttv6.jp Tsuyoshi Momose Cisco Systems G.K. 9-7-1 Akasaka Minato-ku, Tokyo 107-6227JPJapan Phone: +81-3-6738-5154Email:EMail: tmomose@cisco.com Takeshi Inoue NTT Communications3-4-1, Shibaura Minato-ku, Tokyo 108-8118 JPCorporation Kuredo Hakushima Building 3F, 14-15 Higashihakushimacho Chuo-ku, Hiroshima-City, Hiroshima 730-0004 Japan Phone:+81-3-6733-7177 Email:+81-82-563-5030 EMail: inoue@jp.ntt.net Tomohiro Nishitani NTT Communications Corporation 1-1-6, Uchisaiwaicho Chiyodaku, Tokyo 100-8019JPJapan Phone: +81-50-3812-4742Email:EMail: tomohiro.nishitani@ntt.com