Access-Network-Identifier Option in DHCP
draft-ietf-dhc-access-network-identifier-01

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2013-10-21
Replaces draft-bhandari-dhc-access-network-identifier
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
dhc                                                          S. Bhandari
Internet-Draft                                             S. Gundavelli
Intended status: Standards Track                           Cisco Systems
Expires: April 23, 2014                                      J. Korhonen
                                                 Broadcom Communications
                                                              M. Grayson
                                                           Cisco Systems
                                                        October 20, 2013

                Access-Network-Identifier Option in DHCP
              draft-ietf-dhc-access-network-identifier-01

Abstract

   This document specifies the format and mechanism for encoding access
   network identifiers in DHCPv4 and DHCPv6 messages by defining new
   access network identifier options and sub-options.

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 April 23, 2014.

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

Bhandari, et al.         Expires April 23, 2014                 [Page 1]
Internet-Draft           DHCPv4 & v6 ANI options            October 2013

   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Motivation . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  DHCPv4 Access-Network-Identifier Option  . . . . . . . . . . .  5
     4.1.  DHCPv4 Access-Network-Identifier Sub-options . . . . . . .  5
   5.  DHCPv6 Access-Network-Identifier options . . . . . . . . . . .  6
   6.  DHCPv4 and DHCPv6 Access-Network-Identifier Options  . . . . .  6
     6.1.  Access-Network-Type option . . . . . . . . . . . . . . . .  6
     6.2.  Network-Identifier options . . . . . . . . . . . . . . . .  8
     6.3.  Operator identifier options  . . . . . . . . . . . . . . . 11
   7.  Client Behavior  . . . . . . . . . . . . . . . . . . . . . . . 13
   8.  Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 14
   9.  Server Behavior  . . . . . . . . . . . . . . . . . . . . . . . 14
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 15
   12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
   13. Change log . . . . . . . . . . . . . . . . . . . . . . . . . . 15
   14. Normative References . . . . . . . . . . . . . . . . . . . . . 15
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16

Bhandari, et al.         Expires April 23, 2014                 [Page 2]
Internet-Draft           DHCPv4 & v6 ANI options            October 2013

1.  Introduction

   Access network identification of a network device has a range of
   application.  For e.g.  The local mobility anchor in a Proxy Mobile
   IPv6 domain is able to provide access network and access operator
   specific handling or policing of the mobile node traffic using
   information about the access network to which the mobile node is
   attached.

   This document specifies Dynamic Host Configuration Protocol v4
   (DHCPv4) [RFC2131] and Dynamic Host Configuration Protocol v6
   (DHCPv6) [RFC3315] options for access network identification that is
   added by Client or Relay agent in the DHCPv4 or DHCPv6 messages
   towards the Server.

   Dynamic Host Configuration Protocol (DHCP) client or DHCP relay agent
Show full document text