idnits 2.17.1 draft-ietf-sip-dhcp-06.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 3361 5 Title: Dynamic Host Configuration Protocol 6 (DHCP-for-IPv4) Option for Session Initiation 7 Protocol (SIP) Servers 8 Author(s): H. Schulzrinne 9 Status: Standards Track 10 Date: August 2002 11 Mailbox: schulzrinne@cs.columbia.edu 12 Pages: 7 13 Characters: 12549 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-sip-dhcp-06.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3361.txt 20 This document defines a Dynamic Host Configuration Protocol 21 (DHCP-for-IPv4) option that contains a list of domain names or IPv4 22 addresses that can be mapped to one or more Session Initiation 23 Protocol (SIP) outbound proxy servers. This is one of the many 24 methods that a SIP client can use to obtain the addresses of such a 25 local SIP server. 27 This document is a product of the Session Initiation Protocol Working 28 Group of the IETF. 30 This is now a Proposed Standard Protocol. 32 This document specifies an Internet standards track protocol for 33 the Internet community, and requests discussion and suggestions 34 for improvements. Please refer to the current edition of the 35 "Internet Official Protocol Standards" (STD 1) for the 36 standardization state and status of this protocol. Distribution 37 of this memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.