Document Managed by Network Architecture

Introduction

This document details how OSPF area ID's are to be selected for use in Rutgers University's data network. This design applies to both the RUNet2 and RUNet2000 networks. ID's for RUNet2000 areas must be specifically selected from the tables included in this document. ID's for RUNet2 areas may be chosen in any arbitrary manner within the constraints placed on them below.

RUNet2000 area ID's will take the canonical dotted quad form used almost everywhere except Rutgers. The octets will encode useful topological information. RUNet2 area ID's will often be presented in their historical decimal representation, though many tools will only display the dotted-quad equivalent.

2. Area ID Composition

RUNet area ID's are representable as a standard internet dotted-quad. This representation can be decomposed into four segments which each have their own interpretation.

2.1. Octet interpretations

MAN_ID . MINOR_CAMPUS . CORE_TREE . USE/SUB_TREE

2.1.1. MAN_ID

Metropolitan Area Network IDentifier

This octet indicates which geographical major campus or remote location contains the OSPF area.

2.1.1.1. Reserved Encodings

MAN_ID 0 is reserved OSPF areas associated with RUNet2.

MAN_ID 255 is reserved for the university wide services network.

2.1.2. MINOR_CAMPUS

This octet indicates which geographical minor campus or portion of a remote locations contains the OSPF area. The encodings are MAN_ID specific.

2.1.2.1. Reserved Encodings

MINOR_CAMPUS 0 is reserved for compatibility with RUNet2.

MINOR_CAMPUS 255 is reserved for service networks in each MAN.

2.1.3. CORE_TREE

This octet indicates which core device (labeled by building name) the OSPF area is attached to. The encodings are MINOR_CAMPUS specific.

2.1.3.1. Reserved Encodings

CORE_TREE 0 is reserved on RUNet and open for any assignment except 255 on RUNet2.

CORE_TREE 255 is reserved for distribution tree service networks on RUNet.

2.1.4. SUB_TREE

This octet indicates what sub-tree attached to a core device the OSPF area belongs to. Normally this will be 1 as it is not envisioned the network will need to be subdivided to this level.

2.1.4.1. Reserved Encodings

SUB_TREE 0 is reserved on RUNet and available for assignment on RUNet2.

SUB_TREE 255 is reserved on RUNet for distribution tree service networks on RUNet and available for assignment on RUNet2.

3. Area ID Assignments

The following sections detail the current OSPF area id assignments for potential RUNet network locations.

3.1. MAN Assignments

3.1.1. Area 1.x.x.x (Camden)

3.1.2. Area 2.x.x.x (New Brunswick)

3.1.3. Area 3.x.x.x (Newark)

4. OSPF Backbone Area ID's

The backbone is always 0.0.0.0. As we are running a separate OSPF network for RUnet and RUNet2 there will be two backbones with area ID's of 0. There is no way around this so where possible IP address space for each backbone should be selected from different address ranges. With this method you would be able to tell which network (RUNet 2 or RUNet) that backbone address belonged to. This should be considered as backbone address space is assigned.