IP Library › Granted Patent US 12,231,327
Granted Patent B2
US 12,231,327 · App. 18/333,800 · Granted Feb 18, 2025

Reverse forwarding information base enforcement

Inventors: Abilash Menon (Boxborough, MA); Robert Penfield (Concord, MA); Hadriel S. Kaplan (Nashua, NH)
Assignee: 128 Technology, Inc.
H04L45/36H04L47/32H04L49/309
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,231,327
App. No.
18/333,800
Granted
Feb 18, 2025
Kind
B2
Abstract

In exemplary embodiments of the present invention, a router determines whether or not to establish a stateful routing session based on the suitability of one or more candidate return path interfaces. This determination is typically made at the time a first packet for a new session arrives at the router on a given ingress interface. In some cases, the router may be configured to require that the ingress interface be used for the return path of the session, in which case the router may evaluate whether the ingress interface is suitable for the return path and may drop the session if the ingress interface is deemed by the router to be unsuitable for the return path. In other cases, the router may be configured to not require that the ingress interface be used for the return path, in which case the router may evaluate whether at least one interface is suitable for the return path and drop the session if no interface is deemed by the router to be suitable for the return path.

Claims (50)

1. A router comprising:

an interface; and

processing circuitry having access to a memory, the processing circuitry configured to:

receive, via the interface, a packet of a forward packet flow;

determine that the router does not store a valid route for forwarding packets of a reverse packet flow for the forward packet flow via a first candidate interface;

based at least in part on determining that the router does not store the valid route for forwarding packets of the reverse packet flow via the first candidate interface, determine that the router stores a valid route for forwarding packets of the reverse packet flow via a second candidate interface; and

based at least in part on determining that the router stores a valid route for forwarding packets of the reverse packet flow via the second candidate interface, establish a stateful routing session using the second candidate interface for the reverse packet flow.

2. The router of claim 1 , wherein the processing circuitry is further configured to:

receive a packet of the reverse packet flow; and

forward, via the second candidate interface, the packet of the reverse packet flow.

3. The router of claim 1 , wherein to establish the stateful routing session, the processing circuitry is configured to:

modify the packet to include metadata specifying a session identifier for the stateful routing session; and

forward, to a next-hop for the forward packet flow, the modified packet.

4. The router of claim 1 , wherein the interface and the second candidate interface are the same interface.

5. The router of claim 1 , further comprising the second candidate interface, wherein the interface and the second candidate interface are different interfaces.

6. The router of claim 1 , wherein to determine that the router stores the valid route for forwarding packets of the reverse packet flow via the second candidate interface, the processing circuitry is configured to:

determine that a routing information base (RIB) of the router stores a valid route for forwarding the packets of the reverse packet flow via the second candidate interface.

7. The router of claim 1 , wherein to determine that the router stores the valid route for forwarding packets of the reverse packet flow via the second candidate interface, the processing circuitry is configured to:

determine that a next-hop of the route for forwarding the packets of the reverse packet flow is associated with the second candidate interface.

8. The router of claim 1 , wherein to determine that the router stores the valid route for forwarding packets of the reverse packet flow via the second candidate interface, the processing circuitry is configured to:

determine that a routing information base (RIB) of the router stores a valid route for forwarding the packets of the reverse packet flow via the second candidate interface; and

determine that a next-hop of the route for forwarding the packets of the reverse packet flow is associated with the second candidate interface.

9. A method comprising:

receiving, by a router via an interface of the router, a packet of a forward packet flow;

determining, by the router, that the router does not store a valid route for forwarding packets of a reverse packet flow for the forward packet flow via a first candidate interface;

based at least in part on determining that the router does not store the valid route for forwarding packets of the reverse packet flow via the first candidate interface, determining, by the router, that the router stores a valid route for forwarding packets of the reverse packet flow via a second candidate interface; and

based at least in part on determining that the router stores a valid route for forwarding packets of the reverse packet flow via the second candidate interface, establishing, by the router, a stateful routing session using the second candidate interface for the reverse packet flow.

10. The method of claim 9 , wherein method further comprises:

receiving, by the router, a packet of the reverse packet flow; and

forwarding, by the router and via the second candidate interface, the packet of the reverse packet flow.

11. The method of claim 9 , wherein establishing the stateful routing session comprises:

