draft-ietf-ipngwg-icmp-name-lookups-14.txt		draft-ietf-ipngwg-icmp-name-lookups-15.txt
	IPv6 WG M. Crawford		IPv6 WG M. Crawford
	Internet-Draft Fermilab		Internet-Draft Fermilab
	Expires: July 5, 2006 B. Haberman, Ed.		Expires: August 17, 2006 B. Haberman, Ed.
	JHU APL		JHU APL
	January 2006		February 13, 2006
	IPv6 Node Information Queries		IPv6 Node Information Queries
	draft-ietf-ipngwg-icmp-name-lookups-14		draft-ietf-ipngwg-icmp-name-lookups-15
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 35		skipping to change at page 1, line 35
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on July 5, 2006.		This Internet-Draft will expire on August 17, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This document describes a protocol for asking an IPv6 node to supply		This document describes a protocol for asking an IPv6 node to supply
	certain network information, such as its hostname or fully-qualified		certain network information, such as its hostname or fully-qualified
	domain name. IPv6 implementation experience has shown that direct		domain name. IPv6 implementation experience has shown that direct
	skipping to change at page 9, line 50		skipping to change at page 9, line 50
	Figure 3: Node Information Address Query		Figure 3: Node Information Address Query
	o G - If set to 1, Global-scope addresses [12] are requested.		o G - If set to 1, Global-scope addresses [12] are requested.
	o S - If set to 1, Site-local addresses [12] are requested.		o S - If set to 1, Site-local addresses [12] are requested.
	However, Site-local addresses are now deprecated [15] and this		However, Site-local addresses are now deprecated [15] and this
	flag is for backwards compatibility.		flag is for backwards compatibility.
	o L - If set to 1, Link-local addresses [12] are requested.		o L - If set to 1, Link-local addresses [12] are requested.
	o C - If set to 1, IPv4-compatible and IPv4-mapped addresses [3] are		o C - If set to 1, IPv4-compatible (now deprecated) and IPv4-mapped
	requested. As the IPv4-compatible addresses are now deprecated,		addresses [3] are requested. Responses SHOULD include IPv4
	this flag is for backwards compatibility with older		addresses in IPv4-mapped form.
	implementations. Responses SHOULD include IPv4 addresses in IPv4-
	mapped form.
	o A - If set to 1, all the Responder's unicast addresses (of the		o A - If set to 1, all the Responder's unicast addresses (of the
	specified scope(s)) are requested. If 0, only those addresses are		specified scope(s)) are requested. If 0, only those addresses are
	requested which belong to the interface (or any one interface)		requested which belong to the interface (or any one interface)
	which has the Subject Address, or which are associated with the		which has the Subject Address, or which are associated with the
	Subject Name.		Subject Name.
	o T - Defined in a Reply only, indicates that the set of addresses		o T - Defined in a Reply only, indicates that the set of addresses
	is incomplete for space reasons.		is incomplete for space reasons.
	skipping to change at page 11, line 25		skipping to change at page 11, line 22
	may be defined using the "Specification Required" criteria from [16].		may be defined using the "Specification Required" criteria from [16].
	IANA is requested to establish and maintain a registry for the Code		IANA is requested to establish and maintain a registry for the Code
	fields associated with the Node Information Query ICMPv6 Types as a		fields associated with the Node Information Query ICMPv6 Types as a
	part of its ICMPv6 Registry updated in [13].		part of its ICMPv6 Registry updated in [13].
	This document defines five values of Qtype, numbers 0 through 4.		This document defines five values of Qtype, numbers 0 through 4.
	Following the policies outlined in [16], new values, and their		Following the policies outlined in [16], new values, and their
	associated Flags and Reply Data, are to be defined by IETF Consensus.		associated Flags and Reply Data, are to be defined by IETF Consensus.
	The IANA is requested to assign the IPv6 multicast prefix FF02:0:0:0:		The IANA is requested to assign the IPv6 multicast prefix FF02:0:0:0:
	0:2:FF::/104 for use in Node Information Queries as defined in		0:2:FF00::/104 for use in Node Information Queries as defined in
	Section 5. It should be noted that this request does conform with		Section 5. It should be noted that this request does conform with
	the requirements defined in [17].		the requirements defined in [17].
	8. Security Considerations		8. Security Considerations
	This protocol shares the security issues of ICMPv6 that are		This protocol shares the security issues of ICMPv6 that are
	documented in the "Security Considerations" section of [5].		documented in the "Security Considerations" section of [5].
	This protocol has the potential of revealing information useful to a		This protocol has the potential of revealing information useful to a
	would-be attacker. An implementation of this protocol MUST have a		would-be attacker. An implementation of this protocol MUST have a
End of changes. 6 change blocks.
	10 lines changed or deleted		8 lines changed or added
This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/