Getting attached...

[Jason Duerstock]

On Wed, 26 Feb 1997, Bob Fink LBNL wrote:

> Jason,
> 
> Then I would suggest using DIGITAL-CA, NRL or CISCO until more happens in
> the the southeast.

It seems CIC is the closest to me, so I'm going to try go get hooked up
through them.  

Now that I have my connecting point, according to the web page, the next
step is choosing my address.  According to the page...:

> The address format from RFC 1897 is extracted below for your convenience
> in understanding the email example:
>
>
>   | 3 |  5 bits  |  16 bits | 8 |   24 bits  | 8 | 16 bits|48 bits|
>   +---+----------+----------+---+------------+---+--------+-------+
>   |   |          |Autonomous|   |    IPv4    |   | Subnet | Intf. |
>   |010|  11111   |  System  |RES|   Network  |RES|        |       |
>   |   |          |  Number  |   |   Address  |   | Address|  ID   |
>   +---+----------+----------+---+------------+---+--------+-------+
>
> Note that an RFC1897 format address includes the ASN (Autonomous System
> Number) of one's provider, not an ASN that belongs to one's own site.
> (Though a provider uses its own ASN.)

This is would make my address

5F:  (01011111 == first 8 bits)
0D:  T
E9:  +- 3561 (for MCI's ASN)
00:  (RES == reserved...?)
CE:  206. \
9C:  156.  > our IPv4 class C subnet
94:  148. /
00:  (RES == reserved...)

This gives me the first 8 bytes, but I'm unsure as to what the subnet
address and interface ID means...it it safe to assume...:

00: T
01: +- 1 for first address on the subnet

and

00: T
00: |
00: |
00: |
00: |
01: +- interface #1

?

And for RIPE purposes, this would be come

5F0D:E900:CE9C:9400/64 ?

Assuming this is correct, should I register with RIPE first, or actually
try to get the tunnel up and running?

Thanks for the help and sorry about all the questions. :)

Jason Duerstock
jason@linux.aatech.com