1 Agent Technology Scalability Consideration - January 2001 Seminar 37-331 Information &...

1

Agent TechnologyScalability Consideration - January 2001

Seminar 37-331 Information & Kommunikation WS 2000/1 http://www.tik.ee.ethz.ch/~huang/teach/

Christian Gloor & Hans-Peter Roetheli

2

Jini „Intelligent Agent Technology“

Jini ...... Java Intelligent Network Infrastructure

.. „connection technology based on Java“

Network.IQ No Limits in Space

Time.IQ No Performance Limitation

Awareness.IQ Any Transport ProtocolJini.Services.A not low level logistics Jini.Services.B

Jini.FedA Time + Space + Volume Agent.B


3

Jini = „Java Infrastructure + Logistics“

No Waste of Time ! Priority Queues, Speed of Light

How Far? Reach Mobility Flexibility Space

How Much ? Volume Bandwith Burstiness Talkers

• EndPoints Sources Sinks

• Intermediate Hops Broadcast Unicast (Multicast)

• Links Protocols Shared or Dedicated (Non-)Blocking


4

Scalable Implementation

AgendaPart A Jini Recap ETH SS2000 WS2001

Part B: Layer 4+ Beyond Jini RMI JVM

Part C: Layer 4- Below Transport Routing IP

Part D: End 2 End JVM Industry Adoption

Part E: Conclusion Readiness for Intelligent Agents


5

Consumer Orientation and Outside

http://n.ethz.ch/student/rkurmann/UC/ubi_spontan_foils/img1.htm

[3] Presented by Roland Kurmann ETHZ Fachseminar SS2000Ubiquitous Computing Jini service discovery Spontane Vernetzung

RMIsec+ SLP+ IIOP

?AnyNetwork

Transport?

E.g. UMTS

6

[email protected]


Tactical Solutions Might Scale Poorlye.g. IBM SNA*, NetBIOS, IPX/SPX, DECnet

*IBM(1980 - 1990) since 1995 disappearing. Not Routable. Layer 2 Polling

Private Protocols OneWayRoad

Tactics Isolation

..Scalable ?

7

Standalone Cleverness and Scalablility


SLP Relay for LUS

Hybrid {PKI - LUS}

Federations A,,,D

RADIUS A,,,DIIOP

Sooner or later, intelligent federations will require Interop = IP

IETF IP-stack

8

Jini - „Scalable Applications“







9

„Intelligent Federations“


Logistics Bitstream

Routing

Jini IQ

* Balloon Input Output System

*

10

Not Yet JVMJini Zone

e.g. Cisco/IOS


Nortel/Cisco/Alcatel/Siemens/FIPA

Intelligentwhirlpool

Tightly Managed Spontaneousness

LooselyFederating Sandboxes

11

Jini „Distribution & Scalability“







12

Net.Appliances „coreBB“

“Spontaneousenessmight arrive at reasonable

price tag ….in the futureJini 1.1 of Today seems

neither intrinsicallySecure nor Scalable”

e.g. Denial of Service Attack

watch for unnecessary unwantedGrain {sandboxes.interconnect}

“Just want to say Hello Friends”

3200 Packets/Second sustained Talk =

opportunity for benchmarkingscalable Link ISP Capacity

Financial Muscle

13

Where is Your Nearest „Hot Spot?“


Ultimate Jini Prospect Service lpd-”proxy”-interface

Scalability at 100Mbps

“lpd/lpr overcentronics”

Lpt1 Converter to Full Duplex100BaseTX

14

No Collision 1000BaseFX? „No Filter“


Merry Christmas, and …Multi Gigabit Trunkingto support distributed spontaneousness

Need “Intelligent ISP”….… “Kassensturz” or “Beobachter” to reduce January Invoice from ISPs / ASP

15

Switched 100BaseTX and „IPv4Multicast“

End-System (Ethernet adapter IBMFE1: ) Description . . . . . . . . : IBM 10/100 EtherJet PCI Adapter Physical Address. . . . . . : 00-06-29-A9-DF-22 DHCP Enabled. . . . . . . . : No (Normally Yes) IP Address. . . . . . . . . : 10.62.21.136 Subnet Mask . . . . . . . . : 255.255.248.0 Default Gateway . . . . . . : 10.62.16.2 Primary WINS Server . . . . : 192.168.27.74

