Browse Prior Art Database

IPv6 Testing Address Allocation (RFC2471)

IP.com Disclosure Number: IPCOM000003051D
Original Publication Date: 1998-Dec-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 4 page(s) / 7K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Hinden: AUTHOR [+3]

Abstract

This document describes an allocation plan for IPv6 addresses to be used in testing IPv6 prototype software. These addresses are temporary and will be reclaimed in the future. Any IPv6 system using these addresses will have to renumber at some time in the future. These addresses will not to be routable in the Internet other than for IPv6 testing.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 37% of the total text.

Network Working Group R. Hinden

Request for Comments: 2471 Nokia

Obsoletes: 1897 R. Fink

Category: Experimental LBNL

J. Postel

ISI

December 1998

IPv6 Testing Address Allocation

Status of this Memo

This memo defines an Experimental Protocol for the Internet

community. It does not specify an Internet standard of any kind.

Discussion and suggestions for improvement are requested.

Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

1.0 Introduction

This document describes an allocation plan for IPv6 addresses to be

used in testing IPv6 prototype software. These addresses are

temporary and will be reclaimed in the future. Any IPv6 system using

these addresses will have to renumber at some time in the future.

These addresses will not to be routable in the Internet other than

for IPv6 testing.

The address format for the IPv6 test address is consistent with the

"Aggregatable Global Unicast Address Allocation" [AGGR] and "TLA and

NLA Assignment Rules" [TLAASN].

This document is intended to replace RFC 1897 "IPv6 Testing Address

Allocation", January 1996. RFC 1897 will become historic.

The addresses described in this document are consistent with the IPv6

Addressing Architecture [ARCH]. They may be assigned to nodes

manually, with IPv6 Auto Address Allocation [AUTO], or with DHCP for

IPv6 [DHCPv6].

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

document are to be interpreted as described in [RFC2119].

2.0 Address Format

The Aggregatable Global Unicast Address Allocation format defined in

[AGGR] is as follows:

| 3 | 13 | 32 | 16 | 64 bits |

+---+-----+-----------+--------+--------------------------------+

|FP | TLA | NLA ID | SLA ID | Interface ID |

| | ID | | | |

+---+-----+-----------+--------+--------------------------------+

where:

FP = 001 = Format Prefix

This is the Format Prefix used to identify aggregatable

global unicast addresses.

TLA = 0x1FFE = Top-Level Aggregation Identifier

...