draft-ietf-forces-lfb-lib-10.txt   draft-ietf-forces-lfb-lib-11.txt 
Internet Engineering Task Force W. Wang Internet Engineering Task Force W. Wang
Internet-Draft Zhejiang Gongshang University Internet-Draft Zhejiang Gongshang University
Intended status: Standards Track E. Haleplidis Intended status: Standards Track E. Haleplidis
Expires: August 1, 2013 University of Patras Expires: September 16, 2013 University of Patras
K. Ogawa K. Ogawa
NTT Corporation NTT Corporation
C. Li C. Li
Hangzhou H3C Tech. Co., Ltd. Hangzhou DPtech
J. Halpern J. Halpern
Ericsson Ericsson
January 28, 2013 March 15, 2013
ForCES Logical Function Block (LFB) Library ForCES Logical Function Block (LFB) Library
draft-ietf-forces-lfb-lib-10 draft-ietf-forces-lfb-lib-11
Abstract Abstract
This document defines basic classes of Logical Function Blocks (LFBs) This document defines basic classes of Logical Function Blocks (LFBs)
used in the Forwarding and Control Element Separation (ForCES). The used in the Forwarding and Control Element Separation (ForCES). The
basic LFB classes are defined according to ForCES FE model and ForCES basic LFB classes are defined according to ForCES FE model and ForCES
protocol specifications, and are scoped to meet requirements of protocol specifications, and are scoped to meet requirements of
typical router functions and considered as the basic LFB library for typical router functions and considered as the basic LFB library for
ForCES. The library includes the descriptions of the LFBs and the ForCES. The library includes the descriptions of the LFBs and the
XML definitions. XML definitions.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 1, 2013. This Internet-Draft will expire on September 16, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 112, line 7 skipping to change at page 112, line 7
| 0x0000000B | InvalidIPv6DstAddr | See Section 4.4 | | 0x0000000B | InvalidIPv6DstAddr | See Section 4.4 |
+--------------+---------------------------------+------------------+ +--------------+---------------------------------+------------------+
Table 4 Table 4
Validate Error ID 0x80000000-0xFFFFFFFF Validate Error ID 0x80000000-0xFFFFFFFF
Validate Error IDs in this range are reserved for vendor private Validate Error IDs in this range are reserved for vendor private
extensions and are the responsibility of individuals. extensions and are the responsibility of individuals.
11. Security Considerations 11. Security Considerations
The ForCES framework document [RFC3746] provides a comprehensive The ForCES framework document [RFC3746] provides a description of the
security analysis for the overall ForCES architecture. For example, security needs for the overall ForCES architecture. For example, the
the ForCES protocol entities must be authenticated per the ForCES ForCES protocol entities must be authenticated per the ForCES
requirements before they can access the information elements requirements before they can access the information elements
described in this document via ForCES. Access to the information described in this document via ForCES. The ForCES protocol document
contained in this document is accomplished via the ForCES [RFC5810] includes a comprehensive set of security mechanisms and
protocol[RFC5810], which is defined in separate documents, and thus which implementations are required to support, and which deployments
the security issues will be addressed there. can use to meet these needs. The LFBs defined in this document are
similar to other LFBs modeled by the FE model [RFC5812]. In
particular, they have the same security properties. Thus the
security mechanisms and considerations from the ForCES protocol
document [RFC5810] apply and address the issues.
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC5810] Doria, A., Hadi Salim, J., Haas, R., Khosravi, H., Wang, [RFC5810] Doria, A., Hadi Salim, J., Haas, R., Khosravi, H., Wang,
W., Dong, L., Gopal, R., and J. Halpern, "Forwarding and W., Dong, L., Gopal, R., and J. Halpern, "Forwarding and
Control Element Separation (ForCES) Protocol Control Element Separation (ForCES) Protocol
Specification", RFC 5810, March 2010. Specification", RFC 5810, March 2010.
skipping to change at page 114, line 31 skipping to change at page 114, line 31
Email: ehalep@ece.upatras.gr Email: ehalep@ece.upatras.gr
Kentaro Ogawa Kentaro Ogawa
NTT Corporation NTT Corporation
Tokyo, Tokyo,
Japan Japan
Email: ogawa.kentaro@lab.ntt.co.jp Email: ogawa.kentaro@lab.ntt.co.jp
Chuanhuang Li Chuanhuang Li
Hangzhou H3C Tech. Co., Ltd. Hangzhou DPtech
310 Liuhe Road, Zhijiang Science Park 6th Floor, Zhongcai Group, 68 Tonghe Road, Binjiang District
Hangzhou, 310053 Hangzhou, 310051
P.R.China P.R.China
Phone: +86 571 86760000
Email: chuanhuang_li@zjsu.edu.cn Email: chuanhuang_li@zjsu.edu.cn
Halpern Joel Halpern Joel
Ericsson Ericsson
P.O. Box 6049 P.O. Box 6049
Leesburg, 20178 Leesburg, 20178
VA VA
Phone: +1 703 371 3043 Phone: +1 703 371 3043
Email: joel.halpern@ericsson.com Email: joel.halpern@ericsson.com
 End of changes. 9 change blocks. 
16 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/