[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipsec
Subject:    Re: [IPsec] [Editorial Errata Reported] RFC7296 (4930)
From:       Yoav Nir <ynir.ietf () gmail ! com>
Date:       2017-02-08 19:14:15
Message-ID: 6E43ECDE-CB69-4EF5-8FB7-49C46D5A6DF6 () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


This is factually true, and it dates back to RFC 5996 (but not 4306).

It obviously doesn't confuse anyone, so I guess it should be either "held for \
document update"

Yoav

> On 8 Feb 2017, at 17:55, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC7296,
> "Internet Key Exchange Protocol Version 2 (IKEv2)".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7296&eid=4930
> 
> --------------------------------------
> Type: Editorial
> Reported by: Nikolai Malykh <nmalykh@gmail.com>
> 
> Section: 3.16
> 
> Original Text
> -------------
> Note that since IKE passes an indication of initiator identity in the
> first message in the IKE_AUTH exchange, the responder SHOULD NOT send
> EAP Identity requests.  The initiator MAY, however, respond to such
> requests if it receives them.
> 
> Corrected Text
> --------------
> 
> 
> Notes
> -----
> The last sentence of this section contains unnecessary repetition written above \
> (the last sentence in description of Type field). 
> 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.
> 
> --------------------------------------
> RFC7296 (draft-kivinen-ipsecme-ikev2-rfc5996bis-04)
> --------------------------------------
> Title               : Internet Key Exchange Protocol Version 2 (IKEv2)
> Publication Date    : October 2014
> Author(s)           : C. Kaufman, P. Hoffman, Y. Nir, P. Eronen, T. Kivinen
> Category            : INTERNET STANDARD
> Source              : IP Security Maintenance and Extensions
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec


["signature.asc" (signature.asc)]

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYm24HAAoJELhJCxUKWMyZMfcIAKBrEVAhcuhb28fY37JNlS1H
HeIIrn+NqXONl2P3vRD9TX9xvbcOkxyenO/79wDB85p42vP77XF49xib1wOTG9BB
JOyS5H32OE5wHwH9ZUKJjbV1X1nvZjgSvrz/M3oWk26RBwb1S9vCOTxM1sOazFDF
q+oFZuBI6OVEqWAc+Ez0YQaRyfrOwZRkCBYo8PzMoCSVChzmB+gtOm7r+negIYkY
eoxD04JlwUwYSwnjlPs2EbpdQuia/4c28/85FkzH+hZJw9KbXzZ1zPYmPVRq4EpI
UEIbvfL2KsggbKvCKOJOgW0DqnBwzXPX9jwSSV/BpoztDEiK0nBSFeWgMqFi3Wk=
=+9j8
-----END PGP SIGNATURE-----


_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec


[prev in list] [next in list] [prev in thread] [next in thread]