sftp url rfc draft

[Robey Pointer]

Hi there!

At the bzr project (www.bazaar-ng.org) we plan to use sftp urls to  
access remote source-code repositories, and there's been some  
discussion about whether to use the current de-facto standard  
(absolute paths only) or the new RFC draft that you two have posted  
here:
	
<http://www.ietf.org/internet-drafts/draft-ietf-secsh-scp-sftp-ssh- 
uri-03.txt>

which supports both absolute and relative paths.

One point that's come up is that nobody wants to type "%2F" in an url  
to get the equivalent of the old url behavior.  The RFC seems to  
sometimes imply that using "//" would be okay (since it would be  
otherwise meaningless), but sometimes implies that this would be  
unacceptable.

Because this point could affect our decision of which format to use,  
could you clarify if a path like

	sftp://user@host//absolute/path

would be an acceptable equivalent to

	sftp://user@host/%2Fabsolute/path

?

Thanks!

robey