[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-tuexen-tsvwg-sctp-padding) 00 01 02 RFC 4820

Network Working Group                                          M. Tuexen
Internet-Draft                        Muenster Univ. of Applied Sciences
Intended status: Standards Track                              R. Stewart
Expires: March 29, 2007                                           P. Lei
                                                     Cisco Systems, Inc.
                                                      September 25, 2006


                  Padding Chunk and Parameter for SCTP
                  draft-ietf-tsvwg-sctp-padding-01.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on March 29, 2007.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This document defines a padding chunk and a padding parameter and
   describes the required receiver side procedures.  The padding chunk
   is used to pad an SCTP packet to an arbitrary size.  The padding
   parameter is used to pad an SCTP INIT chunk to an arbitrary size.





Tuexen, et al.           Expires March 29, 2007                 [Page 1]

Internet-Draft    Padding Chunk and Parameter for SCTP    September 2006


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Padding Chunk (PAD) . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Padding Parameter (PAD) . . . . . . . . . . . . . . . . . . . . 4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
     5.1.  A New Chunk Type  . . . . . . . . . . . . . . . . . . . . . 5
     5.2.  A New Parameter Type  . . . . . . . . . . . . . . . . . . . 5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . . . 5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 6
   Intellectual Property and Copyright Statements  . . . . . . . . . . 7





































Tuexen, et al.           Expires March 29, 2007                 [Page 2]

Internet-Draft    Padding Chunk and Parameter for SCTP    September 2006


1.  Introduction

   This document defines a padding chunk and a padding parameter and
   describes the required receiver side procedures.  The padding chunk
   is used to pad an SCTP packet to an arbitrary size.  The padding
   parameter is used to pad an SCTP INIT chunk to an arbitrary size.
   The PAD chunk can be used for path MTU discovery.


2.  Conventions

   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL", when they appear in this document, are to be interpreted
   as described in RFC2119 [1].


3.  Padding Chunk (PAD)

   This chunk is used to pad an SCTP packet to an arbitrary size.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Type = 0x84   |   Flags=0     |             Length            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   \                         Padding Data                          /
   /                                                               \
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                 Figure 1

   Type: 1 byte (unsigned integer)
      This value MUST be set to 0x84 for all PAD-chunks.

   Flags: 1 byte (unsigned integer)
      Set to zero on transmit and ignored on receipt.

   Length: 2 bytes (unsigned integer)
      This value holds the length of the Padding Data plus 4.

   Padding Data: n bytes (unsigned integer)
      This holds the Padding Data.  The Padding Data is ignored by the
      receiver.

   The receiver of the PAD chunk MUST discard this chunk and continue
   processing the rest of the chunks in the packet.  Please note that



Tuexen, et al.           Expires March 29, 2007                 [Page 3]

Internet-Draft    Padding Chunk and Parameter for SCTP    September 2006


   this is also the required processing behavior for the PAD chunk when
   it is unknown by the receiver.


4.  Padding Parameter (PAD)

   This parameter is used to pad an INIT chunk to an arbitrary size.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Parameter Type = 0x8005   |       Parameter Length        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   /                                                               /
   \                          Padding Data                         \
   /                                                               /
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                 Figure 2

   Parameter Type: 2 bytes (unsigned integer)
      This value MUST be set to 0x8005.

   Parameter Length: 2 bytes (unsigned integer)
      This value holds the length of the Padding Data plus 4.

   The PAD parameter MAY be included only in the INIT chunk.  It MUST
   NOT be included in any other chunk.  The receiver of the PAD
   parameter MUST silently discard this parameter and continue
   processing the rest of the INIT chunk.  This means that the size of
   the generated COOKIE parameter in the INIT-ACK MUST NOT depend on the
   existence of the PAD parameter in the INIT chunk.  A receiver of a
   PAD parameter MUST NOT include the PAD parameter within any State
   Cookie parameter it generates.


5.  IANA Considerations

   [NOTE to RFC-Editor:

      "RFCXXXX" is to be replaced by the RFC number you assign this
      document.

      The reference to sctp-parameters [3] should be removed from the
      "Normative References" section after the IANA section has been
      removed.

   ]



Tuexen, et al.           Expires March 29, 2007                 [Page 4]

Internet-Draft    Padding Chunk and Parameter for SCTP    September 2006


   This document (RFCXXX) is the reference for all registrations
   described in this section.  All registrations need to be listed in
   the document available at sctp-parameters [3].  The suggested changes
   are described below.

5.1.  A New Chunk Type

   A chunk type for the PAD chunk has to be assigned by IANA.  It is
   suggested to use the value given in Figure 1.  This requires an
   additional line in the "CHUNK TYPES" table of sctp-parameters [3]:

   CHUNK TYPES

   ID Value    Chunk Type                                     Reference
   --------    ----------                                     ---------
   132(0x84)   Padding Chunk (PAD)                            [RFCXXXX]

5.2.  A New Parameter Type

   A parameter type has to be assigned for the PAD parameter by IANA.
   It is suggested to use the values given in Figure 2.  This requires a
   modification in the "CHUNK PARAMETER TYPES" table in sctp-
   parameters [3]: Add a new line to the "INIT Chunk Parameter Types"
   table:

   Chunk Parameter Type                       Value
   --------------------                       -----
   Padding                            32773(0x8005)


6.  Security Considerations

   This document does not add any additional security considerations in
   addition to the ones given in RFC2960 [2].


7.  Acknowledgments

   The authors wish to thank Matthew J. Zekauskas for his invaluable
   comments.


8.  Normative References

   [1]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [2]  Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer,



Tuexen, et al.           Expires March 29, 2007                 [Page 5]

Internet-Draft    Padding Chunk and Parameter for SCTP    September 2006


        H., Taylor, T., Rytina, I., Kalla, M., Zhang, L., and V. Paxson,
        "Stream Control Transmission Protocol", RFC 2960, October 2000.

   [3]  <http://www.iana.org/assignments/sctp-parameters>


Authors' Addresses

   Michael Tuexen
   Muenster Univ. of Applied Sciences
   Stegerwaldstr. 39
   48565 Steinfurt
   Germany

   Email: tuexen@fh-muenster.de


   Randall R. Stewart
   Cisco Systems, Inc.
   4875 Forest Drive
   Suite 200
   Columbia, SC  29206
   USA

   Email: rrs@cisco.com


   Peter Lei
   Cisco Systems, Inc.
   955 Happfield Dr.
   Arlington Heights, IL  60004
   US

   Phone: +1 773 695-8201
   Email: peterlei@cisco.com
















Tuexen, et al.           Expires March 29, 2007                 [Page 6]

Internet-Draft    Padding Chunk and Parameter for SCTP    September 2006


Full Copyright Statement

   Copyright (C) The Internet Society (2006).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Tuexen, et al.           Expires March 29, 2007                 [Page 7]


Html markup produced by rfcmarkup 1.109, available from https://tools.ietf.org/tools/rfcmarkup/