Browse Prior Art Database

Access-Network-Identifier Option in DHCP (RFC7839)

IP.com Disclosure Number: IPCOM000246717D
Original Publication Date: 2016-Jun-01
Included in the Prior Art Database: 2016-Jun-29
Document File: 40 page(s) / 43K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Bhandari: AUTHOR [+5]

Abstract

Access-network identification of a network device has a range of applications. For example, the Local Mobility Anchor (LMA) in a Proxy Mobile IPv6 (PMIPv6) domain is able to provide service treatment for the mobile node's traffic based on the access network to which the mobile node is attached.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

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