@techreport{stewart-tsvwg-sctpipv6-01,
    number =    {draft-stewart-tsvwg-sctpipv6-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-stewart-tsvwg-sctpipv6/01/},
    author =    {Randall R. Stewart and Dr. Steve E. Deering},
    title =     {{IPv6 addressing and Stream Control Transmission Protocol}},
    pagetotal = 3,
    year =      2002,
    month =     apr,
    day =       11,
    abstract =  {Stream Control Transmission Protocol {[}RFC2960{]} provides transparent multi-homing to its upper layer users. This multi-homing is accomplished through the passing of address parameters in the initial setup message used by SCTP. In an IPv4 network all addresses are passed with no consideration for their scope and routeablility. In a IPv6 network special considerations MUST be made to properly bring up associations between SCTP endpoints that have IPv6 {[}RFC2460{]} addresses bound within their association. This document defines those considerations and enumerates general rules that an SCTP endpoint MUST use in formulating both the INIT and INIT-ACK chunks.},
}