rfc9296v2.txt		rfc9296.txt
	skipping to change at line 192 ¶		skipping to change at line 192 ¶
	interface.		interface.
	If the P2P interface is administratively up, then the "oper-status"		If the P2P interface is administratively up, then the "oper-status"
	(defined in [RFC8343]) of that interface SHALL fully reflect the		(defined in [RFC8343]) of that interface SHALL fully reflect the
	state of the underlying interface; if the P2P interface is		state of the underlying interface; if the P2P interface is
	administratively down, then the "oper-status" of that interface SHALL		administratively down, then the "oper-status" of that interface SHALL
	be down. Examples can be found in Appendix A.		be down. Examples can be found in Appendix A.
	4. Security Considerations		4. Security Considerations
	The writeable attribute "admin-status" of the p2povervlan ifType is		The writable attribute "admin-status" of the p2povervlan ifType is
	inherited from [RFC8343]. Other objects associated with the		inherited from [RFC8343]. Other objects associated with the
	p2povervlan ifType are read-only. With this in mind, the		p2povervlan ifType are read-only. With this in mind, the
	considerations discussed in Section 7 of [RFC8343] otherwise apply to		considerations discussed in Section 7 of [RFC8343] otherwise apply to
	the p2povervlan ifType.		the p2povervlan ifType.
	5. IANA Considerations		5. IANA Considerations
	In the "Interface Types (ifType)" registry, value 303 is assigned to		In the "Interface Types (ifType)" registry, value 303 is assigned to
	p2pOverLan [Assignment]. As this document explains how the		p2pOverLan [Assignment]. As this document explains how the
	p2pOverLan (303) ifType is to be used, IANA has amended the reference		p2pOverLan (303) ifType is to be used, IANA has amended the reference
End of changes. 1 change blocks.
	1 lines changed or deleted		1 lines changed or added
This html diff was produced by rfcdiff 1.48.