headers
Gregory S. Chudov | 1 Aug 2009 18:51
Picon
Favicon

Re: [saag] GOST algorithms descriptions

> (id-GostR3411-94-CryptoProParamSet) in all situations. Given that all
> (?)  IETF GOST standards use this param set, why not provide test
> vectors for it rather than the (otherwise unused) TestParamSet?

My understanding is that the drafts are an exact translation of the
official standard,
including the examples, as published in 1994. That kind of makes those examples
reliable and official, but of course additional examples wouldn't hurt.

Also, there is an example of gost3411-94 digest with gost3410-2001
signature in rfc4491.txt.
The bad news is that only the source data and final result (signature
value) are provided there,
with no intermediate values.
Permalink | Reply | 1 comment |
headers
Basil Dolmatov | 3 Aug 2009 11:54
Picon
Favicon

Re: [saag] GOST algorithms descriptions


Gregory S. Chudov пишет:
>> (id-GostR3411-94-CryptoProParamSet) in all situations. Given that all
>> (?)  IETF GOST standards use this param set, why not provide test
>> vectors for it rather than the (otherwise unused) TestParamSet?
> 
> My understanding is that the drafts are an exact translation of the
> official standard,
Yes, they are.
> including the examples, as published in 1994. That kind of makes those examples
> reliable and official, but of course additional examples wouldn't hurt.
> 
> Also, there is an example of gost3411-94 digest with gost3410-2001
> signature in rfc4491.txt.
> The bad news is that only the source data and final result (signature
> value) are provided there,
> with no intermediate values.
It is not "bad news", it is "obvious thing" concerning the fact that the 
purpose of this publication is to provide for the reference the 
translation to English of Russian GOST cryptography standards texts, so 
it can contain the standard texts only (no additions, no changes, no 
deletions).

The only thing we have done it that we consulted with the authors of the 
standards about proper English wording in some places where translation 
was not so obvious and demanded the deep knowlegde of the subject field.

dol <at> 

>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Basil Dolmatov | 5 Aug 2009 13:20
Picon
Favicon

[Fwd: I-D Action:draft-dolmatov-cryptocom-gost2814789-01.txt]

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 <at>
Picon Favicon
From: 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 <at> <Internet-Drafts <at> ietf.org>
Subject: I-D Action:draft-dolmatov-cryptocom-gost2814789-01.txt
Date: 2009-08-05 10:45:01 GMT
(Continue reading)

Permalink | Reply | 1 comment |
headers
Russ Housley | 5 Aug 2009 16:35

draft-dolmatov-cryptocom-gost34102001

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
Permalink | Reply | 2 comments |
headers
Basil Dolmatov | 5 Aug 2009 17:20
Picon
Favicon

Re: draft-dolmatov-cryptocom-gost34102001

Fixed...

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

Thanks!

dol <at> 

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
> 
_______________________________________________
Cfrg mailing list
Cfrg <at> irtf.org
http://www.irtf.org/mailman/listinfo/cfrg
(Continue reading)

Permalink | Reply | 0 comments |
headers
Aaron Falk | 14 Aug 2009 19:31
Picon

[Fwd: Copyrights and the IRTF and Independent Stream]

Forwarding to all active IRTF RG mail lists because this issue affects
the publication rights for IDs and RFCs developed within the IRTF. 
Information about IRTF RFCs can be found in
http://tools.ietf.org/html/draft-irtf-rfcs-03.  Please direct comments
to the RFC-interest list (coordinates below).

--aaron
  IRTF Chair

-------- Original Message --------
Subject: 	[rfc-i] Copyrights and the IRTF and Independent Stream
Date: 	Thu, 13 Aug 2009 18:59:42 +0200
From: 	Olaf Kolkman <olaf <at> NLnetLabs.nl>
To: 	RFC Interest <rfc-interest <at> rfc-editor.org>

Dear Colleagues,

This mail is about rights in RFCs and Internet drafts. The topic draws
context, and uses terminology from:
RFC 4844: The RFC Series and RFC Editor
RFC 4846: Independent Submissions to the RFC Editor
RFC 5378: Rights Contributors Provide to the IETF Trust
RFC 5377: Advice to the Trustees of the IETF Trust on Rights to Be
Granted in IETF Documents

First some administrational notes.

This mail serves as setting a baseline for a public discussion and is
based on a few (virtual and real-life) hallway discussions. The goal
of this discussion is to make sure all issues are brought to the table
(Continue reading)

Permalink | Reply | 0 comments |

Gmane