< draft-haberman-ipv6-ra-flags-option-00.txt		draft-haberman-ipv6-ra-flags-option-01.txt >
	Network Working Group B. Haberman, Ed.		Network Working Group B. Haberman, Ed.
	Internet-Draft JHU APL		Internet-Draft JHU APL
	Intended status: Standards Track R. Hinden		Intended status: Standards Track R. Hinden
	Expires: February 1, 2007 Nokia		Expires: October 15, 2007 Nokia
	July 31, 2006		April 13, 2007
	IPv6 Router Advertisement Flags Option		IPv6 Router Advertisement Flags Option
	draft-haberman-ipv6-ra-flags-option-00		draft-haberman-ipv6-ra-flags-option-01
	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 February 1, 2007.		This Internet-Draft will expire on October 15, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	The IPv6 Neighbor Discovery's Router Advertisement message contains		The IPv6 Neighbor Discovery's Router Advertisement message contains
	an 8-bit field reserved for single-bit flags. Several protocols have		an 8-bit field reserved for single-bit flags. Several protocols have
	reserved flags in this field and others are preparing to reserve a		reserved flags in this field and others are preparing to reserve a
	sufficient number of flags to exhaust the field. This document		sufficient number of flags to exhaust the field. This document
	defines an option to the Router Advertisement message that expands		defines an option to the Router Advertisement message that expands
	the available number of flag bits available.		the available number of flag bits available.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Current Router Advertisement Flags . . . . . . . . . . . . . . 3		3. Current Router Advertisement Flags . . . . . . . . . . . . . . 3
	4. NDP Flags Expansion Option . . . . . . . . . . . . . . . . . . 4		4. Flags Expansion Option . . . . . . . . . . . . . . . . . . . . 4
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
	6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5		6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5		7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	7.1. Normative References . . . . . . . . . . . . . . . . . . . 5		7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
	7.2. Informative References . . . . . . . . . . . . . . . . . . 6		7.2. Informative References . . . . . . . . . . . . . . . . . . 6
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
	Intellectual Property and Copyright Statements . . . . . . . . . . 7		Intellectual Property and Copyright Statements . . . . . . . . . . 7
	1. Introduction		1. Introduction
	The IPv6 Neighbor Discovery Protocol's [1] Router Advertisement		The IPv6 Neighbor Discovery Protocol's [1] Router Advertisement
	message contains an 8-bit field reserved for single-bit flags.		message contains an 8-bit field reserved for single-bit flags.
	Several protocols have reserved flags in this field and others are		Several protocols have reserved flags in this field and others are
	preparing to reserve a sufficient number of flags to exhaust the		preparing to reserve a sufficient number of flags to exhaust the
	skipping to change at page 3, line 47 ¶		skipping to change at page 3, line 47 ¶
	o O - Other Configuration Flag [1]		o O - Other Configuration Flag [1]
	o H - Mobile IPv6 Home Agent Flag [3]		o H - Mobile IPv6 Home Agent Flag [3]
	o Prf - Router Selection Preferences [4]		o Prf - Router Selection Preferences [4]
	o P - Neighbor Discovery Proxy Flag [5]		o P - Neighbor Discovery Proxy Flag [5]
	o R - Reserved		o R - Reserved
	With other protocols in the works that are wanting to use flags in		With other protocols in the works (e.g., Detecting Network
	the NDP messages, it is necessary to define an expansion capability		Attachment) that are wanting to use flags in the NDP messages, it is
	to support new features.		necessary to define an expansion capability to support new features.
	4. NDP Flags Expansion Option		4. Flags Expansion Option
	The Neighbor Discovery specification [1] contains the capability to		The Neighbor Discovery specification [1] contains the capability to
	define NDP options. The following is the definition of the Expanded		define NDP options. The following (Figure 2) is the definition of
	Flags Option (EFO) for NDP messages.		the Expanded Flags Option (EFO) for NDP Router Advertisement
			messages.
	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 | Bit fields available ..		| Type | Length | Bit fields available ..
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	... for assignment |		... for assignment |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 2: NDP Expanded Flags Option		Figure 2: Router Advertisement Expanded Flags Option
	o Type - TBD (to be assigned by IANA)		o Type - TBD (to be assigned by IANA)
	o Length = 1; The length MUST be checked when processing the option		o Length = 1; The length MUST be checked when processing the option
	in order to allow for future expansion of this option if the need		in order to allow for future expansion of this option if the need
	arises.		arises.
	o Bits - allocated by IANA		o Bits - allocated by IANA
	The definition and usage of these bits is to be found in the document		The definition and usage of these bits is to be found in the document
	requesting their allocation.		requesting their allocation.
	This option MUST be the first option immediately following the base		This option:
	NDP header and MUST only occur once in a NDP packet.
			o MUST only occur in Router Advertisement messages
			o MUST be the first option immediately following the Router
			Advertisement message header
			o MUST only occur once in the Router Advertisement message.
	The bit fields within the option are numbered from left to right from		The bit fields within the option are numbered from left to right from
	8 to 47 and follow the numbering of the flag bits in the RA option		8 to 47 and follow the numbering of the flag bits in the RA option
	described in Figure 1.		described in Figure 1. Flag bits 0 to 7 are found in the Router
			Advertisement message header defined in [1]
	5. IANA Considerations		5. IANA Considerations
	The IANA is requested to define a new IPv6 Neighbor Discovery option		The IANA is requested to define a new IPv6 Neighbor Discovery option
	for the option defined in this document of the form:		for the option defined in this document of the form:
	+------+---------------------------+-----------+		+------+---------------------------+-----------+
	| Type | Description | Reference |		| Type | Description | Reference |
	+------+---------------------------+-----------+		+------+---------------------------+-----------+
	| TBA | RA Flags Extension Option | [RFCXXXX] |		| TBA | RA Flags Extension Option | [RFCXXXX] |
	skipping to change at page 7, line 7 ¶		skipping to change at page 7, line 7 ¶
	Nokia		Nokia
	313 Fairchild Drive		313 Fairchild Drive
	Mountain View, CA 94043		Mountain View, CA 94043
	USA		USA
	Phone: +1 650 625 2004		Phone: +1 650 625 2004
	Email: bob.hinden@nokia.com		Email: bob.hinden@nokia.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The Internet Society (2006).		Copyright (C) The IETF Trust (2007).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Intellectual Property		Intellectual Property
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		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		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
End of changes. 14 change blocks.
	23 lines changed or deleted		31 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/