IKEv2 Notification Codes for IPv4/IPv6 Coexistence
draft-boucadair-ipsecme-ipv6-ipv4-codes-00

Document Type Active Internet-Draft (individual)
Last updated 2017-10-06
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                       M. Boucadair
Internet-Draft                                                    Orange
Updates: 7296 (if approved)                              October 6, 2017
Intended status: Standards Track
Expires: April 9, 2018

           IKEv2 Notification Codes for IPv4/IPv6 Coexistence
               draft-boucadair-ipsecme-ipv6-ipv4-codes-00

Abstract

   This document specifies new IKEv2 notification codes to better manage
   IPv4 and IPv6 co-existence.

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 https://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 April 9, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (https://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.

Boucadair                 Expires April 9, 2018                 [Page 1]
Internet-Draft            An Update to RFC7296              October 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Why Not INTERNAL_ADDRESS_FAILURE? . . . . . . . . . . . . . .   3
   3.  An Update to RFC7296  . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   As described in [RFC7849], if the subscription data or network
   configuration allows only one IP address family (IPv4 or IPv6), the
   cellular host must not request a second PDP-Context to the same APN
   for the other IP address family.  The 3GPP network informs the
   cellular host about allowed Packet Data Protocol (PDP) types by means
   of Session Management (SM) cause codes.  In particular, the following
   cause codes can be returned:

   o  cause #50 "PDP type IPv4 only allowed" - This cause code is used
      by the network to indicate that only PDP type IPv4 is allowed for
      the requested Public Data Network (PDN) connectivity.

   o  cause #51 "PDP type IPv6 only allowed" - This cause code is used
      by the network to indicate that only PDP type IPv6 is allowed for
      the requested PDN connectivity.

   o  cause #52 "single address bearers only allowed" - This cause code
      is used by the network to indicate that the requested PDN
      connectivity is accepted with the restriction that only single IP
      version bearers are allowed.

   If the requested IPv4v6 PDP-Context is not supported by the network
   but IPv4 and IPv6 PDP types are allowed, then the cellular host will
   be configured with an IPv4 address or an IPv6 prefix by the network.
   It must initiate another PDP-Context activation of the other address
   family in addition to the one already activated for a given Access
   Point Name (APN).  The purpose of initiating a second PDP-Context is
   to achieve dual-stack connectivity by means of two PDP-Contexts.

   According to 3GPP specifications (TS.24302), when the UE attaches the
   network using a WLAN access by means of IKEv2 capabilities [RFC7296],
   there are no equivalent notification codes to inform the UE why an IP

Boucadair                 Expires April 9, 2018                 [Page 2]
Internet-Draft            An Update to RFC7296              October 2017
Show full document text