[rfc-dist] RFC 4820 on Padding Chunk and Parameter for the Stream Control Transmission Protocol (SCTP)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Thu Mar 29 17:57:49 PDT 2007

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

        RFC 4820

        Title:      Padding Chunk and Parameter for 
                    the Stream Control Transmission Protocol (SCTP) 
        Author:     M. Tuexen, R. Stewart,
                    P. Lei
        Status:     Standards Track
        Date:       March 2007
        Mailbox:    tuexen at fh-muenster.de, 
                    rrs at cisco.com, 
                    peterlei at cisco.com
        Pages:      6
        Characters: 11597
        Updates/Obsoletes/SeeAlso:   None

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

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

This document defines a padding chunk and a padding parameter and
describes the required receiver side procedures.  The padding chunk
is used to pad a Stream Control Transmission Protocol (SCTP) packet
to an arbitrary size.  The padding parameter is used to pad an SCTP
INIT chunk to an arbitrary size.  [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 

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list