DHCP Options for the Port Control Protocol (PCP)
draft-ietf-pcp-dhcp-07

The information below is for an old version of the document
Document Type Active Internet-Draft (pcp WG)
Last updated 2013-03-27
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
PCP Working Group                                           M. Boucadair
Internet-Draft                                            France Telecom
Intended status: Standards Track                                R. Penno
Expires: September 28, 2013                                      D. Wing
                                                                   Cisco
                                                          March 27, 2013

            DHCP Options for the Port Control Protocol (PCP)
                         draft-ietf-pcp-dhcp-07

Abstract

   This document specifies DHCP (IPv4 and IPv6) options to configure
   hosts with Port Control Protocol (PCP) Server names.  The use of
   DHCPv4 or DHCPv6 depends on the PCP deployment scenario.

Requirements Language

   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 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on September 28, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of

Boucadair, et al.      Expires September 28, 2013               [Page 1]
Internet-Draft              PCP DHCP Options                  March 2013

   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  DHCPv6 PCP Server Option  . . . . . . . . . . . . . . . . . .   3
     3.1.  Format  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Client Behavior . . . . . . . . . . . . . . . . . . . . .   4
   4.  DHCPv4 PCP Option . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Format  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Client Behavior . . . . . . . . . . . . . . . . . . . . .   5
   5.  Use of PCP Server Names . . . . . . . . . . . . . . . . . . .   5
   6.  Dual-Stack Hosts  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Guidance to Administrators  . . . . . . . . . . . . . . . . .   5
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  DHCPv6 Option . . . . . . . . . . . . . . . . . . . . . .   6
     9.2.  DHCPv4 Option . . . . . . . . . . . . . . . . . . . . . .   6
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     11.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Appendix A.  Rationale  . . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   This document defines DHCPv4 [RFC2131] and DHCPv6 [RFC3315] options
   which can be used to provision PCP Server [I-D.ietf-pcp-base] names.
   Motivations for not expressing the PCP option as a 32 or 128-bit
   binary address are discussed in Appendix A.

   In order to make use of these options, this document assumes
   appropriate name resolution means (e.g., Section 6.1.1 of [RFC1123])
   are available on the host client.

   The use of DHCPv4 or DHCPv6 depends on the PCP deployment scenarios.

2.  Terminology

   This document makes use of the following terms:
Show full document text