Routing methods, systems, and computer program products for using a region scoped node identifier

• US 10,411,997 B1
• Filed: 08/10/2018
• Issued: 09/10/2019
• Est. Priority Date: 12/27/2012
• Status: Active Grant

• Current Assignee: MORRIS ROUTING TECHNOLOGIES, LLC
• Original Assignee: Sitting Man LLC
• Inventors: Morris, Robert Paul
• Primary Examiner(s): Tran, Jimmy H
• Application Number:
  US16/101,380
• Time in Patent Office: 396 Days
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04W 40/38 adapting due to varying relative distances between nodes

Abstract

In various embodiments, an apparatus, a non-transitory computer-readable media, and a method are provided to: receive a first packet that is specified according to a Multiprotocol Label Switching (MPLS) network protocol and that includes: first data, and a first header with a region scoped node identifier that is in an identifier space having a scope that spans the region of the network and identifies a particular node in the region of the network; and in response to the selection of the region scoped node identifier in connection with the first data, transmit, based on the region scoped node identifier, the first data from a current node to the particular node in the region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.

Claims

1. An apparatus, comprising:

a current node configured to be positioned in a region of a network and to be positioned between a transmitting node and a receiving node, the current node including at least one non-transitory memory configured to store instructions, and one or more processors in communication with the at least one non-transitory memory, wherein the one or more processors is configured to execute the instructions to cause the current node to;

receive a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with a region scoped node identifier that is in an identifier space having a scope that spans the region of the network and that is configured for use in identifying a particular node in the region of the network;

identify the region scoped node identifier of the first header of the first packet;

in connection with the first data, utilize the region scoped node identifier; and

in response to the utilization of the region scoped node identifier in connection with the first data, transmit, based on the region scoped node identifier, the first data from the current node to the particular node in the region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.

2. The apparatus of claim 1, wherein the apparatus is configured such that the first header further includes another region scoped node identifier that is in the identifier space having the scope that spans the region, where the another region scoped node identifier is configured for use in identifying, for the particular node, a next node in the region of the network, for use by the particular node to transmit, based on the another region scoped node identifier, the first data from the particular node to the next node along the network path segment that includes the current node and the receiving node.

3. The apparatus of claim 1, wherein the apparatus is configured such that the first header further includes another region scoped node identifier that is in another identifier space having a scope that spans another region including a next node, where the another region scoped node identifier is configured for use in identifying, for the next node, another particular node in the another region of the network, for use by the next node to transmit, based on the another region scoped node identifier, the first data from the next node to the another particular node along the network path segment that includes the current node and the receiving node.

4. The apparatus of claim 1, wherein the apparatus is configured such that the first header further includes a scope-specific node identifier that is in an entity-specific identifier space that is specific to at least one node of the region including the particular node, where the scope-specific node identifier is configured for use in identifying, for the particular node, a next node in another region in which the particular node does not reside, for use by the particular node to transmit, based on the scope-specific node identifier, the first data from the particular node to the next node along the network path segment that includes the current node and the receiving node.

5. The apparatus of claim 1, wherein the apparatus is configured such that the first header further includes a scope-specific node identifier that is in an entity-specific identifier space that is specific to at least one node in another region including a next node, where the scope-specific node identifier is configured for use in identifying, for the next node, another particular node in yet another region in which the next node does not reside, for use by the next node to transmit, based on the scope-specific node identifier, the first data from the next node to the another particular node along the network path segment that includes the current node and the receiving node.

6. The apparatus of claim 1, wherein the apparatus is configured such that the first header further includes a node scoped network interface identifier that is configured for use in identifying a network interface of the particular node, for use by the particular node to transmit, based on the node scoped network interface identifier, the first data from the network interface of the particular node along the network path segment that includes the current node and the receiving node.

7. The apparatus of claim 1, wherein the apparatus is configured such that the region scoped node identifier results from use of different node-specific identifier spaces that are specific to different nodes in the region in the network, where the different node-specific identifier spaces include identical identifiers for identifying the particular node.

8. The apparatus of claim 7, wherein the apparatus is configured such that:

a first one of the identical identifiers for identifying the particular node in a first one of the different node specific identifier spaces, is defined by a first origin in a first one-dimensional metric space and a first coordinate relative to the first origin; and

a second one of the identical identifiers for identifying the particular node in a second one of the different node specific identifier spaces, is defined by a second origin in a second one-dimensional metric space and a second coordinate relative to the second origin.

9. The apparatus of claim 8, wherein the apparatus is configured such that at least one of:

the first origin and the second origin are identical;

or

the first coordinate and the second coordinate are identical.

10. The apparatus of claim 1, wherein the apparatus is configured to receive, from the transmitting node, a second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

11. The apparatus of claim 10, wherein the apparatus is configured such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

12. The apparatus of claim 10, wherein the apparatus is configured such that the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

13. The apparatus of claim 1, wherein the apparatus is configured to receive, from another transmitting node, a second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

14. The apparatus of claim 13, wherein the apparatus is configured such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

15. The apparatus of claim 13, wherein the apparatus is configured such that the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

16. The apparatus of claim 1, wherein the apparatus is configured such that at least one of:

said region scoped node identifier is configured for use in identifying the particular node by including an identifier of the particular node;

said region scoped node identifier is configured for use in identifying the particular node by being used to look up an identifier of the particular node;

said region scoped node identifier is configured for use in identifying the particular node by being used to look up an identifier of the particular node in a separate location;

said label switching forwarding paradigm includes a Multiprotocol Label Switching (MPLS) network protocol;

said label switching includes Multiprotocol Label Switching (MPLS);

said forwarding paradigm includes a network protocol;

said forwarding paradigm includes a routing protocol;

said identifier space includes an address space;

said region scoped node identifier includes an address;

said region is based on a domain;

said region includes a domain;

said region includes an area;

said first path segment includes a physical path segment;

said first path segment includes a virtual path segment;

said first path segment includes the at least one multi-hop path segment;

said first path segment does not include the at least one multi-hop path segment;

said part of the network path segment that includes the current node and the receiving node, includes a sub-segment of the network path segment that includes the current node and the receiving node;

said plurality of path segments that are capable of communicatively coupling the current node and the particular node as part of the network path segment that includes the current node and the receiving node, includes path sub-segments communicatively coupling the current node and the particular node;

said plurality of path segments that are capable of communicatively coupling the current node and the particular node as part of the network path segment that includes the current node and the receiving node, includes path sub-segments communicatively coupling the current node and the particular node, where one or more additional nodes are communicative coupled between the particular node and the receiving node;

said plurality of path segments that are capable of communicatively coupling the current node and the particular node as part of the network path segment that includes the current node and the receiving node, includes at least one path sub-segment communicatively coupling the current node and the particular node, where no additional node is communicative coupled between the particular node and the receiving node for the at least one path sub-segment;

said first data is transmitted from the current node in another packet that is a copy of the first packet;

said first data is transmitted from the current node in another packet that is at least partially similar to the first packet;

knowledge of only the region scoped node identifier, is insufficient to know a scope thereof;

knowledge of the region scoped node identifier is required to know a scope of the region scoped node identifier;

said region scoped node identifier does not identify any node inside the current node;

said region scoped node identifier only identifies the particular node;

or

said region scoped node identifier identifies the particular node by identifying a certain node inside the particular node.

17. An apparatus, comprising:

a current node configured to be positioned in a region of a network and to be positioned between a transmitting node and a receiving node, the current node including at least one non-transitory memory configured to store instructions, and one or more processors in communication with the at least one non-transitory memory, wherein the one or more processors is configured to execute the instructions to cause the current node to;

receive a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with a scope-specific node identifier that is in an identifier space specific to at least one node in the region of the network and that is configured for use in identifying, for the at least one node, a particular node in another region of the network that does not include the current node;

identify the scope-specific node identifier of the first header of the first packet;

in connection with the first data, utilize the scope-specific node identifier; and

in response to the utilization of the scope-specific node identifier in connection with the first data, transmit, based on the scope-specific node identifier, the first data from the current node to the particular node in the another region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.

18. The apparatus of claim 17, wherein the apparatus is configured such that the first header further includes another scope-specific identifier that is specific to at least one node in the another region and that is configured for use in identifying, for the at least one node in the another region, another particular node in yet another region of the network, for use by the particular node to transmit, based on the another scope-specific identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and the receiving node.

19. The apparatus of claim 17, wherein the apparatus is configured such that the first header further includes a region scoped node identifier that is in another identifier space having a scope that spans the another region of the network and that is configured for use in identifying, for the particular node, another particular node in the another region of the network, for use by the particular node to transmit, based on the region scoped node identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and the receiving node.

20. The apparatus of claim 17, wherein the apparatus is configured such that the first header further includes a node scoped network interface identifier that is configured for use in identifying a network interface of the particular node, for use by the particular node to transmit, based on the node scoped network interface identifier, the first data from the network interface of the particular node along the network path segment that includes the current node and the receiving node.

21. The apparatus of claim 17, wherein the apparatus is configured to receive, from the transmitting node, a second packet including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

22. The apparatus of claim 21, wherein the apparatus is configured such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

23. The apparatus of claim 21, wherein the apparatus is configured such that the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

24. The apparatus of claim 17, wherein the apparatus is configured to receive, from another transmitting node, a second packet including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

25. The apparatus of claim 24, wherein the apparatus is configured such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

26. The apparatus of claim 24, wherein the apparatus is configured such that the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

27. A non-transitory computer-readable media storing instructions, that when executed by one or more processors of a current node configured to be positioned in a region of a network and to be positioned between a transmitting node and a receiving node, cause the current node to:

receive a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with a region scoped node identifier that is in an identifier space having a scope that spans the region of the network and that is configured for use in identifying a particular node in the region of the network;

identify the region scoped node identifier of the first header of the first packet;

in connection with the first data, utilize the region scoped node identifier; and

in response to the utilization of the region scoped node identifier in connection with the first data, transmit, based on the region scoped node identifier, the first data from the current node to the particular node in the region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.

28. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that:

the region scoped node identifier is realized by use of different node-specific identifier spaces that are specific to different nodes in the region in the network, where the different node-specific identifier spaces include identical identifiers for identifying the particular node;

a first one of the identical identifiers for identifying the particular node in a first one of the different node specific identifier spaces, is defined by a first origin in a first one-dimensional metric space and a first coordinate relative to the first origin; and

a second one of the identical identifiers for identifying the particular node in a second one of the different node specific identifier spaces, is defined by a second origin in a second one-dimensional metric space and a second coordinate relative to the second origin;

the first origin and the second origin are identical; and

the first coordinate and the second coordinate are identical.

29. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to receive a second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments;

wherein the instructions, when executed by the one or more processors of the current node, further cause the current node to operate such that;

at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment; and

the second path segment is selected instead of the first path segment based on at least one of;

a response to a change in the network, a change in a policy, or a change in a metric.

32. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes another region scoped node identifier that is in the identifier space having the scope that spans the region, where the another region scoped node identifier is configured for use in identifying, for the particular node, a next node in the region of the network, for use by the particular node to transmit, based on the another region scoped node identifier, the first data from the particular node to the next node along the network path segment that includes the current node and the receiving node.

33. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a region scoped outside scope identifier that is in the identifier space having the scope that spans the region, where the region scoped outside scope identifier is configured for use in identifying, for the particular node and via a routing table lookup, a next path segment in a plurality of path segments to at least one next node in the region of the network without identifying any particular network interface of any particular next node in the at least one next node, for use by the particular node to transmit, based on the region scoped outside scope identifier, the first data from the particular node, via the next path segment, to a next node in the at least one next node along the network path segment that includes the current node and the receiving node.

34. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes another region scoped node identifier that is in another identifier space having a scope that spans another region including a next node, where the another region scoped node identifier is configured for use in identifying, for the next node, another particular node in the another region of the network, for use by the next node to transmit, based on the another region scoped node identifier, the first data from the next node to the another particular node along the network path segment that includes the current node and the receiving node.

35. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a region scoped outside scope identifier that is in another identifier space having a scope that spans another region including a next node, where the region scoped outside scope identifier is configured for use in identifying, for the next node, a next path segment to a next-next node in the region of the network without identifying any particular network interface of the next-next node, for use by the particular node to transmit, based on the region scoped outside scope identifier, the first data from the particular node, via the next path segment, to the next-next node along the network path segment that includes the current node and the receiving node.

36. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a region scoped outside scope identifier that is in the identifier space having the scope that spans the region, where the region scoped outside scope identifier is configured for use in identifying, for the next node and via a routing table lookup, a next path segment in a plurality of path segments to at least one next-next node in the region of the network without identifying any particular network interface of any particular next-next node in the at least one next-next node, for use by the next node to transmit, based on the region scoped outside scope identifier, the first data from the next node, via the next path segment, to a next-next node in the at least one next-next node along the network path segment that includes the current node and the receiving node.

37. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a region scoped outside scope identifier that is in the identifier space having the scope that spans the region, where the region scoped outside scope identifier is configured for use in identifying, for the next node and via a routing table lookup, a next path segment in a plurality of path segments to a plurality of next-next nodes in the region of the network without identifying any particular network interface of any particular next-next node in the plurality of next-next nodes, for use by the next node to transmit, based on the region scoped outside scope identifier, the first data from the next node, via the next path segment, to a next-next node in the plurality of next-next nodes along the network path segment that includes the current node and the receiving node.

38. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a scope-specific node identifier that is in an entity-specific identifier space that is specific to at least one node of the region including the particular node, where the scope-specific node identifier is configured for use in identifying, for the particular node, a next node in another region in which the particular node does not reside, for use by the particular node to transmit, based on the scope-specific node identifier, the first data from the particular node to the next node along the network path segment that includes the current node and the receiving node.

39. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a scope-specific outside scope identifier that is in an entity-specific identifier space that is specific to at least one node of the region including the particular node, where the scope-specific outside scope identifier is configured for use in identifying, for the particular node, a next node at least partially included in another region in which the particular node does not reside, for use by the particular node to transmit, based on the scope-specific outside scope identifier, the first data from the particular node to a network interface of the next node along the network path segment that includes the current node and the receiving node, where the network interface of the next node is not included in the region.

40. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a scope-specific node identifier that is in an entity-specific identifier space that is specific to at least one node in another region including a next node, where the scope-specific node identifier is configured for use in identifying, for the next node, another particular node in yet another region in which the next node does not reside, for use by the next node to transmit, based on the scope-specific node identifier, the first data from the next node to the another particular node along the network path segment that includes the current node and the receiving node.

41. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a scope-specific outside scope identifier that is in an entity-specific identifier space that is specific to at least one node in another region including a next node, where the scope-specific outside scope identifier is configured for use in identifying, for the next node, another particular node at least partially included in yet another region in which the next node does not reside, for use by the next node to transmit, based on the scope-specific outside scope identifier, the first data from the next node to a network interface of the another particular node along the network path segment that includes the current node and the receiving node.

42. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a node scoped network interface identifier that is configured for use in identifying a network interface of the particular node, for use by the particular node to transmit, based on the node scoped network interface identifier, the first data from the network interface of the particular node along the network path segment that includes the current node and the receiving node.

43. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the region scoped node identifier results from use of different node-specific identifier spaces that are specific to different nodes in the region in the network, where the different node-specific identifier spaces include identical identifiers for identifying the particular node.

44. The non-transitory computer-readable media of claim 43, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that:

a first one of the identical identifiers for identifying the particular node in a first one of the different node-specific identifier spaces, is defined by a first origin in a first one-dimensional metric space and a first coordinate relative to the first origin; and

a second one of the identical identifiers for identifying the particular node in a second one of the different node-specific identifier spaces, is defined by a second origin in a second one-dimensional metric space and a second coordinate relative to the second origin.

45. The non-transitory computer-readable media of claim 44, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that at least one of:

the first origin and the second origin are identical;

or

the first coordinate and the second coordinate are identical.

46. The non-transitory computer-readable media of claim 27, wherein a second packet is received, from the transmitting node, the second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

47. The non-transitory computer-readable media of claim 46, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

48. The non-transitory computer-readable media of claim 46, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

49. The non-transitory computer-readable media of claim 27, wherein a second packet is received, from another transmitting node, the second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

50. The non-transitory computer-readable media of claim 49, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

51. The non-transitory computer-readable media of claim 49, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

52. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to detect an indication in the first header that identifies the region scoped node identifier as an active identifier.

53. The non-transitory computer-readable media of claim 52, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first data is transmitted with an indication that identifies the region scoped node identifier as the active identifier.

54. The non-transitory computer-readable media of claim 52, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first data is transmitted with an indication that identifies another identifier in the first header other than the region scoped node identifier as the active identifier.

55. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the region spans a single node.

56. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the region spans a system that includes the current node operating as a first virtual node, where the system further includes the particular node as a second virtual node.

57. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the current node includes a border node for the region.

58. The non-transitory computer-readable media of claim 57, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that:

the first data is received from the transmitting node; and

the region scoped node identifier is received in response to a request that includes an IP address received from the transmitting node along with the first data and that is sent to a topology service.

59. The non-transitory computer-readable media of claim 58, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the topology service is included in the current node.

60. The non-transitory computer-readable media of claim 27, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the region scoped node identifier identifies a particular network interface of the particular node.

61. The non-transitory computer-readable media of claim 60, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the particular network interface is a loopback network interface.

30. A non-transitory computer-readable media storing instructions, that when executed by one or more processors of a current node configured to be positioned in a region of a network and be positioned between a transmitting node and a receiving node, cause the current node to:

receive a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with a scope-specific node identifier that is in an identifier space specific to at least one node in the region of the network and that is configured for use in identifying, for the at least one node, a particular node in another region of the network that does not include the current node;

identify the scope-specific node identifier of the first header of the first packet;

in connection with the first data, utilize the scope-specific node identifier; and

in response to the utilization of the scope-specific node identifier in connection with the first data, transmit, based on the scope-specific node identifier, the first data from the current node to the particular node in the another region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.

31. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that:

the scope-specific node identifier is realized by use of different node-specific identifier spaces that are specific to different nodes in the region in the network, where the different node-specific identifier spaces include identical identifiers for identifying the particular node;

a first one of the identical identifiers for identifying the particular node in a first one of the different node specific identifier spaces, is defined by a first origin in a first one-dimensional metric space and a first coordinate relative to the first origin;

a second one of the identical identifiers for identifying the particular node in a second one of the different node specific identifier spaces, is defined by a second origin in a second one-dimensional metric space and a second coordinate relative to the second origin;

at least one of;

the first origin and the second origin are identical;

or the first coordinate and the second coordinate are identical;

wherein the instructions, when executed by the one or more processors of the current node, further cause the current node to receive a second packet including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments;

wherein the instructions, when executed by the one or more processors of the current node, further cause the current node to operate such that;

at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment; and

the second path segment is selected instead of the first path segment based on at least one of;

a response to a change in the network, a change in a policy, or a change in a metric.

62. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes another scope-specific identifier that is specific to at least one node in the another region and that is configured for use in identifying, for the at least one node in the another region, another particular node in yet another region of the network, for use by the particular node to transmit, based on the another scope-specific identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and the receiving node.

63. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a scope-specific outside scope identifier that is specific to at least one node in the another region and that is configured for use in identifying, for the at least one node in the another region, another particular node at least partially included in yet another region of the network, for use by the particular node to transmit, based on the scope-specific outside scope identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and the receiving node.

64. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a region scoped node identifier that is in another identifier space having a scope that spans the another region of the network and that is configured for use in identifying, for the particular node, another particular node in the another region of the network, for use by the particular node to transmit, based on the region scoped node identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and the receiving node.

65. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a region scoped outside scope identifier that is in another identifier space having a scope that spans the another region of the network and that is configured for use in identifying, for the particular node, another particular node in the another region of the network, for use by the particular node to transmit, based on the region scoped outside scope identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and the receiving node.

66. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first header further includes a node scoped network interface identifier that is configured for use in identifying a network interface of the particular node, for use by the particular node to transmit, based on the node scoped network interface identifier, the first data from the network interface of the particular node along the network path segment that includes the current node and the receiving node.

67. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, allow the current node to receive, from the transmitting node, a second packet including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

68. The non-transitory computer-readable media of claim 67, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

69. The non-transitory computer-readable media of claim 67, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

70. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, allow the current node to receive, from the transmitting node, a second packet including second data and a second header including a scope-specific outside scope identifier, for transmitting, based on the scope-specific outside scope identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

71. The non-transitory computer-readable media of claim 70, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

72. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to map an identical identifier in one node-specific identifier space for another identical identifier in another node-specific identifier space prior to transmitting to the particular node.

73. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, allow the current node to receive, from another transmitting node, a second packet including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

74. The non-transitory computer-readable media of claim 73, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

75. The non-transitory computer-readable media of claim 73, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

76. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to detect an indication in the first header that identifies the scope-specific node identifier as a current identifier.

77. The non-transitory computer-readable media of claim 76, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first data is transmitted with an indication that identifies the scope-specific node identifier as the current identifier.

78. The non-transitory computer-readable media of claim 76, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first data is transmitted with an indication that identifies another identifier in the first header, rather than the scope-specific node identifier, as the current identifier.

79. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the region spans a single node.

80. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the region spans a system that includes the current node operating as a first virtual node, where the system further includes the particular node as a second virtual node.

81. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the current node includes an ingress or source node for the region.

82. The non-transitory computer-readable media of claim 81, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that:

