July 2011 - Register-uri - lists.iana.org

[register] Re: FWD: I-D Action: draft-yevstifeyev-ftp-uri-scheme-05.txt
by Mykyta Yevstifeyev July 31, 2011

July 31, 2011

31.07.2011 11:38, John Cowan wrote: > Mykyta Yevstifeyev scripsit: > >> Sorry for cross-posting to 6 addresses :-); please send >> all your comments to apps-discuss(a)ietf.org. Note to >> public-iri subscribers: please have a look at Section >> 6. Note to register(a)uri.arpa subscribers: please comment >> Appendix A of the document. (The link to HTML version: >> http://tools.ietf.org/html/draft-yevstifeyev-ftp-uri-scheme.) > It's inappropriate to say that the client SHALL request a password > from the user if none is supplied and the server demands one (and > likewise for accounts). The client must be free to fail under such > circumstances, as it may be a robot or otherwise not have a user > available. Likewise with SHALL notify the user, etc. These should be > changed to MAYs or SHOULDs. I think such occurrences of SHALL will be replaced with SHOULD or non-normative "should". (I don't think 'ftp' URIs will be used with applications that have no UI; so I don't see reasons to assume they will be used in such way. But, anyway, your comment regarding SHALL is reasonable). > > Editorial notes: Lots of people don't know what "ibidem" means, or even > its standard abbreviation "ibid". I suggest changing the first instance > to "in RFC 959", the second instance to "below", and the third instance > to "in the<cwd>". I'll make the following corrections: 1st instance - "in RFC 959" (as currently), 2nd one - "in the same document", 3rd one (I guess this is regarding ASCII) - "in RFC 959". > > Note error "internalization" for "internationalization", "internalized" > for "internationalized", etc. Fixed now. > > Note persistent typo "exmaple.com" for "example.com". ACK. Thanks for reading the document. Mykyta >

1 0

[register] FWD: I-D Action: draft-yevstifeyev-ftp-uri-scheme-05.txt
by Mykyta Yevstifeyev July 31, 2011

July 31, 2011

Hello, Sorry for cross-posting to 6 addresses :-); please send all your comments to apps-discuss(a)ietf.org. Note to public-iri subscribers: please have a look at Section 6. Note to register(a)uri.arpa subscribers: please comment Appendix A of the document. (The link to HTML version: http://tools.ietf.org/html/draft-yevstifeyev-ftp-uri-scheme.) Thanks, Mykyta Yevstifeyev > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > Title : The'ftp' URI Scheme > Author(s) : Mykyta Yevstifeyev > Filename : draft-yevstifeyev-ftp-uri-scheme-05.txt > Pages : 29 > Date : 2011-07-24 > > This document specifies the'ftp' Uniform Resource Identifier (URI) > scheme, which is used to refer to resources accessible via File > Transfer Protocol (FTP). It updates RFC 959 and RFC 1738. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-yevstifeyev-ftp-uri-scheme-05.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > This Internet-Draft can be retrieved at: > ftp://ftp.ietf.org/internet-drafts/draft-yevstifeyev-ftp-uri-scheme-05.txt

1 0

[register] Request to change the NAPTR record for ftp.uri.arpa
by Mykyta Yevstifeyev July 14, 2011

July 14, 2011

Hello, I'm currently working in 'ftp' URI scheme specification. Having found the following message: http://www.iana.org/protocols/archives/register-uri/msg00005.html I noticed the inconsistence of recorded NAPTR record with the actual deployed scheme syntax (and including that I'm trying to document in http://tools.ietf.org/html/draft-yevstifeyev-ftp-uri-scheme-04) What I mean is that substitution expression like: > !^ftp://([^:/?#]*).*$!\\1!i Additionally to host-name extracts the userinfo part of an URI, so that <ftp://exmaple:foo@exmaple.com:523/bar> will result in "exmaple:foo@exmaple.com" extracted from an URI as a next key. This isn't a valid DNS name. Therefore, I'm planning to request IANA to change this expression to > !^ftp://([^@]*)([^:/?#]*).*$!\\2!i in my next revision of the draft. This document will undergo IESG approval, so there is no concerns with change controller with this NAPTR record. However, prior to this I'd like to request community feedback on this change. I'm citing the corresponding Appendix of the draft which intends to make this change as well as IANA considerations with this respect. > Appendix A. Dynamic Delegation Discovery System (DDDS) and 'ftp' URIs > > Dynamic Delegation Discovery System (DDDS) is an abstract algorithm > for applying dynamically retrieved string transformation rules to an > application-unique string. The comprehensive DDDS specification > consists of 5 documents, which are defined in RFC 3401 [RFC3401]. > > RFC 3404 [RFC3404] specified a DDDS Application for resolving URIs > using DDDS Algorithm defined in RFC 3402 [RFC3402]. A corresponding > second-level domain has been delegated in the "arpa" zone [RFC3172] - > "uri.arpa" [RFC3405] - for use with this Application. RFC 3404 > specified that First Well Known Rule for the aforementioned DDDS > Application is to append the URI scheme name to ".uri.arpa". > According to the provisions of RFC 3405 [RFC3405], the 'ftp' URI > scheme was previously approved for inclusion in this zone [MSG-REG] > in order to allow its resolving using DDDS. Correspondingly, the > following substitution expression was recorded in the NAPTR DNS > resource record [RFC3403]: > > !^ftp://([^:/?#]*).*$!\1!i > > using the syntax defined in Section 3.2 of RFC 3402. However, taking > the syntax specified in this document, IANA is asked to record the > following new substitution expression in the NAPTR record for > ftp.uri.arpa domain: > > !^ftp://([^@]*)([^:/?#]*).*$!\2!i > > This substitution expression extracts the hostname from a given URI, > forming the next Key. > > Refer to RFC 3404 for detailed description of DDDS Application for > resolving URIs and RFC 3402 for generic DDDS Algorithm. > > Please note that while there is a possibility to resolve 'ftp' URIs > using DDDS, not every given 'ftp' URI may be resolved using this > technique. A specific "hint" is required in order to denote this; > for instance, "the URI <ftp://exmaple.org/foo/bar.txt> refers to the > very valuable information; it is mirrored at a number of servers > which are to be discovered using DDDS". Here [MSG-REG] refers to the above-referenced message. Corresponding IANA considerations are: > 5.3. Maintaining ftp.uri.arpa Domain > > As primarily requested by [MSG-REG] per RFC 3405 [RFC3405], IANA will > continue maintaining the ftp.uri.arpa domain for use of DDDS with > 'ftp' URIs (see Appendix A). Moreover, IANA is requested to change > the existing substitution expression in the NAPTR record for this > domain as described in Appendix A. Any comments from DDDS experts are invited and welcome. Thanks in advance, Mykyta Yevstifeyev

3 6