0 Super one

0 My favourite collection Photos

This is the good time to be emotional before the valentine day and also this is the new year 2010 so this is little bit a picture to have good poem and phrase to share with on my blog.

0 National Do Not Call (NDNC) Registry – START DND to 1909

Informations from Author: Smith Solace

just visit my channel of the sms send sms on callmedaily

below given the number.

The National Do Not Call Registry (NDNC Registry) is setup to curb the Unsolicited Commercial Communication (UCC), which is any telecommunications service message, which is transmitted for the purpose of informing about or soliciting or promoting any commercial transaction in relation to goods, investments or services which a subscriber opts not to receive.

The NDNC Registry will be a database having the list of all telephone numbers of the subscribers who do not want to receive unsolicited messages. Telephone subscriber (land line or mobile) who does not wish to receive UCC, can register their telephone number with their telecom service provider for inclusion in the NDNC. Telecom Service Provider shall upload the telephone number to the NDNC within 45 days of receipt. The Telemarketer will have to verify their calling telephone numbers list with the NDNC registry before making a call.

An amount of Rs 500/- per call/message for the first call has been prescribed to discourage telemarketers who make calls to numbers registered in Do Not Call list. The second call will have a fine of Rs 1000/- and third time the line will be disconnected. The defaulter telemarketer will face disconnection of telecom service.

Each user need to register their number with their communication provider such as BSNL, Airtel, Reliance, Hutch etc. in order to register their cell number of land line number with the NDNC Registry. The provider may provide website interface or SMS interface for registering your number in NDNC Registry. Check with your provider for the details.

0 THE TCP/IP FAMILY TREE

AUTHOR: SMITH SOLACE

The Transmission Control Protocol (TCP) and the Internet Protocol (IP) together form the basis for TCP/IP, a low-level driver that lets computers talk to each other using a network of almost any size. The Internet is connected using TCP/IP as its foundation.

TCP/IP was proposed in 1973. Nine years later, in 1983, a standardized version of the protocol was developed and adopted for wide-area use. In 1983, it also became mandatory that all connections to ARPAnet, the Department of Defense’s predecessor to today’s Internet, be made with TCP/IP.

TCP/IP was developed to solve several problems in moving data from point A to point B. The most important requirement was to guarantee delivery of data on a network that might be under attack from a foreign power. Because the Department of Defense (DoD) developed the Internet, this requirement was paramount and fairly predictable. If an enemy were to attack the military’s computer systems and networks, data must continue to flow, secure and unhampered. The other established requirements were that data be moved efficiently and that its arrival be verified - yet the sending machine might not have any of the same operating characteristics as the receiving machine. TCP and IP both perform unique and vital functions that solve all the problems in moving data between machines over networks.

Transmission Control Protocol
TCP is the transmission layer of the protocol. Its primary function is to ensure reliable and verifiable data exchange between different hosts across a network. TCP performs its tasks by breaking data into manageable pieces and then wrapping the pieces with information called a header that routes the data to its final destination. TCP on the receiving machine then puts all the pieces back together, just as they were before the data was sent. The wrapped and bundled pieces are called datagrams.

The primary pieces of information in the TCP header are the source and destination port numbers, a sequence number for the datagram, and a checksum. Port numbers allow the data to be sent back and forth to the correct process running on each computer. (We cover ports in more detail later in this chapter.) The sequence number lets TCP reassemble the datagrams in the correct order. The checksum lets the protocol determine whether the data received is the data that was sent. The checksum calculates a number by adding all the octets of a datagram; this number is then inserted into the datagram’s header. The receiving computer performs the same calculation, and if the two calculations do not match, an error occurred somewhere along the line, and the datagram is resent.

After the TCP header is inserted into the datagram, TCP passes the datagram to the IP protocol to be routed to its final destinationshows the layout of a datagram with its TCP header structure.

Internet Protocol
IP is the network layer portion of TCP/IP. IP actually moves data from point A to point B across a network. This movement of data is called routing, and that’s really all IP does. (We cover routing in a bit more detail later in this chapter.) IP is typically considered unreliable, meaning that nothing guarantees that the data it routes will even arrive at its destination, much less in the order it was sent. IP relies on TCP to determine whether the data arrived successfully at its destination and to retransmit the data if it hasn’t.

To route data, IP inserts its own header into the datagram after it receives it from TCP. The contents of the IP header are the source and destination addresses, another checksum, and the protocol number. The header informs routers (or gateways) along the way of the datagram’s final destination. for a layout of a datagram complete with its TCP and IP headers. The IP header portion has a gray background.

0 NEW TCP IP PROTOCOLS

