WebSVN – oidplus – Diff – /trunk/plugins/publicPages/100_whois/whois/rfc/draft-viathinksoft-oidwhois-00.nroff



.in 0
 
.nf
.tl 'INTERNET-DRAFT''D. Marschall'
.tl 'Intended Status: Informational''ViaThinkSoft'
.tl 'Expires: <Expiry Date>''August 2020'
.fi
 
.\" Note. The ".tl" directive is used to generate the leading header 
.\" in Internet drafts. The information specified after ".tl" provides
.\" left, center and right components of a line separated by the ' character

 
OID-WHOIS is based on the WHOIS protocol specified in RFC\03912 [RFC3912].
 
During the request, the client sends a query beginning with "oid:", followed by an OID in dot-notation, as defined in RFC\03061, section 2 [RFC3061], but with the following differences:
 
(1) The OID MAY contain a leading dot.
 
(2) To query the root of the OID tree, the OID MUST be either missing or consisting only of a single dot.
 
Examples of valid queries are:
 

(2) "status" MUST be present and SHALL be one of the following values:
 
.in 7
"Information available" means that information about the OID is fully available.
 
"Information partially available" means that part of the information about the OID is not available.  Possible reasons could be that part of the information is redacted due to confidentiality, or the WHOIS service does only know basic information, while the full information can be found somewhere else (e.g. at a referred WHOIS service).  The field "attribute" MAY be used with the value "confidential".
 
"Information unavailable" means that the information about the OID is missing, redacted due to confidentiality, or otherwise unavailable.  The field "attribute" MAY be used with the value "confidential".
.in 3
 
(3) "name" (OPTIONAL) contains the name of the OID.  It SHOULD be as short as possible.

 
.in 7
Note: A line-break, to break up lines which are too long, as defined in section\03.1 ("Format and Encoding") SHALL NOT be used, otherwise, it would be ambiguous if the line-break was used to shorten the line, or if the line-break indicates a new value in case multiple OID-IRI notations are supplied.
.in 3
 
(9) "identifier" (OPTIONAL, multiple values allowed) contains an alphanumeric identifier ("NameForm") as defined in Recommendation ITU-T X.680 (2015) | ISO/IEC 8824-1:2015, clause 12.3 [X680].
 
(10) "standardized-id" (OPTIONAL, multiple values allowed) contains an alphanumeric identifier that has a standardized "NameForm", i.e. in ASN.1 notation, it can be written without its associated number.  See more information in Recommendation ITU-T X.680 (2015) | ISO/IEC 8824-1:2015, clause 32.7 [X680].
 
(11) "unicode-label" (OPTIONAL, multiple values allowed) contains a Non-integer Unicode label, as defined in Recommendation ITU-T X.680 (2015) | ISO/IEC 8824-1:2015, clause 12.27 [X680].
 

 
"no-identifiers" means that the RA is not allocating alphanumeric identifiers.
 
"no-unicode-labels" means that the RA is not allocating Non-integer Unicode labels.
 
"retired" means that the OID is withdrawn, revoked, retired, expired, etc.  Please consult Recommendation ITU-T X.660 (2011) | ISO/IEC 9834-1:2012 [X660] for more information about such cases.
.in 3
 
(15) "parent" (OPTIONAL) contains the OID of the nearest known parent OID, prepended by namespace identifier and double colon, i.e. "oid:".  It MAY be followed by additional human-readable information, e.g. a description or a list of ASN.1 identifiers.  There SHALL be at least 1 whitespace in between.
 
(16) "subordinate" (OPTIONAL, multiple values allowed) contains a list of subordinate OIDs, prepended by namespace identifier and double colon, i.e. "oid:".  It MAY be followed by additional human-readable information, e.g. a description or a list of ASN.1 identifiers.  There SHALL be at least 1 whitespace in between.

(2) "ra-status" MUST be present and SHALL be one of the following values:
 
.in 7
"Information available" means that information about this RA is fully available.
 
"Information partially available" means that part of the information is not available.  A possible reason could be that part of the information is redacted due to confidentiality.  The field "attribute" MAY be used with the value "confidential".
 
