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

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

Copyright Notice

Copyright © The Internet Society (2005).

Abstract

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.

$ORIGIN example.net.
_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       192.0.2.42
tsp                   A       192.0.2.13
ssl                   A       192.0.2.80
www                   A       192.0.2.80

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

Author's Address

Intellectual Property Statement

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.

Disclaimer of Validity

This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Copyright Statement

Copyright © The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

Acknowledgment

Funding for the RFC Editor function is currently provided by the Internet Society.