IPv6 Node Information Queries
RFC 4620
| Document | Type | RFC - Experimental (August 2006; No errata) | |
|---|---|---|---|
| Authors | Matt Crawford , Brian Haberman | ||
| Last updated | 2015-10-14 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 4620 (Experimental) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Margaret Cullen | ||
| Send notices to | (None) | ||
Network Working Group M. Crawford
Request for Comments: 4620 Fermilab
Category: Experimental B. Haberman, Ed.
JHU APL
August 2006
IPv6 Node Information Queries
Status of This Memo
This memo defines an Experimental Protocol for the Internet
community. It does not specify an Internet standard of any kind.
Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document describes a protocol for asking an IPv6 node to supply
certain network information, such as its hostname or fully-qualified
domain name. IPv6 implementation experience has shown that direct
queries for a hostname are useful, and a direct query mechanism for
other information has been found useful in serverless environments
and for debugging.
Table of Contents
1. Introduction ....................................................2
2. Applicability Statement .........................................2
3. Terminology .....................................................2
4. Node Information Messages .......................................3
5. Message Processing ..............................................5
6. Defined Qtypes ..................................................6
6.1. NOOP .......................................................7
6.2. Node Name ..................................................7
6.3. Node Addresses .............................................8
6.4. IPv4 Addresses .............................................9
6.4.1. Discussion ..........................................9
7. IANA Considerations ............................................10
8. Security Considerations ........................................10
9. Acknowledgements ...............................................11
10. References ....................................................11
10.1. Normative References .....................................11
10.2. Informative References ...................................12
Crawford & Haberman Experimental [Page 1]
RFC 4620 IPv6 Node Information Queries August 2006
1. Introduction
This document specifies a mechanism for discovering information about
names and addresses. The applicability of these mechanisms is
currently limited to diagnostic and debugging tools and network
management (e.g., node discovery). In the global internet, the
Domain Name System (DNS) [1][2] is the authoritative source of such
information and this specification is not intended to supplant or
supersede it. In fact, in a well-supported network, the names and
addresses dealt with by this mechanism will be the same ones, with
the same relationships, as those listed in the DNS.
This new Node Information protocol provides facilities that are not
found in the DNS, for example, discovering relationships between
addresses without reference to names. The functions that do overlap
with the DNS may be useful in serverless environments, for debugging,
or in regard to link-local and unique-local addresses [3] that often
will not be listed in the DNS.
2. Applicability Statement
IPv6 Node Information Queries include the capability to provide
forward and reverse name lookups independent of the DNS by sending
packets directly to IPv6 nodes or groups of nodes.
The applicability of these mechanisms is currently limited to
diagnostic and debugging tools and network management (e.g., node
discovery). These mechanisms can be used to learn the addresses and
names for nodes on the other end of a point-to-point link or nodes on
a shared-medium link such as an Ethernet. This is very useful when
debugging problems or when bringing up IPv6 service where there is no
global routing or DNS name services available. IPv6's large auto-
configured addresses make debugging network problems and bringing up
IPv6 service difficult without these mechanisms. An example of an
IPv6 debugging tool using IPv6 Node Information Queries is the ping6
program in the KAME (http://www.kame.net), USAGI, and other IPv6
implementations.
The mechanisms defined in this document may have wider applicability
in the future, but any use beyond debugging and diagnostic tools is
left for further study and is beyond the scope of this document.
3. Terminology
A "Node Information Query" (or "NI Query") message is sent by a
"Querier" node to a "Responder" node in an ICMPv6 packet addressed to
the "Queried Address". The Query contains a "Subject Address" (which
may differ from the Queried Address and may be an IPv6 or IPv4
Crawford & Haberman Experimental [Page 2]
RFC 4620 IPv6 Node Information Queries August 2006
address) or a "Subject Name". The Responder sends a "Node
Information Reply" to the Querier, containing information associated
with the node at the Queried Address. A node receiving an NI Query
will be termed a Responder even if it does not send a reply.
The word "name" in this document refers to a hostname with or without
the domain. Where necessary, the cases of fully-qualified and
single-label names will be distinguished.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [4].
Packet fields marked "unused" must be zero on transmission and, aside
from inclusion in checksums or message integrity checks, ignored on
reception.
4. Node Information Messages
Two types of Node Information messages, the NI Query and the NI
Reply, are carried in ICMPv6 [5] packets. They have the same format.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Qtype | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Nonce +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
/ Data /
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Node Information Messages
Fields:
o Type
* 139 - NI Query
* 140 - NI Reply
Crawford & Haberman Experimental [Page 3]
RFC 4620 IPv6 Node Information Queries August 2006
o Code
* For NI Query
+ 0 - Indicates that the Data field contains an IPv6 address
that is the Subject of this Query.
+ 1 - Indicates that the Data field contains a name that is
the Subject of this Query, or is empty, as in the case of a
NOOP.
+ 2 - Indicates that the Data field contains an IPv4 address
that is the Subject of this Query.
* For NI Reply
+ 0 - Indicates a successful reply. The Reply Data field may
or may not be empty.
+ 1 - Indicates that the Responder refuses to supply the
answer. The Reply Data field will be empty.
+ 2 - Indicates that the Qtype of the Query is unknown to the
Responder. The Reply Data field will be empty.
o Checksum - The ICMPv6 checksum.
o Qtype - A 16-bit field that designates the type of information
requested in a Query or supplied in a Reply. Its value in a Reply
is always copied from the corresponding Query by the Responder.
Five values of Qtype are specified in this document.
o Flags - Qtype-specific flags that may be defined for certain Query
types and their Replies. Flags not defined for a given Qtype must
be zero on transmission and ignored on reception, and must not be
copied from a Query to a Reply unless so specified in the
definition of the Qtype.
o Nonce - An opaque 64-bit field to help avoid spoofing and/or to
aid in matching Replies with Queries. Its value in a Query is
chosen by the Querier. Its value in a Reply is always copied from
the corresponding Request by the Responder.
o Data - In a Query, the Subject Address or Name. In a Reply,
Qtype-specific data is present only when the ICMPv6 Code field is
zero. The length of the Data may be inferred from the IPv6
header's Payload Length field [6], the length of the fixed portion
Crawford & Haberman Experimental [Page 4]
RFC 4620 IPv6 Node Information Queries August 2006
of the NI packet, and the lengths of the ICMPv6 header and
intervening extension headers.
Note that the type of information present in the Data field of a
Query is declared by the ICMP Code, whereas the type of information,
if any, in the Data field of a Reply is determined by the Qtype.
When the Subject of a Query is a name, the name MUST be in DNS wire
format [2]. The name may be either a fully-qualified domain name,
including the terminating zero-length label, or a single DNS label
followed by two zero-length labels. Since a Query contains at most
one name, DNS name compression MUST NOT be used.
5. Message Processing
The Querier constructs an ICMP NI Query and sends it to the address
from which information is wanted. When the Subject of the Query is
an IPv6 address, that address will normally be used as the IPv6
destination address of the Query, but need not be if the Querier has
useful a priori information about the addresses of the target node.
An NI Query may also be sent to a multicast address of link-local
scope [3].
When the Subject is a name, either fully-qualified or single-
component, and the Querier does not have a unicast address for the
target node, the query MUST be sent to a link-scope multicast address
formed in the following way. The Subject Name is converted to the
canonical form defined by DNS Security [7], which is uncompressed
with all alphabetic characters in lowercase. (If additional DNS
label types or character sets for hostnames are defined, the rules
for canonicalizing those labels will be found in their defining
specification.) Compute the MD5 hash [8] of the first label of the
Subject Name--the portion beginning with the first one-octet length
field and up to, but excluding, any subsequent length field. Append
the first 24 bits of that 128-bit hash to the prefix
FF02:0:0:0:0:2:FF00::/104. The resulting multicast address will be
termed the "NI Group Address" for the name. A node will support an
"NI Group Address" for each unique single-label name.
The Nonce MUST be a random or good pseudo-random value to foil
spoofed replies. An implementation that allows multiple independent
processes to send NI Queries MAY use the Nonce value to deliver
Replies to the correct process. Nonetheless, such processes MUST
check the received Nonce and ignore extraneous Replies.
If true communication security is required, IP Security (IPsec) [14]
should be used. Providing the infrastructure to authenticate NI
Crawford & Haberman Experimental [Page 5]
RFC 4620 IPv6 Node Information Queries August 2006
Queries and Replies may be quite difficult outside of a well-defined
community.
Upon receiving an NI Query, the Responder must check the Query's IPv6
destination address and discard the Query without further processing
unless it is one of the Responder's unicast or anycast addresses, or
a link-local scope multicast address that the Responder has joined.
Typically, the latter will be an NI Group Address for a name
belonging to the Responder. A node MAY be configured to discard NI
Queries to multicast addresses other than its NI Group Address(es),
but if so, the default configuration SHOULD be not to discard them.
A Responder must also silently discard a Query whose Subject Address
or Name (in the Data field) does not belong to that node. A single-
component Subject Name matches any fully-qualified name whose first
label matches the Subject. All name matching is done in a case-
independent manner consistent with DNS Security (DNSSEC) name
canonicalization [7].
Next, if Qtype is unknown to the Responder, it must return an NI
Reply with ICMPv6 Code = 2 and no Reply Data. The Responder should
rate-limit such replies as it would ICMPv6 error replies [5].
Next, the Responder should decide whether to refuse an answer, based
on local policy. (See the "Security Considerations" section for
recommended default behavior.) If an answer is refused, depending on
local policy the Responder can elect to silently discard the query or
send an NI Reply with ICMPv6 Code = 1 and no Reply Data. Again, the
Responder should rate-limit such replies as it would ICMPv6 error
replies [5].
Finally, if the Qtype is known and the response is allowed by local
policy, the Responder MUST fill in the Flags and Reply Data of the NI
Reply in accordance with the definition of the Qtype and transmit the
NI Reply. The source address of the NI Reply SHOULD be selected
using the rules defined in [9].
If the Query was sent to a multicast address, transmission of the
Reply MUST be delayed by a random interval between zero and [Query
Response Interval], as defined by Multicast Listener Discovery
Version 2 [10].
6. Defined Qtypes
The following Qtypes are defined. Qtypes 0, 2, and 3 MUST be
supported by any implementation of this protocol. Qtype 4 SHOULD be
supported by any implementation of this protocol on an IPv4/IPv6
dual-stack node and MAY be supported on an IPv6-only node.
Crawford & Haberman Experimental [Page 6]
RFC 4620 IPv6 Node Information Queries August 2006
+-------------+----------------+
| Qtype Value | Qtype Name |
+-------------+----------------+
| 0 | NOOP |
| 1 | unused |
| 2 | Node Name |
| 3 | Node Addresses |
| 4 | IPv4 Addresses |
+-------------+----------------+
6.1. NOOP
This NI type has no defined flags and never has a Data field. A
Reply to an NI NOOP Query tells the Querier that a node with the
Queried Address is up and reachable and implements the Node
Information protocol. On transmission, the ICMPv6 Code in a NOOP
Query must be set to 1 and the Code in a NOOP Reply must be 0. On
reception of a NOOP Query or Reply, the Code must be ignored.
6.2. Node Name
The NI Node Name Query requests the fully-qualified or single-
component name corresponding to the Subject Address or Name. The
Reply Data has the following format.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TTL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Node Names ... |
+ +
/ /
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Node Information Reply Message
o TTL (Time to Live) - MUST be zero. Any non-zero value received
MUST be treated as zero. This field is no longer used but is
present to preserve backward compatibility with older
implementations.
o Node Names - The fully-qualified or single-component name or names
of the Responder that correspond(s) to the Subject Address or
Name, in DNS wire format, Section 3.1 of [2]. Each name MUST be
fully-qualified if the responder knows the domain suffix;
Crawford & Haberman Experimental [Page 7]
RFC 4620 IPv6 Node Information Queries August 2006
otherwise, each name MUST be a single DNS label followed by two
zero-length labels. When multiple node names are returned and
more than one of them is fully-qualified, DNS name compression,
Section 4.1.4 of [2], SHOULD be used, and the offsets are counted
from the first octet of the Data field. An offset of 4, for
example, will point to the beginning of the first name.
The Responder must fill in the TTL field of the Reply with zero.
Only one TTL is included in the Reply.
If the Responder does not know its name at all, it MUST send a Reply
with TTL=0 and no Node Names (or a Reply with Code=1 indicating
refusal to answer). The Querier will be able to determine from the
packet length that the Data field contains no names.
6.3. Node Addresses
The NI Node Addresses Query requests some set of the Responder's IPv6
unicast addresses. The Reply Data is a sequence of 128-bit IPv6
addresses, with each address preceded by a separate 32-bit TTL value,
with Preferred addresses listed before Deprecated addresses [11];
otherwise, they are in no special order. Five flag bits are defined
in the Query and six in the Reply.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Qtype=3 | unused |G|S|L|C|A|T|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Node Information Address Query
o G - If set to 1, Global-scope 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
flag is for backward compatibility.
o L - If set to 1, Link-local addresses [12] are requested.
o C - If set to 1, IPv4-compatible (now deprecated) and IPv4-mapped
addresses [3] are requested. Responses SHOULD include IPv4
addresses in IPv4-mapped form.
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
requested that belong to the interface (or any one interface) that
Crawford & Haberman Experimental [Page 8]
RFC 4620 IPv6 Node Information Queries August 2006
has the Subject Address or that are associated with the Subject
Name.
o T - Defined in a Reply only, indicates that the set of addresses
is incomplete for space reasons.
Flags G, S, L, C, and A are copied from a Query to the corresponding
Reply.
The TTL associated with each address MUST be zero.
6.4. IPv4 Addresses
The NI IPv4 Addresses Query requests some set of the Responder's IPv4
unicast addresses. The Reply Data is a sequence of 32-bit IPv4
addresses, each address preceded by a 32-bit TTL value. One flag bit
is defined in the Query and two in the Reply.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Qtype=4 | unused |A|T|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Node Information IPv4 Address Query
o A - If set to 1, all the Responder's unicast addresses are
requested. If 0, only those addresses are requested that belong
to the interface (or any one interface) that has the Subject
Address.
o T - Defined in a Reply only, indicates that the set of addresses
is incomplete for space reasons.
Flag A is copied from a Query to the corresponding Reply.
The TTL associated with each address MUST be zero.
6.4.1. Discussion
It is possible that a node may treat IPv4 interfaces and IPv6
interfaces as distinct, even though they are associated with the same
hardware. When such a node is responding to an NI Query having a
Subject Address of one type requesting the other type, and the Query
has the A flag set to 0, it SHOULD consider IP interfaces, other than
tunnels, associated with the same hardware as being the same
interface.
Crawford & Haberman Experimental [Page 9]
RFC 4620 IPv6 Node Information Queries August 2006
7. IANA Considerations
ICMPv6 type values 139 and 140 were previously assigned by IANA for
this protocol. This document defines three values of the ICMPv6 Code
field for each of these ICMPv6 Type values. Additional Code values
may be defined using the "Specification Required" criteria from [16].
IANA has established and will maintain a registry for the Code fields
associated with the Node Information Query ICMPv6 Types as a part of
its ICMPv6 Registry updated in [13].
This document defines five values of Qtype, numbers 0 through 4.
Following the policies outlined in [16], new values, and their
associated Flags and Reply Data, are to be defined by IETF Consensus.
The IANA has assigned the IPv6 multicast prefix
FF02:0:0:0:0:2:FF00::/104 for use in Node Information Queries as
defined in Section 5. It should be noted that this assignment does
conform with the requirements defined in [17].
8. Security Considerations
This protocol shares the security issues of ICMPv6 that are
documented in the "Security Considerations" section of [5].
This protocol has the potential of revealing information useful to a
would-be attacker. An implementation of this protocol MUST have a
default configuration that refuses to answer queries from global-
scope [3] addresses.
Implementations SHOULD apply rate-limiting to NI responses to avoid
being used in a denial-of-service attack.
The anti-spoofing Nonce does not give any protection from spoofers
who can eavesdrop the Query or the Reply.
The information learned via this protocol SHOULD NOT be trusted for
making security-relevant decisions unless some other mechanisms
beyond the scope of this document are used to authenticate this
information.
An implementation of this protocol SHOULD provide the ability to
control the dissemination of information related to IPv6 Privacy
Addresses [18]. The default action of this policy SHOULD NOT provide
a response to a Query that contains a node's Privacy Addresses.
A node MUST NOT include Privacy Addresses in any Node Addresses
response that includes a public address, or for which the source
address of the response, the destination address of the request, or
Crawford & Haberman Experimental [Page 10]
RFC 4620 IPv6 Node Information Queries August 2006
the Subject Address of the request is a public address. Similarly, a
node MUST NOT include any address other than the (single) Privacy
Address in any Node Addresses response that includes the Privacy
Address, or for which the source address of the response, the
destination address of the request, or the Subject Address of the
request is the Privacy Address.
9. Acknowledgements
Alain Durand contributed to this specification, and valuable feedback
and implementation experience were provided by Jun-Ichiro Hagino and
Tatuya Jinmei. Other useful comments were received from Robert Elz,
Keith Moore, Elwyn Davies, Pekka Savola, and Dave Thaler. Bob Hinden
and Brian Haberman have acted as document editors during the IETF
advancement process.
This document is not the first proposal of a direct query mechanism
for address-to-name translation. The idea had been discussed briefly
in the IPng working group, and RFC 1788 [19] describes such a
mechanism for IPv4.
10. References
10.1. Normative References
[1] Mockapetris, P., "Domain names - concepts and facilities", STD
13, RFC 1034, November 1987.
[2] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987.
[3] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[4] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[5] Conta, A. and S. Deering, "Internet Control Message Protocol
(ICMPv6) for the Internet Protocol Version 6 (IPv6)
Specification", RFC 2463, December 1998.
[6] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)
Specification", RFC 2460, December 1998.
[7] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose,
"Resource Records for the DNS Security Extensions", RFC 4034,
March 2005.
Crawford & Haberman Experimental [Page 11]
RFC 4620 IPv6 Node Information Queries August 2006
[8] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, April
1992.
[9] Draves, R., "Default Address Selection for Internet Protocol
version 6 (IPv6)", RFC 3484, February 2003.
[10] Vida, R. and L. Costa, "Multicast Listener Discovery Version 2
(MLDv2) for IPv6", RFC 3810, June 2004.
[11] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery
for IP Version 6 (IPv6)", RFC 2461, December 1998.
[12] Hinden, R., Deering, S., and E. Nordmark, "IPv6 Global Unicast
Address Format", RFC 3587, August 2003.
[13] Conta, A., Deering, S., and M. Gupta, "Internet Control Message
Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)
Specification", RFC 4443, March 2006.
10.2. Informative References
[14] Kent, S. and K. Seo, "Security Architecture for the Internet
Protocol", RFC 4301, December 2005.
[15] Huitema, C. and B. Carpenter, "Deprecating Site Local
Addresses", RFC 3879, September 2004.
[16] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP 26, RFC 2434, October
1998.
[17] Haberman, B., "Allocation Guidelines for IPv6 Multicast
Addresses", RFC 3307, August 2002.
[18] Narten, T. and R. Draves, "Privacy Extensions for Stateless
Address Autoconfiguration in IPv6", RFC 3041, January 2001.
[19] Simpson, W., "ICMP Domain Name Messages", RFC 1788, April 1995.
Crawford & Haberman Experimental [Page 12]
RFC 4620 IPv6 Node Information Queries August 2006
Authors' Addresses
Matt Crawford
Fermilab
PO Box 500
Batavia, IL 60510
US
Phone: +1 630 840 3461
EMail: crawdad@fnal.gov
Brian Haberman (editor)
Johns Hopkins University Applied Physics Lab
11100 Johns Hopkins Road
Laurel, MD 20723-6099
US
Phone: +1 443 778 1319
EMail: brian@innovationslab.net
Crawford & Haberman Experimental [Page 13]
RFC 4620 IPv6 Node Information Queries August 2006
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Crawford & Haberman Experimental [Page 14]