"Information unavailable" means that the data is missing (if the WHOIS service does only know the name of the RA and nothing else), redacted due to confidentiality or otherwise unavailable.  The field "attribute" MAY be used with the value "confidential".
.in 3
 
(3) "ra-contact-name" (OPTIONAL, multiple values allowed) contains the name of a person responsible for the allocation of subordinate OIDs, in case "ra" is a group or organization.
 
(4) "ra-address" (OPTIONAL) contains the physical location of the RA.  While a fully qualified postal address is recommended, the field can also just contain a rough location like city and country name, state and country name, or just the country name, etc.  The name of the country SHOULD always be present.
 
(5) "ra-phone" (OPTIONAL, multiple values allowed) contains a landline phone number of the Registration Authority.  It SHOULD be written in the international number format specified in Recommendation ITU-T E.164 (2010) [E164], e.g. +1 206 555 0100.
 
(6) "ra-mobile" (OPTIONAL, multiple values allowed) contains a mobile phone number of the Registration Authority.  It SHOULD be written in the international number format specified in Recommendation ITU-T E.164 (2010) [E164], e.g. +1 206 555 0100.
 

.ti 0
3.3  Digital Signature
 
If integrity/authenticity is required, the whole response can be signed, e.g. by using S/MIME, RSA, or PGP.  This document does not describe a mechanism for detecting which signature method was used.  The creation and verification of the signature are therefore implementation-specific and no interoperability regarding signature creation and validation is given at this time.
 
Depending on the signature method being used, various things need to be appended and/or prepended to the response.  These additional lines MUST be prepended by a percent sign ("%") to avoid that an application confuses these additional lines (e.g. lines belonging to a PGP header) with parts of the actual WHOIS response.
 
.ti 0
3.4  Date/Time Format
 
Date/Time references SHALL be formatted as described in section\03.4.1.

 
The original WHOIS protocol as defined in RFC\03912 [RFC3912] does not define any character set and there is no mechanism for indicating which character set is in use.
 
To enhance interoperability, this document specifies that the request and response MUST be UTF-8 encoded (as defined in RFC\03629 [RFC3629]), without Byte-Order-Mark (BOM).
 
The WHOIS service can define additional field names, but they SHOULD be written in the English language so that there is consistency with the field names defined in this document.
.bp
.ti 0
8  Security Considerations
 
(1) The knowledge of existence or information about some OIDs could be considered confidential.  In this case, the WHOIS service can either deny the existence of the requested OID (by setting the result to "Not found") or redact information in the Object-Section, as defined in section\03.2.2 "Object-Section".

Subversion Repositories oidplus

oidplus/trunk/plugins/publicPages/100_whois/whois/rfc/draft-viathinksoft-oidwhois-00.nroff – Rev 346 → 351

