human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "an efficient linux kernel implementation of service function chaining for legacy vnfs based on ipv6 segment routing"
  Abstract: We consider the IPv6 Segment Routing (SRv6) technology for Service Function Chaining of Virtual Network Functions (VNFs). Most of the VNFs are legacy VNFs (not aware of the SRv6 technology) and expect to process traditional IP packets. An SR proxy is needed to support them. We have extended the implementation of SRv6 in the Linux kernel, realizing an SR-proxy, referred to as SRNK (SR-Proxy Native Kernel). The performance of the proposed solution (SRNKv1) has been evaluated, identifying a poor scalability with respect to the number of VNFs to be supported in a node. Therefore we provided a second design (SRNKv2), enhancing the Linux Policy Routing framework. The performance of SRNKv2 is independent from the number of supported VNFs in a node. We compared the performance of SRNKv2 with a reference scenario not performing the encapsulation and decapsulation operation and demonstrated that the overhead of SRNKv2 is very small, on the order of 3.5%.

Connected through hyperedge HE-1 (induced by source paper "srperf a performance evaluation framework for ipv6 segment routing"):
  with members:
    - "segment routing a comprehensive survey of research activities standardization efforts and implementation results"
    - "implementation of virtual network function chaining through segment routing in a linux based nfv infrastructure"
    - "traffic engineering with segment routing sdn based architectural design and open source implementation"

Connected through hyperedge HE-2 (induced by source paper "segment routing a comprehensive survey of research activities standardization efforts and implementation results"):
  with members:
    - "srperf a performance evaluation framework for ipv6 segment routing"
    - "node constrained traffic engineering theory and applications"
    - "sdn architecture and southbound apis for ipv6 segment routing enabled wide area networks"
    - "flexible failure detection and fast reroute using ebpf and srv6"
    - "leveraging ebpf for programmable network functions with ipv6 segment routing"
    - "centrality based middlepoint selection for traffic engineering with segment routing"
    - "implementation of virtual network function chaining through segment routing in a linux based nfv infrastructure"
    - "control exchange points providing qos enabled end to end services via sdn based inter domain routing orchestration"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.NI(Networking and Internet Architecture)