The AddressOrPrefix Derived AVP Data Format For Diameter
draft-taylor-dime-addressorprefix-00

Document Type Expired Internet-Draft (individual)
Author Tom Taylor 
Last updated 2015-01-26 (latest revision 2014-07-25)
Stream (None)
Formats
Expired & archived
plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-taylor-dime-addressorprefix-00.txt

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

Tom Taylor (tom.taylor.stds@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)