IPv6 Operations (v6ops)J. Massar
Internet-DraftUnfix / SixXS
Expires: January 12, 2006July 11, 2005

IPv6 Tunnel Discovery


Status of this Memo

By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.

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

The list of Internet-Draft Shadow Directories can be accessed at

This Internet-Draft will expire on January 12, 2006.

Copyright Notice

Copyright © The Internet Society (2005).


This document defines how to discover tunnel services using the _service domain.

Table of Contents

1.  Requirements notation
2.  Introduction
3.  Entries in the _service domain
4.  Security Considerations
5.  IANA Considerations
6.  Normative References
§  Author's Address
§  Intellectual Property and Copyright Statements


1. Requirements notation

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).


2. Introduction

When a user requires IPv6 connectivity in a IPv4-only or IPv4 connectivity in a IPv6-only environment, currently a user has to find out where to find a IPv6 or IPv4 provider herself or use 6to4.

This document describes a way how organisations can easily document the location of their services and have local users automatically make use of them.


3. Entries in the _service domain

The following records are possible to be inserted in the organisations _service domain [SERVICE] (Massar, J., “The _service domain and prefix,” July 2005.).

This example mentions to the user to try the TSP and TIC [TIC] (Massar, J., “TIC - Tunnel Information Control Protocol,” January 2004.) protocol first, them having equal weight. When that fails the user can use the website for more information.

_http._tcp            PTR     Example._http._tcp
Example._http._tcp    SRV     42   100    80   www

_https._tcp           PTR     Example._https._tcp
Example._https._tcp   SRV     13   100   443   ssl

; Tunneling Services (Configuration etc)
_tic._tcp             SRV     10   100  3874   tic
_tsp._tcp             SRV     10   100  3653   tsp

; _service domain entries
_service              TXT     "Example"
_website._service     PTR     Example._https._tcp
                      PTR     Example._http._tcp
_ipv6-tunnel._service PTR     _website._service
                      PTR     _tic._tcp
                      PTR     _tsp._tcp

tic                   A
tsp                   A
ssl                   A
www                   A


4. Security Considerations

There are no additional security considerations except the ones already given for the _service domain and prefix.


5. IANA Considerations

There are no considerations for IANA


6. Normative References

[RFC2119] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML).
[SERVICE] Massar, J., “The _service domain and prefix,” draft-massar-dnsop-service-00 (work in progress), July 2005.
[TIC] Massar, J., “TIC - Tunnel Information Control Protocol,” draft-massar-v6ops-tic-00 (work in progress), January 2004.


Author's Address

  Jeroen Massar
  Unfix / SixXS
  Hofpoldersingel 45
  Gouda 2807 LW


Intellectual Property Statement

Disclaimer of Validity

Copyright Statement