References from draft-ietf-l2tpext-sesinfo
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 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | Reference | |
| BCP 18 |
IETF Policy on Character Sets and Languages References Referenced by |
Best Current Practice | Reference | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | Reference | |
| RFC 1661 |
The Point-to-Point Protocol (PPP) References Referenced by |
Internet Standard | Reference | |
| RFC 2026 |
The Internet Standards Process -- Revision 3 References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 2058 |
Remote Authentication Dial In User Service (RADIUS) References Referenced by |
Proposed Standard | Reference | |
| RFC 2059 |
RADIUS Accounting References Referenced by |
Informational | Reference | Possible Downref |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | Reference | |
| RFC 2277 |
IETF Policy on Character Sets and Languages References Referenced by |
Best Current Practice | Reference | |
| RFC 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | Reference | |
| RFC 2661 |
Layer Two Tunneling Protocol "L2TP" References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 3193 |
Securing L2TP using IPsec References Referenced by |
Proposed Standard | Reference |