< draft-yegin-pana-unspecified-addr-02.txt		draft-yegin-pana-unspecified-addr-03.txt >
	Network Working Group A. Yegin		Network Working Group A. Yegin
	Internet-Draft Samsung		Internet-Draft Samsung
	Intended status: Standards Track Y. Ohba		Intended status: Standards Track Y. Ohba
	Expires: March 14, 2011 Toshiba		Expires: March 31, 2011 Toshiba
	L. Morand		L. Morand
	Orange Labs		Orange Labs
	J. Kaippallimalil		J. Kaippallimalil
	Huawei USA		Huawei USA
	September 10, 2010		September 27, 2010
	Protocol for Carrying Authentication for Network Access (PANA) with IPv4		Protocol for Carrying Authentication for Network Access (PANA) with IPv4
	Unspecified Address		Unspecified Address
	draft-yegin-pana-unspecified-addr-02		draft-yegin-pana-unspecified-addr-03
	Abstract		Abstract
	This document defines how PANA client (PaC) can perform PANA		This document defines how PANA client (PaC) can perform PANA
	authentication prior to configuring an IP address.		authentication prior to configuring an IP address.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	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."
	This Internet-Draft will expire on March 14, 2011.		This Internet-Draft will expire on March 31, 2011.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2010 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 3, line 26 ¶		skipping to change at page 3, line 26 ¶
	routing hop, the PaC can run PANA with the PAA prior to configuring		routing hop, the PaC can run PANA with the PAA prior to configuring
	an IP address.		an IP address.
	This document defines an extension of PANA to allow the PaC to use		This document defines an extension of PANA to allow the PaC to use
	IPv4 unspecified address (0.0.0.0) until it gets authenticated/		IPv4 unspecified address (0.0.0.0) until it gets authenticated/
	authorized; and configures an IP address afterwards (possibly using		authorized; and configures an IP address afterwards (possibly using
	DHCP). Such a feature is already available in Mobile IPv4 [RFC3344]		DHCP). Such a feature is already available in Mobile IPv4 [RFC3344]
	where MN can use unspecified IPv4 address with Mobile IP protocol		where MN can use unspecified IPv4 address with Mobile IP protocol
	until it is assigned a home address, and also DHCP [RFC2131].		until it is assigned a home address, and also DHCP [RFC2131].
			This extension is defined only as a solution for use cases in which
			PANA authentication is required prior to any kind of IP address
			allocation or configuration. It is not intended to become the
			default mode of operation for PANA.
	1.1. Specification of Requirements		1.1. Specification of Requirements
	In this document, several words are used to signify the requirements		In this document, several words are used to signify the requirements
	of the specification. These words are often capitalized. The key		of the specification. These words are often capitalized. The key
	words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",		words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
	"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document		"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document
	are to be interpreted as described in [RFC2119].		are to be interpreted as described in [RFC2119].
	2. Details		2. Details
End of changes. 5 change blocks.
	4 lines changed or deleted		9 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/