Frame Status Source Address Dest. Address Size ... Summary 0 M [10.62.21.136] [224.0.1.84] 74 ... ICMP: Echo 0 M [10.62.21.136] [224.0.1.85] 74 ... ICMP: Echo

IETF Routing => http://www.rfc-editor.org/cgi-bin/rfcsearch.pl

“IGMP Snooping” IPv4: RFC 1112 + 2236 Proposed Standardand Wide Area Multicasting (e.g. PIM-SM) are emerging Features


16

Jini Client Leasing „DHCP Synergy“

Why not bundle some Jini LUS with DHCP-Server?

RFC 2489 RFC 2939RFC 1541RFC 1534RFC 1533Long History of RFC‘sProven IETF Recom-mendations


17

224.0.1.84 01:00:5E:00:01:54

DLC: Frame 4 arrived at 10:13:30.7342; frame size is 74 (004A hex) bytes. DLC: Destination = Multicast 01005E000154 DLC: Source = Station IBM A9DF22 DLC: Ethertype = 0800 (IP)IP: Version = 4, header length = 20 bytes IP: Type of service = 00 IP: 000. .... = routine IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: .... ..0. = ECT bit - transport protocol will ignore the CE bit IP: .... ...0 = CE bit - no congestion IP: Total length = 60 bytes IP: Identification = 11536 IP: Flags = 0X IP: .0.. .... = may fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 32 seconds/hops IP: Protocol = 1 (ICMP) IP: Header checksum = 6C97 (correct) IP: Source address = [10.62.21.136] IP: Destination address = [224.0.1.84] IP: No optionsICMP: Type = 8 (Echo) ICMP: Code = 0 ICMP: Checksum = EC5B (correct) ICMP: Identifier = 256 ICMP: Sequence number = 24576 ICMP: [32 bytes of data]ICMP: [Normal end of "ICMP header".]


http://www.isi.edu/in-notes/iana/assignments/multicast-addresses

Layer 3

18

224.0.1.85 01:00:5E:00:01:55

DLC: Frame 5 arrived at 10:13:34.7139; frame size is 74 (004A hex) bytes. DLC: Destination = Multicast 01005E000155 DLC: Source = Station IBM A9DF22 DLC: Ethertype = 0800 (IP) IP: Version = 4, header length = 20 bytes IP: Type of service = 00 IP: 000. .... = routine IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: .... ..0. = ECT bit - transport protocol will ignore the CE bit IP: .... ...0 = CE bit - no congestion IP: Total length = 60 bytes IP: Identification = 13840 IP: Flags = 0X IP: .0.. .... = may fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 32 seconds/hops IP: Protocol = 1 (ICMP) IP: Header checksum = 6396 (correct) IP: Source address = [10.62.21.136] IP: Destination address = [224.0.1.85] IP: No options ICMP: Type = 8 (Echo) ICMP: Code = 0 ICMP: Checksum = EB5B (correct) ICMP: Identifier = 256 ICMP: Sequence number = 24832 ICMP: [32 bytes of data] ICMP: ICMP: [Normal end of "ICMP header".]

An IP Multicast Initiative White Paper

http://www.ipmulticast.com/community/whitepapers/howipmcworks.html

19

Jini „Scalable Federations“







20

Scalability Scope „IP Multicast“


Jini.Federation.ATypical mcast.netType Application?

DependenciesBGP4+, M-BGPOSPF+, MOSPFIGMP SnoopingNew Hardware

Jini.Federation.B

21

otherLUS UnicastMulticast

Broadcast

MyLUS

Proxy

alternateService

Jini Federation „Local Perspective“


otherDirectories

22

Jini „Scalability by Design“







23

Scalability@Peripherals

24

Scalability „Inherited from Logistics“

Today SharedMediaBroadcastUnicasterPrototype

Http/TCP/IPv4/NAT “eventually encapsulation”Collisions CRC QueueDrops Reconfigurations

Best Case DedicatedSwitchedMulticastLogistics

IPv6 AutoconfigurationPublic Key Infrastructure

JDK 1.4(+?)

25

Best of Classic ITU-T/Vendors/IETF


…

DOD

IETF

OMG

ITU-T(x703)

JiniRMI

1 Agent Technology Scalability Consideration - January 2001 Seminar 37-331 Information &...

Documents

Transcript of 1 Agent Technology Scalability Consideration - January 2001 Seminar 37-331 Information &...