idnits 2.17.1 draft-kessens-ride-referencing-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 122 has weird spacing: '...Kessens et. a...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '1' is defined on line 122, but no explicit reference was found in the text -- No information found for draft-ride-classes - is the name correct? -- Possible downref: Normative reference to a draft: ref. '1' Summary: 9 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force David Kessens 2 Draft ISI 3 Expires February 1998 Wilfried Woeber 4 ACONET 5 David Conrad 6 APNIC 8 RIDE referencing 10 Status of this Memo 12 This document is an Internet-Draft. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its areas, 14 and its working groups. Note that other groups may also distribute 15 working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet- Drafts as reference 20 material or to cite them other than as ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check the 23 ``1id-abstracts.txt'' listing contained in the Internet- Drafts 24 Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 25 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 26 ftp.isi.edu (US West Coast). 28 Abstract 30 This document describes two variants of a proposal on how to find 31 information regarding some critical resources (domain names, IP 32 addresses and routing registry information) on the Internet. The 33 proposed solution uses globally unique registry identifiers that are 34 derived from a domain name in use by a registry. 36 Introduction 38 use your domain name as the global registry identifier 40 register in DNS where to query for the data 42 query the appropriate server using the local identifier 44 Draft RIDE referencing August 1997 46 Discussion 48 Advantage: 50 no central authority needed 52 Disadvantage: 54 the same thing. 56 Variant of the prososal: 58 double tree. IANA managed registries.int tree. 60 Detailed proposal 62 globally unique registry identifier 64 local to the registry unique identifier 66 example: KH1-ARIN 68 KH1 is local identifier ARIN is global registry identifier (last part 69 of domain name can possibly be omitted) 71 example: ISI-DOM 73 suffix is not globally unique 75 ISI-DOM is local identifier INTERNIC is global identifier 77 What do we store in DNS? 79 - server, protocol and protocol options - what kind of data is 80 available: 81 IPv4 193/8, 194/8, 195/8, 62/8 82 Domain .NOM, .STORE, ... 83 AS 100-300, 1000-2000 85 Note: IANA is authoritive for most of this data! 87 Which records to use: new record, TXT record, kitchen sink, reusing 88 old record 90 Security considerations 92 The two different schemas described here have somewhat different 93 properties regarding security. 95 Draft RIDE referencing August 1997 97 The IANA delegated model is in principle a very secure way of 98 providing identifiers that indeed point to the registry that contains 99 authoritive data regarding the allocation of Internet resources, 100 provided that DNS security mechanisms get implemented soon. The 101 situation for contact information pointers is somewhat different. 102 While the IANA delegated model provides trusted pointers to trusted 103 repositories of such data, anybody has the ability to register 104 whatever contact data they want to such a trusted registry, and thus 105 not providing much extra trust in the data itself. The distributed 106 approach has no guarantees whatsoever that one can trust that a 107 pointer points to a trusted party, since their is no system in place 108 that checks if registries are trustable. However, the poiters itself 109 are reliable provided that DNSSEC is widely used. Also, the RIDE 110 mechanisms itself provides ways of retrieving the pointed to data and 111 letting an individual registry decide after parsing the data if it 112 contains enough and good enough information to accept the reference. 114 Acknowledgments 116 We would like to thank Carol Orange and everybody that contributed to 117 the work of the RIDE IETF working group in general, for their various 118 comments and suggestions. 120 References 122 [1] D. Kessens et. al., draft-ride-classes-00.txt, 123 March 1997 125 Author's Address: 127 David Kessens, 128 ISI 129 4676 Admiralty Way, Suite 1001 130 Marina del Rey, CA 90292-6695 131 USA 132 davidk@ISI.EDU 134 Wilfried Woeber 135 Vienna University 136 Computer Center - ACOnet 137 Universitaetsstrasse 7 138 A-1010 Vienna 139 Austria 140 Woeber@CC.UniVie.ac.at 142 David Conrad 144 Draft RIDE referencing August 1997 146 APNIC 147 Japan 148 davidc@apnic.net