IP Library › Granted Patent US 12,192,163
Granted Patent B2
US 12,192,163 · App. 18/311,433 · Granted Jan 7, 2025

Systems and methods for advertising internet protocol (IP) version 4 network layer routing information with an IP version 6 next Hop address

Inventor: Gyan S Mishra (Boyds, MD)
Assignee: Verizon Patent and Licensing Inc.
H04L61/251H04L45/50H04L47/17H04L61/5069H04L69/325H04L2101/659
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,192,163
App. No.
18/311,433
Granted
Jan 7, 2025
Kind
B2
Abstract

A first network device associated with a network may establish an Internet protocol version 6 Multiprotocol BGP session with a second network device associated with the network. The first network device and second network device are both capable of forwarding both IPv4 and IPv6 packets with only an IPv6 address configured on the interface of both the first network device and second network device. The first network device may exchange Multiprotocol Reachability capability with second network device for corresponding 2-tuple Address Family Identifier/Subsequent Address Family Identifier. The first network device may advertise Internet protocol version 4 network layer reachability information and may advertise Internet protocol version 6 network layer reachability information with IPv6 extended next hop encoding using Internet Assigned Numbering Authority assigned capability code value 5 to second network device.

Claims (43)

1. A method, comprising:

encoding, by a network device, Internet protocol version 4 network layer reachability information with Internet protocol version 6 network layer reachability information in an Internet protocol version 6 address and via Internet protocol version 6 encoding; and

advertising, by the network device and over an Internet protocol version 6 Core network, the Internet protocol version 6 address via a border gateway protocol and via an Internet protocol version 6 session.

2. The method of claim 1 , further comprising:

establishing a single Internet protocol version 6 session acting as a pure transport mechanism with a second network device associated with the Internet protocol version 6 Core network.

3. The method of claim 1 , further comprising:

utilizing the Internet protocol version 6 address to advertise a multiprotocol label switching-labeled virtual private network address and multicast for a border gateway protocol-multiprotocol label switching Internet protocol virtual private network.

4. The method of claim 1 , wherein the Internet protocol version 4 network layer reachability information includes an Internet protocol version 4 unicast identifier, a virtual private network Internet protocol version 4 identifier, or a multicast virtual private network Internet protocol version 4 identifier.

5. The method of claim 1 , wherein the Internet protocol version 6 network layer reachability information includes an Internet protocol version 6 unicast identifier, a virtual private network Internet protocol version 6 identifier, or a multicast virtual private network Internet protocol version 6 identifier.

6. The method of claim 1 , wherein the Internet protocol version 6 Core network includes a route reflector network device.

7. The method of claim 1 , wherein Internet protocol version 4 network layer reachability information and Internet protocol version 6 network layer reachability information are advertised over an Internet protocol version 6 next hop.

8. A network device, comprising:

one or more processors configured to:

encode Internet protocol version 4 network layer reachability information with Internet protocol version 6 network layer reachability information in an Internet protocol version 6 address and via Internet protocol version 6 encoding; and

advertise, over an Internet protocol version 6 Core network, the Internet protocol version 6 address via an Internet protocol version 6 session,

wherein Internet protocol version 4 network layer reachability information and Internet protocol version 6 network layer reachability information are advertised over an IPv6 next hop.

9. The network device of claim 8 , wherein the Internet protocol version 6 Core network includes

a provider edge network device.

10. The network device of claim 8 , wherein the one or more processors are further configured to:

establish the Internet protocol version 6 session with a second network device to provide traffic to a server device.

11. The network device of claim 8 , wherein the Internet protocol version 6 address eliminates Internet protocol version 4 network devices and Internet protocol version 4 interfaces associated with the Internet protocol version 6 Core network.

12. The network device of claim 8 , wherein the one or more processors are further configured to:

utilize the Internet protocol version 6 address to advertise network layer reachability information.

13. The network device of claim 8 , utilize the Internet protocol version 6 address to advertise a multiprotocol label switching-labeled virtual private network address and multicast for a border gateway protocol-multiprotocol label switching Internet protocol virtual private network.

14. The network device of claim 8 , wherein the one or more processors are further configured to:

utilize the Internet protocol version 6 address to advertise:

a multiprotocol label switching-labeled virtual private network address, and

multicast for a border gateway protocol-multiprotocol label switching Internet protocol virtual private network.

15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a first network device, cause the first network device to:

encode Internet protocol version 4 network layer reachability information with Internet protocol version 6 network layer reachability information in an Internet protocol version 6 address and via Internet protocol version 6 encoding,

advertise, over an Internet protocol version 6 Core network, the Internet protocol version 6 address to a second network device,

wherein Internet protocol version 4 network layer reachability information and Internet protocol version 6 network layer reachability information are advertised over an Internet protocol version 6 next hop.

16. The non-transitory computer-readable medium of claim 15 , wherein the Internet protocol version 6 Core network further includes one or more of:

a first service provider network associated with the first network device and a second service provider network associated with the second network device, or

another network with a first autonomous system and a second autonomous system.

17. The non-transitory computer-readable medium of claim 15 , wherein the Internet protocol version 4 network layer reachability information includes an Internet protocol version 4 unicast identifier, a virtual private network Internet protocol version 4 identifier, or a multicast virtual private network Internet protocol version 4 identifier, and

