PCP WG R. Maglione
Internet-Draft Cisco Systems
Intended status: Standards Track D. Cheng
Expires: November 25, 2013 Huawei Technologies
M. Boucadair
France Telecom
May 24, 2013
RADIUS Extensions for Port Control Protocol (PCP)
draft-maglione-pcp-radius-ext-08
Abstract
This document specifies a new Remote Authentication Dial In User
Service (RADIUS) attribute to carry a Port Control Protocol (PCP)
Server Names. This attribute can be configured on a RADIUS server so
that the information can be conveyed to Network Access Server (NAS)
via RADIUS protocol, and the co-located Dynamic Host Configuration
Protocol (DHCP/DHCPv6) server can then populate the information to
PCP client.
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 November 25, 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
publication of this document. Please review these documents
Maglione, et al. Expires November 25, 2013 [Page 1]
Internet-Draft PCP RADIUS Extensions May 2013
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. PCP Server Configuration using RADIUS and DHCPv4/DHCPv6 . . . 4
4. PCP-Server-Name RADIUS Attribute . . . . . . . . . . . . . . 7
5. Table of attributes . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
Port Control Protocol (PCP) [RFC6887] provides a mechanism to control
how incoming packets are forwarded by upstream devices such as NATs
and firewalls. PCP is a client/server protocol where a PCP client
may reside on a host, a Customer Premises Equipment (CPE), etc.,
which communicates with a PCP server that may reside anywhere in a
network.
[RFC6887] defines a procedure for the PCP client to communicate with
its PCP Server. The IP address of the PCP Server(s) can be
configured to the PCP client; if not the PCP client assumes its
default router as being its PCP server.
[I-D.ietf-pcp-dhcp] defines DHCPv6 and DHCPv4 options which are meant
to be used by a PCP client to discover a PCP server name. However,
provisioning for name of the PCP server is required on a DHCPv4/
DHCPv6 server before it can populate this information.
Maglione, et al. Expires November 25, 2013 [Page 2]
Internet-Draft PCP RADIUS Extensions May 2013
Auto-configuration on a DHCPv4/DHCPv6 is possible in a broadband
network, where typically, user profile is maintained on a Remote
Authentication Dial In User Service (RADIUS) server and RADIUS
datatracker.ietf.org