draft-ietf-forces-applicability-01.txt   draft-ietf-forces-applicability-02.txt 
Internet Engineering Task Force ForCES WG Internet Engineering Task Force ForCES WG
INTERNET-DRAFT Alan Crouch/Intel INTERNET-DRAFT Alan Crouch/Intel
draft-ietf-forces-applicability-01.txt Mark Handley/ICIR draft-ietf-forces-applicability-02.txt Mark Handley/ICIR
14 December 2002 26 June 2003
Expires: June 2003 Expires: December 2003
ForCES Applicability Statement ForCES Applicability Statement
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
skipping to change at page 8, line 39 skipping to change at page 8, line 39
[1]. The ForCES protocol assumes that the CE and FE are in the same [1]. The ForCES protocol assumes that the CE and FE are in the same
administration, and have shared secrets as a means of administration. administration, and have shared secrets as a means of administration.
Whilst it might be technically feasible to have the CE and FE Whilst it might be technically feasible to have the CE and FE
administered independently, we strongly discourage such uses, because administered independently, we strongly discourage such uses, because
they would require a significantly different trust model from that they would require a significantly different trust model from that
ForCES assumes. ForCES assumes.
7. Normative 7. Normative
[1] Anderson, T et. al., "Requirements for Separation of IP Control and [1] Anderson, T et. al., "Requirements for Separation of IP Control and
Forwarding", draft-ietf-forces-requirements-07.txt, October 2002 Forwarding", draft-ietf-forces-requirements-09.txt, May 2003
[2] ForCES Protocol Specification (to-be-written) [2] ForCES Protocol Specification (to-be-written)
8. Informative 8. Informative
[3] Salim, J e. al., "Netlink as an IP Services Protocol", draft-ietf- [3] Salim, J e. al., "Netlink as an IP Services Protocol", draft-ietf-
forces-netlink-03.txt, June 2002 forces-netlink-04.txt, December 2002
[4] Doria, A, Sundell, K, Hellstrand, F, Worster, T, "General Switch [4] Doria, A, Sundell, K, Hellstrand, F, Worster, T, "General Switch
Management Protocol (GSMP) V3" RFC 3292, June 2002 Management Protocol (GSMP) V3" RFC 3292, June 2002
[5] Andersson et al., "LDP Specification" RFC 3036, January 2001 [5] Andersson et al., "LDP Specification" RFC 3036, January 2001
[6] Bradner, S, "Key words for use in RFCs to Indicate Requirement [6] Bradner, S, "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, Harvard University, March 1997 Levels", RFC 2119, Harvard University, March 1997
[7] F. Cuervo et al., "Megaco Protocol Version 1.0" RFC 3015, November [7] F. Cuervo et al., "Megaco Protocol Version 1.0" RFC 3015, November
2000 2000
9. Acknowledgments 9. Acknowledgments
The authors wish to thank Jamal Hadi, Hormuzd Khosravi, Vip Sharma, and The authors wish to thank Jamal Hadi Salim, Hormuzd Khosravi, Vip
many others for their invaluable contributions. Sharma, and many others for their invaluable contributions.
10. Author's Addresses 10. Author's Addresses
Alan Crouch Alan Crouch
Intel Intel
2111 NE 25th Avenue 2111 NE 25th Avenue
Hillsboro, OR 97124 USA Hillsboro, OR 97124 USA
Phone: +1 503 264 2196 Phone: +1 503 264 2196
Email: alan.crouch@intel.com Email: alan.crouch@intel.com
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/