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

IETF · RFC · RFC4364

RFC4364 · BGP/MPLS IP Virtual Private Networks (VPNs)

BGP/MPLS IP Virtual Private Networks (VPNs)

This document describes a method by which a Service Provider may use an IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This method uses a "peer model", in which the customers' edge routers (CE routers) send their routes to the Service Provider's edge routers (PE routers); there is no "overlay" visible to the customer's routing algorithm, and CE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes. [STANDARDS-TRACK]

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

This document describes a method by which a Service Provider may use an IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This method uses a "peer model", in which the customers' edge routers (CE routers) send their routes to the Service Provider's edge routers (PE routers); there is no "overlay" visible to the customer's routing algorithm, and CE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes. [STANDARDS-TRACK]

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

obsoletes: RFC2547

updated_by: RFC4577, RFC4684, RFC5462

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

Полные импортированные сведения карточки
{
  "id": "RFC4364",
  "number": 4364,
  "title_en": "BGP/MPLS IP Virtual Private Networks (VPNs)",
  "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 a method by which a Service Provider may use an IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This method uses a \"peer model\", in which the customers' edge routers (CE routers) send their routes to the Service Provider's edge routers (PE routers); there is no \"overlay\" visible to the customer's routing algorithm, and CE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes. [STANDARDS-TRACK]",
  "authors": [
    "E. Rosen",
    "Y. Rekhter"
  ],
  "organizations": [],
  "publication_date": "2006-02-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": "rtg",
  "area_ru": "Маршрутизация",
  "working_group": "l3vpn",
  "source_draft": "draft-ietf-l3vpn-rfc2547bis-03",
  "page_count": 47,
  "doi": "10.17487/RFC4364",
  "keywords": [
    "service provider",
    "ip backbone",
    "ce router",
    "pe router",
    "border",
    "gateway",
    "protocol",
    "multiprotocol",
    "label",
    "switching",
    "architecture",
    "virtual",
    "private",
    "networks"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC2547"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC4577",
      "RFC4684",
      "RFC5462"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4364/",
    "html": "https://www.rfc-editor.org/rfc/rfc4364.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4364.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4364/"
  }
}