draft-ietf-tram-stun-pmtud-00.txt   draft-ietf-tram-stun-pmtud-01.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: May 8, 2016 Cisco Expires: July 29, 2016 Cisco
November 5, 2015 January 26, 2016
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-00 draft-ietf-tram-stun-pmtud-01
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.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
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 http://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 May 8, 2016. This Internet-Draft will expire on July 29, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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 (http://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
skipping to change at page 2, line 25 skipping to change at page 2, line 25
5.1. Sending the Probe Indications and Report Request . . . . 5 5.1. Sending the Probe Indications and Report Request . . . . 5
5.2. Receiving an ICMP packet . . . . . . . . . . . . . . . . 5 5.2. Receiving an ICMP packet . . . . . . . . . . . . . . . . 5
5.3. Receiving a Probe Indication and Report Request . . . . . 5 5.3. Receiving a Probe Indication and Report Request . . . . . 5
5.4. Receiving a Report Response . . . . . . . . . . . . . . . 6 5.4. Receiving a Report Response . . . . . . . . . . . . . . . 6
5.5. Using Checksum as Packet Identifiers . . . . . . . . . . 6 5.5. Using Checksum as Packet Identifiers . . . . . . . . . . 6
5.6. Using Sequential Numbers as Packet Identifiers . . . . . 6 5.6. Using Sequential Numbers as Packet Identifiers . . . . . 6
6. Probe Support Discovery Mechanisms . . . . . . . . . . . . . 7 6. Probe Support Discovery Mechanisms . . . . . . . . . . . . . 7
6.1. Implicit Mechanism . . . . . . . . . . . . . . . . . . . 7 6.1. Implicit Mechanism . . . . . . . . . . . . . . . . . . . 7
6.2. Probe Support Discovery with TURN . . . . . . . . . . . . 7 6.2. Probe Support Discovery with TURN . . . . . . . . . . . . 7
6.3. Probe Support Discovery with ICE . . . . . . . . . . . . 7 6.3. Probe Support Discovery with ICE . . . . . . . . . . . . 7
7. New STUN Method . . . . . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. New STUN Attributes . . . . . . . . . . . . . . . . . . . . . 8 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8.1. IDENTIFIERS . . . . . . . . . . . . . . . . . . . . . . . 8 8.1. New STUN Methods . . . . . . . . . . . . . . . . . . . . 8
8.2. PMTUD-SUPPORTED . . . . . . . . . . . . . . . . . . . . . 8 8.2. New STUN Attributes . . . . . . . . . . . . . . . . . . . 8
9. Security Considerations . . . . . . . . . . . . . . . . . . . 8 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 10.1. Normative References . . . . . . . . . . . . . . . . . . 9
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 10.2. Informative References . . . . . . . . . . . . . . . . . 9
12.1. Normative References . . . . . . . . . . . . . . . . . . 9 Appendix A. Release Notes . . . . . . . . . . . . . . . . . . . 9
12.2. Informative References . . . . . . . . . . . . . . . . . 9 A.1. Modifications between draft-ietf-tram-stun-pmtud-01 and
Appendix A. Release Notes . . . . . . . . . . . . . . . . . . . 10 draft-ietf-tram-stun-pmtud-00 . . . . . . . . . . . . . . 10
A.1. Modifications between draft-ietf-tram-stun-pmtud-00 and A.2. Modifications between draft-ietf-tram-stun-pmtud-00 and
draft-petithuguenin-tram-stun-pmtud-01 . . . . . . . . . 10 draft-petithuguenin-tram-stun-pmtud-01 . . . . . . . . . 10
A.2. Modifications between draft-petithuguenin-tram-stun-
pmtud-01 and draft-petithuguenin-tram-stun-pmtud-00 . . . 10
A.3. Modifications between draft-petithuguenin-tram-stun- A.3. Modifications between draft-petithuguenin-tram-stun-
pmtud-01 and draft-petithuguenin-tram-stun-pmtud-00 . . . 10
A.4. Modifications between draft-petithuguenin-tram-stun-
pmtud-00 and draft-petithuguenin-behave-stun-pmtud-03 . . 10 pmtud-00 and draft-petithuguenin-behave-stun-pmtud-03 . . 10
A.4. Modifications between draft-petithuguenin-behave-stun-
pmtud-03 and draft-petithuguenin-behave-stun-pmtud-02 . . 10
A.5. Modifications between draft-petithuguenin-behave-stun- A.5. Modifications between draft-petithuguenin-behave-stun-
pmtud-02 and draft-petithuguenin-behave-stun-pmtud-01 . . 10 pmtud-03 and draft-petithuguenin-behave-stun-pmtud-02 . . 10
A.6. Modifications between draft-petithuguenin-behave-stun- A.6. Modifications between draft-petithuguenin-behave-stun-
pmtud-02 and draft-petithuguenin-behave-stun-pmtud-01 . . 10
A.7. Modifications between draft-petithuguenin-behave-stun-
pmtud-01 and draft-petithuguenin-behave-stun-pmtud-00 . . 11 pmtud-01 and draft-petithuguenin-behave-stun-pmtud-00 . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
The Packetization Layer Path MTU Discovery specification [RFC4821] The Packetization Layer Path MTU Discovery specification [RFC4821]
describes a method to discover the path MTU but does not describe a describes a method to discover the path MTU but does not describe a
practical protocol to do so with UDP. practical protocol to do so with UDP.
This document only describes how probing mechanisms are implemented This document only describes how probing mechanisms are implemented
skipping to change at page 8, line 5 skipping to change at page 8, line 5
An ICE [RFC5245] client supporting this STUN usage will add a PMTUD- An ICE [RFC5245] client supporting this STUN usage will add a PMTUD-
SUPPORTED attribute to the Binding Request sent during a connectivity SUPPORTED attribute to the Binding Request sent during a connectivity
check. The ICE server can immediately start to send probes to the check. The ICE server can immediately start to send probes to the
ICE client on reception of a Binding Request with a PMTUD-SUPPORTED ICE client on reception of a Binding Request with a PMTUD-SUPPORTED
attributed. Local candidates receiving Binding Request with the attributed. Local candidates receiving Binding Request with the
PMTUD-SUPPORTED flag must not start PMTUD with the remote candidate PMTUD-SUPPORTED flag must not start PMTUD with the remote candidate
if already done so. The ICE client will then use the Implicit if already done so. The ICE client will then use the Implicit
Mechanism described above to send probes. Mechanism described above to send probes.
7. New STUN Method 7. Security Considerations
This specification defines the following new STUN methods:
0x801 : Probe
0x802 : Report
8. New STUN Attributes
This specification defines the following new STUN attributes: The PMTUD mechanism described in this document does not introduce any
specific security considerations beyond those described in [RFC4821].
0x4001 : IDENTIFIERS The attack described in [RFC4821] applies equally to the mechanism
described in this document.
0xC001 : PMTUD-SUPPORTED 8. IANA Considerations
8.1. IDENTIFIERS This specification defines two new STUN method and two new STUN
attributes. IANA added these new protocol elements to the "STUN
Parameters Registry" created by [RFC5389].
The IDENTIFIERS attribute is used in Report Response. It contains a 8.1. New STUN Methods
list of UDP packet identifiers.
8.2. PMTUD-SUPPORTED This section lists the codepoints for the new STUN methods defined in
this specification. See Sections Section 4 and Section 5 for the
semantics of these new methods.
The PMTUD-SUPPORTED attribute is used in STUN usages and extensions 0xXXX : Probe
to signal the support of this specification. This attribute has no
content.
9. Security Considerations 0xXXX : Report
TBD 8.2. New STUN Attributes
10. IANA Considerations This document defines the IDENTIFIERS STUN attribute, described in
Section 5. IANA has allocated the comprehension-required codepoint
0xXXXX for this attribute.
TBD This document also defines the PMTUD-SUPPORTED STUN attribute,
described in Section 6. IANA has allocated the comprehension-
optional codepoint 0xXXXX for this attribute.
11. Acknowledgements 9. Acknowledgements
Thanks to Eilon Yardeni, Geir Sandbakken and Paal-Erik Martinsen for Thanks to Eilon Yardeni, Geir Sandbakken and Paal-Erik Martinsen for
their review comments, suggestions and questions that helped to their review comments, suggestions and questions that helped to
improve this document. 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.
12. References 10. References
10.1. Normative References
12.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4821] Mathis, M. and J. Heffner, "Packetization Layer Path MTU [RFC4821] Mathis, M. and J. Heffner, "Packetization Layer Path MTU
Discovery", RFC 4821, March 2007. Discovery", RFC 4821, March 2007.
[RFC5389] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing, [RFC5389] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,
"Session Traversal Utilities for NAT (STUN)", RFC 5389, "Session Traversal Utilities for NAT (STUN)", RFC 5389,
October 2008. October 2008.
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT) (ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245, April Traversal for Offer/Answer Protocols", RFC 5245, April
2010. 2010.
12.2. Informative References 10.2. Informative References
[I-D.martinsen-tram-stuntrace] [I-D.martinsen-tram-stuntrace]
Martinsen, P. and D. Wing, "STUN Traceroute", draft- Martinsen, P. and D. Wing, "STUN Traceroute", draft-
martinsen-tram-stuntrace-01 (work in progress), June 2015. martinsen-tram-stuntrace-01 (work in progress), June 2015.
[I-D.martinsen-tram-turnbandwidthprobe] [I-D.martinsen-tram-turnbandwidthprobe]
Martinsen, P., Andersen, T., Salgueiro, G., and M. Petit- Martinsen, P., Andersen, T., Salgueiro, G., and M. Petit-
Huguenin, "Traversal Using Relays around NAT (TURN) Huguenin, "Traversal Using Relays around NAT (TURN)
Bandwidth Probe", draft-martinsen-tram- Bandwidth Probe", draft-martinsen-tram-
turnbandwidthprobe-00 (work in progress), May 2015. turnbandwidthprobe-00 (work in progress), May 2015.
skipping to change at page 10, line 9 skipping to change at page 10, line 5
RFC 5780, May 2010. RFC 5780, May 2010.
[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", RFC 6982, July Code: The Implementation Status Section", RFC 6982, July
2013. 2013.
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-00 and draft- A.1. Modifications between draft-ietf-tram-stun-pmtud-01 and draft-
ietf-tram-stun-pmtud-00
o Added Security Considerations Section.
o Added IANA Considerations Section.
A.2. 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.2. Modifications between draft-petithuguenin-tram-stun-pmtud-01 and A.3. 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.3. Modifications between draft-petithuguenin-tram-stun-pmtud-00 and A.4. 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.4. Modifications between draft-petithuguenin-behave-stun-pmtud-03 and A.5. Modifications between draft-petithuguenin-behave-stun-pmtud-03 and
draft-petithuguenin-behave-stun-pmtud-02 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.5. Modifications between draft-petithuguenin-behave-stun-pmtud-02 and A.6. Modifications between draft-petithuguenin-behave-stun-pmtud-02 and
draft-petithuguenin-behave-stun-pmtud-01 draft-petithuguenin-behave-stun-pmtud-01
o Replaced the transactions identifiers by packet identifiers o Replaced the transactions identifiers by packet identifiers
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.
skipping to change at page 11, line 12 skipping to change at page 11, line 15
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.6. Modifications between draft-petithuguenin-behave-stun-pmtud-01 and A.7. Modifications between draft-petithuguenin-behave-stun-pmtud-01 and
draft-petithuguenin-behave-stun-pmtud-00 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.
 End of changes. 31 change blocks. 
56 lines changed or deleted 61 lines changed or added

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