Abstract Syntax Notation 1 (ASN.

1)
it is used to describe the structure of data to be transferred between the Application Layer and the Presentation Layer of the Open Systems Interconnection (OSI) (next generation networking protocol). ASN.1 is meant to provide a mechanism whereby the Presentation Layer can use a single standard encoding to reliably exchange any arbitrary data structure with other computer systems, while the Application Layer can map the standard encoding into any type of representation or language that is appropriate for the end user. ASN.1 does not describe the content, meaning, or structure of the data, only the way in which it is specified and encoded. These properties make it an excellent choice for a standard way of encoding scientific data. Since ASN.1 does not specify content, specifications can be created as new concepts need to be represented. As it is an International Standards Organization (ISO) standard, the new specification can take advantage of various tools built to work with ASN.1 in general. It removes from scientists the role of specifying ad hoc file formats, and focuses them instead on specifying the content and structure of data necessary to convey scientific meaning.

Data Specification
There are two aspects to ASN.1--the specification of the data and the encoded data itself. The specification describes the abstract structure of the data and the allowed values various fields may take. Frequently scientific data is presented with no formal specification. There may be some documentation describing the data file, but very often it is incomplete or not entirely accurate, since it is usually written about the file rather than as a integral step toward building the file. The ASN.1 specification is formal language, which means it can be automatically and thoroughly checked for errors and inconsistencies in form by machine before any data is collected.

Commercial Tools
A number of commercial and public domain tools are available for working with ASN.1 and for automatically building data handlers of various sorts. They are focused on the use for which ASN.1 was originally intended, the exchange of data between layers of the OSI. As such they tend to automate the process more that AsnTool does, because the domain of use is more limited. The fact that they determine the internal data structures to use and write all the code

to handle them themselves is not a big problem in this case.

Encoding
ASN.1 can be used to encode data in two ways, an ASCII human readable form called "value notation" or "print form," a binary encoding. ASN.1 has separate standards documents for the syntax (specification rules) and the binary encoding rules (BER, or "Basic Encoding Rules"). This was done on purpose to allow various encoding rules for the same abstract syntax. The BER is, at this writing, the only official ISO encoding for ASN.1, but several other encodings which are faster or take less space, are under consideration by ISO. Currently the only binary encoding AsnTool supports is BER.

The management information base (MIB)

The Management Information Base (MIB) is a database containing The information that an agent can collect and a management system can request from an agent A MIB is a set of manageable objects representing various types of information about a network device, such as the number of active sessions or the version of network operating system software that is running on a host. SNMP management systems and agents share a common understanding of MIB objects. For a given MIB, the agent maintains information about the objects in the MIB and the management system retrieves the information in the MIB from the agent.

The database is conceptually organized as a tree. The upper structure of this tree is defined in Requests for Comments (RFC) 1155 and RFC 1213. The internal nodes of the tree represent subdivision by organization or function. MIB variable values are stored in the leaves of this tree. Thus, every distinct variable value corresponds to a unique path from the root of the tree. The children of a node are numbered sequentially from left to right, starting at 1, so that every node in the tree has a unique name, which consists of the sequence of node numbers that comprise the path from the root of the tree to the node. The Example Section of an MIB Tree figure (Figure ) illustrates the relationship of sections of the MIB tree.

MPLS
Multiprotocol-Label Switching (MPLS) is unlike many other networking technologies because it does not rely on a single protocol for getting packets from one point to another across a network. Instead, MPLS assigns each packet of data an individual label, then sends the packet out across any one of numerous paths independent of the transmission protocol. These paths, known as Label Switched Paths (LSPs), are preconfigured in the MPLS device and are known to be reliable network links. As the packet of data traverses the network, it is assigned a new label at each intermittent device until it finally reaches its destination, based on the intermittent router's knowledge of the network.

