COMPANY BACKGROUND AND ITS ORGANISATIONAL STRUCTURE [TEC]

OBJECTIVES AND WORKS OF ORGANISATION TEC shall leverage its status as a centre of excellence in telecom to position India as a lead telecom knowledge and manufacturing hub of asia pacific nations by driving telecom standards, manufacturing support and network building skill sets in the interests of this region and market.TEC is committed to develop standards for the telecommunication sector in India, to ensure development of world class telecom network and smooth interconnection of individual networks. It will discharge its function as a testing & certification body. TEC will endeavor to do continual improvement in its processes by means of ICT implementation and will strive to achieve e TEC system. TEC is committed to provide timely support and advice to DOT on technical and licensing issues in addition to the core issues mentioned above. It ensure timely preparation & updating of new & existing GRs/ IRs /Test Schedules as per the Annual Action Plan, ensure timely conduct of field trials/testing/validation/ certification. To establish Next Generation Network (NGN) Lab in TEC to herald the deployment of such networks in the country: also, setting up of labs for the EMF radiation measurements. It is to ensure continual competency development through training of employees, develop TEC's infrastructure to achieve e-TEC. This will lead to paperless office working.

CHAPTER 1 OSI MODEL

The Open Systems Interconnection (OSI) model is a product of the Open Systems Interconnection effort at the International Organization for Standardization. It is a prescription of characterizing and standardizing the functions of a communications system in terms of abstraction layers. Similar communication functions are grouped into logical layers. A layer serves the layer above it and is served by the layer below it. For example, a layer that provides error-free communications across a network provides the path needed by applications above it, while it calls the next lower layer to send and receive packets that make up the contents of that path Two instances at one layer are connected by a horizontal connection on that layer.

Physical layer
The physical layer defines electrical and physical specifications for devices. In particular, it defines the relationship between a device and a transmission medium, such as a copper or fiber optical cable. This includes the layout of pins, voltages, cable specifications ,hubs, repeaters, network adapters, host bus adapters (HBA used in storage area networks) and more. The major functions and services performed by the physical layer are:

Establishment and termination of a connection to a communications medium. Participation in the process whereby the communication resources are effectively shared among multiple users. For example, contention resolution and flow control.

Modulation or conversion between the representation of digital data in user equipment and the corresponding signals transmitted over a communications channel. These are signals operating over the physical cabling (such as copper and optical fiber) or over a radio link.

Parallel SCSI buses operate in this layer, although it must be remembered that the logical SCSI protocol is a transport layer protocol that runs over this bus. Various physical-layer Ethernet standards are also in this layer; Ethernet incorporates both this layer and the data link layer. The same applies to other local-area networks, such as token ring, FDDI, ITU-T G.hn and IEEE 802.11, as well as personal area networks such as Bluetooth and IEEE 802.15.4.

Data link layer

The data link layer provides the functional and procedural means to transfer data between network entities and to detect and possibly correct errors that may occur in the physical layer. Originally, this layer was intended for point-to-point and point-to-multipoint media, characteristic of wide area media in the telephone system. Local area network

architecture, which included broadcast-capable multi-access media, was developed independently of the ISO work in IEEE Project 802. IEEE work assumed sub-layering and management functions not required for WAN use. In modern practice, only error detection, not flow control using sliding window, is present in data link protocols such as Point-to-Point Protocol (PPP), and, on local area networks, the IEEE 802.2 LLC layer is not used for most protocols on the Ethernet, and on other local area networks, its flow control and acknowledgment mechanisms are rarely used. Sliding window flow control and acknowledgment is used at the transport layer by protocols such as TCP, but is still used in niches where X.25 offers performance advantages. The ITU-T G.hn standard, which provides high-speed local area networking over existing wires (power lines, phone lines and coaxial cables), includes a complete data link layer which provides both error correction and flow control by means of a selective repeat Sliding Window Protocol. Both WAN and LAN service arrange bits, from the physical layer, into logical sequences called frames. Not all physical layer bits necessarily go into frames, as some of these bits are purely intended for physical layer functions. For example, every fifth bit of the FDDI bit stream is not used by the layer. Network layer The network layer provides the functional and procedural means of transferring variable length data sequences from a source host on one network to a destination host on a different network (in contrast to the data link layer which connects hosts within the same network), while maintaining the quality of service requested by the transport layer. The network layer performs network routing functions, and might also perform fragmentation and reassembly, and report delivery errors. Routers operate at this layer, sending data throughout the extended network and making the Internet possible. This is a logical addressing scheme values are chosen by the network engineer. The addressing scheme is not hierarchical. The network layer may be divided into three sub layers:

