| < draft-lee-alto-chinatelecom-trial-00.txt | draft-lee-alto-chinatelecom-trial-01.txt > | |||
|---|---|---|---|---|
| ALTO Kai.Lee | ALTO Kai.Lee | |||
| Internet Draft K.Zhou | Internet-Draft China Telecom | |||
| Intended status: Informational A.Wang | Intended status: Informational GuangYao.Jian | |||
| China Telecom | Expires: April 22, 2011 Xunlei network | |||
| Expires: January 2011 July 5, 2010 | October 22, 2010 | |||
| ALTO and DECADE service trial within China Telecom | ALTO and DECADE service trial within China Telecom | |||
| draft-lee-alto-chinatelecom-trial-00.txt | draft-lee-alto-chinatelecom-trial-01.txt | |||
| Status of this Memo | Status of this Memo | |||
| This Internet-Draft is submitted to IETF in full conformance with the | This Internet-Draft is submitted to IETF in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
| other groups may also distribute working documents as Internet- | other groups may also distribute working documents as Internet- | |||
| Drafts. | Drafts. | |||
| skipping to change at page 1, line 32 ¶ | skipping to change at page 1, line 32 ¶ | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
| This Internet-Draft will expire on April 19, 2010. | This Internet-Draft will expire on April 22, 2011. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2010 IETF Trust and the persons identified as the | Copyright (c) 2010 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| described in the Simplified BSD License. | described in the BSD License. | |||
| Abstract | Abstract | |||
| This document reports the experience of China Telecom in a recent | This document reports the experience of China Telecom in a recent | |||
| experiment with the ALTO service and P2P caches deployment. It is | experiment with the ALTO service and P2P caches deployment. It is | |||
| found that the deployment of the ALTO service significantly improves | found that the deployment of the ALTO service significantly improves | |||
| the capability of a Service Provider to affect the distribution of | the capability of a Service Provider to affect the distribution of | |||
| P2P traffic. It is also found that a traffic localized ALTO policy | P2P traffic. It is also found that a traffic localized ALTO policy | |||
| may decrease the download speed of a P2P user. However, the | may decrease the download speed of a P2P user. However, the | |||
| deployment of some P2P caches can compensate such influence. | deployment of some P2P caches can compensate such influence. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction ................................................. 2 | 1. Introduction ................................................. 3 | |||
| 2. High level description of the trial .......................... 3 | 2. High level description of the trial .......................... 4 | |||
| 2.1. Difference between standard ALTO protocol ............... 3 | 2.1. Difference between standard ALTO protocol ............... 4 | |||
| 2.2. Difference between Comcast's trial ...................... 4 | 2.2. Difference with Comcast's trial ......................... 5 | |||
| 3. Trial results ................................................ 5 | 3. Trial results ................................................ 6 | |||
| 3.1. ALTO server policy test ................................. 6 | 3.1. ALTO server policy test...................................7 | |||
| 3.2. P2P cache test .......................................... 7 | 3.2. P2P cache test .......................................... 8 | |||
| 4. Methods of data collection.................................... 8 | 4. Methods of data collection.................................... 9 | |||
| 5. Next steps ................................................... 9 | 5. Configurations and algorithms in trial ...................... 10 | |||
| 6. Security Considerations....................................... 9 | 5.1. Configuration of PID MAP................................ 10 | |||
| 7. IANA Considerations .......................................... 9 | 5.2. Algorithms of Xunlei using ALTO information ............ 10 | |||
| 8. References ................................................... 9 | 5.3. Configuration of cache system........................... 12 | |||
| Author's Addresses ............................................. 10 | 6. Next steps .................................................. 13 | |||
| 7. Security Considerations...................................... 14 | ||||
| 8. IANA Considerations ......................................... 14 | ||||
| 9. References .................................................. 14 | ||||
| Author's Addresses ............................................. 14 | ||||
| 1. Introduction | 1. Introduction | |||
| Although another trial on P4P, the predecessor of the ALTO, is | Although another trial on P4P, the predecessor of the ALTO, is | |||
| available by Comcast, the impact of ALTO on a large scale real | available by Comcast, the impact of ALTO on a large scale real | |||
| network has never publicly reported. Such real network should post | network has never publicly reported. Such real network should post | |||
| no limitation on either the number of contents or the number of | no limitation on either the number of contents or the number of | |||
| users. This draft reports the experience of China Telecom in a | users. This draft reports the experience of China Telecom in a | |||
| recent experiment with the deployment of the ALTO service and P2P | recent experiment with the deployment of the ALTO service and P2P | |||
| caches. | caches. | |||
| With over 60 million fixed-line broadband subscribers, China Telecom | With over 60 million fixed-line broadband subscribers, China | |||
| is the largest broadband service provider in China. It has one IP | Telecom is the largest broadband service provider in China. It has | |||
| backbone network that cover all of the 31 provinces and about 200 | one IP backbone network that cover all of the 31 provinces and | |||
| MAN networks managed by the provinces respectively. This trial was | about 200 MAN networks managed by the provinces respectively. | |||
| taken place in one province with 7 million broadband subscribers and | This trial was taken place in one province with 7 million | |||
| about 11 MAN networks. | broadband subscribers and about 11 MAN networks. | |||
| Xunlei, the cooperator of this trial, is a leading P2P service | Xunlei, the cooperator of this trial, is a leading P2P service | |||
| provider in China. Xunlei supports both file downloads and real time | provider in China. Xunlei supports both file downloads and real time | |||
| media streaming. In 2009, when was this trail occurring, it serves | media streaming. In 2009, when was this trail occurring, it serves | |||
| over 20 million users each day. | over 20 million users each day. | |||
| This trial is a joint effort of China Telecom and Xunlei. During | This trial is a joint effort of China Telecom and Xunlei. During | |||
| this trial, China Telecom provided the following devices: an alto | this trial, China Telecom provided the following devices: an alto | |||
| server for distribute ALTO information, some P2P caches to test its | server for distribute ALTO information, some P2P caches to test its | |||
| influence on traffic localization and user experience. China Telecom | influence on traffic localization and user experience. China Telecom | |||
| also monitored the traffic load within its backbone. Xunlei provided | also monitored the traffic load within its backbone. Xunlei provided | |||
| the P2P client and users. To support this trial, Xunlei modified its | the P2P client and users. To support this trial, Xunlei modified its | |||
| platform to support ALTO, and recorded operational information on | platform to support ALTO, and recorded operational information on | |||
| its platform according to the requirement of China Telecom. Note | its platform according to the requirement of China Telecom. Note | |||
| that the client of Xunlei was not changed. | that the client of Xunlei was not changed. | |||
| 2. High level description of the trial | 2. High level description of the trial | |||
| skipping to change at page 3, line 34 ¶ | skipping to change at page 4, line 24 ¶ | |||
| Note that ALTO protocol is still on progressing, in this trail, some | Note that ALTO protocol is still on progressing, in this trail, some | |||
| modifications were made to the ALTO. | modifications were made to the ALTO. | |||
| First, a notification mechanism for the ALTO server is introduced. | First, a notification mechanism for the ALTO server is introduced. | |||
| With this mechanism, the ALTO server notifies its clients the | With this mechanism, the ALTO server notifies its clients the | |||
| changes of network maps and cost maps. Thus, ALTO clients can | changes of network maps and cost maps. Thus, ALTO clients can | |||
| respond fast to the change of traffic optimizing policy. | respond fast to the change of traffic optimizing policy. | |||
| One problem that this trail met is to find the effect of ALTO&Cache | One problem that this trail met is to find the effect of ALTO&Cache | |||
| deployment. The traffic within the IP backbone is highly periodical | deployment. The traffic within the IP backbone is highly periodical | |||
| For example, the traffic on each weekend is higher than the workday of | For example, the traffic on each weekend is higher than the workday. | |||
| same week. | ||||
| As such, data should be collected in the same workday in different | As such, data should be collected in the same workday in different | |||
| week. This can facilitate the comparison of the effects on p2p | week. This can facilitate the comparison of the effects on p2p | |||
| traffic under different ALTO configuration and different policy, and | traffic under different ALTO configuration and different policy, and | |||
| to evaluate the effect of ALTO service | to evaluate the effect of ALTO service | |||
| In this trail, ALTO clients were just embedded in the trackers of | In this trail, ALTO clients were just embedded in the trackers of | |||
| Xunlei, not in the Xunlei clients. The reason for this is mainly for | Xunlei, not in the Xunlei clients. The reason for this is mainly for | |||
| deployment consideraton. There are hundreds of millions of Xunlei | deployment consideraton. There are hundreds of millions of Xunlei | |||
| clients in use, To update these clients as the ALTO client in a | clients in use, To update these clients as the ALTO client in a | |||
| skipping to change at page 5, line 13 ¶ | skipping to change at page 6, line 8 ¶ | |||
| b) To lessen the alto server load. | b) To lessen the alto server load. | |||
| c) Above 85% of Xunlei traffic flow is controlled by Xunlei | c) Above 85% of Xunlei traffic flow is controlled by Xunlei | |||
| tracker, the traffic flow from DHT mechanism is less than 15%. | tracker, the traffic flow from DHT mechanism is less than 15%. | |||
| An alto server dedicated for Xunlei tracker can control | An alto server dedicated for Xunlei tracker can control | |||
| majority of Xunlei traffic flow. | majority of Xunlei traffic flow. | |||
| 3. Trial results | 3. Trial results | |||
| This trial used all Xunlei p2p client in the province and all | This trial used all Xunlei p2p client in the province and all | |||
| contents that are requested or served by Xunlei P2P client in the | contents that are requested or served by Xunlei P2P client in the | |||
| province. The trial environment is more realistic than comcast's. A | province. The trial environment is more realistic than comcast's. A | |||
| primary objective of this trial is to measure the effects of traffic | primary objective of this trial is to measure the effects of traffic | |||
| localization and change of users download speed in comparison to | localization and change of users download speed in comparison to normal | |||
| normal p2p activity. | p2p activity. | |||
| The test process is divided into two parts: first part is just | ||||
| The test process is divided into two parts: first part is just | applied the ALTO server to measure the effects of traffic localization | |||
| applied the ALTO server to measure the effects of traffic | and change of P2P user experience. The second part is to introduce the | |||
| localization and change of P2P user experience. The second part is | P2P cache to the trial, to measure the improvement of user download | |||
| to introduce the P2P cache to the trial, to measure the improvement | speed, the bandwidth consumption and their relationship with the scale | |||
| of user download speed, the bandwidth consumption and their | of cache and. | |||
| relationship with the scale of cache and. | ||||
| Our trial starts at 2009.6.12 and ends at 2009.10.18, lasting nearly | Our trial starts at 2009.6.12 and ends at 2009.10.18, lasting nearly | |||
| four months. We do this trial by applying different ALTO policy to | four months. We do this trial by applying different ALTO policy to | |||
| Xunlei tracker. There are two kinds of ALTO policy: One is optimized | Xunlei tracker. There are two kinds of ALTO policy: One is optimized | |||
| policy and the other is normal policy. The optimized policy will try | policy and the other is normal policy. The optimized policy will try to | |||
| to localize the traffic as much as possible by utilizing the | localize the traffic as much as possible by utilizing the information | |||
| information from ALTO server. The normal policy will just use the | from ALTO server. The normal policy will just use the original Xunlei | |||
| original Xunlei peer selection and traffic control rules and no alto | peer selection and traffic control rules and no alto policy are | |||
| policy are involved. We usually change the alto policy in midnight | involved. We usually change the alto policy in midnight of a day and | |||
| of a day and send a notification to Xunlei tracker with notification | send a notification to Xunlei tracker with notification | |||
| mechanism.(http://tools.ietf.org/id/draft-sun-alto-notification- | mechanism.(http://tools.ietf.org/id/draft-sun-alto-notification-02.txt) | |||
| 02.txt) | ||||
| Before we do the trial , we collect the information about Xunlei'S | Before we do the trial , we collect the information about Xunlei'S | |||
| peer and traffic distribution | peer and traffic distribution | |||
| +------------------------------------------+--------------------+ | +------------------------------------------+--------------------+ | |||
| | No |Data Item |Description |The way of | | | No |Data Item |Description |The way of | | |||
| | | | |collection | | | | | |collection | | |||
| +----+---------- -+------------------------+--------------------+ | +----+---------- -+------------------------+--------------------+ | |||
| | 1 |Peer |24.6% is within |Random sampling by | | | 1 |Peer |24.6% is within |Random sampling by | | |||
| | |distribution|the province,75.4% |Xunlei tracker 24 | | | |distribution|the province,75.4% |Xunlei tracker 24 | | |||
| | | |is out of the |times one day | | | | |is out of the |times one day | | |||
| | | |province | | | | | |province | | | |||
| +----+------------+------------------------+--------------------+ | +----+------------+------------------------+--------------------+ | |||
| | |Traffic |76.9% is |Random selecting | | | |Traffic |76.9% is |Random selecting | | |||
| skipping to change at page 9, line 19 ¶ | skipping to change at page 10, line 16 ¶ | |||
| b) Xunlei traffic flow detected by DPI system. The DPI system | b) Xunlei traffic flow detected by DPI system. The DPI system | |||
| just monitored the uplink of the province to China telecom's | just monitored the uplink of the province to China telecom's | |||
| backbone. | backbone. | |||
| 2. Information from Xunlei | 2. Information from Xunlei | |||
| a) Inter-province/intra-province traffic flow. | a) Inter-province/intra-province traffic flow. | |||
| b) User average download speed. | b) User average download speed. | |||
| 5. Next steps | 5. Configurations and algorithms in trial | |||
| 5.1. Configuration of PID MAP | ||||
| a) PID Map: We define 11 PIDs | ||||
| PID1-PID11 represent the 11 MANs of the trial network | ||||
| PID12 represents rest of the Internet | ||||
| b) Cost Map: | ||||
| Bidirectional cost between any PIDs from PID1 to PID11 has the | ||||
| same value 1 | ||||
| Bidirectional cost between PID12 and PIDi (1<=i<=11) has the | ||||
| same value 2 | ||||
| 5.2. Algorithms of Xunlei using ALTO information | ||||
| Xunlei is a hybrid application utilizing both trackers and DHT, | ||||
| About 85% of Xunlei traffic controlled by Xunlei trackers. In this | ||||
| trail ALTO clients just include the xunlei trackers not include the | ||||
| xunlei client. Just the traffic controlled by xunlei tracker has | ||||
| been affected. | ||||
| Before the trial Xunlei tracker peer selection algorithm is: | ||||
| Xunlei Peer selection algorithm depends on two properties: ISP ID | ||||
| and UC (upload capability), the peer selection priority is : | ||||
| Same ISP ID > different ISP ID | ||||
| Higher UC > lower UC | ||||
| The peers with same ISP ID with the requesting peer have higher | ||||
| priority than those with different ISP ID. If peers have same ISP ID | ||||
| then the peers with higher UC have higher priority than those with | ||||
| lower UC. | ||||
| After applying the ALTO information into the xunlei peer selection | ||||
| algorithm. Xunlei changed his Peers select mechanism. All xunlei | ||||
| peers are organized in a tree structure which is indexed by | ||||
| CID(content ID), in the second level ALTO_ISP and normal_ISP | ||||
| represent the network of ISP with and without alto information. In | ||||
| this trial 11 MANs in trial province became 11 ALTO_ISPs.The third | ||||
| level is defined by different upload capability(UC) of peers. The | ||||
| fourth level of normal_ISP branch is the different | ||||
| provinces(PRO1,PRO2) of ISP, the fifth level of the normal_ISP is | ||||
| different city of ISP. | ||||
| +-------------------+ | ||||
| | CID | | ||||
| +-------------------+ | ||||
| / \ | ||||
| +----------+ +----------+ | ||||
| |NORMAL_ISP| | ALTO_ISP | | ||||
| +----------+ +----------+ | ||||
| / | \ / | \ | ||||
| UC_BIG UC_MID UC_SMALL UC_BIG UC_MID UC_SMALL | ||||
| / | | \ | ||||
| PRO1 PRO2 PEER1 PEER2 | ||||
| / | | ||||
| CITY1 CITY2 | ||||
| | \ | ||||
| PEER1 PEER2 | ||||
| The algorithms of cost between origination peer(peer_o) and | ||||
| destination peer(peer_d) is : | ||||
| If (peer_o and peer_d both from ALTO_ISP) | ||||
| If (peer_o and peer_d in the same ALTO_ISP) then cost = 0; | ||||
| Else cost = 100000; | ||||
| Else if (peer_o from ALTO_ISP and peer_d from normal_ISP) cost = | ||||
| 100000; | ||||
| Else if (peer_o from normal_ISP and peer_d from ALTO_ISP) cost = | ||||
| 1000; | ||||
| Else if (peer_o and peer_d both from normal_ISP){ | ||||
| If (peer_o and peer_d from different normal_ISP) cost =1000; | ||||
| Else if (peer_o and peer_d from different province) cost = 100; | ||||
| Else if (peer_o and peer_d from different city) cost = 10; | ||||
| Else cost =0; | ||||
| } | ||||
| The peer select mechanism is lower cost peers will have higher | ||||
| priority | ||||
| The updated peer selection mechanism is not the best mechanism. For | ||||
| example a peer in MAN2 is supposed to be better choice than the | ||||
| peers which not located in china telecom's network when a peer in | ||||
| MAN1 send a content request to tracker. But this mechanism will | ||||
| select the peer out of china telecom's network first then select the | ||||
| peer in the MAN2. Before we defined the network map with 12 PIDs. We | ||||
| first defined a network map with just 2 PIDs. PID1 represent the | ||||
| trial province and PID2 represent the other network to test the | ||||
| backbone traffic saving effect of ALTO service. The test result show | ||||
| that the network map with 12PIDs has almost same backbone traffic | ||||
| saving effect compared to the network map with 2 PIDs. So in the | ||||
| trial we deployed this mechanism. | ||||
| The other change is the number of returned peers from xunlei | ||||
| tracker . If a listing request is from the trial province, the | ||||
| maximum # of returned peers from xunlei tracker is set to 120, not | ||||
| the normal case of 500. | ||||
| 5.3. Configuration of cache system | ||||
| Before we deploy the cache system we have made some statistics about | ||||
| relationship of content popularity and network traffic caused by | ||||
| content with different popularity in trial province. | ||||
| +-----------+---------+----------+-------------+ | ||||
| |content | total |total | proportion | | ||||
| | popularity| size(GB)|traffic | of total | | ||||
| | | |(Gbps) |traffic(%) | | ||||
| +-----------+---------+----------+-------------+ | ||||
| | top 10 | 18.9 | 1.34 | 9.3 | | ||||
| | top 20 | 29.3 | 1.68 | 11.7 | | ||||
| | top 50 | 51.8 | 2.28 | 15.9 | | ||||
| | top 100 | 93.6 | 2.89 | 20.1 | | ||||
| | top 500 | 418.7 | 4.74 | 33 | | ||||
| | top 1000 | 812.4 | 5.88 | 40.9 | | ||||
| | top 2000 | 1518.6 | 7.16 | 49.8 | | ||||
| | top 5000 | 3551 | 8.89 | 61.9 | | ||||
| +-----------+---------+----------+-------------+ | ||||
| Our cache system has limited storage and access bandwidth so we need | ||||
| to know which content is most "valuable" to be cached. According the | ||||
| statistics from xunlei if a downloading task is fed over 100 peers , | ||||
| this task always can get the maximum download speed(this speed | ||||
| depends on the peer's access network, in the trial the average | ||||
| access speed of user is about 2Mbps). The top 2000 | ||||
| popular content almost all have over 100 seeds in trial province. | ||||
| That means the top 2000 popular contents don't need be cached. Our | ||||
| cache policy is just cache the content which's popularity rank | ||||
| behind 2000. | ||||
| 6. Next steps | ||||
| The alto mechanism is very effective to optimize the traffic flow. | The alto mechanism is very effective to optimize the traffic flow. | |||
| But when the traffic is localized, the user average download speed | But when the traffic is localized, the user average download speed | |||
| is slowed down simultaneously. If alto can cooperate with DECADE | is slowed down simultaneously. If alto can cooperate with p2p cache | |||
| or other service performance enhancement mechanism, it will be more | or other service performance enhancement mechanism, it will be more | |||
| practical. | practical. | |||
| The ALTO service's effect depends on the SP such as Xunlei,pando how | ||||
| to use it. The mechanism such as peer selection mechanism and | ||||
| content cache mechanism need to be studied. | ||||
| 6. Security Considerations | 7. Security Considerations | |||
| High-level security considerations can be found in the [draft-ietf- | High-level security considerations can be found in the [draft-ietf- | |||
| alto-problem-statement]. | alto-problem-statement]. | |||
| 7. IANA Considerations | 8. IANA Considerations | |||
| This document requests the registration of a new media type: | This document requests the registration of a new media type: | |||
| "application/alto" | "application/alto" | |||
| 8. References | 9. References | |||
| [RFC 5693] | [RFC 5693] | |||
| Seedorf, J. and E. Burger, "Application-Layer Traffic | Seedorf, J. and E. Burger, "Application-Layer Traffic | |||
| Optimization (ALTO) Problem Statement", RFC 5693, | Optimization (ALTO) Problem Statement", RFC 5693, | |||
| October 2009. | October 2009. | |||
| [I-D.ietf-alto-reqs] | [I-D.ietf-alto-reqs] | |||
| Kiesel, S., Popkin, L., Previdi, S., Woundy, R., and Y. | Kiesel, S., Popkin, L., Previdi, S., Woundy, R., and Y. | |||
| Yang, "Application-Layer Traffic Optimization (ALTO) | Yang, "Application-Layer Traffic Optimization (ALTO) | |||
| Requirements", draft-ietf-alto-reqs-01 (work in | Requirements", draft-ietf-alto-reqs-01 (work in | |||
| progress),July 2009. | progress),July 2009. | |||
| [I-D.penno-alto-protocol] | [I-D.penno-alto-protocol] | |||
| Penno, R. and Y. Yang, "ALTO Protocol", | Penno, R. and Y. Yang, "ALTO Protocol", | |||
| draft-ietf-alto-protocol-01 (work in progress), | draft-ietf-alto-protocol-01 (work in progress), | |||
| July 2009. | July 2009. | |||
| [I-D.song-decade-survey] | ||||
| R. Alimi and Z. Lu, "A Survey of In-network Storage Systems" | ||||
| draft-song-decade-survey-02(work in progress), | ||||
| December , 2009 | ||||
| Author's Addresses | Author's Addresses | |||
| Kai Lee | Kai Lee | |||
| China Telecom Beijing Research Institute | China Telecom Beijing Research Institute | |||
| Room 708 No.118, Xizhimenneidajie, xicheng District | Email: leekai@ctbri.com.cn | |||
| Beijing 100035 | ||||
| China | ||||
| Email: leekai@ctbri.com.cn | ||||
| Aijun Wang | ||||
| China Telecom Beijing Research Institute | ||||
| Room 708 No.118, Xizhimenneidajie, xicheng District | ||||
| Beijing 100035 | ||||
| China | ||||
| Email: wangaj@ctbri.com.cn | ||||
| Kaiyu Zhou | GuangYao Jian | |||
| China Telecom Beijing Research Institute | Xunlei Network | |||
| Room 708 No.118, Xizhimenneidajie, xicheng District | Email: jianguangyao@xunlei.com | |||
| Beijing 100035 | ||||
| China | ||||
| Email: zhouky@ctbri.com.cn | ||||
| End of changes. 23 change blocks. | ||||
| 81 lines changed or deleted | 224 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||