Document expiration date: 3 May 2001                       L. Yeoh



          Top Level DNS Name for addressing by physical context
                     <draft-yeoh-tldhere-00.txt>



INTERNET-DRAFT

     This document is an Internet-Draft and is in full conformance
     with all provisions of Section 10 of RFC2026.

     Internet-Drafts are working documents of the Internet Engineering
     Task Force (IETF), its areas, and its working groups.  Note that
     other groups may also distribute working documents as
     Internet-Drafts.

     Internet-Drafts are draft documents valid for a maximum of six
     months and may be updated, replaced, or obsoleted by other
     documents at any time.  It is inappropriate to use Internet-
     Drafts as reference material or to cite them other than as
     "work in progress."


     The list of current Internet-Drafts can be accessed at
     http://www.ietf.org/ietf/1id-abstracts.txt


     The list of Internet-Draft Shadow Directories can be accessed at
     http://www.ietf.org/shadow.html.

Status of this Memo

     Distribution of this memo is unlimited.

Copyright Notice

     Copyright (C) The Internet Society (2000).  All Rights Reserved.

Abstract

This document proposes the reservation of a special use TLD ( .here. ) to
allow a more convenient addressing of devices by general physical location
or context.

. Introduction

As wireless networking and devices become more common there may be a need
for a convenient way to address hosts by physical location or context,
especially when the users themselves are using mobile or wearable devices.

A step towards this could be by reserving a special public use TLD such as
.here. Then this TLD can be independently hosted at various locations, so
that each resulting .here domain falls under the context of that particular
location.

. Example usage of .here TLD

As an example a user could obtain a list of registered devices in a
particular room or building by visiting https://all.here/ or perhaps just
https://here/. Other forms could include https://who.here/ and
https://what.here/

Say if the user wishes to control an air conditioner in a room, the user
could visit https://airconditioner.here/ for the control page. The user
could also "bookmark" popular settings such as
https://airconditioner.here/settemp?celsius=25 and use it from room to room
(assuming the air conditioners accept the same parameters).

Users of wearable devices could also address and access each other in a
similar manner after registering with the location - e.g.
https://lyeoh.here/sendobjectform or https://somebody.here/getobject?id=12345

. Various Considerations

Users could get the wrong address depending on how the default domain
search is implemented - e.g. xxxx.here first, then xxxx.mydomain.com or
vice versa. Also, it should be assumed that parties controlling the
physical location can attempt to spoof or subvert communications.

Specifying .here. does not guarantee locality. Users may inadvertently or
intentionally access devices at a different physical location.

Third parties could reserve a similar TLD (e.g. .her.) in order to catch
typographical errors or unsuspecting users. As .her. and .he. may well
become future TLDs, perhaps a less vulnerable name than .here should be
used instead. A less elegant alternative is to also reserve the typos, but
the Gere's (e.g. Richard) of the world may protest.

Author's Address

 Lincoln Yeoh
 20, Jalan 225
 46100 Petaling Jaya
 Malaysia

 Phone: +60 3 7874 3422
 EMail: lyeoh@pop.jaring.my

References

 [RFC2606] D. Eastlake and A. Panitz, "Reserved Top Level DNS Names",
RFC2606, June 1999.

Document expiration date: 3 May 2001