Framework documents Joel Halpern IETF 84 Routing Area Open Meeting 1 Drafts included draftatlasirsproblemstatement00 draftwardirsframework00 draftatlasirspolicyframework00 ID: 578758
Download Presentation The PPT/PDF document "Interface to The Internet Routing System..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Interface to The Internet Routing System (IRS)Framework documents
Joel Halpern
IETF 84 – Routing Area Open Meeting
1Slide2
Drafts includeddraft-atlas-irs-problem-statement-00draft-ward-irs-framework-00draft-atlas-irs-policy-framework-00draft-dimitri-irs-arch-frame-00
Draft authors: Alia Atlas, Thomas Nadeau, David Ward
Susan Hares, Joel HalpernDimitri Papadimitriou Martin Vogoureux
Wounter Taverneir, Didier Cole
IETF 84
– Routing Area Open Meeting
2Slide3
What’s the Problem?Applications Need To DynamicallyAnd Knowledgeably, based on:Topology (active & potential)EventsTraffic MeasurementsEtc.Augment Routing, based on:
PolicyFlow & Application AwarenessTime & External Changes
3
Network
Application
Feedback Loop:
Control & InformationSlide4
What’s Needed for the Routing System?Data Models for Routing & Signaling StateRIB Layer: unicast RIBs, mcast RIBs, LFIB, etc.Protocols: ISIS, OSPF, BGP, RSVP-TE, LDP, PIM, mLDP, etc.Related: Policy-Based Routing, QoS, OAM, etc.Framework of Integrating of External Data into RoutingIndirection, Policy, Loop-DetectionFiltered Events for Triggers, Verification & Learning Changed Router StateData Models for StateTopology model, interface, Measurements, etc.Device-Level and Network-Level Interface & Protocol(s)
4Slide5
Main ConcernsStandard data-modelsclear self-describing semanticsSufficient coverage for use-cases needing feedbackApplications aren’t routers – so can’t need to implement a list of routing/signaling protocolsGood security, authorization, & identity mechanismsScaling and responsiveness:Multiple applicationsMany operations per second
Significant data to export, even when filtered
5Slide6
D
IRS Framework at IETF 84
Application
6
IRS Client
Policy Database
Subscription
to Events and
Configuration Templates for Measurement,
Events
,
QoS, OAM, etc
…
IRS Agent
Routing and Signaling Protocols
Topology
Database
RIB Manager
FIB Manager and Data Plane
IRS Protocol
Router
Application
Application
IRS ClientSlide7
3 Key aspects - P.A.L.Programmatic interface – asynchronous and fast Access to information – IRS gives access to information and state that is not usually configured or modeled. Learn additional filtered Events 7Slide8
IRS Interface Key AspectsMultiple Simultaneous Asynchronous OperationsConfiguration - is not reprocessed Duplex CommunicationAsynchronous, Filtered EventsTopologic Information (IGP, BGP, VPN, active/potential)High-ThroughputHighly ResponsiveMulti-Channel (readers/writers)
Capabilities Negotiation/Advertisement (self-describing)
8Slide9
What IRS is notIRS is NOT:the only configuration mechanism a router will ever need,a direct replacement for existing routing/signaling protocols,the only way to read topology and router data that will ever be needed,solely limited to a single network device.9Slide10
IRS: Focused ScopeStart with a defined scope:Small set of data-models (RIB layer) for controlSet of events to support related use-casesData-model for topologyInvestigate protocol options for the interfaceConsider application-friendly paradigmsConsider extensions as well as new definitionsDefine set of motivating use-cases to drive this scope.10Slide11
IRS Policy Framework
Application
Policy Database
IRS Agent
Topology
Database
Application
Application
IRS
Commissioner
IRS Commissioner
Events &
OAM
b
a
Routing
&
Signaling Protocols
RIB Manager
FIB Manager & Data Plane
Policy Database
IRS Agent
Topology
Database
Events &
OAM
Routing
&
Signaling Protocols
RIB Manager
FIB Manager & Data Plane
ID
123
ID:
555
ID:
666
ID:
222
IRS
client
IRS
Client Slide12
Policy Framework 101Policy Definitions Identity Not tied to a single channel One per commissionerOne per agent Role Each commission has a security role Scope - what I can readInfluence – what I can write Resources what agent can consume Example: # of installs, # of events, # operationsPolicy – explicit and implicit
Explicit: what you configure Implicit: What’s implied in protocols or “doing the right thing” in configuration
Policy Actions ConnectivityNo need for active connection
State
Tied to Actions such as get this topology;
Priority
Commissioner gives 3 tasks: pull routes, status on interface 2, turn on interface 3 What’s the orderPrecedence DecisionsAssume configured a route 192.165.2/24
M
ultiple people use IR to move traffic for 192.165.2/24 short term
Who gets to install
what happens when they get done
What happens on a reboot
12Slide13
Q&A13Slide14
Why Policy Framework Help to take Use cases Data ModelsWhat is the scope and influence policy specified for a data model? How does implicit policy in associated routing system effect what IRS can do? AKA - Don’t break implied policyWhat explicit policy does model need? Why: KISS approach (Keep it simple stupid)Best default – because complexity costs Some IRS may require3 phase commit or Time related commits
14