RFC6662 · Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of Operation
Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of Operation
Pre-Congestion Notification (PCN) is a means for protecting the quality of service for inelastic traffic admitted to a Diffserv domain. The overall PCN architecture is described in RFC 5559. This memo is one of a series describing possible boundary-node behaviors for a PCN-domain. The behavior described here is that for a form of measurement-based load control using two PCN marking states: not- marked and excess-traffic-marked. This behavior is known informally as the Single Marking (SM) PCN-boundary-node behavior. This document defines an Experimental Protocol for the Internet community.
IETF · RFCОфициальная английская аннотация
Pre-Congestion Notification (PCN) is a means for protecting the quality of service for inelastic traffic admitted to a Diffserv domain. The overall PCN architecture is described in RFC 5559. This memo is one of a series describing possible boundary-node behaviors for a PCN-domain. The behavior described here is that for a form of measurement-based load control using two PCN marking states: not- marked and excess-traffic-marked. This behavior is known informally as the Single Marking (SM) PCN-boundary-node behavior. This document defines an Experimental Protocol for the Internet community.
{
"id": "RFC6662",
"number": 6662,
"title_en": "Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of Operation",
"title_ru": "",
"summary_ru": "",
"purpose_ru": "",
"use_ru": "",
"full_translation_path": "",
"full_translation_checked_at": "",
"full_translation_source_sha256": "",
"architect_note_ru": "",
"topics_ru": [],
"translation_state": "not_prepared",
"verification_level": "not_prepared",
"verification_level_ru": "Русская выжимка не подготовлена",
"verification_note_ru": "",
"abstract_en": "Pre-Congestion Notification (PCN) is a means for protecting the quality of service for inelastic traffic admitted to a Diffserv domain. The overall PCN architecture is described in RFC 5559. This memo is one of a series describing possible boundary-node behaviors for a PCN-domain. The behavior described here is that for a form of measurement-based load control using two PCN marking states: not- marked and excess-traffic-marked. This behavior is known informally as the Single Marking (SM) PCN-boundary-node behavior. This document defines an Experimental Protocol for the Internet community.",
"authors": [
"A. Charny",
"J. Zhang",
"G. Karagiannis",
"M. Menth",
"T. Taylor"
],
"organizations": [],
"publication_date": "2012-07-01",
"current_status": "EXPERIMENTAL",
"current_status_ru": "Экспериментальный",
"publication_status": "EXPERIMENTAL",
"publication_status_ru": "Экспериментальный",
"lifecycle": "experimental",
"lifecycle_ru": "Экспериментальный",
"stream": "IETF",
"stream_ru": "IETF",
"area": "tsv",
"area_ru": "Транспорт",
"working_group": "pcn",
"source_draft": "draft-ietf-pcn-sm-edge-behaviour-12",
"page_count": 31,
"doi": "10.17487/RFC6662",
"keywords": [
"PCN",
"single marking",
"SM",
"edge node behavior"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc6662/",
"html": "https://www.rfc-editor.org/rfc/rfc6662.html",
"txt": "https://www.rfc-editor.org/rfc/rfc6662.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc6662/"
}
}