Status of this Memo

   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.

   This Internet-Draft will expire on March 6, 2004.

Copyright Notice

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

Abstract

This document describes a way in which individuals and vendors can define URI schemes in a way that avoids name collisions, but with relaxed registration requirements. This is done by allowing URI schemes that start with "vnd-" or "prs-", analogous to similar mechanism MIME media types.

この文書は、名前の衝突を避けられる方法で、 登録要件を緩和しつつ、個人や販売者が URI 方式を定義できる方法を記述します。 これは MIME 媒体型の同様な仕組みと同じように、 vnd- や prs- から始まる URI 方式を認めることによって行います。

Note

Discuss this document on uri@w3.org. A HTML version of this document can be found at http://larry.masinter.net/vnduri.html.

この文書について MAIL:uri@w3.org で議論して下さい。 この文書の HTML 版は http://larry.masinter.net/vnduri.html で見つかります。

1. Introduction

The registration process for URI schemes, described in RFC 2717 [2], requires IESG review and approval of all proposed scheme names within the "IETF tree", which encompasses simple, short, often descriptive URI scheme names (such as http:, fax:, or mailto:).

URI 方式の登録手続きは、 RFC 2717 に記述されていますが、 単純で短くてしばしば記述的な URI 方式名 (たとえば http:, fax:, mailto:) を取巻く「IETF木」内に提案する方式名はすべて IESG の評価と承認を必要としています。

However, there are circumstances where it is desirable to allocate a URI scheme name outside of this process. This document establishes alternative trees, "vnd-" and "prs-", corresponding to the similar concept for MIME type registrations[4]. The rules for use and registration of URI schemes with in these trees are intended to be analogous those for the corresponding MIME type trees.

しかし、この手続きの外で URI 方式名を割当てることが望ましい場面もあります。 この文書は、 MIME 型登録における同様な概念に対応する代替木 vnd- および prs- を確立します。 これらの木での URI 方式の使用と登録のための規則は対応する MIME 型木のものと似た物となっているつもりです。

The "vnd-" tree is used for URI schemes associated with available products or services; "vendor" or "producer" are construed as equivalent and broadly. The registration belongs to the vendor or organization producing software or offering a service that utilizes the URI scheme. Registration in the vendor tree is distinguished by the leading "vnd-", followed, at the discretion of the registration, either by the scheme name or (preferably) by an IANA-approved designation of the producer's name, followed by the specific scheme name. Designations of producers should match those used for media types, and follows the same criteria.

vnd- 木は利用可能な製品やサービスに関連付けられた URI 方式に使用します。「販売者」や「製造者」は等しく広く構成します。 登録はその URI 方式を利用するソフトウェアを生産したりサービスを提供したりする販売者や組織に属します。 販売者木での登録は、最初に vnd- が来た後に、 登録の裁量で、方式名を続けるか、または (できれば) IANA が承認した製造者名称と、それに続けて特定方式名とします。 製造者名称は媒体型に使用するものと一致するべきで、同じ適合基準に従います。

Similarly, the "prs-" tree is intended for URI schemes used experimentally or as individual contributions. The owner of "personal" registrations and associated specifications is the person or entity making the registration, or one to whom responsibility has been transferred as described below.

同様に、 prs- 木は実験的にまたは個人的貢献として使用する URI 方式を意図しています。「個人」登録および関連付けられた仕様書の所有者は登録を行った、または後述の通り責任を移管された個人または団体です。

Note that earlier drafts of this document suggested using "." as the delimiter between "vnd" and the URI scheme. However, RFC 2717 [2] reserved the "-" character for non-IETF registrations (and not "."), so the delimiter was changed for compatibility. Because these earlier drafts were available for several years, however, there may be some URI schemes with "vnd." still in use.

この文書の以前の原案では vnd と URI 方式の間の区切子として . を使用して提案していたことに注意して下さい。 しかし、 RFC 2717 は非 IETF 登録に (. ではなく) - を予約しておりますから、 互換性のために区切子を変更しました。しかし、 以前の原案は幾年もの間利用可能でしたから、 vnd. のついた URI 方式が依然使用されているかもしれません。

2. Syntax

The general syntax for these new trees follows the syntax recommended in RFC 2717 [2]:

これらの新しい木の一般的構文は RFC 2717 で推奨されている構文に従います。

• scheme = ("vnd-" / "prs-") [ vendor-id "-" ] scheme-id
• vendor-id = ALPHA *(ALPHA / DIGIT / "+" )
• scheme-id = ALPHA *(ALPHA / DIGIT / "+" / "-" / "." )

