RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P)
RFC 8658

Document Type RFC - Proposed Standard (November 2019; No errata)
Last updated 2019-11-11
Replaces draft-jiang-softwire-map-radius
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Ian Farrer
Shepherd write-up Show (last changed 2019-04-05)
IESG IESG state RFC 8658 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Éric Vyncke
Send notices to "Yong Cui" <cuiyong@tsinghua.edu.cn>, Ian Farrer <ianfarrer@gmx.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack


Internet Engineering Task Force (IETF)                     S. Jiang, Ed.
Request for Comments: 8658                                        Huawei
Category: Standards Track                                     Y. Fu, Ed.
ISSN: 2070-1721                                                    CNNIC
                                                                  C. Xie
                                                           China Telecom
                                                                   T. Li
                                                     Tsinghua University
                                                       M. Boucadair, Ed.
                                                                  Orange
                                                           November 2019

           RADIUS Attributes for Softwire Mechanisms Based on
                        Address plus Port (A+P)

Abstract

   IPv4-over-IPv6 transition mechanisms provide IPv4 connectivity
   services over IPv6 native networks during the IPv4/IPv6 coexistence
   period.  DHCPv6 options have been defined to configure clients for
   Lightweight 4over6, Mapping of Address and Port with Encapsulation
   (MAP-E), Mapping of Address and Port using Translation (MAP-T)
   unicast softwire mechanisms, and multicast softwires.  However, in
   many networks, configuration information is stored in an
   Authentication, Authorization, and Accounting (AAA) server, which
   utilizes the Remote Authentication Dial In User Service (RADIUS)
   protocol to provide centralized management for users.  When a new
   transition mechanism is developed, new RADIUS attributes need to be
   defined correspondingly.

   This document defines new RADIUS attributes to carry softwire
   configuration parameters based on Address plus Port from a AAA server
   to a Broadband Network Gateway.  Both unicast and multicast
   attributes are covered.

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
   https://www.rfc-editor.org/info/rfc8658.

Copyright Notice

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

Table of Contents

   1.  Introduction
   2.  Terminology
   3.  New RADIUS Attributes
     3.1.  Softwire46-Configuration Attribute
       3.1.1.  Softwire46 Attributes
         3.1.1.1.  Softwire46-MAP-E Attribute
         3.1.1.2.  Softwire46-MAP-T Attribute
         3.1.1.3.  Softwire46-Lightweight-4over6 Attribute
       3.1.2.  Softwire46 Sub-attributes
       3.1.3.  Specification of the Softwire46 Sub-attributes
         3.1.3.1.  Softwire46-Rule Attribute
         3.1.3.2.  Softwire46-BR Attribute
         3.1.3.3.  Softwire46-DMR Attribute
         3.1.3.4.  Softwire46-V4V6Bind Attribute
         3.1.3.5.  Softwire46-PORTPARAMS Attribute
       3.1.4.  Sub-attributes for Softwire46-Rule
         3.1.4.1.  Rule-IPv6-Prefix Attribute
         3.1.4.2.  Rule-IPv4-Prefix Attribute
         3.1.4.3.  EA-Length Attribute
       3.1.5.  Attributes for Softwire46-v4v6Bind
         3.1.5.1.  IPv4-Address Attribute
         3.1.5.2.  Bind-IPv6-Prefix Attribute
       3.1.6.  Attributes for Softwire46-PORTPARAMS
         3.1.6.1.  PSID-Offset Attribute
         3.1.6.2.  PSID-Len Attribute
         3.1.6.3.  PSID Attribute
     3.2.  Softwire46-Priority Attribute
       3.2.1.  Softwire46-Option-Code
     3.3.  Softwire46-Multicast Attribute
       3.3.1.  ASM-Prefix64 Attribute
       3.3.2.  SSM-Prefix64 Attribute
       3.3.3.  U-Prefix64 Attribute
   4.  A Sample Configuration Process with RADIUS
   5.  Table of Attributes
   6.  Security Considerations
   7.  IANA Considerations
     7.1.  New RADIUS Attributes
     7.2.  RADIUS Softwire46 Configuration and Multicast
           Attributes
     7.3.  Softwire46 Mechanisms and Their Identifying Option
           Codes
   8.  References
     8.1.  Normative References
     8.2.  Informative References
Show full document text