
From sant9442@gmail.com  Thu Jul 30 10:40:48 2009
Return-Path: <sant9442@gmail.com>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A67973A715D for <saag@core3.amsl.com>; Thu, 30 Jul 2009 10:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hiuzifFcFGRu for <saag@core3.amsl.com>; Thu, 30 Jul 2009 10:40:46 -0700 (PDT)
Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com [209.85.211.174]) by core3.amsl.com (Postfix) with ESMTP id A8A7428C285 for <saag@ietf.org>; Thu, 30 Jul 2009 10:40:46 -0700 (PDT)
Received: by ywh4 with SMTP id 4so1053350ywh.17 for <saag@ietf.org>; Thu, 30 Jul 2009 10:40:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=XoT65jaPxGLm22F0eIlIkUtIvkaeYDlvWgjsWfs2s4s=; b=TBlmnnP/DmbWlS2bwOALQsYRgjFTw094eaA9NNOajG3b16NbwEI97uAlaJfnVxMWHD w3uao4xWZDWXtDHb2bXJY+tXYOmiU3K5oNlbABWXZLTjnelFEUzHmMmvwzWgr2ZI2bkF QATh3nK5iO26To5MJ3I0TpV6oEO2KGkVy8OeI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=bKbR3itTpNl30KaVTBx428dFl3jxrfnNztJW0GmCfiFh9Ojn25DgYGgrxjUi4LLn7r 7qMr7InluLxxEx8v5T9FrMu7T16PGkUi7cufGLuktitKgLsr56bcw1llliLMGs7kJAtC 01cjLnuIG+wKRtrIJVBxetOzBCafPBr1QAIDs=
Received: by 10.100.34.16 with SMTP id h16mr1976460anh.48.1248975648098; Thu, 30 Jul 2009 10:40:48 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id d24sm409348and.6.2009.07.30.10.40.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 30 Jul 2009 10:40:46 -0700 (PDT)
Sender: HLS <sant9442@gmail.com>
Message-ID: <4A71DB12.7030408@winserver.com>
Date: Thu, 30 Jul 2009 13:40:34 -0400
From: hector <gmail.sant9442@winserver.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: barryleiba@computer.org
References: <6c9fcc2a0907300052m71a3846kb8adae1370e4c678@mail.gmail.com>
In-Reply-To: <6c9fcc2a0907300052m71a3846kb8adae1370e4c678@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sun, 02 Aug 2009 22:07:44 -0700
Cc: saag@ietf.org, IETF DKIM WG <ietf-dkim@mipassoc.org>
Subject: Re: [saag] [ietf-dkim] DKIM summary report (IETF 75)
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jul 2009 17:45:22 -0000

Whats missing is possible a survey on why there is a market of 
potential implementators who are on the fence, have not gave the "go 
ahead" or are just plain leary about the whole thing, even among those 
who have been involved since early on.

In other words, a survey to find out what are the barriers to 
implementation.

--

Barry Leiba wrote:

> The DKIM working group met on Tuesday afternoon.  The group's
> chartered work is nearly done (the last document is in WGLC, and two
> others are now in the RFC Editor queue), so the goal of this meeting
> was to discuss implementation reports and draft-standard progression
> for the base protocol.
> 
> Dave Crocker has posted implementation surveys to the mailing list,
> but has so far gotten few replies.  WG participants were urged to
> complete them, and to pass them on to others.  Barry will pass them to
> MAAWG (Messaging Anti-Abuse Working Group) and urge response, as IETF
> liaison to MAAWG.  Barry would like to collect data not only on
> feature use by signers and verifiers, but also on what use the
> verifiers make of the results.
> 
> There was much discussion about dropping unused or little-used
> features in the process of going to draft standard.  We note that RFC
> 2026 *requires* dropping features that are truly unused, but whether
> to drop others is a different question.  Several opinions were given
> about keeping all features, because, while there's plenty of
> experience with signing and verifying, knowledge of usage of the
> result of verifying is still limited.  We don't yet know what
> verifiers will decide is important, over time.  Counter-argument:
> history shows that when we learn that, we'll find that the features we
> kept purely speculatively will be the wrong ones anyway.
> 
> Informal vote showed approximately a 2-to-1 preference for keeping
> *all* features, versus removing some.  Chairs don't consider that to
> be sufficient for "rough consensus", so it will be discussed on the
> list.  Pasi pointed out, and the chairs agree, that because we had
> consensus on these to start with, the default action, lacking clear
> consensus to remove a feature, is to keep it.
> 
> There was also discussion indicating that documenting DKIM use cases
> could be helpful.  Perhaps this could be added to the "deployment"
> document (in WGLC now), or perhaps using an easily updated wiki.
> 
> Barry Leiba (and Stephen Farrell)
> _______________________________________________
> NOTE WELL: This list operates according to 
> http://mipassoc.org/dkim/ietf-list-rules.html



