All,
Jim and I have updated the Automatic Prefix Delegation draft
to take into account comments and suggestions made in the last few
months. I submitted it to the I-D editor last week, but have not
seen it posted yet so it is attached. Comments and suggestions are
always welcome.
Brian
Individual Submission B. Haberman
Internet DraftJ. Martin
draft-haberman-ipngwg-auto-prefix-02.txt
February 2002
Expires August 2002
Automatic Prefix Delegation Protocol for
Internet Protocol Version 6 (IPv6)
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts. Internet-Drafts are draft documents valid for a maximum of
six months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet- Drafts
as reference material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
The expansion of the IP address space provided by IPv6 makes it both
possible and reasonable to allocate entire subnets to environments
that had been previously limited to a few individual IP addresses.
Other protocols such as Neighbor Discovery and Stateless Address
Autoconfiguration allow hosts within those subnets to be
automatically configured. The router between this subnet and the
upstream world requires just one more piece to make this process
automatic, a network prefix.
This document describes a mechanism for the automated delegation of
an IPv6 network prefix. It allows routers to request either a
specific prefix or any prefix. Upon authorizing the request the
delegating router then returns a prefix and a lifetime for the use
of the prefix. Optionally, the delegating and requesting routers
can exchange routing protocol information.
Haberman, Martin 1
Internet Draft February 2002
1. Introduction
This specification defines the Prefix Delegation (PD) protocol for
Internet Protocol Version 6 (IPv6). Routers use Prefix Delegation to
request a network prefix for use on directly attached networks.
Upon receipt of the request, the delegating router may authenticate
the request, and will establish if the requested prefix size is
acceptable. The delegating router then specifies the prefix for use
and the length of time for which that prefix is delegated.
The Prefix Delegation protocol supports extensible options. These
options may be used to negotiate additional operational parameters,
such as routing protocol information.
2. Terminology
2.1 General
This document uses the terminology defined in [RFC 2460] and [RFC
2461] and in addition:
- Requesting Router - The router that is requesting that a
prefix be assigned
- Delegating Router - The router that is responding to the
prefix request
2.2 Requirements
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 [RFC 2119].
3. Scope of Work
This proposal is meant to give a singly homed leaf router the
ability to obtain an IPv6 prefix that can be used within its leaf
network. Future revisions of this document may support a more
generic approach to dynamic prefix delegation.
It is also assumed that the delegating server/router shares a
network connection with the requesting router. Future revisions may
remove this restriction and allow for either multi-hop messages or a
relay function.
4. Protocol Overview
Haberman, Martin 2
Internet Draft February 2002
The Prefix Delegation protocol defines two new ICMP message types,
the Prefix Request and the Prefix Delegation. The Prefix Requ
