# Re: The Path URN Specification

Rich Salz (rsalz@osf.org)
Mon, 20 Mar 95 14:54:16 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Daniel LaLiberte: "Re: The Path URN Specification"
- Previous message: Roy T. Fielding: "Relative URL draft 06"
- Maybe in reply to: Daniel LaLiberte: "The Path URN Specification"
- Next in thread: Daniel LaLiberte: "Re: The Path URN Specification"
- Reply: Daniel LaLiberte: "Re: The Path URN Specification"

    From: Rich Salz <rsalz@osf.org>

    Date: Mon, 20 Mar 95 14:54:16 -0500

    Message-Id: <9503201954.AA23140@sulphur.osf.org>

    To: owner-uri@bunyip.com, uri@bunyip.com

    Subject: Re: The Path URN Specification

For example, if a
list of one-level down subdomains could be requested, no separate list
need be maintained in the TXT records (hmm, this might be available
already with the "ls" query).
This would probably force a TCP query.

When you look up a domain name, DNS logically starts at the top of the
tree and works its way down.
No, DNS is bottom up.

- Next message: Daniel LaLiberte: "Re: The Path URN Specification"
- Previous message: Roy T. Fielding: "Relative URL draft 06"
- Maybe in reply to: Daniel LaLiberte: "The Path URN Specification"
- Next in thread: Daniel LaLiberte: "Re: The Path URN Specification"
- Reply: Daniel LaLiberte: "Re: The Path URN Specification"