Re: [OSPF] [Editorial Errata Reported] RFC5709 (2989)

["Bhatia, Manav (Manav)" <[e-mail]>]

Yes, the link is incorrect in the HTML version of the RFC. I don't remember giving the URL and don't know how it was inserted in the HTML version. Cant we just fix the HTML page to point to RFC 2328 Appendix D instead of pointing to RFC 5709 Appendix D (which does not even exist!)?

There is no problem with the TXT version of the RFC. 

Cheers, Manav

> -----Original Message-----
> From: RFC Errata System [mailto:[e-mail]] 
> Sent: Tuesday, October 11, 2011 6:21 AM
> To: Bhatia, Manav (Manav); [e-mail]; 
> [e-mail]; [e-mail]; 
> [e-mail]; [e-mail]; [e-mail]; 
> [e-mail]; [e-mail]; 
> [e-mail]; [e-mail]
> Cc: [e-mail]; [e-mail]; [e-mail]
> Subject: [Editorial Errata Reported] RFC5709 (2989)
> 
> 
> The following errata report has been submitted for RFC5709,
> "OSPFv2 HMAC-SHA Cryptographic Authentication".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5709&eid=2989
> 
> --------------------------------------
> Type: Editorial
> Reported by: Dai Wenjie (David Jet) <[e-mail]>
> 
> Section: 3.
> 
> Original Text
> -------------
>    With the additions in this document, the currently valid 
> algorithms    (including mode) for OSPFv2 Cryptographic 
> Authentication include:             Keyed-MD5               
> (defined in RFC 2328, Appendix D)
> 
> Corrected Text
> --------------
>    With the additions in this document, the currently valid 
> algorithms    (including mode) for OSPFv2 Cryptographic 
> Authentication include:             Keyed-MD5               
> (defined in RFC 2328, Appendix D)
> 
> Notes
> -----
> The link 'Appendix D' referenced is incorrect. It is now 
> 'http://tools.ietf.org/html/rfc5709#appendix-D', and it 
> should be 'http://tools.ietf.org/html/rfc2328#appendix-D'. 
> Pay attention to the difference of the numbers in links,please.
> 
> 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. 
> 
> --------------------------------------
> RFC5709 (draft-ietf-ospf-hmac-sha-07)
> --------------------------------------
> Title               : OSPFv2 HMAC-SHA Cryptographic Authentication
> Publication Date    : October 2009
> Author(s)           : M. Bhatia, V. Manral, M. Fanto, R. 
> White, M. Barnes, T. Li, R. Atkinson
> Category            : PROPOSED STANDARD
> Source              : Open Shortest Path First IGP
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG
>