From isms-bounces@lists.ietf.org Wed Mar 01 14:06:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEWem-0007ee-2R; Wed, 01 Mar 2006 14:06:40 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEWel-0007eZ-4a for isms@ietf.org; Wed, 01 Mar 2006 14:06:39 -0500 Received: from minbar.fac.cs.cmu.edu ([128.2.185.161]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FEWej-0003Lg-Tw for isms@ietf.org; Wed, 01 Mar 2006 14:06:39 -0500 Received: from SIRIUS.FAC.CS.CMU.EDU ([128.2.209.170]) by minbar.fac.cs.cmu.edu id aa21126; 1 Mar 2006 14:06 EST Date: Wed, 01 Mar 2006 14:06:27 -0500 From: Jeffrey Hutzelman To: Randy Presuhn , isms@ietf.org Subject: Re: [Isms] ssh transport domain and transport address definitions Message-ID: <8CEBD77847B07D4A94756BF7@sirius.fac.cs.cmu.edu> In-Reply-To: <000601c63cc6$42b6b860$6401a8c0@oemcomputer> References: <04f501c63cc4$c203bfc0$0200a8c0@DJYXPY41> <000601c63cc6$42b6b860$6401a8c0@oemcomputer> Originator-Info: login-token=Mulberry:01U1MIqL27fRyfnoAphtE4F+rFP9Pah4HAyDYNidM=; token_authority=postmaster@andrew.cmu.edu X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Cc: X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org On Tuesday, February 28, 2006 04:22:43 PM -0800 Randy Presuhn wrote: > Hi - > >> From: "David B Harrington" >> To: "'Randy Presuhn'" ; >> Sent: Tuesday, February 28, 2006 4:11 PM >> Subject: RE: [Isms] ssh transport domain and transport address >> definitions > ... >> Please send wordsmithed text. > ... > > When the value is a hostname, it is encoded in ASCII using the > IDNA protocol [RFC3490]. I think you need to be more specific than that. You need to refer to RFC3490 section 4, and specify in each case whether the domain name is being used as a query or storage string. If you want to treat this as an IDN-unaware domain name slot and encode each label using ToASCII, you need to say that explicitly. Incidentally, you should ask the DNS folks about this, but I expect they will tell you that new protocols should specify that IDN's be encoded as UTF-8, not punycode. The latter encoding was intended for use in situations with severe limitations on the encoded form, such as those found in the DNS protocol and some legacy applications. We don't have those limitations here, and using punycode makes about as much sense as using UTF-7. -- Jeff _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Wed Mar 01 21:13:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEdJz-000388-Hy; Wed, 01 Mar 2006 21:13:39 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEdF6-00079O-1C for isms@ietf.org; Wed, 01 Mar 2006 21:08:36 -0500 Received: from pop-siberian.atl.sa.earthlink.net ([207.69.195.71]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEd0d-0002tx-V0 for isms@ietf.org; Wed, 01 Mar 2006 20:53:42 -0500 Received: from h-68-165-4-155.snvacaid.dynamic.covad.net ([68.165.4.155] helo=oemcomputer) by pop-siberian.atl.sa.earthlink.net with smtp (Exim 3.36 #10) id 1FEd0d-0005p5-00 for isms@ietf.org; Wed, 01 Mar 2006 20:53:39 -0500 Message-ID: <000401c63d9c$613cb9c0$6401a8c0@oemcomputer> From: "Randy Presuhn" To: References: <04f501c63cc4$c203bfc0$0200a8c0@DJYXPY41> <000601c63cc6$42b6b860$6401a8c0@oemcomputer> <8CEBD77847B07D4A94756BF7@sirius.fac.cs.cmu.edu> Subject: Re: [Isms] ssh transport domain and transport address definitions Date: Wed, 1 Mar 2006 17:55:26 -0800 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.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Cc: X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org Hi - I've long been in the "just use UTF-8" camp, and it would suit me just fine in this case as well. As I said earlier, as long as the DESCRIPTION makes it clear what is to be done, I'll be happy. The question is how does the WG want it to work? Randy ----- Original Message ----- > From: "Jeffrey Hutzelman" > To: "Randy Presuhn" ; > Sent: Wednesday, March 01, 2006 11:06 AM > Subject: Re: [Isms] ssh transport domain and transport address definitions > > > > On Tuesday, February 28, 2006 04:22:43 PM -0800 Randy Presuhn > wrote: > > > Hi - > > > >> From: "David B Harrington" > >> To: "'Randy Presuhn'" ; > >> Sent: Tuesday, February 28, 2006 4:11 PM > >> Subject: RE: [Isms] ssh transport domain and transport address > >> definitions > > ... > >> Please send wordsmithed text. > > ... > > > > When the value is a hostname, it is encoded in ASCII using the > > IDNA protocol [RFC3490]. > > I think you need to be more specific than that. You need to refer to > RFC3490 section 4, and specify in each case whether the domain name is > being used as a query or storage string. If you want to treat this as an > IDN-unaware domain name slot and encode each label using ToASCII, you need > to say that explicitly. > > Incidentally, you should ask the DNS folks about this, but I expect they > will tell you that new protocols should specify that IDN's be encoded as > UTF-8, not punycode. The latter encoding was intended for use in > situations with severe limitations on the encoded form, such as those found > in the DNS protocol and some legacy applications. We don't have those > limitations here, and using punycode makes about as much sense as using > UTF-7. > > -- Jeff _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Thu Mar 02 04:15:33 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEjuG-0003xZ-UW; Thu, 02 Mar 2006 04:15:32 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEjuF-0003wk-DP for isms@ietf.org; Thu, 02 Mar 2006 04:15:31 -0500 Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEjuD-0004qm-Uo for isms@ietf.org; Thu, 02 Mar 2006 04:15:31 -0500 Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id A16134D651; Thu, 2 Mar 2006 10:15:28 +0100 (CET) Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 11991-09; Thu, 2 Mar 2006 10:15:26 +0100 (CET) Received: from boskop.local (unknown [10.222.1.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.iu-bremen.de (Postfix) with ESMTP id A98394D2C6; Thu, 2 Mar 2006 10:15:26 +0100 (CET) Received: by boskop.local (Postfix, from userid 501) id 7350D6171DB; Thu, 2 Mar 2006 10:15:24 +0100 (CET) Date: Thu, 2 Mar 2006 10:15:23 +0100 From: Juergen Schoenwaelder To: Randy Presuhn , Bert Wijnen , Dan Romascanu Subject: Re: [Isms] ssh transport domain and transport address definitions Message-ID: <20060302091523.GA9883@boskop.local> Mail-Followup-To: Randy Presuhn , Bert Wijnen , Dan Romascanu , isms@ietf.org References: <04f501c63cc4$c203bfc0$0200a8c0@DJYXPY41> <000601c63cc6$42b6b860$6401a8c0@oemcomputer> <8CEBD77847B07D4A94756BF7@sirius.fac.cs.cmu.edu> <000401c63d9c$613cb9c0$6401a8c0@oemcomputer> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000401c63d9c$613cb9c0$6401a8c0@oemcomputer> User-Agent: Mutt/1.5.10i X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de X-Spam-Score: 0.0 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Cc: isms@ietf.org X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: j.schoenwaelder@iu-bremen.de List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org On Wed, Mar 01, 2006 at 05:55:26PM -0800, Randy Presuhn wrote: > I've long been in the "just use UTF-8" camp, and it would > suit me just fine in this case as well. As I said earlier, as long > as the DESCRIPTION makes it clear what is to be done, I'll > be happy. The question is how does the WG want it to work? I think this calls for a more general decision since I am not sure we are well served to handle this differently from WG to WG. The question is whether it is generally realistic to assume that devices do IDN processing and conversion or whether this is the job of the management application. * The InetAddressDNS TC definition is rather vague since when it was created, discussion how to handle IDNs were ongoing and it was not clear what the outcome would be. So the TC is just an OCTET STRING and the DESCRIPTION is silent about IDN stuff (which means we need to clarify this anyway and we might do it in either direction). * The TransportAddressDns TC is basically what Dave Harrington posted here and it says that the colon is ASCII code point 0x3A and the following number is encoded in ASCII digits. Again, it is rather unclear what the character set of the hostname actually is. We might clarify this in either direction. * The DnsName TC uses the DNS protocol encoding of names so this seems to be clearly limited to 7-bit ASCII. * The sysName object description says: By convention, this is the node's fully-qualified domain name and it uses the DisplayString TC. * wwwServiceName contains a fully qualified domain name and is of type DisplayString. * sctpAssocRemHostName uses the DNS protocol encoding and clearly says US-ASCII. * assocRemoteApplication may contain a domain name and uses an SnmpAdminString and it is unclear how to represent IDNs * OwnerString (IF-MIB) may contain a domain name and it seems to be ASCII (but note that this TC is deprecated so we can probably ignore it). * applOpenConnectionNearEndpoint, applOpenConnectionFarEndpoint, applPastConNearEndpoint, applPastConFarEndpoint, applOpenConnectionNearEndpoint, applOpenConnectionFarEndpoint all contains domain names and they use SnmpAdminString. Again, it is unclear how to represent IDNs. I am sure there are more objects that may contain DNS names. If you know some, please let me know. Perhaps we should write up a short document which explains the issue and clarifies for all TCs/object we know of how they are supposed to deal with IDNs. In addition, such a document should specify that any updates to the documents in question should clarify the issues and define the general strategy how SNMP MIB modules should deal with IDNs. Such an activity, however, does not really fall into the ISMS charter. Perhaps the OPS NM ADs (the leaving and the coming) can discuss this and propose whether they want actions to be taken and if so under what umbrella. /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Mon Mar 06 15:50:07 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGMec-00021P-Vd; Mon, 06 Mar 2006 15:50:06 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGMeY-0001sv-BA; Mon, 06 Mar 2006 15:50:02 -0500 Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGMeY-0001Lm-2b; Mon, 06 Mar 2006 15:50:02 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k26Ko1BX024354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Mar 2006 20:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FGMeX-00054t-NX; Mon, 06 Mar 2006 15:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 06 Mar 2006 15:50:01 -0500 X-Spam-Score: 0.3 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: isms@ietf.org Subject: [Isms] I-D ACTION:draft-ietf-isms-secshell-02.txt X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Integrated Security Model for SNMP Working Group of the IETF. Title : Secure Shell Security Model for SNMP Author(s) : J. Salowey, D. Harrington Filename : draft-ietf-isms-secshell-02.txt Pages : 54 Date : 2006-3-6 This memo describes a Security Model for the Simple Network Management Protocol, using the Secure Shell protocol within a Transport Mapping. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isms-secshell-02.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-isms-secshell-02.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-isms-secshell-02.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-3-6101711.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isms-secshell-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isms-secshell-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-3-6101711.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms --NextPart-- From isms-bounces@lists.ietf.org Mon Mar 06 16:05:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGMt9-0004IA-L3; Mon, 06 Mar 2006 16:05:08 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGMeb-0001w4-1U; Mon, 06 Mar 2006 15:50:05 -0500 Received: from [156.154.16.129] (helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGMea-0001NA-VT; Mon, 06 Mar 2006 15:50:05 -0500 Received: from [156.154.24.129] (helo=oak.neustar.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FGMeY-0002v0-Bb; Mon, 06 Mar 2006 15:50:04 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k26Ko1BX024355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Mar 2006 20:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FGMeX-00054y-O6; Mon, 06 Mar 2006 15:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 06 Mar 2006 15:50:01 -0500 X-Spam-Score: -5.9 (-----) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: isms@ietf.org Subject: [Isms] I-D ACTION:draft-ietf-isms-tmsm-01.txt X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Integrated Security Model for SNMP Working Group of the IETF. Title : Transport Mapping Security Model (TMSM) Architectural Extension for the Simple Network Management Protocol (SNMP) Author(s) : D. Harrington, J. Schoenwaelder Filename : draft-ietf-isms-tmsm-01.txt Pages : 52 Date : 2006-3-6 This document describes a Transport Mapping Security Model (TMSM) subsystem for the Simple Network Management Protocol (SNMP) architecture defined in RFC 3411. This document identifies and discusses some key aspects that need to be considered for any transport-mapping-based security model for SNMP. This memo also defines a portion of the Management Information Base (MIB) for managing the Transport Mapping Security Model Subsystem. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isms-tmsm-01.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-isms-tmsm-01.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-isms-tmsm-01.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-3-6102147.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isms-tmsm-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isms-tmsm-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-3-6102147.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms --NextPart-- From isms-bounces@lists.ietf.org Sun Mar 12 05:40:00 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FINzU-0004Y9-6F; Sun, 12 Mar 2006 05:40:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FINzS-0004Tb-Vy for isms@ietf.org; Sun, 12 Mar 2006 05:39:58 -0500 Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FINzQ-0007G4-0o for isms@ietf.org; Sun, 12 Mar 2006 05:39:58 -0500 Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id BDCAB540CD for ; Sun, 12 Mar 2006 11:39:54 +0100 (CET) Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 21572-06; Sun, 12 Mar 2006 11:39:52 +0100 (CET) Received: from boskop.local (unknown [10.222.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.iu-bremen.de (Postfix) with ESMTP id C1BC9540B0; Sun, 12 Mar 2006 11:39:52 +0100 (CET) Received: by boskop.local (Postfix, from userid 501) id 6CC1E62FD3F; Sun, 12 Mar 2006 11:40:46 +0100 (CET) Date: Sun, 12 Mar 2006 11:40:46 +0100 From: Juergen Schoenwaelder To: isms@ietf.org, Vladislav Marinov Message-ID: <20060312104046.GB2103@boskop.local> Mail-Followup-To: isms@ietf.org, Vladislav Marinov References: <20060227201530.GE5695@boskop.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060227201530.GE5695@boskop.local> User-Agent: Mutt/1.5.10i X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de X-Spam-Score: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Cc: Subject: [Isms] Re: ssh transport domain and transport address definitions X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: j.schoenwaelder@iu-bremen.de List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org On Mon, Feb 27, 2006 at 09:15:30PM +0100, Juergen Schoenwaelder wrote: > a) [the opaque solution] > > b) [the "SMI lacks unions" solution, but we reuse TRANSPORT-ADDRESS-MIB] > > c) [the "SMI lacks unions" solution, we prefer to be independent] The current ID specifies the opaque solution, which in principle I agree with. Here is the relevant text plus some comments/questions. TransportAddressSSH ::= TEXTUAL-CONVENTION DISPLAY-HINT "1a" STATUS current DESCRIPTION "[discuss] Represents either a hostname encoded in ASCII using the IDNA protocol [RFC3490] followed by a colon ':' (ASCII character 0x3A) and a decimal port number in ASCII, or an IP address followed by a colon ':' (ASCII character 0x3A) and a decimal port number in ASCII. The name SHOULD be fully qualified whenever possible. This text leaves it open how IP addresses are represented. Note that we have IPv4/IPv6 addresses with and without zone indices. I have clear opinion on the IDNA issue, except that I like to see a consistent strategy to deal with IDNs in future MIB modules. Values of this textual convention are not directly useable as transport-layer addressing information, and require runtime resolution. As such, applications that write them must be prepared for handling errors if such values are not supported, or cannot be resolved (if resolution occurs at the time of the management operation). The DESCRIPTION clause of TransportAddress objects that may have TransportAddressSSH values must fully describe how (and when) such names are to be resolved to IP addresses and vice versa. I am not sure whether this TC is now intented to belong to the family of TransportAddress TCs or not. I think it should not and it belongs to the family of TAddress TCs (and consequently the above paragraph does not make much sense and the TC should be named TAddressSSH rather than TransportAddressSSH). This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair. See comment above. Since I do not consider this an extension of the TransportAddress TCs, this paragraph may not be needed. When this textual convention is used as a syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the OBJECT-TYPE declaration MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers." SYNTAX OCTET STRING (SIZE (1..255)) /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Mon Mar 13 07:07:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIlpw-0005Qv-4Y; Mon, 13 Mar 2006 07:07:44 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIlpu-0005PB-Hm for isms@ietf.org; Mon, 13 Mar 2006 07:07:42 -0500 Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FIlpr-0003wV-3W for isms@ietf.org; Mon, 13 Mar 2006 07:07:42 -0500 Received: from [10.1.1.171] (mito.netlab.nec.de [195.37.70.39]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 9C6C11BAC4D for ; Mon, 13 Mar 2006 13:07:32 +0100 (CET) Date: Mon, 13 Mar 2006 13:07:39 +0100 From: Juergen Quittek To: isms@ietf.org Message-ID: <932DEC691B960095223F6B4F@[10.1.1.171]> X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Cc: Subject: [Isms] draft meeting agenda for Dallas X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org Dear all, Below please find the draft agenda for our session in Dallas. Please send a message to the chairs if you have suggestions for changes. Since we might have remote participants, it would be great if the presenters sent me their slides in advance of the session for uploading them. See you at the session, Juergen -- Juergen Quittek quittek@netlab.nec.de Tel: +49 6221 90511-15 NEC Europe Ltd., Network Laboratories Fax: +49 6221 90511-55 Kurfuersten-Anlage 36, 69115 Heidelberg, Germany http://www.netlab.nec.de ============================================ Integrated Security Model for SNMP WG (isms) Wednesday, March 22 at 0900-1130 ================================ CHAIRS: Juergen Schoenwaelder Juergen Quittek AGENDA: 1) WG Status, Agenda bashing ( 5 min) 2) Discussion of TMSM open issues (40 min) - draft-ietf-isms-tmsm-01.txt 3) Discussion of SSH model open issues (60 min) - draft-ietf-isms-secshell-02.txt 4) Wrap up ( 5 min) - review of action points INTERNET DRAFTS: - Secure Shell Security Model for SNMP - Transport Mapping Security Model (TMSM) for the Simple Network Management Protocol RELATED DRAFTS: - RADIUS NAS-Management Authorization _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Mon Mar 13 12:08:14 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIqWk-0007vu-6C; Mon, 13 Mar 2006 12:08:14 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIqWj-0007vp-Iw for isms@ietf.org; Mon, 13 Mar 2006 12:08:13 -0500 Received: from sccrmhc13.comcast.net ([63.240.77.83]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FIqWi-0005AB-9f for isms@ietf.org; Mon, 13 Mar 2006 12:08:13 -0500 Received: from djyxpy41 (c-24-128-66-70.hsd1.nh.comcast.net[24.128.66.70]) by comcast.net (sccrmhc13) with SMTP id <2006031317081101300o7ebue>; Mon, 13 Mar 2006 17:08:11 +0000 From: "David B Harrington" To: "'Juergen Quittek'" , , Subject: RE: [Isms] draft meeting agenda for Dallas Date: Mon, 13 Mar 2006 12:08:04 -0500 Message-ID: <047901c646c0$b1a5b510$0200a8c0@DJYXPY41> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <932DEC691B960095223F6B4F@[10.1.1.171]> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcZGlrybjjwTxZmVTuClL7YBA7uwRQAHVFBg X-Spam-Score: 0.0 (/) X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7 Cc: X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietfdbh@comcast.net List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org Hi Juergen, Should the agenda include a presentation reviewing the interim meeting, the proposed decisions, and the action items? Will the discussion be oriented toward the list of open issues from the wiki? If so, they should be summarized with the mailing list input so far. You should probably give the URL for the wiki in the agenda. Will the discussion be oriented toward the list of open issues from the [todo] and [discuss] markers in the documents? If so, they should be summarized with the mailing list input so far. This [todo] and [discuss] approach did not seem very effective at IETF64, because there are so many large issues we have not resolved. One action item from the interim was to arrange an editing meeting at IETF65. Do you intend to do so? What specific goals do you hope to achieve at such an editing meeting? My calendar is filling up; if we are going to have an editing meeting, let's get the date and time nailed down, please. Sunday may not be a good choice because people may not be plannign to arrive early enough. I know some of the SNMP experts have chosen to not attend IETF65, and others are planning to leave early in the week. That's going to really limit the options. The editing meeting at IETF64 went down a specific tangent/rathole (notifications and callback) and we never reached any clear decisions or did any editing. The interim became an education meeting, and it failed to achieve clear decisions for forward progress or provide any specific text for the documents. If we are going to have another editing meeting, can we do some actual editing of the documents? Let's address the ratholes on the mailing list and during the formal session, and avoid lots of review of documents people should have already read. David Harrington Standards Manager, IP OAM and Security FutureWei Technologies, a Huawei company dharrington@huawei.com dbharrington@comcast.net ietfdbh@comcast.net > -----Original Message----- > From: Juergen Quittek [mailto:quittek@netlab.nec.de] > Sent: Monday, March 13, 2006 7:08 AM > To: isms@ietf.org > Subject: [Isms] draft meeting agenda for Dallas > > Dear all, > > Below please find the draft agenda for our session in Dallas. > Please send a message to the chairs if you have suggestions > for changes. > > Since we might have remote participants, it would be great > if the presenters sent me their slides in advance of the session > for uploading them. > > See you at the session, > > Juergen > -- > Juergen Quittek quittek@netlab.nec.de Tel: +49 > 6221 90511-15 > NEC Europe Ltd., Network Laboratories Fax: +49 > 6221 90511-55 > Kurfuersten-Anlage 36, 69115 Heidelberg, Germany > http://www.netlab.nec.de > > > ============================================ > Integrated Security Model for SNMP WG (isms) > > Wednesday, March 22 at 0900-1130 > ================================ > > CHAIRS: Juergen Schoenwaelder > Juergen Quittek > > AGENDA: > > 1) WG Status, Agenda bashing ( 5 min) > > 2) Discussion of TMSM open issues (40 min) > - draft-ietf-isms-tmsm-01.txt > > 3) Discussion of SSH model open issues (60 min) > - draft-ietf-isms-secshell-02.txt > > 4) Wrap up ( 5 min) > - review of action points > > > INTERNET DRAFTS: > > - Secure Shell Security Model for SNMP > > > - Transport Mapping Security Model (TMSM) for the Simple Network > Management Protocol > > > > RELATED DRAFTS: > > - RADIUS NAS-Management Authorization > > > > _______________________________________________ > Isms mailing list > Isms@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/isms > _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Mon Mar 20 04:44:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLGwF-0005Om-Eh; Mon, 20 Mar 2006 04:44:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLGwE-0005OS-4h for isms@ietf.org; Mon, 20 Mar 2006 04:44:34 -0500 Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLGwC-0002sB-Ei for isms@ietf.org; Mon, 20 Mar 2006 04:44:34 -0500 Received: from [10.0.1.3] (unknown [130.129.132.169]) by kyoto.netlab.nec.de (Postfix) with ESMTP id A552D1BAC4D; Mon, 20 Mar 2006 10:43:36 +0100 (CET) Date: Mon, 20 Mar 2006 10:44:30 +0100 From: Juergen Quittek To: ietfdbh@comcast.net, isms@ietf.org, j.schoenwaelder@iu-bremen.de Subject: RE: [Isms] draft meeting agenda for Dallas Message-ID: In-Reply-To: <047901c646c0$b1a5b510$0200a8c0@DJYXPY41> References: <047901c646c0$b1a5b510$0200a8c0@DJYXPY41> X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c Cc: X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org Hi Dave, --On 3/13/06 12:08 PM -0500 David B Harrington wrote: > Hi Juergen, > > Should the agenda include a presentation reviewing the interim > meeting, the proposed decisions, and the action items? Would this contain more information than the minutes? I think the minutes cover the results of the interim meeting well. > Will the discussion be oriented toward the list of open issues from > the wiki? If so, they should be summarized with the mailing list input > so far. You should probably give the URL for the wiki in the agenda. Yes, I will see if updates are still possible. > Will the discussion be oriented toward the list of open issues from > the [todo] and [discuss] markers in the documents? If so, they should > be summarized with the mailing list input so far. This [todo] and > [discuss] approach did not seem very effective at IETF64, because > there are so many large issues we have not resolved. We should focus on a few essential ones that are well suited to be solved at a regular WG session. > One action item from the interim was to arrange an editing meeting at > IETF65. Do you intend to do so? What specific goals do you hope to > achieve at such an editing meeting? My calendar is filling up; if we > are going to have an editing meeting, let's get the date and time > nailed down, please. Sunday may not be a good choice because people > may not be plannign to arrive early enough. I know some of the SNMP > experts have chosen to not attend IETF65, and others are planning to > leave early in the week. That's going to really limit the options. Unfortunately, I missed the welcome reception (stuck in the flood) for exploring availability of people during the week. It would be beneficial to have such a meeting. Let's see if we can still arrange it. > The editing meeting at IETF64 went down a specific tangent/rathole > (notifications and callback) and we never reached any clear decisions > or did any editing. The interim became an education meeting, and it > failed to achieve clear decisions for forward progress or provide any > specific text for the documents. If we are going to have another > editing meeting, can we do some actual editing of the documents? Let's > address the ratholes on the mailing list and during the formal > session, and avoid lots of review of documents people should have > already read. Agreed. > David Harrington > Standards Manager, IP OAM and Security > FutureWei Technologies, a Huawei company > dharrington@huawei.com > dbharrington@comcast.net > ietfdbh@comcast.net > > >> -----Original Message----- >> From: Juergen Quittek [mailto:quittek@netlab.nec.de] >> Sent: Monday, March 13, 2006 7:08 AM >> To: isms@ietf.org >> Subject: [Isms] draft meeting agenda for Dallas >> >> Dear all, >> >> Below please find the draft agenda for our session in Dallas. >> Please send a message to the chairs if you have suggestions >> for changes. >> >> Since we might have remote participants, it would be great >> if the presenters sent me their slides in advance of the session >> for uploading them. >> >> See you at the session, >> >> Juergen >> -- >> Juergen Quittek quittek@netlab.nec.de Tel: +49 >> 6221 90511-15 >> NEC Europe Ltd., Network Laboratories Fax: +49 >> 6221 90511-55 >> Kurfuersten-Anlage 36, 69115 Heidelberg, Germany >> http://www.netlab.nec.de >> >> >> ============================================ >> Integrated Security Model for SNMP WG (isms) >> >> Wednesday, March 22 at 0900-1130 >> ================================ >> >> CHAIRS: Juergen Schoenwaelder >> Juergen Quittek >> >> AGENDA: >> >> 1) WG Status, Agenda bashing ( 5 min) >> >> 2) Discussion of TMSM open issues (40 min) >> - draft-ietf-isms-tmsm-01.txt >> >> 3) Discussion of SSH model open issues (60 min) >> - draft-ietf-isms-secshell-02.txt >> >> 4) Wrap up ( 5 min) >> - review of action points >> >> >> INTERNET DRAFTS: >> >> - Secure Shell Security Model for SNMP >> >> >> - Transport Mapping Security Model (TMSM) for the Simple Network >> Management Protocol >> >> >> >> RELATED DRAFTS: >> >> - RADIUS NAS-Management Authorization >> >> >> >> _______________________________________________ >> Isms mailing list >> Isms@lists.ietf.org >> https://www1.ietf.org/mailman/listinfo/isms >> > > _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Mon Mar 20 05:01:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLHCg-0007CL-Ej; Mon, 20 Mar 2006 05:01:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLHCf-0007CE-4y for isms@ietf.org; Mon, 20 Mar 2006 05:01:33 -0500 Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLHCe-0003SX-T0 for isms@ietf.org; Mon, 20 Mar 2006 05:01:33 -0500 Received: from [10.0.1.3] (unknown [130.129.132.169]) by kyoto.netlab.nec.de (Postfix) with ESMTP id C9B491BAC4D for ; Mon, 20 Mar 2006 11:00:37 +0100 (CET) Date: Mon, 20 Mar 2006 11:01:31 +0100 From: Juergen Quittek To: isms@ietf.org Message-ID: <88C4416ABDD27BEFC3AE972F@dhcp-wired-132-169.ietf65.org> X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: Subject: [Isms] ISMS documents X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org Dear all, Our charter lists four documents to be produced by the WG. For two of them we already have progressing versions. For the other two, the charter sets milestones for initial versions in April. The first of them covers the integration of the SSH-SM into Radius AAA. The chairs asked Kaushik Narayan and David Nelson to act as editors of this document and they kindly volunteered. Still further help is welcome. The second one is an ISMS applicability statement. So far, we do not have editors for it. If you would like to volunteer for contributing to one of these WG documents, please send a message to the WG chairs or contact me before or after the ISMS session. Thanks, Juergen _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Mon Mar 20 12:01:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLNks-0002xR-FZ; Mon, 20 Mar 2006 12:01:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLNkq-0002wJ-UV for isms@ietf.org; Mon, 20 Mar 2006 12:01:16 -0500 Received: from keymaster.sharplabs.com ([216.65.151.107] helo=sharplabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLNkn-0001lZ-HN for isms@ietf.org; Mon, 20 Mar 2006 12:01:16 -0500 Received: from admsrvnt02.enet.sharplabs.com (admsrvnt02 [172.29.225.253] (may be forged)) by sharplabs.com (8.13.1/8.13.1) with ESMTP id k2KH16tf007487; Mon, 20 Mar 2006 09:01:06 -0800 (PST) Received: by admsrvnt02.enet.sharplabs.com with Internet Mail Service (5.5.2657.72) id ; Mon, 20 Mar 2006 09:01:06 -0800 Message-ID: From: "McDonald, Ira" To: "'Juergen Quittek'" , ietfdbh@comcast.net, isms@ietf.org, j.schoenwaelder@iu-bremen.de Subject: RE: [Isms] draft meeting agenda for Dallas Date: Mon, 20 Mar 2006 09:00:59 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="ISO-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org Juergen Quittek wrote: > > Hi Dave, > > --On 3/13/06 12:08 PM -0500 David B Harrington wrote: > > > Hi Juergen, > > > > [snip] > > > > The editing meeting at IETF64 went down a specific tangent/rathole > > (notifications and callback) and we never reached any clear > > decisions > > or did any editing. The interim became an education meeting, and it > > failed to achieve clear decisions for forward progress or > > provide any > > specific text for the documents. If we are going to have another > > editing meeting, can we do some actual editing of the > > documents? Let's > > address the ratholes on the mailing list and during the formal > > session, and avoid lots of review of documents people should have > > already read. > > Agreed. > I suggest you try running your IETF65 meeting with two leaders: (a) Moderator leading technical discussion; and (b) Facilitator managing the flow of the meeting. The Facilitator should politely stop rathole topics and turn them quickly into offline action items for one or more participants (in subsequent email notes). The Facilitator should also be the timekeeper who stops on-agenda topics when they run over. We plan to use this model at our upcoming OSDL Printing Summit with 50 participants (a comparable-sized group of techies?). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.5/284 - Release Date: 3/17/2006 _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Tue Mar 21 20:50:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLsUj-00006X-A9; Tue, 21 Mar 2006 20:50:41 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLsUh-00006S-Aa for isms@ietf.org; Tue, 21 Mar 2006 20:50:39 -0500 Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLsUf-0006ad-1e for isms@ietf.org; Tue, 21 Mar 2006 20:50:39 -0500 Received: from dhcp-wireless-132-169.ietf65.org (DHCP-Wireless-132-169.ietf65.org [130.129.132.169]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 8F04B1BAC4D for ; Wed, 22 Mar 2006 02:49:29 +0100 (CET) Date: Wed, 22 Mar 2006 02:50:38 +0100 From: Juergen Quittek To: isms@ietf.org Message-ID: <5F0D83B911D33B0162D022D3@dhcp-wireless-132-169.ietf65.org> X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Cc: Subject: [Isms] ISMS WG Wiki page X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org Dear all, For preparing the ISMS session tomorrow or for following the session from remote, please have a look at the open issues listed at the ISMS WG Wiki page at . Thanks, Juergen _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Thu Mar 23 14:05:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMV7J-000226-JH; Thu, 23 Mar 2006 14:05:05 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMV7I-000221-Aw for isms@ietf.org; Thu, 23 Mar 2006 14:05:04 -0500 Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMV7H-0000Nb-13 for isms@ietf.org; Thu, 23 Mar 2006 14:05:04 -0500 Received: from dhcp-wireless-132-169.ietf65.org (unknown [130.129.132.169]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 0F4601BAC9E; Thu, 23 Mar 2006 20:03:42 +0100 (CET) Date: Thu, 23 Mar 2006 20:05:05 +0100 From: Juergen Quittek To: housley@vigilsec.com, hartmans-ietf@mit.edu, isms@ietf.org Message-ID: X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Cc: saag@mit.edu Subject: [Isms] ISMS IETF65 session summary X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: isms-bounces@lists.ietf.org The ISMS discussed the open issues concerning the transport mapping security model and SSH security model that were identified at the interim meeting in February. Most of them are concerning SNMP notifications. For all issues full or partial solutions were proposed and the documents will be updated accordingly. For the remaining two documents (radius integration and applicability statement), first versions are scheduled in April. Juergen _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Wed Mar 29 09:39:50 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FObpu-0003GP-Hb; Wed, 29 Mar 2006 09:39:50 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FObps-0003GK-Vh for isms@ietf.org; Wed, 29 Mar 2006 09:39:48 -0500 Received: from ns1.cpanel.btnaccess.com ([205.177.121.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FObpr-0007U8-NY for isms@ietf.org; Wed, 29 Mar 2006 09:39:48 -0500 Received: from [65.213.193.6] (helo=ISODELL001) by ns1.cpanel.btnaccess.com with esmtp (Exim 4.52) id 1FObpq-0008GU-JE for isms@ietf.org; Wed, 29 Mar 2006 09:39:46 -0500 From: "Robert Holliday" To: Date: Wed, 29 Mar 2006 09:39:42 -0500 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcZTPp2RPT8T+/KaT9KS9GpRyQlFbg== X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ns1.cpanel.btnaccess.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - isocore.com X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: 0.0 (/) X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c Cc: Subject: [Isms] ICNS 2006: Early Registration Ends April 1 X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2048724873==" Errors-To: isms-bounces@lists.ietf.org Message-Id: This is a multi-part message in MIME format. --===============2048724873== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0027_01C65314.B51D3780" This is a multi-part message in MIME format. ------=_NextPart_000_0027_01C65314.B51D3780 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit International Conference on Network Security 2006, April 17-19, Reston, Virginia Only a few days remain to take advantage of Early Bird Specials when registering for ICNS2006. All those registering before April 1 receive will receive a $200 dollar discount. Don't miss out on the chance to interact with industry leaders in a personal setting and unique format. Technical Program: http://www.isocore.com/networksecurity2006/program.htm Registration: http://www.isocore.com/networksecurity2006/onlineregis.htm ------=_NextPart_000_0027_01C65314.B51D3780 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

International Conference on Network Security 2006, April 17-19, = Reston, Virginia

 

Only a few days remain to = take advantage of Early Bird Specials when registering for ICNS2006.  = All those registering before April 1 receive will receive a $200 dollar = discount.  Don’t miss out on the chance to interact with industry leaders in = a personal setting and unique format.

 

Technical = Program: http://ww= w.isocore.com/networksecurity2006/program.htm

 

Registration= : http:= //www.isocore.com/networksecurity2006/onlineregis.htm

------=_NextPart_000_0027_01C65314.B51D3780-- --===============2048724873== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms --===============2048724873==--