[MEXT] Finishing RFC 3775bis

["Charles E. Perkins" <[e-mail]>]

Hello folks,

One of the new requirements for rfc3775bis is a section
detailing the changes from RFC 3775.  Here's what I wrote
up.  If I forgot one, please remind me and I will
add it.  It's quite painful to go through rfcdiff, yow.
The numbers are the issue numbers from:
	http://trac.tools.ietf.org/wg/mext/trac/report/6

===========================================================

#1 	Last Accepted SQN [Ahmad Muhanna] 	

	Solution: specify that the mobile node update its binding
	sequence number to match the sequence number given in the
	Binding Acknowledgement (if the Binding Acknowledgement
	correctly passes authentication and the status is 135
	(Sequence Number out of window).


#4 	Remove references to site-local addresses [George Tsirtsis] 	

	fixed.

#5 	Wrong protocol number used in discussion about checksum
		pseudo-header: 	

	fixed.

#8 	Application using the care-of address [Julien Laganier]

	Cite IPv6 Socket API for Source Address Selection [RFC5014].

#10 	The usage of "HA lifetime" [Ryuji Wakikawa] 	

	The mobile node SHOULD store the list of home agents for later
	use in case the home agent currently managing the mobile node's
	care-of address forwarding should become unavailable.

#11 	De-registration when returning home [Vijay Devarapalli] 	

	To be able to send and receive packets using its home address
	from the home link, the mobile node MUST send a Binding Update to
	its home agent to instruct its home agent to no longer intercept
	or tunnel packets for it. Until the mobile node sends such a
	de-registration Binding Update, it MUST NOT attempt to send and
	receive packets using its home address from the home link.


#12 	BErr sent by HA too, not only by CN [Alexandru Petrescu]

	Fixed.
  	
#13 	Home Link Detection [Suresh Krishnan] 	

	Proposal: add new section [11.5.2] for Home Link Detection,
	drawing on Internet Draft draft-krishnan-mext-hld.

#14 	References to Bootstrapping [Vijay Devarapalli] 	

	Cited "Mobile IPv6 Bootstrapping in Split Scenario", RFC 5026

#17 	Multi-homed mobile node can cause routing loop between
		home agents [Benjamin Lim]

	Added advisory security considerations in section 15.1, to
	highlight risk of routing loop among HAs (e.g., in 3GPP):

	A malicious mobile node associated to multiple home agents
	could create a routing loop amongst them. This would happen
	when a mobile node binds one home address located on a first
	home agent to another home address on a second home agent.

#18 	Subject: Issues regarding Home Address Option & ICMP /
						Binding errors 	
						[Fabian Mauchle]

	Proposal: Use the value in the Next Header field {50 (ESP),
	51 (AH), 135 (Mobility Header)} to determine, if a Binding
	Cache entry is required.

	Proposal: To avoid spoofing, add to the first paragraph in
	11.3.6: If the source of the ICMP error message is a Home
	Agent, it MUST be ignored.

	Proposal: If the Binding Error Message was sent by the Home
	Agent, the Mobile Node SHOULD send a Binding Update to the
	Home Agent according to Section 11.7.1.
	

#19 	BU de-registration race condition [Kilian Weniger] 	

	Problem arises if de-registration arrives at Home Agent
	before an immediately preceding Binding Update.

	Solution: Home Agent defers BCE removal after sending
	the Binding Acknowledgement.

#6 	Minor editorial corrections and updates 	

NOT done:
#3 	BRR, BErr are sent by HA too, not only by CN
					[Alexandru Petrescu] 	
#7 	DSMIPv6 BU format and RFC 3775 [Tero Kauppinen] 	
#9 	Simultaneous Mobility [Ashutosh Dutta] 	
#15 	BRR sent by HA too, not only by CN [Ahmad Muhanna] 	
#16 	HA behaviour upon MN returning Home [Pascal Thubert] 	


===========================================================

Regards,
Charlie P.