3. Requirements for Scheme Name Registration

4. Security Considerations

The vendor identified by the vendor-id part of the URI scheme name should be consulted for any information regarding the URI scheme and its implementation. To that end, vendors must provide a point of contact that can be reasonably authenticated, for instance, common business contact information (business address, telephone number, etc.). (This is addressed in the registration section above.)

URI 方式とその実装に関する情報は URI 方式名の vendor-id 部分で識別される販売者に問い合わせるべきです。 そのために、販売者はかなり確実な接触点、たとえば代表接触情報 (住所、電話番号など) を提供しなければなりません。 (これは前の登録の章で触れています。)

The registration process encourages vendors to analyze and disclose the security implications of using particular URI schemes. Unregistered schemes or those without appropriate security considerations may be unsafe to use.

登録手続きは販売者に特定 URI 方式を使用することによる安全上の影響を調査し公開するようにお勧めします。 未登録方式や適切な安全上の考察の無い方式は使用すると安全でないかもしれません。

5. IANA Considerations

IANA currently maintains a registry of URI scheme names, per the requirements of RFC 2717. Scheme names established under this process should also be entered in that registry, when requested.

IANA は現在 URI方式名の登録簿を RFC 2717 の要件によって維持しています。 この手続きの下で確立した方式名も要求された時にその登録簿に入れるべきです。

IANA should maintain a separate registry of vendor-id strings, relating the vendor-id to the vendor information (business contact information, etc.) provided in the registration. The vendor-id string list should be used also for vendor strings used in media types, as per RFC 2048. IANA should reject a vendor-id registration if it duplicates an existing registration, seems inappropriate, confusing, misleading, or too similar to another registered vendor-id, at IANA's discression. IANA may offer an alternative vendor-id string that IANA considers more appropriate.

IANA は別途 vendor-id 文字列の登録簿を、 登録で提供された販売者情報 (会社接触情報など) を vendor-id と関連させて維持するべきです。 vendor-id 文字列一覧は RFC 2048 による媒体型で使用される販売者文字列にも使用するべきです。 IANA は、 IANA の裁量により、既存の登録と重複していたり、 不適切に見えたり、他の登録 vendor-id と混乱したり誤解したり似すぎたりする vendor-id を却下するべきです。 IANA は IANA がより適切と考える代替 vendor-id 文字列を提案しても構いません。

A party whose vendor-id registration has been rejected or modified may ask for review of the registration by the IESG, in the manner described in RFC 2026, section 6.5.

vendor-id 登録が却下されたり修正されたりした団体は RFC 2026 6.5 節に記述された方法で IESG に登録の評価を依頼して構いません。

6. Registration forms

Form for vendor information:

登録者情報の書式

      Vendor-ID:        proposed identifier
      Name:      formal name of organization
      Address:   full name of organization
      Telephone: full telephone number
      Type:      type of organization (corporation, educational
                   institution, etc.)
      Contact Information:  name of contact person and location information

The form for scheme names follows RFC 2717, section 6.0.

RFC 2717 6.0 節に従った方式名の書式

       Scheme name:
       Scheme syntax:
       Character encoding considerations:
       Intended usage:
       Applications and/or protocols which use this URL scheme name:
       Interoperability considerations:
       Security considerations:
       Relevant publications:

Normative References

   [1]  Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
        Identifiers (URI): Generic Syntax", RFC 2396, August 1998.

Informative References

   [2]  Petke, R. and I. King, "Registration Procedures for URL Scheme
        Names", RFC 2717, November 1999.

   [3]  Masinter, L., Alvestrand, H., Zigmond, D. and R. Petke,
        "Guidelines for New URL Schemes", RFC 2718, November 1999.

   [4]  Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet
        Mail Extensions (MIME) Part Four: Registration Procedures", RFC
        2048, November 1996.

Authors' Addresses

   Ian King
   Microsoft Corporation
   One Microsoft Way
   Redmond, WA  98052-6399
   US

   Phone: +1 425 703 2293
   EMail: iking@microsoft.com

   Larry Masinter
   Adobe Systems Incorporated
   345 Park Ave
   San Jose, CA  95110
   US

   Phone: +1 408 536 3024
   EMail: LMM@acm.org
   URI:   http://larry.masinter.net

Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property 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; neither does it represent that it
   has made any effort to identify any such rights. Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11. Copies of
   claims of rights made available for publication 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 implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard. Please address the information to the IETF Executive
   Director.

Full Copyright Statement

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

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assignees.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS 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.

Acknowledgment

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

License

RFCのライセンス。

メモ