Route Problem at Relay during DHCPv6 Prefix Delegation
draft-petrescu-relay-route-pd-problem-00

Document Type Expired Internet-Draft (individual)
Authors Mohamed Boucadair  , Leaf Yeh  , Alexandre Petrescu 
Last updated 2014-04-24 (latest revision 2013-10-21)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-petrescu-relay-route-pd-problem-00.txt

Abstract

The operation of a prefix delegation procedure with the DHCPv6 protocol may need route setup and maintenance at the Delegating Router, Requesting Router and on the entity on which the Relay agent is implemented. This document describes the problem of routing during DHCPv6 prefix delegation, and is illustrated by ADSL-type and cellular-type of topologies which may use Relays; we refer to section 14 of RFC 3633 which mentions the need of 'a protocol or other out of band communication to add routing information for delegated prefixes'. Based on this problem, a number of requirements from the service providers are described. A small set of documented solutions are separately mentioned (snooping, route injection, etc.), together with their pros and cons according to a particular judgment.

Authors

Mohamed Boucadair (mohamed.boucadair@orange.com)
Leaf Yeh (leaf.yeh.sdo@gmail.com)
Alexandre Petrescu (alexandru.petrescu@cea.fr)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)