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?