From lars.eggert@nokia.com  Tue Aug  4 04:12:15 2009
Return-Path: <lars.eggert@nokia.com>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D8A3B28C344 for <saag@core3.amsl.com>; Tue,  4 Aug 2009 04:12:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ta7U4gMAmpgE for <saag@core3.amsl.com>; Tue,  4 Aug 2009 04:12:15 -0700 (PDT)
Received: from mail.fit.nokia.com (mail.fit.nokia.com [195.148.124.195]) by core3.amsl.com (Postfix) with ESMTP id E95B728C33B for <saag@ietf.org>; Tue,  4 Aug 2009 04:12:14 -0700 (PDT)
Received: from [10.180.41.51] ([192.100.124.156]) (authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id n74BBVgI046327 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 4 Aug 2009 14:11:32 +0300 (EEST) (envelope-from lars.eggert@nokia.com)
Message-Id: <54EE9175-D8D6-4BC3-B157-4D39436CAC09@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: "Laganier, Julien" <julienl@qualcomm.com>
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C22ACCE6D@NALASEXMB04.na.qualcomm.com>
Content-Type: multipart/signed; boundary=Apple-Mail-19-494142233; micalg=sha1; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 4 Aug 2009 14:11:21 +0300
References: <BF345F63074F8040B58C00A186FCA57F1C22ACCE6D@NALASEXMB04.na.qualcomm.com>
X-Mailer: Apple Mail (2.935.3)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (mail.fit.nokia.com [195.148.124.194]); Tue, 04 Aug 2009 14:11:32 +0300 (EEST)
Cc: "saag@ietf.org" <saag@ietf.org>
Subject: Re: [saag] BTNS non-meeting report
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 11:12:15 -0000

--Apple-Mail-19-494142233
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

On 2009-7-29, at 23:15, Laganier, Julien wrote:
> draft-ietf-btns-connection-latching is in IESG: resolution of the  
> last DISCUSS regarding SCTP handling of latch breakage is being  
> discussed on the WG mailing list.

And TSV folks hope this concludes in a timely manner, since the entire  
set of NFSv4.1 documents have been blocked form publication because of  
this for 26 weeks now...

Lars
--Apple-Mail-19-494142233
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEEi7WbMMKa2GLKFpQDaOBQEwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA4MDgyMzE3NDMzOVoXDTA5MDgyMzE3NDMz
OVowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAlwQVktJZCY89iU6jcW1XnZQN+aMgF2utCUT3H3ZKB5Jbet1SDWt0md/W
571bHjxtn9CfEJdochNL3l9f1WiJNdVbJ182557Ltx9SojqthpqtA0jKEqo2gqrf+raUj1demmo0
6ocsLqv046CrwidOp6k0RAfvkKPLhD4PD9Nk3oaZuxqBz1wY4u8Q83iWMArDeXiQxfNZnOBz5cDs
VvVjTjitm3VANkbD02tNkwl5AHw7htde4yH8hIwlfzqsAtHBEah3HyOvs9b+gHg2pFz9eS+HuotY
ZKycCweRs8NKXoCg+zAkVYi3zvZEH2VOuPlpMQMrB9+fLWg2UBsTeZ864wIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQBMdV2U+ryV5t3nuBFH19XKflodN6Bc60GBYHHY/Z0+Cl08Q75qzTt02IILBg+/YVh/fygb
6pFrOm1sFtLN7fENBfbO2VtpFjP2lGUgbXTVT5xGM6+MtqZiBI6LqexAeY6gsd/taoUfy9fZG42d
ciBA9gSGlQjjWQyG8mb5HR8L9jCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
SLtZswwprYYsoWlANo4FATAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wOTA4MDQxMTExMjJaMCMGCSqGSIb3DQEJBDEWBBTQW0L5S1yclMO9
AeOb2z4wEUBaPjCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEEi7WbMMKa2GLKFpQDaOBQEwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEEi7WbMMKa2GLKFpQDaOBQEw
DQYJKoZIhvcNAQEBBQAEggEAfNhV8hzJUD3e4yrakQJeDrgXu/nQSu17xC4l5C3DRulCC4oTCHBO
dtNTEcdO7hqigNpcvPxJJy5n3+RUs6OLLy3RoTSKNTw6STVK06mXZXdPdo2uJaRuvPPzitFYUnib
4dsJCQB7aqv24jjWeFPr3qVoghFD114hsnGTucilhZDppY+sACUexgq8pCFBSzQTpCpPBLJuKZq/
t8GmA9f3oymWQPyJph7xfI46iNxGGB8JZjx2prcQ5C1ivRSoMKzjVU1lOAW7KNIIC5j2bZ8FZWGW
IL+Ctu0oo9Lj8znwYfj0qbLHFeR1z0m5wblqvO/HVKNOo+J3EIa0/Qos3qNWNAAAAAAAAA==

--Apple-Mail-19-494142233--

From dol@cryptocom.ru  Wed Aug  5 04:20:26 2009
Return-Path: <dol@cryptocom.ru>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E44DE3A69FB for <saag@core3.amsl.com>; Wed,  5 Aug 2009 04:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.129
X-Spam-Level: 
X-Spam-Status: No, score=-1.129 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EwRWUsCUUC3e for <saag@core3.amsl.com>; Wed,  5 Aug 2009 04:20:26 -0700 (PDT)
Received: from mx.cryptocom.ru (mx.cryptocom.ru [87.245.158.60]) by core3.amsl.com (Postfix) with ESMTP id C26DE3A68E3 for <saag@ietf.org>; Wed,  5 Aug 2009 04:20:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx.cryptocom.ru (Postfix) with ESMTP id AC6FC3EC50; Wed,  5 Aug 2009 15:20:27 +0400 (MSD)
X-Virus-Scanned: Debian amavisd-new at cryptocom.ru
Received: from mx.cryptocom.ru ([127.0.0.1]) by localhost (mx.cryptocom.ru [127.0.0.1]) (amavisd-new, port 10024) with LMTP id RbAyZa6Vof89; Wed,  5 Aug 2009 15:20:27 +0400 (MSD)
Received: from [10.51.22.241] (reedcat.lan.cryptocom.ru [10.51.22.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.cryptocom.ru (Postfix) with ESMTP id 163DA3EC49; Wed,  5 Aug 2009 15:20:27 +0400 (MSD)
Message-ID: <4A796AFB.2070905@cryptocom.ru>
Date: Wed, 05 Aug 2009 15:20:27 +0400
From: Basil Dolmatov <dol@cryptocom.ru>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: namedroppers@ops.ietf.org, cfrg@irtf.org, saag@ietf.org
Content-Type: multipart/mixed; boundary="------------010904070109070104010906"
Subject: [saag] [Fwd: I-D Action:draft-dolmatov-cryptocom-gost2814789-01.txt]
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2009 11:20:27 -0000

This is a multi-part message in MIME format.
--------------010904070109070104010906
Content-Type: text/plain; charset=windows-1251; format=flowed
Content-Transfer-Encoding: 7bit

New I-D has been posted, which is a translation to English of text of 
Russian GOST standard (GOST 28147-89) for block ciphering.

This  publication being combined with the drafts
draft-dolmatov-cryptocom-gost34102001-02
draft-dolmatov-cryptocom-gost341194-01

forms a complete set of Russian cryptographic GOST standards in English.


dol@

--------------010904070109070104010906
Content-Type: message/rfc822;
 name="I-D Action:draft-dolmatov-cryptocom-gost2814789-01.txt.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="I-D Action:draft-dolmatov-cryptocom-gost2814789-01.txt.eml"

Return-Path: <i-d-announce-bounces@ietf.org>
X-Spam-Checker-Version: SpamAssassin 3.1.7-deb3 (2006-10-05) on 
	mx.cryptocom.ru
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,
	MIME_BOUND_NEXTPART,NO_REAL_NAME autolearn=no version=3.1.7-deb3
X-Original-To: dol@cryptocom.ru
Delivered-To: dol@cryptocom.ru
Received: from localhost (localhost [127.0.0.1])
	by mx.cryptocom.ru (Postfix) with ESMTP id D044F3EC4D;
	Wed,  5 Aug 2009 14:45:49 +0400 (MSD)
X-Virus-Scanned: Debian amavisd-new at cryptocom.ru
Received: from mx.cryptocom.ru ([127.0.0.1])
	by localhost (mx.cryptocom.ru [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id bGUw-6pusTUw; Wed,  5 Aug 2009 14:45:49 +0400 (MSD)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32])
	by mx.cryptocom.ru (Postfix) with ESMTP id 2CA2E3EC49
	for <dol@cryptocom.ru>; Wed,  5 Aug 2009 14:45:49 +0400 (MSD)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CD8528C553;
	Wed,  5 Aug 2009 03:45:03 -0700 (PDT)
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 88B6528C4F3; Wed,  5 Aug 2009 03:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-dolmatov-cryptocom-gost2814789-01.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090805104501.88B6528C4F3@core3.amsl.com>
Date: Wed,  5 Aug 2009 03:45:01 -0700 (PDT)
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : GOST 28147-89 encryption, decryption and MAC algorithms
	Author(s)       : V. Dolmatov, et al.
	Filename        : draft-dolmatov-cryptocom-gost2814789-01.txt
	Pages           : 14
	Date            : 2009-08-05

This document is intended to be a source of information about the
Russian Federal standard for for electronic encryption, decryption
and MAC algorithms (GOST 28147-89) [GOST28147], which is one of the
official standards in the Russian cryptography, used in Russian 
algorithms (GOST algorithms). Recently, the Russian cryptography
started to be used in different applications intended to work with
the OpenSSL cryptographic library. Thus, this document has been
created for the informational purposes for users of Russian
cryptography.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-dolmatov-cryptocom-gost2814789-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-dolmatov-cryptocom-gost2814789-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-08-05033956.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--NextPart--


--------------010904070109070104010906--

From housley@vigilsec.com  Wed Aug  5 07:57:51 2009
Return-Path: <housley@vigilsec.com>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 452783A6BF0 for <saag@core3.amsl.com>; Wed,  5 Aug 2009 07:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.126
X-Spam-Level: 
X-Spam-Status: No, score=-102.126 tagged_above=-999 required=5 tests=[AWL=0.473, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-9F8m1lGmkh for <saag@core3.amsl.com>; Wed,  5 Aug 2009 07:57:50 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 98F873A6BFF for <saag@ietf.org>; Wed,  5 Aug 2009 07:57:50 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 1F677F24004; Wed,  5 Aug 2009 10:35:35 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id D9VMgdyYBiKO; Wed,  5 Aug 2009 10:35:22 -0400 (EDT)
Received: from THINKPADR52.vigilsec.com (pool-96-241-154-102.washdc.fios.verizon.net [96.241.154.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 8926C9A4721; Wed,  5 Aug 2009 10:35:34 -0400 (EDT)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 05 Aug 2009 10:35:20 -0400
To: Basil Dolmatov <dol@cryptocom.ru>
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4A796AFB.2070905@cryptocom.ru>
References: <4A796AFB.2070905@cryptocom.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20090805143534.8926C9A4721@odin.smetech.net>
Cc: cfrg@irtf.org, saag@ietf.org
Subject: [saag] draft-dolmatov-cryptocom-gost34102001
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2009 14:57:51 -0000

I suggest that you come up with a notation that avoids the use of the 
underscore on the previous line.  Many people do not use a font that 
will ensure proper alignment.

Russ


From dol@cryptocom.ru  Wed Aug  5 09:12:20 2009
Return-Path: <dol@cryptocom.ru>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FE073A6C0F for <saag@core3.amsl.com>; Wed,  5 Aug 2009 09:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.732
X-Spam-Level: 
X-Spam-Status: No, score=-1.732 tagged_above=-999 required=5 tests=[AWL=1.397,  BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0+sUR2S9F5LR for <saag@core3.amsl.com>; Wed,  5 Aug 2009 09:12:19 -0700 (PDT)
Received: from mx.cryptocom.ru (mx.cryptocom.ru [87.245.158.60]) by core3.amsl.com (Postfix) with ESMTP id 4091D3A6BB6 for <saag@ietf.org>; Wed,  5 Aug 2009 09:12:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx.cryptocom.ru (Postfix) with ESMTP id EC6473EC56; Wed,  5 Aug 2009 19:20:03 +0400 (MSD)
X-Virus-Scanned: Debian amavisd-new at cryptocom.ru
Received: from mx.cryptocom.ru ([127.0.0.1]) by localhost (mx.cryptocom.ru [127.0.0.1]) (amavisd-new, port 10024) with LMTP id EO3q+rqLMUp2; Wed,  5 Aug 2009 19:20:03 +0400 (MSD)
Received: from [10.51.22.241] (reedcat.lan.cryptocom.ru [10.51.22.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.cryptocom.ru (Postfix) with ESMTP id 9A1063EC50; Wed,  5 Aug 2009 19:20:03 +0400 (MSD)
Message-ID: <4A79A323.5070809@cryptocom.ru>
Date: Wed, 05 Aug 2009 19:20:03 +0400
From: Basil Dolmatov <dol@cryptocom.ru>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
References: <4A796AFB.2070905@cryptocom.ru> <20090805143534.8926C9A4721@odin.smetech.net>
In-Reply-To: <20090805143534.8926C9A4721@odin.smetech.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: cfrg@irtf.org, saag@ietf.org
Subject: Re: [saag] draft-dolmatov-cryptocom-gost34102001
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2009 16:12:20 -0000

Fixed...

Vector notation changed from letters with vector sign (underscore) to 
simple capital letters (unfortunately, no bold in format :()

Thanks!

dol@

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.

	Title           : GOST R 34.10-2001 digital signature algorithm
	Author(s)       : V. Dolmatov, et al.
	Filename        : draft-dolmatov-cryptocom-gost34102001-03.txt
	Pages           : 17
	Date            : 2009-08-05


Russ Housley пишет:
> I suggest that you come up with a notation that avoids the use of the 
> underscore on the previous line.  Many people do not use a font that 
> will ensure proper alignment.
> 
> Russ
> 

From j.larmouth@btinternet.com  Sun Aug  9 04:55:03 2009
Return-Path: <j.larmouth@btinternet.com>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 852353A6C48 for <saag@core3.amsl.com>; Sun,  9 Aug 2009 04:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Level: 
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNPJ+pC1FtkN for <saag@core3.amsl.com>; Sun,  9 Aug 2009 04:55:02 -0700 (PDT)
Received: from smtp812.mail.ird.yahoo.com (smtp812.mail.ird.yahoo.com [217.146.188.72]) by core3.amsl.com (Postfix) with SMTP id 4016B3A6C44 for <saag@ietf.org>; Sun,  9 Aug 2009 04:55:01 -0700 (PDT)
Received: (qmail 92690 invoked from network); 9 Aug 2009 11:55:03 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:Reply-To:User-Agent:X-Accept-Language:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=K9b0oxUEOCKHJhzEyLacSI4BP7vgWGFrN7j4R7zgPvAYnlIqhtxukvnHsovC63WLh90HHwOp26F+2Bi6VA9AwtljwXNZe1oj2U1Xn2Grbf9BnqwyfctxOEps3OZhea+KQGRqP+vEkfUsOSbtgwREgUgi2UaCPv/iAdd++WiMLt8= ; 
Received: from unknown (HELO ?192.168.1.75?) (j.larmouth@86.145.194.232 with plain) by smtp812.mail.ird.yahoo.com with SMTP; 9 Aug 2009 11:55:02 -0000
X-Yahoo-SMTP: wkRZlpKswBD4hYA5WOvxKyA0utS_ehUG.AZgJb2EFBo2v2XeQHg-
X-YMail-OSG: 5GyQFwoVM1mJEZuCAKFQFpDBE5FK8nRenLFrqq51ySMSGusJyIJcy6mUI32B.upEBMREIWJIlJ_AEA.zeoW2xVuOY8B2g8b7i3Yi38qNo3hUCPgLRmJX3RbaSsVyPobMlRI1bteaSr5of86jPvBDTMN2SdiXsei._WD09jLacvtAwTT2i0mEhQBivolKeKM5Npqa2cyK3WpbFBdQCxPXoRfo0siQgnX7G1giRJieCoj8GSR8h0KsMYR7lwgXOBiSvaXBLEJC2akERTXB0VPOZgzw9q2PcfFHYj8.dPDoxgdiv5ftTgoBoBNYaDYeOMHstY0hEO.9jMJOznlTAISWqWw4E0tc
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4A7EB914.3000508@btinternet.com>
Date: Sun, 09 Aug 2009 12:55:00 +0100
From: John Larmouth <j.larmouth@btinternet.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Sean Turner <turners@ieca.com>
References: <4A7058C5.2060109@ieca.com>
In-Reply-To: <4A7058C5.2060109@ieca.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sun, 09 Aug 2009 23:01:55 -0700
Cc: ietf-smime@imc.org, saag@ietf.org
Subject: Re: [saag] SMIME report (IETF 75)
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: j.larmouth@btinternet.com
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Aug 2009 11:55:03 -0000

Folks,

This may be too late (we are not sure whether the comment was sent in 
earlier or not), or may already have been dealt with.

However, a colleague has checked the ASN.1 and reports:

"I have reviewed draft-ietf-smime-new-asn1-05.txt and 	also draft-ietf-pkix-new-asn1-05.txt
because the smime IMPORTS from that. Everything seems to be OK. I have only one comment about
draft-ietf-pkix-new-asn1-05.txt: in three places in OID values "member-body" is misspelled
as "memberBody".

Jean-Paul."

John L




Sean Turner wrote:

>
> The SMIME WG did not meet in Stockholm.
>
> We have 8 IDs.  Since the last meeting, 5 IDs have entered the RFC 
> editor's queue raising the number of SMIME WG IDs with the RFC editor 
> to 7:
>
> - draft-ietf-smime-multisig
> - draft-ietf-smime-sha2
> - draft-ietf-smime-3850bis
> - draft-ietf-smime-3850bis
> - draft-ietf-smime-3278bis
> - draft-ietf-smime-new-asn1
> - draft-ietf-smime-3852bis
>
> All of the documents are pinned on documents from PKIX, the TLP 
> revisions, or both.
>
> A new version of draft-ietf-smime-rsa-kem was posted to address 
> comments made by Steve Kent during his SECDIR review.  We issued a 2nd 
> WGLC because the revisions were pretty substantial.  One set of 
> comments, which I would categorize as minor, was received during the 
> 2nd WGLC.  A new version will be posted, and then the document will 
> passed to Tim Polk.
>
> Once all the documents have been published we will initiate the 
> procedure to shut down the WG.
>
> spt
>
>

-- 
   Prof John Larmouth
   Larmouth T&PDS Ltd
   (Training and Protocol Design Services Ltd)
   1 Blueberry Road                     
   Bowdon                               j.larmouth@btinternet.com
   Altrincham
   Cheshire
   WA14 3LS                 
   England
   Tel: +44 161 928 1605


From Pasi.Eronen@nokia.com  Tue Aug 18 23:30:19 2009
Return-Path: <Pasi.Eronen@nokia.com>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA6E23A6AF0 for <saag@core3.amsl.com>; Tue, 18 Aug 2009 23:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.255
X-Spam-Level: 
X-Spam-Status: No, score=-6.255 tagged_above=-999 required=5 tests=[AWL=0.344,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sN9jHIr+bJGf for <saag@core3.amsl.com>; Tue, 18 Aug 2009 23:30:19 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id EC9E53A6AF9 for <saag@ietf.org>; Tue, 18 Aug 2009 23:30:17 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n7J6Rm0p025506 for <saag@ietf.org>; Wed, 19 Aug 2009 01:28:05 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 19 Aug 2009 09:28:28 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 19 Aug 2009 09:28:13 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Wed, 19 Aug 2009 08:28:12 +0200
From: <Pasi.Eronen@nokia.com>
To: <saag@ietf.org>
Date: Wed, 19 Aug 2009 08:28:11 +0200
Thread-Topic: IETF75 SAAG draft minutes
Thread-Index: AcogljlEprPSwL4cT6GCOkuMZ56u9Q==
Message-ID: <808FD6E27AD4884E94820BC333B2DB773A730C4EFB@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 19 Aug 2009 06:28:13.0223 (UTC) FILETIME=[3A818370:01CA2096]
X-Nokia-AV: Clean
Subject: [saag] IETF75 SAAG draft minutes
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Aug 2009 06:30:19 -0000

I've uploaded the draft minutes from SAAG here:=20

http://www.ietf.org/proceedings/75/minutes/saag.txt

Please send any corrections/additions to me and Tim.=20
(And big thanks to Jim Schaad for taking notes!)
=20
Best regards,
Pasi

From Pasi.Eronen@nokia.com  Thu Aug 20 09:20:51 2009
Return-Path: <Pasi.Eronen@nokia.com>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDB7028C151 for <saag@core3.amsl.com>; Thu, 20 Aug 2009 09:20:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.27
X-Spam-Level: 
X-Spam-Status: No, score=-6.27 tagged_above=-999 required=5 tests=[AWL=0.329,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id REVZhg6fT8Ne for <saag@core3.amsl.com>; Thu, 20 Aug 2009 09:20:50 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 9D54B28C12E for <saag@ietf.org>; Thu, 20 Aug 2009 09:20:49 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n7KGKROi015149 for <saag@ietf.org>; Thu, 20 Aug 2009 19:20:40 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 20 Aug 2009 19:20:34 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 20 Aug 2009 19:20:29 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-01.mgdnok.nokia.com ([65.54.30.5]) with mapi; Thu, 20 Aug 2009 18:20:29 +0200
From: <Pasi.Eronen@nokia.com>
To: <saag@ietf.org>
Date: Thu, 20 Aug 2009 18:20:26 +0200
Thread-Topic: Draft liaison response to ITU-T JCA-IdM re: identity management
Thread-Index: AcohsiCw8+ayx+BHSZOSrnzuGiKyGQ==
Message-ID: <808FD6E27AD4884E94820BC333B2DB773A73192474@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Aug 2009 16:20:29.0450 (UTC) FILETIME=[22292EA0:01CA21B2]
X-Nokia-AV: Clean
Subject: [saag] Draft liaison response to ITU-T JCA-IdM re: identity management
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Aug 2009 16:20:52 -0000

Hi all,

A while back we received a liaison statement from ITU-T's Joint
Coordination Activity for Identity Management (JCA-IdM), inquiring
about current identity management standards in IETF and our roadmaps
for future work. The liaison statement is available here:

https://datatracker.ietf.org/documents/LIAISON/file654.doc

While we don't usually maintain roadmap PowerPoints in IETF, and the
term "identity management" is rarely used in RFCs, many IETF
technologies have important roles when it comes to managing
identities. Thus, some kind of response is probably warranted.

Tim and I have started preparing a response, briefly listing some IETF
technologies that are somehow related to identity management.  The
list is not intended to cover everything IETF has done (preparing such
a list is unlikely to be a good use of IETF's resources).

The current draft text is included below.  If you have any comments,
or are interested in contributing to the liaison statement text,
please send email to Tim and me within two weeks.
=20
Best regards,
Pasi & Tim

--------------

The Internet Engineering Task Force (IETF) Security Area would like to
thank ITU-T Joint Coordination Activity for Identity Management for
the opportunity to provide information about IETF's identity
management activities.

The IETF has developed or is currently developing a number of
standards dealing with how entities (including humans, hosts, routers,
and so on) are identified, how those identities are authenticated, and
how they're used for, e.g., access control and other purposes.  These
standards may be used to establish, authenticate, and leverage
identity information at various network layers in Internet protocols
and applications.

The IETF does not maintain roadmaps covering past and future work for
identity management specifically, but we believe at least the
following work may be of interest to ITU-T JCA-IdM:

* Transport Layer Security (TLS), HTTP authentication mechanisms,
  and HTTP cookies provide a foundation for authenticating servers
  and users on the web.

* DNS Security (DNSSEC) provides data origin authentication and data
  integrity for DNS names, which are often used as host identities,
  and included in typical user identities such as email addresses and
  SIP URIs.

* DomainKeys Identified Mail (DKIM) provides an authenticated
  identity who claims responsibility for a message, assisting
  in control of spam and phishing.

* S/MIME and OpenPGP provide end-to-end authentication of
  email sender identities.

* Internet X.509 Public Key Infrastructure (PKIX) certificate
  profiles and protocols provide basis for managing identities
  and authorizations with a public key infrastructure.

* Lightweight Directory Access Protocol (LDAP), Remote Authentication
  Dial In User Service (RADIUS), and Diameter are used to access
  directories and authentication/authorization/accounting (AAA)
  servers, facilitating single sign-on and centralized management of
  identity and authorization information.

* Simple Authentication and Security Layer (SASL) framework and
  mechanisms, Kerberos, and Generic Security Service Application
  Program Interface (GSS-API) framework and mechanisms are used to
  authenticate users in number of protocols, ranging from IMAP and
  XMPP/Jabber to NFS and SMB/CIFS. Kerberos is also used to facilitate
  single sign-on especially in enterprise environments.

* Extensible Authentication Protocol (EAP) framework and
  authentication methods are used to authenticate users in, for
  example, wireless networks such as Wi-Fi and WiMAX.

* Session Identity Protocol (SIP) authentication and identity=20
  mechanisms can bw applied to a broad variety of applications,=20
  including voice, conferencing, and messaging.

* Open Authentication Protocol (OAUTH) leverages identity information
  to permit a user to grant a third-party access to their resources,=20
  without sharing or revealing their credentials. =20

* Dynamic Symmetric Key Provisioning Protocol (DSKPP) deals with how
  symmetric key based authentication credentials are provisioned (and
  connected with an existing identity), especially in the context of
  one-time password tokens.

The IETF also leverages identity credentials across network layers
using channel bindings, as described in RFC 5056.  With channel
bindings, authentication results in the application layer are
cryptographically bound to the security mechanisms provided at the
session or transport layer.  Several IETF protocols include support
for channel bindings.

-------------------


From Pasi.Eronen@nokia.com  Mon Aug 31 03:44:18 2009
Return-Path: <Pasi.Eronen@nokia.com>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 697143A6DE7; Mon, 31 Aug 2009 03:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.333
X-Spam-Level: 
X-Spam-Status: No, score=-6.333 tagged_above=-999 required=5 tests=[AWL=0.266,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aRbG89SvLWJU; Mon, 31 Aug 2009 03:44:17 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 1067B3A6D9E; Mon, 31 Aug 2009 03:44:16 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n7VAhpwt021747; Mon, 31 Aug 2009 13:44:13 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 31 Aug 2009 13:44:23 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 31 Aug 2009 13:44:23 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 31 Aug 2009 13:44:12 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-03.mgdnok.nokia.com ([65.54.30.7]) with mapi; Mon, 31 Aug 2009 12:44:12 +0200
From: <Pasi.Eronen@nokia.com>
To: <saag@ietf.org>, <secdir@ietf.org>
Date: Mon, 31 Aug 2009 12:44:10 +0200
Thread-Topic: Pasi's AD Notes for July-August 2009
Thread-Index: AcoqJ/k2vYMRlclsT1Sn73PVeMSLng==
Message-ID: <808FD6E27AD4884E94820BC333B2DB773C014E5818@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 31 Aug 2009 10:44:12.0889 (UTC) FILETIME=[FA898C90:01CA2A27]
Subject: [saag] Pasi's AD Notes for July-August 2009
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Aug 2009 10:44:18 -0000

Here's again a short status update about what things are going on from
my point-of-view. If you notice anything that doesn't look right, let
me know -- miscommunication and mix-ups do happen.

Best regards,
Pasi

MISC NOTES

- Routing ADs appointed Rene Struik as security advisor for ROLL WG.
- Preparing a liaison statement reply to ITU-T regarding
  identity management (draft posted to SAAG recently).
- Compiled statistics for security area mailing lists (posted to=20
  SecDir list).
- Worked with Tim on advice on handling variable-length keys in TCP-AO.
- Some tools/datatracker work.
- (not wearing AD hat): Errata #1628 (for RFC 4742): waiting for
  IANA to update the registry [since 2009-08-31]
- Some discussions re: draft-latze-emu-eap-tpm.

WORKING GROUPS

DKIM
- draft-ietf-dkim-overview: published as RFC 5585.
- draft-ietf-dkim-rfc4871-errata: published as RFC 5672.
- draft-ietf-dkim-ssp: published as RFC 5617.
- Waiting for Stephen and Barry for new charter text (noting that=20
  current work items are completed and adding 4871bis)
- I still need to review what to do about errata 1385, 1532, and 1596

EMU

IPSECME
- draft-ietf-ipsecme-ikev2-resumption: waiting for secretariat
  to send IETF last call announcement [since 2009-08-31].
- A virtual interim meeting is planned for 2009-09-22.
- Still working on fixing the IANA registrations of RFC 4543;=20
  currently waiting for IANA [since 2009-07-31]
- draft-ietf-ipsecme-ikev2-redirect (not wearing AD hat; Tim=20
  is handling this one): waiting for Cullen to review the new
  version and clear his DISCUSS [since 2009-08-04]
- draft-ietf-ipsecme-ikev2-ipv6-config (not wearing AD hat):=20
  waiting for Tim to start IETF last call or provide=20
  additional comments [since 2009-08-20]

ISMS
- draft-ietf-isms-secshell: published as RFC 5592.
- draft-ietf-isms-tmsm: published as RFC 5590.
- draft-ietf-isms-transport-security-model: published as RFC 5591.
- draft-ietf-isms-radius-usage: published as RFC 5608.
- Rechartering approved by IESG.
- Appointed Russ Mundy as new co-chair.

KEYPROV
- Some emails I haven't read yet...

PKIX
- draft-ietf-pkix-rfc4055-update: in RFC Editor queue, waiting for
  smime-3851bis draft (not a normative reference, but authors
  preferred it this way), which is waiting for several other drafts
  (including pkix-3281update and pkix-sha2-dsa-ecdsa).

SASL
- draft-ietf-sasl-scram: in Publication Requested, waiting for
  me to read it [since 2009-08-27]
- (not WG item) draft-altman-tls-channel-bindings: currently
  in informal "pseudo-WGLC" on SASL/TLS WG lists -- I've promised
  to sponsor this as individual submission.
- Mailing list moved to ietf.org - thanks, Paul!

SYSLOG
- draft-ietf-syslog-sign: waiting for authors to submit a revised
  ID before starting IETF last call [since 2009-08-31]
- Recharter text sent to IESG/IAB review, expected to be approved
  in 2009-09-10 IESG telechat.

TLS
- draft-ietf-tls-extractor: waiting for Eric to reply to the
  IETF last call comments that were about the document contents,
  and revise draft if needed [since 2009-08-13]
- draft-ietf-tls-rfc4366-bis: in IETF last call (ends 2009-09-07)
- Worked with secretariat to get Certicom's PDF file stored=20
  on www.ietf.org.
- (not WG item) see SASL WG for draft-altman-tls-channel-bindings
- Looking into errata #117 (for RFC 4346)

OTHER DOCUMENTS

DISCUSSES (active -- something happened within last month)

- draft-cain-post-inch-phishingextns: waiting for authors
  to submit a revised ID [since 2009-08-27]
- draft-freed-sieve-in-xml: waiting for authors to propose changes
  or submit a revised ID [since 2009-08-13]
- draft-housley-tls-authz-extns: waiting for authors to submit
  a revised ID [since 2009-08-13]
- draft-ietf-l3vpn-v6-ext-communities: text agreed, waiting for
  Ross to enter an RFC editor note [since 2009-08-26]
- draft-ietf-ltans-dssc: waiting for authors to submit a=20
  revised ID [since 2009-08-10]
- draft-ietf-mext-binding-revocation: waiting for authors to
  submit a revised ID or RFC editor note [since 2009-08-27]
- draft-ietf-netconf-partial-lock: waiting for authors to=20
  propose text or submit a revised ID [since 2009-08-13]
- draft-ietf-ntp-autokey: waiting for Ralph to get more
  information from WG [since 2009-08-20]
- draft-ietf-opsawg-syslog-alarm: text agreed, waiting for authors=20
  to submit a revised ID or RFC editor note [since 2009-08-27]

DISCUSSES (stalled -- I haven't heard anything from the authors
or document shepherd for over one month)

- draft-ietf-dime-diameter-api: waiting for Dan to get WG's opinion=20
  on whether this will be useful and if yes, why [since 2009-06-18]
- draft-ietf-vrrp-unified-spec: waiting for authors to propose
  text [since 2008-07-26]

DISCUSSES (presumed dead -- I haven't heard anything from the authors
or document shepherd for over three months)

- draft-cheshire-dnsext-nbp: waiting for authors to reply to my
  comments [since 2008-12-03] (pinged again on 2009-04-30 and
  2009-06-09)
- draft-ietf-bfd-base: text agreed, waiting for authors to submit=20
  a revised ID [since 2009-03-19] (pinged again on 2009-04-30
  and 2009-06-09)
- draft-ietf-ntp-ntpv4-proto: waiting for authors to reply to
  my email or submit a revised ID [since 2009-04-16]
- draft-ietf-sipping-policy-package: waiting for draft-ietf-sipping-
  media-policy-dataset to progress (or more information from Robert)
  [since 2008-10-28]

--end--