the first data is received from the transmitting node; and

the scope-specific node identifier is received in response to a request that includes an IP address received from the transmitting node along with the first data and that is sent to a topology service.

83. The non-transitory computer-readable media of claim 82, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the topology service is included in the current node.

84. The non-transitory computer-readable media of claim 30, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the current node identifies the scope-specific identifier based on path information included in the header by a source node, where the path information is received by the source node in response to a request, sent by the source node to a network directory service, that includes a symbolic identifier.

85. The non-transitory computer-readable media of claim 84, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the network directory service includes at least one of a domain name service, a topology service, or a proxy service.

86. The non-transitory computer-readable media of claim 84, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the request is transmitted and the response is received via a domain name service protocol.

87. A method, comprising:

at a current node configured to be positioned in a region of a network and to be positioned between a transmitting node and a receiving node;

identifying a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with a region scoped node identifier that is in an identifier space having a scope that spans the region of the network and that is configured for use in identifying a particular node in the region of the network;

identifying the region scoped node identifier of the first header of the first packet;

in connection with the first data, utilizing the region scoped node identifier; and

in response to the utilization of the region scoped node identifier in connection with the first data, causing transmission, based on the region scoped node identifier, of the first data from the current node to the particular node in the region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.

88. The method of claim 87, wherein:

the region scoped node identifier is realized by use of different node-specific identifier spaces that are specific to different nodes in the region in the network, where the different node-specific identifier spaces include identical identifiers for identifying the particular node;

a first one of the identical identifiers for identifying the particular node in a first one of the different node-specific identifier spaces, is defined by a first origin in a first one-dimensional metric space and a first coordinate relative to the first origin; and

a second one of the identical identifiers for identifying the particular node in a second one of the different node-specific identifier spaces, is defined by a second origin in a second one-dimensional metric space and a second coordinate relative to the second origin;

the first origin and the second origin are identical; and

the first coordinate and the second coordinate are identical.

89. The method of claim 87, and further comprising:

receiving a second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments, wherein;

at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment; and

the second path segment is selected instead of the first path segment based on at least one of;

a response to a change in the network, a change in a policy, or a change in a metric.

90. The method of claim 87, wherein the first header further includes another region scoped node identifier that is in the identifier space having the scope that spans the region, where the another region scoped node identifier is configured for use in identifying, for the particular node, a next node in the region of the network, for use by the particular node to transmit, based on the another region scoped node identifier, the first data from the particular node to the next node along the network path segment that includes the current node and the receiving node.

91. The method of claim 87, wherein the first header further includes a region scoped outside scope identifier that is in the identifier space having the scope that spans the region, where the region scoped outside scope identifier is configured for use in identifying, for the particular node and via a routing table lookup, a next path segment in a plurality of path segments to at least one next node in the region of the network without identifying any particular network interface of any particular next node in the at least one next node, for use by the particular node to transmit, based on the region scoped outside scope identifier, the first data from the particular node, via the next path segment, to a next node in the at least one next node along the network path segment that includes the current node and the receiving node.

92. The method of claim 87, wherein the first header further includes another region scoped node identifier that is in another identifier space having a scope that spans another region including a next node, where the another region scoped node identifier is configured for use in identifying, for the next node, another particular node in the another region of the network, for use by the next node to transmit, based on the another region scoped node identifier, the first data from the next node to the another particular node along the network path segment that includes the current node and the receiving node.

93. The method of claim 87, wherein the first header further includes a region scoped outside scope identifier that is in another identifier space having a scope that spans another region including a next node, where the region scoped outside scope identifier is configured for use in identifying, for the next node, a next path segment to a next-next node in the region of the network without identifying any particular network interface of the next-next node, for use by the particular node to transmit, based on the region scoped outside scope identifier, the first data from the particular node, via the next path segment, to the next-next node along the network path segment that includes the current node and the receiving node.

94. The method of claim 87, wherein the first header further includes a region scoped outside scope identifier that is in the identifier space having the scope that spans the region, where the region scoped outside scope identifier is configured for use in identifying, for the next node and via a routing table lookup, a next path segment in a plurality of path segments to at least one next-next node in the region of the network without identifying any particular network interface of any particular next-next node in the at least one next-next node, for use by the next node to transmit, based on the region scoped outside scope identifier, the first data from the next node, via the next path segment, to a next-next node in the at least one next-next node along the network path segment that includes the current node and the receiving node.

95. The method of claim 87, wherein the first header further includes a region scoped outside scope identifier that is in the identifier space having the scope that spans the region, where the region scoped outside scope identifier is configured for use in identifying, for the next node and via a routing table lookup, a next path segment in a plurality of path segments to a plurality of next-next nodes in the region of the network without identifying any particular network interface of any particular next-next node in the plurality of next-next nodes, for use by the next node to transmit, based on the region scoped outside scope identifier, the first data from the next node, via the next path segment, to a next-next node in the plurality of next-next nodes along the network path segment that includes the current node and the receiving node.

96. The method of claim 87, wherein the first header further includes a scope-specific node identifier that is in an entity-specific identifier space that is specific to at least one node of the region including the particular node, where the scope-specific node identifier is configured for use in identifying, for the particular node, a next node in another region in which the particular node does not reside, for use by the particular node to transmit, based on the scope-specific node identifier, the first data from the particular node to the next node along the network path segment that includes the current node and the receiving node.

97. The method of claim 87, wherein the first header further includes a scope-specific outside scope identifier that is in an entity-specific identifier space that is specific to at least one node of the region including the particular node, where the scope-specific outside scope identifier is configured for use in identifying, for the particular node, a next node at least partially included in another region in which the particular node does not reside, for use by the particular node to transmit, based on the scope-specific outside scope identifier, the first data from the particular node to a network interface of the next node along the network path segment that includes the current node and the receiving node, where the network interface of the next node is not included in the region.

98. The method of claim 87, wherein the first header further includes a scope-specific node identifier that is in an entity-specific identifier space that is specific to at least one node in another region including a next node, where the scope-specific node identifier is configured for use in identifying, for the next node, another particular node in yet another region in which the next node does not reside, for use by the next node to transmit, based on the scope-specific node identifier, the first data from the next node to the another particular node along the network path segment that includes the current node and the receiving node.

99. The method of claim 87, wherein the first header further includes a scope-specific outside scope identifier that is in an entity-specific identifier space that is specific to at least one node in another region including a next node, where the scope-specific outside scope identifier is configured for use in identifying, for the next node, another particular node at least partially included in yet another region in which the next node does not reside, for use by the next node to transmit, based on the scope-specific outside scope identifier, the first data from the next node to a network interface of the another particular node along the network path segment that includes the current node and the receiving node.

100. The method of claim 87, wherein the first header further includes a node scoped network interface identifier that is configured for use in identifying a network interface of the particular node, for use by the particular node to transmit, based on the node scoped network interface identifier, the first data from the network interface of the particular node along the network path segment that includes the current node and the receiving node.

101. The method of claim 87, wherein the region scoped node identifier results from use of different node-specific identifier spaces that are specific to different nodes in the region in the network, where the different node-specific identifier spaces include identical identifiers for identifying the particular node.

102. The method of claim 101, wherein:

