RFC 4938 on PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics

[rfc-editor at rfc-editor.org]

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



        

        RFC 4938



        Title:      PPP Over Ethernet (PPPoE) Extensions 

                    for Credit Flow and Link Metrics 

        Author:     B. Berry, H. Holgate

        Status:     Informational

        Date:       June 2007

        Mailbox:    bberry at cisco.com, 

                    hholgate at cisco.com

        Pages:      17

        Characters: 38288

        Updates/Obsoletes/SeeAlso:   None



        I-D Tag:    draft-bberry-pppoe-credit-06.txt



        URL:        http://www.rfc-editor.org/rfc/rfc4938.txt



This document extends the Point-to-Point over Ethernet (PPPoE)

Protocol with a credit-based flow control mechanism and

Link Quality Metric report.  This optional extension should

improve the performance of PPPoE over media with variable

bandwidth and limited buffering, such as mobile radio links.  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 list and the RFC-DIST list.

Requests to be added to or deleted from the IETF distribution list

should be sent to IETF-REQUEST at IETF.ORG.  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.



Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 



help: ways_to_get_rfcs. For example:



        To: rfc-info at RFC-EDITOR.ORG

        Subject: getting rfcs



        help: ways_to_get_rfcs



Requests for special distribution should be addressed to either the

author of the RFC in question, or toFrom ietf-announce-bounces at ietf.org Sat Jun 30 17:44:41 2007
Return-path: <ietf-announce-bounces at ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4keq-00051L-TU; Sat, 30 Jun 2007 17:39:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4keo-0004zW-7C; Sat, 30 Jun 2007 17:39:06 -0400
Received: from bosco.isi.edu ([128.9.168.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4kej-0000yz-Jq; Sat, 30 Jun 2007 17:39:06 -0400
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 9C5B7D9372; Sat, 30 Jun 2007 14:38:40 -0700 (PDT)
To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
From: rfc-editor at rfc-editor.org
Message-Id: <20070630213840.9C5B7D9372 at bosco.isi.edu>
Date: Sat, 30 Jun 2007 14:38:40 -0700 (PDT)
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Cc: hubmib at ietf.org, rfc-editor at rfc-editor.org
Subject: RFC 4878 on Definitions and Managed Objects for Operations,
	Administration,
	and Maintenance (OAM) Functions on Ethernet-Like Interfaces
X-BeenThere: ietf-announce at ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
	<mailto:ietf-announce-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce at ietf.org>
List-Help: <mailto:ietf-announce-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
	<mailto:ietf-announce-request at ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces at ietf.org


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



        

        RFC 4878



        Title:      Definitions and Managed Objects for 

                    Operations, Administration, and Maintenance (OAM)

                    Functions on Ethernet-Like Interfaces 

        Author:     M. Squire

        Status:     Standards Track

        Date:       June 2007

        Mailbox:    msquire at hatterasnetworks.com

        Pages:      58

        Characters: 130067

        Updates/Obsoletes/SeeAlso:   None



        I-D Tag:    draft-ietf-hubmib-efm-mib-06.txt



        URL:        http://www.rfc-editor.org/rfc/rfc4878.txt



This document defines objects for managing Operations,

Administration, and Maintenance (OAM) capabilities on Ethernet-like

interfaces conformant to the Ethernet OAM functionality defined in

the Ethernet in the First Mile (EFM) clauses of the Ethernet

standards.  The Ethernet OAM functionality is complementary to the

Simple Network Management Protocol (SNMP) in that it is focused on a

small set of link-specific functions for directly connected Ethernet

interfaces.  This document defines objects for controlling those link

OAM functions and for providing results and status of the OAM

functions to management entities.  [STANDARDS TRACK]



This document is a product of the Ethernet Interfaces and Hub MIB

Working Group of the IETF



This is now a Proposed Standard Protocol.



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 Internet

 Official Protocol Standards (STD 1) for the standardization state and

 status of this protocol.  Distribution of this memo is unlimited.



This announcement is sent to the IETF list and the RFC-DIST list.

Requests to be added to or deleted from the IETF distribution list

should be sent to IETF-REQUEST at IETF.ORG.  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.



Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 



help: ways_to_get_rfcs. For example:



        To: rfc-info at RFC-EDITOR.ORG

        Subject: getting rfcs



        help: ways_to_get_rfcs



Requests for special distribution RFC-Manager at RFC-EDITOR.ORG.  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.



Submissions for Requests for Comments should be sent to

RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC

Authors, for further information.





The RFC Editor Team

USC/Information Sciences Institute



...





_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce





 should be addressed to either the

author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.



Submissions for Requests for Comments should be sent to

RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC

Authors, for further information.





The RFC Editor Team

USC/Information Sciences Institute



...





_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce