DLEP Destination Service Announcement
draft-taylor-manet-dlep-dsa-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rick Taylor | ||
| Last updated | 2018-04-19 (Latest revision 2017-07-24) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
When using the Dynamic Link Exchange Protocol (DLEP) [RFC8175] to bootstrap neighbour discovery for routing protocols there is no indication in the core DLEP protocol of the services of the router announced at a destination. This forces an implementation to either rely on a priori configuration or use heuristic probing of well-known ports to discover potential routing peers. This document defines an extension to DLEP to enable a router to advertise its active services to its peer modem, allowing a connected remote modem to announce the services of a router in a DLEP destination message to its peer, removing the need for service discovery between routing peers. The mechanism is designed to be sufficiently generic to allow the advertisement of network services beyond routing protocols, enabling the fast bootstrapping of other protocols such as messaging protocols or header compression.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)