human: Given a hyperedge-centered hypergraph: <hypergraph>, where the center hyperedge is induced by one source paper and its member nodes are the cited papers.

Details of the hypergraph:
Center hyperedge (induced by source paper "tiny buffer tcp for data center networks"):
  Abstract: A low and stable buffer occupancy is critical to achieve high throughput, low packet drop rate, low latency, and low jitter for data center networks. It also allows switch chips to support higher port density, larger lookup tables, or richer functions. Tiny Buffer TCP creatively uses the common RED-based ECN with two novel congestion-window adjustment schemes to significantly reduce the required buffer size. Aiming to eliminate the residual packets in the bottleneck queue, Queue Canceling Decrease amortizes the ideal window reduction to the same number of flows so as to minimize the impact to active flows. In order to keep the buffer occupancy low and stable, Reduced Additive Increase recovers the flow window at a slower pace than normal. We implemented TBTCP in Linux kernel and conducted ns2-based simulations and real network-based tests. Our results show that compared to DCTCP, TBTCP reduces the switch buffer requirement by more than 80%, increases the bandwidth utilization by up to 15%, improves the FCT performance by up to 39%, and achieve a 71% better RTT fairness index.

Includes members:
  Member "homa a receiver driven low latency transport protocol using network priorities":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "a survey on recent advances in transport layer protocols")
  Member "pcc re architecting congestion control for consistent high performance":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "taurus an intelligent data plane")
  Member "finishing flows quickly with preemptive scheduling":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "to schedule or not to schedule when no scheduling can beat the best known flow scheduling algorithm in datacenter networks")

Question: Please tell me which class the source paper 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)