a first one of the identical identifiers for identifying the particular node in a first one of the different node-specific identifier spaces, is defined by a first origin in a first one-dimensional metric space and a first coordinate relative to the first origin; and

a second one of the identical identifiers for identifying the particular node in a second one of the different node-specific identifier spaces, is defined by a second origin in a second one-dimensional metric space and a second coordinate relative to the second origin.

103. The method of claim 102, wherein the first origin and the second origin are identical.

104. The method of claim 102, wherein the first coordinate and the second coordinate are identical.

105. The method of claim 87, and further comprising receiving, from the transmitting node, a second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

106. The method of claim 105, wherein at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

107. The method of claim 87, and further comprising receiving, from another transmitting node, a second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

108. The method of claim 107, wherein at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

109. The method of claim 107, wherein the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

110. The method of claim 87, wherein an indication in the first header that identifies the region scoped node identifier as an active identifier, is detected.

111. The method of claim 110, wherein the first data is transmitted with an indication that identifies the region scoped node identifier as the active identifier.

112. The method of claim 110, wherein the first data is transmitted with an indication that identifies another identifier in the first header other than the region scoped node identifier as the active identifier.

113. The method of claim 87, wherein the region spans a single node.

114. The method of claim 87, wherein the region spans a system that includes the current node operating as a first virtual node, where the system further includes the particular node as a second virtual node.

115. The method of claim 87, wherein the current node includes a border node for the region.

116. The method of claim 115, wherein:

the first data is received from the transmitting node; and

the region scoped node identifier is received in response to a request that includes an IP address received from the transmitting node along with the first data and that is sent to a topology service.

117. The method of claim 116, wherein the topology service is included in the current node.

118. The method of claim 87, wherein the region scoped node identifier identifies a particular network interface of the particular node.

119. The method of claim 118, wherein the particular network interface is a loopback network interface.

120. A method, comprising:

at a current node configured to be positioned in a region of a network and be positioned between a transmitting node and a receiving node;

identifying a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with a scope-specific node identifier that is in an identifier space specific to at least one node in the region of the network and that is configured for use in identifying, for the at least one node, a particular node in another region of the network that does not include the current node;

identifying the scope-specific node identifier of the first header of the first packet;

in connection with the first data, utilizing the scope-specific node identifier; and

in response to the utilization of the scope-specific node identifier in connection with the first data, causing transmission, based on the scope-specific node identifier, of the first data from the current node to the particular node in the another region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.

121. The method of claim 120, wherein:

the scope-specific node identifier is realized by use of different node-specific identifier spaces that are specific to different nodes in the region in the network, where the different node-specific identifier spaces include identical identifiers for identifying the particular node;

a first one of the identical identifiers for identifying the particular node in a first one of the different node-specific identifier spaces, is defined by a first origin in a first one-dimensional metric space and a first coordinate relative to the first origin;

a second one of the identical identifiers for identifying the particular node in a second one of the different node-specific identifier spaces, is defined by a second origin in a second one-dimensional metric space and a second coordinate relative to the second origin;

at least one of;

the first origin and the second origin are identical;

or the first coordinate and the second coordinate are identical;

wherein a second packet is identified including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments;

wherein;

at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment; and

the second path segment is selected instead of the first path segment based on at least one of;

a response to a change in the network, a change in a policy, or a change in a metric.

122. The method of claim 120, wherein the first header further includes another scope-specific identifier that is specific to at least one node in the another region and that is configured for use in identifying, for the at least one node in the another region, another particular node in yet another region of the network, for use by the particular node to transmit, based on the another scope-specific identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and the receiving node.

123. The method of claim 120, wherein the first header further includes a scope-specific outside scope identifier that is specific to at least one node in the another region and that is configured for use in identifying, for the at least one node in the another region, another particular node in yet another region of the network, for use by the particular node to transmit, based on the scope-specific outside scope identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and the receiving node.

124. The method of claim 120, wherein the first header further includes a region scoped node identifier that is in another identifier space having a scope that spans the another region of the network and that is configured for use in identifying, for the particular node, another particular node in the another region of the network, for use by the particular node to transmit, based on the region scoped node identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and the receiving node.

125. The method of claim 120, wherein the first header further includes a region scoped outside scope identifier that is in another identifier space having a scope that spans the another region of the network and that is configured for use in identifying, for the particular node, another particular node in the another region of the network, for use by the particular node to transmit, based on the region scoped outside scope identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and the receiving node.

126. The method of claim 120, wherein the first header further includes a node scoped network interface identifier that is configured for use in identifying a network interface of the particular node, for use by the particular node to transmit, based on the node scoped network interface identifier, the first data from the network interface of the particular node along the network path segment that includes the current node and the receiving node.

127. The method of claim 120, and further comprising:

receiving, from the transmitting node, a second packet including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

128. The method of claim 127, wherein at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

129. The method of claim 127, wherein the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

130. The method of claim 120, wherein a second packet is received from the transmitting node, the second packet including second data and a second header including a scope-specific outside scope identifier, for transmitting, based on the scope-specific outside scope identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

131. The method of claim 130, wherein at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

132. The method of claim 130, wherein the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

133. The method of claim 120, and further comprising receiving, from another transmitting node, a second packet including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

134. The method of claim 133, wherein at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

135. The method of claim 133, wherein the second path segment is selected instead of the first path segment based on at least one of:

a response to a change in the network, a change in a policy, or a change in a metric.

136. The method of claim 120, and further comprising:

detecting an indication in the first header that identifies the scope-specific node identifier as a current identifier.

137. The method of claim 136, wherein the first data is transmitted with an indication that identifies the scope-specific node identifier as the current identifier.

138. The method of claim 136, wherein the first data is transmitted with an indication that identifies another identifier in the first header, rather than the scope-specific node identifier, as the current identifier.

139. The method of claim 120, wherein the region spans a single node.

140. The method of claim 120, wherein the region spans a system that includes the current node operating as a first virtual node, where the system further includes the particular node as a second virtual node.

141. The method of claim 120, and further comprising:

mapping an identical identifier in one node-specific identifier space for another identical identifier in another node-specific identifier space prior to transmitting to the particular node.

142. The method of claim 141, wherein:

the first data is received from the transmitting node; and

the scope-specific node identifier is received in response to a request that includes an IP address received from the transmitting node along with the first data and that is sent to a topology service.

143. The method of claim 142, wherein the topology service is included in the current node.

144. The method of claim 143, wherein the first packet is received in response to a request that includes a symbolic identifier.

145. The method of claim 120, wherein the scope-specific node identifier has an outside scope and does not identify any particular network interface of the particular node.

146. The method of claim 120, wherein the scope-specific node identifier identifies a particular region and does not identify any particular border node of the particular region.

147. A method, comprising:

configuring at least a portion of a plurality of instructions; and

causing storage of the at least portion of the instructions on at least one non-transitory memory, where the instructions, in response to being executed by one or more processors of a current node, cause the current node to;

identify a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with a region scoped node identifier that is in an identifier space having a scope that spans the region of a network and that is configured for use in identifying a particular node in the region of the network;

identify the region scoped node identifier of the first header of the first packet;

in connection with the first data, utilize the region scoped node identifier; and

in response to the utilization of the region scoped node identifier in connection with the first data, transmit, based on the region scoped node identifier, the first data from the current node to the particular node in the region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node.

148. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that;

the region scoped node identifier is realized by use of different node-specific identifier spaces that are specific to different nodes in the region in the network, where the different node-specific identifier spaces include identical identifiers for identifying the particular node;

a first one of the identical identifiers for identifying the particular node in a first one of the different node-specific identifier spaces, is defined by a first origin in a first one-dimensional metric space and a first coordinate relative to the first origin; and

a second one of the identical identifiers for identifying the particular node in a second one of the different node-specific identifier spaces, is defined by a second origin in a second one-dimensional metric space and a second coordinate relative to the second origin;

the first origin and the second origin are identical; and

the first coordinate and the second coordinate are identical.

149. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to allow receipt of a second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments;

wherein the instructions, in response to being executed by the one or more processors of the current node, further cause the current node to operate such that;

at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment; and

the second path segment is selected instead of the first path segment based on at least one of;

a response to a change in the network, a change in a policy, or a change in a metric.

150. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a region scoped outside scope identifier that is in the identifier space having the scope that spans the region, where the region scoped outside scope identifier is configured for use in identifying, for the particular node and via a routing table lookup, a next path segment in a plurality of path segments to at least one next node in the region of the network without identifying any particular network interface of any particular next node in the at least one next node, for use by the particular node to transmit, based on the region scoped outside scope identifier, the first data from the particular node, via the next path segment, to a next node in the at least one next node along the network path segment that includes the current node and a receiving node.

151. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes another region scoped node identifier that is in another identifier space having a scope that spans another region including a next node, where the another region scoped node identifier is configured for use in identifying, for the next node, another particular node in the another region of the network, for use by the next node to transmit, based on the another region scoped node identifier, the first data from the next node to the another particular node along the network path segment that includes the current node.

152. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a region scoped outside scope identifier that is in another identifier space having a scope that spans another region including a next node, where the region scoped outside scope identifier is configured for use in identifying, for the next node, a next path segment to a next-next node in the region of the network without identifying any particular network interface of the next-next node, for use by the particular node to transmit, based on the region scoped outside scope identifier, the first data from the particular node, via the next path segment, to the next-next node along the network path segment that includes the current node.

153. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a region scoped outside scope identifier that is in the identifier space having the scope that spans the region, where the region scoped outside scope identifier is configured for use in identifying, for the next node and via a routing table lookup, a next path segment in a plurality of path segments to at least one next-next node in the region of the network without identifying any particular network interface of any particular next-next node in the at least one next-next node, for use by the next node to transmit, based on the region scoped outside scope identifier, the first data from the next node, via the next path segment, to a next-next node in the at least one next-next node along the network path segment that includes the current node and a receiving node.

154. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a region scoped outside scope identifier that is in the identifier space having the scope that spans the region, where the region scoped outside scope identifier is configured for use in identifying, for the next node and via a routing table lookup, a next path segment in a plurality of path segments to a plurality of next-next nodes in the region of the network without identifying any particular network interface of any particular next-next node in the plurality of next-next nodes, for use by the next node to transmit, based on the region scoped outside scope identifier, the first data from the next node, via the next path segment, to a next-next node in the plurality of next-next nodes along the network path segment that includes the current node and a receiving node.

155. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a scope-specific node identifier that is in an entity-specific identifier space that is specific to at least one node of the region including the particular node, where the scope-specific node identifier is configured for use in identifying, for the particular node, a next node in another region in which the particular node does not reside, for use by the particular node to transmit, based on the scope-specific node identifier, the first data from the particular node to the next node along the network path segment that includes the current node and a receiving node.

156. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a scope-specific outside scope identifier that is in an entity-specific identifier space that is specific to at least one node of the region including the particular node, where the scope-specific outside scope identifier is configured for use in identifying, for the particular node, a next node at least partially included in another region in which the particular node does not reside, for use by the particular node to transmit, based on the scope-specific outside scope identifier, the first data from the particular node to a network interface of the next node along the network path segment that includes the current node and a receiving node, where the network interface of the next node is not included in the region.

157. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a scope-specific node identifier that is in an entity-specific identifier space that is specific to at least one node in another region including a next node, where the scope-specific node identifier is configured for use in identifying, for the next node, another particular node in yet another region in which the next node does not reside, for use by the next node to transmit, based on the scope-specific node identifier, the first data from the next node to the another particular node along the network path segment that includes the current node and a receiving node.

158. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a scope-specific outside scope identifier that is in an entity-specific identifier space that is specific to at least one node in another region including a next node, where the scope-specific outside scope identifier is configured for use in identifying, for the next node, another particular node at least partially included in yet another region in which the next node does not reside, for use by the next node to transmit, based on the scope-specific outside scope identifier, the first data from the next node to a network interface of the another particular node along the network path segment that includes the current node and a receiving node.

159. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a node scoped network interface identifier that is configured for use in identifying a network interface of the particular node, for use by the particular node to transmit, based on the node scoped network interface identifier, the first data from the network interface of the particular node along the network path segment that includes the current node and a receiving node.

160. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the region scoped node identifier results from use of different node-specific identifier spaces that are specific to different nodes in the region in the network, where the different node-specific identifier spaces include identical identifiers for identifying the particular node.

161. The method of claim 160, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that;

a first one of the identical identifiers for identifying the particular node in a first one of the different node-specific identifier spaces, is defined by a first origin in a first one-dimensional metric space and a first coordinate relative to the first origin; and

a second one of the identical identifiers for identifying the particular node in a second one of the different node-specific identifier spaces, is defined by a second origin in a second one-dimensional metric space and a second coordinate relative to the second origin.

162. The method of claim 161, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that at least one of;

the first origin and the second origin are identical;

or

the first coordinate and the second coordinate are identical.

163. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that a second packet is received, from a transmitting node, the second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

164. The method of claim 163, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

165. The method of claim 163, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the second path segment is selected instead of the first path segment based on at least one of;

a response to a change in the network, a change in a policy, or a change in a metric.

166. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that a second packet is received, from another transmitting node, the second packet including second data and a second header including the region scoped node identifier, for transmitting, based on the region scoped node identifier, the second data from the current node to the particular node in the region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

167. The method of claim 166, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

168. The method of claim 166, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the second path segment is selected instead of the first path segment based on at least one of;

a response to a change in the network, a change in a policy, or a change in a metric.

169. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to detect an indication in the first header that identifies the region scoped node identifier as an active identifier.

170. The method of claim 169, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first data is transmitted with an indication that identifies the region scoped node identifier as the active identifier.

171. The method of claim 169, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first data is transmitted with an indication that identifies another identifier in the first header other than the region scoped node identifier as the active identifier.

172. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the region spans a single node.

173. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the region spans a system that includes the current node operating as a first virtual node, where the system further includes the particular node as a second virtual node.

174. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the current node includes a border node for the region.

175. The method of claim 174, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that;

the first data is received from a transmitting node; and

the region scoped node identifier is received in response to a request that includes an IP address received from the transmitting node along with the first data and that is sent to a topology service.

176. The method of claim 175, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the topology service is included in the current node.

177. The method of claim 147, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the region scoped node identifier identifies a particular network interface of the particular node.

178. The method of claim 177, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the particular network interface is a loopback network interface.

179. A method, comprising:

