RE: Draft on Callout Protocol Requirements

Title: RE: Draft on Callout Protocol Requirements

Reinaldo,

We should probably discuss this at IETF 52. As you point out, there are many combinations. A fundamental concept

however is, an administrative domain is independent of an AS. I have have a home network that is a member of my ISPs

AS, however, it clearly is under my own administrative control. In content networking, AS's don't have any hard relationships

with Administrative Domains or Authoritative Domains.

Gary

-----Original Message-----
From: Reinaldo Penno [mailto:reinaldo_penno@xxxxxxxxxxxxxxxxxx]
Sent: Wednesday, November 28, 2001 10:15 AM
To: 'Tomlinson, Gary'; 'Phil Rzewski'
Cc: 'ietf-openproxy@xxxxxxx'
Subject: RE: Draft on Callout Protocol Requirements

Gary,

And the virus scanning example...I will just say that there are infinite combinations based on these examples. I will just say that my IPs are owned by ATT and I do not have an AS. Then we can enter on a discussion on managed services (CPE or network based), and when a network is a CN or not, and ultimately if OPES needs a CN (overlay) or not. etc.

We better take this offline.

regards,

Reinaldo

-----Original Message-----
From: Tomlinson, Gary [mailto:gary.tomlinson@xxxxxxxxxxxxx]
Sent: Wednesday, November 28, 2001 10:06 AM
To: Penno, Reinaldo [SC9:T327:EXCH]; Tomlinson, Gary; 'Phil Rzewski'
Cc: 'ietf-openproxy@xxxxxxx'
Subject: RE: Draft on Callout Protocol Requirements

No, you have your own Content Network that exists entirely with your own administrative domain. AT&T is simply a

packet network you are overlaying for transit.

Gary

-----Original Message-----
From: Reinaldo Penno [mailto:reinaldo_penno@xxxxxxxxxxxxxxxxxx]
Sent: Wednesday, November 28, 2001 9:58 AM
To: 'Tomlinson, Gary'; 'Phil Rzewski'
Cc: 'ietf-openproxy@xxxxxxx'
Subject: RE: Draft on Callout Protocol Requirements

So do we agree that the single reverse proxy on my home (example from the previous email) makes AT&T a Content Network?

> -----Original Message-----
> From: Tomlinson, Gary [mailto:gary.tomlinson@xxxxxxxxxxxxx]
> Sent: Wednesday, November 28, 2001 9:55 AM
> To: 'Phil Rzewski'; Penno, Reinaldo [SC9:T327:EXCH]
> Cc: 'ietf-openproxy@xxxxxxx'
> Subject: RE: Draft on Callout Protocol Requirements
>
>
> I concur completely with Phil's position here. OPES was originally
> predicated on the
> existence of a Content Network. My understanding is, it
> still is. The
> Content Network
> can be as simple as a single caching proxy or as complex as CDN.
>
> Gary
>
> -----Original Message-----
> From: Phil Rzewski [mailto:philr@xxxxxxxxxxx]
> Sent: Tuesday, November 27, 2001 4:27 PM
> To: Reinaldo Penno
> Cc: 'ietf-openproxy@xxxxxxx'
> Subject: RE: Draft on Callout Protocol Requirements
>
>
>
> At 03:22 PM 11/27/2001 -0800, Reinaldo Penno wrote:
>
>
> >
> > > -----Original Message-----
> > > From: Phil Rzewski
[<mailto:philr@xxxxxxxxxxx>mailto:philr@xxxxxxxxxxx]
> > Sent: Monday, November 26, 2001 11:34 AM
> > To: Penno, Reinaldo [SC9:T327:EXCH]
> > Cc: ietf-openproxy@xxxxxxx
> > Subject: RE: Draft on Callout Protocol Requirements
> >
> >
> <snip>
>
> >
> > In brief, we know that in the routed world, once you put two
> > host machines on
> > the same ethernet wire, you technically have a "network". As
> > "networks" go,
> > it's on a whole different scale than one operated by AT&T or
> > the IT department
> > at your local enterprise, but this is why we have terms like
> > "public backbone
> > network", "LAN", "VPN", etc. Similarly, we would argue that
> > once you add ANY
> > proxy ("forward" or "reverse") you have created a type of
> > Content Network.
>
> okay, I can agree with that since it actually adds to my point that to
have
> OPES you only need
> IP connectivity, nothing else. You do not need an CN (and not by a long
shot
> a CDN) overlay network in place BEFORE you install OPES devices.

I'm not sure how you get that from what I said, though maybe I'm failing to
understand something. Back when I was first tracking OPES, the services were
assumed to be provided by either proxylets or callouts to external boxes.
The
device that was making those callouts or calling those proxylets was
typically
described as being a surrogate or proxy of some kind. If that's still true
(is
it not?), then by my definition, you WOULD have a Content Network before you
layer OPES proxylets/callouts on top of it.

>
> You end up having a CN (not an CDN) overlay network AFTER you install an
OPES
> device.

This I'd agree with, but I'm agreeing with the literal statement. :) That
is,
I'd say that any network that contains OPES services is a Content Network (I
think it had to be before you added the OPES services, even). It may be a
CDN,
since a CDN is just a specific type of Content Network. That's determined by
whether it contains components like distribution, request routing, etc.

--
Phil Rzewski - Senior Architect - Inktomi Corporation
650-653-2487 (office) - 650-303-3790 (cell) - 650-653-1848 (fax)