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: "elmo source routed multicast for cloud services"
  Abstract: Modern data-center applications frequently exhibit one-to-many communication patterns and, at the same time, require the fabric to provide sub-millisecond latencies and high throughput. Native IP multicast can achieve these requirements. However, native IP multicast solutions have scalability limitations that make it challenging to offer it as a service for hundreds of thousands of tenants, typical of cloud environments. Tenants must, thus, either add custom support for multicast in their applications or rely on services like overlay multicast, both of which are unicast-based approaches that impose their own overhead on throughput and CPU utilization, leading to higher and unpredictable latencies. In this paper, we present Elmo, a mechanism for native multicast in switches which takes advantage of the unique characteristics of data-center topologies and workloads. Specifically, the symmetric topology and short paths in a data center and the tendency of virtual machines (VMs) from individual tenants to cluster in small portions of the topology. Elmo encodes multicast group information inside packets themselves, significantly reducing the need to store multicast group information in individual network switches. In a data-center topology with 27K hosts, Elmo supports a million multicast groups using a 325-byte packet header while requiring as few as 1.1K multicast flow-table entries on average in leaf switches with a traffic overhead as low as 5%.

Connected through hyperedge HE-1 (induced by source paper "scdp systematic rateless coding for efficient data transport in data centres"):
  with members:
    - "liquid cloud storage"
    - "dual structure data center multicast using software defined networking"
    - "repflow minimizing flow completion times with replicated flows in data centers"
    - "jellyfish networking data centers randomly"

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)