From owner-ietf-cat-wg@lists.Stanford.EDU Fri Jun 1 07:31:40 2001 Received: from lists.Stanford.EDU ([171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA04907 for ; Fri, 1 Jun 2001 07:31:39 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f51AlYa20952 for ietf-cat-wg-out720680; Fri, 1 Jun 2001 03:47:34 -0700 (PDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f51AlXV20947 for ; Fri, 1 Jun 2001 03:47:33 -0700 (PDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03854; Fri, 1 Jun 2001 06:47:10 -0400 (EDT) Message-Id: <200106011047.GAA03854@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-cat-wg@lists.Stanford.EDU From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt Date: Fri, 01 Jun 2001 06:47:10 -0400 Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Common Authentication Technology Working Group of the IETF. Title : SASL GSSAPI mechanisms Author(s) : J. Myers Filename : draft-ietf-cat-sasl-gssapi-05.txt Pages : 14 Date : 31-May-01 The Simple Authentication and Security Layer [SASL] is a method for adding authentication support to connection-based protocols. This document describes the method for using the Generic Security Service Application Program Interface [GSSAPI] in the Simple Authentication and Security Layer [SASL]. This document amends section 7.2 of RFC 2222 [SASL], the definition of the 'GSSAPI' SASL mechanism. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-cat-sasl-gssapi-05.txt 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-cat-sasl-gssapi-05.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-cat-sasl-gssapi-05.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: <20010531122417.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-cat-sasl-gssapi-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-cat-sasl-gssapi-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20010531122417.I-D@ietf.org> --OtherAccess-- --NextPart-- -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Sat Jun 2 16:11:02 2001 Received: from lists.Stanford.EDU ([171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA13311 for ; Sat, 2 Jun 2001 16:11:01 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f52JRmh11285 for ietf-cat-wg-out720680; Sat, 2 Jun 2001 12:27:48 -0700 (PDT) Received: from china.com (TCE-E-7-182-12.bta.net.cn [202.106.182.12]) by lists.Stanford.EDU (8.11.3/8.11.3) with SMTP id f52JRXV11269 for ; Sat, 2 Jun 2001 12:27:34 -0700 (PDT) Received: from china.com([10.1.7.101]) by china.com(AIMC 2.9.5.1) with SMTP id jm23b197e8a; Sun, 03 Jun 2001 03:27:03 +0800 Received: from loki.ietf.org([132.151.1.177]) by china.com(AIMC 2.9.5.1) with SMTP id jm733b17c93c; Fri, 01 Jun 2001 19:35:37 +0800 Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id HAA14897 for ietf-123-outbound.02@ietf.org; Fri, 1 Jun 2001 07:25:00 -0400 (EDT) Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA14627 for ; Fri, 1 Jun 2001 06:47:13 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03854; Fri, 1 Jun 2001 06:47:10 -0400 (EDT) Message-Id: <200106011047.GAA03854@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-cat-wg@lists.Stanford.EDU From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt Date: Fri, 01 Jun 2001 06:47:10 -0400 Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Common Authentication Technology Working Group of the IETF. Title : SASL GSSAPI mechanisms Author(s) : J. Myers Filename : draft-ietf-cat-sasl-gssapi-05.txt Pages : 14 Date : 31-May-01 The Simple Authentication and Security Layer [SASL] is a method for adding authentication support to connection-based protocols. This document describes the method for using the Generic Security Service Application Program Interface [GSSAPI] in the Simple Authentication and Security Layer [SASL]. This document amends section 7.2 of RFC 2222 [SASL], the definition of the 'GSSAPI' SASL mechanism. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-cat-sasl-gssapi-05.txt 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-cat-sasl-gssapi-05.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-cat-sasl-gssapi-05.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: <20010531122417.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-cat-sasl-gssapi-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-cat-sasl-gssapi-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20010531122417.I-D@ietf.org> --OtherAccess-- --NextPart-- -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Tue Jun 5 09:38:24 2001 Received: from lists.Stanford.EDU ([171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA20225 for ; Tue, 5 Jun 2001 09:38:22 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f55D1oR29959 for ietf-cat-wg-out720680; Tue, 5 Jun 2001 06:01:50 -0700 (PDT) Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f55D1nV29954 for ; Tue, 5 Jun 2001 06:01:49 -0700 (PDT) Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [194.39.131.53]) by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id JAA19425 for ; Tue, 5 Jun 2001 09:01:46 -0400 (EDT) Received: from sap-ag.de (smtpde02) by smtpde02.sap-ag.de (out) with ESMTP id PAA02362; Tue, 5 Jun 2001 15:01:50 +0200 (MESZ) From: Martin Rex Message-Id: <200106051300.PAA02623@hw1464.wdf.sap-ag.de> Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt To: jgmyers@netscape.com Date: Tue, 5 Jun 2001 15:00:30 +0200 (METDST) Cc: cat-ietf@mit.edu In-Reply-To: <200106011047.GAA03854@ietf.org> from "Internet-Drafts@ietf.org" at Jun 1, 1 06:47:10 am Reply-To: mrex@sap-ag.de MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-SAP: out X-SAP: out Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Content-Transfer-Encoding: 8bit This I-D missed April 1st by over two months! What nonsense is this with an MD5 hash over an DER-encoded OID to indicate the gssapi mechanism? An ASN.1 OID is meant as a unique identifier and it is supposed to be short. It's plain stupid to use a truncated hash of an ASN.1 OID instead of the OID itself. Quoting from draft-ietf-cat-sasl-gssapi-05.txt: For backwards compatibility with existing implementations of Kerberos V5 and SPNEGO under SASL, the SASL mechanism name for the Kerberos V5 GSSAPI mechanism [GSSAPI-KERBEROS] is "GSSAPI" and the SASL mechanism for the SPNEGO GSSAPI mechanism [SPNEGO] is "GSS-SPNEGO". The SASL mechanism name for any other GSSAPI mechanism is the concatenation of "GSS-" and the Base32 encoding of the first ten bytes of the MD5 hash [MD5] of the ASN.1 DER encoding [ASN1] of the GSSAPI mechanism's OID. Base32 encoding is described later in this document. The Base32 rules on padding characters and characters outside of the base32 alphabet are not relevant to this use of Base32. ... The OID for the SPKM-1 mechanism [SPKM] is 1.3.6.1.5.5.1. The ASN.1 DER encoding of this OID is 06 06 2b 06 01 05 05 01. The MD5 hash of the ASN.1 DER encoding is 57 ee 81 82 4e ac 4d b0 e6 50 9f 60 1f 46 8a 30. The Base32 encoding of the first ten bytes of this is "K7XIDASOVRG3BZSQ". Thus the SASL mechanism name for the SPKM-1 GSSAPI mechanism is "GSS-K7XIDASOVRG3BZSQ". The proposed algorithm to come up with a unique identifier is bloated and complex (requires MD5 and base32-encoding, neither of which is part of ANSI-C). Just use the printable HEX-encoding of the DER-encoded OID element, i.e. for SPKM1: GSS-2B0601050501 Hex-encoding is trivial (even sprintf(3) can be used, and the DER-encoded OID elements are directly available from gss_indicate_mechs(). When converted in printables, a leading length field should be omitted (it is implicit from the printable length). Because of the structure of the OID space, the hex encoding ususally start with "2A" or "2B". -Martin -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Tue Jun 5 11:54:35 2001 Received: from lists.Stanford.EDU ([171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA24116 for ; Tue, 5 Jun 2001 11:54:34 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f55FFl902834 for ietf-cat-wg-out720680; Tue, 5 Jun 2001 08:15:47 -0700 (PDT) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.72.0.53]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f55FFkV02829 for ; Tue, 5 Jun 2001 08:15:46 -0700 (PDT) Received: from rcn.ihtfp.org (me@ORANGE-TOUR.IHTFP.ORG [204.107.200.33]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id LAA02284 for ; Tue, 5 Jun 2001 11:15:40 -0400 (EDT) Received: (from warlord@localhost) by rcn.ihtfp.org (8.9.3) id LAA28010; Tue, 5 Jun 2001 11:15:09 -0400 To: mrex@sap-ag.de Cc: jgmyers@netscape.com, cat-ietf@mit.edu Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt References: <200106051300.PAA02623@hw1464.wdf.sap-ag.de> From: Derek Atkins Date: 05 Jun 2001 11:15:09 -0400 In-Reply-To: Martin Rex's message of "Tue, 5 Jun 2001 15:00:30 +0200 (METDST)" Message-ID: Lines: 61 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Martin, Without reading the rest of the sasl draft to understand the requirements, I can think of a couple of reasons why they might want to do this. One example is if there is a length limit on the size of the SASL mechanism name (20 characters). In that case, you may not be able to use the raw OID, because the 'relevant' bits may fall off the end of the SASL mech name if you just use HEX encoding. By using MD5 (or any other hash) you have a much better spreading of the bits. To put this into perspective, let's say you had two OIDs that looked like 1.3.6.1.5.5.1.1 and 1.3.6.1.5.5.1.2. Let's presume (please don't yell at me if this is wrong -- this is only an example), that the DER encoding of these two OIDs are 06 07 2b 06 01 05 05 01 01 and 06 07 2b 06 01 05 05 01 02 If there truly was a length-limit on the sasl name, then using the raw hex on these encodings wouldn't work, because the difference between the two would 'fall off the end' of the SASL mech string. So, without knowing the requirements for doing things this way, I cannot condemn using MD5 and base32. Kerberos uses MD5, and 3DES, and a lot of other functions which "aren't part of ANSI-C", so how/why is that any different? Besides, you could even use the MD5 code from your Kerberos implementation to implement this. And implementing base32 is REALLY EASY in ANSI-C. It's not like ASN.1; with base32 you at least know your output length exactly based on your input length. -derek Martin Rex writes: > The OID for the SPKM-1 mechanism [SPKM] is 1.3.6.1.5.5.1. The ASN.1 > DER encoding of this OID is 06 06 2b 06 01 05 05 01. The MD5 hash of > the ASN.1 DER encoding is 57 ee 81 82 4e ac 4d b0 e6 50 9f 60 1f 46 > 8a 30. The Base32 encoding of the first ten bytes of this is > "K7XIDASOVRG3BZSQ". Thus the SASL mechanism name for the SPKM-1 > GSSAPI mechanism is "GSS-K7XIDASOVRG3BZSQ". > > > The proposed algorithm to come up with a unique identifier is > bloated and complex (requires MD5 and base32-encoding, neither > of which is part of ANSI-C). > > Just use the printable HEX-encoding of the DER-encoded OID element, > i.e. for SPKM1: GSS-2B0601050501 > Hex-encoding is trivial (even sprintf(3) can be used, and the > DER-encoded OID elements are directly available from gss_indicate_mechs(). > > When converted in printables, a leading length field should be omitted > (it is implicit from the printable length). Because of the structure > of the OID space, the hex encoding ususally start with "2A" or "2B". -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord@MIT.EDU PGP key available -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Tue Jun 5 13:02:22 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA26136 for ; Tue, 5 Jun 2001 13:02:21 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f55GF7005651 for ietf-cat-wg-out720680; Tue, 5 Jun 2001 09:15:07 -0700 (PDT) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.72.0.53]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f55GF6V05636 for ; Tue, 5 Jun 2001 09:15:06 -0700 (PDT) Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [194.39.131.53]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id MAA22730; Tue, 5 Jun 2001 12:14:55 -0400 (EDT) Received: from sap-ag.de (smtpde02) by smtpde02.sap-ag.de (out) with ESMTP id SAA07894; Tue, 5 Jun 2001 18:15:37 +0200 (MESZ) From: Martin Rex Message-Id: <200106051614.SAA03673@hw1464.wdf.sap-ag.de> Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt To: warlord@mit.edu (Derek Atkins) Date: Tue, 5 Jun 2001 18:14:23 +0200 (METDST) Cc: cat-ietf@mit.edu In-Reply-To: from "Derek Atkins" at Jun 5, 1 11:15:09 am Reply-To: mrex@sap-ag.de MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-SAP: out X-SAP: out Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Content-Transfer-Encoding: 8bit Derek Atkins wrote: > > Without reading the rest of the sasl draft to understand the > requirements, I can think of a couple of reasons why they might want > to do this. > > One example is if there is a length limit on the size of the SASL > mechanism name (20 characters). In that case, you may not be able to > use the raw OID, because the 'relevant' bits may fall off the end of > the SASL mech name if you just use HEX encoding. By using MD5 (or any > other hash) you have a much better spreading of the bits. > > To put this into perspective, let's say you had two OIDs that looked like > 1.3.6.1.5.5.1.1 and 1.3.6.1.5.5.1.2. Let's presume (please don't yell > at me if this is wrong -- this is only an example), that the DER encoding > of these two OIDs are > 06 07 2b 06 01 05 05 01 01 > and 06 07 2b 06 01 05 05 01 02 Btw. I suggested not to include the OID-tag (06) and the length field (07). The reason why using a hash is bad is that you can't reverse it. The OID in GSS-API is meant to identify the GSS-API mechanism. If the peer is presented only with the truncated hash, it has no possibility to figure out what mechanism is meant if there is no match with the mechanism known at the moment. The OIDs give you at least a starting point to look for the mechanism (spec or vendor). > > If there truly was a length-limit on the sasl name, then using the raw > hex on these encodings wouldn't work, because the difference between > the two would 'fall off the end' of the SASL mech string. Using the shorter prefix "G-" plus the hex encoded octets of the OID elements should give enough space for all *reasonable* GSS-API mechanism OIDs. If they really have a size problem, maybe they should be using base64 instead of hex (or base32) since it generates smaller output and is more commonly used -- or is there an even worse restriction on the length *and* value? > > So, without knowing the requirements for doing things this way, I > cannot condemn using MD5 and base32. Kerberos uses MD5, and 3DES, and > a lot of other functions which "aren't part of ANSI-C", so how/why is > that any different? Besides, you could even use the MD5 code from > your Kerberos implementation to implement this. And implementing > base32 is REALLY EASY in ANSI-C. It's not like ASN.1; with base32 you > at least know your output length exactly based on your input length. MD5 has been published as sample C-Code in RFC 1321, the Base32 sample C-Code is listed in the appendix of this draft. Getting the code is not the problem I was referring to. It is the excessive code and complexity that I'm objecting to. > > -derek > > Martin Rex writes: > > > The OID for the SPKM-1 mechanism [SPKM] is 1.3.6.1.5.5.1. The ASN.1 > > DER encoding of this OID is 06 06 2b 06 01 05 05 01. The MD5 hash of > > the ASN.1 DER encoding is 57 ee 81 82 4e ac 4d b0 e6 50 9f 60 1f 46 > > 8a 30. The Base32 encoding of the first ten bytes of this is > > "K7XIDASOVRG3BZSQ". Thus the SASL mechanism name for the SPKM-1 > > GSSAPI mechanism is "GSS-K7XIDASOVRG3BZSQ". > > > > > > The proposed algorithm to come up with a unique identifier is > > bloated and complex (requires MD5 and base32-encoding, neither > > of which is part of ANSI-C). > > > > Just use the printable HEX-encoding of the DER-encoded OID element, > > i.e. for SPKM1: GSS-2B0601050501 > > Hex-encoding is trivial (even sprintf(3) can be used, and the > > DER-encoded OID elements are directly available from gss_indicate_mechs(). > > > > When converted in printables, a leading length field should be omitted > > (it is implicit from the printable length). Because of the structure > > of the OID space, the hex encoding ususally start with "2A" or "2B". -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Tue Jun 5 13:30:46 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA26769 for ; Tue, 5 Jun 2001 13:30:45 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f55GjFu07852 for ietf-cat-wg-out720680; Tue, 5 Jun 2001 09:45:15 -0700 (PDT) Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f55GjEV07847 for ; Tue, 5 Jun 2001 09:45:14 -0700 (PDT) Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [194.39.131.53]) by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id MAA04029; Tue, 5 Jun 2001 12:45:12 -0400 (EDT) Received: from sap-ag.de (smtpde02) by smtpde02.sap-ag.de (out) with ESMTP id SAA01753; Tue, 5 Jun 2001 18:44:05 +0200 (MESZ) From: Martin Rex Message-Id: <200106051642.SAA03791@hw1464.wdf.sap-ag.de> Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt To: warlord@mit.edu (Derek Atkins) Date: Tue, 5 Jun 2001 18:42:47 +0200 (METDST) Cc: cat-ietf@mit.edu In-Reply-To: from "Derek Atkins" at Jun 5, 1 11:15:09 am Reply-To: mrex@sap-ag.de MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-SAP: out X-SAP: out Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Content-Transfer-Encoding: 8bit Derek Atkins wrote: > > Without reading the rest of the sasl draft to understand the > requirements, I can think of a couple of reasons why they might want > to do this. > > One example is if there is a length limit on the size of the SASL > mechanism name (20 characters). In that case, you may not be able to > use the raw OID, because the 'relevant' bits may fall off the end of > the SASL mech name if you just use HEX encoding. By using MD5 (or any > other hash) you have a much better spreading of the bits. OUCH! You're right, I didn't know about that size limit for SASL mechanisms. It's plain stupid to define such a seriously limited namespace in the first place. The SASL spec (rfc2222) apparently didn't receive any serious peer review before it was put onto standards track. Quoting from rfc2222.txt: The command has a required argument identifying a SASL mechanism.^M SASL mechanisms are named by strings, from 1 to 20 characters in^M length, consisting of upper-case letters, digits, hyphens, and/or^M underscores. SASL mechanism names must be registered with the IANA.^M Procedures for registering new SASL mechanisms are given in the^M section "Registration procedures"^M Limiting the available namespace in size and valid characters in such a fashion is about as reasonalbe as claiming that 640KByte of RAM is enough for applications ... -Martin -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Tue Jun 5 13:42:43 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA27034 for ; Tue, 5 Jun 2001 13:42:42 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f55Gx4h08423 for ietf-cat-wg-out720680; Tue, 5 Jun 2001 09:59:04 -0700 (PDT) Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f55Gx2V08418 for ; Tue, 5 Jun 2001 09:59:03 -0700 (PDT) Received: from rcn.ihtfp.org (me@ORANGE-TOUR.IHTFP.ORG [204.107.200.33]) by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id MAA10049 for ; Tue, 5 Jun 2001 12:59:01 -0400 (EDT) Received: (from warlord@localhost) by rcn.ihtfp.org (8.9.3) id MAA28131; Tue, 5 Jun 2001 12:58:49 -0400 To: mrex@sap-ag.de Cc: cat-ietf@mit.edu Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt References: <200106051614.SAA03673@hw1464.wdf.sap-ag.de> From: Derek Atkins Date: 05 Jun 2001 12:58:48 -0400 In-Reply-To: Martin Rex's message of "Tue, 5 Jun 2001 18:14:23 +0200 (METDST)" Message-ID: Lines: 31 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Martin Rex writes: > The reason why using a hash is bad is that you can't reverse it. > The OID in GSS-API is meant to identify the GSS-API mechanism. > If the peer is presented only with the truncated hash, it has no > possibility to figure out what mechanism is meant if there is no > match with the mechanism known at the moment. The OIDs give you > at least a starting point to look for the mechanism (spec or vendor). Yes, this is a problem. I think there is a trade-off between the assurance of unique mech-ids (for long OIDs) and the convenience of being able to convert a SASL-mech into an unknown GSSAPI OID. I think they decided they'd rather have guaranteed uniqueness for all OIDs. > Using the shorter prefix "G-" plus the hex encoded octets of the > OID elements should give enough space for all *reasonable* GSS-API > mechanism OIDs. Who are we to decide what is a "reasonable" OID length? Also, as you noticed, there _IS_ a constraint on both length and value. Sigh. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord@MIT.EDU PGP key available -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Tue Jun 5 14:49:52 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28136 for ; Tue, 5 Jun 2001 14:49:51 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f55I11g13081 for ietf-cat-wg-out720680; Tue, 5 Jun 2001 11:01:01 -0700 (PDT) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.72.0.53]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f55I10V13076 for ; Tue, 5 Jun 2001 11:01:00 -0700 (PDT) Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [194.39.131.53]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id OAA28351; Tue, 5 Jun 2001 14:00:58 -0400 (EDT) Received: from sap-ag.de (smtpde02) by smtpde02.sap-ag.de (out) with ESMTP id UAA24762; Tue, 5 Jun 2001 20:01:39 +0200 (MESZ) From: Martin Rex Message-Id: <200106051800.UAA04258@hw1464.wdf.sap-ag.de> Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt To: warlord@mit.edu (Derek Atkins) Date: Tue, 5 Jun 2001 20:00:25 +0200 (METDST) Cc: cat-ietf@mit.edu In-Reply-To: from "Derek Atkins" at Jun 5, 1 12:58:48 pm Reply-To: mrex@sap-ag.de MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-SAP: out X-SAP: out Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Content-Transfer-Encoding: 8bit Derek Atkins wrote: > > Martin Rex writes: > > > The reason why using a hash is bad is that you can't reverse it. > > The OID in GSS-API is meant to identify the GSS-API mechanism. > > If the peer is presented only with the truncated hash, it has no > > possibility to figure out what mechanism is meant if there is no > > match with the mechanism known at the moment. The OIDs give you > > at least a starting point to look for the mechanism (spec or vendor). > > Yes, this is a problem. I think there is a trade-off between the > assurance of unique mech-ids (for long OIDs) and the convenience of > being able to convert a SASL-mech into an unknown GSSAPI OID. I think > they decided they'd rather have guaranteed uniqueness for all OIDs. > > > Using the shorter prefix "G-" plus the hex encoded octets of the > > OID elements should give enough space for all *reasonable* GSS-API > > mechanism OIDs. > > Who are we to decide what is a "reasonable" OID length? When I wrote that I didn't know about the 20 char limit, which when using hex encoding and "G-" prefix would result in at most 9-byte OIDs -- which is really too tight. My own GSS-API mechanism OID (from the IANA-managed SNMP-enterprise arc) is 10 bytes. With reasonable I meant less than 15 bytes for the elements part. This should be achievable with OIDs from the SNMP-enterprise arc. Officially assigned OID arcs from any of the ISO-member bodies result in even shorter OIDs, however the ISO-folks are trying to "lease out" OID arcs for $$$$/year. It's a MPIA when protocol specs are written with just enough space for the first version and no air for backward compatible future extensions. Maybe the IESG can catch such flaws in future specs (especially when the document is not the product of a working group). -Martin -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Tue Jun 5 15:15:35 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA28611 for ; Tue, 5 Jun 2001 15:15:34 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f55IPdW14680 for ietf-cat-wg-out720680; Tue, 5 Jun 2001 11:25:39 -0700 (PDT) Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f55IPcV14675 for ; Tue, 5 Jun 2001 11:25:38 -0700 (PDT) Received: from dns2.anl.gov (dns2.anl.gov [146.139.254.3]) by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id OAA09479; Tue, 5 Jun 2001 14:25:37 -0400 (EDT) Received: from anl.gov (atalanta.ctd.anl.gov [146.137.64.60]) by dns2.anl.gov (8.9.1a/8.9.1) with ESMTP id NAA02732; Tue, 5 Jun 2001 13:25:17 -0500 (CDT) Message-ID: <3B1D248D.B6689ED8@anl.gov> Date: Tue, 05 Jun 2001 13:27:25 -0500 From: "Douglas E. Engert" X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: mrex@sap-ag.de CC: Derek Atkins , cat-ietf@mit.edu Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt References: <200106051642.SAA03791@hw1464.wdf.sap-ag.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Content-Transfer-Encoding: 7bit Martin Rex wrote: > > Derek Atkins wrote: > > > > Without reading the rest of the sasl draft to understand the > > requirements, I can think of a couple of reasons why they might want > > to do this. > > > > One example is if there is a length limit on the size of the SASL > > mechanism name (20 characters). In that case, you may not be able to > > use the raw OID, because the 'relevant' bits may fall off the end of > > the SASL mech name if you just use HEX encoding. By using MD5 (or any > > other hash) you have a much better spreading of the bits. > > OUCH! You're right, I didn't know about that size limit for > SASL mechanisms. It's plain stupid to define such a seriously > limited namespace in the first place. The SASL spec (rfc2222) > apparently didn't receive any serious peer review before it > was put onto standards track. > > Quoting from rfc2222.txt: > The command has a required argument identifying a SASL mechanism.^M > SASL mechanisms are named by strings, from 1 to 20 characters in^M > length, consisting of upper-case letters, digits, hyphens, and/or^M > underscores. SASL mechanism names must be registered with the IANA.^M > Procedures for registering new SASL mechanisms are given in the^M > section "Registration procedures"^M > Since the RFC 2222 says SASL mechanisms MUST be registered, why do they have to be base32 names in the first place? If the intent of the draft was to provide well known unique names to both sides, this is already implicitly required by registering with IANA. The draft says: Each and every GSSAPI mechanism used within SASL is implicitly registered by this specification. I am assuming that the above realy says you do not need to register these names with IANA. Then says: SASL mechanism names starting with "GSS-" are reserved for SASL mechanisms which conform to this document. They would imply that I could still have a GSS SASL name of GSSMECH-MYOWN and register it with IANA. Is there any restriction on having two SASL names for the same GSS mechanism? > Limiting the available namespace in size and valid characters > in such a fashion is about as reasonalbe as claiming that > 640KByte of RAM is enough for applications ... > > -Martin > -++**==--++**==--++**==--++**==--++**==--++**==--++**== > This message was posted through the Stanford campus mailing list > server. If you wish to unsubscribe from this mailing list, send the > message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu -- Douglas E. Engert Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Fri Jun 8 16:19:13 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA20170 for ; Fri, 8 Jun 2001 16:19:12 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f58JH5c06793 for ietf-cat-wg-out720680; Fri, 8 Jun 2001 12:17:05 -0700 (PDT) Received: from ms.shehfung.com.tw ([210.61.197.130]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f58JH2V06786 for ; Fri, 8 Jun 2001 12:17:02 -0700 (PDT) Received: from I634tU7AI [12.64.6.171] by ms.shehfung.com.tw (SMTPD32-6.04) id A49D261025C; Sat, 09 Jun 2001 03:16:45 +0800 DATE: 08 Jun 24 12:17:17 PM FROM: ZJ0usRF4b@juno.com Message-ID: Content-Type: text/html Apparently-To: Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Untitled Document Educate yourself about everything you ever wanted to know !!!

Individually, these products often sell for as much as $100!!!

1. Satellite TV/RCA Dish Descrambler

Our unique, complete plans for building your own home satellite TV descrambler. For access to a clear reception of pay TV signals on your home satellite dish! It does not require any additional equipment! Complete PC board template & instructions! This also includes a manual for accessing the RCA/DSS satellite dish to receive free pay channels. All the latest information for doing it right.

2. X-Ray Envelope Spray

Have you ever wanted to read the contents of an envelope without opening it? Many government and other organizations use what is known as X-Ray Envelope Spray to do this! An envelope is sprayed with this secret chemical and it becomes translucent for a short period of time, which allows the contents to be read without opening. Private supply houses sell small cans of this aerosol spray for up to $50 a can! The spray is actually a commonly available item found in major grocery and discount stores. No modification of the spray is needed, as it is ready to use as X-Ray Envelope Spray and sells for about $1.99 in retail stores!

3. How to Find Anyone and Obtain Unlisted Phone Numbers

Tired of getting the wrong number? Stop looking! We can help! We'll show you how to get the unlisted phone number of anyone. No one can hide now! Simple. Skip tracers use these tricks. We also include everything you need to know about finding missing people or loved ones from the comfort of your home. Why pay money when you can do it yourself?

4. Radar Zapper

This simply technique converts existing radar detectors into a device that will jam police radar. This device sends false readings back to the police radar! Works on virtually all detectors and easy to use!

5. Untraceable E-Mail

How to send totally anonymous and untraceable E-mail. We're not talking about those generic Yahoo! Accounts -- this is the real McCoy, anonymous email. Everything explained. Absolutely untraceable.

6. Underground Guide to Utility Meters

The illustrated guide to gas, water & electric meters! We show you in detail methods many people use to stop, slow down, even reverse all three types! This underground manual is one of our most popular items! Complete illustrated techniques and easy to do. Shows how to defeat all major brands & models of gas, water & electric meters.

7. Scan-Tron Genius

Here at last!! This very controversial report describes in detail how any student can easily defeat Scan-Tron test readers to pass a test even though he does not know the answer! This simple method will fool the scan reader into thinking you answered correctly! No tools needed. Completely tested. You won't believe how simple this method is!

8. Bad Credit Cleaning Manual

Simple ways to restore your bad credit rating to A++. Don't pay a credit counselor good money to do what you can do yourself. Many methods presented here - some legal & some "not so legal". Wipe your slate clean from your own home. Get a fresh start.

9. Pass Drug Tests

Don't use of drugs! However, many innocent people are victims of drug testing. Some over the counter medicine can trigger false results & cost you your job. Proven methods to beat drug tests. We show you how to build a simple device that can fool the best! Protect yourself & your job, even if you don't use drugs.

10.Cable TV Decoders

How to get cable TV and turn your converter box into "full service" mode. This is the latest and best way to gain access. Also, how to build your own "snooper stopper" for pennies. Prevents cable companies from spying on you.

11. Free Long Distance

You can make long distance calls to other countries at no cost! The information in these reports explains everything you need to call other countries! Country codes, city codes, overseas sender codes! Call England, Germany, the UK, practically anywhere!

12. Dissolving Checks

We show you in detail the "insufficient funds" checks scam used by people to obtain goods & cash without having any money in the account. Many people do not even use false ID's in pulling this scam off. Complete detailed instructions plus rare information on the famous "dissolving" checks. These checks "dissolve" after being chemically coated & deposited in the bank leaving no trace of the writer or account number. Not for illegal purposes. See how others do it.

13. Outsmart Lie Detector Tests

Hundreds of thousands of people in this country are wrongfully fired or not hired simply because they did not pass the lie detector test even though they've done nothing wrong! Read drugless methods to help pass whether you are lying or not! A valuable tool for any job seeker. Don't be harassed by your employer ever again. Tested and proven.

14. Lock-picks & Lock-picking.

Why buy expensive lock-picks & pay for rip-off mail order locksmith courses? We'll show you how to make your own professional lock-picks. Exact detailed drawings & construction techniques! This is perhaps the easiest to understand course ever published on this hush-hush subject. You won't believe how easy it is to make these tools! We also show you how a basic lock works & how they are picked. This publication is complete with detailed drawings & illustrations.

ALL IN ONE!!! PREVIOUSLY SOLD FOR HUNDREDS!!! ORDER NOW!!!

That's 14 products, all for just $29.95 [shipping & handling included]. CA residents please add sales tax

We accept cash, personal checks, money orders and cashiers checks. You must include a

Primary and secondary E-mail address, as we will be emailing you all the reports as soon as your payment is received.

Print the following form & mail it to:

Info 4 Edu Only

1300 N. Cahuenga Blvd # 362
Los Angeles, CA 9002

Please Print Clearly

Name: _________________________________________________

Primary Email Address: ___________________________________

Secondary Email Address: _________________________________

Make your check payable to: Info 4 Edu Only

DISCLAIMER: Please note that this information is being provided for educational purposes only. The information itself is legal, while the usage of such information may be illegal. We do not advocate unauthorized use or theft of any services. If in doubt, check your local laws and act accordingly. NOTE: All of the publications are Copyright 2001 by Info 4 Edu Only . We aggressively protect our copyrights and will seek prosecution of any website, web-master, web hosting service or anyone else that is in violation of US & International Copyright Laws.

To be removed from our future mailing please email optout7846@aol.com with the word remove in the subject line -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Sat Jun 9 17:06:37 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA18844 for ; Sat, 9 Jun 2001 17:06:37 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f59KPHZ18971 for ietf-cat-wg-out720680; Sat, 9 Jun 2001 13:25:17 -0700 (PDT) Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f59KPGV18966 for ; Sat, 9 Jun 2001 13:25:16 -0700 (PDT) Received: from netscape.com (r2d2.netscape.com [205.217.237.47]) by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id QAA16782 for ; Sat, 9 Jun 2001 16:25:15 -0400 (EDT) Received: from continuity.mcom.com (continuity.mcom.com [205.217.237.112]) by netscape.com (8.10.0/8.10.0) with ESMTP id f59KO6r00467 for ; Sat, 9 Jun 2001 13:24:06 -0700 (PDT) Received: from continuity.mcom.com (localhost [127.0.0.1]) by continuity.mcom.com (980427.SGI.8.8.8/8.8.5) with SMTP id NAA92035 for ; Sat, 9 Jun 2001 13:24:06 -0700 (PDT) To: cat-ietf@mit.edu Path: not-for-mail From: John Gardiner Myers Newsgroups: mcom.list.cat-ietf,mcom.list.ietf-sasl Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt Date: Sat, 09 Jun 2001 13:24:02 -0700 Organization: Netscape Communications Corporation Lines: 36 Message-ID: <3B2285E2.189ECBAB@netscape.com> References: <200106051642.SAA03791@hw1464.wdf.sap-ag.de> <3B1D248D.B6689ED8@anl.gov> NNTP-Posting-Host: 205.217.228.206 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Content-Transfer-Encoding: 7bit "Douglas E. Engert" wrote: > I am assuming that the above realy says you do not need to register > these names with IANA. Correct. > Then says: > SASL mechanism names starting with "GSS-" are reserved for SASL > mechanisms which conform to this document. The intent is to carve out a portion of the SASL mechanism namespace so that GSSAPI SASL mechanism name registration is done through the OID registration process instead of the IANA registration process. Once a GSSAPI mechanism has been registered through GSSAPI's process (assigning an OID), no additional registration work need be necessary to get a legal SASL mechanism name. An implementation, knowing nothing about a GSSAPI mechanism other than its OID, can determine its SASL mechanism name. > They would imply that I could still have a GSS SASL name of GSSMECH-MYOWN > and register it with IANA. You can register any SASL mechanism name you like, as long as the name is not already taken and as long as the name is not in a reserved portion of the namespace (such as the portion of the namespace starting with "GSS-"). Such a mechanism will not conform to the SASL-GSSAPI specification and will not interoperate with implementations conforming to the SASL-GSSAPI specification. > Is there any restriction on having two SASL names for the same GSS mechanism? No, just as there is no restricition on having two OIDs for the same GSS mechanism. Having multiple names will, however, lead to noninteroprability. -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Mon Jun 11 13:54:57 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15940 for ; Mon, 11 Jun 2001 13:54:56 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f5BHA1925723 for ietf-cat-wg-out720680; Mon, 11 Jun 2001 10:10:01 -0700 (PDT) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.72.0.53]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f5BH9xV25718 for ; Mon, 11 Jun 2001 10:10:00 -0700 (PDT) Received: from mail5.microsoft.com (mail5.microsoft.com [131.107.3.121]) by fort-point-station.mit.edu (8.9.2/8.9.2) with SMTP id NAA01574 for ; Mon, 11 Jun 2001 13:09:58 -0400 (EDT) Received: from 157.54.9.100 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 11 Jun 2001 09:21:51 -0700 (Pacific Daylight Time) Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-imc-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2883); Mon, 11 Jun 2001 09:21:34 -0700 Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2883); Mon, 11 Jun 2001 09:21:24 -0700 Received: from win-msg-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.52]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 11 Jun 2001 09:20:10 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt Date: Mon, 11 Jun 2001 09:20:10 -0700 Message-ID: <4AEE3169443CDD4796CA8A00B02191CD4EE6E2@win-msg-01.wingroup.windeploy.ntdev.microsoft.com> Thread-Topic: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt Thread-Index: AcDxJVG2egkBPbYLR9GI2PVY/2zZogBbFlaw From: "John Brezak" To: "John Gardiner Myers" , X-OriginalArrivalTime: 11 Jun 2001 16:20:10.0508 (UTC) FILETIME=[62EADCC0:01C0F292] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by lists.Stanford.EDU id f5BHA0V25719 Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Content-Transfer-Encoding: 8bit What about GSS mechanisms with OID that were typo'ed in the implementation? The mechtype code knows how to deal with it, but the OID based registration mechanism will not deal with this very well. I'd prefer to use the IANA registered names as Doug suggests instead of an algorithmic OID based encoding scheme. If it is to be an OID, it should be a straight forward encoding - either in printable dotted notation, or asn.1 encoded. You could get around the byte limit for names by adding an extension field after the authorization ID carrying the full (encoded) OID. -----Original Message----- From: John Gardiner Myers [mailto:jgmyers@netscape.com] Sent: Saturday, June 09, 2001 1:24 PM To: cat-ietf@mit.edu Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt "Douglas E. Engert" wrote: > I am assuming that the above realy says you do not need to register > these names with IANA. Correct. > Then says: > SASL mechanism names starting with "GSS-" are reserved for SASL > mechanisms which conform to this document. The intent is to carve out a portion of the SASL mechanism namespace so that GSSAPI SASL mechanism name registration is done through the OID registration process instead of the IANA registration process. Once a GSSAPI mechanism has been registered through GSSAPI's process (assigning an OID), no additional registration work need be necessary to get a legal SASL mechanism name. An implementation, knowing nothing about a GSSAPI mechanism other than its OID, can determine its SASL mechanism name. > They would imply that I could still have a GSS SASL name of > GSSMECH-MYOWN and register it with IANA. You can register any SASL mechanism name you like, as long as the name is not already taken and as long as the name is not in a reserved portion of the namespace (such as the portion of the namespace starting with "GSS-"). Such a mechanism will not conform to the SASL-GSSAPI specification and will not interoperate with implementations conforming to the SASL-GSSAPI specification. > Is there any restriction on having two SASL names for the same GSS > mechanism? No, just as there is no restricition on having two OIDs for the same GSS mechanism. Having multiple names will, however, lead to noninteroprability. -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Mon Jun 11 20:44:59 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21361 for ; Mon, 11 Jun 2001 20:44:59 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f5BNioa25282 for ietf-cat-wg-out720680; Mon, 11 Jun 2001 16:44:50 -0700 (PDT) Received: from alisier.wanadoo.fr (smtp-rt-9.wanadoo.fr [193.252.19.55]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f5BNinV25277 for ; Mon, 11 Jun 2001 16:44:49 -0700 (PDT) Received: from andira.wanadoo.fr (193.252.19.152) by alisier.wanadoo.fr; 12 Jun 2001 01:44:42 +0200 Received: from [193.249.226.48] (193.249.226.48) by andira.wanadoo.fr; 12 Jun 2001 01:44:40 +0200 Message-ID: <3b2557ea3b2afc44@andira.wanadoo.fr> (added by andira.wanadoo.fr) From: "business_francophone@hotmail.com" To: ietf-cat-wg@lists.Stanford.EDU Subject: Offre Spéciale X-Mailer: Mail Bomber Reply-To: business_francophone@hotmail.com Date: Tue, 12 Jun 2001 01:38:19 +0100 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Augmentez de 300 % la frequentation de votre site internet en moins de 90 jours........... http://www.miws-usa.com/miws/Page_23.htm Ceci comprend : - un audit de votre site - un referencement tout les quinzes jours pendant 90 jours - une analyse de vos meta-tags ( optimisé a 100 % au lieu de 35 % habituel) - positionnement dans les principaux moteurs de recherche - un echange de banniere ciblés - etc........... http://www.miws-usa.com/miws/Page_23.htm L'equipe de "business Francophone" vous recevez cette email car vous etes parrainé par 1452125@computerserve.com si vous ne souhaitez pas recevoir nos 4 mailngs ( pas plus pas moins) renvoyé ce mail -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Tue Jun 12 12:46:44 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19121 for ; Tue, 12 Jun 2001 12:46:43 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f5CG6Bx23041 for ietf-cat-wg-out720680; Tue, 12 Jun 2001 09:06:11 -0700 (PDT) Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f5CG6AV23035 for ; Tue, 12 Jun 2001 09:06:10 -0700 (PDT) Received: from dns2.anl.gov (dns2.anl.gov [146.139.254.3]) by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id MAA04101 for ; Tue, 12 Jun 2001 12:06:09 -0400 (EDT) Received: from anl.gov (atalanta.ctd.anl.gov [146.137.64.60]) by dns2.anl.gov (8.9.1a/8.9.1) with ESMTP id LAA21849; Tue, 12 Jun 2001 11:06:08 -0500 (CDT) Message-ID: <3B263E73.570CA4F9@anl.gov> Date: Tue, 12 Jun 2001 11:08:19 -0500 From: "Douglas E. Engert" X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cat-ietf@mit.edu CC: Mei-Hui Su , carl@isi.edu, gawor@mcs.anl.gov, tuecke@mcs.anl.gov, welch@mcs.anl.gov Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt References: <200106112149.OAA10891@hammie.isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Content-Transfer-Encoding: 7bit Cat-ietf'ers, We have a GSSAPI implementation called GSI, which we are adding under SASL. We are at the point where we are looking at the choice of a SASL mechanisum name. So our discussion fits right in with the discusion on the cat-ietf list. I would call your attention to the last few paragraph for comments. Mei-Hui Su wrote: > > In openldap, it gets a list of modules to be loaded from the conf file and > then load them all in during startup, > > In Sasl, When they got started, it checks with all the possible plugin > shared libraries in the specified plugin-dir and tries to dlopen them one > by one and there is an internal table associate with each plugin > library. So it is extensible, by the fact that there is a library in the directory? > That table contains what to call during handshaking etc. and then > the server/client keep tracks of 'valid' mechanism name if the plugin was > successfully dlopened and saves a link to it. So it sounds like a plugin can return multiple mechanisum names? > And when a request comes for a > 'particular' mechanism, server/client would base on the name and follow the > link to the right plugin code. So the changes I did was to force another > mechanism name into gssapi's plugin's shared libraries. It looks like they > thought about multiple mechanism name associates with a mechanism type but > there is no easy way to add it but to hacking new one in to the source. Did you only have to change the plugin? > But > like you said, the problem still exists when there really should be multiple > plugin libraries for different favors of GSSAPI because the 'libgssapiv2.la' > that brings in dependency would differ for krb5 and GSI ones. Yes and no. Since GSS API is designed to allow multiple mechanisms to be accessed via the single API, there could be a single gssapi plugin, which loaded all the available gssapi libs, then returned their SASL names. The mechglue code from Sun, and distributed with the MIT Kerberos code for example could be used in the SASL gssapi plugin. The problem is that SASL is trying to negotiate a mechanism name, but GSSAPI uses mechanism OIDs. And one plugin or GSS lib can have multiple mechanisms. So the use of the GSI-base32name may not be as bad as it looks, if the plugin can generate the name from the mechanism OIDs on the fly and return the list to the SASL library. In this way the client and server will both have a a list of names which maps to all the possible GSSAPI mechanism OIDs they support. So the reverse mapping from SASL mechanism name to OID is not needed, and the SASL mechanism name does not need to be readable. If all this holds true for other implementations of SASL, then the draft is not as objectionable as I had first thought. > > mei -- Douglas E. Engert Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Wed Jun 13 04:35:26 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17513 for ; Wed, 13 Jun 2001 04:35:26 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f5D7xxf19284 for ietf-cat-wg-out720680; Wed, 13 Jun 2001 00:59:59 -0700 (PDT) Received: from e250.jctp.gov.cn ([202.102.182.34]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f5D7xgV19279 for ; Wed, 13 Jun 2001 00:59:43 -0700 (PDT) Received: from v1CCcwQfL ([64.86.192.70]) by e250.jctp.gov.cn (8.9.1/8.9.1) with SMTP id PAA28186; Wed, 13 Jun 2001 15:49:57 +0800 (CST) From: gBjnAQw6D@mindspring.com DATE: 13 Jun 01 12:53:24 AM Message-ID: Content-Type: text/html SUBJECT: Hydraulic Repairs-30% Discount! Apparently-To: Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk WE CAN SAVE YOUR COMPANY ALOT OF MONEY On Your Hydraulic Remanufacturing Think about this . . . if you could SAVE A MINIMUM of 30% on all future hydraulic repairs compared to what your current source is charging you, would you check it out? You bet you would because you know it would improve YOUR BOTTOM LINE! HOW ARE WE ABLE TO DO THIS? By dealing with us electronically (direct), your company will be avoiding all of the normal overhead charges associated with a sales staff, such as: SALES SALARIES SALES COMMISSIONS CAR ALLOWANCES EXPENSE ACCOUNTS TRAVEL & ENTERTAINMENT ETC. We invite you to try our services and find out what hundreds of other companies already know . . . Servo Kinetics does excellent work! · WE ARE CERTIFIED BY THE U.S. NAVY UNDER MIL SPEC-45208A · WE ARE CURRENTLY REMANUFACTURING THE SPACE SHUTTLE SIMULATOR FOR NASA (UNITED SPACE ALLIANCE). · WE CAN PROVIDE YOUR COMPANY WITH THE SAME QUALITY WE GIVE TO OUR GOVERNMENT CONTRACTS SEND US YOUR HYDRAULIC: * Pumps * Motors * Cylinders * Accumulators * Directional Control Valves * Control Panels * Rotary Actuators * Blow Molding Actuators * Test Lab Precision & Fatigue Rated Actuators * Plastic Injection Units or Cylinders (any size) * Die Cast Shot-End Units or Cylinders (any size) and many, many other types of general hydraulic components that are to numerous to mention. SEND US YOUR SERVO OR PROPORTIONAL VALVES: Servo Kinetics has a truly State-of-the-Art Servo and Proportional Valve Laboratory that can repair virtually any servo or proportional valve, regardless of the manufacturer, as shown below. MAJOR MANUFACTURERS WE REPAIR REGULARLY: MOOG * ATCHLEY * REXROTH * PARKER * VICKERS * PEGASUS BOSCH * TEXTRON * OIL GEAR * DOWTY * LOGANSPORT * ABEX HUNKER * DYVAL * OLSEN * CINCINNATI * TOWLER * RVA SUNDSTRAND * DENISON * KAWASAKI * HONEYWELL * SLI * BULLARD * ULTRA * BOXTEL * GLEASON * YUKEN * FUJITSU Check out our website at http://servokinetics.com where you can fill-out and submit our "Customer Contact Form"; once received we will contact you promptly. In addition, you are welcome to call us at 800.824.0808 or e-mail us at servo@servokinetics.com. We thank you and look forward to doing some trial work for your company. Servo KInetics, INC 3616 Plaza Drive Ann Arbor, MI 48108. @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ This mailing is done by an independent marketing co. We apologize if this message has reached you in error. Save the Planet, Save the Trees! Advertise via Email. No wasted paper! Delete with one simple keystroke! Less refuse in our Dumps! This is the new way of the new millennium To be removed please email optout7846@aol.com with the word "remove" in the subject line. @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Thu Jun 14 10:07:28 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29897 for ; Thu, 14 Jun 2001 10:07:27 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f5ED8nW11728 for ietf-cat-wg-out720680; Thu, 14 Jun 2001 06:08:49 -0700 (PDT) Received: from tango.SoftHome.net (tango.SoftHome.net [204.144.231.49]) by lists.Stanford.EDU (8.11.3/8.11.3) with SMTP id f5ED8mV11723 for ; Thu, 14 Jun 2001 06:08:48 -0700 (PDT) Message-Id: <200106141308.f5ED8mV11723@lists.Stanford.EDU> Received: (qmail 29753 invoked by uid 417); 14 Jun 2001 13:12:52 -0000 Received: from unknown (HELO plain) (193.188.120.58) by i-softhome-tango with SMTP; 14 Jun 2001 13:12:52 -0000 From: noor555@softhome.net To: ietf-cat-wg@lists.Stanford.EDU Subject: Making over Half Million Dollars every 4 to 5 Months from your Home Date: Thu, 14 Jun 2001 16:09:38 Mime-Version: 1.0 Content-Type: text/plain; charset="DEFAULT_CHARSET" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk AS SEEN ON NATIONAL TV: Making over Half Million Dollars every 4 to 5 Months from your Home for an investment of only $25 U.S. Dollars expense one time THANK'S TO THE COMPUTER AGE AND THE INTERNET! ================================================== BE A MILLIONAIRE LIKE OTHERS WITHIN A YEAR!!! Before you say ''Bull'', please read the following. This is the letter you have been hearing about on the news lately. Due to the popularity of this letter on the Internet, a national weekly news program recently devoted an entire show to the investigation of this program described below, to see if it really can make people money. The show also investigated whether or not the program was legal. Their findings proved once and for all that there are ''absolutely NO Laws prohibiting the participation in the program and if people can follow the simple instructions, they are bound to make some mega bucks with only $25 out of pocket cost''. DUE TO THE RECENT INCREASE OF POPULARITY & RESPECT THIS PROGRAM HAS ATTAINED, IT IS CURRENTLY WORKING BETTER THAN EVER. This is what one had to say: ''Thanks to this profitable opportunity. I was approached many times before but each time I passed on it. I am so glad I finally joined just to see what one could expect in return for the minimal effort and money required. To my astonishment, I received total $610,470.00 in 21 weeks, with money still coming in." Pam Hedland, Fort Lee, New Jersey. =================================================== Here is another testimonial: "This program has been around for a long time but I never believed in it. But one day when I received this again in the mail I decided to gamble my $25 on it. I followed the simple instructions and 3 weeks later the money started to come in. First month I only made $240.00 but the next 2 months after that I made a total of $290,000.00. So far, in the past 8 months by re-entering the program, I have made over $710,000.00 and I am playing it again. The key to success in this program is to follow the simple steps and NOT change anything.'' More testimonials later but first, ===== PRINT THIS NOW FOR YOUR FUTURE REFERENCE ====== $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ If you would like to make at least $500,000 every 4 to 5 months easily And comfortably, please read the following...THEN READ IT AGAIN and AGAIN!!! $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ FOLLOW THE SIMPLE INSTRUCTION BELOW AND YOUR FINANCIAL DREAMS WILL COME TRUE, GUARANTEED! INSTRUCTIONS: =====Order all 5 reports shown on the list below ===== For each report, send $5 CASH, THE NAME & NUMBER OF THE REPORT YOU ARE ORDERING and YOUR E-MAIL ADDRESS to the person whose name appears ON THAT LIST next to the report. MAKE SURE YOUR RETURN ADDRESS IS ON YOUR ENVELOPE TOP LEFT CORNER in case of any mail problems. === When you place your order, make sure you order each of the 5 reports. You will need all 5 reports so that you can save them on your computer and resell them. YOUR TOTAL COST $5 X 5=$25.00. Within a few days you will receive, vie e-mail, each of the 5 reports from these 5 different individuals. Save them on your computer so they will be accessible for you to send to the 1,000's of people who will order them from you. Also make a floppy of these reports and keep it on your desk in case something happen to your computer. IMPORTANT - DO NOT alter the names of the people who are listed next to each report, or their sequence on the list, in any way other than what is instructed below in step '' 1 through 6 '' or you will lose out on majority of your profits. Once you understand the way this works, you will also see how it does not work if you change it. Remember, this method has been tested, and if you alter, it will NOT work !!! People have tried to put their friends/relatives names on all five thinking they could get all the money. But it does not work this way. Believe us, we all have tried to be greedy and then nothing happened. So Do Not try to change anything other than what is instructed. Because if you do, it will not work for you. Remember, honesty reaps the reward!!! 1.... After you have ordered all 5 reports, take this advertisement and REMOVE the name & address of the person in REPORT # 5. This person has made it through the cycle and is no doubt counting their fortune. 2.... Move the name & address in REPORT # 4 down TO REPORT # 5. 3.... Move the name & address in REPORT # 3 down TO REPORT # 4. 4.... Move the name & address in REPORT # 2 down TO REPORT # 3. 5.... Move the name & address in REPORT # 1 down TO REPORT # 2 6.... Insert YOUR name & address in the REPORT # 1 Position. PLEASE MAKE SURE you copy every name & address ACCURATELY! ========================================================== **** Take this entire letter, with the modified list of names, and save it on your computer. DO NOT MAKE ANY OTHER CHANGES. Save this on a disk as well just in case you lose any data. To assist you with marketing your business on the internet, the 5 reports you purchase will provide you with invaluable marketing information which includes how to send bulk e-mails legally, where to find thousands of free classified ads and much more. There are 2 Primary methods to get this venture going: METHOD # 1: BY SENDING BULK E-MAIL LEGALLY ========================================================== Let's say that you decide to start small, just to see how it goes, and we will assume You and those involved send out only 5,000 e-mails each. Let's also assume that the mailing receive only a 0.2% response (the response could be much better but lets just say it is only 0.2%. Also many people will send out hundreds of thousands e-mails instead of only 5,000 each). Continuing with this example, you send out only 5,000 e-mails. With a 0.2% response, that is only 10 orders for report # 1. Those 10 people responded by sending out 5,000 e-mail each for a total of 50,000. Out of those 50,000 e-mails only 0.2% responded with orders. That's=100 people responded and ordered Report # 2. Those 100 people mail out 5,000 e-mails each for a total of 500,000 e-mails. The 0.2% response to that is 1000 orders for Report # 3. Those 1000 people send out 5,000 e-mails each for a total of 5 million e-mails sent out. The 0.2% response to that is 10,000 orders for Report # 4. Those 10,000 people send out 5,000 e-mails each for a total of 50,000,000 (50 million) e-mails. The 0.2% response to that is 100,000 orders for Report # 5 THAT'S 100,000 ORDERS TIMES $5 EACH=$500,000.00 (half million). Your total income in this example is: 1..... $50 + 2..... $500 + 3.....$5,000 + 4.... $50,000 + 5..... $500,000 ....... Grand Total=$555,550.00 NUMBERS DO NOT LIE. GET A PENCIL & PAPER AND FIGUREOUT THE WORST POSSIBLE RESPONSES AND NO MATTER HOW YOU CALCULATE IT, YOU WILL STILL MAKE A LOT OF MONEY ! ========================================================= REMEMBER FRIEND, THIS IS ASSUMING ONLY 10 PEOPLE ORDERING OUT OF 5,000 YOU MAILED TO. Dare to think for a moment what would happen if everyone or half or even one 4th of those people mailed 100,000e-mails each or more? There are over 150 million people on the Internet worldwide and counting. Believe me, many people will do just that, and more! METHOD # 2 : BY PLACING FREE ADS ON THE INTERNET ======================================================= Advertising on the net is very very inexpensive and there are hundreds of FREE places to advertise. Placing a lot of free ads on the Internet will easily get a larger response. We strongly suggest you start with Method # 1 and add METHOD # 2 as you go along. For every $5 you receive, all you must do is e-mail them the Report they ordered. That's it. Always provide same day service on all orders. This will guarantee that the e-mail they send out, with your name and address on it, will be prompt because they can not advertise until they receive the report. =========== AVAILABLE REPORTS ==================== ORDER EACH REPORT BY ITS NUMBER & NAME ONLY. Notes: Always send $5 cash (U.S. CURRENCY) for each Report. Checks NOT accepted. Make sure the cash is concealed by wrapping it in at least 2 sheets of paper. On one of those sheets of paper, Write the NUMBER & the NAME of the Report you are ordering, YOUR E-MAIL ADDRESS and your name and postal address. PLACE YOUR ORDER FOR THESE REPORTS NOW : ==================================================== REPORT# 1: The Insider's Guide to Advertising for Free on the Net Order Report #1 from: Nada Mahmood P.O. Box 5385 Manama, Bahrain Arabian Gulf _______________________________________________ REPORT # 2: The Insider's Guide to Sending Bulk e-mail on the Net Order Report # 2 from: M. Dore 6340, 42nd Avenue, apt. 5 Montreal (Quebec) Canada H1T 2S8 _____________________________________________________________ REPORT # 3: Secret to Multilevel Marketing on the Net Order Report # 3 from : Howard Bishop Jr. 266 Hunter Drive Lawrenceville,VA.23868 ____________________________________________________________ REPORT # 4: How to Become a Millionaire Utilizing MLM & the Net Order Report # 4 from: P. Condinho 2549 Mason Heights Mississauga, Ontario L5B 2S3, Canada ____________________________________________________________ REPORT #5: How to Send Out 0ne Million e-mails for Free Order Report # 5 from: G. Hostetler 205 Freda Ln. Lowell, Ma. 01854 USA ____________________________________________________________ $$$$$$$$$ YOUR SUCCESS GUIDELINES $$$$$$$$$$$ Follow these guidelines to guarantee your success: === If you do not receive at least 10 orders for Report #1 within 2 weeks, continue sending e-mails until you do. === After you have received 10 orders, 2 to 3 weeks after that you should receive 100 orders or more for REPORT # 2. If you did not, continue advertising or sending e-mails until you do. === Once you have received 100 or more orders for Report # 2, YOU CAN RELAX, because the system is already working for you, and the cash will continue to roll in ! THIS IS IMPORTANT TO REMEMBER: Every time your name is moved down on the list, you are placed in front of a Different report. You can KEEP TRACK of your PROGRESS by watching which report people are ordering from you. IF YOU WANT TO GENERATE MORE INCOME SEND ANOTHER BATCH OF E-MAILS AND START THE WHOLE PROCESS AGAIN. There is NO LIMIT to the income you can generate from this business !!! ====================================================== FOLLOWING IS A NOTE FROM THE ORIGINATOR OF THIS PROGRAM: You have just received information that can give you financial freedom for the rest of your life, with NO RISK and JUST A LITTLE BIT OF EFFORT. You can make more money in the next few weeks and months than you have ever imagined. Follow the program EXACTLY AS INSTRUCTED. Do Not change it in any way. It works exceedingly well as it is now. Remember to e-mail a copy of this exciting report after you have put your name and address in Report #1 and moved others to #2 ...........#5 as instructed above. One of the people you send this to may send out 100,000 or more e-mails and your name will be on every one of them. Remember though, the more you send out the more potential customers you will reach. So my friend, I have given you the ideas, information, materials and opportunity to become financially independent. IT IS UP TO YOU NOW ! ============ MORE TESTIMONIALS ================ "My name is Mitchell. My wife, Jody and I live in Chicago. I am an accountant with a major U.S. Corporation and I make pretty good money. When I received this program I grumbled to Jody about receiving ''junk mail''. I made fun of the whole thing,spouting my knowledge of the population and percentages involved. I ''knew'' it wouldn't work. Jody totally ignored my supposed intelligence and few days later she jumped in with both feet. I made merciless fun of her, and was ready to lay the old ''I told you so'' on her when the thing didn't work. Well, the laugh was on me! Within 3 weeks she had received 50 responses. Within the next 45 days she had Received total $ 147,200.00 ........... all cash! I was shocked. I have joined Jody in her ''hobby''. Mitchell Wolf M.D., Chicago, Illinois ====================================================== ''Not being the gambling type, it took me several weeks to make up my mind to participate in this plan. But conservative that I am, I decided that the initial investment was so little that there was just no way that I wouldn't get enough orders to at least get my money back''. '' I was surprised when I found my medium size post office box crammed with orders. I made $319,210.00in the first 12 weeks. The nice thing about this deal is that it does not matter where people live. There simply isn't a better investment with a faster return and so big." Dan Sondstrom, Alberta, Canada ======================================================= ''I had received this program before. I deleted it, but later I wondered if I should have given it a try. Of course, I had no idea who to contact to get another copy, so I had to wait until I was e-mailed again by someone else.........11 months passed then it luckily came again...... I did not delete this one! I made more than $490,000 on my first try and all the money came within 22 weeks." Susan De Suza, New York, N.Y. ======================================================= ''It really is a great opportunity to make relatively easy money with little cost to you. I followed the simple instructions carefully and within 10 days the money started to come in. My first month I made $20,560.00 and by the end of third month my total cash count was $362,840.00. Life is beautiful, Thanx to internet.". Fred Dellaca, Westport, New Zealand ======================================================= ORDER YOUR REPORTS TODAY AND GET STARTED ON 'YOUR' ROAD TO FINANCIAL FREEDOM ! ======================================================= If you have any questions of the legality of this program, contact the Office of Associate Director for Marketing Practices, Federal Trade Commission, Bureau of Consumer Protection, Washington, D.C. -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Mon Jun 18 17:57:57 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22109 for ; Mon, 18 Jun 2001 17:57:56 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f5IKqI807096 for ietf-cat-wg-out720680; Mon, 18 Jun 2001 13:52:18 -0700 (PDT) Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f5IKqHV07091 for ; Mon, 18 Jun 2001 13:52:17 -0700 (PDT) Received: from cap1.CapAccess.org (root@cap1.CapAccess.org [151.200.199.10]) by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with SMTP id QAA27558; Mon, 18 Jun 2001 16:52:14 -0400 (EDT) From: jwayne45@care2.com Received: from care2.com (da001d1377.atl-ga.osd.concentric.net [64.3.197.98]) by cap1.CapAccess.org (8.6.12/8.6.10) with SMTP id VAA25889; Sun, 17 Jun 1973 21:21:42 -0400 Subject: toner Date: Sun, 17 Jun 2001 21:14:46 Message-Id: <891.543708.823082@care2.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk PLEASE FORWARD TO THE PERSON RESPONSIBLE FOR PURCHASING YOUR LASER PRINTER SUPPLIES **** VORTEX SUPPLIES **** LASER PRINTER TONER CARTRIDGES, COPIER AND FAX CARTRIDGES SAVE UP TO 30% FROM RETAIL ORDER BY PHONE:1-888-288-9043 ORDER BY FAX: 1-888-977-1577 CUSTOMER SERVICE: 1-888-248-2015 E-MAIL REMOVAL LINE: 1-888-248-4930 UNIVERSITY AND/OR SCHOOL PURCHASE ORDERS WELCOME. (NO CREDIT APPROVAL REQUIRED) ALL OTHER PURCHASE ORDER REQUESTS REQUIRE CREDIT APPROVAL. PAY BY CHECK (C.O.D), CREDIT CARD OR PURCHASE ORDER (NET 30 DAYS). IF YOUR ORDER IS BY CREDIT CARD PLEASE LEAVE YOUR CREDIT CARD # PLUS EXPIRATION DATE. IF YOUR ORDER IS BY PURCHASE ORDER LEAVE YOUR SHIPPING/BILLING ADDRESSES AND YOUR P.O. NUMBER FOR THOSE OF YOU WHO REQUIRE MORE INFORMATION ABOUT OUR COMPANY INCUDING FEDERAL TAX ID NUMBER, CLOSEST SHIPPING OR CORPORATE ADDRESS IN THE CONTINENTAL U.S. OR FOR CATALOG REQUESTS PLEASE CALL OUR CUSTOMER SERVICE LINE 1-888-248-2015 OUR NEW , LASER PRINTER TONER CARTRIDGE, PRICES ARE AS FOLLOWS: (PLEASE ORDER BY PAGE NUMBER AND/OR ITEM NUMBER) HEWLETT PACKARD: (ON PAGE 2) ITEM #1 LASERJET SERIES 4L,4P (74A)------------------------$44 ITEM #2 LASERJET SERIES 1100 (92A)-------------------------$44 ITEM #3 LASERJET SERIES 2 (95A)----------------------------$39 ITEM #4 LASERJET SERIES 2P (75A)---------------------------$54 ITEM #5 LASERJET SERIES 5P,6P,5MP, 6MP (3903A)---------- -$44 ITEM #6 LASERJET SERIES 5SI, 8000 (09A)--------------------$95 ITEM #7 LASERJET SERIES 2100 (96A)-------------------------$74 ITEM #8 LASERJET SERIES 8100 (82X)------------------------$145 ITEM #9 LASERJET SERIES 5L/6L (3906A)----------------------$35 ITEM #10 LASERJET SERIES 4V---------------------------------$95 ITEM #11 LASERJET SERIES 4000 (27X)--------------------------$72 ITEM #12 LASERJET SERIES 3SI/4SI (91A)-----------------------$54 ITEM #13 LASERJET SERIES 4, 4M, 5,5M-------------------------$49 ITEM #13A LASERJET SERIES 5000 (29X)-------------------------$95 HEWLETT PACKARD FAX (ON PAGE 2) ITEM #14 LASERFAX 500, 700 (FX1)----------$49 ITEM #15 LASERFAX 5000,7000 (FX2)--------$54 ITEM #16 LASERFAX (FX3)------------------$59 ITEM #17 LASERFAX (FX4)------------------$54 LEXMARK/IBM (ON PAGE 3) OPTRA 4019, 4029 HIGH YIELD---------------$89 OPTRA R, 4039, 4049 HIGH YIELD-----------$105 OPTRA E-----------------------------------$59 OPTRA N----------------------------------$115 OPTRA S----------------------------------$165 EPSON (ON PAGE 4) ACTION LASER 7000,7500,8000,9000----------$105 ACTION LASER 1000,1500--------------------$105 CANON PRINTERS (ON PAGE 5) PLEASE CALL FOR MODELS AND UPDATED PRICES FOR CANON PRINTER CARTRIDGES PANASONIC (0N PAGE 7) NEC SERIES 2 MODELS 90 AND 95----------$105 APPLE (0N PAGE 8) LASER WRITER PRO 600 or 16/600------------------$49 LASER WRITER SELECT 300,320,360-----------------$74 LASER WRITER 300 AND 320------------------------$54 LASER WRITER NT, 2NT----------------------------$54 LASER WRITER 12/640-----------------------------$79 CANON FAX (ON PAGE 9) LASERCLASS 4000 (FX3)---------------------------$59 LASERCLASS 5000,6000,7000 (FX2)-----------------$54 LASERFAX 5000,7000 (FX2)------------------------$54 LASERFAX 8500,9000 (FX4)------------------------$54 CANON COPIERS (PAGE 10) PC 3, 6RE, 7 AND 11 (A30)---------------------$69 PC 300,320,700,720 and 760 (E-40)-------------$89 IF YOUR CARTRIDGE IS NOT LISTED CALL CUSTOMER SERVICE AT 1-888-248-2015 90 DAY UNLIMITED WARRANTY INCLUDED ON ALL PRODUCTS. ALL TRADEMARKS AND BRAND NAMES LISTED ABOVE ARE PROPERTY OF THE RESPECTIVE HOLDERS AND USED FOR DESCRIPTIVE PURPOSES ONLY. -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Mon Jun 18 18:39:03 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22800 for ; Mon, 18 Jun 2001 18:39:02 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f5ILYma10904 for ietf-cat-wg-out720680; Mon, 18 Jun 2001 14:34:48 -0700 (PDT) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.72.0.53]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f5ILYjV10899 for ; Mon, 18 Jun 2001 14:34:45 -0700 (PDT) Received: from netscape.com (c3po.netscape.com [205.217.237.46]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id RAA24677 for ; Mon, 18 Jun 2001 17:34:44 -0400 (EDT) Received: from u-gotmail.red.iplanet.com (u-gotmail.red.iplanet.com [192.18.73.45]) by netscape.com (8.10.0/8.10.0) with ESMTP id f5ILYAY09334 for ; Mon, 18 Jun 2001 14:34:11 -0700 (PDT) Received: from netscape.com (jgmyers-nt.red.iplanet.com [192.18.126.70]) by we-gotmail.red.iplanet.com (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTPS id <0GF500LEQAMAAW@we-gotmail.red.iplanet.com> for cat-ietf@mit.edu; Mon, 18 Jun 2001 14:35:00 -0700 (PDT) Date: Mon, 18 Jun 2001 14:34:07 -0700 From: John Gardiner Myers Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt To: cat-ietf@mit.edu Message-id: <3B2E73CF.B99049B4@netscape.com> MIME-version: 1.0 X-Mailer: Mozilla 4.77 [en] (WinNT; U) Content-type: multipart/signed; boundary=------------msD7274DC319E637E85F045771; micalg=sha1; protocol="application/x-pkcs7-signature" X-Accept-Language: en References: <4AEE3169443CDD4796CA8A00B02191CD4EE6E2@win-msg-01.wingroup.windeploy.ntdev.microsoft.com> Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk This is a cryptographically signed message in MIME format. --------------msD7274DC319E637E85F045771 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit John Brezak wrote: > What about GSS mechanisms with OID that were typo'ed in the > implementation? The mechtype code knows how to deal with it, but the OID > based registration mechanism will not deal with this very well. I'm sorry, I don't understand what you're describing. Could you give an example? > I'd prefer to use the IANA registered names as Doug suggests instead of > an algorithmic OID based encoding scheme. Which IANA registered names? As far as I was aware, there are is no IANA registry of GSS mechanisms and the only names that a caller to the GSS API can get for available mechanisms are the OIDs. > If it is to be an OID, it should be a straight forward encoding - either > in printable dotted notation, or asn.1 encoded. You could get around the > byte limit for names by adding an extension field after the > authorization ID carrying the full (encoded) OID. The list of mechanisms available on the server has to be communicated before the client calls GSS_Init_sec_context. The part of the negotiation where the authorization ID is sent is far too late. --------------msD7274DC319E637E85F045771 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature Content-Transfer-Encoding: base64 MIIJFwYJKoZIhvcNAQcCoIIJCDCCCQQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BuowggMMMIICdaADAgECAgI6gTANBgkqhkiG9w0BAQQFADCBkzELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRswGQYDVQQKExJBbWVyaWNhIE9u bGluZSBJbmMxGTAXBgNVBAsTEEFPTCBUZWNobm9sb2dpZXMxJzAlBgNVBAMTHkludHJhbmV0 IENlcnRpZmljYXRlIEF1dGhvcml0eTAeFw0wMTA2MDQyMDExMTNaFw0wMTEyMDEyMDExMTNa MIGCMRMwEQYKCZImiZPyLGQBGRYDY29tMRgwFgYKCZImiZPyLGQBGRYIbmV0c2NhcGUxIzAh BgkqhkiG9w0BCQEWFGpnbXllcnNAbmV0c2NhcGUuY29tMRMwEQYDVQQDEwpKb2huIE15ZXJz MRcwFQYKCZImiZPyLGQBARMHamdteWVyczCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA 0UkG0d+rgk8JBbwwFyX3GgQtTdP8ytSaxbUlZkCOqfqboqMDGfwAr/ViYFXvfnQBHPOgZSCW /nBq9G4hhq+eSEigPSL/Jw7fGul/UGcbb++8tQtwSEYE91I0TxkiA9EyWtZkud+GTHtXHHAG 4U3q9YQVeMw7eokjFD5ibjw7oP8CAwEAAaN+MHwwEQYJYIZIAYb4QgEBBAQDAgWgMA4GA1Ud DwEB/wQEAwIF4DA2BggrBgEFBQcBAQQqMCgwJgYIKwYBBQUHMAGGGmh0dHA6Ly9uc29jc3Au bmV0c2NhcGUuY29tMB8GA1UdIwQYMBaAFCnbsi2Dfn+LI7vCzGa5Oegp8wKGMA0GCSqGSIb3 DQEBBAUAA4GBACFZ+RGdH+SD6DciubG2E2rk90iryfwKnAMkZtxAaL3a2Hm+Pszv8unYwCo1 DUvSuYz+lWJ+WXCv3+I98boe6za4kLt8tcv+bEoSNZv9516vYLk+xih1E2EY2w9B2tRH6ljy UPgwPp47oQKsp4Q30nHO3wahiS6C77Lhr8ENK41WMIID1jCCAz+gAwIBAgIEAgAB5jANBgkq hkiG9w0BAQUFADBFMQswCQYDVQQGEwJVUzEYMBYGA1UEChMPR1RFIENvcnBvcmF0aW9uMRww GgYDVQQDExNHVEUgQ3liZXJUcnVzdCBSb290MB4XDTAxMDYwMTEyNDcwMFoXDTA0MDYwMTIz NTkwMFowgZMxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEWMBQGA1UEBxMNTW91bnRhaW4g VmlldzEbMBkGA1UEChMSQW1lcmljYSBPbmxpbmUgSW5jMRkwFwYDVQQLExBBT0wgVGVjaG5v bG9naWVzMScwJQYDVQQDEx5JbnRyYW5ldCBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkwgZ8wDQYJ KoZIhvcNAQEBBQADgY0AMIGJAoGBAOLvXyx2Q4lLGl+z5fiqb4svgU1n/71KD2MuxNyF9p4s SSYg/wAX5IiIad79g1fgoxEZEarW3Lzvs9IVLlTGbny/2bnDRtMJBYTlU1xI7YSFmg47PRYH XPCzeauaEKW8waTReEwG5WRB/AUlYybr7wzHblShjM5UV7YfktqyEkuNAgMBAAGjggGCMIIB fjBNBgNVHR8ERjBEMEKgQKA+hjxodHRwOi8vd3d3MS51cy1ob3N0aW5nLmJhbHRpbW9yZS5j b20vY2dpLWJpbi9DUkwvR1RFUm9vdC5jZ2kwHQYDVR0OBBYEFCnbsi2Dfn+LI7vCzGa5Oegp 8wKGMGYGA1UdIARfMF0wRgYKKoZIhvhjAQIBBTA4MDYGCCsGAQUFBwIBFipodHRwOi8vd3d3 LmJhbHRpbW9yZS5jb20vQ1BTL09tbmlSb290Lmh0bWwwEwYDKgMEMAwwCgYIKwYBBQUHAgEw WAYDVR0jBFEwT6FJpEcwRTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD0dURSBDb3Jwb3JhdGlv bjEcMBoGA1UEAxMTR1RFIEN5YmVyVHJ1c3QgUm9vdIICAaMwKwYDVR0QBCQwIoAPMjAwMTA2 MDExMjQ3MzBagQ8yMDAzMDkwMTIzNTkwMFowDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwQIMAYB Af8CAQEwDQYJKoZIhvcNAQEFBQADgYEASmIO2fpGdwQKbA3d/tIiOZkQCq6ILYY9V4TmEiQ3 aftZXuIRsPmfpFeGimkfBmPRfe4zNkkQIA8flxcsJ2w9bDkEe+JF6IcbVLZgQW0drgXznfk6 NJrje2tMcfjrqCuDsDWQTBloce3wYyJewlvsIHq1sFFz6QfugWd2eVP3ldQxggH1MIIB8QIB ATCBmjCBkzELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBW aWV3MRswGQYDVQQKExJBbWVyaWNhIE9ubGluZSBJbmMxGTAXBgNVBAsTEEFPTCBUZWNobm9s b2dpZXMxJzAlBgNVBAMTHkludHJhbmV0IENlcnRpZmljYXRlIEF1dGhvcml0eQICOoEwCQYF Kw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0w MTA2MTgyMTM0MDdaMCMGCSqGSIb3DQEJBDEWBBQ9zi0mT1EGQRKl5ULUXpUZVJyWNzBSBgkq hkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggq hkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgBqmpMGPo/3wQvwA 8BNHBnEDTIFeiXG8l3OQ74M0/taEITOw72SYnCi2pkzciBssqLeILblwgYS9KENAaZOmrhVs lV46h2UmPiW2ve8haCdlmWKFmLmfMZjAs1EGkBdix6MAz32+nBI6QWMpleihBRdAdKYS3gdW N5uiKsX7icRe --------------msD7274DC319E637E85F045771-- -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Mon Jun 18 19:10:50 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23658 for ; Mon, 18 Jun 2001 19:10:48 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f5IM6Bb11875 for ietf-cat-wg-out720680; Mon, 18 Jun 2001 15:06:11 -0700 (PDT) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.72.0.53]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f5ILojV11346 for ; Mon, 18 Jun 2001 14:50:45 -0700 (PDT) Received: from netscape.com (c3po.netscape.com [205.217.237.46]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id RAA29132 for ; Mon, 18 Jun 2001 17:50:44 -0400 (EDT) Received: from continuity.mcom.com (continuity.mcom.com [205.217.237.112]) by netscape.com (8.10.0/8.10.0) with ESMTP id f5ILoAY13022 for ; Mon, 18 Jun 2001 14:50:10 -0700 (PDT) Received: from continuity.mcom.com (localhost [127.0.0.1]) by continuity.mcom.com (980427.SGI.8.8.8/8.8.5) with SMTP id OAA42473 for ; Mon, 18 Jun 2001 14:50:11 -0700 (PDT) To: cat-ietf@mit.edu Path: not-for-mail From: John Gardiner Myers Newsgroups: mcom.list.cat-ietf Subject: Re: I-D ACTION:draft-ietf-cat-sasl-gssapi-05.txt Date: Mon, 18 Jun 2001 14:48:50 -0700 Organization: Netscape Communications Corporation Lines: 75 Message-ID: <3B2E7742.AFE79C5E@netscape.com> References: <200106112149.OAA10891@hammie.isi.edu> <3B263E73.570CA4F9@anl.gov> NNTP-Posting-Host: 192.18.126.70 Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms952C8898575C34FEFA7CECA6" X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: en Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk This is a cryptographically signed message in MIME format. --------------ms952C8898575C34FEFA7CECA6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Douglas E. Engert" wrote: > Since GSS API is designed to allow multiple mechanisms to be > accessed via the single API, there could be a single gssapi plugin, which > loaded all the available gssapi libs, then returned their SASL names. > [...] if the plugin can generate the name from the mechanism OIDs on the fly and > return the list to the SASL library. In this way the client and server will > both have a a list of names which maps to all the possible GSSAPI mechanism > OIDs they support. So the reverse mapping from SASL mechanism name to OID is > not needed, and the SASL mechanism name does not need to be readable. The draft was designed to permit this type of implementation. Specifically, it took the constraint that it should be possible for SASL implementations to be written against the GSS API, exposing GSS mechanisms without needing any information about those mechanisms other than can be obtained through the GSS API. --------------ms952C8898575C34FEFA7CECA6 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature Content-Transfer-Encoding: base64 MIIJFwYJKoZIhvcNAQcCoIIJCDCCCQQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BuowggMMMIICdaADAgECAgI6gTANBgkqhkiG9w0BAQQFADCBkzELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRswGQYDVQQKExJBbWVyaWNhIE9u bGluZSBJbmMxGTAXBgNVBAsTEEFPTCBUZWNobm9sb2dpZXMxJzAlBgNVBAMTHkludHJhbmV0 IENlcnRpZmljYXRlIEF1dGhvcml0eTAeFw0wMTA2MDQyMDExMTNaFw0wMTEyMDEyMDExMTNa MIGCMRMwEQYKCZImiZPyLGQBGRYDY29tMRgwFgYKCZImiZPyLGQBGRYIbmV0c2NhcGUxIzAh BgkqhkiG9w0BCQEWFGpnbXllcnNAbmV0c2NhcGUuY29tMRMwEQYDVQQDEwpKb2huIE15ZXJz MRcwFQYKCZImiZPyLGQBARMHamdteWVyczCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA 0UkG0d+rgk8JBbwwFyX3GgQtTdP8ytSaxbUlZkCOqfqboqMDGfwAr/ViYFXvfnQBHPOgZSCW /nBq9G4hhq+eSEigPSL/Jw7fGul/UGcbb++8tQtwSEYE91I0TxkiA9EyWtZkud+GTHtXHHAG 4U3q9YQVeMw7eokjFD5ibjw7oP8CAwEAAaN+MHwwEQYJYIZIAYb4QgEBBAQDAgWgMA4GA1Ud DwEB/wQEAwIF4DA2BggrBgEFBQcBAQQqMCgwJgYIKwYBBQUHMAGGGmh0dHA6Ly9uc29jc3Au bmV0c2NhcGUuY29tMB8GA1UdIwQYMBaAFCnbsi2Dfn+LI7vCzGa5Oegp8wKGMA0GCSqGSIb3 DQEBBAUAA4GBACFZ+RGdH+SD6DciubG2E2rk90iryfwKnAMkZtxAaL3a2Hm+Pszv8unYwCo1 DUvSuYz+lWJ+WXCv3+I98boe6za4kLt8tcv+bEoSNZv9516vYLk+xih1E2EY2w9B2tRH6ljy UPgwPp47oQKsp4Q30nHO3wahiS6C77Lhr8ENK41WMIID1jCCAz+gAwIBAgIEAgAB5jANBgkq hkiG9w0BAQUFADBFMQswCQYDVQQGEwJVUzEYMBYGA1UEChMPR1RFIENvcnBvcmF0aW9uMRww GgYDVQQDExNHVEUgQ3liZXJUcnVzdCBSb290MB4XDTAxMDYwMTEyNDcwMFoXDTA0MDYwMTIz NTkwMFowgZMxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEWMBQGA1UEBxMNTW91bnRhaW4g VmlldzEbMBkGA1UEChMSQW1lcmljYSBPbmxpbmUgSW5jMRkwFwYDVQQLExBBT0wgVGVjaG5v bG9naWVzMScwJQYDVQQDEx5JbnRyYW5ldCBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkwgZ8wDQYJ KoZIhvcNAQEBBQADgY0AMIGJAoGBAOLvXyx2Q4lLGl+z5fiqb4svgU1n/71KD2MuxNyF9p4s SSYg/wAX5IiIad79g1fgoxEZEarW3Lzvs9IVLlTGbny/2bnDRtMJBYTlU1xI7YSFmg47PRYH XPCzeauaEKW8waTReEwG5WRB/AUlYybr7wzHblShjM5UV7YfktqyEkuNAgMBAAGjggGCMIIB fjBNBgNVHR8ERjBEMEKgQKA+hjxodHRwOi8vd3d3MS51cy1ob3N0aW5nLmJhbHRpbW9yZS5j b20vY2dpLWJpbi9DUkwvR1RFUm9vdC5jZ2kwHQYDVR0OBBYEFCnbsi2Dfn+LI7vCzGa5Oegp 8wKGMGYGA1UdIARfMF0wRgYKKoZIhvhjAQIBBTA4MDYGCCsGAQUFBwIBFipodHRwOi8vd3d3 LmJhbHRpbW9yZS5jb20vQ1BTL09tbmlSb290Lmh0bWwwEwYDKgMEMAwwCgYIKwYBBQUHAgEw WAYDVR0jBFEwT6FJpEcwRTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD0dURSBDb3Jwb3JhdGlv bjEcMBoGA1UEAxMTR1RFIEN5YmVyVHJ1c3QgUm9vdIICAaMwKwYDVR0QBCQwIoAPMjAwMTA2 MDExMjQ3MzBagQ8yMDAzMDkwMTIzNTkwMFowDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwQIMAYB Af8CAQEwDQYJKoZIhvcNAQEFBQADgYEASmIO2fpGdwQKbA3d/tIiOZkQCq6ILYY9V4TmEiQ3 aftZXuIRsPmfpFeGimkfBmPRfe4zNkkQIA8flxcsJ2w9bDkEe+JF6IcbVLZgQW0drgXznfk6 NJrje2tMcfjrqCuDsDWQTBloce3wYyJewlvsIHq1sFFz6QfugWd2eVP3ldQxggH1MIIB8QIB ATCBmjCBkzELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBW aWV3MRswGQYDVQQKExJBbWVyaWNhIE9ubGluZSBJbmMxGTAXBgNVBAsTEEFPTCBUZWNobm9s b2dpZXMxJzAlBgNVBAMTHkludHJhbmV0IENlcnRpZmljYXRlIEF1dGhvcml0eQICOoEwCQYF Kw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0w MTA2MTgyMTQ4NTBaMCMGCSqGSIb3DQEJBDEWBBRrb8zTDDqPhZU5rwSSzEsjFCZkJjBSBgkq hkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggq hkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgFdZMJJPdXAZiVjF Yy2YNBMkR77bhAVes+3dkb4TamUMsLWoVyGKAXcHOsqlgt/ZpfbXceeGUoeIxsVjC2c0mHpx KpESwjFdEx7KNIwvGNqJayeDFgRysG48fJ75IddnBl0xVBFj0aBRPp8OUrcxEX5Gs6Vq8TZz 92IvC/5bkQTM --------------ms952C8898575C34FEFA7CECA6-- -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu From owner-ietf-cat-wg@lists.Stanford.EDU Tue Jun 19 07:41:10 2001 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18156 for ; Tue, 19 Jun 2001 07:41:09 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.11.3/8.11.3) id f5JAU1d16022 for ietf-cat-wg-out720680; Tue, 19 Jun 2001 03:30:01 -0700 (PDT) Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by lists.Stanford.EDU (8.11.3/8.11.3) with ESMTP id f5JARRV15851 for ; Tue, 19 Jun 2001 03:27:28 -0700 (PDT) Received: from www.kwangyang.ac.kr ([210.90.123.2]) by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with ESMTP id GAA01147 for ; Tue, 19 Jun 2001 06:27:26 -0400 (EDT) From: postmaster@mail3.9netway.com Received: from ..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................! .......................................... Message-Id: <200106191018.TAA08519@www.kwangyang.ac.kr> Date: Tue, 19 Jun 2001 06:29:01 -0400 To: MasterCD2001-LastChance@yahoo.com Subject: MasterCD 2001 - E-BIZ Purchasing Sources Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk Last chance for MasterCD2001 at $99.95! Don't be fooled by ANY offer for the outdated MasterDisc 2000, aka MD2000! Due to the many Internet copyright pirates, and those who have copied and released our products without our consent, we have a very, very special offer for you. Due to the overwhelming response to this offer we have become aware that some of you may have not been able to reach us successfully, so we wanted to be sure you had an opportunity to contact us again. Due to technical difficulties, we may not have received your order or your removal request. Removal instructions are located at the end of this message. Please note that our fax number has changed to: 401-621-7810 The Ultimate Internet Marketing Tool, MasterCD2001, now updated with contacts representing 12 Million domains Worldwide! ***$99.95*** until June 22nd! OK, you held out at $999.00, at $799.00 and at $499.00, so here's a one time offer you can't refuse to get: MasterCD2001 for only $99.95. We've slashed the price to get you hooked on our data products. Unlimited usage is yours permanently for just $99.95! You can now access, import and export information about contacts for nearly 12 Million domain names worldwide. All of the domain owners have registered at least one .com, .net or .org domain name, which makes them serious prospects for Internet related business. Our newest database on CD-ROM contains the Names, Contact Information, Physical Address, SIC, Phone #, Fax #, URL (Domain Name), and Contact E-Mail Address which allows you to efficiently target companies Worldwide. Physical Addresses let you target businesses by, Country, State, City, Province, Zip Code, Telephone Area Code, numerous SIC codes and even Local Exchange Prefixes. The data is supplied in a delimited ASCII text format which makes it easy to link or import records into contact management, spreadsheet and all other database related applications. MasterCD2001 NOW ONLY $99.95(US) plus $20 shipping & handling for 2-Day UPS Air within the 48 contiguous United States, $40 shipping & handling otherwise, which includes non-contiguous US and Canada. We are currently shipping our 2nd Quarter 2001 release. Complete the buyer and shipping info, print and fax this form with the completed credit card information. Updates are available quarterly for $99.95 each. This powerful marketing tool is a 100% tax-deductible business expense! Time is running out quickly, so don't delay. ORDER NOW! ______________________________________________________________________ EVISION, USA Must Be Received by: June 22nd ORDER FORM IMPORTANT: To reduce potential order delays, please type your information if possible. If you cannot type your order, then please be sure your writing is legible. Orders are accepted by fax only, for maximum security. Orders will NOT be taken by e-mail or phone. Due to this incredibly discounted promotional price, we are accepting only credit card orders faxed to: *** 401-621-7810 *** Promotional Code: 619Q2C2 Please Send Me: MasterCD2001 for $99.95(US) plus $20 shipping & handling for 2-Day UPS Air within the contiguous US, $40 shipping & handling for International orders (includes Canada and non-contiguous US.) MasterCD2001 _______________$99.95 (plus shipping & handling) S&H Contiguous US __________$20.00_______ S&H Non-Contiguous US_______$40.00_______ Total________ No orders will be accepted without the above shipping and handling fee. I am entering the number of updates I wish to have automatically sent to me, following this one time offer and the "locked in price" of $99.95, plus the above shipping and handling charges, billed each quarter to my credit card only after it is shipped to me. YES_____ Automatically Ship [ ] updates at $99.95 plus the above S&H and bill my credit card at the time of shipping. NO THANK YOU ______ Do not ship any updates and bill my credit card one time only. Please note the required fields below: * = required Buyer/Shipping info: *Name: __________________________________________________________________ Company Name (if applicable): ___________________________________________ *Shipping Address: ______________________________________________________ *City: ______________________________________ *State/Province: ____________________________ *Postal Code: _______________________________ *Country: ___________________________________ *Telephone: _______________________________________________ *Fax: _____________________________________________________ *E-mail Address: __________________________________________ This e-mail address will not be used for ANY purpose other than communication from our company regarding your order. Without providing an e-mail address, you will not be able to track your order. Promotional Code: 619Q2C2 *Card Type-circle one: (MasterCard) (Visa) (Amex) (Discover) *Credit Card Number: ______________________________________ *Expiration Date: _________________________________________ *Signature: _______________________________________________ *Name as appears on Card: _________________________________ *Billing Address of Credit Card if different than shipping: ___________________________________________________________ City & Province/State & Postal Code: ___________________________________________________________ Fax & Email are the only forms of correspondence available due to the incredible pricing of this offer, so please be sure your email address is legible & accurate. EVISION Customer Service will be provided by E-mail or Fax only. Please fax the completed form to >> 401-621-7810 << Promotional Code: 619Q2C2 Evision, USA END ORDER FORM ______________________________________________________________________ ###################################################################### This message is not intended for residents in the States of WA, NV, CA, TN, RI, NC & VA. Screening of addresses has been done to the best of our technical ability. If you wish to remove yourself from future communication, please reply to this email with the word remove in the subject line. One time limited offer only. We reserve the right to revert to standard pricing after June 22nd. ................................................................... -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu