Extensions to Generic Aggregate RSVP for IPv4 and IPv6 Reservations over Pre-Congestion Notification (PCN) Domains

Bhargava, Anurag; Karagiannis, Georgios

doi:10.17487/rfc7417

Cited by 1 publication

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…On the signaling in a PCN-domain, P. Eardley [1] refers to related work that consider specific signaling protocols or frameworks like next steps in signaling (NSIS, [18] ), resource reservation protocol (RSVP, [19] ) and extensions to RSVP [20] . In [2] , signaling is considered out of scope and refers to [20] as well.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Flow termination signaling in the centralized pre-congestion notification architecture

et al. 2017

View full text Add to dashboard Cite

a b s t r a c tPre-congestion notification (PCN) protects inelastic traffic by using feedback on network link loads on and acting upon this accordingly. These actions comprise to admission control and termination of flows. Two PCN architectures have been defined by IETF: the centralized and decentralized PCN architecture. The decentralized PCN architecture has received much attention in the literature whereas the centralized PCN architecture has not. In the decentralized architecture, feedback is sent from the egress nodes to ingress nodes, which then take and apply decisions regarding admission of new flows and/or termination of ongoing flows. Signaling occurs only between ingress and egress nodes.In the centralized architecture these decisions are made at a central node, which requires proper signaling for action and information exchange between the central node and the egress and ingress nodes. This signaling has been suggested by other authors, but is not fully defined yet. Our contribution is twofold. We define signaling in the centralized PCN architecture focussing on flow termination, which completes the definition of the signaling in the centralized PCN architecture. Secondly, we run extensive simulations showing that the proposed signaling works well and that the performances of the centralized PCN and the decentralized PCN architectures are similar. Hence, it is expected that results from existing research on the effectiveness of decentralized PCN are also valid when the centralized PCN architecture is used.

show abstract

Section: Introductionmentioning

confidence: 99%

“…In [2] , signaling is considered out of scope and refers to [20] as well. NSIS mainly focuses on protocols for signaling that follow the same paths along which the user-data flows, i.e.…”

Section: Introductionmentioning

confidence: 99%

Flow termination signaling in the centralized pre-congestion notification architecture

et al. 2017

View full text Add to dashboard Cite

show abstract

Extensions to Generic Aggregate RSVP for IPv4 and IPv6 Reservations over Pre-Congestion Notification (PCN) Domains

Abstract: This document specifies extensions to Generic Aggregate RSVP (RFC 4860) for support of the Pre-Congestion Notification (PCN) Controlled Load (CL) and Single Marking (SM) edge behaviors over a Diffserv cloud using PCN.

Cited by 1 publication

References 6 publications

Flow termination signaling in the centralized pre-congestion notification architecture

Flow termination signaling in the centralized pre-congestion notification architecture

Contact Info

Product

Resources

About