From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Wed Feb 01 18:50:16 2006 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F4Rjs-00046r-2f for secsh-archive@megatron.ietf.org; Wed, 01 Feb 2006 18:50:16 -0500 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28047 for ; Wed, 1 Feb 2006 18:48:39 -0500 (EST) Received: by mail.netbsd.org (Postfix, from userid 0) id CA22763B2FF; Wed, 1 Feb 2006 23:50:05 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from newodin.ietf.org (unknown [132.151.6.50]) by mail.netbsd.org (Postfix) with ESMTP id B1DD263B2FD for ; Wed, 1 Feb 2006 23:50:02 +0000 (UTC) Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1F4Rjd-0006CN-So; Wed, 01 Feb 2006 18:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org Cc: ietf-ssh@NetBSD.org From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-secsh-scp-sftp-ssh-uri-03.txt Message-Id: Date: Wed, 01 Feb 2006 18:50:01 -0500 Sender: ietf-ssh-owner@NetBSD.org Precedence: list --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Shell Working Group of the IETF. Title : Uniform Resource Identifier (URI) Scheme for Secure File Transfer Protocol (SFTP) and Secure Shell (SSH) Author(s) : S. Suehring, J. Salowey Filename : draft-ietf-secsh-scp-sftp-ssh-uri-03.txt Pages : 10 Date : 2005-8-29 This document describes the Uniform Resource Identifiers used to locate resources for the Secure File Transfer Protocol (SFTP) and the Secure Shell (SSH) protocols. The document describes the generic syntax involved in URI definitions as well as specific definitions for each protocol. These specific definitions may include user credentials such as username and also may include other parameters such as host key fingerprint. In addition, security considerations and examples are also provided within this document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-secsh-scp-sftp-ssh-uri-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-2-1162836.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-secsh-scp-sftp-ssh-uri-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-2-1162836.I-D@ietf.org> --OtherAccess-- --NextPart-- From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Thu Feb 02 15:50:20 2006 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F4lPI-0006uV-JB for secsh-archive@megatron.ietf.org; Thu, 02 Feb 2006 15:50:20 -0500 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08123 for ; Thu, 2 Feb 2006 15:48:42 -0500 (EST) Received: by mail.netbsd.org (Postfix, from userid 0) id 7F2BC63B41D; Thu, 2 Feb 2006 20:50:09 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from newodin.ietf.org (unknown [132.151.6.50]) by mail.netbsd.org (Postfix) with ESMTP id 6BDD963B29C for ; Thu, 2 Feb 2006 20:50:08 +0000 (UTC) Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1F4lOz-0002eR-KB; Thu, 02 Feb 2006 15:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org Cc: ietf-ssh@NetBSD.org From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-secsh-scp-sftp-ssh-uri-04.txt Message-Id: Date: Thu, 02 Feb 2006 15:50:01 -0500 Sender: ietf-ssh-owner@NetBSD.org Precedence: list --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Shell Working Group of the IETF. Title : Uniform Resource Identifier (URI) Scheme for Secure File Transfer Protocol (SFTP) and Secure Shell (SSH) Author(s) : S. Suehring, J. Salowey Filename : draft-ietf-secsh-scp-sftp-ssh-uri-04.txt Pages : 11 Date : 2006-2-2 This document describes the Uniform Resource Identifiers used to locate resources for the Secure File Transfer Protocol (SFTP) and the Secure Shell (SSH) protocols. The document describes the generic syntax involved in URI definitions as well as specific definitions for each protocol. These specific definitions may include user credentials such as username and also may include other parameters such as host key fingerprint. In addition, security considerations and examples are also provided within this document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-secsh-scp-sftp-ssh-uri-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-2-2142839.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-secsh-scp-sftp-ssh-uri-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-2-2142839.I-D@ietf.org> --OtherAccess-- --NextPart-- From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Sat Feb 04 13:44:50 2006 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5SOl-0003Uw-QW for secsh-archive@megatron.ietf.org; Sat, 04 Feb 2006 13:44:50 -0500 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28186 for ; Sat, 4 Feb 2006 13:42:49 -0500 (EST) Received: by mail.netbsd.org (Postfix, from userid 0) id C344A63B5CC; Sat, 4 Feb 2006 18:44:07 +0000 (UTC) X-Original-To: ietf-ssh@NetBSD.org Delivered-To: ietf-ssh@NetBSD.org Received: from galaxy.systems.pipex.net (galaxy.systems.pipex.net [62.241.162.31]) by mail.netbsd.org (Postfix) with ESMTP id 0A3BA63B5CE for ; Sat, 4 Feb 2006 18:44:07 +0000 (UTC) Received: from pc6 (1Cust60.tnt5.lnd4.gbr.da.uu.net [62.188.134.60]) by galaxy.systems.pipex.net (Postfix) with SMTP id 67B52E0003C2; Sat, 4 Feb 2006 18:20:54 +0000 (GMT) Message-ID: <040f01c629af$3f9ff120$0601a8c0@pc6> Reply-To: "Tom Petch" From: "Tom Petch" To: "Salowey, Joe" , "Steve Suehring" , References: <7210B31550AC934A8637D6619739CE69068C20A8@e2k-sea-xch2.sea-alpha.cisco.com> Subject: draft-ietf-secsh-scp-sftp-ssh-uri-04.txt Date: Sat, 4 Feb 2006 18:12:21 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 7bit Good to see that -04 has made it (after a re-issue of -03). I think it is fine but could be improved with some minor emendations to the language, namely - URL appears nine times - I think URI is better in each case - 3.3 lacks / as a reserved character which 4.3 I think rightly includes - s /the/they/ in the last phrase of 3.3 and 4.3 - path-empty could be removed from 2 - 4.5 talks of UTF which is a character encoding scheme or character encoding syntax, or a transformation format (depending on which standards body you are in). I suggest amending the sentence to be "Path segments SHOULD be represented in the UTF-8 [RFC3629] character encoding syntax and clients SHOULD NOT disable UTF-8 encoding on the server with the filename-translation-control extension. " I note that secsh-filexfer does use "... MUST send all filenames encoded in UTF-8" even if the parameter name uses the work translation (unfortunately:-). Finally, draft-shur-pack-uri-scheme-00.txt gives a new (for me) slant of how to deal with authority, path and / - I will be interested to see how it is received. Tom Petch From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Fri Feb 10 17:03:57 2006 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7gMv-0006i4-IG for secsh-archive@megatron.ietf.org; Fri, 10 Feb 2006 17:03:57 -0500 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05553 for ; Fri, 10 Feb 2006 17:02:07 -0500 (EST) Received: by mail.netbsd.org (Postfix, from userid 0) id 6EAB563B241; Fri, 10 Feb 2006 22:03:43 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from carter-zimmerman.mit.edu (carter-zimmerman.dyn.MIT.EDU [18.188.3.148]) by mail.netbsd.org (Postfix) with ESMTP id 7645463B15A for ; Fri, 10 Feb 2006 22:03:42 +0000 (UTC) Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id 3B25BE0053; Fri, 10 Feb 2006 16:32:14 -0500 (EST) To: ietf-ssh@NetBSD.org Subject: [(nowhere)] FW: Please re-review draft-ietf-secsh-publickeyfile [I06-050928-0006] From: Sam Hartman Date: Fri, 10 Feb 2006 16:32:14 -0500 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: ietf-ssh-owner@NetBSD.org Precedence: list --=-=-= Folks, I'm holding a discuss on the ssh publickeyfile draft because IANA doesn't understand what they are supposed to do. The IANA change is one I didn't see discussed on the list and it seems to have introduced problems. Bill, I assume you can work to resolution on this. --=-=-= Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from solipsist-nation MIME-Version: 1.0 ([unix socket]) by solipsist-nation (Cyrus v2.1.16-IPv6-Debian-2.1.16-10) with LMTP; Fri, 10 Feb 2006 16:19:34 -0500 X-Sieve: CMU Sieve 2.2 Return-Path: Received: from south-station-annex.mit.edu (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by suchdamage.org (Postfix) with ESMTP id BEE1413105 for ; Fri, 10 Feb 2006 16:19:33 -0500 (EST) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by south-station-annex.mit.edu (8.12.4/8.9.2) with ESMTP id k1ALJWRj027225 for ; Fri, 10 Feb 2006 16:19:32 -0500 (EST) Received: from g13.icann.org (g13.icann.org [192.0.34.122]) by fort-point-station.mit.edu (8.12.4/8.9.2) with ESMTP id k1ALJOwA022905 for ; Fri, 10 Feb 2006 16:19:24 -0500 (EST) Received: from g13.icann.org (g13.icann.org [127.0.0.1]) by g13.icann.org (8.12.11/8.12.11) with ESMTP id k1ALJaHL013768 for ; Fri, 10 Feb 2006 13:19:36 -0800 Received: (from apache@localhost) by g13.icann.org (8.12.11/8.12.11/Submit) id k1ALJaMx013767; Fri, 10 Feb 2006 13:19:36 -0800 Date: Fri, 10 Feb 2006 13:19:36 -0800 Message-Id: <200602102119.k1ALJaMx013767@g13.icann.org> To: hartmans-ietf@mit.edu Subject: FW: Please re-review draft-ietf-secsh-publickeyfile [I06-050928-0006] From: iana-drafts@icann.org Reply-To: iana-drafts@icann.org Cc: X-Scanned-By: MIMEDefang 2.42 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on solipsist-nation.suchdamage.org X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,NO_REAL_NAME autolearn=no version=3.0.2 MIME-Version: 1.0 Sam, Sorry for the delayed response. I have reviewed the new version and have put new comments in the tracker. However, the IANA Considerations section still needs work. There is not much detail regarding what type of registry, are these values, what are the registration procedures, etc. If you need for me to look at a new version of the IANA Considerations section, please let me know. Thanks, Michelle IANA -----Original Message----- From: Sam Hartman [mailto:hartmans-ietf@mit.edu] Sent: Tuesday, January 31, 2006 5:59 PM To: iana@iana.org Subject: Please re-review draft-ietf-secsh-publickeyfile Hi. the IANA considerations for this draft used to include no actions but now includes actions. I'd appreciate it if you would review these actions. --=-=-=-- From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Fri Feb 10 17:18:02 2006 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7gaS-0005eg-3o for secsh-archive@megatron.ietf.org; Fri, 10 Feb 2006 17:18:02 -0500 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06651 for ; Fri, 10 Feb 2006 17:16:03 -0500 (EST) Received: by mail.netbsd.org (Postfix, from userid 0) id 4F9C563B24A; Fri, 10 Feb 2006 22:17:44 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from vandyke.com (mail.vandyke.com [204.134.9.1]) by mail.netbsd.org (Postfix) with ESMTP id 3CA3063B15A for ; Fri, 10 Feb 2006 22:17:43 +0000 (UTC) Received: from [127.0.0.1] (HELO [0.0.0.0]) by vandyke.com (CommuniGate Pro SMTP 3.4.7) with ESMTP id 8513525; Fri, 10 Feb 2006 15:17:47 -0700 Message-ID: <43ED116A.2090102@vandyke.com> Date: Fri, 10 Feb 2006 15:19:22 -0700 From: Joseph Galbraith User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Sam Hartman CC: ietf-ssh@NetBSD.org Subject: Re: [(nowhere)] FW: Please re-review draft-ietf-secsh-publickeyfile [I06-050928-0006] References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: ietf-ssh-owner@NetBSD.org Precedence: list Content-Transfer-Encoding: 7bit The introduction of the iana section was in response to a comment by Jacob Nevins with regards to this section: 3.3.3. New Headers Headers with header-tags beginning with "x-" are considered experimental, and may be used without IETF consensus. All other headers are reserved for use only by IETF consensus. Jacob noted in his email: > Doesn't this imply the existence of an IANA registry, contrary to what > section 5 "IANA Considerations" says? I'll see if I can work on a little bit more for the IANA section (text welcome if someone knows exactly what details IANA needs.) Thanks, Joseph Sam Hartman wrote: > > Folks, I'm holding a discuss on the ssh publickeyfile draft because IANA > doesn't understand what they are supposed to do. > The IANA change is one I didn't see discussed on the list and it seems to have introduced problems. > > Bill, I assume you can work to resolution on this. > > > > ------------------------------------------------------------------------ > > > ([unix socket]) by solipsist-nation (Cyrus > v2.1.16-IPv6-Debian-2.1.16-10) with LMTP; Fri, 10 Feb 2006 16:19:34 > -0500 X-Sieve: CMU Sieve 2.2 Return-Path: > Received: from south-station-annex.mit.edu > (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) (using TLSv1 with cipher > DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) > by suchdamage.org (Postfix) with ESMTP id BEE1413105 for > ; Fri, 10 Feb 2006 16:19:33 -0500 (EST) > Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU > [18.7.7.76]) by south-station-annex.mit.edu (8.12.4/8.9.2) with ESMTP > id k1ALJWRj027225 for ; Fri, 10 Feb 2006 > 16:19:32 -0500 (EST) Received: from g13.icann.org (g13.icann.org > [192.0.34.122]) by fort-point-station.mit.edu (8.12.4/8.9.2) with > ESMTP id k1ALJOwA022905 for ; Fri, 10 Feb 2006 > 16:19:24 -0500 (EST) Received: from g13.icann.org (g13.icann.org > [127.0.0.1]) by g13.icann.org (8.12.11/8.12.11) with ESMTP id > k1ALJaHL013768 for ; Fri, 10 Feb 2006 13:19:36 > -0800 Received: (from apache@localhost) by g13.icann.org > (8.12.11/8.12.11/Submit) id k1ALJaMx013767; Fri, 10 Feb 2006 13:19:36 > -0800 Date: Fri, 10 Feb 2006 13:19:36 -0800 Message-Id: > <200602102119.k1ALJaMx013767@g13.icann.org> To: hartmans-ietf@mit.edu > Subject: FW: Please re-review draft-ietf-secsh-publickeyfile > [I06-050928-0006] From: iana-drafts@icann.org Reply-To: > iana-drafts@icann.org Cc: X-Scanned-By: MIMEDefang 2.42 > X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on > solipsist-nation.suchdamage.org X-Spam-Level: X-Spam-Status: No, > score=-1.3 required=5.0 tests=BAYES_00,NO_REAL_NAME autolearn=no > version=3.0.2 > MIME-Version: 1.0 > > > Sam, > > Sorry for the delayed response. > > I have reviewed the new version and have put new comments in the tracker. > However, the IANA Considerations section still needs work. There is not much detail regarding what type of registry, are these values, what are the registration procedures, etc. > > If you need for me to look at a new version of the IANA Considerations section, please let me know. > > Thanks, > > Michelle > IANA > > > -----Original Message----- > From: Sam Hartman [mailto:hartmans-ietf@mit.edu] > Sent: Tuesday, January 31, 2006 5:59 PM > To: iana@iana.org > Subject: Please re-review draft-ietf-secsh-publickeyfile > > > Hi. the IANA considerations for this draft used to include no actions but > now includes actions. I'd appreciate it if you would review these actions. > > > > > > > > > From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Fri Feb 10 17:47:00 2006 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7h2a-000091-RN for secsh-archive@megatron.ietf.org; Fri, 10 Feb 2006 17:47:00 -0500 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08403 for ; Fri, 10 Feb 2006 17:45:16 -0500 (EST) Received: by mail.netbsd.org (Postfix, from userid 0) id 599A963B254; Fri, 10 Feb 2006 22:46:57 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mail.netbsd.org (Postfix) with ESMTP id A662963B253 for ; Fri, 10 Feb 2006 22:46:56 +0000 (UTC) Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local (return-path jacobn@chiark.greenend.org.uk) id 1F7h2V-0004Ks-00 for ietf-ssh@netbsd.org; Fri, 10 Feb 2006 22:46:55 +0000 Date: Fri, 10 Feb 2006 22:46:55 +0000 From: Jacob Nevins To: ietf-ssh@NetBSD.org Subject: Re: DH key exchange message numbers Message-ID: <20060210224655.GA15641@chiark.greenend.org.uk> Reply-To: ietf-ssh@NetBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: ietf-ssh-owner@NetBSD.org Precedence: list Jeffrey Hutzelman writes: > I think we need an RFC Errata on this one... :-( In case anyone else was wondering: an erratum has been submitted, and is visible in a public mbox folder: but RFC-Editor is not processing errata at the moment, so this won't be visible from the RFC Search page: (15 November 2005) From bounces-ietf-ssh-owner-secsh-archive=odin.ietf.org@NetBSD.org Fri Feb 10 18:16:31 2006 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7hV9-0000Sz-NC for secsh-archive@megatron.ietf.org; Fri, 10 Feb 2006 18:16:31 -0500 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10982 for ; Fri, 10 Feb 2006 18:14:37 -0500 (EST) Received: by mail.netbsd.org (Postfix, from userid 0) id E971763B23B; Fri, 10 Feb 2006 23:16:07 +0000 (UTC) X-Original-To: ietf-ssh@netbsd.org Delivered-To: ietf-ssh@netbsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mail.netbsd.org (Postfix) with ESMTP id 3BAE463B138 for ; Fri, 10 Feb 2006 23:16:07 +0000 (UTC) Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local (return-path jacobn@chiark.greenend.org.uk) id 1F7hUk-0002ii-00 for ietf-ssh@netbsd.org; Fri, 10 Feb 2006 23:16:06 +0000 Date: Fri, 10 Feb 2006 23:16:06 +0000 From: Jacob Nevins To: ietf-ssh@NetBSD.org Subject: Re: [(nowhere)] FW: Please re-review draft-ietf-secsh-publickeyfile [I06-050928-0006] Message-ID: <20060210231606.GB15641@chiark.greenend.org.uk> Reply-To: ietf-ssh@NetBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43ED116A.2090102@vandyke.com> User-Agent: Mutt/1.3.28i Sender: ietf-ssh-owner@NetBSD.org Precedence: list Joseph Galbraith writes: > The introduction of the iana section was in response to a comment by > Jacob Nevins [...] It was also noted by the IESG (Brian Carpenter quoting Joel Halpern's Gen-ART review). > I'll see if I can work on a little bit more for the IANA section > (text welcome if someone knows exactly what details IANA needs.) I guess RFC2434/BCP0026 might be of use? Could it be as simple as moving the language about "IETF Consensus" and X-headers to the IANA Considerations section, and referencing 2434? From recovered-from-private-archive Thu Mar 23 23:05:05 2006 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ST8TYhJlTLjjS0zH8w3Yj0KLur1G6cMtYBW1X4WlOXg2CgNxj0gLtNJGBqa6Ig332Yygp7Vy29f7wE28LJHSjWrADRmV/vP/gzOYCDjym/2D0FdfOXAJoiholH0bB8O3ga368TW8DBPttk5E9KP+JVKmbH0hL49xe9pA2iFVyok= ; Content-Type: text/plain; charset=iso-8859-1 To: ietf-ssh@netbsd.org MIME-Version: 1.0 From: GOKUL KANNAN Date: Tue, 21 Feb 2006 10:02:29 +0000 (GMT) Received: by mail.netbsd.org (Postfix, from userid 0) id 492C663B223; Tue, 21 Feb 2006 10:09:13 +0000 (UTC) Received: from web8320.mail.in.yahoo.com (web8320.mail.in.yahoo.com [202.43.219.75]) by mail.netbsd.org (Postfix) with SMTP id B4F3663B13E for ; Tue, 21 Feb 2006 10:09:11 +0000 (UTC) Received: (qmail 43581 invoked by uid 60001); 21 Feb 2006 10:02:29 -0000 Received: from [203.199.198.232] by web8320.mail.in.yahoo.com via HTTP; Tue, 21 Feb 2006 10:02:29 GMT Delivered-To: ietf-ssh@netbsd.org Subject: Doubt on SSH Content-Transfer-Encoding: 8bit Precedence: list Sender: ietf-ssh-owner@NetBSD.org X-Original-To: ietf-ssh@netbsd.org Message-ID: <20060221100229.43579.qmail@web8320.mail.in.yahoo.com> Hi, I'm a final year M.C.A student. I'm doing my project in C language on windows platform. In my project I have to connect my system with a remote server(i.e Linux Server) via SSH. Could you please help me in developing the C program to conect a remote server through SSH.(Note : I'm using Visual Studio i.e., vc++ for C coding). Yours, Gokula Kannan. S __________________________________________________________ Yahoo! India Matrimony: Find your partner now. Go to http://yahoo.shaadi.com From recovered-from-private-archive Thu Mar 23 23:05:05 2006 Reply-To: "Nickolay L." X-Mailer: The Bat! (v3.0.1.33) Professional Content-Type: text/plain; charset=us-ascii In-Reply-To: <20060221100229.43579.qmail@web8320.mail.in.yahoo.com> To: ietf-ssh@netbsd.org MIME-Version: 1.0 References: <20060221100229.43579.qmail@web8320.mail.in.yahoo.com> <20060221100229.43579.qmail@web8320.mail.in.yahoo.com> From: "Nickolay L." X-Virus-Scanned: amavisd-new at ip.net.ua Date: Tue, 21 Feb 2006 12:54:48 +0200 Received: by mail.netbsd.org (Postfix, from userid 0) id C60B663B1CA; Tue, 21 Feb 2006 13:09:37 +0000 (UTC) Received: from mail.ipnet.kiev.ua (cielago.ip.net.ua [82.193.96.7]) by mail.netbsd.org (Postfix) with ESMTP id AE87563B10D for ; Tue, 21 Feb 2006 13:09:36 +0000 (UTC) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by mail.ipnet.kiev.ua (8.13.4/8.13.4) with ESMTP id k1LCEXqB087959 for ; Tue, 21 Feb 2006 14:14:33 +0200 (EET) (envelope-from ni4@ukr.net) Received: from mail.ipnet.kiev.ua ([82.193.96.7]) by localhost (rocky.ip.net.ua [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 56735-01-14 for ; Tue, 21 Feb 2006 14:14:14 +0200 (EET) Received: from INFERNAL (172.16.2.165.cl.ipnet.kiev.ua [172.16.2.165]) by mail.ipnet.kiev.ua (8.13.4/8.13.4) with ESMTP id k1LAwVr4067454 for ; Tue, 21 Feb 2006 12:58:32 +0200 (EET) (envelope-from ni4@ukr.net) Delivered-To: ietf-ssh@netbsd.org Subject: Re: Doubt on SSH Content-Transfer-Encoding: 7bit Precedence: list X-Priority: 3 (Normal) Sender: ietf-ssh-owner@NetBSD.org X-Original-To: ietf-ssh@netbsd.org Message-ID: <636119130.20060221125448@ukr.net> Hello GOKUL, GK> Hi, GK> I'm a final year M.C.A student. I'm doing my project GK> in C language on windows platform. In my project I GK> have to connect my system with a remote server(i.e GK> Linux Server) via SSH. Could you please help me in GK> developing the C program to conect a remote server GK> through SSH.(Note : I'm using Visual Studio i.e., vc++ GK> for C coding). I think, it isn't a right place to ask for such help. You need to start from investigating SSH RFC drafts (draft-ietf-secsh-*), which can be downloaded from IETF online directory. GK> Yours, GK> Gokula Kannan. S -- Best regards,Nickolay mailto: From recovered-from-private-archive Thu Mar 23 23:05:05 2006 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed In-Reply-To: <636119130.20060221125448@ukr.net> To: ietf-ssh@NetBSD.org MIME-Version: 1.0 References: <20060221100229.43579.qmail@web8320.mail.in.yahoo.com> <636119130.20060221125448@ukr.net> <636119130.20060221125448@ukr.net> From: Chris Lonvick Date: Tue, 21 Feb 2006 05:45:39 -0800 (PST) Received: by mail.netbsd.org (Postfix, from userid 0) id 8FB3463B2E4; Tue, 21 Feb 2006 13:46:43 +0000 (UTC) Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by mail.netbsd.org (Postfix) with ESMTP id E422B63B2DE for ; Tue, 21 Feb 2006 13:46:42 +0000 (UTC) Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 21 Feb 2006 05:45:42 -0800 Received: from sjc-cde-011.cisco.com (sjc-cde-011.cisco.com [171.70.90.145]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k1LDjdgZ016971 for ; Tue, 21 Feb 2006 05:45:40 -0800 (PST) Delivered-To: ietf-ssh@netbsd.org Subject: Re: Doubt on SSH Precedence: list X-IronPort-AV: i="4.02,134,1139212800"; d="scan'208"; a="1778212107:sNHT28747266" Sender: ietf-ssh-owner@NetBSD.org X-Original-To: ietf-ssh@netbsd.org Message-ID: Hi, On Tue, 21 Feb 2006, Nickolay L. wrote: > Hello GOKUL, > > GK> Hi, > GK> I'm a final year M.C.A student. I'm doing my project > GK> in C language on windows platform. In my project I > GK> have to connect my system with a remote server(i.e > GK> Linux Server) via SSH. Could you please help me in > GK> developing the C program to conect a remote server > GK> through SSH.(Note : I'm using Visual Studio i.e., vc++ > GK> for C coding). > I think, it isn't a right place to ask for such help. A better place would be be ssh discussion list on SecurityFocus. There's much information in the archive. http://www.securityfocus.com/archive > You need to start from investigating SSH RFC drafts > (draft-ietf-secsh-*), which can be downloaded from IETF online > directory. SSH RFCs - drafts no longer. :) Start with RFC 4251. http://www.ietf.org/rfc/rfc4251.txt Best of Luck, Chris From recovered-from-private-archive Thu Mar 23 23:05:05 2006 Reply-To: "Nickolay L." X-Mailer: The Bat! (v3.0.1.33) Professional Content-Type: text/plain; charset=us-ascii In-Reply-To: To: Chris Lonvick MIME-Version: 1.0 References: <20060221100229.43579.qmail@web8320.mail.in.yahoo.com> <636119130.20060221125448@ukr.net> From: "Nickolay L." X-Virus-Scanned: amavisd-new at ip.net.ua Date: Tue, 21 Feb 2006 15:50:37 +0200 Received: by mail.netbsd.org (Postfix, from userid 0) id A91AE63B3B5; Tue, 21 Feb 2006 15:20:00 +0000 (UTC) Received: from mail.ipnet.kiev.ua (cielago.ip.net.ua [82.193.96.7]) by mail.netbsd.org (Postfix) with ESMTP id A27CB63B142 for ; Tue, 21 Feb 2006 15:19:59 +0000 (UTC) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by mail.ipnet.kiev.ua (8.13.4/8.13.4) with ESMTP id k1LFJvKw025260 for ; Tue, 21 Feb 2006 17:19:57 +0200 (EET) (envelope-from ni4@ukr.net) Received: from mail.ipnet.kiev.ua ([82.193.96.7]) by localhost (rocky.ip.net.ua [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 68937-01-28 for ; Tue, 21 Feb 2006 17:19:37 +0200 (EET) Received: from INFERNAL (172.16.2.165.cl.ipnet.kiev.ua [172.16.2.165]) by mail.ipnet.kiev.ua (8.13.4/8.13.4) with ESMTP id k1LDsLup008966 for ; Tue, 21 Feb 2006 15:54:21 +0200 (EET) (envelope-from ni4@ukr.net) Delivered-To: ietf-ssh@NetBSD.org Subject: Re[2]: Doubt on SSH Content-Transfer-Encoding: 7bit Precedence: list X-Priority: 3 (Normal) Sender: ietf-ssh-owner@NetBSD.org X-Original-To: ietf-ssh@NetBSD.org Message-ID: <375513058.20060221155037@ukr.net> Hello Chris, >> You need to start from investigating SSH RFC drafts >> (draft-ietf-secsh-*), which can be downloaded from IETF online >> directory. CL> SSH RFCs - drafts no longer. :) Start with RFC 4251. CL> http://www.ietf.org/rfc/rfc4251.txt Uh, yes. My fault :-) -- Best regards,Nickolay mailto: From recovered-from-private-archive Thu Mar 23 23:05:05 2006 User-Agent: Mutt/1.5.9i Reply-To: ietf-ssh@netbsd.org Content-Type: text/plain; charset=us-ascii To: ietf-ssh@netbsd.org Mime-Version: 1.0 From: Jacob Nevins Date: Wed, 22 Feb 2006 11:48:47 +0000 Received: by mail.netbsd.org (Postfix, from userid 0) id 6267663B49E; Wed, 22 Feb 2006 11:48:48 +0000 (UTC) Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mail.netbsd.org (Postfix) with ESMTP id A881263B1D4 for ; Wed, 22 Feb 2006 11:48:47 +0000 (UTC) Received: by chiark.greenend.org.uk (Debian Exim 3.36 #1) with local (return-path jacobn@chiark.greenend.org.uk) id 1FBsUB-0006wt-00 for ietf-ssh@netbsd.org; Wed, 22 Feb 2006 11:48:47 +0000 Delivered-To: ietf-ssh@netbsd.org Content-Disposition: inline Subject: dh-group-exchange in AUTH48 Precedence: list Sender: ietf-ssh-owner@NetBSD.org X-Original-To: ietf-ssh@netbsd.org Message-ID: <20060222114847.GA25162@chiark.greenend.org.uk> In case anyone's interested, the dh-group-exchange draft appears to be in the AUTH48 directory right now: From recovered-from-private-archive Thu Mar 23 23:05:06 2006 X-Mailer: Mulberry/3.1.6 (Linux/x86) Content-Type: text/plain; charset=us-ascii; format=flowed In-Reply-To: <20060222114847.GA25162@chiark.greenend.org.uk> To: ietf-ssh@NetBSD.org MIME-Version: 1.0 References: <20060222114847.GA25162@chiark.greenend.org.uk> <20060222114847.GA25162@chiark.greenend.org.uk> From: Jeffrey Hutzelman Date: Fri, 24 Feb 2006 18:59:53 -0500 Received: by mail.netbsd.org (Postfix, from userid 0) id DB54263B15B; Sat, 25 Feb 2006 00:00:10 +0000 (UTC) Received: from minbar.fac.cs.cmu.edu (MINBAR.FAC.CS.CMU.EDU [128.2.185.161]) by mail.netbsd.org (Postfix) with SMTP id 239A863B10C for ; Sat, 25 Feb 2006 00:00:09 +0000 (UTC) Received: from SIRIUS.FAC.CS.CMU.EDU ([128.2.209.170]) by minbar.fac.cs.cmu.edu id aa18262; 24 Feb 2006 18:59 EST Originator-Info: login-token=Mulberry:01VRYWBr9+i3qhYY6HiJRGdeyITTHcSo/Ci0Rri5Y=; token_authority=postmaster@andrew.cmu.edu Delivered-To: ietf-ssh@NetBSD.org Content-Disposition: inline Subject: Re: dh-group-exchange in AUTH48 Content-Transfer-Encoding: 7bit Precedence: list Sender: ietf-ssh-owner@NetBSD.org X-Original-To: ietf-ssh@NetBSD.org Message-ID: On Wednesday, February 22, 2006 11:48:47 AM +0000 Jacob Nevins wrote: > In case anyone's interested, the dh-group-exchange draft appears to be > in the AUTH48 directory right now: > According to the RFC Editor queue history it has been in AUTH48 for 6 days. From recovered-from-private-archive Thu Mar 23 23:05:06 2006 X-Mailer: Barca 2.0 (3350) - Licensed Version Content-Type: text/plain; charset="ISO-8859-1" To: Joseph Galbraith , In-Reply-To: <43CFBBB9.9080205@vandyke.com> References: <43CFBBB9.9080205@vandyke.com> Mime-Version: 1.0 From: denis bider Date: Sun, 26 Feb 2006 17:15:00 +0100 Received: by mail.netbsd.org (Postfix, from userid 0) id 8890A63B330; Sun, 26 Feb 2006 17:16:13 +0000 (UTC) Received: from renown.cnchost.com (renown.concentric.net [207.155.248.7]) by mail.netbsd.org (Postfix) with ESMTP id A7A8C63B10D for ; Sun, 26 Feb 2006 17:16:12 +0000 (UTC) Received: from nucleus (BSN-77-185-155.dsl.siol.net [193.77.185.155]) by renown.cnchost.com id LAA03382; Sun, 26 Feb 2006 11:15:03 -0500 (EST) [ConcentricHost SMTP Relay 1.17] Delivered-To: ietf-ssh@netbsd.org Subject: additional ACE flag required in SFTP draft?, speling and grammer fikses Content-Transfer-Encoding: quoted-printable Precedence: list Sender: ietf-ssh-owner@NetBSD.org X-Original-To: ietf-ssh@netbsd.org Message-ID: <200622617150.396130@nucleus> Hello Joseph, everyone - I got around to continuing our SFTP v6 implementation, and I am now trying= to synchronize my existing implementation (according to draft 10) with the= latest version of the draft (12). Among other things, draft 12 defines: ace-flag A combination of the following flag values. See NFS Version 4 Protocol [RFC3010] section 5.9.2: ACE4_FILE_INHERIT_ACE 0x00000001 ACE4_DIRECTORY_INHERIT_ACE 0x00000002 ACE4_NO_PROPAGATE_INHERIT_ACE 0x00000004 ACE4_INHERIT_ONLY_ACE 0x00000008 ACE4_SUCCESSFUL_ACCESS_ACE_FLAG 0x00000010 ACE4_FAILED_ACCESS_ACE_FLAG 0x00000020 ACE4_IDENTIFIER_GROUP 0x00000040 Unfortunately, when sending an ACL, the lack of an INHERITED value among= these flags provides the server with no way to inform the client which of= the included ACEs are inherited and which are defined explicitly for the= object for which the ACL is being sent. I propose that an additional ACE flag is required which will allow the= server to convey to the client the information that a certain ACE is= inherited (or isn't). I would also like to report the following spelling/grammar errors - which= probably is not an exhaustive list, but regardless. :) - "The ACE data structure is composes as follows:" ^^^^^^^^ - "If the both the INCLUDE and the PRESENT bit are set" ^^^ - "but their are no ALLOW/DENY entries in the list" ^^^^^ - "into a ACL" ^^^^^ - "the clients intent" ^^^^^^^ - "capabilities that the user may have in to allow" ^^?^^ - "restore the file from backup medium" ^^^^?^^^^^^^^^^^^^ - "their may be other uses for this data" ^^^^^ Best regards, denis From recovered-from-private-archive Thu Mar 23 23:05:06 2006 X-Mailer: Barca 2.0 (3350) - Licensed Version Content-Type: text/plain; charset="ISO-8859-1" To: Joseph Galbraith , In-Reply-To: <200622617150.396130@nucleus> References: <200622617150.396130@nucleus> Mime-Version: 1.0 From: denis bider Date: Sun, 26 Feb 2006 18:44:42 +0100 Received: by mail.netbsd.org (Postfix, from userid 0) id 7BDEA63B343; Sun, 26 Feb 2006 19:16:33 +0000 (UTC) Received: from tonnant.cnchost.com (tonnant.concentric.net [207.155.248.72]) by mail.netbsd.org (Postfix) with ESMTP id CBA0763B331 for ; Sun, 26 Feb 2006 19:16:32 +0000 (UTC) Received: from nucleus (BSN-77-185-155.dsl.siol.net [193.77.185.155]) by tonnant.cnchost.com id MAA18938; Sun, 26 Feb 2006 12:44:44 -0500 (EST) [ConcentricHost SMTP Relay 1.17] Delivered-To: ietf-ssh@netbsd.org Subject: SFTP 6 - ACE mask value for ACCESS_SYSTEM_SECURITY Content-Transfer-Encoding: quoted-printable Precedence: list Sender: ietf-ssh-owner@NetBSD.org X-Original-To: ietf-ssh@netbsd.org Message-ID: <2006226184442.234903@nucleus> I also spotted this detail. The SFTP 6 draft (version 12) defines: ace-mask Combination of the following flags (taken from [RFC3010], section 5.9.3. The semantic meaning of these flags is also given in [RFC3010]. ACE4_READ_DATA 0x00000001 ACE4_LIST_DIRECTORY 0x00000001 ACE4_WRITE_DATA 0x00000002 ACE4_ADD_FILE 0x00000002 ACE4_APPEND_DATA 0x00000004 ACE4_ADD_SUBDIRECTORY 0x00000004 ACE4_READ_NAMED_ATTRS 0x00000008 ACE4_WRITE_NAMED_ATTRS 0x00000010 ACE4_EXECUTE 0x00000020 ACE4_DELETE_CHILD 0x00000040 ACE4_READ_ATTRIBUTES 0x00000080 ACE4_WRITE_ATTRIBUTES 0x00000100 ACE4_DELETE 0x00010000 ACE4_READ_ACL 0x00020000 ACE4_WRITE_ACL 0x00040000 ACE4_WRITE_OWNER 0x00080000 ACE4_SYNCHRONIZE 0x00100000 This matches quite directly the file access rights available in Windows.= However, it omits one special access right that has to do with accessing= AUDIT and ALARM ACL entries - the ACCESS_SYSTEM_SECURITY access right.= According to MSDN ("SACL Access Right"): The ACCESS_SYSTEM_SECURITY access right is not valid in a DACL because DACLs do not control access to a SACL. However, you can use the ACCESS_SYSTEM_SECURITY access right in a SACL to audit attempts to use the access right. This flag is not used in ALLOW and DENY ACEs. However, it can appear in an= AUDIT or ALARM ACE, in which case it can be useful for auditing= unauthorized attempts to access the AUDIT/ALARM part of a file's access= control list. I suggest that it would be straightforward and useful to define a value for= this access right in SFTP. denis From recovered-from-private-archive Thu Mar 23 23:05:06 2006 User-Agent: Mutt/1.5.9i Reply-To: ietf-ssh@netbsd.org In-Reply-To: <20060210231606.GB15641@chiark.greenend.org.uk> Content-Type: text/plain; charset=us-ascii To: ietf-ssh@netbsd.org References: <20060210231606.GB15641@chiark.greenend.org.uk> Mime-Version: 1.0 From: Jacob Nevins Date: Sun, 26 Feb 2006 22:09:51 +0000 Received: by mail.netbsd.org (Postfix, from userid 0) id 9BAF163B396; Sun, 26 Feb 2006 22:09:52 +0000 (UTC) Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mail.netbsd.org (Postfix) with ESMTP id 3AF4E63B3C8 for ; Sun, 26 Feb 2006 22:09:51 +0000 (UTC) Received: by chiark.greenend.org.uk (Debian Exim 3.36 #1) with local (return-path jacobn@chiark.greenend.org.uk) id 1FDU5P-0004Q6-00 for ietf-ssh@netbsd.org; Sun, 26 Feb 2006 22:09:51 +0000 Delivered-To: ietf-ssh@netbsd.org Content-Disposition: inline Subject: Re: [(nowhere)] FW: Please re-review draft-ietf-secsh-publickeyfile [I06-050928-0006] Precedence: list Sender: ietf-ssh-owner@NetBSD.org X-Original-To: ietf-ssh@netbsd.org Message-ID: <20060226220951.GA24363@chiark.greenend.org.uk> I wrote: > I guess RFC2434/BCP0026 might be of use? > > Could it be as simple as moving the language about "IETF Consensus" and > X-headers to the IANA Considerations section, and referencing 2434? Sam Hartman threatened to bounce this draft if nothing happened before the end of February. Something has happened, but then it all went quiet again. So, here's a minimal attempt to sort out the "IANA Considerations" section, based on reading RFC 2434: Section 3.3 "Key file header", change the following text: before: Compliant implementations MUST ignore unrecognized header fields. Implementations SHOULD preserve unrecognized header fields when manipulating the key file. after: The space of header-tags is managed as described in Section 5. Compliant implementations MUST ignore headers with unrecognized header-tags. Implementations SHOULD preserve such unrecognized headers when manipulating the key file. Section 3.3.3 "New Headers": replace whole section: before: 3.3.3. New Headers Headers with header-tags beginning with "x-" are considered experimental, and may be used without IETF consensus. All other headers are reserved for use only by IETF consensus. after: 3.3.3. Private Use Headers Headers with header-tags beginning with "x-" are reserved for private use. Section 5 "IANA Considerations": replace entire section text: before: An IANA registry needs to be created containing the defined header- tags. These are 'subject' and 'comment' after: Section 3.3 defines a new namespace of "Header-tags". These are US-ASCII strings of maximum length 64 characters, and are case-insensitive. The following header-tags are defined by this document: subject comment In addition, all header-tags beginning with "x-" are reserved for Private Use, as defined in [RFC2434]. Further allocations are to be made by IETF Consensus, as defined in [RFC2434]. Section 7.2 "Informative References" (right section?): add one: [RFC2434] Narten, T. and Alvestrand, H., "Guidelines for Writing an IANA Considerations Section in RFCs", RFC 2434, October 1998. From recovered-from-private-archive Thu Mar 23 23:05:06 2006 User-Agent: Thunderbird 1.5 (Windows/20051025) Content-Type: text/plain; charset=ISO-8859-1; format=flowed In-Reply-To: <20060226220951.GA24363@chiark.greenend.org.uk> To: ietf-ssh@netbsd.org References: <20060226220951.GA24363@chiark.greenend.org.uk> <20060226220951.GA24363@chiark.greenend.org.uk> MIME-Version: 1.0 From: Joseph Galbraith Date: Mon, 27 Feb 2006 08:43:17 -0700 Received: by mail.netbsd.org (Postfix, from userid 0) id 594F263B154; Mon, 27 Feb 2006 15:43:23 +0000 (UTC) Received: from vandyke.com (mail.vandyke.com [204.134.9.1]) by mail.netbsd.org (Postfix) with ESMTP id 7760363B11F for ; Mon, 27 Feb 2006 15:43:22 +0000 (UTC) Received: from [127.0.0.1] (HELO [127.0.0.3]) by vandyke.com (CommuniGate Pro SMTP 3.4.7) with ESMTP id 8598822 for ietf-ssh@netbsd.org; Mon, 27 Feb 2006 08:43:27 -0700 Delivered-To: ietf-ssh@netbsd.org Subject: Re: [(nowhere)] FW: Please re-review draft-ietf-secsh-publickeyfile [I06-050928-0006] Content-Transfer-Encoding: 7bit Precedence: list Sender: ietf-ssh-owner@NetBSD.org X-Original-To: ietf-ssh@netbsd.org Message-ID: <44031E15.4090903@vandyke.com> Thank you! I will make the changes you suggest and re-publish this evening or tomorrow morning so we beat the meeting cutoff. Thanks, Joseph Jacob Nevins wrote: > I wrote: >> I guess RFC2434/BCP0026 might be of use? >> >> Could it be as simple as moving the language about "IETF Consensus" and >> X-headers to the IANA Considerations section, and referencing 2434? > > Sam Hartman threatened to bounce this draft if nothing happened before > the end of February. Something has happened, but then it all went quiet > again. So, here's a minimal attempt to sort out the "IANA > Considerations" section, based on reading RFC 2434: > > Section 3.3 "Key file header", change the following text: > > before: > Compliant implementations MUST ignore unrecognized header fields. > Implementations SHOULD preserve unrecognized header fields when > manipulating the key file. > > after: > The space of header-tags is managed as described in Section 5. > > Compliant implementations MUST ignore headers with unrecognized > header-tags. Implementations SHOULD preserve such unrecognized > headers when manipulating the key file. > > Section 3.3.3 "New Headers": replace whole section: > > before: > 3.3.3. New Headers > > Headers with header-tags beginning with "x-" are considered > experimental, and may be used without IETF consensus. > > All other headers are reserved for use only by IETF consensus. > > after: > 3.3.3. Private Use Headers > > Headers with header-tags beginning with "x-" are reserved for > private use. > > Section 5 "IANA Considerations": replace entire section text: > > before: > An IANA registry needs to be created containing the defined header- > tags. These are 'subject' and 'comment' > > after: > Section 3.3 defines a new namespace of "Header-tags". These are > US-ASCII strings of maximum length 64 characters, and are > case-insensitive. > > The following header-tags are defined by this document: > subject > comment > > In addition, all header-tags beginning with "x-" are reserved for > Private Use, as defined in [RFC2434]. > > Further allocations are to be made by IETF Consensus, as defined > in [RFC2434]. > > Section 7.2 "Informative References" (right section?): add one: > > [RFC2434] Narten, T. and Alvestrand, H., "Guidelines for Writing an > IANA Considerations Section in RFCs", RFC 2434, > October 1998. >