< draft-yegin-pana-unspecified-addr-04.txt		draft-yegin-pana-unspecified-addr-05.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: Informational Y. Ohba
	Expires: September 29, 2011 Toshiba		Expires: June 18, 2012 Toshiba
	L. Morand		L. Morand
	Orange Labs		Orange Labs
	J. Kaippallimalil		J. Kaippallimalil
	Huawei USA		Huawei USA
	March 28, 2011		December 16, 2011
	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-04		draft-yegin-pana-unspecified-addr-05
	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 September 29, 2011.		This Internet-Draft will expire on June 18, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 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 6, line 8 ¶		skipping to change at page 6, line 8 ¶
	drop any PAR that is L2-broadcast and without carrying a Token AVP.		drop any PAR that is L2-broadcast and without carrying a Token AVP.
	Any legacy PaC that does not implement this specification will		Any legacy PaC that does not implement this specification will
	automatically drop the incoming PAR that carries the Token AVP as		automatically drop the incoming PAR that carries the Token AVP as
	this is an unrecognized AVP. This is the standard behavior defined		this is an unrecognized AVP. This is the standard behavior defined
	in [RFC5191].		in [RFC5191].
	4. PAA Behavior		4. PAA Behavior
	If a PAA receives a PCI whose source IP address is unspecified but		If a PAA receives a PCI whose source IP address is unspecified but
	that does not carry a Token AVP, then it SHALL drop the PCI. The PAA		that does not carry a Token AVP, then it SHALL drop the PCI.
	SHALL ignore a Token AVP if it is contained in any message other than
	PCI.
	When the PAA needs to send a packet to a PaC that is using an		When the PAA needs to send a packet to a PaC that is using an
	unspecified IP address, then the PAA shall set the destination IP		unspecified IP address, then the PAA shall set the destination IP
	address to 255.255.255.255. The PAA SHOULD set the destination L2		address to 255.255.255.255. The PAA SHOULD set the destination L2
	address to the source L2 address retrieved from the incoming PaC		address to the source L2 address retrieved from the incoming PaC
	packet, when possible; otherwise set to L2 broadcast address. If		packet, when possible; otherwise set to L2 broadcast address. If
	this is the very first PAR message sent to L2 broadcast address in		this is the very first PAR message sent to L2 broadcast address in
	response to a PCI message containing a Token AVP, then the PAA SHALL		response to a PCI message containing a Token AVP, then the PAA SHALL
	include a Token AVP copied from the PCI. The PAA SHOULD NOT include		include a Token AVP copied from the PCI. The PAA SHOULD NOT include
	a Token AVP in any other PANA message, as an already-assigned PANA		a Token AVP in any other PANA message, as an already-assigned PANA
	skipping to change at page 9, line 36 ¶		skipping to change at page 9, line 36 ¶
	Phone: +33 1 4529 62 57		Phone: +33 1 4529 62 57
	Email: Lionel.morand@orange-ftgroup.com		Email: Lionel.morand@orange-ftgroup.com
	John Kaippallimalil		John Kaippallimalil
	Huawei USA		Huawei USA
	1700 Alma Dr., Suite 500		1700 Alma Dr., Suite 500
	Plano, TX 75082		Plano, TX 75082
	USA		USA
	Phone: +1 214 606 2005		Phone: +1 214 606 2005
	Email: jkaippal@huawei.com		Email: john.kaippallimalil@huawei.com
End of changes. 6 change blocks.
	8 lines changed or deleted		6 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/