RFC 7839 - Access-Network-Identifier Option in DHCP


Document	Type	RFC - Proposed Standard (June 2016; No errata) Was draft-ietf-dhc-access-network-identifier (dhc WG)
	Last updated	2016-06-15
	Replaces	draft-bhandari-dhc-access-network-identifier
	Stream	IETF
	Formats	plain text pdf html bibtex
	Reviews	GENART Telechat Review (of -10): Ready GENART Last Call Review (of -08): Ready OPSDIR Last Call Review (of -08): Has Issues SECDIR Last Call Review (of -08): Has Issues
Stream	WG state	Submitted to IESG for Publication (wg milestones: Dec 2014 - WG last call on acce..., Apr 2015 - Submit access-networ... )
	Document shepherd	Sheng Jiang
	Shepherd write-up	Show (last changed 2015-09-16)
IESG	IESG state	RFC 7839 (Proposed Standard)
	Consensus Boilerplate	Yes
	Telechat date
	Responsible AD	Brian Haberman
	Send notices to	(None)
IANA	IANA review state	Version Changed - Review Needed
	IANA action state	RFC-Ed-Ack

Email authors IPR References Referenced by Nits

Internet Engineering Task Force (IETF)                       S. Bhandari
Request for Comments: 7839                                 S. Gundavelli
Category: Standards Track                                     M. Grayson
ISSN: 2070-1721                                                  B. Volz
                                                           Cisco Systems
                                                             J. Korhonen
                                                        Broadcom Limited
                                                               June 2016

                Access-Network-Identifier Option in DHCP

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7839.

Copyright Notice

   Copyright (c) 2016 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
   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.

Bhandari, et al.             Standards Track                    [Page 1]
RFC 7839            ANI Options for DHCPv4 and DHCPv6          June 2016

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
     4.2.  DHCPv4 Access-Technology-Type Sub-option  . . . . . . . .   6
     4.3.  DHCPv4 Network-Identifier Sub-options . . . . . . . . . .   7
       4.3.1.  DHCPv4 Network-Name Sub-option  . . . . . . . . . . .   7
       4.3.2.  DHCPv4 Access-Point-Name Sub-option . . . . . . . . .   8
       4.3.3.  DHCPv4 Access-Point-BSSID Sub-option  . . . . . . . .   9
     4.4.  DHCPv4 Operator-Identifier Sub-options  . . . . . . . . .   9
       4.4.1.  DHCPv4 Operator-Identifier Sub-option . . . . . . . .   9
       4.4.2.  DHCPv4 Operator-Realm Sub-option  . . . . . . . . . .  10
   5.  DHCPv6 Access-Network-Identifier Options  . . . . . . . . . .  10
     5.1.  DHCPv6 Access-Technology-Type Option  . . . . . . . . . .  11
     5.2.  DHCPv6 Network-Identifier Options . . . . . . . . . . . .  11
       5.2.1.  DHCPv6 Network-Name Option  . . . . . . . . . . . . .  12
       5.2.2.  DHCPv6 Access-Point-Name Option . . . . . . . . . . .  12
       5.2.3.  DHCPv6 Access-Point-BSSID Option  . . . . . . . . . .  13
     5.3.  DHCPv6 Operator-Identifier Options  . . . . . . . . . . .  13
       5.3.1.  DHCPv6 Operator-Identifier Option . . . . . . . . . .  13
       5.3.2.  DHCPv6 Operator-Realm Option  . . . . . . . . . . . .  14
   6.  Relay Agent Behavior  . . . . . . . . . . . . . . . . . . . .  14
   7.  Server Behavior . . . . . . . . . . . . . . . . . . . . . . .  15
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     10.2.  Informative References . . . . . . . . . . . . . . . . .  18
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

Bhandari, et al.             Standards Track                    [Page 2]
RFC 7839            ANI Options for DHCPv4 and DHCPv6          June 2016

1.  Introduction

   Access-network identification of a network device has a range of

Show full document text

Access-Network-Identifier Option in DHCPRFC 7839

Access-Network-Identifier Option in DHCP
RFC 7839