References from draft-ietf-teas-actn-requirements
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 |
Possible Reference | ||
draft-cheng-actn-ptn-requirements |
ACTN Use-cases for Packet Transport Networks in Mobile Backhaul Networks
References Referenced by |
informatively references | ||
draft-dhody-actn-poi-use-case |
Packet Optical Integration (POI) Use Cases for Abstraction and Control of TE Networks (ACTN)
References Referenced by |
informatively references | ||
draft-fang-actn-multidomain-dci |
ACTN Use Case for Multi-domain Data Center Interconnect
References Referenced by |
informatively references | ||
draft-ietf-teas-actn-framework |
Framework for Abstraction and Control of TE Networks (ACTN)
References Referenced by |
Informational | normatively references | |
draft-klee-teas-actn-connectivity-multi-domain |
ACTN use-case for E2E network services in multiple vendor domain transport networks
References Referenced by |
informatively references | ||
draft-kumaki-teas-actn-multitenant-vno |
ACTN : Use case for Multi Tenant VNO
References Referenced by |
informatively references | ||
draft-lopez-actn-vno-multidomains |
ACTN Use-case for Virtual Network Operation for Multiple Domains in a Single Operator Network
References Referenced by |
informatively references | ||
draft-shin-actn-mvno-multi-domain |
ACTN Use-case for Mobile Virtual Network Operation for Multiple Domains in a Single Operator Network
References Referenced by |
informatively references | ||
draft-suzuki-teas-actn-multidomain-opc |
Use-case and Requirements for Multi-domain Operation Plane Change
References Referenced by |
informatively references | ||
draft-xu-actn-perf-dynamic-service-control |
Use Cases and Requirements of Dynamic Service Control based on Performance Monitoring in ACTN Architecture
References Referenced by |
informatively references | ||
draft-xu-teas-actn-abstract-alarm-report |
Requirements of Abstract Alarm Report in ACTN architecture
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | informatively references | |
RFC 5541 |
Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)
References Referenced by |
Proposed Standard | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | informatively references |