idnits 2.17.1 draft-ietf-ipv6-default-addr-select-09.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 3484 5 Title: Default Address Selection for Internet Protocol 6 version 6 (IPv6) 7 Author(s): R. Draves 8 Status: Standards Track 9 Date: February 2003 10 Mailbox: richdr@microsoft.com 11 Pages: 24 12 Characters: 55076 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-ipv6-default-addr-select-09.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3484.txt 19 This document describes two algorithms, for source address selection 20 and for destination address selection. The algorithms specify default 21 behavior for all Internet Protocol version 6 (IPv6) implementations. 22 They do not override choices made by applications or upper-layer 23 protocols, nor do they preclude the development of more advanced 24 mechanisms for address selection. The two algorithms share a common 25 context, including an optional mechanism for allowing administrators 26 to provide policy that can override the default behavior. In dual 27 stack implementations, the destination address selection algorithm can 28 consider both IPv4 and IPv6 addresses - depending on the available 29 source addresses, the algorithm might prefer IPv6 addresses over IPv4 30 addresses, or vice-versa. 32 All IPv6 nodes, including both hosts and routers, must implement 33 default address selection as defined in this specification. 35 This document is a product of the IP Version 6 Working Group of the 36 IETF. 38 This is now a Proposed Standard Protocol. 40 This document specifies an Internet standards track protocol for 41 the Internet community, and requests discussion and suggestions 42 for improvements. Please refer to the current edition of the 43 "Internet Official Protocol Standards" (STD 1) for the 44 standardization state and status of this protocol. Distribution 45 of this memo is unlimited. 47 This announcement is sent to the IETF list and the RFC-DIST list. 48 Requests to be added to or deleted from the IETF distribution list 49 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 50 added to or deleted from the RFC-DIST distribution list should 51 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 53 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 54 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 55 help: ways_to_get_rfcs. For example: 57 To: rfc-info@RFC-EDITOR.ORG 58 Subject: getting rfcs 60 help: ways_to_get_rfcs 62 Requests for special distribution should be addressed to either the 63 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 64 specifically noted otherwise on the RFC itself, all RFCs are for 65 unlimited distribution.echo 66 Submissions for Requests for Comments should be sent to 67 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 68 Authors, for further information.