Re: [Editorial Errata Reported] RFC3931 (3766)

"Carlos Pignataro (cpignata)" <[email protected]> Mon, 28 Oct 2013 17:12:50 +0000
Newsgroups gmane.ietf.l2tpext
Message-ID <[email protected]>
Brian,

Looking at the guidelines at http://www.ietf.org/iesg/statement/errata-processing.html, you are right.

Thanks,

-- Carlos.

On Oct 28, 2013, at 9:25 AM, Brian Haberman <[email protected]> wrote:

> Actually, since it does not impact a reader's ability to parse the
> sentence, I will mark it as Hold For Document Update.
> 
> Regards,
> Brian
> 
> On 10/27/13 10:38 PM, Carlos Pignataro (cpignata) wrote:
>> This seems to be an accurate, yet harmless, editorial nit. I would Verify it as such.
>> 
>> Thanks,
>> 
>> -- Carlos.
>> 
>> On Oct 26, 2013, at 8:37 PM, RFC Errata System <[email protected]> wrote:
>> 
>>> The following errata report has been submitted for RFC3931,
>>> "Layer Two Tunneling Protocol - Version 3 (L2TPv3)".
>>> 
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=3931&eid=3766
>>> 
>>> --------------------------------------
>>> Type: Editorial
>>> Reported by: Chaz Granholm <[email protected]>
>>> 
>>> Section: 8.2.3
>>> 
>>> Original Text
>>> -------------
>>> Further, it is far easier to change a compromised L2TPv3
>>> 
>>>  Cookie than a compromised IP address," and a cryptographically random
>>> 
>>>  [RFC1750] value is far less likely to be discovered by brute-force
>>> 
>>>  attacks compared to an IP address.
>>> 
>>> Corrected Text
>>> --------------
>>> Further, it is far easier to change a compromised L2TPv3
>>> 
>>>  Cookie than a compromised IP address, and a cryptographically random
>>> 
>>>  [RFC1750] value is far less likely to be discovered by brute-force
>>> 
>>>  attacks compared to an IP address.
>>> 
>>> Notes
>>> -----
>>> Erroneous quotation mark.
>>> 
>>> Instructions:
>>> -------------
>>> This errata 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 (IESG)
>>> can log in to change the status and edit the report, if necessary. 
>>> 
>>> --------------------------------------
>>> RFC3931 (draft-ietf-l2tpext-l2tp-base-15)
>>> --------------------------------------
>>> Title               : Layer Two Tunneling Protocol - Version 3 (L2TPv3)
>>> Publication Date    : March 2005
>>> Author(s)           : J. Lau, Ed., M. Townsley, Ed., I. Goyret, Ed.
>>> Category            : PROPOSED STANDARD
>>> Source              : Layer Two Tunneling Protocol Extensions
>>> Area                : Internet
>>> Stream              : IETF
>>> Verifying Party     : IESG
>> 
>

_______________________________________________
L2tpext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/l2tpext
signature.asc (application/pgp-signature, 203 B)
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlJumxEACgkQtfDPGTp3USz/nwCbB4b2VpMlRNk5C0q1Z0r8PS3B
TsIAnjukaVzCSrPYZq4dQKyIF/kngvT1
=LDgv
-----END PGP SIGNATURE-----