Protocol Action: The Naming Authority Pointer (NAPTR) DNS Resource Record to Proposed Standard
The IESG <iesg-secretary@ietf.org> Mon, 18 September 2000 15:06 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10701; Mon, 18 Sep 2000 11:06:47 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id LAA07648 for ietf-123-outbound.10@ietf.org; Mon, 18 Sep 2000 11:05:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id KAA07611 for <all-ietf@loki.ietf.org>; Mon, 18 Sep 2000 10:58:35 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10166; Mon, 18 Sep 2000 10:58:35 -0400 (EDT)
Message-Id: <200009181458.KAA10166@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>, IANA <iana@iana.org>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: urn-ietf@lists.internic.net.cnri.reston.va
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: The Naming Authority Pointer (NAPTR) DNS Resource Record to Proposed Standard
Date: Mon, 18 Sep 2000 10:58:35 -0400
Sender: scoya@cnri.reston.va.us
The IESG has approved the Internet-Draft 'The Naming Authority Pointer (NAPTR) DNS Resource Record' <draft-ietf-urn-naptr-rr-04.txt> as a Proposed Standard. This document is the product of the Uniform Resource Names Working Group. The IESG contact persons are Ned Freed abd Patrik Faltstrom. This document updates RFC 2168. Technical Summary This document updates RFC 2168, and replaces all parts of RFC 2168 which have to do with the definitions of the NAPTR resource record definition. This document further adds the flag "u" which makes it possible to return a URI as a result of a rewrite rule. Working Group Summary The working agreed upon on how to move RFC 2168 forward, which includes breaking out the definition of the actual resource record type, the NAPTR, which is defined in RFC 2168. No issues regarding the definitions of the NAPTR were rised on the mailing list, but further work is needed regarding the work on RFC 2168 which talks about URN. Protocol Quality The spec was reviewed for the IESG by Patrik Faltstrom. Note to RFC Editor: Please make two changes in section 2 (NAPTR RR Format): From: Domain TTL Class Order Preference Flags Service Regexp Replacement to: Domain TTL Class Type Order Preference Flags Service Regexp Replacement and From: Class Standard DNS meaning.[1] to: Class Standard DNS meaning.[1] Type The Type Code[1] for NAPTR is 35. Finally, please append the following at the end of Section 3: IMPLEMENTATION NOTE Implementation of the regexp algorithm is dependent on the charset of the original string provided by the application. A charset of US-ASCII is assumed; specific application profiles of NAPTR may specify an alternate charset if appropriate.