Port Control Protocol (PCP) Authentication Mechanism
draft-ietf-pcp-authentication-13

 
Document Type Active Internet-Draft (pcp WG)
Last updated 2015-07-02
Replaces draft-wasserman-pcp-authentication
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Dave Thaler
Shepherd write-up Show (last changed 2015-05-29)
IESG IESG state IESG Evaluation
Telechat date On agenda of 2015-07-09 IESG telechat
Needs 9 more YES or NO OBJECTION positions to pass.
Responsible AD Brian Haberman
Send notices to "Dave Thaler" <dthaler@microsoft.com>
IANA IANA review state Version Changed - Review Needed
IANA action state None
Network Working Group                                       M. Wasserman
Internet-Draft                                                S. Hartman
Updates: 6887 (if approved)                            Painless Security
Intended status: Standards Track                                D. Zhang
Expires: January 4, 2016                                          Huawei
                                                                T. Reddy
                                                                   Cisco
                                                           July 03, 2015

          Port Control Protocol (PCP) Authentication Mechanism
                    draft-ietf-pcp-authentication-13

Abstract

   An IPv4 or IPv6 host can use the Port Control Protocol (PCP) to
   flexibly manage the IP address and port mapping information on
   Network Address Translators (NATs) or firewalls, to facilitate
   communication with remote hosts.  However, the un-controlled
   generation or deletion of IP address mappings on such network devices
   may cause security risks and should be avoided.  In some cases the
   client may need to prove that it is authorized to modify, create or
   delete PCP mappings.  This document describes an in-band
   authentication mechanism for PCP that can be used in those cases.
   The Extensible Authentication Protocol (EAP) is used to perform
   authentication between PCP devices.

   This document updates RFC6887.

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 January 4, 2016.

Wasserman, et al.        Expires January 4, 2016                [Page 1]
Internet-Draft             PCP Authentication                  July 2015

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Protocol Details  . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Session Initiation  . . . . . . . . . . . . . . . . . . .   5
       3.1.1.  Authentication triggered by the client  . . . . . . .   6
       3.1.2.  Authentication triggered by the server  . . . . . . .   7
       3.1.3.  Authentication using EAP  . . . . . . . . . . . . . .   7
     3.2.  Session Termination . . . . . . . . . . . . . . . . . . .   9
     3.3.  Session Re-Authentication . . . . . . . . . . . . . . . .  10
   4.  PA Security Association . . . . . . . . . . . . . . . . . . .  11
   5.  Packet Format . . . . . . . . . . . . . . . . . . . . . . . .  12
     5.1.  Packet Format of PCP Auth Messages  . . . . . . . . . . .  12
     5.2.  Opcode-specific information of AUTHENTICATION Opcode  . .  13
     5.3.  NONCE Option  . . . . . . . . . . . . . . . . . . . . . .  14
     5.4.  AUTHENTICATION_TAG Option . . . . . . . . . . . . . . . .  14
     5.5.  PA_AUTHENTICATION_TAG . . . . . . . . . . . . . . . . . .  16
     5.6.  EAP_PAYLOAD Option  . . . . . . . . . . . . . . . . . . .  17
     5.7.  PRF Option  . . . . . . . . . . . . . . . . . . . . . . .  17
     5.8.  MAC_ALGORITHM Option  . . . . . . . . . . . . . . . . . .  18
     5.9.  SESSION_LIFETIME Option . . . . . . . . . . . . . . . . .  18
     5.10. RECEIVED_PAK Option . . . . . . . . . . . . . . . . . . .  19
     5.11. ID_INDICATOR Option . . . . . . . . . . . . . . . . . . .  19
   6.  Processing Rules  . . . . . . . . . . . . . . . . . . . . . .  20
     6.1.  Authentication Data Generation  . . . . . . . . . . . . .  20
     6.2.  Authentication Data Validation  . . . . . . . . . . . . .  21
Show full document text