RFC 6096 on Stream Control Transmission Protocol (SCTP) Chunk Flags Registration

rfc-editor@rfc-editor.org Wed, 26 January 2011 01:41 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 770EF3A6906; Tue, 25 Jan 2011 17:41:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.006
X-Spam-Level:
X-Spam-Status: No, score=-102.006 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 Yy251nLgtjl9; Tue, 25 Jan 2011 17:41:16 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id CD9B93A68CC; Tue, 25 Jan 2011 17:41:16 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0F445E06FD; Tue, 25 Jan 2011 17:44:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6096 on Stream Control Transmission Protocol (SCTP) Chunk Flags Registration
From: rfc-editor@rfc-editor.org
Message-Id: <20110126014416.0F445E06FD@rfc-editor.org>
Date: Tue, 25 Jan 2011 17:44:16 -0800
Cc: tsvwg@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: Wed, 26 Jan 2011 01:41:17 -0000

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

        
        RFC 6096

        Title:      Stream Control Transmission Protocol (SCTP) 
                    Chunk Flags Registration 
        Author:     M. Tuexen, R. Stewart
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2011
        Mailbox:    tuexen@fh-muenster.de, 
                    randall@lakerest.net
        Pages:      8
        Characters: 15368
        Updates:    RFC4960

        I-D Tag:    draft-ietf-tsvwg-sctp-chunk-flags-02.txt

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

This document defines the procedure for registering chunk flags with
the Internet Assigned Numbers Authority (IANA) for the Stream Control
Transmission Protocol (SCTP).  It updates RFC 4960 and also defines
the IANA registry for contents for currently defined chunk types.  It
does not change SCTP in any other way.  [STANDARDS-TRACK]

This document is a product of the Transport Area Working Group 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