draft-ietf-forces-interoperability-01.txt   draft-ietf-forces-interoperability-02.txt 
Internet Engineering Task Force E. Haleplidis Internet Engineering Task Force E. Haleplidis
Internet-Draft University of Patras Internet-Draft University of Patras
Intended status: Informational K. Ogawa Intended status: Informational K. Ogawa
Expires: December 5, 2009 NTT Corporation Expires: December 31, 2009 NTT Corporation
X. Wang X. Wang
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
June 3, 2009 C. Li
Zhejiang Gongshang University
June 29, 2009
ForCES Interoperability Draft ForCES Interoperability Draft
draft-ietf-forces-interoperability-01 draft-ietf-forces-interoperability-02
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 37
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 5, 2009. This Internet-Draft will expire on December 31, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 27 skipping to change at page 2, line 27
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. ForCES Protocol . . . . . . . . . . . . . . . . . . . . . 4 2.1. ForCES Protocol . . . . . . . . . . . . . . . . . . . . . 4
2.2. ForCES Model . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. ForCES Model . . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Transport mapping layer . . . . . . . . . . . . . . . . . 4 2.3. Transport mapping layer . . . . . . . . . . . . . . . . . 4
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Date, Location and Access . . . . . . . . . . . . . . . . . . 8 4. Date, Location and Access . . . . . . . . . . . . . . . . . . 8
4.1. Date . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.1. Date . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2. Location . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.2. Location . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3. Access . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.3. Access . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5. Testbed architecture . . . . . . . . . . . . . . . . . . . . . 9 5. Testbed architecture . . . . . . . . . . . . . . . . . . . . . 10
5.1. Local configuration . . . . . . . . . . . . . . . . . . . 9 5.1. Local configuration . . . . . . . . . . . . . . . . . . . 10
5.2. Distributed configuration . . . . . . . . . . . . . . . . 10 5.2. Distributed configuration . . . . . . . . . . . . . . . . 11
6. Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.1. Scenario 1 - Pre-association Setup . . . . . . . . . . . . 11 6.1. Scenario 1 - Pre-association Setup . . . . . . . . . . . . 12
6.2. Scenario 2 - TML priority channels connection . . . . . . 12 6.2. Scenario 2 - TML priority channels connection . . . . . . 13
6.3. Scenario 3 - Association Setup - Association Complete . . 12 6.3. Scenario 3 - Association Setup - Association Complete . . 13
6.4. Scenario 4 - CE query . . . . . . . . . . . . . . . . . . 12 6.4. Scenario 4 - CE query . . . . . . . . . . . . . . . . . . 13
6.5. Scenario 5 - Heartbeat monitoring . . . . . . . . . . . . 13 6.5. Scenario 5 - Heartbeat monitoring . . . . . . . . . . . . 14
6.6. Scenario 6 - Simple Config Command . . . . . . . . . . . . 13 6.6. Scenario 6 - Simple Config Command . . . . . . . . . . . . 14
6.7. Scenario 7 - Association Teardown . . . . . . . . . . . . 13 6.7. Scenario 7 - Association Teardown . . . . . . . . . . . . 14
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17 9. Security Considerations . . . . . . . . . . . . . . . . . . . 18
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
10.1. Normative References . . . . . . . . . . . . . . . . . . . 18 10.1. Normative References . . . . . . . . . . . . . . . . . . . 19
10.2. Informative References . . . . . . . . . . . . . . . . . . 18 10.2. Informative References . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
1. Terminology and Conventions 1. Terminology and Conventions
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
skipping to change at page 6, line 24 skipping to change at page 6, line 24
Instance is represented by an LFB Instance ID. As a result, an Instance is represented by an LFB Instance ID. As a result, an
LFB Class ID associated with an LFB Instance ID uniquely specifies LFB Class ID associated with an LFB Instance ID uniquely specifies
an LFB existence. an LFB existence.
LFB Metadata - Metadata is used to communicate per-packet state LFB Metadata - Metadata is used to communicate per-packet state
from one LFB to another, but is not sent across the network. The from one LFB to another, but is not sent across the network. The
FE model defines how such metadata is identified, produced and FE model defines how such metadata is identified, produced and
consumed by the LFBs. It defines the functionality but not how consumed by the LFBs. It defines the functionality but not how
metadata is encoded within an implementation. metadata is encoded within an implementation.
LFB Attribute - Operational parameters of the LFBs that must be LFB Component - Operational parameters of the LFBs that must be
visible to the CEs are conceptualized in the FE model as the LFB visible to the CEs are conceptualized in the FE model as the LFB
attributes. The LFB attributes include, for example, flags, components. The LFB components include, for example, flags,
single parameter arguments, complex arguments, and tables that the single parameter arguments, complex arguments, and tables that the
CE can read and/or write via the ForCES protocol (see below). CE can read and/or write via the ForCES protocol (see below).
LFB Topology - Representation of how the LFB instances are LFB Topology - Representation of how the LFB instances are
logically interconnected and placed along the datapath within one logically interconnected and placed along the datapath within one
FE. Sometimes it is also called intra-FE topology, to be FE. Sometimes it is also called intra-FE topology, to be
distinguished from inter-FE topology. distinguished from inter-FE topology.
Pre-association Phase - The period of time during which an FE Pre-association Phase - The period of time during which an FE
Manager and a CE Manager are determining which FE(s) and CE(s) Manager and a CE Manager are determining which FE(s) and CE(s)
skipping to change at page 8, line 46 skipping to change at page 8, line 46
2. Via coach station. Get from the airport to the coach station via 2. Via coach station. Get from the airport to the coach station via
X93 bus towards the Kifissos Coach Station. At the Coach Station X93 bus towards the Kifissos Coach Station. At the Coach Station
there are buses to Patras every 30 minutes. The Bus to Patras there are buses to Patras every 30 minutes. The Bus to Patras
may take about 2:30 - 3:00 hours, and the ride of the X93 bus may may take about 2:30 - 3:00 hours, and the ride of the X93 bus may
take about 30 mins - 1hour depending on the traffic, so it's take about 30 mins - 1hour depending on the traffic, so it's
about 3:30 - 4:30 hours away with the wait at the Coach Station. about 3:30 - 4:30 hours away with the wait at the Coach Station.
3. Via Train. It is recommended you already have booked your ticket 3. Via Train. It is recommended you already have booked your ticket
beforehand as there are not many trains going to Patras, and beforehand as there are not many trains going to Patras, and
mostly are booked in advanced. Athens International Airport is mostly are booked in advanced. It is not recommended that you
connected to Athens Central Railway Station (Larissis Station) take the train to Patras, as you have to change at least 2
via the Suburban Rail. From there you can take a train to trains. In order to reach Patras from the Athens International
Patras. The train takes about 3:30 hours to go to Patras. The Airport you need to take the Suburban Rail to Neratziotissa.
Suburban rail will take you about 30 mins. So it's minimum 4:00 From there you must take ISAP to Pireaus. There you must change
hours away. again to Suburban Rail to reach Kiato. From Kiato you can catch
a train to Patras. It will take you at least 5 hours to reach
Patras.
5. Testbed architecture 5. Testbed architecture
Most FEs and CEs should be located locally at the University of Most FEs and CEs should be located locally at the University of
Patras premises. But if some parties would like to participate but Patras premises. But if some parties would like to participate but
cannot attend the interoperability test locally a connection over the cannot attend the interoperability test locally a connection over the
internet MAY be created. internet MAY be created.
The actual test will take place between FEs and CEs of different The actual test will take place between FEs and CEs of different
implementors with different permutations. implementors with different permutations.
All protocol messages of each scenario will be monitored using a All protocol messages of each scenario will be monitored using a
protocol network analyzer to test validity. The current tool that protocol network analyzer to test validity. Two tools shall be used:
will be used is a modified tcpdump [tcpdump].
o A modified tcpdump [tcpdump].
o A modified Ethereal [ethereal].
All NE's in all the scenarios will be comprised of one CE and one FE All NE's in all the scenarios will be comprised of one CE and one FE
from different implementors. from different implementors.
5.1. Local configuration 5.1. Local configuration
Hardware/Software (CEs and FEs) that will be located within the Hardware/Software (CEs and FEs) that will be located within the
University of Patras premises, will be connected together using University of Patras premises, will be connected together using
switches. switches.
skipping to change at page 18, line 48 skipping to change at page 19, line 48
of IP Control and Forwarding", RFC 3654, November 2003. of IP Control and Forwarding", RFC 3654, November 2003.
[RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal, [RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal,
"Forwarding and Control Element Separation (ForCES) "Forwarding and Control Element Separation (ForCES)
Framework", RFC 3746, April 2004. Framework", RFC 3746, April 2004.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[ethereal]
"Ethereal is a protocol analyzer. The specific ethereal
that will be used is an updated Ethereal, by Fenggen Jia,
that can analyze and decode the ForCES protocol
messages.", <http://peach.ease.lsoft.com/scripts/
wa.exe?A2=ind0906&L=FORCES&T=0&F=&S=&P=1048>.
[tcpdump] "Tcpdump is a linux protocol analyzer. The specific [tcpdump] "Tcpdump is a linux protocol analyzer. The specific
tcpdump that will be used is a modified tcpdump, by the tcpdump that will be used is a modified tcpdump, by Jamal
chair Jamal Hadi Salim, that can analyze and decode the Hadi Salim, that can analyze and decode the ForCES
ForCES protocol messages.". protocol messages.", <http://peach.ease.lsoft.com/scripts/
wa.exe?A2=ind0906&L=FORCES&T=0&F=&S=&P=2262>.
Authors' Addresses Authors' Addresses
Evangelos Haleplidis Evangelos Haleplidis
University of Patras University of Patras
Patras, Patras,
Greece Greece
Email: ehalep@ece.upatras.gr Email: ehalep@ece.upatras.gr
skipping to change at line 608 skipping to change at page 21, line 26
Tokyo, Tokyo,
Japan Japan
Email: ogawa.kentaro@lab.ntt.co.jp Email: ogawa.kentaro@lab.ntt.co.jp
Xin-ping Wang Xin-ping Wang
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
China China
Email: carly.wang@huawei.com Email: carly.wang@huawei.com
Chuanhuang Li
Zhejiang Gongshang University
18, Xuezheng Str., Xiasha University Town
Hangzhou, 310018
P.R.China
Phone: +86-571-28877751
Email: chuanhuang_li@pop.zjgsu.edu.cn
 End of changes. 12 change blocks. 
35 lines changed or deleted 50 lines changed or added

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