References from RFC 4937
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
References Referenced by |
normatively references | ||
| BCP 26 |
References Referenced by |
normatively references | ||
| BCP 78 |
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2516 |
A Method for Transmitting PPP Over Ethernet (PPPoE)
References Referenced by |
Informational | normatively references | |
| RFC 4638 |
Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE)
References Referenced by |
Informational | informatively references | |
| RFC 4938 |
PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics
References Referenced by |
Informational | informatively references |