draft-ietf-tram-stun-pmtud-06.txt   draft-ietf-tram-stun-pmtud-07.txt 
TRAM M. Petit-Huguenin TRAM M. Petit-Huguenin
Internet-Draft Impedance Mismatch Internet-Draft Impedance Mismatch
Intended status: Standards Track G. Salgueiro Intended status: Standards Track G. Salgueiro
Expires: March 5, 2018 Cisco Expires: September 4, 2018 Cisco
September 1, 2017 March 3, 2018
Path MTU Discovery Using Session Traversal Utilities for NAT (STUN) Path MTU Discovery Using Session Traversal Utilities for NAT (STUN)
draft-ietf-tram-stun-pmtud-06 draft-ietf-tram-stun-pmtud-07
Abstract Abstract
This document describes a Session Traversal Utilities for NAT (STUN) This document describes a Session Traversal Utilities for NAT (STUN)
Usage for Path MTU Discovery (PMTUD) between a client and a server. Usage for Path MTU Discovery (PMTUD) between a client and a server.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 http://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 March 5, 2018. This Internet-Draft will expire on September 4, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
(http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
skipping to change at page 2, line 36 skipping to change at page 2, line 36
6.1. IDENTIFIERS . . . . . . . . . . . . . . . . . . . . . . . 11 6.1. IDENTIFIERS . . . . . . . . . . . . . . . . . . . . . . . 11
6.2. PMTUD-SUPPORTED . . . . . . . . . . . . . . . . . . . . . 11 6.2. PMTUD-SUPPORTED . . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8.1. New STUN Methods . . . . . . . . . . . . . . . . . . . . 12 8.1. New STUN Methods . . . . . . . . . . . . . . . . . . . . 12
8.2. New STUN Attributes . . . . . . . . . . . . . . . . . . . 12 8.2. New STUN Attributes . . . . . . . . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
9.1. Normative References . . . . . . . . . . . . . . . . . . 12 9.1. Normative References . . . . . . . . . . . . . . . . . . 12
9.2. Informative References . . . . . . . . . . . . . . . . . 13 9.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. Release Notes . . . . . . . . . . . . . . . . . . . 13 Appendix A. Release Notes . . . . . . . . . . . . . . . . . . . 13
A.1. Modifications between draft-ietf-tram-stun-pmtud-06 and A.1. Modifications between draft-ietf-tram-stun-pmtud-07 and
draft-ietf-tram-stun-pmtud-05 . . . . . . . . . . . . . . 13 draft-ietf-tram-stun-pmtud-06 . . . . . . . . . . . . . . 13
A.2. Modifications between draft-ietf-tram-stun-pmtud-05 and A.2. Modifications between draft-ietf-tram-stun-pmtud-06 and
draft-ietf-tram-stun-pmtud-05 . . . . . . . . . . . . . . 14
A.3. Modifications between draft-ietf-tram-stun-pmtud-05 and
draft-ietf-tram-stun-pmtud-04 . . . . . . . . . . . . . . 14 draft-ietf-tram-stun-pmtud-04 . . . . . . . . . . . . . . 14
A.3. Modifications between draft-ietf-tram-stun-pmtud-04 and A.4. Modifications between draft-ietf-tram-stun-pmtud-04 and
draft-ietf-tram-stun-pmtud-03 . . . . . . . . . . . . . . 14 draft-ietf-tram-stun-pmtud-03 . . . . . . . . . . . . . . 14
A.4. Modifications between draft-ietf-tram-stun-pmtud-03 and A.5. Modifications between draft-ietf-tram-stun-pmtud-03 and
draft-ietf-tram-stun-pmtud-02 . . . . . . . . . . . . . . 14 draft-ietf-tram-stun-pmtud-02 . . . . . . . . . . . . . . 14
A.5. Modifications between draft-ietf-tram-stun-pmtud-02 and A.6. Modifications between draft-ietf-tram-stun-pmtud-02 and
draft-ietf-tram-stun-pmtud-01 . . . . . . . . . . . . . . 15 draft-ietf-tram-stun-pmtud-01 . . . . . . . . . . . . . . 15
A.6. Modifications between draft-ietf-tram-stun-pmtud-01 and A.7. Modifications between draft-ietf-tram-stun-pmtud-01 and
draft-ietf-tram-stun-pmtud-00 . . . . . . . . . . . . . . 15 draft-ietf-tram-stun-pmtud-00 . . . . . . . . . . . . . . 15
A.7. Modifications between draft-ietf-tram-stun-pmtud-00 and A.8. Modifications between draft-ietf-tram-stun-pmtud-00 and
draft-petithuguenin-tram-stun-pmtud-01 . . . . . . . . . 15 draft-petithuguenin-tram-stun-pmtud-01 . . . . . . . . . 15
A.8. Modifications between draft-petithuguenin-tram-stun-
pmtud-01 and draft-petithuguenin-tram-stun-pmtud-00 . . . 15
A.9. Modifications between draft-petithuguenin-tram-stun- A.9. Modifications between draft-petithuguenin-tram-stun-
pmtud-01 and draft-petithuguenin-tram-stun-pmtud-00 . . . 15
A.10. Modifications between draft-petithuguenin-tram-stun-
pmtud-00 and draft-petithuguenin-behave-stun-pmtud-03 . . 15 pmtud-00 and draft-petithuguenin-behave-stun-pmtud-03 . . 15
A.10. Modifications between draft-petithuguenin-behave-stun-
pmtud-03 and draft-petithuguenin-behave-stun-pmtud-02 . . 15
A.11. Modifications between draft-petithuguenin-behave-stun- A.11. Modifications between draft-petithuguenin-behave-stun-
pmtud-02 and draft-petithuguenin-behave-stun-pmtud-01 . . 16 pmtud-03 and draft-petithuguenin-behave-stun-pmtud-02 . . 16
A.12. Modifications between draft-petithuguenin-behave-stun- A.12. Modifications between draft-petithuguenin-behave-stun-
pmtud-02 and draft-petithuguenin-behave-stun-pmtud-01 . . 16
A.13. Modifications between draft-petithuguenin-behave-stun-
pmtud-01 and draft-petithuguenin-behave-stun-pmtud-00 . . 16 pmtud-01 and draft-petithuguenin-behave-stun-pmtud-00 . . 16
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
The Packetization Layer Path MTU Discovery (PMTUD) specification The Packetization Layer Path MTU Discovery (PMTUD) specification
[RFC4821] describes a method to discover the Path MTU but does not [RFC4821] describes a method to discover the Path MTU but does not
describe a practical protocol to do so with UDP. describe a practical protocol to do so with UDP.
Not all UDP-based protocols implement the Path MTU discovery Not all UDP-based protocols implement the Path MTU discovery
mechanism described in [RFC4821]. These protocols can make use of mechanism described in [RFC4821]. These protocols can make use of
the probing mechanisms described in this document instead of the probing mechanisms described in this document instead of
skipping to change at page 6, line 12 skipping to change at page 6, line 12
server side of both the Simple Probing mechanism (Section 4.1) and server side of both the Simple Probing mechanism (Section 4.1) and
the Complete Probing mechanism (Section 4.2). the Complete Probing mechanism (Section 4.2).
Implementations supporting this specification MUST implement the Implementations supporting this specification MUST implement the
client side of the Complete Probing mechanism. They MAY implement client side of the Complete Probing mechanism. They MAY implement
the client side of the Simple Probing mechanism. the client side of the Simple Probing mechanism.
4.1. Simple Probing Mechanism 4.1. Simple Probing Mechanism
The Simple Probing mechanism is implemented by sending a Probe The Simple Probing mechanism is implemented by sending a Probe
Request with a PADDING [RFC5780] attribute and the DF bit set over Request with a PADDING [RFC5780] attribute over UDP with the DF bit
UDP. A router on the path to the server can reject this request with set in the IP header. A router on the path to the server can reject
an ICMP message or drop it. this request with an ICMP message or drop it.
4.1.1. Sending a Probe Request 4.1.1. Sending a Probe Request
A client forms a Probe Request by using the Probe Method and A client forms a Probe Request by using the Probe Method and
following the rules in Section 7.1 of [RFC5389]. following the rules in Section 7.1 of [RFC5389].
The Probe transaction MUST be authenticated if the Simple Probing The Probe transaction MUST be authenticated if the Simple Probing
mechanism is used in conjunction with the Implicit Probing Support mechanism is used in conjunction with the Implicit Probing Support
mechanism described in Section 5.2. If not, the Probe transaction mechanism described in Section 5.2. If not, the Probe transaction
MAY be authenticated. MAY be authenticated.
skipping to change at page 7, line 18 skipping to change at page 7, line 18
[RFC5389]. If a response is received this is interpreted as a Probe [RFC5389]. If a response is received this is interpreted as a Probe
Success, as defined in [RFC4821] Section 7.6.1. If an ICMP packet Success, as defined in [RFC4821] Section 7.6.1. If an ICMP packet
"Fragmentation needed" is received then this is interpreted as a "Fragmentation needed" is received then this is interpreted as a
Probe Failure, as defined in [RFC4821] Section 7.6.2. If the Probe Probe Failure, as defined in [RFC4821] Section 7.6.2. If the Probe
transaction times out, then this is interpreted as a Probe transaction times out, then this is interpreted as a Probe
Inconclusive, as defined in [RFC4821] Section 7.6.4. Inconclusive, as defined in [RFC4821] Section 7.6.4.
4.2. Complete Probing Mechanism 4.2. Complete Probing Mechanism
The Complete Probing mechanism is implemented by sending one or more The Complete Probing mechanism is implemented by sending one or more
Probe Indications with a PADDING attribute and the DF bit set over Probe Indications with a PADDING attribute over UDP with the DF bit
UDP followed by a Report Request to the same server. A router on the set in the IP header followed by a Report Request to the same server.
path to the server can reject this Indication with an ICMP message or A router on the path to the server can reject this Indication with an
drop it. The server keeps a chronologically ordered list of ICMP message or drop it. The server keeps a chronologically ordered
identifiers for all packets received (including retransmitted list of identifiers for all packets received (including retransmitted
packets) and sends this list back to the client in the Report packets) and sends this list back to the client in the Report
Response. The client analyzes this list to find which packets were Response. The client analyzes this list to find which packets were
not received. Because UDP packets do not contain an identifier, the not received. Because UDP packets do not contain an identifier, the
Complete Probing mechanism needs a way to identify each packet Complete Probing mechanism needs a way to identify each packet
received. received.
Some protocols may already have a way of identifying each individual Some application layer protocols may already have a way of
UDP packet, in which case these identifiers SHOULD be used in the identifying each individual UDP packet, in which case these
IDENTIFIERS attribute of the Report Response. While there are other identifiers SHOULD be used in the IDENTIFIERS attribute of the Report
possible packet identification schemes, this document describes two Response. While there are other possible packet identification
different ways to identify a specific packet. schemes, this document describes two different ways to identify a
specific packet.
In the first packet identification mechanism, the server computes a In the first packet identification mechanism, the server computes a
checksum over each packet received and sends back to the sender the checksum over each packet received and sends back to the sender the
list of checksums ordered chronologically. The client compares this list of checksums ordered chronologically. The client compares this
list to its own list of checksums. list to its own list of checksums.
In the second packet identification mechanism, the client prepends In the second packet identification mechanism, the client prepends
the UDP data with a header that provides a sequence number. The the UDP data with a header that provides a sequence number. The
server sends back the chronologically ordered list of sequence server sends back the chronologically ordered list of sequence
numbers received that the client then compares with its own list. numbers received that the client then compares with its own list.
skipping to change at page 12, line 15 skipping to change at page 12, line 15
7. Security Considerations 7. Security Considerations
The PMTUD mechanism described in this document does not introduce any The PMTUD mechanism described in this document does not introduce any
specific security considerations beyond those described in [RFC4821]. specific security considerations beyond those described in [RFC4821].
The attacks described in Section 11 of [RFC4821] apply equally to the The attacks described in Section 11 of [RFC4821] apply equally to the
mechanism described in this document. mechanism described in this document.
The Simple Probing mechanism may be used without authentication The Simple Probing mechanism may be used without authentication
because this usage by itself cannot trigger an amplification attack because this usage by itself cannot trigger an amplification attack
because the Probe Response is smaller than the Probe Request. An as the Probe Response is smaller than the Probe Request. An
unauthenticated Simple Probing mechanism cannot be used in unauthenticated Simple Probing mechanism cannot be used in
conjunction with the Implicit Probing Support Signaling mechanism in conjunction with the Implicit Probing Support Signaling mechanism in
order to prevent amplification attacks. order to prevent amplification attacks.
8. IANA Considerations 8. IANA Considerations
This specification defines two new STUN methods and two new STUN This specification defines two new STUN methods and two new STUN
attributes. IANA added these new protocol elements to the "STUN attributes. IANA added these new protocol elements to the "STUN
Parameters Registry" created by [RFC5389]. Parameters Registry" created by [RFC5389].
skipping to change at page 13, line 45 skipping to change at page 13, line 45
[RFC5780] MacDonald, D. and B. Lowekamp, "NAT Behavior Discovery [RFC5780] MacDonald, D. and B. Lowekamp, "NAT Behavior Discovery
Using Session Traversal Utilities for NAT (STUN)", Using Session Traversal Utilities for NAT (STUN)",
RFC 5780, DOI 10.17487/RFC5780, May 2010, RFC 5780, DOI 10.17487/RFC5780, May 2010,
<http://www.rfc-editor.org/info/rfc5780>. <http://www.rfc-editor.org/info/rfc5780>.
Appendix A. Release Notes Appendix A. Release Notes
This section must be removed before publication as an RFC. This section must be removed before publication as an RFC.
A.1. Modifications between draft-ietf-tram-stun-pmtud-06 and draft- A.1. Modifications between draft-ietf-tram-stun-pmtud-07 and draft-
ietf-tram-stun-pmtud-06
o Updates following Shepherd review.
A.2. Modifications between draft-ietf-tram-stun-pmtud-06 and draft-
ietf-tram-stun-pmtud-05 ietf-tram-stun-pmtud-05
o Nits. o Nits.
o Restore missing changelog for previous version. o Restore missing changelog for previous version.
A.2. Modifications between draft-ietf-tram-stun-pmtud-05 and draft- A.3. Modifications between draft-ietf-tram-stun-pmtud-05 and draft-
ietf-tram-stun-pmtud-04 ietf-tram-stun-pmtud-04
o Modifications following Brandon Williams review. o Modifications following Brandon Williams review.
A.3. Modifications between draft-ietf-tram-stun-pmtud-04 and draft- A.4. Modifications between draft-ietf-tram-stun-pmtud-04 and draft-
ietf-tram-stun-pmtud-03 ietf-tram-stun-pmtud-03
o Modifications following Simon Perreault and Brandon Williams o Modifications following Simon Perreault and Brandon Williams
reviews. reviews.
A.4. Modifications between draft-ietf-tram-stun-pmtud-03 and draft- A.5. Modifications between draft-ietf-tram-stun-pmtud-03 and draft-
ietf-tram-stun-pmtud-02 ietf-tram-stun-pmtud-02
o Add new Overview of Operations section with ladder diagrams. o Add new Overview of Operations section with ladder diagrams.
o Authentication is mandatory for the Complete Probing mechanism, o Authentication is mandatory for the Complete Probing mechanism,
optional for the Simple Probing mechanism. optional for the Simple Probing mechanism.
o All the ICE specific text moves to a separate draft to be o All the ICE specific text moves to a separate draft to be
discussed in the ICE WG. discussed in the ICE WG.
skipping to change at page 15, line 9 skipping to change at page 15, line 17
o Each usage of this specification must the format of the o Each usage of this specification must the format of the
IDENTIFIERS attribute contents. IDENTIFIERS attribute contents.
o Better define the implicit signaling mechanism. o Better define the implicit signaling mechanism.
o Extend the Security Consideration section. o Extend the Security Consideration section.
o Tons of nits. o Tons of nits.
A.5. Modifications between draft-ietf-tram-stun-pmtud-02 and draft- A.6. Modifications between draft-ietf-tram-stun-pmtud-02 and draft-
ietf-tram-stun-pmtud-01 ietf-tram-stun-pmtud-01
o Cleaned up references. o Cleaned up references.
A.6. Modifications between draft-ietf-tram-stun-pmtud-01 and draft- A.7. Modifications between draft-ietf-tram-stun-pmtud-01 and draft-
ietf-tram-stun-pmtud-00 ietf-tram-stun-pmtud-00
o Added Security Considerations Section. o Added Security Considerations Section.
o Added IANA Considerations Section. o Added IANA Considerations Section.
A.7. Modifications between draft-ietf-tram-stun-pmtud-00 and draft- A.8. Modifications between draft-ietf-tram-stun-pmtud-00 and draft-
petithuguenin-tram-stun-pmtud-01 petithuguenin-tram-stun-pmtud-01
o Adopted by WG - Text unchanged. o Adopted by WG - Text unchanged.
A.8. Modifications between draft-petithuguenin-tram-stun-pmtud-01 and A.9. Modifications between draft-petithuguenin-tram-stun-pmtud-01 and
draft-petithuguenin-tram-stun-pmtud-00 draft-petithuguenin-tram-stun-pmtud-00
o Moved some Introduction text to the Probing Mechanism section. o Moved some Introduction text to the Probing Mechanism section.
o Added cross-reference to the other two STUN troubleshooting o Added cross-reference to the other two STUN troubleshooting
mechanism drafts. mechanism drafts.
o Updated references. o Updated references.
o Added Gonzalo Salgueiro as co-author. o Added Gonzalo Salgueiro as co-author.
A.9. Modifications between draft-petithuguenin-tram-stun-pmtud-00 and A.10. Modifications between draft-petithuguenin-tram-stun-pmtud-00 and
draft-petithuguenin-behave-stun-pmtud-03 draft-petithuguenin-behave-stun-pmtud-03
o General refresh for republication. o General refresh for republication.
A.10. Modifications between draft-petithuguenin-behave-stun-pmtud-03 A.11. Modifications between draft-petithuguenin-behave-stun-pmtud-03
and draft-petithuguenin-behave-stun-pmtud-02 and draft-petithuguenin-behave-stun-pmtud-02
o Changed author address. o Changed author address.
o Changed the IPR to trust200902. o Changed the IPR to trust200902.
A.11. Modifications between draft-petithuguenin-behave-stun-pmtud-02 A.12. Modifications between draft-petithuguenin-behave-stun-pmtud-02
and draft-petithuguenin-behave-stun-pmtud-01 and draft-petithuguenin-behave-stun-pmtud-01
o Defined checksum and sequential numbers as possible packet o Defined checksum and sequential numbers as possible packet
identifiers. identifiers.
o Updated the reference to RFC 5389 o Updated the reference to RFC 5389
o The FINGERPRINT attribute is now mandatory. o The FINGERPRINT attribute is now mandatory.
o Changed the delay between Probe indication and Report request to o Changed the delay between Probe indication and Report request to
be RTO/2 or 50 milliseconds. be RTO/2 or 50 milliseconds.
o Added ICMP packet processing. o Added ICMP packet processing.
o Added Full-Stop Timeout detection. o Added Full-Stop Timeout detection.
o Stated that Binding request with PMTUD-SUPPORTED does not start o Stated that Binding request with PMTUD-SUPPORTED does not start
the PMTUD process if already started. the PMTUD process if already started.
A.12. Modifications between draft-petithuguenin-behave-stun-pmtud-01 A.13. Modifications between draft-petithuguenin-behave-stun-pmtud-01
and draft-petithuguenin-behave-stun-pmtud-00 and draft-petithuguenin-behave-stun-pmtud-00
o Removed the use of modified STUN transaction but shorten the o Removed the use of modified STUN transaction but shorten the
retransmission for the simple probing mechanism. retransmission for the simple probing mechanism.
o Added a complete probing mechanism. o Added a complete probing mechanism.
o Removed the PADDING-RECEIVED attribute. o Removed the PADDING-RECEIVED attribute.
o Added release notes. o Added release notes.
Acknowledgements Acknowledgements
Thanks to Eilon Yardeni, Geir Sandbakken, Paal-Erik Martinsen, Thanks to Eilon Yardeni, Geir Sandbakken, Paal-Erik Martinsen,
Tirumaleswar Reddy, Ram Mohan R, Simon Perreault, and Brandon Tirumaleswar Reddy, Ram Mohan R, Simon Perreault, Brandon Williams,
Williams for their review comments, suggestions and questions that and Tolga Asveren for their review comments, suggestions and
helped to improve this document. questions that helped to improve this document.
Special thanks to Dan Wing, who supported this document since its Special thanks to Dan Wing, who supported this document since its
first publication back in 2008. first publication back in 2008.
Authors' Addresses Authors' Addresses
Marc Petit-Huguenin Marc Petit-Huguenin
Impedance Mismatch Impedance Mismatch
Email: marc@petit-huguenin.org Email: marc@petit-huguenin.org
 End of changes. 35 change blocks. 
51 lines changed or deleted 59 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/