<?xml version="1.0" encoding="US-ASCII"?>
<!-- -*- xml -*- -->
<!-- This template is for creating an Internet Draft using xml2rfc,
  which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
  <!-- One method to get references from the online citation libraries.
  There has to be one entity for each item to be referenced.
  An alternate method (rfc include) is described in the references. -->

<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC3552 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552.xml">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC4312 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4312.xml">
<!ENTITY RFC4132 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4132.xml">
<!ENTITY RFC3657 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3657.xml">
<!ENTITY RFC4301 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4301.xml">
<!ENTITY RFC4302 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4302.xml">
<!ENTITY RFC4306 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4306.xml">
<!ENTITY RFC2411 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2411.xml">
<!ENTITY RFC4051 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4051.xml">
<!ENTITY RFC4086 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4086.xml">
<!ENTITY RFC3713 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3713.xml">
<!ENTITY RFC4494 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4494.xml">
<!ENTITY RFC4615 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4615.xml">
<!ENTITY RFC4303 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4303.xml">
<!ENTITY RFC2409 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2409.xml">
<!ENTITY RFC4346 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4346.xml">
<!ENTITY RFC5246 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5246.xml">
<!ENTITY RFC4492 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4492.xml">
<!ENTITY RFC5288 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5288.xml">
<!ENTITY RFC5289 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5289.xml">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
  please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
  (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
  (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-kanno-tls-camellia-ecc-sha-00" ipr="trust200811">
  <!-- category values: std, bcp, info, exp, and historic
    ipr values: full3667, noModification3667, noDerivatives3667
    you can add the attributes updates="NNNN" and obsoletes="NNNN"
    they will automatically be output with "(if approved)" -->

  <front>
    <!-- The abbreviated title is used in the page header - it is only necessary if the
      full title is longer than 39 characters -->

    <title abbrev="Addition of Camellia ECC Cipher Suites"> Addition of Camellia Elliptic Curve Cipher Suites with SHA-1 and SHA-2</title>

    <author initials="S." surname="Kanno"
      fullname="Satoru Kanno">
      <organization>
	NTT Software Corporation
      </organization>
      <address>
	<phone>+81-45-212-7577</phone>
	<facsimile>+81-45-212-9800</facsimile>
	<email>kanno-s@po.ntts.co.jp</email>
      </address>
    </author>

    <author initials="M." surname="Kanda"
      fullname="Masayuki Kanda">
      <organization>
	Nippon Telegraph and Telephone Corporation
      </organization>
      <address>
	<phone>+81-422-59-3456</phone>
	<facsimile>+81-422-59-4015 </facsimile>
	<email>kanda.masayuki@lab.ntt.co.jp</email>
      </address>
    </author>
    
    
    <date />

    <!-- If the month and year are both specified and are the current ones, xml2rfc will fill
      in the current day for you. If only the current year is specified, xml2rfc will fill
      in the current day and month for you. If the year is not the current one, it is
      necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the
      purpose of calculating the expiry date).  With drafts it is normally sufficient to
      specify just the year. -->

    <!-- Meta-data Declarations -->

    <area>Security</area>

    <workgroup>Network Working Group</workgroup>

    <!-- WG name at the upperleft corner of the doc,
      IETF is fine for individual submissions.
      If this element is not present, the default is "Network Working Group",
      which is used by the RFC Editor as a nod to the history of the IETF. -->

    <keyword>Block Cipher</keyword>
    <keyword>Security</keyword>
    <keyword>Camellia</keyword>
    <keyword>ECC</keyword>
    <keyword>TLS</keyword>
    <keyword>CBC</keyword>
    <keyword>SHA2</keyword>
    <keyword>SHA</keyword>

    <!-- Keywords will be incorporated into HTML output
      files in a meta tag but they have no effect on text or nroff
      output. If you submit your draft to the RFC Editor, the
      keywords will be used for the search engine. -->

    <abstract>
      <t> 
      This document specifies a set of elliptic curve cipher suites
      for the Transport Security Layer (TLS) protocol to support 
      the Camellia encryption algorithm as a block cipher. 
      This document describes sixteen new cipher suites for TLS that
      specify HMAC-SHA1 and HMAC-SHA2.
      </t>
    </abstract>
  </front>

  <middle>
<section anchor="intro" title="Introduction">
		<t>
			This document specifies a set of elliptic curve cipher suites
			for the Transport Security Layer (TLS) protocol to support 
			the Camellia encryption algorithm as a block cipher. 
			This document describes sixteen new cipher suites for TLS that
			specify HMAC-SHA1 and HMAC-SHA2.
		</t>
		<t>
			The algorithm specification and object identifiers are described in
			<xref target="RFC3713" />.
		</t>

    <section title="Terminology">
	<t>
	 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
     document are to be interpreted as described in <xref target="RFC2119" />.
	</t>
    </section>
</section>

<section title="Cipher Suites" >
	<t>
		This document defines sixteen new cipher suites to be added to TLS.
		All use Elliptic Curve Cryptography for key exchange and digital
		signature, as defined in <xref target="RFC4492" />.
	</t>
	<t>
		The sixteen cipher suites use Camellia <xref target="RFC3713" /> in Cipher
		Block Chaining (CBC) mode with HMAC-based MAC.
	</t>
	<t>
		The cipher suites defined here have the following identifiers:
	</t>
      
      <figure>
          <artwork align="left"><![CDATA[
     CipherSuite TLS_ECDH_ECDSA_WITH_CAMELLIA_128_CBC_SHA    = {TBD,TBD}
     CipherSuite TLS_ECDH_ECDSA_WITH_CAMELLIA_256_CBC_SHA    = {TBD,TBD}
     CipherSuite TLS_ECDHE_ECDSA_WITH_CAMELLIA_128_CBC_SHA   = {TBD,TBD}
     CipherSuite TLS_ECDHE_ECDSA_WITH_CAMELLIA_256_CBC_SHA   = {TBD,TBD}
     CipherSuite TLS_ECDH_RSA_WITH_CAMELLIA_128_CBC_SHA      = {TBD,TBD}
     CipherSuite TLS_ECDH_RSA_WITH_CAMELLIA_256_CBC_SHA      = {TBD,TBD}
     CipherSuite TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA     = {TBD,TBD}
     CipherSuite TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA     = {TBD,TBD}
     
     CipherSuite TLS_ECDHE_ECDSA_WITH_CAMELLIA_128_CBC_SHA256  = {TBD,TBD};
     CipherSuite TLS_ECDHE_ECDSA_WITH_CAMELLIA_256_CBC_SHA384  = {TBD,TBD};
     CipherSuite TLS_ECDH_ECDSA_WITH_CAMELLIA_128_CBC_SHA256   = {TBD,TBD};
     CipherSuite TLS_ECDH_ECDSA_WITH_CAMELLIA_256_CBC_SHA384   = {TBD,TBD};
     CipherSuite TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256    = {TBD,TBD};
     CipherSuite TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384    = {TBD,TBD};
     CipherSuite TLS_ECDH_RSA_WITH_CAMELLIA_128_CBC_SHA256     = {TBD,TBD};
     CipherSuite TLS_ECDH_RSA_WITH_CAMELLIA_256_CBC_SHA384     = {TBD,TBD};
            ]]></artwork>
	</figure>
    </section>


    <section anchor="IANA" title="IANA Considerations">
	<t>
		IANA is requested to allocate the following numbers 
		in the TLS Cipher Suite Registry:
	</t>
	<figure>
	<artwork align="left"><![CDATA[
     CipherSuite TLS_ECDH_ECDSA_WITH_CAMELLIA_128_CBC_SHA    = {TBD,TBD}
     CipherSuite TLS_ECDH_ECDSA_WITH_CAMELLIA_256_CBC_SHA    = {TBD,TBD}
     CipherSuite TLS_ECDHE_ECDSA_WITH_CAMELLIA_128_CBC_SHA   = {TBD,TBD}
     CipherSuite TLS_ECDHE_ECDSA_WITH_CAMELLIA_256_CBC_SHA   = {TBD,TBD}
     CipherSuite TLS_ECDH_RSA_WITH_CAMELLIA_128_CBC_SHA      = {TBD,TBD}
     CipherSuite TLS_ECDH_RSA_WITH_CAMELLIA_256_CBC_SHA      = {TBD,TBD}
     CipherSuite TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA     = {TBD,TBD}
     CipherSuite TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA     = {TBD,TBD}
     
     CipherSuite TLS_ECDHE_ECDSA_WITH_CAMELLIA_128_CBC_SHA256  = {TBD,TBD};
     CipherSuite TLS_ECDHE_ECDSA_WITH_CAMELLIA_256_CBC_SHA384  = {TBD,TBD};
     CipherSuite TLS_ECDH_ECDSA_WITH_CAMELLIA_128_CBC_SHA256   = {TBD,TBD};
     CipherSuite TLS_ECDH_ECDSA_WITH_CAMELLIA_256_CBC_SHA384   = {TBD,TBD};
     CipherSuite TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256    = {TBD,TBD};
     CipherSuite TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384    = {TBD,TBD};
     CipherSuite TLS_ECDH_RSA_WITH_CAMELLIA_128_CBC_SHA256     = {TBD,TBD};
     CipherSuite TLS_ECDH_RSA_WITH_CAMELLIA_256_CBC_SHA384     = {TBD,TBD};
		]]></artwork>
	</figure>
</section>

	<section anchor="Security" title="Security Considerations">
      <t>
		At the time of writing this document, there are no known weak keys
		for Camellia.
      </t>
      <t>
      	The security considerations in RFC 5289 <xref target="RFC5289" /> apply to this document as well. 
      </t>
	</section>
         
  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
    <!-- References split into informative and normative -->

    <!-- There are 2 ways to insert reference entries from the citation libraries:
      1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
      2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
      (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

      Both are cited textually in the same manner: by using xref elements.
      If you use the PI option, xml2rfc will, by default, try to find included files in the same
      directory as the including file. You can also define the XML_LIBRARY environment variable
      with a value containing a set of directories to search.  These can be either in the local
      filing system or remote ones accessed by http (http://domain/dir/... ).-->

<references title="Normative References">
      &RFC2119;
      &RFC3713;
      &RFC4492;
      &RFC5289;
</references>

<!--
<references title="Informative References">
</references>
-->
    <!-- Change Log

      v00 2006-03-15  EBD   Initial version

      v01 2006-04-03  EBD   Moved PI location back to position 1 -
      v3.1 of XMLmind is better with them at this location.
      v02 2007-03-07  AH    removed extraneous nested_list attribute,
      other minor corrections
      v03 2007-03-09  EBD   Added comments on null IANA sections and fixed heading capitalization.
      Modified comments around figure to reflect non-implementation of
      figure indent control.  Put in reference using anchor="DOMINATION".
      Fixed up the date specification comments to reflect current truth.
      v04 2007-03-09 AH     Major changes: shortened discussion of PIs,
      added discussion of rfc include.
      v05 2007-03-10 EBD    Added preamble to C program example to tell about ABNF and alternative
      images. Removed meta-characters from comments (causes problems).  -->
  </back>
</rfc>
