Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Introduction to IPv6
Similar a Introduction to IPv6 (20)
Más de SenthilKumar Selvaraj
Más de SenthilKumar Selvaraj (12)
Introduction to IPv6
- 1. A senthilkumars @huawei.com A journey of 1000 miles starts with a single step!! Introduction To IPng
- 2. Let us know about Huawei
- 8. R&D Based on a Shared Platform Constructing a “speed, quality and cost” advantage, through modular structure, standardization and sharing technology (CBB methodology). Uniform operation and maintenance platform IP+Optical platform Common software and hardware platform Fixed access platform Wireless access platform Service control platform Intelligent network platform Terminal service platform Uniform engineering and material development platform
- 12. VISION To enrich life through communication MISSION To focus on our customers’ challenges and needs by providing excellent communications network solutions and services in order to consistently create maximum value for customers. Vision and Mission www.huawei.com
- 15. Enriching Life Through Communication Huawei Technologies Co., Ltd. Add: Huawei Base, Bantian, Longgang District, Shenzhen Tel: +86-755-28780808 Zip Code: 518129 http://www.huawei.com
- 20. Background
- 27. Return to an End-to-End Architecture New Technologies/Applications for Home Users ‘ Always-on’—Cable, DSL, Ethernet@home, Wireless,… Global Addressing Realm Always-on Devices Need an Address When You Call Them
- 37. A new Header
- 38. The IPv6 Header 40 Octets, 8 fields 0 31 Version Class Flow Label Payload Length Next Header Hop Limit 128 bit Source Address 128 bit Destination Address 4 12 24 16
- 39. The IPv4 Header 20 octets + options : 13 fields, including 3 flag bits 0 31 Ver IHL Total Length Identifier Flags Fragment Offset 32 bit Source Address 32 bit Destination Address 4 8 24 16 Service Type Options and Padding Time to Live Header Checksum Protocol shaded fields are absent from IPv6 header
- 41. Extension Headers next header = TCP TCP header + data IPv6 header next header = Routing TCP header + data Routing header next header = TCP IPv6 header next header = Routing fragment of TCP header + data Routing header next header = Fragment Fragment header next header = TCP IPv6 header
- 44. Routing Header
- 46. Routing Header
- 47. Example of Using the Routing Header S A B D
- 48. Addressing
- 64. Security
- 67. Encapsulating Security Payload (ESP) Payload Next Header Security Parameters Index (SPI) Sequence Number Authentication Data Padding Length Padding
- 73. Mobility
- 75. Mobile IP (v4 version) home agent home location of mobile host foreign agent mobile host correspondent host
- 76. Mobile IP (v4 version) home agent home location of mobile host foreign agent mobile host correspondent host
- 77. Mobile IP (v4 version) home agent home location of mobile host foreign agent mobile host correspondent host
- 78. Mobile IP (v4 version) home agent home location of mobile host foreign agent mobile host correspondent host
- 79. Mobile IP (v6 version) home agent home location of mobile host mobile host correspondent host
- 80. Mobile IP (v6 version) home agent home location of mobile host mobile host correspondent host
- 81. Mobile IP (v6 version) home agent home location of mobile host mobile host correspondent host
- 82. Mobile IP (v6 version) home agent home location of mobile host mobile host correspondent host
- 83. Mobile IP (v6 version) home agent home location of mobile host mobile host correspondent host
- 84. IPv6 Routing
- 89. Porting Issues
- 101. IPv4 - IPv6 Co-Existence / Transition
- 110. 6to4 tunnels IPv4 IPv6 IPv6 6to4 prefix is 2002::/16 + IPv4 address. 2002:a.b.c.d::/48 IPv6 Internet 6to4 relay 2002:B00:1::1 Announces 2002::/16 to the IPv6 Internet 130.67.0.1 148.122.0.1 11.0.0.1 2002:8243:1::/48 2002:947A:1::/48 FP (3bits) TLA (13bits) IPv4 Address (32bits) SLA ID (16bits) Interface ID (64bits) 001 0x0002 ISP assigned Locally administered Auto configured
- 111. 6to4 tunnels II NB: there is a draft describing how to use IPv4 anycast to reach the relay router. (This is already supported, by our implementation...) Has to use 6to4 addresses, not native. Works without adjacent native IPv6 routers Requires relay router to reach native IPv6 Internet Only site border router needs to know about 6to4 All issues that NMBA networks have. Minimal configuration Cons Pros
- 112. Configured tunnels -------------------------------------- |IPv4 header|IPv6 header IPv6 payload| -------------------------------------- IPv4 protocol type = 41 IPv4 IPv6 IPv6 3ffe:c00:1::/48 3ffe:c00:2::/48 130.67.0.1 148.122.0.1
- 113. Configured tunnels II No keepalive mechanism, interface is always up Real addresses Inefficient traffic patterns Multicast Has to be configured and managed As point to point links Cons Pros
- 114. Automatic tunnels IPv4 IPv6 IPv6 Connects dual stacked nodes Quite obsolete IPv6 Internet 130.67.0.1 ::130.67.0.1 148.122.0.1 ::148.122.0.1 IPv4 Address (32bits) ISP assigned Defined 0
- 115. Automatic tunnels II Has to use IPv4 compatible addresses Useful for some other mechanisms, like BGP tunnels Difficult to reach the native IPv6 Internet, without injecting IPv4 routing information in the IPv6 routing table Obsolete Cons Pros
- 121. Current Status
- 131. Next Steps
- 136. Questions…
- 137. s.senthilkumar Technical project lead, IPOS-IPv6 Huawei Technologies India PVT LTD Level 3,4,5 and 7, Leela Galleria The Leela Palace, No 23, Airport Road, Bangalore – 560-008 E-Mail: senthilkumars@huawei.com
Notas del editor
- Established in 1988, Huawei Technologies is an innovative and customer-oriented global ICT (Information and Communication Technology) company that provides high quality products, solutions, and services. (Huawei is fully owned by its staff. In other words, employees are the owners of this company. That’s why employees work so hard and get so committed to their work.) By September 2005, Huawei has over 35,000 employees, 90% of them with a bachelor's degree or higher and over 48% people (about 16,800) devoted to R&D. Each year, Huawei invests no less than 10% of its revenue on R&D. This ensures that Huawei is a leading player in technology and to meet our customers’ demands very quickly. Huawei’s full product portfolio covers wireless network products (UMTS/HSDPA, CDMA2000, GSM/GPRS/EDGE and WiMAX), network products (NGN, xDSL, optical transmission, data communications), application and software products (IN, mobile data, OSS/BSS, CDN/SAN), and terminals. We are becoming a leading global supplier with products deployed in more than 90 countries, including the US, the UK, France, Portugal, Russia, Brazil, Singapore and Thailand, and serving 22 of the world’s top 50 operators Our last year’s contract sales reached 5.58 billion USD. In the first half of 2005, our contract sales reached over US$4.1 billion, an increase of 85% over last year, over 62% of which (US$2.47 billion) is from international markets.
- This slide shows Huawei’s HR (Human Resources) layout. Among our 35,000 staff members, 90% of employees hold bachelor's degree or higher. In R&D, we have a pre-research department to keep abreast with the latest technologies. Each year, 10% of our total R&D investment is put into pre-research. As for marketing, sales and customer service, we invest 38% of our staff in this area, as we understand that customer satisfaction is, and should be, the only benchmark to evaluate our work performance.
- In order to support our global operations, we have established our global sales and after-sales centers in the global market, including eight regional headquarters and over 70 branch offices outside China: they are located in North America, South America, CIS (the Commonwealth of Independent States), Western Europe, Eastern Europe, North Africa & Middle East, Southern Africa and Asia Pacific. To ensure customer-satisfied maintenance services, we have built a 3-Level Technical Support Service System, ranging from the Headquarters, Regional Headquarters and each single country or region. According to the Gallup survey, Huawei has been holding the No.1 position in terms of service quality and customer satisfaction for many years in the Chinese market. In the international market, we put high priority on improving our customer service. We have invested a lot in after-sales service to ensure high-level service in order to build a long-term partnership with our customers. According to the most recent survey done by Heavy Reading, a London-based research organization under the LightReading group, Huawei has won 16.7% customer recognition in customer service and support in early 2005 compared with the less than 1% in their last survey in autumn of 2003, ranking No.4 among all the worldwide vendors.
- Huawei has established a complete set of documented processes for all business procedures . Huawei QMS is seamless ly integrated with main business pro cedures such as Integrated Product Development, IPD, Integrated Supply Chain, ISC, Customer Service, and so on. Customer requirements from CRM (Customer Relationship Management) process is collected by OR process and is analyzed by MM process. MM drive s the IPD process to develop new product. Customer contracts from CRM process is inputted in to the ISC (Integrated Supply Chain) process which man ages sourcing, manufactur ing and logistic s. The CS (Customer Service) process manage s installation, commissioning, spare part s and customer training.
- Huawei’s major development strategy includes four points. 1. Serving our customers is the only reason why Huawei exists; Customer demand is the fundamental driving force of our development. 2. High quality, excellent service, low operating costs, and giving top priority to meeting customer requirements to enhance their competitiveness and profitability. 3. Continuously performing management transformation to realize efficient process-based organization operation for ensuring quality end-to-end delivery. 4. Developing with our peers in the industry as both competitors and partners to jointly create a favorable environment and share the benefits of the value chain.
- These slides were prepared in January, 2001.
- Overview of Internet Protocol version 6 Current status of IPv6 specifications, implementations, and transition tools Not Cisco specific! Background Header formats Packet size issues Addressing & routing Security Quality of service Mobility ICMPv6 & neighbor discovery Effects on higher layers IPv4-IPv6 coexistence & transition Current status
- IPv4 and ST were both specified in the late 1970’s. ST was a complementary protocol to IP, providing a connection-oriented internetwork service that was used to support early experiments in Internet audio/video teleconferencing. SIP[P], CATNIP, Pip, and TUBA were the four candidates considered in the early 1990’s by the IETF for the new IP. SIPP was the “winner”, after it was changed from having 64-bit addresses to 128-bit addresses. SIP = Simple Internet Protocol SIPP = Simple Internet Protocol Plus CATNIP = Common Address Technology for Next-Generation IP Pip = Paul’s IP? TUBA = TCP and UDP with Bigger Addresses (aka CLNP, the OSI Connectionless Network Layer Protocol)
- The IETF first recognized the problem of eventual IPv4 address exhaustion around 1990, and predicted we had about ten years to go, based on extrapolation of growth to that point (before the Web!). Indeed, it is only in the past year that the “IP address crunch” has become widely acknowledged. Note: We don’t expect there to be a day when the last IPv4 address is handed out; rather, they will just continue to become harder and harder to obtain, i.e., effectively running out, if not technically.
- “ IPng” stands for IP Next Generation, and was the working name for the new IP in the early phase of its development.
- IPsec = the IP-layer security protocols, ESP (Encapsulating Security Payload) and AH (Authentication Header), which are defined for both IPv4 and IPv6. These protocols allow receivers to detect and discard packets that have been modified in transit, e.g., by bad guys or by transmission errors. Unfortunately, NATs work by modifying packets in transit…
- Note that Quality of Service is not one of the benefits of IPv6 over IPv4, despite what you may have heard. Both versions of IP have exactly the same QoS features defined. The only difference is the presence of the Flow Label field in IPv6, which allows more efficient packet classification by routers, but this is really a minor implementation optimization, rather than a significant new QoS feature.
- Overview of Internet Protocol version 6 Current status of IPv6 specifications, implementations, and transition tools Not Cisco specific! Background Header formats Packet size issues Addressing & routing Security Quality of service Mobility ICMPv6 & neighbor discovery Effects on higher layers IPv4-IPv6 coexistence & transition Current status
- This is the general form of Global Unicast Addresses; some more specific forms are shown on the next two slides. TLAs are intended to be assigned to large, “tier-1” IP Service Providers (and perhaps, some day, to multi-ISP exchanges, such an an exchange serving a geographical region) One or more NLA fields are be used by TLAs to number their attached down-stream providers and/or end-subscriber sites. The SLA* field is used by end-subscriber sites to number their internal subnets. Very large sites might create a hierarchy of subnets within the SLA* field. The Interface ID field is used to number individual nodes (interfaces, actually) attached to a specific subnet. IPv6’s address auto-configuration technique depends on having the Interface ID field be 64-bits wide. The currently-proposed address allocation policy assigns a 16-bit SLA* field to every subscriber site (or, in other words, each subscriber is assigned a /48 prefix), but this policy is subject to change some day, so you should not assume a fixed boundary between the NLA* and SLA* fields.
- Current LANs like Ethernet use 48-bit MAC addresses defined by the IEEE 802 standards. The IEEE has introduced a new, 64-bit address space called EUI-64, for new kinds of LANs. There is a standard mapping from a 48-bit MAC into a 64-bit EUI-64.
- Overview of Internet Protocol version 6 Current status of IPv6 specifications, implementations, and transition tools Not Cisco specific! Background Header formats Packet size issues Addressing & routing Security Quality of service Mobility ICMPv6 & neighbor discovery Effects on higher layers IPv4-IPv6 coexistence & transition Current status
- Same two basic approaches are defined for both IPv4 and IPv6.
- Most of the RIP issues should be fixed in 12.2(2)T.
- Since BGP now supports multiple address families, we felt that it would make more sense to move the BGP commands up to the top level. I.e show ip bgp is now show bgp ipv4. The old CLI will still be supported. Currently only the IPv6 address family has moved to the new CLI.
- Overview of Internet Protocol version 6 Current status of IPv6 specifications, implementations, and transition tools Not Cisco specific! Background Header formats Packet size issues Addressing & routing Security Quality of service Mobility ICMPv6 & neighbor discovery Effects on higher layers IPv4-IPv6 coexistence & transition Current status
- Toolbox of mechanisms which can be combined.
- draft-ietf-ngtrans-6to4-07.txt Uses addresses out of the 6to4 address block, 2002::/16. A site’s prefix /48 is created by appending one of it’s global IPv4 addresses to this prefix. I.e 2002:10.67.0.1::/48.
- RFC2893 (obsoletes RFC1933) Just like point to point links. IPv6 packets are encapsulated in IPv4, protocol type 41.
- RFC2893 (RFC1933)
- Fragmentation: An IPv6 tunnel endpoint should only fragment when the IPv4 MTU is less than 1300 bytes. As long as the IPv4 MTU is larger, Path MTU discovery should take care to tell the IPv6 end-node about the MTU. The current implementation sets IPv6 MTU to IPv4 MTU - 20. If the path has a smaller MTU, IPv4 will have to fragment.
- There is nothing wrong with having the same interface ID on multiple interfaces on the same router. That is for example the typical case for IPv6 over IPv4 tunnels. Note that we will possibly change the way we generate the interface ID on point to point links, to just be the first MAC address in the box, in EUI-64 format.
- Overview of Internet Protocol version 6 Current status of IPv6 specifications, implementations, and transition tools Not Cisco specific! Background Header formats Packet size issues Addressing & routing Security Quality of service Mobility ICMPv6 & neighbor discovery Effects on higher layers IPv4-IPv6 coexistence & transition Current status
- Add text
- Add text
- Add text