wherein the Internet protocol version 6 network layer reachability information includes an Internet protocol version 6 unicast identifier, a virtual private network Internet protocol version 6 identifier, or a multicast virtual private network Internet protocol version 6 identifier.

18. The non-transitory computer-readable medium of claim 15 , wherein the second network device is a route reflector network device.

19. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the first network device to:

utilize the Internet protocol version 6 address to advertise a multiprotocol label switching-labeled virtual private network address and multicast for a border gateway protocol-multiprotocol label switching Internet protocol virtual private network.

20. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the first network device to:

establish a single Internet protocol version 6 session acting as a pure transport mechanism with the second network device associated with the Internet protocol version 6 Core network.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 4, 2023
From: MISHRA, GYAN S.
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 063539/0677 →
Continuity (2)
Continuation 17302154 · Apr 26, 2021
Related Publication 20230275869A1 · Aug 31, 2023
References Cited (32)
US 7246175B1 · Tappan · 2007 [cited by examiner]
US 9191318B1 · Van De Velde et al. · 2015 [cited by applicant]
US 20080170578A1 · Ould-Brahim · 2008 [cited by applicant]
US 20140189160A1 · Haddad · 2014 [cited by examiner]
US 20140215179A1 · Matsuhira · 2014 [cited by examiner]
US 20150295888A1 · Maslak · 2015 [cited by applicant]
US 20180109450A1 · Filsfils et al. · 2018 [cited by applicant]
US 20190166048A1 · Srinivasan · 2019 [cited by examiner]
US 20210336870A1 · Zhao et al. · 2021 [cited by applicant]
“Multiprotocol BGP”, Juniper, Mar. 26, 2021, https://web.archive.org/web/20210414120057/https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/multiprotocol-bgp.html (Capture on waybackmachine f… [cited by applicant]
Aggarwal, et al., “BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs”, Internet Engineering Task Force (IETF), Feb. 2012, 59 Pages. [cited by applicant]
Bates, et al., “Multiprotocol Extensions for BGP-4”, Network Working Group, Jan. 2007, 12 Pages. [cited by applicant]
Bradner, “Key words for use in RFCs to Indicate Requirement Levels”, https://tools.ietf.org/html/rfc2119, Mar. 1997, 4 pages. [cited by applicant]
Chen, et al., “Dynamic Capability for BGP-4 drafl-ielf-idr-dynamic-cap-14.txt”, Network Working Group, Dec. 5, 2011, 7 Pages. [cited by applicant]
Cotton, et al., “Guidelines for Writing an IANA Considerations Section in RFCs”, Internet Engineering Task Force (IETF), Jun. 2017, 47 Pages. [cited by applicant]
De Clercq, et al., “BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN”, Network Working Group, Sep. 2006, 18 Pages. [cited by applicant]
De Clercq, et al., “Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)”, Network Working Group, Feb. 2007, 14 Pages. [cited by applicant]
Hinden, et al., “IP Version 6 Addressing Architecture”, Network Working Group, Feb. 2006, 25 Pages. [cited by applicant]
Le Faucheur, et al., “Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop”, Network Working Group, May 2009, 10 Pages. [cited by applicant]
Leiba, “Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words”, Internet Engineering Task Force (IETF), May 2017, 4 Pages. [cited by applicant]
Li, et al., “Softwire Problem Statement”, Network Working Group, Jul. 2007, 23 Pages. [cited by applicant]
Marques, et al., “Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)”, Network Working Group, Nov. 2006, 14 Pages. [cited by applicant]
Marques, “Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing”, Network Working Group, Mar. 1999, 5 Pages. [cited by applicant]
Mishra, et al., “Deployment Guidelines for Edge Peering IPv4-NLRI with IPv6-NH draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-02”, BESS Working Group, Mar. 23, 2021, 12 Pages. [cited by applicant]
Mishra, et al., “IPv4 NLRI with IPv6 Next Hop Use Cases drafl-mishra-bess-deplment-guidlin-ipv4nlri-ipv6nh-00”, BESS Working Group, Mar. 22, 2021, 12 Pages. [cited by applicant]
Mishra, et al., “IPv4 NLRI with IPv6 Next Hop Use Cases drafl-mishra-bess-ipv4nlri-ipv6nh-use-cases-10”. [cited by applicant]
Rosen, et al., “BGP/MPLS IP Virtual Private Networks (VPNs)”, Network Working Group, Feb. 2006, 47 Pages. [cited by applicant]
Rosen, et al., “Multicast in MPLS/BGP IP VPNs”, Internet Engineering Task Force (IETF), Feb. 2012, 88 Pages. [cited by applicant]
Rosen, et al., “Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)”, Internet Engineering Task Force (IETF), Jan. 2011, 32 Pages. [cited by applicant]
Rosen, “Using BGP to Bind MPLS Labels to Address Prefixes”, Internet Engineering Task Force (IETF), Oct. 2017, 23 Pages. [cited by applicant]
Scudder, et al., “Capabilities Advertisement with BGP-4”, Network Working Group, Feb. 2009, 7 Pages. [cited by applicant]
Wu, et al., “Softwire Mesh Framework”, Network Working Group, Jun. 2009, 31 Pages. [cited by applicant]