⌕ Поиск по атласу

IETF · RFC · RFC5129

RFC5129 · Explicit Congestion Marking in MPLS

Explicit Congestion Marking in MPLS

RFC 3270 defines how to support the Diffserv architecture in MPLS networks, including how to encode Diffserv Code Points (DSCPs) in an MPLS header. DSCPs may be encoded in the EXP field, while other uses of that field are not precluded. RFC 3270 makes no statement about how Explicit Congestion Notification (ECN) marking might be encoded in the MPLS header. This document defines how an operator might define some of the EXP codepoints for explicit congestion notification, without precluding other uses. [STANDARDS-TRACK]

Официальная английская аннотация

RFC 3270 defines how to support the Diffserv architecture in MPLS networks, including how to encode Diffserv Code Points (DSCPs) in an MPLS header. DSCPs may be encoded in the EXP field, while other uses of that field are not precluded. RFC 3270 makes no statement about how Explicit Congestion Notification (ECN) marking might be encoded in the MPLS header. This document defines how an operator might define some of the EXP codepoints for explicit congestion notification, without precluding other uses. [STANDARDS-TRACK]

Связи документа

updates: RFC3032

updated_by: RFC5462

Официальный источник · 2008-01-01

Полные импортированные сведения карточки
{
  "id": "RFC5129",
  "number": 5129,
  "title_en": "Explicit Congestion Marking in MPLS",
  "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": "RFC 3270 defines how to support the Diffserv architecture in MPLS networks, including how to encode Diffserv Code Points (DSCPs) in an MPLS header. DSCPs may be encoded in the EXP field, while other uses of that field are not precluded. RFC 3270 makes no statement about how Explicit Congestion Notification (ECN) marking might be encoded in the MPLS header. This document defines how an operator might define some of the EXP codepoints for explicit congestion notification, without precluding other uses. [STANDARDS-TRACK]",
  "authors": [
    "B. Davie",
    "B. Briscoe",
    "J. Tay"
  ],
  "organizations": [],
  "publication_date": "2008-01-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "tsvwg",
  "source_draft": "draft-ietf-tsvwg-ecn-mpls-02",
  "page_count": 21,
  "doi": "10.17487/RFC5129",
  "keywords": [
    "Diffserv",
    "Differentiated Services",
    "QOS",
    "ECN tunnel"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC3032"
    ],
    "updated_by": [
      "RFC5462"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc5129/",
    "html": "https://www.rfc-editor.org/rfc/rfc5129.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc5129.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc5129/"
  }
}