The AddressOrPrefix Derived AVP Data Format For Diameter
draft-taylor-dime-addressorprefix-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tom Taylor | ||
| Last updated | 2015-01-26 (Latest revision 2014-07-25) | ||
| 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
Section 4.3.1 of the Diameter base specification [RFC6733] defines a number of derived AVP data formats. This collection includes the Address format, which is suitable for encoding complete addresses. In some potential applications, however, there is a requirement to encode a prefix rather than a complete address. This document defines the AddressOrPrefix derived AVP data format, modelled after the Address format defined in [RFC6733], but allowing the same AVP to represent a prefix of any length up to a full address. This document updates RFC 6733.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)