[radext] RFC 7542 on The Network Access Identifier

rfc-editor@rfc-editor.org Fri, 01 May 2015 19:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0150E1B2E17; Fri, 1 May 2015 12:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.612
X-Spam-Level:
X-Spam-Status: No, score=-104.612 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_NAIL=2.3, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 utvrXBajJrts; Fri, 1 May 2015 12:29:22 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 974D01B2E1D; Fri, 1 May 2015 12:29:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4BDFF180092; Fri, 1 May 2015 12:28:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150501192813.4BDFF180092@rfc-editor.org>
Date: Fri, 1 May 2015 12:28:13 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/GmaFR4X9y15dC9KknX4SP2v6ywI>
Cc: radext@ietf.org, rfc-editor@rfc-editor.org
Subject: [radext] RFC 7542 on The Network Access Identifier
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 May 2015 19:29:24 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7542

        Title:      The Network Access Identifier 
        Author:     A. DeKok
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2015
        Mailbox:    aland@freeradius.org
        Pages:      30
        Characters: 66596
        Obsoletes:  RFC 4282

        I-D Tag:    draft-ietf-radext-nai-15.txt

        URL:        https://www.rfc-editor.org/info/rfc7542

In order to provide inter-domain authentication services, it is
necessary to have a standardized method that domains can use to
identify each other's users.  This document defines the syntax for
the Network Access Identifier (NAI), the user identifier submitted by
the client prior to accessing resources.  This document is a revised
version of RFC 4282.  It addresses issues with international
character sets and makes a number of other corrections to RFC 4282.

This document is a product of the RADIUS EXTensions 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/rfc.html

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