Skip to main content

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

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Lawrence W. Conroy
Last updated 2005-07-06
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

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 W. Conroy

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