idnits 2.17.1 draft-ietf-mpls-git-uus-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3033 5 Title: The Assignment of the Information Field and 6 Protocol Identifier in the Q.2941 Generic 7 Identifier and Q.2957 User-to-user Signaling for 8 the Internet Protocol 9 Author(s): M. Suzuki 10 Status: Standards Track 11 Date: January 2001 12 Mailbox: suzuki.muneyoshi@lab.ntt.co.jp 13 Pages: 25 14 Characters: 52188 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-mpls-git-uus-04.txt 19 URL: ftp://ftp.isi.edu/in-notes/rfc3033.txt 21 The purpose of this document is to specify the assignment of the 22 information field and protocol identifier in the Q.2941 Generic 23 Identifier and Q.2957 User-to-user Signaling for the Internet 24 protocol. 26 The assignment, that is specified in section 4 of this document, is 27 designed for advanced B-ISDN signaling support of the Internet 28 protocol, especially the B-ISDN signaling support for the connection 29 that corresponds to the session in the Internet protocol which is 30 clarified in section 2. This specification provides an indispensable 31 framework for the implementation of long-lived session and 32 QoS-sensitive session transfers over ATM. 34 This document is a product of the Multiprotocol Label Switching 35 Working Group of the IETF. 37 This is now a Proposed Standard Protocol. 39 This document specifies an Internet standards track protocol for 40 the Internet community, and requests discussion and suggestions 41 for improvements. Please refer to the current edition of the 42 "Internet Official Protocol Standards" (STD 1) for the 43 standardization state and status of this protocol. Distribution 44 of this memo is unlimited. 46 This announcement is sent to the IETF list and the RFC-DIST list. 47 Requests to be added to or deleted from the IETF distribution list 48 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 49 added to or deleted from the RFC-DIST distribution list should 50 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 52 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 53 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 54 help: ways_to_get_rfcs. For example: 56 To: rfc-info@RFC-EDITOR.ORG 57 Subject: getting rfcs 59 help: ways_to_get_rfcs 61 Requests for special distribution should be addressed to either the 62 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 63 specifically noted otherwise on the RFC itself, all RFCs are for 64 unlimited distribution.echo 65 Submissions for Requests for Comments should be sent to 66 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 67 Authors, for further information.