idnits 2.17.1 draft-xiao-tcp-prec-03.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 2873 5 Title: TCP Processing of the IPv4 Precedence Field 6 Author(s): X. Xiao, A. Hannan, V. Paxson, E. Crabbe 7 Status: Standards Track 8 Date: June 2000 9 Mailbox: xipeng@gblx.net, alan@ivmg.net, 10 edc@explosive.net, vern@aciri.org 11 Pages: 8 12 Characters: 15565 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-xiao-tcp-prec-03.txt 17 URL: ftp://ftp.isi.edu/in-notes/rfc2873.txt 19 This memo describes a conflict between TCP [RFC793] and DiffServ 20 [RFC2475] on the use of the three leftmost bits in the TOS octet of 21 an IPv4 header [RFC791]. In a network that contains DiffServ-capable 22 nodes, such a conflict can cause failures in establishing TCP 23 connections or can cause some established TCP connections to be reset 24 undesirably. This memo proposes a modification to TCP for resolving 25 the conflict. 27 Because the IPv6 [RFC2460] traffic class octet does not have any 28 defined meaning except what is defined in RFC 2474, and in particular 29 does not define precedence or security parameter bits, there is no 30 conflict between TCP and DiffServ on the use of any bits in the IPv6 31 traffic class octet. 33 This is now a Proposed Standard Protocol. 35 This document specifies an Internet standards track protocol for 36 the Internet community, and requests discussion and suggestions 37 for improvements. Please refer to the current edition of the 38 "Internet Official Protocol Standards" (STD 1) for the 39 standardization state and status of this protocol. Distribution 40 of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.