< draft-thubert-6lo-rfc6775-update-reqs-00.txt		draft-thubert-6lo-rfc6775-update-reqs-01.txt >
	6Lo P. Thubert, Ed.		6Lo P. Thubert, Ed.
	Internet-Draft cisco		Internet-Draft cisco
	Intended status: Standards Track June 19, 2014		Intended status: Standards Track June 19, 2014
	Expires: December 19, 2014		Expires: December 19, 2014
	Requirements for an update to 6LoWPAN ND		Requirements for an update to 6LoWPAN ND
	draft-thubert-6lo-rfc6775-update-reqs-00		draft-thubert-6lo-rfc6775-update-reqs-01
	Abstract		Abstract
	Work presented at the 6TiSCH and 6MAN working groups suggest a number		Work presented at the 6TiSCH and 6MAN working groups suggest a number
	of enhancements to the 6LoWPAN ND mechanism. This document		of enhancements to the 6LoWPAN ND mechanism. This document
	elaborates on such requirements.		elaborates on such requirements.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	skipping to change at page 8, line 53 ¶		skipping to change at page 8, line 53 ¶
	refrain from sending gratuitous NA(O) or other form of distributed		refrain from sending gratuitous NA(O) or other form of distributed
	ND cache clean-up over the backbone. For instance, the flag		ND cache clean-up over the backbone. For instance, the flag
	should be reset after the DAD operation upon address formation.		should be reset after the DAD operation upon address formation.
	5. Security Considerations		5. Security Considerations
	This specification expects that the link layer is sufficiently		This specification expects that the link layer is sufficiently
	protected, either by means of physical or IP security for the		protected, either by means of physical or IP security for the
	Backbone Link or MAC sublayer cryptography. In particular, it is		Backbone Link or MAC sublayer cryptography. In particular, it is
	expected that the LLN MAC provides secure unicast to/from the		expected that the LLN MAC provides secure unicast to/from the
	Backbone Router and secure 6BBRoadcast from the Backbone Router in a		Backbone Router and secure broadcast from the Backbone Router in a
	way that prevents tempering with or replaying the RA messages.		way that prevents tempering with or replaying the RA messages.
	The use of EUI-64 for forming the Interface ID in the link local		The use of EUI-64 for forming the Interface ID in the link local
	address prevents the usage of Secure ND ([RFC3971] and [RFC3972]) and		address prevents the usage of Secure ND ([RFC3971] and [RFC3972]) and
	address privacy techniques. Considering the envisioned deployments		address privacy techniques. Considering the envisioned deployments
	and the MAC layer security applied, this is not considered an issue		and the MAC layer security applied, this is not considered an issue
	at this time.		at this time. It is envisioned that the device could form a single
			CGA-based Unique Interface ID (CUID) to securely bind all of its
			addresses. The CUID would be used as Unique Interface Identifier in
			the ARO option and the Secure ND procedures would be changed to use
			it as opposed to the source IPv6 address.
	6. IANA Considerations		6. IANA Considerations
	A new type is requested for an ND option.		A new type is requested for an ND option.
	7. Acknowledgments		7. Acknowledgments
	TBD		Samita, Erik, JP, Eric, Thomas, you will all recognize your influence
			in this work...
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2460] Deering, S.E. and R.M. Hinden, "Internet Protocol, Version		[RFC2460] Deering, S.E. and R.M. Hinden, "Internet Protocol, Version
	6 (IPv6) Specification", RFC 2460, December 1998.		6 (IPv6) Specification", RFC 2460, December 1998.
	skipping to change at page 10, line 40 ¶		skipping to change at page 10, line 44 ¶
	Palattella, M., Thubert, P., Watteyne, T. and Q. Wang,		Palattella, M., Thubert, P., Watteyne, T. and Q. Wang,
	"Terminology in IPv6 over the TSCH mode of IEEE		"Terminology in IPv6 over the TSCH mode of IEEE
	802.15.4e", Internet-Draft draft-ietf-6tisch-		802.15.4e", Internet-Draft draft-ietf-6tisch-
	terminology-00, November 2013.		terminology-00, November 2013.
	[I-D.ietf-roll-terminology]		[I-D.ietf-roll-terminology]
	Vasseur, J., "Terms used in Routing for Low power And		Vasseur, J., "Terms used in Routing for Low power And
	Lossy Networks", Internet-Draft draft-ietf-roll-		Lossy Networks", Internet-Draft draft-ietf-roll-
	terminology-13, October 2013.		terminology-13, October 2013.
	[I-D.van-beijnum-multi-mtu]
	Beijnum, I., "Extensions for Multi-MTU Subnets", Internet-
	Draft draft-van-beijnum-multi-mtu-03, July 2010.
	[RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A. and P.		[RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A. and P.
	Thubert, "Network Mobility (NEMO) Basic Support Protocol",		Thubert, "Network Mobility (NEMO) Basic Support Protocol",
	RFC 3963, January 2005.		RFC 3963, January 2005.
	[RFC3971] Arkko, J., Kempf, J., Zill, B. and P. Nikander, "SEcure		[RFC3971] Arkko, J., Kempf, J., Zill, B. and P. Nikander, "SEcure
	Neighbor Discovery (SEND)", RFC 3971, March 2005.		Neighbor Discovery (SEND)", RFC 3971, March 2005.
	[RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)",		[RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)",
	RFC 3972, March 2005.		RFC 3972, March 2005.
End of changes. 5 change blocks.
	8 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/