< draft-shen-ipv6-nd-name-seq-options-00.txt		draft-shen-ipv6-nd-name-seq-options-01.txt >
	Network Working Group Naiming Shen		Network Working Group Naiming Shen
	Internet Draft Redback Networks		Internet Draft Redback Networks
	Expiration Date: December 2003 June 2003		Expiration Date: December 2003 June 2003
	Link Name and Sequence Options for IPv6 Neighbor Discovery		Link Name and Sequence Options for IPv6 Neighbor Discovery
	draft-shen-ipv6-nd-name-seq-options-00.txt		draft-shen-ipv6-nd-name-seq-options-01.txt
	1. Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026.		all provisions of Section 10 of RFC2026.
	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
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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.
	2. Abstract		Abstract
	To facilitate network troubleshooting and management in IPv6		To facilitate network troubleshooting and management in IPv6
	environment, two new options for IPv6 Neighbor Discovery messages		environment, two new options for IPv6 Neighbor Discovery messages
	are proposed in this document. The Link-Name option is used in		are proposed in this document. The Link-Name option is used in
	Router Advertisement message, and the Sequence-Number option is		Router Advertisement message, and the Sequence-Number option is
	used in Neighbor Solicitation and Neighbor Advertisement messages.		used in Neighbor Solicitation and Neighbor Advertisement messages.
	3. Introduction		1. Introduction
	The Router Advertisement message in Neighbor Discovery for IPv6 [1]		The Router Advertisement message in Neighbor Discovery for IPv6 [1]
	currently has defined options with source link-layer address,		currently has defined options with source link-layer address,
	MTU and prefix information. It is obvious that, by inspecting		MTU and prefix information. It is obvious that, by inspecting
	a link-local address of the neighbor from diagnostics information		a link-local address of the neighbor from diagnostics information
	is less clear than symbolic names. This draft proposes a mechanism		is less clear than symbolic names. This draft proposes a mechanism
	allowing Router Advertisement message to include a Link-Name		allowing Router Advertisement message to include a Link-Name
	option.		option.
	When Neighbor Advertisement message is received from a neighbor,		When Neighbor Advertisement message is received from a neighbor,
	and if the Neighbor Solicitation messages were retransmitted, it		and if the Neighbor Solicitation messages were retransmitted, it
	is useful from troubleshooting point of view to learn which		is useful from troubleshooting point of view to learn which
	Neighbor Solicitation message the Neighbor Advertisement message		Neighbor Solicitation message the Neighbor Advertisement message
	replied to and what is the round trip delay for this address		replied to and what is the round trip delay for this address
	resolution, similar to the sequence number and round-trip time		resolution, similar to the sequence number and round-trip time
	scheme used in ICMP request/reply implementation.		scheme used in ICMP request/reply implementation.
	4. Link-Name Option		2. Neighbor Discovery Option Additions
			Two new options for Neighbor Discovery are defined in this
			document, the Link-Name option and the Sequence-Number option.
			2.1 Link-Name Option
	The Link-Name option MAY be included in Router Advertisement		The Link-Name option MAY be included in Router Advertisement
	message. A typical Link-Name can be a combination of router name,		message. A typical Link-Name may be a combination of router name,
	virtual router identifier and interface name of the link.		virtual router identifier and interface name of the link.
	0 1 2 3		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		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 | Length | Link-Name String ....		| Type | Length | Link-Name String ....
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Fields:		Fields:
	Type Link-Name [TBD: IANA]		Type 103, Link-Name [TBD: IANA]
	Length 6 (including the type and length fields, total 48		Length 1-32 (8 to 256 bytes including the type and length
	bytes)		fields)
	Link-Name String		Link-Name String
	This field identifies the symbolic name of the link		This field identifies the symbolic name of the link
	of the router. The string is null-terminated if the		on the router. The string is null-terminated if the
	name is less than 46 bytes.		actual length of the name is less than specified.
	The option MUST be silently ignored for other Neighbor Discovery		The option MUST be silently ignored for other Neighbor Discovery
	messages.		messages.
	5. Sequence-Number Option		2.2 Sequence-Number Option
	The Sequence-Number option MAY be included in Neighbor Solicitation		The Sequence-Number option MAY be included in Neighbor Solicitation
	message and Neighbor Advertisement message. The sequence number		message and Neighbor Advertisement message. The sequence number
	is maintained for each cache entry and is increased by one for each		is maintained for each cache entry and is increased by one for each
	Neighbor Solicitation sent for the entry. A Neighbor Advertisement		Neighbor Solicitation sent for the entry. A Neighbor Advertisement
	message only include this option when responding to the Neighbor		message only includes this option when responding to the Neighbor
	Solicitation message, and it SHOULD simply copy the Sequence-Number		Solicitation message, and it MUST simply copy the Sequence-Number
	Option from the Neighbor Solicitation packet unchanged.		Option from the Neighbor Solicitation packet unchanged if it
			supports this extension.
	0 1 2 3		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		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 | Length | Sequence-Number |		| Type | Length | Sequence-Number |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| NS User Data |		| NS Local Data ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Fields:		Fields:
	Type Sequence-Number [TBD: IANA]		Type 104, Sequence-Number [TBD: IANA]
	Length 1 (8 bytes including the type and length fields)		Length 1-32 (8 to 256 bytes including the type and length
			fields)
	Sequence-Number		Sequence-Number
	A 16-bit unsigned integer in network byte order.		A 16-bit unsigned integer in network byte order.
	NS User Data		NS Local Data
	A 32-bit unsigned integer in network byte order. This		This data has only local significance to the sender
	value has only local significance to the sender of		of the Neighbor Solicitation packet. For example, it
	the Neighbor Solicitation packet. For example, it		can contain a timestamp in milliseconds.
	can be a timestamp in milliseconds.
	The option SHOULD only be used in Neighbor Solicitation message		The option SHOULD only be used in Neighbor Solicitation message
	when the source address is not an unspecified address. The		when the source address is not an unspecified address. The
	Neighbor Advertisement SHOULD relay the option back to the		Neighbor Advertisement SHOULD relay the option back to the
	sender of the Neighbor Solicitation packet when responding to		sender of the Neighbor Solicitation packet when responding to
	the Neighbor Solicitation. This option SHOULD not be used in		the Neighbor Solicitation. This option SHOULD not be used in
	unsolicited Neighbor Advertisement message.		unsolicited Neighbor Advertisement message.
	6. Security Considerations		3. Security Considerations
	This extension does not introduce any security issues.		This document has no known security implications.
	7. Acknowledgments		4. IANA Considerations
			The author has chosen "103" as the type code for Link-Name option,
			and "104" as the type code for Sequence-Number option. Those need
			to be allocated by IANA.
			5. Acknowledgments
	TBD.		TBD.
	8. References		6. Normative References
	[1] Narten, T., Nordmark, E. and W. Simpson, "Neighbor Discovery		[1] Narten, T., Nordmark, E. and W. Simpson, "Neighbor Discovery
	for IP Version 6 (IPv6)", RFC 2461, December 1998.		for IP Version 6 (IPv6)", RFC 2461, December 1998.
	9. Author Information		7. Author Information
	Naiming Shen		Naiming Shen
	Redback Networks, Inc.		Redback Networks, Inc.
	300 Holger Way		300 Holger Way
	San Jose, CA 95134		San Jose, CA 95134
	e-mail: naiming@redback.com		e-mail: naiming@redback.com
			8. Full Copyright Statement
			Copyright (C) The Internet Society (2001). All Rights Reserved.
			This document and translations of it may be copied and furnished to
			others, and derivative works that comment on or otherwise explain it
			or assist in its implementation may be prepared, copied, published
			and distributed, in whole or in part, without restriction of any
			kind, provided that the above copyright notice and this paragraph are
			included on all such copies and derivative works. However, this
			document itself may not be modified in any way, such as by removing
			the copyright notice or references to the Internet Society or other
			Internet organizations, except as needed for the purpose of
			developing Internet standards in which case the procedures for
			copyrights defined in the Internet Standards process must be
			followed, or as required to translate it into languages other than
			English.
			The limited permissions granted above are perpetual and will not be
			revoked by the Internet Society or its successors or assigns.
			This document and the information contained herein is provided on an
			"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
			TASK FORCE DISCLAIMS 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.
End of changes. 21 change blocks.
	28 lines changed or deleted		40 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/