Other TCP/IP Protocols
The TCP/IP family consists of several other protocols typically referred to as application protocols, which are specialized protocols that use TCP/IP as their foundation. With the ever-growing popularity of the Internet, new application protocols are being developed at a blistering pace. Let’s look at a few:
• Address Resolution Protocol (ARP) helps link a physical media access control address (an Ethernet address) with a node’s associated IP address.
• Internet Control Message Protocol (ICMP) works at the IP network layer level and helps with network layer management and control, ensuring that errors are noted and corrected.
• Universal Datagram Protocol (UDP) is a connectionless protocol that is generally considered an unreliable way to send data across a network because it does not guarantee that the data sent will ever arrive at its destination. UDP is, however, a very efficient and fast way to send data because it does not have to connect and disconnect to send it, thus reducing network overhead.
• Simple Network Management Protocol (SNMP) makes it possible to collect information from network devices and lets network administrators manipulate configuration settings.
• Simple Mail Transfer Protocol (SMTP) allows for basic e-mail service across a network.
• Network News Transfer Protocol (NNTP) enables the propagation of public discussion forums.
• Telnet is a terminal emulation program that lets a user log on to a computer from a remote location.
• Internet Relay Chat (IRC) lets numerous users connect to a server, where they can all "chat" using real-time text-based messages.
• The World Wide Web, or the Web, as it’s commonly called, is a hypertext transfer protocol that makes it possible to display documents containing clickable links to other documents.
• File Transfer Protocol (FTP) lets users transfer files across a network.
• Finger lets one user look up contact information about another user by asking a specific system for that information.
• Whois lets a user query the global Whois databases for contact and location information about a user or domain name.
• Gopher lets a user search for documents and files containing specific keywords and phrases.
• Archie searches for files by file name or parts of file names.
• RealAudio allows for the transmission and receipt of prerecorded and live audio across a network.
• VDOLive enables the transmission and receipt of prerecorded and live video across a network.
Ports and Sockets
Data sent from one computer to another on a TCP/IP network is sent to a port on the receiving computer. A port is like a person at a particular address. You can certainly send postal mail to any address you desire; however, you usually address the mail to a particular person or department so that it gets into the right hands. Ports let the correct process receive the data directly.

All ports are assigned unique numbers ranging from 0 to 32768. Today, many ports are numerically standardized and preassigned. For example, SMTP mail servers normally run on port 25, and Web servers normally run on port 80. TCP/IP uses a modifiable lookup table, usually stored in a file called Services, to determine the correct port for the correct data type. Ports may be queried by name or number. Ports can sometimes be defined on the fly by a program that facilitates other actions.

TCP uses the IP address of the receiving computer, along with the correct port number, to build the socket address. We discuss sockets later in this section; for now, just understand that sockets are low-level tools used to read and write data from, not to be confused with ports.

TCP creates a connection to the receiving computer using the socket address. Although TCP sometimes stays connected while data is being sent, staying connected while transferring data is not necessary and in fact is not the norm. After the data is sent, TCP simply disconnects from the socket. Furthermore, datagrams can arrive at the destination at different times and out of sequence. As I mentioned earlier, TCP/IP receives the datagrams and puts them together in the right order, complete with an acknowledgment to the sender.

Sockets are low-level interfaces to the TCP/IP family that were initially developed for Unix operating systems (the BSD Unix operating system was the first). Sockets are like files on your hard drive; you can read from them and write to them, which is exactly how they are used in a TCP/IP networking environment. A socket is created either to await a connection and any subsequent data exchange or to create a connection and initiate a data exchange. When a server uses a socket to wait for an incoming connection, it is a passive socket; when a client uses a socket to initiate a connection, it is an active socket. The only difference between active and passive sockets is the way different software packages use them.

0 CJ ADD1

0 TCP IP GENERATION NEXT

The Future of TCP/IP - IP Next Generation
As you may have gathered, TCP/IP is an ever-evolving family of protocols. With the explosion of the Internet, we are seeing some of the limitations of this protocol suite. One problem in particular is that we will soon run out of usable IP addresses under the current specification, with so many new connections to the Internet being built and installed every day. Another major issue is security. Both of these serious problems are being addressed by various consortia that are quickly finding the answers. Let’s look at one of the foremost proposed solutions because it is likely to become a integral part of the protocol suite in the very near future.

