dccp@ietf.org
[Top] [All Lists]

Re: [dccp] FW: New Version Notification for draft-ietf-dccp-udpencap-01

Subject: Re: [dccp] FW: New Version Notification for draft-ietf-dccp-udpencap-01
From: "Phelan, Tom"
Date: Mon, 28 Jun 2010 10:29:41 -0400
Hi Christian,

Yes, RFC 5762 applies to DCCP-UDP also, with the SDP extensions in the DCCP-UDP 
draft.

Tom P.

> -----Original Message-----
> From: dccp-bounces@xxxxxxxx [mailto:dccp-bounces@xxxxxxxx] On Behalf Of
> Christian Hoene
> Sent: Sunday, June 27, 2010 9:45 AM
> To: Colin Perkins
> Cc: dccp@xxxxxxxx
> Subject: Re: [dccp] FW: New Version Notification for draft-ietf-dccp-
> udpencap-01
> 
> On Sun, 2010-06-27 at 11:33 +0100, Colin Perkins wrote:
> > See RFC 5762 for the standard DCCP case.
> 
> yes, in 5.3 Connection Management I found it. I assume similar is valid
> for DCCP-UDP to reuse a DCCP connection.
> 
> Thanks
>  Christian
> 
> 
> >
> > Colin
> >
> >
> > On 27 Jun 2010, at 11:29, Christian Hoene wrote:
> >
> > > Hello,
> > >
> > > May I ask a question?
> > > For me as a user of DCCP, - I am not an expert in this area - it is
> > > unclear how to set up a bidirectional RTP connection with DCCP-UDP
> > > or DCCP-STD.
> > >
> > > Do two DCCP connections have to be opened - one for each direction
> > > -, or did I missed some RFCs or drafts describing how to negotiate
> > > it with SDP?
> > >
> > > With best regard,
> > >
> > > Christian
> > >
> > >
> > >
> > > ---------------------------------------------------------------
> > > Dr.-Ing. Christian Hoene
> > > Interactive Communication Systems (ICS), University of Tübingen
> > > Sand 13, 72076 Tübingen, Germany, Phone +49 7071 2970532
> > > http://www.net.uni-tuebingen.de/
> > >
> > >
> > > -----Original Message-----
> > > From: dccp-bounces@xxxxxxxx [mailto:dccp-bounces@xxxxxxxx] On Behalf
> > > Of Phelan, Tom
> > > Sent: Thursday, June 24, 2010 9:15 PM
> > > To: dccp@xxxxxxxx
> > > Subject: [dccp] FW: New Version Notification for draft-ietf-dccp-
> > > udpencap-01
> > >
> > > Hi All,
> > >
> > > I've created a new version of dccp-udpencap (see below).  The major
> > > changes are using the standard DCCP header and not allowing the use of
> > > partial checksums.  Feedback appreciated.
> > >
> > > Tom P.
> > >
> > > -----Original Message-----
> > > From: IETF I-D Submission Tool [mailto:idsubmission@xxxxxxxx]
> > > Sent: Thursday, June 24, 2010 3:13 PM
> > > To: Phelan, Tom
> > > Subject: New Version Notification for draft-ietf-dccp-udpencap-01
> > >
> > >
> > > A new version of I-D, draft-ietf-dccp-udpencap-01.txt has been
> > > successfully submitted by Thomas Phelan and posted to the IETF
> > > repository.
> > >
> > > Filename:  draft-ietf-dccp-udpencap
> > > Revision:  01
> > > Title:             Datagram Congestion Control Protocol (DCCP)
> > > Encapsulation in UDP for NAT Traversal (DCCP-UDP)
> > > Creation_date:     2010-06-24
> > > WG ID:             dccp
> > > Number_of_pages: 11
> > >
> > > Abstract:
> > > This document specifies an alternative encapsulation of the Datagram
> > > Congestion Control Protocol (DCCP), referred to as DCCP-UDP.  This
> > > encapsulation will allow DCCP to be carried through the current
> > > generation of Network Address Translation (NAT) middleboxes without
> > > modification of those middleboxes.
> > >
> > <
> > >
> > >
> > > The IETF Secretariat.
> > >
> > >
> >
> >
> >
> 
> 

<Prev in Thread] Current Thread [Next in Thread>