headers
internet-drafts | 25 Jun 2012 19:52
Picon
Favicon

I-D Action: draft-ietf-dccp-udpencap-11.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Datagram Congestion Control Protocol Working Group of the IETF.

	Title           : Datagram Congestion Control Protocol (DCCP) Encapsulation for NAT Traversal (DCCP-UDP)
	Author(s)       : Tom Phelan
                          Godred Fairhurst
                          Colin Perkins
	Filename        : draft-ietf-dccp-udpencap-11.txt
	Pages           : 20
	Date            : 2012-06-25

Abstract:
   This document specifies an alternative encapsulation of the Datagram
   Congestion Control Protocol (DCCP), referred to as DCCP-UDP.  This
   encapsulation allows DCCP to be carried through the current
   generation of Network Address Translation (NAT) middleboxes without
   modification of those middleboxes.  This document also updates the
   SDP information for DCCP defined in RFC 5762.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dccp-udpencap

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dccp-udpencap-11

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-dccp-udpencap-11

Internet-Drafts are also available by anonymous FTP at:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Carsten Bormann | 26 Jun 2012 00:51
Favicon
Gravatar

Re: I-D Action: draft-ietf-dccp-udpencap-11.txt

Ah, great, I see that you have picked up some (but not all) of my comments.

New nits:

-- What is DCCP-STP?
-- I don't think that RFC 5124 defines the media-field.
   (Did you want to reference 5234 here?)

--
           o  This specification also permits the use of DTLS with the UDP	
 	      transport that encapsulates DCCP packets.  When DTLS is used at	
 	      the encapsulation layer this protects the DCCP headers.  This	
 	      prevents the headers from being inspected or updated by network	
 	      middleboxes (such as firewalls and NAPT).  It also eliminates the	
 	      need for a spearate DTLS handshake for each DCCP connection.

Where does it permit that?
(If this sentence is intended to be normatively define entirely new functionality, it MUST NOT be in the
security considerations.)
How exactly does the definition of the 4-/6-tuples change when you do that?
E.g., what happens if the DTLS epoch changes?

-- spearate

Grüße, Carsten
Permalink | Reply | 0 comments |

Gmane