Jeff Doyle


Upcoming Events

Where the Cloud Touches Down: Simplifying Data Center Infrastructure Management

Thursday, July 25, 2013
10:00 AM PT/1:00 PM ET

In most data centers, DCIM rests on a shaky foundation of manual record keeping and scattered documentation. OpManager replaces data center documentation with a single repository for data, QRCodes for asset tracking, accurate 3D mapping of asset locations, and a configuration management database (CMDB). In this webcast, sponsored by ManageEngine, you will see how a real-world datacenter mapping stored in racktables gets imported into OpManager, which then provides a 3D visualization of where assets actually are. You'll also see how the QR Code generator helps you make the link between real assets and the monitoring world, and how the layered CMDB provides a single point of view for all your configuration data.

Register Now!

A Network Computing Webinar:
SDN First Steps

Thursday, August 8, 2013
11:00 AM PT / 2:00 PM ET

This webinar will help attendees understand the overall concept of SDN and its benefits, describe the different conceptual approaches to SDN, and examine the various technologies, both proprietary and open source, that are emerging. It will also help users decide whether SDN makes sense in their environment, and outline the first steps IT can take for testing SDN technologies.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

See more from this blogger

The Fear And Loathing Of /64s On Point-To-Point Links

I discussed in a previous article the necessity of abandoning IPv4 thinking when creating IPv6 address designs, and how our deeply ingrained need to conserve addresses can muddle our thinking. Nowhere does this conservative aversion to address waste snarl at us as menacingly as when we consider – completely compliant with the recommendations of ARIN and other RIRs – assigning /64 subnets to point-to-point links.

"You want me to allot a subnet with 18 million trillion addresses to a link that will only ever use two of them? Are you kidding me?" We know all the arguments for what we get in exchange for squander: Easier address management with one-size-fits-all subnets; simpler address interpretation; scaling; flexibility.

But still. Only using two addresses out of 18 million trillion? (Saying "million trillion" is a lot of fun if you imitate Carl Sagan’s voice.) Well, ask yourself when a /64 is acceptable.

Most people would say they can accept it on a regular LAN or VLAN segment. All righty then. To be fair, let’s take a really big LAN. Say, 5000 devices. Is a /64 acceptable there? Yes, you say? So we’re wasting (1.8 x 1019) – 5000 addresses instead of (1.8 x 1019) – 2 addresses. The difference between 5000 and 2 relative to 18 million trillion is miniscule. It diminishes to practically nothing. If it were any smaller it would be the amount I’m being paid to write this.

And yet a /64 on a LAN is acceptable and a /64 on a point-to-point link is not. IPv4 thinking can twist our reason. All of this does not mean there are not reasons to use a prefix other than /64 on point-to-point links – it only means address waste is not one of them. In fact, there are dueling RFCs on the topic.

RFC 3627 makes its case right in the title: "Use of /127 Prefix Length Between Routers Considered Harmful." The central argument in the document, however, is not as striking as the title suggests. Here it is:

  • When you use a /127 prefix on a point-to-point link, you have exactly two addresses available: PREFIX::0/127 and PREFIX::1/127. The problem the RFC cites is that the router being assigned PREFIX::1/127 might add the Subnet-Router Anycast address, which would be PREFIX::0/127. Then the router on the other end of the link, configured with PREFIX::0/127 will fail the Duplicate Address Detection test.


    Page:  1 | 2345  | Next Page »


    Related Reading


    More Insights


  • Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

     
    Disqus Tips To upload an avatar photo, first complete your Disqus profile. | Please read our commenting policy.
     
    Vendor Comparisons
    Network Computing’s Vendor Comparisons provide extensive details on products and services, including downloadable feature matrices. Our categories include:

    Next Gen Network Reports

    Research and Reports

    Network Computing: April 2013



    TechWeb Careers