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

IETF · RFC · RFC4303

RFC4303 · IP Encapsulating Security Payload (ESP)

IP Encapsulating Security Payload (ESP)

This document describes an updated version of the Encapsulating Security Payload (ESP) protocol, which is designed to provide a mix of security services in IPv4 and IPv6. ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality. This document obsoletes RFC 2406 (November 1998). [STANDARDS-TRACK]

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

This document describes an updated version of the Encapsulating Security Payload (ESP) protocol, which is designed to provide a mix of security services in IPv4 and IPv6. ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality. This document obsoletes RFC 2406 (November 1998). [STANDARDS-TRACK]

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

obsoletes: RFC2406

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

Полные импортированные сведения карточки
{
  "id": "RFC4303",
  "number": 4303,
  "title_en": "IP Encapsulating Security Payload (ESP)",
  "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": "This document describes an updated version of the Encapsulating Security Payload (ESP) protocol, which is designed to provide a mix of security services in IPv4 and IPv6. ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality. This document obsoletes RFC 2406 (November 1998). [STANDARDS-TRACK]",
  "authors": [
    "S. Kent"
  ],
  "organizations": [],
  "publication_date": "2005-12-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": "sec",
  "area_ru": "Безопасность",
  "working_group": "ipsec",
  "source_draft": "draft-ietf-ipsec-esp-v3-10",
  "page_count": 44,
  "doi": "10.17487/RFC4303",
  "keywords": [
    "ESP",
    "ipsec",
    "internet",
    "protocol",
    "encapsulating",
    "security",
    "ipv4",
    "ipv6",
    "ip security",
    "confidentiality",
    "authentication",
    "integrity",
    "anti-replay",
    "ah",
    "ip authentication header",
    "ike",
    "internet key exchange",
    "ikev2",
    "esn",
    "extended sequence number"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC2406"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4303/",
    "html": "https://www.rfc-editor.org/rfc/rfc4303.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4303.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4303/"
  }
}