RFC 5515 on Layer 2 Tunneling Protocol (L2TP) Access Line Information Attribute Value Pair (AVP) Extensions
rfc-editor@rfc-editor.org Tue, 05 May 2009 23:24 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 46D533A6BAD for <ietf-announce@core3.amsl.com>; Tue, 5 May 2009 16:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.224
X-Spam-Level:
X-Spam-Status: No, score=-17.224 tagged_above=-999 required=5 tests=[AWL=0.375, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1BHc9OCC1lz4 for <ietf-announce@core3.amsl.com>; Tue, 5 May 2009 16:24:36 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 5D44F3A687A for <ietf-announce@ietf.org>; Tue, 5 May 2009 16:24:36 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id A5A4429C03D; Tue, 5 May 2009 16:22:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5515 on Layer 2 Tunneling Protocol (L2TP) Access Line Information Attribute Value Pair (AVP) Extensions
From: rfc-editor@rfc-editor.org
Message-Id: <20090505232248.A5A4429C03D@bosco.isi.edu>
Date: Tue, 05 May 2009 16:22:48 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 May 2009 23:24:37 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 5515
Title: Layer 2 Tunneling Protocol (L2TP)
Access Line Information Attribute Value Pair
(AVP) Extensions
Author: V. Mammoliti, C. Pignataro,
P. Arberg, J. Gibbons,
P. Howard
Status: Informational
Date: May 2009
Mailbox: vince@cisco.com,
cpignata@cisco.com,
parberg@redback.com,
jgibbons@juniper.net,
howsoft@mindspring.com
Pages: 28
Characters: 60768
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-mammoliti-l2tp-accessline-avp-06.txt
URL: http://www.rfc-editor.org/rfc/rfc5515.txt
This document describes a set of Layer 2 Tunneling Protocol (L2TP)
Attribute Value Pair (AVP) extensions designed to carry the
subscriber Access Line identification and characterization
information that arrives at the Broadband Remote Access Server (BRAS)
with L2TP Access Concentrator (LAC) functionality. It also describes
a mechanism to report connection speed changes, after the initial
connection speeds are sent during session establishment. The primary
purpose of this document is to provide a reference for DSL equipment
vendors wishing to interoperate with other vendors' products. The
L2TP AVPs defined in this document are applicable to both L2TPv2 and
L2TPv3. This memo provides information for the Internet community.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://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
USC/Information Sciences Institute