headers
Internet-Drafts | 16 Jun 2008 19:15
Picon
Favicon

I-D Action:draft-ietf-dccp-serv-codes-06.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           : The DCCP Service Code
	Author(s)       : G. Fairhurst
	Filename        : draft-ietf-dccp-serv-codes-06.txt
	Pages           : 26
	Date            : 2008-06-16

This document describes the usage of Service Codes by the Datagram 
Congestion Control Protocol, RFC 4340. It motivates the setting of a 
Service Code by applications. Service Codes provide a method to 
identify the intended service/application to process a DCCP 
connection request. This provides improved flexibility in the use and 
assignment of port numbers for connection multiplexing. The use of a 
DCCP Service Code can also enable more explicit coordination of 
services with middleboxes (e.g. network address translators and 
firewalls). It updates the specification provided in RFC 4340.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dccp-serv-codes-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment (draft-ietf-dccp-serv-codes-06.txt): message/external-body, 70 bytes
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 19 Jun 2008 10:00
Picon
Favicon

I-D Action:draft-ietf-dccp-simul-open-01.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           : DCCP Simultaneous-Open Technique to Facilitate NAT/Middlebox Traversal
	Author(s)       : G. Fairhurst, G. Renker
	Filename        : draft-ietf-dccp-simul-open-01.txt
	Pages           : 26
	Date            : 2008-06-17

This document specifies an update to the Datagram Congestion Control
Protocol (DCCP), a connection-oriented and datagram-based transport
protocol.

The update assists DCCP applications which need to communicate
through one or more middleboxes (e.g.  Network Address Translators or
firewalls), where establishing necessary middlebox state requires
peering endpoints to initiate communication in a near-simultaneous
manner.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dccp-simul-open-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment (draft-ietf-dccp-simul-open-01.txt): message/external-body, 70 bytes
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gorry Fairhurst | 19 Jun 2008 10:43
Picon
Picon

Reminder of WG Agenda and I-D submission deadlines.


This is a reminder of the cut-off dates for draft submission for IETF-72 
(Dublin):

- Monday, July 7th for -00s by 17:00 PDT (24:00 UTC/GMT)

- Monday, July 14th for -01+ by 17:00 PDT (24:00 UTC/GMT)

Refer here for complete details:
http://www.ietf.org/meetings/72/72-cutoff_dates.html

Please use the ID submission tool to upload your document:
https://datatracker.ietf.org/idst/upload.cgi

It will be published very quickly this way, but I will note that it does 
not check for ALL the nits, so it's a good idea to run idnits before 
submitting:
http://tools.ietf.org/tools/idnits/

Also, please send me a note if you want agenda time to present an ID. I 
have started building the agenda for DCCP.  Agenda time preference will 
be given to WG items. Please TELL the chairs as soon as possible if you 
would like to add/change anything for the Agenda (or will not be able to 
present this meeting). The current DRAFT agenda is at:
http://www.ietf.org/proceedings/08jul/agenda/dccp.txt

Best wishes,

Gorry & Tom
(DCCP Co-Chairs)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gorry Fairhurst | 20 Jun 2008 15:07
Picon
Picon

Re: draft-ietf-dccp-serv-codes-06 - Treatment of SC in Ipsec SPD ???

I received this email from Alfred (cc'ed above), who has kindly allowed 
me to forwrad this to the dccp list. It asks about the use of IPsec 
SPD's with DCCP Service Codes... an interesting question - do others 
have ideas on how this should be handled in this I-D?

Gorry

Alfred � wrote:
> Hello,
> I have a few comments on the Internet-Draft authored by you,
>     draft-ietf-dccp-serv-codes-06.
> 
> (1)  IPsec
> 
> Recently, a new proposal to add the GRE key as a new selector
> to IPsec has been posted (draft-deng-ipsec-gre-key-ts-00).
> 
> This has reminded me of once having noticed a potential need
> for adding the DCCP service code as a selector to IPsec as well.
> Quickly looking for possibly related I-Ds, I stumbled over your I-D.
> 
> Section 5.3 of your I-D deals with IPsec, but it seems to be
> incompatible in spirit with the description of the intended
> use of the DCCP Service Code in the remainder of the document.
> 
> I envision that the DCCP Service Code might be an appropriate
> selector for the IPsec SPD, in order to initiate specific IPsec
> treatment (IPsec SA setup) based on the needs to protect such
> service.  Conforming to the rules posed in your draft, the SAD
> subsequently would have to use the 'classical' transport selector
(Continue reading)

Permalink | Reply | 2 comments |
headers
Phelan, Tom | 23 Jun 2008 15:12

Re: WG status for draft-fairhurst-tsvwg-dccp-qs

Hi All,

So, while the hum for this didn't reach deafening levels :-), we did
receive several messages in support and none against.  Therefore we'll
make this a working group item.  Gorry will have a name-change update
out anytime now.

Tom P.

> -----Original Message-----
> From: Sally Floyd [mailto:sallyfloyd <at> mac.com]
> Sent: Thursday, May 22, 2008 12:14 AM
> To: Phelan, Tom
> Cc: dccp <at> ietf.org
> Subject: Re: [dccp] WG status for draft-fairhurst-tsvwg-dccp-qs
> 
> > In Philly, we decided to poll the mailing list for support in making
> > draft-fairhurst-tsvwg-dccp-qs a working group draft (Quick Start for
> > DCCP).  So this is the poll :-).
> >
> > Please actively respond with positive, negative or don't care
opinions
> > -- I can't hear you hum around the world :-).
> 
> I would be in favor of adopting this as a working group item.
> 
> - Sally
> http://www.icir.org/floyd/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lars Eggert | 24 Jun 2008 13:30
Picon
Gravatar

Re: draft-ietf-dccp-serv-codes-06 - Treatment of SC in Ipsec SPD ???

Hi,

On 2008-6-20, at 16:07, ext Gorry Fairhurst wrote:
> I received this email from Alfred (cc'ed above), who has kindly  
> allowed me to forwrad this to the dccp list. It asks about the use  
> of IPsec SPD's with DCCP Service Codes... an interesting question -  
> do others have ideas on how this should be handled in this I-D?

Alfred raises a good point. But I don't think this document is the  
place to describe an extension to IPsec to allow DCCP selectors. We'd  
need a SEC area document for that.

Coincidentally, Pasi is likely to charter an IPSECME (IPsec  
maintenance and minor extensions) WG in the near future, which IMO  
would be the perfect home for this.

Lars

PS: Hm, I wonder if we ever got SCTP selectors specified for IPsec. If  
not, that'd be another thing for this new WG.
Permalink | Reply | 1 comment |
headers
Gorry Fairhurst | 24 Jun 2008 13:54
Picon
Picon

Re: draft-ietf-dccp-serv-codes-06 - Treatment of SC in Ipsec SPD ???

Thanks, it could be interesting to explore if future IPsec maintenance 
should consider this as a possible extension.

So, do people think there is anything that needs to be added to the 
current wording in section 5.3 "Interactions with IPsec" of this document?

   "IPsec uses port numbers to perform access control in transport mode
    [RFC4301].  Security policies can define port-specific access control
    (PROTECT, BYPASS, DISCARD), as well as port-specific algorithms and
    keys. Similarly, firewall policies allow or block traffic based on
    port numbers.

    Use of port numbers in IPsec selectors and firewalls may assume that
    the numbers correspond to Well Known services. It is useful to note
    that there is no such requirement; any service may run on any port,
    subject to mutual agreement between the endpoint hosts.  Use of the
    Service Code may interfere with this assumption both within IPsec and
    in other firewall systems, but it does not add a new vulnerability.
    New implementations of IPsec and firewall systems may interpret the
    Service Code when implementing policy rules, but should not rely on
    either port numbers or Service Codes to indicate a specific service.

    This is not an issue for IPsec because the entire DCCP header and
    payload are protected by all IPsec modes. None of the DCCP header is
    protected by application-layer security, e.g., DTLS [ID.DTLS], so
    again this is not an issue [RFC4347]."

Gorry

Lars Eggert wrote:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gorry Fairhurst | 25 Jun 2008 14:53
Picon
Picon

New working group work item: draft-ietf-dccp-quickstart-00


We'd like to thank Tom for his email, and I am now pleased to issue a 
new revision of my previous draft with a name change to reflect this now
being adopted as WG work item:

"draft-ietf-dccp-quickstart-00"
has replaced
"draft-fairhurst-tsvwg-dccp-qs-03"

Tom will be shepherding the IETF process for this draft - as a co-chair, 
I can't run the process on my own drafts -  so please address all 
procedural questions to him.

By the way, we're still VERY keen to here of any experience or comments 
that may help to improve this draft,

Arjuna and Gorry
Permalink | Reply | 0 comments |
headers
Internet-Drafts | 25 Jun 2008 15:00
Picon
Favicon

I-D Action:draft-ietf-dccp-quickstart-00.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           : Quick-Start for Datagram Congestion Control Protocol (DCCP)
	Author(s)       : G. Fairhurst
	Filename        : draft-ietf-dccp-quickstart-00.txt
	Pages           : 19
	Date            : 2008-06-25

This document specifies the use of the Quick-Start mechanism by the 
Datagram Congestion Control Protocol (DCCP).  DCCP is a transport 
protocol that allows the transmission of congestion-controlled, 
unreliable datagrams.  DCCP is intended for applications such as 
streaming media, Internet telephony, and on-line games.  In DCCP, an 
application has a choice of congestion control mechanisms, each 
specified by a Congestion Control Identifier (CCID). This document 
specifies general procedures applicable to all DCCP CCIDs and 
specific procedures for the use of Quick-Start with DCCP CCID-2 and 
CCID-3.  Quick-Start enables a DCCP sender to cooperate with any 
Quick-Start routers along the end-to-end path to determine an 
allowed sending rate at the start and, at times, in the middle of a 
DCCP connection (e.g., after an idle or application-limited period).  
The present specification is provided for use in controlled 
environments, and not as a mechanism that would be intended or 
appropriate for ubiquitous deployment in the global Internet.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dccp-quickstart-00.txt

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

Permalink | Reply | 0 comments |

Gmane