DNS Update Based Service Function Update
draft-xu-dnssd-sf-update-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Xiaohu Xu | ||
| Last updated | 2014-11-17 (Latest revision 2014-05-16) | ||
| 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
In a Service Function Chaining (SFC)-enabled domain, the Domain Name System (DNS) can be used as a mechanism for Service Function (SF) auto-discovery [I-D.xu-dnssd-sf-discovery]. Since the information associated with SF instances (e.g., capacity and current load) would change dynamically, the information associated with SF instances which is stored in the DNS sever needs to be updated accordingly. This document describes how to use the DNS UPDATE mechanism [RFC2136] to dynamically update the corresponding Resource Records (RRs) for SF instances.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)