References from draft-eastlake-sfc-parallel
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 | informatively references | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust
References Referenced by |
Best Current Practice | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | informatively references | |
| RFC 5378 |
Rights Contributors Provide to the IETF Trust
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7665 |
Service Function Chaining (SFC) Architecture
References Referenced by |
Informational | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | informatively references | |
| RFC 8300 |
Network Service Header (NSH)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 8459 |
Hierarchical Service Function Chaining (hSFC)
References Referenced by |
Experimental | informatively references |