1. Sub network access that considers protocols that deal with the interface to networks, such as X.25; 2. Sub network-dependent convergence when it is necessary to bring the level of a transit network up to the level of networks on either side 3. Sub network-independent convergence handles transfer across multiple networks transport layer The transport layer provides transparent transfer of data between end users, providing reliable data transfer services to the upper layers. The transport layer controls the reliability of a given link through flow control, segmentation/de segmentation, and error control. Some protocols are state- and connection-oriented. This means that the transport layer can keep track of the segments and retransmit those that fail. The transport layer also provides the acknowledgement of the successful data transmission and sends the next data if no errors occurred.

Session Layer
The session layer controls the dialogues (connections) between computers. It establishes, manages and terminates the connections between the local and remote application. It provides for full-duplex, half-duplex, or simplex operation, and establishes check pointing, adjournment, termination, and restart procedures. The OSI model made this layer responsible for graceful close of sessions, which is a property of the Transmission Control Protocol, and also for session check pointing and recovery, which is not usually used in the Internet Protocol Suite. The session layer is commonly implemented explicitly in application environments that use remote procedure calls. On this level, Inter-Process communication happen (SIGHUP, SIGKILL, End Process, etc.).

Presentation layer
The presentation layer establishes context between application-layer entities, in which the higher-layer entities may use different syntax and semantics if the presentation service provides a mapping between them. If a mapping is available, presentation service data units are encapsulated into session protocol data units, and passed down the stack.

This layer provides independence from data representation (e.g., encryption) by translating between application and network formats. The presentation layer transforms data into the form that the application accepts. This layer formats and encrypts data to be sent across a network. It is sometimes called the syntax layer.

Application layer
The application layer is the OSI layer closest to the end user, which means that both the OSI application layer and the user interact directly with the software application. This layer interacts with software applications that implement a communicating component. Such application programs fall outside the scope of the OSI model. Application-layer functions typically include identifying communication partners, determining resource availability, and synchronizing communication. When identifying communication partners, the application layer determines the identity and availability of communication partners for an application with data to transmit. When determining resource availability, the application layer must decide whether sufficient network or the requested communication exist. In synchronizing communication, all communication between

applications requires cooperation that is managed by the application layer. Some examples of application-layer implementations also include:

CHAPTER 2 WHAT IS INTERNET PROTOCOL (IP) ?

Communications protocol, a set of rules & regulations that determine how data is transmitted in telecommunications and computer networking The Internet Protocol (IP) is the principal communications protocol used for

relaying data-grams (also known as network packets) across an internet work using the Internet Protocol Suite. Responsible for routing packets across network boundaries, it is the primary protocol that establishes the Internet. IP is the primary protocol in the Internet Layer of the Internet Protocol Suite and has the task of delivering data-grams from the source host to the destination host solely based on the addresses. For this purpose, IP defines datagram structures that encapsulate the data to be delivered. It also defines addressing methods that are used to label the datagram source and destination. Historically, IP was the connectionless datagram service in the original Transmission Control Program introduced by Vint Cerf and Bob Kahn in 1974, the other being the connection-oriented Transmission Control Protocol (TCP). The Internet Protocol Suite is therefore often referred to as TCP/IP. The first major version of IP, Internet Protocol Version 4 (IPv4), is the dominant protocol of the internet. Its successor is Internet Protocol Version 6

FUNCTION
The Internet Protocol is responsible for addressing hosts and routing data-grams (packets) from a source host to the destination host across one or more IP networks. For this purpose the Internet Protocol defines an addressing system that has two functions: identifying hosts and providing a logical location service. This is accomplished by defining standard data-grams and a standard addressing system

IP Packet Format

The following discussion describes the IP packet fields illustrated in Figure is given below

VersionIndicates the version of IP currently used. IP Header Length (IHL)Indicates the datagram header length in 32-bit words. Type-of-ServiceSpecifies how an upper-layer protocol would like a current datagram to be handled, and assigns datagrams various levels of importance. Total LengthSpecifies the length, in bytes, of the entire IP packet, including the data and header. IdentificationContains an integer that identifies the current datagram. This field is used to help piece together datagram fragments. FlagsConsists of a 3-bit field of which the two low-order (least-significant) bits control fragmentation. The low-order bit specifies whether the packet can be

