Latest Technologies: Resource ReSerVation Protocol

India Latest Technology - NANO

The much awaited Tata small car, which is giving sleepless nights to its rivals, was finally unveiled at the Auto Expo 2008. The small car, which is priced at Rs100, 000 (2,500 dollars), has been named Nano. According to the Tata Motors, the Nano will hit the Indian roads later this year. Ever since the Tatas announced their intention of developing the 1 lakh car (touted as people’s car), the auto industry experts have been raising doubts over the price, features, safety and specifications of Tata Nano. Have a look at specifications and other aspects of the Tata Nano, the four door mini-hatchback.

Looks & Dimensions of Nano: Keeping in mind the young age group, the Tata Motors has strived well to give the Nano a contemporary and stylish look. The snub-nosed small car derives inspiration from Fiat 500 and Nissan Micra. As far as dimensions of the car are concerned, Nano is 3.1 metres (10.23 feet) long, 1.5 metres wide and 1.6 metres high and can accommodate four to five people.

Engine: The small car sports a two cylinder 623 cc, 33 horsepower rear mounted multi-point fuel injection (MPFi) petrol engine. Tata claims that the car can touch the top speed of 105 kms.

Fuel Efficiency: Engineers at Tata Motors have designed an efficient engine that can run 20 Kms on every litre of petrol.

Pollution: Against the criticism and concerns of the environmentalists, Nano surpasses Indian regulatory requirements and Euro IV emission norms. In fact, Tata claims that the small car is less polluting than most of the bikes on Indian roads.

Safety: Tata says that they have tested the small car extensively for front, rear and side collisions and come out with a product that exceeds current regulatory requirements. The safety features of the Nano include a strong passenger compartment, intrusion resistant doors, seat belts, sturdy seats and anchorage.
Price: The base model of the car will sport a price tag of Rs 100,000 (2,500 dollars) which excludes taxes and transport costs. The high end/deluxe models will include air-conditioning and other features to be incorporated based on suggestions of the common people

Thursday, February 14, 2008

Resource ReSerVation Protocol - RSVP

The RSVP protocol is part of a larger effort to enhance the current Internet architecture with support for Quality of Service flows. The RSVP protocol is used by a host to request specific qualities of service from the network for particular application data streams or flows. RSVP is also used by routers to deliver quality-of-service (QoS) requests to all nodes along the path(s) of the flows and to establish and maintain state to provide the requested service. RSVP requests will generally result in resources being reserved in each node along the data path.

A host uses RSVP to request a specific Quality of Service (QoS) from the network, on behalf of an application data stream.

RSVP carries the request through the network, visiting each node the network uses to carry the stream. At each node, RSVP attempts to make a resource reservation for the stream.

To make a resource reservation at a node, the RSVP daemon communicates with two local decision modules, admission control

and policy control. Admission control determines whether the node has sufficient available resources to supply the requested

QoS. Policy control determines whether the user has administrative permission to make the reservation. If either check fails,

the RSVP program returns an error notification to the application process that originated the request. If both checks

succeed, the RSVP daemon sets parameters in a packet classifier and packet scheduler to obtain the desired QoS. The packet

classifier determines the QoS class for each packet and the scheduler orders packet transmission to achieve the promised QoS

for each stream.

A primary feature of RSVP is its scalability. RSVP scales to very large multicast groups because it uses receiver-oriented

reservation requests that merge as they progress up the multicast tree. The reservation for a single receiver does not need

to travel to the source of a multicast tree; rather it travels only until it reaches a reserved branch of the tree. While the

RSVP protocol is designed specifically for multicast applications, it may also make unicast reservations.

RSVP is also designed to utilize the robustness of current Internet routing algorithms. RSVP does not perform its own

routing; instead it uses underlying routing protocols to determine where it should carry reservation requests. As routing

changes paths to adapt to topology changes, RSVP adapts its reservation to the new paths wherever reservations are in place.

This modularity does not rule out RSVP from using other routing services. Current research within the RSVP project is

focusing on designing RSVP to use routing services that provide alternate paths and fixed paths.

RSVP runs over IP, both IPv4 and IPv6. Among RSVP's other features, it provides opaque transport of traffic control and

policy control messages, and provides transparent operation through non-supporting regions.