| < draft-nslag-mpls-deprecate-md5-02.txt | draft-nslag-mpls-deprecate-md5-03.txt > | |||
|---|---|---|---|---|
| MPLS Working Group L. Andersson | MPLS Working Group L. Andersson | |||
| Internet-Draft Bronze Dragon Consulting | Internet-Draft Bronze Dragon Consulting | |||
| Intended status: Informational S. Bryant | Intended status: Informational S. Bryant | |||
| Expires: September 2, 2018 A. Malis | Expires: March 7, 2019 A. Malis | |||
| Huawei Technologies | Huawei Technologies | |||
| N. Leymann | N. Leymann | |||
| Deutsche Telekom | Deutsche Telekom | |||
| G. Swallow | G. Swallow | |||
| Independent | Independent | |||
| March 1, 2018 | September 3, 2018 | |||
| Deprecating MD5 for LDP | Deprecating MD5 for LDP | |||
| draft-nslag-mpls-deprecate-md5-02.txt | draft-nslag-mpls-deprecate-md5-03 | |||
| Abstract | Abstract | |||
| When the MPLS Label Distribution Protocol (LDP) was specified circa | When the MPLS Label Distribution Protocol (LDP) was specified circa | |||
| 1999, there were very strong requirements that LDP should use a | 1999, there were very strong requirements that LDP should use a | |||
| cryptographic hash function to sign LDP protocol messages. MD5 was | cryptographic hash function to sign LDP protocol messages. MD5 was | |||
| widely used at that time, and was the obvious choices. | widely used at that time, and was the obvious choices. | |||
| However, even when this decision was being taken there were concerns | However, even when this decision was being taken there were concerns | |||
| as to whether MD5 was a strong enough signing option. This | as to whether MD5 was a strong enough signing option. This | |||
| skipping to change at page 2, line 10 ¶ | skipping to change at page 2, line 10 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on September 2, 2018. | This Internet-Draft will expire on March 7, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| End of changes. 4 change blocks. | ||||
| 4 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||