fragmented. The middle bit specifies whether the packet is the last fragment in a series of fragmented packets. The third or high-order bit is not used. Fragment OffsetIndicates the position of the fragments data relative to the beginning of the data in the original datagram, which allows the destination IP process to properly reconstruct the original datagram. Time-to-LiveMaintains a counter that gradually decrements down to zero, at which point the datagram is discarded. This keeps packets from looping endlessly. ProtocolIndicates which upper-layer protocol receives incoming packets after IP processing is complete. Header ChecksumHelps ensure IP header integrity. Source AddressSpecifies the sending node. Destination AddressSpecifies the receiving node. OptionsAllows IP to support various options, such as security. DataContains upper-layer information

Transmission Control Protocol (TCP)

The TCP provides reliable transmission of data in an IP environment. TCP corresponds to the transport layer (Layer 4) of the OSI reference model. Among the services TCP provides are stream data transfer, reliability, efficient flow control, full-duplex operation, and multiplexing. With stream data transfer, TCP delivers an unstructured stream of bytes identified by sequence numbers. This service benefits applications because they do not have to chop data into blocks before handing it off to TCP. Instead, TCP groups bytes into segments and passes them to IP for delivery. TCP offers reliability by providing connection-oriented, end-to-end reliable packet delivery through an internetwork. It does this by sequencing bytes with a forwarding acknowledgment number that indicates to the

10

destination the next byte the source expects to receive. Bytes not acknowledged within a specified time period are retransmitted. The reliability mechanism of TCP allows devices to deal with lost, delayed, duplicate, or misread packets. A time-out mechanism allows devices to detect lost packets and request retransmission. TCP offers efficient flow control, which means that, when sending acknowledgments back to the source, the receiving TCP process indicates the highest sequence number it can receive without overflowing its internal buffers. Full-duplex operation means that TCP processes can both send and receive at the same time. Finally, TCPs multiplexing means that numerous simultaneous upper-layer conversations can be multiplexed over a single connection.

TCP FORMAT

11

The following descriptions summarize the TCP packet fields Source Port and Destination PortIdentifies points at which upper-layer source and destination processes receive TCP services. Sequence NumberUsually specifies the number assigned to the first byte of data in the current message. In the connection-establishment phase, this field also can be used to identify an initial sequence number to be used in an upcoming transmission. Acknowledgment NumberContains the sequence number of the next byte of data the sender of the packet expects to receive. Data OffsetIndicates the number of 32-bit words in the TCP header. ReservedRemains reserved for future use. FlagsCarries a variety of control information, including the SYN and ACK bits used for connection establishment, and the FIN bit used for connection termination. WindowSpecifies the size of the senders receive window (that is, the buffer space available for incoming data). ChecksumIndicates whether the header was damaged in transit. Urgent PointerPoints to the first urgent data byte in the packet. OptionsSpecifies various TCP options. DataContains upper-layer information.

12

CHAPTER 3 IPV6
IPv6 (Internet Protocol version 6) is a revision of the Internet Protocol (IP) developed by the Internet Engineering Task Force (IETF). IPv6 is intended to succeed IPv4, which is the dominant communications protocol for most Internet traffic as of 2012. IPv6 was developed to deal with the long-anticipated problem of IPv4 running out of addresses. IPv6 implements a new addressing system that allows for far more addresses to be assigned than with IPv4.

TECHNICAL DEFINITION
IPv6, like the most commonly used IPv4 (as of 2012), is an Internet-layer protocol for packet-switched internetworking and provides end-to-end datagram transmission

across multiple IP networks. It is described in Internet standard document RFC 2460, published in December 1998. In addition to offering more addresses, IPv6 also implements features not present in IPv4. It simplifies aspects of address assignment network renumbering and router announcements when changing network connectivity providers. The IPv6 subnet size has been standardized by fixing the size of the host identifier portion of an address to 64 bits to facilitate an automatic mechanism for forming the host identifier from link-layer media addressing information (MAC address). Network security is also integrated into the design of the IPv6 architecture, including the option of IPsec.

13

IPv6 Addresses and Prefixes

IPv6 addresses are hexadecimal, and are made up of eight pairs of octets separated by colons (:). An example of a valid address isfe80:0000:0000:0000:0260:0000:97ff:64aa. In the interests of brevity, addresses can be abbreviated in two ways: Leading zeros can be omitted, so this address can be written

asfe80:0:0:0:260:0:97ff:64aa. Consecutive zeros can be replaced with a double colon, so this address can be written as fe80::260:0:97ff:64aa. Note that a double colon can replace any number of consecutive zeros, but an address can only contain one double colon.

The Basic IPv6 Header

The IPv6 header no longer contains the header length, identification, flags, fragment offset and header checksum fields. Some of these options have been placed in extension headers. The Time To Live field has been replaced with a hop limit, and the IPv4 Type of Service field is now replaced with a Traffic Class field.

Version (4 bits) The constant 6 (bit sequence 0110). Traffic Class (8 bits)

14

The bits of this field hold two values. The 6 most-significant bits are used for DSCP, which is used to classify packets. The remaining two bits are used for ECN priority values subdivide into ranges: traffic where the source provides congestion control and non-congestion control traffic.

Flow Label (20 bits)

Originally created for giving real-time applications special service. The flow label when set to a non-zero value now serves as a hint to routers and switches with multiple outbound paths that these packets should stay on the same path so that they will not be reordered. It has further been suggested that the flow label be used to help detect spoofed packets.

Payload Length (16 bits)

The size of the payload in octets, including any extension headers. The length is set to zero when a Hop-by-Hop extension header carries a Jumbo Payload option

Next Header (8 bits)

Specifies the type of the next header. This field usually specifies the transport layer protocol used by a packet's payload. When extension headers are present in the packet this field indicates which extension header follows. The values are shared with those used for the IPv4 protocol field, as both fields have the same function (see List of IP protocol numbers).

Hop Limit (8 bits)

Replaces the time to live field of IPv4. This value is decremented by one at each intermediate node visited by the packet. When the counter reaches 0 the packet is discarded Source Address (128 bits) The IPv6 address of the sending node. Destination Address (128 bits) he IPv6 address of the destination node(s).In order to increase performance, and since current link layer technology is assumed to provide sufficient error detection, the header has no checksum to protect it

15

Extension headers
Extension headers carry optional Internet Layer information, and are placed between the fixed header and the upper-layer protocol header. The headers form a chain, using the Next Header fields. The Next Header field in the fixed header indicates the type of the first extension header; the Next Header field of the last extension header indicates the type of the upper-layer protocol header in the payload of the packet. All extension headers are a multiple of 8 octets in size; some extension headers require internal padding to meet this requirement. There are several extension headers defined,] and new extension headers may be defined in the future. Extension headers are to be examined and processed at the packet's destination only, except for Hop-by-Hop Options, which need to be processed at every intermediate node on the packet's path, including sending and receiving node. The defined extension headers below are listed in the preferred order, should there be more than one extension header following the fixed header. Note that all extension headers are optional and should only appear at most once, except for the Destination Options header, which may appear twice.

16

Extension Header

Type Description

Hop-by-Hop Options

Options that need to be examined by all devices on the path.

Destination routing header)

Options (before

60

Options that need to be examined only by the destination of the packet.

Routing

43

Methods to specify the route for a datagram (used with Mobile IPv6).

Fragment

44

Contains parameters for fragmentation of datagrams.

Authentication Header (AH)

51

Contains information used to verify the authenticity of most parts of the packet.

Encapsulating Security Payload (ESP)

50

Carries

encrypted

data

for

secure

communication.

Destination

Options (before

upper-layer header)

60

Options that need to be examined only by the destination of the packet.

Mobility (currently upper-layer header)

without

135

Parameters used with Mobile IPv6.

17

Fragmentation
Unlike in IPv4, IPv6 routers never fragment IPv6 packets. Packets exceeding the size of the maximum transmission unit of the destination link are dropped and this condition is signaled by a Packet too Big ICMPv6 type 2 message to the originating node, similarly to the IPv4 method when the Don't Fragment bit set. End nodes in IPv6 are expected to perform path MTU discovery to determine the maximum size of packets to send, and the upper-layer protocol is expected to limit the payload size. However, if the upper-layer protocol is unable to do so, the sending host may use the Fragment extension header in order to perform end-to-end fragmentation of IPv6 packets. Any data link layer conveying IPv6 data must be capable of delivering an IP packet containing 1280 bytes without the need to invoke end-to-end fragmentation at the IP layer.

Icmpv6
Internet Control Message Protocol version 6 (ICMPv6) is the implementation of the Internet Control Message Protocol (ICMP) for Internet Protocol version 6 (IPv6) defined in RFC 4443 ICMPv6 is an integral part of IPv6 and performs error reporting, diagnostic functions (e.g., ping), and a framework for extensions to implement future changes.

18

CHAPTER 4 MIGRATION FROM IPV4 TO IPV6

Migrating from IPv4 to IPv6 in an instant is impossible because of the huge size of the Internet and of the great number of IPv4 users. Moreover, many organizations are becoming more and more dependent on the Internet for their daily work, and they therefore cannot tolerate downtime for the replacement of the IP protocol. As a result, there will not be one special day on which IPv4 will be turned off and IPv6 turned on because the two protocols can coexist without any problems. The migration from IPv4 to IPv6 must be implemented node by node by using autoconfiguration procedures eliminate the need to configure IPv6 hosts manually. This way, users can immediately benefit from the many advantages of IPv6 while maintaining the possibility of communicating with IPv4 users or peripherals. Consequently, there is no reason to delay updating to IPv6! We have already seen that some IPv6 characteristics are explicitly designed to simplify the migration. For example, IPv6 addresses can be automatically derived from IPv4 addresses, IPv6 tunnels can be built on IPv4 networks, and at least in the initial phase, all IPv6 nodes will follow the dual stack approach; that is, they will support both IPv4 and IPv6 at the same time. This good level of compatibility between IPv4 and IPv6 may cause some users to think that the migration to IPv6 is useless. In the future, the choice of not migrating to IPv6 will limit the possibility of evolving because it will prevent users from accessing new implementations that, starting from 2000, will concern IPv6 only. IPv6 has been accurately designed, discussed thoroughly, and tested in the field by the IETF and by many other research institutions.

19

The key goals of the migration are as follow: .The use of IPv6 hosts and routers must be distributed over the Internet in a simple and progressive way, with a little interdependence. Network administrators and end users must think that the migration is easy to understand and implement. A set of mechanisms called SIT (Simple Internet Transition) has been implemented; it includes protocols and management rules to simplify the migration. The main characteristics of SIT are the following: Possibility of a progressive and non traumatic transition: IPv4hosts and routers can be updated to IPv6, one at a time, without requiring other hosts or routers to be updated simultaneously. Minimum requirements for updating: The only requirement for updating hosts to IPv6 is the availability of a DNS server to manage IPv6 addresses. No requirements are needed for routers. Addressing simplicity: When a router or a host is updated to IPv6, it can also continue to use IPv4 addresses. Low initial cost: No preparatory work is necessary to begin the migration to IPv6.

Mechanisms used by SIT include the following: A structure of IPv6 addresses that allows the derivation of IPv6 addresses from IPv4 addresses. The availability of the dual stack on hosts and on routers during the transition that is, the presence of both IPv4 and IPv6 stacks at the same time. A technique to encapsulate IPv6 packets inside IPv4 packets (tunneling) to allow IPv6 packets to traverse clouds not yet updated to IPv6. An optional technique that consists of translating IPv6 headers into IPv4 headers and vice versa to allow, in an advanced phase of the migration, IPv4-only nodes to communicate with IPv6-only nodes. The SIT approach guarantees that IPv6 hosts can interoperate with IPv4 hosts initially on the entire Internet. When the migration is completed, this interoperability will be locally guaranteed for a long time. This capability allows for the protection of investments made on IPv4;

20

simple devices that cannot be updated to IPv6for example, network printers and terminal serverswill continue to operate with IPv4 until they are no longer used. The possibility of a gradual migration allows manufacturers to integrate IPv6 in routers, operating systems, and network software when they think that implementations are stable and users to begin the migration at a time they consider the most appropriate. Migration problems are described in RFC 19331. The following sections of this chapter are dedicated to describing these problems.

Tunneling

As we mentioned in the introduction, while the IPv6 routing infrastructure is being deployed, the routing will continue to be based on IPv4. Tunneling techniques allow use of IPv4 networks to carry the IPv6 traffic. Hosts and routers supporting the dual stack (also called IPv4/IPv6 nodes) can use tunnels to route IPv6 packets over IPv4 regions In this example, host A sends the native IPv6 packet to router R1, which retransmits the packet in an IPv4 tunnel to router R2, which finally transmits it as a native IPv6 packet to host B. In this case, the tunnel is managed by R1 and R2.

21

From the encapsulation point of view, implementing a tunnel means encapsulating an IPv6 packet inside an IPv4 packet, as shown in Figure

Alternative Tunneling Schemes

During the migration, the tunneling technique can be used in the following ways:

22

Router-to-router: IPv6/IPv4 routers interconnected by an IPv4 infrastructure can tunnel IPv6 packets between themselves. See Figure (a). Host-to-router: IPv6/IPv4 hosts can tunnel IPv6 packets to an intermediary IPv6/IPv4 router that can be reached via an IPv4 infrastructure. See Figure (b). Host-to-host: IPv6/IPv4 hosts that are interconnected by an IPv4 infrastructure can tunnel IPv6 packets between themselves. See Figure (c). Router-to-host: IPv6/IPv4 routers can use tunnels to reach an IPv6/IPv4 host via an IPv4 infrastructure. See Figure (d). In the first two tunneling methodsrouter-to-router and host-to-routerthe IPv6 packet is tunneled to a router; therefore, the endpoint of this type of tunnel is a router that must decode the IPv6 packet and forward it to its final destination. No relationship exists between the router address and the final destination address. For this reason, the router address that is the tunnel endpoint must be manually configured. This type of tunnel is called a configured tunnel. In the last two tunneling methodshost-to-host and router-to-host the IPv6/IPv4 packet is tunneled from a host or from a router to its destination host. In this case, the tunnel endpoint address and the destination host address are the same. If the IPv6 address used for the destination node is an IPv4-compatible address .endpoint IPv4 address can be automatically derived from the IPv6 address, and therefore no manual configurations are necessary. These tunnel share also called automatic tunnels.

Hop Limit
In IPv6, a tunnel is like a single point-to-point link, and each tunnel corresponds to a hop. The Hop Limit field of the IPv6 header is therefore decremented by one when an IPv6 packet traverses a tunnel, independently from the number of IPv4 links the tunnel consists of.

Dual Stack Approach

23

The dual stack approach consists of providing hosts and routers with IPv6 and IPv4 protocol stacks. In the case of an IPv6/IPv4 host, a possible organization of protocol stacks .The dual stack approach doesnt necessarily require the ability to create tunnels, whereas the ability to create tunnels requires the dual stack approach. In general, both approaches are provided by IPv6/IPv4 implementations. The following is a simple description of the way the dual stack approach operates: If the destination address used by the application is an IPv4 address, then the IPv4 protocols stack is used. If the destination address used by the application is an IPv6 address with an embedded IPv4 address, then IPv6 is encapsulated inside IPv4. If the destination address is an IPv6 address of another type, then IPv6 is used, possibly encapsulated in the default configured tunnel.

6-Bone
The 6-Bone project (http://www-cnr.lbl.gov/6bone/) is a spontaneous derivation of the IETF IPng working group, and its aim is to implement and test IPv6 protocols with the final goal of replacing IPv4 with IPv6 on the Internet. 6-Bone is an informal collaboration between several research institutions located in Northern America, Europe, and Japan. A strategic phase of the migration from IPv4 to IPv6 is represented by able to transport IPv6 packets. As in the case of the present Internet IPv4backbone, the IPv6 backbone will consist of many ISPs and of user networks interconnected to form the new Internet. Until protocols of the IPv6 stack will be widely available and tested, with particular reference to the interoperability of implementations, ISPs and users may not want to migrate production IPv4 routers to avoid risks. Therefore, identifying a way to provide an IPv6 connectivity on the entire Internet without modifying the present IPv4 Internet is necessary in order to test IPv6 protocols and to use them as soon as possible. the implementation of an IPv6 backbone covering the entire Internet and

24

CHAPTER 5 LAB VIEW AND WORK

Conformance Testing
Conformance testing, also known as compliance testing, is a methodology used to ensure that a product or processor system meets a defined set of standards. These standards are commonly defined by large, independent entities such as the Institute of Electrical and Electronics Engineers (IEEE), the World Wide Web Consortium (W3C), European Telecommunications Standards Institute (ETSI), Internet Engineering Task Force (IETF) etc .In the industry, once the set of tests have been completed and found to comply with all the applicable standards, it is advertised as having been certified by the organization that defined the standards and the organization that has conducted the tests.

Conformance Testing of IPv6 Related Protocols

IPv6 is defined by over 60 IETF RFCs. The implementation of very large and complex RFCs is prone to misunderstanding and misinterpretation. Conformance testing of IPv6 protocols is a comprehensive and rigorous test methodology that ensures heterogeneous IPv6 devices behave consistently to the IPv6 specifications and correctly work in a multivendor environment. It increases product quality and gives confidence to the customers in using network devices in the IPv6 network and ensures interoperability with other devices. Conformance testing also saves time and money, by allowing vendors to verify a products design throughout the entire product lifecycle. Problems can be identified earlier in the development stage, reducing costly last-minute rework and post-deployment problems.

25

Conformance and performance testing of IPv6 requires a test bed that can test the performance and scalability limitations of a device or system under test. Creating such a test bed from hundreds of routers or switches is prohibitively expensive and difficult to manage. These tests can be simulated in the test lab to simulate real-world network conditions by using Spirent Test Centre

Spirent Test Centre

Spirent test center is an equipment to measure the performance, functionality and conformance of Layer 2 to layer 7 equipment under a variety of realistic and worst case scenarios. The key strength of Spirent test centre is a deterministic and repeatable test methodology.

Spirent Test Centre enables users to introduce impairment conditions like delay that occur over the network. It has 10/100/ 1000 MBPS, and 10 GBPS Ethernet ports (electrical and optical) ports for validating and evaluating new products and technologies. Spirent Test Centre emulates various protocols, network configuration, traffic impairments for testing various protocols related to IPv4 and IPv6. NGN lab in TEC has a test bed to emulate hundreds of routers, hosts and other network devices for

26

conformance, performance and interoperability testing. Following diagram shows the various elements of the NGN lab and their connectivity.

27

Terminology used
Node: Router: Host: Upper layer: A device that implements IPv6. A node that forwards IPv6 packets not explicitlyaddressed to itself. Any node that is not a router. A protocol layer immediately above IPv6. Examples are transport protocols such as TCP and UDP, controlprotocols such as ICMP, routing protocols such as OSPF,and internet or lower-layer protocols being "tunneled"over IPv6 such as IPX,AppleTalk, or IPv6 itself. Link: A communication facility or medium over which nodes can communicate at the link layer, i.e., the layerimmediately below IPv6. Examples are Ethernets (simpleor bridged); PPP links; X.25, Frame Relay, or ATMnetworks; and internet (or higher) layer "tunnels",such as tunnels over IPv4 or IPv6 itself. Neighbors: Interface: Address: Packet: Link MTU: Nodes attached to the same link. Node's attachment to a link. An IPv6-layer identifier for an interface or a set of interfaces. An IPv6 header plus payload. The maximum transmission unit, i.e., maximum packetsize in octets, that can be conveyed over a link. Path MTU: The minimum link MTU of all the links in a path betweena source node and a destination node.

28

(A) Conformance testing of Host as DUT

(B)Conformance testing of Router as DUT

29

Procedure for IPv6 Conformance Testing Using Spirent Test Centre. Steps: 1. Open Spirent Test Center Conformance Application from the user terminal.

30

2.Wait till the following screen appears.

31

3.Click to chassis. To view available ports.

32

4. Select the desire no. of available ports to reserve for performing testes.

33

5.Select a test say IPv6 Host and click on Load Test Suite to load the testing suite for testing

6.Select Set Parameters to enter parameters for the test selected in accordance to the test topology.

Enter a. IUT link local address. b. IUT Global address. c. IUT link layer address i.e. MAC address d. Tester Global interface addresses

34

7. Apply parameters (to save parameters use SAVE option on the GUI).

35

8. After setting parameters click on Map Ports (PCOs) to link logical address of ports to the physical ports as per the test topology.

36

9. Now click on select\run tests to perform testing.

10. Select the desired tests to be performed and click on start.

37

11. To view the progress of test click on Execute summary.

From here test result can be seen and test Report can be generated and saved.

38

BIBILOGRAPHY 1. 2. 3. WWW.wikipedia.org www.alliedtelesis.co.nz www.ip6.com

39