Rev 346		Rev 351
Line 16...		Line 16...
16	.in 0	16	.in 0
17		17
18	.nf	18	.nf
19	.tl 'INTERNET-DRAFT''D. Marschall'	19	.tl 'INTERNET-DRAFT''D. Marschall'
20	.tl 'Intended Status: Informational''ViaThinkSoft'	20	.tl 'Intended Status: Informational''ViaThinkSoft'
21	.tl 'Expires: <Expiry Date>''July 2020'	21	.tl 'Expires: <Expiry Date>''August 2020'
22	.fi	22	.fi
23		23
24	.\" Note. The ".tl" directive is used to generate the leading header	24	.\" Note. The ".tl" directive is used to generate the leading header
25	.\" in Internet drafts. The information specified after ".tl" provides	25	.\" in Internet drafts. The information specified after ".tl" provides
26	.\" left, center and right components of a line separated by the ' character	26	.\" left, center and right components of a line separated by the ' character
Line 144...		Line 144...
144		144
145	OID-WHOIS is based on the WHOIS protocol specified in RFC\03912 [RFC3912].	145	OID-WHOIS is based on the WHOIS protocol specified in RFC\03912 [RFC3912].
146		146
147	During the request, the client sends a query beginning with "oid:", followed by an OID in dot-notation, as defined in RFC\03061, section 2 [RFC3061], but with the following differences:	147	During the request, the client sends a query beginning with "oid:", followed by an OID in dot-notation, as defined in RFC\03061, section 2 [RFC3061], but with the following differences:
148		148
149	(1) The OID MAY contain a leading dot at the beginning.	149	(1) The OID MAY contain a leading dot.
150		150
151	(2) To query the root of the OID tree, the OID MUST be either missing or consisting only of a single dot.	151	(2) To query the root of the OID tree, the OID MUST be either missing or consisting only of a single dot.
152		152
153	Examples of valid queries are:	153	Examples of valid queries are:
154		154
Line 293...		Line 293...
293	(2) "status" MUST be present and SHALL be one of the following values:	293	(2) "status" MUST be present and SHALL be one of the following values:
294		294
295	.in 7	295	.in 7
296	"Information available" means that information about the OID is fully available.	296	"Information available" means that information about the OID is fully available.
297		297
298	"Information partially available" means that part of the information about the OID is not available. Possible reasons could be that part of the information was redacted due to confidentiality, or the WHOIS service does only know basic information, while the full information can be found somewhere else (e.g. at a referred WHOIS service). The field "attribute" MAY be used with the value "confidential".	298	"Information partially available" means that part of the information about the OID is not available. Possible reasons could be that part of the information is redacted due to confidentiality, or the WHOIS service does only know basic information, while the full information can be found somewhere else (e.g. at a referred WHOIS service). The field "attribute" MAY be used with the value "confidential".
299		299
300	"Information unavailable" means that the information about the OID is missing, redacted due to confidentiality, or otherwise unavailable. The field "attribute" MAY be used with the value "confidential".	300	"Information unavailable" means that the information about the OID is missing, redacted due to confidentiality, or otherwise unavailable. The field "attribute" MAY be used with the value "confidential".
301	.in 3	301	.in 3
302		302
303	(3) "name" (OPTIONAL) contains the name of the OID. It SHOULD be as short as possible.	303	(3) "name" (OPTIONAL) contains the name of the OID. It SHOULD be as short as possible.
Line 318...		Line 318...
318		318
319	.in 7	319	.in 7
320	Note: A line-break, to break up lines which are too long, as defined in section\03.1 ("Format and Encoding") SHALL NOT be used, otherwise, it would be ambiguous if the line-break was used to shorten the line, or if the line-break indicates a new value in case multiple OID-IRI notations are supplied.	320	Note: A line-break, to break up lines which are too long, as defined in section\03.1 ("Format and Encoding") SHALL NOT be used, otherwise, it would be ambiguous if the line-break was used to shorten the line, or if the line-break indicates a new value in case multiple OID-IRI notations are supplied.
321	.in 3	321	.in 3
322		322
323	(9) "identifier" (OPTIONAL, multiple values allowed) contains the alphanumeric identifier ("NameForm") as defined in Recommendation ITU-T X.680 (2015) \| ISO/IEC 8824-1:2015, clause 12.3 [X680].	323	(9) "identifier" (OPTIONAL, multiple values allowed) contains an alphanumeric identifier ("NameForm") as defined in Recommendation ITU-T X.680 (2015) \| ISO/IEC 8824-1:2015, clause 12.3 [X680].
324		324
325	(10) "standardized-id" (OPTIONAL, multiple values allowed) contains an alphanumeric identifier that has a standardized "NameForm", i.e. in ASN.1 notation, it can be written without its associated number. See more information in Recommendation ITU-T X.680 (2015) \| ISO/IEC 8824-1:2015, clause 32.7 [X680].	325	(10) "standardized-id" (OPTIONAL, multiple values allowed) contains an alphanumeric identifier that has a standardized "NameForm", i.e. in ASN.1 notation, it can be written without its associated number. See more information in Recommendation ITU-T X.680 (2015) \| ISO/IEC 8824-1:2015, clause 32.7 [X680].
326		326
327	(11) "unicode-label" (OPTIONAL, multiple values allowed) contains a Non-integer Unicode label, as defined in Recommendation ITU-T X.680 (2015) \| ISO/IEC 8824-1:2015, clause 12.27 [X680].	327	(11) "unicode-label" (OPTIONAL, multiple values allowed) contains a Non-integer Unicode label, as defined in Recommendation ITU-T X.680 (2015) \| ISO/IEC 8824-1:2015, clause 12.27 [X680].
328		328
Line 343...		Line 343...
343		343
344	"no-identifiers" means that the RA is not allocating alphanumeric identifiers.	344	"no-identifiers" means that the RA is not allocating alphanumeric identifiers.
345		345
346	"no-unicode-labels" means that the RA is not allocating Non-integer Unicode labels.	346	"no-unicode-labels" means that the RA is not allocating Non-integer Unicode labels.
347		347
348	"retired" means that the OID is invalidated, revoked, retired, expired, etc. Please consult Recommendation ITU-T X.660 (2011) \| ISO/IEC 9834-1:2012 [X660] for more information about such cases.	348	"retired" means that the OID is withdrawn, revoked, retired, expired, etc. Please consult Recommendation ITU-T X.660 (2011) \| ISO/IEC 9834-1:2012 [X660] for more information about such cases.
349	.in 3	349	.in 3
350		350
351	(15) "parent" (OPTIONAL) contains the OID of the nearest known parent OID, prepended by namespace identifier and double colon, i.e. "oid:". It MAY be followed by additional human-readable information, e.g. a description or a list of ASN.1 identifiers. There SHALL be at least 1 whitespace in between.	351	(15) "parent" (OPTIONAL) contains the OID of the nearest known parent OID, prepended by namespace identifier and double colon, i.e. "oid:". It MAY be followed by additional human-readable information, e.g. a description or a list of ASN.1 identifiers. There SHALL be at least 1 whitespace in between.
352		352
353	(16) "subordinate" (OPTIONAL, multiple values allowed) contains a list of subordinate OIDs, prepended by namespace identifier and double colon, i.e. "oid:". It MAY be followed by additional human-readable information, e.g. a description or a list of ASN.1 identifiers. There SHALL be at least 1 whitespace in between.	353	(16) "subordinate" (OPTIONAL, multiple values allowed) contains a list of subordinate OIDs, prepended by namespace identifier and double colon, i.e. "oid:". It MAY be followed by additional human-readable information, e.g. a description or a list of ASN.1 identifiers. There SHALL be at least 1 whitespace in between.
Line 370...		Line 370...
370	(2) "ra-status" MUST be present and SHALL be one of the following values:	370	(2) "ra-status" MUST be present and SHALL be one of the following values:
371		371
372	.in 7	372	.in 7
373	"Information available" means that information about this RA is fully available.	373	"Information available" means that information about this RA is fully available.
374		374
375	"Information partially available" means that part of the information is not available. A possible reason could be that part of the information was redacted due to confidentiality. The field "attribute" MAY be used with the value "confidential".	375	"Information partially available" means that part of the information is not available. A possible reason could be that part of the information is redacted due to confidentiality. The field "attribute" MAY be used with the value "confidential".
376		376
377	"Information unavailable" means that the data is missing (if the WHOIS service does only know the name of the RA and nothing else), redacted due to confidentiality or otherwise unavailable. The field "attribute" MAY be used with the value "confidential".	377	"Information unavailable" means that the data is missing (if the WHOIS service does only know the name of the RA and nothing else), redacted due to confidentiality or otherwise unavailable. The field "attribute" MAY be used with the value "confidential".
378	.in 3	378	.in 3
379		379
380	(3) "ra-contact-name" (OPTIONAL, multiple values allowed) contains the name of a person responsible for the allocation and administration of subordinate OIDs, in case "ra" is a group or organization.	380	(3) "ra-contact-name" (OPTIONAL, multiple values allowed) contains the name of a person responsible for the allocation of subordinate OIDs, in case "ra" is a group or organization.
381		381
382	(4) "ra-address" (OPTIONAL) contains the physical location of the RA. While a fully qualified postal address is recommended, the field can also just contain a rough location like city and country name, state and country name, or just the country name. The name of the country SHOULD always be present.	382	(4) "ra-address" (OPTIONAL) contains the physical location of the RA. While a fully qualified postal address is recommended, the field can also just contain a rough location like city and country name, state and country name, or just the country name, etc. The name of the country SHOULD always be present.
383		383
384	(5) "ra-phone" (OPTIONAL, multiple values allowed) contains a landline phone number of the Registration Authority. It SHOULD be written in the international number format specified in Recommendation ITU-T E.164 (2010) [E164], e.g. +1 206 555 0100.	384	(5) "ra-phone" (OPTIONAL, multiple values allowed) contains a landline phone number of the Registration Authority. It SHOULD be written in the international number format specified in Recommendation ITU-T E.164 (2010) [E164], e.g. +1 206 555 0100.
385		385
386	(6) "ra-mobile" (OPTIONAL, multiple values allowed) contains a mobile phone number of the Registration Authority. It SHOULD be written in the international number format specified in Recommendation ITU-T E.164 (2010) [E164], e.g. +1 206 555 0100.	386	(6) "ra-mobile" (OPTIONAL, multiple values allowed) contains a mobile phone number of the Registration Authority. It SHOULD be written in the international number format specified in Recommendation ITU-T E.164 (2010) [E164], e.g. +1 206 555 0100.
387		387
Line 425...		Line 425...
425	.ti 0	425	.ti 0
426	3.3 Digital Signature	426	3.3 Digital Signature
427		427
428	If integrity/authenticity is required, the whole response can be signed, e.g. by using S/MIME, RSA, or PGP. This document does not describe a mechanism for detecting which signature method was used. The creation and verification of the signature are therefore implementation-specific and no interoperability regarding signature creation and validation is given at this time.	428	If integrity/authenticity is required, the whole response can be signed, e.g. by using S/MIME, RSA, or PGP. This document does not describe a mechanism for detecting which signature method was used. The creation and verification of the signature are therefore implementation-specific and no interoperability regarding signature creation and validation is given at this time.
429		429
430	Depending on the signature method being used, various things need to be appended and/or prepended to the response. These additional lines MUST be prepended by a percent sign ("%") to avoid that an application confuses these additional lines (e.g. lines belonging to a PGP header) with part of the actual WHOIS response.	430	Depending on the signature method being used, various things need to be appended and/or prepended to the response. These additional lines MUST be prepended by a percent sign ("%") to avoid that an application confuses these additional lines (e.g. lines belonging to a PGP header) with parts of the actual WHOIS response.
431		431
432	.ti 0	432	.ti 0
433	3.4 Date/Time Format	433	3.4 Date/Time Format
434		434
435	Date/Time references SHALL be formatted as described in section\03.4.1.	435	Date/Time references SHALL be formatted as described in section\03.4.1.
Line 650...		Line 650...
650		650
651	The original WHOIS protocol as defined in RFC\03912 [RFC3912] does not define any character set and there is no mechanism for indicating which character set is in use.	651	The original WHOIS protocol as defined in RFC\03912 [RFC3912] does not define any character set and there is no mechanism for indicating which character set is in use.
652		652
653	To enhance interoperability, this document specifies that the request and response MUST be UTF-8 encoded (as defined in RFC\03629 [RFC3629]), without Byte-Order-Mark (BOM).	653	To enhance interoperability, this document specifies that the request and response MUST be UTF-8 encoded (as defined in RFC\03629 [RFC3629]), without Byte-Order-Mark (BOM).
654		654
655	The WHOIS service can define additional field names, but they SHOULD be written in the English language so that there is consistency with the other field names defined in this document.	655	The WHOIS service can define additional field names, but they SHOULD be written in the English language so that there is consistency with the field names defined in this document.
656	.bp	656	.bp
657	.ti 0	657	.ti 0
658	8 Security Considerations	658	8 Security Considerations
659		659
660	(1) The knowledge of existence or information about some OIDs could be considered confidential. In this case, the WHOIS service can either deny the existence of the requested OID (by setting the result to "Not found") or redact information in the Object-Section, as defined in section\03.2.2 "Object-Section".	660	(1) The knowledge of existence or information about some OIDs could be considered confidential. In this case, the WHOIS service can either deny the existence of the requested OID (by setting the result to "Not found") or redact information in the Object-Section, as defined in section\03.2.2 "Object-Section".