For these reasons, and as described in greater detail below, it is my opinion that the methods recited in the subject claims were known and obvious to one of ordinary skill in the art prior to the filing of the ’069 patent.

In my opinion, a person of ordinary skill in the art seeking to improve or modify the system taught in Francis would have looked to similar concepts discussed in Gilbert for inspiration.

Additionally, a person of ordinary skill in the art seeking to further improve the system in Francis by increasing the efficiency of the join process would have also been inspired by Gilbert’s use of a network manager to identify and contact an existing member node.

A person of ordinary skill in the art would have been further inspired by the efficiencies achieved by Gilbert’s teachings of having the portal computer sending the connection request to existing nodes on the network.

A person of ordinary skill in the art seeking to advance Francis’s objective that “each member establishes the same number of mesh links” would have looked to Gilbert for inspiration on how to maintain such a topology while adding new nodes.

Yoid Documentation https://web.archive.org/web/20020831070444/http://www.icir.org/yoid/... 2001 27 captures 31 Aug 02 - 30 Nov 16 Yoid Documentation Papers "Yoid: Extending the Internet Multicast Architecture" Paul Francis, Unrefereed report, 38 pages, April 2, 2000 Abstract For browsing: all on one page one page per section For printing: yoidArch.ps (1/2 meg) yoidArch.ps.gz (100k) Specifications "Yoid Tree Management Protocol (YTMP) Specification" Paul Francis, Specification, 60 pages, April 2, 2000 ytmp.ps (600k) ytmp.ps.gz (160k) ytmp.pdf (400k) (made with ps2pdf ... may not display well) "Yoid Distribution Protocol (YDP) Specification" Paul Francis, Specification, 8 pages, April 2, 2000 ydp.ps (150k) ydp.ps.gz (40k) ydp.pdf (120k) (made with ps2pdf ... may not display well) "Yoid Identification Protocol (YIDP) Specification" Paul Francis, Specification, 9 pages, April 2, 2000 yidp.ps (150k) yidp.ps.gz (40k) (40k) yidp.pdf (120k) (made with ps2pdf ... may not display well) Talks "Yoid Architecture Overview" Paul Francis, 17 slides, Oct. 1999 For remote browsing: html For local browsing or printing: html.zip ppt

Yoid Documentation https://web.archive.org/web/20020831070444/http://www.icir.org/yoid/... "Overview of Yoid Dynamic Topology Configuration" 27 captures Paul Francis, 22 slides, Oct. 1999 31 Aug 02 - 30 Nov 16 For remote browsing: html For local browsing or printing: html.zip ppt "Yoid Research Topics" Paul Francis, 10 slides, Oct. 1999 For remote browsing: html For local browsing or printing: html.zip ppt Paul Francis, ACIRI francis@aciri.org April 2, 2000 2001

You are not recognized as a member of this group.

If you are already a member, you may have joined with an email address not linked to this Yahoo!

If so, link that address to your Yahoo!

[ Join ] Group Info Members: 32 Founded: Dec 15, 1999 Language: English Group Settings · Not listed in directory · Open membership · All messages require approval · Only the moderator may post · Public archives · Email attachments are permitted Copyright © 2001 Yahoo!

Privacy Policy - Terms of Service - Guidelines - Help

Yallcast Goal: Unify Both Tracks • “Host”-based distribution tree – Tunneled over IP unicast (and multicast) – Buffering in hosts (or not) • DNS name-based group addressing • Dynamically self-configuring topologies 0003

Yallcast Architecture Overview • Rendezvous Nodes: – Bootstrap members into tree-mesh • Member Nodes: – Dynamically configure into tree-mesh – Send, receive, and forward frames • Group ID: – rendezvousName, treeName, [udpPort] 0005

Yallcast Content Protocols • Application frame-based • Per-source 64-bit byte sequencing – Frame can be forwarded over tree or mesh • Tag-based headers (hop by hop) – Frame source id --> 16-bit tag – HxH source id, HxH dest id, group id --> 64-bit tag 0012

Comparison to IP Multicast  Routing table scalability  Group ID (address) assignment  End-to-end Reliability  Congestion Control  Proximity discovery  Delivery efficiency (for non-reliable) 0013

Trickier Comparisons • Evolutionary Path – Don’t need any infrastructure in advance – Just bundle with app – Add infrastructure as needed • Buffering – Hosts have lots of buffer---async distribution – But introduces new coordination problems 0014