RFC 5811 on SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) Protocol

rfc-editor@rfc-editor.org Fri, 19 March 2010 02:17 UTC

Return-Path: <wwwrun@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 7D1073A6C89; Thu, 18 Mar 2010 19:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[AWL=-0.530, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
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 kr866s9JBMfo; Thu, 18 Mar 2010 19:17:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id E72113A6C81; Thu, 18 Mar 2010 19:17:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7E1B5E075E; Thu, 18 Mar 2010 19:18:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5811 on SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) Protocol
From: rfc-editor@rfc-editor.org
Message-Id: <20100319021804.7E1B5E075E@rfc-editor.org>
Date: Thu, 18 Mar 2010 19:18:04 -0700 (PDT)
Cc: forces@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: Fri, 19 Mar 2010 02:17:53 -0000

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

        
        RFC 5811

        Title:      SCTP-Based Transport Mapping Layer (TML) 
                    for the Forwarding and Control Element 
                    Separation (ForCES) Protocol 
        Author:     J. Hadi Salim, K. Ogawa
        Status:     Standards Track
        Date:       March 2010
        Mailbox:    hadi@mojatatu.com, 
                    ogawa.kentaro@lab.ntt.co.jp
        Pages:      28
        Characters: 61443
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-forces-sctptml-08.txt

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

This document defines the SCTP-based TML (Transport Mapping Layer)
for the ForCES (Forwarding and Control Element Separation) protocol.
It explains the rationale for choosing the SCTP (Stream Control
Transmission Protocol) and also describes how this TML addresses all
the requirements required by and the ForCES protocol.  [STANDARDS 
TRACK]

This document is a product of the Forwarding and Control Element Separation 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
Association Management Solutions, LLC