{
  "draft": "draft-ietf-spring-segment-routing-policy-22",
  "doc_id": "RFC9256",
  "title": "Segment Routing Policy Architecture",
  "authors": [
    "C. Filsfils",
    "K. Talaulikar, Ed.",
    "D. Voyer",
    "A. Bogdanov",
    "P. Mattes"
  ],
  "format": [
    "XML",
    "TEXT",
    "HTML",
    "PDF"
  ],
  "page_count": "35",
  "pub_status": "PROPOSED STANDARD",
  "status": "PROPOSED STANDARD",
  "source": "Source Packet Routing in Networking",
  "abstract": "Segment Routing (SR) allows a node to steer a packet flow along any path. Intermediate per-path states are eliminated thanks to source routing. SR Policy is an ordered list of segments (i.e., instructions) that represent a source-routed policy. Packet flows are steered into an SR Policy on a node where it is instantiated called a headend node. The packets steered into an SR Policy carry an ordered list of segments associated with that SR Policy.\n\n This document updates RFC 8402 as it details the concepts of SR Policy and steering into an SR Policy.",
  "pub_date": "July 2022",
  "keywords": [
    "Segment Routing",
    "SR Policy",
    "SR-MPLS",
    "SRv6",
    "Traffic Engineering"
  ],
  "obsoletes": [],
  "obsoleted_by": [],
  "updates": [
    "RFC8402"
  ],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC9256",
  "errata_url": null
}