Access-Network-Identifer Option in DHCP
draft-bhandari-dhc-access-network-identifier-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-08-22
Replaced by draft-ietf-dhc-access-network-identifier, rfc7839
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        S. Bhandari
Internet-Draft                                             S. Gundavelli
Intended status: Standards Track                           Cisco Systems
Expires: February 23, 2013                                   J. Korhonen
                                                  Nokia Siemens Networks
                                                              M. Grayson
                                                                   Cisco
                                                         August 22, 2012

                Access-Network-Identifer Option in DHCP
            draft-bhandari-dhc-access-network-identifier-01

Abstract

   This document specifies the format and mechanism that is to be used
   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 February 23, 2013.

Copyright Notice

   Copyright (c) 2012 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 February 23, 2013               [Page 1]
Internet-Draft           DHCPv4 & v6 ANI options             August 2012

   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 option  . . . . . . . . . . . . . . . .  8
     6.3.  Operator-Identifier option . . . . . . . . . . . . . . . .  9
   7.  Client Behavior  . . . . . . . . . . . . . . . . . . . . . . . 11
   8.  Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 11
   9.  Server Behavior  . . . . . . . . . . . . . . . . . . . . . . . 11
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
     10.1. DHCPv4 Access-Network-Identifier Sub-option registry . . . 12
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
   13. Change log . . . . . . . . . . . . . . . . . . . . . . . . . . 13
   14. Normative References . . . . . . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14

Bhandari, et al.        Expires February 23, 2013               [Page 2]
Internet-Draft           DHCPv4 & v6 ANI options             August 2012

1.  Introduction

   Access network idenfication of a network device has a range of
   application.  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
Show full document text