Method and system for using extension headers to support protocol stack migration

1. A method for routing, comprising:

at a first node in a first network having a plurality of nodes, wherein a subset of the plurality of nodes are battery backed nodes:

receiving a first packet from a transmitting node, wherein the first packet has a first IP fixed header, a first hop-by-hop extension header, and a first payload, wherein the first hop-by-hop extension header includes non-IP protocol data, including data identifying at least one battery-backed node;

using the data identifying the at least one battery-backed node received in the first packet to select a second node in the first network to receive a second packet, wherein the second node is battery backed;

providing the second packet having a second IP fixed header, a second hop-by-hop extension header, and a second payload, wherein the second hop-by-hop extension header includes second non-IP protocol data; and

routing the second packet to the second node in the first network; and

at the second node in the first network:

receiving the second packet from the first node;

providing a third packet having a third IP fixed header, a third hop-by-hop extension header, and a third payload, wherein the third hop-by-hop extension header includes third non-IP protocol data; and

routing the third packet to a third node outside the first network.

2. The method of claim 1 , wherein the non-IP protocol data of the first hop-by-hop extension header includes information for routing within the first network using persistent routing.

3. The method of claim 1 , wherein the non-IP protocol data of the first hop-by-hop extension header includes one or more of the following: a non-IP address, a message ID, a fragment ID, security information, or encryption information.

4. The method of claim 1 , wherein the non-IP protocol data in the first extension header includes a time to live (TTL) value, and wherein the method further comprises:

at the first node,

confirming that the TTL value has not reached a predetermined threshold prior to routing the second packet to the second node in the first network.

5. The method of claim 1 , wherein the second non-IP protocol data in the second hop-by-hop extension header is different than the non-IP protocol data in the first hop-by-hop extension header.

6. The method of claim 1 , wherein the first node adds its address to the second hop-by-hop extension header and the second node adds its address to the third hop-by-hop extension header.

7. A battery-backed device in a network, comprising:

an application layer that includes a first application; and

a plurality of layers below the application layer, wherein one of the layers below the application layer is an IP layer,

wherein the device receives a first packet having a first IP fixed header, a first hop-by-hop extension header, and a first payload from a transmitting device, wherein the first hop-by-hop extension header includes non-IP protocol data, including data identifying at least one battery backed node in the network, wherein the network includes a plurality of nodes and only a subset of the nodes are battery-backed, and wherein the first application uses the data identifying the at least one battery backed node to select a second battery backed device in the network and the device generates a second packet having a second IP fixed header, a second hop-by-hop extension header, and a second payload and routes the second packet to the second battery-backed device in the network.

8. The device of claim 7 , wherein the non-IP protocol data of the first hop-by-hop extension header includes information for routing within the network using persistent routing.

9. The device of claim 7 , wherein the non-IP protocol data includes time to live (TTL) data, wherein the device confirms that the TTL data has not reached a predetermined threshold prior to routing the second packet to the second battery backed device in the network.

10. The device of claim 7 , wherein the application layer includes a second application designed for an IP protocol stack.

11. A method for providing an IP packet, comprising:

receiving, at a second node in a network, a first IP packet from a first node in the network, wherein the first IP packet includes a first IP fixed header, a first hop-by-hop extension header, and a first payload, wherein the first IP fixed header includes a hop limit value and the first hop-by-hop extension header includes non-IP protocol data, including a first time to live (TTL) value;

using at least a portion of the non-IP protocol data to determine whether the first TTL value has reached a predetermined threshold, wherein the first TTL value specifies a number of seconds;

if the first TTL value has reached the predetermined threshold, then overriding the hop limit value and discarding the first IP packet regardless of the value of the IP hop limit, or

if the first TTL value has not reached the predetermined threshold, then using the non-IP protocol data to select a third node in the network;

providing a second IP packet that includes a second IP header, a second hop-by-hop extension header, and a second payload, wherein the second hop-by-hop extension header includes non-IP protocol data including a second TTL value; and

transmitting the second IP packet to the third node.

12. The method of claim 11 , wherein the non-IP protocol data from the first hop-by-hop extension header includes information for routing within the network using at least one of the following routing options: persistent routing, quick routing, or reliable routing.

13. The method of claim 11 , wherein the non-IP protocol data of the first hop-by-hop extension header includes one or more of the following: a non-IP address, a message ID, a fragment ID, security information, or encryption information.

14. The method of claim 11 , wherein providing a second IP packet further comprises adding an address for the second node to the second IP extension header.