draft-ietf-tram-stun-pmtud-07.txt   draft-ietf-tram-stun-pmtud-08.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: September 4, 2018 Cisco Expires: November 15, 2018 Cisco
March 3, 2018 May 14, 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-07 draft-ietf-tram-stun-pmtud-08
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 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 4, 2018. This Internet-Draft will expire on November 15, 2018.
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
skipping to change at page 2, line 32 skipping to change at page 2, line 32
5. Probe Support Signaling Mechanisms . . . . . . . . . . . . . 10 5. Probe Support Signaling Mechanisms . . . . . . . . . . . . . 10
5.1. Explicit Probe Support Signaling Mechanism . . . . . . . 11 5.1. Explicit Probe Support Signaling Mechanism . . . . . . . 11
5.2. Implicit Probe Support Signaling Mechanism . . . . . . . 11 5.2. Implicit Probe Support Signaling Mechanism . . . . . . . 11
6. STUN Attributes . . . . . . . . . . . . . . . . . . . . . . . 11 6. STUN Attributes . . . . . . . . . . . . . . . . . . . . . . . 11
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 . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . 12 9.1. Normative References . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . 13 9.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. Release Notes . . . . . . . . . . . . . . . . . . . 13 Appendix A. Release Notes . . . . . . . . . . . . . . . . . . . 14
A.1. Modifications between draft-ietf-tram-stun-pmtud-07 and A.1. Modifications between draft-ietf-tram-stun-pmtud-08 and
draft-ietf-tram-stun-pmtud-06 . . . . . . . . . . . . . . 13 draft-ietf-tram-stun-pmtud-07 . . . . . . . . . . . . . . 14
A.2. Modifications between draft-ietf-tram-stun-pmtud-06 and A.2. Modifications between draft-ietf-tram-stun-pmtud-07 and
draft-ietf-tram-stun-pmtud-06 . . . . . . . . . . . . . . 14
A.3. Modifications between draft-ietf-tram-stun-pmtud-06 and
draft-ietf-tram-stun-pmtud-05 . . . . . . . . . . . . . . 14 draft-ietf-tram-stun-pmtud-05 . . . . . . . . . . . . . . 14
A.3. Modifications between draft-ietf-tram-stun-pmtud-05 and A.4. Modifications between draft-ietf-tram-stun-pmtud-05 and
draft-ietf-tram-stun-pmtud-04 . . . . . . . . . . . . . . 14 draft-ietf-tram-stun-pmtud-04 . . . . . . . . . . . . . . 14
A.4. Modifications between draft-ietf-tram-stun-pmtud-04 and A.5. Modifications between draft-ietf-tram-stun-pmtud-04 and
draft-ietf-tram-stun-pmtud-03 . . . . . . . . . . . . . . 14 draft-ietf-tram-stun-pmtud-03 . . . . . . . . . . . . . . 14
A.5. Modifications between draft-ietf-tram-stun-pmtud-03 and A.6. Modifications between draft-ietf-tram-stun-pmtud-03 and
draft-ietf-tram-stun-pmtud-02 . . . . . . . . . . . . . . 14 draft-ietf-tram-stun-pmtud-02 . . . . . . . . . . . . . . 14
A.6. Modifications between draft-ietf-tram-stun-pmtud-02 and A.7. Modifications between draft-ietf-tram-stun-pmtud-02 and
draft-ietf-tram-stun-pmtud-01 . . . . . . . . . . . . . . 15 draft-ietf-tram-stun-pmtud-01 . . . . . . . . . . . . . . 15
A.7. Modifications between draft-ietf-tram-stun-pmtud-01 and A.8. Modifications between draft-ietf-tram-stun-pmtud-01 and
draft-ietf-tram-stun-pmtud-00 . . . . . . . . . . . . . . 15 draft-ietf-tram-stun-pmtud-00 . . . . . . . . . . . . . . 15
A.8. Modifications between draft-ietf-tram-stun-pmtud-00 and A.9. Modifications between draft-ietf-tram-stun-pmtud-00 and
draft-petithuguenin-tram-stun-pmtud-01 . . . . . . . . . 15 draft-petithuguenin-tram-stun-pmtud-01 . . . . . . . . . 15
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- A.10. Modifications between draft-petithuguenin-tram-stun-
pmtud-00 and draft-petithuguenin-behave-stun-pmtud-03 . . 15 pmtud-01 and draft-petithuguenin-tram-stun-pmtud-00 . . . 16
A.11. Modifications between draft-petithuguenin-behave-stun- A.11. Modifications between draft-petithuguenin-tram-stun-
pmtud-03 and draft-petithuguenin-behave-stun-pmtud-02 . . 16 pmtud-00 and draft-petithuguenin-behave-stun-pmtud-03 . . 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 pmtud-03 and draft-petithuguenin-behave-stun-pmtud-02 . . 16
A.13. Modifications between draft-petithuguenin-behave-stun- A.13. Modifications between draft-petithuguenin-behave-stun-
pmtud-01 and draft-petithuguenin-behave-stun-pmtud-00 . . 16 pmtud-02 and draft-petithuguenin-behave-stun-pmtud-01 . . 16
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16 A.14. Modifications between draft-petithuguenin-behave-stun-
pmtud-01 and draft-petithuguenin-behave-stun-pmtud-00 . . 17
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 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 Many UDP-based protocols do not 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
designing their own adhoc extension. These probing mechanisms are designing their own adhoc extension. These probing mechanisms are
implemented with Session Traversal Utilities for NAT (STUN), but implemented with Session Traversal Utilities for NAT (STUN), but
their usage is not limited to STUN-based protocols. their usage is not limited to STUN-based protocols.
The STUN usage defined in this document for Path MTU Discovery The STUN usage defined in this document for Path MTU Discovery
(PMTUD) between a client and a server permits proper operations of (PMTUD) between a client and a server permits proper operations of
UDP-based applications in the network. It also simplifies UDP-based applications in the network. It also simplifies
troubleshooting and has multiple other applications across a wide troubleshooting and has multiple other applications across a wide
skipping to change at page 5, line 32 skipping to change at page 5, line 32
|------------------>| |------------------>|
| Report Response | | Report Response |
|<------------------| |<------------------|
| | | |
Figure 2: Complete Probing Example Figure 2: Complete Probing Example
3. Terminology 3. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. When these "OPTIONAL" in this document are to be interpreted as described in BCP
words are not in ALL CAPS (such as "must" or "Must"), they have their 14 [RFC2119][RFC8174] when, and only when, they appear in all
usual English meanings, and are not to be interpreted as RFC 2119 key capitals, as shown here.
words.
4. Probing Mechanisms 4. Probing Mechanisms
The Probing mechanism is used to discover the Path MTU in one The Probing mechanism is used to discover the Path MTU in one
direction only, from the client to the server. direction only, from the client to the server.
Two Probing mechanisms are described, a Simple Probing mechanism and Two Probing mechanisms are described, a Simple Probing mechanism and
a more complete mechanism that can converge quicker and find an a more complete mechanism that can converge quicker and find an
appropriate PMTU in the presence of congestion. Additionally, the appropriate PMTU in the presence of congestion. Additionally, the
Simple Probing mechanism does not require authentication, whereas the Simple Probing mechanism does not require authentication, whereas the
skipping to change at page 7, line 34 skipping to change at page 7, line 34
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 application layer protocols may already have a way of Some application layer protocols may already have a way of
identifying each individual UDP packet, in which case these identifying each individual UDP packet, in which case these
identifiers SHOULD be used in the IDENTIFIERS attribute of the Report identifiers SHOULD be used in the IDENTIFIERS attribute of the Report
Response. While there are other possible packet identification Response. While there are other possible packet identification
schemes, this document describes two different ways to identify a schemes, this document describes two different ways to identify a
specific packet. specific packet when no application layer protocol-specific
identification mechanism is available.
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 8, line 17 skipping to change at page 8, line 18
Then the client sends the Probe Indication to the server over UDP Then the client sends the Probe Indication to the server over UDP
with the DF bit set. with the DF bit set.
Then the client forms a Report Request by following the rules in Then the client forms a Report Request by following the rules in
[RFC5389] Section 7.1. The Report transaction MUST be authenticated [RFC5389] Section 7.1. The Report transaction MUST be authenticated
to prevent amplification attacks. The client MUST add the to prevent amplification attacks. The client MUST add the
FINGERPRINT attribute so the STUN messages are disambiguated from the FINGERPRINT attribute so the STUN messages are disambiguated from the
other protocol packets. other protocol packets.
Then the client waits half the RTO, if it is known, or 250 ms after Then the client waits half the RTO after sending the last Probe
sending the last Probe Indication and then sends the Report Request Indication and then sends the Report Request to the server over UDP.
to the server over UDP.
4.2.2. Receiving an ICMP Packet 4.2.2. Receiving an ICMP Packet
If an ICMP packet "Fragmentation needed" is received then this is If an ICMP packet "Fragmentation needed" is received then this is
interpreted as a Probe Failure, as defined in [RFC4821] Section 7.5. interpreted as a Probe Failure, as defined in [RFC4821] Section 7.5.
4.2.3. Receiving a Probe Indication and Report Request 4.2.3. Receiving a Probe Indication and Report Request
A server supporting this specification will keep the identifiers of A server supporting this specification will keep the identifiers of
all packets received in a chronologically ordered list. The packets all packets received in a chronologically ordered list. The packets
skipping to change at page 9, line 31 skipping to change at page 9, line 31
4.2.5. Using Checksums as Packet Identifiers 4.2.5. Using Checksums as Packet Identifiers
When using a checksum as a packet identifier, the client calculates When using a checksum as a packet identifier, the client calculates
the checksum for each packet sent over UDP that is not a STUN Probe the checksum for each packet sent over UDP that is not a STUN Probe
Indication or Request and keeps this checksum in a chronologically Indication or Request and keeps this checksum in a chronologically
ordered list. The client also keeps the checksum of the STUN Probe ordered list. The client also keeps the checksum of the STUN Probe
Indication or Request sent in that same chronologically ordered list. Indication or Request sent in that same chronologically ordered list.
The algorithm used to calculate the checksum is similar to the The algorithm used to calculate the checksum is similar to the
algorithm used for the FINGERPRINT attribute (i.e., the CRC-32 of the algorithm used for the FINGERPRINT attribute (i.e., the CRC-32 of the
payload XOR'ed with the 32-bit value 0x5354554e). payload XOR'ed with the 32-bit value 0x5354554e [ITU.V42.2002]).
For each STUN Probe Indication or Request, the server retrieves the For each STUN Probe Indication or Request, the server retrieves the
STUN FINGERPRINT value. For all other packets, the server calculates STUN FINGERPRINT value. For all other packets, the server calculates
the checksum as described above. It puts these FINGERPRINT and the checksum as described above. It puts these FINGERPRINT and
checksum values in a chronologically ordered list that is sent back checksum values in a chronologically ordered list that is sent back
in the Report Response. in the Report Response.
The contents of the IDENTIFIERS attribute is a list of 4 byte The contents of the IDENTIFIERS attribute is a list of 4 byte
numbers, each using the same encoding that is used for the contents numbers, each using the same encoding that is used for the contents
of the FINGERPRINT attribute. of the FINGERPRINT attribute.
skipping to change at page 12, line 23 skipping to change at page 12, line 23
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
as 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.
Parameters Registry" created by [RFC5389].
8.1. New STUN Methods 8.1. New STUN Methods
This section lists the codepoints for the new STUN methods defined in IANA is requested to add the following methods to the STUN Method
this specification. See Sections Section 4.1 and Section 4.2 for the Registry:
semantics of these new methods.
0xXXX : Probe 0xXXX : Probe
0xXXX : Report 0xXXX : Report
See Sections Section 4.1 and Section 4.2 for the semantics of these
new methods.
8.2. New STUN Attributes 8.2. New STUN Attributes
This document defines the IDENTIFIERS STUN attribute, described in IANA is requested to add the following attributes to the STUN Method
Section 6.1. IANA has allocated the comprehension-required codepoint Registry:
0xXXXX for this attribute.
This document also defines the PMTUD-SUPPORTED STUN attribute, Comprehension-required range (0x0000-0x7FFF):
described in Section 6.2. IANA has allocated the comprehension- 0xXXXX: IDENTIFIERS
optional codepoint 0xXXXX for this attribute.
Comprehension-optional range (0x8000-0xFFFF)
0xXXXX: PMTUD-SUPPORTED
This IDENTIFIERS STUN attribute is defined in Section 6.1, the PMTUD-
SUPPORTED STUN attribute is defined in Section 6.2.
9. References 9. References
9.1. Normative References 9.1. Normative References
[ITU.V42.2002]
International Telecommunications Union, "Error-correcting
Procedures for DCEs Using Asynchronous-to-Synchronous
Conversion", ITU-T Recommendation V.42, 2002.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC4821] Mathis, M. and J. Heffner, "Packetization Layer Path MTU [RFC4821] Mathis, M. and J. Heffner, "Packetization Layer Path MTU
Discovery", RFC 4821, DOI 10.17487/RFC4821, March 2007, Discovery", RFC 4821, DOI 10.17487/RFC4821, March 2007,
<http://www.rfc-editor.org/info/rfc4821>. <http://www.rfc-editor.org/info/rfc4821>.
[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,
DOI 10.17487/RFC5389, October 2008, DOI 10.17487/RFC5389, October 2008,
<http://www.rfc-editor.org/info/rfc5389>. <http://www.rfc-editor.org/info/rfc5389>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <http://www.rfc-editor.org/info/rfc8174>.
9.2. Informative References 9.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-
skipping to change at page 13, line 45 skipping to change at page 14, line 9
[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-07 and draft- A.1. Modifications between draft-ietf-tram-stun-pmtud-08 and draft-
ietf-tram-stun-pmtud-07
o Updates following Spencer's review.
A.2. Modifications between draft-ietf-tram-stun-pmtud-07 and draft-
ietf-tram-stun-pmtud-06 ietf-tram-stun-pmtud-06
o Updates following Shepherd review. o Updates following Shepherd review.
A.2. Modifications between draft-ietf-tram-stun-pmtud-06 and draft- A.3. 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.3. Modifications between draft-ietf-tram-stun-pmtud-05 and draft- A.4. 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.4. Modifications between draft-ietf-tram-stun-pmtud-04 and draft- A.5. 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.5. Modifications between draft-ietf-tram-stun-pmtud-03 and draft- A.6. 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 17 skipping to change at page 15, line 33
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.6. Modifications between draft-ietf-tram-stun-pmtud-02 and draft- A.7. 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.7. Modifications between draft-ietf-tram-stun-pmtud-01 and draft- A.8. 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.8. Modifications between draft-ietf-tram-stun-pmtud-00 and draft- A.9. 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.9. Modifications between draft-petithuguenin-tram-stun-pmtud-01 and A.10. 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.10. Modifications between draft-petithuguenin-tram-stun-pmtud-00 and A.11. 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.11. Modifications between draft-petithuguenin-behave-stun-pmtud-03 A.12. 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.12. Modifications between draft-petithuguenin-behave-stun-pmtud-02 A.13. 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.13. Modifications between draft-petithuguenin-behave-stun-pmtud-01 A.14. 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, Brandon Williams, Tirumaleswar Reddy, Ram Mohan R, Simon Perreault, Brandon Williams,
and Tolga Asveren for their review comments, suggestions and Tolga Asveren, and Spencer Dawkins for their review comments,
questions that helped to improve this document. suggestions and 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. 41 change blocks. 
62 lines changed or deleted 82 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/