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

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: RFC Editor <rfc-editor@rfc-editor.org>
Cc: The IESG <iesg@ietf.org>, <iana@iana.org>, ietf-announce@ietf.org
Subject: Re: Informational RFC to be: 

The IESG has no problem with the publication of 'PPP Over Ethernet 
(PPPoE) Extensions for Credit Flow and Link Metrics' 
<draft-bberry-pppoe-credit-07.txt> as an Informational RFC. 

The IESG would also like the IRSG or RFC-Editor to review the comments in 
the datatracker 
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is Mark Townsley.

A URL of this Internet-Draft is:

The process for such documents is described at http://www.rfc-editor.org/indsubs.html.

Thank you,

The IESG Secretary

Technical Summary
   This document extends the Point-to-Point Over Ethernet (PPPoE) 
   Protocol [2] 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.
Working Group Summary
   This is an individual submission. However, the pppext WG provided 
   review. See RFC Editor's note for pppext warning about this
Protocol Quality

   This document received extensive review from the pppext WG. The
   document was also reviewed by Mark Townsley. We are told that there
   are two independent, interoperable, implementations and that it 
   has been deployed. 

Note to RFC Editor

  2. The IESG thinks that this work is related to IETF work done in WG
     pppext, but this does not prevent publishing.

Editor, this document defines new PPPoE tags and messages. The PPPoE IANA
registry for PPPoE is in the process of being set up, as defined in
draft-arberg-pppoe-iana-00.txt (which is targeted to become a BCP). Please
include a reference to this document for tag/message allocation and go through
IANA to obtain the values.

Please see Comments in the tracker, which include some constructive
recommendations for this document.


  "The PPP Extensions Working Group (pppext) has reservations about
  the desirability of the feature described in this document.  In
  particular, it solves a general problem at an inappropriate layer
  and it may have unpredictable interactions with higher and lower
  level protocols.  The techniques described in this document are
  intended for use with a particular deployment technique that uses a
  PPP termination separated from a radio termination by an Ethernet,
  and that has radio-side flow control for a slower PPP-only link to
  remote nodes.  Implementors are better advised to avoid split
  termination with inter-media protocol translation, and use standard
  Internet Protocol routing instead."