Benefits Because MPLS allows each individual node (or hop) along the network path to assign its own label, the service relies on the individual router's knowledge of the network topology to achieve transmission of data. If a particular circuit or link is down, the router closest to that circuit will assign an alternate lable, making the MPLS network "self healing" and much more resistant to sporadic network outages. This self-healing tendency allows MPLS packets to overcome latency or jitter issues which may beset traditional networks, improving the overall MPLS network performance. In addition, MPLS relies on

any number of protocols for transferring data packets, providing inherent redundancy in the transmission of MPLS packets.

Identification Just as voice telephone networking relies on signaling systems to set up circuits, MPLS also relies on signaling to identify its intended network path. Through signaling, MPLS can inform the routers and network devices along the originally intended path of incoming data, increasing the reliability of the labels assigned by these network elements. Depending on configuration--and the function of the particular network--either of two signaling systems may be used with MPLS: Local Distribution Protocol (LDP) or Resource Reservation Protocol - Traffic Engineering (RSVP-TE).

Types MPLS service itself is independent of protocols and may transfer data packets across a variety of network types. MPLS service may be paired with networks using ATM, Frame Relay, Ethernet, IP, or even older technologies.

Potential Because of its advanced transmission facilities and self-healing nature, MPLS has tremendous potential for data networking. Among the possible uses is optical-MPLS, or using lightwave frequencies in place of data labels to increase the speed with which data packets are transmitted. Optical-MPLS certainly stands to increase the speed at which commercial data flows, making tremendous gains in the transmission of large or sensitive data sets. MPLS may also be applied as a high-level switching and/or transmission method in hierarchical networks; this configuration would allow switches to operate at a higher level, conceivably increasing network speed and efficiency.

IPV6
IPv6 (Internet Protocol version 6) is the successor to IPv4, which is the current IP protocol version used on the Internet. As the Internet becomes more widely used, the IPv4 address space is likely to be exhausted some time early in this century. IPv6, however, can eliminate this address exhaustion problem. IPv6 address space is 128-bit and is much wider than IPv4 address space. Another feature of IPv6 is that security and automatic network set-up technologies are supported normally.

Advantagies of ipv6

1) Increased address space 2) More efficient routing 3) Reduced management requirement 4) Improved methods to change ISP 5) Better mobility support 6) Multi-homing 7) Security 8) Scoped address: link-local, site-local and global-address space http://niksi-ismo.blogspot.com/2011/06/ipv6-future-of-internet.html

EXTENSIBLE AUTHUNTICATION PROTOCOL

Extensible Authentication Protocol (EAP) is an authentication protocol used in PPP and 802.11 connections that can support multiple authentication mechanisms. IEEE 802.1x is based on EAP and is referred to as EAPoL (EAP over LAN). EAPol is used by EAPoW (EAP over Wireless) in the 802.11 standard to distribute WEP keys. EAP is a simple encapsulation that can run over any link layer. EAP typically runs directly over the link layer without requiring IP and therefore includes its own support for in-order delivery and retransmission.There are three main components to the authentication conversation:

Supplicant (client software) Authenticator (access point) Authentication Server (a RADIUS/AAA server)

The following graphic shows how these components are connected.

EAP Packet Format Code Identifier 1 byte1 byte Length Data 2 bytes variable length

The EAP packet can be carried in any type of frame (e.g. on PPP links it is carried in a PPP frame with a protocol number 0xC227). The fields in the packets are:

Code The Code field is one byte long and is used to interpret the Data field by identifying the type of EAP packet.

Code Description Reference 0 1 2 3 4 5 6 RFC 3748 RFC 3748 RFC 3748 RFC 3748 RFC 5296

Request Response Success Failure Initiate

Finish RFC 5296

Identifier The Identifier field is one byte long and contains an unsigned integer used to match requests with responses. Each new transmission uses a new Identifier number.

Length The Length field is two bytes long and contains the number of bytes in the entire packet. EAP assumes anything in excess of the Length is padding that can be ignored.

Data The Data field has a variable length (including zero bytes). The value of the Code field defines the way the Data field is to be interpreted.