From nobody Mon Aug 6 08:53:20 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EFCB130EF6 for ; Mon, 6 Aug 2018 08:53:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t8tt13zs0SSq for ; Mon, 6 Aug 2018 08:53:06 -0700 (PDT) Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 201A1130ED6 for ; Mon, 6 Aug 2018 08:53:06 -0700 (PDT) Received: by mail-lj1-x229.google.com with SMTP id 203-v6so10965287ljj.13 for ; Mon, 06 Aug 2018 08:53:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=MQfQj8nqPEhVQo+FFL0ceE85u7LLzhwKaoN+nlMIWcg=; b=lsUmr7vua9q7GehMA0GkyKP7UUOuqdyF3JpXgD6h7vzrCDvOpfolK8WCZ0FvtXicnt oHig9eviK/nwz6yAMiw1pBeZuAzSxmBPgGtFYlIbq6zlazCIOcaV/hCzfvyu8n4r5jC3 tCGLgXUTaXIlqvlf2BWIzP932wnIOTDwFn4jtv0gPKUav/o0lwZ0reE/r3rdUPFMQfY3 vn4PF8a2JDd20icWXVGHm8PezKgq0Al6WrRehBH2nZTNT4PPNxlko4D2AhlguV9MYcR6 aDPPCe4kPnCc3SCUhiFmo9NclomXjrleWjg+FLe+3EwAbgZY1ditsujob7+Xcebyfawi xXBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=MQfQj8nqPEhVQo+FFL0ceE85u7LLzhwKaoN+nlMIWcg=; b=SrSyatGhbggz43tjAfSKRJn9fQCPcUDLKsFZfi+SwiMHyyXD0JzcoiySM5W99/T826 wGGcWSkD3UqOnfXA4oLG/E/NU5MAULqnun832pfm7ZoefmwwCroBBvCUNIVdoLal6JTG pm25ip+WmXnooHvJk8UWTm1shYaconCF6IYoibELblsGJh74ML4EITa9ut6gPqr6nDgh dHgSqLou7rc3cAnB94qZ6Lblj3knI26xJblrzHRX3C7rRb5dVgc9jD1GuUlgTOOlEaen YmGMVRDa7edhJT33sX/nXH4F7L8SPZ3wzRIDiuavZ0hZtCEa2Lllkvj7gMEfnmeQezfR pC+A== X-Gm-Message-State: AOUpUlEjrR/dvuG6u6uy9bO9S+4GRkDzsv6ph3/qVjvzdqf6qX5l/6EJ nymqsljDeuFm+vM5Tp1QnVIG1OInBYp/AqU7k9I= X-Google-Smtp-Source: AAOMgpetJB2sm+OrN3F8ZUQZrA/uEjRVludpEPAQqjjVhzehjCDnmzrYcXHKRyY0q8x1TL2FFj6GlRGmlJuP1572aS8= X-Received: by 2002:a2e:1d50:: with SMTP id d77-v6mr12945273ljd.104.1533570784297; Mon, 06 Aug 2018 08:53:04 -0700 (PDT) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 2002:a2e:5295:0:0:0:0:0 with HTTP; Mon, 6 Aug 2018 08:53:03 -0700 (PDT) In-Reply-To: <83201.1530913429@eng-mail01.juniper.net> References: <153052153971.27909.10469976224660738011@ietfa.amsl.com> <83201.1530913429@eng-mail01.juniper.net> From: Daniel Migault Date: Mon, 6 Aug 2018 11:53:03 -0400 X-Google-Sender-Auth: 2jo9YUg9ks5974Hnv6KYbng-3NA Message-ID: To: "Mark D. Baushke" Cc: curdle Content-Type: multipart/alternative; boundary="000000000000d605b40572c645b7" Archived-At: Subject: Re: [Curdle] I-D Action: draft-ietf-curdle-ssh-ed25519-ed448-01.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Aug 2018 15:53:19 -0000 --000000000000d605b40572c645b7 Content-Type: text/plain; charset="UTF-8" Hi, In addition to Mark's comment, please find my review of the document. Comments are indicative, so you may find better ways to address them than what I suggest. Please update the next version by the end of August. Yours, Daniel Ed25519 and Ed 448 public key algorithms for the Secure Shell (SSH) protocol draft-ietf-curdle-ssh-ed25519-ed448-01 [...] 1. Introduction Secure Shell (SSH) [RFC4251] is a secure remote-login protocol. It provides for an extensible variety of public key algorithms for identifying servers and users to one another. Ed25519 [RFC8032] is a digital signature system. OpenSSH 6.5 [OpenSSH-6.5] introduced support for using Ed25519 for server and user authentication. Compatible support for Ed25519 has since been added to other SSH implementations. Ed448 [RFC8032] is another digital signature system. I am reading the sentence "Compatible support" as variants, and a such the current document may describe on eor the other variant. I am not sure the Ed448 sentence adds much information. I would rather propose the following wording: OLD: OpenSSH 6.5 [OpenSSH-6.5] introduced support for using Ed25519 for server and user authentication. Compatible support for Ed25519 has since been added to other SSH implementations. Ed448 [RFC8032] is another digital signature system. NEW: OpenSSH 6.5 [OpenSSH-6.5] introduced support for using Ed25519 for server and user authentication and was then followed by other implementations. This document describes the method implemented by OpenSSH and others, and formalizes its use of the name "ssh-ed25519". Additionally, it also describes the use of Ed448 and formalizes its use of the name "ssh-ed448". [TO BE REMOVED: Please send comments on this draft to curdle@ietf.org.] 2. Conventions Used in This Document 3. Public Key Algorithm 4. Public Key Format 5. Signature Algorithm 6. Signature Format 7. Verification Algorithm 8. SSHFP DNS resource records The main purpose of this section is the IANA registration for the "SSHFP RR Types for public key algorithms" registry. I would thus start the section as follows: Usage and generation of SSHFP DNS resource record is described in RFC 4255. The generation of SSHFP resource records for "ssh-ed25519" keys is described in [RFC7479]. This section illustrates the generation of SSHFP resource records for "ssh-ed448" keys and the document specifies the corresponding Ed448 code point to the "SSHFP RR Types for public key algorithms" IANA registry. The generation of SSHFP resource records for "ssh-ed25519" keys is described in [RFC7479]. The generation of SSHFP resource records for "ssh-ed448" keys is described as follows. Harris & Velvindron Expires January 3, 2019 [Page 3] Internet-Draft Ed25519 for SSH July 2018 the SSHFP Resource Record for the Ed448 public key with SHA-256 fingerprint would be example be: ssh.hackers.mu IN SSHFP 5 2 ( a87f1b687ac0e57d2a081a2f2826723 34d90ed316d2b818ca9580ea384d924 01 ) probably having the DNS in a figure would ease the reading. I believe it would also be nice to have the key used to generate the example. 5 is 'To be defined' TBD Maybe it would be good to also indicate that 2 indicates the SHA2 as a complete example. (rfc6594). 9. IANA Considerations This document augments the Public Key Algorithm Names in [RFC4250], Section 4.6.2 [RFC4250]. IANA is requested to add to the Public Key Algorithm Names registry [IANA-PKA] with the following entry: It is also better to indicate the type of review. In this case the addition of the code point requires an IETF review. Public Key Algorithm Name Reference ------------------------- ---------- ssh-ed25519 This Draft ssh-ed448 This Draft IANA must add the following entry to the "SSHFP RR Types for public key algorithms" registry: is requested may be better ;-) The registry got a Public Key Format column. This should also be mentioned in this section. +--------+-------------+------------+ | Value | Description | Reference | +--------+-------------+------------+ | 5 | Ed448 | [this-draft] | +--------+-------------+------------+ [TO BE REMOVED: This registration should take place at the following location: ] Maybe that would be good to have the URL as an informational reference. The reference is for the previous registry ( i.e. Public Key Algorithm name reference. The latest is https://www.iana.org/assignments/dns-sshfp-rr-parameters/dns-sshfp-rr-parameters.xhtml The review is also an IETF review. Though 5 is the most likely value. It might be better to have it as TBD and then suggest TBD to be 5 to the IANA. 10. Security Considerations The security considerations in [RFC4251], Section 9 [RFC4251] apply to all SSH implementations, including those using Ed25519 and Ed448. RFC6469 may also be references here. The security considerations in [RFC8032], Section 8 [RFC8032] apply to all uses of Ed25519 and Ed448 including those in SSH. On Fri, Jul 6, 2018 at 5:43 PM, Mark D. Baushke wrote: > The https://tools.ietf.org/html/draft-ietf-curdle-ssh-ed25519-ed448-01 > looks better than the -00 revision. > > A very minor correction should be the table in section 9 which adds the > SSHFP RR Type value 5 for "Ed448" for SSHFP RR Types for public key > algorithms. > > I believe there should be an informative reference to [IANA-SSHFP] > https://www.iana.org/assignments/dns-sshfp-rr-parameters/dns-sshfp-rr- > parameters.xhtml#dns-sshfp-rr-parameters-1 > > which is the IANA.ORG parameter table that should be updated. > > Thank you, > -- Mark > > _______________________________________________ > Curdle mailing list > Curdle@ietf.org > https://www.ietf.org/mailman/listinfo/curdle > --000000000000d605b40572c645b7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

In addition to Mark= 's comment, please find my review of the document. Comments are indicat= ive, so you may find better ways to address them than what I suggest. Pleas= e update the next version by the end of August.

Yours,
Daniel





=C2=A0 Ed25519 and Ed 448 public key algorithms for the Secure Shell = (SSH)
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 protocol
=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 draft-ietf-curdle-ssh-ed25519-ed448-01

[...]
1.=C2=A0 Intr= oduction

=C2=A0=C2=A0 Secure Shell (SSH) [RFC4251] is a secure remot= e-login protocol.=C2=A0 It
=C2=A0=C2=A0 provides for an extensible varie= ty of public key algorithms for
=C2=A0=C2=A0 identifying servers and use= rs to one another.=C2=A0 Ed25519 [RFC8032] is a
=C2=A0=C2=A0 digital sig= nature system.=C2=A0 OpenSSH 6.5 [OpenSSH-6.5] introduced
=C2=A0=C2=A0 s= upport for using Ed25519 for server and user authentication.
=C2=A0=C2= =A0 Compatible support for Ed25519 has since been added to other SSH
=C2= =A0=C2=A0 implementations. Ed448 [RFC8032] is another digital signature
= =C2=A0=C2=A0 system.

<mglt>
I am rea= ding the sentence "Compatible support" as variants, and a such th= e current document may describe on eor the other variant. I am not sure the= Ed448 sentence adds much information. I would rather propose the following= wording:

OLD:
=C2=A0OpenSSH 6.5 [OpenSSH-6.5] introduced
=C2= =A0=C2=A0 support for using Ed25519 for server and user authentication.
= =C2=A0=C2=A0 Compatible support for Ed25519 has since been added to other S= SH
=C2=A0=C2=A0 implementations. Ed448 [RFC8032] is another digital sign= ature
=C2=A0=C2=A0 system.

NEW:

=C2=A0OpenSSH 6.5 [OpenSSH= -6.5] introduced
=C2=A0=C2=A0 support for using Ed25519 for server and u= ser authentication and was then followed by other implementations.
<= /mglt>

=C2=A0=C2=A0 This document describes the method implemente= d by OpenSSH and others,
=C2=A0=C2=A0 and formalizes its use of the name= "ssh-ed25519".=C2=A0 Additionally, it
=C2=A0=C2=A0 also descr= ibes the use of Ed448 and formalizes its use of the name
=C2=A0=C2=A0 &q= uot;ssh-ed448".

=C2=A0=C2=A0 [TO BE REMOVED: Please send commen= ts on this draft to
=C2=A0=C2=A0 curd= le@ietf.org.]

2.=C2=A0 Conventions Used in This Document
3.= =C2=A0 Public Key Algorithm
4.=C2=A0 Public Key Format
5.=C2=A0 Signa= ture Algorithm
6.=C2=A0 Signature Format
7.=C2=A0 Verification Algori= thm
8.=C2=A0 SSHFP DNS resource records

<mglt>
The main = purpose of this section is the IANA registration for the "SSHFP RR Typ= es for public
=C2=A0=C2=A0 key algorithms" registry. I would thus s= tart the section as follows:

Usage and generation of SSHFP DNS resou= rce record is described in RFC 4255. The generation of SSHFP resource recor= ds for "ssh-ed25519" keys is described in [RFC7479]. This section= illustrates the generation of SSHFP resource records for "ssh-ed448&q= uot; keys and the document specifies the corresponding Ed448 code point to = the "SSHFP RR Types for public key algorithms" IANA registry. </mglt>

=C2=A0=C2=A0 The generation of SSHFP resource records= for "ssh-ed25519" keys is
=C2=A0=C2=A0 described in [RFC7479]= .

=C2=A0=C2=A0 The generation of SSHFP resource records for "ss= h-ed448" keys is
=C2=A0=C2=A0 described as follows.



=

Harris & Velvindron=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Expires Janua= ry 3, 2019=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 [Page 3]
=0C
Internet-Draft=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Ed= 25519 for SSH=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 July 2018


=C2= =A0=C2=A0 the SSHFP Resource Record for the Ed448 public key with SHA-256=C2=A0=C2=A0 fingerprint would be example be: ssh.hackers.mu IN SSHFP 5 2 (
=C2=A0=C2=A0 a87f1b687ac0e57d2a= 081a2f2826723 34d90ed316d2b818ca9580ea384d924 01 )

<mglt>
p= robably having the DNS in a figure would ease the reading.
I believe it= would also be nice to have the key used to generate the example.
5 is = 'To be defined' TBD
Maybe it would be good to also indicate that= 2 indicates the SHA2 as a complete example. (rfc6594).
</mglt>
9.=C2=A0 IANA Considerations

=C2=A0=C2=A0 This document augment= s the Public Key Algorithm Names in [RFC4250],
=C2=A0=C2=A0 Section 4.6.= 2 [RFC4250].


=C2=A0=C2=A0 IANA is requested to add to the Public= Key Algorithm Names registry
=C2=A0=C2=A0 [IANA-PKA] with the following= entry:

<mglt>
It is also better to indicate the type of re= view. In this case the addition of the code point requires an IETF review.<= br></mglt>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Public Key Algorithm= Name Reference
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 --------------------= ----- ----------
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ssh-ed25519=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= This Draft
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ssh-ed448=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 This Draft

=C2=A0=C2=A0 IANA must add the following entry to = the "SSHFP RR Types for public
=C2=A0=C2=A0 key algorithms" re= gistry:
<mglt>
is requested may be better ;-)
The registry g= ot a Public Key Format column. This should also be mentioned in this sectio= n.=C2=A0
</mglt>

