RFC 8921: Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)

In plain English — editorial summary, not part of the RFC

This document defines the Connectivity Provisioning Negotiation Protocol (CPNP), which is designed to facilitate the dynamic negotiation of service parameters. CPNP is a generic protocol that can be used for various negotiation purposes that include (but are not necessarily limited to) connectivity provisioning services, storage facilities, Content Delivery Networks, etc.

Document record

Document ID

RFC8921

Published

October 2020

Authors

M. Boucadair; C. Jacquenet; D. Zhang; P. Georgatsos

Status

INFORMATIONAL

Stream

INDEPENDENT

Area

—

Pages

49

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC8921

Topics

• SDN
• Order Request Handling
• Automation
• Dynamic Provisioning
• CDN
• Interconnection
• Service Delivery
• Service Activation

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 8969A Framework for Automating Service and Network Management with YANGCurrent

  January 2021

• RFC 7767Application-Initiated Check-Pointing via the Port Control Protocol (PCP)Current

  February 2016

• RFC 8782Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationObsoleted

  May 2020

• RFC 8768Constrained Application Protocol (CoAP) Hop-Limit OptionCurrent

  March 2020

• RFC 9132Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationCurrent

  September 2021

• RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent

  December 2021

• RFC 8676YANG Modules for IPv4-in-IPv6 Address plus Port (A+P) SoftwiresCurrent

  November 2019

• RFC 9181A Common YANG Data Model for Layer 2 and Layer 3 VPNsCurrent

  February 2022

Also filed under

• INFORMATIONAL
• 2020
• INDEPENDENT stream