Interface to the Routing System
charter-ietf-i2rs-00-01

Working Group Name:
Interfaces to the Routing System (I2RS)

IETF Area:
Routing Area

Chair(s):
TBD
Routing Area Director(s):
Adrian Farrel <adrian@olddog.co.uk>
Routing Area Advisor:
Adrian Farrel <adrian@olddog.co.uk>
Operations Area Advisor:
TBD

Mailing Lists:
General Discussion: i2rs@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/i2rs
Archive: http://www.ietf.org/mail-archive/web/i2rs/current/maillist.html

Description of Working Group:

A routing system is all or part of a routing network such as an interface, a collection of
interfaces, a router, or a collection of routers. Interfaces to the Routing System (I2RS)
facilitate real-time or event driven interaction with the routing system. These allow
information, policies, and operational parameters to be injected into and retrieved (as
read or notification) from the routing system while retaining data consistency and
coherency across the routers and routing infrastructure, and between multiple
interactions with the routing system.

The I2RS working group works to develop a framework and architecture that will
enable specific use cases, and lead to an understanding of the informational models
and requirements for encodings and protocols. Small and well-scoped use cases are
critical to constrain the scope of the work and achieve sufficient focus for the working
group to deliver successfully. Initial work within the working group will be limited to
within a single administrative domain.

The working group is chartered to work on the following items:

• Architecture and framework for I2RS including considerations of policy and security

• Tightly scoped key use cases for operational use of I2RS. These use cases will
  include at least:
  o Interactions with the RIB.
  o Association of routing policies with routing state.
  o The ability to extract information about topology from the
  network. Injection and creation of topology will not be
  considered as an initial work item.

• Other use cases may be adopted by the working group only after milestones have
  been added to the charter page.

• Abstract information models consistent with the use cases.

• Requirements for I2RS protocols and encoding languages.

• An analysis of existing IETF and other protocols and encoding languages against the
  requirements.

The working group is not currently chartered to develop protocols, encoding
languages, or data models. The objective of this work effort is to arrive at common
standards for these items, but these items are dependent on the progress of the topics
listed above. Work for these items will be conducted in this working group only after a
re-charter, and/or may be carried out in another working group with specific
responsibility for the protocol or encoding language.

Goals and Milestones:

: Request publication of an Informational document defining the problem statement
: Request publication of an Informational document defining the architecture framework
: Request publication of an Informational document defining general RIB-based use cases
: Request publication of an Informational document defining policy-related use cases
: Request publication of an Informational document defining topology use cases
: Request publication of an Informational document defining the protocol requirements
: Request publication of an Informational document defining encoding language requirements
: Request publication of a Standards Track document defining a general information model
: Request publication of a Standards Track document defining an information model for RIB-
based use cases
: Request publication of a Standards Track document defining an information model for
policy-related use cases
: Request publication of a Standards Track document defining an information model for
topology use cases
: Request publication of an Informational document providing an analysis of existing IETF and
other protocols and encoding languages against the requirements
: Consider re-chartering