=C2=A0=C2=A0 +--------+-------------+----= --------+

=C2=A0=C2=A0 | Value | Description | Reference |

= =C2=A0=C2=A0 +--------+-------------+------------+

=C2=A0=C2=A0 | 5 = | Ed448 | [this-draft]=C2=A0 |

=C2=A0=C2=A0 +--------+-------------+= ------------+

=C2=A0=C2=A0 [TO BE REMOVED: This registration should = take place at the following
=C2=A0=C2=A0 location: <http://www.iana.org/assignme= nts/ssh-parameters/ssh-
=C2=A0=C2=A0 parameters.xhtml#ssh-parameters= -19>]

<mglt>
Maybe that would be good to have the URL a= s an informational reference. The reference is for the previous registry ( = i.e. Public Key Algorithm name reference.

The latest is https://www.iana.org/assignments/dns-sshfp-rr-parameters/dns-ss= hfp-rr-parameters.xhtml

The review is also an IETF review.
Though 5 is the most likely value. It might be better to have it as TBD a= nd then suggest TBD to be 5 to the IANA.=C2=A0=C2=A0
</mglt>
= =C2=A0
10.=C2=A0 Security Considerations

=C2=A0=C2=A0 The securit= y considerations in [RFC4251], Section 9 [RFC4251] apply
=C2=A0=C2=A0 to= all SSH implementations, including those using Ed25519 and Ed448.

<mglt>
RFC6469 may also be references = here.
</mglt>

=C2=A0=C2=A0 Th= e security considerations in [RFC8032], Section 8 [RFC8032] apply
=C2=A0= =C2=A0 to all uses of Ed25519 and Ed448 including those in SSH.


=

On Fr= i, Jul 6, 2018 at 5:43 PM, Mark D. Baushke <mdb@juniper.net> w= rote:
The https://tools.ietf.org/html/draft-ietf-curdle-ssh-ed25519-= ed448-01
looks better than the -00 revision.

A very minor correction should be the table in section 9 which adds the
SSHFP RR Type value 5 for "Ed448" for SSHFP RR Types for public k= ey
algorithms.

I believe there should be an informative reference to [IANA-SSHFP]
https://www.iana.org/assignments/dns-sshfp-rr-paramet= ers/dns-sshfp-rr-parameters.xhtml#dns-sshfp-rr-parameters-1
which is the IANA.ORG parameter table that should be updated.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Thank you,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -- Mark

_______________________________________________
Curdle mailing list
Curdle@ietf.org
https://www.ietf.org/mailman/listinfo/curdle

--000000000000d605b40572c645b7-- From nobody Mon Aug 6 22:38:44 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90996130E09; Mon, 6 Aug 2018 22:38:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pgv-lE9lztI0; Mon, 6 Aug 2018 22:38:41 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9CD3130DD8; Mon, 6 Aug 2018 22:38:41 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 8BFBEB817BB; Mon, 6 Aug 2018 22:38:38 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, curdle@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20180807053838.8BFBEB817BB@rfc-editor.org> Date: Mon, 6 Aug 2018 22:38:38 -0700 (PDT) Archived-At: Subject: [Curdle] =?utf-8?q?RFC_8410_on_Algorithm_Identifiers_for_Ed25519?= =?utf-8?q?=2C_Ed448=2C_X25519=2C_and_X448_for_Use_in_the_Internet_X=2E509?= =?utf-8?q?_Public_Key_Infrastructure?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Aug 2018 05:38:43 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8410 Title: Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure Author: S. Josefsson, J. Schaad Status: Standards Track Stream: IETF Date: August 2018 Mailbox: simon@josefsson.org, ietf@augustcellars.com Pages: 20 Characters: 34896 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-curdle-pkix-10.txt URL: https://www.rfc-editor.org/info/rfc8410 DOI: 10.17487/RFC8410 This document specifies algorithm identifiers and ASN.1 encoding formats for elliptic curve constructs using the curve25519 and curve448 curves. The signature algorithms covered are Ed25519 and Ed448. The key agreement algorithms covered are X25519 and X448. The encoding for public key, private key, and Edwards-curve Digital Signature Algorithm (EdDSA) structures is provided. This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Mon Aug 6 22:38:58 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0F9F130F19; Mon, 6 Aug 2018 22:38:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Te5EUTYr8GAA; Mon, 6 Aug 2018 22:38:45 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 904FB130E09; Mon, 6 Aug 2018 22:38:45 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 6B391B817C1; Mon, 6 Aug 2018 22:38:42 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, curdle@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20180807053842.6B391B817C1@rfc-editor.org> Date: Mon, 6 Aug 2018 22:38:42 -0700 (PDT) Archived-At: Subject: [Curdle] =?utf-8?q?RFC_8411_on_IANA_Registration_for_the_Cryptog?= =?utf-8?q?raphic_Algorithm_Object_Identifier_Range?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Aug 2018 05:38:54 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8411 Title: IANA Registration for the Cryptographic Algorithm Object Identifier Range Author: J. Schaad, R. Andrews Status: Informational Stream: IETF Date: August 2018 Mailbox: ietf@augustcellars.com, rick.andrews@digicert.com Pages: 5 Characters: 8985 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-schaad-curdle-oid-registry-03.txt URL: https://www.rfc-editor.org/info/rfc8411 DOI: 10.17487/RFC8411 When the Curdle Security Working Group was chartered, a range of object identifiers was donated by DigiCert, Inc. for the purpose of registering the Edwards Elliptic Curve key agreement and signature algorithms. This donated set of OIDs allowed for shorter values than would be possible using the existing S/MIME or PKIX arcs. This document describes the donated range and the identifiers that were assigned from that range, transfers control of that range to IANA, and establishes IANA allocation policies for any future assignments within that range. This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Mon Aug 6 22:39:12 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF501130F69; Mon, 6 Aug 2018 22:38:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tvCZYhWAHgPp; Mon, 6 Aug 2018 22:38:50 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB882130E87; Mon, 6 Aug 2018 22:38:50 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 836FCB817CF; Mon, 6 Aug 2018 22:38:47 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, curdle@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20180807053847.836FCB817CF@rfc-editor.org> Date: Mon, 6 Aug 2018 22:38:47 -0700 (PDT) Archived-At: Subject: [Curdle] =?utf-8?q?RFC_8418_on_Use_of_the_Elliptic_Curve_Diffie-?= =?utf-8?q?Hellman_Key_Agreement_Algorithm_with_X25519_and_X448_in_the_Cry?= =?utf-8?q?ptographic_Message_Syntax_=28CMS=29?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Aug 2018 05:39:00 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8418 Title: Use of the Elliptic Curve Diffie-Hellman Key Agreement Algorithm with X25519 and X448 in the Cryptographic Message Syntax (CMS) Author: R. Housley Status: Standards Track Stream: IETF Date: August 2018 Mailbox: housley@vigilsec.com Pages: 18 Characters: 36498 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-curdle-cms-ecdh-new-curves-10.txt URL: https://www.rfc-editor.org/info/rfc8418 DOI: 10.17487/RFC8418 This document describes the conventions for using the Elliptic Curve Diffie-Hellman (ECDH) key agreement algorithm with curve25519 and curve448 in the Cryptographic Message Syntax (CMS). This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Mon Aug 6 22:39:57 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 550B6130F79; Mon, 6 Aug 2018 22:39:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UE2aAc6QsvR6; Mon, 6 Aug 2018 22:39:39 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DEA2130F8B; Mon, 6 Aug 2018 22:39:38 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 61311B817C0; Mon, 6 Aug 2018 22:39:35 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, curdle@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20180807053935.61311B817C0@rfc-editor.org> Date: Mon, 6 Aug 2018 22:39:35 -0700 (PDT) Archived-At: Subject: [Curdle] =?utf-8?q?RFC_8419_on_Use_of_Edwards-Curve_Digital_Sign?= =?utf-8?q?ature_Algorithm_=28EdDSA=29_Signatures_in_the_Cryptographic_Mes?= =?utf-8?q?sage_Syntax_=28CMS=29?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Aug 2018 05:39:49 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8419 Title: Use of Edwards-Curve Digital Signature Algorithm (EdDSA) Signatures in the Cryptographic Message Syntax (CMS) Author: R. Housley Status: Standards Track Stream: IETF Date: August 2018 Mailbox: housley@vigilsec.com Pages: 9 Characters: 19080 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-curdle-cms-eddsa-signatures-08.txt URL: https://www.rfc-editor.org/info/rfc8419 DOI: 10.17487/RFC8419 This document specifies the conventions for using the Edwards-curve Digital Signature Algorithm (EdDSA) for curve25519 and curve448 in the Cryptographic Message Syntax (CMS). For each curve, EdDSA defines the PureEdDSA and HashEdDSA modes. However, the HashEdDSA mode is not used with the CMS. In addition, no context string is used with the CMS. This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Tue Aug 7 06:00:06 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC2EE128CFD for ; Tue, 7 Aug 2018 06:00:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSvcKLte3Ayr for ; Tue, 7 Aug 2018 06:00:01 -0700 (PDT) Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86313124BE5 for ; Tue, 7 Aug 2018 06:00:01 -0700 (PDT) Received: by mail-lf1-x12a.google.com with SMTP id a134-v6so11572837lfe.6 for ; Tue, 07 Aug 2018 06:00:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to:cc; bh=BhVzGMZI1UveRNsT5+gcXwwOlrM6XQN0SrAi2waROEg=; b=ryaViNDwW/qM9jhaykzS++MnaHJ4iAa2ig3ATuiXjBHCP9RpUdekqt1lnIVzg3JNlV iy8JCgQ8PuXtrN9oehNt4XgM6NFfmIV3DQ78/8kKcWBJymLnVhEKxSWMKpYWxZ3gXN7V LmMi6+Mgmz4BSH7IgLHtgvlqmGaVk+bPIlwMyWlgBxFcGi/tomT0tahEWwpqeZtZgDV/ AqQCJ1VgVVDjFJDm+z39qRINpJWEr388TCFcxKAc8AD7g/MYYDqysyXxi3fC955KiquD P+pV0X1ObV48rfWDStEtp5p0NFTm0JgENHDFbBWz+H8l3226FGiMpzNXQNOprhb3Q2D4 9l2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to:cc; bh=BhVzGMZI1UveRNsT5+gcXwwOlrM6XQN0SrAi2waROEg=; b=OYLe6jSQCzqVo8UYALJGNCbUuqL9/9pRgrz2uOmkyR2rBxo+1TrM2bN2hbuk7nPqLp KdrHAUd3ouGCh5KRh5Cd/vhOLK5uPWI5zpfjBGuN3ckaeVJPBccUlRhg0Wo1nmdD1u8e 0ZVHCdHAwygBnYK6UJ0avL4vri+ROk7xO+ANVJpjQwRPQbT13SPJXjQJaSv5317M9Bu0 /IHGbEW0hMbtpb/Rxg26hr5DNNoyc4ro25oHEIC3gADYANygBquRTE1g4ws4eTXIj6Vi +G2Lw0Wuuk7BlucV7bPzReQSg3OKRfcvzDIMiElrLcIsN89EFtyMq14WFqIOGDjKzDnm GCeQ== X-Gm-Message-State: AOUpUlGsIjumMOoQ5LajkaEpgho/B90Nf0cQaqdYBZNguerqoQDCVk90 fZB9/S8OPPXPuKEuZ/87Fli78RXdJ3nCiyvsVjoHZQ== X-Google-Smtp-Source: AAOMgpcwZ+I7q4RwVrAcGGbOQ69UbN7Q85E1YAVOydzxmLhl4sIITCd35kf89gHPZ6hnXN8BIxoB4AtvDEW00yyXAiM= X-Received: by 2002:a19:95c9:: with SMTP id x192-v6mr13921691lfd.37.1533646799562; Tue, 07 Aug 2018 05:59:59 -0700 (PDT) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 2002:a2e:5295:0:0:0:0:0 with HTTP; Tue, 7 Aug 2018 05:59:59 -0700 (PDT) From: Daniel Migault Date: Tue, 7 Aug 2018 08:59:59 -0400 X-Google-Sender-Auth: dUc8puRLA8YwwJxVvVGAwtH4dqc Message-ID: To: curdle Cc: RFC Editor , drafts-update-ref@iana.org Content-Type: multipart/alternative; boundary="000000000000b2f0360572d7f884" Archived-At: Subject: [Curdle] 8410, 8411, 8418, 8419 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Aug 2018 13:00:05 -0000 --000000000000b2f0360572d7f884 Content-Type: text/plain; charset="UTF-8" Thanks you to the co-authors, the RFC editor, the IANA as well as to the WG for supporting the publication of these documents! Yours, Daniel On Tue, Aug 7, 2018 at 1:38 AM, wrote: > A new Request for Comments is now available in online RFC libraries. > > > RFC 8410 > > Title: Algorithm Identifiers for Ed25519, Ed448, > X25519, and X448 for Use in > the Internet X.509 Public Key Infrastructure > Author: S. Josefsson, > J. Schaad > Status: Standards Track > Stream: IETF > Date: August 2018 > Mailbox: simon@josefsson.org, > ietf@augustcellars.com > Pages: 20 > Characters: 34896 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-curdle-pkix-10.txt > > URL: https://www.rfc-editor.org/info/rfc8410 > > DOI: 10.17487/RFC8410 > > This document specifies algorithm identifiers and ASN.1 encoding > formats for elliptic curve constructs using the curve25519 and > curve448 curves. The signature algorithms covered are Ed25519 and > Ed448. The key agreement algorithms covered are X25519 and X448. > The encoding for public key, private key, and Edwards-curve Digital > Signature Algorithm (EdDSA) structures is provided. > > This document is a product of the CURves, Deprecating and a Little more > Encryption Working Group of the IETF. > > This is now a Proposed Standard. > > STANDARDS TRACK: This document specifies an Internet Standards Track > protocol for the Internet community, and requests discussion and > suggestions > for improvements. Please refer to the current edition of the Official > Internet Protocol Standards (https://www.rfc-editor.org/standards) for > the > standardization state and status of this protocol. Distribution of this > memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > https://www.ietf.org/mailman/listinfo/ietf-announce > https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see https://www.rfc-editor.org/search > For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > _______________________________________________ > Curdle mailing list > Curdle@ietf.org > https://www.ietf.org/mailman/listinfo/curdle > --000000000000b2f0360572d7f884 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks you to the co-authors, the RFC editor, the IAN= A as well as to the WG for supporting the publication of these documents!

Yours,
Daniel

On Tue, Aug 7, 2018 at 1:38 AM= , <rfc-editor@rfc-editor.org> wrote:
A new Request for Comments is now available in online R= FC libraries.


=C2=A0 =C2=A0 =C2=A0 =C2=A0 RFC 8410

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title:=C2=A0 =C2=A0 =C2=A0 Algorithm Identifier= s for Ed25519, Ed448,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 X2551= 9, and X448 for Use in
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the I= nternet X.509 Public Key Infrastructure
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author:=C2=A0 =C2=A0 =C2=A0S. Josefsson,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 J. Sc= haad
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Status:=C2=A0 =C2=A0 =C2=A0Standards Track
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stream:=C2=A0 =C2=A0 =C2=A0IETF
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date:=C2=A0 =C2=A0 =C2=A0 =C2=A0August 2018
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Mailbox:=C2=A0 =C2=A0 simon@josefsson.org,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ietf@augustcellars.c= om
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages:=C2=A0 =C2=A0 =C2=A0 20
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Characters: 34896
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Updates/Obsoletes/SeeAlso:=C2=A0 =C2=A0None

=C2=A0 =C2=A0 =C2=A0 =C2=A0 I-D Tag:=C2=A0 =C2=A0 draft-ietf-curdle-pkix-10= .txt

=C2=A0 =C2=A0 =C2=A0 =C2=A0 URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 h= ttps://www.rfc-editor.org/info/rfc8410

=C2=A0 =C2=A0 =C2=A0 =C2=A0 DOI:=C2=A0 =C2=A0 =C2=A0 =C2=A0 10.17487/RFC841= 0

This document specifies algorithm identifiers and ASN.1 encoding
formats for elliptic curve constructs using the curve25519 and
curve448 curves.=C2=A0 The signature algorithms covered are Ed25519 and
Ed448.=C2=A0 The key agreement algorithms covered are X25519 and X448.
The encoding for public key, private key, and Edwards-curve Digital
Signature Algorithm (EdDSA) structures is provided.

This document is a product of the CURves, Deprecating and a Little more Enc= ryption Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestion= s
for improvements.=C2=A0 Please refer to the current edition of the Official=
Internet Protocol Standards (https://www.rfc-editor.org/sta= ndards) for the
standardization state and status of this protocol.=C2=A0 Distribution of th= is
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
=C2=A0 https://www.ietf.org/mailman/listinf= o/ietf-announce
=C2=A0 https://mailman.rfc-editor.org/m= ailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.=C2=A0 Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

_______________________________________________
Curdle mailing list
Curdle@ietf.org https://www.ietf.org/mailman/listinfo/curdle

--000000000000b2f0360572d7f884-- From nobody Thu Aug 9 04:06:37 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DA1D130E1C for ; Thu, 9 Aug 2018 04:06:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hackers-mu.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRIRNIEEgV_R for ; Thu, 9 Aug 2018 04:06:32 -0700 (PDT) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3D7A130E17 for ; Thu, 9 Aug 2018 04:06:32 -0700 (PDT) Received: by mail-oi0-x232.google.com with SMTP id j205-v6so9116746oib.4 for ; Thu, 09 Aug 2018 04:06:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hackers-mu.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iq5XMIH2OukQZnOGm9pv8++1AtyAJgRPd6yVXjubV5Q=; b=dhwrB+5eSEoPPFl5pL1LavcMLii8qjog7bQ4Xn0T7QpV3qcdB0beX23MnlgR1XnvPK peNUXG1JWLkevKuCm6Dsb2Q16wQcyjliG/K7PZqrOAYoZ9jSXIrVfVwBoUh42eWtMRdq 2cZXq8lxB7ek/UTb7qHCF7eP2qwUeCHXFp+mjR6bCLKLAperSCXQX4QE8qY7wh8wlOlh atZ6Z4CzhEDaKnq2RfdSQeOatDNdSqbKA4F6CnjOywciAFin5FICeiYbVuCiCsSH5xbV ZuNk72qY3zi2O6yb9EKLrtld2mS6cRWDuIfc3yjfJQicCgK8/em99uAKt+k5o0IZXJGB wx4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iq5XMIH2OukQZnOGm9pv8++1AtyAJgRPd6yVXjubV5Q=; b=pjl1BD8UGwndbxuJsqGYXxbgUYdF7BZRBiyL6BMfBI+IJ5Q+jDgGMDNDnWxhIPhbi/ RFCjukFrj2UkvCZ/pDc0TERam0Pn+gtENbom3P1d6T4gd5xcJXJR9rWuj7ArjFChp5QT 8l9bvCSoGiEEQwIUgByeuTqZaR8AO+K2ocTtDshuZL39rtPTKf0dJvphntMiXutmAXHB h0ktcu5HmRuWvkEvs0BPL9FTR5r9uPJx0LjtUF/iuYGXRVIphrSwUVW37Y6krEG7KPvh LLplwDmAG6VnbaRl1oYkKNP4D0nKbwGMaJAQCPGbp2QR35u08rDWkgh3QEqIpGfQji+m NlQA== X-Gm-Message-State: AOUpUlHlr4zKptEs2b11k9xvphLjE5kmsSbV5gkLhPREv8aXW6YQFBka vworVsy9Eo+dT89PvjbjKyqAoofOfyEAywaVeqo/Kw== X-Google-Smtp-Source: AA+uWPw7LZ18z2QtilyO4ijaOv2Qa12aAqL6QjKADDp7QlfQ460HVN0yEABrMCI7Bj4YbPYtnFP3043ePL7AZsjbwP8= X-Received: by 2002:aca:abc6:: with SMTP id u189-v6mr1703407oie.61.1533812791892; Thu, 09 Aug 2018 04:06:31 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4a:ad8f:0:0:0:0:0 with HTTP; Thu, 9 Aug 2018 04:06:30 -0700 (PDT) In-Reply-To: References: From: Loganaden Velvindron Date: Thu, 9 Aug 2018 15:06:30 +0400 Message-ID: To: Daniel Migault Cc: curdle Content-Type: multipart/mixed; boundary="0000000000009d18440572fe9e3e" Archived-At: Subject: Re: [Curdle] draft-ietf-curdle-rc4-die-die-die-06 review X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Aug 2018 11:06:36 -0000 --0000000000009d18440572fe9e3e Content-Type: text/plain; charset="UTF-8" Please find attached the revised xml file for rev 07, with the feedback received. I'm going to upload once the chairs clear this: https://datatracker.ietf.org/submit/status/97172/ On Tue, Jul 17, 2018 at 9:58 PM, Daniel Migault wrote: > Hi, > > We would like to thank Loganaden Velvindron for volunteering to co-author > and move the draft forward. > > Yours, > Daniel > > On Fri, Jul 6, 2018 at 5:13 PM, Daniel Migault > wrote: >> >> Hi, >> >> We would like to move the draft to the IESG, however, the draft has not >> been updated to address the comments received on the mailing list. We have >> privately contacted the author 3 times with the email address provided to >> the draft, but we did not receive any response. The purpose of this email is >> to first try to contact the author of draft via another channel and >> understand if he has any plan to move the draft forward. In addition, we >> would also like to see if there is any interest by some members of the group >> to co-author the draft and move the draft forward. For those interested in >> co-authoring the draft, please contact us privately. >> >> Our goal is to have all drafts - that is the two remaining drafts in WGLC >> - submitted by end of august. >> >> Yours, >> Rich and Daniel >> >> On Tue, May 15, 2018 at 1:00 PM, Daniel Migault >> wrote: >>> >>> Hi, >>> >>> Please find my review for draft-ietf-curdle-rc4-die-die-die-06 [1]. I >>> have also proposed text, so please comment the review in the mail. I am >>> willing to start a WGLC as soon as the draft is being updated. >>> >>> Yours, >>> Daniel >>> >>> >>> [1] https://tools.ietf.org/html/draft-ietf-curdle-rc4-die-die-die-06 >>> >>> >>> RFC-Editor: >>> >>> I personally find the ton of the sentence a bit aggressive, thus I would >>> remove it or just leave the RFC reference. >>> >>> """ >>> Non-ASCII characters are allowed in RFCs as per RFC 7997. >>> """ >>> >>> I see deprecation and move to historic status as very similar to >>> draft-ietf-curdle-des-des-des-die-die-die-05 and I assume that is correct. >>> >>> Abstract: >>> >>> The sentence below is a bit hard to parse. >>> "" >>> and formally obsoletes and moves to >>> Historic RFC 4345. >>> "" >>> >>> I would propose instead: >>> >>> """ >>> This document deprecates RC4 in Secure Shell (SSH). Therefore, this >>> document updates RFC 4253, and moves to Historic RFC 4345. >>> """ >>> >>> 1. Introduction >>> >>> >>> """ >>> RC4 is broken"" >>> """ >>> >>> Although English is not my main language, it sounds a bit abrupt to me >>> and it might be preferred to sue something around the lines of >>> draft-ietf-curdle-des-des-des-die-die-die-05: >>> >>> RC4 encryption is steadily weakening in cryptographic strength, and the >>> deprecation process should be begun for their use in SSH. >>> >>> >>> It seems to me that sections 1, 2 3 could be merged. I would propose the >>> following text. I am providing comments in . >>> >>> >>> >>> 1. Introduction >>> >>> >>> The usage of RC4 suites ( also designated as arcfour ) for SSH are >>> specified in RFC 4253 and RFC 4345. RFC 4253 specifies the allocation of the >>> "arcfour" cipher for SSH. RFC 4345 specifies and allocates the the >>> "arcfour-128" and "arcfour-256" ciphers for SSH. >>> >>> RC4 encryption is steadily weakening in cryptographic strength >>> [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and the deprecation >>> process should be begun for their use in Secure Shell (SSH) [RFC4253]. >>> Accordingly, RFC 4253 is updated to note the deprecation of the RC4 ciphers >>> and RFC 4345 is moved to Historic as all ciphers it specifies MUST NOT be >>> used. >>> >>> I believe that this document is very closed to >>> [draft-ietf-curdle-des-des-des-die-die-die-05] and as such a reference to it >>> should be mentioned. >>> >>> >>> 2. Requirements Notation >>> >>> 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 BCP 14 [RFC2119, RFC8174] >>> when, and only when, they appear in all capitals, as shown here. >>> >>> 3. Updates to RFC 4253 >>> >>> RFC 4253 is updated to prohibit arcfour's use in SSH. >>> >>> >>> """ >>> The last sentence of the paragraph on RC4 (called "arcfour" >>> in [RFC4253]) in Section 6.3 of [RFC4253] >>> """ >>> >>> I believe that it might be clearer to quote the text as it is not easy to >>> locate it. I would propose the text below. >>> >>> RFC 4253 allocate the "arcfour" cipher in Section 6.3 by defining a list >>> of defined ciphers where the "arcfour" cipher appears as optional as >>> mentioned below: >>> >>> """ >>> arcfour OPTIONAL the ARCFOUR stream cipher >>> with a 128-bit key >>> """ >>> >>> The current document updates the status of the "arcfour" ciphers in the >>> list of RFC 4253 Section 6.3 by moving it from OPTIONAL to MUST NOT. >>> >>> """ >>> arcfour MUST NOT the ARCFOUR stream cipher >>> with a 128-bit key >>> """ >>> >>> RFC 4253 defines the "arcfour" ciphers with the text mentioned below: >>> """ >>> The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. >>> The Arcfour cipher is believed to be compatible with the RC4 cipher >>> [SCHNEIER]. Arcfour (and RC4) has problems with weak keys, and >>> should be used with caution. >>> """ >>> >>> The current document updates RFC 4253 Section 6.3 by replacing th etext >>> above with the following text: >>> >>> """ >>> The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. >>> The Arcfour cipher is believed to be compatible with the RC4 cipher >>> [SCHNEIER]. Arcfour (and RC4) is steadily weakening in cryptographic >>> strength [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and >>> MUST NOT be used. >>> """ >>> >>> 4. IANA Considerations >>> >>> There is a reference to 3DES i think should be removed. In >>> addition, IANA cannot be required to update RFCs. IANA is assigned to update >>> the SSH registries. With [IANA] being an informational reference to >>> https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml, I >>> would propose the following text : >>> >>> The IANA is requested to update the Encryption Algorithm Name Registry >>> of the Secure Shell (SSH) Protocol Parameters [IANA]. The Registration >>> procedure is IETF Review which is achieved by this document. The registry >>> should be updated as follows: >>> >>> Encryption Algorithm Name Reference Note >>> arcfour [RFC-TBD] >>> arcfour128 [RFC-TBD] >>> arcfour256 [RFC-TBD] >>> >>> >>> Where TBD is the RFC number assigned to the document. >>> >>> >>> >> > > > _______________________________________________ > Curdle mailing list > Curdle@ietf.org > https://www.ietf.org/mailman/listinfo/curdle > --0000000000009d18440572fe9e3e Content-Type: text/xml; charset="US-ASCII"; name="draft-ietf-curdle-rc4-die-die-die.xml" Content-Disposition: attachment; filename="draft-ietf-curdle-rc4-die-die-die.xml" Content-Transfer-Encoding: base64 X-Attachment-Id: f_jkmgib2p0 PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVMtQVNDSUkiPz4KPCFET0NUWVBFIHJmYyBT WVNURU0gInJmYzI2MjkuZHRkIiBbCjwhLS0gT25lIG1ldGhvZCB0byBnZXQgcmVmZXJlbmNlcyBm cm9tIHRoZSBvbmxpbmUgY2l0YXRpb24gbGlicmFyaWVzLgogICAgVGhlcmUgaGFzIHRvIGJlIG9u ZSBlbnRpdHkgZm9yIGVhY2ggaXRlbSB0byBiZSByZWZlcmVuY2VkLiAKICAgIEFuIGFsdGVybmF0 ZSBtZXRob2QgKHJmYyBpbmNsdWRlKSBpcyBkZXNjcmliZWQgaW4gdGhlIHJlZmVyZW5jZXMuIC0t PgoKPCFFTlRJVFkgUkZDMjExOSBTWVNURU0gImh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1Ymxp Yy9yZmMvYmlieG1sL3JlZmVyZW5jZS5SRkMuMjExOS54bWwiPgo8IUVOVElUWSBSRkM1MjI2IFNZ U1RFTSAiaHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwvcmVmZXJlbmNl LlJGQy41MjI2LnhtbCI+CjwhRU5USVRZIFJGQzQzNDUgU1lTVEVNICJodHRwOi8veG1sLnJlc291 cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbC9yZWZlcmVuY2UuUkZDLjQzNDUueG1sIj4KPCFFTlRJ VFkgUkZDNDI1MyBTWVNURU0gImh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmli eG1sL3JlZmVyZW5jZS5SRkMuNDI1My54bWwiPgo8IUVOVElUWSBSRkM3NDY1IFNZU1RFTSAiaHR0 cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwvcmVmZXJlbmNlLlJGQy43NDY1 LnhtbCI+Cl0+Cjw/eG1sLXN0eWxlc2hlZXQgdHlwZT0ndGV4dC94c2wnIGhyZWY9J3JmYzI2Mjku eHNsdCcgPz4KPCEtLSB1c2VkIGJ5IFhTTFQgcHJvY2Vzc29ycyAtLT4KPCEtLSBGb3IgYSBjb21w bGV0ZSBsaXN0IGFuZCBkZXNjcmlwdGlvbiBvZiBwcm9jZXNzaW5nIGluc3RydWN0aW9ucyAoUElz KSwgCiAgICBwbGVhc2Ugc2VlIGh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL2F1dGhvcmluZy9SRUFE TUUuaHRtbC4gLS0+CjwhLS0gQmVsb3cgYXJlIGdlbmVyYWxseSBhcHBsaWNhYmxlIFByb2Nlc3Np bmcgSW5zdHJ1Y3Rpb25zIChQSXMpIHRoYXQgbW9zdCBJLURzIG1pZ2h0IHdhbnQgdG8gdXNlLgog ICAgKEhlcmUgdGhleSBhcmUgc2V0IGRpZmZlcmVudGx5IHRoYW4gdGhlaXIgZGVmYXVsdHMgaW4g eG1sMnJmYyB2MS4zMikgLS0+Cjw/cmZjIHN0cmljdD0ieWVzIiA/Pgo8IS0tIGdpdmUgZXJyb3Jz IHJlZ2FyZGluZyBJRC1uaXRzIGFuZCBEVEQgdmFsaWRhdGlvbiAtLT4KPCEtLSBjb250cm9sIHRo ZSB0YWJsZSBvZiBjb250ZW50cyAoVG9DKSAtLT4KPD9yZmMgdG9jPSJ5ZXMiPz4KPCEtLSBnZW5l cmF0ZSBhIFRvQyAtLT4KPD9yZmMgdG9jZGVwdGg9IjQiPz4KPCEtLSB0aGUgbnVtYmVyIG9mIGxl dmVscyBvZiBzdWJzZWN0aW9ucyBpbiBUb0MuIGRlZmF1bHQ6IDMgLS0+CjwhLS0gY29udHJvbCBy ZWZlcmVuY2VzIC0tPgo8P3JmYyBzeW1yZWZzPSJ5ZXMiPz4KPCEtLSB1c2Ugc3ltYm9saWMgcmVm ZXJlbmNlcyB0YWdzLCBpLmUsIFtSRkMyMTE5XSBpbnN0ZWFkIG9mIFsxXSAtLT4KPD9yZmMgc29y dHJlZnM9InllcyIgPz4KPCEtLSBzb3J0IHRoZSByZWZlcmVuY2UgZW50cmllcyBhbHBoYWJldGlj YWxseSAtLT4KPCEtLSBjb250cm9sIHZlcnRpY2FsIHdoaXRlIHNwYWNlIAogICAgKHVzaW5nIHRo ZXNlIFBJcyBhcyBmb2xsb3dzIGlzIHJlY29tbWVuZGVkIGJ5IHRoZSBSRkMgRWRpdG9yKSAtLT4K PD9yZmMgY29tcGFjdD0ieWVzIiA/Pgo8IS0tIGRvIG5vdCBzdGFydCBlYWNoIG1haW4gc2VjdGlv biBvbiBhIG5ldyBwYWdlIC0tPgo8P3JmYyBzdWJjb21wYWN0PSJubyIgPz4KPCEtLSBrZWVwIG9u ZSBibGFuayBsaW5lIGJldHdlZW4gbGlzdCBpdGVtcyAtLT4KPCEtLSBlbmQgb2YgbGlzdCBvZiBw b3B1bGFyIEktRCBwcm9jZXNzaW5nIGluc3RydWN0aW9ucyAtLT4KPHJmYyBjYXRlZ29yeT0iYmNw IiBvYnNvbGV0ZXM9IjQzMjUiIHVwZGF0ZXM9IjQyNTMiIGRvY05hbWU9ImRyYWZ0LWlldGYtY3Vy ZGxlLXJjNC1kaWUtZGllLWRpZS0wNyIgaXByPSJ0cnVzdDIwMDkwMiI+CiA8IS0tIGNhdGVnb3J5 IHZhbHVlczogc3RkLCBiY3AsIGluZm8sIGV4cCwgYW5kIGhpc3RvcmljCiAgICBpcHIgdmFsdWVz OiB0cnVzdDIwMDkwMiwgbm9Nb2RpZmljYXRpb25UcnVzdDIwMDkwMiwgbm9EZXJpdmF0aXZlc1Ry dXN0MjAwOTAyLAogICAgICAgb3IgcHJlNTM3OFRydXN0MjAwOTAyCiAgICB5b3UgY2FuIGFkZCB0 aGUgYXR0cmlidXRlcyB1cGRhdGVzPSJOTk5OIiBhbmQgb2Jzb2xldGVzPSJOTk5OIiAKICAgIHRo ZXkgd2lsbCBhdXRvbWF0aWNhbGx5IGJlIG91dHB1dCB3aXRoICIoaWYgYXBwcm92ZWQpIiAtLT4K CiA8IS0tICoqKioqIEZST05UIE1BVFRFUiAqKioqKiAtLT4KCiA8ZnJvbnQ+CiAgIDwhLS0gVGhl IGFiYnJldmlhdGVkIHRpdGxlIGlzIHVzZWQgaW4gdGhlIHBhZ2UgaGVhZGVyIC0gaXQgaXMgb25s eSBuZWNlc3NhcnkgaWYgdGhlIAogICAgICAgIGZ1bGwgdGl0bGUgaXMgbG9uZ2VyIHRoYW4gMzkg Y2hhcmFjdGVycyAtLT4KCiAgIDx0aXRsZSBhYmJyZXY9ImRyYWZ0LWlldGYtY3VyZGxlLXJjNC1k aWUtZGllLWRpZSI+RGVwcmVjYXRpbmcgUkM0IGluIFNlY3VyZSBTaGVsbCAoU1NIKTwvdGl0bGU+ CgogICA8IS0tIGFkZCAncm9sZT0iZWRpdG9yIicgYmVsb3cgZm9yIHRoZSBlZGl0b3JzIGlmIGFw cHJvcHJpYXRlIC0tPgoKICAgPCEtLSBBbm90aGVyIGF1dGhvciB3aG8gY2xhaW1zIHRvIGJlIGFu IGVkaXRvciAtLT4KCiAgIDxhdXRob3IgZnVsbG5hbWU9Ikx1aXMgQ2FtYXJhIiBpbml0aWFscz0i TC5DLiIgCiAgICAgICAgICAgc3VybmFtZT0iQ2FtYXJhIj4KICAgICA8b3JnYW5pemF0aW9uPjwv b3JnYW5pemF0aW9uPgoKICAgICA8YWRkcmVzcz4KICAgICAgIDxwb3N0YWw+CiAgICAgICAgIDxz dHJlZXQ+PC9zdHJlZXQ+CgogICAgICAgICA8IS0tIFJlb3JkZXIgdGhlc2UgaWYgeW91ciBjb3Vu dHJ5IGRvZXMgdGhpbmdzIGRpZmZlcmVudGx5IC0tPgoKICAgICAgICAgPGNpdHk+PC9jaXR5PgoK ICAgICAgICAgPHJlZ2lvbj48L3JlZ2lvbj4KCiAgICAgICAgIDxjb2RlPjwvY29kZT4KCiAgICAg ICAgIDxjb3VudHJ5PjwvY291bnRyeT4KICAgICAgIDwvcG9zdGFsPgoKICAgICAgIDxwaG9uZT48 L3Bob25lPgoKICAgICAgIDxlbWFpbD5sdWlzLmNhbWFyYUBsaXZlLmNvbS5wdDwvZW1haWw+Cgog ICAgICAgPCEtLSB1cmkgYW5kIGZhY3NpbWlsZSBlbGVtZW50cyBtYXkgYWxzbyBiZSBhZGRlZCAt LT4KICAgICA8L2FkZHJlc3M+CiAgIDwvYXV0aG9yPgoKICAgPGF1dGhvciBmdWxsbmFtZT0iTG9n YW5hZGVuIFZlbHZpbmRyb24iIGluaXRpYWxzPSJMLlYuIiAKICAgICAgICAgICBzdXJuYW1lPSJW ZWx2aW5kcm9uIj4KICAgICA8b3JnYW5pemF0aW9uPjwvb3JnYW5pemF0aW9uPgoKICAgICA8YWRk cmVzcz4KICAgICAgIDxwb3N0YWw+CiAgICAgICAgIDxzdHJlZXQ+PC9zdHJlZXQ+CgogICAgICAg ICA8IS0tIFJlb3JkZXIgdGhlc2UgaWYgeW91ciBjb3VudHJ5IGRvZXMgdGhpbmdzIGRpZmZlcmVu dGx5IC0tPgoKICAgICAgICAgPGNpdHk+PC9jaXR5PgoKICAgICAgICAgPHJlZ2lvbj48L3JlZ2lv bj4KCiAgICAgICAgIDxjb2RlPjwvY29kZT4KCiAgICAgICAgIDxjb3VudHJ5Pk1hdXJpdGl1czwv Y291bnRyeT4KICAgICAgIDwvcG9zdGFsPgoKICAgICAgIDxwaG9uZT48L3Bob25lPgoKICAgICAg IDxlbWFpbD5sb2dhbkBoYWNrZXJzLm11PC9lbWFpbD4KCiAgICAgICA8IS0tIHVyaSBhbmQgZmFj c2ltaWxlIGVsZW1lbnRzIG1heSBhbHNvIGJlIGFkZGVkIC0tPgogICAgIDwvYWRkcmVzcz4KICAg PC9hdXRob3I+CiAgIDxkYXRlIHllYXI9IjIwMTgiIC8+CgoKCiAgIDwhLS0gTWV0YS1kYXRhIERl Y2xhcmF0aW9ucyAtLT4KCiAgIDxhcmVhPkdlbmVyYWw8L2FyZWE+CgogICA8d29ya2dyb3VwPklu dGVybmV0IEVuZ2luZWVyaW5nIFRhc2sgRm9yY2U8L3dvcmtncm91cD4KCiAgIDwhLS0gV0cgbmFt ZSBhdCB0aGUgdXBwZXJsZWZ0IGNvcm5lciBvZiB0aGUgZG9jLAogICAgICAgIElFVEYgaXMgZmlu ZSBmb3IgaW5kaXZpZHVhbCBzdWJtaXNzaW9ucy4gIAoJIElmIHRoaXMgZWxlbWVudCBpcyBub3Qg cHJlc2VudCwgdGhlIGRlZmF1bHQgaXMgIk5ldHdvcmsgV29ya2luZyBHcm91cCIsCiAgICAgICAg d2hpY2ggaXMgdXNlZCBieSB0aGUgUkZDIEVkaXRvciBhcyBhIG5vZCB0byB0aGUgaGlzdG9yeSBv ZiB0aGUgSUVURi4gLS0+CgogICA8a2V5d29yZD50ZW1wbGF0ZTwva2V5d29yZD4KCiAgIDwhLS0g S2V5d29yZHMgd2lsbCBiZSBpbmNvcnBvcmF0ZWQgaW50byBIVE1MIG91dHB1dAogICAgICAgIGZp bGVzIGluIGEgbWV0YSB0YWcgYnV0IHRoZXkgaGF2ZSBubyBlZmZlY3Qgb24gdGV4dCBvciBucm9m ZgogICAgICAgIG91dHB1dC4gSWYgeW91IHN1Ym1pdCB5b3VyIGRyYWZ0IHRvIHRoZSBSRkMgRWRp dG9yLCB0aGUKICAgICAgICBrZXl3b3JkcyB3aWxsIGJlIHVzZWQgZm9yIHRoZSBzZWFyY2ggZW5n aW5lLiAtLT4KCiAgIDxhYnN0cmFjdD4KICAgICA8dD4gICBUaGlzIGRvY3VtZW50IGRlcHJlY2F0 ZXMgUkM0IGluIFNlY3VyZSBTaGVsbCAoU1NIKS4gIFRoZXJlZm9yZSwgdGhpcwogICBkb2N1bWVu dCB1cGRhdGVzIDx4cmVmIHRhcmdldD0iUkZDNDI1MyI+PC94cmVmPiwgYW5kIGZvcm1hbGx5IG9i c29sZXRlcyBhbmQgbW92ZXMgdG8KICAgSGlzdG9yaWMgPHhyZWYgdGFyZ2V0PSJSRkM0MzQ1Ij48 L3hyZWY+LgogPC90PgogICA8L2Fic3RyYWN0PgogPC9mcm9udD4KCiA8bWlkZGxlPgogICA8c2Vj dGlvbiB0aXRsZT0iSW50cm9kdWN0aW9uIj4KICAgICA8dD5UaGUgdXNhZ2Ugb2YgUkM0IHN1aXRl cyAoIGFsc28gZGVzaWduYXRlZCBhcyBhcmNmb3VyICkgZm9yIFNTSCBhcmUgc3BlY2lmaWVkIGlu IDx4cmVmIHRhcmdldD0iUkZDNDI1MyI+PC94cmVmPiBhbmQgPHhyZWYgdGFyZ2V0PSJSRkM0MzQ1 Ij48L3hyZWY+LiAKICAgICA8eHJlZiB0YXJnZXQ9IlJGQzQyNTMiPjwveHJlZj4gc3BlY2lmaWVz IHRoZSBhbGxvY2F0aW9uIG9mIHRoZSAiYXJjZm91ciIgY2lwaGVyIGZvciBTU0guIDx4cmVmIHRh cmdldD0iUkZDNDM0NSI+PC94cmVmPiBzcGVjaWZpZXMgYW5kIGFsbG9jYXRlcyB0aGUgCiAgICAg dGhlICJhcmNmb3VyLTEyOCIgYW5kICJhcmNmb3VyLTI1NiIgY2lwaGVycyBmb3IgU1NILiAKCiAg ICAgUkM0IGVuY3J5cHRpb24gaXMgc3RlYWRpbHkgd2Vha2VuaW5nIGluIGNyeXB0b2dyYXBoaWMg c3RyZW5ndGggPHhyZWYgdGFyZ2V0PSJSRkM3NDY1Ij48L3hyZWY+IDx4cmVmIHRhcmdldD0iSS1E LmlldGYtY3VyZGxlLWRlcy1kZXMtZGVzLWRpZS1kaWUtZGllIj48L3hyZWY+LCAKICAgICBhbmQg dGhlIGRlcHJlY2F0aW9uIHByb2Nlc3Mgc2hvdWxkIGJlIGJlZ3VuIGZvciB0aGVpciB1c2UgaW4g U2VjdXJlIFNoZWxsIChTU0gpIDx4cmVmIHRhcmdldD0iUkZDNDI1MyI+PC94cmVmPi4gQWNjb3Jk aW5nbHksIDx4cmVmIHRhcmdldD0iUkZDNDI1MyI+PC94cmVmPiBpcyAKICAgICB1cGRhdGVkIHRv IG5vdGUgdGhlIGRlcHJlY2F0aW9uIG9mIHRoZSBSQzQgY2lwaGVycyBhbmQgPHhyZWYgdGFyZ2V0 PSJSRkM0MzQ1Ij48L3hyZWY+IGlzIG1vdmVkIHRvIEhpc3RvcmljIGFzIGFsbCBjaXBoZXJzIGl0 IHNwZWNpZmllcyBNVVNUIE5PVCBiZSB1c2VkLiAgPC90PgoKICAgICA8c2VjdGlvbiB0aXRsZT0i UmVxdWlyZW1lbnRzIExhbmd1YWdlIj4KICAgICAgIDx0PlRoZSBrZXkgd29yZHMgIk1VU1QiLCAi TVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9UIiwKICAgICAgICJTSE9V TEQiLCAiU0hPVUxEIE5PVCIsICJSRUNPTU1FTkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFMIiBp biB0aGlzCiAgICAgICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVk IGluIDx4cmVmCiAgICAgICB0YXJnZXQ9IlJGQzIxMTkiPlJGQyAyMTE5PC94cmVmPi48L3Q+CiAg ICAgPC9zZWN0aW9uPgogICA8L3NlY3Rpb24+Cgo8c2VjdGlvbiB0aXRsZT0iVXBkYXRlcyB0byBS RkMgNDI1MyI+Cjx0Pgo8eHJlZiB0YXJnZXQ9IlJGQzQyNTMiPjwveHJlZj4gaXMgdXBkYXRlZCB0 byBwcm9oaWJpdCBhcmNmb3VyJ3MgdXNlIGluIFNTSC4KPHhyZWYgdGFyZ2V0PSJSRkM0MjUzIj48 L3hyZWY+IGFsbG9jYXRlcyB0aGUgImFyY2ZvdXIiIGNpcGhlciBpbiBTZWN0aW9uIDYuMyBieSBk ZWZpbmluZyBhIGxpc3Qgb2YgZGVmaW5lZCBjaXBoZXJzIHdoZXJlIHRoZSAiYXJjZm91ciIgY2lw aGVyIGFwcGVhcnMgYXMgb3B0aW9uYWwgYXMgbWVudGlvbmVkIGJlbG93OiAKPC90Pgo8dGV4dHRh YmxlPgogICAgICAgIDx0dGNvbCA+PC90dGNvbD4KICAgICAgICA8dHRjb2wgPjwvdHRjb2w+CiAg ICAgICAgPHR0Y29sID48L3R0Y29sPgoKICAgIDxjPmFyY2ZvdXIgICAgICAgICAgIDwvYz4gIAog ICAgPGM+T1BUSU9OQUwgICAgICAgICAgICA8L2M+CiAgICAgPGM+dGhlIEFSQ0ZPVVIgc3RyZWFt IGNpcGhlciB3aXRoIGEgMTI4LWJpdCBrZXkgPC9jPiAKPC90ZXh0dGFibGU+Cjx0PgpUaGUgY3Vy cmVudCBkb2N1bWVudCB1cGRhdGVzIHRoZSBzdGF0dXMgb2YgdGhlICJhcmNmb3VyIiBjaXBoZXJz IGluIHRoZSBsaXN0IG9mIDx4cmVmIHRhcmdldD0iUkZDNDI1MyI+PC94cmVmPiBTZWN0aW9uIDYu MyBieSBtb3ZpbmcgaXQgZnJvbSBPUFRJT05BTCB0byBNVVNUIE5PVC4gCjwvdD4KPHRleHR0YWJs ZT4KICAgICAgICA8dHRjb2wgPjwvdHRjb2w+CiAgICAgICAgPHR0Y29sID48L3R0Y29sPgogICAg ICAgIDx0dGNvbCA+PC90dGNvbD4KIDxjPiBhcmNmb3VyIDwvYz4gICAgICAgPGM+TVVTVCBOT1Qg PC9jPiAgICAgICAgPGM+IHRoZSBBUkNGT1VSIHN0cmVhbSBjaXBoZXIgd2l0aCBhIDEyOC1iaXQg a2V5PC9jPgo8L3RleHR0YWJsZT4KCjx0Pgo8eHJlZiB0YXJnZXQ9IlJGQzQyNTMiPjwveHJlZj4g ZGVmaW5lcyB0aGUgImFyY2ZvdXIiIGNpcGhlcnMgd2l0aCB0aGUgdGV4dCBtZW50aW9uZWQgYmVs b3c6IAo8L3Q+Cjx0PgogICBUaGUgImFyY2ZvdXIiIGNpcGhlciBpcyB0aGUgQXJjZm91ciBzdHJl YW0gY2lwaGVyIHdpdGggMTI4LWJpdCBrZXlzLgogICBUaGUgQXJjZm91ciBjaXBoZXIgaXMgYmVs aWV2ZWQgdG8gYmUgY29tcGF0aWJsZSB3aXRoIHRoZSBSQzQgY2lwaGVyCiAgIDx4cmVmIHRhcmdl dD0gIlNDSE5FSUVSIj48L3hyZWY+LiAgQXJjZm91ciAoYW5kIFJDNCkgaGFzIHByb2JsZW1zIHdp dGggd2VhayBrZXlzLCBhbmQKICAgc2hvdWxkIGJlIHVzZWQgd2l0aCBjYXV0aW9uLgo8L3Q+ICAK PHQ+ClRoZSBjdXJyZW50IGRvY3VtZW50IHVwZGF0ZXMgPHhyZWYgdGFyZ2V0PSJSRkM0MjUzIj48 L3hyZWY+IFNlY3Rpb24gNi4zIGJ5IHJlcGxhY2luZyB0aGUgdGV4dCBhYm92ZSB3aXRoIHRoZSBm b2xsb3dpbmcgdGV4dDoKPC90Pgo8dD4gCiAgVGhlICJhcmNmb3VyIiBjaXBoZXIgaXMgdGhlIEFy Y2ZvdXIgc3RyZWFtIGNpcGhlciB3aXRoIDEyOC1iaXQga2V5cy4KICAgVGhlIEFyY2ZvdXIgY2lw aGVyIGlzIGJlbGlldmVkIHRvIGJlIGNvbXBhdGlibGUgd2l0aCB0aGUgUkM0IGNpcGhlcgogICA8 eHJlZiB0YXJnZXQ9ICJTQ0hORUlFUiI+PC94cmVmPi4gIEFyY2ZvdXIgKGFuZCBSQzQpIGlzIHN0 ZWFkaWx5IHdlYWtlbmluZyBpbiBjcnlwdG9ncmFwaGljIHN0cmVuZ3RoIDx4cmVmIHRhcmdldD0i UkZDNzQ2NSI+PC94cmVmPiA8eHJlZiB0YXJnZXQ9IkktRC5pZXRmLWN1cmRsZS1kZXMtZGVzLWRl cy1kaWUtZGllLWRpZSI+PC94cmVmPiwgYW5kCiAgIE1VU1QgTk9UIGJlIHVzZWQuCjwvdD4KPC9z ZWN0aW9uPgogCgoKICAgPCEtLSBQb3NzaWJseSBhICdDb250cmlidXRvcnMnIHNlY3Rpb24gLi4u IC0tPgoKICAgPHNlY3Rpb24gYW5jaG9yPSJJQU5BIiB0aXRsZT0iSUFOQSBDb25zaWRlcmF0aW9u cyI+CiAgICAgPHQ+VGhlIElBTkEgaXMgcmVxdWVzdGVkIHRvIHVwZGF0ZSB0aGUgRW5jcnlwdGlv biBBbGdvcml0aG0gTmFtZSAgUmVnaXN0cnkgb2YgdGhlIFNlY3VyZSBTaGVsbCAoU1NIKSBQcm90 b2NvbCBQYXJhbWV0ZXJzIFtJQU5BXS4gClRoZSBSZWdpc3RyYXRpb24gcHJvY2VkdXJlIGlzIElF VEYgUmV2aWV3IHdoaWNoIGlzIGFjaGlldmVkIGJ5IHRoaXMgZG9jdW1lbnQuIFRoZSByZWdpc3Ry eSBzaG91bGQgYmUgdXBkYXRlZCBhcyBmb2xsb3dzOjwvdD4KPHRleHR0YWJsZT4KPHR0Y29sPkVu Y3J5cHRpb24gPC90dGNvbD4gPHR0Y29sPkFsZ29yaXRobSAgTmFtZSAgIFJlZmVyZW5jZSAgIE5v dGU8L3R0Y29sPiAKPGM+YXJjZm91cjwvYz4gICAgICAgICAgICAgICAgICAgICAgICAgPGM+IFtS RkMtVEJEXTwvYz4gICAgIAo8Yz5hcmNmb3VyMTI4IDwvYz4gICAgICAgICAgICAgICAgIDxjPiAg IFtSRkMtVEJEXSA8L2M+ICAgIAo8Yz5hcmNmb3VyMjU2IDwvYz4gICAgICAgICAgICAgICAgICA8 Yz4gICBbUkZDLVRCRF0gPC9jPiAgICAKPC90ZXh0dGFibGU+Cgo8dD5XaGVyZSBUQkQgaXMgdGhl IFJGQyBudW1iZXIgYXNzaWduZWQgdG8gdGhlIGRvY3VtZW50LiA8L3Q+CgogICAgIDx0PkFsbCBk cmFmdHMgYXJlIHJlcXVpcmVkIHRvIGhhdmUgYW4gSUFOQSBjb25zaWRlcmF0aW9ucyBzZWN0aW9u IChzZWUKICAgICA8eHJlZiB0YXJnZXQ9IlJGQzUyMjYiPkd1aWRlbGluZXMgZm9yIFdyaXRpbmcg YW4gSUFOQSBDb25zaWRlcmF0aW9ucyBTZWN0aW9uIGluIFJGQ3M8L3hyZWY+IGZvciBhIGd1aWRl KS4gSWYgdGhlIGRyYWZ0IGRvZXMgbm90IHJlcXVpcmUgSUFOQSB0byBkbwogICAgIGFueXRoaW5n LCB0aGUgc2VjdGlvbiBjb250YWlucyBhbiBleHBsaWNpdCBzdGF0ZW1lbnQgdGhhdCB0aGlzIGlz IHRoZQogICAgIGNhc2UgKGFzIGFib3ZlKS4gSWYgdGhlcmUgYXJlIG5vIHJlcXVpcmVtZW50cyBm b3IgSUFOQSwgdGhlIHNlY3Rpb24gd2lsbAogICAgIGJlIHJlbW92ZWQgZHVyaW5nIGNvbnZlcnNp b24gaW50byBhbiBSRkMgYnkgdGhlIFJGQyBFZGl0b3IuPC90PgogICA8L3NlY3Rpb24+CgogICA8 c2VjdGlvbiBhbmNob3I9IkFja25vd2xlZGdlbWVudHMiIHRpdGxlPSJBY2tub3dsZWRnZW1lbnRz Ij4KICAgICA8dD5UaGUgYXV0aG9ycyB3b3VsZCBsaWtlIHRvIHRoYW5rIERhbmllbCBNaWdhdWx0 IDwvdD4KCiAgIDwvc2VjdGlvbj4KICAgPHNlY3Rpb24gYW5jaG9yPSJTZWN1cml0eSIgdGl0bGU9 IlNlY3VyaXR5IENvbnNpZGVyYXRpb25zIj4KICAgICA8dD5UaGlzIGRvY3VtZW50IG9ubHkgcHJv aGliaXRzIHRoZSB1c2Ugb2YgUkM0IGluIFNTSCwgYW5kIGludHJvZHVjZXMgbm8KICAgbmV3IHNl Y3VyaXR5IGNvbnNpZGVyYXRpb25zLjwvdD4KICAgPC9zZWN0aW9uPgogPC9taWRkbGU+CgogPCEt LSAgKioqKipCQUNLIE1BVFRFUiAqKioqKiAtLT4KCiA8YmFjaz4KICAgPCEtLSBSZWZlcmVuY2Vz IHNwbGl0IGludG8gaW5mb3JtYXRpdmUgYW5kIG5vcm1hdGl2ZSAtLT4KCiAgCgogICA8cmVmZXJl bmNlcyB0aXRsZT0iTm9ybWF0aXZlIFJlZmVyZW5jZXMiPgogICAgIDwhLS0/cmZjIGluY2x1ZGU9 Imh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmlieG1sL3JlZmVyZW5jZS5SRkMu MjExOS54bWwiPy0tPgogICAgICZSRkMyMTE5OwogICA8cmVmZXJlbmNlIGFuY2hvcj0iU0NITkVJ RVIiIHRhcmdldD0iU0NITkVJRVIiPgogICAgICAgIDxmcm9udD4KICAgICAgICAgICAgPHRpdGxl PkFwcGxpZWQgQ3J5cHRvZ3JhcGh5IFNlY29uZCBFZGl0aW9uOgogICAgICAgICAgICAgICAgICBw cm90b2NvbHMgYWxnb3JpdGhtcyBhbmQgc291cmNlIGluIGNvZGUgaW4gQyA8L3RpdGxlPgogICAg ICAgICAgICA8YXV0aG9yIGluaXRpYWxzPSJCLlMiIHN1cm5hbWU9IlNjaG5laWVyIiBmdWxsbmFt ZT0iQnJ1Y2UgU2NobmVpZXIiPgogICAgICAgICAgICAgICAgPG9yZ2FuaXphdGlvbiAvPgogICAg ICAgICAgICA8L2F1dGhvcj4KICAgICAgICAgICAgPGRhdGUgbW9udGg9IiIgeWVhcj0iMTk5NiIg Lz4KICAgICAgICA8L2Zyb250PgogICAgICAgIDxzZXJpZXNJbmZvIG5hbWU9IiIgdmFsdWU9IiIg Lz4KICAgIDwvcmVmZXJlbmNlPgoKIAogICA8L3JlZmVyZW5jZXM+CgogICA8cmVmZXJlbmNlcyB0 aXRsZT0iSW5mb3JtYXRpdmUgUmVmZXJlbmNlcyI+CiAgICAgPCEtLSBIZXJlIHdlIHVzZSBlbnRp dGllcyB0aGF0IHdlIGRlZmluZWQgYXQgdGhlIGJlZ2lubmluZy4gLS0+CgoKICAgICAmUkZDNTIy NjsKCiAgICAgJlJGQzQzNDU7CgogICAgICZSRkM0MjUzOwoKICAgICZSRkM3NDY1OwoKICAgPHJl ZmVyZW5jZSBhbmNob3I9J0ktRC5pZXRmLWN1cmRsZS1kZXMtZGVzLWRlcy1kaWUtZGllLWRpZSc+ Cjxmcm9udD4KPHRpdGxlPkRlcHJlY2F0ZSAzREVTIGFuZCBSQzQgaW4gS2VyYmVyb3M8L3RpdGxl PgoKPGF1dGhvciBpbml0aWFscz0nQicgc3VybmFtZT0nS2FkdWsnIGZ1bGxuYW1lPSdCZW5qYW1p biBLYWR1ayc+CiAgICA8b3JnYW5pemF0aW9uIC8+CjwvYXV0aG9yPgoKPGF1dGhvciBpbml0aWFs cz0nTScgc3VybmFtZT0nU2hvcnQnIGZ1bGxuYW1lPSdNaWNoaWtvIFNob3J0Jz4KICAgIDxvcmdh bml6YXRpb24gLz4KPC9hdXRob3I+Cgo8ZGF0ZSBtb250aD0nU2VwdGVtYmVyJyBkYXk9JzE4JyB5 ZWFyPScyMDE3JyAvPgoKPGFic3RyYWN0Pjx0PlRoZSAzREVTIGFuZCBSQzQgZW5jcnlwdGlvbiB0 eXBlcyBhcmUgc3RlYWRpbHkgd2Vha2VuaW5nIGluIGNyeXB0b2dyYXBoaWMgc3RyZW5ndGgsIGFu ZCB0aGUgZGVwcmVjYXRpb24gcHJvY2VzcyBzaG91bGQgYmUgYmVndW4gZm9yIHRoZWlyIHVzZSBp biBLZXJiZXJvcy4gIEFjY29yZGluZ2x5LCBSRkMgNDc1NyBpcyBtb3ZlZCB0byBIaXN0b3JpYyBz dGF0dXMsIGFzIG5vbmUgb2YgdGhlIGVuY3J5cHRpb24gdHlwZXMgaXQgc3BlY2lmaWVzIHNob3Vs ZCBiZSB1c2VkLCBhbmQgUkZDIDM5NjEgaXMgdXBkYXRlZCB0byBub3RlIHRoZSBkZXByZWNhdGlv biBvZiB0aGUgdHJpcGxlLURFUyBlbmNyeXB0aW9uIHR5cGVzLjwvdD48L2Fic3RyYWN0PgoKPC9m cm9udD4KCjxzZXJpZXNJbmZvIG5hbWU9J0ludGVybmV0LURyYWZ0JyB2YWx1ZT0nZHJhZnQtaWV0 Zi1jdXJkbGUtZGVzLWRlcy1kZXMtZGllLWRpZS1kaWUtMDUnIC8+Cjxmb3JtYXQgdHlwZT0nVFhU JwogICAgICAgIHRhcmdldD0naHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh ZnQtaWV0Zi1jdXJkbGUtZGVzLWRlcy1kZXMtZGllLWRpZS1kaWUtMDUudHh0JyAvPgo8L3JlZmVy ZW5jZT4KCgoKICAgICA8IS0tIEEgcmVmZXJlbmNlIHdyaXR0ZW4gYnkgYnkgYW4gb3JnYW5pemF0 aW9uIG5vdCBhIHBlcnNvbi4gLS0+CgogICA8L3JlZmVyZW5jZXM+CgoKICAgPCEtLSBDaGFuZ2Ug TG9nCgp2MDcgcmVwcm9kdWNlIC0wNiBvZiBsdWlzJyBkcmFmdCArIHVwZGF0ZSB3aXRoIGRhbmll bCdzIGNvbW1lbnRzCnYwOCB1cGRhdGVzIGZyb20gZGFuaWVsLgogLS0+CiA8L2JhY2s+CjwvcmZj Pgo= --0000000000009d18440572fe9e3e-- From nobody Thu Aug 9 06:52:27 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9C8130E70 for ; Thu, 9 Aug 2018 06:52:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zbMQ9OjuG9W1 for ; Thu, 9 Aug 2018 06:52:12 -0700 (PDT) Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E41761277D2 for ; Thu, 9 Aug 2018 06:52:11 -0700 (PDT) Received: by mail-lj1-x22e.google.com with SMTP id s12-v6so4561470ljj.0 for ; Thu, 09 Aug 2018 06:52:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=JVzsb/TDUw6//dgzllU9fjacltE0kiwl9PJHYS9Th9c=; b=rXLqgiPUtZMv7EzhIDs7OYVpfIdihBhQB2hZj7yCNXsd90CTbcu7ermcBPvNlZ0Fua 9e9RYiqLc/F03SkgaEzKBrOTFv2WhU5CggUiHrxCCz3Ca2IkfPFyOvWS2Ygu0t4xbHIi m7t1/hQrgWIN1FGFaWcrkHaww41Th+ZC8Azjppqn42zZerQJwnjJxyOx6Lyg7h0zUHEL fwdjyK64C80+Pz4JMBej+WsIkVqGRBoHEYuq9jV84CallRVrwip+nO70ffW9jTynFCOr 40nbDaNr/uCAfUBNKlcu01RI2nHDf5aOVO7BOaeMFW1Qkxg7FN/mW9aygUHK4oUS9lzK vbFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=JVzsb/TDUw6//dgzllU9fjacltE0kiwl9PJHYS9Th9c=; b=Qxk3nYiilpnpmkMsUYvnGR8da88+WWkFm2PKJJcO9QJnFDqSzs2OkPheXcUeE/0SEz Geuw61fk6L6qq5Jtkf2xPrd5+6z9FoliQwDndyT7ztkVtzWBpLgkmYV48cIZ4kwz+wD1 bFjcR79HLCOLpDAXQLFfxtiuDBXgfiN2W6FsqS3mc2UOS1bn0xZMQLGUqhAwVqzTCsPV 7PSM/osypsQCi+i7w8IicFYFBkfAODUqqZdsqLbSqDv3iBsOZ1UTfky4VJiUXDvrCDkf YNhAw9lRYEOfm5SBlDXbZIivg8v2UbelRpGzFbllKuJHMzXytSw4NGpjitWHaDe+5QWB BQfA== X-Gm-Message-State: AOUpUlF+tXrLJ/B4anNJbaHkfGcY5TmtNUTvzgnS0FZop+14Fj8pK/be S6oHxom1a6SpyuB8dRCLrzorJstLxmyssFu8f3NxRQ== X-Google-Smtp-Source: AA+uWPzKaPohhorADSzNw/OLAEydJq/WrIKOp5EaJxhvGrHlGaXHughNhsT//o21Wp0uBVZJ4aq5qzCTkMvylVjEEBc= X-Received: by 2002:a2e:5b4a:: with SMTP id p71-v6mr1761792ljb.91.1533822730183; Thu, 09 Aug 2018 06:52:10 -0700 (PDT) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 2002:a2e:5295:0:0:0:0:0 with HTTP; Thu, 9 Aug 2018 06:52:09 -0700 (PDT) In-Reply-To: References: From: Daniel Migault Date: Thu, 9 Aug 2018 09:52:09 -0400 X-Google-Sender-Auth: jmZz4RR5R0ZfEECkTKmyRLylIS4 Message-ID: To: Loganaden Velvindron Cc: curdle Content-Type: multipart/alternative; boundary="000000000000fb28a3057300ee20" Archived-At: Subject: Re: [Curdle] draft-ietf-curdle-rc4-die-die-die-06 review X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Aug 2018 13:52:26 -0000 --000000000000fb28a3057300ee20 Content-Type: text/plain; charset="UTF-8" Hi, I think that should be fine now - I can see that we both of us has approved the link. Thanks for updating the document! Let us know if you encounter any issues! Yours, Daniel On Thu, Aug 9, 2018 at 7:06 AM, Loganaden Velvindron wrote: > Please find attached the revised xml file for rev 07, with the > feedback received. > > I'm going to upload once the chairs clear this: > https://datatracker.ietf.org/submit/status/97172/ > > > > On Tue, Jul 17, 2018 at 9:58 PM, Daniel Migault > wrote: > > Hi, > > > > We would like to thank Loganaden Velvindron for volunteering to co-author > > and move the draft forward. > > > > Yours, > > Daniel > > > > On Fri, Jul 6, 2018 at 5:13 PM, Daniel Migault < > daniel.migault@ericsson.com> > > wrote: > >> > >> Hi, > >> > >> We would like to move the draft to the IESG, however, the draft has not > >> been updated to address the comments received on the mailing list. We > have > >> privately contacted the author 3 times with the email address provided > to > >> the draft, but we did not receive any response. The purpose of this > email is > >> to first try to contact the author of draft via another channel and > >> understand if he has any plan to move the draft forward. In addition, we > >> would also like to see if there is any interest by some members of the > group > >> to co-author the draft and move the draft forward. For those interested > in > >> co-authoring the draft, please contact us privately. > >> > >> Our goal is to have all drafts - that is the two remaining drafts in > WGLC > >> - submitted by end of august. > >> > >> Yours, > >> Rich and Daniel > >> > >> On Tue, May 15, 2018 at 1:00 PM, Daniel Migault > >> wrote: > >>> > >>> Hi, > >>> > >>> Please find my review for draft-ietf-curdle-rc4-die-die-die-06 [1]. I > >>> have also proposed text, so please comment the review in the mail. I am > >>> willing to start a WGLC as soon as the draft is being updated. > >>> > >>> Yours, > >>> Daniel > >>> > >>> > >>> [1] https://tools.ietf.org/html/draft-ietf-curdle-rc4-die-die-die-06 > >>> > >>> > >>> RFC-Editor: > >>> > >>> I personally find the ton of the sentence a bit aggressive, thus I > would > >>> remove it or just leave the RFC reference. > >>> > >>> """ > >>> Non-ASCII characters are allowed in RFCs as per RFC 7997. > >>> """ > >>> > >>> I see deprecation and move to historic status as very similar to > >>> draft-ietf-curdle-des-des-des-die-die-die-05 and I assume that is > correct. > >>> > >>> Abstract: > >>> > >>> The sentence below is a bit hard to parse. > >>> "" > >>> and formally obsoletes and moves to > >>> Historic RFC 4345. > >>> "" > >>> > >>> I would propose instead: > >>> > >>> """ > >>> This document deprecates RC4 in Secure Shell (SSH). Therefore, this > >>> document updates RFC 4253, and moves to Historic RFC 4345. > >>> """ > >>> > >>> 1. Introduction > >>> > >>> > >>> """ > >>> RC4 is broken"" > >>> """ > >>> > >>> Although English is not my main language, it sounds a bit abrupt to me > >>> and it might be preferred to sue something around the lines of > >>> draft-ietf-curdle-des-des-des-die-die-die-05: > >>> > >>> RC4 encryption is steadily weakening in cryptographic strength, and the > >>> deprecation process should be begun for their use in SSH. > >>> > >>> > >>> It seems to me that sections 1, 2 3 could be merged. I would propose > the > >>> following text. I am providing comments in . > >>> > >>> > >>> > >>> 1. Introduction > >>> > >>> > >>> The usage of RC4 suites ( also designated as arcfour ) for SSH are > >>> specified in RFC 4253 and RFC 4345. RFC 4253 specifies the allocation > of the > >>> "arcfour" cipher for SSH. RFC 4345 specifies and allocates the the > >>> "arcfour-128" and "arcfour-256" ciphers for SSH. > >>> > >>> RC4 encryption is steadily weakening in cryptographic strength > >>> [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and the > deprecation > >>> process should be begun for their use in Secure Shell (SSH) [RFC4253]. > >>> Accordingly, RFC 4253 is updated to note the deprecation of the RC4 > ciphers > >>> and RFC 4345 is moved to Historic as all ciphers it specifies MUST NOT > be > >>> used. > >>> > >>> I believe that this document is very closed to > >>> [draft-ietf-curdle-des-des-des-die-die-die-05] and as such a > reference to it > >>> should be mentioned. > >>> > >>> > >>> 2. Requirements Notation > >>> > >>> 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 BCP 14 [RFC2119, > RFC8174] > >>> when, and only when, they appear in all capitals, as shown here. > >>> > >>> 3. Updates to RFC 4253 > >>> > >>> RFC 4253 is updated to prohibit arcfour's use in SSH. > >>> > >>> > >>> """ > >>> The last sentence of the paragraph on RC4 (called "arcfour" > >>> in [RFC4253]) in Section 6.3 of [RFC4253] > >>> """ > >>> > >>> I believe that it might be clearer to quote the text as it is not easy > to > >>> locate it. I would propose the text below. > >>> > >>> RFC 4253 allocate the "arcfour" cipher in Section 6.3 by defining a > list > >>> of defined ciphers where the "arcfour" cipher appears as optional as > >>> mentioned below: > >>> > >>> """ > >>> arcfour OPTIONAL the ARCFOUR stream cipher > >>> with a 128-bit key > >>> """ > >>> > >>> The current document updates the status of the "arcfour" ciphers in the > >>> list of RFC 4253 Section 6.3 by moving it from OPTIONAL to MUST NOT. > >>> > >>> """ > >>> arcfour MUST NOT the ARCFOUR stream cipher > >>> with a 128-bit key > >>> """ > >>> > >>> RFC 4253 defines the "arcfour" ciphers with the text mentioned below: > >>> """ > >>> The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. > >>> The Arcfour cipher is believed to be compatible with the RC4 cipher > >>> [SCHNEIER]. Arcfour (and RC4) has problems with weak keys, and > >>> should be used with caution. > >>> """ > >>> > >>> The current document updates RFC 4253 Section 6.3 by replacing th etext > >>> above with the following text: > >>> > >>> """ > >>> The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. > >>> The Arcfour cipher is believed to be compatible with the RC4 cipher > >>> [SCHNEIER]. Arcfour (and RC4) is steadily weakening in > cryptographic > >>> strength [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], and > >>> MUST NOT be used. > >>> """ > >>> > >>> 4. IANA Considerations > >>> > >>> There is a reference to 3DES i think should be removed. In > >>> addition, IANA cannot be required to update RFCs. IANA is assigned to > update > >>> the SSH registries. With [IANA] being an informational reference to > >>> https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml, > I > >>> would propose the following text : > >>> > >>> The IANA is requested to update the Encryption Algorithm Name Registry > >>> of the Secure Shell (SSH) Protocol Parameters [IANA]. The Registration > >>> procedure is IETF Review which is achieved by this document. The > registry > >>> should be updated as follows: > >>> > >>> Encryption Algorithm Name Reference Note > >>> arcfour [RFC-TBD] > >>> arcfour128 [RFC-TBD] > >>> arcfour256 [RFC-TBD] > >>> > >>> > >>> Where TBD is the RFC number assigned to the document. > >>> > >>> > >>> > >> > > > > > > _______________________________________________ > > Curdle mailing list > > Curdle@ietf.org > > https://www.ietf.org/mailman/listinfo/curdle > > > > _______________________________________________ > Curdle mailing list > Curdle@ietf.org > https://www.ietf.org/mailman/listinfo/curdle > > --000000000000fb28a3057300ee20 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I think that should= be fine now - I can see that we both of us has approved the link. Thanks f= or updating the document! Let us know if you encounter any issues!

Yours,
Daniel

On Thu, Aug 9, 2018 at 7:06 AM,= Loganaden Velvindron <logan@hackers.mu> wrote:
Please find attached the revised xml file for rev 07, = with the
feedback received.

I'm going to upload once the chairs clear this:
https://datatracker.ietf.org/submit/status/971= 72/



On Tue, Jul 17, 2018 at 9:58 PM, Daniel Migault
<d= aniel.migault@ericsson.com> wrote:
> Hi,
>
> We would like to thank Loganaden Velvindron for volunteering to co-aut= hor
> and move the draft forward.
>
> Yours,
> Daniel
>
> On Fri, Jul 6, 2018 at 5:13 PM, Daniel Migault <daniel.migault@ericsson.com>
> wrote:
>>
>> Hi,
>>
>> We would like to move the draft to the IESG, however, the draft ha= s not
>> been updated to address the comments received on the mailing list.= We have
>> privately contacted the author 3 times with the email address prov= ided to
>> the draft, but we did not receive any response. The purpose of thi= s email is
>> to first try to contact the author of draft via another channel an= d
>> understand if he has any plan to move the draft forward. In additi= on, we
>> would also like to see if there is any interest by some members of= the group
>> to co-author the draft and move the draft forward. For those inter= ested in
>> co-authoring the draft, please contact us privately.
>>
>> Our goal is to have all drafts - that is the two remaining drafts = in WGLC
>> - submitted by end of august.
>>
>> Yours,
>> Rich and Daniel
>>
>> On Tue, May 15, 2018 at 1:00 PM, Daniel Migault
>> <daniel.migault@= ericsson.com> wrote:
>>>
>>> Hi,
>>>
>>> Please find my review for draft-ietf-curdle-rc4-die-die-d= ie-06 [1]. I
>>> have also proposed text, so please comment the review in the m= ail. I am
>>> willing to start a WGLC as soon as the draft is being updated.=
>>>
>>> Yours,
>>> Daniel
>>>
>>>
>>> [1] https://tools.ietf.= org/html/draft-ietf-curdle-rc4-die-die-die-06
>>>
>>>
>>> RFC-Editor:
>>>
>>> I personally find the ton of the sentence a bit aggressive, th= us I would
>>> remove it or just leave the RFC reference.
>>>
>>> """
>>> Non-ASCII characters are allowed in RFCs as per RFC 7997.
>>> """
>>>
>>> I see deprecation and move to historic status as very similar = to
>>> draft-ietf-curdle-des-des-des-die-die-die-05 and I assume= that is correct.
>>>
>>> Abstract:
>>>
>>> The sentence below is a bit hard to parse.
>>> ""
>>> and formally obsoletes and moves to
>>>=C2=A0 =C2=A0 Historic RFC 4345.
>>> ""
>>>
>>> I would propose instead:
>>>
>>> """
>>> This document deprecates RC4 in Secure Shell (SSH).=C2=A0 Ther= efore, this
>>>=C2=A0 =C2=A0 document updates RFC 4253, and moves to Historic = RFC 4345.
>>> """
>>>
>>> 1. Introduction
>>>
>>>
>>> """
>>> RC4 is broken""
>>> """
>>>
>>> Although English is not my main language, it sounds a bit abru= pt to me
>>> and it might be preferred to sue something around the lines of=
>>> draft-ietf-curdle-des-des-des-die-die-die-05:
>>>
>>> RC4 encryption is steadily weakening in cryptographic strength= , and the
>>> deprecation process should be begun for their use in SSH.
>>>
>>>
>>> It seems to me that sections 1, 2 3 could be merged. I would p= ropose the
>>> following text. I am providing comments in <mglt></mg= lt>.
>>>
>>>
>>>
>>> 1. Introduction
>>>
>>>
>>> The usage of RC4 suites ( also designated as arcfour ) for SSH= are
>>> specified in RFC 4253 and RFC 4345. RFC 4253 specifies the all= ocation of the
>>> "arcfour" cipher for SSH. RFC 4345 specifies and all= ocates the the
>>> "arcfour-128" and "arcfour-256" ciphers fo= r SSH.
>>>
>>> RC4 encryption is steadily weakening in cryptographic strength=
>>> [RFC7457][draft-ietf-curdle-des-des-des-die-die-die-05], = and the deprecation
>>> process should be begun for their use in Secure Shell (SSH) [R= FC4253].
>>> Accordingly, RFC 4253 is updated to note the deprecation of th= e RC4 ciphers
>>> and RFC 4345 is moved to Historic as all ciphers it specifies = MUST NOT be
>>> used.
>>>
>>> <mglt>I believe that this document is very closed to
>>> [draft-ietf-curdle-des-des-des-die-die-die-05] and as suc= h a reference to it
>>> should be mentioned. </mglt>
>>>
>>>
>>> 2.=C2=A0 Requirements Notation
>>>
>>>=C2=A0 The key words "MUST", "MUST NOT", &q= uot;REQUIRED", "SHALL", "SHALL NOT",
>>> "SHOULD", "SHOULD NOT", "RECOMMENDED&= quot;, "MAY", and "OPTIONAL" in this
>>> document are to be interpreted as described in BCP 14 [RFC2119= , RFC8174]
>>> when, and only when, they appear in all capitals, as shown her= e.
>>>
>>> 3. Updates to RFC 4253
>>>
>>> RFC 4253 is updated to prohibit arcfour's use in SSH.
>>>
>>> <mglt>
>>> """
>>> The last sentence of the paragraph on RC4 (called "arcfou= r"
>>>=C2=A0 =C2=A0 in [RFC4253]) in Section 6.3 of [RFC4253]
>>> """
>>>
>>> I believe that it might be clearer to quote the text as it is = not easy to
>>> locate it. I would propose the text below. </mglt>
>>>
>>> RFC 4253 allocate the "arcfour" cipher in Section 6.= 3 by defining a list
>>> of defined ciphers where the "arcfour" cipher appear= s as optional as
>>> mentioned below:
>>>
>>> """
>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0arcfour=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 OPTIONAL=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the ARCFOUR stream cipher=
>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 with a 128-bit key
>>> """
>>>
>>> The current document updates the status of the "arcfour&q= uot; ciphers in the
>>> list of RFC 4253 Section 6.3 by moving it from OPTIONAL to MUS= T NOT.
>>>
>>> """
>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0arcfour=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 MUST NOT=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the ARCFOUR stream cipher=
>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 with a 128-bit key
>>> """
>>>
>>> RFC 4253 defines the "arcfour" ciphers with the text= mentioned below:
>>> """
>>>=C2=A0 =C2=A0 The "arcfour" cipher is the Arcfour str= eam cipher with 128-bit keys.
>>>=C2=A0 =C2=A0 The Arcfour cipher is believed to be compatible w= ith the RC4 cipher
>>>=C2=A0 =C2=A0 [SCHNEIER].=C2=A0 Arcfour (and RC4) has problems = with weak keys, and
>>>=C2=A0 =C2=A0 should be used with caution.
>>> """
>>>
>>> The current document updates RFC 4253 Section 6.3 by replacing= th etext
>>> above with the following text:
>>>
>>> """
>>>=C2=A0 =C2=A0 The "arcfour" cipher is the Arcfour str= eam cipher with 128-bit keys.
>>>=C2=A0 =C2=A0 The Arcfour cipher is believed to be compatible w= ith the RC4 cipher
>>>=C2=A0 =C2=A0 [SCHNEIER].=C2=A0 Arcfour (and RC4) is steadily w= eakening in cryptographic
>>> strength [RFC7457][draft-ietf-curdle-des-des-des-die-die-= die-05], and
>>>=C2=A0 =C2=A0 MUST NOT be used.
>>> """
>>>
>>> 4. IANA Considerations
>>>
>>> <mglt>There is a reference to 3DES i think should be rem= oved. In
>>> addition, IANA cannot be required to update RFCs. IANA is assi= gned to update
>>> the SSH registries. With [IANA] being an informational referen= ce to
>>> https://www.iana.or= g/assignments/ssh-parameters/ssh-parameters.xhtml,=C2=A0 I >>> would propose the following text :</mglt>
>>>
>>> The IANA is requested to update the Encryption Algorithm Name= =C2=A0 Registry
>>> of the Secure Shell (SSH) Protocol Parameters [IANA]. The Regi= stration
>>> procedure is IETF Review which is achieved by this document. T= he registry
>>> should be updated as follows:
>>>
>>> Encryption Algorithm Name=C2=A0 =C2=A0 =C2=A0Reference=C2=A0 = =C2=A0 =C2=A0Note
>>> arcfour=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [RFC-TBD]
>>> arcfour128=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0[RFC-TBD]
>>> arcfour256=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0[RFC-TBD]
>>>
>>>
>>> Where TBD is the RFC number assigned to the document.
>>>
>>>
>>>
>>
>
>
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org
> https://www.ietf.org/mailman/listinfo/curdle
>

_______________________________________________
Curdle mailing list
Curdle@ietf.org
https://www.ietf.org/mailman/listinfo/curdle

--000000000000fb28a3057300ee20-- From nobody Thu Aug 9 07:58:16 2018 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D7D21130DE9; Thu, 9 Aug 2018 07:58:13 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.83.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: curdle@ietf.org Message-ID: <153382669373.28832.13517374138866210921@ietfa.amsl.com> Date: Thu, 09 Aug 2018 07:58:13 -0700 Archived-At: Subject: [Curdle] I-D Action: draft-ietf-curdle-rc4-die-die-die-07.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Aug 2018 14:58:15 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the CURves, Deprecating and a Little more Encryption WG of the IETF. Title : Deprecating RC4 in Secure Shell (SSH) Authors : Luis Camara Loganaden Velvindron Filename : draft-ietf-curdle-rc4-die-die-die-07.txt Pages : 3 Date : 2018-07-22 Abstract: This document deprecates RC4 in Secure Shell (SSH). Therefore, this document updates RFC 4253, and moves to Historic RFC 4345. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-curdle-rc4-die-die-die/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-curdle-rc4-die-die-die-07 https://datatracker.ietf.org/doc/html/draft-ietf-curdle-rc4-die-die-die-07 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-curdle-rc4-die-die-die-07 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Aug 9 08:19:30 2018 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 225EA130E0E; Thu, 9 Aug 2018 08:19:23 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.83.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: curdle@ietf.org Message-ID: <153382796309.28611.7101122523616377657@ietfa.amsl.com> Date: Thu, 09 Aug 2018 08:19:23 -0700 Archived-At: Subject: [Curdle] I-D Action: draft-ietf-curdle-rc4-die-die-die-08.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Aug 2018 15:19:24 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the CURves, Deprecating and a Little more Encryption WG of the IETF. Title : Deprecating RC4 in Secure Shell (SSH) Authors : Luis Camara Loganaden Velvindron Filename : draft-ietf-curdle-rc4-die-die-die-08.txt Pages : 5 Date : 2018-08-09 Abstract: This document deprecates RC4 in Secure Shell (SSH). Therefore, this document updates [RFC4253], and formally obsoletes and moves to Historic [RFC4345]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-curdle-rc4-die-die-die/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-curdle-rc4-die-die-die-08 https://datatracker.ietf.org/doc/html/draft-ietf-curdle-rc4-die-die-die-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-curdle-rc4-die-die-die-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Aug 10 04:59:03 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF82F130DE5 for ; Fri, 10 Aug 2018 04:59:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOoprs-c_MfC for ; Fri, 10 Aug 2018 04:58:59 -0700 (PDT) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9F6D126DBF for ; Fri, 10 Aug 2018 04:58:58 -0700 (PDT) Received: by mail-it0-x230.google.com with SMTP id v71-v6so2263589itb.3 for ; Fri, 10 Aug 2018 04:58:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VWPBPLHXsBKsW6rLY1r582ONpUQDip0VPUa8BnzFLQw=; b=C3UmQrRysKYsfGgbl8fndawUYdK779DZIGFFzR3u5e/HpCg54n0g9kQtFa8gOZ41AA 0JC+ZVmuiwJW+h5OtnzRemk2InVzPywm+2GV/oaFXkRqtCXLuJLzfxaRaHp2nsMPfkpH KVmg3XVKs/xbTX7pgsGpEsdYgzJD5kEJ28xqfL3qRUCUhxahciuLgdLbyL0FpZdqnAMl 2Fprf246Gg89ZMCaUpGOGz8hFxqeTfJ6gnY/uXnLHuKjY12eqmikYdKD3j0YAo15cZnr SogfrCuf/XGHzRefcqt+OQbiEhViPm4AHIckLinqlHS7EDsuH1BgZSRWemvK2aolsci4 wTbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=VWPBPLHXsBKsW6rLY1r582ONpUQDip0VPUa8BnzFLQw=; b=WkHerBX4EfgMaGSf8Cj32X5XiNzQxXl//9B2emmRdRqbEHUfXzkYWvS4FLV+jPgiCj Trwiy3bZK/vb/9iM/px16Jl+WEAprza/mAPz4evKAIhHqlxTkuOfnpYtHXL4RW+iZcqE 5cPpUZ88MkdYdyhdXDaShKkYKJNbMk/152IzBAKygDVwyed1ONolQYUhTnqeXyLy5eRK kocCOEMptf1XQXaN0D62I0ZJb7ZOb1iCy/K0EVEqBt3bUYVfEoUYeFG6vwSdMRhPtofQ DnmBn4nTeysxYyRTpprA3AhQd4AyWNbvNnxp7BcIDH5XNCClxvDzev8Ul5iyukbUJ5Kb px+Q== X-Gm-Message-State: AOUpUlFhi6XQn7nODCzEULB87E+ON2R3Mg7eTEyny5kL4zQhBXUCV7ao 8csfIQI8N/EPCYyH26rGAbEiNy2eeQPYeDtimG4= X-Google-Smtp-Source: AA+uWPwzuneT2NTxPTS2Jt+SymJwdwxkOmUqRj6iApuzAOGgIB165HRJdYuXjYrLfU4OEfmgMbQsSjf066EpvSdGw2A= X-Received: by 2002:a02:4a0a:: with SMTP id k10-v6mr5181375jab.134.1533902338107; Fri, 10 Aug 2018 04:58:58 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:5e47:0:0:0:0:0 with HTTP; Fri, 10 Aug 2018 04:58:57 -0700 (PDT) In-Reply-To: References: <153052153971.27909.10469976224660738011@ietfa.amsl.com> <83201.1530913429@eng-mail01.juniper.net> From: Loganaden Velvindron Date: Fri, 10 Aug 2018 15:58:57 +0400 Message-ID: To: Daniel Migault Cc: "Mark D. Baushke" , curdle Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Curdle] I-D Action: draft-ietf-curdle-ssh-ed25519-ed448-01.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 11:59:02 -0000 On Mon, Aug 6, 2018 at 7:53 PM, Daniel Migault wrote: > Hi, > > In addition to Mark's comment, please find my review of the document. > Comments are indicative, so you may find better ways to address them than > what I suggest. Please update the next version by the end of August. > > Yours, > Daniel > > > > > > > Ed25519 and Ed 448 public key algorithms for the Secure Shell (SSH) > protocol > draft-ietf-curdle-ssh-ed25519-ed448-01 > > [...] > 1. Introduction > > Secure Shell (SSH) [RFC4251] is a secure remote-login protocol. It > provides for an extensible variety of public key algorithms for > identifying servers and users to one another. Ed25519 [RFC8032] is a > digital signature system. OpenSSH 6.5 [OpenSSH-6.5] introduced > support for using Ed25519 for server and user authentication. > Compatible support for Ed25519 has since been added to other SSH > implementations. Ed448 [RFC8032] is another digital signature > system. > > > I am reading the sentence "Compatible support" as variants, and a such the > current document may describe on eor the other variant. I am not sure the > Ed448 sentence adds much information. I would rather propose the following > wording: > > OLD: > OpenSSH 6.5 [OpenSSH-6.5] introduced > support for using Ed25519 for server and user authentication. > Compatible support for Ed25519 has since been added to other SSH > implementations. Ed448 [RFC8032] is another digital signature > system. > > NEW: > > OpenSSH 6.5 [OpenSSH-6.5] introduced > support for using Ed25519 for server and user authentication and was then > followed by other implementations. > > > This document describes the method implemented by OpenSSH and others, > and formalizes its use of the name "ssh-ed25519". Additionally, it > also describes the use of Ed448 and formalizes its use of the name > "ssh-ed448". > > [TO BE REMOVED: Please send comments on this draft to > curdle@ietf.org.] > > 2. Conventions Used in This Document > 3. Public Key Algorithm > 4. Public Key Format > 5. Signature Algorithm > 6. Signature Format > 7. Verification Algorithm > 8. SSHFP DNS resource records > > > The main purpose of this section is the IANA registration for the "SSHFP RR > Types for public > key algorithms" registry. I would thus start the section as follows: > > Usage and generation of SSHFP DNS resource record is described in RFC 4255. > The generation of SSHFP resource records for "ssh-ed25519" keys is described > in [RFC7479]. This section illustrates the generation of SSHFP resource > records for "ssh-ed448" keys and the document specifies the corresponding > Ed448 code point to the "SSHFP RR Types for public key algorithms" IANA > registry. > > > The generation of SSHFP resource records for "ssh-ed25519" keys is > described in [RFC7479].. > > The generation of SSHFP resource records for "ssh-ed448" keys is > described as follows. > > > > > > Harris & Velvindron Expires January 3, 2019 [Page 3] > > Internet-Draft Ed25519 for SSH July 2018 > > > the SSHFP Resource Record for the Ed448 public key with SHA-256 > fingerprint would be example be: ssh.hackers.mu IN SSHFP 5 2 ( > a87f1b687ac0e57d2a081a2f2826723 34d90ed316d2b818ca9580ea384d924 01 ) > > > probably having the DNS in a figure would ease the reading. > I believe it would also be nice to have the key used to generate the > example. > 5 is 'To be defined' TBD > Maybe it would be good to also indicate that 2 indicates the SHA2 as a > complete example. (rfc6594). > > > 9. IANA Considerations > > This document augments the Public Key Algorithm Names in [RFC4250], > Section 4.6.2 [RFC4250]. > > > IANA is requested to add to the Public Key Algorithm Names registry > [IANA-PKA] with the following entry: > > > It is also better to indicate the type of review. In this case the addition > of the code point requires an IETF review. > > Public Key Algorithm Name Reference > ------------------------- ---------- > ssh-ed25519 This Draft > ssh-ed448 This Draft > > IANA must add the following entry to the "SSHFP RR Types for public > key algorithms" registry: > > is requested may be better ;-) > The registry got a Public Key Format column. This should also be mentioned > in this section. > > > +--------+-------------+------------+ > > | Value | Description | Reference | > > +--------+-------------+------------+ > > | 5 | Ed448 | [this-draft] | > > +--------+-------------+------------+ > > [TO BE REMOVED: This registration should take place at the following > location: parameters.xhtml#ssh-parameters-19>] > > > Maybe that would be good to have the URL as an informational reference. The > reference is for the previous registry ( i.e. Public Key Algorithm name > reference. > > The latest is > https://www.iana.org/assignments/dns-sshfp-rr-parameters/dns-sshfp-rr-parameters.xhtml > > The review is also an IETF review. > > Though 5 is the most likely value. It might be better to have it as TBD and > then suggest TBD to be 5 to the IANA. > > > 10. Security Considerations > > The security considerations in [RFC4251], Section 9 [RFC4251] apply > to all SSH implementations, including those using Ed25519 and Ed448. > > > RFC6469 may also be references here. > Thank you Daniel. I will update the document with your comments. Are you sure that RFC6469 can be referenced as it refers to " RTP Payload Format for DV (IEC 61834) Video". > > The security considerations in [RFC8032], Section 8 [RFC8032] apply > to all uses of Ed25519 and Ed448 including those in SSH. > > > > On Fri, Jul 6, 2018 at 5:43 PM, Mark D. Baushke wrote: >> >> The https://tools.ietf.org/html/draft-ietf-curdle-ssh-ed25519-ed448-01 >> looks better than the -00 revision. >> >> A very minor correction should be the table in section 9 which adds the >> SSHFP RR Type value 5 for "Ed448" for SSHFP RR Types for public key >> algorithms. >> >> I believe there should be an informative reference to [IANA-SSHFP] >> >> https://www.iana.org/assignments/dns-sshfp-rr-parameters/dns-sshfp-rr-parameters.xhtml#dns-sshfp-rr-parameters-1 >> >> which is the IANA.ORG parameter table that should be updated. >> >> Thank you, >> -- Mark >> >> _______________________________________________ >> Curdle mailing list >> Curdle@ietf.org >> https://www.ietf.org/mailman/listinfo/curdle > > > > _______________________________________________ > Curdle mailing list > Curdle@ietf.org > https://www.ietf.org/mailman/listinfo/curdle > From nobody Sun Aug 12 23:43:54 2018 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9C2129619; Sun, 12 Aug 2018 23:43:52 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.83.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: curdle@ietf.org Message-ID: <153414263197.11981.2271405028348839449@ietfa.amsl.com> Date: Sun, 12 Aug 2018 23:43:52 -0700 Archived-At: Subject: [Curdle] I-D Action: draft-ietf-curdle-ssh-ed25519-ed448-02.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2018 06:43:52 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the CURves, Deprecating and a Little more Encryption WG of the IETF. Title : Ed25519 and Ed 448 public key algorithms for the Secure Shell (SSH) protocol Authors : Ben Harris Loganaden Velvindron Filename : draft-ietf-curdle-ssh-ed25519-ed448-02.txt Pages : 6 Date : 2018-08-12 Abstract: This document describes the use of the Ed25519 and Ed448 digital signature algorithm in the Secure Shell (SSH) protocol. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-ed25519-ed448/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-curdle-ssh-ed25519-ed448-02 https://datatracker.ietf.org/doc/html/draft-ietf-curdle-ssh-ed25519-ed448-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-curdle-ssh-ed25519-ed448-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Aug 13 10:27:40 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C338130FF7 for ; Mon, 13 Aug 2018 10:27:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRg2DyTbXKIz for ; Mon, 13 Aug 2018 10:27:28 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA2F9131017 for ; Mon, 13 Aug 2018 10:27:28 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 0B4DBB801F8; Mon, 13 Aug 2018 10:27:21 -0700 (PDT) To: simon@josefsson.org, ietf@augustcellars.com, kaduk@mit.edu, ekr@rtfm.com, daniel.migault@ericsson.com, rsalz@akamai.com X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: conradoplg@gmail.com, curdle@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20180813172721.0B4DBB801F8@rfc-editor.org> Date: Mon, 13 Aug 2018 10:27:21 -0700 (PDT) Archived-At: Subject: [Curdle] [Editorial Errata Reported] RFC8410 (5459) X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2018 17:27:37 -0000 The following errata report has been submitted for RFC8410, "Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5459 -------------------------------------- Type: Editorial Reported by: Conrado Gouvea Section: 7 Original Text ------------- -----BEGIN PRIVATE KEY----- MHICAQEwBQYDK2VwBCIEINTuctv5E1hK1bbY8fdp+K06/nwoy/HU++CXqI9EdVhC oB8wHQYKKoZIhvcNAQkJFDEPDA1DdXJkbGUgQ2hhaXJzgSEAGb9ECWmEzf6FQbrB Z9w7lshQhqowtrbLDFw4rXAxZuE= -----END PRIVATE KEY------ Corrected Text -------------- -----BEGIN PRIVATE KEY----- MHICAQEwBQYDK2VwBCIEINTuctv5E1hK1bbY8fdp+K06/nwoy/HU++CXqI9EdVhC oB8wHQYKKoZIhvcNAQkJFDEPDA1DdXJkbGUgQ2hhaXJzgSEAGb9ECWmEzf6FQbrB Z9w7lshQhqowtrbLDFw4rXAxZuE= -----END PRIVATE KEY----- Notes ----- Should be five dashes instead of six, at the end Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8410 (draft-ietf-curdle-pkix-10) -------------------------------------- Title : Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure Publication Date : August 2018 Author(s) : S. Josefsson, J. Schaad Category : PROPOSED STANDARD Source : CURves, Deprecating and a Little more Encryption Area : Security Stream : IETF Verifying Party : IESG From nobody Mon Aug 13 10:41:36 2018 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE068130E05; Mon, 13 Aug 2018 10:41:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bfBraD1LktZN; Mon, 13 Aug 2018 10:41:32 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74862130E01; Mon, 13 Aug 2018 10:41:32 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id C57F4B80835; Mon, 13 Aug 2018 10:41:24 -0700 (PDT) To: conradoplg@gmail.com, simon@josefsson.org, ietf@augustcellars.com X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: kaduk@mit.edu, iesg@ietf.org, curdle@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20180813174124.C57F4B80835@rfc-editor.org> Date: Mon, 13 Aug 2018 10:41:24 -0700 (PDT) Archived-At: Subject: [Curdle] [Errata Held for Document Update] RFC8410 (5459) X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2018 17:41:34 -0000 The following errata report has been held for document update for RFC8410, "Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5459 -------------------------------------- Status: Held for Document Update Type: Editorial Reported by: Conrado Gouvea Date Reported: 2018-08-13 Held by: Benjamin Kaduk (IESG) Section: 7 Original Text ------------- -----BEGIN PRIVATE KEY----- MHICAQEwBQYDK2VwBCIEINTuctv5E1hK1bbY8fdp+K06/nwoy/HU++CXqI9EdVhC oB8wHQYKKoZIhvcNAQkJFDEPDA1DdXJkbGUgQ2hhaXJzgSEAGb9ECWmEzf6FQbrB Z9w7lshQhqowtrbLDFw4rXAxZuE= -----END PRIVATE KEY------ Corrected Text -------------- -----BEGIN PRIVATE KEY----- MHICAQEwBQYDK2VwBCIEINTuctv5E1hK1bbY8fdp+K06/nwoy/HU++CXqI9EdVhC oB8wHQYKKoZIhvcNAQkJFDEPDA1DdXJkbGUgQ2hhaXJzgSEAGb9ECWmEzf6FQbrB Z9w7lshQhqowtrbLDFw4rXAxZuE= -----END PRIVATE KEY----- Notes ----- Should be five dashes instead of six, at the end -------------------------------------- RFC8410 (draft-ietf-curdle-pkix-10) -------------------------------------- Title : Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure Publication Date : August 2018 Author(s) : S. Josefsson, J. Schaad Category : PROPOSED STANDARD Source : CURves, Deprecating and a Little more Encryption Area : Security Stream : IETF Verifying Party : IESG From nobody Wed Aug 15 11:29:30 2018 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C10131078; Wed, 15 Aug 2018 11:29:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: rsalz@akamai.com, curdle@ietf.org, curdle-chairs@ietf.org, ekr@rtfm.com X-Test-IDTracker: no X-IETF-IDTracker: 6.83.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153435776686.3194.9528707811748997616.idtracker@ietfa.amsl.com> Date: Wed, 15 Aug 2018 11:29:26 -0700 Archived-At: Subject: [Curdle] curdle - Not having a session at IETF 103 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 18:29:29 -0000 Rich Salz, a chair of the curdle working group, indicated that the curdle working group does not plan to hold a session at IETF 103. This message was generated and sent by the IETF Meeting Session Request Tool. From nobody Mon Aug 20 23:06:40 2018 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EEF51130DE9; Mon, 20 Aug 2018 23:06:37 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.83.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: curdle@ietf.org Message-ID: <153483159792.22992.7670418212698694439@ietfa.amsl.com> Date: Mon, 20 Aug 2018 23:06:37 -0700 Archived-At: Subject: [Curdle] I-D Action: draft-ietf-curdle-ssh-ed25519-ed448-03.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.27 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2018 06:06:38 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the CURves, Deprecating and a Little more Encryption WG of the IETF. Title : Ed25519 and Ed448 public key algorithms for the Secure Shell (SSH) protocol Authors : Ben Harris Loganaden Velvindron Filename : draft-ietf-curdle-ssh-ed25519-ed448-03.txt Pages : 6 Date : 2018-08-20 Abstract: This document describes the use of the Ed25519 and Ed448 digital signature algorithm in the Secure Shell (SSH) protocol. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-ed25519-ed448/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-curdle-ssh-ed25519-ed448-03 https://datatracker.ietf.org/doc/html/draft-ietf-curdle-ssh-ed25519-ed448-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-curdle-ssh-ed25519-ed448-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/