modifying the packet to include metadata specifying a session identifier for the stateful routing session; and

forwarding, to a next-hop for the forward packet flow, the modified packet.

12. The method of claim 9 , wherein the interface and the second candidate interface are the same interface.

13. The method of claim 9 , wherein the interface and the second candidate interface are different interfaces.

14. The method of claim 9 , wherein determining that the router stores the valid route for forwarding packets of the reverse packet flow via the second candidate interface comprises:

determining that a routing information base (RIB) of the router stores a valid route for forwarding the packets of the reverse packet flow via the second candidate interface.

15. The method of claim 9 , wherein determining that the router stores the valid route for forwarding packets of the reverse packet flow via the second candidate interface comprises:

determining that a next-hop of the route for forwarding the packets of the reverse packet flow is associated with the second candidate interface.

16. Non-transitory, computer-readable media comprising instructions that, when executed, are configured to cause processing circuitry of a router to:

receive, via an interface of the router, a packet of a forward packet flow;

determine that the router does not store a valid route for forwarding packets of a reverse packet flow for the forward packet flow via a first candidate interface;

based at least in part on determining that the router does not store the valid route for forwarding packets of the reverse packet flow via the first candidate interface, determine that the router stores a valid route for forwarding packets of the reverse packet flow via a second candidate interface; and

based at least in part on determining that the router stores a valid route for forwarding packets of the reverse packet flow via the second candidate interface, establish a stateful routing session using the second candidate interface for the reverse packet flow.

17. The computer-readable media of claim 16 , wherein the instructions are further configured to cause the processing circuitry to:

receive a packet of the reverse packet flow; and

forward, via the second candidate interface, the packet of the reverse packet flow.

18. The computer-readable media of claim 16 , wherein to establish the stateful routing session, the instructions are configured to cause the processing circuitry to:

modify the packet to include metadata specifying a session identifier for the stateful routing session; and

forward, to a next-hop for the forward packet flow, the modified packet.

Assignments (2)
NUNC PRO TUNC ASSIGNMENT Recorded May 6, 2026
From: 128 TECHNOLOGY, INC.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 075513/0087 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2025
From: MENON, ABILASH; PENFIELD, ROBERT; KAPLAN, HADRIEL S.
To: 128 TECHNOLOGY, INC.
Reel/Frame 071772/0697 →
Continuity (3)
Continuation 17305985 · Jul 19, 2021
Continuation 15169003 · May 31, 2016
Related Publication 20230327984A1 · Oct 12, 2023
References Cited (186)
US 6515963B1 · Bechtolsheim et al. · 2003 [cited by applicant]
US 6563824B1 · Bhatia et al. · 2003 [cited by applicant]
US 6584071B1 · Kodialam et al. · 2003 [cited by applicant]
US 6721334B1 · Ketcham · 2004 [cited by applicant]
US 6738387B1 · Lin et al. · 2004 [cited by applicant]
US 6778531B1 · Kodialam et al. · 2004 [cited by applicant]
US 6798743B1 · Ma et al. · 2004 [cited by applicant]
US 7020143B2 · Zdan · 2006 [cited by applicant]
US 7035214B1 · Seddigh et al. · 2006 [cited by applicant]
US 7106739B2 · Beier · 2006 [cited by applicant]
US 7154902B1 · Sikdar · 2006 [cited by applicant]
US 7218632B1 · Bechtolsheim et al. · 2007 [cited by applicant]
US 7315541B1 · Housel et al. · 2008 [cited by applicant]
US 7373660B1 · Guichard et al. · 2008 [cited by applicant]
US 7466703B1 · Arunachalam et al. · 2008 [cited by applicant]
US 7492713B1 · Turner et al. · 2009 [cited by applicant]
US 7536720B2 · Burdett et al. · 2009 [cited by applicant]
US 7634805B2 · Aroya · 2009 [cited by applicant]
US 7706411B2 · Wakumoto et al. · 2010 [cited by applicant]
US 7730301B2 · Correll et al. · 2010 [cited by applicant]
US 7773611B2 · Booth, III et al. · 2010 [cited by applicant]
US 7872973B2 · Sterne et al. · 2011 [cited by applicant]
US 7949785B2 · Alkhatib et al. · 2011 [cited by applicant]
US 8068417B1 · Roberts · 2011 [cited by applicant]
US 8094560B2 · Bagepalli et al. · 2012 [cited by applicant]
US 8139479B1 · Raszuk · 2012 [cited by applicant]
US 8316435B1 · Varadhan · 2012 [cited by examiner]
US RE44119E · Wang et al. · 2013 [cited by applicant]
US 8437248B2 · Li et al. · 2013 [cited by applicant]
US 8527641B2 · Degaonkar et al. · 2013 [cited by applicant]
US 8570893B2 · Guo et al. · 2013 [cited by applicant]
US 8584199B1 · Chen et al. · 2013 [cited by applicant]
US 8634428B2 · Le Pennec et al. · 2014 [cited by applicant]
US 8699373B1 · Pani · 2014 [cited by applicant]
US 8705524B1 · Kelly et al. · 2014 [cited by applicant]
US 8804489B2 · Lu et al. · 2014 [cited by applicant]
US 8942085B1 · Pani et al. · 2015 [cited by applicant]
US 8989020B2 · So · 2015 [cited by applicant]
US 9059920B2 · Ravindran et al. · 2015 [cited by applicant]
US 9160652B2 · Taillon et al. · 2015 [cited by applicant]
US 9240953B2 · Carlstrom · 2016 [cited by applicant]
US 9246800B1 · Ramamoorthi et al. · 2016 [cited by applicant]
US 9276864B1 · Vincent · 2016 [cited by applicant]
US 9729439B2 · MeLampy et al. · 2017 [cited by applicant]
US 9729682B2 · Kumar et al. · 2017 [cited by applicant]
US 9762485B2 · Kaplan et al. · 2017 [cited by applicant]
US 9871748B2 · Gosselin et al. · 2018 [cited by applicant]
US 9985883B2 · MeLampy et al. · 2018 [cited by applicant]
US 10200264B2 · Menon et al. · 2019 [cited by applicant]
US 10277506B2 · Timmons et al. · 2019 [cited by applicant]
US 10432522B2 · Kaplan et al. · 2019 [cited by applicant]
US 11075836B2 · Menon et al. · 2021 [cited by applicant]
US 20010030649A1 · Mamiya et al. · 2001 [cited by applicant]
US 20020044553A1 · Chakravorty · 2002 [cited by applicant]
US 20020075883A1 · Dell et al. · 2002 [cited by applicant]
US 20020176363A1 · Durinovic-Johri et al. · 2002 [cited by applicant]
US 20030198189A1 · Roberts et al. · 2003 [cited by applicant]
US 20030214938A1 · Jindal et al. · 2003 [cited by applicant]
US 20040004955A1 · Lewis · 2004 [cited by applicant]
US 20040088542A1 · Daude et al. · 2004 [cited by applicant]
US 20040264481A1 · Darling et al. · 2004 [cited by applicant]
US 20050036616A1 · Huang et al. · 2005 [cited by applicant]
US 20050063307A1 · Samuels et al. · 2005 [cited by applicant]
US 20050182932A1 · Wheeler · 2005 [cited by applicant]
US 20050238022A1 · Panigrahy · 2005 [cited by applicant]
US 20060146813A1 · Biswas et al. · 2006 [cited by applicant]
US 20060176894A1 · Oh et al. · 2006 [cited by applicant]
US 20070171825A1 · Roberts et al. · 2007 [cited by applicant]
US 20070171826A1 · Roberts et al. · 2007 [cited by applicant]
US 20070253418A1 · Shiri et al. · 2007 [cited by applicant]
US 20080159145A1 · Muthukrishnan et al. · 2008 [cited by applicant]
US 20080214175A1 · Papadoglou et al. · 2008 [cited by applicant]
US 20090007021A1 · Hayton · 2009 [cited by applicant]
US 20090059958A1 · Nakata · 2009 [cited by applicant]
US 20100125898A1 · Dubuc et al. · 2010 [cited by applicant]
US 20100191968A1 · Patil et al. · 2010 [cited by applicant]
US 20110007743A1 · Kuwahara et al. · 2011 [cited by applicant]
US 20110069714A1 · Le Pennec · 2011 [cited by examiner]
US 20110299554A1 · Ros-Giralt et al. · 2011 [cited by applicant]
US 20120144061A1 · Song · 2012 [cited by applicant]
US 20120236860A1 · Kompella et al. · 2012 [cited by applicant]
US 20130088994A1 · Guo et al. · 2013 [cited by applicant]
US 20130194971A1 · Montessoro · 2013 [cited by examiner]
US 20130227166A1 · Ravindran et al. · 2013 [cited by applicant]
US 20130229922A1 · Li et al. · 2013 [cited by applicant]
US 20130230051A1 · Lockwood · 2013 [cited by applicant]
US 20130297824A1 · Lan et al. · 2013 [cited by applicant]
US 20140040488A1 · Small et al. · 2014 [cited by applicant]
US 20150117454A1 · Koponen et al. · 2015 [cited by applicant]
US 20150188814A1 · Jain et al. · 2015 [cited by applicant]
US 20150215841A1 · Hsu et al. · 2015 [cited by applicant]
US 20150229618A1 · Wan et al. · 2015 [cited by applicant]
US 20150372898A1 · Haramaty et al. · 2015 [cited by applicant]
US 20150372916A1 · Haramaty et al. · 2015 [cited by applicant]
US 20150381324A1 · Mirsky et al. · 2015 [cited by applicant]
US 20160036694A1 · Abdul et al. · 2016 [cited by applicant]
US 20160094444A1 · MeLampy et al. · 2016 [cited by applicant]
US 20160105471A1 · Nunes et al. · 2016 [cited by applicant]
US 20160119089A1 · Zhang · 2016 [cited by applicant]
US 20160164780A1 · Timmons et al. · 2016 [cited by applicant]
US 20160269284A1 · Cheng et al. · 2016 [cited by applicant]
US 20160344565A1 · Batz et al. · 2016 [cited by applicant]
US 20160344715A1 · Kumar et al. · 2016 [cited by applicant]
US 20160344803A1 · Batz et al. · 2016 [cited by applicant]
US 20170063681A1 · Kaplan et al. · 2017 [cited by applicant]
US 20170063927A1 · Schultz et al. · 2017 [cited by applicant]
US 20170171110A1 · Gosselin et al. · 2017 [cited by applicant]
US 20170250906A1 · MeLampy et al. · 2017 [cited by applicant]
US 20210336878A1 · Vastholil · 2021 [cited by examiner]
US 20210344593A1 · Menon et al. · 2021 [cited by applicant]
US 20210409336A1 · Talur · 2021 [cited by examiner]
CN 101552703A · 2009 [cited by applicant]
CN 101646220A · 2010 [cited by applicant]
CN 101068242B · 2010 [cited by applicant]
CN 102158371A · 2011 [cited by applicant]
CN 102594600 · 2012 [cited by applicant]
CN 101640629B · 2012 [cited by applicant]
CN 102739507A · 2012 [cited by applicant]
CN 101207604B · 2013 [cited by applicant]
CN 102769679B · 2015 [cited by applicant]
CN 103179192B · 2015 [cited by applicant]
CN 105245469A · 2016 [cited by applicant]
EP 1418705 · 2006 [cited by applicant]
EP 1313267B1 · 2006 [cited by applicant]
EP 2339784 · 2011 [cited by applicant]
GB 1473898A · 1977 [cited by applicant]
KR 1020110062994A · 2011 [cited by applicant]
WO 2007084707A2 · 2007 [cited by applicant]
WO 2007084755A2 · 2007 [cited by applicant]
WO 2008043230A1 · 2008 [cited by applicant]
WO 2015131537A1 · 2015 [cited by applicant]
“A case for stateful forwarding plane”, Computer Communications, Elsevier, vol. 36, No. 7, pp. 779-791, Apr. 2013. [cited by applicant]
“Active queue management”, https://en.wikipedia.org/wiki/Active_queue_management, 2 pages, Apr. 22, 2015. [cited by applicant]
“Design, Implementation and Performance of a Content-Based Switch”, In INFOCOM 2000, Proceedings of the Nineteenth Annual Joint Conference of the IEEE Computer and Communications Societies, Tel Aviv, Israel, 10 pages, M… [cited by applicant]
“Internet Protocol,” Darpa Internet Program Protocol Specification, Information Sciences Institute, RFC 791, Sep. 1981, 51 pp. [cited by applicant]
“Network architecture for joint failure recovery and traffic engineering”, SIGMETRICS '11, Proceedings of the ACM SIGMETRICS Joint International Conference on Measurement and Modeling of Computer Systems, San Jose, CA, … [cited by applicant]
“Transmission Control Protocol,” Darpa Internet Program Protocol Specification, Information Sciences Institute, RFC 793, Sep. 1981, 91 pp. [cited by applicant]
1.2 Overview of a TCP communications session, RPG IV Socket Tutorial (http://www.scottklement.com/rug/socketut/overview), 2 pages, 2001. Applicant points out in accordance with MPEP 609.04(a) that the 2001 year of publi… [cited by applicant]
1Pv6 Segment Routing Header (SRH), Network Working Group, Draft, 24 pages, Jul. 3, 2014. [cited by applicant]
A Technique for Low Energy Mapping and Routing in Network-on-Chip Architectures, ISLPED '05 Proceedings of the 2005 International Symposium on Low Power Electronics and Design, 6 pages, Aug. 8-10, 2005. [cited by applicant]
A Unified Approach to Constrained Mapping and Routing on Network-on-Chip Architectures, CODES+ISSS '05 Proceedings of the 3rd IEEE/ACM/IFIP International Conference on Hardware/Software Codesign and System Synthesis, 6 … [cited by applicant]
Bidirectional Forwarding Detection (BFD), Internet Engineering Task Force (IETF), Request for Comments 5880, ISSN: 2070-1721, Juniper Networks, 49 pages, Jun. 2010. [cited by applicant]
Deering et al., “Internet Protocol, Version 6 (IPv6) Specification,” Network Working Group, RFC 2460, Dec. 1998, 39 pp. [cited by applicant]
Definition of TCP/IP abc's, PC Magazine Encyclopedia (www.pcmag.com/encyclopedia/term/52615), 5 pages, 2005. Applicant points out in accordance with MPEP 609.04(a) that the 2005 year of publication is sufficiently earli… [cited by applicant]
Equal-cost multi-path routing, 1 page, dated Sep. 12, 2013. [cited by applicant]
Functional Requirements for Uniform Resource Names, Network Working Group, Request for Comments 1737, 7 pages, Dec. 1994. [cited by applicant]
International Preliminary Report on Patentability from International Application No. PCT/US2017/032905, mailed Dec. 4, 2018, 4 pp. [cited by applicant]
International Search Report—International Application No. PCT/US2017/032478, dated Aug. 24, 2017, together with the Written Opinion of the International Searching Authority, 9 pages. [cited by applicant]
International Search Report—International Application No. PCT/US2017/032702, dated Aug. 17, 2017, together with the Written Opinion of the International Searching Authority, 8 pages. [cited by applicant]
International Search Report—International Application No. PCT/US2017/032907, dated Aug. 3, 2017, together with the Written Opinion of the International Searching Authority, 8 pages. [cited by applicant]
International Search Report—International Application No. PCT/US2017/032905, dated Sep. 3, 2017, together with the Written Opinion of the International Searching Authority, 9 pages. [cited by applicant]
International Search Report—Application No. PCT/US2016/026938, dated Jul. 28, 2016, together with the Written Opinion of the International Searching Authority, 9 pages. [cited by applicant]
International Search Report—International Application No. PCT/2015/044815, dated Dec. 6, 2015, together with the Written Opinion of the International Searching Authority, 8 pages. [cited by applicant]
International Search Report—International Application No. PCT/US2015/060840, dated Mar. 8, 2016, together with the Written Opinion of the International Searching Authority, 13 pages. [cited by applicant]
International Search Report—International Application No. PCT/US2016/013416, dated Jun. 8, 2016, together with the Written Opinion of the International Searching Authority, 12 pages. [cited by applicant]
Introduction to Receive Side Scaling, Developer Resources, https://msdn.microsoft.com/enus/library/windows/hardware/ff556942(v=vs.85).aspx, 3 pages, Apr. 2014. [cited by applicant]
LAN switching, 5 pages, dated Jun. 12, 2013. [cited by applicant]
Layer 3 Switches Explained, Happy Router, 6 pages, dated Aug. 30, 2007. [cited by applicant]
Making Better Use of All Those TCP ACK Packets, Computer Science Department, Worcester Polytechnic Institute, 10 pages, 2005. Applicant points out in accordance with MPEP 609.04(a) that the 2005 year of publication is s… [cited by applicant]
Management information base, 6 pages, dated Jul. 15, 2013. [cited by applicant]
Multi-queue network interfaces with SMP on Linux, Greenhost, https://greenhost.net/2013/04/10/multi-gueue-network- interfaces-with-smp-on-linux/, 5 pages, Apr. 10, 2013. [cited by applicant]
Network address translation, 11 pages, dated Sep. 24, 2013. [cited by applicant]
Network Functions Virtualisation—Introductory White Paper, Issue 1, at the “SDN and OpenFlow World Congress”, Darmstadt-Germany, (http://portal.etsi.org/nfv/nfv_white_paper), 16 pages, dated Oct. 22, 2012. [cited by applicant]
Network interface controller, https:/ /en.wikipedia.org/wiki/Network_interface_controller, 5 pages, May 19, 2015. [cited by applicant]
Network socket, 4 pages, dated Sep. 19, 2013. [cited by applicant]
Non-RSS Receive Processing, Developer Resources, https://msdn.microsoft.com/enus/library/windows/hardware/ff568798(v=vs.85).aspx, 2 pages, Jan. 2015. [cited by applicant]
Observing routing asymmetry in Internet traffic, (www.caida.org/research/traffic-analysis/asvmmetry/1 ), 7 pages, dated Jul. 17, 2013. [cited by applicant]
Open vSwitch, 2 pages, dated Nov. 24, 2013. [cited by applicant]
Parallel Express Forwarding on the Cisco 10000 Series, (White Paper) Cisco Systems, 4 pages, printed Jun. 17, 2015. [cited by applicant]
Postel, “ User Datagram Protocol,” RFC 768, Aug. 28, 1980, 3 pp. [cited by applicant]
Programmer's Guide, Release 16.04.0, 216 pages, Apr. 12, 2016. [cited by applicant]
Prosecution History from U.S. Appl. No. 15/169,003, dated Dec. 28, 2017 through Mar. 24, 2021, 160 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/305,985, dated Nov. 16, 2021 through Mar. 21, 2023, 19 pp. [cited by applicant]
Reverse path forwarding, 3 pages, dated Jul. 31, 2013. [cited by applicant]
Router (computing), 8 pages, dated Sep. 23, 2013. [cited by applicant]
RSS with a Single Hardware Receive Queue, Developer Resources, https://msdn.microsoft.com/enus/library/windows/hardware/ff570727(v=vs.85).aspx, 2 pages, Jan. 2015. [cited by applicant]
RSS with Hardware Queuing, Developer Resources, https://msdn.microsoft.com/enus/library/windows/hardware/ff570728(v=vs.85).aspx, 2 pages, Jan. 2015. [cited by applicant]
Segment Routing Architecture, Network Working Group, Draft, 28 pages, Oct. 21, 2013. [cited by applicant]
Software-defined networking, 6 pages, dated Sep. 16, 2013. [cited by applicant]
The Next Generation of IP-Flow Routing, SSGRR 2003S International Conference, L'Aquila, Italy, 11 pages, Jul. 29, 2003. [cited by applicant]
Transmission Control Protocol (TCP) Parameters, (www.iana.org/assignments/tcp-parameters/tcpparameters.xhtm), 5 pages, dated Sep. 22, 2014. [cited by applicant]
Transmission Control Protocol, 18 pages, dated Sep. 16, 2013. [cited by applicant]
Uniform Resource Identifier (URI): Generic Syntax, Network Working Group, Request for Comments 3986, The Internet Society, 61 pages, Jan. 2005. [cited by applicant]
What is routing table? Posted by Margaret Rouse (http://searchnetworking.techtarget.com/definition/routing-table), 5 pages, Apr. 2007. [cited by applicant]
Xps: Transmit Packet Steering, Eklektix, Inc., 11 pages, Oct. 26, 2010. [cited by applicant]
YANG—A Data Modeling Language for the Network Configuration Protocol (NETCONF), Internet Engineering Task Force (IETF), Request for Comments 6020, ISSN: 2070-1721, 173 pages, Oct. 2010. [cited by applicant]