Ken Kempster wrote:
>
> On Tue, 5 Nov 1996, Bruno Raoult wrote:
>
> > Hi,
> >
> > On 1 Nov 1996, Brian B Mitchell wrote:
> > > Hi Everyone,
> > > (Bruno, we have had this discussion)
> > >
> > > Products
> > > 1. Reuter 3000 Fixed Income Requires UDP Port 256/257
and port 31010 over tcp
> > > 2. Reuters Newyear 2000 Requires UDP Port 7091
> > > 3. Reuters Business Breifing Uses only TCP
port 9451 over tcp
> > > 4. Reuter Web (see Reuter Mail)
> > > 5. Reuter Mail Requires UDP 1024-65535
> > > 6. Reuter 3000 Equities Uses only TCP
port 5100
> > > 7. Reuter Broker Research Uses Netbios Encapsulated with TCP
> > > General
> > > 8. Any product requiring Reuter Login (Fixed Income, Web, Mail,) must use UDP
> > > Port 256/257
used for authentication
> > > 9. All products require UDP/53(DNS) & UDP/520 (RIP)
>
> Where are you getting this UDP info from? I have been told
> that the only UDP traffic is from the NewsYear 2000 service
> and the initial logins.
>
> This info. comes from the head of Reuters Marketing.
>
> > >
> >
> > Ok. Looking at this list, you are surely not intested in TCP traffic.
> > I think it is a problem, as the address translation system cannot permit
> > to know which is the real Reuters host sending packets.
> >
> > > In the Reuter documents there is further reference to Reuters Treasury 3000,
> > > Reuters Securities 3000 and Reuters Messaging Products. Does anyone have
> > > knowledge of these ?.
> > I think that:
> > Reuters security 3000 = Security 2000 (triarch) + Reuters Mail +
> > Reuters 3000 Equities
> > Reuters Treasury 3000 = Treasury 2000 (?) + Reuters Mail +
> > Reuters 3000 Fixed Income
> >
> > I do not know about messaging products.
> >
> > >I am trying to establish how much concern there currently is, within the Market
> > >Data User community surrounding this suite of products.
> > >
> > >Reuters, needless to say, have a very bullish approach, in that they say that
> > >market demand will overide the security concerns. For those of us charged with
> > >securing our networks, I certainly feel that this should not be the approach to
> > >take however, pressure from the business and the business users will surely
> > >grow.
> > >
> > >In order to address this issue, and to push back on Reuters, I would appreciate
> > >any comments or input you may have surrounding these issues. Furthermore, as
> > >the increased need for TCP/IP connectivity grows, this is only the tip of the
> > >iceberg. Guaranteed, Telerate, Knight Ridder, Bloomberg will follow suite very
> > >soon.
> > >
> >
> > Bye.
> >
> >
> > \|||/
> > (. .)
> > +-------------ooO-(_)-Ooo------------------------------------------------+
> > | Bruno RAOULT - Chess, tonight? |
> > | |
> > | Tel. (33-1) 42.13.45.19 Fax: (33-1) 42.13.69.66 |
> > | Kobby. (33-1) 51.01.20.71 e-mail: br @
ota .
societe-generale .
fr |
> > +------------------------------------------------------------------------+
> > || ||
> > ooO Ooo
> >
> >
> >
>
> ----------------------------
> Ken Kempster
> Republic National Bank
> kempster @
monarch .
rnb .
com
> ----------------------------
I thought that this discussion was interesting to many people on the list, and do
forward it.
If we go further in the Reuters services, you will see that they use Address translation
for their network. That is to say that the session server is connected to your network
with an address belonging to your network. The real server that yoou will connect to are
on a network type 172.16.x.y.The session server is performing a routing function.
For load balancing purposes they are unable to tell you what is the ip address used by
the servers.Then I had to allow the complet class 172.16.0.0 be routed through our
network for the corresponding services. That is to say that I could not apply any
restriction on the source address. After a certain time of use we should be able to
restrict those addresses to the one we see in use.
--
Christian ALT E-mail: calt @
tla .
ch
Telecom and Logistics Associates phone & fax : +41 22 328 14 88
10, Rue des Savoises, CH-1205 Geneva http://www.tla.ch
|
|