configuring at least a portion of a plurality of instructions; and

causing storage of the at least portion of the instructions on at least one non-transitory memory, where the instructions, in response to being executed by one or more processors of a current node, cause the current node to;

identify a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with a scope-specific node identifier that is in an identifier space specific to at least one node in a region of a network and that is configured for use in identifying, for the at least one node, a particular node in another region of the network that does not include the current node;

identify the scope-specific node identifier of the first header of the first packet;

in connection with the first data, utilize the scope-specific node identifier; and

in response to the utilization of the scope-specific node identifier in connection with the first data, transmit, based on the scope-specific node identifier, the first data from the current node to the particular node in the another region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node.

180. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that;

the scope-specific node identifier is realized by use of different node-specific identifier spaces that are specific to different nodes in the region in the network, where the different node-specific identifier spaces include identical identifiers for identifying the particular node;

a first one of the identical identifiers for identifying the particular node in a first one of the different node-specific identifier spaces, is defined by a first origin in a first one-dimensional metric space and a first coordinate relative to the first origin;

a second one of the identical identifiers for identifying the particular node in a second one of the different node-specific identifier spaces, is defined by a second origin in a second one-dimensional metric space and a second coordinate relative to the second origin;

at least one of;

the first origin and the second origin are identical;

or the first coordinate and the second coordinate are identical;

wherein the instructions, in response to being executed by the one or more processors of the current node, further cause the current node to receive a second packet including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments;

wherein the instructions, in response to being executed by the one or more processors of the current node, further cause the current node to operate such that;

at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment; and

the second path segment is selected instead of the first path segment based on at least one of;

a response to a change in the network, a change in a policy, or a change in a metric.

181. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes another scope-specific identifier that is specific to at least one node in the another region and that is configured for use in identifying, for the at least one node in the another region, another particular node in yet another region of the network, for use by the particular node to transmit, based on the another scope-specific identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and a receiving node.

182. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a scope-specific outside scope identifier that is specific to at least one node in the another region and that is configured for use in identifying, for the at least one node in the another region, another particular node in yet another region of the network, for use by the particular node to transmit, based on the scope-specific outside scope identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and a receiving node.

183. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a region scoped node identifier that is in another identifier space having a scope that spans the another region of the network and that is configured for use in identifying, for the particular node, another particular node in the another region of the network, for use by the particular node to transmit, based on the region scoped node identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and a receiving node.

184. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a region scoped outside scope identifier that is in another identifier space having a scope that spans the another region of the network and that is configured for use in identifying, for the particular node, another particular node in the another region of the network, for use by the particular node to transmit, based on the region scoped outside scope identifier, the first data from the particular node to the another particular node along the network path segment that includes the current node and a receiving node.

185. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first header further includes a node scoped network interface identifier that is configured for use in identifying a network interface of the particular node, for use by the particular node to transmit, based on the node scoped network interface identifier, the first data from the network interface of the particular node along the network path segment that includes the current node and a receiving node.

186. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is allowed to receive, from a transmitting node, a second packet including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

187. The method of claim 186, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

188. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to map an identical identifier in one node-specific identifier space for another identical identifier in another node-specific identifier space prior to transmitting to the particular node.

189. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is allowed to receive, from a transmitting node, a second packet including second data and a second header including a scope-specific outside scope identifier, for transmitting, based on the scope-specific outside scope identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

190. The method of claim 189, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

191. The method of claim 189, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the second path segment is selected instead of the first path segment based on at least one of;

a response to a change in the network, a change in a policy, or a change in a metric.

192. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is allowed to receive, from another transmitting node, a second packet including second data and a second header including the scope-specific node identifier, for transmitting, based on the scope-specific node identifier, the second data from the current node to the particular node in the another region via a second path segment selected, utilizing the routing table of the current node, from the plurality of path segments.

193. The method of claim 192, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that at least one of the first path segment or the second path segment is the at least one multi-hop path segment, and at least one of the first path segment or the second path segment is not the at least one multi-hop path segment.

194. The method of claim 192, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the second path segment is selected instead of the first path segment based on at least one of;

a response to a change in the network, a change in a policy, or a change in a metric.

195. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to detect an indication in the first header that identifies the scope-specific node identifier as a current identifier.

196. The method of claim 195, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first data is transmitted with an indication that identifies the scope-specific node identifier as the current identifier.

197. The method of claim 195, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first data is transmitted with an indication that identifies another identifier in the first header, rather than the scope-specific node identifier, as the current identifier.

198. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the region spans a single node.

199. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the region spans a system that includes the current node operating as a first virtual node, where the system further includes the particular node as a second virtual node.

200. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the current node includes an ingress or source node for the region.

201. The method of claim 200, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that;

the first data is received from a transmitting node; and

the scope-specific node identifier is received in response to a request that includes an IP address received from the transmitting node along with the first data and that is sent to a topology service.

202. The method of claim 201, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the topology service is included in the current node.

203. The method of claim 202, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the first packet is received in response to a request that includes a symbolic identifier.

204. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the scope-specific node identifier has an outside scope and does not identify any particular network interface of the particular node.

205. The method of claim 179, and comprising:

further configuring the at least portion of the instructions such that, in response to the instructions being executed by the one or more processors of the current node, the current node is caused to operate such that the scope-specific node identifier identifies a particular region and does not identify any particular border node of the particular region.

206. The method of claim 205, wherein at least one of:

only part of the instructions is subject to the configuring;

only the at least portion of the instructions is subject to the configuring;

an entirety of the instructions is subject to the configuring;

the at least portion of the instructions that is subject to the configuring, is also subject to the further configuring;

the at least portion of the instructions that is subject to the configuring, is the same as the at least portion of the instructions that is subject to the further configuring;

the at least portion of the instructions that is subject to the configuring, is different from the at least portion of the instructions that is subject to the further configuring;

a first part of the at least portion of the instructions is subject to the configuring, and a second part of the at least portion of the instructions that is subject to the further configuring;

the configuring occurs at the current node;

the configuring occurs at a certain node other than the current node;

the configuring and the further configuring occur at the current node;

the configuring and the further configuring occur at a certain node other than the current node;

the configuring occurs at the current node and the further configuring occurs at a certain node other than the current node;

the further configuring occurs at the current node and the configuring occurs at a certain node other than the current node;

the at least portion of the instructions that is subject to the configuring is a part thereof that, in response to being executed by the one or more processors of the current node, causes the current node to perform the first instance of the identification, the second instance of the identification, the utilization, and the transmission;

the at least portion of the instructions that is subject to the configuring is a part thereof that, in response to being executed by the one or more processors of the current node, causes the current node to perform at least one of the first instance of the identification, the second instance of the identification, the utilization, or the transmission;

the at least portion of the instructions that is subject to the configuring is not a part thereof that, in response to being executed by the one or more processors of the current node, causes the current node to perform the first instance of the identification, the second instance of the identification, the utilization, or the transmission;

the at least portion of the instructions that is subject to the configuring is a part thereof that, in response to being executed by the one or more processors of the current node, causes the current node to perform at least one operation other than the first instance of the identification, the second instance of the identification, the utilize, and the transmit;

the configuring includes customization;

the configuring includes causing the scope-specific node identifier to be set;

the configuring includes causing the scope-specific node identifier to be created;

the configuring includes causing at least one aspect of the scope-specific node identifier to be set;

the configuring includes causing at least one aspect of the scope-specific node identifier to be created;

the configuring includes causing an index associated with the scope-specific node identifier to be set;

the configuring includes causing an index associated with the scope-specific node identifier to be created;

the plurality of the instructions includes a subset of instructions required for the current node to operate;

the plurality of the instructions includes an entirety of instructions required for the current node to operate;

the causing storage includes causing storage of the at least portion of the instructions on the at least one non-transitory memory for being accessible to a user so that the user is capable of installing the instructions on other memory of the current node, for execution;

the causing storage includes causing storage of the at least portion of the instructions on the at least one non-transitory memory, that is part of the current node;

the causing storage includes causing storage of the at least portion of the instructions on the at least one non-transitory memory, that is part of the current node, so that the current node is provided to a user for use;

the causing storage includes installation of the instructions;

the causing storage includes causing transfer of the instructions from persistent storage to volatile memory;

the at least one non-transitory memory includes a register;

the at least one non-transitory memory includes volatile memory;

the at least one non-transitory memory includes persistent storage;

the method further comprises configuring the current node;

the method further comprises coupling the at least one non-transitory memory to the one or more processors;

the method further comprises providing the current node;

the method further comprises providing the at least one non-transitory memory;

the method further comprises providing the one or more processors;

the at least one non-transitory memory is part of the current node;

or

the at least one non-transitory memory is separate from current node memory of the current node.

207. A non-transitory computer-readable media storing instructions, that when executed by one or more processors of a current node configured to be positioned in a region of a network and to be positioned between a transmitting node and a receiving node, cause the current node to:

receive a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with an outside scope identifier that is in an identifier space specific to at least one node in the region of the network and that is configured for use in identifying, for the at least one node, another region of the network that does not include the current node;

identify the outside scope identifier of the first header of the first packet;

in connection with the first data, utilize the outside scope identifier; and

in response to the utilization of the outside scope identifier in connection with the first data, transmit, based on the outside scope identifier, the first data from the current node to a particular node at least partially included in the another region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.

208. The non-transitory computer-readable media of claim 207, wherein the outside scope identifier includes a region scoped outside scope identifier.

209. The non-transitory computer-readable media of claim 208, wherein the region scoped identifier is in an identifier space that spans a region that includes the current node and a network interface of the particular node, and the first data is transmitted via the first path segment to the network interface of the particular node.

210. The non-transitory computer-readable media of claim 207, wherein the outside scope identifier includes a node scoped outside scope identifier.

211. The non-transitory computer readable media of claim 207, wherein the outside scope identifier includes a scope-specific outside scope identifier that is in an identifier space that spans a region that includes at least the current node.

212. The non-transitory computer readable media of claim 211, wherein the instructions, when executed by the one or more processors of the current node, cause the current node to operate such that the first data is transmitted via the first path segment to a network interface of the particular node, where the network interface of the particular node is not included in the region.

213. A method, comprising:

at a current node configured to be positioned in a region of a network and to be positioned between a transmitting node and a receiving node;

identifying a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with an outside scope identifier that is in an identifier space specific to at least one node in the region of the network and that is configured for use in identifying, for the at least one node, another region of the network that does not include the current node;

identifying the outside scope identifier of the first header of the first packet;

in connection with the first data, utilizing the outside scope identifier; and

in response to the utilization of the outside scope identifier in connection with the first data, transmitting, based on the outside scope identifier, the first data from the current node to a particular node at least partially included in the another region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.

214. The method of claim 213, wherein the outside scope identifier includes a region scoped outside scope identifier.

215. The method of claim 214, wherein the region scoped identifier is in an identifier space that spans a region that includes the current node and a network interface of the particular node, and the first data is transmitted via the first path segment to the network interface of the particular node.

216. The method of claim 213, wherein the outside scope identifier includes a node scoped outside scope identifier.

217. The method of claim 213, wherein the outside scope identifier includes a scope-specific outside scope identifier that is in an identifier space that spans a region that includes at least the current node.

218. The method of claim 217, wherein the first data is transmitted via the first path segment to a network interface of the particular node, where the network interface of the particular node is not included in the region.

219. A method, comprising:

configuring at least a portion of a plurality of instructions; and

causing storage of the at least portion of the instructions on at least one non-transitory memory, where the instructions, in response to being executed by one or more processors of a current node, cause the current node to;

identify a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with an outside scope identifier that is in an identifier space specific to at least one node in a region of a network and that is configured for use in identifying, for the at least one node, another region of the network that does not include the current node;

identify the outside scope identifier of the first header of the first packet;

in connection with the first data, utilize the outside scope identifier; and

in response to the utilization of the outside scope identifier in connection with the first data, transmit, based on the outside scope identifier, the first data from the current node to a particular node at least partially included in the another region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node.

220. The method of claim 219, wherein the outside scope identifier includes a region scoped outside scope identifier.

221. The method of claim 220, wherein the region scoped identifier is in an identifier space that spans a region that includes the current node and a network interface of the particular node, and the first data is transmitted via the first path segment to the network interface of the particular node.

222. The method of claim 219, wherein the outside scope identifier includes a node scoped outside scope identifier.

223. The method of claim 219, wherein the outside scope identifier includes a scope-specific outside scope identifier that is in an identifier space that spans a region that includes at least the current node.

224. The method of claim 223, wherein the first data is transmitted via the first path segment to a network interface of the particular node, where the network interface of the particular node is not included in the region.

225. The method of claim 219, and further comprising:

configuring at least part of the plurality of instructions, where the instructions, in response to being executed by the one or more processors of the current node, cause the current node to;

map an identical identifier in one node-specific identifier space for another identical identifier in another node-specific identifier space prior to transmitting to the particular node.

226. A current node configured to be positioned in a region of a network and to be positioned between a transmitting node and a receiving node, the current node comprising:

means for receiving a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with a scope-specific node identifier that is in an identifier space specific to at least one node in the region of the network and that is configured for use in identifying, for the at least one node, a particular node in another region of the network that does not include the current node, wherein the current node is configured to identify the scope-specific node identifier of the first header of the first packet and, in connection with the first data, utilize the scope-specific node identifier; and

means for, in response to the utilization of the scope-specific node identifier in connection with the first data, transmitting, based on the scope-specific node identifier, the first data from the current node to the particular node in the another region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.

227. A current node configured to be positioned in a region of a network and to be positioned between a transmitting node and a receiving node, the current node comprising:

means for receiving a first packet that is specified according to a label forwarding paradigm and that includes;

first data, and a first header with an outside scope identifier that is in an identifier space specific to at least one node in the region of the network and that is configured for use in identifying, for the at least one node, another region of the network that does not include the current node, wherein the current node is configured to identify the outside scope identifier of the first header of the first packet and, in connection with the first data, utilize the outside scope identifier; and

means for, in response to the utilization of the outside scope identifier in connection with the first data, transmitting, based on the outside scope identifier, the first data from the current node to a particular node at least partially included in the another region via a first path segment selected, utilizing a routing table of the current node, from a plurality of path segments that include at least one multi-hop path segment and that are capable of communicatively coupling the current node and the particular node as part of a network path segment that includes the current node and the receiving node.