- From: Ryan Sleevi <sleevi@google.com>
- Date: Mon, 19 Oct 2015 23:33:35 -0700
- To: Anirban Basu <xon-basu@kddi.com>
- Cc: public-webcrypto@w3.org
- Message-ID: <CACvaWvaa_bKcPi+Q0CKX0-_AD05cE8jwrN+FA3m2wCGX8+kYZw@mail.gmail.com>
On Oct 19, 2015 10:51 PM, "Anirban Basu" <xon-basu@kddi.com> wrote: > > KCipher-2 is a fast and lightweight stream cipher developed within the > KDDI R&D Laboratories. It has been standardised by the ISO/IEC and > recommended by the Japanese government (see links at > http://anirbanbasu.github.io/w3c-web-crypto/). We wish to standardise > KCipher-2 as a cipher available within the Web Crypto API. > Do you expect any user agent interest? That is more or less a prerequisite for standardization. > > Please note that I am new to writing the algorithm specification in the > W3C recommended structure, so it would be great if you could point out > any oversights of non-conformance. I am also aware of the 78 warning > messages that Respec raises on the Working Draft document. My > understanding is that if/when accepted, the main content of this draft > will be included within the Web Crypto API specification as a new > algorithm. Thus, the missing references will be automatically fixed > then. Please do correct me if I am wrong, and if this KCipher-2 draft is > expected to be a standalone document on its own. The KCipher-2 draft would be a document of its own.
Received on Tuesday, 20 October 2015 06:34:09 UTC