The current version of the IP protocol is version 4, or IPv4, and the next generation, IPv6 or IPng (IP next generation), is set to become formally adopted. IPng was recommended by the IPng Area Directors of the Internet Engineering Task Force (IETF) at the Toronto IETF meeting held on July 25, 1994, as documented in RFC 1752, "The Recommendation for the IP Next Generation Protocol." (Request for Comments (RFCs) are a standard way to propose and debate the merits of any significant change or modification to a standard involving TCP/IP and the Internet in an open forum.) IPng was approved by the Internet Engineering Steering Group and made a Proposed Standard on November 17, 1994. The core set of IPng protocols was made an official IETF Proposed Standard on September 18, 1995.

IPng can be installed as a normal software upgrade to Internet devices and is interoperable with the current version of IPv4 found in today’s TCP/IP protocol. IPng is designed to run well on high performance networks, such as Asynchronous Transfer Mode (ATM), and at the same time is still efficient for low-bandwidth networks, such as wireless networks. In addition, IPng provides a platform for new Internet functions that will be required in the near future.

IPng was designed to be an evolutionary step up from IPv4 but not to be a radical step away from it. Functions that work in IPv4 were kept in the IPng specification, and likewise, the functions that didn’t work were removed. The changes from IPv4 to IPng fall primarily into the following categories:
• Expanded routing and addressing capabilities.
• IPng increases the IP address size from 32 bits to 128 bits, which obviously supports more levels of addressing and a much greater number of addressable nodes. IPng also facilitates a simpler means of automatically configuring IP addresses.
• A new type of address, the anycast address, is defined in IPng. An anycast address identifies nodes; a packet sent to an anycast address is delivered to one of the nodes. Using anycast addresses in the IPng source route lets nodes control the path along which their traffic flows. IPng address types are discussed further later in this section.
• Header format simplification - Some IPv4 header fields have been dropped or made optional to reduce the common processing cost of packet handling and to keep the bandwidth cost of the IPng header as low as possible despite the increased size of the addresses. Even though the IPng addresses are four times longer than the IPv4 addresses, the IPng header is only twice the size of the IPv4 header.
• Improved support for options - Changes in the way IP header options are encoded allow for more efficient forwarding, less stringent limits on the length of options, and greater flexibility for introducing new options.
• Quality-of-service capabilities - A new capability enables the labeling of packets belonging to particular traffic flows for which the sender requests special handling, such as nondefault quality of service or real-time service.
• Authentication and privacy capabilities - IPng defines extensions that provide support for authentication, data integrity, and confidentiality. These definitions are included as a basic element of IPng and will be included in all implementations.
There are three basic types of IPng addresses: unicast, anycast, and multicast. Unicast addresses identify a single interface. Anycast addresses identify a set of interfaces so that a packet sent to an anycast address is delivered to one member of the set. Multicast addresses identify groups of interfaces, so that a packet sent to a multicast address is delivered to all the interfaces in the group. Multicast addresses in IPng supersede broadcast addresses.

IPng supports 128-bit addresses, or four times the number of bits as the IPv4 32-bit addresses. This 128-bit addressing scheme is several times the size of the current IPv4 32-bit address space - 4 billion squared times the current space, or 340,282,366,920,938,463,463,374,607,431,768,211,456 bits.

The Internet has a number of major security problems and lacks effective privacy and authentication mechanisms below the application layer. IPng corrects these shortcomings with two integrated options that provide security services. These two options may be used separately or together to provide different levels of security to different users. This feature is very important because different user communities have different security requirements.

The first security mechanism, the IPng Authentication Header, is an extension header that gives IPng datagrams authentication and integrity without confidentiality. Although the extension is algorithm independent and will support many different authentication techniques, the use of an MD5 security system has been proposed to help ensure this feature’s interoperability within the Internet.

The IPng Authentication Header can eliminate a significant class of network attacks, including host-masquerading attacks. Using the IPng Authentication Header is particularly important when source routing is used with IPng because of the known risks in IP source routing. Its placement at the Internet layer can help provide host origin authentication to those upper-layer protocols and services that currently lack meaningful protection schemes.

The second security extension header provided with IPng is the IPng Encapsulating Security Header. This particular mechanism provides integrity and confidentiality to IPng datagrams. It’s simpler than similar security protocols, such as the Network Layer Security Protocol (ISO NLSP), but it remains flexible and algorithm independent. To ensure this header’s interoperability over the Internet, the Data Encryption Standard (DES) algorithm in the Cipher Block Chaining (CBC) mode (DES CBC) is being used as the standard algorithm. The DES CBC encryption process employs a 64-bit cryptographic key system.

Overall, IPng appears to be a very promising way of minimizing, if not eliminating, a few of the major problems in TCP/IP networking, especially Internet and security problems. You can expect every major vendor on the planet to adopt and implement this new protocol version in its hardware and software.