Non-Terminal NAPTR Processing: A Modest Proposal
draft-conroy-enum-modestproposal-00

Document Type Expired Internet-Draft (individual)
Last updated 2005-07-06
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
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-conroy-enum-modestproposal-00.txt

Abstract

Recent Discussions within the IETF and in other fora have highlighted differences in interpretation of the set of standards associated with ENUM and DDDS, on which it relies. Specifically, the operation and semantics surrounding support for non-terminal NAPTRs has led to some confusion. This document is an attempt to add clarification to non- terminal NAPTR processing. In this, it clarifies RFC3403. A subsequent document will build on this one to extend RFC3761 further, permitting registration of non-terminal Enumservices.

Authors

Lawrence Conroy (lconroy@insensate.co.uk)

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