Cooperative Agreement Between the ISOC/IETF and ISO/IEC Joint Technical Committee 1/Sub Committee 6 (JTC1/SC6) on IS-IS Routing Protocol Development
draft-zinin-ietf-jtc1-aggr-01

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3563.
Author Alex D. Zinin
Last updated 2018-08-07 (Latest revision 2002-12-23)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
txt htmlized pdf bibtex bibxml
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3563 (Informational)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Alex D. Zinin
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-zinin-ietf-jtc1-aggr-01 
A new Request for Comments is now available in online RFC libraries.

        RFC 3563

        Title:      Cooperative Agreement Between the ISOC/IETF and
                    ISO/IEC Joint Technical Committee 1/Sub
                    Committee 6 (JTC1/SC6) on IS-IS Routing Protocols
        Author(s):  A. Zinin
        Status:     Informational
        Date:       July 2003
        Mailbox:    zinin@psg.com
        Pages:      8
        Characters: 14974
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-zinin-ietf-jtc1-aggr-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3563.txt

This document contains the text of the agreement signed between
ISOC/IETF and ISO/IEC JTC1/SC6 regarding cooperative development of
the IS-IS routing protocol.  The agreement includes definitions of the
related work scopes for the two organizations, request for creation
and maintenance of an IS-IS registry by IANA, as well as
collaboration guidelines.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.