1 / 22

WP03: Collaborative work environment

WP03: Collaborative work environment. Index. Workpackage objective Point to point applications migration Multipoint collaborative applications migration LONG platform service deployment. Objectives. Define guidelines for applications migration. Basic point to point applications.

bronson
Télécharger la présentation

WP03: Collaborative work environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP03: Collaborative work environment

  2. Index • Workpackage objective • Point to point applications migration • Multipoint collaborative applications migration • LONG platform service deployment

  3. Objectives • Define guidelines for applications migration. • Basic point to point applications. • Advanced collaborative applications. • Select and adapt a selected applications set. • Setup basic services. • Adapt representative services. • mgen • Streaming video • ISABEL • Collaborative application. • Support various network scenarios.

  4. Participants and efforts role effort scheduled 3pm 5pm 5,2pm 6pm 11pm 34,9pm

  5. Milestones D31: Point to point application migration D32: Guidelines for CSCW applications migration D33: Applic. over special networks M24 M0 M6 M18 M12 M3.1: First applications migration M3.2: CSCW application migration over special networks

  6. Point to point application migration guidelines • When source code is available. • Review communication APIs • C • C++ • SOCKS • Java • Scripting languages • Perl • TCL (not available) • When source code is not available. • Dual-stack should be provided.

  7. IPv6 & IPv4 interoperability

  8. Protocol independent architecture

  9. Common porting problems • Allocate enough memory for new structures • Portability of System Socket API • IP address management • Fully Qualified Domain Names should be used • Remove application dependencies on the IP addresses • Use network independent identifiers • IP address parser • IPv4_address:port • Literal IPv6 addresses in URLs specifications (RFC-2732) • http://[2001:720:1500:1::A100]:80/ • Allow correct lookback (::1) communication • Size of Application Datagram Payload (MTU) • Fragmentation managed by application

  10. Collaborative applications migration guidelines • Application communication models • Interpersonal applications (point to point bidirectional) • Broadcast applications (one way communication) • Groupware applications (group bidirectional communication) • Group communication models • Graph topology with many point to point connections • IPv4 and IPv6 allowed (with dual stack) • Multicast • Broadcast (only IPv4 nodes are allowed) • IP multicast (only IPv6 nodes are allowed)

  11. Interaction between application instances application instance with media objects application instance with media objects application control and media manipulation application control application control media management and temporal adjusments with synchronization media management media management QoS connection end-to-end QoS control end-to-end QoS control network subsystem

  12. ISABEL Architecture Interactive Site Kernel Participant registry Local configuration SESSION COORDINATION LAYER Audio adaptation Video adaptation Pointer adaptation ... Ftp adaptation Unrel. trans. adaptation Rel. trans. adaptation Notepad adaptation Whiteboard adaptation ADAPTATIONLAYER Audio Video Pointer Slides Notepad ... Whiteboard COMPONENTSLAYER Irouter: unreliable transport Reliable transport QoS and NETWORK LAYER Network

  13. ISABEL Architecture • Sessioncoordinationlayer: • change application Node Unique Identifiers • Component adaptation layer • Cooperative adaptation layer • QoS networklayer • Management and reliable componentes (reliable service) • Multimedia real time broadcast (unreliable service) PORTING TO IPv6

  14. ISABEL IPv4 & IPv6 interoperability • ISABEL over IPv4 networks • Graph topology • Multicast topology • Combination : multicast islands interconnection • ISABEL over IPv6 networks • Graph topology • Multicast topology • Combination : multicast islands interconnection • ISABEL over IPv4/IPv6 networks • Graph topology • Combination : multicast islands interconnection

  15. LONG platform : services deployment

  16. Sendmail 8.12.1 is used to provide SMTP access, that supports IPv6 and IPv4 sockets to receive and send mail. Mail can be sent to Internet from LONG network using cantonal Mail Server. Mail to local users is saved in cantonal. A domain has been registered and will be configured to allow incoming mail. The domain is @ist-long.com A POP3 server will be configured to allow LONG users to get their mail. MAIL clientA.partner1.long ClientA IPv6 LONG Backbone 3FFE:3328:6:2::/64 Mail Server cantonal.tid.long ( 3FFE:3328:6:2::5) Internet State:

  17. UEV IPv4 Translation Mechanism Internet LONG Partner IPv6 News Server IPv6 News Server IPv4 News Server News Client IPv4 News Client IPv6 News Client IPv4 News Client IPv6 News • Several servers/clients available • Servers • INN (*nix) - with different branches of IPv6 development • SN (*nix) • ?Exchange/IIS? (Windows) • Clients • Mozilla (*nix, Windows, others) • TRN (*nix) • NN-TK (*nix) • TIN (*nix) • Already running an IPv6/IPv4 news server • Using INN 2.3.2 +North IPv6 Patch State:

  18. Aim: seamlessly connect IPv4 and IPv6 clients FreeBSD and Linux IRC servers (ircd) Coexistence between IPv4 and IPv6 achieved Using TRT translator between IPv6-only and IPv4-only servers IRC server application allowing connections from both IPv4 and IPv6 servers Frequently used inside the project to coordinate inter-partner experiments External users can join any channel IRC Client UC3M network TRT translator IPv4 server IPv6 server IPv6 LONG Backbone Client IPv6 server IPv4 server UPM network State:

  19. LDAP server OpenLDAP implementation from University of Michigan. The last stable release is 2.0.2.1. Local functionality tests. Distributed data bases UPC (master) and UPM (secondary). Future work: Integrate UC3M Interaction with IPv4/IPv6 clients and IPv4/IPv6 servers through translation mechanisms (NAT-PT). Clients with graphic interface UPC LDAP primary server IPv6 UPM LDAP server IPv6 LDAP LONG IPv6 network NAT-PT UC3M LDAP server IPv4 client IPv6 graphic client IPv4 State:

  20. Setup a Web server per site Apache 2.0.32 Public LONG Web project IPv4 : http://long.ccaba.upc.es IPv6 : http://www.upc.long Web navigators Lynx Mozilla 0.9.4 Netscape 4.79 WEB tools Interface to some basic tools WEB Internet IPv4 long.ccaba.upc.es www.tid.long www.upc.long LONG IPv6 network www.ptin.long www.upm.long www.uev.long www.uc3m.long State:

  21. VideoStreaming client It is an open-source video player (MPlayer for Linux) modified to use IPv6 sockets. VideoStreaming server For TCP, it is just a HTTP server. In this case, it is a simple HTTP server developed by TID. TCP connections used as transport layer are fully supported. UDP Unicast and Multicast are under development. Future work: Finish the UDP client and server. Multicast tests using FreeBSD as router. Videostreaming Server (UPM) LONG IPv6 network Client (TID) State:

  22. The aim is to support synchronous collaborative work inside the project ISABEL IPv6 version 4.5 All sites connected to LONG network Used to maintain many small coordination project meetings All LONG partners connected IPv6 LONG network is used Pending tasks Test mobile IP clients Test over asymmetric channels UC3M PTIN TIDd UPM UEV TID UPC Teleconference NORTEL State:

More Related