跳到主要內容

臺灣博碩士論文加值系統

(98.82.120.188) 您好!臺灣時間:2024/09/20 09:51
字體大小: 字級放大   字級縮小   預設字形  
回查詢結果 :::

詳目顯示

: 
twitterline
研究生:林傳能
研究生(外文):Chuan-Neng Lin
論文名稱:利用TrafficClass及FlowLabel提供IPv6服務品質之研究
論文名稱(外文):Study of IPv6 QoS Provision by Using Traffic Class and Flow Label
指導教授:黃文祥黃文祥引用關係梁廷宇
指導教授(外文):Wen-Shyang HwangTyng-Yeu Liang
學位類別:碩士
校院名稱:國立高雄應用科技大學
系所名稱:電機工程系碩士班
學門:工程學門
學類:電資工程學類
論文種類:學術論文
論文出版年:2006
畢業學年度:94
語文別:中文
論文頁數:62
中文關鍵詞:流量類別流量標示
外文關鍵詞:Traffic ClassFlow Label
相關次數:
  • 被引用被引用:0
  • 點閱點閱:824
  • 評分評分:
  • 下載下載:55
  • 收藏至我的研究室書目清單書目收藏:0
隨著網際網路的盛行及智慧家電與3G無線通訊時代的到來,使得IPv4位址不足的問題逐漸受到重視,根據亞太網路資訊中心發布的IPv4 Address Consumption Model可以預估在2010至2015年之間IPv4位址將會消耗殆盡,即使目前有網路位址轉換(Network Address Translation, NAT)與無等級內部路由(Classless InterDomain Routing, CIDR)等技術來暫時解決IP位址不足的情況。在1995年時Internet Engineering Task Force (IETF),制定了下世代的網際網路協定IPv6來解決IPv4位址不足的問題並且針對在IPv4的不足處進行補強與改善,特別是在服務品質(QoS)方面在IPv6表頭中加入了Traffic Class與Flow Label欄位做為QoS方面的應用。
雖然在IPv4已經有用Differentiated Service Codepoint (DSCP)欄位來做為差異性服務(DiffServ)。但在使用差異性服務來做為End-to-end QoS保證的機制下,網域中的所有路由器都必須提供差異性服務的功能,其主要原因在於差異性服務的架構是用邊緣路由器來給予封包不同的對待等級,以後再由核心路由器依據Per Hop Behaviors (PHBs)來給予不同等級的對待,因此封包有可能會經過網域中的任何一台路由器。此外,邊緣路由器若採用5-tuple(source and destination address, ports, and protocol)做為分類的依據,則往往容易造成邊緣路由器上的負擔。基於上述的考量,本文提出使用Traffic Class與Flow Label的End-to-end QoS機制來減輕邊緣路由器在分類上的負擔並且克服網域中所有路由器必須提供差異性服務能力的限制。
With the rapid growth of internet, Information Appliances (IA), and 3G wireless communications, the problem of insufficient IPv4 address was considered gradually. According to the IPv4 address consumption model which was issued by Asia-pacific Network Information Center (APNIC), the IPv4 address space will be exhausted about 2010-2015. Although Network Address Translation (NAT) and Classless Inter-Domain Routing (CIDR) can solve the situation temporarily, but the problem still is not overcome thoroughly. Therefore Internet Engineering Task Force (IETF) has promoted a next generational internet protocol IPv6 in 1995 to solve the above problem. Besides IPv6 enhances and improves the insufficient IPv4 address in QoS aspect. IPv6 especially adds Traffic Class and Flow Label fields in its packet header for QoS applications.
Although Differentiated Service Codepoint (DSCP) field in IPv4 packet header is used for DiffServ, but all routers must provide DiffServ capacity in the internet domain for End-to-end QoS provisioning. The reason is edge routers aggregate and mark packets for differentiated classes and core routers only treat packets by Per Hop Behaviors (PHBs) for differentiated services. Therefore packets may be passed by any router in internet domain. Besides edge routers should manage traffic with 5-tuple (source and destination addresses, ports, protocol) for classification, it would make edge routers in heavy load. On the basis of above consideration, this paper proposes an End-to-end QoS mechanism by using Traffic Class and Flow Label to reduce the load of classification in edge routers and overcome all routers have to provide DiffServ capacity in the internet domain.
摘 要 i
Abstract ii
致 謝 iii
目 錄 iv
圖目錄 v
第一章 前 言 1
第二章 背 景 6
2.1 Quality of Service 6
2.1.1 IntServ 6
2.1.2 DiffServ 8
2.1.3 MPLS 12
2.1.4 IntServ, DiffServ, and MPLS 14
2.2 Internet Protocol Header 15
2.3 Flow Label 18
2.3.1 Specification of IPv6 Flow Label 18
2.3.2 A Scalable Architecture for End-to-end QoS Provisioning 20
2.3.3 Hybrid Approach for IPv6 QoS 22
第三章 Proposed QoS Mechanism for IPv6 27
3.1 Bit Patterns for Flow Label 27
3.2 FLMT and FLFT 28
3.3 Scenario for QoS Mechanism 29
3.4 Features 34
第四章 實驗模擬與討論 36
4.1 模擬環境 36
4.2 模擬結果與分析 37
4.2.1 Time Sliding Window Three Color Marker (TSWTCM) 38
4.2.2 Two Rate Three Color Marker (TRTCM) 42
4.2.3 Single Rate Three Color Marker (SRTCM) 46
第五章 結論與未來工作 51
參考文獻 53
[1]http://bgp.potaroo.net/ipv4/
[2]S. Bradmer and A. Mankin, “The Recommendation for the IP Next Generation Protocol”, IETF Network Working Group RFC 1752, 1995.
[3]http://www.nri.co.jp/english/news/2005/050519.html, “NRI announces an IT development road map to FY2009”, Nomura Research Institute, Ltd. 2005.
[4]http://anf.ne.kr/~ipv6, ANF IPv6 Task Force in Korea.
[5]http://www.byrnesmedia.com/News/March2005/internetmultimedia2005.html, “Internet and Multimedia 2005 : The On-Demand Media Consumer”, 2005.
[6]S. Deering and R. Hinden, “Internet Protocol, Version 6 (IPv6) Specification”, IETF Network Group RFC 2460, 1998.
[7]K. Nichols, S. Blake, F. Baker, and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", Network Working Group RFC 2474, 1998.
[8]S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, and W. Weiss, "An Architecture for Differentiated Services", Network Working Group RFC 2475, 1988.
[9]R. Braden, L. Zhang, S. Berson, S. Herzog, and S. Jamin, "Resource ReSerVation Protocol (RSVP)", Network Working Group RFC2205, 1997.
[10]R. Braden, D. Clark, and S. Shenker, "Integrated Services in the Internet Architecture: an Overview", Network Working Group RFC 1633, 1994.
[11]K. Nichols, V. Jacobson, and L. Zhang, "A Two-bit Differentiated Services Architecture for the Internet", Network Working Group RFC 2638, 1999.
[12]Rahul Banerjee, Sumeshwar Paul Malhotra, and Mahaveer M, “A Modified Specification for use of the IPv6 Flow Label for providing An efficient Quality of Service using a hybrid approach”, IPng Working Groups Internet Draft < draft- banerjee-flowlabel-ipv6-qos-03.txt >, 2002.
[13]A. Conta and B. Carpenter, “A proposal for the IPv6 Flow Label Specification”, IPng Working Groups Internet Draft , 2001.
[14]Rahul Banerjee, N. Preethi, and M. Sethuraman, “Design and Implementation of the Quality-of-Service in IPv6 using the modified Hop-by-Hop Extension header - A Practicable Mechanism”, IPv6 Working Group Internet Draft < draft-banerjee- ipv6-quality-service-02.txt>, 2002.
[15]Spiridon Bakiras and Victor O.K. Li, “A scalable architecture for End-to-end QoS provisioning”, 2004.
[16]J. Rajahalme, A. Conta, B. Carpenter, and S. Deering, "IPv6 Flow Label Specification", Network Working Group, 2004.
[17]W. Fang, N. Seddigh, and B. Nandy, " Time Sliding Window Three Colour Marker (TSWTCM)", Network Working Group RFC 2859, 2000.
[18]J. Heinanen and R. Guerin, "A Single Rate Three Color Marker", Network Working Group RFC 2697, 1999.
[19]J. Heinanen and R. Guerin, "A Two Rate Three Color Marker", Network Working Group RFC 2698, 1998.
[20]T. Dreibholz, "An IPv4 Flowlabel Option", Network Working Group Internet-Draft , 2005.
[21]E. Rosen, A. Viswanathan, and R. Callon, “Multiprotocol Label Switching Architecture”, Network Working Group RFC 3031, 2001.
[22]E. Rosen, D. Tappan, G. Fedorkow, Y. Rekhter, D. Farinacci, T. Li, and A. Conta, “MPLS Label Stack Encoding”, Network Working Group RFC3032, 2001.
QRCODE
 
 
 
 
 
                                                                                                                                                                                                                                                                                                                                                                                                               
第一頁 上一頁 下一頁 最後一頁 top
無相關論文