< draft-chen-rtgwg-key-table-yang-01.txt		draft-chen-rtgwg-key-table-yang-02.txt >
	Internet Draft I. Chen		Internet Draft I. Chen
	<draft-chen-rtgwg-key-table-yang-01.txt> Ericsson		<draft-chen-rtgwg-key-table-yang-02.txt> Ericsson
	Intended Status: Standards Track		Intended Status: Standards Track
	Expires in 6 months November 2, 2015		Expires in 6 months November 2, 2015
	YANG Data Model for RFC 7210 Key Table		YANG Data Model for RFC 7210 Key Table
	<draft-chen-rtgwg-key-table-yang-00.txt>		<draft-chen-rtgwg-key-table-yang-02.txt>
	Status of this Memo		Status of this Memo
	Distribution of this memo is unlimited.		Distribution of this memo is unlimited.
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 14, line 17 ¶		skipping to change at page 14, line 17 ¶
	"should be considered for processing received traffic.";		"should be considered for processing received traffic.";
	}		}
	leaf accept-lifetime-end {		leaf accept-lifetime-end {
	type lifetime-type;		type lifetime-type;
	mandatory true;		mandatory true;
	description		description
	"Specify the latest date and time at which this key " +		"Specify the latest date and time at which this key " +
	"should be considered for processing received traffic.";		"should be considered for processing received traffic.";
	}		}
	}		}
	} }		}
			}
	<CODE ENDS>		<CODE ENDS>
	5. Usage		5. Usage
	A routing protocol that requires cryptographic key authentication		A routing protocol that requires cryptographic key authentication
	should customize the key table base model such that the resulting		should customize the key table base model such that the resulting
	YANG modules describe all the necessary attributes and also the valid		YANG modules describe all the necessary attributes and also the valid
	values of these attributes.		values of these attributes.
	skipping to change at page 19, line 6 ¶		skipping to change at page 19, line 6 ¶
	"should be identical to the value of " +		"should be identical to the value of " +
	"ospf-local-key-name.";		"ospf-local-key-name.";
	}		}
	description		description
	"An OSPF security association, i.e. key";		"An OSPF security association, i.e. key";
	}		}
	description		description
	"An OSPF key chain";		"An OSPF key chain";
	}		}
	} }		}
			}
	6. Security Consideration.		6. Security Consideration.
	TBD.		TBD.
	7. IANA Considerations		7. IANA Considerations
	TBD.		TBD.
	8. References		8. References
	skipping to change at page 19, line 30 ¶		skipping to change at page 19, line 31 ¶
	[RFC7210] Housley, R., Polk, T., Hartman, S., and D. Zhang,		[RFC7210] Housley, R., Polk, T., Hartman, S., and D. Zhang,
	"Database of Long-Lived Symmetric Cryptographic Keys", RFC		"Database of Long-Lived Symmetric Cryptographic Keys", RFC
	7210, April 2014, <http://www.rfc-		7210, April 2014, <http://www.rfc-
	editor.org/info/rfc7210>.		editor.org/info/rfc7210>.
	[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for		[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
	the Network Configuration Protocol (NETCONF)", RFC 6020,		the Network Configuration Protocol (NETCONF)", RFC 6020,
	DOI 10.17487/RFC6020, October 2010, <http://www.rfc-		DOI 10.17487/RFC6020, October 2010, <http://www.rfc-
	editor.org/info/rfc6020>.		editor.org/info/rfc6020>.
	Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A.		[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
	Bierman, Ed., "Network Configuration Protocol (NETCONF)",		and A. Bierman, Ed., "Network Configuration Protocol
	RFC 6241, DOI 10.17487/RFC6241, June 2011,		(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
	<http://www.rfc-editor.org/info/rfc6241>.		<http://www.rfc-editor.org/info/rfc6241>.
	[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.
	8.2. Informative References		8.2. Informative References
	[I-D.acee-rtg-yang-key-chain] Lindem, A., Qu, Y., Yeung, D., Chen,		[I-D.acee-rtg-yang-key-chain] Lindem, A., Qu, Y., Yeung, D., Chen,
	I., Zhang, J., and Y. Yang, "Key Chain YANG Data Model",		I., Zhang, J., and Y. Yang, "Key Chain YANG Data Model",
	draft-acee-rtg-yang-key-chain-09 (work in progress),		draft-acee-rtg-yang-key-chain-09 (work in progress),
End of changes. 5 change blocks.
	7 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/