CIDR and Classful Routing

Rekhter, Y.

doi:10.17487/rfc1817

Cited by 8 publications

(5 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…While sound in theory (according to "CIDR and Classful Routing" [24]), it didn't work in practice. Because today's Internet is bifurcated into commercial/commodity networks and research/education networks (Internet2's Abilene), some institutions connected to both types employ creative routing policies.…”

Section: Service Provider Isink Case Studymentioning

confidence: 99%

On the Design and Use of Internet Sinks for Network Abuse Monitoring

Yegneswaran

Barford

Plonka

2004

Lecture Notes in Computer Science

125

View full text Add to dashboard Cite

Abstract.Monitoring unused or dark IP addresses offers opportunities to significantly improve and expand knowledge of abuse activity without many of the problems associated with typical network intrusion detection and firewall systems. In this paper, we address the problem of designing and deploying a system for monitoring large unused address spaces such as class A telescopes with 16M IP addresses. We describe the architecture and implementation of the Internet Sink (iSink) system which measures packet traffic on unused IP addresses in an efficient, extensible and scalable fashion. In contrast to traditional intrusion detection systems or firewalls, iSink includes an active component that generates response packets to incoming traffic. This gives the iSink an important advantage in discriminating between different types of attacks (through examination of the response payloads). The key feature of iSink's design that distinguishes it from other unused address space monitors is that its active response component is stateless and thus highly scalable. We report performance results of our iSink implementation in both controlled laboratory experiments and from a case study of a live deployment. Our results demonstrate the efficiency and scalability of our implementation as well as the important perspective on abuse activity that is afforded by its use.

show abstract

Section: Service Provider Isink Case Studymentioning

confidence: 99%

On the Design and Use of Internet Sinks for Network Abuse Monitoring

Yegneswaran

Barford

Plonka

2004

Lecture Notes in Computer Science

125

View full text Add to dashboard Cite

show abstract

“…Furthermore setting up a cut-through VC may be unnecessary and even undesirable for certain short-lived flows where it would be hard to justify the associated overhead 4 of the end-to-end connection and its setup, especially for flows that make no assumptions about QoS anyway. These issues are covered in more detail in [22] which suggests assigning responsibility for the VC cut-through decision to the sending application. Based on findings in [14] the majority of flows would not be suitable for VC cutthrough and so would continue to be forwarded in a connectionless hop-byhop manner over the default VCs as shown in Figure 2.…”

Section: Nhrpmentioning

confidence: 99%

ATM switching and IP routing integration: the next stage in Internet evolution?

White

1998

IEEE Commun. Mag.

View full text Add to dashboard Cite

User demand for more bandwidth and QoS support has fuelled interest in the use of ATM as an underlying link-layer technology in the Internet. The challenge is how best to exploit the potential benefits of ATM while maintaining the inherent strengths of the IP layer that have made the Internet so successful. The suitability of various schemes with regard to meeting these goals is described. In particular we focus on recent work that tightly integrates the IP and ATM layers to produce hybrid(or integrated) ATM switch/ IP routers with very favourable characteristics.

show abstract

“…This, in practical business terms, requires mid-level providers and users to adhere to a restrictive policy with regard to IP address space allocation, ownership, and portability [25,[27][28][29][30][31]. The above statement is no longer true with provider-based CIDR because arbitrary interconnections are restricted and actively discouraged.…”

Section: Bgp-4 and Classless Inferdomain Roufingmentioning

confidence: 99%

Internet exterior routing protocol development: problems, issues, and misconceptions

Bass¹

1997

IEEE Network

View full text Add to dashboard Cite

G l o b a l routing in the Internet continues to have scalability problems which underscore weaknesses in the design and implementation of the various TCP/IP exterior routing protocols. T h i s article explores the historical design a n d development relative to the decision-making process i n the specification and implementation of Internet external routing protocols, in particular discussing problems associated with provider-based address space allocation.his interim solution in no way constrains the selection of the next generation addressing and routing technology. '' -RFC 1367, October 1992 (1J In 1977 published a detailed discussion of hierarchical routing in large internetworks. In their landmark paper, "Hierarchical Routing for Large Networks," they discussed the problems associated with scalability and the length of the route forwarding table in large packet-switched networks. They concluded that hierarchical routing was a requirement €or very large lidworks. Routing tables require less information for destination networks far from the source relative to hop count or another nearness metric. Detailed routing information, one entry per destination, is required for near nodes. The construction of logical sets in the routing hierarchy is not related to geographical distances. Instead, administrative clustering of routing domains becomes the technical basis for designing large scalable internetworks.Problems and issues with scalability in packet-switched networks were well documented prior to 1982, the publication date of Rosen's Internet Request for Comment, "Exterior Gateway Protocol" (EGP) [3]. In this publication, Rosen discussed hierarchical routing and the limitations of EGP clearly and concisely, cautioning the reader that EGP did not "constitute a network routing algorithm." Unable to predict the explosive growth of the Internet, the National Science Foundation (NSF), Internet Engineering Task Force (IEW), Internet Activities Board (IAB), Internet Protocol (IP) service providers, and router vendors embarked on a development track redesigning EGP in favor of the Border Gateway Protocol (BGP). Policy-based routing dominated requirements for global scalability in large packet switched networks.Further inspection confirms that the early IP exterior routing protocol development track by Internet developers and router vendors was dominated by concerns about policy-based routing [4-61. It was not until 1992 that the engineering focus in the IBI'F apparently began to shift from policy-based routing to global network scalability [7-91.A short synopsis of IP exterior routing protocol development is presented in the next section, highlighting EGP, BGP, and policy-based routing in the Internet. The section after that introduces the paradigm shift from a concentration on policy-based routing to an emphasis on global IP scalability. The focus then returns to the BGP-34BGP-4 paradigm shift associated with classless inteidoiiiaiii routing (CIDR). Impoitant quotations in the Internet Requests for Comments (RFCs) ar...

show abstract

CIDR and Classful Routing

Abstract: CIDR and Classful Routing Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Cited by 8 publications

References 0 publications

On the Design and Use of Internet Sinks for Network Abuse Monitoring

On the Design and Use of Internet Sinks for Network Abuse Monitoring

ATM switching and IP routing integration: the next stage in Internet evolution?

Internet exterior routing protocol development: problems, issues, and misconceptions

Contact Info

Product

Resources

About