PPP over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics
draft-bberry-rfc4938bis-00

State Change Notice email list have been change to sratliff@cisco.com, bberry@cisco.com, pdice@cisco.com, timothy.kaiser@harris.com, Michael.D.Adams@L-3com.com, draft-bberry-rfc4938bis@tools.ietf.org, rfc-editor@rfc-editor.org from sratliff@cisco.com, bberry@cisco.com, pdice@cisco.com, timothy.kaiser@harris.com, Michael.D.Adams@L-3com.com, draft-bberry-rfc4938bis@tools.ietf.org

[Ballot discuss]
Some editorial comments that can be covered with an RFC editor note.

Section 3.2.1, 1st Discovery PADR packet diagram: s/Metric TLV/TLV/

Section 3.2.1, 2nd Discovery PADR packet diagram: the LENGTH should, I think, be 0x0E

Section 3.2.2, 2nd Discovery PADS packet diagram: the LENGTH should be 0x14

Section 3.2.4, 2nd para: s/Credit Tag TLV/Credit TLV/

Following up on Adrian's DISCUSS, I found "IANA Considerations" section a little confusing.  Usually, such a section will list actions requested of IANA, rather than reporting actions already taken?  The tables in the section list "See the reference" under "Description" and [RF4938bis] as the reference.  Isn't this doc RFC4938bis?  Perhaps give the sections in this doc that describe each of the TLVs?  Anyway, I'm confused.

IANA comments:

Action #1:

Upon approval of this document, IANA will make the following
changes in the "PPPoE TAG Values (16-bit values)" registry at
http://www.iana.org/assignments/pppoe-parameters

OLD:

TAG Value TAG Name Tag Description Reference
------------ --------------------- --------------------- ---------
262 (0x0106) Credits See the reference [RFC4938]
263 (0x0107) Metrics See the reference [RFC4938]
264 (0x0108) Sequence Number See the reference [RFC4938]
265 (0x0109) Credit Scale Factor See the reference [Berry][draft-
bberry-rfc4938bis-00.txt]


NEW:
TAG Value TAG Name Tag Description Reference
------------ --------------------- --------------------- ---------
262 (0x0106) Credits See the reference [RFC-bberry-rfc4938bis-00]
263 (0x0107) Metrics See the reference [RFC-bberry-rfc4938bis-00]
264 (0x0108) Sequence Number See the reference [RFC-bberry-rfc4938bis-00]
265 (0x0109) Credit Scale Factor See the reference [RFC-bberry-rfc4938bis-00]


Action #2:

Upon approval of this document, IANA will make the following
changes in the "PPPoE Active Discovery Code fields (8-bit values)"
registry at
http://www.iana.org/assignments/pppoe-parameters

OLD:

Code PPPoE Packet Name Description Reference
------------ ------------------------- ----------------- ---------
10 0x0a PADG, Session-Grant See the reference [RFC4938]
11 0x0b PADC, Session-Credit Response See the reference [RFC4938]
12 0x0c PADQ, Quality See the reference [RFC4938]


NEW:

Code PPPoE Packet Name Description Reference
------------ ------------------------- ----------------- ---------
10 0x0a PADG, Session-Grant See the reference [RFC-bberry-rfc4938bis-00]
11 0x0b PADC, Session-Credit Response See the reference [RFC-bberry-rfc4938bis-00]
12 0x0c PADQ, Quality See the reference [RFC-bberry-rfc4938bis-00]


We understand the above to be the only IANA Actions for this document.

[Ballot discuss]
Small point, but I believe the text in the IANA section is now wrong.

It currently says...

"IANA has assigned the following PPPoE TLV Values as noted in [3]"

This was correct for the 4938 allocations that *were* listed in RFC 4937 [3]. But this bis requests a new allocation of code point 265 that was not mentioned in RFC 4937.

So, I believe the section should be split into the three code points as described in [3] (with the existing text), and the new code point as defined in this bis.

Should take 30 seconds to write an RFC Editor note and then I will clear.

Request for pppext review given, but there were no takers.


-------- Original Message --------
Subject: [Pppext] Review of draft-bberry-rfc4938bis-00.txt
Date: Thu, 13 Nov 2008 22:38:11 +0100
From: Mark Townsley
To: pppext@ietf.org, draft-bberry-rfc4938bis@tools.ietf.org


pppext folks,

draft-bberry-rfc4938bis-00.txt has been submitted to the RFC Editor as
an independent submission, thus not an IETF consensus document in any
way. However, as with other pppoe documents, I would like pppext to take
a look at it and provide any comments to the authors here.  Unless I
hear otherwise from the authors or a revision is needed and not ready in
time, the document will be on the Dec 4 IESG telechat, so please submit
any comments by that time.

Thanks in advance all,

- Mark
_______________________________________________
Pppext mailing list
Pppext@ietf.org
https://www.ietf.org/mailman/listinfo/pppext

[Ballot discuss]
Which RFC 3932 response is being proposed for this document?

Given the strong IESG Note in RFC4938, what does the PPEXT WG have to say about this revision?

IESG,

This document was submitted to the RFC Editor to be published as an
Informational Independent Submission: draft-bberry-rfc4938bis-00.txt.

Please let us know if this document conflicts with the IETF standards
process or other work being done in the IETF community.

Four week timeout expires on 29 October 2008.


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

This document extends the Point-to-Point over Ethernet (PPPoE)
Protocol with an optional credit-based flow control mechanism and
an optional Link Quality Metric report. These optional extensions
improve the performance of PPPoE over media with variable bandwidth
and limited buffering, such as mobile point-to-point radio links.


This document is a minor extension to RFC 4938, to provide scaling of
several fields. The RFC Editor expects that the IESG will want to
attach the same IESG disclaimer to this document that they attached to
4938.


Sincerely,

Sandy Ginoza - USC/ISI
Request for Comments Documents