[Softwires] RFC 8658 on RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P)
rfc-editor@rfc-editor.org Tue, 12 November 2019 00:13 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A61A120884; Mon, 11 Nov 2019 16:13:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YAZ7GE258F8r; Mon, 11 Nov 2019 16:13:22 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B35031200FD; Mon, 11 Nov 2019 16:13:22 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 84DF6F4073E; Mon, 11 Nov 2019 16:13:19 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, softwires@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20191112001319.84DF6F4073E@rfc-editor.org>
Date: Mon, 11 Nov 2019 16:13:19 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/jFN_08EWLdahAToGswkaIUnMt9k>
Subject: [Softwires] RFC 8658 on RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2019 00:13:32 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8658 Title: RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P) Author: S. Jiang, Ed., Y. Fu, Ed., C. Xie, T. Li, M. Boucadair, Ed. Status: Standards Track Stream: IETF Date: November 2019 Mailbox: jiangsheng@huawei.com, eleven711711@foxmail.com, xiechf.bri@chinatelecom.cn, peter416733@gmail.com, mohamed.boucadair@orange.com Pages: 34 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-softwire-map-radius-26.txt URL: https://www.rfc-editor.org/info/rfc8658 DOI: 10.17487/RFC8658 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. This document is a product of the Softwires Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC