RFC 5595 on The Datagram Congestion Control Protocol (DCCP) Service Codes

rfc-editor@rfc-editor.org Thu, 17 September 2009 23:07 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F413E28C0F0; Thu, 17 Sep 2009 16:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.584
X-Spam-Level:
X-Spam-Status: No, score=-16.584 tagged_above=-999 required=5 tests=[AWL=0.415, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dk9-LDj18Ogo; Thu, 17 Sep 2009 16:07:38 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 100C03A6B36; Thu, 17 Sep 2009 16:07:38 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id A56633256F0; Thu, 17 Sep 2009 16:08:02 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5595 on The Datagram Congestion Control Protocol (DCCP) Service Codes
From: rfc-editor@rfc-editor.org
Message-Id: <20090917230802.A56633256F0@bosco.isi.edu>
Date: Thu, 17 Sep 2009 16:08:02 -0700
Cc: dccp@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2009 23:07:39 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5595

        Title:      The Datagram Congestion Control Protocol 
                    (DCCP) Service Codes 
        Author:     G. Fairhurst
        Status:     Standards Track
        Date:       September 2009
        Mailbox:    gorry@erg.abdn.ac.uk
        Pages:      19
        Characters: 44803
        Updates:    RFC4340

        I-D Tag:    draft-ietf-dccp-serv-codes-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5595.txt

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).  This document updates the specification provided in RFC
4340.  [STANDARDS TRACK]

This document is a product of the Datagram Congestion Control Protocol Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute