From mailnull@www1.ietf.org  Fri Nov  1 04:38:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02107
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 04:38:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA19euZ12439
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 04:40:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA19euv12436
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 04:40:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02100
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 04:38:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA19dev12369;
	Fri, 1 Nov 2002 04:39:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA19chv12310
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 04:38:43 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA02094
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 04:36:06 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.08916-0@bells.cs.ucl.ac.uk>; Fri, 1 Nov 2002 09:38:25 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Bill Woodcock <woody@pch.net>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Re: draft-ietf-ieprep-requirements-01
In-reply-to: Your message of "Thu, 31 Oct 2002 09:24:17 PST." <Pine.GSO.4.44.0210310912140.4172-100000@paixhost.pch.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 01 Nov 2002 09:38:24 +0000
Message-ID: <584.1036143504@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


>    > It would be more constructive if you could provide technical points
>    > of discussion.
>
> Peter and I tried that at the last meeting, and nobody wanted to talk
> about technology.  Instead, we get this document, which consists largely
> of statements of the form "The PSTN makes toast!" and "We _like_ toast!"
> and "The Internet SHOULD make toast!" and "Salespeople SHOULD tell us that
> the Internet makes toast!"

again.  I shall simply ask that you provide technical points of
discussion.  if you wish to go in another direction, please send me 
private email.  or, you can speak to me in private in the hallsways 
as i did for nearly an hour with Peter at Yokohama.

>    > at the Yokohama meeting, there was basically no contentious arguements
>    > expressed about the version -00 draft
>
> Very generous of you to characterize Peter and myself as uncontentious.
> Or perhaps you're just forgetting that you ignored everything we said.

i generally try to be quite precise when i send email.  When Hal Folts
spoke on the draft-ietf-ieprep-requirements-00 draft, there were no 
contentious arguements - read the minutes, or ask others who attended.  

there were indeed quite a number of contentious comments when others had
spoken, but my original comment above did not refer to those drafts or
presentations.

> I would really welcome _any little tidbit of technical anything_ that
> could be debated.  As it is, the document is just a bunch of
> long-winded platitudes about the PSTN and about sales practices.  Not much
> for an engineer to debate.

noted.  i guess we'll move on.

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 05:05:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02574
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 05:05:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1A79w14053
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 05:07:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1A78v14050
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 05:07:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02569
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 05:04:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1A66v13731;
	Fri, 1 Nov 2002 05:06:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1A5vv13708
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 05:05:57 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA02546
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 05:03:31 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.10842-0@bells.cs.ucl.ac.uk>; Fri, 1 Nov 2002 10:05:50 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Bill Woodcock <woody@pch.net>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Re: draft-ietf-ieprep-requirements-01
In-reply-to: Your message of "Thu, 31 Oct 2002 09:56:07 PST." <Pine.GSO.4.44.0210310936180.4562-100000@paixhost.pch.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 01 Nov 2002 10:05:49 +0000
Message-ID: <624.1036145149@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> This was what I was principally objecting to at the Yokohama meeting:
> there seems to be an underlying assumption that the PSTN will connect to
> arbitrary other voice networks.  My own network appears to be the
> exception in that PSTN operators do in fact seem to be eager to connect to
> it and bear the costs of doing so, but in the general case, they don't
> seem to be interested in doing so.

understood.  you have stated your own case, and portions have connected 
in the UK and other countries.  but acknowledging that portions have, or 
simply that the condition can occur is not a expectation that this will
happen across the board or must occur.  we can add verbage to clarify this
in the draft.

>    > > >> We assume the presence of Service Level Agreements
>    > > > Which are a marketing, sales, and collections fiction.
>    > > He's saying the assumption is not well founded.
>    > we have used the term "business agreement" instead of SLAs in our
>    > other documents.
>
> Right.  So isn't this CLEARLY OUTSIDE THE REALM OF THE IETF?  Since when
> does the IETF standardize business agreements?

stating its existance and assuming its usage instead of unfunded
mandates (which are a BAD thing) is not standardizing business 
agreements.

>    >>>> Emergency traffic should be able to transit multiple service
>    >>>> providers.
>    > The original passage probably should have stated "labeled emergency
>    > traffic".  The traffic  itself could be diff-serv marked IP packets.
>    > Or they could be labeled application layer packets.  In either case,
>    > the user would have the expectation that the labeled traffic
>    > transits other providers as opposed to be dropped because it is
>    > unrecognized.
>
> Then the user's expectation would be unfulfilled.
> 
> You're completely missing the point.  _No_ traffic is going to transit
> multiple service providers unless the service providers are
> interconnected.  Interconnection is a physical process, not a sales
> process.

we are in total agreement with what you just stated, but that is not
the "user expectation" that was intended or inferred.  I will rewrite
the original passage.

>   > the intent of the original passage
>   > was aimed at the QoS experienced by the end-user and not necessarily
>   > that offered by the network.  for example, using lower quality/bandwidth
>   > codecs, or adding FEC -- ie, something other than standard end-to-end
>   > service.
>
> Then it doesn't belong in the document, does it?  Users are welcome to do
> whatever users do.  That doesn't constitute an expectation of service
> providers.

one thing to keep in mind.  the document is not aimed exclusively at the 
IP network layer.  if it was, then agreed, the above would not belong.

-ken



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 06:44:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04009
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 06:44:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1BkLb18911
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 06:46:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1BkLv18908
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 06:46:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04004
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 06:43:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1BjCv18881;
	Fri, 1 Nov 2002 06:45:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1BiLv18829
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 06:44:21 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA03964
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 06:41:54 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.20245-0@bells.cs.ucl.ac.uk>; Fri, 1 Nov 2002 11:44:07 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Bill Woodcock <woody@pch.net>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-reply-to: Your message of "Thu, 31 Oct 2002 13:57:59 PST." <Pine.GSO.4.44.0210311347480.7917-100000@paixhost.pch.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 01 Nov 2002 11:44:05 +0000
Message-ID: <820.1036151045@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> No disagreement with any of that.  Have you, however, been able to find
> any IP telephony (by your definition, SIP or equivalent) using site
> pairs which are experiencing interconnection performance worse than
> that?  The only connection we've been able to find which failed to
> exceed PSTN quality was actually a satellite modem connection, so it
> was, in effect, tunnelled through the PSTN.

yes, through parts of the transatlantic link.  some connections between
the US and Chile (locations other than Santiago), and between the US and
New Zealand.  the caveat is that this loss of PSTN quality is over the 
busy period of the day (as opposed to 24/7), and at times asymetric. 
New Zealand & transatlantic cases carried other traffic, but still stayed 
within the classic ~90%-to-10% ratio of TCP/UDP.  

> And that was the link adjacent to the end-user, and was carrying no
> other traffic. Thus no amount of QoS, dif-serv, SLA, et cetera would
> have been of any help.
>
> My operational experience tells me that that's a generalizable truth.
> That unlike in the PSTN, in the Internet, if there's a path, it'll be
> sufficient, and if there isn't a path, no amount of QoS will fix the
> basic lack of ability to forward packets.

I would qualify your statement as "usually" the case. its the peak times 
(and transient problems) that are of concern.

As a side note, i try to listen to a few jazz stations in the states,
and its nasty in my afternoon, with streaming audio dropping on occasion
because of loss.  American football VoIP radio stations on Sundays are
also frustrating for me at times.

>    > This problem is further compounded when toll-quality service is
>    > expected because it assumes a default service model that is
>    > better than best effort.  This in turn can increase the
>    > probability that a form of call-blocking can occur with VoIP or
>    > IP telephony traffic.
>
> What's meant by "toll-quality service?"  I'm perhaps incorrectly
> reading that as "voice quality similar to that experienced by users of
> the PSTN."  If that interpretation is as intended, 

your interpretation is correct.  its a term used in the telco world, and 
I've heard it used in IP telephony groups of the IETF.  However, I shall
provide an explanation in the draft.

> it implies that the
> authors believe that IP telephony on the commodity Internet doesn't
> universally exceed that threshold.

the word universally is quite a strong word.  in terms of 24/7 and the
five 9's that the PSTN aims at, no, i don't believe the non-US portion
of the Internet "universally" exceeds the threshold for IP telephony.

>    > 3.1.  Alternate Path Routing
>    > This objective involves the ability to discover and use a
>    > different path to route IP telephony traffic around congestion
>    > points and thus avoid them. Ideally, the discovery process would
>    > be accomplished in an expedient manner (possibly even a priori to
>    > the need of its existence).  At this level, we make no
>    > requirements as to how the alternate path is accomplished, or
>    > even at which layer it is achieved -- e.g., the network versus
>    > the application layer.  But this kind of capability, at least in
>    > a minimal form, would help contribute to increasing the
>    > probability of call completion of IEPS traffic.
>
> I cannot begin to express the depth of my disagreement with this
> assertion.  _Nothing short of a backhoe_ will have a more adverse
> effect upon the likelihood of call completion than routing it on a path
> other than that of the production traffic.

then, I would assume you have expressed your total objection to TRIP.

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 06:55:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04169
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 06:55:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Buu619170
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 06:56:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Buuv19167
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 06:56:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04162
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 06:54:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Bu2v19136;
	Fri, 1 Nov 2002 06:56:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Bt7v19101
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 06:55:07 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA04142
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 06:52:41 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.21750-0@bells.cs.ucl.ac.uk>; Fri, 1 Nov 2002 11:54:38 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: RJ Atkinson <rja@extremenetworks.com>
cc: Bill Woodcock <woody@pch.net>, ieprep@ietf.org
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-reply-to: Your message of "Thu, 31 Oct 2002 19:31:46 EST." <4D74530F-ED31-11D6-8A6A-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 01 Nov 2002 11:54:37 +0000
Message-ID: <839.1036151677@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> >> 3.1.  Alternate Path Routing
>
> And actually, this "requirement" is one driven by a PSTN-like 
> architecture
> where routing is NOT dynamic and instead is static, configured at call
> setup time.  The Internet does not have that problem so doesn't need the
> above "requirement".

it will probably be easier to take the word "requirement" out of the
section title.  the document is just a framework, and not a requiremnts
document.

> With the IP world's dynamic routing, the above requirement is not 
> appropriate or helpful to achieving better quality connectivity during 
> a calamity. The 9/11 calamity, several earthquakes, and sundry other 
> disasters around the world have shown that dynamic IP routing is nearly 
> impossible to beat.
> To give another example, the Iraqis reportedly used dynamic IP routing
> to keep some of their command & control networks up and working during 
> the Gulf War

right,  but here is a counter argument.  IP routing may still route flows
through a path that has loss that is tolerable to elastic traffic, but
considered intolerable for VoIP traffic.  hence, alternate path 
application layer routing (ala TRIP) may be of help to circumvent this 
duality.

within the context of the framework document, its simply a value added
functionality to be considered.

-ken




_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 07:36:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04985
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 07:36:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Cbxh21719
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 07:37:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Cbxv21716
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 07:37:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04976
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 07:35:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Cb3v21203;
	Fri, 1 Nov 2002 07:37:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Cafv21086
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 07:36:41 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04960
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 07:34:14 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1CaAm6028200;
	Fri, 1 Nov 2002 07:36:10 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1Ca3H9020048
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 1 Nov 2002 07:36:05 -0500 (EST)
Message-ID: <3DC275A8.7060107@cs.columbia.edu>
Date: Fri, 01 Nov 2002 07:38:00 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
CC: Bill Woodcock <woody@pch.net>, ieprep@ietf.org
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
References: <820.1036151045@cs.ucl.ac.uk>
In-Reply-To: <820.1036151045@cs.ucl.ac.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

There have been approximately half a dozen published papers that have 
attempted to characterize VoIP quality over various parts of the 
Internet. Not surprisingly, there are generally three observations:
- some pairwise sessions almost always work well, with < 2% packet loss;
- some have intermittent "hick ups" with bursts of very high or 100% 
packet loss (which are sufficiently long that no FEC or other 
compensation mechanism can deal with them);
- some are persistently bad to unusable, typically but not exclusively 
for sessions between North America and Latin America and parts of Asia, 
as well as between non-NA regions.

Search in netbib (http://www.cs.columbia.edu/~hgs/netbib) for 
references, if you'd like more details. This is probably only marginally 
related to the WG, but I can dig up the citations. It's obviously pretty 
hard to deduce from these limited experiments involving maybe at most a 
dozen sites what the precise likelihood of success is. All reasonable 
estimates would put it significantly below 99.9%.

Ken Carlberg wrote:

> yes, through parts of the transatlantic link.  some connections between
> the US and Chile (locations other than Santiago), and between the US and
> New Zealand.  the caveat is that this loss of PSTN quality is over the
> busy period of the day (as opposed to 24/7), and at times asymetric.
> New Zealand & transatlantic cases carried other traffic, but still stayed
> within the classic ~90%-to-10% ratio of TCP/UDP.
>
>
> >And that was the link adjacent to the end-user, and was carrying no
> >other traffic. Thus no amount of QoS, dif-serv, SLA, et cetera would
> >have been of any help.
> >
> >My operational experience tells me that that's a generalizable truth.
> >That unlike in the PSTN, in the Internet, if there's a path, it'll be
> >sufficient, and if there isn't a path, no amount of QoS will fix the
> >basic lack of ability to forward packets.
>
>
> I would qualify your statement as "usually" the case. its the peak times
> (and transient problems) that are of concern.
>
> As a side note, i try to listen to a few jazz stations in the states,
> and its nasty in my afternoon, with streaming audio dropping on occasion
> because of loss.  American football VoIP radio stations on Sundays are
> also frustrating for me at times.
>
>
> >   > This problem is further compounded when toll-quality service is
> >   > expected because it assumes a default service model that is
> >   > better than best effort.  This in turn can increase the
> >   > probability that a form of call-blocking can occur with VoIP or
> >   > IP telephony traffic.
> >
> >What's meant by "toll-quality service?"  I'm perhaps incorrectly
> >reading that as "voice quality similar to that experienced by users of
> >the PSTN."  If that interpretation is as intended,
>
>
> your interpretation is correct.  its a term used in the telco world, and
> I've heard it used in IP telephony groups of the IETF.  However, I shall
> provide an explanation in the draft.
>
>
> >it implies that the
> >authors believe that IP telephony on the commodity Internet doesn't
> >universally exceed that threshold.
>
>
> the word universally is quite a strong word.  in terms of 24/7 and the
> five 9's that the PSTN aims at, no, i don't believe the non-US portion
> of the Internet "universally" exceeds the threshold for IP telephony.
>
>
> >   > 3.1.  Alternate Path Routing
> >   > This objective involves the ability to discover and use a
> >   > different path to route IP telephony traffic around congestion
> >   > points and thus avoid them. Ideally, the discovery process would
> >   > be accomplished in an expedient manner (possibly even a priori to
> >   > the need of its existence).  At this level, we make no
> >   > requirements as to how the alternate path is accomplished, or
> >   > even at which layer it is achieved -- e.g., the network versus
> >   > the application layer.  But this kind of capability, at least in
> >   > a minimal form, would help contribute to increasing the
> >   > probability of call completion of IEPS traffic.
> >
> >I cannot begin to express the depth of my disagreement with this
> >assertion.  _Nothing short of a backhoe_ will have a more adverse
> >effect upon the likelihood of call completion than routing it on a path
> >other than that of the production traffic.
>
>
> then, I would assume you have expressed your total objection to TRIP.
>
> -ken
>
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 10:20:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15967
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 10:20:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1FMpb23620
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 10:22:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1FMpv23617
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 10:22:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15947
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 10:20:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1FLDv23563;
	Fri, 1 Nov 2002 10:21:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1FKjv23446
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 10:20:45 -0500
Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15772
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 10:18:18 -0500 (EST)
Received: from KC-MAIL1.kc.umkc.edu ([134.193.143.161] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 1 Nov 2002 09:20:41 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Subject: Re: [Ieprep] Re: draft-ietf-ieprep-requirements-01
Date: Fri, 1 Nov 2002 09:20:41 -0600
Message-ID: <EC61AA563B48B6459EEE976942BEA1190141C39B@KC-MAIL1.kc.umkc.edu>
Thread-Topic: Re: [Ieprep] Re: draft-ietf-ieprep-requirements-01
Thread-Index: AcKBHUJYXyObZqt7Tx20L3FlVVTx5wADwYlQACN5clA=
From: "Beard, Cory" <beardc@umkc.edu>
To: <ieprep@ietf.org>
X-OriginalArrivalTime: 01 Nov 2002 15:20:41.0752 (UTC) FILETIME=[3D9EE980:01C281BA]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA1FKjv23447
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> Until such time as you get other organisations and other
> countries to represent themselves here and present their 
> perspectives, preferably in their own documents about what 
> services they use today and plan to use in the future, the 
> rest of us (who aren't monetarily or 
> contractually
> beholden to NCS) can only realistically know that the document 
> represents
> your views based on your experience at NCS.

I agree with you that other organizations should be represented.

That said, however, how might one expect that the "requirements" (wish list) would change?  Do we believe other organizations would want much less?  Much more?  Something different?  If so, can anyone give an example?

Also, is there an expectation that everything that is in this proposed Informational RFC has to be able to be provided in the short term?  I believe Hal's goal is that this be a document that would be applicable over a longer term and that some of the capabilities be provided soon and others more in the future.

Now, if we agree that some of the proposed capabilities would never be expected to be feasible, those should certainly be removed from the document.

Cory Beard
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 10:54:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18155
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 10:54:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1FuNv03692
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 10:56:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1FuNv03689
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 10:56:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18105
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 10:53:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1FtBv03628;
	Fri, 1 Nov 2002 10:55:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Fsiv03544
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 10:54:44 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18067
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 10:52:16 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Fri, 1 Nov 2002 07:51:53 -0800
Received: from ro178-88.ro.nps.navy.mil (ro178-88.ro.nps.navy.mil [131.120.178.88])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gA1Fr7b9016094;
	Fri, 1 Nov 2002 07:53:07 -0800 (PST)
Subject: Re: [Ieprep] draft-ietf-ieprep-requirements-01.txt
From: Rex Buddenberg <budden@nps.navy.mil>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>
In-Reply-To: <736E6C52-ED0F-11D6-BE27-00039357A82A@extremenetworks.com>
References: <736E6C52-ED0F-11D6-BE27-00039357A82A@extremenetworks.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1036120386.1084.96.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 01 Nov 2002 08:51:16 -0800
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Thu, 2002-10-31 at 12:29, RJ Atkinson wrote:

> Section 1,
> meta:		It is unclear whether the author intends only VoIP applications
> 			when the phrase "Emergency Telecommunications Service" is used
> 			xor means other things in addition (e.g. email, web).  This needs
> 			to be made more clear at a minimum.  If only the voice applications
> 			are intended, that scoping needs to be a whole lot more clear than
> 			it is at present.
> 

and

> Section 1.2,
> page ?:		I think it is possible that the PSTN is migrating to VoIP, as  
> this
> 			claims, but I do not think that it is certain to be the case.  The
> 			PSTN architecture is very much tailored for voice services and the
> 			Internet architecture is quite deliberately general (not tailored
> 			for voice services).  So it isn't really universally accepted that
> 			"convergence" is happening or guaranteed to happen.

Went through a rather lengthy discussion on this topic with a couple of
thesis students who just graduated.  Let me replay some of it; at least
partly germane.

As an economic analysis, the students did some life cycle costing
against three choices. If you need to replace your PBX then:
	- buy a new PBX?
	- buy a VOIP capability instead?  (Assumption is that you have a data
network)
	- some hybrid between?
The analysis clearly said buy whole hog into VOIP; don't buy a new PBX
(the month following, our campus bought a new PBX...)

What was not covered in this analysis was the economies of 'collapsed
bandwidth'.  Right now, the typical naval ship has several radios, each
with a 3kHz voice equivalent bandwidth (ignoring digitization and ssb
stuff).  And the commstas have the ability to splice radio calls into
the PSTN (phone patch).  Yeah, all these radios are mutually interfering
emitters.  But a large (and proportionally growing) portion of the radio
comms is data.  If you push all of that into a fewer number of larger
sized pipes (keeping overall bandwidth constant) the number of emitters
goes down (less self-interference).  There are a whole bunch of
economies here to avoiding having to maintain voice channels, video
channels and data channels and just having IP channels.  All of this
argument reinforces the economy conclusion the students did find.

Why is this important to ieprep?  Many (most?) emergency services
providers have mobile platforms and need the radios to reach to them. 
Further, the radio links are often impressed as altroutes to cover
damaged fiber/copper links between fixed sites.  It makes a whole lot
more sense in the longer term for all of these emergency services
outfits to each maintain a single flavor of radio-WAN plumbing.  



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 12:43:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25032
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 12:43:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Hjup10533
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 12:45:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Hjuv10530
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 12:45:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25025
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 12:43:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1HjAv10511;
	Fri, 1 Nov 2002 12:45:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Hitv10469
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 12:44:55 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25001
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 12:42:26 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA1Hcwd28578;
	Fri, 1 Nov 2002 09:38:58 -0800 (PST)
Date: Fri, 1 Nov 2002 09:38:58 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <820.1036151045@cs.ucl.ac.uk>
Message-ID: <Pine.GSO.4.44.0211010933500.28183-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 1 Nov 2002, Ken Carlberg wrote:
    > > it implies that the
    > > authors believe that IP telephony on the commodity Internet doesn't
    > > universally exceed that threshold.
    >
    > the word universally is quite a strong word.  in terms of 24/7 and the
    > five 9's that the PSTN aims at, no, i don't believe the non-US portion
    > of the Internet "universally" exceeds the threshold for IP telephony.

I'll try to be very clear: I do not mean that every IP telephony call
which I've experienced has exceeded the quality of the best PSTN call.

I mean that the distribution curve of IP telephony call quality, if you
will, is at or above that of that of PSTN calls.  Thus the best IP
telephony calls exceed the quality of the best PSTN calls, the 90th
percentile IP telephony calls exceed the 90th percentile PSTN calls, the
10th percentile IP telephony calls exceed the quality of 10th percentile
PSTN calls, et cetera.  Obviously the worst calls fail to complete, in
both cases.

As I said, this is my personal qualitative experience from daily use
consisting of many calls on a global SIP network.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 12:45:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25128
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 12:45:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1HlkW11034
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 12:47:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Hlkv11031
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 12:47:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25116
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 12:45:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Hl4v10934;
	Fri, 1 Nov 2002 12:47:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Hkxv10830
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 12:46:59 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25079
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 12:44:30 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA1Hf2d28610;
	Fri, 1 Nov 2002 09:41:02 -0800 (PST)
Date: Fri, 1 Nov 2002 09:41:02 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
cc: RJ Atkinson <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <839.1036151677@cs.ucl.ac.uk>
Message-ID: <Pine.GSO.4.44.0211010939530.28183-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > right,  but here is a counter argument.  IP routing may still route flows
    > through a path that has loss that is tolerable to elastic traffic, but
    > considered intolerable for VoIP traffic.  hence, alternate path
    > application layer routing (ala TRIP) may be of help to circumvent this
    > duality.
    >
    > within the context of the framework document, its simply a value added
    > functionality to be considered.

I think Ran's point, and mine, is that this is not a value add, it's a
value subtraction.  In the real world, this simply won't work.  It's a
Rube Goldberg contraption which no one has any incentive to try to make
work.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:07:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26546
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:07:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1I9nh22152
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:09:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1I9nv22149
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:09:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26523
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:07:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1I94v22070;
	Fri, 1 Nov 2002 13:09:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1I8av21509
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:08:36 -0500
Received: from imo-m04.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26456
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:06:07 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m04.mx.aol.com (mail_out_v34.13.) id b.14.155fed8 (25914);
	Fri, 1 Nov 2002 13:08:17 -0500 (EST)
Message-ID: <14.155fed8.2af41d10@aol.com>
Date: Fri, 1 Nov 2002 13:08:16 EST
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
To: woody@pch.net, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_14.155fed8.2af41d10_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_14.155fed8.2af41d10_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 10/31/2002 6:52:04 PM Eastern Standard Time, woody@pch.net 
writes:


>    > 3.1.  Alternate Path Routing
>     > This objective involves the ability to discover and use a
>     > different path to route IP telephony traffic around congestion
>     > points and thus avoid them. Ideally, the discovery process would
>     > be accomplished in an expedient manner (possibly even a priori to
>     > the need of its existence).  At this level, we make no
>     > requirements as to how the alternate path is accomplished, or
>     > even at which layer it is achieved -- e.g., the network versus
>     > the application layer.  But this kind of capability, at least in
>     > a minimal form, would help contribute to increasing the
>     > probability of call completion of IEPS traffic.
> 
> I cannot begin to express the depth of my disagreement with this
> assertion.  _Nothing short of a backhoe_ will have a more adverse
> effect upon the likelihood of call completion than routing it on a path
> other than that of the production traffic.
> 
> The degree of increased complexity _which has no other purpose_ and
> _would receive no other use_. Emergency systems which share no fate
> with production systems, don't get regular use, and aren't associated
> with any revenue are, without question, doomed to failure.
> 


[MAP] I can't imagine why you are questioning this requirement. It is a 
fundamental requirement of any network to be able to route around congestion 
(and failures).

But, I suspect (presume?) that the Internet already successfully does this, 
so the requirement may not require anything new. But then, once we agree on 
the requirement, we can then decide if anything new is needed.

Mike Pierce
Artel


--part1_14.155fed8.2af41d10_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 10/31/2002 6:52:04 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&gt; 3.1. &nbsp;Alternate Path Routing
<BR> &nbsp;&nbsp;&nbsp;&gt; This objective involves the ability to discover and use a
<BR> &nbsp;&nbsp;&nbsp;&gt; different path to route IP telephony traffic around congestion
<BR> &nbsp;&nbsp;&nbsp;&gt; points and thus avoid them. Ideally, the discovery process would
<BR> &nbsp;&nbsp;&nbsp;&gt; be accomplished in an expedient manner (possibly even a priori to
<BR> &nbsp;&nbsp;&nbsp;&gt; the need of its existence). &nbsp;At this level, we make no
<BR> &nbsp;&nbsp;&nbsp;&gt; requirements as to how the alternate path is accomplished, or
<BR> &nbsp;&nbsp;&nbsp;&gt; even at which layer it is achieved -- e.g., the network versus
<BR> &nbsp;&nbsp;&nbsp;&gt; the application layer. &nbsp;But this kind of capability, at least in
<BR> &nbsp;&nbsp;&nbsp;&gt; a minimal form, would help contribute to increasing the
<BR> &nbsp;&nbsp;&nbsp;&gt; probability of call completion of IEPS traffic.
<BR>
<BR>I cannot begin to express the depth of my disagreement with this
<BR>assertion. &nbsp;_Nothing short of a backhoe_ will have a more adverse
<BR>effect upon the likelihood of call completion than routing it on a path
<BR>other than that of the production traffic.
<BR>
<BR>The degree of increased complexity _which has no other purpose_ and
<BR>_would receive no other use_. Emergency systems which share no fate
<BR>with production systems, don't get regular use, and aren't associated
<BR>with any revenue are, without question, doomed to failure.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] I can't imagine why you are questioning this requirement. It is a fundamental requirement of any network to be able to route around congestion (and failures).
<BR>
<BR>But, I suspect (presume?) that the Internet already successfully does this, so the requirement may not require anything new. But then, once we agree on the requirement, we can then decide if anything new is needed.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_14.155fed8.2af41d10_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:07:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26555
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:07:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1I9nr22171
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:09:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1I9nv22168
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:09:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26526
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:07:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1I92v22048;
	Fri, 1 Nov 2002 13:09:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1I8Pv21366
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:08:25 -0500
Received: from imo-d04.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26442
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:05:55 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d04.mx.aol.com (mail_out_v34.13.) id b.6c.2514456c (25914);
	Fri, 1 Nov 2002 13:07:55 -0500 (EST)
Message-ID: <6c.2514456c.2af41cfb@aol.com>
Date: Fri, 1 Nov 2002 13:07:55 EST
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
To: woody@pch.net, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_6c.2514456c.2af41cfb_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_6c.2514456c.2af41cfb_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 10/31/2002 6:15:09 PM Eastern Standard Time, woody@pch.net 
writes:


>    > Primary Objectives in support of authorized emergency calls:
>     > 2) Interaction with PSTN
>     > The second objective involves the interaction of IP telephony
>     > signaling with existing PSTN support for emergency related voice
>     > communications.  As mentioned above in Section 1.2, standard
>     > T1.631 [26] specifies emergency code points for SS7.
>     > Specifically, the National Security and Emergency Preparedness
>     > (NS/EP) Calling Party Category code point is defined for ISUP IAM
>     > messages used by SS7 [26].  Hence, our objective in the
>     > interaction between the PSTN and IP telephony with respect to
>     > IEPS (and national indicators) is a direct mapping between
>     > related code points.
> 
> This seems problematic to me, in exactly the same way as if a user came
> before the IETF with a draft which stated that that their objective was
> to have carriers peer. That's nice, but that's a business decision to
> be made by the carriers, and it doesn't really serve any useful goal to
> say that it's nice in an official IETF document.  This seems like
> another statement of the "We like toast!" variety.
> 
> Simply stating that "interaction with the PSTN is a primary objective"
> isn't going to get the PSTN carriers to run around buying connections
> to all the different IP telephony networks, and I doubt the NCS would
> be really happy paying the marked-up pass-through cost of doing so,
> even if the telcos felt like doing it.
> 



[MAP] I would suggest you read more carefully before commenting and be more 
careful in your quoting. The above quote from the requirements document does 
not say "interaction with the PSTN is a primary objective" as you claim (and 
comment on).

It says "our objective is ... a direct mapping between related code points". 
This clearly refers to a case if interaction with the PSTN takes place.

Independent from whatever the IEPREP requirement is talking about, we must 
presume that there is interaction between any IP-based network providing 
"public" telephony service and the PSTN. I really can't believe you are 
questioning this aspect. If you want a statement that the requirements in 
this document do not apply to completely private Voice over IP networks, then 
that should be no problem. But it doesn't change the set of requirements in 
IEPREP which are designed to identify what protocol work is necessary to 
support other networks.

Mike Pierce
Artel


--part1_6c.2514456c.2af41cfb_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 10/31/2002 6:15:09 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&gt; Primary Objectives in support of authorized emergency calls:
<BR> &nbsp;&nbsp;&nbsp;&gt; 2) Interaction with PSTN
<BR> &nbsp;&nbsp;&nbsp;&gt; The second objective involves the interaction of IP telephony
<BR> &nbsp;&nbsp;&nbsp;&gt; signaling with existing PSTN support for emergency related voice
<BR> &nbsp;&nbsp;&nbsp;&gt; communications. &nbsp;As mentioned above in Section 1.2, standard
<BR> &nbsp;&nbsp;&nbsp;&gt; T1.631 [26] specifies emergency code points for SS7.
<BR> &nbsp;&nbsp;&nbsp;&gt; Specifically, the National Security and Emergency Preparedness
<BR> &nbsp;&nbsp;&nbsp;&gt; (NS/EP) Calling Party Category code point is defined for ISUP IAM
<BR> &nbsp;&nbsp;&nbsp;&gt; messages used by SS7 [26]. &nbsp;Hence, our objective in the
<BR> &nbsp;&nbsp;&nbsp;&gt; interaction between the PSTN and IP telephony with respect to
<BR> &nbsp;&nbsp;&nbsp;&gt; IEPS (and national indicators) is a direct mapping between
<BR> &nbsp;&nbsp;&nbsp;&gt; related code points.
<BR>
<BR>This seems problematic to me, in exactly the same way as if a user came
<BR>before the IETF with a draft which stated that that their objective was
<BR>to have carriers peer. That's nice, but that's a business decision to
<BR>be made by the carriers, and it doesn't really serve any useful goal to
<BR>say that it's nice in an official IETF document. &nbsp;This seems like
<BR>another statement of the "We like toast!" variety.
<BR>
<BR>Simply stating that "interaction with the PSTN is a primary objective"
<BR>isn't going to get the PSTN carriers to run around buying connections
<BR>to all the different IP telephony networks, and I doubt the NCS would
<BR>be really happy paying the marked-up pass-through cost of doing so,
<BR>even if the telcos felt like doing it.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>
<BR>[MAP] I would suggest you read more carefully before commenting and be more careful in your quoting. The above quote from the requirements document does not say "interaction with the PSTN is a primary objective" as you claim (and comment on).
<BR>
<BR>It says "our objective is ... a direct mapping between related code points". This clearly refers to a case if interaction with the PSTN takes place.
<BR>
<BR>Independent from whatever the IEPREP requirement is talking about, we must presume that there is interaction between any IP-based network providing "public" telephony service and the PSTN. I really can't believe you are questioning this aspect. If you want a statement that the requirements in this document do not apply to completely private Voice over IP networks, then that should be no problem. But it doesn't change the set of requirements in IEPREP which are designed to identify what protocol work is necessary to support other networks.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_6c.2514456c.2af41cfb_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:09:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26646
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:09:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1IBfV22456
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:11:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IBev22453
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:11:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26613
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:09:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IB1v22387;
	Fri, 1 Nov 2002 13:11:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IALv22221
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:10:21 -0500
Received: from imo-r07.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26562
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:07:51 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r07.mx.aol.com (mail_out_v34.13.) id b.10e.19894b9f (25914);
	Fri, 1 Nov 2002 13:09:18 -0500 (EST)
Message-ID: <10e.19894b9f.2af41d4d@aol.com>
Date: Fri, 1 Nov 2002 13:09:17 EST
Subject: Re: [Ieprep] Re: draft-ietf-ieprep-requirements-01
To: woody@pch.net, jmpolk@cisco.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_10e.19894b9f.2af41d4d_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_10e.19894b9f.2af41d4d_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 10/31/2002 4:17:07 PM Eastern Standard Time, woody@pch.net 
writes:


> Please clarify this?  My objection is to someone suggesting that they're
> requiring something of me (QoS or interconnection with arbitrary other
> networks being two examples) which I may either be unable to complete
> autonomously, which they may be unwilling to pay for, or which I may have
> neither engineering nor business motivation to do.
> 


[MAP] I'll clarify it.

No one ever said that this requirements document is intended to set 
requirements on the operator of a network to interconnection with anyone or 
to do anything. This is a requirements document to hand to SIPPING/ SIP/ or 
whatever other WG to tell them what capabilities need to be supported in 
various protocol standards. Once such protocols are available, every 
equipment vendor and network operator is free to decide whether or not they 
will support these capabilities. If your network doesn't want to do business 
with a user (e.g., US government) who wants these capabilities, then that is 
your business choice. Same with a vendor.

So can we get off this discussion about not requiring business issues and 
talk about the technical side of the requirements?

Mike Pierce
Artel


--part1_10e.19894b9f.2af41d4d_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 10/31/2002 4:17:07 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Please clarify this? &nbsp;My objection is to someone suggesting that they're
<BR>requiring something of me (QoS or interconnection with arbitrary other
<BR>networks being two examples) which I may either be unable to complete
<BR>autonomously, which they may be unwilling to pay for, or which I may have
<BR>neither engineering nor business motivation to do.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] I'll clarify it.
<BR>
<BR>No one ever said that this requirements document is intended to set requirements on the operator of a network to interconnection with anyone or to do anything. This is a requirements document to hand to SIPPING/ SIP/ or whatever other WG to tell them what capabilities need to be supported in various protocol standards. Once such protocols are available, every equipment vendor and network operator is free to decide whether or not they will support these capabilities. If your network doesn't want to do business with a user (e.g., US government) who wants these capabilities, then that is your business choice. Same with a vendor.
<BR>
<BR>So can we get off this discussion about not requiring business issues and talk about the technical side of the requirements?
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_10e.19894b9f.2af41d4d_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:22:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27352
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:22:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1IOAf25817
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:24:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IOAv25814
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:24:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27331
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:21:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IN2v25731;
	Fri, 1 Nov 2002 13:23:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IM4v25675
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:22:04 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27248
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:19:34 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA1IG8d29814;
	Fri, 1 Nov 2002 10:16:09 -0800 (PST)
Date: Fri, 1 Nov 2002 10:16:08 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: ieprep@ietf.org
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <6c.2514456c.2af41cfb@aol.com>
Message-ID: <Pine.GSO.4.44.0211011014440.28183-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 1 Nov 2002 Mpierce1@aol.com wrote:
    > Independent from whatever the IEPREP requirement is talking about, we must
    > presume that there is interaction between any IP-based network providing
    > "public" telephony service and the PSTN. I really can't believe you are
    > questioning this aspect.

Well, I certainly wouldn't _assume_ that the PSTN operators will connect
to the rest of the network.  They aren't _generally_ eager to
interconnect, certainly.  In nearly every case that I've experienced, they
actively avoid interconnecting.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:26:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27525
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:26:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1IS7626057
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:28:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IS7v26054
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:28:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27518
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:25:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IR1v25972;
	Fri, 1 Nov 2002 13:27:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IQbv25940
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:26:37 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27439
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:24:07 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA1IKgd29894;
	Fri, 1 Nov 2002 10:20:42 -0800 (PST)
Date: Fri, 1 Nov 2002 10:20:42 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: ieprep@ietf.org
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <14.155fed8.2af41d10@aol.com>
Message-ID: <Pine.GSO.4.44.0211011017030.28183-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 1 Nov 2002 Mpierce1@aol.com wrote:
    > [MAP] I can't imagine why you are questioning this requirement. It is a
    > fundamental requirement of any network to be able to route around congestion
    > (and failures).

Not at all.  The Internet, for instance, selects the best extant path.
This is _packet switching_, not _channel switching_.  Congestion is an
_instantaneous_ condition on the Internet, it's not a condition which can
be predicted at call-setup time.

    > But, I suspect (presume?) that the Internet already successfully does this,
    > so the requirement may not require anything new.

You presume wrong.  The Internet consists of individual routers,
each of which works independently to select the best extant path, not a
centralized system which selects a non-optimal uncongested path.

We did it this way because it was an improvement.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:28:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27614
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:28:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1IU3N26197
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:30:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IU3v26194
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:30:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27607
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:27:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IT1v26113;
	Fri, 1 Nov 2002 13:29:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1ISCv26071
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:28:12 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27522
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:25:42 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA1IMBd29933;
	Fri, 1 Nov 2002 10:22:11 -0800 (PST)
Date: Fri, 1 Nov 2002 10:22:11 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: jmpolk@cisco.com, <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: draft-ietf-ieprep-requirements-01
In-Reply-To: <10e.19894b9f.2af41d4d@aol.com>
Message-ID: <Pine.GSO.4.44.0211011021300.28183-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 1 Nov 2002 Mpierce1@aol.com wrote:
    > This is a requirements document to hand to SIPPING/ SIP/ or
    > whatever other WG to tell them what capabilities need to be supported in
    > various protocol standards.

Please pick one, and specify it in the title and abstract.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:29:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27694
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:29:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1IVH926294
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:31:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IVHv26291
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:31:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27668
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:28:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IU1v26182;
	Fri, 1 Nov 2002 13:30:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1ITZv26143
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:29:35 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27569
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:27:05 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 187gXx-0004PG-00; Fri, 01 Nov 2002 13:29:29 -0500
Date: Fri, 1 Nov 2002 13:29:29 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: Mpierce1@aol.com
cc: woody@pch.net, <ieprep@ietf.org>
Subject: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <14.155fed8.2af41d10@aol.com>
Message-ID: <Pine.GSO.4.40.0211011317030.16917-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


On Fri, 1 Nov 2002 Mpierce1@aol.com wrote:
> >    > 3.1.  Alternate Path Routing
> [MAP] I can't imagine why you are questioning this requirement. It is a
> fundamental requirement of any network to be able to route around congestion
> (and failures).

Because its not a fundamental requirement.

Routing around failures is a different requirement from routing around
congestion. In a packet-switched network, "congestion" is not a failure
condition.

In a circuit-switched world, congestion avoidance is a requirement because
circuit-switched networks are inherently blocking along a path.  Circuit
switched networks require alternate path routing during congestion.

On the other hand packet-switch networks are not inherently blocking along
a path under congestion conditions.  You can still send traffic through a
congested path with queue management.  At the first BOF Fred Baker
reported on some testing Cisco did on congested links and what effect it
had on the service delivery.

Both packet-switched and circuit-switch networks need to route around
circuit failures.  Circuit-switched networks use alternate path routing
around congestion. Packet switched networks use queue management during
congestion.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:30:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27771
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:30:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1IWBH26412
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:32:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IWBv26409
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:32:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27738
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:29:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IV0v26255;
	Fri, 1 Nov 2002 13:31:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IUvv26226
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:30:57 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27643
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:28:27 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1IUqm6010140;
	Fri, 1 Nov 2002 13:30:52 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1IUoH9003810
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 1 Nov 2002 13:30:51 -0500 (EST)
Message-ID: <3DC2C8CE.2030604@cs.columbia.edu>
Date: Fri, 01 Nov 2002 13:32:46 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Woodcock <woody@pch.net>
CC: Mpierce1@aol.com, ieprep@ietf.org
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
References: <Pine.GSO.4.44.0211011014440.28183-100000@paixhost.pch.net>
In-Reply-To: <Pine.GSO.4.44.0211011014440.28183-100000@paixhost.pch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

This also depends on what kind of interconnection you're talking about. 
Certainly, operators aren't eager to interconnect at the SS7 level, 
although in many cases they're legally obligated if the other party is a 
registered CLEC or IXC. LECs obviously connect to all kinds of IXCs, 
with little apparent difficulty. Whether the IXC or CLEC uses ISDN 
circuits or VoIP internally does not seem to matter, as long as the 
interface is something bell heads can understand.

For customer circuits, they have very little say about whether they want 
to connect to a "PBX with DID" that happens to be PSTN gateway into a 
large VoIP cloud. In many cases, the latter is perfectly sufficient.

> Well, I certainly wouldn't _assume_ that the PSTN operators will connect
> to the rest of the network.  They aren't _generally_ eager to
> interconnect, certainly.  In nearly every case that I've experienced, they
> actively avoid interconnecting.
>
>                                 -Bill
>
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:36:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27991
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:36:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Ic4c27363
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:38:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Ic4v27360
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:38:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27971
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:35:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Ib3v26803;
	Fri, 1 Nov 2002 13:37:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IaNv26661
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:36:24 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27935
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:33:53 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA1IUQd00176;
	Fri, 1 Nov 2002 10:30:26 -0800 (PST)
Date: Fri, 1 Nov 2002 10:30:26 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: Mpierce1@aol.com, <ieprep@ietf.org>
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <3DC2C8CE.2030604@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211011026080.28183-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 1 Nov 2002, Henning Schulzrinne wrote:
    > This also depends on what kind of interconnection you're talking about.
    > Certainly, operators aren't eager to interconnect at the SS7 level,

Nor am I willing to give them or sell them an SS7 interconnection.  I'm
williing to give them or sell them a SIP or H.323 connection, or if I'm in
a particularly generous mood, PRIs.

    > although in many cases they're legally obligated if the other party is a
    > registered CLEC or IXC.

Uh, sorry, those are all PSTN operators, by definition.  We were talking
about whether the PSTN operators were going to connect to the network, not
whether they were going to connect to each other.  I realize that they
reluctantly connect to each other.

    > Whether the IXC or CLEC uses ISDN
    > circuits or VoIP internally does not seem to matter, as long as the
    > interface is something bell heads can understand.

Uh, sorry, that's not a requirement.  Whether they're able to progress
beyond ninteenth-century technology is their problem, not mine.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:45:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28222
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:45:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1IlG927735
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:47:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IlGv27732
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:47:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28195
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:44:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Ik4v27682;
	Fri, 1 Nov 2002 13:46:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Ij2v27647
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:45:02 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28174
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:42:32 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1Iipm6011094;
	Fri, 1 Nov 2002 13:44:51 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1IioH9004341
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 1 Nov 2002 13:44:51 -0500 (EST)
Message-ID: <3DC2CC15.2020102@cs.columbia.edu>
Date: Fri, 01 Nov 2002 13:46:45 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sean Donelan <sean@donelan.com>
CC: Mpierce1@aol.com, woody@pch.net, ieprep@ietf.org
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
References: <Pine.GSO.4.40.0211011317030.16917-100000@clifden.donelan.com>
In-Reply-To: <Pine.GSO.4.40.0211011317030.16917-100000@clifden.donelan.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

While your view certainly represents the "traditional" Internet view and 
current operational practice, one should not forget that there has been 
a large body of more recent research work related to QoS routing. (And 
the good work in that area is well aware of the potential pitfalls that 
lie that way; rehashing the trade-offs here probably serves little 
purpose.) It would probably be wise to at least become aware of that 
work before dismissing things out of hand. The IEPREP documents might 
avoid misunderstandings if they hinted at that general area, so that the 
technically aware reader can file the requirement appropriately.

The IEPREP documents may want to make it clearer as to whether they are 
talking about capabilities that can be supported, with minor local 
additions, using the current operational Internet infrastructure or 
whether they require more fundamental changes. Requirements for QoS 
routing, say, would not be something we can dump in the lap of an 
existing WG, since there is none that I know of. (There is the routing 
IRTF group, but its focus seems to lie elsewhere at the moment.)

It is a separate, charter-level discussion whether IEPREP should 
restrict itself to requirements that can likely be satisfied by work 
that can be accomplished by current chartered IETF WGs.

Sean Donelan wrote:

> On Fri, 1 Nov 2002 Mpierce1@aol.com wrote:
>
> >>   > 3.1.  Alternate Path Routing
> >
> >[MAP] I can't imagine why you are questioning this requirement. It is a
> >fundamental requirement of any network to be able to route around 
> congestion
> >(and failures).
>
>
> Because its not a fundamental requirement.
>
> Routing around failures is a different requirement from routing around
> congestion. In a packet-switched network, "congestion" is not a failure
> condition.
>
> In a circuit-switched world, congestion avoidance is a requirement because
> circuit-switched networks are inherently blocking along a path.  Circuit
> switched networks require alternate path routing during congestion.
>
> On the other hand packet-switch networks are not inherently blocking along
> a path under congestion conditions.  You can still send traffic through a
> congested path with queue management.  At the first BOF Fred Baker
> reported on some testing Cisco did on congested links and what effect it
> had on the service delivery.
>
> Both packet-switched and circuit-switch networks need to route around
> circuit failures.  Circuit-switched networks use alternate path routing
> around congestion. Packet switched networks use queue management during
> congestion.
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:55:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28789
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:55:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Ivoi28260
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:57:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Ivov28257
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:57:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28744
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:55:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Iugv28175;
	Fri, 1 Nov 2002 13:56:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Irrv28072
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:53:53 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28467
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:51:23 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1Irmm6011612;
	Fri, 1 Nov 2002 13:53:48 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1IrkH9004516
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 1 Nov 2002 13:53:47 -0500 (EST)
Message-ID: <3DC2CE2E.8030701@cs.columbia.edu>
Date: Fri, 01 Nov 2002 13:55:42 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Woodcock <woody@pch.net>
CC: Mpierce1@aol.com, ieprep@ietf.org
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
References: <Pine.GSO.4.44.0211011026080.28183-100000@paixhost.pch.net>
In-Reply-To: <Pine.GSO.4.44.0211011026080.28183-100000@paixhost.pch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The 19th century carriers have the billion customers. Nobody forces you 
to connect to anything if your customers would prefer not to talk to 
those poor souls stuck in the 19th century.

However, the IEPREP documents assume, not completely unrealistically, 
that the 19th century technology carriers and those connected to them 
will not upgrade immediately, but that talking to them is still 
desirable in whatever passes as near term.

This has nothing whatsoever to do with the way that the IP side is run 
or not run or whether the current operational Internet is "better" or 
not than the PSTN. Some of the requirements of reliable, high-quality 
service that well-run parts of the PSTN has strived for seem like 
reasonable objectives.

Bill Woodcock wrote:

>       On Fri, 1 Nov 2002, Henning Schulzrinne wrote:
>     > This also depends on what kind of interconnection you're talking 
> about.
>     > Certainly, operators aren't eager to interconnect at the SS7 level,
>
> Nor am I willing to give them or sell them an SS7 interconnection.  I'm
> williing to give them or sell them a SIP or H.323 connection, or if I'm in
> a particularly generous mood, PRIs.
>
>     > although in many cases they're legally obligated if the other 
> party is a
>     > registered CLEC or IXC.
>
> Uh, sorry, those are all PSTN operators, by definition.  We were talking
> about whether the PSTN operators were going to connect to the network, not
> whether they were going to connect to each other.  I realize that they
> reluctantly connect to each other.
>
>     > Whether the IXC or CLEC uses ISDN
>     > circuits or VoIP internally does not seem to matter, as long as the
>     > interface is something bell heads can understand.
>
> Uh, sorry, that's not a requirement.  Whether they're able to progress
> beyond ninteenth-century technology is their problem, not mine.
>
>                                 -Bill
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:56:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28818
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:56:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1IwAf28352
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 13:58:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IwAv28349
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:58:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28781
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:55:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Iv2v28205;
	Fri, 1 Nov 2002 13:57:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1IuPv28143
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 13:56:25 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28627
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:53:55 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA1IoMd00666;
	Fri, 1 Nov 2002 10:50:22 -0800 (PST)
Date: Fri, 1 Nov 2002 10:50:22 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: Sean Donelan <sean@donelan.com>, <Mpierce1@aol.com>, <ieprep@ietf.org>
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <3DC2CC15.2020102@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211011046590.28183-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 1 Nov 2002, Henning Schulzrinne wrote:
    > While your view certainly represents the "traditional" Internet view and
    > current operational practice, one should not forget that there has been
    > a large body of more recent research work related to QoS routing.
    > It would probably be wise to at least become aware of that
    > work before dismissing things out of hand.

Don't be insulting.  Sean is an _operator_.  He's _unfortunately well
acquainted_ with QoS, having _implemented it in the field_ rather than
theorized about it or played with it in the lab.

QoS was an experiment which we've passed well beyond, thank god.  Anyone
still wasting time talking about it is severely disassociated with
reality.  Remember ATM?  QoS was 1999's ATM.  Remember MPLS?  Right, I
think you get my point.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 13:59:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28939
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:59:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1J1ut28572
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 14:01:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1J1uv28569
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 14:01:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28929
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 13:59:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1J12v28546;
	Fri, 1 Nov 2002 14:01:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1J0iv28514
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 14:00:44 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28873
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:58:14 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA1IxKEs004157;
	Fri, 1 Nov 2002 13:59:20 -0500 (EST)
Date: Fri, 1 Nov 2002 13:59:20 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211011859.gA1IxKEs004157@newdev.harvard.edu>
To: hgs@cs.columbia.edu, sean@donelan.com
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Cc: ieprep@ietf.org, Mpierce1@aol.com, woody@pch.net
In-Reply-To: <3DC2CC15.2020102@cs.columbia.edu>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Henning sez:
> While your view certainly represents the "traditional" Internet view and 
> current operational practice, one should not forget that there has been 
> a large body of more recent research work related to QoS routing.

this brings up two questions to me

1/ how close is that research to being deployed in ISPs?

and more importantally

2/ should this WG be talking about what the Internet can be expected
   to be able to do now or in the immediate future (see 1st deliverable
   in the WG charter) of speculate on what might be possible at some
   point in the future?

(my feeling, if its not clear, is that we should stick to the world
of today and the near future)

Scott

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 14:03:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29140
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 14:03:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1J5UT28797
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 14:05:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1J5Uv28794
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 14:05:30 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29129
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 14:03:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1J40v28722;
	Fri, 1 Nov 2002 14:04:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1J39v28688
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 14:03:09 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29015
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 14:00:36 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA1Iv9d00854;
	Fri, 1 Nov 2002 10:57:09 -0800 (PST)
Date: Fri, 1 Nov 2002 10:57:09 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: Mpierce1@aol.com, <ieprep@ietf.org>
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <3DC2CE2E.8030701@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211011051290.28183-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 1 Nov 2002, Henning Schulzrinne wrote:
    > The 19th century carriers have the billion customers. Nobody forces you
    > to connect to anything if your customers would prefer not to talk to
    > those poor souls stuck in the 19th century.

Yep, and McDonalds has sold billions of what purport to be hamburgers.
This isn't useful information in the context of something that describes
itself as a requirements draft in the IETF.

    > However, the IEPREP documents assume, not completely unrealistically,
    > that the 19th century technology carriers and those connected to them
    > will not upgrade immediately, but that talking to them is still
    > desirable in whatever passes as near term.

The IEPREP documents appear to be documenting _one user's desire_ to
continue to talk to the PSTN.  If they want to continue to talk to the
PSTN, there is, as you point out, _nothing stopping them_.  This has
_nothing to do with the IETF_ and should have _nothing to do with me_.
The one user under discussion appears to be quite happy spending my tax
dollars to continue to buy ninteenth-century technology from PSTN
carriers.  They have that forum, their customer relationship, in which
they're perfectly welcome to discuss with those providers their desire
that those providers interconnect with the rest of the world.  This
doesn't require the IETF.  There's certainly no need to require anything
of me.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 14:07:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29389
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 14:07:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1J9AB29506
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 14:09:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1J9Av29503
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 14:09:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29368
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 14:06:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1J82v29467;
	Fri, 1 Nov 2002 14:08:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1J7Mv29359
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 14:07:22 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29209
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 14:04:52 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA1J1Ld00976;
	Fri, 1 Nov 2002 11:01:21 -0800 (PST)
Date: Fri, 1 Nov 2002 11:01:21 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Scott  Bradner <sob@harvard.edu>
cc: hgs@cs.columbia.edu, <sean@donelan.com>, <ieprep@ietf.org>,
        <Mpierce1@aol.com>
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <200211011859.gA1IxKEs004157@newdev.harvard.edu>
Message-ID: <Pine.GSO.4.44.0211011058440.28183-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 1 Nov 2002, Scott  Bradner wrote:
    > > a large body of more recent research work related to QoS routing.
    > this brings up two questions to me
    > 1/ how close is that research to being deployed in ISPs?

We all deployed it, tried very hard to make it work, since people who
purported to be smart kept telling us that it was supposed to make things
better, and then threw it away when we determined empirically that they
were wrong.

    > 2/ should this WG be talking about what the Internet can be expected
    >    to be able to do now or in the immediate future (see 1st deliverable
    >    in the WG charter) of speculate on what might be possible at some
    >    point in the future?
    >
    > (my feeling, if its not clear, is that we should stick to the world
    > of today and the near future)

Yep.  Particularly since they're not talking about dependencies on future
practices, but instead upon ones which have already been deprecated and
removed.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 14:15:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29642
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 14:15:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1JHfA29846
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 14:17:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JHfv29843
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 14:17:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29618
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 14:15:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JG1v29771;
	Fri, 1 Nov 2002 14:16:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JFQv29734
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 14:15:26 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29564
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 14:12:56 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1JFJm6013587;
	Fri, 1 Nov 2002 14:15:19 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1JFHH9005378
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 1 Nov 2002 14:15:18 -0500 (EST)
Message-ID: <3DC2D339.8050004@cs.columbia.edu>
Date: Fri, 01 Nov 2002 14:17:13 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Woodcock <woody@pch.net>
CC: Mpierce1@aol.com, ieprep@ietf.org
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
References: <Pine.GSO.4.44.0211011051290.28183-100000@paixhost.pch.net>
In-Reply-To: <Pine.GSO.4.44.0211011051290.28183-100000@paixhost.pch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Requirements should be phrased to be understood as "if you would like to 
do X, here are some things to consider". The IETF has a long tradition 
of doing interconnection to legacy technology, dating back as far as the 
significant efforts to connect SMTP to X.400. This did not mean that any 
ISP was forced by the IETF to run an X.400 gateway. I don't take a 
position on whether the current documents express the "if" part 
sufficiently clearly. Maybe you can help by suggesting appropriate wording.

If you're objecting to having the IETF discuss interconnection with the 
PSTN, you probably should take this discussion to a higher layer of IETF 
management, as this topic is part of the charter of at least the ENUM, 
SIPPING, MEGACO, IPTEL, AVT and SIP WGs. The IEPREP charter clearly 
contains this interconnection functionality, as in "These capabilities 
include: conventional telephone, cellular phones" and several other places.

Bill Woodcock wrote:

>       On Fri, 1 Nov 2002, Henning Schulzrinne wrote:
>     > The 19th century carriers have the billion customers. Nobody 
> forces you
>     > to connect to anything if your customers would prefer not to talk to
>     > those poor souls stuck in the 19th century.
>
> Yep, and McDonalds has sold billions of what purport to be hamburgers.
> This isn't useful information in the context of something that describes
> itself as a requirements draft in the IETF.
>
>     > However, the IEPREP documents assume, not completely 
> unrealistically,
>     > that the 19th century technology carriers and those connected to 
> them
>     > will not upgrade immediately, but that talking to them is still
>     > desirable in whatever passes as near term.
>
> The IEPREP documents appear to be documenting _one user's desire_ to
> continue to talk to the PSTN.  If they want to continue to talk to the
> PSTN, there is, as you point out, _nothing stopping them_.  This has
> _nothing to do with the IETF_ and should have _nothing to do with me_.
> The one user under discussion appears to be quite happy spending my tax
> dollars to continue to buy ninteenth-century technology from PSTN
> carriers.  They have that forum, their customer relationship, in which
> they're perfectly welcome to discuss with those providers their desire
> that those providers interconnect with the rest of the world.  This
> doesn't require the IETF.  There's certainly no need to require anything
> of me.
>
>                                 -Bill
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 14:19:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29840
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 14:19:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1JL7N30139
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 14:21:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JL7v30136
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 14:21:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29826
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 14:18:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JK2v30056;
	Fri, 1 Nov 2002 14:20:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JJcv29994
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 14:19:38 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA29761
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 14:17:07 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 1 Nov 2002 19:14:26 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <V04YABB4>; Fri, 1 Nov 2002 14:19:37 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3CD6@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Sean Donelan'" <sean@donelan.com>, Mpierce1@aol.com
Cc: woody@pch.net, ieprep@ietf.org
Subject: RE: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework
	-02.txt
Date: Fri, 1 Nov 2002 14:19:28 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

GETS also uses trunk queuing when there is a congestion at the LEC ( not
just alternate routing paths in the IXC). This queuing mechanism would not
drop GETS calls immediately when a congestion occurs. By the way, how are
you doing it in your network to accommodate emergency traffic when
congestions occur at the access nodes (not the distribution or the core)?
How about priority queuing or weighted fair  queuing ?

In my opinion, end-to-end QoS is still a big issue in the Internet.

Regards,

An

-----Original Message-----
From: Sean Donelan [mailto:sean@donelan.com]
Sent: Friday, November 01, 2002 1:29 PM
To: Mpierce1@aol.com
Cc: woody@pch.net; ieprep@ietf.org
Subject: Congestion avoidance Re: [Ieprep]
draft-ietf-ieprep-framework-02.txt



On Fri, 1 Nov 2002 Mpierce1@aol.com wrote:
> >    > 3.1.  Alternate Path Routing
> [MAP] I can't imagine why you are questioning this requirement. It is a
> fundamental requirement of any network to be able to route around
congestion
> (and failures).

Because its not a fundamental requirement.

Routing around failures is a different requirement from routing around
congestion. In a packet-switched network, "congestion" is not a failure
condition.

In a circuit-switched world, congestion avoidance is a requirement because
circuit-switched networks are inherently blocking along a path.  Circuit
switched networks require alternate path routing during congestion.

On the other hand packet-switch networks are not inherently blocking along
a path under congestion conditions.  You can still send traffic through a
congested path with queue management.  At the first BOF Fred Baker
reported on some testing Cisco did on congested links and what effect it
had on the service delivery.

Both packet-switched and circuit-switch networks need to route around
circuit failures.  Circuit-switched networks use alternate path routing
around congestion. Packet switched networks use queue management during
congestion.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 14:24:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00092
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 14:24:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1JQ3w30333
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 14:26:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JQ3v30330
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 14:26:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00080
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 14:23:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JP2v30311;
	Fri, 1 Nov 2002 14:25:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JOvv30290
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 14:24:57 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29939
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 14:22:26 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA1JJ0d01430;
	Fri, 1 Nov 2002 11:19:00 -0800 (PST)
Date: Fri, 1 Nov 2002 11:19:00 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: Mpierce1@aol.com, <ieprep@ietf.org>
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <3DC2D339.8050004@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211011113070.28183-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 1 Nov 2002, Henning Schulzrinne wrote:
    > Requirements should be phrased to be understood as "if you would like to
    > do X, here are some things to consider". The IETF has a long tradition
    > of doing interconnection to legacy technology...

Yes, but please remember that this isn't an IETF-originated initiative,
this is a U.S. government-originated initiative.  The IETF has a long
tradition of calling things "requirements" and subsequently ignoring them.
The U.S. government has a long tradition of calling things "requirements"
and then killing people on the basis of them.  We have a basic difference
of institutional culture here, and a fundamentally dangerous ambiguity
surrounding the use of the word "requirement".

    > If you're objecting to having the IETF discuss interconnection with the
    > PSTN

Of course not.  The issue isn't _how_ or _whether_.  The former is clearly
the responsibility of the IETF to define, and the latter is a preexisting
real-world condition.  The question is one of _mandating_ interconnection,
which is clearly _not_ within the purview of the IETF, and unfortunately
_exactly_ the sort of thing that the U.S. government tries to do all the
time.  If that's _really not the intent here_, the document can be
withdrawn, and there won't be a problem.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 14:24:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00106
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 14:24:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1JQ6G30348
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 14:26:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JQ6v30345
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 14:26:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00084
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 14:23:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JO7v30266;
	Fri, 1 Nov 2002 14:24:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JNRv30235
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 14:23:27 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29915
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 14:20:56 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 187hO2-0004SN-00; Fri, 01 Nov 2002 14:23:18 -0500
Date: Fri, 1 Nov 2002 14:23:18 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: Scott  Bradner <sob@harvard.edu>
cc: ieprep@ietf.org
In-Reply-To: <200211011859.gA1IxKEs004157@newdev.harvard.edu>
Message-ID: <Pine.GSO.4.40.0211011405360.17066-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] Operational Experience
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

As long-time readers know, I've been very much in favor of getting
operational experience, identifying the operational problems, and then
solving those problems which have an impact.  I'm not a fan of solving
problems for the sake of solving problems.

I'm don't claim any of the existing systems are perfect.  I don't claim
they will work under every possible condition.  Actually, I expect we'll
find some significant problems in the systems.  I want to find out what
those problems are.  Just getting Bill's INOC-DBA system working, we've
discovered several issues which aren't covered by any of the IEPREP
documents, that need to be addressed in an operational system.

Solutions which require changing how the installed base works may be
technically elegant.  But if a crisis happened this afternoon (or in the
next 10 years), something that worked over the existing Internet would
probably be more useful.

On Fri, 1 Nov 2002, Scott  Bradner wrote:
> this brings up two questions to me
>
> 1/ how close is that research to being deployed in ISPs?
>
> and more importantally
>
> 2/ should this WG be talking about what the Internet can be expected
>    to be able to do now or in the immediate future (see 1st deliverable
>    in the WG charter) of speculate on what might be possible at some
>    point in the future?
>
> (my feeling, if its not clear, is that we should stick to the world
> of today and the near future)

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 14:26:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00165
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 14:26:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1JSRW30458
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 14:28:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JSQv30455
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 14:28:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00158
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 14:25:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JR1v30398;
	Fri, 1 Nov 2002 14:27:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JQVv30368
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 14:26:31 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00090
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 14:24:00 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1JQ9m6014485;
	Fri, 1 Nov 2002 14:26:09 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA1JQ7H9005940
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 1 Nov 2002 14:26:08 -0500 (EST)
Message-ID: <3DC2D5C3.70702@cs.columbia.edu>
Date: Fri, 01 Nov 2002 14:28:03 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott Bradner <sob@harvard.edu>
CC: sean@donelan.com, ieprep@ietf.org, Mpierce1@aol.com, woody@pch.net
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
References: <200211011859.gA1IxKEs004157@newdev.harvard.edu>
In-Reply-To: <200211011859.gA1IxKEs004157@newdev.harvard.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

At the very least, it would be helpful if drafts clearly separate the 
"here and now" from the "it might be nice to have (topic for future 
research)" and "this is unlikely to be feasible in the Internet as-is". 
The danger with requirements and similar work seems to be that this is 
taken as a license to require things that are extremely unlikely to 
happen in a time frame suitable for IETF output.

Since these documents are also meant for people outside the IETF, 
explicitly identifying things that are unlikely to be feasible 
short-term may be valuable.

(I would be curious what concrete QoS routing has been deployed, tested 
and discarded, given that none was ever really standardized in the IETF, 
as far as I can tell. RFC 2386 seems to be the only output of the QOSR 
working group that concluded in early 1999.)

Scott Bradner wrote:

> Henning sez:
>
> >While your view certainly represents the "traditional" Internet view and
> >current operational practice, one should not forget that there has been
> >a large body of more recent research work related to QoS routing.
>
>
> this brings up two questions to me
>
> 1/ how close is that research to being deployed in ISPs?
>
> and more importantally
>
> 2/ should this WG be talking about what the Internet can be expected
>    to be able to do now or in the immediate future (see 1st deliverable
>    in the WG charter) of speculate on what might be possible at some
>    point in the future?
>
> (my feeling, if its not clear, is that we should stick to the world
> of today and the near future)
>
> Scott


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 15:23:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02821
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 15:23:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1KPrY01561
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 15:25:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1KPrv01558
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 15:25:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02788
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 15:23:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1KP3v01524;
	Fri, 1 Nov 2002 15:25:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1KOEv01468
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 15:24:14 -0500
Received: from mail2.mx.voyager.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02769
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 15:21:42 -0500 (EST)
Received: from mail.delta-info.com (clyde.delta-info.com [146.145.21.34])
	by mail2.mx.voyager.net (8.11.6/8.10.2) with ESMTP id gA1KO6Q43657
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 15:24:07 -0500 (EST)
Received: from s15 ([])
        by mail.delta-info.com (Merak 4.00.100) with SMTP id DVB36921;
        Fri, 01 Nov 2002 15:12:53 -0500
Reply-To: <gthom@delta-info.com>
From: "Gary Thom" <gthom@delta-info.com>
To: <ieprep@ietf.org>, "Bill Woodcock" <woody@pch.net>
Subject: RE: [Ieprep] draft-ietf-ieprep-framework-02.txt
Date: Fri, 1 Nov 2002 15:24:24 -0500
Message-ID: <NDBBKMIGCLLNAOGKKDDPEEDGDDAA.gthom@delta-info.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <Pine.GSO.4.44.0211011113070.28183-100000@paixhost.pch.net>
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Is anyone else getting tired of listenning to this mis-conceived,
self-serving, never ending argument????

First, there is no intent to mandate anything for anyone. If the wording in
the document gives you that impression, PLEASE someone change the wording so
we can get passed this point and not have to hear this argument again.

Second, the intent IS to provide information on the functionality that is
necessary (hence the term requirements) to support emergency communications,
when desired, on IP networks. This information will be provided to the
people who develop the protocols (SIP in particular) so that they can add
the necessary OPTIONAL parameters and OPTIONAL procedures to the protocol to
support the the desired functionality.

If a user wants this OPTIONAL functionality, the user will have to pay for
it. If the service provider does not want to provide it, the user can go
somewhere else. Notice that no one is yet being killed by the government.

The desire of the user is to be able to give emergency calls a higher
probability of call completion than non-emergency calls in order to improve
emergency response efforts.

There are two levels effected by this need (better not say requirement).
First the protocol (SIP) may need to indicate to other elements in the
network that receive and interpret the protocol messages that this message
is related to an emergency call, so that the element can take action (if
appropriate) or make decisions to help improve the probability of call
completion (this means the probability that the call goes through). This is
where OPTIONAL additions may be needed in the protocol.

The other more complex issue relates to what happens the the media streams
after the call is established. Can we improve the probability that the media
streams related to the emergency call will get through and still be
inteligable.

It would be nice to see some technical / operational discussion of these
issues. nuff said.

Gary

 --------------------------------------------
 Name   : Gary A. Thom
 Company: Delta Information Systems, Inc.
 Address: 300 Welsh Rd., Bldg 3
          Horsham, PA 19044 USA
 Phone  : +1-215-657-5270 x123
 Fax    : +1-215-657-5273
 E-mail : gthom@delta-info.com
 Website: www.delta-info.com
--------------------------------------------


> -----Original Message-----
> From: ieprep-admin@ietf.org [mailto:ieprep-admin@ietf.org]On Behalf Of
> Bill Woodcock
> Sent: Friday, November 01, 2002 2:19 PM
> To: Henning Schulzrinne
> Cc: Mpierce1@aol.com; ieprep@ietf.org
> Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
>
>
>       On Fri, 1 Nov 2002, Henning Schulzrinne wrote:
>     > Requirements should be phrased to be understood as "if you
> would like to
>     > do X, here are some things to consider". The IETF has a
> long tradition
>     > of doing interconnection to legacy technology...
>
> Yes, but please remember that this isn't an IETF-originated initiative,
> this is a U.S. government-originated initiative.  The IETF has a long
> tradition of calling things "requirements" and subsequently ignoring them.
> The U.S. government has a long tradition of calling things "requirements"
> and then killing people on the basis of them.  We have a basic difference
> of institutional culture here, and a fundamentally dangerous ambiguity
> surrounding the use of the word "requirement".
>
>     > If you're objecting to having the IETF discuss
> interconnection with the
>     > PSTN
>
> Of course not.  The issue isn't _how_ or _whether_.  The former is clearly
> the responsibility of the IETF to define, and the latter is a preexisting
> real-world condition.  The question is one of _mandating_ interconnection,
> which is clearly _not_ within the purview of the IETF, and unfortunately
> _exactly_ the sort of thing that the U.S. government tries to do all the
> time.  If that's _really not the intent here_, the document can be
> withdrawn, and there won't be a problem.
>
>                                 -Bill
>
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 15:45:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03534
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 15:45:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1KlfG02940
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 15:47:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Klfv02937
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 15:47:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03531
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 15:45:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Kg2v02750;
	Fri, 1 Nov 2002 15:42:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1KeAv02673
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 15:40:10 -0500
Received: from cpmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03308
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 15:37:39 -0500 (EST)
Received: from cp-its-ieg01.mail.saic.com by cpmx.mail.saic.com for ieprep@ietf.org; Fri, 1 Nov 2002 12:39:48 -0800
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by cp-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002110112394318884
 ; Fri, 01 Nov 2002 12:39:43 -0800
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WBZX30X2>; Fri, 1 Nov 2002 15:41:05 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E778BF@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Nguyen, An'" <nguyena@ncs.gov>
Cc: woody@pch.net, ieprep@ietf.org
Subject: RE: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Date: Fri, 1 Nov 2002 15:39:47 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

An,

>By the 
> way, how are
> you doing it in your network to accommodate emergency traffic when
> congestions occur at the access nodes (not the distribution 
> or the core)?
> How about priority queuing or weighted fair  queuing ?

Bill told me about his VoIP system last year.  I'm sure he will correct me
if I have got  something wrong or things have changed.  But, he said that
QoS was not an issue.  Since the core was OC48s and OC192s running at 20%
utilization or less, there was lots of capacity.  The system was running
mostly in developed country ISPs.  

Access nodes, if I understand what you mean, don't pose a problem because
this VoIP system serves ISP NOC operators.  So they could increase their
bandwidth to the exchange if that turned out to be a problem.  It didn't
sound like it was one.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 15:51:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03844
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 15:51:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Krdj03203
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 15:53:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Krdv03200
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 15:53:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03839
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 15:51:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Kqvv03149;
	Fri, 1 Nov 2002 15:52:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Kpuv03080
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 15:51:56 -0500
Received: from sj-msg-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03727
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 15:49:26 -0500 (EST)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id gA1KpkgM005880
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 12:51:46 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ABF79784;
	Fri, 1 Nov 2002 12:49:23 -0800 (PST)
Date: Fri, 1 Nov 2002 12:52:30 -0800
Mime-Version: 1.0 (Apple Message framework v546)
Content-Type: multipart/alternative; boundary=Apple-Mail-6--105307771
From: Rohan Mahy <rohan@cisco.com>
To: ieprep@ietf.org
Message-Id: <D6898030-EDDB-11D6-98BC-0003938AF740@cisco.com>
X-Mailer: Apple Mail (2.546)
Subject: [Ieprep] interconnect requirements discussion
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--Apple-Mail-6--105307771
Content-Type: text/plain;
	charset=ISO-8859-1;
	format=flowed
Content-Transfer-Encoding: quoted-printable

Hi,

I'd like to propose reword this statement:
   =A0> Primary Objectives in support of authorized emergency calls:
=A0=A0=A0> 2) Interaction with PSTN
=A0=A0=A0> The second objective involves the interaction of IP telephony
=A0=A0=A0> signaling with existing PSTN support for emergency related =
voice
=A0=A0=A0> communications. =A0As mentioned above in Section 1.2, =
standard
=A0=A0=A0> T1.631 [26] specifies emergency code points for SS7.
=A0=A0=A0> Specifically, the National Security and Emergency =
Preparedness
=A0=A0=A0> (NS/EP) Calling Party Category code point is defined for ISUP =
IAM
=A0=A0=A0> messages used by SS7 [26]. =A0Hence, our objective in the
=A0=A0=A0> interaction between the PSTN and IP telephony with respect to
=A0=A0=A0> IEPS (and national indicators) is a direct mapping between
=A0=A0=A0> related code points.

To something more like this.
     Primary Objectives in support of authorized emergency calls:
=A0=A0=A0 2) No loss of information when interacting with PSTN signaling
=A0=A0=A0 The second objective involves the interaction of IP telephony
=A0=A0=A0 signaling with existing PSTN support for emergency related =
voice
=A0=A0=A0 communications. =A0As mentioned above in Section 1.2, standard
=A0=A0=A0 T1.631 [26] specifies emergency code points for SS7.
=A0=A0=A0 Specifically, the National Security and Emergency Preparedness
=A0=A0=A0 (NS/EP) Calling Party Category code point is defined for ISUP =
IAM
=A0=A0=A0 messages used by SS7 [26]. =A0Hence, when IP providers choose =
to
     interconnect with the PSTN, it is our objective that this
=A0=A0=A0 interaction between the PSTN and IP telephony with respect to
=A0=A0=A0 IEPS (and national indicators) is a semantically =
straightforward,
     reversible mapping of comparable code points.

I believe that this addresses Bill's concern while preserving the=20
apparent goal of the original paragraph

thanks,
-rohan=

--Apple-Mail-6--105307771
Content-Type: text/enriched;
	charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<fontfamily><param>Arial</param>Hi,


I'd like to propose reword this statement:

  =A0> Primary Objectives in support of authorized emergency calls:

=A0=A0=A0> 2) Interaction with PSTN

=A0=A0=A0> The second objective involves the interaction of IP telephony

=A0=A0=A0> signaling with existing PSTN support for emergency related =
voice

=A0=A0=A0> communications. =A0As mentioned above in Section 1.2, =
standard

=A0=A0=A0> T1.631 [26] specifies emergency code points for SS7.

=A0=A0=A0> Specifically, the National Security and Emergency =
Preparedness

=A0=A0=A0> (NS/EP) Calling Party Category code point is defined for ISUP =
IAM

=A0=A0=A0> messages used by SS7 [26]. =A0Hence, our objective in the

=A0=A0=A0> interaction between the PSTN and IP telephony with respect to

=A0=A0=A0> IEPS (and national indicators) is a direct mapping between

=A0=A0=A0> related code points.


To something more like this.

    Primary Objectives in support of authorized emergency calls:

=A0=A0=A0 2) No loss of information when interacting with PSTN signaling

=A0=A0=A0 The second objective involves the interaction of IP telephony

=A0=A0=A0 signaling with existing PSTN support for emergency related =
voice

=A0=A0=A0 communications. =A0As mentioned above in Section 1.2, standard

=A0=A0=A0 T1.631 [26] specifies emergency code points for SS7.

=A0=A0=A0 Specifically, the National Security and Emergency Preparedness

=A0=A0=A0 (NS/EP) Calling Party Category code point is defined for ISUP =
IAM

=A0=A0=A0 messages used by SS7 [26]. =A0Hence, when IP providers choose =
to=20

    interconnect with the PSTN, it is our objective that this

=A0=A0=A0 interaction between the PSTN and IP telephony with respect to

=A0=A0=A0 IEPS (and national indicators) is a semantically =
straightforward,=20

    reversible mapping of comparable code points.


I believe that this addresses Bill's concern while preserving the
apparent goal of the original paragraph


thanks,

-rohan</fontfamily>=

--Apple-Mail-6--105307771--

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 16:17:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04595
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 16:17:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1LJrr04803
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 16:19:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1LJrv04800
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 16:19:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04571
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 16:17:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1LJ3v04769;
	Fri, 1 Nov 2002 16:19:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1LI3v04745
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 16:18:03 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04507
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 16:15:32 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 187jAr-0004X1-00; Fri, 01 Nov 2002 16:17:49 -0500
Date: Fri, 1 Nov 2002 16:17:49 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
cc: "'Nguyen, An'" <nguyena@ncs.gov>, <woody@pch.net>, <ieprep@ietf.org>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E778BF@mcl-its-exs01>
Message-ID: <Pine.GSO.4.40.0211011605370.17391-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] The Real Problem: Emergency traffic through firewalls
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Fri, 1 Nov 2002, King, Kimberly  S. wrote:
> Bill told me about his VoIP system last year.  I'm sure he will correct me
> if I have got  something wrong or things have changed.  But, he said that
> QoS was not an issue.  Since the core was OC48s and OC192s running at 20%
> utilization or less, there was lots of capacity.  The system was running
> mostly in developed country ISPs.

It started out that way. But now people are using their INOC-DBA phones at
home, on the road, from conferences in China, at the end of satellite
links.

So far QoS has been a non-problem.

The number 1 problem, and biggest headache, is getting emergency traffic
to pass through firewalls.  What magic bit I can set in my packets to
tell firewalls to let my emergency traffic through?

As a practical solution, we are specifying in great detail our protocol
characteristics (ports/protocol/ips), so the firewall people will let our
calls pass.

If you want to compare it to GETS, its like getting hotel PBX's to
recognize area code 710.  It doesn't matter what magic is done in the PSTN
to give calls special handling if you can't get past the hotel PBX.  On
the other hand, if GETS had used a 1-800 prefix, and then did special
magic inside the network, most PBX's would have let the calls through by
default.

The same will probably be true with the Internet.  You want to use stuff
that works by default as much as possible, to get the emergency calls
through parts of the network which don't know about your magic.  Only
apply the magic to the parts of the network which understand the magic.

This type of practical stuff is discovered when you have operational
experience.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 16:36:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05317
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 16:36:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1LcvM06149
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 16:38:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Lcvv06146
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 16:38:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05298
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 16:36:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Lc3v06129;
	Fri, 1 Nov 2002 16:38:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1LbVv06090
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 16:37:31 -0500
Received: from wells.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05255
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 16:35:00 -0500 (EST)
Received: from JMPOLK-W2K (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id NAA07534 for <ieprep@ietf.org>; Fri, 1 Nov 2002 13:37:24 -0800 (PST)
Message-Id: <4.1.20021101153436.02843ef8@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Fri, 01 Nov 2002 15:37:13 -0600
To: ieprep@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Ieprep] interconnect requirements discussion
In-Reply-To: <D6898030-EDDB-11D6-98BC-0003938AF740@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

If this makes Bill's users less confused about their service with(in) Bill's
network, I'm all for it.

Quoting my 5 year old (from the back seat): "are we there yet"?

At 12:52 PM 11/1/2002 -0800, Rohan Mahy wrote: 
>
> Hi, 
>
> I'd like to propose reword this statement: 
>    > Primary Objectives in support of authorized emergency calls: 
>    > 2) Interaction with PSTN 
>    > The second objective involves the interaction of IP telephony 
>    > signaling with existing PSTN support for emergency related voice 
>    > communications.  As mentioned above in Section 1.2, standard 
>    > T1.631 [26] specifies emergency code points for SS7. 
>    > Specifically, the National Security and Emergency Preparedness 
>    > (NS/EP) Calling Party Category code point is defined for ISUP IAM 
>    > messages used by SS7 [26].  Hence, our objective in the 
>    > interaction between the PSTN and IP telephony with respect to 
>    > IEPS (and national indicators) is a direct mapping between 
>    > related code points. 
>
> To something more like this. 
>     Primary Objectives in support of authorized emergency calls: 
>     2) No loss of information when interacting with PSTN signaling 
>     The second objective involves the interaction of IP telephony 
>     signaling with existing PSTN support for emergency related voice 
>     communications.  As mentioned above in Section 1.2, standard 
>     T1.631 [26] specifies emergency code points for SS7. 
>     Specifically, the National Security and Emergency Preparedness 
>     (NS/EP) Calling Party Category code point is defined for ISUP IAM 
>     messages used by SS7 [26].  Hence, when IP providers choose to 
>     interconnect with the PSTN, it is our objective that this 
>     interaction between the PSTN and IP telephony with respect to 
>     IEPS (and national indicators) is a semantically straightforward, 
>     reversible mapping of comparable code points. 
>
> I believe that this addresses Bill's concern while preserving the apparent
> goal of the original paragraph 
>
> thanks, 
> -rohan



cheers,
James 

              *************************************
"People generally demand more respect for their own rights than 
                         they are willing to allow for others"


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 17:34:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07106
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 17:34:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Mali09539
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 17:36:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Malv09536
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 17:36:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07097
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 17:34:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Ma6v09498;
	Fri, 1 Nov 2002 17:36:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1MZov09448
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 17:35:50 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07048
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 17:33:19 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.22746-0@bells.cs.ucl.ac.uk>; Fri, 1 Nov 2002 22:34:48 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Rohan Mahy <rohan@cisco.com>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] interconnect requirements discussion
In-reply-to: Your message of "Fri, 01 Nov 2002 12:52:30 PST." <D6898030-EDDB-11D6-98BC-0003938AF740@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Date: Fri, 01 Nov 2002 22:34:47 +0000
Message-ID: <28627.1036190087@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA1MZov09449
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> I'd like to propose reword this statement:
> 
> To something more like this.
>     Primary Objectives in support of authorized emergency calls:
>     2) No loss of information when interacting with PSTN signaling
>     The second objective involves the interaction of IP telephony
>     signaling with existing PSTN support for emergency related voice
>     communications.  As mentioned above in Section 1.2, standard
>     T1.631 [26] specifies emergency code points for SS7.
>     Specifically, the National Security and Emergency Preparedness
>     (NS/EP) Calling Party Category code point is defined for ISUP IAM
>     messages used by SS7 [26].  Hence, when IP providers choose to 
>     interconnect with the PSTN, it is our objective that this
>     interaction between the PSTN and IP telephony with respect to
>     IEPS (and national indicators) is a semantically straightforward, 
>     reversible mapping of comparable code points.

fine.  the change will be made.

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 17:34:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07108
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 17:34:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Mala09554
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 17:36:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Malv09551
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 17:36:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07099
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 17:34:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Ma5v09482;
	Fri, 1 Nov 2002 17:36:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1MZnv09444
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 17:35:49 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07046
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 17:33:18 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.22624-0@bells.cs.ucl.ac.uk>; Fri, 1 Nov 2002 22:33:16 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: Sean Donelan <sean@donelan.com>, Mpierce1@aol.com, woody@pch.net,
        ieprep@ietf.org
In-reply-to: Your message of "Fri, 01 Nov 2002 13:46:45 EST." <3DC2CC15.2020102@cs.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 01 Nov 2002 22:33:14 +0000
Message-ID: <28209.1036189994@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Subject: [Ieprep] Re: Congestion avoidance Re: [Ieprep]
 draft-ietf-ieprep-framework-02.txt
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> The IEPREP documents may want to make it clearer as to whether they are 
> talking about capabilities that can be supported, with minor local 
> additions, using the current operational Internet infrastructure...

yes, can do with respect to making it clearer.

> At the very least, it would be helpful if drafts clearly separate the 
> "here and now" from the "it might be nice to have (topic for future 
> research)" and "this is unlikely to be feasible in the Internet as-is". 
> The danger with requirements and similar work seems to be that this is 
> taken as a license to require things that are extremely unlikely to 
> happen in a time frame suitable for IETF output.

within reason, the Framework document attempts to to this where
appropriate.  the unfortunate aspect was the use of the word 
"requirement" in the document.  as stated earlier, different
phrasing will be used to avoid this confusion.

> Since these documents are also meant for people outside the IETF, 
> explicitly identifying things that are unlikely to be feasible 
> short-term may be valuable.

agreed.  in addition, more background than normally used is meant to 
educate both the traditional IETF'ers and those of other backgrounds

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 17:40:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07237
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 17:40:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Mggu10348
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 17:42:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Mggv10345
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 17:42:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07231
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 17:40:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Mg2v10329;
	Fri, 1 Nov 2002 17:42:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Mfpv10315
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 17:41:51 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07207
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 17:39:19 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 1 Nov 2002 22:36:36 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <V04YAHG1>; Fri, 1 Nov 2002 17:41:48 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3CD9@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>
Cc: woody@pch.net, ieprep@ietf.org
Subject: RE: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework
	-02.txt
Date: Fri, 1 Nov 2002 17:41:41 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Kimberly,

There is no problem now with the core, I agree. But the picture might look
different later on. 

Are you saying if there is any problem with the access node, the network
operators will solve the problem by throwing more equipment at it? The
question is that how dynamic is that bandwidth increasing in response to
congestions?

An

-----Original Message-----
From: King, Kimberly S. [mailto:KIMBERLY.S.KING@saic.com]
Sent: Friday, November 01, 2002 3:40 PM
To: 'Nguyen, An'
Cc: woody@pch.net; ieprep@ietf.org
Subject: RE: Congestion avoidance Re: [Ieprep]
draft-ietf-ieprep-framework-02.txt


An,

>By the 
> way, how are
> you doing it in your network to accommodate emergency traffic when
> congestions occur at the access nodes (not the distribution 
> or the core)?
> How about priority queuing or weighted fair  queuing ?

Bill told me about his VoIP system last year.  I'm sure he will correct me
if I have got  something wrong or things have changed.  But, he said that
QoS was not an issue.  Since the core was OC48s and OC192s running at 20%
utilization or less, there was lots of capacity.  The system was running
mostly in developed country ISPs.  

Access nodes, if I understand what you mean, don't pose a problem because
this VoIP system serves ISP NOC operators.  So they could increase their
bandwidth to the exchange if that turned out to be a problem.  It didn't
sound like it was one.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 18:18:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08099
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 18:18:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1NKpE12218
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 18:20:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1NKpv12215
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 18:20:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08093
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 18:18:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1NK5v12186;
	Fri, 1 Nov 2002 18:20:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1NJpv12137
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 18:19:51 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08084
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 18:17:19 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <QXJ5193B>; Fri, 1 Nov 2002 18:17:42 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A414940@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Rohan Mahy'" <rohan@cisco.com>, ieprep@ietf.org
Subject: RE: [Ieprep] interconnect requirements discussion
Date: Fri, 1 Nov 2002 18:17:32 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C281FC.DB26A5C0"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C281FC.DB26A5C0
Content-Type: text/plain;
	charset="iso-8859-1"

It satisfies me.

-----Original Message-----
From: Rohan Mahy [mailto:rohan@cisco.com]
Sent: Friday, November 01, 2002 3:53 PM
To: ieprep@ietf.org
Subject: [Ieprep] interconnect requirements discussion



Hi, 


I'd like to propose reword this statement: 

 > Primary Objectives in support of authorized emergency calls: 

   > 2) Interaction with PSTN 

   > The second objective involves the interaction of IP telephony 

   > signaling with existing PSTN support for emergency related voice 

   > communications.  As mentioned above in Section 1.2, standard 

   > T1.631 [26] specifies emergency code points for SS7. 

   > Specifically, the National Security and Emergency Preparedness 

   > (NS/EP) Calling Party Category code point is defined for ISUP IAM 

   > messages used by SS7 [26].  Hence, our objective in the 

   > interaction between the PSTN and IP telephony with respect to 

   > IEPS (and national indicators) is a direct mapping between 

   > related code points. 


To something more like this. 

Primary Objectives in support of authorized emergency calls: 

    2) No loss of information when interacting with PSTN signaling 

    The second objective involves the interaction of IP telephony 

    signaling with existing PSTN support for emergency related voice 

    communications.  As mentioned above in Section 1.2, standard 

    T1.631 [26] specifies emergency code points for SS7. 

    Specifically, the National Security and Emergency Preparedness 

    (NS/EP) Calling Party Category code point is defined for ISUP IAM 

    messages used by SS7 [26].  Hence, when IP providers choose to 

interconnect with the PSTN, it is our objective that this 

    interaction between the PSTN and IP telephony with respect to 

    IEPS (and national indicators) is a semantically straightforward, 

reversible mapping of comparable code points. 


I believe that this addresses Bill's concern while preserving the apparent
goal of the original paragraph 


thanks, 

-rohan


------_=_NextPart_001_01C281FC.DB26A5C0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE></TITLE>

<META content="MSHTML 5.50.4134.600" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=480281923-01112002><FONT face=Arial color=#0000ff size=2>It 
satisfies me.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Rohan Mahy 
  [mailto:rohan@cisco.com]<BR><B>Sent:</B> Friday, November 01, 2002 3:53 
  PM<BR><B>To:</B> ieprep@ietf.org<BR><B>Subject:</B> [Ieprep] interconnect 
  requirements discussion<BR><BR></FONT></DIV>
  <P><FONT face=Arial>Hi, </FONT></P><BR>
  <P><FONT face=Arial>I'd like to propose reword this statement: </FONT></P>
  <P><FONT face=Arial>&nbsp;&gt; Primary Objectives in support of authorized 
  emergency calls: </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; 2) Interaction with PSTN 
</FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; The second objective involves the 
  interaction of IP telephony </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; signaling with existing PSTN 
  support for emergency related voice </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; communications. &nbsp;As mentioned 
  above in Section 1.2, standard </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; T1.631 [26] specifies emergency 
  code points for SS7. </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; Specifically, the National Security 
  and Emergency Preparedness </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; (NS/EP) Calling Party Category code 
  point is defined for ISUP IAM </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; messages used by SS7 [26]. 
  &nbsp;Hence, our objective in the </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; interaction between the PSTN and IP 
  telephony with respect to </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; IEPS (and national indicators) is a 
  direct mapping between </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp;&gt; related code points. 
</FONT></P><BR>
  <P><FONT face=Arial>To something more like this. </FONT></P>
  <P><FONT face=Arial>Primary Objectives in support of authorized emergency 
  calls: </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp; 2) No loss of information when 
  interacting with PSTN signaling </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp; The second objective involves the 
  interaction of IP telephony </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp; signaling with existing PSTN support 
  for emergency related voice </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp; communications. &nbsp;As mentioned 
  above in Section 1.2, standard </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp; T1.631 [26] specifies emergency code 
  points for SS7. </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp; Specifically, the National Security and 
  Emergency Preparedness </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp; (NS/EP) Calling Party Category code 
  point is defined for ISUP IAM </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp; messages used by SS7 [26]. &nbsp;Hence, 
  when IP providers choose to </FONT></P>
  <P><FONT face=Arial>interconnect with the PSTN, it is our objective that this 
  </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp; interaction between the PSTN and IP 
  telephony with respect to </FONT></P>
  <P><FONT face=Arial>&nbsp;&nbsp;&nbsp; IEPS (and national indicators) is a 
  semantically straightforward, </FONT></P>
  <P><FONT face=Arial>reversible mapping of comparable code points. 
  </FONT></P><BR>
  <P><FONT face=Arial>I believe that this addresses Bill's concern while 
  preserving the apparent goal of the original paragraph </FONT></P><BR>
  <P><FONT face=Arial>thanks, </FONT></P>
  <P><FONT face=Arial>-rohan</FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C281FC.DB26A5C0--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 19:25:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10106
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 19:25:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA20R9J15831
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 19:27:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA20R9v15828
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 19:27:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10103
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 19:24:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA20QKv15805;
	Fri, 1 Nov 2002 19:26:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA20PQv15772
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 19:25:26 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10065
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 19:22:53 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 1 Nov 2002 18:25:18 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Date: Fri, 1 Nov 2002 18:25:18 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9AFD3@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Thread-Index: AcKCBlJc13CZOJiJQ52GJQ3CBIDCLQ==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>,
        "Scott Bradner" <sob@harvard.edu>
Cc: <sean@donelan.com>, <ieprep@ietf.org>, <Mpierce1@aol.com>, <woody@pch.net>
X-OriginalArrivalTime: 02 Nov 2002 00:25:18.0772 (UTC) FILETIME=[52A47740:01C28206]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA20PUv15774
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> While your view certainly represents the "traditional" Internet view and 
> current operational practice, one should not forget that there has been 
> a large body of more recent research work related to QoS routing.
[...]
> (I would be curious what concrete QoS routing has been deployed, tested 
> and discarded, given that none was ever really  standardized in the IETF, 
> as far as I can tell. RFC 2386 seems to be the only  output of the QOSR 
> working group that concluded in early 1999.)

  The non-deployment of many QoS technologies ( including QoS routing) is
mainly due to gap between the operational/engineering/research community.

- For example, scalability is not the only issue for lack of interest
  in Integrated services. Intserv expects reservation to cross administrative
  boundaries without any hurdle( which is highly impractical!!!) 

- Also, many of the QoS routing schemes are load-insensitive and assumes 
  connection-oriented nature, which is again impractical. QoS routing
  researchers assume many things which practical network doesn't support
 ( e.g. unequal splitting.) To be frank, most of the QoS routing schemes will
  be overkill for the network ( even if the operators are ready to deploy.)

- Lack of necessary business models. For example, Diffserv is supported 
  only edge to edge ( not e2e) due to lack of proper inter-domain
  economic models. 

  Their are many places (particularly access) where QoS techniques are 
necessary. But, we should try our best to rely on our heuristics & 
inference from operational experience to solve the problems of the Network.  

  I don't think, we have realized any of geoff's ideas for QoS 
deployement (RFC 2990.) So, it high time that we look back and restrategise 
ourself wrt QoS research. Though, its totally out of scope for ieprep, it 
is _necessary_ for IETF to look into the issues of complexity/overloading/arch 
in many of the QoS proposals. Some of the starting points:
http://www.nanog.org/mtg-0210/complexity.html
http://www.ietf.org/internet-drafts/draft-iab-considerations-03.txt
http://www.ieee-infocom.org/2002/images/Panel-2/2-6_Lixia_Zhang.pdf  

Thats said, lets stop the QoS/bandwidth/deployment discussion and worry about
other important issues.




 




  



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  1 21:02:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12529
	for <ieprep-archive@odin.ietf.org>; Fri, 1 Nov 2002 21:02:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA2247Y21241
	for ieprep-archive@odin.ietf.org; Fri, 1 Nov 2002 21:04:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2247v21238
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 21:04:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12498
	for <ieprep-web-archive@ietf.org>; Fri, 1 Nov 2002 21:01:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA223Iv21198;
	Fri, 1 Nov 2002 21:03:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA222Ov21110
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 21:02:24 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12405
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 20:59:50 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 1 Nov 2002 20:02:16 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Date: Fri, 1 Nov 2002 20:02:15 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9AFD4@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Thread-Index: AcKCE93fgqClsZEVQGKiz1r9FyAxJg==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>,
        "Ken Carlberg" <K.Carlberg@cs.ucl.ac.uk>
Cc: "Bill Woodcock" <woody@pch.net>, <ieprep@ietf.org>
X-OriginalArrivalTime: 02 Nov 2002 02:02:16.0383 (UTC) FILETIME=[DE3574F0:01C28213]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA222Ov21111
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

--- Henning Schulzrinne <hgs@cs.columbia.edu> wrote:
> There have been approximately half a dozen published
> papers that have 
> attempted to characterize VoIP quality over various
> parts of the 
> Internet. Not surprisingly, there are generally
> three observations:
[...]
> - some are persistently bad to unusable, typically
> but not exclusively 
> for sessions between North America and Latin America
> and parts of Asia, 
> as well as between non-NA regions.
 sometimes even backbone(fig 9-14 in
http://www.ieee-infocom.org/2002/papers/355.pdf.) They
have shown that even over-provisioned paths provide poor 
VoIP performance by using some backbone traces. 
Even with good echo cancellation and G.711 encoder, some 
over-provisioned links provide less than 3.5 MOS level
(which is well below PSTN expectations.) But, I like their 
conclusion/ further work where they try to achieve higher 
MOS by just optimizing play out buffers( unlike 
run-of-the-mill statements like "I have QoS for rescue".) 
But still diffserv is an obvious approach here.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  2 07:06:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03018
	for <ieprep-archive@odin.ietf.org>; Sat, 2 Nov 2002 07:06:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA2C8Qa26896
	for ieprep-archive@odin.ietf.org; Sat, 2 Nov 2002 07:08:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2C8Qv26893
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 2 Nov 2002 07:08:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03015
	for <ieprep-web-archive@ietf.org>; Sat, 2 Nov 2002 07:05:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2C7Zv26852;
	Sat, 2 Nov 2002 07:07:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2C6jv26248
	for <ieprep@optimus.ietf.org>; Sat, 2 Nov 2002 07:06:45 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02970
	for <ieprep@ietf.org>; Sat, 2 Nov 2002 07:04:18 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id BFF9E67103; Sat,  2 Nov 2002 03:26:43 -0500 (EST)
Date: Sat, 2 Nov 2002 07:06:44 -0500
Subject: Re: [Ieprep] draft-ietf-ieprep-requirements-01.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Rex Buddenberg <budden@nps.navy.mil>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <1036120386.1084.96.camel@localhost.localdomain>
Message-Id: <8DECFE85-EE5B-11D6-9F10-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 1, 2002, at 11:51 America/Montreal, Rex Buddenberg wrote:
> As an economic analysis, the students did some life cycle costing
> against three choices. If you need to replace your PBX then:
> 	- buy a new PBX?
> 	- buy a VOIP capability instead?  (Assumption is that you have a data
> network)
> 	- some hybrid between?
> The analysis clearly said buy whole hog into VOIP; don't buy a new PBX
> (the month following, our campus bought a new PBX...)

Extreme did that analysis within the last ~year and reached the 
conclusion
that a PBX had lower life-cycle and business costs.  So we have a PBX
at the office I work in.  Not sure what was in your students' analysis,
but maybe their model had different assumptions than a business might 
use.

> What was not covered in this analysis was the economies of 'collapsed
> bandwidth'.  Right now, the typical naval ship has several radios, each
> with a 3kHz voice equivalent bandwidth (ignoring digitization and ssb
> stuff).  And the commstas have the ability to splice radio calls into
> the PSTN (phone patch).  Yeah, all these radios are mutually 
> interfering
> emitters.  But a large (and proportionally growing) portion of the 
> radio
> comms is data.  If you push all of that into a fewer number of larger
> sized pipes (keeping overall bandwidth constant) the number of emitters
> goes down (less self-interference).  There are a whole bunch of
> economies here to avoiding having to maintain voice channels, video
> channels and data channels and just having IP channels.  All of this
> argument reinforces the economy conclusion the students did find.

And the USN has been trying to merge its stovepipe comm systems for at
least 10 years (that I personally recall) with near zero success.  One
of the problems has been getting different groups of people responsible
for different (sub)systems to agree on how a shared bandwidth comm 
system
would allocate its bandwidth.  Another problem is that the RF 
characteristics
of those systems vary significantly (consider HF Radio and the sunspot 
cycle
with SHF SATCOM and rain fade; similar issues in theory but very 
different
in operational practice).  In the early 90s, this activity was sometimes
called "Copernicus" by some parts of the USN.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  2 07:07:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03044
	for <ieprep-archive@odin.ietf.org>; Sat, 2 Nov 2002 07:07:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA2C9kE26935
	for ieprep-archive@odin.ietf.org; Sat, 2 Nov 2002 07:09:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2C9kv26932
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 2 Nov 2002 07:09:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03038
	for <ieprep-web-archive@ietf.org>; Sat, 2 Nov 2002 07:07:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2C91v26921;
	Sat, 2 Nov 2002 07:09:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2C8Nv26889
	for <ieprep@optimus.ietf.org>; Sat, 2 Nov 2002 07:08:23 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03012
	for <ieprep@ietf.org>; Sat, 2 Nov 2002 07:05:56 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id E53D367103; Sat,  2 Nov 2002 03:28:21 -0500 (EST)
Date: Sat, 2 Nov 2002 07:08:22 -0500
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>, <ieprep@ietf.org>
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211010939530.28183-100000@paixhost.pch.net>
Message-Id: <C8633ACD-EE5B-11D6-9F10-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 1, 2002, at 12:41 America/Montreal, Bill Woodcock wrote:

>> right,  but here is a counter argument.  IP routing may still route 
>> flows
>> through a path that has loss that is tolerable to elastic traffic, but
>> considered intolerable for VoIP traffic.  hence, alternate path
>> application layer routing (ala TRIP) may be of help to circumvent this
>> duality.
>>
>> within the context of the framework document, its simply a value added
>> functionality to be considered.
>
> I think Ran's point, and mine, is that this is not a value add, it's a
> value subtraction.  In the real world, this simply won't work.  It's a
> Rube Goldberg contraption which no one has any incentive to try to make
> work.

My other point is that if the intent really is *application-layer* 
routing,
then that precision was not obvious in my reading of the current text.
Though I do basically share the belief that relying on normal IP dynamic
routing is probably the more successful strategy overall...

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  2 09:51:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06023
	for <ieprep-archive@odin.ietf.org>; Sat, 2 Nov 2002 09:51:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA2Erso02230
	for ieprep-archive@odin.ietf.org; Sat, 2 Nov 2002 09:53:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2Errv02227
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 2 Nov 2002 09:53:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06017
	for <ieprep-web-archive@ietf.org>; Sat, 2 Nov 2002 09:51:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2Er7v02207;
	Sat, 2 Nov 2002 09:53:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2EqRv02178
	for <ieprep@optimus.ietf.org>; Sat, 2 Nov 2002 09:52:27 -0500
Received: from cpmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06009
	for <ieprep@ietf.org>; Sat, 2 Nov 2002 09:49:58 -0500 (EST)
Received: from cp-its-ieg01.mail.saic.com by cpmx.mail.saic.com for ieprep@ietf.org; Sat, 2 Nov 2002 06:52:06 -0800
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by cp-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002110206520207284
 for <ieprep@ietf.org>; Sat, 02 Nov 2002 06:52:02 -0800
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WBZ42RVY>; Sat, 2 Nov 2002 09:51:55 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E778C0@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'ieprep@ietf.org'" <ieprep@ietf.org>
Date: Sat, 2 Nov 2002 09:52:07 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Ieprep] QoS in the Internet
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

For those of you that are interested in background material on QoS in the
Internet...

Geoff Huston: QoS Fact or Fiction
http://www.potaroo.net/papers/ipj/3-1-qos.pdf

Interconnection, Peering, and Settlements
http://www.potaroo.net/papers/inet99/peering.htm
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  2 11:40:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08367
	for <ieprep-archive@odin.ietf.org>; Sat, 2 Nov 2002 11:40:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA2GgD107909
	for ieprep-archive@odin.ietf.org; Sat, 2 Nov 2002 11:42:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2GgDv07906
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 2 Nov 2002 11:42:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08356
	for <ieprep-web-archive@ietf.org>; Sat, 2 Nov 2002 11:39:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2GfFv07888;
	Sat, 2 Nov 2002 11:41:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2GeVv07872
	for <ieprep@optimus.ietf.org>; Sat, 2 Nov 2002 11:40:31 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08352
	for <ieprep@ietf.org>; Sat, 2 Nov 2002 11:38:02 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA2Gdjaq007031
	for ieprep@ietf.org; Sat, 2 Nov 2002 11:39:45 -0500 (EST)
Date: Sat, 2 Nov 2002 11:39:45 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211021639.gA2Gdjaq007031@newdev.harvard.edu>
To: ieprep@ietf.org
Subject: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

I'm going to follow Kimberly's lead and try to focus the discussion of
draft-ietf-ieprep-requirements-01.txt by going through it a few
requirements at a time. 

After we discuss the requirements we can go back to look at the other
material in the document.

(as an aside, it does help to number requirements as is done in the SIP
requirements - it makes it easier to talk about them and it makes it easier
for documents which talk about meeting requirements to talk about which
requirements they are talking about - I've numbered the requirements here
for ease of discussion)

As noted on the list yesterday - I think that we need to be quite careful
to specify whether we are talking about what requirements can be met on the
Internet (and private IP networks) with existing or near-term technology
and what would require significant new technology development.

I think that we also need to be careful to say what requirements can be met
with the current Internet architectural model (of autonomous
interconnecting with no particular service guarantees) and what would
require a change in this architectural model.  Along this line, we should
also be careful to say which requirements are targeted at use within an
enterprise (such as a telephone company using IP internally), at a single
ISP and which are expected to be able to be met for traffic spanning ISPs
in the open Internet.

my notes/questions at ">>"

User Requirements - 1-5

  The basic user requirements that need to be considered in providing
  emergency telecommunication capabilities to support recovery
  operations from serious disaster situations are summarized as
  follows.  Note that we assume the presence of Service Level
  Agreements in cases where user requirements cover expectations of  
  service providers:

>> see above - I'm not sure what the context is for the last
>> sentence - are we talking about the customer of a single ISP
>> using only that ISP for the emergency communications to other
>> sites on the same ISP?  If so I can see how a SLA could be 
>> used, otherwise I do not know what SLA is being referred to
   
  1  Users should be able to use public telecommunication
     resources for supporting emergency communications to help
     organize and coordinate immediate disaster recovery
     operations.
>> I do not know what is meant by "public telecommunication 
>> resources " - does this refer to the PSTN or to the Internet?

>> This seems more of a goal than a requirement.
>> Requirements should be specific enough to know if they are being 
>> met, use within an enterprise network, or within a single ISP
>> is quite different than use of the general Internet where
>> there is no guarantee where the other end of the communication
>> may be.
   
  2  Users that access emergency telecommunications service must
     be authenticated.  This should be accomplished in a timely
     manner.
>> see above, this does not seem specific enough to know if
>> its being met - for example, I can see a case where no 
>> authentication is needed over the IP part of an emergency
>> call because there are no facilities for authentication or
>> because the is no need to authenticate because there are 
>> adequate resources but that authentication might well be needed
>> with the PSTN side of a IP-to-PSTN gateway - maybe this needs
>> to say something like 'users of emergency telecommunications
>> services which require special allocation of network resources
>> must be authenticated'  
>> also there is no reason to think that authentication to one 
>> part of a communications path means authentication to the
>> rest of the path - for example, I have to go through an
>> authentication process to access part of the Harvard network
>> but that authentication is not forwarded to a IP-to-PSTN
>> gateway I might be using, nor would the Harvard authentication 
>> make any sense to the gateway 
   
  3  When networks reach traffic saturation emergency
     communication sessions should be provided with a
     higher probability of completion over non-emergency  
     communications.  We assume the presence of a service level
     agreement to accomplish this latter case. (Note: Sessions
     identified as emergency communication could be processed as
     normal traffic along with all non-emergency traffic when
     sufficient network bandwidth and resources are available.)
>> see above - this is very different within an enterprise, within
>> a single ISP and across the Internet
>> also - I would think that each ISP would decide how
>> to eet any emergency service requirement - in a few cases
>> this could mean prioritizing emergency traffic at the expense
>> of their normal customer traffic but I would expect that
>> would not be the normal case - I doubt that most ISPs
>> will be willing to starve their regular customers, who may be
>> trying to respond to the same emergency, I would expect that
>> it sis far more likely that an ISP will set aside some set
>> amount of network capacity to provide this service on
   
  4  Once an emergency communications session is established,
     the user should be able to complete the session without
     being interrupted or having the quality of the
     communications be degraded excessively.
>> I'm not sure what this means - what happens if the tail
>> circuit gets cut and there is no connectivity - or what 
>> happens if there is too much emergency traffic for the 
>> available resources?


  5  There must exist a mapping association between labels
     defined by various standards bodies.  This mapping will   
     help facilitate inter-working of services in cases where 
     gateways and networks support emergency telecommunications 
     services.
>> does this imply that the function of bridging two PSTN networks
>> over the Internet has to be able to translate between
>> two, potentially incompatible, label types?
>> it would seem to me that this would be a problem for a
>> standards organization that develops a new set of 
>> label set and not of the IP-based technology used to do 
>> bridging - i.e. it is a gateway not a transport problem

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  2 13:24:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10079
	for <ieprep-archive@odin.ietf.org>; Sat, 2 Nov 2002 13:24:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA2IQLo12821
	for ieprep-archive@odin.ietf.org; Sat, 2 Nov 2002 13:26:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2IQLv12818
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 2 Nov 2002 13:26:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09991
	for <ieprep-web-archive@ietf.org>; Sat, 2 Nov 2002 13:23:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2IMGv12598;
	Sat, 2 Nov 2002 13:22:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Jfwv31620
	for <ieprep@optimus.ietf.org>; Fri, 1 Nov 2002 14:41:58 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA00585
	for <ieprep@ietf.org>; Fri, 1 Nov 2002 14:39:22 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 1 Nov 2002 19:36:40 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <V04YAB96>; Fri, 1 Nov 2002 14:41:15 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3CD7@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: Scott Bradner <sob@harvard.edu>
Cc: sean@donelan.com, ieprep@ietf.org, Mpierce1@aol.com, woody@pch.net
Subject: RE: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework
	-02.txt
Date: Fri, 1 Nov 2002 14:41:00 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C281DE.9AED4900"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C281DE.9AED4900
Content-Type: text/plain;
	charset="iso-8859-1"

While still on this QoS topic, is anyone aware of the ITU-T Y.1541 which
defines QoS parameters in the IP networks?

An Nguyen/NCS

 

-----Original Message-----
From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
Sent: Friday, November 01, 2002 2:28 PM
To: Scott Bradner
Cc: sean@donelan.com; ieprep@ietf.org; Mpierce1@aol.com; woody@pch.net
Subject: Re: Congestion avoidance Re: [Ieprep]
draft-ietf-ieprep-framework-02.txt


At the very least, it would be helpful if drafts clearly separate the 
"here and now" from the "it might be nice to have (topic for future 
research)" and "this is unlikely to be feasible in the Internet as-is". 
The danger with requirements and similar work seems to be that this is 
taken as a license to require things that are extremely unlikely to 
happen in a time frame suitable for IETF output.

Since these documents are also meant for people outside the IETF, 
explicitly identifying things that are unlikely to be feasible 
short-term may be valuable.

(I would be curious what concrete QoS routing has been deployed, tested 
and discarded, given that none was ever really standardized in the IETF, 
as far as I can tell. RFC 2386 seems to be the only output of the QOSR 
working group that concluded in early 1999.)

Scott Bradner wrote:

> Henning sez:
>
> >While your view certainly represents the "traditional" Internet view and
> >current operational practice, one should not forget that there has been
> >a large body of more recent research work related to QoS routing.
>
>
> this brings up two questions to me
>
> 1/ how close is that research to being deployed in ISPs?
>
> and more importantally
>
> 2/ should this WG be talking about what the Internet can be expected
>    to be able to do now or in the immediate future (see 1st deliverable
>    in the WG charter) of speculate on what might be possible at some
>    point in the future?
>
> (my feeling, if its not clear, is that we should stick to the world
> of today and the near future)
>
> Scott


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep


------_=_NextPart_000_01C281DE.9AED4900
Content-Type: application/msword;
	name="1a130351.doc"
Content-Disposition: attachment;
	filename="1a130351.doc"
Content-Transfer-Encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAAFAAAANAEAAAAAAAAA
EAAANgEAAAEAAAD+////AAAAADEBAAAyAQAAMwEAAHYBAAAAAgAA////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////s
pcEAayAJBAAA+BK/AAAAAAAAEAAAAAAABAAAwP8AAA4AYmpiah+uH64AAAAAAAAAAAAAAAAAAAAA
AAAJBBYAdRcCAH3EAAB9xAAAlfoAAAAAAAACAQAAAAAAAAAAAAAAAAAAKAAAAAAAAAD//w8AAAAA
AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAGwAAAAAAIYXAAAAAAAAhhcAAIYX
AAAAAAAAhhcAAAAAAADWFwAAAAAAANYXAAAAAAAA1hcAAHQAAAAAAAAAAAAAAEoYAAAAAAAAaIEA
AAAAAABogQAAAAAAAGiBAADIAAAAMIIAAHQAAACkggAAlAMAAEoYAAAAAAAAlNkAAJ4BAABEhgAA
/AEAAECIAABMAAAAjIgAAAAAAACMiAAAAAAAAIyIAAAAAAAAG4oAAKQMAAC/lgAAtAMAAHOaAADc
AQAAzdYAAAIAAADP1gAAAAAAAM/WAAAAAAAAz9YAAC4AAAD91gAADAEAAAnYAAAMAQAAFdkAACQA
AAAy2wAAIAIAAFLdAADCAAAAOdkAABUAAAAAAAAAAAAAAAAAAAAAAAAA1hcAAAAAAABPnAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAD5iQAAIgAAABuKAAAAAAAAT5wAAAAAAABPnAAAAAAAADnZAAAAAAAA
vaYAAAAAAACGFwAAAAAAAIYXAAAAAAAAjIgAAAAAAAAAAAAAAAAAAIyIAABtAQAATtkAABYAAAC9
pgAAAAAAAL2mAAAAAAAAvaYAAAAAAABPnAAA2AcAAIYXAAA4AAAAjIgAAAAAAADWFwAAAAAAAIyI
AAAAAAAAzdYAAAAAAAAAAAAAAAAAAL2mAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAT5wAAAAAAADN1gAAAAAAAL2mAADiBAAAvaYAAAAAAACfqwAA
2gIAADG+AAAMAgAAvhcAABgAAADWFwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAscAAAAAAAACMiAAAAAAAADiGAAAMAAAAQPfJQB1u
wgFKGAAAHmkAAGiBAAAAAAAAJ6QAAFYCAAA9wAAAOgAAAAAAAAAAAAAAscAAABwWAABk2QAAMAAA
AJTZAAAAAAAAd8AAADoAAAAU3gAAAAAAAH2mAABAAAAAFN4AAAAAAACxwAAAAAAAAL2mAAAAAAAA
ShgAAAAAAABKGAAAAAAAAIYXAAAAAAAAhhcAAAAAAACGFwAAAAAAAIYXAAAAAAAAAgDZAAAAVUlU
IC0gU2VjdGV1ciBkZSBsYSBub3JtYWxpc2F0aW9uIGRlcyB06WzpY29tbXVuaWNhdGlvbnMNSVRV
IC0gVGVsZWNvbW11bmljYXRpb24gU3RhbmRhcmRpemF0aW9uIFNlY3Rvcg1VSVQgLSBTZWN0b3Ig
ZGUgTm9ybWFsaXphY2nzbiBkZSBsYXMgVGVsZWNvbXVuaWNhY2lvbmVzDQ1TdHVkeSBQZXJpb2Qg
MjAwMS0yMDA0CQkJCQkJCQlXRCCWIDIgcmV2IDENDQEgIDEzCQEgIEQueHh4DQ1HZW5ldmEsICCW
IE1heSAyMDAyDQkBICBFDVF1ZXN0aW9uKHMpOgk2LzEzDQ1TT1VSQ0UqOglFZGl0b3INDVRJVExF
OglSZXZpc2lvbnMgZm9yIERyYWZ0IE5ldyBSZWNvbW1lbmRhdGlvbiBZLjE1NDEsIE5ldHdvcmsg
UGVyZm9ybWFuY2UgT2JqZWN0aXZlcyBmb3IgSVAtQmFzZWQgU2VydmljZXMgKG5ldyB0aXRsZSkN
X19fX19fX19fX19fX19fX19fXw1BQlNUUkFDVA1UaGlzIGNvbnRyaWJ1dGlvbiBjb250YWlucyB0
aGUgT2N0IDIwMDEgdmVyc2lvbiBvZiBSZWMuIFkuMTU0MS4gIA0NX19fX19fX19fX19fX19fX19f
Xw0MCA0BBw1JTlRFUk5BVElPTkFMICBURUxFQ09NTVVOSUNBVElPTiAgVU5JT04HBw0NDUlUVS1U
B1kuMTU0MQcHVEVMRUNPTU1VTklDQVRJT04LU1RBTkRBUkRJWkFUSU9OICBTRUNUT1ILT0YgIElU
VQcoRHJhZnQgMTAvMDEpICAgBwcNDQ0NDVNFUklFUyBZOiBHTE9CQUwgSU5GT1JNQVRJT04gSU5G
UkFTVFJVQ1RVUkUNDQ0NTmV0d29yayBQZXJmb3JtYW5jZSBPYmplY3RpdmVzIGZvciBJUC1CYXNl
ZCBTZXJ2aWNlcyANDURyYWZ0IElUVS1UICBSZWNvbW1lbmRhdGlvbiAgWS4xNTQxDShQcmV2aW91
c2x5ICBDQ0lUVCAgUmVjb21tZW5kYXRpb24pDUVkaXRvcpJzIE5vdGU6IEFsbCBmcm9udCBtYXR0
ZXIgKHRpdGxlIHBhZ2UsIGV0Yy4pIHRvIGJlIGVkaXRlZCBieSB0aGUgVFNCLg0MSVRVLVQgIFJF
Q09NTUVOREFUSU9OICBZLjE1NDENDU5ldHdvcmsgUGVyZm9ybWFuY2UgT2JqZWN0aXZlcyBmb3Ig
SVAtQmFzZWQgU2VydmljZXMHB1N1bW1hcnkNVGhpcyBSZWNvbW1lbmRhdGlvbiBkZWZpbmVzIGNs
YXNzZXMgb2YgbmV0d29yayBRdWFsaXR5IG9mIFNlcnZpY2UgKFFvUyksIGFuZCBzcGVjaWZpZXMg
cHJvdmlzaW9uYWwgb2JqZWN0aXZlcyBmb3IgSW50ZXJuZXQgUHJvdG9jb2wgbmV0d29yayBwZXJm
b3JtYW5jZSBwYXJhbWV0ZXJzLiBUaGVzZSBjbGFzc2VzIGFyZSBpbnRlbmRlZCB0byBiZSB0aGUg
YmFzaXMgZm9yIGFncmVlbWVudHMgYW1vbmcgbmV0d29yayBwcm92aWRlcnMsIGFuZCBiZXR3ZWVu
IGVuZCB1c2VycyBhbmQgdGhlaXIgbmV0d29yayBwcm92aWRlcnMuIA1BcHBlbmRpeCBJIHByb3Zp
ZGVzIGluZm9ybWF0aW9uIGFib3V0IGhvdyBBVE0gbWlnaHQgc3VwcG9ydCBvZiBJUCBsYXllciBw
ZXJmb3JtYW5jZS4gQXBwZW5kaXggSUkgZGlzY3Vzc2VzIGFsdGVybmF0aXZlcyBmb3IgZGVmaW5p
bmcgSVAgZGVsYXkgdmFyaWF0aW9uLiBUaGUgbWF0ZXJpYWwgaW4gQXBwZW5kaXggSUkgd2lsbCBl
dmVudHVhbGx5IGJlIGluY29ycG9yYXRlZCBpbnRvIFJlY29tbWVuZGF0aW9uIFkuMTU0MC4gQXBw
ZW5kaXggSUlJIHByZXNlbnRzIHRoZSBIeXBvdGhldGljYWwgUmVmZXJlbmNlIFBhdGhzIGFnYWlu
c3Qgd2hpY2ggdGhlIFkuMTU0MSBRb1Mgb2JqZWN0aXZlcyB3ZXJlIHRlc3RlZCBmb3IgZmVhc2li
aWxpdHkuICBBcHBlbmRpeCBJViBnaXZlcyBleGFtcGxlIGNvbXB1dGF0aW9ucyBvZiBJUERWLiBB
cHBlbmRpeCBWIGRpc2N1c3NlcyBpc3N1ZXMgdGhhdCBtdXN0IGJlIGNvbnNpZGVyZWQgd2hlbmV2
ZXIgSVAgbWVhc3VyZW1lbnRzIGFyZSBtYWRlLiBBcHBlbmRpeCBWSSBkZXNjcmliZXMgdGhlIHJl
bGF0aW9uc2hpcCBiZXR3ZWVuIHRoaXMgUmVjb21tZW5kYXRpb24gYW5kIHRoZSBJRVRGIGRlZmlu
ZWQgbWVjaGFuaXNtcyBmb3IgbWFuYWdpbmcgUW9TLiBBcHBlbmRpeCBWSUkgZGlzY3Vzc2VzIHRo
ZSBJUFREIG9iamVjdGl2ZSBhbmQgaG93IGl0IHJlbGF0ZXMgdG8gb3RoZXIgUmVjb21tZW5kYXRp
b25zLiBBcHBlbmRpeCBWSUlJIHByZXNlbnRzIGEgQmlibGlvZ3JhcGh5LiBBcHBlbmRpeCBJWCBk
aXNjdXNzZXMgcG90ZW50aWFsIGFwcGxpY2F0aW9ucyBvZiAgSVAgTmV0d29ya3MuBwdTb3VyY2UN
SVRVLVQgUmVjb21tZW5kYXRpb24gWS4xNTQxIGlzIGN1cnJlbnRseSBiZWluZyBkcmFmdGVkIGJ5
IElUVS1UIFN0dWR5IEdyb3VwIDEzLgcHDQxDT05URU5UUw0TIFRPQyBcbyAiMS0zIiAUMQlTY29w
ZQkTIFBBR0VSRUYgX1RvYzQ3Njc3ODk2MyBcaCABFDEVDTIJUmVmZXJlbmNlcwkTIFBBR0VSRUYg
X1RvYzQ3Njc3ODk2NCBcaCABFDEVDTMJQWJicmV2aWF0aW9ucwkTIFBBR0VSRUYgX1RvYzQ3Njc3
ODk2NSBcaCABFDIVDTQJTmV0d29yayBwZXJmb3JtYW5jZSB3aGVuIHNvbWUgcGFja2V0cyBhcmUg
bm9uLWNvbmZvcm1pbmcJEyBQQUdFUkVGIF9Ub2M0NzY3Nzg5NjYgXGggARQzFQ01CU5ldHdvcmsg
cGVyZm9ybWFuY2Ugb2JqZWN0aXZlcwkTIFBBR0VSRUYgX1RvYzQ3Njc3ODk2NyBcaCABFDQVDTUu
MSBHZW5lcmFsIGRpc2N1c3Npb24gb2YgUW9TCRMgUEFHRVJFRiBfVG9jNDc2Nzc4OTY4IFxoIAEU
NBUNNS4yCVFvUyBjbGFzc2VzCRMgUEFHRVJFRiBfVG9jNDc2Nzc4OTY5IFxoIAEUNBUNNS4yLjEJ
TmF0dXJlIG9mIHRoZSBuZXR3b3JrIHBlcmZvcm1hbmNlIG9iamVjdGl2ZXMJEyBQQUdFUkVGIF9U
b2M0NzY3Nzg5NzAgXGggARQ1FQ01LjIuMglVbmJvdW5kZWQgKHVuc3BlY2lmaWVkKSBwZXJmb3Jt
YW5jZQkTIFBBR0VSRUYgX1RvYzQ3Njc3ODk3MSBcaCABFDYVDTYJQXZhaWxhYmlsaXR5IG9iamVj
dGl2ZXMJEyBQQUdFUkVGIF9Ub2M0NzY3Nzg5NzIgXGggARQ5FQ03CUFsbG9jYXRpb24gb2YgdGhl
IHBlcmZvcm1hbmNlIG9iamVjdGl2ZXMJEyBQQUdFUkVGIF9Ub2M0NzY3Nzg5NzMgXGggARQxMBUN
Ny4xCUdlbmVyYWwgY29uc2lkZXJhdGlvbnMgZm9yIGFsbG9jYXRpb24gcnVsZXMJEyBQQUdFUkVG
IF9Ub2M0NzY3Nzg5NzQgXGggFEVycm9yISBCb29rbWFyayBub3QgZGVmaW5lZC4VDTcuMglSb3V0
ZSBsZW5ndGggY2FsY3VsYXRpb24JEyBQQUdFUkVGIF9Ub2M0NzY3Nzg5NzUgXGggFEVycm9yISBC
b29rbWFyayBub3QgZGVmaW5lZC4VDRVBcHBlbmRpeCBJCUFUTSBuZXR3b3JrIFFvUyBzdXBwb3J0
IG9mIElQIFFvUwk4DUFwcGVuZGl4IElJCUlQIERlbGF5IFZhcmlhdGlvbiBwYXJhbWV0ZXIgZGVm
aW5pdGlvbiBjb25zaWRlcmF0aW9ucwk5DUFwcGVuZGl4IElJSQlIeXBvdGhldGljYWwgUmVmZXJl
bmNlIFBhdGhzIGZvciB2YWxpZGF0aW5nIHRoZSBJUCBwZXJmb3JtYW5jZSBvYmplY3RpdmVzCTEw
DUFwcGVuZGl4IElWCU1hdGVyaWFsIHJlbGV2YW50IHRvIElQIHBlcmZvcm1hbmNlIG1lYXN1cmVt
ZW50IG1ldGhvZHMJMTYNQXBwZW5kaXggVglBcHBsaWNhYmlsaXR5IG9mIHRoZSBJRVRGIEludGVn
cmF0ZWQgU2VydmljZXMgYW5kIERpZmZlcmVudGlhdGVkIFNlcnZpY2VzIHRvIElQIFFvUyBjbGFz
c2VzCTE3DUFwcGVuZGl4IFZJCVJlbGF0aW9uc2hpcHMgYW1vbmcgdHJhbnNpdCBkZWxheSBvYmpl
Y3RpdmVzCTE4DUFwcGVuZGl4IFZJSQlCaWxpb2dyYXBoeQkxOQ0NDAxSZWNvbW1lbmRhdGlvbiBZ
LjE1NDENTmV0d29yayBQZXJmb3JtYW5jZSBPYmplY3RpdmVzIGZvciBJUC1CYXNlZCBTZXJ2aWNl
cw1TY29wZQ1UaGlzIFJlY29tbWVuZGF0aW9uIHNwZWNpZmllcyBJUCBwZXJmb3JtYW5jZSB2YWx1
ZXMgdG8gYmUgYWNoaWV2ZWQgaW50ZXJuYXRpb25hbGx5IGZvciBlYWNoIG9mIHRoZSBwZXJmb3Jt
YW5jZSBwYXJhbWV0ZXJzIGRlZmluZWQgaW4gSVRVLVQgUmVjb21tZW5kYXRpb24gWS4xNTQwLiBT
b21lIG9mIHRoZXNlIHZhbHVlcyBkZXBlbmQgb24gd2hpY2ggUXVhbGl0eSBvZiBTZXJ2aWNlIChR
b1MpIGNsYXNzIHRoZSBlbmQedXNlcnMgYW5kIG5ldHdvcmsgcHJvdmlkZXJzIGFncmVlIG9uLiBU
aGlzIFJlY29tbWVuZGF0aW9uIGRlZmluZXMgc2l4IGRpZmZlcmVudCBRb1MgY2xhc3Nlcy4gVGhp
cyBSZWNvbW1lbmRhdGlvbiBhcHBsaWVzIHRvIGludGVybmF0aW9uYWwgZW5kLXRvLWVuZCBJUCBu
ZXR3b3JrIHBhdGhzLiBUaGUgUW9TIGNsYXNzZXMgZGVmaW5lZCBoZXJlIGFyZSBpbnRlbmRlZCB0
byBiZSB0aGUgYmFzaXMgb2YgYWdyZWVtZW50cyBiZXR3ZWVuIGVuZC11c2VycyBhbmQgbmV0d29y
ayBzZXJ2aWNlIHByb3ZpZGVycywgYW5kIGJldHdlZW4gc2VydmljZSBwcm92aWRlcnMuIFRoZSBj
bGFzc2VzIHNob3VsZCBjb250aW51ZSB0byBiZSB1c2VkIHdoZW4gc3RhdGljIGFncmVlbWVudHMg
Z2l2ZSB3YXkgdG8gZHluYW1pYyByZXF1ZXN0cyBzdXBwb3J0ZWQgYnkgUW9TIHNwZWNpZmljYXRp
b24gcHJvdG9jb2xzLiBUaGUgbGltaXRlZCBudW1iZXIgb2YgUW9TIGNsYXNzZXMgZGVmaW5lZCBo
ZXJlIHN1cHBvcnQgYSB3aWRlIHJhbmdlIG9mIGFwcGxpY2F0aW9ucywgaW5jbHVkaW5nIHRoZSBm
b2xsb3dpbmc6IHBvaW50LXRvLXBvaW50IHRlbGVwaG9ueSwgbXVsdGltZWRpYSBjb25mZXJlbmNp
bmcsIGFuZCBpbnRlcmFjdGl2ZSBkYXRhIHRyYW5zZmVyLiBXaGlsZSB0aGUgcGVyZm9ybWFuY2Ug
bmVlZHMgb2YgdGhlc2UgYXBwbGljYXRpb25zIGFyZSBtb3JlIGRlbWFuZGluZyB0aGFuIG1vc3Qs
IHRoZXJlIG1heSBiZSBvdGhlciBhcHBsaWNhdGlvbnMgdGhhdCByZXF1aXJlIG5ldyBvciByZXZp
c2VkIGNsYXNzZXMuIEFueSBkZXNpcmUgZm9yIG5ldyBjbGFzc2VzIG11c3QgYmUgYmFsYW5jZWQg
d2l0aCB0aGUgcmVxdWlyZW1lbnQgb2YgZmVhc2libGUgaW1wbGVtZW50YXRpb24sIGFuZCB0aGUg
bnVtYmVyIG9mIGNsYXNzZXMgbXVzdCBiZSBzbWFsbCBmb3IgaW1wbGVtZW50YXRpb25zIHRvIHNj
YWxlIGluIGdsb2JhbCBuZXR3b3Jrcy4NVGhlIFFvUyBvYmplY3RpdmVzIGFyZSBhcHBsaWNhYmxl
IHdoZW4gYWNjZXNzIGxpbmsgc3BlZWRzIGFyZSBhdCB0aGUgVDEgb3IgRTEgcmF0ZSBhbmQgaGln
aGVyLg1OT1RFoDGglqBUaGlzIFJlY29tbWVuZGF0aW9uIHV0aWxpc2VzIHBhcmFtZXRlcnMgZGVm
aW5lZCBpbiBSZWNvbW1lbmRhdGlvbiBZLjE1NDAgKGZvcm1lcmx5IEkuMzgwKSB0aGF0IGNhbiBi
ZSB1c2VkIHRvIGNoYXJhY3RlcmlzZSBJUCBzZXJ2aWNlIHByb3ZpZGVkIHVzaW5nIElQdjQ7IGFw
cGxpY2FiaWxpdHkgb3IgZXh0ZW5zaW9uIHRvIG90aGVyIHByb3RvY29scyAoZS5nLiBJUHY2KSBp
cyBmb3IgZnVydGhlciBzdHVkeS4NUmVmZXJlbmNlcw1UaGUgZm9sbG93aW5nIHJlZmVyZW5jZXMg
YW5kIElUVS1UIFJlY29tbWVuZGF0aW9ucyBjb250YWluIHByb3Zpc2lvbnMgd2hpY2gsIHRocm91
Z2ggcmVmZXJlbmNlIGluIHRoaXMgdGV4dCwgY29uc3RpdHV0ZSBwcm92aXNpb25zIG9mIHRoaXMg
UmVjb21tZW5kYXRpb24uIEFsbCBSZWNvbW1lbmRhdGlvbnMgYW5kIG90aGVyIHJlZmVyZW5jZXMg
YXJlIHN1YmplY3QgdG8gcmV2aXNpb247IGFsbCB1c2VycyBvZiB0aGlzIFJlY29tbWVuZGF0aW9u
IGFyZSB0aGVyZWZvcmUgZW5jb3VyYWdlZCB0byBpbnZlc3RpZ2F0ZSB0aGUgcG9zc2liaWxpdHkg
b2YgYXBwbHlpbmcgdGhlIG1vc3QgcmVjZW50IGVkaXRpb24gb2YgdGhlIFJlY29tbWVuZGF0aW9u
cyBsaXN0ZWQgYmVsb3cuIEEgbGlzdCBvZiB0aGUgY3VycmVudGx5IHZhbGlkIElUVS1UIFJlY29t
bWVuZGF0aW9ucyBpcyByZWd1bGFybHkgcHVibGlzaGVkLg1bMV0JSVRVHlQgUmVjb21tZW5kYXRp
b24gRy4xMTQsIE9uZS13YXkgdHJhbnNtaXNzaW9uIHRpbWUuDVsyXQlJVFUeVCBSZWNvbW1lbmRh
dGlvbiBHLjEwOSwgRGVmaW5pdGlvbiBvZiBjYXRlZ29yaWVzIG9mIHNwZWVjaCB0cmFuc21pc3Np
b24gcXVhbGl0eS4uDVszXQlJVFUeVCBSZWNvbW1lbmRhdGlvbiBHLjgyNiwgRXJyb3IgcGVyZm9y
bWFuY2UgcGFyYW1ldGVycyBhbmQgb2JqZWN0aXZlcyBmb3IgaW50ZXJuYXRpb25hbCwgY29uc3Rh
bnQgYml0IHJhdGUgZGlnaXRhbCBwYXRocyBhdCBvciBhYm92ZSB0aGUgcHJpbWFyeSByYXRlLg1b
NF0JSVRVHlQgUmVjb21tZW5kYXRpb24gSS4xMTMsIFZvY2FidWxhcnkgb2YgdGVybXMgZm9yIGJy
b2FkYmFuZCBhc3BlY3RzIG9mIElTRE4uIA1bNV0JSVRVHlQgUmVjb21tZW5kYXRpb24gSS4zNTAs
IEdlbmVyYWwgYXNwZWN0cyBvZiBxdWFsaXR5IG9mIHNlcnZpY2UgYW5kIG5ldHdvcmsgcGVyZm9y
bWFuY2UgaW4gZGlnaXRhbCBuZXR3b3JrcywgaW5jbHVkaW5nIElTRE5zLg1bNl0JSVRVLVQgUmVj
b21tZW5kYXRpb24gWS4xNTQwLCBJbnRlcm5ldCBQcm90b2NvbCBEYXRhIENvbW11bmljYXRpb24g
U2VydmljZSCWIElQIFBhY2tldCBUcmFuc2ZlciBhbmQgQXZhaWxhYmlsaXR5IFBlcmZvcm1hbmNl
IFBhcmFtZXRlcnMgDVs3XQlSRkMgNzkxIChTVEQtNSkgLSBJbnRlcm5ldCBQcm90b2NvbCAoSVAp
LCBEQVJQQSBJbnRlcm5ldCBwcm9ncmFtIHByb3RvY29sIHNwZWNpZmljYXRpb24sIFNlcHRlbWJl
ciAxOTgxLg1bOF0JSVRVLVQgUmVjb21tZW5kYXRpb24gWS4xMjMxLCBJbnRlcm5ldCBwcm90b2Nv
bCBhc3BlY3RzIJYgQXJjaGl0ZWN0dXJlLCBhY2Nlc3MsIG5ldHdvcmsgY2FwYWJpbGl0aWVzIGFu
ZCByZXNvdXJjZSBtYW5hZ2VtZW50LCBJUCBBY2Nlc3MgTmV0d29yayBBcmNoaXRlY3R1cmUsIDIw
MDEuDVs5XQlJVFUtVCBSZWNvbW1lbmRhdGlvbiBFLjY1MSwgUmVmZXJlbmNlIENvbm5lY3Rpb25z
IGZvciBUcmFmZmljIEVuZ2luZWVyaW5nIG9mIElQIEFjY2VzcyBOZXR3b3JrcywgDQ1BYmJyZXZp
YXRpb25zDVRoaXMgUmVjb21tZW5kYXRpb24gdXNlcyB0aGUgZm9sbG93aW5nIGFiYnJldmlhdGlv
bnM6DUFUTQlhc3luY2hyb25vdXMgdHJhbnNmZXIgbW9kZQ1BRglhc3N1cmVkIGZvcndhcmRpbmcN
Q0JSCWNvbnN0YW50IGJpdCByYXRlDUNEVgljZWxsIGRlbGF5IHZhcmlhdGlvbg1DRVIJY2VsbCBl
cnJvciByYXRpbw1DTFIJY2VsbCBsb3NzIHJhdGlvDUNTCWNpcmN1aXQgc2VjdGlvbiANRFMJZGlm
ZmVyZW50aWF0ZWQgc2VydmljZXMNRFNUCWRlc3RpbmF0aW9uIGhvc3QNRTEJRGlnaXRhbCBIaWVy
YXJjaHkgVHJhbnNtaXNzaW9uIGF0IDIuMDQ4IE1icHMNRTMJRGlnaXRhbCBIaWVyYXJjaHkgVHJh
bnNtaXNzaW9uIGF0IDM0IE1icHMNRUYJZXhwZWRpdGVkIGZvcndhcmRpbmcNRklGTwlmaXJzdC1p
biwgZmlyc3Qtb3V0DUZUUAlmaWxlIHRyYW5zZmVyIHByb3RvY29sDUdXCWdhdGV3YXkgcm91dGVy
DUhSRQloeXBvdGhldGljYWwgcmVmZXJlbmNlIGVuZHBvaW50DUhSUAloeXBvdGhldGljYWwgcmVm
ZXJlbmNlIHBhdGgNSFRUUAloeXBlcnRleHQgdHJhbnNmZXIgcHJvdG9jb2wNSUVURglJbnRlcm5l
dCBFbmdpbmVlcmluZyBUYXNrIEZvcmNlDUlQCUludGVybmV0IHByb3RvY29sDUlQRFYJSVAgcGFj
a2V0IGRlbGF5IHZhcmlhdGlvbg1JUEVSCUlQIHBhY2tldCBlcnJvciByYXRpbw1JUExSCUlQIHBh
Y2tldCBsb3NzIHJhdGlvDUlQUkUJSVAgcGFja2V0IHRyYW5zZmVyIHJlZmVyZW5jZSBldmVudA1J
UE9UCW9jdGV0IGJhc2VkIElQIHBhY2tldCB0aHJvdWdocHV0DUlQUFQJSVAgcGFja2V0IHRocm91
Z2hwdXQNSVBURAlJUCBwYWNrZXQgdHJhbnNmZXIgZGVsYXkNSVNQCUludGVybmV0IHNlcnZpY2Ug
cHJvdmlkZXINSVRVLVQJSW50ZXJuYXRpb25hbCBUZWxlY29tbXVuaWNhdGlvbiBVbmlvbiAtIFRl
bGVjb21tdW5pY2F0aW9uIFN0YW5kYXJkaXphdGlvbiBTZWN0b3INTEwJbG93ZXIgbGF5ZXJzLCBw
cm90b2NvbHMgYW5kIHRlY2hub2xvZ3kgc3VwcG9ydGluZyB0aGUgSVAgbGF5ZXINTWF2CXRoZSBt
aW5pbXVtIG51bWJlciBvZiBwYWNrZXRzIHJlY29tbWVuZGVkIGZvciBhc3Nlc3NpbmcgdGhlIGF2
YWlsYWJpbGl0eSBzdGF0ZQ1NUAltZWFzdXJlbWVudCBwb2ludA1NUExTCW11bHRpLXByb3RvY29s
IGxhYmVsIHN3aXRjaGluZw1NVEJJU08JbWVhbiB0aW1lIGJldHdlZW4gSVAgc2VydmljZSBvdXRh
Z2VzDU1UVElTUgltZWFuIHRpbWUgdG8gSVAgc2VydmljZSByZXN0b3JhbA1OCXRoZSBudW1iZXIg
b2YgcGFja2V0cyBpbiBhIHRocm91Z2hwdXQgcHJvYmUgb2Ygc2l6ZSBODU5JCW5ldHdvcmsgaW50
ZXJmYWNlDU5TCW5ldHdvcmsgc2VjdGlvbg1OU0UJbmV0d29yayBzZWN0aW9uIGVuc2VtYmxlDU5T
UAluZXR3b3JrIHNlcnZpY2UgcHJvdmlkZXINT1NQRglvcGVuIHNob3J0ZXN0IHBhdGggZmlyc3QN
UERCCXBlciBkb21haW4gYmVoYXZpb3IgDVBESAlwbGVzaW9zeW5jaHJvbm91cyBkaWdpdGFsIGhp
ZXJhcmNoeQ1QSEIJcGVyIGhvcCBiZWhhdmlvciANUElBCXBlcmNlbnQgSVAgc2VydmljZSBhdmFp
bGFiaWxpdHkNUElVCXBlcmNlbnQgSVAgc2VydmljZSB1bmF2YWlsYWJpbGl0eQ1wa3QJSVAgZGF0
YWdyYW0gKElQIHBhY2tldCkNUW9TCXF1YWxpdHkgb2Ygc2VydmljZQ1SCXJvdXRlcg1SRkMJUmVx
dWVzdCBmb3IgQ29tbWVudA1SU1ZQCXJlc291cmNlIHJlc2VydmF0aW9uIHByb3RvY29sDVJUUAly
ZWFsLXRpbWUgdHJhbnNwb3J0IHByb3RvY29sDVNESAlzeW5jaHJvbm91cyBkaWdpdGFsIGhpZXJh
cmNoeQ1TUFIJc3B1cmlvdXMgcGFja2V0IHJhdGlvDVNSQwlzb3VyY2UgaG9zdA1TVEQJc3RhbmRh
cmQNVDEJRGlnaXRhbCBIaWVyYXJjaHkgVHJhbnNtaXNzaW9uIGF0IDEuNTQ0IE1icHMNVDMJRGln
aXRhbCBIaWVyYXJjaHkgVHJhbnNtaXNzaW9uIGF0IDQ1IE1icHMNVG1heAltYXhpbXVtIElQIHBh
Y2tldCBkZWxheSBiZXlvbmQgd2hpY2ggdGhlIHBhY2tldCBpcyBkZWNsYXJlZCB0byBiZSBsb3N0
DVRhdgltaW5pbXVtIGxlbmd0aCBvZiB0aW1lIG9mIElQIGF2YWlsYWJpbGl0eTsgbWluaW11bSBs
ZW5ndGggb2YgdGltZSBvZiBJUCB1bmF2YWlsYWJpbGl0eQ1UQkQJdG8gYmUgZGV0ZXJtaW5lZA1U
Q1AJdHJhbnNtaXNzaW9uIGNvbnRyb2wgcHJvdG9jb2wNVERNQQl0aW1lIGRpdmlzaW9uIG11bHRp
cGxlIGFjY2Vzcw1UT1MJdHlwZSBvZiBzZXJ2aWNlDVRUTAl0aW1lIHRvIGxpdmUNVURQCXVzZXIg
ZGF0YWdyYW0gcHJvdG9jb2wNVlRDCXZpZGVvIHRlbGVjb25mZXJlbmNlDQ1UcmFuc2ZlciBDYXBh
Y2l0eSwgQ2FwYWNpdHkgQWdyZWVtZW50cywgYW5kIHRoZSBBcHBsaWNhYmlsaXR5IG9mIFFvUyBD
bGFzc2VzIA1UaGlzIGNsYXVzZSBhZGRyZXNzZXMgdGhlIHRvcGljIG9mIG5ldHdvcmsgdHJhbnNm
ZXIgY2FwYWNpdHkgKHRoZSBlZmZlY3RpdmUgYml0IHJhdGUgZGVsaXZlcmVkIHRvIGEgZmxvdyBv
dmVyIGEgdGltZSBpbnRlcnZhbCksIGFuZCBpdHMgcmVsYXRpb25zaGlwIHRvIHRoZSBwYWNrZXQg
dHJhbnNmZXIgUXVhbGl0eSBvZiBTZXJ2aWNlIChRb1MpIHBhcmFtZXRlcnMgZGVmaW5lZCBpbiBS
ZWNvbW1lbmRhdGlvbiBZLjE1NDAsIGFuZCBvYmplY3RpdmVzIHNwZWNpZmllZCBoZXJlLg1UcmFu
c2ZlciBDYXBhY2l0eSBpcyBhIGZ1bmRhbWVudGFsIFFvUyBwYXJhbWV0ZXIgaGF2aW5nIHByaW1h
cnkgaW5mbHVlbmNlIG92ZXIgdGhlIHBlcmZvcm1hbmNlIHBlcmNlaXZlZCBieSBlbmQtdXNlcnMu
IE1hbnkgdXNlciBhcHBsaWNhdGlvbnMgaGF2ZSBtaW5pbXVtIGNhcGFjaXR5IHJlcXVpcmVtZW50
czsgdGhlc2UgcmVxdWlyZW1lbnRzIHNob3VsZCBiZSBjb25zaWRlcmVkIHdoZW4gZW50ZXJpbmcg
aW50byBzZXJ2aWNlIGFncmVlbWVudHMuIFJlY29tbWVuZGF0aW9uIFkuMTU0MCBkb2VzIG5vdCBk
ZWZpbmUgYSBwYXJhbWV0ZXIgZm9yIGNhcGFjaXR5LCBob3dldmVyIGl0IGRvZXMgZGVmaW5lIHRo
ZSBQYWNrZXQgTG9zcyBwYXJhbWV0ZXIuIExvc3QgYml0cyBvciBvY3RldHMgY2FuIGJlIHN1YnRy
YWN0ZWQgZnJvbSB0aGUgdG90YWwgc2VudCB0byBkZXRlcm1pbmUgbmV0d29yayBjYXBhY2l0eS4g
QW4gaW5kZXBlbmRlbnQgZGVmaW5pdGlvbiBvZiBjYXBhY2l0eSBpcyBmb3IgZnVydGhlciBzdHVk
eS4NSXQgaXMgYXNzdW1lZCB0aGF0IHRoZSB1c2VyIGFuZCBuZXR3b3JrIHByb3ZpZGVyIGhhdmUg
YWdyZWVkIG9uIHRoZSBtYXhpbXVtIGNhcGFjaXR5IHRoYXQgd2lsbCBiZSBhdmFpbGFibGUgdG8g
b25lIG9yIG1vcmUgcGFja2V0IGZsb3dzIGluIGEgc3BlY2lmaWMgUW9TIGNsYXNzLiBBIHBhY2tl
dCBmbG93IGlzIHRoZSB0cmFmZmljIGFzc29jaWF0ZWQgd2l0aCBhIGdpdmVuIGNvbm5lY3Rpb24g
b3IgY29ubmVjdGlvbmxlc3Mgc3RyZWFtIGhhdmluZyB0aGUgc2FtZSBzb3VyY2UgaG9zdCAoU1JD
KSwgZGVzdGluYXRpb24gaG9zdCAoRFNUKSwgY2xhc3Mgb2Ygc2VydmljZSwgYW5kIHNlc3Npb24g
aWRlbnRpZmljYXRpb24uIE90aGVyIGRvY3VtZW50cyBtYXkgdXNlIHRoZSB0ZXJtcyBtaWNyb2Zs
b3cgb3Igc3ViLWZsb3cgIHdoZW4gcmVmZXJyaW5nIHRvIHRyYWZmaWMgc3RyZWFtcyB3aXRoIHRo
aXMgZGVncmVlIG9mIGNsYXNzaWZpY2F0aW9uLiBJbml0aWFsbHksIHRoZSBhZ3JlZWluZyBwYXJ0
aWVzIG1heSB1c2Ugd2hhdGV2ZXIgY2FwYWNpdHkgc3BlY2lmaWNhdGlvbnMgdGhleSBjb25zaWRl
ciBhcHByb3ByaWF0ZSwgc28gbG9uZyBhcyB0aGV5IGFsbG93IGJvdGggZW5mb3JjZW1lbnQgYW5k
IHZlcmlmaWNhdGlvbi4gRm9yIGV4YW1wbGUsIHBlYWsgYml0IHJhdGUgKGluY2x1ZGluZyBsb3dl
ciBsYXllciBvdmVyaGVhZCkgbWF5IGJlIHN1ZmZpY2llbnQuIFRoZSBuZXR3b3JrIHByb3ZpZGVy
IGFncmVlcyB0byB0cmFuc2ZlciBwYWNrZXRzIGF0IHRoZSBzcGVjaWZpZWQgY2FwYWNpdHkgaW4g
YWNjb3JkYW5jZSB3aXRoIHRoZSBhZ3JlZWQgUW9TIGNsYXNzLg1XaGVuIHRoZSBwcm90b2NvbHMg
YW5kIHN5c3RlbXMgdGhhdCBzdXBwb3J0IGR5bmFtaWMgcmVxdWVzdHMgYXJlIGF2YWlsYWJsZSwg
dGhlIHVzZXIgd2lsbCBuZWdvdGlhdGUgYSB0cmFmZmljIGNvbnRyYWN0LiBTdWNoIGEgY29udHJh
Y3Qgc3BlY2lmaWVzIG9uZSBvciBzZXZlcmFsIHRyYWZmaWMgcGFyYW1ldGVycyAoc3VjaCBhcyB0
aG9zZSBkZWZpbmVkIGluIFJlYy4gWS5pcHRjLCBvciBSU1ZQKSBhbmQgdGhlIFFvUyBjbGFzcywg
YW5kIGFwcGxpZXMgdG8gYSBzcGVjaWZpYyBmbG93LiAgDVRoZSBuZXR3b3JrIHBlcmZvcm1hbmNl
IG9iamVjdGl2ZXMgbWF5IG5vIGxvbmdlciBiZSBhcHBsaWNhYmxlIHdoZW4gdGhlcmUgYXJlIHBh
Y2tldHMgc3VibWl0dGVkIGluIGV4Y2VzcyBvZiB0aGUgY2FwYWNpdHkgYWdyZWVtZW50IG9yIHRo
ZSBuZWdvdGlhdGVkIHRyYWZmaWMgY29udHJhY3QuIElmIGV4Y2VzcyBwYWNrZXRzIGFyZSBvYnNl
cnZlZCwgdGhlIG5ldHdvcmsgaXMgYWxsb3dlZCB0byBkaXNjYXJkIGEgbnVtYmVyIG9mIHBhY2tl
dHMgZXF1YWwgdG8gdGhlIG51bWJlciBvZiBleGNlc3MgcGFja2V0cy4gU3VjaCBkaXNjYXJkZWQg
cGFja2V0cyBhcmUgbm90IGNvdW50ZWQgYXMgbG9zdCBwYWNrZXRzIGluIGFzc2Vzc2luZyB0aGUg
bmV0d29yaydzIElQTFIgcGVyZm9ybWFuY2UuIA1JdCBpcyBhIG5ldHdvcmsgcHJpdmlsZWdlIHRv
IGRlZmluZSBpdHMgcmVzcG9uc2UgdG8gZmxvd3Mgd2l0aCBleGNlc3MgcGFja2V0cywgcG9zc2li
bHkgYmFzZWQgb24gdGhlIG51bWJlciBvZiBleGNlc3MgcGFja2V0cyBvYnNlcnZlZC4gV2hlbiBh
IGZsb3cgaW5jbHVkZXMgZXhjZXNzIHBhY2tldHMsIG5vIG5ldHdvcmsgcGVyZm9ybWFuY2UgY29t
bWl0bWVudHMgbmVlZCBiZSBob25vdXJlZC4gSG93ZXZlciwgdGhlIG5ldHdvcmsgbWF5IG9mZmVy
IG1vZGlmaWVkIG5ldHdvcmsgcGVyZm9ybWFuY2UgY29tbWl0bWVudHMuDQ1OZXR3b3JrIHBlcmZv
cm1hbmNlIG9iamVjdGl2ZXMNVGhpcyBjbGF1c2UgZGlzY3Vzc2VzIG9iamVjdGl2ZXMgZm9yIHRo
ZSB1c2VyIGluZm9ybWF0aW9uIHRyYW5zZmVyIHBlcmZvcm1hbmNlIG9mIHB1YmxpYyBJUCBzZXJ2
aWNlcy4gVGhlc2Ugb2JqZWN0aXZlcyBhcmUgc3RhdGVkIGluIHRlcm1zIG9mIHRoZSBJUCBsYXll
ciBwZXJmb3JtYW5jZSBwYXJhbWV0ZXJzIGRlZmluZWQgaW4gSVRVLVQgUmVjb21tZW5kYXRpb24g
WS4xNTQwLiBBIHN1bW1hcnkgb2YgdGhlIG9iamVjdGl2ZXMgY2FuIGJlIGZvdW5kIGluIFRhYmxl
IDEgdG9nZXRoZXIgd2l0aCBpdHMgYXNzb2NpYXRlZCBnZW5lcmFsIG5vdGVzLiBBbGwgdmFsdWVz
IGluIFRhYmxlIDEgYXJlIHByb3Zpc2lvbmFsIGFuZCB0aGV5IG5lZWQgbm90IGJlIG1ldCB1bnRp
bCB0aGV5IGFyZSByZXZpc2VkICh1cCBvciBkb3duKSBiYXNlZCBvbiByZWFsIG9wZXJhdGlvbmFs
IGV4cGVyaWVuY2UuDRMgRU1CRUQgRXF1YXRpb24uMyAgFAEVR2VuZXJhbCBkaXNjdXNzaW9uIG9m
IFFvUw1UaGUgUW9TIGNsYXNzIGRlZmluaXRpb25zIGluIFRhYmxloDEgcHJlc2VudCBib3VuZHMg
b24gdGhlIGVuZC10by1lbmQgbmV0d29yayBwZXJmb3JtYW5jZS4gQXMgbG9uZyBhcyB0aGUgdXNl
cnMgKGFuZCBpbmRpdmlkdWFsIG5ldHdvcmtzKSBkbyBub3QgZXhjZWVkIHRoZSBhZ3JlZWQgY2Fw
YWNpdHkgc3BlY2lmaWNhdGlvbiBvciB0cmFmZmljIGNvbnRyYWN0LCBhbmQgYSBwYXRoIGlzIGF2
YWlsYWJsZSAoYXMgZGVmaW5lZCBpbiBZLjE1NDApLCBuZXR3b3JrIHByb3ZpZGVycyBzaG91bGQg
Y29sbGFib3JhdGl2ZWx5IHN1cHBvcnQgdGhlc2UgZW5kLXRvLWVuZCBib3VuZHMgZm9yIHRoZSBs
aWZldGltZSBvZiB0aGUgZmxvdy4NVGhlIGFjdHVhbCBRb1Mgb2ZmZXJlZCB0byBhIGdpdmVuIGZs
b3cgd2lsbCBkZXBlbmQgb24gdGhlIGRpc3RhbmNlIGFuZCBjb21wbGV4aXR5IG9mIHRoZSBwYXRo
IHRyYXZlcnNlZC4gSXQgd2lsbCBvZnRlbiBiZSBiZXR0ZXIgdGhhbiB0aGUgYm91bmRzIGluY2x1
ZGVkIHdpdGggdGhlIFFvUyBjbGFzcyBkZWZpbml0aW9ucyBpbiBUYWJsZSAxLg1TdGF0aWMgUW9T
IGNsYXNzIGFncmVlbWVudHMgY2FuIGJlIGltcGxlbWVudGVkIGJ5IGFzc29jaWF0aW5nIHBhY2tl
dCBtYXJraW5ncyAoZS5nLiwgVHlwZSBvZiBTZXJ2aWNlIHByZWNlZGVuY2UgYml0cyBvciBEaWZm
LVNlcnYgQ29kZSBQb2ludCkgd2l0aCBhIHNwZWNpZmljIGNsYXNzLiANUHJvdG9jb2xzIHRvIHN1
cHBvcnQgZHluYW1pYyBRb1MgcmVxdWVzdHMgYmV0d2VlbiB1c2VycyBhbmQgbmV0d29yayBwcm92
aWRlcnMsIGFuZCBiZXR3ZWVuIG5ldHdvcmsgcHJvdmlkZXJzLCBhcmUgdW5kZXIgc3R1ZHkuIFdo
ZW4gdGhlc2UgcHJvdG9jb2xzIGFuZCBzdXBwb3J0aW5nIHN5c3RlbXMgYXJlIGltcGxlbWVudGVk
LCB1c2VycyBvciBuZXR3b3JrcyBtYXkgcmVxdWVzdCBhbmQgcmVjZWl2ZSBkaWZmZXJlbnQgUW9T
IGNsYXNzZXMgb24gYSBmbG93LWJ5LWZsb3cgYmFzaXMuIEluIHRoaXMgZmFzaGlvbiwgdGhlIGRp
c3RpbmN0IHBlcmZvcm1hbmNlIG5lZWRzIG9mIGRpZmZlcmVudCBzZXJ2aWNlcyBhbmQgYXBwbGlj
YXRpb25zIGNhbiBiZSBjb21tdW5pY2F0ZWQsIGV2YWx1YXRlZCwgYW5kIGFja25vd2xlZGdlZCAo
b3IgcmVqZWN0ZWQsIG9yIG1vZGlmaWVkKS4NUmVmZXJlbmNlIFBhdGggZm9yIEVuZC10by1FbmQg
UW9TDUVhY2ggcGFja2V0IGluIGEgZmxvdyBmb2xsb3dzIGEgc3BlY2lmaWMgcGF0aC4gIEFueSBm
bG93ICh3aXRoIG9uZSBvciBtb3JlIHBhY2tldHMgb24gYSBwYXRoKSB0aGF0IHNhdGlzZmllcyB0
aGUgcGVyZm9ybWFuY2Ugb2JqZWN0aXZlcyBvZiB0aGlzIGNsYXVzZSBjYW4gYmUgY29uc2lkZXJl
ZCBmdWxseSBjb21wbGlhbnQgd2l0aCB0aGUgbm9ybWF0aXZlIHJlY29tbWVuZGF0aW9ucyBvZiBZ
LjE1NDEuDVRoZSBlbmQtdG8tZW5kIHBlcmZvcm1hbmNlIG9iamVjdGl2ZXMgYXJlIGRlZmluZWQg
Zm9yIHRoZSBJUCBwZXJmb3JtYW5jZSBwYXJhbWV0ZXJzIGNvcnJlc3BvbmRpbmcgdG8gdGhlIElQ
IHBhY2tldCB0cmFuc2ZlciByZWZlcmVuY2UgZXZlbnRzIChJUFJFcykuIFRoZSBlbmQtdG8tZW5k
IElQIHBlcmZvcm1hbmNlIG9iamVjdGl2ZXMgYXBwbHkgZnJvbSBOZXR3b3JrIEludGVyZmFjZSB0
byBOZXR3b3JrIEludGVyZmFjZSBpbiBGaWd1cmUgMS4gVGhlIGVuZC10by1lbmQgSVAgbmV0d29y
ayBwYXRoIGluY2x1ZGVzIHRoZSBzZXQgb2YgTmV0d29yayBTZWN0aW9ucyAoTlMpIGFuZCBpbnRl
ci1uZXR3b3JrIGxpbmtzIHRoYXQgcHJvdmlkZSB0aGUgdHJhbnNwb3J0IG9mIElQIHBhY2tldHMg
dHJhbnNtaXR0ZWQgZnJvbSBTUkMgdG8gRFNUOyB0aGUgcHJvdG9jb2xzIGJlbG93IGFuZCBpbmNs
dWRpbmcgdGhlIElQIGxheWVyIChsYXllciAxIHRvIGxheWVyIDMpIHdpdGhpbiB0aGUgU1JDIGFu
ZCBEU1QgbWF5IGFsc28gYmUgY29uc2lkZXJlZCBwYXJ0IG9mIGFuIElQIG5ldHdvcmsuICBOUyBh
cmUgc3lub255bW91cyB3aXRoIG9wZXJhdG9yIGRvbWFpbnMsIGFuZCBtYXkgaW5jbHVkZSBJUCBB
Y2Nlc3MgTmV0d29yayBBcmNoaXRlY3R1cmVzIGFzIGRlc2NyaWJlZCBpbiBSZWNvbW1lbmRhdGlv
bnMgRS42NTEgYW5kIFkuMTIzMS4gVGhpcyBSZWZlcmVuY2UgUGF0aCBpcyBhbiBhZGFwdGF0aW9u
IG9mIHRoZSBZLjE1NDAgUGVyZm9ybWFuY2UgTW9kZWwuDQENRmlndXJlIBMgU0VRIEZpZ3VyZSBc
KiBBUkFCSUMgFDEVICAgRW5kLUVuZCBSZWZlcmVuY2UgUGF0aCBmb3IgUW9TIE9iamVjdGl2ZXMg
DVRoZSBDdXN0b21lciBJbnN0YWxsYXRpb24gaW5jbHVkZXMgYWxsIFRlcm1pbmFsIEVxdWlwbWVu
dCAoVEUpLCBzdWNoIGFzIGEgaG9zdCBhbmQgYW55IHJvdXRlciBvciBMQU4gaWYgcHJlc2VudC4g
VGhlcmUgd2lsbCBiZSBvbmx5IG9uZSBodW1hbiBVc2VyIGluIHNvbWUgYXBwbGljYXRpb25zLiBT
cGVjaWZpY2F0aW9ucyBmb3IgVEUgYW5kIHRoZSBVc2VyLXRvLVVzZXIgQ29ubmVjdGlvbiBhcmUg
YmV5b25kIHRoZSBzY29wZSBvZiB0aGlzIFJlY29tbWVuZGF0aW9uLiBUaGUgZ2F0ZXdheXMgdGhh
dCBjb25uZWN0IHdpdGggdGVybWluYWwgZXF1aXBtZW50IG1heSBhbHNvIGJlIGNhbGxlZCBBY2Nl
c3MgR2F0ZXdheXMuDVJlZmVyZW5jZSBQYXRocyBoYXZlIHRoZSBmb2xsb3dpbmcgYXR0cmlidXRl
czoNSVAgY2xvdWRzIG1heSBzdXBwb3J0IFVzZXItdG8tVXNlciBjb25uZWN0aW9ucywgVXNlci10
by1Ib3N0IGNvbm5lY3Rpb25zLCBhbmQgb3RoZXIgZW5kcG9pbnQgdmFyaWF0aW9ucy4gDU5ldHdv
cmsgU2VjdGlvbnMgbWF5IGJlIHJlcHJlc2VudGVkIGFzIGNsb3VkcyB3aXRoIEdhdGV3YXkgcm91
dGVycyBvbiB0aGVpciBlZGdlcywgYW5kIHNvbWUgbnVtYmVyIG9mIGludGVyaW9yIHJvdXRlcnMg
d2l0aCB2YXJpb3VzIHJvbGVzLg1UaGUgbnVtYmVyIG9mIE5ldHdvcmsgU2VjdGlvbnMgaW4gYSBn
aXZlbiBwYXRoIG1heSBkZXBlbmQgdXBvbiB0aGUgQ2xhc3Mgb2YgU2VydmljZSBvZmZlcmVkLCBh
bG9uZyB3aXRoIHRoZSBjb21wbGV4aXR5IGFuZCBnZW9ncmFwaGljIHNwYW4gb2YgZWFjaCBOZXR3
b3JrIFNlY3Rpb24uDVRoZSBzY29wZSBvZiB0aGlzIFJlY29tbWVuZGF0aW9uIGFsbG93cyBvbmUg
b3IgbW9yZSBOZXR3b3JrIFNlY3Rpb25zIGluIGEgcGF0aC4NVGhlIE5ldHdvcmsgU2VjdGlvbnMg
c3VwcG9ydGluZyB0aGUgcGFja2V0cyBpbiBhIGZsb3cgbWF5IGNoYW5nZSBkdXJpbmcgaXRzIGxp
ZmUuDUlQIGNvbm5lY3Rpdml0eSBzcGFucyBpbnRlcm5hdGlvbmFsIGJvdW5kYXJpZXMsIGJ1dCBk
b2VzIG5vdCBmb2xsb3cgY2lyY3VpdCBzd2l0Y2hlZCBjb252ZW50aW9ucyAoZS5nLiwgdGhlcmUg
bWF5IG5vdCBiZSBpZGVudGlmaWFibGUgZ2F0ZXdheXMgYXQgYW4gaW50ZXJuYXRpb25hbCBib3Vu
ZGFyeSBpZiB0aGUgc2FtZSBuZXR3b3JrIHNlY3Rpb24gaXMgdXNlZCBvbiBib3RoIHNpZGVzIG9m
IHRoZSBib3VuZGFyeSkuDVFvUyBjbGFzc2VzDVRoaXMgc3ViY2xhdXNlIGRlc2NyaWJlcyB0aGUg
Y3VycmVudGx5IGRlZmluZWQgUW9TIGNsYXNzZXMuIEVhY2ggUW9TIGNsYXNzIGNyZWF0ZXMgYSBz
cGVjaWZpYyBjb21iaW5hdGlvbiBvZiBib3VuZHMgb24gdGhlIHBlcmZvcm1hbmNlIHZhbHVlcy4g
VGhpcyBzdWJjbGF1c2UgaW5jbHVkZXMgZ3VpZGFuY2UgYXMgdG8gd2hlbiBlYWNoIFFvUyBjbGFz
cyBtaWdodCBiZSB1c2VkLCBidXQgaXQgZG9lcyBub3QgbWFuZGF0ZSB0aGUgdXNlIG9mIGFueSBw
YXJ0aWN1bGFyIFFvUyBjbGFzcyBpbiBhbnkgcGFydGljdWxhciBjb250ZXh0Lg1OYXR1cmUgb2Yg
dGhlIG5ldHdvcmsgcGVyZm9ybWFuY2Ugb2JqZWN0aXZlcw1UaGUgb2JqZWN0aXZlcyBpbiBUYWJs
ZSAxIGFwcGx5IHRvIHB1YmxpYyBJUCBuZXR3b3JrcywgYmV0d2VlbiBNUHMgdGhhdCBkZWxpbWl0
IHRoZSBlbmQtdG8tZW5kIElQIG5ldHdvcmsuIFRoZSBvYmplY3RpdmVzIGFyZSBiZWxpZXZlZCB0
byBiZSBhY2hpZXZhYmxlIG9uIGNvbW1vbiBpbXBsZW1lbnRhdGlvbnMgb2YgSVAgTmV0d29ya3Mu
DVRoZSBsZWZ0LWhhbmQgcGFydCBvZiBUYWJsZSAxIGluZGljYXRlcyB0aGUgc3RhdGlzdGljYWwg
bmF0dXJlIG9mIHRoZSBwZXJmb3JtYW5jZSBvYmplY3RpdmVzIHRoYXQgYXBwZWFyIGluIHRoZSBz
dWJzZXF1ZW50IHJvd3MuDVRoZSBwZXJmb3JtYW5jZSBvYmplY3RpdmVzIGZvciBJUCBwYWNrZXQg
dHJhbnNmZXIgZGVsYXkgYXJlIHVwcGVyIGJvdW5kcyBvbiB0aGUgdW5kZXJseWluZyBtZWFuIElQ
VEQgZm9yIHRoZSBmbG93LiBBbHRob3VnaCBtYW55IGluZGl2aWR1YWwgcGFja2V0cyBtYXkgaGF2
ZSB0cmFuc2ZlciBkZWxheXMgdGhhdCBleGNlZWQgdGhpcyBib3VuZCwgdGhlIGF2ZXJhZ2UgSVBU
RCBmb3IgbGlmZXRpbWUgb2YgdGhlIGZsb3cgKGEgc3RhdGlzdGljYWwgZXN0aW1hdG9yIG9mIHRo
ZSBtZWFuKSBzaG91bGQgbm9ybWFsbHkgYmUgbGVzcyB0aGFuIHRoZSBhcHBsaWNhYmxlIGJvdW5k
IGZyb20gVGFibGUgMS4NVGhlIHBlcmZvcm1hbmNlIG9iamVjdGl2ZXMgZm9yIDItcG9pbnQgSVAg
UGFja2V0IERlbGF5IFZhcmlhdGlvbiBhcmUgYmFzZWQgb24gYW4gdXBwZXIgYm91bmQgb24gdGhl
IDEtMTCWMyBxdWFudGlsZSBvZiB0aGUgdW5kZXJseWluZyBJUFREIGRpc3RyaWJ1dGlvbiBmb3Ig
dGhlIGZsb3cuIFRoZSAxLTEwljMgcXVhbnRpbGUgYWxsb3dzIHNob3J0IGV2YWx1YXRpb24gaW50
ZXJ2YWxzIChlLmcsIGEgc2FtcGxlIHdpdGggMTAwMCBwYWNrZXRzIGlzIHRoZSBtaW5pbXVtIG5l
Y2Vzc2FyeSB0byBldmFsdWF0ZSB0aGlzIGJvdW5kKS4gQWxzbywgdGhpcyBhbGxvd3MgbW9yZSBm
bGV4aWJpbGl0eSBpbiBuZXR3b3JrIGRlc2lnbnMgd2hlcmUgZW5naW5lZXJpbmcgb2YgZGVsYXkg
YnVpbGRvdXQgYnVmZmVycyBhbmQgcm91dGVyIHF1ZXVlIGxlbmd0aHMgbXVzdCBhY2hpZXZlIGFu
IG92ZXJhbGwgSVBMUiBvYmplY3RpdmUgb24gdGhlIG9yZGVyIG9mIDEwljMuIFVzZSBvZiBsb3dl
ciBxdWFudGlsZSB2YWx1ZXMgd2lsbCByZXN1bHQgaW4gdW5kZXItZXN0aW1hdGVzIG9mIGRlLWpp
dHRlciBidWZmZXIgc2l6ZSwgYW5kIHRoZSBlZmZlY3RpdmUgcGFja2V0IGxvc3Mgd291bGQgZXhj
ZWVkIHRoZSBvdmVyYWxsIElQTFIgb2JqZWN0aXZlIChlLmcuLCBhbiB1cHBlciBxdWFudGlsZSBv
ZiAxLTEwljIgbWF5IGhhdmUgYW4gb3ZlcmFsbCBwYWNrZXQgbG9zcyBvZiAxLjElLCB3aXRoIElQ
TFI9MTCWMykuIE90aGVyIHN0YXRpc3RpY2FsIHRlY2huaXF1ZXMgYW5kIGRlZmluaXRpb25zIGZv
ciBJUERWIGFyZSBiZWluZyBzdHVkaWVkIGFzIGRlc2NyaWJlZCBpbiBBcHBlbmRpeCBJSSwgYW5k
IEFwcGVuZGl4IElWIGRpc2N1c3NlcyBJUERWIHBlcmZvcm1hbmNlIGVzdGltYXRpb24uDVRoZSBw
ZXJmb3JtYW5jZSBvYmplY3RpdmVzIGZvciB0aGUgSVAgcGFja2V0IGxvc3MgcmF0aW9zIGFyZSB1
cHBlciBib3VuZHMgb24gdGhlIElQIHBhY2tldCBsb3NzIGZvciB0aGUgZmxvdy4gQWx0aG91Z2gg
aW5kaXZpZHVhbCBwYWNrZXRzIHdpbGwgYmUgbG9zdCwgdGhlIHVuZGVybHlpbmcgcHJvYmFiaWxp
dHkgdGhhdCBhbnkgaW5kaXZpZHVhbCBwYWNrZXQgaXMgbG9zdCBkdXJpbmcgdGhlIGZsb3cgc2hv
dWxkIGJlIGxlc3MgdGhhbiB0aGUgYXBwbGljYWJsZSBib3VuZCBmcm9tIFRhYmxlIDEuDUV2YWx1
YXRpb24gaW50ZXJ2YWxzIGFuZCBSZXBvcnRpbmcgUmVxdWlyZW1lbnRzDVRoZSBvYmplY3RpdmVz
IGluIFRhYmxlIDEgY2Fubm90IGJlIGFzc2Vzc2VkIGluc3RhbnRhbmVvdXNseS4gRXZhbHVhdGlv
biBpbnRlcnZhbHMgcHJvZHVjZSBzdWJzZXRzIG9mIHRoZSBwYWNrZXQgcG9wdWxhdGlvbiBvZiBp
bnRlcmVzdCAoYXMgZGVmaW5lZCBpbiBSZWMuIFkuMTU0MCkuIElkZWFsbHksIHRoZXNlIGludGVy
dmFscyBhcmU6DVN1ZmZpY2llbnRseSBsb25nIHRvIGluY2x1ZGUgZW5vdWdoIHBhY2tldHMgb2Yg
dGhlIGRlc2lyZWQgZmxvdywgd2l0aCByZXNwZWN0IHRvIHRoZSByYXRpb3MgYW5kIHF1YW50aWxl
cyBzcGVjaWZpZWQuDVN1ZmZpY2llbnRseSBsb25nIHRvIHJlZmxlY3QgYSBwZXJpb2Qgb2YgdHlw
aWNhbCB1c2FnZSAoZmxvdyBsaWZldGltZSksIG9yIHVzZXIgZXZhbHVhdGlvbi4NU3VmZmljaWVu
dGx5IHNob3J0IHRvIGVuc3VyZSBhIGJhbGFuY2Ugb2YgYWNjZXB0YWJsZSBwZXJmb3JtYW5jZSB0
aHJvdWdob3V0IGVhY2ggaW50ZXJ2YWwgKGludGVydmFscyBvZiBwb29yIHBlcmZvcm1hbmNlIHNo
b3VsZCBiZSBpZGVudGlmaWVkLCBub3Qgb2JzY3VyZWQgd2l0aGluIGEgdmVyeSBsb25nIGV2YWx1
YXRpb24gaW50ZXJ2YWwpLg1TdWZmaWNpZW50bHkgc2hvcnQgdG8gYWRkcmVzcyB0aGUgcHJhY3Rp
Y2FsIGFzcGVjdHMgb2YgbWVhc3VyZW1lbnQuDUZvciB0ZWxlcGhvbnksIGEgbWluaW11bSBpbnRl
cnZhbCBvbiB0aGUgb3JkZXIgb2YgMTAgdG8gMjAgc2Vjb25kcyBpcyBuZWVkZWQgd2l0aCB0eXBp
Y2FsIHBhY2tldCByYXRlcyAoNTAgdG8gMTAwIHBhY2tldHMgcGVyIHNlY29uZCksIGFuZCBpbnRl
cnZhbHMgc2hvdWxkIGhhdmUgYW4gdXBwZXIgbGltaXQgb24gdGhlIG9yZGVyIG9mIG1pbnV0ZXMu
IEEgdmFsdWUgb2YgMSBtaW51dGUgaXMgcHJvdmlzaW9uYWxseSBzdWdnZXN0ZWQsIGFuZCBpbiBh
bnkgY2FzZSB0aGUgdmFsdWUgdXNlZCBtdXN0IGJlIHJlcG9ydGVkLCBhbG9uZyB3aXRoIGFueSBh
c3N1bXB0aW9ucyBhbmQgY29uZmlkZW5jZSBpbnRlcnZhbHMuICBNaW5pbWFsbHkgYWNjZXB0YWJs
ZSBlc3RpbWF0aW9uIG1ldGhvZG9sb2dpZXMgYXJlIGludGVuZGVkIGZvciBmdXR1cmUgcmV2aXNp
b25zIG9mIHRoaXMgUmVjb21tZW5kYXRpb24uIE1ldGhvZHMgdG8gdmVyaWZ5IGFjaGlldmVtZW50
IG9mIHRoZSBvYmplY3RpdmVzIGFyZSBmb3IgZnVydGhlciBzdHVkeS4NUGFja2V0IFNpemUgZm9y
IEV2YWx1YXRpb24gDVBhY2tldCBzaXplIGluZmx1ZW5jZXMgdGhlIHJlc3VsdHMgZm9yIG1vc3Qg
cGVyZm9ybWFuY2UgcGFyYW1ldGVycy4gIEEgcmFuZ2Ugb2YgcGFja2V0IHNpemVzIG1heSBiZSBh
cHByb3ByaWF0ZSBzaW5jZSBtYW55IGZsb3dzIGhhdmUgY29uc2lkZXJhYmxlIHNpemUgdmFyaWF0
aW9uLiAgSG93ZXZlciwgZXZhbHVhdGlvbiBpcyBzaW1wbGlmaWVkIHdpdGggYSBzaW5nbGUgcGFj
a2V0IHNpemUgd2hlbiBldmFsdWF0aW5nIElQRFYsIG9yIHdoZW4gdGhlIGFzc2Vzc21lbnQgdGFy
Z2V0cyBmbG93cyB0aGF0IHN1cHBvcnQgY29uc3RhbnQgYml0IHJhdGUgc291cmNlcywgYW5kIHRo
ZXJlZm9yZSBhIGZpeGVkIGluZm9ybWF0aW9uIGZpZWxkIHNpemUgaXMgcmVjb21tZW5kZWQuIElu
Zm9ybWF0aW9uIGZpZWxkcyBvZiBlaXRoZXIgMTYwIG9jdGV0cyBvciAxNTAwIG9jdGV0cyBhcmUg
c3VnZ2VzdGVkLCBhbmQgdGhlIGZpZWxkIHNpemUgdXNlZCBtdXN0IGJlIHJlcG9ydGVkLiBBbHNv
LCBhbiBpbmZvcm1hdGlvbiBmaWVsZCBvZiAxNTAwIG9jdGV0cyBpcyByZWNvbW1lbmRlZCBmb3Ig
cGVyZm9ybWFuY2UgZXN0aW1hdGlvbiBvZiBJUCBwYXJhbWV0ZXJzIHdoZW4gdXNpbmcgbG93ZXIg
bGF5ZXIgdGVzdHMsIHN1Y2ggYXMgYml0IGVycm9yIG1lYXN1cmVtZW50cy4NVW5zcGVjaWZpZWQg
KFVuYm91bmRlZCkgcGVyZm9ybWFuY2UNRm9yIHNvbWUgUW9TIGNsYXNzZXMgdGhlIHZhbHVlIGZv
ciBzb21lIHBlcmZvcm1hbmNlIHBhcmFtZXRlcnMgaXMgZGVzaWduYXRlZCAiVSIuIEluIHRoZXNl
IGNhc2VzLCB0aGUgSVRVHlQgc2V0cyBubyBvYmplY3RpdmVzIHJlZ2FyZGluZyB0aGVzZSBwYXJh
bWV0ZXJzIGFuZCBhbnkgZGVmYXVsdCBZLjE1NDEgb2JqZWN0aXZlcyBmb3IgdGhlc2UgcGFyYW1l
dGVycyBjYW4gYmUgaWdub3JlZC4gTmV0d29yayBvcGVyYXRvcnMgbWF5IHVuaWxhdGVyYWxseSBl
bGVjdCB0byBhc3N1cmUgc29tZSBtaW5pbXVtIHF1YWxpdHkgbGV2ZWwgZm9yIHRoZSB1bnNwZWNp
ZmllZCBwYXJhbWV0ZXJzLCBidXQgdGhlIElUVR5UIHdpbGwgbm90IHJlY29tbWVuZCBhbnkgc3Vj
aCBtaW5pbXVtLg1Vc2VycyBvZiB0aGVzZSBRb1MgY2xhc3NlcyBzaG91bGQgYmUgYXdhcmUgdGhh
dCB0aGUgcGVyZm9ybWFuY2Ugb2YgdW5zcGVjaWZpZWQgcGFyYW1ldGVycyBjYW4sIGF0IHRpbWVz
LCBiZSBhcmJpdHJhcmlseSBwb29yLiBIb3dldmVyLCB0aGUgZ2VuZXJhbCBleHBlY3RhdGlvbiBp
cyB0aGF0IG1lYW4gSVBURCB3aWxsIGJlIG5vIGdyZWF0ZXIgdGhhbiAxIHNlY29uZC4NTk9URSCW
IFRoZSB3b3JkICJ1bnNwZWNpZmllZCIgbWF5IGhhdmUgYSBkaWZmZXJlbnQgbWVhbmluZyBpbiBS
ZWNvbW1lbmRhdGlvbnMgY29uY2VybmluZyBCHklTRE4gc2lnbmFsbGluZy4NDVRhYmxlIDEvWS4x
NTQxIA1Qcm92aXNpb25hbCBJUCBRb1MgY2xhc3MgZGVmaW5pdGlvbnMgYW5kIG5ldHdvcmsgcGVy
Zm9ybWFuY2Ugb2JqZWN0aXZlcw0HB1FvUyBDbGFzc2VzBwdOZXR3b3JrIFBlcmZvcm1hbmNlIFBh
cmFtZXRlcgdOYXR1cmUgb2YgTmV0d29yayBQZXJmb3JtYW5jZSBPYmplY3RpdmUHQ2xhc3MgMA0H
Q2xhc3MgMQ0gDQdDbGFzcyAyDQdDbGFzcyAzDQdDbGFzcyA0DQdDbGFzcyA1DVVuLXNwZWNpZmll
ZCAHB0lQVEQHVXBwZXIgYm91bmQgb24gdGhlIG1lYW4gSVBURCAoTm90ZSAxKQcxMDBtcwc0MDBt
cwcxMDBtcwc0MDBtcwcxIHMHVQcHSVBEVgdVcHBlciBib3VuZCBvbiB0aGUgMS0xMC0zIHF1YW50
aWxlIG9mICBJUFREIG1pbnVzIHRoZSBtaW5pbXVtIElQVEQgKE5vdGUgMikHNTBtcyAoTm90ZSAz
KQc1MG1zIChOb3RlIDMpB1UHVQdVB1UHB0lQTFIHVXBwZXIgYm91bmQgb24gdGhlIHBhY2tldCBs
b3NzIHByb2JhYmlsaXR5BzEqMTAtMyAoTm90ZSA0KQcxKjEwLTMgKE5vdGUgNCkHMSoxMC0zBzEq
MTAtMwcxKjEwLTMHVQcHSVBFUgdVcHBlciBib3VuZAcxKjEwLTQgKE5vdGUgNSkHVQcHR2VuZXJh
bCBOb3RlczoHB1RoZSBvYmplY3RpdmVzIGFwcGx5IHRvIHB1YmxpYyBJUCBOZXR3b3Jrcy4gVGhl
IG9iamVjdGl2ZXMgYXJlIGJlbGlldmVkIHRvIGJlIGFjaGlldmFibGUgb24gY29tbW9uIElQIG5l
dHdvcmsgaW1wbGVtZW50YXRpb25zLiBUaGUgbmV0d29yayBwcm92aWRlcnMnIGNvbW1pdG1lbnQg
dG8gdGhlIHVzZXIgaXMgdG8gYXR0ZW1wdCB0byBkZWxpdmVyIHBhY2tldHMgaW4gYSB3YXkgdGhh
dCBhY2hpZXZlcyBlYWNoIG9mIHRoZSBhcHBsaWNhYmxlIG9iamVjdGl2ZXMuIFRoZSB2YXN0IG1h
am9yaXR5IG9mIElQIHBhdGhzIGFkdmVydGlzaW5nIGNvbmZvcm1hbmNlIHdpdGggUmVjb21tZW5k
YXRpb24gWS4xNTQxIHNob3VsZCBtZWV0IHRob3NlIG9iamVjdGl2ZXMuIEZvciBzb21lIHBhcmFt
ZXRlcnMsIHBlcmZvcm1hbmNlIG9uIHNob3J0ZXIgYW5kL29yIGxlc3MgY29tcGxleCBwYXRocyBt
YXkgYmUgc2lnbmlmaWNhbnRseSBiZXR0ZXIuBwdBbiBldmFsdWF0aW9uIGludGVydmFsIG9mIDEg
bWludXRlIGlzIHByb3Zpc2lvbmFsbHkgc3VnZ2VzdGVkIGZvciBJUFRELCBJUERWLCBhbmQgSVBM
UiwgYW5kIGluIGFsbCBjYXNlcyB0aGUgaW50ZXJ2YWwgbXVzdCBiZSByZXBvcnRlZC4HB0luZGl2
aWR1YWwgbmV0d29yayBwcm92aWRlcnMgbWF5IGNob29zZSB0byBvZmZlciBwZXJmb3JtYW5jZSBj
b21taXRtZW50cyBiZXR0ZXIgdGhhbiB0aGVzZSBvYmplY3RpdmVzLgcHIlUiIG1lYW5zICJ1bnNw
ZWNpZmllZCIgb3IgInVuYm91bmRlZCIuIFdoZW4gdGhlIHBlcmZvcm1hbmNlIHJlbGF0aXZlIHRv
IGEgcGFydGljdWxhciBwYXJhbWV0ZXIgaXMgaWRlbnRpZmllZCBhcyBiZWluZyAiVSIgdGhlIElU
VR5UIGVzdGFibGlzaGVzIG5vIG9iamVjdGl2ZSBmb3IgdGhpcyBwYXJhbWV0ZXIgYW5kIGFueSBk
ZWZhdWx0IFkuMTU0MSBvYmplY3RpdmUgY2FuIGJlIGlnbm9yZWQuIFdoZW4gdGhlIG9iamVjdGl2
ZSBmb3IgYSBwYXJhbWV0ZXIgaXMgc2V0IHRvICJVIiwgcGVyZm9ybWFuY2Ugd2l0aCByZXNwZWN0
IHRvIHRoYXQgcGFyYW1ldGVyIG1heSwgYXQgdGltZXMsIGJlIGFyYml0cmFyaWx5IHBvb3IuBwcN
QWxsIHZhbHVlcyBhcmUgcHJvdmlzaW9uYWwgYW5kIHRoZXkgbmVlZCBub3QgYmUgbWV0IGJ5IG5l
dHdvcmtzIHVudGlsIHRoZXkgYXJlIHJldmlzZWQgKHVwIG9yIGRvd24pIGJhc2VkIG9uIHJlYWwg
b3BlcmF0aW9uYWwgZXhwZXJpZW5jZQ1Ob3RlIDEgliBWZXJ5IGxvbmcgcHJvcGFnYXRpb24gdGlt
ZXMgd2lsbCBwcmV2ZW50IGxvdyBlbmQtdG8tZW5kIGRlbGF5IG9iamVjdGl2ZXMgZnJvbSBiZWlu
ZyBtZXQuIEluIHRoZXNlIGFuZCBzb21lIG90aGVyIGNpcmN1bXN0YW5jZXMsIHRoZSBJUFREIG9i
amVjdGl2ZXMgaW4gQ2xhc3NlcyAwIGFuZCAyIHdpbGwgbm90IGFsd2F5cyBiZSBhY2hpZXZhYmxl
LiBFdmVyeSBuZXR3b3JrIHByb3ZpZGVyIHdpbGwgZW5jb3VudGVyIHRoZXNlIGNpcmN1bXN0YW5j
ZXMgYW5kIHRoZSByYW5nZSBvZiBJUFREIG9iamVjdGl2ZXMgaW4gVGFibGUgMS9ZLjE1NDEgcHJv
dmlkZXMgYWNoaWV2YWJsZSBRb1MgY2xhc3NlcyBhcyBhbHRlcm5hdGl2ZXMuIFRoZSBkZWxheSBv
YmplY3RpdmVzIG9mIGEgY2xhc3MgZG8gbm90IHByZWNsdWRlIGEgbmV0d29yayBwcm92aWRlciBm
cm9tIG9mZmVyaW5nIHNlcnZpY2VzIHdpdGggc2hvcnRlciBkZWxheSBjb21taXRtZW50cy4gQWNj
b3JkaW5nIHRvIHRoZSBkZWZpbml0aW9uIG9mIElQVEQgaW4gWS4xNTQwLCBwYWNrZXQgaW5zZXJ0
aW9uIHRpbWUgaXMgaW5jbHVkZWQgaW4gdGhlIElQVEQgb2JqZWN0aXZlLiBUaGlzIFJlY29tbWVu
ZGF0aW9uIHN1Z2dlc3RzIGEgbWF4aW11bSBwYWNrZXQgaW5mb3JtYXRpb24gZmllbGQgb2YgMTUw
MCBieXRlcyBmb3IgZXZhbHVhdGluZyB0aGVzZSBvYmplY3RpdmVzLg1Ob3RlIDIgliBUaGUgZGVm
aW5pdGlvbiBhbmQgbmF0dXJlIG9mIHRoZSBJUERWIG9iamVjdGl2ZSBpcyB1bmRlciBzdHVkeS4g
U2VlIEFwcGVuZGl4IElJIGZvciBtb3JlIGRldGFpbHMuDU5vdGUgMyCWVGhpcyB2YWx1ZSBpcyBk
ZXBlbmRlbnQgb24gdGhlIGNhcGFjaXR5IG9mIGludGVyLW5ldHdvcmsgbGlua3MuIFNtYWxsZXIg
dmFyaWF0aW9ucyBhcmUgcG9zc2libGUgd2hlbiBhbGwgY2FwYWNpdGllcyBhcmUgaGlnaGVyIHRo
YW4gcHJpbWFyeSByYXRlIChUMSBvciBFMSksIG9yIHdoZW4gY29tcGV0aW5nIHBhY2tldCBpbmZv
cm1hdGlvbiBmaWVsZHMgYXJlIHNtYWxsZXIgdGhhbiAxNTAwIGJ5dGVzIChzZWUgQXBwZW5kaXgg
SVYpLg1Ob3RlIDQgliBUaGUgQ2xhc3MgMCBhbmQgMSBvYmplY3RpdmVzIGZvciBJUExSIGFyZSBw
YXJ0bHkgYmFzZWQgb24gc3R1ZGllcyBzaG93aW5nIHRoYXQgaGlnaCBxdWFsaXR5IHZvaWNlIGFw
cGxpY2F0aW9ucyBhbmQgdm9pY2UgY29kZWNzIHdpbGwgYmUgZXNzZW50aWFsbHkgdW5hZmZlY3Rl
ZCBieSBhIDEwLTMgSVBMUi4NTm90ZSA1IJYgVGhpcyB2YWx1ZSBlbnN1cmVzIHRoYXQgcGFja2V0
IGxvc3MgaXMgdGhlIGRvbWluYW50IHNvdXJjZSBvZiBkZWZlY3RzIHByZXNlbnRlZCB0byB1cHBl
ciBsYXllcnMsIGFuZCBpcyBmZWFzaWJsZSB3aXRoIElQIHRyYW5zcG9ydCBvbiBBVE0uDQcHRGlz
Y3Vzc2lvbiBvZiB0aGUgSVBURCBPYmplY3RpdmVzDVZlcnkgbG9uZyBwcm9wYWdhdGlvbiB0aW1l
cyB3aWxsIHByZXZlbnQgbG93IGVuZC10by1lbmQgZGVsYXkgb2JqZWN0aXZlcyBmcm9tIGJlaW5n
IG1ldC4gSW4gdGhlc2UgYW5kIHNvbWUgb3RoZXIgY2lyY3Vtc3RhbmNlcywgdGhlIElQVEQgb2Jq
ZWN0aXZlcyBpbiBDbGFzc2VzIDAgYW5kIDIgd2lsbCBub3QgYWx3YXlzIGJlIGFjaGlldmFibGUu
IEl0IHNob3VsZCBiZSBub3RlZCB0aGF0IHRoZSBkZWxheSBvYmplY3RpdmVzIG9mIGEgY2xhc3Mg
ZG8gbm90IHByZWNsdWRlIGEgbmV0d29yayBwcm92aWRlciBmcm9tIG9mZmVyaW5nIHNlcnZpY2Vz
IHdpdGggc2hvcnRlciBkZWxheSBjb21taXRtZW50cy4gIEFueSBzdWNoIGNvbW1pdG1lbnQgc2hv
dWxkIGJlIGV4cGxpY2l0bHkgc3RhdGVkLiBTZWUgQXBwZW5kaXggSUlJIGZvciBhbiBleGFtcGxl
IGNhbGN1bGF0aW9uIG9mIElQVEQgb24gYSBnbG9iYWwgcm91dGUuIEV2ZXJ5IG5ldHdvcmsgcHJv
dmlkZXIgd2lsbCBlbmNvdW50ZXIgdGhlc2UgY2lyY3Vtc3RhbmNlcyAoZWl0aGVyIGFzIGEgc2lu
Z2xlIG5ldHdvcmssIG9yIHdoZW4gd29ya2luZyBpbiBjb29wZXJhdGlvbiB3aXRoIG90aGVyIG5l
dHdvcmtzIHRvIHByb3ZpZGUgdGhlIGVuZC10by1lbmQgcGF0aCksIGFuZCB0aGUgcmFuZ2Ugb2Yg
SVBURCBvYmplY3RpdmVzIGluIFRhYmxlIDEvWS4xNTQxIHByb3ZpZGVzIGFjaGlldmFibGUgUW9T
IGNsYXNzZXMgYXMgYWx0ZXJuYXRpdmVzLiBEZXNwaXRlIGRpZmZlcmVudCByb3V0aW5nIGFuZCBk
aXN0YW5jZSBjb25zaWRlcmF0aW9ucywgcmVsYXRlZCBjbGFzc2VzIChlLmcuLCBDbGFzc2VzIDAg
YW5kIDEpIHdvdWxkIHR5cGljYWxseSBiZSBpbXBsZW1lbnRlZCB1c2luZyB0aGUgc2FtZSBub2Rl
IG1lY2hhbmlzbXMuDUFjY29yZGluZyB0byB0aGUgZGVmaW5pdGlvbiBvZiBJUFREIGluIFkuMTU0
MCwgcGFja2V0IGluc2VydGlvbiB0aW1lIGlzIGluY2x1ZGVkIGluIHRoZSBJUFREIG9iamVjdGl2
ZXMuIFRoaXMgUmVjb21tZW5kYXRpb24gc3VnZ2VzdHMgYSBtYXhpbXVtIHBhY2tldCBpbmZvcm1h
dGlvbiBmaWVsZCBvZiAxNTAwIGJ5dGVzIGZvciBldmFsdWF0aW5nIHRoZSBvYmplY3RpdmVzLg1H
dWlkYW5jZSBvbiBDbGFzcyBVc2FnZQ1UaGUgZm9sbG93aW5nIHRhYmxlIGdpdmVzIHNvbWUgZ3Vp
ZGFuY2UgZm9yIHRoZSBhcHBsaWNhYmlsaXR5IGFuZCBlbmdpbmVlcmluZyBvZiB0aGUgUW9TIENs
YXNzZXMuIA0MVGFibGUgMi9ZLjE1NDENR3VpZGFuY2UgZm9yIElQIFFvUyBjbGFzc2VzDVFvUyBD
bGFzcwdBcHBsaWNhdGlvbnMgKEV4YW1wbGVzKQdOb2RlIE1lY2hhbmlzbXMHTmV0d29yayBUZWNo
bmlxdWVzBwcwB1JlYWwtVGltZSwgSml0dGVyIHNlbnNpdGl2ZSwgaGlnaCBpbnRlcmFjdGlvbihW
b0lQLCBWVEMpB1NlcGFyYXRlIFF1ZXVlIHdpdGggcHJlZmVyZW50aWFsIHNlcnZpY2luZywgVHJh
ZmZpYyBncm9vbWluZwdDb25zdHJhaW5lZCBSb3V0aW5nIGFuZCBEaXN0YW5jZQcHMQdSZWFsLVRp
bWUsIEppdHRlciBzZW5zaXRpdmUsIGludGVyYWN0aXZlIChWb0lQLCBWVEMpLgcHTGVzcyBjb25z
dHJhaW5lZCBSb3V0aW5nIGFuZCBEaXN0YW5jZXMHBzIHVHJhbnNhY3Rpb24gRGF0YSwgSGlnaGx5
IEludGVyYWN0aXZlLCAoU2lnbmFsaW5nKQdTZXBhcmF0ZSBRdWV1ZSwgRHJvcCBwcmlvcml0eQdD
b25zdHJhaW5lZCBSb3V0aW5nIGFuZCBEaXN0YW5jZQcHMwdUcmFuc2FjdGlvbiBEYXRhLCBJbnRl
cmFjdGl2ZSAHB0xlc3MgY29uc3RyYWluZWQgUm91dGluZyBhbmQgRGlzdGFuY2VzBwc0B0xvdyBM
b3NzIE9ubHkgKFNob3J0IFRyYW5zYWN0aW9ucywgQnVsayBEYXRhLCBWaWRlbyBTdHJlYW1pbmcp
B0xvbmcgUXVldWUsIERyb3AgcHJpb3JpdHkHQW55IHJvdXRlL3BhdGgHBzUHVHJhZGl0aW9uYWwg
QXBwbGljYXRpb25zIG9mIERlZmF1bHQgSVAgTmV0d29ya3MgB1NlcGFyYXRlIFF1ZXVlIChsb3dl
c3QgcHJpb3JpdHkpB0FueSByb3V0ZS9wYXRoBwcNVHJhZmZpYyBwb2xpY2luZyBhbmQgb3Igc2hh
cGluZyBtYXkgYWxzbyBiZSBhcHBsaWVkIGluIG5ldHdvcmsgbm9kZXMuIA1EaXNjdXNzaW9uIG9m
IEJyb2FkY2FzdCBRdWFsaXR5IFRlbGV2aXNpb24gdHJhbnNwb3J0IG9uIElQIG1heSBiZSBmb3Vu
ZCBpbiBBcHBlbmRpeCBJWC4NQXZhaWxhYmlsaXR5IG9iamVjdGl2ZXMNVGhpcyBzZWN0aW9uIHdp
bGwgaW5jbHVkZSBpbmZvcm1hdGlvbiBhYm91dCBhdmFpbGFiaWxpdHkgb2JqZWN0aXZlcyBiYXNl
ZCBvbiB0aGUgYXZhaWxhYmlsaXR5IHBhcmFtZXRlciBkZWZpbmVkIGluIFkuMTU0MC4gVGhlIG9i
amVjdGl2ZXMgcmVxdWlyZSBtb3JlIHN0dWR5LCBzaW5jZSBmdW5kYW1lbnRhbCBuZXR3b3JrIGRl
c2lnbiBvcHRpb25zIGFyZSByYXBpZGx5IGNoYW5naW5nLg0gQWNoaWV2ZW1lbnQgb2YgdGhlIHBl
cmZvcm1hbmNlIG9iamVjdGl2ZXMNRnVydGhlciBzdHVkeSBpcyByZXF1aXJlZCB0byBkZXRlcm1p
bmUgaG93IHRvIGFjaGlldmUgdGhlc2UgcGVyZm9ybWFuY2Ugb2JqZWN0aXZlcyB3aGVuIG11bHRp
cGxlIG5ldHdvcmsgcHJvdmlkZXJzIGFyZSBpbnZvbHZlZC4NDUFwcGVuZGl4IEkNKEluZm9ybWF0
aXZlKQ1BVE0gTmV0d29yayBRb1Mgc3VwcG9ydCBvZiBJUCBRb1MNDVRoaXMgQXBwZW5kaXggcHJl
c2VudHMgYW4gYW5hbHlzaXMgb2YgbWFwcGluZyBJUCBwZXJmb3JtYW5jZSBwYXJhbWV0ZXJzIG9u
IHRvcCBvZiB0aGUgQVRNIFFvUyBDbGFzcyBvYmplY3RpdmVzIGFzIHNwZWNpZmllZCBpbiBJLjM1
Ni4gVGhlIHB1cnBvc2Ugb2YgdGhpcyBhbmFseXNpcyBpcyB0byBlc3RpbWF0ZSBJUCBsZXZlbCBw
ZXJmb3JtYW5jZSBvYnRhaW5lZCB3aGVuIEFUTSBpcyB1c2VkIGFzIHRoZSB1bmRlcmx5aW5nIHRy
YW5zcG9ydC4gQmVjYXVzZSB0aGVyZSBhcmUgbm8gcm91dGVycyBjb25zaWRlcmVkIGluIHRoaXMg
YW5hbHlzaXMsIHRoZSBJUCBwZXJmb3JtYW5jZSBudW1iZXJzIHNob3duIGhlcmUgYXJlIHRoZSBi
ZXN0IHRoYXQgY2FuIGJlIGV4cGVjdGVkLiBJbiBzY2VuYXJpb3Mgd2hlcmUgaW50ZXJtZWRpYXRl
IHJvdXRlcnMgZXhpc3QsIHRoZSBJUCBwZXJmb3JtYW5jZSB3aWxsIGJlIHdvcnNlLg0NVGFibGUg
SS4xLiBJUCBQYWNrZXQgTG9zcyBSYXRpbyAoSVBMUikgdmFsdWVzIGNvcnJlc3BvbmRpbmcgdG8g
QVRNIFFvUyBTZXJ2aWNlIGNsYXNzZXMgMSBhbmQgMiAoSVAgcGFja2V0IHNpemUgNDAgYnl0ZXM7
IGFsbCBlcnJvcmVkIHBhY2tldHMgYXJlIGFzc3VtZWQgbG9zdCkNQVRNIFFvUyBDbGFzcwdkZWxp
dmVyZWQLQVRNIENFUgdkZWxpdmVyZWQLQVRNIENMUgdyZXN1bHRpbmcLSVBMUgcHMQc0LjAwIEUt
MDYHMy4wMCBFLTA3BzQuMzAgRS0wNgcHMgcHMS4wMCBFLTA1BzEuNDAgRS0wNQcHVGFibGUgSS4y
LiAgSVAgUGFja2V0IFRyYW5zZmVyIERlbGF5IChJUFREKSB2YWx1ZXMgZm9yIGEgZmxvdyBvdmVy
IGEgTmF0aW9uYWwgUG9ydGlvbiBhbmQgYW4gRW5kLXRvLUVuZCBGbG93DU5ldHdvcmsgUG9ydGlv
bgdJUFREIHJlc3VsdGluZyBmcm9tIEFUTSBRb1MgQ2xhc3MgMQsobm8gZGVsYXkgZnJvbSBJUCBy
b3V0ZXJzKQcHTmF0aW9uYWwgUG9ydGlvbgd+MjcuNCBtcwcHRW5kLXRvLUVuZAc0MDAgbXMHBw1U
aGUgdmFsdWUgb2YgdGhlIENlbGwgRXJyb3IgUmF0aW8gKENFUikgaW4gdGhlIEFUTSBjbGFzc2Vz
IGlzIDQgeCAxMC02IC4gIElmIElQIHBhY2tldHMgYXJlIGxvbmcgKDE1MDAgYnl0ZXMpIGFuZCBl
cnJvcmVkIGNlbGxzIGNhdXNlIGVycm9yZWQgSVAgcGFja2V0cywgdGhlIHZhbHVlIG9mIElQIHBh
Y2tldCBlcnJvciByYXRpbyB3aWxsIGJlIGFib3V0IDEwLTQgLg1DZWxsIE1pc2luc2VydGlvbiBS
YXRpbyAoQ01SKSBpcyBjdXJyZW50bHkgc3BlY2lmaWVkIGFzIDEvZGF5LiAgVGhlIGltcGxpY2F0
aW9ucyBvZiBDTVIgb24gU1BSIHJlcXVpcmVzIG1vcmUgc3R1ZHkuDVRoZXNlIHZhbHVlcyBtYXkg
YmUgdXNlZCBhcyBndWlkZWxpbmVzIGZvciByZWZpbmluZyB0aGUgSVAgUW9TIGNsYXNzZXMuDQ1B
cHBlbmRpeCBJSQ0oSW5mb3JtYXRpdmUpDUlQIERlbGF5IFZhcmlhdGlvbiBQYXJhbWV0ZXIgRGVm
aW5pdGlvbiBDb25zaWRlcmF0aW9ucw0NVGhpcyBBcHBlbmRpeCBkaXNjdXNzZXMgY29uc2lkZXJh
dGlvbnMgZm9yIHRoZSBkZWZpbml0aW9uIG9mIElQRFYgYW5kIHRoZSB1c2Ugb2YgYWx0ZXJuYXRl
IHN0YXRpc3RpY2FsIG1ldGhvZHMgZm9yIHRoZSBJUERWIG9iamVjdGl2ZS4gDUluIG9yZGVyIHRv
IHByb3ZpZGUgZ3VpZGFuY2UgdG8gZGVzaWduZXJzIG9mIGppdHRlciBidWZmZXIgaW4gZWRnZSBl
cXVpcG1lbnQsIHRoZSBwYXJhbWV0ZXIocykgbmVlZCB0byBjYXB0dXJlIHRoZSBlZmZlY3RzIG9m
IHRoZSBmb2xsb3dpbmcgb24gSVBEViA6DXJvdXRpbmUgY29uZ2VzdGlvbiBpbiB0aGUgbmV0d29y
ayAoaGlnaCBmcmVxdWVuY3kgSVBURCB2YXJpYXRpb25zKQ1UQ1Agd2luZG93aW5nIGJlaGF2aW9y
IChsb3cgZnJlcXVlbmN5IElQVEQgdmFyaWF0aW9ucykNcGVyaW9kaWMgYW5kIGFwZXJpb2RpYyB2
YXJpYXRpb25zIGluIGF2ZXJhZ2UgbmV0d29yayBsb2FkaW5nIChsb3cgZnJlcXVlbmN5IElQVEQg
dmFyaWF0aW9ucykNUm91dGluZyB1cGRhdGUgZWZmZWN0cyBvbiBJUFREIChpbnN0YW50YW5lb3Vz
IChhbmQgcG9zc2libHkgbGFyZ2UpIGNoYW5nZXMgaW4gSVBURCkNVGhlIGN1cnJlbnQgZGVmaW5p
dGlvbiBvZiBJUCBEZWxheSBWYXJpYXRpb24gaXMNEyBFTUJFRCBFcXVhdGlvbi4zICAUARUgDXdo
ZXJlLA1JUFREdXBwZXIgaXMgdGhlIDEtMTAtMyBxdWFudGlsZSBvZiBJUFREIGluIHRoZSBldmFs
dWF0aW9uIGludGVydmFsDUlQVERtaW4gaXMgdGhlIG1pbmltdW0gSVBURCBpbiB0aGUgZXZhbHVh
dGlvbiBpbnRlcnZhbA0NVGhlIGRlZmluaXRpb24gb2YgSVBEViBpcyBiYXNlZCBvbiB0aGUgcmVm
ZXJlbmNlIGV2ZW50cyBnaXZlbiBpbiBZLjE1NDAgQXBwZW5kaXggSUkuIEhlcmUsIHRoZSBub21p
bmFsIGRlbGF5IGlzIGJhc2VkIG9uIHRoZSBwYWNrZXQgd2l0aCB0aGUgbWluaW11bSBvbmUtd2F5
IGRlbGF5IChhcyBhbiBhbHRlcm5hdGl2ZSB0byB0aGUgZmlyc3QgcGFja2V0LCBvciB0aGUgYXZl
cmFnZSBvZiB0aGUgcG9wdWxhdGlvbiBhcyB0aGUgbm9taW5hbCBkZWxheSkuDQ1UaGUgc3BlY2lm
aWNhdGlvbiBvZiB0aGUgMS0xMC0zIHF1YW50aWxlIChlcXVpdmFsZW50IHRvIHRoZSA5OS45dGgg
cGVyY2VudGlsZSkgaXMgaW5mbHVlbmNlZCBieSB0aGUgc2l6ZSBvZiB0aGUgcGFja2V0IHNhbXBs
ZSBpbiBhIDEgbWludXRlIG1lYXN1cmVtZW50IGludGVydmFsIGFuZCB0aGUgSVBMUiBvYmplY3Rp
dmUgKDEwLTMsIHJlc3VsdGluZyBpbiBvdmVyYWxsIGxvc3MgcmF0aW8gb2JqZWN0aXZlIG9mIGFi
b3V0IDEwLTMuIFNtYWxsZXIgcXVhbnRpbGVzIHdvdWxkIGFkZCBtb3JlIGxvc3NlcywgYXMgc2hv
d24gYmVsb3cuDQ0TIEVNQkVEIEV4Y2VsLlNoZWV0LjggIBQBFQ1GaWd1cmUgEyBTRVEgRmlndXJl
IFwqIEFSQUJJQyAUMhUgIEVmZmVjdCBvZiBkaWZmZXJlbnQgSVBEViBRdWFudGlsZXMgb24gT3Zl
cmFsbCBMb3NzIHdoZW4gSVBMUj0wLjAwMQ1BbiBleGFtcGxlIGFsdGVybmF0ZSBkZWZpbml0aW9u
IG9mIElQIERlbGF5IFZhcmlhdGlvbiBpcyBnaXZlbiBoZXJlLiBJUCBEZWxheSBWYXJpYXRpb24g
bWF5IGJlIGRlZmluZWQgYXMgdGhlIG1heGltdW0gSVBURCBtaW51cyB0aGUgbWluaW11bSBJUFRE
IGR1cmluZyBhIGdpdmVuIHNob3J0IG1lYXN1cmVtZW50IGludGVydmFsLg0TIEVNQkVEIEVxdWF0
aW9uLjMgIBQBFSANDXdoZXJlLA1JUFREbWF4IGlzIHRoZSBtYXhpbXVtIElQVEQgcmVjb3JkZWQg
ZHVyaW5nIGEgbWVhc3VyZW1lbnQgaW50ZXJ2YWwNSVBURG1pbiBpcyB0aGUgbWluaW11bSBJUFRE
IHJlY29yZGVkIGR1cmluZyBhIG1lYXN1cmVtZW50IGludGVydmFsDQ1TZXZlcmFsIHZhbHVlcyBv
ZiBJUERWIGFyZSBtZWFzdXJlZCBvdmVyIGEgbGFyZ2UgdGltZSBpbnRlcnZhbCwgY29tcHJpc2lu
ZyBvZiBzZXZlcmFsIHNob3J0IG1lYXN1cmVtZW50IGludGVydmFscy4gVGhlIDk1dGggcGVyY2Vu
dGlsZSBvZiB0aGVzZSBJUERWIHZhbHVlcyBpcyBleHBlY3RlZCB0byBtZWV0IGEgZGVzaXJlZCBv
YmplY3RpdmUuIFRoaXMgaXMgYSBzaW1wbGUgYW5kIGZhaXJseSBhY2N1cmF0ZSBtZXRob2QgZm9y
IGNhbGN1bGF0aW5nIElQRFYgaW4gcmVhbC10aW1lLiBUaGUgYWN0dWFsIHZhbHVlIG9mIHRoZSBt
ZWFzdXJlbWVudCBpbnRlcnZhbCBpcyBmb3IgZnVydGhlciBzdHVkeS4gVGhlIG1lYXN1cmVtZW50
IGludGVydmFsIGluZmx1ZW5jZXMgdGhlIGFiaWxpdHkgb2YgdGhlIG1ldHJpYyB0byBjYXB0dXJl
IGxvdyBhbmQgaGlnaCBmcmVxdWVuY3kgdmFyaWF0aW9ucyBpbiB0aGUgSVAgcGFja2V0IGRlbGF5
IGJlaGF2aW9yLg0NDUFwcGVuZGl4IElJSSANKEluZm9ybWF0aXZlKQ1FeGFtcGxlIEh5cG90aGV0
aWNhbCByZWZlcmVuY2UgcGF0aHMgZm9yIHZhbGlkYXRpbmcgdGhlIElQIHBlcmZvcm1hbmNlIG9i
amVjdGl2ZXMNVGhpcyBBcHBlbmRpeCBwcmVzZW50cyB0aGUgaHlwb3RoZXRpY2FsIHJlZmVyZW5j
ZSBwYXRocyBjb25zaWRlcmVkIGluIHZhbGlkYXRpbmcgdGhlIGZlYXNpYmlsaXR5IG9mIHRoZSBl
bmQtdG8tZW5kIHBlcmZvcm1hbmNlIG9iamVjdGl2ZXMgcHJlc2VudGVkIGluIGNsYXVzZSA1LiBU
aGVzZSBoeXBvdGhldGljYWwgcmVmZXJlbmNlIHBhdGhzIChIUlApIGFyZSBleGFtcGxlcyBvbmx5
LiBUaGUgbWF0ZXJpYWwgaW4gdGhpcyBBcHBlbmRpeCBpcyBub3Qgbm9ybWF0aXZlIGFuZCBkb2Vz
IG5vdCByZWNvbW1lbmQgb3IgYWR2b2NhdGUgYW55IHBhcnRpY3VsYXIgcGF0aCBhcmNoaXRlY3R1
cmVzLiANRWFjaCBwYWNrZXQgaW4gYSBmbG93IGZvbGxvd3MgYSBzcGVjaWZpYyBwYXRoLiAgQW55
IGZsb3cgKHdpdGggb25lIG9yIG1vcmUgcGFja2V0cyBvbiBhIHBhdGgpIHRoYXQgc2F0aXNmaWVz
IHRoZSBwZXJmb3JtYW5jZSBvYmplY3RpdmVzIG9mIGNsYXVzZSA1IGNhbiBiZSBjb25zaWRlcmVk
IGZ1bGx5IGNvbXBsaWFudCB3aXRoIHRoZSBub3JtYXRpdmUgcmVjb21tZW5kYXRpb25zIG9mIFku
MTU0MS4NVGhlIGVuZC10by1lbmQgcGVyZm9ybWFuY2Ugb2JqZWN0aXZlcyBhcmUgZGVmaW5lZCBm
b3IgdGhlIElQIHBlcmZvcm1hbmNlIHBhcmFtZXRlcnMgY29ycmVzcG9uZGluZyB0byB0aGUgSVAg
cGFja2V0IHRyYW5zZmVyIHJlZmVyZW5jZSBldmVudHMgKElQUkVzKS4gVGhlIGVuZC10by1lbmQg
SVAgbmV0d29yayBpbmNsdWRlcyB0aGUgc2V0IG9mIE5ldHdvcmsgU2VjdGlvbnMgKE5TKSBhbmQg
aW50ZXItbmV0d29yayBsaW5rcyB0aGF0IHByb3ZpZGUgdGhlIHRyYW5zcG9ydCBvZiBJUCBwYWNr
ZXRzIHRyYW5zbWl0dGVkIGZyb20gU1JDIHRvIERTVDsgdGhlIHByb3RvY29scyBiZWxvdyBhbmQg
aW5jbHVkaW5nIHRoZSBJUCBsYXllciAobGF5ZXIgMSB0byBsYXllciAzKSB3aXRoaW4gdGhlIFNS
QyBhbmQgRFNUIG1heSBhbHNvIGJlIGNvbnNpZGVyZWQgcGFydCBvZiBhbiBJUCBuZXR3b3JrLiAg
DQ1JSUkuMQlOdW1iZXIgSVAgbm9kZXMgaW4gdGhlIEhSUA1IUlBzIGhhdmUgc2ltaWxhciBhdHRy
aWJ1dGVzIHRvIHRoZSByZWZlcmVuY2UgcGF0aCBvZiBjbGF1c2UgNS4NTmV0d29yayBTZWN0aW9u
cyBtYXkgYmUgcmVwcmVzZW50ZWQgYXMgY2xvdWRzIHdpdGggR2F0ZXdheSByb3V0ZXJzIG9uIHRo
ZWlyIGVkZ2VzLCBhbmQgc29tZSBudW1iZXIgb2YgaW50ZXJpb3Igcm91dGVycyB3aXRoIHZhcmlv
dXMgcm9sZXMuICBJbiB0aGlzIGNhc2UsIEhSUHMgYXJlIGVxdWl2YWxlbnQgdG8gdGhlICJwYXRo
IGRpZ2VzdCIgb2YgUkZDIDIzMzAuDUVhY2ggTlMgbWF5IGJlIGNvbXBvc2VkIG9mIElQIE5vZGVz
IHBlcmZvcm1pbmcgQWNjZXNzLCBEaXN0cmlidXRpb24sIGFuZCBDb3JlIFJvbGVzLCBhcyBpbGx1
c3RyYXRlZCBiZWxvdy4NAQ1GaWd1cmUgEyBTRVEgRmlndXJlIFwqIEFSQUJJQyAUMxUgIFJvbGUg
b2YgSVAgTm9kZXMgaW4gYSBOZXR3b3JrIFNlY3Rpb24NTm90ZSB0aGF0IDEgb3IgbW9yZSByb3V0
ZXJzIGFyZSBuZWVkZWQgdG8gY29tcGxldGUgZWFjaCByb2xlLCBhbmQgdGhlIENvcmUgcGF0aCBp
bGx1c3RyYXRlZCBoYXMgZm91ciByb3V0ZXJzIGluIHRhbmRlbS4gIEEgcGF0aCB0aHJvdWdoIGEg
TlMgY291bGQgZW5jb3VudGVyIGFzIGZldyBhcyAzIHJvdXRlcnMsIG9yIGFzIG1hbnkgYXMgOCBp
biB0aGlzIGV4YW1wbGUuDVJvdXRlciBjb250cmlidXRpb24gdG8gdmFyaW91cyBwYXJhbWV0ZXJz
IG1heSB2YXJ5IGFjY29yZGluZyB0byB0aGVpciByb2xlLg1UYWJsZSATIFNFUSBUYWJsZSBcKiBB
UkFCSUMgFDEVICBFeGFtcGxlcyBvZiB0eXBpY2FsIGRlbGF5IGNvbnRyaWJ1dGlvbiBieSByb3V0
ZXIgcm9sZQ1Sb2xlB0F2ZXJhZ2UgVG90YWwgRGVsYXkNKHN1bSBvZiBxdWV1aW5nICYgcHJvY2Vz
c2luZykHRGVsYXkgVmFyaWF0aW9uBwdBY2Nlc3MgR2F0ZXdheQcxMCBtcwcxNiBtcwcHSW50ZXJu
ZXR3b3JraW5nIEdhdGV3YXkHMyBtcwczIG1zBwdEaXN0cmlidXRpb24HMyBtcwczIG1zBwdDb3Jl
BzIgbXMHMyBtcwcHTm90ZTogSW50ZXJuZXR3b3JraW5nIEdhdGV3YXlzIHR5cGljYWxseSBoYXZl
IHBlcmZvcm1hbmNlIGNoYXJhY3RlcmlzdGljcyBkaWZmZXJlbnQgdGhhbiBBY2Nlc3MgR2F0ZXdh
eXMuDU9uZSBvZiB0aGUga2V5IGFwcGxpY2F0aW9ucyBvZiB0aGlzIFJlY29tbWVuZGF0aW9uIGlz
IFZvaWNlIG92ZXIgSVAgc3VwcG9ydC4gDUZvciBleGFtcGxlLCBhIHRlbGVwaG9ueSBIeXBvdGhl
dGljYWwgUmVmZXJlbmNlIEVuZHBvaW50IChIUkUpIGZvciBtZWRpYSBtYXkgYmUgYXMgc2hvd24g
YmVsb3cuICBJbmZvcm1hdGlvbiBmbG93cyBmcm9tIHRoZSBUYWxrZXIgZG93biB0aHJvdWdoIHRo
ZSBwcm90b2NvbCBzdGFjayBvbiB0aGUgbGVmdCwgYWNyb3NzIHRoZSBIUlAsIGFuZCB1cCB0aGUg
cHJvdG9jb2wgc3RhY2sgb24gdGhlIHJpZ2h0IHRvIHRoZSBMaXN0ZW5lciAob25seSBvbmUgc2Vu
ZGluZyBkaXJlY3Rpb24gaXMgc2hvd24pLiAgDQ1UYWxrZXIHB0xpc3RlbmVyBwdHLjcxMSBjb2Rl
cgcHRy43MTEgZGVjb2RlciwgQXBwZW5kaXggSSAgUGFja2V0IExvc3MgQ29uY2VhbG1lbnQHB1JU
UCAyMG1zIHBheWxvYWQgc2l6ZQcHNjAgbXMgSml0dGVyIEJ1ZmZlcgcHVURQBwdVRFAHB0lQBwdJ
UAcHByhsb3dlciBsYXllcnMpBwcHRmlndXJlIBMgU0VRIEZpZ3VyZSBcKiBBUkFCSUMgFDQVIEV4
YW1wbGUgIEh5cG90aGV0aWNhbCBSZWZlcmVuY2UgRW5kcG9pbnQNDVJvdXRlIGxlbmd0aCBjYWxj
dWxhdGlvbg1JZiB0aGUgZGlzdGFuY2UtYmFzZWQgY29tcG9uZW50IGlzIHByb3BvcnRpb25hbCB0
byB0aGUgYWN0dWFsIHRlcnJlc3RyaWFsIGRpc3RhbmNlLCBwbHVzIGEgcHJvcG9ydGlvbmFsIGFs
bG93YW5jZSBmb3IgYSB0eXBpY2FsIHBoeXNpY2FsLXJvdXRlLXRvLWFjdHVhbC1kaXN0YW5jZSBy
YXRpby4gVGhlIHJvdXRlIGxlbmd0aCBjYWxjdWxhdGlvbiB1c2VkIGhlcmUgaXMgYmFzZWQgb24g
SVRVLVQgUmVjb21tZW5kYXRpb24gRy44MjYsIGFuZCBvbmx5IGZvciB0aGUgbG9uZyBkaXN0YW5j
ZXMgY29uc2lkZXJlZCBoZXJlLiBJZiBEa20gaXMgdGhlIGFpci1yb3V0ZSBkaXN0YW5jZSBiZXR3
ZWVuIHRoZSB0d28gTVBzIHRoYXQgYm91bmQgdGhlIHBvcnRpb24sIHRoZW4gdGhlIHJvdXRlIGxl
bmd0aCBjYWxjdWxhdGlvbiBpczoNlQlpZiBEa20gKCAxMjAwLCBSa22gKKAxLjI1ICggRGttDVRo
ZSBhYm92ZSBkb2VzIG5vdCBhcHBseSB3aGVuIHRoZSBwb3J0aW9uIGNvbnRhaW5zIGEgc2F0ZWxs
aXRlIGhvcC4NDUlJSS4yCUV4YW1wbGUgY29tcHV0YXRpb25zIHRvIHN1cHBvcnQgZW5kLWVuZCBD
bGFzcyAwIGFuZCBDbGFzcyAxIGRlbGF5DUNsYXNzIFggTmV0d29yayBEZWxheSBDb21wdXRhdGlv
biAoWD0gMCAgdGhyb3VnaCA0KQ1UaGlzIHNlY3Rpb24gY2FsY3VsYXRlcyB0aGUgSVBURCBmb3Ig
YW55IHBhdGggcG9ydGlvbiBzdXBwb3J0aW5nIGGgUU9TIGNsYXNzIFggZmxvdy4gV2hlbiBhIGZs
b3cgcG9ydGlvbiBkb2VzIG5vdCBjb250YWluIGEgc2F0ZWxsaXRlIGhvcCwgaXRzIGNvbXB1dGVk
IElQVEQgaXMgKHVzaW5nIHRoZSBkZWxheSBmb3Igb3B0aWNhbCB0cmFuc3BvcnQgZ2l2ZW4gaW4g
Ry4xMTQpOg1JUFREIChpbiBtaWNyb3NlY29uZHMpICggKFJrbSAoIDUpICsgKE5BICogREEpICsg
KE5EICogREQpICsgKE5DICogREMpICsgKE5JICogREkpDUluIHRoaXMgZm9ybXVsYToNlQlSa20g
cmVwcmVzZW50cyB0aGUgcm91dGUgbGVuZ3RoIGFzc3VtcHRpb24gY29tcHV0ZWQgYWJvdmUuDZUJ
KFJrbSAoIDUpIGlzIGFuIGFsbG93YW5jZSBmb3IgImRpc3RhbmNlIiB3aXRoaW4gdGhlIHBvcnRp
b24uDZUJTkEsIE5ELCBOQywgYW5kIE5JIHJlcHJlc2VudCB0aGUgbnVtYmVyIG9mIElQIGFjY2Vz
cyBnYXRld2F5LCBkaXN0cmlidXRpb24sIGNvcmUgYW5kIGludGVybmV0d29yayBnYXRld2F5IG5v
ZGVzIHJlc3BlY3RpdmVseTsgY29uc2lzdGVudCB3aXRoIHRoZSBuZXR3b3JrIHNlY3Rpb24gZXhh
bXBsZSBpbiBGaWd1cmUgMi4NlQlEQSwgREQsIERDLCBhbmQgTkkgcmVwcmVzZW50IHRoZSBkZWxh
eSBvZiBJUCBhY2Nlc3MgZ2F0ZXdheSwgZGlzdHJpYnV0aW9uLCBjb3JlIGFuZCBpbnRlcm5ldHdv
cmsgZ2F0ZXdheSBub2RlcyByZXNwZWN0aXZlbHk7IGNvbnNpc3RlbnQgd2l0aCBmb3IgdGhlIHZh
bHVlcyBmb3IgQ2xhc3MgWCAoZS5nLiwgVGFibGUgMSkuDU1heGltdW0gSVBEViBtYXkgYmUgY2Fs
Y3VsYXRlZCBzaW1pbGFybHkuDUFzIGFuIGV4YW1wbGUgb2YgdGhpcyBjYWxjdWxhdGlvbiwgY29u
c2lkZXIgdGhlIGZvbGxvd2luZyBIUlAuICBUaGlzIHBhdGggY29udGFpbnMgdGhlIG1pbmltdW0g
bnVtYmVyIG9mIElQIG5ldHdvcmtzICh0d28pLCBhbmQgYW4gaW50ZXJuZXR3b3JraW5nIHBvaW50
Lg0BDUZpZ3VyZSATIFNFUSBGaWd1cmUgXCogQVJBQklDIBQ1FSAgSHlwb3RoZXRpY2FsIFJlZmVy
ZW5jZSBQYXRoIGZvciBRb1MgQ2xhc3MgMA1JbnRlcmlvciByb3V0ZXIgY29uZmlndXJhdGlvbnMg
YXJlIG5vdCBzaG93biBpbiB0aGUgSHlwb3RoZXRpY2FsIFJlZmVyZW5jZSBQYXRoIChIUlApIG9m
IEZpZ3VyZSA0LiAgVGhlIG51bWJlciBvZiBDb3JlIGFuZCBEaXN0cmlidXRpb24gcm91dGVycyBj
YW4gYmUgZm91bmQgaW4gVGFibGUgMi4NQXNzdW1wdGlvbnM6DURpc3RhbmNlIHVzZWQgaXMgYXBw
cm94aW1hdGVseSB0aGUgc3BhbiBiZXR3ZWVuIERheXRvbmEgQmVhY2ggYW5kIFNlYXR0bGUgKFVT
IERpYWdvbmFsLCBsb25nZXIgdGhhbiBMaXNib24gdG8gTW9zY293KS4NQWNjZXNzIGxpbmtzIGFy
ZSBUMSBjYXBhY2l0eSwgb3RoZXJzIGFyZSBsYXJnZXIgdGhhbiBUMSAoZS5nLiwgT0MtMykuDUxh
cmdlc3QgUGFja2V0IFNpemUgaXMgMTUwMCBieXRlcywgYW5kIFZvSVAgcGFja2V0IHNpemUgaXMg
MjAwIGJ5dGVzLiANTm9uLUlQIG5ldHdvcmtzIGFyZSBuZWVkZWQgYmV0d2VlbiB0aGUgTkkgYW5k
IEFjY2VzcyBHVy4NDA1UYWJsZSATIFNFUSBUYWJsZSBcKiBBUkFCSUMgFDIVIEFuYWx5c2lzIG9m
IEV4YW1wbGUgQ2xhc3MgMCBQYXRoDUVsZW1lbnQHBwdBdmUgSVBURAcHB01heCBJUERWBwdEaXN0
YW5jZQc0MDcwB2ttBwcHBwcHUm91dGUHNTA4Ny41B2ttBzI1BwcHBwcHBwcHBwcHB0luc2VydGlv
biBUaW1lBzIwMAdieXRlcwcxBzE1MDAHYnl0ZXMsIDhtcwcHBwcHBwcHBwcHTm9uIElQIE5ldCAx
BwcHMTUHBwcwBwcHBwcHBwcHB0lQIE5ldCAxB04HSVBURCBlYWNoBwcHVmFyIGVhY2gHBwdBY2Nl
c3MsIE5BBzEHMTAHMTAHBzE2BzE2BwdEaXN0cmlidXRpb24sIE5EBzEHMwczBwczBzMHB0NvcmUs
IE5DBzIHMgc0BwczBzYHB0ludGVybmV0d29yayBHVywgTkkHMQczBzMHBzMHMwcHBwcHBwcHBwdJ
UCBOZXQgMgdOB0lQVEQgZWFjaAcHB1ZhciBlYWNoBwcHQWNjZXNzLCBOQQcxBzEwBzEwBwcxNgcx
NgcHRGlzdHJpYnV0aW9uLCBORAcxBzMHMwcHMwczBwdDb3JlLCBOQwc0BzIHOAcHMwcxMgcHSW50
ZXJuZXR3b3JrIEdXLCBOSQcxBzMHMwcHMwczBwcHBwcHBwcHB05vbiBJUCBOZXQgMgcHBzE1BwcH
MAcHBwcHBwcHBwdUb3RhbCwgbXMHBwcxMDAHBwc2MgcHDVRhYmxlIDIgZ2l2ZXMgdGhlIEhSUCBj
b25maWd1cmF0aW9uIGluIHRlcm1zIG9mIG51bWJlciBhbmQgdHlwZSBvZiByb3V0ZXJzLCBkaXN0
YW5jZSwgYW5kIGNvbnRyaWJ1dGlvbiBvZiBhbGwgSFJQIGNvbXBvbmVudHMgdG8gZGVsYXkgKElQ
VEQpIGFuZCBkZWxheSB2YXJpYXRpb24gKElQRFYpLiBOb3RlIHRoYXQgdGhlIGNhbGN1bGF0aW9u
IG9mIE1heGltdW0gSVBEViBoZXJlIGlzIHZlcnkgcGVzc2ltaXN0aWMgKGFzc3VtaW5nIHdvcnN0
IGNhc2UgYWRkaXRpb24gb2YgZWFjaCBub2RlKSwgYW5kIGlzIHRoZXJlZm9yZSBncmVhdGVyIHRo
YW4gdGhlIHNwZWNpZmljYXRpb24gb2YgSVBEViBpbiB0aGUgYm9keSBvZiB0aGlzIFJlY29tbWVu
ZGF0aW9uLg1BIEhSUCB3aXRoIDEyMDAwIGttIGFpciBkaXN0YW5jZSBiZXR3ZWVuIHNvdXJjZSBh
bmQgZGVzdGluYXRpb24gKGVxdWl2YWxlbnQgdG8gY29udGluZW50YWwgVS5TLiBkaWFnb25hbCBk
aXN0YW5jZSkgY2FuIHByb2R1Y2UgYXZlcmFnZSBJUFREIG9mIDE1MCBtcyAsIGJ1dCB0aGUgSVBE
ViBvbiB0aGlzIHBhdGggd2lsbCBub3QgY2hhbmdlLiANVXNpbmcgdGhlIEh5cG90aGV0aWNhbCBS
ZWZlcmVuY2UgRW5kcG9pbnQgaW4gRmlndXJlIDQsIGVuZHBvaW50IGRlbGF5IGlzIGFzIGJlbG93
Lg0NVGFibGUgEyBTRVEgVGFibGUgXCogQVJBQklDIBQzFSBFbmRwb2ludCBEZWxheSBBbmFseXNp
cw0HRGVsYXksIG1zB05vdGVzBwdQYWNrZXQgRm9ybWF0aW9uBzQwBzIgdGltZXMgZnJhbWUgc2l6
ZSBwbHVzIDAgbG9vay1haGVhZAcHSml0dGVyIEJ1ZmZlciwgYXZlLgczMAdjZW50ZXIgb2YgNjBt
cyBidWZmZXIHB1BhY2tldCBMb3NzIENvbmNlYWwuBzEwB29uZSBQTEMgImZyYW1lIgcHBwcHB1Rv
dGFsLCBtcwc4MAcHBw1UaGUgdG90YWwgYXZlcmFnZSBkZWxheSBmb3IgdGhlIDQwNzAga20gdXNl
ci10by11c2VyIHBhdGggaXMgMTAwKzgwPTE4MCBtcywgcmVzdWx0aW5nIGluIGFuIGFwcHJveGlt
YXRlIFItdmFsdWUgb2YgODcgKGFzc3VtaW5nIHRoYXQgSVBMUjwxMC0zIGhhcyB6ZXJvIGltcGFp
cm1lbnQgZmFjdG9yIHdpdGggRy43MTEgQXBwZW5kaXggSSBjb25jZWFsbWVudCkuIFRoZSBIUlAg
c3VwcG9ydHMgdGhlIEhpZ2ggc3BlZWNoIHF1YWxpdHkgY2F0ZWdvcnkgb2YgRy4xMDkgKDkwPlIo
ODAsIGVxdWFsIHRvIHRoZSB0cmFuc21pc3Npb24gcXVhbGl0eSBSLWZhY3RvciByZXF1aXJlbWVu
dCBpbiB0aGUgVElQSE9OIEd1YXJhbnRlZWQgKEhpZ2gpIHNwZWVjaCBRb1MgQ2xhc3MuIEcuMTc3
IGlsbHVzdHJhdGVzIHRoZSB0cmFkZW9mZiBiZXR3ZWVuIHNwZWVjaCBjb2RlYyBpbXBhaXJtZW50
cyBhbmQgZGVsYXkpLiBVc2luZyB0aGUgMTIwMDBrbSBIUlAgd2l0aCBJUFREIG9mIDE1MCBtcywg
YW4gYXBwcm94aW1hdGUgUi12YWx1ZSBvZiA4MyBpcyBwb3NzaWJsZSB1bmRlciB0aGUgc2FtZSBh
c3N1bXB0aW9ucy4NQSA1MG1zIEN1c3RvbWVyIEluc3RhbGxhdGlvbiAoMS13YXkgc2VuZCBhbmQg
cmVjZWl2ZSkgaXMgcG9zc2libGUgd2l0aCBhIHBhY2tldCBmb3JtYXRpb24gdGltZSBvZiAxMCBt
cyBhbmQgYSA1MCBtcyBkZS1qaXR0ZXIgYnVmZmVyLiBUaGUgQ2xhc3MgMCBwYXRoIElQVEQgYW5k
IEN1c3RvbWVyIEluc3RhbGxhdGlvbiBkZWxheXMgc3VtIHRvIGEgMS13YXkgbW91dGgtdG8tZWFy
IHRyYW5zbWlzc2lvbiB0aW1lIG9mIDE1MCBtcywgc2F0aXNmeWluZyB0aGUgbmVlZHMgb2YgbW9z
dCBhcHBsaWNhdGlvbnMgKGFzIHBlciBHLjExNCksIGFuZCBwcm9kdWNlcyBhbiBFIG1vZGVsIFIt
dmFsdWUgb2YgYXBwcm94aW1hdGVseSA5MC4NDQdEZWxheSwgbXMHTm90ZXMHB1BhY2tldCBGb3Jt
YXRpb24HMjAHMiB0aW1lcyBmcmFtZSBzaXplIHBsdXMgMCBsb29rLWFoZWFkBwdEZS1KaXR0ZXIg
QnVmZmVyLCBhdmUuBzI1B2NlbnRlciBvZiA1MG1zIGJ1ZmZlcgcHUGFja2V0IExvc3MgQ29uY2Vh
bC4HMAeTUmVwZWF0IFByZXZpb3VzlCByZXF1aXJlcyBubyBhZGRpdGlvbmFsIGRlbGF5IAcHT3Ro
ZXIgRXF1aXBtZW50BzUHBwdUb3RhbCwgbXMHNTAHBwcNDUlJSS4zCUVYQU1QTEUgRU5ELUVORCBD
TEFTUyAxIERFTEFZIENPTVBVVEFUSU9ODUNsYXNzIDEgaXMgYXZhaWxhYmxlIHRvIHN1cHBvcnQg
bG9uZ2VyIHBhdGggbGVuZ3RocyBhbmQgbW9yZSBjb21wbGV4IG5ldHdvcmsgcGF0aHMuIEluIHRo
aXMgZXhhbXBsZSwgd2UgYWRkIGEgdHJhbnNpdCBJUCBOZXR3b3JrIFNlY3Rpb24sIGZvciBhIHRv
dGFsIG9mIDMgTlMuDVRhYmxlIBMgU0VRIFRhYmxlIFwqIEFSQUJJQyAUNBUgIEV4YW1wbGUgQ2Fs
Y3VsYXRpb24gZm9yIENsYXNzIDEgUGF0aA1FbGVtZW50BwcHQXZlIElQRFQHBwdNYXggSVBEVgcH
RGlzdGFuY2UHB2ttBwcHBwcHUm91dGUHMjc1MDAHa20HMTM4BwcHBwcHBwcHBwcHB0luc2VydGlv
biBUaW1lBzIwMAdieXRlcwcxBzE1MDAHQnl0ZXMsIDggbXMHBwcHBwcHBwcHB05vbiBJUCBOZXQg
MQcHBzE1BwcHMAcHBwcHBwcHBwdJUCBOZXQgMQdOB0lQRFQgZWFjaAcHB1ZhciBlYWNoBwcHQWNj
ZXNzLCBOQQcxBzEwBzEwBwcxNgcxNgcHRGlzdHJpYnV0aW9uLCBORAcxBzMHMwcHMwczBwdDb3Jl
LCBOQwcyBzIHNAcHMwc2BwdJbnRlcm5ldHdvcmsgR1csIE5JBzEHMwczBwczBzMHBwcHBwcHBwcH
SVAgTmV0IDIHTgdJUERUIGVhY2gHBwdWYXIgZWFjaAcHB0Rpc3RyaWJ1dGlvbiwgTkQHMgczBzYH
BzMHNgcHQ29yZSwgTkMHNAcyBzgHBzMHMTIHB0ludGVybmV0d29yayBHVywgTkkHMgczBzYHBzMH
NgcHBwcHBwcHBwdJUCBOZXQgMwdOB0lQRFQgZWFjaAcHB1ZhciBlYWNoBwcHQWNjZXNzLCBOQQcx
BzEwBzEwBwcxNgcxNgcHRGlzdHJpYnV0aW9uLCBORAcxBzMHMwcHMwczBwdDb3JlLCBOQwc0BzIH
OAcHMwcxMgcHSW50ZXJuZXR3b3JrIEdXLCBOSQcxBzMHMwcHMwczBwcHBwcHBwcHB05vbiBJUCBO
ZXQgMgcHBzE1BwcHMAcHBwcHBwcHBwcHBwcHBwcHB1RvdGFsLCBtcwcHBzIzMwcHBzg2BwdUYWJs
ZSA0IGdpdmVzIHRoZSBIUlAgY29uZmlndXJhdGlvbiBpbiB0ZXJtcyBvZiBudW1iZXIgYW5kIHR5
cGUgb2Ygcm91dGVycywgZGlzdGFuY2UsIGFuZCBjb250cmlidXRpb24gb2YgYWxsIEhSUCBjb21w
b25lbnRzIHRvIGRlbGF5IChJUFREKSBhbmQgZGVsYXkgdmFyaWF0aW9uIChJUERWKS4NDUlJSS40
CUV4YW1wbGUgY29tcHV0YXRpb25zIHRvIHN1cHBvcnQgZW5kLWVuZCBDbGFzcyA0IGRlbGF5IA1G
b2xsb3dpbmcgdGhlIGZvcm0gb2YgdGhlIGNhbGN1bGF0aW9uIGFib3ZlLCB3ZSBjYW4gZXhwYW5k
IHRoZSBudW1iZXIgb2YgTlMgaGF2aW5nIGRlbGF5IGNvbnRyaWJ1dGlvbnMgZ2l2ZW4gaW4gVGFi
bGUgMS9JSUksIG9yIHdlIGNhbiBleHBhbmQgdGhlIGNvbnRyaWJ1dGlvbnMgYXMgZm9sbG93czoN
VGFibGUgEyBTRVEgVGFibGUgXCogQVJBQklDIBQ1FSAgQ2xhc3MgNCBEZWxheSBjb250cmlidXRp
b24gYnkgcm91dGVyIHJvbGUNUm9sZQdBdmVyYWdlIFRvdGFsIERlbGF5DShzdW0gb2YgcXVldWlu
ZyAmIHByb2Nlc3NpbmcpBwdBY2Nlc3MgR2F0ZXdheQcyMDAgbXMHB0ludGVybmV0d29ya2luZyBH
YXRld2F5BzY0IG1zBwdEaXN0cmlidXRpb24HNjQgbXMHB0NvcmUHMyBtcwcHDUhlcmUsIHdpdGgg
YSByb3V0ZSBsZW5ndGggb2YgMjcsNTAwIGttLCB0aGUgYXZlcmFnZSAxLXdheSBkZWxheSB3b3Vs
ZCBiZSA4ODQgbXMgKHVzaW5nIHRoZSBIUlAgd2l0aCBub2RlIGNvbmZpZ3VyYXRpb24gYXMgZGVz
Y3JpYmVkIGluIFRhYmxlIDIvSUlJKS4NDUlJSS41CUxvYWRpbmcgd2l0aGluIHRoZSBIUlANVGhl
IGZyYWN0aW9uIG9mIGVhY2ggdHJhbnNtaXNzaW9uIGxpbmsgb2NjdXBpZWQgYnkgYWN0aXZlIHBh
Y2tldHMgaXMgb25lIG9mIHRoZSBmYWN0b3JzIHRvIGJlIGNvbnNpZGVyZWQgaW4gdGhlIEhSUHMu
IFRoZSBsb2FkIGxldmVscyBhdCB3aGljaCB0aGUgbmV0d29yayB3aWxsIGNvbnRpbnVvdXNseSBv
cGVyYXRlIGlzIGFub3RoZXIgZmFjdG9yLg1JSUkuNglHZW9zdGF0aW9uYXJ5IHNhdGVsbGl0ZXMg
d2l0aGluIHRoZSBIUlANVGhlIHVzZSBvZiBnZW8tc3RhdGlvbmFyeSBzYXRlbGxpdGVzIHdhcyBj
b25zaWRlcmVkIGR1cmluZyB0aGUgc3R1ZHkgb2YgdGhlIEhSUHMuIEEgc2luZ2xlIGdlby1zdGF0
aW9uYXJ5IHNhdGVsbGl0ZSBjYW4gYmUgdXNlZCB3aXRoaW4gdGhlIEhSUHMgYW5kIHN0aWxsIGFj
aGlldmUgZW5kLXRvLWVuZCBvYmplY3RpdmVzIG9uIHRoZSBhc3N1bXB0aW9uIHRoYXQgaXQgcmVw
bGFjZXMgc2lnbmlmaWNhbnQgdGVycmVzdHJpYWwgZGlzdGFuY2UsIG11bHRpcGxlIElQIG5vZGVz
LCBhbmQvb3IgdHJhbnNpdCBuZXR3b3JrIHNlY3Rpb25zLg1UaGUgdXNlIG9mIGxvdy0gYW5kIG1l
ZGl1bS0gRWFydGggb3JiaXQgc2F0ZWxsaXRlcyB3YXMgbm90IGNvbnNpZGVyZWQgaW4gY29ubmVj
dGlvbiB3aXRoIHRoZXNlIEhSUHMuDVdoZW4gYSBwYXRoIGNvbnRhaW5zIGEgc2F0ZWxsaXRlIGhv
cCwgdGhpcyBwb3J0aW9uIHdpbGwgcmVxdWlyZSBhbiBJUFREIG9mIDMyMCBtcywgdG8gYWNjb3Vu
dCBmb3IgbG93IGVhcnRoIHN0YXRpb24gdmlld2luZyBhbmdsZSwgbG93IHJhdGUgVERNQSBzeXN0
ZW1zLCBvciBib3RoLiBJbiB0aGUgY2FzZSBvZiBhIHNhdGVsbGl0ZSBwb3NzZXNzaW5nIG9uLWJv
YXJkIHByb2Nlc3NpbmcgY2FwYWJpbGl0aWVzLCAzMzAgbXMgb2YgSVBURCBpcyBuZWVkZWQsIHRv
IGFjY291bnQgZm9yIG9uLWJvYXJkIHByb2Nlc3NpbmcgYW5kIHBhY2tldCBxdWV1aW5nIGRlbGF5
cy4gIA1JdCBpcyBleHBlY3RlZCB0aGF0IG1vc3QgSFJQcyB3aGljaCBpbmNsdWRlIGEgZ2VvLXN0
YXRpb25hcnkgc2F0ZWxsaXRlIHdpbGwgYWNoaWV2ZSBJUFREIGJlbG93IDQwMCBtcy4gSG93ZXZl
ciwgaW4gc29tZSBjYXNlcyB0aGUgdmFsdWUgb2YgNDAwIG1zIG1heSBiZSBleGNlZWRlZC4gRm9y
IHZlcnkgbG9uZyBwYXRocyB0byByZW1vdGUgYXJlYXMsIG5ldHdvcmsgcHJvdmlkZXJzIG1heSBu
ZWVkIHRvIG1ha2UgYWRkaXRpb25hbCBiaWxhdGVyYWwgYWdyZWVtZW50cyB0byBpbXByb3ZlIHRo
ZSBwcm9iYWJpbGl0eSBvZiBhY2hpZXZpbmcgdGhlIDQwMCBtcyBvYmplY3RpdmUuDQ0NDEFQUEVO
RElYIElWDShJbmZvcm1hdGl2ZSkNRXhhbXBsZSBDYWxjdWxhdGlvbnMgb2YgSVAgUGFja2V0IERl
bGF5IFZhcmlhdGlvbiANVGhpcyBhcHBlbmRpeCBwcm92aWRlcyBtYXRlcmlhbCB0byBmYWNpbGl0
YXRlIHRoZSBjYWxjdWxhdGlvbiBvZiB0aGUgSVAgcGFja2V0IGRlbGF5IHZhcmlhdGlvbiAoSVBE
VikgZm9yIHRob3NlIElQIFFvUyBjbGFzc2VzIHdoZXJlIGEgcmF0aGVyIHN0cmljdCB2YWx1ZSBm
b3IgdGhlIElQRFYgaXMgc3BlY2lmaWVkLCBpLmUuIElQIFFvUyBjbGFzc6AwIGFuZCBjbGFzc6Ax
LiANRm9yIHRoZSBjYWxjdWxhdGlvbnMgaGVyZSBpdCBpcyBhc3N1bWVkIHRoYXQgYSBuZXR3b3Jr
IG9wZXJhdG9yIHByb3ZpZGVzIGEgY2hvaWNlIG9mIGRpZmZlcmVudCBJUCBRb1MgY2xhc3NlcyBh
bHNvIGluY2x1ZGluZyBRb1MgY2xhc3NlcyBmb3Igd2hpY2ggbm8gSVBEViBvYmplY3RpdmVzIGFy
ZSBzcGVjaWZpZWQuIFRoaXMgbWl4IG9mIHByb3BlcnRpZXMgbW90aXZhdGVzIHRoZSBub3Rpb24g
b2Ygk2RlbGF5IHZhcmlhdGlvbi1zZW5zaXRpdmWUIGZsb3dzIChlLmcuIFFvUyBjbGFzc6AwIGFu
ZCBjbGFzc6AxKSBhbmQgIJNkZWxheSB2YXJpYXRpb24taW5zZW5zaXRpdmWUIGZsb3dzIChlLmcu
IFFvUyBjbGFzc2VzoDIsIDMsIDQsIGFuZCA1KS4gSXQgaXMgZnVydGhlciBhc3N1bWVkIHRoYXQg
YW4gb3BlcmF0b3IgcHJvdmlkaW5nIHN1Y2ggYSBtaXggb2YgUW9TIGNsYXNzZXMsIGRvZXMgYSBy
ZWFzb25hYmxlIGVmZm9ydCB0byBzZXBhcmF0ZSB0aGUgdmFyaWF0aW9uLXNlbnNpdGl2ZSBmcm9t
IHRoZSB2YXJpYXRpb24taW5zZW5zaXRpdmUgZmxvd3MuIEtleSBlbGVtZW50cyBpbiBzdWNoIGFu
IGVmZm9ydCBjb25zaXN0IGluIGEgcGFja2V0IHNjaGVkdWxpbmcgc3RyYXRlZ3kgYW5kIGFkZGl0
aW9uYWwgdHJhZmZpYyBjb250cm9sIG1lYXN1cmVzLiBGb3IgdGhlIGNhbGN1bGF0aW9ucyBpbiB0
aGlzIEFwcGVuZGl4IGl0IGlzIGFzc3VtZWQgdGhhdCBwYWNrZXRzIG9mIHZhcmlhdGlvbi1zZW5z
aXRpdmUgZmxvd3MgYXJlIHNjaGVkdWxlZCB3aXRoIG5vbi1wcmUtZW1wdGl2ZSBwcmlvcml0eSBv
dmVyIHBhY2tldHMgZnJvbSB2YXJpYXRpb24taW5zZW5zaXRpdmUgZmxvd3MgYW5kIHRoYXQgdGhl
IHNjaGVkdWxpbmcgd2l0aGluIGVhY2ggb2YgdGhlc2UgdHdvIGNhdGVnb3JpZXMgaXMgRklGTy4g
DU5vdGUuCVRoaXMgc2ltcGxlIGFzc3VtcHRpb24gb25seSBzZXJ2ZXMgdGhlIHB1cnBvc2UgdG8g
YXJyaXZlIGF0IGEgkWNhbGN1bGFibGWSIG1vZGVsLiBPdGhlciBwYWNrZXQgc2NoZWR1bGluZyBz
dHJhdGVnaWVzIChzdWNoIGFzIFdlaWdodGVkIEZhaXIgUXVldWluZykgb3IgdHJhZmZpYyBjb250
cm9sIG1lYXN1cmVzIGFyZSBub3QgZXhjbHVkZWQuIEl0IGlzIGZ1cnRoZXIgYXNzdW1lZCB0aGF0
IHRoZSBwZXJmb3JtYW5jZSBvZiBvdGhlciBhcHByb2FjaGVzIGlzIGVpdGhlciBiZXR0ZXIgb3Ig
bm90IG11Y2ggd29yc2UgdGhhbiB0aGUgcGVyZm9ybWFuY2Ugb2YgdGhlIGFwcHJvYWNoIHVzZWQg
Zm9yIHRoZXNlIGNhbGN1bGF0aW9ucy4gDUlWLjEJQ29udHJpYnV0b3JzIHRvIElQIHBhY2tldCBk
ZWxheSB2YXJpYXRpb24NVGhlIGZvbGxvd2luZyBmYWN0b3JzIGFyZSB0YWtlbiBpbnRvIGFjY291
bnQgYXMgdGhlIG1vc3Qgc2lnbmlmaWNhbnQgY29udHJpYnV0b3JzIHRvIElQIHBhY2tldCBkZWxh
eSB2YXJpYXRpb24gKElQRFYpIGZvciB0aGUgdmFyaWF0aW9uLXNlbnNpdGl2ZSBmbG93cy4NVmFy
aWFibGUgZGVsYXkgYmVjYXVzZSB0aGUgcHJvY2Vzc2luZyBkZWxheSBmb3IgdGhlIHBhY2tldJJz
IGZvcndhcmRpbmcgZGVjaXNpb24gKHJvdXRpbmcgbG9vax51cCkgaXMgbm90IGEgc2luZ2xlIGZp
eGVkIHZhbHVlIGJ1dCBtYXkgdmFyeSBmcm9tIHBhY2tldCB0byBwYWNrZXQuIA1WYXJpYWJsZSBk
ZWxheSBiZWNhdXNlIHRoZSBwYWNrZXQgaGFzIHRvIHdhaXQgYmVoaW5kIG90aGVyIHZhcmlhdGlv
bi1zZW5zaXRpdmUgcGFja2V0cyB3aGljaCBhcnJpdmVkIGVhcmxpZXIuDVZhcmlhYmxlIGRlbGF5
IGJlY2F1c2UgdGhlIHBhY2tldCBoYXMgdG8gd2FpdCBmb3IgdGhlIHNlcnZpY2UgY29tcGxldGlv
biBvZiBhIHZhcmlhdGlvbi1pbnNlbnNpdGl2ZSBwYWNrZXQgd2hpY2ggYXJyaXZlZCBlYXJsaWVy
IGFuZCBpcyBhbHJlYWR5IGluIHNlcnZpY2UuIA1JVi4yCU1vZGVscyBhbmQgY2FsY3VsYXRpb24g
cHJvY2VkdXJlcyB0byBlc3RhYmxpc2ggYW4gdXBwZXIgYm91bmQgdG8gdGhlIElQRFYNSVYuMi4x
CURlbGF5IHZhcmlhdGlvbiBkdWUgdG8gcm91dGluZyBsb29rLXVwDUZvciBhbiBhcnJpdmluZyBw
YWNrZXQsIHRoZSByb3V0ZXIgbmVlZHMgdG8gZXN0YWJsaXNoLCBiYXNlZCBvbiB0aGUgSVAgYWRk
cmVzcywgdGhlIG91dGdvaW5nIHBvcnQgdG8gd2hpY2ggdGhlIHBhY2tldCBpcyB0byBiZSBmb3J3
YXJkZWQuIFRoZSB0aW1lIHJlcXVpcmVkIGZvciB0aGlzIGZvcndhcmRpbmcgZGVjaXNpb24gbWF5
IHZhcnkgZnJvbSBwYWNrZXQgdG8gcGFja2V0LiANSGlnaCBwZXJmb3JtYW5jZSByb3V0ZXJzIG1h
eSBjYWNoZSByZWNlbnRseSB1c2VkIElQIGFkZHJlc3NlcyB0byBzcGVlZC11cCB0aGlzIHByb2Nl
c3MgZm9yIHN1YnNlcXVlbnQgcGFja2V0cy4gVGhlbiwgYWxsIHBhY2tldHMgb2YgYSBmbG93LCBl
eGNlcHQgdGhlIGZpcnN0IG9uZSwgYXJlIGV4cGVjdGVkIHRvIGV4cGVyaWVuY2UgYSBzaG9ydCBs
b29rLXVwIGRlbGF5IGFuZCB2ZXJ5IHNtYWxsIHZhcmlhdGlvbiBiZXR3ZWVuIHRoZW0uIFRob3Vn
aCwgc3RyaWN0bHksIHRoZSBsb25nZXIgZGVsYXkgb2YgdGhlIGZpcnN0IHBhY2tldCBjb250cmli
dXRlcyB0byB0aGUgSVBEViwgdGhlIGV4Y2VwdGlvbmFsIGRlbGF5IG9mIHRoZSBmaXJzdCBwYWNr
ZXQgaXMgZGlzcmVnYXJkZWQgaW4gdGhlc2UgY2FsY3VsYXRpb25zIGJlY2F1c2UgaXQgaXMgYSCR
b25lIG9mZpIgZXZlbnQgYW5kIGl0cyBlZmZlY3Qgd2lsbCB2YW5pc2ggaW4gZmxvd3Mgd2l0aCBh
IHJlbGF0aXZlIGxvbmcgZHVyYXRpb24gKGUuZy4gYSBWb0lQIGZsb3cpLiANSXQgaXMgZXhwZWN0
ZWQgdGhhdCB0aGUgcGFja2V0LXRvLXBhY2tldCB2YXJpYXRpb24gaW4gdGhlIHJvdXRpbmcgbG9v
ay11cCBkZWxheSBpcyBub3QgbW9yZSB0aGFuIGEgZmV3IHRlbnMgb2YgbWljcm9zZWNvbmRzIGlu
IGVhY2ggcm91dGVyLiBGb3IgdGhlIGNhbGN1bGF0aW9ucyB0aGUgdmFyaWFiaWxpdHkgaXMgYXNz
dW1lZCB0byBiZSBsZXNzIHRoYW4gMzCgKHMgcGVyIHJvdXRlci4gDUJlY2F1c2UgdGhlcmUgaXMg
bGl0dGxlIGluZm9ybWF0aW9uIGF2YWlsYWJsZSBhYm91dCB0aGUgZGlzdHJpYnV0aW9uIG9mIHRo
aXMgZGVsYXkgY29tcG9uZW50LCB0aGUgYWdncmVnYXRlZCB2YXJpYWJpbGl0eSBvdmVyIHNldmVy
YWwgcm91dGVycyBpbiB0YW5kZW0gaXMgc2V0IHRvIHRoZSBzdW0gb2YgdGhlIGluZGl2aWR1YWwg
dmFyaWFiaWxpdGllcywgaS5lLiBzdGF0aXN0aWNhbCBlZmZlY3RzIGFyZSBub3QgdGFrZW4gaW50
byBhY2NvdW50IGZvciB0aGlzIElQRFYgY29tcG9uZW50LiANSVYuMi4yCURlbGF5IHZhcmlhdGlv
biBkdWUgdG8gdmFyaWF0aW9uLXNlbnNpdGl2ZSBwYWNrZXRzDUEgdmFyaWF0aW9uLXNlbnNpdGl2
ZSBwYWNrZXQgd2lsbCBoYXZlIHRvIHdhaXQgZm9yIG90aGVyIHZhcmlhdGlvbi1zZW5zaXRpdmUg
cGFja2V0cyB0byBiZSBzZXJ2aWNlZCB3aGljaCBhcnJpdmVkIGVhcmxpZXIgKEZJRk8gZGlzY2lw
bGluZSkuIEVhY2ggdmFyaWF0aW9uLXNlbnNpdGl2ZSBmbG93IGlzIG1vZGVsbGVkIGFzIGEgY29u
dGludW91cyBmbG93IG9mIHBhY2tldHMgd2l0aCBuZWdsaWdpYmxlIDEecG9pbnQgSVAgcGFja2V0
IGRlbGF5IHZhcmlhdGlvbiwgY29tcGFyYWJsZSB0byB0aGUgY29uY2VwdCBvZiCRbmVnbGlnaWJs
ZSBDRFaSIHVzZWQgZm9yIGFuIENCUiBzdHJlYW0gb2YgQVRNIGNlbGxzIChzZWUgUmVjb21tZW5k
YXRpb24gRS43MzYpLiANRm9yIHRoZSBjYWxjdWxhdGlvbnMgaXQgaXMgZnVydGhlciBhc3N1bWVk
IHRoYXQgYWxsIHZhcmlhdGlvbi1zZW5zaXRpdmUgcGFja2V0cyBoYXZlIGEgZml4ZWQgc2l6ZSBv
ZiAxNTAwoGJ5dGUuIFRoaXMgYWxsb3dzIHRvIGFwcGx5IHRoZSB3ZWxsLWtub3duIE0vRC8xIHF1
ZXVpbmcgbW9kZWwgKHNlZSBSZWNvbW1lbmRhdGlvbiBFLjczNikgZm9yIHRoZSBjYWxjdWxhdGlv
biBvZiB0aGlzIGNvbXBvbmVudCBpbiB0aGUgcGFja2V0IGRlbGF5IHZhcmlhdGlvbi4gVGhlIGZp
eGVkIHNlcnZpY2UgdGltZSBpcyBkZXRlcm1pbmVkIGJ5IHRoZSBhc3N1bWVkIGZpeGVkIHBhY2tl
dCBzaXplICgxNTAwoGJ5dGUpIGFuZCB0aGUgcm91dGVyknMgb3V0cHV0IGxpbmsgcmF0ZSwgZS5n
LiA4MC4xM6AocyBvbiBhbiBTVE0eMSBsaW5rLiANRm9yIHRoZSBhZ2dyZWdhdGlvbiBvZiB0aGlz
IGRlbGF5IGNvbXBvbmVudCBvdmVyIHNldmVyYWwgcm91dGVycyBpbiB0YW5kZW0sIHRoZSBjb252
b2x1dGlvbiBvZiB0aGUgcmVsZXZhbnQgZGVsYXkgZGlzdHJpYnV0aW9ucyBpcyB0byBiZSB1c2Vk
LCB0YWtpbmcgaW50byBhY2NvdW50IGRpZmZlcmVudCBvdXRwdXQgbGluayByYXRlcyB3aGVuIGFw
cGxpY2FibGUuIFRoZSBsb3dlciBxdWFudGlsZSBpcyBhc3N1bWVkIHRvIGJlIHplcm8sIHRoZSBo
aWdoZXIgKDEeMTAeMykgcXVhbnRpbGUgY2FuIGJlIGFwcHJveGltYXRlZCBhY2N1cmF0ZWx5IHVz
aW5nIGxhcmdlIGRldmlhdGlvbnMgdGhlb3J5LCBpbiBwYXJ0aWN1bGFyIHRoZSBCYWhhZHVyLVJh
byBlc3RpbWF0ZSBhcyB3b3JrZWQgb3V0IGluoFtJRklQXS4gDUZpZ3VyZSBJVi4xIGlsbHVzdHJh
dGVzIHRoZSByZXN1bHQgb2Ygc3VjaCBjYWxjdWxhdGlvbnMuIEl0IHNob3dzIHRoZSAoMR4xMB4z
KSBkZWxheSB2YXJpYXRpb24gcXVhbnRpbGUgZm9yIHRoZSBhZ2dyZWdhdGVkIGRlbGF5IGNvbXBv
bmVudCBkdWUgdG8gaW50ZXJmZXJlbmNlIGZyb20gdmFyaWF0aW9uLXNlbnNpdGl2ZSB0cmFmZmlj
LCBmb3IgZGlmZmVyZW50IGxvYWQgbGV2ZWxzIG9mIHZhcmlhdGlvbi1zZW5zaXRpdmUgdHJhZmZp
YyBhbmQgZm9yIGRpZmZlcmVudCBudW1iZXJzIG9mIHJvdXRlciBob3BzIGluIHRhbmRlbS4gDQEN
RmlndXJlIElWLjEvWS4xNTQxLiAgVGhlICgxHjEwHjMpIHF1YW50aWxlIG9mIHRoZSBhZ2dyZWdh
dGVkIHF1ZXVpbmcgZGVsYXkgY29tcG9uZW50IGR1ZSB0byB2YXJpYXRpb24tc2Vuc2l0aXZlIHRy
YWZmaWMgZm9yIGRpZmZlcmVudCBsZXZlbHMgb2YgdGhlIHZhcmlhdGlvbi1zZW5zaXRpdmUgdHJh
ZmZpYyBhbmQgZm9yIGRpZmZlcmVudCBudW1iZXIgb2Ygcm91dGVyIGhvcHMgaW4gdGFuZGVtLiAN
RmlndXJloElWLjEgYXNzdW1lcyB0aGF0IGFsbCBsaW5rcyBpbiB0aGUgbmV0d29yayBhcmUgU1RN
HjEgYW5kIGFsbCBsaW5rcyBzaG93aW5nIHRoZSBzYW1lIGxvYWQgbGV2ZWwgZm9yIHZhcmlhdGlv
bi1zZW5zaXRpdmUgdHJhZmZpYy4gSWYgb25lIG9yIG1vcmUgbGlua3MgaGF2ZSBhIGhpZ2hlciBj
YXBhY2l0eSB0aGFuIFNUTR4xLCB0aGUgcmVzdWx0aW5nIGVuZC10by1lbmQgZGVsYXkgd2lsbCBi
ZSBsb3dlcjsgaWYgc29tZSBsaW5rcyBoYXZlIGEgbG93ZXIgY2FwYWNpdHkgdGhlIHJlc3VsdGlu
ZyBlbmQtdG8tZW5kIGRlbGF5IHdpbGwgYmUgaGlnaGVyLiBUaGVzZSBlZmZlY3RzIGNhbiBiZSBj
YWxjdWxhdGVkIChzZWUgSVYuMi40KSBidXQgY2Fubm90IGJlIGVhc2lseSByZWZsZWN0ZWQgaW4g
RmlndXJloElWLjEuIA1GaW5hbGx5LCBpdCBpcyBhc3N1bWVkIHRoYXQgaW4gYSBuZXR3b3JrIHdo
aWNoIHN1cHBvcnRzIGJvdGggdmFyaWF0aW9uLXNlbnNpdGl2ZSBhbmQgdmFyaWF0aW9uLWluc2Vu
c2l0aXZlIHRyYWZmaWMsIHRoZSBsb2FkIG9mIHZhcmlhdGlvbi1zZW5zaXRpdmUgdHJhZmZpYyBv
biBhIGxpbmsgaXMgbm90IG1vcmUgdGhhbiA1MCUgb2YgdGhlIGxpbmsgdG8gcmVmbGVjdCB0aGUg
b2JzZXJ2ZWQgdHJlbmQgdG93YXJkcyCRbW9yZSBkYXRhIHRoYW4gdm9pY2WSLiBUaGVuLCBmcm9t
IEZpZ3VyZaBJVi4xIGl0IGNhbiBiZSBkZXJpdmVkIHRoYXQgdGhpcyBkZWxheSBjb21wb25lbnQg
Y29udHJpYnV0ZXMgbm8gbW9yZSB0aGFuIGFib3V0IDIuNDigbXMgdG8gdGhlIElQRFYgb24gdGhl
IHBhdGgsIGV2ZW4gaWYgdGhlIHBhdGNoIGNyb3NzZXMgYSB2ZXJ5IGhpZ2ggbnVtYmVyIG9mIDI1
IFNUTR4xIHJvdXRlciBob3BzLiANSVYuMi4zCURlbGF5IHZhcmlhdGlvbiBkdWUgdG8gYSB2YXJp
YXRpb24taW5zZW5zaXRpdmUgcGFja2V0DUFuIGFycml2aW5nIHZhcmlhdGlvbi1zZW5zaXRpdmUg
cGFja2V0IGRvZXMgbm90IHByZR5lbXB0IHRoZSBzZXJ2aWNpbmcgb2YgYW4gdmFyaWF0aW9uLWlu
c2Vuc2l0aXZlIHBhY2tldCB3aGljaCBhcnJpdmVkIGVhcmxpZXIuIENvbnNlcXVlbnRseSwgdGhl
IHZhcmlhdGlvbi1zZW5zaXRpdmUgcGFja2V0IG1heSBleHBlcmllbmNlIGEgcXVldWluZyBjb21w
b25lbnQgaW4gZWFjaCByb3V0ZXIgYm91bmRlZCBieSB0aGUgdGltZSBpdCB0YWtlcyB0byBzZXJ2
ZSBhIHZhcmlhdGlvbi1pbnNlbnNpdGl2ZSBwYWNrZXQuIA1Gb3IgdGhlIGNhbGN1bGF0aW9uIGl0
IGlzIGFzc3VtZWQgdGhhdCBlYWNoIHZhcmlhdGlvbi1zZW5zaXRpdmUgcGFja2V0IGV4cGVyaWVu
Y2VzIGEgcmFuZG9tIGRlbGF5IGR1ZSB0byBhIHZhcmlhdGlvbi1pbnNlbnNpdGl2ZSBwYWNrZXQg
d2hpY2ggaXMgdW5pZm9ybWx5IGRpc3RyaWJ1dGVkIGJldHdlZW4gemVybyBhbmQgdGhlIHNlcnZp
Y2UgdGltZSBvZiBtYXhpbXVtIHNpemVkICgxNTAwoGJ5dGUpIHZhcmlhdGlvbi1pbnNlbnNpdGl2
ZSBwYWNrZXQgb24gdGhlIHJlbGV2YW50IG91dHB1dCBsaW5rIHJhdGUuIE9uIGFuIFNUTR4xIG91
dHB1dCBsaW5rIHRoaXMgY29ycmVzcG9uZHMgdG8gYSB1bmlmb3JtbHkgZGlzdHJpYnV0ZWQgZGVs
YXkgYmV0d2VlbiAwIGFuZCA4MC4xM6AocyBpbiBlYWNoIHJvdXRlci4NRm9yIHRoZSBhZ2dyZWdh
dGlvbiBvZiB0aGlzIGRlbGF5IGNvbXBvbmVudCBvdmVyIHNldmVyYWwgcm91dGVycyBpbiB0YW5k
ZW0sIHRoZSBjb252b2x1dGlvbiBvZiB0aGUgcmVsZXZhbnQgZGVsYXkgZGlzdHJpYnV0aW9ucyBt
YXkgYmUgdXNlZCwgdGFraW5nIGludG8gYWNjb3VudCBkaWZmZXJlbnQgb3V0cHV0IGxpbmsgcmF0
ZXMgd2hlbiBhcHBsaWNhYmxlLiBUaGUgbG93ZXIgcXVhbnRpbGUgaXMgYXNzdW1lZCB0byBiZSB6
ZXJvLCB0aGUgaGlnaGVyICgxHjEwHjMpIHF1YW50aWxlIGNhbiBiZSBjYWxjdWxhdGVkIGV4YWN0
bHkuIEluIG1vc3QgY2FzZXMgYSBnb29kIGFwcHJveGltYXRpb24gaXMgYWNoaWV2ZWQgYnkgdXNp
bmcgYW4gYXBwcm94aW1hdGlvbiBieSBhIG5vcm1hbCAoR2F1c3NpYW4pIGRpc3RyaWJ1dGlvbiBv
ciB0aGUgd29yc3QgY2FzZSwgd2hpY2hldmVyIHlpZWxkcyB0aGUgc21hbGxlc3QgdmFsdWUuIFRo
ZSAoMR4xMB4zKSBxdWFudGlsZSBpcyBmb3VuZCBhdCAgKCigK6AzLjcyKCgpLiAgDUlWLjIuNAlB
Z2dyZWdhdGVkIGRlbGF5IHZhcmlhdGlvbiBmb3IgdmFyaWF0aW9uLXNlbnNpdGl2ZSBwYWNrZXRz
DUFuIHVwcGVyIGJvdW5kIHRvIHRoZSBJUERWIG9uIGEgSFJQIGlzIGZvdW5kIGJ5IGFkZGluZyB0
aGUgdmFsdWVzIGNhbGN1bGF0ZWQgZm9yIGVhY2ggb2YgdGhlIHRocmVlIGNvbXBvbmVudHMgaW4g
SVYuMi4xIHRvoElWLjIuMy4gDU5vdGU6CVRoZSB0aHVzIGNhbGN1bGF0ZWQgdmFsdWUgaXMgZXhw
ZWN0ZWQgdG8gYmUgaGlnaGVyIHRoYW4gdGhlIHZhbHVlIGV4cGVyaWVuY2VkIGluIGEgcmVhbCBu
ZXR3b3JrLiBUaGUgZm9sbG93aW5nIGZhY3RvcnMgYXJlIG5vdGVkLg1UaGUgYWRkaXRpb24gb2Yg
dGhyZWUgcXVhbnRpbGUgdmFsdWVzIHlpZWxkcyBhIGhpZ2hlciB2YWx1ZSB0aGFuIHRoZSBhY3R1
YWwgZGVsYXkgcXVhbnRpbGUuDVRoZSBhY3R1YWwgc2l6ZSBvZiB2YXJpYXRpb24tc2Vuc2l0aXZl
IHBhY2tldHMgKHN1Y2ggYXMgVm9JUCBwYWNrZXRzKSBpcyBleHBlY3RlZCB0byBiZSBtdWNoIHNt
YWxsZXIgdGhhbiB0aGUgYXNzdW1lZCBzaXplIG9mIDE1MDCgYnl0ZS4gSW4gYWRkaXRpb24sIHRo
ZSBsb2FkIHdpdGggdmFyaWF0aW9uLXNlbnNpdGl2ZSB0cmFmZmljIG9uIG1vc3QgbGlua3MgaXMg
ZXhwZWN0ZWQgdG8gYmUgc21hbGxlciB0aGFuIHRoZSBhc3N1bWVkIHZhbHVlIG9mIDUwJS4gVGhl
cmVmb3JlLCB0aGUgYWN0dWFsIHF1ZXVpbmcgZGVsYXkgZHVlIHRvIGludGVyZmVyZW5jZSB3aXRo
IHZhcmlhdGlvbi1zZW5zaXRpdmUgdHJhZmZpYyBpcyBleHBlY3RlZCB0byBiZSBzbWFsbGVyIHRo
YW4gY2FsY3VsYXRlZC4gDVRoZSBhY3R1YWwgZGlzdHJpYnV0aW9uIG9mIHZhcmlhdGlvbi1pbnNl
bnNpdGl2ZSBwYWNrZXRzIChlLmcuIFRDUCBhY2tzKSBhbHNvIGNvbnRhaW5zIHBhY2tldCB3aGlj
aCBhcmUgKG11Y2gpIHNtYWxsZXIgdGhhbiB0aGUgYXNzdW1lZCBzaXplIG9mIDE1MDCgYnl0ZS4g
SW4gYWRkaXRpb24sIHRoZSB0b3RhbCBsb2FkICh2YXJpYXRpb24tc2Vuc2l0aXZlIHBsdXMgdmFy
aWF0aW9uLWluc2Vuc2l0aXZlIHRyYWZmaWMpIG9uIG1vc3QgbGlua3MgaXMgZXhwZWN0ZWQgdG8g
YmUgdXN1YWxseSBzbWFsbGVyIHRoYW4gdGhlIGFzc3VtZWQgdmFsdWUgb2YgMTAwJS4gVGhlcmVm
b3JlLCB0aGUgYWN0dWFsIHF1ZXVpbmcgZGVsYXkgZHVlIHRvIGludGVyZmVyZW5jZSB3aXRoIHZh
cmlhdGlvbi1pbnNlbnNpdGl2ZSB0cmFmZmljIGlzIGV4cGVjdGVkIHRvIGJlIHNtYWxsZXIgdGhh
biBjYWxjdWxhdGVkLiANSVYuMwlDYWxjdWxhdGlvbiBleGFtcGxlcw1UaGUgZm9sbG93aW5nIHNo
b3dzIHRocmVlIGV4YW1wbGVzIGZvciB0aGUgY2FsY3VsYXRpb24gb2YgdGhlIElQRFYgaW5kdWNl
ZCBvbiBhIHVzZXItdG8tdXNlciBIUlAgKHNlZSBGaWd1cmWgMSkuDUFuIGV4YW1wbGUgd2hlcmUg
YWxsIGxpbmtzIGFyZSByZWxhdGl2ZWx5IGhpZ2ggc3BlZWQgKFNUTR4xIG9yIGhpZ2hlcikuDUFu
IGV4YW1wbGUgd2hlcmUgdGhlIGxpbmtzIGJldHdlZW4gY3VzdG9tZXIgYW5kIG5ldHdvcmsgYW5k
IHRoZSBsaW5rcyBiZXR3ZWVuIG5ldHdvcmsgc2VjdGlvbnMgaGF2ZSBhIGxvd2VyIHNwZWVkIChF
MyBvciBUMykuIA1BbiBleGFtcGxlIHdoZXJlIHRoZSBsaW5rcyBiZXR3ZWVuIGN1c3RvbWVyIGFu
ZCBuZXR3b3JrIGFyZSBsb3cgc3BlZWQgKGUuZy4gMS41NDSgTWJpdC9zLCBUMSkuIA1JVi4zLjEJ
RXhhbXBsZSB3aXRoIFNUTR4xIGxpbmtzDUluIHRoaXMgZXhhbXBsZSBhbGwgbGlua3MgYXJlIGFz
c3VtZWQgdG8gYmUgU1RNHjEuIFRoZSBIUlAgYmV0d2VlbiB0aGUgbmV0d29yayBpbnRlcmZhY2Vz
IG9mIHRoZSBJUCBuZXR3b3JrIGNsb3VkIChzZWUgQXBwZW5kaXigSUlJLCBGaWd1cmWgNCkgY29u
c2lzdHMgaW4gMTIgcm91dGVyIGhvcHMuIFRodXMsIHRoZSBjb250cmlidXRpbmcgZmFjdG9ycyB0
byB0aGUgSVBEViBvbiB0aGlzIHBhdGggY2FuIGJlIGNhbGN1bGF0ZWQgYXMgZm9sbG93cy4NUm91
dGVyIGxvb2stdXAgZGVsYXkgdmFyaWF0aW9uIChzZWUgSVYuMi4xKTogMTKgKKAzMKAoc6A9oDAu
MzagbXMuDVF1ZXVpbmcgZGVsYXkgdmFyaWF0aW9uIGR1ZSB0byB2YXJpYXRpb24tc2Vuc2l0aXZl
IHRyYWZmaWMgKHNlZSBGaWd1cmWgSVYuMSBmb3IgNTAlIGxvYWQgYW5kIDEyoGhvcHMgU1RNHjEp
OiAooDEuMzagbXMuDVF1ZXVpbmcgZGVsYXkgdmFyaWF0aW9uIGR1ZSB0byB2YXJpYXRpb24taW5z
ZW5zaXRpdmUgdHJhZmZpYyAoc2VloElWLjIuMyk6ICigOS4wMaAooDgwLjEzoChzoD2gMC43MqBt
cy4NVGh1cywgdGhlIElQRFYgb24gdGhpcyBoaWdoIGxpbmsgcmF0ZSBwYXRoIGNhbiBiZSBleHBl
Y3RlZCB0byBiZSBzbWFsbGVyIHRoYW4gMi40NKBtcy4gDUlWLjMuMglFeGFtcGxlIHdpdGggRTMg
aW50ZXJjb25uZWN0aW5nIGxpbmtzDUluIHRoaXMgZXhhbXBsZSBhbGwgbGlua3MgYXJlIGFzc3Vt
ZWQgdG8gYmUgU1RNHjEgZXhjZXB0IHRoZSB1c2VyLW5ldHdvcmsgbGlua3MgYW5kIHRoZSBsaW5r
IGJldHdlZW4gbmV0d29yayBzZWN0aW9ucyB3aGljaCBhcmUgYXNzdW1lZCB0byBiZSBFMyAoMzSg
TWJpdC9zKS4gVGhlIEhSUCBiZXR3ZWVuIHRoZSBuZXR3b3JrIGludGVyZmFjZXMgb2YgdGhlIElQ
IG5ldHdvcmsgY2xvdWQgKHNlZSBBcHBlbmRpeKBJSUksIEZpZ3VyZaA0KSBjb25zaXN0cyBpbiAx
MiByb3V0ZXIgaG9wcywgb2Ygd2hpY2ggMiBob3BzIGhhdmUgdGhlIGxvd2VyIEUzIGJpdCByYXRl
LiBUaHVzLCB0aGUgY29udHJpYnV0aW5nIGZhY3RvcnMgdG8gdGhlIElQRFYgb24gdGhpcyBwYXRo
IGNhbiBiZSBjYWxjdWxhdGVkIGFzIGZvbGxvd3MuDVJvdXRlciBsb29rLXVwIGRlbGF5IHZhcmlh
dGlvbiAoc2VlIElWLjIuMSk6IDEyoCigMzCgKHOgPaAwLjM2oG1zLg1RdWV1aW5nIGRlbGF5IHZh
cmlhdGlvbiBkdWUgdG8gdmFyaWF0aW9uLXNlbnNpdGl2ZSB0cmFmZmljIChmb3IgNTAlIGxvYWQg
YW5kIDEwoGhvcHMgU1RNHjEgcGx1cyAyoGhvcHMgRTMpOiAooDIuOTKgbXMuDVF1ZXVpbmcgZGVs
YXkgdmFyaWF0aW9uIGR1ZSB0byB2YXJpYXRpb24taW5zZW5zaXRpdmUgdHJhZmZpYyAoZm9yIDEw
oGhvcHMgU1RNHjEgcGx1cyAyIGhvcHOgRTMpOiAooDEuMTmgbXMuDVRodXMsIHRoZSBJUERWIG9u
IHRoaXMgbWl4ZWQgbGluayByYXRlIHBhdGggY2FuIGJlIGV4cGVjdGVkIHRvIGJlIHNtYWxsZXIg
dGhhbiA0LjQ3oG1zLiANSVYuMy4zCUV4YW1wbGUgd2l0aCBsb3cgcmF0ZSBhY2Nlc3MgbGlua3MN
SW4gdGhpcyBleGFtcGxlIGFsbCBsaW5rcyBhcmUgYXNzdW1lZCB0byBiZSBTVE0eMSBleGNlcHQg
dGhlIHVzZXItbmV0d29yayBsaW5rcyB3aGljaCBhcmUgYXNzdW1lZCB0byBiZSBhYm91dCAxLjWg
TWJpdC9zIFQxLiBUaGUgSFJQIGJldHdlZW4gdGhlIG5ldHdvcmsgaW50ZXJmYWNlcyBvZiB0aGUg
SVAgbmV0d29yayBjbG91ZCAoc2VlIEFwcGVuZGl4oElJSSwgRmlndXJloDQpIGNvbnNpc3RzIGlu
IDEyIHJvdXRlciBob3BzLCBvZiB3aGljaCAxIGhvcCBoYXMgdGhlIGxvd2VyIGJpdCByYXRlLiBJ
biB0aGlzIGNhc2UgdGhlIGFjY2VzcyBsaW5rIGNvbnRyaWJ1dGlvbiBpcyB0cmVhdGVkIHNlcGFy
YXRlbHkuIFRoZSBjb250cmlidXRpbmcgZmFjdG9ycyB0byB0aGUgSVBEViBvbiB0aGUgaGlnaCBy
YXRlIHBhcnQgb2YgdGhpcyBwYXRoIGNhbiBiZSBjYWxjdWxhdGVkIGFzIGZvbGxvd3MuDVJvdXRl
ciBsb29rLXVwIGRlbGF5IHZhcmlhdGlvbiAoc2VlIElWLjIuMSk6IDEyoCigMzCgKHOgPaAwLjM2
oG1zLg1RdWV1aW5nIGRlbGF5IHZhcmlhdGlvbiBkdWUgdG8gdmFyaWF0aW9uLXNlbnNpdGl2ZSB0
cmFmZmljIChmb3IgNTAlIGxvYWQgYW5kIDExoGhvcHMgU1RNHjEpOiAooDEuMjmgbXMuDVF1ZXVp
bmcgZGVsYXkgdmFyaWF0aW9uIGR1ZSB0byB2YXJpYXRpb24taW5zZW5zaXRpdmUgdHJhZmZpYyAo
Zm9yIDExoGhvcHMgU1RNHjEpOiAooDguMzY0oCigODAuMTOgKHOgPaAwLi42N6Btcy4NVGh1cywg
dGhlIElQRFYgb24gdGhpcyBoaWdoIGxpbmsgY29yZSBwYXRoIGNhbiBiZSBleHBlY3RlZCB0byBi
ZSBzbWFsbGVyIHRoYW4gMi4zMqBtcy4gDU9uIHRoZSBhY2Nlc3MgbGlua3MsIHRoZSBkZWxheSBj
b250cmlidXRpb24gZHVlIHRvIGludGVyZmVyZW5jZSB3aXRoIGEgdmFyaWF0aW9uLWluc2Vuc2l0
aXZlIHBhY2tldCBtYXkgYmUgYXMgbXVjaCBhcyAxNS42oG1zIHdoZW4gdHdvIDE1MDAgYnl0ZSBw
YWNrZXRzIGFyZSBzZXJ2ZWQgYWhlYWQgb2YgYSB2YXJpYXRpb24tc2Vuc2l0aXZlIHBhY2tldCAo
b25lIG9mIHRoZXNlIHBhY2tldHMgbWF5IGJlIHBhcnQgb2YgdGhlIGRlbGF5IHNlbnNpdGl2ZSBm
bG93KS4gVGhlIGNvbnRyaWJ1dGlvbiB0byB0aGUgSVBEViBkdWUgdG8gaW50ZXJmZXJlbmNlIHdp
dGggb3RoZXIgdmFyaWF0aW9uLXNlbnNpdGl2ZSBmbG93cyBoaWdobHkgZGVwZW5kcyBvbiB0aGUg
bnVtYmVyIG9mIHRoZXNlIGZsb3dzIGFuZCBvbiB0aGUgYWN0dWFsIHBhY2tldCBzaXplcyB1c2Vk
LiANTm90ZSB0aGF0IHRoZSBudW1iZXIgb2YgdmFyaWF0aW9uLXNlbnNpdGl2ZSBmbG93cyBhbmQg
dGhlIHJlbGF0ZWQgcGFja2V0IHNpemUgb24gdGhlIGxvdyByYXRlIGFjY2VzcyBsaW5rIGlzIGRl
dGVybWluZWQgYnkgYXBwbGljYXRpb25zIHNlbGVjdGVkIGJ5IHRoZSBlbmQtdXNlcnMuIFdpdGhv
dXQgc29tZSBpbmZsdWVuY2UsIHRoZSBuZXR3b3JrIG9wZXJhdG9yIHdpbGwgZmluZCBoaW1zZWxm
IGluIGEgZGlmZmljdWx0IHBvc2l0aW9uIHRvIGNvbW1pdCB0byBhIHN0cmluZ2VudCB2YWx1ZSBm
b3IgdGhlIElQRFYgbmV0d29yayBwZXJmb3JtYW5jZSBvYmplY3RpdmUgaW4gdGhlIHByZXNlbmNl
IG9mIGEgbG93IHJhdGUgYWNjZXNzIGxpbmsuIA1JZiB0aGUgZGVsYXkgc2Vuc2l0aXZlIHRyYWZm
aWMgaGFzIGNvbnN0YW50IHBhY2tldCBzaXplIChlYWNoIGNvbnRhaW5pbmcgMjCgbXMgb2YgRy43
MTEgY29kZWQgdm9pY2UsIGNvbnNpc3RlbnQgd2l0aCBBcHBlbmRpeKBJSUkpLCBhbmQgb2NjdXBp
ZXMgbm8gbW9yZSB0aGFuIDUwICUgb2YgdGhlIGFjY2VzcyBsaW5rLCB0aGVuIGRlbGF5IGNhbiBi
ZSBlc3RpbWF0ZWQgYXMgZm9sbG93cy4gVGhlcmUgbWF5IGJlIHVwIHRvIDkgdm9pY2UgZmxvd3Mg
b2YgNTCgcGFja2V0L3MsIGVhY2ggMTYwoGJ5dGUgcGF5bG9hZCBwbHVzIDQwoGJ5dGUgUlRQLCBV
RFAgYW5kIElQIGhlYWRlcnMgKGVhY2ggdG90YWwgODCga2JpdC9zKS4NUXVldWluZyBkZWxheSB2
YXJpYXRpb24gZHVlIHRvIHZhcmlhdGlvbi1zZW5zaXRpdmUgdHJhZmZpYyAoZm9yIDQ2LjklIGxv
YWQgYW5kIDEgaG9wIFQxKSwgdXNpbmcgdGhlIE0vRC8xIHF1ZXVpbmcgbW9kZWwgc2hvd3MgdGhh
dCB0aGUgZGVsYXkgY29udHJpYnV0aW9uIGR1ZSB0byB0aG9zZSByZWxhdGl2ZWx5IHNtYWxsIHZh
cmlhdGlvbi1zZW5zaXRpdmUgcGFja2V0cyBvbiB0aGUgYWNjZXNzIGxpbmsgaXMgNS4xMqBtcy4g
DVF1ZXVpbmcgZGVsYXkgdmFyaWF0aW9uIGR1ZSB0byB2YXJpYXRpb24taW5zZW5zaXRpdmUgdHJh
ZmZpYyAoZm9yIDEgaG9wIFQxKTogNy44MaBtcy4NVGhlIGNvbnRyaWJ1dGlvbiB0byB0aGUgZGVs
YXkgdmFyaWF0aW9uIG9uIHRoZSBhY2Nlc3MgbGluayB0aHVzIGFnZ3JlZ2F0ZXMgdG8gMTIuOTOg
bXMgdGh1cyB0b3RhbGxpbmcgdG8gMTUuMjWgbXMuIFRoZSBhY2Nlc3MgbGluayBjb250cmlidXRp
b24gdGh1cyBkb21pbmF0ZXMgdGhlIElQRFYgaW4gdGhpcyBjYXNlLiANSVYuMy40CUV4YW1wbGUg
c3VtbWFyeSBhbmQgY29uY2x1c2lvbnMNVGhlIGNhbGN1bGF0aW9uIGV4YW1wbGVzIHNob3cgdGhh
dCBhIG5ldHdvcmsgb3BlcmF0b3Igd2hvIGRvZXMgYSBtb2Rlc3QgZWZmb3J0IHRvIHN1cHBvcnQg
Ym90aCB2YXJpYXRpb24tc2Vuc2l0aXZlIGFuZCB2YXJpYXRpb24taW5zZW5zaXRpdmUgdHJhZmZp
YyBjYW4gY29tbWl0IHRvIHJhdGhlciBzdHJpbmdlbnQgdmFsdWVzIGZvciB0aGUgSVBEViBvbiBh
IGxvbmcgSFJQIHdoZXJlIGFsbCBsaW5rcyBoYXZlIGEgcmVhc29uYWJseSBoaWdoIHJhdGUgKGUu
Zy4gYSBtaXggb2YgU1RNHjEgYW5kIEUzL1QzIG9yIGhpZ2hlcikuIENvbW1pdHRpbmcgdG8gYW4g
SVBEViB2YWx1ZSBpbiB0aGUgb3JkZXIgb2YgMTCgbXMgbGVhdmVzIGFtcGxlIHJvb20gZm9yIGFk
ZGl0aW9uYWwgbG93ZXIgcmF0ZSAoRTMvVDMpIGxpbmtzIG9yIGZvciBhbiBhZGRpdGlvbmFsIG5l
dHdvcmsgc2VjdGlvbi4gDUlmIGEgbG93IHJhdGUgbGluayAoMS41oE1iaXQvcyBUMSwgb3IgRTEp
IGlzIHByZXNlbnQsIGNvbW1pdHRpbmcgdG8gYW55IGxvdyBJUERWIHZhbHVlIGJlY29tZXMgZGlm
ZmljdWx0LiBUaGUgbmV0d29yayBvcGVyYXRvciBoYXMgbGl0dGxlIG9yIG5vIGNvbnRyb2wgb3Zl
ciB0aGUgYWN0dWFsIG51bWJlciBvZiB2YXJpYXRpb24tc2Vuc2l0aXZlIGZsb3dzIGFuZCB0aGUg
YWN0dWFsIHBhY2tldCBzaXplIG9mIHRoZSB2YXJpYXRpb24tc2Vuc2l0aXZlIHBhY2tldHMuIFRo
ZXJlZm9yZSwgdGhlIElQRFYgY29tbWl0bWVudHMgbWFkZSBieSB0aGUgbmV0d29yayBpbiB0aGlz
IGNhc2Ugd2lsbCBiZSBkb21pbmF0ZWQgYnkgdGhlIGFjY2VzcyBsaW5rLCBhbmQgd2lsbCBuZWVk
IHRvIGJlIGNvbnNpZGVyYWJseSBsYXJnZXIgdGhhbiAxMG1zLCBhcyBzaG93biBpbiBUYWJsZSAx
LiBPbiB0aGUgYWNjZXNzIGxpbmssIHRoZSBlbmQtdXNlciBoYXMgY29udHJvbCBvdmVyIHRoZSBu
dW1iZXIgYW5kIHR5cGUgb2YgZmxvd3MgZGVzaWduYXRlZCBmb3IgYSBkZWxheSBzZW5zaXRpdmUg
Y2xhc3MsIGFuZCB0aGVyZWZvcmUgb3ZlciB0aGUgcmVzdWx0aW5nIElQRFYuICBVbmRlciB0aGUg
YXNzdW1wdGlvbiB0aGF0IHRoZSBhY2Nlc3MgbGluayBpcyBvbmx5IG1vZGVzdGx5IGxvYWRlZCAo
PDUwJSkgd2l0aCB2YXJpYXRpb24tc2Vuc2l0aXZlIHRyYWZmaWMgYW5kIHRoYXQgdGhlIGRvbWlu
YW50IHNpemUgb2YgdGhvc2UgcGFja2V0cyB3aWxsIGJlIHNtYWxsIGNvbXBhcmVkIHRvIHRoZSAx
NTAwoGJ5dGUgbWF4aW11bSBzaXplLCBhbiBhZGRpdGlvbmFsIGFsbG93YW5jZSBvZiAyMKBtcyBm
b3Igb25lIGxvdyByYXRlIGFjY2VzcyBsaW5rIG1heSBiZSBzdWZmaWNpZW50Lg0NQXBwZW5kaXgg
Vg0oSW5mb3JtYXRpdmUpDU1hdGVyaWFsIHJlbGV2YW50IHRvIElQIHBlcmZvcm1hbmNlIG1lYXN1
cmVtZW50IG1ldGhvZHMNVGhpcyBhcHBlbmRpeCwgd2hpY2ggaXMgZm9yIGZ1cnRoZXIgc3R1ZHks
IHdpbGwgZGVzY3JpYmUgaW1wb3J0YW50IGlzc3VlcyB0byBjb25zaWRlciBhcyBJUCBwZXJmb3Jt
YW5jZSBtZWFzdXJlbWVudCBtZXRob2RzIGFyZSBkZXZlbG9wZWQuIEl0IHdpbGwgZGVzY3JpYmUg
dGhlIGVmZmVjdHMgb2YgY29uZGl0aW9ucyBleHRlcm5hbCB0byB0aGUgc2VjdGlvbnMgdW5kZXIg
dGVzdCwgaW5jbHVkaW5nIHRyYWZmaWMgY29uc2lkZXJhdGlvbnMsIG9uIG1lYXN1cmVkIHBlcmZv
cm1hbmNlLg1UaGUgZm9sbG93aW5nIGNvbmRpdGlvbnMgc2hvdWxkIGJlIHNwZWNpZmllZCBhbmQg
Y29udHJvbGxlZCBkdXJpbmcgSVAgcGVyZm9ybWFuY2UgbWVhc3VyZW1lbnRzOg0xKQl0aGUgZXhh
Y3Qgc2VjdGlvbnMgYmVpbmcgbWVhc3VyZWQNU1JDIGFuZCBEU1QgZm9yIGVuZC10by1lbmQgbWVh
c3VyZW1lbnRzDU1QIGJvdW5kaW5nIGFuIE5TRSBiZWluZyBtZWFzdXJlZAtOb3RlOiBpdCBpcyBu
b3QgbmVjZXNzYXJ5IHRvIG1lYXN1cmUgYmV0d2VlbiBhbGwgTVAgcGFpcnMgb3IgYWxsIFNSQyBh
bmQgRFNUIHBhaXJzIGluIG9yZGVyIHRvIGNoYXJhY3Rlcml6ZSBwZXJmb3JtYW5jZQ0yKQltZWFz
dXJlbWVudCB0aW1lDWhvdyBsb25nIHNhbXBsZXMgd2VyZSBjb2xsZWN0ZWQNd2hlbiB0aGUgbWVh
c3VyZW1lbnQgb2NjdXJyZWQNMykJZXhhY3QgdHJhZmZpYyBjaGFyYWN0ZXJpc3RpY3MNcmF0ZSBh
dCB3aGljaCB0aGUgU1JDIGlzIG9mZmVyaW5nIHRyYWZmaWMNU1JDIHRyYWZmaWMgcGF0dGVybg1j
b21wZXRpbmcgdHJhZmZpYyBhdCB0aGUgU1JDIGFuZCBEU1QNSVAgcGFja2V0IHNpemUNNCkJdHlw
ZSBvZiBtZWFzdXJlbWVudA1pbi1zZXJ2aWNlIG9yIG91dC1vZi1zZXJ2aWNlDWFjdGl2ZSBvciBw
YXNzaXZlDTUpCXN1bW1hcmllcyBvZiB0aGUgbWVhc3VyZWQgZGF0YQ1tZWFucywgd29yc3QtY2Fz
ZSwgZW1waXJpY2FsIHF1YW50aWxlcw1zdW1tYXJpemluZyBwZXJpb2QNc2hvcnQgcGVyaW9kIChl
LmcuIG9uZSBtaW51dGUpDWxvbmcgcGVyaW9kIChlLmcuIG9uZSBob3VyLCBvbmUgZGF5LCBvbmUg
d2Vlaywgb25lIG1vbnRoKQ1BUFBFTkRJWCBWSQ0oSW5mb3JtYXRpdmUpDUFwcGxpY2FiaWxpdHkg
b2YgdGhlIElFVEYgRGlmZmVyZW50aWF0ZWQgU2VydmljZXMgdG8gSVAgUW9TIGNsYXNzZXMgDVRo
aXMgYXBwZW5kaXggYWRkcmVzc2VzIHRoZSBhcHBsaWNhYmlsaXR5IG9mIERpZmZlcmVudGlhdGVk
IFNlcnZpY2VzIGFzIGRlZmluZWQgYnkgdGhlIElFVEYgdG8gc3VwcG9ydGluZyB0aGUgZGVmaW5l
ZCBJUCBRb1MgY2xhc3Nlcy4gTm8gUW9TIG9iamVjdGl2ZXMgYXJlIHNwZWNpZmllZCBpbiB0aGUg
ZGVmaW5pdGlvbnMgb2YgdGhlc2UgSUVURiBjYXBhYmlsaXRpZXMuIEhvd2V2ZXIsIHRoZSBzZXJ2
aWNlIG1vZGVscyBkbyBzcGVjaWZ5IHRoYXQgdGhlIHVzZXJzIG9mIHRoZSBzZXJ2aWNlIGNhbiBy
ZWx5IG9uIHNwZWNpZmljIFFvUyBjaGFyYWN0ZXJpc3RpY3MuDVdoZW4gdGhlIElQIE5ldHdvcmsg
Q2xvdWQgb2YgRmlndXJlIDEgaXMgYSBEaWZmc2VydiAoRFMpIFJlZ2lvbiBbUkZDMjQ3NF0sIHRo
ZW4gdGhlIFFvUyBDbGFzc2VzIHNwZWNpZnkgdGhlIGVuZC10by1lbmQgcGVyZm9ybWFuY2Ugb2Jq
ZWN0aXZlcyBmb3IgdGhhdCByZWdpb24uIEEgRFMgUmVnaW9uIG1heSBjb250YWluIG9uZSBvciBt
b3JlIERTIERvbWFpbnMgKE5ldHdvcmsgU2VjdGlvbnMpLCBjb25mb3JtaW5nIHRvIFBlciBEb21h
aW4gQmVoYXZpb3JzIChQREIpIFtSRkMzMDg2XSB3aXRoIG1lYXN1cmFibGUgZWRnZS10by1lZGdl
IHNlcnZpY2UgbGV2ZWwgc3BlY2lmaWNhdGlvbnMuIFBEQiBzcGVjaWZpY2F0aW9ucyBhcmUgd29y
ayBpbiBwcm9ncmVzcy4gT25lIG9yIG1vcmUgUGVyIEhvcCBCZWhhdmlvcnMgKFBIQnMpIG1heSBi
ZSBjb21iaW5lZCB3aXRoIG90aGVyIERpZmZzZXJ2IHRvb2xzIChzdWNoIGFzIHRyYWZmaWMgY29u
ZGl0aW9uZXJzKSB0byBjb25zdHJ1Y3QgUGVyIERvbWFpbiBCZWhhdmlvcnMuIFRoZSBjdXJyZW50
bHkgZGVmaW5lZCBEaWZmZXJlbnRpYXRlZCBTZXJ2aWNlcyBQSEJzIGFyZSBBc3N1cmVkIEZvcndh
cmRpbmcgKEFGKSBbUkZDMjU5N10gYW5kIEV4cGVkaXRlZCBGb3J3YXJkaW5nIChFRikgW1JGQzI1
OThdLiBUaGUgQUYgc3BlY2lmaWNhdGlvbiBkZWZpbmVzIGEgZ3JvdXAgb2YgNCBBRiBjbGFzc2Vz
IHRoYXQgc2hvdWxkIGJlIGhhbmRsZWQgaW5kZXBlbmRlbnRseS4gDVRoZSBmb2xsb3dpbmcgVGFi
bGUgVkkuMS9ZLjE1NDEgYXNzb2NpYXRlcyB0aGUgWS4xNTQxIFFvUyBjbGFzc2VzIHRvIEludGVn
cmF0ZWQgYW5kIERpZmZlcmVudGlhdGVkIFNlcnZpY2VzLiBUaGlzIHRhYmxlIGFzc3VtZXMgdGhh
dCBhbGwgSVAgcGFja2V0cyBhcmUgaW4gcHJvZmlsZSwgd2hlbiBzdWNoIGEgdHJhZmZpYyBwcm9m
aWxlIGlzIHNwZWNpZmllZCBmb3IgdGhlIElQIHBhY2tldCBzdHJlYW0uDQ1UYWJsZSBWSS4xL1ku
MTU0MQ1Qb3NzaWJsZSBBc3NvY2lhdGlvbiBvZiBZLjE1NDEgUW9TIGNsYXNzZXMgd2l0aCBEaWZm
ZXJlbnRpYXRlZCBTZXJ2aWNlcw1JUCB0cmFuc2ZlciBzZXJ2aWNlB0lQIFFvUyBjbGFzcwdSZW1h
cmtzBwdCZXN0IEVmZm9ydCBQREIHVW5zcGVjaWZpZWQNUW9TIGNsYXNzIDUHYSBsZWdhY3kgSVAg
c2VydmljZSwgd2hlbiBvcGVyYXRlZCBvbiBhIGxpZ2h0bHkgbG9hZGVkIG5ldHdvcmsgbWF5IGFj
aGlldmUgYSBnb29kIGxldmVsIG9mIElQIFFvUwcHUERCcyBiYXNlZCBvbiBBc3N1cmVkIEZvcndh
cmRpbmcNBw1Rb1MgY2xhc3NlcyAyLDMsNAd0aGUgSVBMUiBvYmplY3RpdmUgb25seSBhcHBsaWVz
IHRvIHRoZSBJUCBwYWNrZXRzIGluIHRoZSBoaWdoZXIgcHJpb3JpdHkgbGV2ZWxzIG9mIGVhY2gg
QUYgY2xhc3MuDVRoZSBJUFREICBhcHBsaWVzIHRvIGFsbCBwYWNrZXRzBwdQREJzIGJhc2VkIG9u
IEV4cGVkaXRlZCBGb3J3YXJkaW5nDQcNUW9TIGNsYXNzZXMgMCBhbmQgMQ0HBwdBUFBFTkRJWCBW
SUkNKEluZm9ybWF0aXZlKQ1SZWxhdGlvbnNoaXBzIGFtb25nIHRyYW5zaXQgZGVsYXkgb2JqZWN0
aXZlcyANVGhpcyBhcHBlbmRpeCBleHBsYWlucyBob3cgdGhlIGxvbmctc3RhbmRpbmcgZ3VpZGFu
Y2Ugb24gdHJhbnNtaXNzaW9uIGRlbGF5IHByb3ZpZGVkIGJ5IFJlY29tbWVuZGF0aW9uIEcuMTE0
IHJlbGF0ZXMgdG8gdGhlIHBhY2tldCB0cmFuc2ZlciBkZWxheSBvYmplY3RpdmVzIHNwZWNpZmll
ZCBpbiBZLjE1NDEuDVJlY29tbWVuZGF0aW9uIEcuMTE0IGhhcyBpdHMgcm9vdHMgaW4gbmV0d29y
ayBwbGFubmluZywgYW5kIHNvIHRoZSBvbmx5IGRlbGF5IHZhbHVlIHNwZWNpZmllZCBpbiBHLjEx
NCBpcyA0MDAgbXMsIGFuZCB0aGlzIHZhbHVlIGlzIG9uZS13YXksIE5JLXRvLU5JIChzcGVjaWZp
Y2FsbHkgdGhlIFQtcmVmZXJlbmNlIHBvaW50cykuIFRoaXMgdmFsdWUgb2YgNDAwbXMgaGFzIGhp
c3RvcmljYWxseSBjb3ZlcmVkIHByaW1hcmlseSBwcm9wYWdhdGlvbiBkZWxheXMgYW5kIGNhbiB0
aGVyZWZvcmUgZ2VuZXJhbGx5IHN1cHBvcnQgdGhlIDI3LDUwMCBrbSByZWZlcmVuY2UgY29ubmVj
dGlvbiAoc2VlIFJlYy4gRy44MDEpIHRoYXQgbWFueSBJVFUgUmVjb21tZW5kYXRpb25zIGFyZSBi
YXNlZCB1cG9uLCBpbmNsdWRpbmcgdGhlIGFsbG93YW5jZSBmb3IgZ2Vvc3RhdGlvbmFyeSBzYXRl
bGxpdGVzLiANV2hlbiBHLjExNCB3YXMgZmlyc3QgZGV2ZWxvcGVkLCBuZXR3b3JrIGFuZCB1c2Vy
IHRlcm1pbmFscyBkaWQgbm90IGFkZCBhcHByZWNpYWJsZSBkZWxheXMgdG8gdGhlIHRvdGFsIGRl
bGF5IHNlZW4gYnkgdGhlIHVzZXIgYXBwbGljYXRpb24gKGUuZy4sIG1vdXRoLXRvLWVhcikuIFdp
dGggdGhlIHByb2xpZmVyYXRpb24gb2YgcGFja2V0IG5ldHdvcmtzIGFuZCB0ZXJtaW5hbHMgd2l0
aCBpbnRlbnNpdmUgc2lnbmFsIHByb2Nlc3NpbmcsIHN1Y2ggYXMgd2lyZWxlc3Mgb3IgbXVsdGlt
ZWRpYSB0ZXJtaW5hbHMsIHRoZSBkZWxheXMgYWRkZWQgYnkgdGVybWluYWxzIGNhbiBiZSB2ZXJ5
IGxhcmdlICh0ZW5zIG9mIG1zIG9yIG1vcmUpLiBUaGlzIGlzIHdoeSBHLjExNCB3YXMgcmV2aXNl
ZCBpbiByZWNlbnQgeWVhcnMtLW5vdCB0byBjaGFuZ2UgdGhlIE5JLXRvLU5JIHZhbHVlIG9mIDQw
MCBtcy0tYnV0IHRvIGVtcGhhc2l6ZSB0aGUgbmVlZCB0byBsaW1pdCBzaWduYWwgcHJvY2Vzc2lu
Zy1yZWxhdGVkIGRlbGF5cyAoYW5kIHBhY2tldGl6YXRpb24gZGVsYXlzKS4gDVNvbWUgY29uZnVz
aW9uIG1heSBiZSBjYXVzZWQgYnkgdGhlIHN0YXRlbWVudCBpbiBHLjExNCB0aGF0IGhpZ2hseSBp
bnRlcmFjdGl2ZSBhcHBsaWNhdGlvbnMgY2FuIGJlIGFmZmVjdGVkIGJ5IGRlbGF5cyBsZXNzIHRo
YW4gMTUwIG1zLCBhIGZhY3QgYm9ybmUgb3V0IGJ5IHRoZSBleHBlcmltZW50YWwgZGF0YSBvZiBB
cHBlbmRpeCBCIHRvIEcuMTE0LiBUaGlzIHN0YXRlbWVudCBpcyBpbnRlbmRlZCB0byBtYWtlIHRo
ZSByZWFkZXIgb2YgRy4xMTQgYXdhcmUgdGhhdCBzb21lIGFwcGxpY2F0aW9ucyBhcmUgYWZmZWN0
ZWQgYnkgZGVsYXlzIG11Y2ggbG93ZXIgdGhhbiB0aGUgNDAwIG1zIGxpbWl0IHJlY29tbWVuZGVk
IGZvciB0aGUgTkktdG8tTkkgcGF0aC4gVGhlIHNhbWUgcmF0aW9uYWxlIGlzIHRodXMgYXBwbGlj
YWJsZSB0byBZLjE1NDEgKHdoaWNoIHNwZWNpZmllcyBvbmx5IHRoZSBOSS10by1OSSBwYXRoKTsg
dGhhdCBpcywgZXZlbiBpZiB0aGUgbmV0d29yayBkZWxheSBpcyBrZXB0IGJlbG93IDQwMCBtcywg
cGVyaGFwcyBldmVuIHdlbGwgYmVsb3cgNDAwbXMsIGhpZ2hseSBpbnRlcmFjdGl2ZSBhcHBsaWNh
dGlvbnMgY2FuIGJlIGFkdmVyc2VseSBhZmZlY3RlZCBpZiB0aGUgdXNlciBkZXBsb3lzIHRlcm1p
bmFsIGVxdWlwbWVudCB0aGF0IGFkZHMgc3Vic3RhbnRpYWwgZGVsYXkgdG8gdGhlIGRlbGF5IHBy
b2R1Y2VkIGluIHRoZSBuZXR3b3JrLiBUaGUgbmV0d29yayBwcm92aWRlciAod2hvIG1heSB1c2Ug
c2F0ZWxsaXRlcywgQVRNLSBvciBJUC1iYXNlZCBuZXR3b3JrcywgZm9yIGV4YW1wbGUpIGNhbiBk
byBub3RoaW5nIGFib3V0IHRoZSBkZWxheXMgaW50cm9kdWNlZCBieSB1c2VyIHRlcm1pbmFscy4N
T25lIGNvdWxkIHBhcmFwaHJhc2UgdGhlIHNpdHVhdGlvbiBhcyBmb2xsb3dzOiBHLjExNCByZWNv
bW1lbmRzIGxpbWl0aW5nIG5ldHdvcmsgZGVsYXlzIHRvIDQwMCBtcyBhbmQgY2F1dGlvbnMgYWdh
aW5zdCBhbGxvd2luZyBwcm9jZXNzaW5nIGRlbGF5IHRvIGNyZWVwIGludG8gdGVybWluYWxzIHRv
byBsaWJlcmFsbHkuIFNvbWUgb2YgdGhlIGNsYXNzZXMgb2YgWS4xNTQxIHJlZmxlY3QgdGhpcyBs
aW1pdCBkaXJlY3RseS4gSW4gYWRkaXRpb24sIFkuMTU0MSBhbGxvd3MgdGhlIGZsZXhpYmlsaXR5
IG9mIHN1cHBvcnRpbmcgaGlnaGx5IGludGVyYWN0aXZlIGFwcGxpY2F0aW9ucywgdGhyb3VnaCB0
aGUgdXNlIG9mIGJvdGggbG93LWRlbGF5IHRlcm1pbmFscyBhbmQgdGhlIGxvdy1kZWxheSBRT1Mg
Y2xhc3NlcyBvZiBZLjE1NDEuDVJlY29tbWVuZGF0aW9uIEkuMzU2IHN1cHBvcnRzIHRoZSA0MDAg
bXMgbGltaXQsIGluIGl0cyBjbGFzc2VzIGZvciBBVE0gcGVyZm9ybWFuY2UuDQ0NQXBwZW5kaXgg
VklJSQ0oSW5mb3JtYXRpdmUpDUJpYmxpb2dyYXBoeQ1SRkMgNzY4IChTVEQtNikgLSBVc2VyIERh
dGFncmFtIFByb3RvY29sIChVRFApDVJGQyA3OTIgKFNURC01KSAtIEludGVybmV0IENvbnRyb2wg
TWVzc2FnZSBQcm90b2NvbCAoSUNNUCkNUkZDIDc5MyAoU1RELTcpIC0gVHJhbnNtaXNzaW9uIENv
bnRyb2wgUHJvdG9jb2wgKFRDUCkNUkZDIDkxOSAoU1RELTUpIC0gQnJvYWRjYXN0aW5nIEludGVy
bmV0IGRhdGFncmFtcw1SRkMgOTIyIChTVEQtNSkgLSBCcm9hZGNhc3RpbmcgSW50ZXJuZXQgZGF0
YWdyYW1zIGluIHRoZSBwcmVzZW5jZSBvZiBzdWJuZXRzDVJGQyA5NTkgKFNURC05KSAtIEZpbGUg
VHJhbnNmZXIgUHJvdG9jb2wgKEZUUCkNUkZDIDk1MCAtIEludGVybmV0IFN0YW5kYXJkIFN1Ym5l
dHRpbmcgUHJvY2VkdXJlICh1cGRhdGVzIFJGQyA3OTIpDVJGQyAxMzA1IC0gTmV0d29yayBUaW1l
IFByb3RvY29sICh2MykNUkZDMTc4NiAtIFJlcHJlc2VudGF0aW9uIG9mIElQIFJvdXRpbmcgUG9s
aWNpZXMgaW4gYSBSb3V0aW5nIFJlZ2lzdHJ5DVJGQyAxODEyIC0gUmVxdWlyZW1lbnRzIGZvciBJ
UCBWZXJzaW9uIDQgUm91dGVycw1SRkMgMjAxOCAtIFRDUCBzZWxlY3RpdmUgYWNrbm93bGVkZ21l
bnQgb3B0aW9ucw1SRkMgMjMzMCAtIEZyYW1ld29yayBmb3IgSVAgcGVyZm9ybWFuY2UgbWV0cmlj
cw1SRkMgMjQ3NCAtIERlZmluaXRpb24gb2YgdGhlIERpZmZlcmVudGlhdGVkIFNlcnZpY2VzIEZp
ZWxkIChEUyBGaWVsZCkgaW4gdGhlIElQdjQgYW5kIElQdjYgSGVhZGVycw1SRkMgMjQ3NSAtIEFu
IEFyY2hpdGVjdHVyZSBmb3IgRGlmZmVyZW50aWF0ZWQgU2VydmljZXMNUkZDIDI1OTcgLSBBc3N1
cmVkIEZvcndhcmRpbmcgUEhCIEdyb3VwDVJGQyAyNTk4IC0gQW4gRXhwZWRpdGVkIEZvcndhcmRp
bmcgUEhCDVJGQyAyNjc5IC0gQSBPbmUtd2F5IERlbGF5IE1ldHJpYyBmb3IgSVBQTSANUkZDIDI2
ODAgLSBBIE9uZS13YXkgUGFja2V0IExvc3MgTWV0cmljIGZvciBJUFBNIA1SRkMgMjY4MSAtIEEg
Um91bmQtdHJpcCBEZWxheSBNZXRyaWMgZm9yIElQUE0gDVJGQyAzMDg2IC0gRGVmaW5pdGlvbiBv
ZiBEaWZmZXJlbnRpYXRlZCBTZXJ2aWNlcyBQZXIgRG9tYWluIEJlaGF2aW9ycyBhbmQgUnVsZXMg
Zm9yIHRoZWlyIFNwZWNpZmljYXRpb24NVElQSE9OIFRSIDEwMSAzMjkgLSBQYXJ0IDIsIFF1YWxp
dHkgb2YgU2VydmljZSAoUW9TKSBDbGFzc2VzDVN0dWR5IEdyb3VwIDEyIERlbGF5ZWQgQ29udHJp
YnV0aW9uIEQuMTUsIFRoZSBlZmZlY3Qgb2YgUGFja2V0IExvc3NlcyBvbiBTcGVlY2ggUXVhbGl0
eSwgQy4gS2FybHNzb24sIFRlbGlhIEFCLCBGZWIgMjAwMS4NVDEgU3RhbmRhcmQgVDEuNTIyLTIw
MDAsIFF1YWxpdHkgb2YgU2VydmljZSBmb3IgQnVzaW5lc3MgTXVsdGltZWRpYSBDb25mZXJlbmNp
bmcuDVtJRklQXSBNaWNoZWygTWFuZGplcywgS2Vlc6B2YW6gZGVyoFdhbCwgUm9ioEtvb2lqLCBI
YXJyaWWgQmFzdGlhYW5zZW4sIEVuZC10by1lbmQgZGVsYXkgbW9kZWxzIGZvciBpbnRlcmFjdGl2
ZSBzZXJ2aWNlcyBvbiBhIGxhcmdlLXNjYWxlIElQIG5ldHdvcms7IFNldmVudGggSUZJUCB3b3Jr
c2hvcCBvbiBQZXJmb3JtYW5jZSBNb2RlbGxpbmcgYW5kIEV2YWx1YXRpb24gb2YgQVRNIE5ldHdv
cmtzOiBJRklQIEFUTSc5OTsgQW50d2VycCwgQmVsZ2l1bTsgSnVuZSAyOB4zMCwgMTk5OS4gUGFw
ZXIgNDIuIFByb2NlZWRpbmdzIGVkaXRlZCBieSBHdWlkb6BILqBQZXRpdC4NSi4gUGFkaHllLCBW
LiBGaXJvaXUsIEQuIFRvd3NsZXksIEouIEt1cm9zZSwgIk1vZGVsaW5nIFRDUCBSZW5vIFBlcmZv
cm1hbmNlOiBBIFNpbXBsZSBNb2RlbCBhbmQgaXRzIEVtcGlyaWNhbCBWYWxpZGF0aW9uLCIgSUVB
TkVQLCB2b2wuIDgsIG5vLiAyLCBwcC4gMTMzLS0xNDUsIEFwci4gMjAwMA0NQXBwZW5kaXggSVgN
KEluZm9ybWF0aXZlKQ1EaXNjdXNzaW9uIG9mIEJyb2FkY2FzdCBRdWFsaXR5IERpZ2l0YWwgVmlk
ZW8gb24gSVAgTmV0d29ya3MNRWRpdG9yknMgTm90ZTogVGhlIHRleHQgb2YgdGhpcyBzZWN0aW9u
IGlzIHRvIGJlIHByb3ZpZGVkLCBhbHRob3VnaCBpdCB3aWxsIHByb2JhYmx5IGJlZ2luIGFzIGZv
bGxvd3M6DVRoZSBDbGFzc2VzIGluIFRhYmxlIDEvWS4xNTQxIGFyZSBpbnRlbmRlZCB0byBjb3Zl
ciBhIGJyb2FkIHJhbmdlIG9mIGFwcGxpY2F0aW9ucyBmb3Igd2hpY2ggdGhlIHRyYW5zcG9ydCBy
ZXF1aXJlbWVudHMgYXJlIGtub3duLiAgRXhhbXBsZXMgb2YgYXBwbGljYXRpb25zIG5vdCBjb3Zl
cmVkIGJ5IHRoZXNlIGNsYXNzZXMgYXJlIGJyb2FkY2FzdCBUViBkaXN0cmlidXRpb24sIHByb2dy
YW0gYXVkaW8sIERpZ2l0YWwgQ2luZW1hLCBhbmQgY29tcHJlc3NlZCBIRFRWIHRyYW5zcG9ydCwg
d2hlcmUgdmVyeSBsb3cgbG9zcyBtYXkgYmUgbmVlZGVkLCBhbmQgcG9zc2libHkgbG93IG5ldHdv
cmsgZGVsYXkuDUF0IHRoZSB0aW1lIG9mIHB1YmxpY2F0aW9uLCBtb3JlIHN0dWR5IGlzIG5lZWRl
ZCB0byBkZWZpbmUgcGFja2V0IHRyYW5zZmVyIHBlcmZvcm1hbmNlIHJlcXVpcmVtZW50cyBmb3Ig
ZGlnaXRhbCB2aWRlbyB0cmFuc3BvcnQgYXQgdmVyeSBoaWdoIHRyYW5zcG9ydCByYXRlcywgdXNp
bmcgYXBwbGljYXRpb25zIHdpdGggbG93IHRvbGVyYW5jZSB0byBpbXBhaXJtZW50cywgZm9yIGFu
IGV4dHJlbWVseSBkZW1hbmRpbmcgY29tbXVuaXR5IG9mIHVzZXJzLg0NZW5kIG9mIERyYWZ0IFJl
Y29tbWVuZGF0aW9uIFkuMTU0MQ0NX19fX19fX19fX19fX19fX19fX18NDQ0NVDFBMS4zLzIwMDEt
MDM1IFIxDQ0NQ09OVEFDVDogIEEuQy5Nb3J0b24sIEVkaXRvcjsgICAgICAgICAgIGVtYWlsOiAT
IEhZUEVSTElOSyBtYWlsdG86cmNhbmFkYXlAYXR0LmNvbTsgARRhY21vcnRvbkBhdHQuY29tOxUg
VGVsOiA3MzItNDIwLTE1NzE7IEZheDogNzMyLTM2OC0xMTkyDQ0NDQ0NDQ0NDQ0NDVBhZ2UgEyBQ
QUdFIBQxNBUNDQ0NDQ0NDVBhZ2UgEyBQQUdFIBQxFQ0NUGFnZSATIFBBR0UgFDIVDQ0NDQ0NQU5O
RVggXw0odG8gdGhlIFJlcG9ydCBvZiBXUCA0LzEzKQ0NDQ0AAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAOQQAAKEEAADMBAAAzQQAAM4EAADS
BAAA0wQAANQEAADWBAAA3AQAAPIEAADzBAAA9QQAAPYEAACmBQAArwUAAAcGAAAIBgAACQYAAAoG
AAALBgAADAYAADMGAAA4BgAAPQYAAD4GAABEBgAARgYAAFcGAABYBgAAdwYAAHgGAACIBgAAigYA
AI8GAAD58/EA6ubj3ADmANUA5gDxAMoAwbqxpp6QnoSeeW55ZqaeWwAAABRDShIAT0oCAFFKAgBt
SAkEc0gJBAAPNQiBQ0oUAG1ICQRzSAkEFENKFABPSgMAUUoDAG1ICQRzSAkEABRDShQAT0oCAFFK
AgBtSAkEc0gJBAAXNQiBQ0o8AE9KAgBRSgIAbUgJBHNICQQbNQiBQIgoAENKSABPSgIAUUoCAG1I
CQRzSAkEDzUIgUNKEgBtSAkEc0gJBBRDShwAT0oCAFFKAgBtSAkEc0gJBAAQT0oDAFFKAwBtSAkE
c0gJBAAMQ0oQAG1ICQRzSAkEABEDapkHAABVCAFtSAkEc0gJBBQDagAAAABVCAFtSAAEbkgABHUI
AQANA2rzBAAARUjU/1UIAQ0DaoQCAABFSNT/VQgBBENKHAAABzUIgUNKHAANA2oAAAAARUjU/1UI
AQM1CIELNQiBbUgKDHNICgwLNQiBbUgMEHNIDBAAIwAEAAA5BAAAaAQAAKAEAAChBAAAzAQAAM0E
AADcBAAA3QQAAPEEAAD3BAAACQUAAAoFAAAaBQAAGwUAAJIFAACmBQAArwUAAPEFAADyBQAABgYA
AAcGAAAJBgAACwYAAAwGAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9
AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAA/QAAAAAA
AAAAAAAAAP0AAAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAA8QAAAAAAAAAAAAAAAPEAAAAAAAAAAAAA
AADrAAAAAAAAAAAAAAAA6wAAAAAAAAAAAAAAAOsAAAAAAAAAAAAAAADmAAAAAAAAAAAAAAAA5gAA
AAAAAAAAAAAAAP0AAAAAAAAAAAAAAADhAAAAAAAAAAAAAAAA5gAAAAAAAAAAAAAAAOYAAAAAAAAA
AAAAAADhAAAAAAAAAAAAAAAA2QAAAAAAAAAAAAAAANEAAAAAAAAAAAAAAAAAAAAAAAAIAAATpAAA
FiQBSWYBAAAACBEAE6QAABYkAUlmAQAAAAAEAAADJABhJAAABAAAAyQBYSQBAAU5AA3GBQABigUA
AAUAAA3GBQABigUAAAUAAA3GBQAB8BMAAAEAAAAYAAQAAJX+AACX/wAAv/8AAP39/QAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAABAQMMBgAANAYAADUGAAA2BgAANwYAADgGAAA+BgAA
RQYAAEYGAAB4BgAA9wAAAAAAAAAAAAAAALMAAAAAAAAAAAAAAACxAAAAAAAAAAAAAAAAsQAAAAAA
AAAAAAAAALEAAAAAAAAAAAAAAACrAAAAAAAAAAAAAAAAoAAAAAAAAAAAAAAAAF0QAQAAAAAAAAAA
AABUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJAAADJAAWJAFJZgEAAABhJAAAQgAAFiQBFyQBSWYB
AAAAApZVAAjWMAACNQXtFm4mAAa4EQAAAAAAAAAAAAAAAAAAAAAABoEPAAAAAAAAAAAAAAAAAAAA
ABT2AQAAGtYIAAAA/wAAAP8b1ggAAAD/AAAA/xzWCAAAAP8AAAD/HdYIAAAA/wAAAP801gYAAQoD
VQBh9gOKBQsAAAMkAhOk8AAWJAFJZgEAAABhJAIGAAAWJAFJZgEAAAAAAQAARAAAFiQBFyQBSWYB
AAAAApZsAAM0AQjWMAAClP/8BOEkAAZoBQAAAAAAAAAAAAAAAAAAAAAABuUfAAAAAAAAAAAAAAAA
AAAAABT2AQAAGtYIAAAA/wAAAP8b1ggAAAD/AAAA/xzWCAAAAP8AAAD/HdYIAAAA/wAAAP801gYA
AQoDbABh9gMAAAgAABOkHAEWJAFJZgEAAAAACXgGAACJBgAAigYAAIsGAACMBgAAjQYAAI4GAACP
BgAAuwYAALwGAAC9BgAAvgYAAPQGAAD1BgAA9AAAAAAAAAAAAAAAALEAAAAAAAAAAAAAAACrAAAA
AAAAAAAAAAAAqwAAAAAAAAAAAAAAAKsAAAAAAAAAAAAAAACrAAAAAAAAAAAAAAAAqwAAAAAAAAAA
AAAAAKIAAAAAAAAAAAAAAACiAAAAAAAAAAAAAAAAhQAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAB0
AAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAMAAADJAAPhIoFE6TwAEAmAF6EigVhJAAA
BAAAAyQAYSQAABwAAA3GBQABpyUCD4SKBROkOQAmZAwBAAEoZAwBAAFQxggAAAD/DAEBAFLGCAAA
AP8MAQEAXoSKBQAIAAADJAAPhIoFXoSKBWEkAAAFAAANxgUAAaclAgBCAAAWJAEXJAFJZgEAAAAC
llUACNYwAAI1Be0WbiYABrgRAAAAAAAAAAAAAAAAAAAAAAAGgQ8AAAAAAAAAAAAAAAAAAAAAFPYB
AAAa1ggAAAD/AAAA/xvWCAAAAP8AAAD/HNYIAAAA/wAAAP8d1ggAAAD/AAAA/zTWBgABCgNVAGH2
A4oFCwAAAyQCE6QAABYkAUlmAQAAAGEkAgANjwYAALwGAAC9BgAAvgYAAPQGAAD1BgAAGQcAADwH
AAA9BwAAiQcAAKkHAADdBwAA3gcAAN8HAADnBwAAOQwAAD8MAACRDAAAkgwAAJMMAACcDAAAnQwA
AKsMAACsDAAAtAwAALUMAADPDAAA0AwAANEMAADSDAAA0wwAAOEMAADiDAAA/AwAAP0MAAD+DAAA
/wwAAAANAAARDQAAEg0AAPXp3unZ9c7Hvbaqx9mk2aTZndmkkqSSjIGMc4GMgYyBjGWBjIGMgQAA
ABoCCIEDagBFAAAGCAFVCAFtSAAEbkgABHUIAQAaAgiBA2qDRAAABggBVQgBbUgABG5IAAR1CAEA
FANqAAAAAFUIAW1IAARuSAAEdQgBAAttSAAEbkgABHUIARQDagAAAAA1CIFVCAFtSAkEc0gJBAAM
Q0oWAG1ICQRzSAkEAAs1CIFtSAkEc0gJBBc1CIFDSiAAT0oCAFFKAgBtSAkEc0gJBAxDShgAbUgJ
BHNICQQAEzUIgU9KAgBRSgIAbUgJBHNICQQMQ0ogAG1ICQRzSAkEABRDShQAT0oCAFFKAgBtSAkE
c0gJBAAIbUgJBHNICQQAFENKEgBPSgIAUUoCAG1ICQRzSAkEABc1CIFDSiQAT0oCAFFKAgBtSAkE
c0gJBBRDSiAAT0oCAFFKAgBtSAkEc0gJBCf1BgAAGQcAAD0HAACJBwAAigcAAKgHAACpBwAA3gcA
AN8HAADnBwAAEgkAADgMAADpAAAAAAAAAAAAAAAA0wAAAAAAAAAAAAAAAKkAAAAAAAAAAAAAAACn
AAAAAAAAAAAAAAAAoQAAAAAAAAAAAAAAAKEAAAAAAAAAAAAAAACbAAAAAAAAAAAAAAAAa2gRAAAA
AAAAAAAAAGUAAAAAAAAAAAAAAABlAAAAAAAAAAAAAAAAZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
BgAAFiQBSWYBAAAAAC8AABYkARckAUlmAQAAAAKWbAAI1hoAAZT/bSYABtkmAAAAAAAAAAAAAAAA
AAAAABT2AQAAGtYEAAAA/xvWBAAAAP8c1gQAAAD/HdYEAAAA/zTWBgABCgNsAGH2AwAABjQAFiQB
SWYBAAAABkYAFiQBSWYBAAAAAAFGAAApAAANxgUAAaclAg+EgwUTpDkAFKR4ABiEegQZhBEyGyaQ
IyQCJmQMAQABKGQMAQABLoSgBS+EuwBQxggAAAD/DAEBAFLGCAAAAP8MAQEAXoSDBQAVAAADJAAP
hIoFE6TIABiEegQZhBEyGyaQIyQCLoSgBS+EuwBehIoFYSQAABUAAAMkAA+EigUTpDwAGIR6BBmE
ETIbJpAjJAIuhKAFL4S7AF6EigVhJAAACzgMAAA5DAAAQAwAAJAMAACRDAAAkgwAAJMMAACcDAAA
1AwAAAENAAAxDQAAjA0AAM0NAAALDgAAOw4AAI4OAADYDgAAEg8AAF4PAADIDwAAz2ABAAAAAAAA
AAAAAMkAAAAAAAAAAAAAAADJAAAAAAAAAAAAAAAAzwAAAAAAAAAAAAAAAMcAAAAAAAAAAAAAAADH
AAAAAAAAAAAAAAAAwQAAAAAAAAAAAAAAALoAAAAAAAAAAAAAAAC6AAAAAAAAAAAAAAAAugAAAAAA
AAAAAAAAALoAAAAAAAAAAAAAAAC6AAAAAAAAAAAAAAAAtAAAAAAAAAAAAAAAAK0AAAAAAAAAAAAA
AACmAAAAAAAAAAAAAAAApgAAAAAAAAAAAAAAALoAAAAAAAAAAAAAAAC6AAAAAAAAAAAAAAAArQAA
AAAAAAAAAAAAAAAAAAAABxUADcYIAAKwBO8lAAoHEwANxggAAtAC7yUACgAFEwANxgUAAe8lCgcU
AA3GCAAC4AHvJQAKBgAAAyQBQCYAYSQBAAEAAAYAABYkAUlmAQAAAAAvAAAWJAEXJAFJZgEAAAAC
lmwACNYaAAGU/20mAAbZJgAAAAAAAAAAAAAAAAAAAAAU9gEAABrWBAAAAP8b1gQAAAD/HNYEAAAA
/x3WBAAAAP801gYAAQoDbABh9gMAAAATEg0AACwNAAAtDQAALg0AAC8NAAAwDQAAbA0AAG0NAACH
DQAAiA0AAIkNAACKDQAAiw0AAK0NAACuDQAAyA0AAMkNAADKDQAAyw0AAMwNAADrDQAA7A0AAAYO
AAAHDgAACA4AAAkOAAAKDgAAGw4AABwOAAA2DgAANw4AADgOAAA5DgAAOg4AAG4OAABvDgAAiQ4A
AIoOAACLDgAAjA4AAI0OAAC4DgAAuQ4AANMOAADUDgAA1Q4AANYOAADXDgAA8g4AAPMOAAANDwAA
+evg+eD54PnS4Png+eD5xOD54Png+bbg+eD54Pmo4Png+eD5muD54Png+Yzg+eD54PkAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAABoCCIEDamtIAAAGCAFVCAFtSAAEbkgABHUIAQAaAgiBA2ruRwAA
BggBVQgBbUgABG5IAAR1CAEAGgIIgQNqcUcAAAYIAVUIAW1IAARuSAAEdQgBABoCCIEDavRGAAAG
CAFVCAFtSAAEbkgABHUIAQAaAgiBA2p3RgAABggBVQgBbUgABG5IAAR1CAEAGgIIgQNq+kUAAAYI
AVUIAW1IAARuSAAEdQgBABQDagAAAABVCAFtSAAEbkgABHUIAQAaAgiBA2p9RQAABggBVQgBbUgA
BG5IAAR1CAEAC21IAARuSAAEdQgBADINDwAADg8AAA8PAAAQDwAAEQ8AAD0PAAA+DwAAWA8AAFkP
AABaDwAAXA8AAF0PAACODwAAjw8AAKkPAACqDwAAxg8AAMcPAADlDwAA5g8AAAAQAAABEAAAHRAA
AB4QAAAfEAAAIBAAAEARAACbEQAA4xEAAOgRAADzEQAA+BEAAGcXAABaGAAAURoAAGoaAACMGgAA
xBoAAOYaAABhGwAAgxsAALQbAADXGwAAORwAAFwcAADFHAAA3RwAACIdAABVHQAA1B0AAPsdAABC
HgAAhh4AAEMiAABFIgAAyiUAAM0lAAAWJgAAGCYAACQnAAByJwAAmjEAAH0zAAB+MwAAkTMAAPLn
4efh5+HT5+Hn4efh58vn4efh58vn4cK6tLrhuuGvAK+pr6mvqa+pr6mvqa+pr6mvqa8ApwCnAKcA
rwCvwq8AAAAAAAAAAAAAA0gqAgs2CIFtSAkEc0gJBAhtSAkEc0gJBAALOwiBbUgJBHNICQQOOwiB
bUgABG5IAAR1CAEAEQNqAAAAAFUIAW1ICQRzSAkEDjUIgW1IAARuSAAEdQgBABoCCIEDamVJAAAG
CAFVCAFtSAAEbkgABHUIAQALbUgABG5IAAR1CAEUA2oAAAAAVQgBbUgABG5IAAR1CAEAGgIIgQNq
6EgAAAYIAVUIAW1IAARuSAAEdQgBQMgPAAAfEAAATxAAAJQQAADuEAAANREAAJ8RAADbEQAA9xEA
APgRAAD5EQAA+hEAABASAABFEgAASxIAAAgXAABnFwAAWxgAAGYYAAAxGgAAbBoAAMYaAABjGwAA
txsAADscAAD4AAAAAAAAAAAAAAAA7wAAAAAAAAAAAAAAAO8AAAAAAAAAAAAAAADvAAAAAAAAAAAA
AAAA7wAAAAAAAAAAAAAAAO8AAAAAAAAAAAAAAADvAAAAAAAAAAAAAAAA6AAAAAAAAAAAAAAAAOgA
AAAAAAAAAAAAAADgAAAAAAAAAAAAAAAA4AAAAAAAAAAAAAAAAOAAAAAAAAAAAAAAAADdAAAAAAAA
AAAAAAAA2wAAAAAAAAAAAAAAANkAAAAAAAAAAAAAAADZAAAAAAAAAAAAAAAA2QAAAAAAAAAAAAAA
ANsAAAAAAAAAAAAAAADVAAAAAAAAAAAAAAAA0wAAAAAAAAAAAAAAANMAAAAAAAAAAAAAAADTAAAA
AAAAAAAAAAAA0wAAAAAAAAAAAAAAANMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAExAAADAAAUpHgA
AAEAAAABAQADNABAJgAABzYABSQABiQAMSQAQCYABxQADcYIAAKgBTonAAoACBQADcYLAAOgBXAI
OicAAgoHEwANxggAAtAC7yUACgAYOxwAAMccAAA0HQAA2x0AAEEeAABCHgAAUB4AAIYeAAClHgAA
ux4AANEeAADqHgAA/x4AABMfAAAnHwAAQh8AAFcfAACHHwAAtB8AAMwfAADlHwAAACAAABIgAAA2
IAAAViAAAHcgAACcIAAAsSAAANAgAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAA
AAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD4AAAAAAAAAAAAAAAA
9AAAAAAAAAAAAAAAAPIAAAAAAAAAAAAAAADyAAAAAAAAAAAAAAAA8gAAAAAAAAAAAAAAAPIAAAAA
AAAAAAAAAADyAAAAAAAAAAAAAAAA8gAAAAAAAAAAAAAAAPIAAAAAAAAAAAAAAADyAAAAAAAAAAAA
AAAA8gAAAAAAAAAAAAAAAPIAAAAAAAAAAAAAAADyAAAAAAAAAAAAAAAA8gAAAAAAAAAAAAAAAPIA
AAAAAAAAAAAAAADyAAAAAAAAAAAAAAAA8gAAAAAAAAAAAAAAAPIAAAAAAAAAAAAAAADyAAAAAAAA
AAAAAAAA8gAAAAAAAAAAAAAAAPIAAAAAAAAAAAAAAADyAAAAAAAAAAAAAAAAAAAAAAABVQAAA1UA
E6SIAAMAAAYkAQABAQAAATEAABzQIAAA6yAAAAUhAAAtIQAAUyEAAG0hAACLIQAAqSEAAAAiAABC
IgAAlSIAAKoiAADOIgAA+iIAACIjAABaIwAAbyMAAIIjAACfIwAAvCMAANojAADzIwAAGyQAADEk
AABVJAAAeyQAAJckAACuJAAAtyQAAM8kAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAA
AAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAA
AAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0A
AAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAA
AAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAA
AP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAA
AAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAA
AAAAAAAAAAAAAAAAAAABVQAAHc8kAADyJAAAEyUAADUlAABPJQAAXyUAAGwlAACcJQAAySUAABUm
AABwJgAAhSYAAKcmAADKJgAA3iYAAO8mAAAKJwAAIycAACQnAAByJwAAgygAAIsqAADMLQAA5S4A
AG8wAACaMQAAmzEAALoxAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9
AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAA
AAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAA
AAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAA
AAAAAAAAAAAAAP0AAAAAAAAAAAAAAADzAAAAAAAAAAAAAAAA8QAAAAAAAAAAAAAAAOwAAAAAAAAA
AAAAAADsAAAAAAAAAAAAAAAA7AAAAAAAAAAAAAAAAOwAAAAAAAAAAAAAAADxAAAAAAAAAAAAAAAA
8QAAAAAAAAAAAAAAAOoAAAAAAAAAAAAAAAAAAAAAAAABAQAABAAABSQBBiQBAAEAAAAJAQAPhBgD
EYTo/F6EGANghOj8AAFVAAAbujEAAH0zAACuMwAAFDUAANk1AAB/NgAAODgAAFo4AABBOQAAQTwA
AEM8AACSPAAA9D0AACM+AACNPgAAGD8AALw/AAAMQAAAXkAAAE5BAABaQQAAikIAALdCAAB5QwAA
+kMAAE9FAADLSAAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAA
AAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAP0AAAAAAAAAAAAA
AAD9AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAOsAAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAA
AAAAAAAAAAAAAOYAAAAAAAAAAAAAAADmAAAAAAAAAAAAAAAA5gAAAAAAAAAAAAAAAOYAAAAAAAAA
AAAAAADmAAAAAAAAAAAAAAAA5gAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA
5AAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA3wAAAAAAAAAAAAAAAP0AAAAA
AAAAAAAAAAAABAAABSQBBiQBAAEDAAUAAAomAAtGEQAACl4AGIQAABmEAAAbJgAjJAAvhAAAAAQA
AAMkAWEkAQABAgAAAQAAABqRMwAAkjMAAJMzAACUMwAAWjgAAEE8AABCPAAAQzwAAEo8AABLPAAA
YTwAAGI8AABjPAAAZDwAAJI8AABOQQAAt0UAALlFAAD9RQAA/0UAADJHAAA0RwAA8kcAAPVHAAAq
SAAALEgAAOBOAABzUQAAWVQAAGlUAACxVAAA3lQAACJVAAAjVQAAS1UAAI9VAACTVQAAllUAAJtV
AACyVQAAtFUAAAxWAAARVgAAQFYAAEJWAABQVgAAUlYAAGBWAABiVgAAZ1YAAGlWAABuVgAAcFYA
AHRWAAB5VgAAiVYAAItWAACYVgAAp1YAAKhWAACCWAAAg1gAAAtZAAAMWQAAc1kAAHRZAADXWgAA
2VoAAGJbAADu49rVANAAzcbNxr7GzQDVuNW41bjVuNW41QDVstUAsACwALAAsACuALAArgCuAK4A
rgCuALAArgDVANUA1QDVANUAsgAAAAADSCoBAzUIgQs1CIFtSAkEc0gJBAtIKgFtSAkEc0gJBA9D
ShYAbUgABG5IAAR1CAENA2oAAAAAQ0oWAFUIAQRDShYAAAkDakpLAABVCAEIbUgJBHNICQQAEQNq
AAAAAFUIAW1ICQRzSAkEFQNq4kkAAEVI9v9VCAFtSAkEc0gJBCEDagARQz8KCAE1CIFDShQAVQgB
VggBbUgABG5IAAR1CAEARMtIAADoSQAAGEoAANtKAABQSwAArEsAAHFMAAC1TAAAxE4AAOBOAABz
UQAAl1EAABlTAADsUwAAWFQAAFlUAABpVAAAsVQAALJUAACzVAAAv1QAAP0AAAAAAAAAAAAAAAD7
AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAA
AAAAAAAAAPYAAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAP0AAAAAAAAAAAAA
AAD7AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD0AAAAAAAAAAAAAAAA/QAA
AAAAAAAAAAAAAPEAAAAAAAAAAAAAAADtAAAAAAAAAAAAAAAA5AAAAAAAAAAAAAAAAOQAAAAAAAAA
AAAAAADYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAALEAAFJAAT
pHgAFKQAABYkAUlmAQAAAAkAAAMkARYkAUlmAQAAAGEkAQADJQATpAAAAykAByQBAAFDAAUAAAom
AAtGEwAAAQMAAAEAAAAUv1QAAMBUAADeVAAABlUAAA5VAAAPVQAAF1UAABlVAAAaVQAAIlUAACNV
AAArVQAALFUAAHwwAgAAAAAAAAAAAABxAAAAAAAAAAAAAAAAcQAAAAAAAAAAAAAAAGgAAAAAAAAA
AAAAAABoAAAAAAAAAAAAAAAAaAAAAAAAAAAAAAAAAGgAAAAAAAAAAAAAAABoAAAAAAAAAAAAAAAA
aAAAAAAAAAAAAAAAAGgAAAAAAAAAAAAAAABoAAAAAAAAAAAAAAAAaAAAAAAAAAAAAAAAAAkAAAMk
ARYkAUlmAQAAAGEkAQsPAAUkAAYkABOkeAAWJAFJZgEAAACDAAAWJAEXJAFJZgEAAAAAVAEAApZs
AAM0AQXWGAYBAQAGAQEABgEBAAYBAQAGAQEABgEBAAjWRgADlP9SBfAM9CYABr4F//////////8E
AQAA/////wAGngf//////////wQBAAAEAQAAAAYEGgAAAAD/////AAAAAAAAAAAKdBAAHwAT1jAA
AAAABgEAAAAAAAAGAQAAAAAAAAYBAAAAAAAABgEAAAAAAAAGAQAAAAAAAAYBAAAU9gEAABrWDP//
////////AAAA/xvWDP///////////////xzWDAAAAP8AAAD/AAAA/x3WDP////8AAAD/AAAA/zTW
BgABCgNsAGH2AwAAAAwsVQAANFUAADVVAAA9VQAAS1UAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAA
AAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJAAADJAEW
JAFJZgEAAABhJAEABEtVAABMVQAAHigBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAADgAAAWJAEXJAFJZgEAAAAAVAEAApZsAAXWGAYBAQAGAQEABgEBAAYB
AQAGAQEABgEBAAjWtAAIlP9SBfAM7BAkFVwZlB0mIvQmAAa+Bf////8AAAAAAAAAAAAAAAAABp4H
/////wAAAAAAAAAAAAAAAAAG/AMAAAAAAAAAAAAAAAAAAAAAAAY4BAAAAAAAAAAAAAAAAAAAAAAA
BjgEAAAAAAAAAAAAAAAAAAAAAAAGOAQAAAAAAAAAAAAAAAAAAAAAAAaSBAAAAAAAAAAAAAAAAAAA
AAAABs4EAAAAAAAAAAAAAAAAAAAAAAp0EAAfABPWMAAAAAAGAQAAAAAAAAYBAAAAAAAABgEAAAAA
AAAGAQAAAAAAAAYBAAAAAAAABgEAABT2AQAAGtYg//////////8AAAD/AAAA/wAAAP8AAAD/AAAA
/wAAAP8b1iAAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xzWIAAAAP8AAAD/AAAA/wAA
AP8AAAD/AAAA/wAAAP8AAAD/HdYgAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYA
AQoDbABh9gMAAAABTFUAAFFVAAB3VQAAfVUAAINVAACJVQAAj1UAAJNVAACVVQAA8wAAAAAAAAAA
AAAAAOoAAAAAAAAAAAAAAADfAAAAAAAAAAAAAAAA6gAAAAAAAAAAAAAAAN8AAAAAAAAAAAAAAADq
AAAAAAAAAAAAAAAA0gAAAAAAAAAAAAAAAOoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADRAABSQABiQAE6R4ABSkAAAWJAFJZgEA
AAALDwAFJAAGJAATpHgAFiQBSWYBAAAACQAAAyQBFiQBSWYBAAAAYSQBAAsQAAUkABOkeAAUpAAA
FiQBSWYBAAAAAAiVVQAAllUAAJtVAAAe2AEAAAAAAAAAAAAAFQAAAAAAAAAAAAAAAAAAAAAJAAAD
JAEWJAFJZgEAAABhJAEA4AAAFiQBFyQBSWYBAAAAAFQBAAKWbAAF1hgGAQEABgEBAAYBAQAGAQEA
BgEBAAYBAQAI1rQACJT/UgXwDOwQJBVcGZQdJiL0JgAGvgUAAAAAAAAAAAAAAAAAAAAAAAaeBwAA
AAAAAAAAAAAAAAAAAAAABvwDAAAAAAAAAAAAAAAAAAAAAAAGOAQAAAAAAAAAAAAAAAAAAAAAAAY4
BAAAAAAAAAAAAAAAAAAAAAAABjgEAAAAAAAAAAAAAAAAAAAAAAAGkgQAAAAAAAAAAAAAAAAAAAAA
AAbOBAAAAAAAAAAAAAAAAAAAAAAKdBAAHwAT1jAAAAAABgEAAAAAAAAGAQAAAAAAAAYBAAAAAAAA
BgEAAAAAAAAGAQAAAAAAAAYBAAAU9gEAABrWIAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/G9YgAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c1iAAAAD/AAAA/wAAAP8AAAD/
AAAA/wAAAP8AAAD/AAAA/x3WIAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/NNYGAAEK
A2wAYfYDAAAAAptVAADnVQAA9VUAAANWAAAFVgAAB1YAAAlWAAALVgAA9gAAAAAAAAAAAAAAAPYA
AAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAA
AAAAAAAA9gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkAAAMkARYkAUlm
AQAAAGEkAQAHC1YAAAxWAAARVgAAHqABAAAAAAAAAAAAABUAAAAAAAAAAAAAAAAAAAAACQAAAyQB
FiQBSWYBAAAAYSQBAOAAABYkARckAUlmAQAAAABUAQAClmwABdYYBgEBAAYBAQAGAQEABgEBAAYB
AQAGAQEACNa0AAiU/1IF8AzsECQVXBmUHSYi9CYABr4FAAAAAAAAAAAAAAAAAAAAAAAGngcAAAAA
AAAAAAAAAAAAAAAAAAb8AwAAAAAAAAAAAAAAAAAAAAAABjgEAAAAAAAAAAAAAAAAAAAAAAAGOAQA
AAAAAAAAAAAAAAAAAAAAAAY4BAAAAAAAAAAAAAAAAAAAAAAABpIEAAAAAAAAAAAAAAAAAAAAAAAG
zgQAAAAAAAAAAAAAAAAAAAAACnQQAB8AE9YwAAAAAAYBAAAAAAAABgEAAAAAAAAGAQAAAAAAAAYB
AAAAAAAABgEAAAAAAAAGAQAAFPYBAAAa1iAAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA
/xvWIAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYgAAAA/wAAAP8AAAD/AAAA/wAA
AP8AAAD/AAAA/wAAAP8d1iAAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABCgNs
AGH2AwAAAAIRVgAAPFYAAExWAABcVgAAY1YAAGpWAABxVgAAc1YAAPYAAAAAAAAAAAAAAAD2AAAA
AAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAA
AAAAAPYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJAAADJAEWJAFJZgEA
AABhJAEAB3NWAAB0VgAAeVYAAB6QAAAAAAAAAAAAAAAVAAAAAAAAAAAAAAAAAAAAAAkAAAMkARYk
AUlmAQAAAGEkAQDgAAAWJAEXJAFJZgEAAAAAVAEAApZsAAXWGAYBAQAGAQEABgEBAAYBAQAGAQEA
BgEBAAjWtAAIlP9SBfAM7BAkFVwZlB0mIvQmAAa+BQAAAAAAAAAAAAAAAAAAAAAABp4HAAAAAAAA
AAAAAAAAAAAAAAAG/AMAAAAAAAAAAAAAAAAAAAAAAAY4BAAAAAAAAAAAAAAAAAAAAAAABjgEAAAA
AAAAAAAAAAAAAAAAAAAGOAQAAAAAAAAAAAAAAAAAAAAAAAaSBAAAAAAAAAAAAAAAAAAAAAAABs4E
AAAAAAAAAAAAAAAAAAAAAAp0EAAfABPWMAAAAAAGAQAAAAAAAAYBAAAAAAAABgEAAAAAAAAGAQAA
AAAAAAYBAAAAAAAABgEAABT2AQAAGtYgAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b
1iAAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xzWIAAAAP8AAAD/AAAA/wAAAP8AAAD/
AAAA/wAAAP8AAAD/HdYgAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQoDbABh
9gMAAAACeVYAAIVWAACVVgAAl1YAAJhWAACnVgAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2
AAAAAAAAAAAAAAAAYEAAAAAAAAAAAAAAAFgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAB0MABiQBFiQBSWYBAAAAlgAAFiQBFyQBSWYBAAAAAFQBAAKWbAADNAEF1hgG
AQEABgEBAAYBAQAGAQEABgEBAAYBAQAI1lwABJT/UgXwDCYi9CYABr4FAAAAAAAAAAAAAAAAAAAA
AAAGngcAAAAAAAAAAAAAAAAAAAAAAAY2FQAAAAAAAAAAAAAAAAAAAAAABs4EAAAAAAAAAAAAAAAA
AAAAAAp0EAAfABPWMAAAAAAGAQAAAAAAAAYBAAAAAAAABgEAAAAAAAAGAQAAAAAAAAYBAAAAAAAA
BgEAABT2AQAAGtYQAAAA/wAAAP8AAAD/AAAA/xvWEAAAAP8AAAD/AAAA/wAAAP8c1hAAAAD/AAAA
/wAAAP8AAAD/HdYQAAAA/wAAAP8AAAD/AAAA/zTWBgABCgNsAGH2AwAACQAAAyQBFiQBSWYBAAAA
YSQBAAWnVgAAqFYAAIJYAACDWAAAC1kAAAxZAACibAcAAAAAAAAAAAAAlQAAAAAAAAAAAAAAADgk
AgAAAAAAAAAAAACVAAAAAAAAAAAAAAAAOKABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAXQAAFiQBFyQBSWYBAAAAAFQBAAKWbAADNAEF1hgGAQEABgEBAAYBAQAGAQEABgEBAAYBAQAI
1hoAAZT/9CYABmAn/////wAAAAD/////AAAAAAp0EAAfABPWMAAAAAAGAQAAAAAAAAYBAAAAAAAA
BgEAAAAAAAAGAQAAAAAAAAYBAAAAAAAABgEAABT2AQAAGtYE/////xvWBAAAAP8c1gT/////HdYE
AAAA/zTWBgABCgNsAGH2AwAADSQAAyQDE6R4ABSkeAAWJAFJZgEAAABhJANdAAAWJAEXJAFJZgEA
AAAAVAEAApZsAAM0AQXWGAYBAQAGAQEABgEBAAYBAQAGAQEABgEBAAjWGgABlP/0JgAGYCcAAAAA
AAAAAP////8AAAAACnQQAB8AE9YwAAAAAAYBAAAAAAAABgEAAAAAAAAGAQAAAAAAAAYBAAAAAAAA
BgEAAAAAAAAGAQAAFPYBAAAa1gQAAAD/G9YEAAAA/xzWBP////8d1gQAAAD/NNYGAAEKA2wAYfYD
AAAABQxZAABzWQAAdFkAANdaAADYWgAA9QAAAAAAAAAAAAAAAJiQBQAAAAAAAAAAAACLAAAAAAAA
AAAAAAAALgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAXQAAFiQBFyQBSWYBAAAAAFQB
AAKWbAADNAEF1hgGAQEABgEBAAYBAQAGAQEABgEBAAYBAQAI1hoAAZT/9CYABmAn/////wAAAAAA
AAAAAAAAAAp0EAAfABPWMAAAAAAGAQAAAAAAAAYBAAAAAAAABgEAAAAAAAAGAQAAAAAAAAYBAAAA
AAAABgEAABT2AQAAGtYE/////xvWBAAAAP8c1gQAAAD/HdYEAAAA/zTWBgABCgNsAGH2AwAADSQA
AyQDE6R4ABSkeAAWJAFJZgEAAABhJANdAAAWJAEXJAFJZgEAAAAAVAEAApZsAAM0AQXWGAYBAQAG
AQEABgEBAAYBAQAGAQEABgEBAAjWGgABlP/0JgAGYCf/////AAAAAP////8AAAAACnQQAB8AE9Yw
AAAAAAYBAAAAAAAABgEAAAAAAAAGAQAAAAAAAAYBAAAAAAAABgEAAAAAAAAGAQAAFPYBAAAa1gT/
////G9YEAAAA/xzWBP////8d1gQAAAD/NNYGAAEKA2wAYfYDAAAKJAATpHgAFKR4ABYkAUlmAQAA
AAAE2FoAANlaAABiWwAAIF4AAIteAACLXwAAQ2AAANdgAADYYAAA2WAAAPtgAAB5ZAAAT2UAAGdl
AADKZQAA2mUAAPZlAAD9AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAA
AAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAA
AAAAAJYAAAAAAAAAAAAAAACUAAAAAAAAAAAAAAAAkgAAAAAAAAAAAAAAAJIAAAAAAAAAAAAAAACU
AAAAAAAAAAAAAAAAkgAAAAAAAAAAAAAAAJAAAAAAAAAAAAAAAACMAAAAAAAAAAAAAAAAAAAAAAAD
JQATpAAAAAEpAAABAAAAAQMAWgAAFiQBFyQBSWYBAAAAAFQBAAKWawADNAEF1hgEAQAABAEAAAQB
AAAEAQAAAAAAAAAAAAAI1hoAAZX/PSUABqglAAAAAAAAAAAAAAAAAAAAABPWMAAAAP8EAQAAAAAA
/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wAAAAAAAAD/AAAAABT2AQAAGtYEAAAA/xvWBAAAAP8c
1gQAAAD/HdYEAAAA/zTWBgABCgNrAGH2AwAABkMAFiQBSWYBAAAAAAYkAAMkARSkeABhJAEAASQA
ABBiWwAAOmAAADxgAADZYAAA+2AAAE5lAABPZQAAZmUAAMhlAADJZQAAymUAAPVlAADEaAAAfGkA
AFlqAAARawAAH2sAALRtAAD1bQAAnG4AAM9uAADqbgAA624AAF9vAABhbwAA6G8AAOpvAAC2cAAA
xHAAAIRxAABFcwAAdXMAAHZzAACJcwAAinMAAItzAACMcwAAjnMAAJlzAACecwAAqnMAAKxzAADd
cwAA4HMAADJ1AAA0dQAAVXUAAFd1AADNdQAAznUAANB1AADSdQAACXYAAAt2AABHdgAASHYAAF52
AABfdgAAYHYAAGF2AABpdgAAanYAAIB2AACBdgAA+/X7APsA+wD7APsA+wD78/vt++377fv1+/X7
8/sA++T71Mnk+wDHAMUAxwDFAMUAwQDFAMUAvACsp7wAvAC8AAAAAAAAAAAAAAAAAAAACQNqCFwA
AFUIAR4DakrwtD4KCAFDShQAVQgBVggBbUgABG5IAAR1CAEACQNqAAAAAFUIAQYJagEAo/AAA0gq
AQNIKgIVA2ruWQAARUj4/1UIAW1ICQRzSAkEHgNq3Nd6PgoIAUNKFABVCAFWCAFtSAAEbkgABHUI
AQARA2oAAAAAVQgBbUgJBHNICQQLNQiBbUgJBHNICQQDNgiBC0gqAW1ICQRzSAkECG1ICQRzSAkE
P/ZlAAAAZgAAGGYAAChmAAA7ZgAAPGYAAD5mAAB3ZgAAtGYAANVmAAD2AAAAAAAAAAAAAAAA8AAA
AAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAAWmgCAAAAAAAAAAAAAPYAAAAAAAAA
AAAAAABRAAAAAAAAAAAAAAAAUQAAAAAAAAAAAAAAAFEAAAAAAAAAAAAAAAAAAAAAAAkAAAMkABYk
AUlmAQAAAGEkAJYAABYkARckAUlmAQAAAABUAQAClmwAAzQBBdYYDAEBAAwBAQAMAQEADAEBAAYB
AQAGAQEACNZcAASU/xgEHw4mGC0iAAaEBAAAAAAAAAAADAEBAAAAAAAABgcKAAAAAAAAAAAMAQEA
AAAAAAAGBwoAAAAAAAAAAAwBAQAAAAAAAAYHCgAAAAAAAAAADAEBAAAAAAAKdBQAvwAT1jAAAAAA
DAEAAAAAAAAMAQAAAAAAAAwBAAAAAAAADAEAAAAAAAAGAQAAAAAAAAYBAAAU9gEAABrWEAAAAP8A
AAD/AAAA/wAAAP8b1hAAAAD/AAAA/wAAAP8AAAD/HNYQAAAAAAAAAAAAAAAAAAAAAB3WEAAAAP8A
AAD/AAAA/wAAAP801gYAAQoDbABh9gMAAAYAABYkAUlmAQAAAAkAAAMkARYkAUlmAQAAAGEkAQAJ
1WYAANZmAADYZgAADmcAAA9nAAA2ZwAAaYQBAAAAAAAAAAAAAGAAAAAAAAAAAAAAAABXAAAAAAAA
AAAAAAAAVwAAAAAAAAAAAAAAAFcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAACQAAAyQAFiQBSWYBAAAAYSQACQAAAyQBFiQBSWYBAAAAYSQBlgAAFiQBFyQBSWYBAAAAAFQB
AAKWbAADNAEF1hgMAQEADAEBAAwBAQAMAQEABgEBAAYBAQAI1lwABJT/GAQfDiYYLSIABoQE////
/wAAAAAAAAAAAAAAAAAGBwr/////AAAAAAAAAAAAAAAA4AYHCv////8AAAAAAAAAAAAAAAAABgcK
/////wAAAAAAAAAAAAAAAAp0FAC/ABPWMAAAAAAMAQAAAAAAAAwBAAAAAAAADAEAAAAAAAAMAQAA
AAAAAAYBAAAAAAAABgEAABT2AQAAGtYQ/////////////////////xvWEAAAAP8AAAD/AAAA/wAA
AP8c1hAAAAD/AAAA/wAAAP8AAAD/HdYQAAAA/wAAAP8AAAD/AAAA/zTWBgABCgNsAGH2AwAAAAU2
ZwAAN2cAADlnAABrZwAAiWcAAKpnAABp0AEAAAAAAAAAAAAAYAAAAAAAAAAAAAAAAFcAAAAAAAAA
AAAAAABXAAAAAAAAAAAAAAAAVwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAJAAADJAAWJAFJZgEAAABhJAAJAAADJAEWJAFJZgEAAABhJAGWAAAWJAEXJAFJZgEAAAAAVAEA
ApZsAAM0AQXWGAwBAQAMAQEADAEBAAwBAQAGAQEABgEBAAjWXAAElP8YBB8OJhgtIgAGhAQAAAAA
AAAAAAAAAAAAAAAAAAYHCgAAAAAAAAAAAAAAAAAAAAAgBgcKAAAAAAAAAAAAAAAAAAAAAAAGBwoA
AAAAAAAAAAAAAAAAAAAACnQUAL8AE9YwAAAAAAwBAAAAAAAADAEAAAAAAAAMAQAAAAAAAAwBAAAA
AAAABgEAAAAAAAAGAQAAFPYBAAAa1hAAAAD/AAAA/wAAAP8AAAD/G9YQAAAA/wAAAP8AAAD/AAAA
/xzWEAAAAP8AAAD/AAAA/wAAAP8d1hAAAAD/AAAA/wAAAP8AAAD/NNYGAAEKA2wAYfYDAAAABapn
AACrZwAArWcAAMxnAADNZwAA9GcAAGkoAQAAAAAAAAAAAABgAAAAAAAAAAAAAAAAVwAAAAAAAAAA
AAAAAFcAAAAAAAAAAAAAAABXAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAkAAAMkABYkAUlmAQAAAGEkAAkAAAMkARYkAUlmAQAAAGEkAZYAABYkARckAUlmAQAAAABUAQAC
lmwAAzQBBdYYDAEBAAwBAQAMAQEADAEBAAYBAQAGAQEACNZcAASU/xgEHw4mGC0iAAaEBAAAAAAA
AAAAAAAAAAAAAAAABgcKAAAAAAAAAAAAAAAAAAAAAOAGBwoAAAAAAAAAAAAAAAAAAAAAAAYHCgAA
AAAAAAAAAAAAAAAAAAAKdBQAvwAT1jAAAAAADAEAAAAAAAAMAQAAAAAAAAwBAAAAAAAADAEAAAAA
AAAGAQAAAAAAAAYBAAAU9gEAABrWEAAAAP8AAAD/AAAA/wAAAP8b1hAAAAD/AAAA/wAAAP8AAAD/
HNYQAAAA/wAAAP8AAAD/AAAA/x3WEAAAAP8AAAD/AAAA/wAAAP801gYAAQoDbABh9gMAAAAF9GcA
APVnAAD3ZwAANmgAAFBoAABfaAAAaawBAAAAAAAAAAAAAGAAAAAAAAAAAAAAAABRAAAAAAAAAAAA
AAAASAAAAAAAAAAAAAAAAEgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACQAAAyQAFiQBSWYBAAAAYSQADzIADcYPAgwTGCYD
pwQ0BsEHwMDAFiQBSWYBAAAACQAAAyQBFiQBSWYBAAAAYSQBlgAAFiQBFyQBSWYBAAAAAFQBAAKW
bAADNAEF1hgMAQEADAEBAAwBAQAMAQEABgEBAAYBAQAI1lwABJT/GAQfDiYYLSIABoQEAAAAAAAA
AAAAAAAAAAAAAAAGBwoAAAAAAAAAAAAAAAAAAAAAIAYHCgAAAAAAAAAAAAAAAAAAAAAABgcKAAAA
AAAAAAAAAAAAAAAAAAp0FAC/ABPWMAAAAAAMAQAAAAAAAAwBAAAAAAAADAEAAAAAAAAMAQAAAAAA
AAYBAAAAAAAABgEAABT2AQAAGtYQAAAA/wAAAP8AAAD/AAAA/xvWEAAAAP8AAAD/AAAA/wAAAP8c
1hAAAAD/AAAA/wAAAP8AAAD/HdYQAAAA/wAAAP8AAAD/AAAA/zTWBgABCgNsAGH2AwAAAAVfaAAA
YGgAAGJoAACTaAAAtGgAAMNoAADEaAAAxWgAAAxpAABkaQAAaZABAAAAAAAAAAAAAGAAAAAAAAAA
AAAAAABXAAAAAAAAAAAAAAAAVwAAAAAAAAAAAAAAAFcAAAAAAAAAAAAAAABpAAAAAAAAAAAAAAAA
VQAAAAAAAAAAAAAAAFUAAAAAAAAAAAAAAABVAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAJ
AAADJAAWJAFJZgEAAABhJAAJAAADJAEWJAFJZgEAAABhJAGWAAAWJAEXJAFJZgEAAAAAVAEAApZs
AAM0AQXWGAwBAQAMAQEADAEBAAwBAQAGAQEABgEBAAjWXAAElP8YBB8OJhgtIgAGhAQAAAAAAAAA
AAAAAAAAAAAAAAYHCgAAAAAAAAAAAAAAAAAAAAAABgcKAAAAAAAAAAAAAAAAAAAAAAAGBwoAAAAA
AAAAAAAAAAAAAAAACnQUAL8AE9YwAAAAAAwBAAAAAAAADAEAAAAAAAAMAQAAAAAAAAwBAAAAAAAA
BgEAAAAAAAAGAQAAFPYBAAAa1hAAAAD/AAAA/wAAAP8AAAD/G9YQAAAA/wAAAP8AAAD/AAAA/xzW
EAAAAP8AAAD/AAAA/wAAAP8d1hAAAAD/AAAA/wAAAP8AAAD/NNYGAAEKA2wAYfYDAAAACWRpAAB8
aQAAWWoAAIRqAAAFawAABmsAABFrAAAfawAAQWsAAEJrAAAUbQAAFW0AALRtAADCbQAA1G0AAOZt
AAD1bQAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAA
APsAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9AAAAAAAAAAAAAAAAPIAAAAAAAAAAAAAAAD7AAAA
AAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA5wAAAAAAAAAA
AAAAAOcAAAAAAAAAAAAAAADnAAAAAAAAAAAAAAAA5wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAkAAAMkARYkAUlmAQAAAGEkAQABJQAAAS8AAAEPAAAEEgAHJAFAJgAAAQAAAAEBAAAQ9W0AAPZt
AAD4bQAAAm4AAAxuAAAWbgAAb4QAAAAAAAAAAAAAAGYAAAAAAAAAAAAAAABmAAAAAAAAAAAAAAAA
ZgAAAAAAAAAAAAAAAGYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACQAAAyQBFiQBSWYBAAAAYSQBAI8AABYkARckAUlm
AQAAAAKWbAAF1hgEAQAABAEAAAQBAAAEAQAABAEAAAQBAAAI1lwABJT/OgjgEIYZLCIABqYIAAAA
AAAAAAAAAAAAAAAAAAAGpggAAAAAAAAAAAAAAAAAAAAAAAamCAAAAAAAAAAAAAAAAAAAAAAABqYI
AAAAAAAAAAAAAAAAAAAAABPWMAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQB
AAAAAAD/BAEAABT2AQAAGtYQAAAA/wAAAP8AAAD/AAAA/xvWEAAAAP8AAAD/AAAA/wAAAP8c1hAA
AAD/AAAA/wAAAP8AAAD/HdYQAAAA/wAAAP8AAAD/AAAA/zTWBgABCgNsAGH2AwAAAAUWbgAAF24A
ABluAAAabgAAJG4AAC5uAABuYAAAAAAAAAAAAAAAZQAAAAAAAAAAAAAAAGUAAAAAAAAAAAAAAABl
AAAAAAAAAAAAAAAAZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACQAAAyQBFiQBSWYBAAAAYSQBkQAAFiQBFyQBSWYBAAAA
ApZsAAM0AQXWGAQBAAAEAQAABAEAAAQBAAAEAQAABAEAAAjWXAAElP86COAQhhksIgAGpggAAAAA
AAAAAAAAAAAAAAAA4AamCAAAAAAAAAAAAAAAAAAAAAAABqYIAAAAAAAAAAAAAAAAAAAAAAAGpggA
AAAAAAAAAAAAAAAAAAAAE9YwAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEA
AAAAAP8EAQAAFPYBAAAa1hAAAAD/AAAA/wAAAP8AAAD/G9YQAAAA/wAAAP8AAAD/AAAA/xzWEAAA
AP8AAAD/AAAA/wAAAP8d1hAAAAD/AAAA/wAAAP8AAAD/NNYGAAEKA2wAYfYDAAAABS5uAAAvbgAA
nG4AAKxuAADrbgAAbgAAAAAAAAAAAAAAAGwAAAAAAAAAAAAAAABjAAAAAAAAAAAAAAAAYwAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAkAAAMkARYkAUlmAQAAAGEkAQABJQCRAAAWJAEXJAFJZgEAAAAC
lmwAAzQBBdYYBAEAAAQBAAAEAQAABAEAAAQBAAAEAQAACNZcAASU/zoI4BCGGSwiAAamCAAAAAAA
AAAAAAAAAAAAAAAgBqYIAAAAAAAAAAAAAAAAAAAAAAAGpggAAAAAAAAAAAAAAAAAAAAAAAamCAAA
AAAAAAAAAAAAAAAAAAAT1jAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAA
AAAA/wQBAAAU9gEAABrWEAAAAP8AAAD/AAAA/wAAAP8b1hAAAAD/AAAA/wAAAP8AAAD/HNYQAAAA
/wAAAP8AAAD/AAAA/x3WEAAAAP8AAAD/AAAA/wAAAP801gYAAQoDbABh9gMAAAAE624AAOxuAAD9
bgAABm8AAAdvAAASbwAAGW8AABpvAAAbbwAA7W8AAGFwAACpcAAAqnAAALZwAACTbAAAAAAAAAAA
AAAAigAAAAAAAAAAAAAAAH8AAAAAAAAAAAAAAACTTAAAAAAAAAAAAAAAigAAAAAAAAAAAAAAAIoA
AAAAAAAAAAAAAACTAAAAAAAAAAAAAAAAegAAAAAAAAAAAAAAAHgAAAAAAAAAAAAAAAB4AAAAAAAA
AAAAAAAAeAAAAAAAAAAAAAAAAHgAAAAAAAAAAAAAAABzAAAAAAAAAAAAAAAAAAAAAAAABC0AByQB
QCYAAAEAAAAEAAADJAFhJAELDwAFJAAGJAATpHgAFiQBSWYBAAAACQAAAyQBFiQBSWYBAAAAYSQB
AGsAABYkARckAUlmAQAAAABUAQAClmwABdYYBAEAAAQBAAAEAQAABAEAAAQBAAAEAQAACNYwAAKU
/9QKFBYABkALAAAAAAAAAAAAAAAAAAAAAAAGQAsAAAAAAAAAAAAAAAAAAAAAE9YwAAAA/wQBAAAA
AAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAFPYBAAAa1ggAAAD/AAAA/xvW
CAAAAP8AAAD/HNYIAAAA/wAAAP8d1ggAAAD/AAAA/zTWBgABCgNsAGH2AwAAAA22cAAAxHAAAPtw
AAD8cAAAhHEAABpyAABdcgAAlHIAAPFyAABFcwAAdXMAAI5zAACVcwAA2XMAABB0AAARdAAAFHUA
ABV1AABGdgAAR3YAAGJ2AADIdgAAhXcAAJ53AACfdwAApncAAOl3AAD9AAAAAAAAAAAAAAAA+wAA
AAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9AAAAAAAAAAAAAAAAO8AAAAAAAAA
AAAAAADvAAAAAAAAAAAAAAAA7wAAAAAAAAAAAAAAAO8AAAAAAAAAAAAAAAD0AAAAAAAAAAAAAAAA
9AAAAAAAAAAAAAAAAO0AAAAAAAAAAAAAAADoAAAAAAAAAAAAAAAA6AAAAAAAAAAAAAAAAO0AAAAA
AAAAAAAAAADtAAAAAAAAAAAAAAAA7QAAAAAAAAAAAAAAAO0AAAAAAAAAAAAAAADtAAAAAAAAAAAA
AAAA4wAAAAAAAAAAAAAAAOEAAAAAAAAAAAAAAAD0AAAAAAAAAAAAAAAA9AAAAAAAAAAAAAAAAPQA
AAAAAAAAAAAAAADtAAAAAAAAAAAAAAAA6AAAAAAAAAAAAAAAAAAAAAAAAV4AAARZAAMkAWEkAQVZ
AAomAAtGAQAAAVkABVkACiYAC0YCAAABAAAABC4AAyQAYSQAAAEvAAABLgAAGoF2AACCdgAAg3YA
AMh2AACFdwAAhncAAJl3AACadwAAm3cAAJx3AACfdwAAqncAAK13AADtdwAA8HcAAKZ4AACoeAAA
EXoAACB6AAAuegAAgHoAAHp+AACcfgAAF4AAABiAAAAZgAAAIIAAACGAAAA3gAAAOIAAADmAAAA6
gAAAUIAAAGGAAABigAAAgYEAAIeBAACIgQAAnYEAAJ6BAACfgQAAoIEAANeBAADYgQAAA4UAAAqF
AAALhQAAIYUAACKFAAAjhQAAJIUAAE2FAABOhQAAT4UAAGiFAACVhgAAl4YAAASHAAAKhwAADIcA
AA2HAAD59ADv5u/YzebvAMsAywDJAO/D7wDvALrvt7C3sKiwt6jvALewt7CosKi3ALewt7CosKi3
AKYAywCinKIAAAAAAAAAAAo2CIFDShgASCoCAAc2CIFDShgAAzUIgQ9DShYAbUgABG5IAAR1CAEN
A2oAAAAAQ0oWAFUIAQRDShYAABEDavFjAABVCAFtSAkEc0gJBAs2CIFtSAkEc0gJBANIKgEDSCoC
FQNquGEAAEVI+v9VCAFtSAkEc0gJBBsDarGhbzsKCAFDShQAVQgBVggBbUgJBHNICQQRA2oAAAAA
VQgBbUgJBHNICQQIbUgJBHNICQQACQNqAAAAAFUIAQttSAAEbkgABHUIAQA86XcAACx4AAAteAAA
EHoAABF6AAASegAAIHoAAC56AACAegAA03sAALd8AAB6fgAAe34AAJx+AADcfgAArH8AABeAAAAZ
gAAAYoAAADWBAACBgQAA2IEAAN2BAADxgQAAD4IAAPoAAAAAAAAAAAAAAAD4AAAAAAAAAAAAAAAA
+AAAAAAAAAAAAAAAAPgAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAAAPEAAAAA
AAAAAAAAAADvAAAAAAAAAAAAAAAA7QAAAAAAAAAAAAAAAO0AAAAAAAAAAAAAAADtAAAAAAAAAAAA
AAAA7QAAAAAAAAAAAAAAAOsAAAAAAAAAAAAAAADtAAAAAAAAAAAAAAAA7QAAAAAAAAAAAAAAAO0A
AAAAAAAAAAAAAADmAAAAAAAAAAAAAAAA5gAAAAAAAAAAAAAAAO0AAAAAAAAAAAAAAADtAAAAAAAA
AAAAAAAA5AAAAAAAAAAAAAAAANsAAAAAAAAAAAAAAADbAAAAAAAAAAAAAAAA2wAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACQAAAyQBFiQBSWYBAAAAYSQBAAFeAAAEAAADJAFh
JAEAARQAAAEAAAABLwAAAS4AAy0AByQBAAEcAAABWQAFWQAKJgALRgEAABgPggAAH4IAACCCAAAv
ggAANYIAADuCAAD0AAAAAAAAAAAAAAAAcnAAAAAAAAAAAAAAAGkAAAAAAAAAAAAAAABpAAAAAAAA
AAAAAAAAaQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJAAADJAEWJAFJZgEAAABhJAEAgQAAFiQBFyQBSWYB
AAAAAFQBAAKWbAAF1hgMAQEADAEBAAwBAQAMAQEABgEBAAYBAQAI1kYAA5T/lAaDD00WAAYABwAA
AAAAAAAADAEBAAAAAAAABu8IAAAAAAAAAAAMAQEAAAAAAAAGygYAAAAAAAAAAAwBAQAAAAAACnQU
AL8AE9YwAAAAAAwBAAAAAAAADAEAAAAAAAAMAQAAAAAAAAwBAAAAAAAABgEAAAAAAAAGAQAAFPYB
AAAa1gwAAAD/AAAA/wAAAP8b1gwAAAD/AAAA/wAAAP8c1gwAAAAAAAAAAAAAAAAd1gwAAAD/AAAA
/wAAAP801gYAAQoDbABh9gMAAAsPAAUkAAYkABOkeAAWJAFJZgEAAAAABTuCAAA8ggAAVIIAAFmC
AABeggAAX4IAAGyCAABxggAAdoIAAH2MAAAAAAAAAAAAAAB0AAAAAAAAAAAAAAAAdAAAAAAAAAAA
AAAAAHQAAAAAAAAAAAAAAAB9YAAAAAAAAAAAAAAAdAAAAAAAAAAAAAAAAHQAAAAAAAAAAAAAAAB0
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJAAADJAEWJAFJ
ZgEAAABhJAEAgQAAFiQBFyQBSWYBAAAAAFQBAAKWbAAF1hgMAQEADAEBAAwBAQAMAQEABgEBAAYB
AQAI1kYAA5T/lAaDD00WAAYAB/////8AAAAAAAAAAAAAAAAABu8I/////wAAAAAAAAAAAAAAAAAG
ygb/////AAAAAAAAAAAAAAAACnQUAL8AE9YwAAAAAAwBAAAAAAAADAEAAAAAAAAMAQAAAAAAAAwB
AAAAAAAABgEAAAAAAAAGAQAAFPYBAAAa1gz///////////////8b1gwAAAD/AAAA/wAAAP8c1gwA
AAD/AAAA/wAAAP8d1gwAAAD/AAAA/wAAAP801gYAAQoDbABh9gMAAAAIdoIAAHeCAAB8ggAAgYIA
AIaCAACHggAA8YIAAD+DAABfhAAAYIQAAGeEAABohAAAcYQAAH1AAAAAAAAAAAAAAAB0AAAAAAAA
AAAAAAAAdAAAAAAAAAAAAAAAAHQAAAAAAAAAAAAAAAB9AAAAAAAAAAAAAAAAcgAAAAAAAAAAAAAA
AHIAAAAAAAAAAAAAAAByAAAAAAAAAAAAAAAAcgAAAAAAAAAAAAAAAGkAAAAAAAAAAAAAAABpAAAA
AAAAAAAAAAAAaQAAAAAAAAAAAAAAAAAACQAAAyQAFiQBSWYBAAAAYSQAAAEAAAkAAAMkARYkAUlm
AQAAAGEkAQCBAAAWJAEXJAFJZgEAAAAAVAEAApZsAAXWGAwBAQAMAQEADAEBAAwBAQAGAQEABgEB
AAjWRgADlP+UBoMPTRYABgAHAAAAAAAAAAAAAAAAAAAAAAAG7wgAAAAAAAAAAAAAAAAAAAAAAAbK
BgAAAAAAAAAAAAAAAAAAAAAKdBQAvwAT1jAAAAAADAEAAAAAAAAMAQAAAAAAAAwBAAAAAAAADAEA
AAAAAAAGAQAAAAAAAAYBAAAU9gEAABrWDAAAAP8AAAD/AAAA/xvWDAAAAP8AAAD/AAAA/xzWDAAA
AP8AAAD/AAAA/x3WDAAAAP8AAAD/AAAA/zTWBgABCgNsAGH2AwAAAAxxhAAAcoQAAH6EAAB/hAAA
soQAAIEEAQAAAAAAAAAAAAB4AAAAAAAAAAAAAAAAeAAAAAAAAAAAAAAAAHgAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJAAAD
JAAWJAFJZgEAAABhJAB+AAAWJAEXJAFJZgEAAAAClmwAAzQBBdYYBAEAAAQBAAAEAQAABAEAAAQB
AAAEAQAACNZGAAOU/xwLpBYsIgAGiAsAAAAAAAAAAAAAAAAAAAAAYAaIC/////8AAAAAAAAAAAAA
AAAABogLAAAAAAAAAAAAAAAAAAAAABPWMAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAA
AAAA/wQBAAAAAAD/BAEAABT2AQAAGtYMAAAA//////8AAAD/G9YMAAAA/wAAAP8AAAD/HNYMAAAA
/wAAAP8AAAD/HdYMAAAA/wAAAP8AAAD/NNYGAAEKA2wAYfYDAAAABLKEAACzhAAAyYQAAMqEAADe
hAAA34QAAOOEAADkhAAA6IQAAOmEAADshAAA7YQAAPCEAADxhAAAgbAAAAAAAAAAAAAAAHgAAAAA
AAAAAAAAAAB4AAAAAAAAAAAAAAAAeAAAAAAAAAAAAAAAAIEoAAAAAAAAAAAAAAB4AAAAAAAAAAAA
AAAAeAAAAAAAAAAAAAAAAHgAAAAAAAAAAAAAAACBIAAAAAAAAAAAAAAAeAAAAAAAAAAAAAAAAHgA
AAAAAAAAAAAAAAB4AAAAAAAAAAAAAAAAgUgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkAAAMk
ABYkAUlmAQAAAGEkAH4AABYkARckAUlmAQAAAAKWbAADNAEF1hgEAQAABAEAAAQBAAAEAQAABAEA
AAQBAAAI1kYAA5T/HAukFiwiAAaICwAAAAAAAAAAAAAAAAAAAAAgBogLAAAAAAAAAAAAAAAAAAAA
AAAGiAsAAAAAAAAAAAAAAAAAAAAAE9YwAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAA
AAD/BAEAAAAAAP8EAQAAFPYBAAAa1gwAAAD/AAAA/wAAAP8b1gwAAAD/AAAA/wAAAP8c1gwAAAD/
AAAA/wAAAP8d1gwAAAD/AAAA/wAAAP801gYAAQoDbABh9gMAAAAN8YQAAPKEAAABhQAAAoUAAAOF
AABOhQAAT4UAAGiFAAAEhwAAJocAAGqHAABrhwAAs4cAAOeHAAD2AAAAAAAAAAAAAAAA9gAAAAAA
AAAAAAAAAPYAAAAAAAAAAAAAAAB5AAAAAAAAAAAAAAAAdwAAAAAAAAAAAAAAAHUAAAAAAAAAAAAA
AAB1AAAAAAAAAAAAAAAAdQAAAAAAAAAAAAAAAHMAAAAAAAAAAAAAAAB1AAAAAAAAAAAAAAAAdQAA
AAAAAAAAAAAAAHEAAAAAAAAAAAAAAAB1AAAAAAAAAAAAAAAAAAABFAAAARUAAAEAAAABXgAAfAAA
FiQBFyQBSWYBAAAAApZsAAXWGAQBAAAEAQAABAEAAAQBAAAEAQAABAEAAAjWRgADlP8cC6QWLCIA
BogLAAAAAAAAAAAAAAAAAAAAAAAGiAsAAAAAAAAAAAAAAAAAAAAAAAaICwAAAAAAAAAAAAAAAAAA
AAAT1jAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAAAAD/BAEAAAAAAP8EAQAAAAAA/wQBAAAU9gEA
ABrWDAAAAP8AAAD/AAAA/xvWDAAAAP8AAAD/AAAA/xzWDAAAAP8AAAD/AAAA/x3WDAAAAP8AAAD/
AAAA/zTWBgABCgNsAGH2AwAACQAAAyQAFiQBSWYBAAAAYSQAAA0NhwAADocAABaHAAAYhwAAGYcA
ABqHAAAghwAAIYcAACOHAAAlhwAAJocAAGuHAABxhwAAsocAALOHAADnhwAAv4gAANaIAADXiAAA
2ogAANyIAADdiAAA3ogAAOaIAADniAAA64gAAOyIAADyiAAA9IgAAPeIAAD4iAAA/ogAAACJAAAD
iQAABIkAAAqJAAAMiQAAD4kAABCJAAASiQAAJokAACiJAABkiQAAZokAAGeJAABoiQAAookAAKOJ
AACmiQAAqYkAAKqJAACsiQAAsokAALOJAABbigAAXIoAAF+KAABiigAAY4oAAGWKAABrigAAbIoA
ANeLAADYiwAA2YsAAOCLAADhiwAA94sAAPiLAAD49O705/Tg9O70ANsA29kA1tDWzNbG1szWzNbM
1szWzNbM1szWzNYAxADEAMAAxADEAMQAxADEAMQAxADEALfb1rDWsAAAAAAAAAAADQNqAAAAAENK
FgBVCAERA2olagAAVQgBbUgJBHNICQQGCWoBALTwAANIKgIKCWoBALTwQ0oWAAAHQ0oWAEgqAgoJ
agEAo/BDShYAAARDShYAAAM1CIEIbUgJBHNICQQADQlqAQC08DYIgUNKGAANCWoBAD3wNgiBQ0oY
AAo2CIFDShgASCoCAAc2CIFDShgADQlqAQA+8DYIgUNKGAAAROeHAAC/iAAAEokAACOJAABgiQAA
n4kAAFiKAAATiwAAPYsAANeLAADZiwAAKIwAANGMAADejAAAVY0AAJuNAADijQAAG44AAB2OAABe
jgAAZo4AAGeOAABojgAAcY4AAHKOAABzjgAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD3AAAA
AAAAAAAAAAAA9QAAAAAAAAAAAAAAAPUAAAAAAAAAAAAAAAD1AAAAAAAAAAAAAAAA9QAAAAAAAAAA
AAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAAD9
AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAOsAAAAAAAAAAAAAAADrAAAAAAAAAAAAAAAA6wAAAAAA
AAAAAAAAAOsAAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA6QAAAAAAAAAAAAAAAOMAAAAAAAAAAAAA
AADaAAAAAAAAAAAAAAAA2gAAAAAAAAAAAAAAAOMAAAAAAAAAAAAAAADaAAAAAAAAAAAAAAAA2gAA
AAAAAAAAAAAAAAAAAAAAAAAJAAADJAIWJAFJZgEAAABhJAIGAAAWJAFJZgEAAAAAAV4ABQAACiYA
C0YSAAAEAAADJAFhJAEAASYAAAMAABSkPAAAATIAAAEAAAAZ+IsAAPmLAAD6iwAAKIwAAB2OAAAj
jgAAJI4AADmOAAA6jgAAO44AADyOAABejgAAfY4AADGPAAAzjwAAUo8AAFSPAABnjwAAaY8AAIeP
AACJjwAAyI8AAMqPAADpjwAA648AAP6PAAAAkAAAH5AAACGQAABUkAAAapAAAPiSAAD+kgAA/5IA
ABSTAAAVkwAAFpMAABeTAAAwkwAA5pMAAHOUAAB1lAAA9ZQAAPaUAAAflgAAhZcAAF6YAABtmAAA
bpgAAG+YAAB1mAAAn5gAAESZAABFmQAAWpkAAFuZAABcmQAAXZkAAIOZAACEmQAAopkAAPfw7QDt
8O3w9/Dt49rQ2tDa0NrQ2tDa0NrQ2tDa4wDt8O3w9/Dt2gDOAMoAxdrjAMW9uQC0ALSutK6rnQAA
AAAAAAAAAAAbNQiBQioBQ0oUAGgIAG1ICQRwaAAAAABzSAkEBENKGAAAC21IAARuSAAEdQgBCQNq
AAAAAFUIAQc1CIFDShQADzUIgUNKFABtSAkEc0gJBAhtSAkEc0gJBAAGCWoBALPwAANIKgETQioB
Q0oWAEgqAmgIAHBoAAAAABBCKgFDShYAaAgAcGgAAAAAABM1CIFCKgFDShYAaAgAcGgAAAAABENK
FgAADQNqAAAAAENKFgBVCAEPQ0oWAG1IAARuSAAEdQgBADxzjgAAfI4AAH2OAACGjgAAi44AAI6O
AACPjgAAkI4AAJGOAAD5AAAAAAAAAAAAAAAAU1gAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAABKAAAA
AAAAAAAAAAAA+QAAAAAAAAAAAAAAAEoAAAAAAAAAAAAAAABKAAAAAAAAAAAAAAAASgAAAAAAAAAA
AAAAAAAAAAAAAAAACQAAAyQCFiQBSWYBAAAAYSQCAKUAABYkARckAUlmAQAAAABUAQAClh4AB5TI
AAjWngAH4v/EB7cLqQ+IE44XgBtzH4AG4gcGAQAABgEAAAYBAAAGAQAAgAbzAwYBAAAGAQAABgEA
AAYBAACABvIDBgEAAAYBAAAGAQAABgEAAIAG3wMGAQAABgEAAAYBAAAGAQAAgAYGBAYBAAAGAQAA
BgEAAAYBAACABvIDBgEAAAYBAAAGAQAABgEAAIAG8wMGAQAABgEAAAYBAAAGAQAAFPYBAAAa1hwA
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA
/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAA
AP8AAAD/NNYGAAEKAx4AYfYDAAAGAAAWJAFJZgEAAAAACJGOAACSjgAAk44AAJmOAACgjgAAo44A
AKaOAACnjgAAqI4AAPYAAAAAAAAAAAAAAABQXAAAAAAAAAAAAAAASgAAAAAAAAAAAAAAAPYAAAAA
AAAAAAAAAABKAAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAA
AAAAAAAAAAAAAAAGAAAWJAFJZgEAAAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlMgACNaeAAfi
/8QHtwupD4gTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG
8gMGAQAABgEAAAYBAAAGAQAAAAbfAwYBAAAGAQAABgEAAAYBAAAABgYEBgEAAAYBAAAGAQAABgEA
AAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/
AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA
/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP80
1gYAAQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEkAgAIqI4AAKmOAACqjgAAq44AAKyOAACtjgAA
ro4AAK+OAACwjgAAsY4AAPYAAAAAAAAAAAAAAABQIAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYA
AAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAA
AAAAAAAA9gAAAAAAAAAAAAAAAAAAAAClAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeUyAAI1p4AB+L/
xAe3C6kPiBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAby
AwYBAAAGAQAABgEAAAYBAAAABt8DBgEAAAYBAAAGAQAABgEAAAAGBgQGAQAABgEAAAYBAAAGAQAA
AAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAABT2AQAAGtYcAAAA/wAAAP8A
AAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c1hwAAAD/
AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/zTW
BgABCgMeAGH2AwAACQAAAyQCFiQBSWYBAAAAYSQCAAmxjgAAso4AAMGOAADFjgAAy44AAM2OAADS
jgAA3Y4AAFm0AAAAAAAAAAAAAABTAAAAAAAAAAAAAAAASgAAAAAAAAAAAAAAAFMAAAAAAAAAAAAA
AABKAAAAAAAAAAAAAAAASgAAAAAAAAAAAAAAAEEAAAAAAAAAAAAAAAAAAAAAAAAACQAAAyQAFiQB
SWYBAAAAYSQACQAAAyQCFiQBSWYBAAAAYSQCBgAAFiQBSWYBAAAAAKUAABYkARckAUlmAQAAAABU
AQAClh4AB5TIAAjWngAH4v/EB7cLqQ+IE44XgBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYB
AAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG3wMGAQAABgEAAAYBAAAGAQAAAAYG
BAYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAA
FPYBAAAa1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAA
AP8AAAD/AAAA/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8A
AAD/AAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAAB92OAADejgAA344AAOCOAADhjgAA4o4AAOOO
AADkjgAA5Y4AAOaOAAD2AAAAAAAAAAAAAAAAUCAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAA
AAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAA
AAAAAPYAAAAAAAAAAAAAAAAAAAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlMgACNaeAAfi/8QH
twupD4gTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMG
AQAABgEAAAYBAAAGAQAAAAbfAwYBAAAGAQAABgEAAAYBAAAABgYEBgEAAAYBAAAGAQAABgEAAAAG
8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/AAAA
/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA/wAA
AP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYA
AQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEkAgAJ5o4AAOeOAAD0jgAA9Y4AAPaOAAD5jgAA+o4A
APuOAAD9jgAAWVwAAAAAAAAAAAAAAFMAAAAAAAAAAAAAAABKAAAAAAAAAAAAAAAASgAAAAAAAAAA
AAAAAEoAAAAAAAAAAAAAAABKAAAAAAAAAAAAAAAASgAAAAAAAAAAAAAAAEoAAAAAAAAAAAAAAAAA
AAAAAAAAAAkAAAMkAhYkAUlmAQAAAGEkAgYAABYkAUlmAQAAAAClAAAWJAEXJAFJZgEAAAAAVAEA
ApYeAAeUyAAI1p4AB+L/xAe3C6kPiBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAA
BgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABt8DBgEAAAYBAAAGAQAABgEAAAAGBgQG
AQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAABT2
AQAAGtYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/
AAAA/wAAAP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA
/wAAAP8AAAD/AAAA/zTWBgABCgMeAGH2AwAAAAj9jgAA/o4AAP+OAAAAjwAAAY8AAAKPAAADjwAA
BI8AAAWPAAAGjwAAWSAAAAAAAAAAAAAAAFAAAAAAAAAAAAAAAABQAAAAAAAAAAAAAAAAUAAAAAAA
AAAAAAAAAFAAAAAAAAAAAAAAAABQAAAAAAAAAAAAAAAAUAAAAAAAAAAAAAAAAFAAAAAAAAAAAAAA
AABZiAAAAAAAAAAAAAAAAAAACQAAAyQCFiQBSWYBAAAAYSQCAKUAABYkARckAUlmAQAAAABUAQAC
lh4AB5TIAAjWngAH4v/EB7cLqQ+IE44XgBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAG
AQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG3wMGAQAABgEAAAYBAAAGAQAAAAYGBAYB
AAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYB
AAAa1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/AAAA/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/
AAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAACQaPAAAPjwAAEY8AABuPAAAcjwAAHY8AACaPAAAn
jwAAKI8AAPkAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAA
AADwAAAAAAAAAAAAAAAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAABKbAAAAAAAAAAAAAAAAAAA
AAAAAAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlMgACNaeAAfi/8QHtwupD4gTjheAG3MfAAbi
BwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAA
AAbfAwYBAAAGAQAABgEAAAYBAAAABgYEBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAG
AQAAAAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAA
AP8b1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQoDHgBh9gMAAAkAAAMk
AhYkAUlmAQAAAGEkAgYAABYkAUlmAQAAAAAIKI8AADOPAAA1jwAAOI8AADuPAAA8jwAAP48AAEKP
AABDjwAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAA
APAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAEp0AAAAAAAAAAAAAAAAAAAA
AAAAAAClAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeUyAAI1p4AB+L/xAe3C6kPiBOOF4Abcx8ABuIH
BgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAA
Bt8DBgEAAAYBAAAGAQAABgEAAAAGBgQGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYB
AAAABvMDBgEAAAYBAAAGAQAABgEAABT2AQAAGtYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA
/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAA
AP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABCgMeAGH2AwAACQAAAyQC
FiQBSWYBAAAAYSQCBgAAFiQBSWYBAAAAAAhDjwAAVI8AAFaPAABYjwAAWo8AAFuPAABdjwAAX48A
AGCPAAD5AAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA
8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAASlQAAAAAAAAAAAAAAAAAAAAA
AAAAAKUAABYkARckAUlmAQAAAABUAQAClh4AB5TIAAjWngAH4v/EB7cLqQ+IE44XgBtzHwAG4gcG
AQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG
3wMGAQAABgEAAAYBAAAGAQAAAAYGBAYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEA
AAAG8wMGAQAABgEAAAYBAAAGAQAAFPYBAAAa1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/
G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA
/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAJAAADJAIW
JAFJZgEAAABhJAIGAAAWJAFJZgEAAAAACGCPAABpjwAAa48AAG2PAABvjwAAcI8AAHKPAAB0jwAA
dY8AAPkAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADw
AAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAABKgAAAAAAAAAAAAAAAAAAAAAAA
AAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlMgACNaeAAfi/8QHtwupD4gTjheAG3MfAAbiBwYB
AAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbf
AwYBAAAGAQAABgEAAAYBAAAABgYEBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAA
AAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b
1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/
AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQoDHgBh9gMAAAkAAAMkAhYk
AUlmAQAAAGEkAgYAABYkAUlmAQAAAAAIdY8AAImPAACLjwAAjY8AAI+PAACQjwAAko8AAJSPAACV
jwAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAA
AAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAEogAAAAAAAAAAAAAAAAAAAAAAAA
AAClAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeUyAAI1p4AB+L/xAe3C6kPiBOOF4Abcx8ABuIHBgEA
AAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABt8D
BgEAAAYBAAAGAQAABgEAAAAGBgQGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAA
BvMDBgEAAAYBAAAGAQAABgEAABT2AQAAGtYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvW
HAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABCgMeAGH2AwAACQAAAyQCFiQB
SWYBAAAAYSQCBgAAFiQBSWYBAAAAAAiVjwAAlo8AAJePAACYjwAAmY8AAJqPAACbjwAAnI8AAJ2P
AAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAA
AAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAAUIgAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAKUAABYkARckAUlmAQAAAABUAQAClh4AB5TIAAjWngAH4v/EB7cLqQ+IE44X
gBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAG
AQAABgEAAAAG3wMGAQAABgEAAAYBAAAGAQAAAAYGBAYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYB
AAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYBAAAa1hwAAAD/AAAA/wAAAP8AAAD/AAAA
/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xzWHAAAAP8AAAD/AAAA/wAA
AP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYD
AAAJAAADJAIWJAFJZgEAAABhJAIACJ2PAACmjwAAqI8AALKPAACzjwAAtI8AAL2PAAC+jwAAv48A
APkAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAA
AAAAAAAAAAAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAABKbAAAAAAAAAAAAAAAAAAAAAAAAAAA
pQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlMgACNaeAAfi/8QHtwupD4gTjheAG3MfAAbiBwYBAAAG
AQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbfAwYB
AAAGAQAABgEAAAYBAAAABgYEBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbz
AwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwA
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA
/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQoDHgBh9gMAAAkAAAMkAhYkAUlm
AQAAAGEkAgYAABYkAUlmAQAAAAAIv48AAMqPAADMjwAAz48AANKPAADTjwAA1o8AANmPAADajwAA
+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAA
AAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAEp0AAAAAAAAAAAAAAAAAAAAAAAAAACl
AAAWJAEXJAFJZgEAAAAAVAEAApYeAAeUyAAI1p4AB+L/xAe3C6kPiBOOF4Abcx8ABuIHBgEAAAYB
AAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABt8DBgEA
AAYBAAAGAQAABgEAAAAGBgQGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMD
BgEAAAYBAAAGAQAABgEAABT2AQAAGtYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAA
AP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/
HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABCgMeAGH2AwAACQAAAyQCFiQBSWYB
AAAAYSQCBgAAFiQBSWYBAAAAAAjajwAA648AAO2PAADvjwAA8Y8AAPKPAAD0jwAA9o8AAPePAAD5
AAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAA
AAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAASlgAAAAAAAAAAAAAAAAAAAAAAAAAAKUA
ABYkARckAUlmAQAAAABUAQAClh4AB5TIAAjWngAH4v/EB7cLqQ+IE44XgBtzHwAG4gcGAQAABgEA
AAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG3wMGAQAA
BgEAAAYBAAAGAQAAAAYGBAYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMG
AQAABgEAAAYBAAAGAQAAFPYBAAAa1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA
/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d
1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAJAAADJAIWJAFJZgEA
AABhJAIGAAAWJAFJZgEAAAAACPePAAAAkAAAApAAAASQAAAGkAAAB5AAAAmQAAAMkAAADZAAAPkA
AAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAA
AAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAABKgAAAAAAAAAAAAAAAAAAAAAAAAAAApQAA
FiQBFyQBSWYBAAAAAFQBAAKWHgAHlMgACNaeAAfi/8QHtwupD4gTjheAG3MfAAbiBwYBAAAGAQAA
BgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbfAwYBAAAG
AQAABgEAAAYBAAAABgYEBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYB
AAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/
AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3W
HAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAA
AGEkAgYAABYkAUlmAQAAAAAIDZAAACGQAAAjkAAAJZAAACeQAAAokAAAKpAAACyQAAAtkAAA+QAA
AAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAA
AAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAEogAAAAAAAAAAAAAAAAAAAAAAAAAAClAAAW
JAEXJAFJZgEAAAAAVAEAApYeAAeUyAAI1p4AB+L/xAe3C6kPiBOOF4Abcx8ABuIHBgEAAAYBAAAG
AQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABt8DBgEAAAYB
AAAGAQAABgEAAAAGBgQGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEA
AAYBAAAGAQAABgEAABT2AQAAGtYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8A
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYc
AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABCgMeAGH2AwAACQAAAyQCFiQBSWYBAAAA
YSQCBgAAFiQBSWYBAAAAAAgtkAAALpAAAC+QAAAwkAAAMZAAADKQAAAzkAAANJAAADWQAAD2AAAA
AAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAA
AAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAAUFwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAKUAABYkARckAUlmAQAAAABUAQAClh4AB5TIAAjWngAH4v/EB7cLqQ+IE44XgBtzHwAG
4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEA
AAAG3wMGAQAABgEAAAYBAAAGAQAAAAYGBAYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAA
BgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYBAAAa1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/
AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAJAAAD
JAIWJAFJZgEAAABhJAIACDWQAABCkAAAQ5AAAESQAABHkAAASJAAAEmQAABLkAAATJAAAPkAAAAA
AAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAA
AAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAABKIAAAAAAAAAAAAAAAAAAAAAAAAAAApQAAFiQB
FyQBSWYBAAAAAFQBAAKWHgAHlMgACNaeAAfi/8QHtwupD4gTjheAG3MfAAbiBwYBAAAGAQAABgEA
AAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbfAwYBAAAGAQAA
BgEAAAYBAAAABgYEBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAG
AQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA
/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAA
AP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEk
AgYAABYkAUlmAQAAAAAITJAAAE2QAABOkAAAT5AAAFCQAABRkAAAUpAAAFOQAABUkAAA9gAAAAAA
AAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAA
AAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAFBYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAClAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeUyAAI1p4AB+L/xAe3C6kPiBOOF4Abcx8ABuIH
BgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAA
Bt8DBgEAAAYBAAAGAQAABgEAAAAGBgQGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYB
AAAABvMDBgEAAAYBAAAGAQAABgEAABT2AQAAGtYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA
/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAA
AP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABCgMeAGH2AwAACQAAAyQC
FiQBSWYBAAAAYSQCAAhUkAAAXpAAAF+QAABgkAAAZJAAAGWQAABmkAAAaZAAAGqQAAD5AAAAAAAA
AAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAA
APAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAASgAAAAAAAAAAAAAAAAAAAAAAAAAAAKUAABYkARck
AUlmAQAAAABUAQAClh4AB5TIAAjWngAH4v/EB7cLqQ+IE44XgBtzHwAG4gcGAQAABgEAAAYBAAAG
AQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG3wMGAQAABgEAAAYB
AAAGAQAAAAYGBAYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEA
AAYBAAAGAQAAFPYBAAAa1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8A
AAD/AAAA/wAAAP8AAAD/AAAA/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/
AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAJAAADJAIWJAFJZgEAAABhJAIG
AAAWJAFJZgEAAAAACGqQAABrkAAA4JEAAKSSAAD3kgAA+JIAADCTAAAxkwAAO5MAAEGTAABCkwAA
U5MAAFaTAAB7kwAAfJMAAJCTAACTkwAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAA
AAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA8gAAAAAAAAAAAAAA
AOwAAAAAAAAAAAAAAADsAAAAAAAAAAAAAAAAkugAAAAAAAAAAAAAAOwAAAAAAAAAAAAAAADyAAAA
AAAAAAAAAAAA7AAAAAAAAAAAAAAAAJK4AAAAAAAAAAAAAADsAAAAAAAAAAAAAAAA8gAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAWQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlPcACNZGAAPi/8QH
twvJGAAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABhINBgEAAAYBAAAG
AQAABgEAABT2AQAAGtYMAAAA/wAAAP8AAAD/G9YMAAAA/wAAAP8AAAD/HNYMAAAA/wAAAP8AAAD/
HdYMAAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAGAAAWJAFJZgEAAAAJAAADJAIWJAFJZgEAAABh
JAIAAV4AAAEAAAAQk5MAAKmTAACqkwAAv5MAAMKTAADSkwAA05MAANSTAADVkwAA1pMAANeTAADh
kwAA5JMAAOWTAADmkwAA55MAAB+WAACElwAA+QAAAAAAAAAAAAAAAJ+kAAAAAAAAAAAAAAD5AAAA
AAAAAAAAAAAAlgAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAACfEAAAAAAAAAAAAAAAlgAAAAAAAAAA
AAAAAJYAAAAAAAAAAAAAAACWAAAAAAAAAAAAAAAAnzwAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAACW
AAAAAAAAAAAAAAAAlgAAAAAAAAAAAAAAAJ8AAAAAAAAAAAAAAACUAAAAAAAAAAAAAAAAlAAAAAAA
AAAAAAAAAJQAAAAAAAAAAAAAAAAAAAAAAQAACQAAAyQCFiQBSWYBAAAAYSQCAFkAABYkARckAUlm
AQAAAABUAQAClh4AB5T3AAjWRgAD4v/EB7cLyRgABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAA
BgEAAAYBAAAGAQAAAAYSDQYBAAAGAQAABgEAAAYBAAAU9gEAABrWDAAAAP8AAAD/AAAA/xvWDAAA
AP8AAAD/AAAA/xzWDAAAAP8AAAD/AAAA/x3WDAAAAP8AAAD/AAAA/zTWBgABCgMeAGH2AwAABgAA
FiQBSWYBAAAAABGElwAAhZcAAIaXAACQlwAAlpcAAJeXAAColwAAq5cAANCXAADRlwAA6JcAAOuX
AAABmAAAApgAABeYAAAZmAAASZgAAP0AAAAAAAAAAAAAAAD0AAAAAAAAAAAAAAAA7gAAAAAAAAAA
AAAAAOUAAAAAAAAAAAAAAACL6AAAAAAAAAAAAAAA7gAAAAAAAAAAAAAAAPQAAAAAAAAAAAAAAADl
AAAAAAAAAAAAAAAAi8QAAAAAAAAAAAAAAO4AAAAAAAAAAAAAAAD0AAAAAAAAAAAAAAAA5QAAAAAA
AAAAAAAAAIsgAQAAAAAAAAAAAADuAAAAAAAAAAAAAAAA9AAAAAAAAAAAAAAAAOUAAAAAAAAAAAAA
AAAAAABZAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeU9wAI1kYAA+L/xAe3C8kYAAbiBwYBAAAGAQAA
BgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAGEg0GAQAABgEAAAYBAAAGAQAAFPYBAAAa1gwA
AAD/AAAA/wAAAP8b1gwAAAD/AAAA/wAAAP8c1gwAAAD/AAAA/wAAAP8d1gwAAAD/AAAA/wAAAP80
1gYAAQoDHgBh9gMAAAkAAAMkABYkAUlmAQAAAGEkAAYAABYkAUlmAQAAAAkAAAMkAhYkAUlmAQAA
AGEkAgABAAAAEEmYAABKmAAAWpgAAFyYAABdmAAAXpgAAGiYAABrmAAAbJgAAG2YAABumAAAb5gA
AJ+YAAA+mQAAhJkAAIyZAAClUAAAAAAAAAAAAAAAnwAAAAAAAAAAAAAAAJYAAAAAAAAAAAAAAACN
AAAAAAAAAAAAAAAApTwAAAAAAAAAAAAAAJ8AAAAAAAAAAAAAAACWAAAAAAAAAAAAAAAAlgAAAAAA
AAAAAAAAAKUAAAAAAAAAAAAAAACLAAAAAAAAAAAAAAAAiwAAAAAAAAAAAAAAAIsAAAAAAAAAAAAA
AACLAAAAAAAAAAAAAAAAiQAAAAAAAAAAAAAAAJ8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AV4AAAEAAAkAAAMkABYkAUlmAQAAAGEkAAkAAAMkAhYkAUlmAQAAAGEkAgYAABYkAUlmAQAAAABZ
AAAWJAEXJAFJZgEAAAAAVAEAApYeAAeU9wAI1kYAA+L/xAe3C8kYAAbiBwYBAAAGAQAABgEAAAYB
AAAABvMDBgEAAAYBAAAGAQAABgEAAAAGEg0GAQAABgEAAAYBAAAGAQAAFPYBAAAa1gwAAAD/AAAA
/wAAAP8b1gwAAAD/AAAA/wAAAP8c1gwAAAD/AAAA/wAAAP8d1gwAAAD/AAAA/wAAAP801gYAAQoD
HgBh9gMAAAAPjJkAAI2ZAACOmQAAl5kAAJiZAACZmQAAopkAAKOZAACsmQAA9gAAAAAAAAAAAAAA
APYAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAADwAAAA
AAAAAAAAAAAASkgAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAAAAAAAAAAAAAAClAAAWJAEXJAFJZgEA
AAAAVAEAApYeAAeU9wAI1p4AB+L/xAe3C6kPnBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG
8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEA
AAAG8gMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAA
BgEAABT2AQAAGtYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAA
AP8AAAD/AAAA/wAAAP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8A
AAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABCgMeAGH2AwAABgAAFiQBSWYBAAAACQAAAyQCFiQBSWYB
AAAAYSQCAAiimQAAo5kAALSZAAC1mQAAy5kAAMyZAADTmQAA1JkAAAGaAAACmgAACZoAAAqaAAAg
mgAAIZoAACiaAAApmgAASpoAAEuaAABUmgAAVZoAAGWaAABmmgAAdZoAAHaaAACCmgAAg5oAAIqa
AACLmgAAl5oAAJiaAACqmgAAq5oAALeaAAC4mgAAv5oAAMCaAADhmgAA4poAAPGaAADymgAA/poA
AP+aAAAGmwAAB5sAABSbAAAVmwAAJ5sAACibAAA0mwAANZsAADybAAA9mwAAXpsAAF+bAABomwAA
aZsAAHmbAAB6mwAAiZsAAIqbAACWmwAAl5sAAJ6bAACfmwAArJsAAK2bAAC/mwAAwJsAAMybAADN
mwAA1JsAANWbAADrmwAA7JsAAPObAAD0mwAA+5sAAPybAADz5tvm2+bb5tvm2+bb5tvm29LI5tvS
yObb0sjm29LI5tvm2+bb0sjm29LI5tvSyObb5tvm29LI5tvSyObb0sjm29LI5tvm2+bb5tvm2wAA
AAAAAAAAAAAAE0IqAUNKFABIKgJoCABwaAAAAAAQQioBQ0oUAGgIAHBoAAAAAAAUQioBaAgAbUgJ
BHBoAAAAAHNICQQAGEIqAUNKFABoCABtSAkEcGgAAAAAc0gJBAAXNQiBQioBaAgAbUgJBHBoAAAA
AHNICQQATayZAACtmQAAsJkAALGZAACymQAAs5kAALSZAAC1mQAAu5kAAPYAAAAAAAAAAAAAAADw
AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAA
AAAAAAAAAEpcAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAAAAAAAAAAAAAApQAAFiQBFyQBSWYBAAAA
AFQBAAKWHgAHlPcACNaeAAfi/8QHtwupD5wTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMD
BgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAA
BvIDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYB
AAAU9gEAABrWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/
AAAA/wAAAP8AAAD/HNYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA
/wAAAP8AAAD/AAAA/wAAAP801gYAAQoDHgBh9gMAAAYAABYkAUlmAQAAAAkAAAMkAhYkAUlmAQAA
AGEkAgAIu5kAAMGZAADEmQAAyJkAAMmZAADKmQAAy5kAAMyZAADNmQAA9gAAAAAAAAAAAAAAAPAA
AAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAA
AAAAAAAASiAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAAAAAAAAAAAAAClAAAWJAEXJAFJZgEAAAAA
VAEAApYeAAeU9wAI1p4AB+L/xAe3C6kPnBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMG
AQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG
8gMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEA
ABT2AQAAGtYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAAAP8A
AAD/AAAA/wAAAP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8AAAD/
AAAA/wAAAP8AAAD/AAAA/zTWBgABCgMeAGH2AwAABgAAFiQBSWYBAAAACQAAAyQCFiQBSWYBAAAA
YSQCAAjNmQAAzpkAAM+ZAADQmQAA0ZkAANKZAADTmQAA1JkAAOOZAAD2AAAAAAAAAAAAAAAA9gAA
AAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAA
AAAAAABQuAAAAAAAAAAAAAAASgAAAAAAAAAAAAAAAAAAAAAAAAAABgAAFiQBSWYBAAAAAKUAABYk
ARckAUlmAQAAAABUAQAClh4AB5T3AAjWngAH4v/EB7cLqQ+cE44XgBtzHwAG4gcGAQAABgEAAAYB
AAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEA
AAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAA
BgEAAAYBAAAGAQAAFPYBAAAa1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAA
AP8AAAD/AAAA/wAAAP8AAAD/AAAA/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwA
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAJAAADJAIWJAFJZgEAAABh
JAIACOOZAADnmQAA7ZkAAO+ZAAD0mQAAAJoAAAGaAAACmgAA9gAAAAAAAAAAAAAAAPAAAAAAAAAA
AAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAOcAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA
QSAAAAAAAAAAAAAAAAAAAAAAAAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlPcACNaeAAfi/8QH
twupD5wTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMG
AQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG
8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/AAAA
/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA/wAA
AP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYA
AQoDHgBh9gMAAAkAAAMkABYkAUlmAQAAAGEkAAYAABYkAUlmAQAAAAkAAAMkAhYkAUlmAQAAAGEk
AgAHApoAAAOaAAAEmgAABZoAAAaaAAAHmgAACJoAAAmaAAAKmgAA9gAAAAAAAAAAAAAAAPYAAAAA
AAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAA
AAAA9gAAAAAAAAAAAAAAAFBcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAClAAAWJAEX
JAFJZgEAAAAAVAEAApYeAAeU9wAI1p4AB+L/xAe3C6kPnBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAA
BgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAG
AQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYB
AAAGAQAABgEAABT2AQAAGtYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/
AAAA/wAAAP8AAAD/AAAA/wAAAP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA
/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgABCgMeAGH2AwAACQAAAyQCFiQBSWYBAAAAYSQC
AAgKmgAAF5oAABiaAAAZmgAAHJoAAB2aAAAemgAAIJoAACGaAAD5AAAAAAAAAAAAAAAA8AAAAAAA
AAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAA
AADwAAAAAAAAAAAAAAAASiAAAAAAAAAAAAAAAAAAAAAAAAAAAKUAABYkARckAUlmAQAAAABUAQAC
lh4AB5T3AAjWngAH4v/EB7cLqQ+cE44XgBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAG
AQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYB
AAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYB
AAAa1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/AAAA/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/
AAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAJAAADJAIWJAFJZgEAAABhJAIGAAAWJAFJZgEAAAAA
CCGaAAAimgAAI5oAACSaAAAlmgAAJpoAACeaAAAomgAAKZoAAPYAAAAAAAAAAAAAAAD2AAAAAAAA
AAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAA
APYAAAAAAAAAAAAAAABQiAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAApQAAFiQBFyQB
SWYBAAAAAFQBAAKWHgAHlPcACNaeAAfi/8QHtwupD5wTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYB
AAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEA
AAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAA
BgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAA
AP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8A
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEkAgAI
KZoAADKaAAA0mgAAPpoAAD+aAABAmgAASZoAAEqaAABLmgAA+QAAAAAAAAAAAAAAAPkAAAAAAAAA
AAAAAAD5AAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA
8AAAAAAAAAAAAAAAAEpsAAAAAAAAAAAAAAAAAAAAAAAAAAClAAAWJAEXJAFJZgEAAAAAVAEAApYe
AAeU9wAI1p4AB+L/xAe3C6kPnBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEA
AAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAA
BgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAABT2AQAA
GtYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA
/wAAAP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAA
AP8AAAD/AAAA/zTWBgABCgMeAGH2AwAACQAAAyQCFiQBSWYBAAAAYSQCBgAAFiQBSWYBAAAAAAhL
mgAAVpoAAFiaAABbmgAAXpoAAF+aAABimgAAZZoAAGaaAAD5AAAAAAAAAAAAAAAA8AAAAAAAAAAA
AAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADw
AAAAAAAAAAAAAAAASnQAAAAAAAAAAAAAAAAAAAAAAAAAAKUAABYkARckAUlmAQAAAABUAQAClh4A
B5T3AAjWngAH4v/EB7cLqQ+cE44XgBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAA
BgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAG
AQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYBAAAa
1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/
AAAA/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/AAAA
/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAJAAADJAIWJAFJZgEAAABhJAIGAAAWJAFJZgEAAAAACGaa
AAB3mgAAeZoAAHuaAAB9mgAAfpoAAICaAACCmgAAg5oAAPkAAAAAAAAAAAAAAADwAAAAAAAAAAAA
AAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAA
AAAAAAAAAAAAAABKVAAAAAAAAAAAAAAAAAAAAAAAAAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAH
lPcACNaeAAfi/8QHtwupD5wTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAG
AQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYB
AAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrW
HAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/HNYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/
AAAA/wAAAP801gYAAQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEkAgYAABYkAUlmAQAAAAAIg5oA
AIyaAACOmgAAkJoAAJKaAACTmgAAlZoAAJeaAACYmgAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAA
AADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAA
AAAAAAAAAAAAAEqAAAAAAAAAAAAAAAAAAAAAAAAAAAClAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeU
9wAI1p4AB+L/xAe3C6kPnBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYB
AAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEA
AAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAABT2AQAAGtYc
AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAA
AP8c1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/AAAA/zTWBgABCgMeAGH2AwAACQAAAyQCFiQBSWYBAAAAYSQCBgAAFiQBSWYBAAAAAAiYmgAA
rJoAAK6aAACwmgAAspoAALOaAAC1mgAAt5oAALiaAAD5AAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAA
APAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAA
AAAAAAAAAAAASiAAAAAAAAAAAAAAAAAAAAAAAAAAAKUAABYkARckAUlmAQAAAABUAQAClh4AB5T3
AAjWngAH4v/EB7cLqQ+cE44XgBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEA
AAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAA
BgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYBAAAa1hwA
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA
/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAA
AP8AAAD/NNYGAAEKAx4AYfYDAAAJAAADJAIWJAFJZgEAAABhJAIGAAAWJAFJZgEAAAAACLiaAAC5
mgAAupoAALuaAAC8mgAAvZoAAL6aAAC/mgAAwJoAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA
9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAA
AAAAAAAAAABQiAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAApQAAFiQBFyQBSWYBAAAA
AFQBAAKWHgAHlPcACNaeAAfi/8QHtwupD5wTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMD
BgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAA
BvIDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYB
AAAU9gEAABrWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/
AAAA/wAAAP8AAAD/HNYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA
/wAAAP8AAAD/AAAA/wAAAP801gYAAQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEkAgAIwJoAAMma
AADLmgAA1ZoAANaaAADXmgAA4JoAAOGaAADimgAA+QAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAAD5
AAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA8AAAAAAA
AAAAAAAAAEp0AAAAAAAAAAAAAAAAAAAAAAAAAAClAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeU9wAI
1p4AB+L/xAe3C6kPnBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAG
AQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYB
AAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAABT2AQAAGtYcAAAA
/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c
1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/
AAAA/zTWBgABCgMeAGH2AwAACQAAAyQCFiQBSWYBAAAAYSQCBgAAFiQBSWYBAAAAAAjimgAA85oA
APWaAAD3mgAA+ZoAAPqaAAD8mgAA/poAAP+aAAD5AAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAA
AAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAA
AAAAAAAASlgAAAAAAAAAAAAAAAAAAAAAAAAAAKUAABYkARckAUlmAQAAAABUAQAClh4AB5T3AAjW
ngAH4v/EB7cLqQ+cE44XgBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYB
AAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEA
AAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYBAAAa1hwAAAD/
AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xzW
HAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/NNYGAAEKAx4AYfYDAAAJAAADJAIWJAFJZgEAAABhJAIGAAAWJAFJZgEAAAAACP+aAAAImwAA
CpsAAAybAAAOmwAAD5sAABGbAAAUmwAAFZsAAPkAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAA
AAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAA
AAAAAABKgAAAAAAAAAAAAAAAAAAAAAAAAAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlPcACNae
AAfi/8QHtwupD5wTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEA
AAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAA
BgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8A
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYc
AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAA
AP801gYAAQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEkAgYAABYkAUlmAQAAAAAIFZsAACmbAAAr
mwAALZsAAC+bAAAwmwAAMpsAADSbAAA1mwAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAA
AAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAA
AAAAAEogAAAAAAAAAAAAAAAAAAAAAAAAAAClAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeU9wAI1p4A
B+L/xAe3C6kPnBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAA
AAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAG
AQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAABT2AQAAGtYcAAAA/wAA
AP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c1hwA
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA
/zTWBgABCgMeAGH2AwAACQAAAyQCFiQBSWYBAAAAYSQCBgAAFiQBSWYBAAAAAAg1mwAANpsAADeb
AAA4mwAAOZsAADqbAAA7mwAAPJsAAD2bAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAA
AAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAA
AAAAUIgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKUAABYkARckAUlmAQAAAABUAQAC
lh4AB5T3AAjWngAH4v/EB7cLqQ+cE44XgBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAG
AQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYB
AAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYB
AAAa1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/AAAA/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/
AAAA/wAAAP8AAAD/NNYGAAEKAx4AYfYDAAAJAAADJAIWJAFJZgEAAABhJAIACD2bAABGmwAASJsA
AFKbAABTmwAAVJsAAF2bAABemwAAX5sAAPkAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA+QAAAAAA
AAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAA
AABKbAAAAAAAAAAAAAAAAAAAAAAAAAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlPcACNaeAAfi
/8QHtwupD5wTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG
8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEA
AAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/
AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA
/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP80
1gYAAQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEkAgYAABYkAUlmAQAAAAAIX5sAAGqbAABsmwAA
b5sAAHKbAABzmwAAdpsAAHmbAAB6mwAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAA
AAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAA
AEp0AAAAAAAAAAAAAAAAAAAAAAAAAAClAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeU9wAI1p4AB+L/
xAe3C6kPnBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAby
AwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAA
AAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAABT2AQAAGtYcAAAA/wAAAP8A
AAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c1hwAAAD/
AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/zTW
BgABCgMeAGH2AwAACQAAAyQCFiQBSWYBAAAAYSQCBgAAFiQBSWYBAAAAAAh6mwAAi5sAAI2bAACP
mwAAkZsAAJKbAACUmwAAlpsAAJebAAD5AAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAA
AAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA
SlgAAAAAAAAAAAAAAAAAAAAAAAAAAKUAABYkARckAUlmAQAAAABUAQAClh4AB5T3AAjWngAH4v/E
B7cLqQ+cE44XgBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvID
BgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAA
BvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYBAAAa1hwAAAD/AAAA/wAA
AP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xzWHAAAAP8A
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/NNYG
AAEKAx4AYfYDAAAJAAADJAIWJAFJZgEAAABhJAIGAAAWJAFJZgEAAAAACJebAACgmwAAopsAAKSb
AACmmwAAp5sAAKmbAACsmwAArZsAAPkAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAA
AAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAABK
gAAAAAAAAAAAAAAAAAAAAAAAAAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlPcACNaeAAfi/8QH
twupD5wTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMG
AQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG
8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/AAAA
/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA/wAA
AP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYA
AQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEkAgYAABYkAUlmAQAAAAAIrZsAAMGbAADDmwAAxZsA
AMebAADImwAAypsAAMybAADNmwAA+QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAA
AAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAEog
AAAAAAAAAAAAAAAAAAAAAAAAAAClAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeU9wAI1p4AB+L/xAe3
C6kPnBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYB
AAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAby
AwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAABT2AQAAGtYcAAAA/wAAAP8AAAD/
AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c1hwAAAD/AAAA
/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/zTWBgAB
CgMeAGH2AwAACQAAAyQCFiQBSWYBAAAAYSQCBgAAFiQBSWYBAAAAAAjNmwAAzpsAAM+bAADQmwAA
0ZsAANKbAADTmwAA1JsAANWbAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAA
AAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAAUFwA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKUAABYkARckAUlmAQAAAABUAQAClh4AB5T3
AAjWngAH4v/EB7cLqQ+cE44XgBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEA
AAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAA
BgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYBAAAa1hwA
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA
/xzWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAA
AP8AAAD/NNYGAAEKAx4AYfYDAAAJAAADJAIWJAFJZgEAAABhJAIACNWbAADimwAA45sAAOSbAADn
mwAA6JsAAOmbAADrmwAA7JsAAPkAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAA
APAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAABKIAAA
AAAAAAAAAAAAAAAAAAAAAAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlPcACNaeAAfi/8QHtwup
D5wTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAA
BgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8gMG
AQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8AAAD/AAAA/wAA
AP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYcAAAA/wAAAP8A
AAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP801gYAAQoD
HgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEkAgYAABYkAUlmAQAAAAAI7JsAAO2bAADumwAA75sAAPCb
AADxmwAA8psAAPObAAD0mwAA9ZsAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAA
AAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAABQ
IAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAAAAAAClAAAWJAEXJAFJZgEAAAAAVAEAApYeAAeU9wAI
1p4AB+L/xAe3C6kPnBOOF4Abcx8ABuIHBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAG
AQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAAAAG8gMGAQAABgEAAAYB
AAAGAQAAAAbyAwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEAABT2AQAAGtYcAAAA
/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xvWHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8c
1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HdYcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/
AAAA/zTWBgABCgMeAGH2AwAACQAAAyQCFiQBSWYBAAAAYSQCAAn1mwAA9psAAPebAAD4mwAA+ZsA
APqbAAD7mwAA/JsAAAacAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2
AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAABQWAAAAAAAAAAAAAAASgAAAAAA
AAAAAAAAAAAAAAAAAAAABgAAFiQBSWYBAAAAAKUAABYkARckAUlmAQAAAABUAQAClh4AB5T3AAjW
ngAH4v/EB7cLqQ+cE44XgBtzHwAG4gcGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYB
AAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAAAbyAwYBAAAGAQAABgEA
AAYBAAAABvIDBgEAAAYBAAAGAQAABgEAAAAG8wMGAQAABgEAAAYBAAAGAQAAFPYBAAAa1hwAAAD/
AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/G9YcAAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/xzW
HAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8d1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8A
AAD/NNYGAAEKAx4AYfYDAAAJAAADJAIWJAFJZgEAAABhJAIACAacAAAHnAAACJwAAAycAAANnAAA
DpwAABGcAAASnAAAu5wAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYA
AAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAFAAAAAAAAAAAAAAAABOAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAApQAAFiQBFyQBSWYBAAAAAFQBAAKWHgAHlPcACNae
AAfi/8QHtwupD5wTjheAG3MfAAbiBwYBAAAGAQAABgEAAAYBAAAABvMDBgEAAAYBAAAGAQAABgEA
AAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAABvIDBgEAAAYBAAAGAQAA
BgEAAAAG8gMGAQAABgEAAAYBAAAGAQAAAAbzAwYBAAAGAQAABgEAAAYBAAAU9gEAABrWHAAAAP8A
AAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8b1hwAAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/HNYc
AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/x3WHAAAAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAA
AP801gYAAQoDHgBh9gMAAAkAAAMkAhYkAUlmAQAAAGEkAgAI/JsAABGcAAASnAAAu5wAAMKcAAD3
nAAApZ0AAKudAACsnQAAwZ0AAMKdAADDnQAAxJ0AAO+dAADwnQAAfZ4AACegAABKpAAAS6QAAEyk
AABNpAAAWqQAAGikAACbpAAAHLEAAB2xAACAtQAAgbUAAKC2AACitgAAd7cAAHm3AABbuAAAXLgA
AF24AABkuAAAZrgAAHK4AAB7uAAAfbgAAJS/AACVvwAAr8AAALHAAACFwQAAh8EAAKDBAAChwQAA
qMEAAKnBAACqwQAA/cIAAKzGAAA3xwAAXsgAAH/JAACvyQAAsMkAALTJAAC1yQAAL8oAAPHlAOAA
4N3W3dbO1s7dAOAAzOAA4Mjg3cLdwt2+3b7dud2y3bLdvt3C3b7dvt3C3aym3QDdAN0AogCeAAAA
AAAAAAAAAAAAAAYJagEAbfAABglqAQC08AAKCWoBAHPwQ0oWAAAKCWoBANfwQ0oWAAAMQ0oWAG1I
DBBzSAwQAAkDaoB4AABVCAEHQ0oWAEgqAQoJagEAbfBDShYAAAY1CIE2CIEAAzUIgQ9DShYAbUgA
BG5IAAR1CAENA2oAAAAAQ0oWAFUIAQRDShYAAAhtSAkEc0gJBAAXNQiBQioBaAgAbUgJBHBoAAAA
AHNICQQbNQiBQioBQ0oUAGgIAG1ICQRwaAAAAABzSAkEADy7nAAAvJwAAPmcAAClnQAA8J0AAPWd
AAAJngAAJ54AACieAAA3ngAAPp4AAP0AAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA7AAAAAAAAAAA
AAAAAOoAAAAAAAAAAAAAAADhAAAAAAAAAAAAAAAA4QAAAAAAAAAAAAAAAOEAAAAAAAAAAAAAAABy
XAAAAAAAAAAAAAAA4QAAAAAAAAAAAAAAAOEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAbgAAFiQBFyQBSWYBAAAAAFQBAAKW
bAAF1hgMAQEADAEBAAwBAQAMAQEABgEBAAYBAQAI1jAAApT/lAaDDwAGAAcAAAAAAAAAAAwBAQAA
AAAAAAbvCAAAAAAAAAAADAEBAAAAAAAKdBQAvwAT1jAAAAAADAEAAAAAAAAMAQAAAAAAAAwBAAAA
AAAADAEAAAAAAAAGAQAAAAAAAAYBAAAU9gEAABrWCAAAAP8AAAD/G9YIAAAA/wAAAP8c1ggAAAAA
AAAAAB3WCAAAAP8AAAD/NNYGAAEKA2wAYfYDAAAJAAADJAEWJAFJZgEAAABhJAEAAV4AAA4mAA3G
BwEaAwHQAsAPhAAAEYQAAF6EAABghAAAAAEUAAABAAAACj6eAAA/ngAAV54AAF2eAABengAAa54A
AHGeAACQfAAAAAAAAAAAAAAAhwAAAAAAAAAAAAAAAIcAAAAAAAAAAAAAAACQUAAAAAAAAAAAAAAA
hwAAAAAAAAAAAAAAAIcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAkAAAMkARYkAUlmAQAAAGEkAQBuAAAWJAEXJAFJZgEAAAAAVAEA
ApZsAAXWGAwBAQAMAQEADAEBAAwBAQAGAQEABgEBAAjWMAAClP+UBoMPAAYAB/////8AAAAAAAAA
AAAAAAAABu8I/////wAAAAAAAAAAAAAAAAp0FAC/ABPWMAAAAAAMAQAAAAAAAAwBAAAAAAAADAEA
AAAAAAAMAQAAAAAAAAYBAAAAAAAABgEAABT2AQAAGtYI//////////8b1ggAAAD/AAAA/xzWCAAA
AP8AAAD/HdYIAAAA/wAAAP801gYAAQoDbABh9gMAAAAGcZ4AAHKeAAB3ngAAfJ4AAH2eAAB+ngAA
E58AABSfAAAxnwAA+Z8AACegAABYoQAAvaEAAAKjAACQLAAAAAAAAAAAAAAAhwAAAAAAAAAAAAAA
AIcAAAAAAAAAAAAAAACQAAAAAAAAAAAAAAAAeAAAAAAAAAAAAAAAAHgAAAAAAAAAAAAAAAB4AAAA
AAAAAAAAAAAAdgAAAAAAAAAAAAAAAHQAAAAAAAAAAAAAAAB2AAAAAAAAAAAAAAAAdAAAAAAAAAAA
AAAAAHQAAAAAAAAAAAAAAAB0AAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAARQAAA4mAA3GBwEaAwHQ
AsAPhAAAEYQAAF6EAABghAAACQAAAyQBFiQBSWYBAAAAYSQBAG4AABYkARckAUlmAQAAAABUAQAC
lmwABdYYDAEBAAwBAQAMAQEADAEBAAYBAQAGAQEACNYwAAKU/5QGgw8ABgAHAAAAAAAAAAAAAAAA
AAAAAAAG7wgAAAAAAAAAAAAAAAAAAAAACnQUAL8AE9YwAAAAAAwBAAAAAAAADAEAAAAAAAAMAQAA
AAAAAAwBAAAAAAAABgEAAAAAAAAGAQAAFPYBAAAa1ggAAAD/AAAA/xvWCAAAAP8AAAD/HNYIAAAA
/wAAAP8d1ggAAAD/AAAA/zTWBgABCgNsAGH2AwAAAA0CowAAS6QAAEykAABNpAAATqQAAFqkAABo
pAAAm6QAAHOlAAABqQAAb6oAAJ6qAAA3qwAA26sAAEmsAADmrAAANa0AAGOtAAA9rgAATbAAACyx
AABFsgAAf7IAAPizAACWtQAALLcAAFu4AAD9AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPkAAAAA
AAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPQAAAAAAAAAAAAAAAD0AAAAAAAAAAAA
AAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA7wAAAAAAAAAAAAAAAP0A
AAAAAAAAAAAAAADqAAAAAAAAAAAAAAAA6gAAAAAAAAAAAAAAAOoAAAAAAAAAAAAAAADvAAAAAAAA
AAAAAAAA5QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAA
AP0AAAAAAAAAAAAAAADlAAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAA
AAAAAAAAAAAA/QAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUDAAomAAtGAAAFAAAKJgALRhcABQIA
CiYAC0YAAAABLwADLgAHJAEAAVsAAAEUAAABAAAAGlu4AABduAAAQbkAAN66AACtvAAA6rwAABG+
AACnvwAAr8EAAPHBAAB1wgAA/cIAAFnDAADlxAAArMYAAMbGAAA3xwAAf8cAAP7HAABeyAAAfsgA
AH/JAADCyQAAOsoAAKLKAAD6ygAAJ8sAAL/MAAD9AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPkA
AAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA9AAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAAD5AAAAAAAA
AAAAAAAA+QAAAAAAAAAAAAAAAPQAAAAAAAAAAAAAAAD5AAAAAAAAAAAAAAAA+QAAAAAAAAAAAAAA
APIAAAAAAAAAAAAAAADyAAAAAAAAAAAAAAAA8gAAAAAAAAAAAAAAAO0AAAAAAAAAAAAAAAD5AAAA
AAAAAAAAAAAA8gAAAAAAAAAAAAAAAPIAAAAAAAAAAAAAAADyAAAAAAAAAAAAAAAA7QAAAAAAAAAA
AAAAAPkAAAAAAAAAAAAAAADyAAAAAAAAAAAAAAAA8gAAAAAAAAAAAAAAAPIAAAAAAAAAAAAAAAD5
AAAAAAAAAAAAAAAA7QAAAAAAAAAAAAAAAPkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUCAAomAAtG
AAAAAWEABQMACiYAC0YAAAABAAAAASoAAAFgAAAbL8oAADDKAACFygAAhsoAAIzKAACNygAAlMoA
AJXKAACiygAA8MoAAPfKAAC/zAAA78wAAPDMAAD0zAAA9cwAAG7NAABvzQAA2s0AANvNAADlzQAA
NM4AADvOAAAr0AAAW9AAAFzQAABg0AAAYdAAAMvQAADM0AAAKNEAACnRAAAw0QAAMdEAADjRAAA5
0QAAR9EAAJXRAACc0QAAJNYAACTYAABM3QAAUd0AAILdAACO3QAAnN0AANTdAAAd4gAAK+IAADvi
AAA84gAAcOIAAIPnAACE5wAAlucAAJXpAACj6QAA0ekAAMfzAADV8wAA4/MAAPDzAAAC9AAAHvQA
ADH0AABa9AAAbPQAAI/0AACi9AAAwfQAANT0AAAP9QAAIfUAAD71AABI9QAAbvUAAIz1AACn9QAA
sfUAAPwA/AD4APQA8e3xAPgA9AD8APwA8e3xAPgA9AD8APwA+AD0APHt8QDx7fHo4Nvo1+jR6ADo
y+jX6ADo4NvoxejF6MXoxejF6MXoxejF6As2CIFtSAkEc0gJBAs1CIFtSAkEc0gJBAs7CIFtSAkE
c0gJBAY1CIE2CIEACE9KAABRSgAAAA82CIFDShgAT0oAAFFKAAAIbUgJBHNICQQABzUIgUNKFgAE
Q0oWAAAGCWoBAG3wAAYJagEAtPAABglqAQC78E6/zAAAAs0AAHnNAADlzQAAPs4AAGjOAAAr0AAA
btAAANbQAABH0QAAn9EAAFHTAADB1AAAJNYAABjXAABu1wAAJdgAAEzYAAAM2gAAgt0AAIPdAACO
3QAAnN0AANTdAADq3gAASt8AAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAA
APsAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAA
AAAAAAAAAAAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAA
AAAAAPsAAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD2
AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA6wAAAAAA
AAAAAAAAAOkAAAAAAAAAAAAAAADnAAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAVYAAAFXAAAELQAHJAFAJgAGLQAD
JANAJgBhJAMFAgAKJgALRgAAAAEAAAABYQAAGUrfAABv3wAAl98AADHgAABF4AAAZeAAAIPgAACk
4AAAzuAAAOLgAAAH4QAAFuEAAC3hAADyAAAAAAAAAAAAAAAA4QAAAAAAAAAAAAAAANAAAAAAAAAA
AAAAAADyAAAAAAAAAAAAAAAAvwAAAAAAAAAAAAAAAK4AAAAAAAAAAAAAAADyAAAAAAAAAAAAAAAA
nQAAAAAAAAAAAAAAAIwAAAAAAAAAAAAAAAB7AAAAAAAAAAAAAAAAagAAAAAAAAAAAAAAAPIAAAAA
AAAAAAAAAAAAAAAAEQAAAyQACiYAC0YMAA3GBwFoAQE4BAYPhDgEXoQ4BGEkABEAAAMkAAomAAtG
CwANxgcBaAEBOAQGD4Q4BF6EOARhJAARAAADJAAKJgALRgoADcYHAWgBATgEBg+EOARehDgEYSQA
EQAAAyQACiYAC0YJAA3GBwFoAQE4BAYPhDgEXoQ4BGEkABEAAAMkAAomAAtGCAANxgcBaAEBOAQG
D4Q4BF6EOARhJAARAAADJAAKJgALRgcADcYHAWgBATgEBg+EOARehDgEYSQAEQAAAyQACiYAC0YG
AA3GBwFoAQE4BAYPhDgEXoQ4BGEkABEAAAMkAAomAAtGBQANxgcBaAEBOAQGD4Q4BF6EOARhJAAA
DAAAAyQAD4TQAhGEMP1ehNACYIQw/WEkAAAMLeEAAErhAABc4QAAfuEAAKXhAAC44QAA1+EAABHi
AAAd4gAAK+IAAHDiAAC04wAAnOYAAIPnAACE5wAAlucAAN7nAADy5wAA/+cAAO4AAAAAAAAAAAAA
AADuAAAAAAAAAAAAAAAA4QAAAAAAAAAAAAAAANAAAAAAAAAAAAAAAADQAAAAAAAAAAAAAAAAvwAA
AAAAAAAAAAAAAL8AAAAAAAAAAAAAAAC8AAAAAAAAAAAAAAAAugAAAAAAAAAAAAAAALoAAAAAAAAA
AAAAAACzAAAAAAAAAAAAAAAAswAAAAAAAAAAAAAAALMAAAAAAAAAAAAAAACxAAAAAAAAAAAAAAAA
rwAAAAAAAAAAAAAAAKsAAAAAAAAAAAAAAACfAAAAAAAAAAAAAAAAnwAAAAAAAAAAAAAAAAAAAAAA
AAAAAAsQAAUkABOkeAAUpHgAFiQBSWYBAAAAAAMlABOkAAAAASkAAAEQAAAGWQADJAMTpHgAYSQD
AAEvAAMuAAckAREAAAMkAAomAAtGDwANxgcBaAEBCAcGD4QIB16ECAdhJAARAAADJAAKJgALRg4A
DcYHAWgBATgEBg+EOARehDgEYSQAAAwAAAMkAA+E0AIRhDD9XoTQAmCEMP1hJAARAAADJAAKJgAL
Rg0ADcYHAWgBATgEBg+EOARehDgEYSQAABL/5wAAB+gAAAjoAAAY6AAAJOgAADDoAACS6AAAk+gA
ALToAAC16AAAtugAAPMAAAAAAAAAAAAAAABzLAIAAAAAAAAAAAAAagAAAAAAAAAAAAAAAGoAAAAA
AAAAAAAAAABfAAAAAAAAAAAAAAAAVwAAAAAAAAAAAAAAAHPkAgAAAAAAAAAAAABqAAAAAAAAAAAA
AAAAXwAAAAAAAAAAAAAAAGoAAAAAAAAAAAAAAAAIAAAUpHgAFiQBSWYBAAAACwAAAyQBFKR4ABYk
AUlmAQAAAGEkAQkAAAMkARYkAUlmAQAAAGEkAYAAABYkARckAUlmAQAAAABUAQAClkcAAzQBBdYY
BgEAAAYBAAAGAQAABgEAAAYBAAAGAQAACNZGAAO5/5UIcRGxHwAG3AgAAAAAAAAAAAYDAAAAAAAA
AAbcCAAAAAAAAAAABgMAAAAAAAAABkAOAAAAAAAAAAAGAwAAAAAAABPWMAAAAP8GAQAAAAAA/wYB
AAAAAAD/BgEAAAAAAP8GAQAAAAAA/wYBAAAAAAD/BgEAABT2AQAAGtYMAAAA/wAAAP8AAAD/G9YM
AAAA/wAAAP8AAAD/HNYMAAAA/wAAAP8AAAD/HdYMAAAA/wAAAP8AAAD/NNYGAAEKA0cAYfYDAAAA
CxAABSQAE6R4ABSkeAAWJAFJZgEAAAAACrboAADI6AAAKukAAEvpAABM6QAAb+kAAHDpAABx6QAA
hekAAIbpAACH6QAA9AAAAAAAAAAAAAAAAO4AAAAAAAAAAAAAAADuAAAAAAAAAAAAAAAAbvAAAAAA
AAAAAAAAAGUAAAAAAAAAAAAAAAD0AAAAAAAAAAAAAAAAZQAAAAAAAAAAAAAAAPQAAAAAAAAAAAAA
AAD0AAAAAAAAAAAAAAAA7gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJ
AAADJAEWJAFJZgEAAABhJAGAAAAWJAEXJAFJZgEAAAAAVAEAApZHAAM0AQXWGAYBAAAGAQAABgEA
AAYBAAAGAQAABgEAAAjWRgADuf+VCHERsR8ABtwI/////wAAAAAAAAAAAAAAAAAG3Aj/////AAAA
AAAAAAAAAAAAAAZADv////8AAAAAAAAAAAAAAAAT1jAAAAD/BgEAAAAAAP8GAQAAAAAA/wYBAAAA
AAD/BgEAAAAAAP8GAQAAAAAA/wYBAAAU9gEAABrWDP///////////////xvWDAAAAP8AAAD/AAAA
/xzWDAAAAP8AAAD/AAAA/x3WDAAAAP8AAAD/AAAA/zTWBgABCgNHAGH2AwAABgAAFiQBSWYBAAAA
CwAAAyQBFKR4ABYkAUlmAQAAAGEkAQAKh+kAAIjpAACV6QAAo+kAANHpAACD6gAAR+wAAG3uAADP
8QAAcfMAAMXzAADG8wAAx/MAAH8AAAAAAAAAAAAAAAB8AAAAAAAAAAAAAAAAegAAAAAAAAAAAAAA
AHoAAAAAAAAAAAAAAAB4AAAAAAAAAAAAAAAAeAAAAAAAAAAAAAAAAHgAAAAAAAAAAAAAAAB4AAAA
AAAAAAAAAAAAeAAAAAAAAAAAAAAAAHgAAAAAAAAAAAAAAABxAAAAAAAAAAAAAAAAcQAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGWQADJAMTpHgAYSQDAAEAAAABLwADLgAHJAGAAAAWJAEX
JAFJZgEAAAAAVAEAApZHAAM0AQXWGAYBAAAGAQAABgEAAAYBAAAGAQAABgEAAAjWRgADuf+VCHER
sR8ABtwIAAAAAAAAAAAAAAAAAAAAAAAG3AgAAAAAAAAAAAAAAAAAAAAAAAZADgAAAAAAAAAAAAAA
AAAAAAAT1jAAAAD/BgEAAAAAAP8GAQAAAAAA/wYBAAAAAAD/BgEAAAAAAP8GAQAAAAAA/wYBAAAU
9gEAABrWDAAAAP8AAAD/AAAA/xvWDAAAAP8AAAD/AAAA/xzWDAAAAP8AAAD/AAAA/x3WDAAAAP8A
AAD/AAAA/zTWBgABCgNHAGH2AwAAAAzH8wAA1fMAAOPzAADw8wAAH/QAAFr0AACQ9AAAwvQAAA/1
AAA+9QAAgfUAAKf1AADt9QAAHvYAAE72AAB+9gAA4fYAABj3AABA9wAAZ/cAAJP3AADF9wAA9PcA
AFz4AACZ+AAAE/kAAGX5AACr+gAAVfsAAPwAAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA+AAAAAAA
AAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAA
AAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAA
AAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAA
AAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA
9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAA
AAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAQAAAAFWAAABVwADLQAHJAEAHLH1AADt9QAA9/UAAB72AAAp9gAATfYAAFn2AAB+9gAAifYA
AOH2AADs9gAAGPcAACP3AABA9wAAS/cAAGf3AABy9wAAkfcAAJ73AADD9wAA0PcAAPL3AAD/9wAA
XPgAAHj4AACZ+AAAw/gAAPH4AAAS+QAAE/kAACz5AABj+QAArfkAAPv5AACq+gAA2foAACb7AABV
+wAAVvsAAGL7AABw+wAArfsAALz7AADY+wAA5vsAABT8AABx/gAAlf4AAML+AADx/gAA8v4AABb/
AAAX/wAAGP8AACn/AAAq/wAAUP8AAGH/AABi/wAAaP8AAGn/AABr/wAAbP8AAHn/AAB6/wAAgP8A
AIH/AAD59Pn0+fT59Pn0+fT59Pn0+fT59Pn0+fHt8e3x7fHt8e3x9Pn0APTl4Pn02vQA9ADWzdbB
zbvN1gC0sbSptAC0sbQAAAAADzBKRABtSAAEbkgABHUIAQQwSkQAAA0DagAAAAAwSkQAVQgBCzBK
XwA1CIFDShQAFgIIgQNq44sAAAYIATUIgUNKFABVCAEAEANqAAAAADUIgUNKFABVCAEABzUIgUNK
FAALNQiBbUgJBHNICQQIT0oAAFFKAAAADzYIgUNKGABPSgAAUUoAAAc2CIFDShYABENKFgAACG1I
CQRzSAkEAAs2CIFtSAkEc0gJBABCVfsAAFb7AABi+wAAcPsAAK37AAAU/AAAbf0AAHD+AABx/gAA
lP4AAJX+AACq/gAAq/4AAKz+AACt/gAAwP4AAMH+AADC/gAAUP8AAFH/AABS/wAAU/8AAPgAAAAA
AAAAAAAAAAD1AAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAAAPEAAAAAAAAAAAAAAADtAAAAAAAAAAAA
AAAA6wAAAAAAAAAAAAAAAOsAAAAAAAAAAAAAAADrAAAAAAAAAAAAAAAA3AAAAAAAAAAAAAAAAOsA
AAAAAAAAAAAAAADrAAAAAAAAAAAAAAAA6wAAAAAAAAAAAAAAANIAAAAAAAAAAAAAAADrAAAAAAAA
AAAAAAAAxQAAAAAAAAAAAAAAAMUAAAAAAAAAAAAAAADrAAAAAAAAAAAAAAAAuwAAAAAAAAAAAAAA
ALsAAAAAAAAAAAAAAADrAAAAAAAAAAAAAAAA0gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACR8A
DoRoARGEaAFdhGgBYIRoAQAMIAADJAIOhGgBEYRoAV2EaAFghGgBYSQCAAkgAA6EaAERhGgBXYRo
AWCEaAEPAAADJAETpJABJGQGAQABTsYIAAAA/wYBAQBhJAEAAQAAAAMRABOkeAAAAVYAAAFXAAMt
AAckAQAGWQADJAMTpHgAYSQDABVT/wAAVP8AAFX/AABW/wAAV/8AAFj/AABZ/wAAWv8AAFv/AABc
/wAAbf8AAG7/AABv/wAAcP8AAHH/AABy/wAAc/8AAHT/AACE/wAAhf8AAJX/AACW/wAAl/8AAJj/
AACZ/wAA/QAAAAAAAAAAAAAAAPMAAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAA
AP0AAAAAAAAAAAAAAADpAAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAOkAAAAAAAAAAAAAAAD9AAAA
AAAAAAAAAAAA5AAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAADkAAAAAAAAAAAAAAAA/QAAAAAAAAAA
AAAAAN8AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA3QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAADk
AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAOQAAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAA
AAAAAAAAANYAAAAAAAAAAAAAAADWAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGAAADJAET
pAAAYSQBAAEfAAAEHwADJAJhJAIABB8AAyQBYSQBAAkAAA6EaAERhGgBXYRoAWCEaAEACR8ADoRo
ARGEaAFdhGgBYIRoAQABAAAAGIH/AACC/wAAg/8AAIr/AACL/wAAkf8AAJL/AACT/wAAlP8AAJf/
AACi/wAAvP8AAL//AADA/wAA9/AA8O3w9/AA6eYA4QAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAhtSAkEc0gJBAAEQ0oWAAAHNQiBQ0oWAAQwSkQAAA0DagAAAAAwSkQAVQgB
DzBKRABtSAAEbkgABHUIAQANmf8AAJr/AACi/wAAvf8AAL7/AAC//wAAwP8AAPgAAAAAAAAAAAAA
AAD4AAAAAAAAAAAAAAAA+AAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEA
AAAGAAADJAETpAAAYSQBAAYyABEwARQwDyZQCQAcUAEAH7CFLiCwwkEhsEYEIrBGBCOQRgQkkEYE
JbAAABew2wEYsNsBMgARMAEUMA8mUAkAHFABAB+whS4gsMJBIbBGBCKwRgQjkEYEJJBGBCWwAAAX
sNsBGLDbATUAETABFDAPJlAJABxQAQAfsIUuILDCQSGwRgQisEYEI5BGBCSQRgQlsAAAF7DbARiw
2wEaMAI1ABEwARQwPyZQCQAcUAEAH7CFLiCwwkEhsEYEIrBGBCOQRgQkkEYEJbAAABew2wEYsNsB
GjACMgARMAEUMD8mUAkAHFABAB+whS4gsMJBIbBGBCKwRgQjkEYEJJBGBCWwAAAXsNsBGLDbATUA
CTAAETABFDA/JlAJABxQAQAfsIUuILDCQSGwRgQisEYEI5BGBCSQRgQlsAAAF7DbARiw2wEyABEw
ARQwPyZQCQAcUAEAH7CFLiCwwkEhsEYEIrBGBCOQRgQkkEYEJbAAABew2wEYsNsBAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAIQCAABEAGQAAAAAAAAAAgAAAAAAAAAAAAAAAADUCOcD6APoAwAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADwAE8EIAAACyBArwCAAAAAEEAAAACgAAUwAL8B4A
AAAEQQEAAAA/AQAABwCBAREAABC/AQwAHwD/AQAACAAAABDwBAAAAAAAAIAyAAfw7gEAAAMEjr5V
WLGEMrzKQJGNByX5Hv8AygEAAAEAAABEAAAAAACXAWAhG/DCAQAAjr5VWLGEMrzKQJGNByX5Ho4C
AAAAAAAAAAAAACAOAABABgAAUOUVADivCQCQAQAAAP542m1SPUvDUBS976Vp0jTVIg5SRIKD1UHB
0h9QEOmkg+3gJK00asA0xVRCwKGzkz/AoTi4u0oHcRBHcXVxEhykgm5q431fimDC451z373vnNwb
AhkArUoAKEwDe3RcGaoQJUQiQpMk4WiJTMnYMlWn2Z8Km1bSztgEorn0OBQgYWWQR36F6BzXYw7g
CVOzMseGtWZ3rx53XIAGYS4+aG/EzcAJE6D45muxvx3sAyzo1un90Uv0gOtudxgxDmBBChMXMdvE
vWSV9JkcKx3Ggt9KPpL8jP49v9YE/5J8QAT/jP/xAyn0U/d8N3TW3cjZCPxmG5SfTd0Kf/0Qvr8S
8bUlq6FPmgai1bB72PICYsropcEudkLFt9KsoS3XlrzM5gQrge+F3lvbwftZvKe9a6zn1YPgsOOp
2DykEdVQIHZErE8qGRZ7xpgrNfqkYHKNouI3wkPRlrzMVVATRUMvaFtyXhafKW8EiO7kweBswP8C
QulsLQ67rg/RSN+5MOCYsI4wBwqraYnuENB4/TfmrnEobwIAAEQAZAAAAAAAAAACAAAAAAAAAAAA
AAAAANQI5wPoA+gDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPAATwQgAAALIECvAI
AAAAAgQAAAAKAABTAAvwHgAAAARBAgAAAD8BAAAHAIEBEQAAEL8BDAAfAP8BAAAIAAAAEPAEAAAA
AQAAgDIAB/DZAQAAAwThVNBjL6KyIDrdRmEKsepz/wC1AQAAAQAAAMgCAAAAAJcBYCEb8K0BAADh
VNBjL6KyIDrdRmEKsepzegIAAAAAAAAAAAAAIA4AAEAGAABQ5RUAOK8JAHsBAAAA/njabVG/S8NA
FP7u0ktt2mpxkuIQHNwULOIgCIKuOtji3NRGDbSptNESUOjs5OQkUhz8KzqIk6O4uji5lQpu/mh8
uVyqBROO+76797333XsMKUBbYwDHLMJP0ErxGHHGFGI8CAKJFtmMOlvi8W16pMjwdd2cnCY0r08h
jyCUIUf8jtAtrZcs8EqhaRWTwZblHZb8Ixsos9DFJ+8MpRlchAU4/bmiX680asCHMK6eTvvtZ1qP
B4N2yAEDCQpcoOgJ2gtGQaxkQ+nAj/iD4kPFb/j4/b0W8W/FeyziX/4/fpAgPyWnbrfMbbtt7jTq
lovYz64w9F8/TO5vpMrIvGXR1anjeHdNz2pW+9bofJk0wEbD9ZpO5XjPiXx0tGvZ2oabUdwVf+O8
UVxehNZMN634KpKENu2a5dtVFqm7rKobMpus7pzY8fl4dc8x1GwMOT/5aESdyMm8QE9OnHE+V/Rb
nl1H+1LsnyVxzsLXUwsQ43gyUScYNKn/Acpxc6+mAgAARABkAAAAAAAAAAIAAAAAAAAAAAAAAAAA
CAznA+gD6AMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8ABPBCAAAAsgQK8AgAAAAD
BAAAAAoAAFMAC/AeAAAABEEDAAAAPwEAAAcAgQERAAAQvwEMAB8A/wEAAAgAAAAQ8AQAAAACAACA
MgAH8BACAAADBFXgR18xvk26BSEIYrCfxjP/AOwBAAABAAAANwUAAAAAlwFgIRvw5AEAAFXgR18x
vk26BSEIYrCfxjMkAwAAAAAAAAAAAABAEwAAQAYAAMDWHQA4rwkAsgEAAAD+eNptUr9Lw0AUfnfX
9MdZMLRLEYfg4KZocXJycauCtn9AI54ayA8htTEg0tlJiotbcXDyT+hQnBxExNW9uIjuauvd5a41
YMJx78t979738j0EBQDSRQAY5kE8Bl8FrCOMkIoQHo/HMlpGFfVtFevTmUlGEW9kN8olHi1mZ2EO
xiINTI4HPLoVqAww5NQZxSnClt06asTHDKCJhIov3BlJMXApCmD+mvXY2wtcgGuDbr6cvUevfD0f
fkQCA1DIcOISZ+f5XqVVo1YSqR9xgh8UHil8g9Pn9yTBPwr3UYK/43/0QIbraTgeC61tFlm7gWf7
oPWsZ2l7qgfJ/XOiq2k8muJXMV/jU1NcaflFhc8pdwTCwLU95rfYJG+FpnmQoTzad8LjwHf2XKZ5
dyThUYXXpCsNdtoK1F0d8iTtchSnQ4Z5wQl8N7YmnG7+b70OqRGhy27bjmvzckznTu/XuT00UD0W
FT6ggh2yE5eJpizNq6R66qE38l9PPXSV6qmHpjUZUDVFVE6atAcSz0zISdSXs4kwXqjHYYt5EBnk
YCcHF0j4lOVnOtYzlHiGgMj8Xye2iKDqPAAARABkAAAAAAAAAAIAAAAAAAAAAAAAAAAA7wQcBegD
6AMAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8ABPA8AAAAsgQK8AgAAAAEBAAAAAoA
AEMAC/AYAAAABEEEAAAAgQERAAAQvwEAABAA/wEAAAgAAAAQ8AQAAAADAACAMgAH8Fo8AAADBNz3
8cjE4LoDZoPtmxJJi8//ADY8AAABAAAA3QcAAAAAnQFgIRvwLjwAANz38cjE4LoDZoPtmxJJi882
VgAA//8AAP//AABZBAEAgQQBALg7DAA4rAwA/DsAAAD+eJxdvAW4FmUXtr1iaKWkREBKRFokpSQE
pFMalO4OkRAEpEVQECnp7s5NN0hLS4mAiAiIlMB/zrzv+3/H98lxsp9nz8w999z3Wte61rO3qMQT
8Teyi8SSibGE/wJwjSvhm1fsy6B+EL5KYC/571VeZYmdSBJJ6a4tPu3eqev76SuXq1uncllJ9d8j
WaR0pw6dP+3epmn7Ful7teneOn3nbs26tuncPUelNh07de/aqWObZunfey9PeBdTi+6i4djRfQN9
NfoaSzX6Gpuvcfn61CT673/n5VSROHz91/Q/B/77Xf2/RjHeJ+RrZo/137P6BbWDkP+8+8/Isf6f
ke2/I8v/NbLL/2bcVMMRl8kyWcrf1X2FfAiFfZXk9DWSCVL6Okngm0ThH9sqv9t2uWw75WfbKwds
v2yzw7LajslCOyXT7Yx8ZxdkhF2Wgfar9LKb0sH+lGb2t9Sxx1LVXsiHZlrE4uq7llDftmSa1tJo
csuor1hWDSyXPtX8el+L6O9aWi9rRT2j1fWo9tb5Okin60idrOP0W53Cq9k6RJdqP12vvXSbdtED
2k5Pagv9RZvoTa2n97SmPtPKGss+0kRWWl+3YvqWFdbcll8L27v6oWXXKty1vmXW5pZeOzOTvpZK
v7IUOs6S6jRmuMBe0VUWX7cy44MW6Glmfw3umugznia2/ytJ/alkgwL+WAbCaF4P9fu8vi89/C8p
A4V4nQ6S+t9c87c8s3/kLityzZ7KaTjIWFsZcxVjz+M+U7jfOO47mDl8bom1IyvVnLnVZY6VmGtp
5lzQsmlOy6kZeJaUVlBftSLqVlIfaTm9w8r9ysqd0zqsXiPdo800hvVZzTotZL2ms24TWb8xOlqH
sp5fsK49dKZ24GgLXc4VG/VDPa4lGKEgI+XRPzSb/qMZ9YWm0bisUGJm9jqzzMSMszP7/DxNCbsv
H7HfNdn3RnZVWtkv0sXOST9iYygx8o0dkSl2UOYSO8uJoc3E0x7bIsdtk/xi6+SmrZG/bZW8sBUS
j3hM7kvkTV8k2aGgL5DSUNnnSQOYyevpHsbtgCiGY2Sc5g++g2n6brBQswer9a0gRjME+zVtcEJT
Bhc1SXBDEwT3NFbwjOSKZU89kf3tKe1Pz2A3Pbtd9rx2zovacS9jh7yWbfbGttZb2mLvaHO9v03w
wTbaR9kQ/9b6+Q/Ww2dYO59nzXyZ1fM1Vt03WTnfbiV8r+X3w5bdT1hGP22p/KIl9GsW+A17arft
L7tnv9lDu2BP7Kj9a3tMfAtHV1hcRovvUzl7rCX2oZbU+1gK78QILSy1N7A0Xs3SMbt0XsjSey5G
zwhimf1vzezHNKPvhWWa3mfB95rOR2oaH6ipvaem8raawhtrMq+hSb2sJvSi+orn0fieWWN7KjV/
VV8gM0/tkTyy2/LALhGjJ+Q2WX6dXbrEzpy3eXLKpsgxG0fMfiU7rS9x21n2W1fef8b3vySeR8lF
myhXbLbcsCVcv0Hu2W55SAQ8sfOo0Q0xfyCBv5T4Ho85EE2enjnlYH6FmGcZ5lyNuTfkGVrzPN15
tn6axYdrVh8PSzSbb4BjmsMvwt+8fgEpLCvrkZV1ycL6ZGadMrJeGVm3dKxfOu/CGvZhLYeypmNZ
23CdF7Deq1j3cP33sQ/H2Y8L9shu2gO7b3d5d9ti+3V24xJXn2XUU5bTj1hB328lfadVZM9rsveN
iIEW7F4nYqI3sTHQx9lwYuVbYmai97WZ3tB2eA3b56XsDLP7xfPYb/62/eFp7b6/RiwmMMTeYgWP
iNE7xOo1YvY0sXtYMwW79O1gIzG9lNieTYzP1IJRrIcx39nD+F/LOm1HY7ZKat8iqVDrFJAU9U4M
CVHy+BGr0J9VrP8y9iFkiTyGv22B3Ie/2N9bcMPmsOdz0KdZ7OUs9n0G+z6D/f2Rff6R/Z4qW2CD
TZZZMIPX38N4jo2F0Zw7DL7i2sHwJWMNgP6M/Tl05d6doSMx1R7akvltUYDWERukOfHWHHVoSrVp
ilJ8Qvx8gmo0JhYbE0cNicuGKE3jiMccewovOFe0KYrUPCKutkRDW6LhrVGr1uhoW3S9LVraHgVr
j56Gmt/Z0mlXNLUrVag7utozIgu6mw1y6ADLC/nQ4kLUhkI6zN7XEVZcx1gZHQvfWwWopD9YFZ1q
VaG6/ghzrA5aXkcXWT1ooMuska6IaKJr7FNdZ810A2yxVtSXVrrT2ulu2G8dqDUd9Ih10WNwwrpR
d0J66HnrpZfgivXW6xF99Jb1ox7107/sC70P/9hAfQxPbRD5PEjFh2hciO9DybOh5P9w8mo48TJS
348YrmWhPMcqQRXOrQm1fZDWixioDaCRf6FN4FNysQW08j7QW9tE9NIO0Mm7aTfvBB20R0Q77RXR
Rnt7K2ihfbwZNNF+3gga6BdeD2rqQK8ORXn9PuTjWF7IwbnZIDPXhmRkrPSQjrHTQGrulQqSaRdP
ComZxysQX9t5XIitzfyFNKMmfwpNqM9N/B+p7X9ITb8pVfyqVPLLUgFK+Rn5wE9LcT8lRaGAH5F8
kMP3Ut/3kmPb5T85tpcc20t+7ZRkkJTvJYaE5N4rEJe8iw2BbyDPNlDN1pFn63Bna3BQ/6lw9+Ev
qtxduEMe3ILr5OEVuGSLyLlF5NwCtHQBeTdP9sJu8mcdrCGf5sAsXv8A33NsNIzi3BEwjGsHRywh
75aQd8vIu5AV0hc+596fRayRntCZ6tuZfOsYsZU83Al7ycOQg9Iy4gj5eAz+4vV9+Idjj+Ep5/4L
Rj4FEJt8ig8JyafEkJScSgYpyKlU+llEOvIqnfYn3/qTawPItQH4sC/Jt8EROXQU+TbaCpBf7+u3
5Np4mEyuTY0oq7PItzkwj5xbQM4tIt+WwCrybQ1sIN82wRbybSvsJs/2w2Hy7FhEGz1Frp2Gs+Ta
ebhoncitTuRWF/Kqi94g527DHfLuLvxF3v0N/5B3T+Ffcu8FGLnwCiQkN5JBCnIlM2QldwpAIV6X
gjIcqwCVOLdmRB+tE9GbHOtNjvUix3qRYz3IsZBuxG5IF/KtCzHdBloR659CA2I/pA65UBsqkRsV
oAyvS0EBjuWDPJybC7KSG1kgMzmaEdIzVjpIQ46khlTkcApIRk4nhcTcMyH3jg9xmUtIbOYo8ELq
4XvrkU91oCb5VBNPWx2q4XGr4Her+J9SnvwqC6X8V7hKbl0mty7jhc+RW+fIrTOSl3zLQ67lgqzk
WmY/TI4dJMf2R3kW5lv8qL4N0qTBfX0l+AV+0/jB73Bf4waP4YXGDgKLHcS2IIhvFiSEpFTTFPbC
U0E6+9fTU2Ez22PPav94NlxfLqpuXvvL8+H+ClKFC9vvXsyu+oe4wI+o0NXtlNe0E17Hjng9O4yH
2O+NbLd/atu9mW3FT2zyVrbB29gab2crvIMtwactwGPM8W42w3vYVO9lP8B4721j8R2jvR+OoB/u
8QvcwRfWxwdaL+jmg6yDD7Gm0BBvUguq+HA8ynA8ylC8yVAzjv1jQ3Akg+wO3LKBdg0u2hd22vrZ
CThsfWyv9badsMV62TrrYSusmy2xLjYPZlgnm2od7HtrZ2OtjY20FjYUBtqnXN3EPrNG1tUaWHur
Y62ttjW1mtbYqltdq2w1rKJVsXJW3j60MlbSilsJK2RFLJ8VtjyW37JZXsvMq/SWw9LwLoVlsaSW
0V6xdBaX78SyVPZSk9kj+rx79A936PVuqdlp/UtP6J96jH5vv17VnXRv2+n5luguXUTHMkvX6gxd
qVPp9CbTm3xP1zee7mUsHeA3dDCj6AZH6Nc6jL8H61f6pQ7gT1/tT8fYl47mc+2kn9H39NRW2p0e
qCudTWd6w45aW9vTH7WlT2pLv9SabrOlFoPC2pwOtLm+q001J2TST/RNSKmNNQnclk/0Blyidz4P
J6S5oo16WFrqXtgtrXWHtNUY2Cjtda101NXSWZdLV10s3XW+9NS58pnOlM91uvTVKdJfJ8oAnSBf
6jgZoSNkrA6Q8dpfvte+Mlk/l1naVeZpZ1mkHWWZtpcV2lbWaGtZpy1lBq+n8v0fOP49532r3eUb
/YzxhjHuKO4zjvtN4L6TuP8U5jGd+cxmbnNhIXNdypxXMv/VsJ7n2cyzbZPGuhP2SkM9CEekPs9Z
X09LXZ65rl6Tj1mDj1mTupoWMmh9fQve0YaaG95jnQpCMdatJHzIOlZkTatCTda4DuvdiHX/lD1o
wV60Y086sTfd2KPe7Fdf9i3cxa/YxxG8+oa9/Y53E3k3hT2fyXfmEgMLiYXlxMRq4mSbzqHLXUHP
uob4WacXdIte1q30rgeJsVP6WM/Su15UsevE323i8JGmsueaxpSojU30xidmExO7qYjldER2Zito
WYnxXFaM75Qk3ksT9+WsFLlQnpyoRG7UIEfqki+NrR750oC8aUT+fEoeNSOfWpBXbcjWduRZBxtN
/n1LHn5PTk4lN2eRowvI1WXk7SrO3ABbyeedZORBrjpCvp+C81x9Ca7bcHqRkejASLrI0fQqo+lM
xqATY+gLx6IZY9GOMdYYmnKsHXTykXQjI+lWh6M5Q20ojERLxsC36M736M9ktGgGujQH5qFTS9Cs
FbAGDVuHlm1C07aibTvRub2wH907jP4dQwdPo4nn0MYL6ORlr00XXRkd/QhNLYe2lkZjS6K1xdDc
wmhvQTQ4H1qcB03OgT5nQ6ezoNkZ0W50IkgNqSx+kMxeCRLDK5YwiAuBJQ4E/qUGPI7qwMmo578p
P8sJOS6X5Jycl6tyWm7y/i85Kv/IIXkh+ySW7pJXiefk5GNa8vEtYjwnsZ6fmC9GTn5I/FcmL+uQ
C43JiZbQmfwI83MAjCBfxsEknSbX4Davn0McmylJIBU9bkabK9lsvuSzhVLcFktZWyrVbLnUt5X0
I6vpb9ZLD9so/SxGhtoOGWN78G376JkOySI7KqvoZbbYafzdefmJnvtnuy6X7ZbctLt4xAf4xif4
yLBXjkWPHI/eOBHePblm9zf0Pc+ghf1tLek59SPPr9W9CH6iJB6iLDW/Ib65KZ66rX7lnXWUowaO
2vhXOs2/1tk+QRf6FF3qs3W1L9aNvlpjfJPu8J26x/frIfrro35WT/o1PeO39ILf00v+TK+523W6
1Vt0rXf8DbvrmeyeZ7cH1NNHXtSe0Hc/80r23GvZS7rel97cNOhoHvSE/nS4X8FEixP8CMt4vQH2
c+wYnOXcs5YgOA1H7NVgN4zi9WD43OIFXbmmLTTlmrqcX43zy3OP4tyvAPfNxRzetof+JvNJydwS
2W2PxVyf63V/qFf8jv7i1/WcX9Sf/ZQe98P6k+/Wfb5Fd9FDx/hS1mEu6zGNdZmg8/0b1mkY6/Ul
6/Y569eVdWyrg705PUpDvFFp/FAxeqX8Wtlzazl/R0t4Js3vaTWnp9S32at07FkKd/zhS/qCJ/QC
D+gB7sgf7PGvdk3OsedH7Sw99SnZjsdeZz/JMjuAx98jU4mXb22bDLfNMpA46kU8dSauWhJfjYm1
WsRcBWKvFDFYiFjMY9MlC6SzaZLMpkgCmyRP0P571JgbcJFaMB0m8vpr+Ipj/aE7taE98d0cGhDf
NYn9iuRBafKhMDXrXXLkHXIlAznzBvmThDyKRz4pefWvbJO/ZY/8Qb79Kj/JBTlGXp6KcjP8FD6z
H7BsvpCvc+VNnykpfZok8UmSwCeI+3fyzL6RhzaaPmg4PdBQ+p9B9D0D5Yj1Y036sCa9ZaP1kpXW
TRZbF5ltnWSKdZDvrB09Txv6nDb0Nq2ku7Wgf2lBj9KMtflUykEJa0KuNpGX+qn8Dpe1mZzRFnIc
Dmgr2QEbtY2s1HayUDvIbGVs7SLfaTcZpT1kiPaWL7SP9NJ+0kkHSisdJJ/qUKmnw6W6jmaNxqAh
49CSCWjKJMnN+r3N2mVk3dKgKclYs4RoTVx8gLFe/1mrXfKnHECrfkKzTrJeZ1CsX6PvhEfCMzbJ
U1kjostQsEWs9BxWfIak1Mmo2PeSSceyG6PZleFSkBkV0y/YqT7Mphez6oaadZJGPFELnq4DT9qV
J/9cG6FoDWSY1sUhfCwTtIZM0yoyVyvJYq0gq7W8bNYysktLsTKlWKHick6LylW4pe8TQYXkkRYQ
tXysaD5JaXnlTchteaQg9OR1XxjMMbo3mWYF2KlC7Nj7stqKymbYZcXZ0Q/kmJWSs1aGbrc8nW8F
uWeV5JFVkZdWQ+J4LUnkdSW5N5C03kgy+aeS3ZvJe96KzqEdXUQnuopudBi9pJb3kfr+hTT1QdLa
h0pHHy09faz09fHypU+WYf6jfO1z5DtfIJN8jcylK19Eh77Cd8k6PyBb/Khs959lL93IYTqUY1SU
03Qu5+lkLtHZXHfTW3Q+d+iEHtAZPaJbekb39BLF9SC3xgnya4KgmCYKSutrQUVNGVTXVEE9TRM0
0fRBK80YdNIsQS/NGvTTbMEQzRGM0jzBOM0bTNJ8wUwtECzUQsFKfT/YqEWDHVo8OKAfBMfhjJYK
LsNNLRP8BY+0bFDZyga1rUzQGJpbqaA9dLcPgr4w2IqjkkWD7+z9YIoVCmYaY1u+YKXlDTZanmCr
5Qj2WjYUNSvKmiW4aBmD65Y+uGNpggeWOnhmKQP314J4nihI4q8GKT1O8KbHCjK7Btn8mefxJ17I
H3hxv+tl/LZX8Btew694XT/vjf20N/cT3tn3ek/f6V/5Kh/pS3ysz/PxPtNn+ASf49/4Ih/hy/xL
X+N9fQNnbuGK7d6Wq5r6QW/oR/xjRqnCaOUZ9QO/6O9zh/f8umf3W/4Wd03rf3pK/8sT+d8ex/9x
9af+BD9xDz9xCz9xDT9xHi9xAh9xEHbhJWLwEWvxEEthLh5imiUNJsDXlow6lIy6lCJoCSV5XRAy
cOx1SMK58bhG4Qk95z36zVv0mtfgAv3mSbXgkEqwS194jP5L7XhK7fiH2vE3teO+T9Q/qR1/+Agi
6Etqz+fUnu7Uzw56nh7+tDfRE15Pj3h1PegVdS91ZDt1ZIsX1A3+rq6hjiyjjiyijsyjjkz2BPo9
9X8s/ffI6OdLfxPhfxLpv0tn/0XaEsGN/SepS1TX8D1SybeRJZvpt9eTNavps5dKqMG5fDZ99nT6
6knyhk8ky76TV/0bsm402TecLBxKNg4iK78gO/vJebT3BNp7EO3difZuQXvXor1L0d65aO40mIDm
fo3mfoXe9kdre1ojdLgRNaoBOtxAPrZ6aHE9tLgOylEHLa4nf8FN1OgynEGZjsI+bSLbUKr1sBLV
Woh6zYRJKNk4tHkkqjYIbe6DwnVD6TqgzS1QvSaoXx1UsCq6XA5FLIkyFtZv5D39TrJT47Kgy+mo
aamoZ4mpZfGpZQF17F9Zi0/ciF+Mkd9R3l+pX2fQ4+P8vYd329DjTejxMrR4EVo8By3+URKgwUl0
PFo8Vt7UkTjKodxlIFrcj7v2lhJUjXLMsjIzrk1lacCTNOOJ2vCEXXjanuhvf61F5a1GhalCpalA
xSlP5SnLE5fiyT+gIhWnMhVFh99nZQqxQvlYqXxU8LxyV/Ogw7lYxVysZg5JBCktG1qcDS3OihZn
ZQeysRPZ2JEc7EwOdigXO5WLHcvDzuVlB/NJDOxGow+jz6fQ5oto8zW0+Tba/ABtfoY2u1eQeF6F
al1NXkeXM/jH8rbXl9zocgF0uai3kDLociXvQNR1QYt7yCfeW1p6P2nvA6U7mvy5j5QBPgYtHo8W
/4AW/4gWz5LpaPJcX4Yeb0KLt6LFu2Qn0bvXL8hZtPgiWnyFCL/h/8gd/1fuocUP0eInnhj9TYH+
pkN/M6O/2dHfd9HfguhvCU0dlEN/K6O/tTVz0Aj9bYH2tkN7u6G9fdDeQWjvSHT3G3R3Iro7Hd2d
j+YuR2/Xo7UxaO0+OKrl0eEKwS/wm1ZCgysFz7VKkNKqBG9atSA3FOR1OahqldDlSuhyBRSlAk63
PE63LLpcFl0ugy6XQpc/CGaj04vR6dXo9CZ0eicafRCNPoZGn0Wjr6DRt9Dnu5Y5eIQ+P0efY3nq
IIGnDF5Dn99AnzN4giAr+pzLPcjnL1HJJ17KH6Ka91DPO6joDdT0Gqp60Vv7We/uh/1z348ub0GX
16HJS3yyz0WdJ6HJ3/kK/xpNHuab0OatnLmTK/Z6R65q6cf8Ez/l9RmlBqNVQo/LoMdFuUMB/8Nz
o8fv+H3PgB6/7o89CXqcwF+4u1BRLHiIFt9Bh6+jwxfR4VNo6WF0dTf6GoPWroelaO9cS4Uup0aX
UwfDeOL+0NLSsaLpghK8Lghvc+xNSMK5cbjmpaZgR5IFd+kHb2ni4KomDM6h08fR6QNo9A40eqMG
VFehyr6gx/mXXuexf4dGj0Kfv0Kf+6PPPdHnLuhzO/S5mV70BnrWa+spr6zHvJwe9hK63wvrTn9P
t3p23eRvoc1v6gp/XZf4a2jzqzoDXZ7qij4/lbHo8miidii6/KX/ihs5gz6flOa+TxoS4R+jy9V8
o1TwtVLKl5NBi8mk+ZEuh/r8n98TMYkdhL5ZLStZkp3jb3E8PbqdyvH0aLb7OAngDnp93YbIb3AJ
z3wa3T4DR/HNR2A/+r0d/d5oPWQTrELDV8JidHwU2j0Y+qPf3dHvjtAcDW+MhpeDEmh4bHihoX9u
ggtsIpdQstORh24mx2B/5KNbyHZYgE7PinS6mwxGn/ujhj3R547oc0sU8hMdInVRy2qoZgU0Oh/a
nIu+IwvanB5tzgBvoM+voc9Cf/EUXX4G92VH1Fvcgd/o6y+j0FfgHB1G6KCPQHgkPCtGHkRXbJDH
skpeyBJxXSBxdJYkgsTodwpIrj9wp/G49PHcdQyOfaTkYWYFID8zLYKWl2L2FXiahjxZe560C0/f
G/3+gso1FP88Bg0fj3eeg34vQrs3od070e79gINjdYrKWfT7CoT++SY6/hf++R90XNDg2BB66BRo
cjoIfXQuNLoA9OR1XxjM8VEwDa2ejU5vhl1o9X40+oqVld/hFjp9Dw/9CA/90qpJXLQ6jtfAQ38s
KSC518NHN8BHNyCimkgOyI5250O7C3sbKYl2l0O7q6LbDdDtZj5EOqHZvfxbGYReD/epMga9Hu/z
ZLKvknm+QRb7FlnpO2Q9UR3jR2QHzmMHUb6PaP/J2Rtnj/w3OeMP5LLfh8fyGxnyu8ch62LDK7ik
18jGN8jKDGRoeshCtuYic/ORxUXJ6FJkdwV9PaiGplfja11NGzTWDEFLdL2lZgo64qt7ou190fbB
mgtyouvvBmPR9/1o+XE4BqfR9MtwCW6g63/BXfgHfa+MTtdGoxtDc3S6PXRHq/tGev0+ProQOv1u
sM1y4qFz4Z3fDn6xTKhZZlQtY/CnpUXh0uGhQx/9BqqXKvgXAk8WxHccpCcJknrCIJXHxVPHC9J7
7OAttyC7/+vZ/Lm/i2IWRj0r+k30+7p/BAXR8QKQyx+hsI9Q2CeeEZ1Pi96ngxT48kTUgMQQF69u
3OOpJQ/uc98/UMhfmc8FasfPzDGGerKeeW+AGdSayfQFfahBfaEbtKMmtYdm0Ihnbgy1oBLrUNnC
viPsP8I+JOxHwr4k7E/CPqU4fUwe+plcwWgYwj70Yz96UW87sT+doRU1uImmCz6B+uxhdRS7oiYP
KkEZTRIU11eDAhovyKOxgqyqQSZ9jtt94smp84n0nsfT2+56w5/JNX+IH7glp/yaHPHzchAO+WnZ
7cdkqx+UTb5b1qCsy2A5rncB6jobNZ0IP/hcGYdyjoLRqOdXPgE/MkEG+tfSA7r7MLzKMOngA+RT
7yv1vLtU9s7yobeXEt5aCnpzeZdcyUsPms0b45ybQCNJ4w2hniTz2pKQPEuIP4rtVeUFOfiCXvYf
8vEv8vKmfSiXydPLeKt9VgKK4aSLR70wDkBm4cGmQtgvjyTPB0HYQ/ch73tA2FcX5H1ueJNzUkIc
rlO04BEacw+veAuuojnntIScp4c/DgfQpF36oexGnzbjMxfjN+dqVZmndeR7POgErS/foGXfaEMZ
hjcdhr4N0MYyUJvisFvisFtKV22Ny26NgneWxtpXKukAKaODpbiOkEL6teTVcZINFc+MiqfTmTjs
uZIU9Y6Pu46ta0V1Mwq+XR7KbrkrB+WWHJPrclHOyjU5xbsj0XfDo885y3UTyrxM0uoiyaTzJCuK
nQe1LoDjroSfr4jjro5a1+DO9ZlBPVT7Ux0mrZlRK2pLJ3qAz7S/9KLefIGCD9HPZbT2xGX3wl13
wV13wlW3YWXasEKtqGGtcNUt5HfU/SXEiT4v+lSKQ9noM6Rm0giaUR87RJ8vtZJu0M/asEvhZ0/t
2LF2sojeaAW1dYV1lw32mWyj7u6jd/qJOvyT9Zef6ad+oT7/YoPlVxsmf9hIGCFGFManB4vv36PU
P0o6VDYtZERpM0E2vEFY///nBUKNqOlXvZ5f8BZ+0rv4Pu/lu3yor/ZRvtTH+Xw67Vl03N/j7sb6
Ytzech/ka72f7/B2nN3Mj3odrqzqZ1CaC14ST/eBX8JB/uJFGDmf/+Y5/Hd67TuozR+ejl47Jf4u
EWqUGIcZl547Dj5PUSVDwZ7Qc9/C512zgL7bUZ249N7xcbTx6b1fQX0S4+8S4++S4e2S0XOnoOdO
gUNOhb9LFXzA6wJQENJzPBW8Don/+3m/wmOqwU083VW4BuepECdw/wepFgfpwXdSObZQRZboI59D
RZmDv5tKdfleH8BdH6N/wZ8+XO/A7z5Qf/PeetW76TW47O31grfUM95YT3pdPerV9JBX0H1eUnd4
ESiqGz2PrvW3dTmVarln1Pko1BTUaYrH14ko1Dh/gbo8hid0OQ/gPpXzD+lHB9OFbqYdVbGJH5Ka
+L/KHkO13YiyrKX6rpT32OPQ34W/4ZiHvX/Hp7H3E+nNJ6AuE4iLcVT1oVT3IfIY7uPxbhFbV4ix
q3Aeb3eC2DsJB/F1O/F1W+jP1xKXS4nTZTCX+J0GPenFO0JLevHG8DG9eDkoYbVxI7XxeWFvXocO
sw6dZtif18Pv1cPvhT16AzkCW6MevYmsgxXkzIKoT28hM+AH8mosHnAErulz8q0rnXB7cq85Tqox
+ViFHC2Lw/qAvP0/6jGBDnqipNFp5P00uuqZOLW5aMFSMXgqq1GQ1XThm+nGd6AZO3B7e3B+x+U0
HOXVLr6zG2LwgBvwgEvwfgvkJbyQWYw0VeLh9xJDIv0WhRmDVo3hbsNRmSHMYIi8g2LkxqkWYrbF
ca9lUYpKPEktFKI+T9mUp23N03dmNXrg/fppDdSlCk63knxL7z4ZrZ2F5i5Ag1fg9fbj9Y7g9U7T
r1+CsG//TXOwwjminj02vXlCCPv2FPTr6SDs3XNZFvxfFnYqK648K/17tqh/HwJhL9+P9z0g7O8L
8j43vIlfTAmJ8Itx4CX3vQGXNX/kPc9QI45SHw4wv5VaWlZpOfxqeXatAqpYSaZoRZlKbfiOZxql
1VHM2vjbepHP7U9t6ElN6AJdqQttqQnNtS2euKN8rF3Z0Z5SHpX9ANV9X79kR4dJDh2Fox+Ho59A
PZhCPZgur7CjsakLSl14xk7eRe1vyV5qwQlqwVlqwXXZL7fZxXuylVqwTmLpCkmCc39d58ibOgOH
PplRJ0t2djEH5MO5v089KAyliKXy1INyxFVVdvUTqlRLqlULYq4Du9qN+Ouun0lf7U5l68GudZFx
7PAk4nQW1W0mcbsw+hlAS9nAU65nx7fBUXb9DFymOt6Ev4iAlxAn+iyrHnWiHnUi/HyrgdSGRtFn
Xo2kBXSIPgdrwm41obqHOdhG5lhrWUJuriFHN5OrO6gbB8jbA9SN4/Rp58jnc/Y5TqE/rmEgDMBB
DMZJDMNRjIQRuI3xkhpXngEnk95ZE58hOX0Orn6WvI3bedeXoSPL6CnXSDGc+oc49Yq+nX5zO33n
XmmEW28IrXFQnfySdITP/TZu6C6u6K4MwWkNx3GNwa2Px6n/gFOf46nodTPrKs+m6zwvfXBx3e1l
6Isr0R/XoE+uT7/8CX1za/rnjtBBL3l39LUP7m0QfInujqDXDj8PHYse/wAT6cGnodNz0exlsBQN
j6FP34WeH0LbT8FJevjws9bwM9db1IHwc9iwJoSfzYaf0Yaf1Yaf2Yaf3baEFrzvAF/BEM4ZDRNg
PLVoDiyFJdSoLRY72AkH4QC16zh17Jy98Kv2r9+0x/7Y/nah7sX2Pz0hdTCF3/I0fsMz+zVc+yXP
6+dx7We9hJ/ycn7MK/thr+27/VP4xLd6a2jjq7wPfO5LfIAv8OEwjOr8tf/o4+E7/9an+xifw5FF
PthXeHff7j2gI6M0ZdRm8DF3qcYdw94grP8/R78LdUtDXcgmE8j/aTAXjxgDu/GIh/GGP8Mp/OFF
esVr9IrP8J+BlxX38hIP4nslSQpJvIq8Tq+YETLgX9+GrF6XCKoruekXC+J1i+F7P4QyeODK3o4q
1ok+sQ9++Qv88xDp48OJntFEzbdEzff0iVPpE2fIDBzMPF9Cr7iBPnELfeIO2eX76RH3wTk55zfk
Kj3iVSrlTf9b/iTy/qQ/fErUPfWEREEiSE4UpGX3M7Hz2egJC2gq+oY3IE1Qlr6iLD1hJXrCWvQd
Dek/GurbQXPNDjmCtvQlbekJu2re4EstAPmDEVo4GKNFoGiwjh5wCz3gPtgLp7VS8AtchOtahd6n
Cj1ileBfrRaktGpBCkhnNYLcUJDX5aCqVaFnqkLvWAlXUynoTz85GFZbUfrGwrig/ERaASItX3DM
8hJp7xJpOYOz9GNXLEfwO/3kLcsa3LUswV/2VvDYMgQv6Cmf08PF8jRBGnrIjP5K8A79Y36XoAj9
YmlcWFUisw7x0Mh/JU5+IdrOETs/EXEH8IMx+MH1eMGlPsXn4Qon4wXH+0qibS3RthlPuI0z93kn
rmhFTDXg6pqMUhn/V4w4L0q8F2D0gvjAPHjAd/wucf+3Z+DOr+MDU9ORJmUmSfCACfyZv8LMnK72
Gbn0EB/4Dzl2hxzcTU7G4O3Ww1I65AkwjCfrDy3pUBtDcV4XgIKQhePp4E1ITCcbG4/4gh1/Cf/Q
Pf6pyfCCSYMraMIKOsYF+L8FRMksdGMyneO3RM63+MCReL8heL9+6Ew/fF8P9Kczvq+t/oJWnfNa
+jPaddzL6k9o2QEvqLv8Xcir29C4zZ4Jv5cW0ulST4LfS6Az8XnT/CUd5WO6yfvwQL4mcofh8Qb5
VenlP+P1jksL34PG7pA6+Lzqvh7tXS2lfSmZNBednhH5+dDX50azQ93Oz/uSvkI+gPK+Tj6Cqr5J
qkAtNLsBnW0zsqYpdPRTZNxZOtazaPV1tPo2nvOujIQxZM94dHuym/5IBs0hgxZ5MjQ7vW7wLLrF
c+h2z6d7/X096B/oES+vJ7yKnvaP9bw3RKvbo9NdWade0BOd7s/aDUWfR8MoPPV3rO1UmIJOz2a9
w89UF7H+q2ClJsSfJ0ajkwZ32aPwc9nw89k47F/4eW34uW34+W34OW74eW5jaMT7FtAf+nHOUJgA
44mbJbAe1qHdWywhWRQEf6DRf6PRT9FooweJTywmRqNTEZ/p0eis9C25ICdKmR+dLoJGV/TTXt1P
0DEdpGM66M1R1vbQwbd4b9/gA2EAGv2VL/PRMAqNHoci/wAT+Xs2Gr2IjFmDPm/yz3wvV+31rozU
kpFbwSfcpb5fIYOuUAGuey2o5LfJpNt0Vw+8EJ1SXn/u78HbHitI7/GC1P5qEHj4OVFqMiVd8Kdl
DG5a5uAyOnDGsgVH0YYDlifYEf3stkCwygoFg6wMulKGlSpDhSuP1pQPmkEjq8BqVgiqQFn0pxwU
gFxoUu7o5xThzyvCn1uEP78If44R/jwj/LlGqHvhzzrKBOu1VPCNFgpGopGjYBB62Q3t7A7to5+d
ZAtaoK0toZFmDmprxuBjqIL+ltPUQQmys6AmDwpBDn01eEvjBW9qrCAlGZpEn9MpPfJHcpsove63
5JJflNN+UHYT2dt9m2yCzb5Z1vhyWYCDme2zZRr86NPJtklk2iT5lk5olH8jX8FQHyVf+DD5zL+U
rtDN+9NhdZV63hGH0xqn04asa0XWNZUi3pgMayC5vA5OqS58jGuqDdUlFTUvlVeTxF5R4lIL43oF
OvKP4EN5Sr18ah/QYRWXC9TQk1ZQDlFTD1kB2QXhz8224LXnQPgztan47/EQ/pxtdOTXw/r8v//n
82r0u2p35TGxex9f8Se+4ia+4gI6+jM99lF8xUH0dTdau4UefA1Rs4z4nYe/mOEfEoflUO6K6HpV
/4J47kWkdUL9WxPXjakAtbwJMdfES+E/3qca5CHW00BSIvShtfLbRuzDdmvm6+xTX2xNfCZMtAY+
yur5l1bHP7Pa3t6qe1Or6h9bRa9o5byklfaCVsKzWxHPYIU8ueX1BJbLX2o2f6iZ/XdN55c1lZ/U
pH5AX/FtGttXq6AMj2263rcJ+ruN1Ks2SC9Ybz1pnfSQtdDd1ki3WE1dZxV1mZXUeVZYp1o2HW0Z
dYil0T6WTLtZQm1nsbWZida3p1LD7ksF+0M+sJv0R1fpky5IZvtZ0thxSWY/SXzbL2Z75bFup3vd
Sv+zSS7qOjmla+SgrpKdugxnv4TebJHMo6v4EcbrPHqdeTKYDqMv1Od1DajAsVJQiHPzcF1WOpH0
jPE6YyXRDZJAt9BTbqeP2S0P6FruyGG5QS9zLeppttDBbJAnsoZeZ4XE4fpEjJOS8dIxdhbuk0tn
SQE6muL6I13Lj1KX/rQp9OX1YBjNsfHwI+fN45oVXLuJMXYy/8OMeYq5XOLZbvGM93jWp7ozevZX
7DC95FF6yZOS1c5JHrss79tvUop1q8T6fcw6NmY9W1lc7cT69mKdB1pmHWs5dLK9p7OsmC6yyrrJ
6uhOa6IHrY0et256zvqxh0P1pn2jf9kU9nauvrDl7PVm9nwPe39cU/sFTe83iYl7xMZzzeNxrIC/
ZoX9TeLnHeIoP/FUIoqrql7LavonxFxbYq+nNSL+mhCHnxKPLYjLFsRnK+K0DfHazg/DaevgV+C2
dfJkRH469Dsr5PV2OJV2Xhb3U4VYr0vMN4W25EE38qEPuTGIHBlNrozH30wlf+aQR0vIpzW4qE3k
1058/H68zlGy5gJ5eJVacpO8/DPyN7H9hb+wMG8zWpjDibQrjqmr76GK7KMGHEL/j6L/x8nBn5nD
GXz6BfLwUvSbK/mpBblxU+/gpjJFv71y11P6PU9EXYiHiwo/RXtmj/yBPfE79syv23O/ZC953pd+
zDT6jcjtsNliBdNggsUJOke//RgrqAgfcqwY5+WHnFzzFqRljOSMlYgx4zD2y1B7cUN39Z7fwBFd
wg2d1dvs2S1y9rrvoPJv1ivk7S++WC9Q2c/Qlf3sE3BHX+OOhukhH6D7/DPcUVfcUVvcUXNd7410
tdfR5V5VF/tHOKSSOtuL4JDy6yTPqRP8bR3nGXSUv6HD/DX90l/V/nj73nSV3XApnXArbVDEFtSD
Jv4r2v0LfcU5+ouTUs5/Qrv3od070O4YnNJGeQcHlZbakAoXlZS68Ardb2yfKOLfyWP7Wu7TGf9h
X8lv9qX8Qvd8hi76uH0Wdda76LRj6LrXWTtZYa1kgbWQWfYpmt0EzW4gY+jih1odGWi1pbfVlG5W
XdpZVbr4ynT0FaWufSTVrBz6U45c+lCKWmk0qDQaVJI8KylJrQS5V0KuaUk0p6Ts1yJyRAvLCbih
BdGjgvIvr80KSyorQn4WkRxWTPJBUa4rxRgVoBpj1mX8RtynBfdsx727MYc+zGUg8xrO/MYwz3DO
U61R9AyLrFn0TBusTfSMe3jWQzzzSZ49/CThqg2Qm6zJn6zNPzZK/rVvqG/fUesmUfemSQqfKWl8
Pr3fUnq/lTjStfIea/+hH6KG/orzvBXtUwf2LNy7cA/DvRzmyaO9Dfc43Ospnluns/ezvZgu9NK4
5oq60qvjoOvoRm+sMd5Sd+Aw93h33HZf4mow8TWCOBtHvE0k7qYTf/OJw+XE5HqcaAwxuodY/YmY
PUXsXtSHfp1YvoPLf6jP0JjnHot4T0Dsv0YevEE+ZILs5Md7Fi8oAqUtQVAN6tqrQWvobInIo0TB
bF6vhs0cOwjHOPcs113i+htwh/EeMu5zxnfnHni3JHQ8KcnXN8nbt8jf7OTxe+RzIfK6OPkd/lZE
BVxnDXK/Lp1UYzqq5uhBaz9JP3/UQ91IGv0u7FCbgC+YKIFMkrjwikyRxJBMpkkqmS5pIL3MlMwy
W7LKXMkh8yUPvCcLpaAslsKyVEpASVku5WSlVJTVUlnWSk1ZL3VkozSQzdJEYqSZbJNW0E52CJEh
3WSf9II+cki+kJ9kEAyV4zJSTsoY+Vm+ldPyvZxlRueZyUVmcIW7X+Gu17nbDe5yi7vc5g53GP0u
oz5g1AdyQB4x0hNGesYoL+Ucle8XKuRVqt9Niad/yKv6J1Xwb6rnY3lN/6UavpQ31DWtxtEMmkAz
aSJ9S5PrO/q6Zue7ufnuu3wnP98pyLsS/F1Si+iHvCqnpbWqVtTq/KnNnzpaT+trI22sn2hTbc6f
ttpT+2rniP4cDxnAeCH99U1Iy7E3IK0O5k4juP/X+rZ+x90maU6dzh3n6nu6kLsu18K6VovpZu68
gzvvZg4H9SM9ppX1NPM4rzX1CuPf0Lp6WxvqPWbxiDk805aq1lZjWUdNYJ01iX2mr1tffdMGaCYb
rO/YV5rDRmhe+1oL2DgtapO0jE3TCvimKjZfP7bF2tBWa3Nbr21th3a3Q9rXftIv7RL1+ob+YA/w
TY90gT3HQ6mtsFi2zuLZBnvVtthrtt3etMP2lh2zd+yU5bTT9q6dt4J2yYrYNStp1+0ju2NV7Z7V
tAdWz/6xhvbUPrF/raUJddm8s8X27hYfX/iK97fEPtiS+TBL4SMslX9laajZaXyApeNYOv/cMlLH
M3J+Zu8akYXrs3hHy8pYIdm8JTS3HPjLHNT+XN4YGloerwO18ZU1obrl86pQGe9QDj7Ec5aMeN+L
QRErio8o6u9ZcX8XctsHeIsP/G0rhT8thdcoQ/0r469bWU8Ciaw8+lDe41kFd1CrhG5U4ms1tKMG
xz7mnHqeEu+RFt+RAd/xFn4jOz4jt3XjXj28sPXGt/Tz0vaFf2SDmNsQ5jqceY9m/mN5lm95tu95
xh945qmswwzWYxZrM491WsR6LfFvbIVPsFU+xdb5dNvgc20zHifGV9oOX297PMb2+Q475PvsJ//J
jvpJO+nn7Ge8wDk8wQV8zy/4g8v4hF/9if3mL+13j0XHmwCXkoQOOKX/jS49xmM8xWv86++6BAXd
gmIeBKU9dvCRxw+q+itBHU8YNPKkQVNPFrT2FEFnTx309DRBX08XDPb0wQjPFHzjbwUT/e1gmr8T
zPXswWLPGaz2d4ON/l6ww/MH+7xgcNQLBz97keCClwiuecngtpcO7vmHwRMvF2jwURAnqBgkCioH
yYOqQdqgZpAB0gbVg9d5n5zvJ+H4q5wXLygX4GK4pnTwnHGeMd5DLxY8YPy7cJt73eC+17j/Zc/N
/XIGZ5jTSeZ2lDkeYq77mPMez8Dc0gcxPMdGnmctz7WS/nopz7mQ553viYPZPPt01mAKazHR4wbf
sS7fsD5fs1Yj4CvW7UvWrz/r2Nf/8Z6saVf/C+3+Ez/5B17vd7zlTfzeb7jK8Gewl+nCfsFVXsBV
nsNVnsFVnsRVHqfvP+rF0PvC+MP8foA6sQcfuIe92UbtiPEMvpn92uBv+Dr2bo2/5qv8VVxpPHC6
vpc2B184wx/Zj/RvU/2eTSYGxvsNYu06MXfFxvhF4u8CcXjGhhIvQ/w4sfkznLGBfH8gx7/gvC/8
GrF7HW5YH8boQxz1ZrzexFIvxg/pwb16+HPiXXHN7l2IrS4eB5+dIKIDc+uAZ23HPNt5crx2Sngd
v/0GpMVvZ4BM9J1vwdt473cimnhOyM1qvQvveQPWIqQe61KP7rYOa/QxaxVSi3ULqeEfRVRjPUOq
eGWoSndbHWrjrutElGWEsqx9GY6X4vwPuLYo473P2AW4Vz7unYc55GJeOVjrbMw3C/PPyLOkZ53T
8ZypeeZU5FMK1iKp30XjbqF11y0ueRebNTTW8z//GsghtHEPGrnD/rYYNHO93bWVdtuW2i1biJbO
RlOnoa2T7KJNsLP2DXo7wk7Yl3bQ+tt++8x2W3fbaR1tq7VHn1ui003R68a2Cu1dZrVtiVW3BVbR
5lg5m2UlbLIVtu8tv41Ht8dadvvaMtlXaPpge90GGNXEEjBiHOtszqjPqRG3qBnXtJad10p2RstT
L4raHi1kMZrHlmoGW6hpqS+v0be9ZiupR4fgJ01kF+GSvmp34C616hk813iWiGqShDukhTepLm/D
O9ytMBSh4pSGD+2lVobqXNEQGnN1S2htT5jRE21qD/n+Xa3N7KradS3HnUoyw8J2WnPaQX3L9lIR
d1AZY5jVeu68koq5VF/qfH2is/WOTtTr1OVL1OdzOkxPUq/36WdU4u4aox2V2qgrqbZz8QDT8QKT
qMjf4Q2+oVKPoGI3x0/U11c5Eod6rdTtp5Jff5N39bJk13Pytp6UTPoTnf2u6P8PDP+fpji6FO8y
Hx8zEz8zBW8zEY/zLZ5nNN5nKD5oIJ6oj1ySHnilLnimdvinFnIUz3VI6uGvasou/Ng2vNlmKY1b
KoZrKohPy4uLyoF/y4KXS4+zSs0dQs+XkLvEjfxg6Av/9691hf+C1//+ta5AakWfIM2X58TWc+Ls
pU2BaabUE6Vn9ojZFitivsWBBNSYVyOWWiJI4sstOaSk7rwOb/hqyxCxlhq7lvq6mloaspIaGrKc
mrncqjBGFV9IzVxotRi3FvXrY+5TN2Km1WcO9altDX0SHND6Efu0TMRc3RKxT+dFHNA5EYd0VsR8
dG4hrETrVsN69C5kM5oXA9uoqztgFzU2ZA86uBf2o4UhB9HCI2jhCRvpp9DDkNM2LOKsDUYHv4T+
aGHfiGv2OfRED7tH3LLO0Jb8bw0t0cZPoDGa0BDqo78fo5E1oApaUQkqoJdloBT6kQ/yotfxIA6v
n7E7j/j7XsQTPNYTdOIRGvEIjXhoV+ASjusinOeMU3ACNTkWcceOcPZhOIiy7Ie9dgPtuIGfu4Z2
hFxBP67YJkbZxCjrI87bahRnZcQpWx5xwhYz2mJGm89o8xltbsRe1GoP7LKZ6NlM20YUbYa1RNRq
WE50hSy0iVw10Q7odxH7dHDEXE3iIftUIw7ocwuZYGFs/u9fl+sexet6+YGY+IE9/p49/p4YHE88
jWevv2Wvv2Wfx/pG2MwexrCHW2En+xiym30M2UtNOwxH2MeQYzYA+rPf/dnrvhGn2dPT9hn73TPi
PPt6nn29ZB2hLfvdEpqy342hIftdH+pSD2tBDWpiFajE/pePuIe3vIfPfMDePsCfPiSXHrLHD8i5
BzznPf6+x5+70Z/b7NstuMGra3CFdxcjblALbrAb19jba+zEJXbiEjtwnj09z56eZj9DTlFVQk6w
E8dsY8QR9jXkMHu6F3azKyE7qToh29nbrRDDTm2GjeztWljO3oYsZG/nwwGdHrFLp0Xs0CkR23RS
RIx+HbFc43hIjD6zkG36KGKXPozYow8iphDB02A6ET0T5hLhIQtZl5DF6NBKNChkNWu2Hv1Zj/5s
RH9CNqNBm9GgGHszYiu6ExJDToVsZv1DNpJnG9mT9ejOevZoLXsVspp8XMk+LoaF5GrIfPY2ZLY1
j5jOfk+DieR0yAFtGbFLm0fs0KYR2/STiBitErFcV0XE6IyIbfpjxA6dGrFLJ0cc0B8iJtn/9LlQ
9O8yppb0esTS6ynLGHHaCkU8sqkSctpWRZyyNRHHbF3EIV0TcUBXRezTqRFztZCG7NOMEQc0fcSR
/z/P2kf3zUf1OmbJuWfKiLOWKuK8pY64aGkiLjG3kCuWK+KOzZOQK8wl5JJtiLhom2CLnIezFhNx
yrZFHPvv1wPUy5BduiVih26K2KYbImJ0XsRyzaUhMZomYpumjtihqSJ2acqIA/T/IacsfJb/retX
0fOVlIzkSZaIR/aDhpy2BRGncDYhx+iYQ27p5IjbOjbijo6MuKtDIu7poIgHOhD60a33iXiivena
e+M9ekW49YiIZ93wJd30DasVMVe7WcgbViMijlXDGVXDBVWJoL/EAVXC/VSgPy8PZenVy0Tc01Lw
AY6oaMQdev+Q25oj4hZ3CDmG6wo5ZekiTlv4/P/b87nRmlSX9syrPS6uccRybWMhSaxRRBxrEPFS
60U80zoRj3BjD+GB1oy4h3u7izu7y5xvM+dbzDnkBvMNuc58r2tx+xUv+Stzvaq5IIdd5q4hp+21
iPOWHFKieinRuDQRVyxzxB2bpSFXbFHEJTxeyEVmfBHPdx7O2uqIU7Y24rJOhcl6lT0M+VWHw1D8
4JCIG+zfDf2Cve4Hvdnjz9jfnuxt94gH2lUfwiPtHPEMv/gcXmp7VdYtkYXr59G/ifr/ATF/iqh9
AAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAjQyep5+brOEYyCAKoAS6kLAgAAAAgAAAAOAAAAXwBUAG8AYwA0ADcANgA3ADcA
OAA5ADYAMwAAAH0AAABEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAACNDJ6nn5us4RjIIAqgBLqQsCAAAACAAAAA4AAABfAFQAbwBj
ADQANwA2ADcANwA4ADkANgA0AAAAfQAAAEQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAI0Mnqefm6zhGMggCqAEupCwIAAAAIAAAA
DgAAAF8AVABvAGMANAA3ADYANwA3ADgAOQA2ADUAAAB9AAAARAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAjQyep5+brOEYyCAKoA
S6kLAgAAAAgAAAAOAAAAXwBUAG8AYwA0ADcANgA3ADcAOAA5ADYANgAAAH0AAABEAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACNDJ
6nn5us4RjIIAqgBLqQsCAAAACAAAAA4AAABfAFQAbwBjADQANwA2ADcANwA4ADkANgA3AAAAfQAA
AEQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAI0Mnqefm6zhGMggCqAEupCwIAAAAIAAAADgAAAF8AVABvAGMANAA3ADYANwA3ADgA
OQA2ADgAAAB9AAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAjQyep5+brOEYyCAKoAS6kLAgAAAAgAAAAOAAAAXwBUAG8AYwA0
ADcANgA3ADcAOAA5ADYAOQAAAH0AAABEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACNDJ6nn5us4RjIIAqgBLqQsCAAAACAAAAA4A
AABfAFQAbwBjADQANwA2ADcANwA4ADkANwAwAAAAfQAAAEQAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAI0Mnqefm6zhGMggCqAEup
CwIAAAAIAAAADgAAAF8AVABvAGMANAA3ADYANwA3ADgAOQA3ADEAAAB9AAAARAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAjQyep5
+brOEYyCAKoAS6kLAgAAAAgAAAAOAAAAXwBUAG8AYwA0ADcANgA3ADcAOAA5ADcAMgAAAH0AAABE
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAACNDJ6nn5us4RjIIAqgBLqQsCAAAACAAAAA4AAABfAFQAbwBjADQANwA2ADcANwA4ADkA
NwAzAAAAaAEAAEQAZAAAAAAAAAACAAAAAAAAAAAAAAAAALQAAQAAAAIAAAADAAAABAAAAAUAAAAG
AAAABwAAAAgAAAAJAAAACgAAAAsAAAAMAAAADQAAAA4AAAAPAAAAEAAAABEAAAASAAAAEwAAABQA
AAAVAAAAFgAAABcAAAAYAAAAGQAAABoAAAAbAAAAHAAAAB0AAAAeAAAAHwAAACAAAAAhAAAAIgAA
ACMAAAAkAAAAJQAAACYAAAAnAAAAKAAAACkAAAAqAAAAKwAAACwAAAAtAAAALgAAAC8AAAAwAAAA
MQAAADIAAAAzAAAANAAAADUAAAA2AAAANwAAADgAAAA5AAAAOgAAADsAAAA8AAAAPQAAAD4AAAA/
AAAAQAAAAEEAAABCAAAAQwAAAEQAAABFAAAARgAAAEcAAABIAAAASQAAAEoAAABLAAAATAAAAE0A
AABOAAAATwAAAFAAAABRAAAAUgAAAFMAAABUAAAAVQAAAFYAAABXAAAAWAAAAFkAAABaAAAAWwAA
AFwAAABdAAAAXgAAAF8AAABgAAAAYQAAAGIAAABjAAAAZAAAAGUAAABmAAAAZwAAAGgAAABpAAAA
agAAAGsAAABsAAAAbQAAAG4AAABvAAAAcAAAAHEAAAByAAAAcwAAAHQAAAB1AAAAdgAAAHcAAAB4
AAAAeQAAAHoAAAB7AAAAfAAAAH0AAAB+AAAAfwAAAIAAAACBAAAAggAAAIMAAACEAAAAhQAAAIYA
AACHAAAAiAAAAIkAAACKAAAAiwAAAIwAAACNAAAAjgAAAI8AAACQAAAAkQAAAJIAAACTAAAAlAAA
AJUAAACWAAAAlwAAAJgAAACZAAAAmgAAAJsAAACcAAAAnQAAAJ4AAACfAAAAoAAAAKEAAACiAAAA
owAAAKQAAAClAAAApgAAAKcAAACoAAAAqQAAAKoAAACrAAAArAAAAK0AAACuAAAArwAAALAAAACx
AAAAsgAAALMAAAC0AAAAtQAAALYAAAC3AAAAuAAAALkAAAC6AAAAuwAAALwAAAC9AAAAvgAAAL8A
AADAAAAAwQAAAMIAAADDAAAAxAAAAMUAAADGAAAAxwAAAMgAAADJAAAAygAAAMsAAADMAAAAzQAA
AM4AAADPAAAA0AAAANEAAADSAAAA0wAAANQAAADVAAAA1gAAANcAAADYAAAA2QAAANoAAADbAAAA
3AAAAN0AAADeAAAA3wAAAOAAAADhAAAA4gAAAOMAAADkAAAA5QAAAOYAAADnAAAA6AAAAOkAAADq
AAAA6wAAAOwAAADtAAAA7gAAAO8AAADwAAAA8QAAAPIAAADzAAAA9AAAAPUAAAD2AAAA9wAAAPgA
AAD5AAAA+gAAAPsAAAD8AAAA/QAAAP4AAAD/AAAAAAEAAAEBAAACAQAAAwEAAAQBAAAFAQAABgEA
AAcBAAAIAQAACQEAAAoBAAALAQAA/v///w0BAAAOAQAADwEAABABAAARAQAAEgEAABMBAAAUAQAA
FQEAABYBAAAXAQAAGAEAABkBAAAaAQAAGwEAABwBAAAdAQAAHgEAAB8BAAAgAQAAIQEAACIBAAAj
AQAAJAEAACUBAAAmAQAAJwEAACgBAAApAQAAKgEAACsBAAAsAQAALQEAAC4BAAAvAQAAMAEAAHcB
AAD9/////f////3///81AQAAOAEAAP7///86AQAAOQEAADsBAABxAQAAcgEAAD0BAAA+AQAAPwEA
AEABAABBAQAAQgEAAEMBAABEAQAARQEAAEYBAABHAQAASAEAAEkBAABKAQAASwEAAEwBAABNAQAA
TgEAAE8BAABQAQAAUQEAAFIBAABTAQAAVAEAAFUBAABWAQAAVwEAAFgBAABZAQAAWgEAAFsBAABc
AQAAXQEAAF4BAABfAQAAYAEAAGEBAABiAQAAYwEAAGQBAABlAQAAZgEAAGcBAABoAQAAaQEAAGoB
AABrAQAAbAEAAG0BAABuAQAAbwEAAHABAAD+////cwEAAHQBAAB1AQAAmQEAAJoBAAD9////eAEA
AHkBAAB6AQAAewEAAHwBAAB9AQAAfgEAAH8BAACAAQAAUgBvAG8AdAAgAEUAbgB0AHIAeQAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYABQH//////////xsAAAAG
CQIAAAAAAMAAAAAAAABGAAAAAAAAAAAAAAAAwBHQQB1uwgE3AQAAwAwAAAAAAABEAGEAdABhAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgAC
Af///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwBAACujAAA
AAAAAFcAbwByAGQARABvAGMAdQBtAGUAbgB0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAaAAIBGgAAAP//////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAHUXAgAAAAAATwBiAGoAZQBjAHQAUABvAG8AbAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYAAQEdAAAA/////w4AAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAKA7vEAdbsIBwBHQQB1uwgEAAAAAAAAAAAAAAABfADEAMAA2ADEAMwA1ADkAOAA3ADIAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGAABAf//////////BgAAAALO
AgAAAAAAwAAAAAAAAEYAAAAAoDu8QB1uwgGgO7xAHW7CAQAAAAAAAAAAAAAAAAEATwBsAGUAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKAAIB
////////////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABQAAAAA
AAAAAQBDAG8AbQBwAE8AYgBqAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAABIAAgEFAAAABwAAAP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAABAAAAZgAAAAAAAAADAE8AYgBqAEkAbgBmAG8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEgACAf////8IAAAA/////wAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAEAAAAAAAAAP7///8CAAAA/v////7////+/////v///wcA
AAD+/////v///woAAAD+/////v///w0AAAD+/////v///xAAAAARAAAAEgAAAP7///8UAAAAFQAA
ABYAAAAXAAAAGAAAABkAAAAaAAAA/v////7///8dAAAA/v////7///8gAAAA/v///yIAAAAjAAAA
JAAAACUAAAAmAAAAJwAAAP7///8pAAAAKgAAACsAAAAsAAAALQAAAC4AAAAvAAAAMAAAAP7///8y
AAAA/v//////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////AQAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEA/v8DCgAA/////wLOAgAAAAAA
wAAAAAAAAEYXAAAATWljcm9zb2Z0IEVxdWF0aW9uIDMuMAAMAAAARFMgRXF1YXRpb24ACwAAAEVx
dWF0aW9uLjMA9DmycQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
ABwAAAACANnhCAAAAAAAAAD0bUkA8HlJAAAAAAADAQEDAAoA7wAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAABAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAQD+/wMKAAD/////As4CAAAAAADAAAAAAAAARhcAAABNaWNyb3NvZnQg
RXF1YXRpb24gMy4wAAwAAABEUyBFcXVhdGlvbgALAAAARXF1YXRpb24uMwD0ObJxAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABFAHEAdQBhAHQAaQBvAG4AIABOAGEAdABpAHYA
ZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAACAP///////////////wAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAkAAAAAAAAAF8AMQAwADQAOAAyADMA
OAAwADQANAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYAAEBFQAA
AP////8LAAAAAs4CAAAAAADAAAAAAAAARgAAAADA3MNAHW7CAcDcw0AdbsIBAAAAAAAAAAAAAAAA
AQBPAGwAZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAoAAgH///////////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAFAAAAFAAAAAAAAAABAEMAbwBtAHAATwBiAGoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAEgACAQoAAAAMAAAA/////wAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAYAAABmAAAAAAAAAAMATwBiAGoASQBuAGYAbwAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASAAIB/////w0AAAD/////AAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAQAAAAAAAAARQBxAHUAYQB0AGkAbwBu
ACAATgBhAHQAaQB2AGUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAgD/////
//////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJAAAAgAAAAAAAAABf
ADEAMAA1ADIAMAA0ADUAMwA4ADYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAGAABAQkAAAAEAAAAEAAAACAIAgAAAAAAwAAAAAAAAEYAAAAAYGPFQB1uwgFgY8VAHW7C
AQAAAAAAAAAAAAAAAAEATwBsAGUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAKAAIB////////////////AAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAACwAAABQAAAAAAAAAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABwAAAACAFrUZAAAAAAAAACggUkA5HhJ
AAAAAAADAQEDAAoBEoNJABKDUAASg0QAEoNWAAKGPQASg0kAEoNQABKDVAASg0QACxKDdQASg3AA
EoNwABKDZQASg3IACgKGEiISg0kAEoNQABKDVAASg0QACxKCbQASgmkAEoJuAAAAAQAAAgAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEA
/v8DCgAA/////yAIAgAAAAAAwAAAAAAAAEYWAAAATWljcm9zb2Z0IEV4Y2VsIENoYXJ0AAYAAABC
aWZmOAAOAAAARXhjZWwuU2hlZXQuOAD0ObJxAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAP7/AAAECgIAAAAAAAAAAAAAAAAAAAAAAAEAAADghZ/y+U9oEKuR
CAArJ7PZMAAAAJQAAAAGAAAAAQAAADgAAAABAEMAbwBtAHAATwBiAGoAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEgACAQ8AAAASAAAA/////wAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwAAABiAAAAAAAAAAMATwBiAGoASQBuAGYAbwAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASAAIB////////
////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADgAAAAQAAAAAAAAAVwBv
AHIAawBiAG8AbwBrAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAABIAAgARAAAAEwAAAP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8
AQAAaWgAAAAAAAAFAFMAdQBtAG0AYQByAHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAKAACAf////8UAAAA/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAA8AAADEAAAAAAAAAAkIEAAABgUA8hXMB0kAAAAGAAAAQgACALAEYQECAAAA
PQEMAAYAAQACAAQABQADAJwAAgAOAN4ACAA8EwIAEQACCj0AEgBoAWkApR6VEDgAAAAAAAEAWAIx
ABoAyAAAAP9/kAEAAAAAAP4FAUEAcgBpAGEAbAAxABoAyAAAAP9/kAEAAAAAAP4FAUEAcgBpAGEA
bAAxABoAyAAAAP9/kAEAAAAAAP4FAUEAcgBpAGEAbAAxABoAyAAAAP9/kAEAAAAAAP4FAUEAcgBp
AGEAbAAxABoAyAABAP9/vAIAAAACAP4FAUEAcgBpAGEAbAAxAC4AyAABAP9/vAIAAAABAP4PAVQA
aQBtAGUAcwAgAE4AZQB3ACAAUgBvAG0AYQBuADEALgDIAAAA/3+QAQAAAAEA/g8BVABpAG0AZQBz
ACAATgBlAHcAIABSAG8AbQBhAG4AMQAaAMgAAAD/f5ABAAAAAAD+BQFBAHIAaQBhAGwAMQAaAMgA
AAD/f5ABAAAAAAD+BQFBAHIAaQBhAGwAMQAaAMgAAQD/f7wCAAAAAAD+BQFBAHIAaQBhAGwAMQAa
AMgAAAD/f5ABAAAAAAD+BQFBAHIAaQBhAGwAMQAaAMgAAQD/f7wCAAAAAAD+BQFBAHIAaQBhAGwA
MQAaAMgAAAD/f5ABAAAAAAD+BQFBAHIAaQBhAGwAHgQcAAUAFwAAIiQiIywjIzBfKTtcKCIkIiMs
IyMwXCkeBCEABgAcAAAiJCIjLCMjMF8pO1tSZWRdXCgiJCIjLCMjMFwpHgQiAAcAHQAAIiQiIywj
IzAuMDBfKTtcKCIkIiMsIyMwLjAwXCkeBCcACAAiAAAiJCIjLCMjMC4wMF8pO1tSZWRdXCgiJCIj
LCMjMC4wMFwpHgQ3ACoAMgAAXygiJCIqICMsIyMwXyk7XygiJCIqIFwoIywjIzBcKTtfKCIkIiog
Ii0iXyk7XyhAXykeBC4AKQApAABfKCogIywjIzBfKTtfKCogXCgjLCMjMFwpO18oKiAiLSJfKTtf
KEBfKR4EPwAsADoAAF8oIiQiKiAjLCMjMC4wMF8pO18oIiQiKiBcKCMsIyMwLjAwXCk7XygiJCIq
ICItIj8/Xyk7XyhAXykeBDYAKwAxAABfKCogIywjIzAuMDBfKTtfKCogXCgjLCMjMC4wMFwpO18o
KiAiLSI/P18pO18oQF8pHgQIAKQAAwAAMC4wHgQLAKUABgAAMC5FKzAw4AAUAAAAAAD1/yAAAAAA
AAAAAAAAAMAg4AAUAAEAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAEAAAD1/yAAAPQAAAAAAAAAAMAg
4AAUAAIAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAIAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAAAAAD1
/yAAAPQAAAAAAAAAAMAg4AAUAAAAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAAAAAD1/yAAAPQAAAAA
AAAAAMAg4AAUAAAAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAAAAAD1/yAAAPQAAAAAAAAAAMAg4AAU
AAAAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAAAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAAAAAD1/yAA
APQAAAAAAAAAAMAg4AAUAAAAAAD1/yAAAPQAAAAAAAAAAMAg4AAUAAAAAAD1/yAAAPQAAAAAAAAA
AMAg4AAUAAAAAAABACAAAAAAAAAAAAAAAMAg4AAUAAEAKwD1/yAAAPgAAAAAAAAAAMAg4AAUAAEA
KQD1/yAAAPgAAAAAAAAAAMAg4AAUAAEALAD1/yAAAPgAAAAAAAAAAMAg4AAUAAEAKgD1/yAAAPgA
AAAAAAAAAMAg4AAUAAEACQD1/yAAAPgAAAAAAAAAAMAg4AAUAAUAAAABACAAAAgAAAAAAAAAAMAg
4AAUAAYAAAABACAAACgREUAgQCAAAMAg4AAUAAcAAAABACAAACgREUAgQCAAAMAg4AAUAAcAAAAB
ACAAAAgAAAAAAAAAAMAg4AAUAAcAAQABACAAACwREUAgQCAAAMAg4AAUAAYAAQABACAAACwREUAg
QCAAAMAg4AAUAAAACwABACAAAAQAAAAAAAAAAMAgkwIEABCAA/+TAgQAEYAG/5MCBAASgAT/kwIE
ABOAB/+TAgQAAIAA/5MCBAAUgAX/hQAOAKANAAAAAgYAQ2hhcnQxhQAKAFMYAAAAAAIASVCFAAoA
5icAAAAAAgBURYUAEABRLwAAAAAIAElQICgxNTAphQAXAOQ+AAAAAA8ASVAgKENsYXNzMSA0MDAp
hQAWAAJRAAAAAA4ASVBEViBRdWFudGlsZXOMAAQAAQABAK4BBAAGAAEEFwAOAAIAAAABAAEAAAAF
AAUA6wBaAA8AAPBSAAAAAAAG8BgAAAABCAAAAgAAAAIAAAABAAAAAQAAAAIAAAAzAAvwEgAAAL8A
CAAIAIEBCQAACMABQAAACEAAHvEQAAAADQAACAwAAAgXAAAI9wAAEPwACgJtAAAAIwAAAAgAAERp
c3RhbmNlBQAAUm91dGUOAABJbnNlcnRpb24gVGltZQwAAE5vbiBJUCBOZXQgMQgAAElQIE5ldCAx
CQAASVBEVCBlYWNoCAAAVmFyIGVhY2gIAABJUCBOZXQgMgwAAE5vbiBJUCBOZXQgMgIAAGttBQAA
Ynl0ZXMIAABNYXggSVBEVggAAEF2ZSBJUERUBwAARWxlbWVudAkAAFRvdGFsLCBtcxMAAFBhY2tl
dCBMb3NzIENvbmNlYWwRAABKaXR0ZXIgQnVmZmVyLGF2ZQkAAERlbGF5LCBtcxAAAFBhY2tldCBG
b3JtYXRpb24FAABOb3RlcxUAAGNlbnRlciBvZiA2MG1zIGJ1ZmZlcg8AAG9uZSBQTEMgImZyYW1l
IiQAADIgdGltZXMgZnJhbWUgc2l6ZSBwbHVzIDAgbG9vay1haGVhZBIAAEVuZHBvaW50ICsgSVBE
VCxtcxAAAChSIGlzIGFwcHJveCA4NykKAABBY2Nlc3MsIE5BEAAARGlzdHJpYnV0aW9uLCBORAgA
AENvcmUsIE5DEwAASW50ZXJuZXR3b3JrIEdXLCBOSQEAAE4IAABJUCBOZXQgMwgAAFF1YW50aWxl
BAAASVBMUgwAAE92ZXJhbGwgTG9zcxwAAE92ZXJhbGwgTG9zcyB3aXRoIElQTFI9MS5FLTP/ACIE
CAB0BwAADAAAANQHAABsAAAAMggAAMoAAADTCAAAawEAAEEJAADZAQAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAABAAAAAkE
AAABAAAAHrfbAaLNYgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABN/wAATU4A
DAAAAAAAAAAAAAAAAAAAAAAAAAAAGNCdMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAGmHcDAWt9sBBAAAAJrNYgAEAAAAAQAAAAQAAACazWIAFrfbAQQAAAADEwAATQwAAA0B
AAAHGAAAAAAAAAAAAAAAAAAAAAAAAE0AAAEBAAAATf8AAAAAAACchtsBtAZUMEjNYgB0AAAAAAAA
AAIAxzAAAMUwAAAAAE0AAAFN/wAATf8AAAAAAAB/em0wDgDHMNEAAACKzWIA/AAAAAkAAACdRQQw
AADFMOyjxzDRAAAAis1iAP0AAACKzWIAjM9iAN+/AzCKzWIAnIbbAQAAAACMz2IAdAAAAAAAAACG
qQ4wAAAAAIjNYgAHAAAA/////8CF2wHIz2IAAAAAAAcAUABlAHIAYwBlAG4AdAAAAAAAAAAwAF0A
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAHkHAAABAAAAAAAAAPx+2wEAAAAAHM9iAAAAAAAIAAAAAQAA
AAzvnTAAAAAAXACHABjPYgABAAAA/xAAMMZ7VDCCgVQwrogQMLUaiQBUAIcAZRAAMAIAAAASAIcA
Fv7bAXCiDjAwAAAAEgCHAAIAAAAI/tsBAAAAAAgAhwD8AYcAAQAAAAEAAAAW/tsBAAAAAAEAAAAA
AAAAMAAAAAAAAACczmIAgZ8OMAIAAAACAAAACwAAAP7///8GAocAys9iAMjPYgAIAIcAAQAAAA4A
AADua1QwAAAAAGUQADCge1Qw7ASJAEwAAAD/EAAwAQAAAIjPYgBAAB7xEAAAANjOYgDWnHowAAAA
ANAUSQEIAAAA6M5iANAUSQGIZHswsGNUMPjOYgAIAAAAAQAAANAUSQEEAAAADM9iANAUSQEsz2IA
j6V9MLhSVDAAAAAAzQAAACzPYgAAAAAAiM9iAIjPYgBoz2IAkKd6MM0AAAAAAAAAiM9iAAEAAADQ
FEkBWgAAAOsAAACwz2IAAAAAACLQYgAlhRAwyM9iAFoAAADQFEkBAAgAAJVgCTDrAAAAWgAAAMjP
YgBRYAkwqAQCAvutDjAAAAAAlstiAP////8AEAICAAAKAAAACQgQAAAGIADyFcwHSQAAAAYAAAAU
AAAAFQAAAIMAAgAAAIQAAgAAAKEAIgAAYCBJAQABAAEABgAAAGttAAAAAAAA4D8AAAAAAADgP1BE
MwACAAMAYBAKAM4TPQ7IAAAACwBgEAoAzhM9DsgAAQAMAGAQCgDOEz0OyAABAA0AARACAAAAAhAQ
AAAAAAAAAAAA6L90AdB/sgAzEAAAoAAEAAEAAQBkEAgAAAABAAAAAQAyEAQAAAACADMQAAAHEAwA
AAAAAAAA//8JAE0AChAQAMDAwAAAAAAAAAAAAE4ATQA0EAAAAxAMAAEAAQAcABwAAQAAADMQAABR
EA8AAAIAAAAABwA6AQAAAAEADRA8AAAAHAFPAHYAZQByAGEAbABsACAATABvAHMAcwAgAHcAaQB0
AGgAIABJAFAATABSAD0AMQAuAEUALQAzAFEQEwABAgAACwALADsBAAEAHAABAAEAURATAAICAAAL
AAsAOwEAAQAcAAAAAABREAgAAwEAAAAAAAAGEAgA//8AAAAAAAAzEAAAXxACAAAANBAAAEUQAgAA
ADQQAABEEAQACgAAACQQAgACACUQIAACAgEAAAAAANf///+o////AAAAAAAAAACxAE0AIBAAADMQ
AABPEBQAAgACAAAAAAAAAAAAAAAAAAAAAAAmEAIACwBREAgAAAEAAAAAAAA0EAAAJBACAAMAJRAg
AAICAQAAAAAA1////6j///8AAAAAAAAAALEATQAgEAAAMxAAAE8QFAACAAIAAAAAAAAAAAAAAAAA
AAAAACYQAgANAFEQCAAAAQAAAAAAADQQAABGEAIAAQBBEBIAAAAlAwAAcAEAAHwLAADQBwAAMxAA
AE8QFAACAAIAFwEAAK8AAAA3DgAAsQoAAB0QEgAAAAAAAAAAAAAAAAAAAAAAAAAzEAAAHxAqAAAA
AAAAAAAAAAAAAAAA8L8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD9AU4QAgClAB4QHgACAAMBAAAA
AAAAAAAAAAAAAAAAAAAAAAAjAE0AAAA0EAAAHRASAAEAAAAAAAAAAAAAAAAAAAAAADMQAAAfECoA
AAAAAAAAAAAAAAAAAADwvwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIwC0BHhAeAAIAAwEAAAAAAAAA
AAAAAAAAAAAAAAAAACMATQAAACEQAgABAAcQDAAAAAAAAAD//wkATQA0EAAAJRAgAAICAQAAAAAA
aQcAAGALAAD8AgAAlAEAAIEATQAAAAAAMxAAAE8QFAACAAIAAAAAAAAAAABdAAAAFwAAACYQAgAM
AFEQCAAAAQAAAAAAAA0QHgAAAA0BSQBQAEQAVgAgAFEAdQBhAG4AdABpAGwAZQAnEAYAAwAAAAAA
NBAAACUQIAACAgEAAAAAAFoAAABmAgAAvQAAAOUFAACBAk0AAABaADMQAABPEBQAAgACAAAAAAAA
AAAAFwAAAFYAAAAmEAIADABREAgAAAEAAAAAAAANEB4AAAANAU8AdgBlAHIAYQBsAGwAIAAgAEwA
bwBzAHMAJxAGAAIAAAAAADQQAAA1EAAAMhAEAAAAAwAzEAAABxAMAICAgAAAAAAAAAAXAAoQEADA
wMAAAAAAAAAAAABOAE0ANBAAABQQFAAAAAAAAAAAAAAAAAAAAAAAAAAAADMQAAAbEAYAZAABAAAA
IhAKAAAAAAAAAAAADwAVEBQAjQUAAMYNAACkBgAAlAEAAAABDwAzEAAATxAUAAUAAgCNBQAAxg0A
AAAAAAAAAAAAJRAgAAICAQAAAAAA1////6j///8AAAAAAAAAALEATQAAAAAAMxAAAE8QFAACAAIA
AAAAAAAAAAAAAAAAAAAAAFEQCAAAAQAAAAAAADQQAAAyEAQAAAADADMQAAAHEAwAAAAAAAAA//8J
AE0AChAQAMDAwAAAAAAAAAAAAE4ATQA0EAAANBAAAAYQCAAAAAAA/f8AADMQAABfEAIAAAAHEAwA
AAAAAAAA//8JAE0AChAQAMDAwAAAAAAAAQABAE4ATQALEAIAAABdEAIAAQAJEBQAAAAAAAAAAAAA
AAAATQBNADwAAAA0EAAANBAAADQQAAAlECAAAgIBAAAAAADX////qP///wAAAAAAAAAA8QBNAGCR
AAAzEAAATxAUAAIAAgAAAAAAAAAAAAAAAAAAAAAAURAIAAABAAAAAAAAJxAGAAEAAAAAADQQAAA0
EAAAAAIOAAAAAAAcAAAAAAABAAAAZRACAAIAAwIOAAAAAAAAAJqZmZmZmbk/AwIOAAEAAAAAAArX
o3A9Crc/AwIOAAIAAAAAAHsUrkfherQ/AwIOAAMAAAAAAOxRuB6F67E/AwIOAAQAAAAAALgehetR
uK4/AwIOAAUAAAAAAJqZmZmZmak/AwIOAAYAAAAAAGwUrkfheqQ/AwIOAAcAAAAAAJsehetRuJ4/
AwIOAAgAAAAAAF4UrkfhepQ/AwIOAAkAAAAAAEcUrkfheoQ/AwIOAAoAAAAAADvfT42XboI/AwIO
AAsAAAAAAPyp8dJNYoA/AwIOAAwAAAAAAHnpJjEIrHw/AwIOAA0AAAAAAPp+arx0k3g/AwIOAA4A
AAAAAHsUrkfhenQ/AwIOAA8AAAAAAPyp8dJNYnA/AwIOABAAAAAAABF/arx0k2g/AwIOABEAAAAA
ABOq8dJNYmA/AwIOABIAAAAAACqq8dJNYlA/AwIOABMAAAAAAJLLf0i/fU0/AwIOABQAAAAAAC1D
HOviNko/AwIOABUAAAAAAMe6uI0G8EY/AwIOABYAAAAAAGEyVTAqqUM/AwIOABcAAAAAAPyp8dJN
YkA/AwIOABgAAAAAAC1DHOviNjo/AwIOABkAAAAAAGEyVTAqqTM/AwIOABoAAAAAAC1DHOviNio/
AwIOABsAAAAAAHZDHOviNho/ZRACAAEAAwIOAAAAAAAAAEJg5dAi27k/AwIOAAEAAAAAALKd76fG
S7c/AwIOAAIAAAAAACPb+X5qvLQ/AwIOAAMAAAAAAJQYBFYOLbI/AwIOAAQAAAAAAAisHFpkO68/
AwIOAAUAAAAAAOomMQisHKo/AwIOAAYAAAAAALyhRbbz/aQ/AwIOAAcAAAAAADs5tMh2vp8/AwIO
AAgAAAAAAP4u3SQGgZU/AwIOAAkAAAAAAIZJDAIrh4Y/AwIOAAoAAAAAAHoUrkfheoQ/AwIOAAsA
AAAAADzfT42XboI/AwIOAAwAAAAAAPyp8dJNYoA/AwIOAA0AAAAAAHnpJjEIrHw/AwIOAA4AAAAA
APp+arx0k3g/AwIOAA8AAAAAAHsUrkfhenQ/AwIOABAAAAAAAAiq8dJNYnA/AwIOABEAAAAAABF/
arx0k2g/AwIOABIAAAAAABOq8dJNYmA/AwIOABMAAAAAAMWPMXctIV8/AwIOABQAAAAAAJLLf0i/
fV0/AwIOABUAAAAAAGAHzhlR2ls/AwIOABYAAAAAACxDHOviNlo/AwIOABcAAAAAAPp+arx0k1g/
AwIOABgAAAAAAMe6uI0G8FY/AwIOABkAAAAAAJT2Bl+YTFU/AwIOABoAAAAAAGIyVTAqqVM/AwIO
ABsAAAAAADNuowG8BVI/ZRACAAMAPgIKABsGAAAAADNuowEKAAAACQgQAAAGEADyFcwHSQAAAAYA
AAANAAIAAQAMAAIAZAAPAAIAAQARAAIAAAAQAAgA/Knx0k1iUD9fAAIAAQAqAAIAAAArAAIAAACC
AAIAAQCAAAgAAAAAAAAAAAAlAgQAAAD/AIEAAgDBBBQAAAAVAAAAgwACAAAAhAACAAAATQCOAwAA
SABQACAATABhAHMAZQByAEoAZQB0ACAANQBQAC8ANQBNAFAAIABQAG8AcwB0AFMAYwByAGkAcAB0
AAAAAAAAAAAEAwTUALgCH2cAAAEAAQDqCm8IZAABAAcAWAIBAAEAWAIDAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAA
AMASAADIGQAAAQAAAAAAAAABAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAA0r1677/GvUEhaAQABAAEA
AAAAAAEAAAAAAAIAAgABAFIDAADCAQAAAAAAAAAAZAAAAAAAAAD//wAA//8AAP//AAD//wAA//8A
AP//AAD//wAA//8AAP//AAD//wAA//8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP//Q3VzdG9tIHBhZ2UgMQAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAWEMAALRDAAAA
AAAAQ3VzdG9tIHBhZ2UgMgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAWEMAALRDAAAAAAAAQ3VzdG9tIHBhZ2UgMwAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAWEMAALRDAAAAAAAAAAAAAAAAAAChACIA
AQBkAAEAAQABAAIAWAJYAgAAAAAAAOA/AAAAAAAA4D8BAFUAAgAIAH0ADAAAAAAASRIPAAIAAgAA
Ag4AAQAAABkAAAAAAAcAAAAIAhAAAQAAAAcA/wAAAFQwgAEVAAgCEAACAAAABwD/AAAAYgAAAQMA
CAIQAAMAAAAHAP8AAAAAAAABYgAIAhAABAAAAAcA/wAAAACDAAFiAAgCEAAFAAAABwD/AAAAwYEA
AQKDCAIQAAYAAAAHAP8AAAAAAAABAAAIAhAABwAAAAcA/wAAAAAAAAEAAAgCEAAIAAAABwD/AAAA
YgAAAQIACAIQAAkAAAAHAP8AAAAAAAABYgAIAhAACgAAAAcA/wAAAAAAAAFUAAgCEAALAAAABwD/
AAAAYgAAAQGDCAIQAAwAAAAHAP8AAAAAgwABAAAIAhAADQAAAAcA/wAAAAAAAAFiAAgCEAAOAAAA
BwD/AAAAAoMAAQAACAIQAA8AAAAHAP8AAAAAAAABAoMIAhAAEAAAAAcA/wAAAAKDAAECgwgCEAAR
AAAABwD/AAAAAAAAAWIACAIQABIAAAAHAP8AAAAQMAABYgAIAhAAEwAAAAcA/wAAAAcCAAEIAAgC
EAAUAAAABwD/AAAAEDAAAQAACAIQABUAAAAHAP8AAAAIMAABAAAIAhAAFgAAAAcA/wAAAAgwAAEA
AAgCEAAXAAAABwD/AAAABwIAAQAACAIQABgAAAAHAP8AAADZAYABFQAEAhAAAQAAABYABwAARWxl
bWVudL4ACgABAAEAFgAWAAIABAIRAAEAAwAWAAgAAEF2ZSBJUERUvgAKAAEABAAWABYABQAEAhEA
AQAGABYACAAATWF4IElQRFYEAhEAAgAAABcACAAARGlzdGFuY2V+AgoAAgABABcAAPyvQAQCCwAC
AAIAFwACAABrbb4ADgACAAMAGQAXABcAFwAGAAQCDgADAAAAFwAFAABSb3V0ZQYAJQADAAEAFwAA
AAAAgP2zQAAAZQDg/Q8ARAIAAcAfAAAAAAAA9D8FBAILAAMAAgAXAAIAAGttBgAjAAMAAwAZAGZm
ZmZmljlAAAAMAAb/DQBEAwABwB4FAAUe6AMGvgAMAAMABAAXABcAFwAGAL4AFAAEAAAAFwAXABcA
GQAXABcAFwAGAAQCFwAFAAAAFwAOAABJbnNlcnRpb24gVGltZX4CCgAFAAEAFwAAAGlABAIOAAUA
AgAXAAUAAGJ5dGVzBgAjAAUAAwAZAG+s/kCPlPA/AAAYAAP/DQBEBQABwB4IAAUeCAYGfgIKAAUA
BAAXAABwl0AEAg4ABQAFABcABQAAYnl0ZXMGACMABQAGABkAUYPdmYwWH0AAAAMAA/4NAEQFAATA
HggABR4IBga+ABQABgAAABcAFwAXABkAFwAXABcABgAEAhUABwAAABcADAAATm9uIElQIE5ldCAx
vgAKAAcAAQAXABcAAgB+AgoABwADABkAAAAuQL4ACgAHAAQAFwAXAAUAfgIKAAcABgAXAAAAAAC+
ABQACAAAABcAFwAXABkAFwAXABcABgAEAhEACQAAABcACAAASVAgTmV0IDEEAgoACQABABcAAQAA
TgQCEgAJAAIAFwAJAABJUERUIGVhY2i+AAoACQADABkAFwAEAAQCEQAJAAUAFwAIAABWYXIgZWFj
aAECBgAJAAYAFwAEAhMACgAAABcACgAAQWNjZXNzLCBOQb0AEgAKAAEAFwAAAPA/FwAAACRAAgAG
ACEACgADABkAAAAAAAAAJEAAAAMAAf8LAEQKAAHARAoAAsAFAQIGAAoABAAXAH4CCgAKAAUAFwAA
ADBABgAhAAoABgAXAAAAAAAAADBAAAANAAP/CwBECgABwEQKAAXABQQCGQALAAAAFwAQAABEaXN0
cmlidXRpb24sIE5EvQASAAsAAQAXAAAA8D8XAAAACEACAAYAIQALAAMAGQAAAAAAAAAIQAAACgAD
/wsARAsAAcBECwACwAUBAgYACwAEABcAfgIKAAsABQAXAAAACEAGACEACwAGABcAAAAAAAAACEAA
AAoABv8LAEQLAAHARAsABcAFBAIRAAwAAAAXAAgAAENvcmUsIE5DvQASAAwAAQAXAAAAAEAXAAAA
AEACAAYAIQAMAAMAGQAAAAAAAAAQQAAABQAD/wsARAwAAcBEDAACwAUBAgYADAAEABcAfgIKAAwA
BQAXAAAACEAGACEADAAGABcAAAAAAAAAGEAAABgABv8LAEQMAAHARAwABcAFBAIcAA0AAAAXABMA
AEludGVybmV0d29yayBHVywgTkm9ABIADQABABcAAADwPxcAAAAIQAIABgAhAA0AAwAZAAAAAAAA
AAhAAAALAAP/CwBEDQABwEQNAALABQECBgANAAQAFwB+AgoADQAFABcAAAAIQAYAIQANAAYAFwAA
AAAAAAAIQAAACwAG/wsARA0AAcBEDQAFwAW+ABQADgAAABcAFwAXABkAFwAXABcABgAEAhEADwAA
ABcACAAASVAgTmV0IDIEAgoADwABABcAAQAATgQCEgAPAAIAFwAJAABJUERUIGVhY2i+AAoADwAD
ABkAFwAEAAQCEQAPAAUAFwAIAABWYXIgZWFjaAECBgAPAAYAFwAEAhMAEAAAABcACgAAQWNjZXNz
LCBOQb0AEgAQAAEAFwAAAPA/FwAAACRAAgAGACEAEAADABkAAAAAAAAAJEAAAA0ABv8LAEQQAAHA
RBAAAsAFAQIGABAABAAXAH4CCgAQAAUAFwAAADBABgAhABAABgAXAAAAAAAAADBAAAAQAAP/CwBE
EAABwEQQAAXABQQCGQARAAAAFwAQAABEaXN0cmlidXRpb24sIE5EvQASABEAAQAXAAAA8D8XAAAA
CEACAAYAIQARAAMAGQAAAAAAAAAIQAAAEAAG/wsARBEAAcBEEQACwAUBAgYAEQAEABcAfgIKABEA
BQAXAAAACEAGACEAEQAGABcAAAAAAAAACEAAABEAA/8LAEQRAAHARBEABcAFBAIRABIAAAAXAAgA
AENvcmUsIE5DvQASABIAAQAXAAAAEEAXAAAAAEACAAYAIQASAAMAGQAAAAAAAAAgQAAAEQAG/wsA
RBIAAcBEEgACwAUBAgYAEgAEABcAfgIKABIABQAXAAAACEAGACEAEgAGABcAAAAAAAAAKEAAABIA
A/8LAEQSAAHARBIABcAFBAIcABMAAAAXABMAAEludGVybmV0d29yayBHVywgTkm9ABIAEwABABcA
AADwPxcAAAAIQAIABgAhABMAAwAZAAAAAAAAAAhAAAASAAb/CwBEEwABwEQTAALABQECBgATAAQA
FwB+AgoAEwAFABcAAAAIQAYAIQATAAYAFwAAAAAAAAAIQAAAEwAD/wsARBMAAcBEEwAFwAW+ABQA
FAAAABcAFwAXABkAFwAXABcABgAEAhUAFQAAABcADAAATm9uIElQIE5ldCAyvgAKABUAAQAXABcA
AgB+AgoAFQADABkAAAAuQL4ACgAVAAQAFwAXAAUAfgIKABUABgAXAAAAAAC+ABQAFgAAABcAFwAX
ABkAFwAXABcABgC+ABQAFwAAABcAFwAXABkAFwAXABcABgAEAhIAGAAAABYACQAAVG90YWwsIG1z
vgAKABgAAQAWABYAAgAGACMAGAADABoAS5Sd1usnWUAAABMABv8NACUDABUAA8ADwBkQAQC+AAoA
GAAEABYAFgAFAAYAIwAYAAYAFgAAAAAAAABPQAAADAAD/w0AJQcAFQAGwAbAGRABANcANADQCgAA
zAFaAEQAgQAYAKkAGABRABgAZgCPAJUAjQCYABgAZgCPAJUAjQCYABgAUQAYABgAPgISALYAAAAA
AEAAAAAAAAAAAAAAAB0ADwADBQAEAAAAAQAFAAUABAYKAAAACQgQAAAGEADyFcwHSQAAAAYAAAAN
AAIAAQAMAAIAZAAPAAIAAQARAAIAAAAQAAgA/Knx0k1iUD9fAAIAAQAqAAIAAAArAAIAAACCAAIA
AQCAAAgAAAAAAAAAAAAlAgQAAAD/AIEAAgDBBBQAAAAVAAAAgwACAAAAhAACAAAATQCOAwAASABQ
ACAATABhAHMAZQByAEoAZQB0ACAANQBQAC8ANQBNAFAAIABQAG8AcwB0AFMAYwByAGkAcAB0AAAA
AAAAAAAEAwTUALgCH2cAAAEAAQDqCm8IZAABAAcAWAIBAAEAWAIDAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAMAS
AADIGQAAAQAAAAAAAAABAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAA0r1677/GvUEhaAQABAAEAAAAA
AAEAAAAAAAIAAgABAFIDAADCAQAAAAAAAAAAZAAAAAAAAAD//wAA//8AAP//AAD//wAA//8AAP//
AAD//wAA//8AAP//AAD//wAA//8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP//Q3VzdG9tIHBhZ2UgMQAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAWEMAALRDAAAAAAAA
Q3VzdG9tIHBhZ2UgMgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAWEMAALRDAAAAAAAAQ3VzdG9tIHBhZ2UgMwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAWEMAALRDAAAAAAAAAAAAAAAAAAChACIAAQBk
AAEAAQABAAIAWAJYAgAAAAAAAOA/AAAAAAAA4D8BAFUAAgAIAH0ADAAAAAAASRIYAAIAAgB9AAwA
AQABACQJGAAAAAIAfQAMAAIAAgBtGxgAAgACAH0ADAADAAABJAkYAAAAAgAAAg4AAQAAAAsAAAAA
AAMAAAAIAhAAAQAAAAMA/wAAAFQwAAESAAgCEAACAAAAAwD/AAAAYgAAAQMACAIQAAMAAAADAP8A
AAAAAAABYgAIAhAABAAAAAMA/wAAAACDAAFiAAgCEAAFAAAAAwD/AAAAwYEAAQKDCAIQAAYAAAAD
AP8AAAAAAAABAAAIAhAACQAAAAMA/wAAAAAAAAEAAAgCEAAKAAAAAwD/AAAAYgAAAQIAAQIGAAEA
AAAXAAQCEgABAAEAFwAJAABEZWxheSwgbXMEAg4AAQACABcABQAATm90ZXMEAhkAAgAAABcAEAAA
UGFja2V0IEZvcm1hdGlvbn4CCgACAAEAFwAAAERABAItAAIAAgAXACQAADIgdGltZXMgZnJhbWUg
c2l6ZSBwbHVzIDAgbG9vay1haGVhZAQCGgADAAAAFwARAABKaXR0ZXIgQnVmZmVyLGF2ZX4CCgAD
AAEAFwAAAD5ABAIeAAMAAgAXABUAAGNlbnRlciBvZiA2MG1zIGJ1ZmZlcgQCHAAEAAAAFwATAABQ
YWNrZXQgTG9zcyBDb25jZWFsfgIKAAQAAQAXAAAAJEAEAhgABAACABcADwAAb25lIFBMQyAiZnJh
bWUivgAMAAUAAAAXABcAFwACAAQCEgAGAAAAFwAJAABUb3RhbCwgbXMGACMABgABABcAAAAAAAAA
VEAAAG1zZv0NACUCAAQAAcABwBkQAQABAgYABgACABcABAIbAAkAAAAYABIAAEVuZHBvaW50ICsg
SVBEVCxtcwYAIwAJAAEAGAAmyk7r9ZNmQAAABgAB/g0ARAYAAcBaAAAYAAPAAwECBgAJAAIAGAAE
AhkACgAAABgAEAAAKFIgaXMgYXBwcm94IDg3Kb4ACgAKAAEAGAAYAAIA1wAUAJgCAACMADIAXABO
AEoAEABHAFAAPgISALYAAAAAAEAAAAAAAAAAAAAAAB0ADwADAQAAAAAAAQABAAYAAAIKAAAACQgQ
AAAGEADyFcwHSQAAAAYAAAANAAIAAQAMAAIAZAAPAAIAAQARAAIAAAAQAAgA/Knx0k1iUD9fAAIA
AQAqAAIAAAArAAIAAACCAAIAAQCAAAgAAAAAAAAAAAAlAgQAAAD/AIEAAgDBBBQAAAAVAAAAgwAC
AAAAhAACAAAATQCOAwAASABQACAATABhAHMAZQByAEoAZQB0ACAANQBQAC8ANQBNAFAAIABQAG8A
cwB0AFMAYwByAGkAcAB0AAAAAAAAAAAEAwTUALgCH2cAAAEAAQDqCm8IZAABAAcAWAIBAAEAWAID
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAACAAAAMASAADIGQAAAQAAAAAAAAABAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAA0
r1677/GvUEhaAQABAAEAAAAAAAEAAAAAAAIAAgABAFIDAADCAQAAAAAAAAAAZAAAAAAAAAD//wAA
//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP//Q3Vz
dG9tIHBhZ2UgMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAWEMAALRDAAAAAAAAQ3VzdG9tIHBhZ2UgMgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAWEMAALRDAAAAAAAAQ3VzdG9tIHBhZ2UgMwAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAWEMAALRDAAAA
AAAAAAAAAAAAAAChACIAAQBkAAEAAQABAAIAWAJYAgAAAAAAAOA/AAAAAAAA4D8BAFUAAgAIAH0A
DAAAAAAASRIPAAIAAgAAAg4AAQAAABkAAAAAAAcAAAAIAhAAAQAAAAcA/wAAAFQwgAEVAAgCEAAC
AAAABwD/AAAAYgAAAQMACAIQAAMAAAAHAP8AAAAAAAABYgAIAhAABAAAAAcA/wAAAACDAAFiAAgC
EAAFAAAABwD/AAAAwYEAAQKDCAIQAAYAAAAHAP8AAAAAAAABAAAIAhAABwAAAAcA/wAAAAAAAAEA
AAgCEAAIAAAABwD/AAAAYgAAAQIACAIQAAkAAAAHAP8AAAAAAAABYgAIAhAACgAAAAcA/wAAAAAA
AAFUAAgCEAALAAAABwD/AAAAYgAAAQGDCAIQAAwAAAAHAP8AAAAAgwABAAAIAhAADQAAAAcA/wAA
AAAAAAFiAAgCEAAOAAAABwD/AAAAAoMAAQAACAIQAA8AAAAHAP8AAAAAAAABAoMIAhAAEAAAAAcA
/wAAAAKDAAECgwgCEAARAAAABwD/AAAAAAAAAWIACAIQABIAAAAHAP8AAAAQMAABYgAIAhAAEwAA
AAcA/wAAAAGDAAECgwgCEAAUAAAABwD/AAAAYgAAAfBFCAIQABUAAAAHAP8AAAD//wABYgAIAhAA
FgAAAAcA/wAAAAKDAAFiAAgCEAAXAAAABwD/AAAA8GUAAQAACAIQABgAAAAHAP8AAADZAYABFQAE
AhAAAQAAABYABwAARWxlbWVudL4ACgABAAEAFgAWAAIABAIRAAEAAwAWAAgAAEF2ZSBJUERUvgAK
AAEABAAWABYABQAEAhEAAQAGABYACAAATWF4IElQRFYEAhEAAgAAABcACAAARGlzdGFuY2V+AgoA
AgABABcAAHDHQAQCCwACAAIAFwACAABrbb4ADgACAAMAGQAXABcAFwAGAAQCDgADAAAAFwAFAABS
b3V0ZQYAJQADAAEAFwAAAAAAAEzNQAAAAwAD/w8ARAIAAcAfAAAAAAAA9D8FBAILAAMAAgAXAAIA
AGttBgAjAAMAAwAZAAAAAAAAwFJAAAAMAAb/DQBEAwABwB4FAAUe6AMGvgAMAAMABAAXABcAFwAG
AL4AFAAEAAAAFwAXABcAGQAXABcAFwAGAAQCFwAFAAAAFwAOAABJbnNlcnRpb24gVGltZX4CCgAF
AAEAFwAAAGlABAIOAAUAAgAXAAUAAGJ5dGVzBgAjAAUAAwAZAG+s/kCPlPA/AAAYAAP/DQBEBQAB
wB4IAAUeCAYGfgIKAAUABAAXAABwl0AEAg4ABQAFABcABQAAYnl0ZXMGACMABQAGABkAUYPdmYwW
H0AAAAMAAf4NAEQFAATAHggABR4IBga+ABQABgAAABcAFwAXABkAFwAXABcABgAEAhUABwAAABcA
DAAATm9uIElQIE5ldCAxvgAKAAcAAQAXABcAAgB+AgoABwADABkAAAAuQL4ACgAHAAQAFwAXAAUA
fgIKAAcABgAXAAAAAAC+ABQACAAAABcAFwAXABkAFwAXABcABgAEAhEACQAAABcACAAASVAgTmV0
IDEEAgoACQABABcAAQAATgQCEgAJAAIAFwAJAABJUERUIGVhY2i+AAoACQADABkAFwAEAAQCEQAJ
AAUAFwAIAABWYXIgZWFjaAECBgAJAAYAFwAEAhMACgAAABcACgAAQWNjZXNzLCBOQb0AEgAKAAEA
FwAAAPA/FwAAACRAAgAGACEACgADABkAAAAAAAAAJEAAAAoAA/0LAEQKAAHARAoAAsAFAQIGAAoA
BAAXAH4CCgAKAAUAFwAAADBABgAhAAoABgAXAAAAAAAAADBAAAANAAP/CwBECgABwEQKAAXABQQC
GQALAAAAFwAQAABEaXN0cmlidXRpb24sIE5EvQASAAsAAQAXAAAA8D8XAAAACEACAAYAIQALAAMA
GQAAAAAAAAAIQAAACgAD/wsARAsAAcBECwACwAUBAgYACwAEABcAfgIKAAsABQAXAAAACEAGACEA
CwAGABcAAAAAAAAACEAAAAoABv8LAEQLAAHARAsABcAFBAIRAAwAAAAXAAgAAENvcmUsIE5DvQAS
AAwAAQAXAAAAAEAXAAAAAEACAAYAIQAMAAMAGQAAAAAAAAAQQAAABQAD/wsARAwAAcBEDAACwAUB
AgYADAAEABcAfgIKAAwABQAXAAAACEAGACEADAAGABcAAAAAAAAAGEAAABgABv8LAEQMAAHARAwA
BcAFBAIcAA0AAAAXABMAAEludGVybmV0d29yayBHVywgTkm9ABIADQABABcAAADwPxcAAAAIQAIA
BgAhAA0AAwAZAAAAAAAAAAhAAAALAAP/CwBEDQABwEQNAALABQECBgANAAQAFwB+AgoADQAFABcA
AAAIQAYAIQANAAYAFwAAAAAAAAAIQAAACwAG/wsARA0AAcBEDQAFwAW+ABQADgAAABcAFwAXABkA
FwAXABcABgAEAhEADwAAABcACAAASVAgTmV0IDIEAgoADwABABcAAQAATgQCEgAPAAIAFwAJAABJ
UERUIGVhY2i+AAoADwADABkAFwAEAAQCEQAPAAUAFwAIAABWYXIgZWFjaAECBgAPAAYAFwAEAhMA
EAAAABcACgAAQWNjZXNzLCBOQb0AEgAQAAEAFwAAAPA/FwAAACRAAgAGACEAEAADABkAAAAAAAAA
JEAAAA0ABv8LAEQQAAHARBAAAsAFAQIGABAABAAXAH4CCgAQAAUAFwAAADBABgAhABAABgAXAAAA
AAAAADBAAAAQAAP/CwBEEAABwEQQAAXABQQCGQARAAAAFwAQAABEaXN0cmlidXRpb24sIE5EvQAS
ABEAAQAXAAAA8D8XAAAACEACAAYAIQARAAMAGQAAAAAAAAAIQAAAEAAG/wsARBEAAcBEEQACwAUB
AgYAEQAEABcAfgIKABEABQAXAAAACEAGACEAEQAGABcAAAAAAAAACEAAABEAA/8LAEQRAAHARBEA
BcAFBAIRABIAAAAXAAgAAENvcmUsIE5DvQASABIAAQAXAAAAEEAXAAAAAEACAAYAIQASAAMAGQAA
AAAAAAAgQAAAEQAG/wsARBIAAcBEEgACwAUBAgYAEgAEABcAfgIKABIABQAXAAAACEAGACEAEgAG
ABcAAAAAAAAAKEAAABIAA/8LAEQSAAHARBIABcAFBAIcABMAAAAXABMAAEludGVybmV0d29yayBH
VywgTkm9ABIAEwABABcAAADwPxcAAAAIQAIABgAhABMAAwAZAAAAAAAAAAhAAAASAAb/CwBEEwAB
wEQTAALABQECBgATAAQAFwB+AgoAEwAFABcAAAAIQAYAIQATAAYAFwAAAAAAAAAIQAAAEwAD/wsA
RBMAAcBEEwAFwAW+ABQAFAAAABcAFwAXABkAFwAXABcABgAEAhUAFQAAABcADAAATm9uIElQIE5l
dCAyvgAKABUAAQAXABcAAgB+AgoAFQADABkAAAAuQL4ACgAVAAQAFwAXAAUAfgIKABUABgAXAAAA
AAC+ABQAFgAAABcAFwAXABkAFwAXABcABgC+ABQAFwAAABcAFwAXABkAFwAXABcABgAEAhIAGAAA
ABYACQAAVG90YWwsIG1zvgAKABgAAQAWABYAAgAGACMAGAADABoAWf2BHinBYkAAABMABv8NACUD
ABUAA8ADwBkQAQC+AAoAGAAEABYAFgAFAAYAIwAYAAYAFgAAAAAAAABPQAAADAAD/w0AJQcAFQAG
wAbAGRABANcANADQCgAAzAFaAEQAgQAYAKkAGABRABgAZgCPAJUAjQCYABgAZgCPAJUAjQCYABgA
UQAYABgAPgISALYAAAAAAEAAAAAAAAAAAAAAAB0ADwADAwABAAAAAQADAAMAAQEKAAAACQgQAAAG
EADyFcwHSQAAAAYAAAANAAIAAQAMAAIAZAAPAAIAAQARAAIAAAAQAAgA/Knx0k1iUD9fAAIAAQAq
AAIAAAArAAIAAACCAAIAAQCAAAgAAAAAAAAAAAAlAgQAAAD/AIEAAgDBBBQAAAAVAAAAgwACAAAA
hAACAAAATQCOAwAASABQACAATABKACAAOAAxADAAMAAgAFMAZQByAGkAZQBzACAAUABTAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAEAwTUALgCH3cAAAEAAQDqCm8IZAABAAcAWAIBAAIAWAIDAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAACAAAAMASAADIGQAAAQAAAAAAAAABAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAF+hGT
djf6sBo+GwABAAEAAAAAAAEAAAAAAAIAAgABACQEAADCAQAAAAAAAAAAZAAAAAAAAAD//wAA//8B
AP//AAD//wEA//8AAP//AAD//wAA//8BAP//AQD//wAA//8BAP//AQD//wAA//8AAP//AAD//wAA
//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AgD//wIA//8DAP//AQD//wAA//8AAP//AAD/
/wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP//Q3VzdG9t
IHBhZ2UgMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAi0MAQAdEAAAAAAAAQ3VzdG9tIHBhZ2UgMgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAi0MAQAdEAAAAAAAAQ3VzdG9tIHBhZ2UgMwAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAi0MAQAdEAAAAAAAA
AAAAAAAAAAChACIAAQBkAAEAAQABAAIAWAJYAgAAAAAAAOA/AAAAAAAA4D8BAFUAAgAIAH0ADAAA
AAAASRIPAAIAAgAAAg4AAQAAAB4AAAAAAAcAAAAIAhAAAQAAAAcA/wAAAFQwgAEVAAgCEAACAAAA
BwD/AAAAYgAAAQMACAIQAAMAAAAHAP8AAAAAAAABYgAIAhAABAAAAAcA/wAAAACDAAFiAAgCEAAF
AAAABwD/AAAAwYEAAQKDCAIQAAYAAAAHAP8AAAAAAAABAAAIAhAABwAAAAcA/wAAAAAAAAEAAAgC
EAAIAAAABwD/AAAAYgAAAQIACAIQAAkAAAAHAP8AAAAAAAABYgAIAhAACgAAAAcA/wAAAAAAAAFU
AAgCEAALAAAABwD/AAAAYgAAAQGDCAIQAAwAAAAHAP8AAAAAgwABAAAIAhAADQAAAAcA/wAAAAAA
AAFiAAgCEAAOAAAABwD/AAAAAoMAAQAACAIQAA8AAAAHAP8AAAAAAAABAoMIAhAAEAAAAAcA/wAA
AAKDAAECgwgCEAARAAAABwD/AAAAAAAAAWIACAIQABIAAAAHAP8AAAAQMAABYgAIAhAAEwAAAAcA
/wAAAAGDAAECgwgCEAAUAAAABwD/AAAAYgAAAfBFCAIQABUAAAAHAP8AAAD//wABYgAIAhAAFgAA
AAcA/wAAAAKDAAFiAAgCEAAXAAAABwD/AAAA8GUAAQAACAIQABgAAAAHAP8AAADZAQABAAAIAhAA
GQAAAAcA/wAAAAAAAAHwRQgCEAAaAAAABwD/AAAAAYMAAQAACAIQABsAAAAHAP8AAAD8ggABAAAI
AhAAHAAAAAcA/wAAAFQwAAFUAAgCEAAdAAAABwD/AAAAAoOAARWABAIQAAEAAAAWAAcAAEVsZW1l
bnS+AAoAAQABABYAFgACAAQCEQABAAMAFgAIAABBdmUgSVBEVL4ACgABAAQAFgAWAAUABAIRAAEA
BgAWAAgAAE1heCBJUERWBAIRAAIAAAAXAAgAAERpc3RhbmNlfgIKAAIAAQAXAADb2kAEAgsAAgAC
ABcAAgAAa22+AA4AAgADABkAFwAXABcABgAEAg4AAwAAABcABQAAUm91dGV+AgoAAwABABcAANva
QAQCCwADAAIAFwACAABrbQYAIwADAAMAGQAAAAAAADBhQAAADAAG/w0ARAMAAcAeBQAFHugDBr4A
DAADAAQAFwAXABcABgC+ABQABAAAABcAFwAXABkAFwAXABcABgAEAhcABQAAABcADgAASW5zZXJ0
aW9uIFRpbWV+AgoABQABABcAAABpQAQCDgAFAAIAFwAFAABieXRlcwYAIwAFAAMAGQBvrP5Aj5Tw
PwAAHQAD/w0ARAUAAcAeCAAFHggGBn4CCgAFAAQAFwAAcJdABAIOAAUABQAXAAUAAGJ5dGVzBgAj
AAUABgAZAFGD3ZmMFh9AAAASAAb+DQBEBQAEwB4IAAUeCAYGvgAUAAYAAAAXABcAFwAZABcAFwAX
AAYABAIVAAcAAAAXAAwAAE5vbiBJUCBOZXQgMb4ACgAHAAEAFwAXAAIAfgIKAAcAAwAZAAAALkC+
AAoABwAEABcAFwAFAH4CCgAHAAYAFwAAAAAAvgAUAAgAAAAXABcAFwAZABcAFwAXAAYABAIRAAkA
AAAXAAgAAElQIE5ldCAxBAIKAAkAAQAXAAEAAE4EAhIACQACABcACQAASVBEVCBlYWNovgAKAAkA
AwAZABcABAAEAhEACQAFABcACAAAVmFyIGVhY2gBAgYACQAGABcABAITAAoAAAAXAAoAAEFjY2Vz
cywgTkG9ABIACgABABcAAADwPxcAAAAkQAIABgAhAAoAAwAZAAAAAAAAACRAAAAKAAP9CwBECgAB
wEQKAALABQECBgAKAAQAFwB+AgoACgAFABcAAAAwQAYAIQAKAAYAFwAAAAAAAAAwQAAADQAD/wsA
RAoAAcBECgAFwAUEAhkACwAAABcAEAAARGlzdHJpYnV0aW9uLCBORL0AEgALAAEAFwAAAPA/FwAA
AAhAAgAGACEACwADABkAAAAAAAAACEAAAAoAA/8LAEQLAAHARAsAAsAFAQIGAAsABAAXAH4CCgAL
AAUAFwAAAAhABgAhAAsABgAXAAAAAAAAAAhAAAAKAAb/CwBECwABwEQLAAXABQQCEQAMAAAAFwAI
AABDb3JlLCBOQ70AEgAMAAEAFwAAAABAFwAAAABAAgAGACEADAADABkAAAAAAAAAEEAAAAUAA/8L
AEQMAAHARAwAAsAFAQIGAAwABAAXAH4CCgAMAAUAFwAAAAhABgAhAAwABgAXAAAAAAAAABhAAAAd
AAb/CwBEDAABwEQMAAXABQQCHAANAAAAFwATAABJbnRlcm5ldHdvcmsgR1csIE5JvQASAA0AAQAX
AAAA8D8XAAAACEACAAYAIQANAAMAGQAAAAAAAAAIQAAACwAD/wsARA0AAcBEDQACwAUBAgYADQAE
ABcAfgIKAA0ABQAXAAAACEAGACEADQAGABcAAAAAAAAACEAAAAsABv8LAEQNAAHARA0ABcAFvgAU
AA4AAAAXABcAFwAZABcAFwAXAAYABAIRAA8AAAAXAAgAAElQIE5ldCAyBAIKAA8AAQAXAAEAAE4E
AhIADwACABcACQAASVBEVCBlYWNovgAKAA8AAwAZABcABAAEAhEADwAFABcACAAAVmFyIGVhY2gB
AgYADwAGABcABAIZABAAAAAXABAAAERpc3RyaWJ1dGlvbiwgTkS9ABIAEAABABcAAAAAQBcAAAAI
QAIABgAhABAAAwAZAAAAAAAAABhAAAADAAP/CwBEEAABwEQQAALABQECBgAQAAQAFwB+AgoAEAAF
ABcAAAAIQAYAIQAQAAYAFwAAAAAAAAAYQAAAEAAD/wsARBAAAcBEEAAFwAUEAhEAEQAAABcACAAA
Q29yZSwgTkO9ABIAEQABABcAAAAQQBcAAAAAQAIABgAhABEAAwAZAAAAAAAAACBAAAAQAAb/CwBE
EQABwEQRAALABQECBgARAAQAFwB+AgoAEQAFABcAAAAIQAYAIQARAAYAFwAAAAAAAAAoQAAAEQAD
/wsARBEAAcBEEQAFwAUEAhwAEgAAABcAEwAASW50ZXJuZXR3b3JrIEdXLCBOSb0AEgASAAEAFwAA
AABAFwAAAAhAAgAGACEAEgADABkAAAAAAAAAGEAAABEABv8LAEQSAAHARBIAAsAFAQIGABIABAAX
AH4CCgASAAUAFwAAAAhABgAhABIABgAXAAAAAAAAABhAAAASAAP/CwBEEgABwEQSAAXABb4AFAAT
AAAAFwAXABcAGQAXABcAFwAGAAQCEQAUAAAAFwAIAABJUCBOZXQgMwQCCgAUAAEAFwABAABOBAIS
ABQAAgAXAAkAAElQRFQgZWFjaL4ACgAUAAMAGQAXAAQABAIRABQABQAXAAgAAFZhciBlYWNoAQIG
ABQABgAXAAQCEwAVAAAAFwAKAABBY2Nlc3MsIE5BvQASABUAAQAXAAAA8D8XAAAAJEACAAYAIQAV
AAMAGQAAAAAAAAAkQAAADQAG/wsARBUAAcBEFQACwAUBAgYAFQAEABcAfgIKABUABQAXAAAAMEAG
ACEAFQAGABcAAAAAAAAAMEAAABUAA/8LAEQVAAHARBUABcAFBAIZABYAAAAXABAAAERpc3RyaWJ1
dGlvbiwgTkS9ABIAFgABABcAAADwPxcAAAAIQAIABgAhABYAAwAZAAAAAAAAAAhAAAAVAAb/CwBE
FgABwEQWAALABQECBgAWAAQAFwB+AgoAFgAFABcAAAAIQAYAIQAWAAYAFwAAAAAAAAAIQAAAFgAD
/wsARBYAAcBEFgAFwAUEAhEAFwAAABcACAAAQ29yZSwgTkO9ABIAFwABABcAAAAQQBcAAAAAQAIA
BgAhABcAAwAZAAAAAAAAACBAAAAWAAb/CwBEFwABwEQXAALABQECBgAXAAQAFwB+AgoAFwAFABcA
AAAIQAYAIQAXAAYAFwAAAAAAAAAoQAAAFwAD/wsARBcAAcBEFwAFwAUEAhwAGAAAABcAEwAASW50
ZXJuZXR3b3JrIEdXLCBOSb0AEgAYAAEAFwAAAPA/FwAAAAhAAgAGACEAGAADABkAAAAAAAAACEAA
ABcABv8LAEQYAAHARBgAAsAFAQIGABgABAAXAH4CCgAYAAUAFwAAAAhABgAhABgABgAXAAAAAAAA
AAhAAAAYAAP/CwBEGAABwEQYAAXABb4AFAAZAAAAFwAXABcAGQAXABcAFwAGAAQCFQAaAAAAFwAM
AABOb24gSVAgTmV0IDK+AAoAGgABABcAFwACAH4CCgAaAAMAGQAAAC5AvgAKABoABAAXABcABQB+
AgoAGgAGABcAAAAAAL4AFAAbAAAAFwAXABcAGQAXABcAFwAGAL4AFAAcAAAAFwAXABcAGQAXABcA
FwAGAAQCEgAdAAAAFgAJAABUb3RhbCwgbXO+AAoAHQABABYAFgACAAYAIwAdAAMAGgBZ/YEeKRFt
QAAAGAAG/w0AJQMAGgADwAPAGRABAL4ACgAdAAQAFgAWAAUABgAjAB0ABgAWAAAAAAAAgFVAAAAM
AAP/DQAlBwAaAAbABsAZEAEA1wA+AFENAAAwAloARABmABgAqQAYAFEAGABmAI8AlQCNAJgAGABm
AJUAjQCYABgAZgCPAJUAjQCYABgAUQAYABgAPgISALYAAQAAAEAAAAAAAAAAAAAAAB0ADwADBAAB
AAAAAQAEAAQAAQEKAAAACQgQAAAGEADyFcwHSQAAAAYAAAANAAIAAQAMAAIAZAAPAAIAAQARAAIA
AAAQAAgA/Knx0k1iUD9fAAIAAQAqAAIAAAArAAIAAACCAAIAAQCAAAgAAAAAAAAAAAAlAgQAAAD/
AIEAAgDBBBQAAAAVAAAAgwACAAAAhAACAAAAoQAiAAAA/wABAAEAAQAEAAABAQEAAAAAAADgPwAA
AAAAAOA/wAZVAAIACAAAAg4AAAAAAB0AAAAAAAMAAAAIAhAAAAAAAAMA/wAAAFQwAAESAAgCEAAB
AAAAAwD/AAAAYgAAAQMACAIQAAIAAAADAP8AAAAAAAABYgAIAhAAAwAAAAMA/wAAAACDAAFiAAgC
EAAEAAAAAwD/AAAAwYEAAQKDCAIQAAUAAAADAP8AAAAAAAABAAAIAhAABgAAAAMA/wAAAAAAAAEA
AAgCEAAHAAAAAwD/AAAAYgAAAQIACAIQAAgAAAADAP8AAAAAAAABYgAIAhAACQAAAAMA/wAAAAAA
AAFUAAgCEAAKAAAAAwD/AAAAYgAAAQGDCAIQAAsAAAADAP8AAAAAgwABAAAIAhAADAAAAAMA/wAA
AAAAAAFiAAgCEAANAAAAAwD/AAAAAoMAAQAACAIQAA4AAAADAP8AAAAAAAABAoMIAhAADwAAAAMA
/wAAAAKDAAECgwgCEAAQAAAAAwD/AAAAAAAAAWIACAIQABEAAAADAP8AAAAQMAABYgAIAhAAEgAA
AAMA/wAAAAGDAAECgwgCEAATAAAAAwD/AAAAYgAAAfBFCAIQABQAAAADAP8AAAD//wABYgAIAhAA
FQAAAAMA/wAAAAKDAAFiAAgCEAAWAAAAAwD/AAAA8GUAAQAACAIQABcAAAADAP8AAADZAQABAAAI
AhAAGAAAAAMA/wAAAAAAAAHwRQgCEAAZAAAAAwD/AAAAAYMAAQAACAIQABoAAAADAP8AAAD8ggAB
AAAIAhAAGwAAAAMA/wAAAFQwAAFUAAgCEAAcAAAAAwD/AAAAAoMAARWABAIRAAAAAAAPAAgAAFF1
YW50aWxlBAIlAAAAAQAPABwAAE92ZXJhbGwgTG9zcyB3aXRoIElQTFI9MS5FLTMEAg0AAAACAA8A
BAAASVBMUn4CCgABAAAAGwABACRABgAlAAEAAQAbAEJg5dAi27k/AAAgTG/9DwBEAQAAwB/8qfHS
TWJQPwMDAg4AAQACABsA/Knx0k1iUD9+AgoAAgAAABsAAQAiQAYAJQACAAEAGwCyne+nxku3PwAA
AQAB/w8ARAIAAMAf/Knx0k1iUD8DAwIOAAIAAgAbAPyp8dJNYlA/fgIKAAMAAAAbAAEAIEAGACUA
AwABABsAI9v5fmq8tD8AAAIAAf8PAEQDAADAH/yp8dJNYlA/AwMCDgADAAIAGwD8qfHSTWJQP34C
CgAEAAAAGwABABxABgAlAAQAAQAbAJQYBFYOLbI/AAADAAH/DwBEBAAAwB/8qfHSTWJQPwMDAg4A
BAACABsA/Knx0k1iUD9+AgoABQAAABsAAQAYQAYAJQAFAAEAGwAIrBxaZDuvPwAABAAB/w8ARAUA
AMAf/Knx0k1iUD8DAwIOAAUAAgAbAPyp8dJNYlA/fgIKAAYAAAAbAAEAFEAGACUABgABABsA6iYx
CKwcqj8IAAUAAf8PAEQGAADAH/yp8dJNYlA/AwMCDgAGAAIAGwD8qfHSTWJQPwMCDgAHAAAAGwBs
FK5H4XqkPwYAJQAHAAEAGwC8oUW28/2kPwgABgAB/w8ARAcAAMAf/Knx0k1iUD8DAwIOAAcAAgAb
APyp8dJNYlA/AwIOAAgAAAAbAJsehetRuJ4/BgAlAAgAAQAbADs5tMh2vp8/CAAHAAH/DwBECAAA
wB/8qfHSTWJQPwMDAg4ACAACABsA/Knx0k1iUD8DAg4ACQAAABsAXhSuR+F6lD8GACUACQABABsA
/i7dJAaBlT8IAAgAAf8PAEQJAADAH/yp8dJNYlA/AwMCDgAJAAIAGwD8qfHSTWJQPwMCDgAKAAAA
GwBHFK5H4XqEPwYAJQAKAAEAGwCGSQwCK4eGPwgACQAB/w8ARAoAAMAf/Knx0k1iUD8DAwIOAAoA
AgAbAPyp8dJNYlA/AwIOAAsAAAAbADvfT42XboI/BgAlAAsAAQAbAHoUrkfheoQ/CAAKAAH/DwBE
CwAAwB/8qfHSTWJQPwMDAg4ACwACABsA/Knx0k1iUD8DAg4ADAAAABsA/Knx0k1igD8GACUADAAB
ABsAPN9PjZdugj8IAAsAAf8PAEQMAADAH/yp8dJNYlA/AwMCDgAMAAIAGwD8qfHSTWJQPwMCDgAN
AAAAGwB56SYxCKx8PwYAJQANAAEAGwD8qfHSTWKAPwgADAAB/w8ARA0AAMAf/Knx0k1iUD8DAwIO
AA0AAgAbAPyp8dJNYlA/AwIOAA4AAAAbAPp+arx0k3g/BgAlAA4AAQAbAHnpJjEIrHw/CAANAAH/
DwBEDgAAwB/8qfHSTWJQPwMDAg4ADgACABsA/Knx0k1iUD9+AgoADwAAABsAAQDgPwYAJQAPAAEA
GwD6fmq8dJN4PwgADgAB/w8ARA8AAMAf/Knx0k1iUD8DAwIOAA8AAgAbAPyp8dJNYlA/AwIOABAA
AAAbAPyp8dJNYnA/BgAlABAAAQAbAHsUrkfhenQ/CAAPAAH/DwBEEAAAwB/8qfHSTWJQPwMDAg4A
EAACABsA/Knx0k1iUD8DAg4AEQAAABsAEX9qvHSTaD8GACUAEQABABsACKrx0k1icD8IABAAAf8P
AEQRAADAH/yp8dJNYlA/AwMCDgARAAIAGwD8qfHSTWJQPwMCDgASAAAAGwATqvHSTWJgPwYAJQAS
AAEAGwARf2q8dJNoPwgAEQAB/w8ARBIAAMAf/Knx0k1iUD8DAwIOABIAAgAbAPyp8dJNYlA/AwIO
ABMAAAAbACqq8dJNYlA/BgAlABMAAQAbABOq8dJNYmA/CAASAAH/DwBEEwAAwB/8qfHSTWJQPwMD
Ag4AEwACABsA/Knx0k1iUD8DAg4AFAAAABsAkst/SL99TT8GACUAFAABABsAxY8xdy0hXz8IABMA
Af8PAEQUAADAH/yp8dJNYlA/AwMCDgAUAAIAGwD8qfHSTWJQPwMCDgAVAAAAGwAtQxzr4jZKPwYA
JQAVAAEAGwCSy39Iv31dPwgAFAAB/w8ARBUAAMAf/Knx0k1iUD8DAwIOABUAAgAbAPyp8dJNYlA/
AwIOABYAAAAbAMe6uI0G8EY/BgAlABYAAQAbAGAHzhlR2ls/CAAVAAH/DwBEFgAAwB/8qfHSTWJQ
PwMDAg4AFgACABsA/Knx0k1iUD8DAg4AFwAAABsAYTJVMCqpQz8GACUAFwABABsALEMc6+I2Wj8I
ABYAAf8PAEQXAADAH/yp8dJNYlA/AwMCDgAXAAIAGwD8qfHSTWJQPwMCDgAYAAAAGwD8qfHSTWJA
PwYAJQAYAAEAGwD6fmq8dJNYPwgAFwAB/w8ARBgAAMAf/Knx0k1iUD8DAwIOABgAAgAbAPyp8dJN
YlA/AwIOABkAAAAbAC1DHOviNjo/BgAlABkAAQAbAMe6uI0G8FY/CAAYAAH/DwBEGQAAwB/8qfHS
TWJQPwMDAg4AGQACABsA/Knx0k1iUD8DAg4AGgAAABsAYTJVMCqpMz8GACUAGgABABsAlPYGX5hM
VT8IABkAAf8PAEQaAADAH/yp8dJNYlA/AwMCDgAaAAIAGwD8qfHSTWJQPwMCDgAbAAAAGwAtQxzr
4jYqPwYAJQAbAAEAGwBiMlUwKqlTPwgAGgAB/w8ARBsAAMAf/Knx0k1iUD8DAwIOABsAAgAbAPyp
8dJNYlA/AwIOABwAAAAbAHZDHOviNho/BgAlABwAAQAbADNuowG8BVI/CAAbAAH+DwBEHAAAwB/8
qfHSTWJQPwMDAg4AHAACABsA/Knx0k1iUD/XAD4A4woAADACTwBJAEkASQBJAEkASQBNAE0ATQBN
AE0ATQBNAE0ASQBNAE0ATQBNAE0ATQBNAE0ATQBNAE0ATQDsAM4ADwAC8MYAAAAQAAjwCAAAAAIA
AAABBAAADwAD8K4AAAAPAATwKAAAAAEACfAQAAAAAAAAAHMUdAAAAAAAAAAAAAIACvAIAAAAAAQA
AAUAAAAPAATwdgAAAJIMCvAIAAAAAQQAAAAKAACjAAvwPAAAAH8ABAEEAb8ACAAIAIEBTgAACIMB
TQAACL8BAAARAMABTQAACMsBAQAAAP8BCAAIAD8CAAACAL8DAAAIAAAAEPASAAAAAAACAPADAgBL
AAoA4AMRAB4AAAAR8AAAAABdABoAFQASAAUAAQARQAAAAADUHEkBAAAAAAAAAAAJCBAAAAYgAPIV
zAdJAAAABgAAABQAAAAVAAAAgwACAAAAhAACAAAATQCOAwAASABQACAATABKACAAOAAxADAAMAAg
AFMAZQByAGkAZQBzACAAUABTAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAwTUALgCH3cAAAIA
AQDqCm8IZAABAAcAWAIBAAIAWAIDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAMASAADIGQAAAQAAAAAAAAABAAAA
AgAAAAAAAAAAAAAAAAAAAAAAAAAF+hGTdjf6sBo+GwABAAEAAAAAAAEAAAAAAAIAAgABACQEAADC
AQAAAAAAAAAAZAAAAAAAAAD//wAA//8BAP//AAD//wEA//8AAP//AAD//wAA//8BAP//AQD//wAA
//8BAP//AQD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AgD/
/wIA//8DAP//AQD//wAA//8AAP//AAD//wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAP//Q3VzdG9tIHBhZ2UgMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAi0MAQAdEAAAAAAAAQ3VzdG9tIHBhZ2UgMgAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAi0MAQAdEAAAA
AAAAQ3VzdG9tIHBhZ2UgMwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAi0MAQAdEAAAAAAAAAAAAAAAAAAChACIAAQBkAAEAAQABAAAAWAJYAgAAAAAA
AOA/AAAAAAAA4D8BADMAAgADAGAQCgDOEz0OyAAAAAgAYBAKAM4TPQ7IAAEACQBgEAoAzhM9DsgA
AQAKABIAAgAAAAEQAgAAAAIQEAAAAAAAAAAAAOj/fwHQv70AMxAAAKAABAABAAEAZBAIAAAAAQAA
AAEAMhAEAAAAAgAzEAAABxAMAAAAAAAAAP//CQBNAAoQEADAwMAAAAAAAAAAAABOAE0ANBAAAAMQ
DAABAAEAHAAcAAEAAAAzEAAAURAPAAACAAAAAAcAOgEAAAABAA0QPAAAABwBTwB2AGUAcgBhAGwA
bAAgAEwAbwBzAHMAIAB3AGkAdABoACAASQBQAEwAUgA9ADEALgBFAC0AMwBREBMAAQIAAAsACwA7
AQABABwAAQABAFEQEwACAgAACwALADsBAAEAHAAAAAAAURAIAAMBAAAAAAAABhAIAP//AAAAAAAA
MxAAAF8QAgAAADQQAABFEAIAAAA0EAAARBAEAAoAAAAkEAIAAgAlECAAAgIBAAAAAADY////rv//
/wAAAAAAAAAAsQBNACAQAAAzEAAATxAUAAIAAgAAAAAAAAAAAAAAAAAAAAAAJhACAAgAURAIAAAB
AAAAAAAANBAAACQQAgADACUQIAACAgEAAAAAANj///+u////AAAAAAAAAACxAE0AIBAAADMQAABP
EBQAAgACAAAAAAAAAAAAAAAAAAAAAAAmEAIACQBREAgAAAEAAAAAAAA0EAAARhACAAEAQRASAAAA
DQMAAFoBAACcCwAASwgAADMQAABPEBQAAgACAA8BAAClAAAAQQ4AAP8KAAAdEBIAAAAAAAAAAAAA
AAAAAAAAAAAAMxAAAB8QKgAAAAAAAAAAAAAAAAAAAPC/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
/QFOEAIApQAeEB4AAgADAQAAAAAAAAAAAAAAAAAAAAAAAAAAIwBNAAAANBAAAB0QEgABAAAAAAAA
AAAAAAAAAAAAAAAzEAAAHxAqAAAAAAAAAAAAAAAAAAAA8L8AAAAAAAAAAAAAAAAAAAAAAAAAAAAA
CMAtAR4QHgACAAMBAAAAAAAAAAAAAAAAAAAAAAAAAAAjAE0AAAAhEAIAAQAHEAwAAAAAAAAA//8J
AE0ANBAAACUQIAACAgEAAAAAAGgHAACjCwAA5QIAAHsBAACBAE0AAAAAADMQAABPEBQAAgACAAAA
AAAAAAAAXQAAABcAAAAmEAIACgBREAgAAAEAAAAAAAANEB4AAAANAUkAUABEAFYAIABRAHUAYQBu
AHQAaQBsAGUAJxAGAAMAAAAAADQQAAAlECAAAgIBAAAAAABYAAAAswIAALcAAACIBQAAgQJNAAAA
WgAzEAAATxAUAAIAAgAAAAAAAAAAABcAAABWAAAAJhACAAoAURAIAAABAAAAAAAADRAeAAAADQFP
AHYAZQByAGEAbABsACAAIABMAG8AcwBzACcQBgACAAAAAAA0EAAANRAAADIQBAAAAAMAMxAAAAcQ
DACAgIAAAAAAAAAAFwAKEBAAwMDAAAAAAAAAAAAATgBNADQQAAAUEBQAAAAAAAAAAAAAAAAAAAAA
AAAAAAAzEAAAGxAGAGQAAQAAACIQCgAAAAAAAAAAAA8AFRAUAKIFAADkDQAAcQYAAHsBAAAAAQ8A
MxAAAE8QFAAFAAIAogUAAOQNAAAAAAAAAAAAACUQIAACAgEAAAAAANj///+u////AAAAAAAAAACx
AE0AAAAAADMQAABPEBQAAgACAAAAAAAAAAAAAAAAAAAAAABREAgAAAEAAAAAAAA0EAAAMhAEAAAA
AwAzEAAABxAMAAAAAAAAAP//CQBNAAoQEADAwMAAAAAAAAAAAABOAE0ANBAAADQQAAAGEAgAAAAA
AP3/AAAzEAAAXxACAAAABxAMAAAAAAAAAP//CQBNAAoQEADAwMAAAAAAAAEAAQBOAE0ACxACAAAA
XRACAAEACRAUAAAAAAAAAAAAAAAAAE0ATQA8AAAANBAAADQQAAA0EAAAJRAgAAICAQAAAAAA2P//
/67///8AAAAAAAAAAPEATQDQPQAAMxAAAE8QFAACAAIAAAAAAAAAAAAAAAAAAAAAAFEQCAAAAQAA
AAAAACcQBgABAAAAAAA0EAAANBAAAAACDgAAAAAAHAAAAAAAAQAAAGUQAgACAGUQAgABAGUQAgAD
AAoAAADtABgAAAAZ8RAAAAABAAAAAAAAAAEEAAABBAAAPgISALYAAAAAAEAAAAAAAAAAAAAAAB0A
DwADAQABAAAAAQABAAEAAQEKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAQAAAAAgAAABUAAAAEgAAAGgAAAAMAAAA
gAAAABMAAACMAAAAAgAAAOQEAAAeAAAACgAAAEFsIE1vcnRvbgAgAB4AAAAKAAAAQWwgTW9ydG9u
ACAAHgAAABAAAABNaWNyb3NvZnQgRXhjZWwAQAAAAIAXmJLOPsABAwAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+/wAABAoC
AAAAAAAAAAAAAAAAAAAAAAACAAAAAtXN1ZwuGxCTlwgAKyz5rkQAAAAF1c3VnC4bEJOXCAArLPmu
ZAEAACABAAAJAAAAAQAAAFAAAAAPAAAAWAAAABcAAABoAAAACwAAAHAAAAAQAAAAeAAAABMAAACA
AAAAFgAAAIgAAAANAAAAkAAAAAwAAADlAAAAAgAAAOQEAAAeAAAABQAAAEFUJlQAAENoAwAAADEV
CAALAAAAAAAAAAsAAAAAAAAACwAAAAAAAAALAAAAAAAAAB4QAAAGAAAAAwAAAElQAAMAAABURQAJ
AAAASVAgKDE1MCkAEAAAAElQIChDbGFzczEgNDAwKQAPAAAASVBEViBRdWFudGlsZXMABwAAAENo
YXJ0MQAMEAAABAAAAB4AAAALAAAAV29ya3NoZQUARABvAGMAdQBtAGUAbgB0AFMAdQBtAG0AYQBy
AHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAAAAA4AAIA////////////////AAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEwAAAPwBAAAAAAAAXwA5ADkANwAxADcAMQA2
ADMAMwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYAAQD/////
/////xcAAAACzgIAAAAAAMAAAAAAAABGAAAAAADqxkAdbsIBAOrGQB1uwgEAAAAAAAAAAAAAAAAB
AE8AbABlAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAACgACAf///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
ABsAAAAUAAAAAAAAAAEAQwBvAG0AcABPAGIAagAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAASAAIBFgAAABgAAAD/////AAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAHAAAAGYAAAAAAAAAZXRzAAMAAAAFAAAAHgAAAAcAAABDaGFydHMAAwAA
AAEAAAAAmAAAAAMAAAAAAAAAIAAAAAEAAAA2AAAAAgAAAD4AAAABAAAAAgAAAAoAAABfUElEX0dV
SUQAAgAAAOQEAABBAAAATgAAAHsARgAwADgANwAyADYAQwAxAC0AQQBBAEEAMgAtADEAMQBEADQA
LQA4ADMANgAyAC0AMAAwADEAMABBADQARABFADkANAAzADkAfQAAAAAAAAAAAAAAAQAAAgAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEA
/v8DCgAA/////wLOAgAAAAAAwAAAAAAAAEYXAAAATWljcm9zb2Z0IEVxdWF0aW9uIDMuMAAMAAAA
RFMgRXF1YXRpb24ACwAAAEVxdWF0aW9uLjMA9DmycQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAABwAAAACAD7BXAAAAAAAAAAQuxQARA8VAAAAAAADAQEDAAoBEoNJ
ABKDUAASg0QAEoNWAAKGPQASg0kAEoNQABIDAE8AYgBqAEkAbgBmAG8AAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEgACAf////8ZAAAA/////wAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB4AAAAEAAAAAAAAAEUAcQB1AGEAdABpAG8AbgAg
AE4AYQB0AGkAdgBlAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAIA////////
////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHwAAAHgAAAAAAAAAMQBU
AGEAYgBsAGUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAA4AAgABAAAAAwAAAP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACi
AQAAFN4AAAAAAAAFAFMAdQBtAG0AYQByAHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAKAACAQIAAAAcAAAA/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAACEAAADAAQAAAAAAAINUABKDRAALEoJtABKCYQASgngACgKGEiISg0kAEoNQ
ABKDVAASg0QACxKCbQASgmkAEoJuAAAAAAAAAAAAAAD+/wAABAACAAAAAAAAAAAAAAAAAAAAAAAB
AAAA4IWf8vlPaBCrkQgAKyez2TAAAACQAQAAEgAAAAEAAACYAAAAAgAAAKAAAAADAAAAwAAAAAQA
AADMAAAABQAAANwAAAAGAAAA6AAAAAcAAAD0AAAACAAAAAgBAAAJAAAAGAEAABIAAAAkAQAACgAA
AEABAAALAAAATAEAAAwAAABYAQAADQAAAGQBAAAOAAAAcAEAAA8AAAB4AQAAEAAAAIABAAATAAAA
iAEAAAIAAADkBAAAHgAAABYAAABSZWMgWS4xNTQxICgxMC8wMy8wMSkAOQAeAAAAAQAAAABlYyAe
AAAACAAAAEtDRy9BQ00AHgAAAAEAAAAAQ0cvHgAAAAEAAAAAQ0cvHgAAAAsAAABGTEFTSEUuRE9U
ACgeAAAACAAAAERJU0FOZXQAHgAAAAIAAAAyAFNBHgAAABMAAABNaWNyb3NvZnQgV29yZCA5LjAA
MUAAAAAAjIZHAAAAAEAAAAAAboDySWzBAUAAAAAAcmk+HW7CAUAAAAAAcmk+HW7CAQMAAAABAAAA
AwAAAD8kAAADAAAAns4AAAMAAAAAAAAAgQEAAIIBAACDAQAAhAEAAIUBAACGAQAAhwEAAIgBAACJ
AQAAigEAAIsBAACMAQAAjQEAAI4BAACPAQAAkAEAAJEBAACSAQAAkwEAAJQBAACVAQAAlgEAAJcB
AACYAQAA/v////7///+bAQAA/v///50BAACeAQAAnwEAAKABAAChAQAAsQEAAKMBAACkAQAApQEA
AKYBAACnAQAAqAEAAKkBAACqAQAAqwEAAKwBAACtAQAArgEAAK8BAACwAQAAnAEAALIBAACzAQAA
tAEAALUBAAC2AQAAtwEAALgBAAC5AQAAugEAALsBAAC8AQAAvQEAAL4BAAC/AQAAwAEAAMEBAADC
AQAAwwEAAMQBAADFAQAAxgEAAMcBAADIAQAAyQEAAMoBAADLAQAAzAEAAM0BAADOAQAAzwEAANAB
AADRAQAA0gEAANMBAADUAQAA1QEAANYBAADXAQAA2AEAANkBAADaAQAA2wEAANwBAADdAQAA3gEA
AN8BAADgAQAA4QEAAOIBAADjAQAA5AEAAOUBAADmAQAA5wEAAOgBAADpAQAA6gEAAOsBAADsAQAA
7QEAAO4BAADvAQAA8AEAAPEBAADyAQAA8wEAAPQBAAD1AQAA9gEAAPcBAAD4AQAA+QEAAPoBAAD7
AQAA/AEAAP0BAAD+AQAA/wEAAAECAABUAegD6AMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAA8ABPBCAAAAsgQK8AgAAAAEBAAAAAoAAFMAC/AeAAAABEEEAAAAPwEAAAcAgQERAAAQvwEM
AB8A/wEAAAgAAAAQ8AQAAAADAACAMgAH8NIAAAADBDi0hfdQzgtOL7yPyeYa0zf/AK4AAAABAAAA
JkoAAAAAlwFgIRvwpgAAADi0hfdQzgtOL7yPyeYa0zeoAAAAAAAAAAAAAAAgAQAAIAIAAMi9AQBY
SgMAdAAAAAD+eJxjZOBkYGAOYQABITDJCsScTCAWCxAzMTKCRRiZ/v//DxbRY5QAixgyMUJVczPB
9PEwKTApMILMUWPjZ5Bi+A/SxCAA5B8AspYB8QMg+xhQIzdUDQ+Db2JJRkhlQSoDQwADF1SUC6yT
EeweZjAJAFBlGhSkDgAARABkAAAAAAAAAAIAAAAAAAAAAAAAAAAAryh3FT8DPgMAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8ABPA8AAAAsgQK8AgAAAAGBAAAAAoAAEMAC/AYAAAABEEG
AAAAgQERAAAQvwEAABAA/wEAAAgAAAAQ8AQAAAAFAACAMgAH8BQOAAADBA/pKDuGY2wD6rCej8fk
I/P/APANAAABAAAAjksAAAAAbgBgIRvw6A0AAA/pKDuGY2wD6rCej8fkI/OiNwAAkgAAABkBAADY
EAAArwkAADjqZADIPjUAtg0AAAD+eJy9Wwt0VMUZnrkz8899320Eu5KUXNBAKIGzaKOtiA1ikADl
rDyK2LRuxPWUkAckixERi7Gc5tBoFh+oRdvYc/C0lbZBi7UtqLS1tjbSWCtQ0TZUUYoP1lOxig86
97EgbDbs3SzdeyZ39965833/9/8z9597JxgpCJHnihHi6EGMxOczoowBC4XRUfFBKIRuF0fOEuf2
hBD6uaiu+DVkt4Ykfn3WP3K2e4SiYjR/TjQ6DP0xhSJOm8NEudS4Dnkf1a+turUQktC75MQ2ifhl
+UeGubUo0pFDD/ttMFE06Sx8u/tNlzbI00NUfKPYEJYg9JGUrukcnYA91kck5h5zDBvtn8Fu/WL6
ffpnKUX6sXe1Vyd9teRfjY590lcTZIj9h586c5ykV4O6DBWnhos+zK073L2q+6hXM5kmi+YvaYy3
2nPibfbc5sa6JnGN1wpzW0tlac05NxGH3b0kLHIUPlddQkdIzun51ZPRZL8O9utIJ+yP64MQeESk
0cf4e/psoc+5+qQVSduf5hXy/XWmHzezRZuzxcn9Yr+AZrSPjrefZiCLfRmRUBRHab8oJyOkkWUf
CVwknIHcK3nIh0lQ5D4pSlMkd+T09SdH0m+sFOkzT1ZqIM8F8aZqFdKbOwbkmM2bLxmepi+YQTXt
N6K0z8zfm9ssD3lBKCjyk1aURkPBvTm4dmH6AFsPiKRIrtptE3H4lih9osIjFGWNmudE7G3LaHWo
UfMecU5ftrAafa0AUbNFcMxuef6K7jMQqdKytZt7O5eriPTwobVTTNeTB6RlUkjK1cO6aKtWeHiT
2MdJkBgNSTHSLUq+vcNBrvCRKwMiRwRyZEjIzn3SQWYBkZFARjkj5+61URSRZM79spN4XiujQb2W
JDFi0/y95iBX+MjBvJYkEYE8NK/1+l57QQrmtT6pW5ShIN/nI28KiNztboWPl3fEOB6DXOOlFrx4
OQxB4yUGMZKC/OPFQa7wkYPFSwwiAjn3eMldu30ckWjWkTYjG+Sedvt5UO2iPEb6ef7aOcgVPnIw
7aI8IpBPh3ZTTXGXMnLVbrPhaVdtBtWux4iRKjN/7RzkCh85mHY9RkQgnw7tlmuI9Ku5aveS6mm3
QguqXb8aI8u0/LVzkCt85GDa9asRgXw6tNsisiM7Z+1KfO22qkG1s4V2PWr+2pX42jnIwbSzhXY9
6unQbr21TEJWrtp9ZHra3WUF1Q5ZMZK08tfOQa7wkYNph6yIQM4/t3CQnYzQQQ6WESJL5G1W7hnh
QMi9PnKwrAZZfVLSyj+rcZDv85GDZTXI6hbIwbMab3981riap0gyI4fJd9boPHVzZo3PgFNnoi02
FD62ebWzzx9P5jZFS5FoxngzVG7r1CDcTvbYcBGZxYLrdOG5NsjFY85z0XPIcyhConQymUJryDh6
JRlGG8nHpJ3sJ/eSXvIIeZjsJPeQN8hqotA6UaOazKTlpIHqpIseknbTrdIodqO0lFVLW9lnpL+z
9/HHrB+Xwp/wVHgEXw0/wO3QibvhBrwN6vFuqMUpiGKZT8elfAo+n5+PZ/MIvppX4DY+DnfysfgB
PgZvFeWPvBwf4hPwMPkL+AL5YrxIrsE3yAvwRjmGfy0vxXvkBH5PXoXPUL6FRytrcESU2cpNOK6s
xKuVBL5TacQ/VuL4caUWv6rMxIr6JVyiTsIT1fF4qlqGF6ijcb1q4zWibFbPxnvUsfht9fOYahPw
CO1cPEn7Ip6hVeGYVoOv1+bj9Vodfkhbjp/WbsGvaPdgpPfgkL4dj9J78Xn6XjxdfxM365a0UT9f
+pMek97XO6Vy41fSV40D0i1GmPzUuIzsMK4ifzPayH7jNvKe8SBh5nZyhvk8KTUPknHmUXKuOYx+
yRxHp5hTaJUZpVPNxfTL5nX0InMdvcC8n0bMLbTcfIqONP9OzzDfotzE7IgxnL1hlLO9xkXs18Zi
dpfRwZqMzWy6sZN9znibvatr0KuPgQf1KXCzHoVl+iKI6TGI6tdClb4UInoT2PpyCOktcFRrgX9o
zbBdq4eNWh3coC2EK7RZMFybBP9Ry+Cv6lmwRbUgqXJYpkoQVRFMUjEUqRTeVVTYpYTgMSUMG5VR
EFPOgzKlGmTlK3BQng+98pXwM/kb0CXHYJkoUfnrEJEXgSXPhbf5THiWV8FDvBK+yUdCGQf4F6TY
DniNdcPLbA3sYjHoY1XwLBsFvQyL/T72F/Zb9lf2Q7aLXcP+yarZK2wse42p7AB7ix5gffQ1tpXu
Y9+jL7I1tI/F6e/YdLqVjaGbGKV3sn3kZvYEaWT3k4XsJlLFriZj2QIygtUQg11MjtIvkHdoBXmF
jiF/ozZ5in6ObKXFZJMod4nv36ajSCsdS66mkQBPVjMyUdEH3xRdFETvHcNz6bXl7jhbhHpEP9qC
j8DDmPCtWOOP4SK+HYf5DlzCnxZ9qxfb/FXJ5gelUn5IKuH/kcL8famIfyhp/BOJ8KPSEedpH+Sd
y1Bv/natKBtyGm/SzG0ag1G0Hs6hrVBOV8FE2g6VtAOm0E6YTrsgSpMQgSRcCF0wDTphFnTAXGiH
K2AV1EIrXAX1IGaeeTN/iXvMx6hBmYv5Guzj9fAqb4UDfJWI2nY4zDvgY94JIHdBSE5CSknCEaUL
iNoJmtohekY7hNVVUKK2QqlaDyKHzJt5g+Yxf9QIylxk/LBc9OmE1grXa6vgJq0d1modcKvWCRu0
LujWkrDGSMI6owvuMDpho9EBPzTa4UfGKthstMLPjXoQs668mV9kenG+wQoa51VmCqaaR+ASk/Bq
U+MzzCL+FTPMLzdL+EKzlNeaNk9YNr/BKuXfskr4LVaYd1hF/LuWxm+zCO+yjkDSyj/OnZzTYX6m
mSvzS13mNnKeUEwih6GSHIELySdwCSF8NuH8CqLxOLF4ghTxtWQ430DC/CdkBH+clPDnyUj+b1LK
w9Tm5YbNFxqlvNEYyduNEn63MYL/xAjzbcZw3msU8b2GxQ8YGn/X4PwTg3AwPwFNKGWZhyFk5m/x
S9jrI3HLe7oQYIaHRQ+x+vlQRsPNAvFlse/PCXmYiyyj3fhFvhPv4U/hXfxx/Dx/FO/kD+Mn+Bb8
GO/BPXkzqrU8RrdaQRnFrBd5vbWHt1i7+ErreX6ztZOvtZ7g37EeEyV3RgPnoBfzhJqE6zKeU+Wb
g45ETg6q8B7uZKNz4om25pal9rz44sSS5iZUjcajYvE3gkRUi5y0Uvx2jhSLX5GA2fNOfq5u84dY
oZhf4DK/l+9ntvhW3XTNBFHstAXll8TrWuItwpKW65YsjtuTXcY28vbhDMtsVOXaZrvFs9Q5U+we
zczGc2Go+wwnaM77/8ub57l4lXm1pfht7dacV+vjBLdg6pfx30Mb/KFgb+O8uEkBoqc7bi7m1EwC
ZLxLG2rEV2mnP+JrxGh+JyoU87F+DOx0V1tMW9GaaG4UIV7T1Jqoa2ioc/lXCZZlLttZfiTb/hHP
ivxt2R2y+eiMZ7xDtaXW+P/bcpt8m97PVxZsJJrg2rJIfoSdJb4taI23TEg0T3D29rTmpiYvsuxy
EVVlrh22y9o+9jvsWupsn4618AB9PPf4XiT/QnHie368Id7qj4HOCDTZRRjvIx8f34Y6Mi2Sz9Pz
G5luUj6U+uTMd9NDWydQo8ws4Fqh9QomA3E88R6eadkm3icX7llW2rJnoHArINYrqwXHbVnfGeba
Tp3yhtInX6lka+fk/OqrosEKUQ6JUqkEyTWvVCLKQVHyzewc5I9kD5kFREYCGeWMnC0qroU+ua9g
8T7ajwpVzJmc/t7SuKSprsGuXr5iybLGeFNistvTZ7mjitP3w34OlB5XnW/BeuzPlGLlVjnzXWm+
FhS5FoCyjjvtX1aXiLfVrfTvxOPdfeYIn0u7IbfdlcrD3PHt3OYViXhLlW/7+DzGqTv0PvlgRoTn
a3WJ77dzVDHBRNGW5kTz4uYGe16ibvHSSn9sjvj+cfIQb6Q+9b3uVGuKLHZUepL0ZF33OLD1L4ir
xrKnMq7K13ovN+5mR7GTG8+eOkdEZbXYhm7d69aT5J6s6wCzWfe6NZb9tGArHNPWvW4Gs+5EVsul
tervcOH6WanL6iJpHXd6Rk302GRpWkPzimtsEWOZ86IqPxsJmmOV0fWkjfyywHf1FHnHvavPqake
pP+mVzx7n3R8ZIsc8BnfTCcRm6Isq60gq50HzTYSKvDa2BSZaZ7aztwtW2fadFGWPpHNsslKg3Gr
fLteWMtA6dULZ9ndim6cr+zN4Di4Zc3KN0I75M8XbC4zyrXsQuUaw/lfg3SnqmkSt5tr6xbHB3jW
kL4D2e6YPj6rDifnLh3MW3l7Hwy+8vZ+SJGOgs1v0itvf8uGnnemPbeFrhYct2VwTHvuVFncjdxT
IikPrsR6OUVuLNgImlbiUV5IJZYLjtnW+J5aiRmKp0StOrgSXxejyoyCZS9pJdqVQioxRXC8Mcsc
4tRKWJqnxNn64Eqco6eIVbDnSWklarRCKkEFx2lZ1o+fWom9uqfEIWNwJVJGimSOnkNVYrhRSCX6
BEcry9rCTCUGtnSi9Lq1Bm8vcH73Af6vm99dOm++GN0rc3jOcDKrd6Q1+OkC59QfYCw5rObNnSY4
VYltcFbHNXOi6EMp5LJDaJuLgSVp9LyVrYl4IzrmGU97NsB/tH36c+J/wDnPhoh7/H+z4fiwGgIA
AEQAZAAAAAAAAAACAAAAAAAAAAAAAAAAAAQLLAHoA+gDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAPAATwQgAAALIECvAIAAAABwQAAAAKAABTAAvwHgAAAARBBwAAAD8BAAAGAIEBEQAA
EL8BDAAfAP8BAAAIAAAAEPAEAAAABgAAgDIAB/CEAQAAAwRmjKjKO9rbpxQNYsZzxzgI/wBgAQAA
AQAAACxbAAAAAG4AYCEb8FgBAABmjKjKO9rbpxQNYsZzxzgIKgIAAAAAAAAAAAAAoBEAAOABAACw
UhsA6OcCACYBAAAA/nichVFNS8NAEH0zaWubBEyFgngKHrxV0LvgofhxUMQGz60QsGDaYCqSm949
+BM89Vd48OTv6E/wLhhnpxsJuXSXgZm3M2/ezhA6gNMjgNGDOU2xDhuvIcZEihAXRaHIPm0rcsBk
sz0u63xe0nt3S7y91iZ2UJgiBBJ/ivclNuoCCyn0bI6Pi/H8LsrTGDhWBT8cFioEb6QqGEE0SeIs
vIyfwutZMp4CL0ZJX95FPQ7dEbUCR7xkMrUcz78lB63hIP3Vd4Ur8w1yfhUNSuS1WUdOsEIGN3XN
6/rB9iO4lmvZNrN7TNP4QWdVVW9WIDcY5snt7B5c19y2HKeeSe3/x2cNEx9pDzNnV3ehA7U9Amxo
9KHbI+bdYZ7N42Slr6rT0bw/budTWrAFAABEAGQAAAAAAAAAAgAAAAAAAAAAAAAAAAAPHuIO6APo
AwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADwAE8DwAAACyBArwCAAAAAcEAAAACgAA
QwAL8BgAAAAEQQcAAACBAREAABC/AQAAEAD/AQAACAAAABDwBAAAAAYAAIAyAAfwIAUAAAMEXMI5
mJQzBpLyfehkDZRJt/8A/AQAAAEAAABMXAAAAABuAGAhG/D0BAAAXMI5mJQzBpLyfehkDZRJt2QV
AAAAAAAAAAAAAAECAAD+AAAACI9KAADqJADCBAAAAP54nNVYa2hcRRT+ztzdZHdta2jS/kirLCFa
FVKz2YKgKEpVrFQbbSnFWmyMcRvcVuzGV30F29rWFunDR2DBVJAi+Ef6p1AfXfwj6h/tH0G2EugP
CQgGYvERdT1n7p25+7ib3U02AfcyO9+cOfe85txzZy4hCjhnY+A+AfmFuUWVQaRyuRxCjEK0VPeK
lJ5Zov7lWYfRtZq+hgqF0pFwXaUluXRfnq/DSO7h/ndm7NA2jHp/ox4Y9QZyby6fw5lvplCYmcLp
0x8yeRQFYeO/ggcK3qDATTSsU+If8JfW6f669EwPEVq5/1uRqznuUlVVfsfjh5YOjxqq6rWRZ7RV
i4JIXkhZ9UsQ/1aG/uGlllEbtxk1XXCjcJxMPO7aOzyQtvrCZXyfqWC+ljp7335Xbpu2ysglpbo2
v5gZGdpt5LYG+tkyB3+rrXtE91NV8oW8WeXJNRqoJMvN8yMSVoX+xAzHLRy4YrU8ImuVr8XXHORR
uMIj5dkcqbBvGffdThgpdCJP0rKMs3pcKz5qwfwZZztWsg0yWhH6DUfoEs5rrg61nemz16t25smT
y93pcbcr8a0Z9voZVRn/UntN/CR/pHZVroZvY7AfnZ4f7SpbhHyPUvNaAVWHR7VzoJYPWWtl2OPN
YhClvsiqDtq1S1mZg0WemntTKI1IhxqviJLQdlraTku7bO+9DENLVdhZXzTDDeTHH3N4/huR/z4m
qNFsaER+Fpe0/OD3p6mWxfku7/KuEg1B1SfC/XWO0tVmN66xY8EZxO1Y8D50I6bHjsav4nrsxw2W
JvgQbsIx3mEYmuCT6MUYkpYmeBy34CPchiWaFtL4LO7EOazHF7gXyzW9VeMvcR++wv24iE3IYwsm
sJWzZ5uVJ/hnPIJJbLc0wb/gUfyKHZYmeBqP8d5nwNIEz+Bx3sM8YWmCQ/QkojRsaYKvpqewgvZY
muDV9Ay6acT6IXgtvYAk7cOt9LL1Q/Ad9ArW02t4kF7HNnoDO+gQPxmHrTzBg3QEQ9wMTfAuehNp
OmrXQnCGjvlrw/glesuOBR+k41aG4KN0AifopKUJHqNT+IDetrYL/pjewSf0Ls5xW6bpYY0vcPua
3sNFbnkam1OeV98ZNOc5qke+qar/d/mVu3r3iSa0c98XO4UbdT4k1vb23tPTmxTNrXxFvd7l2lzK
1RfMtbyUK1HO1VxfxaeFjGWw/OIItmmvz3C+t2iv2ed1os34a+Yf8OeTQfPfwc73Bc1v8ecTxfOL
E8/ap4F6djL16P0e/XSeK295nFfpOHyOK1jKaEP/3VvjDz07sGdkOD2koxHVEYlx7skV0ldkwa2d
PUrN13cQa3Az50RQFrpnvAPOAcc747WVn/Eiukr3xfbzsypR3PTc0N6BdDoe3/h0JlNijXn7L17s
wot4vrvi7fibsf8SLeV1dxqH6Sd8uuDyq+3gyk8sk7hQ8ww2iR8s97dlbwzJsITOnAn8iNVFmSOJ
E39+eGRXfEP/xodvl/KUjPHdbtV34HhVyq1UUW8c4j6q3wkR+LVsPtGqPBv5edaM1ZhN/nzePI3I
r322m32/3/j3D/M9zf2VP2/F/pp64ftZ++uH4S//Zhl0ZzFv5ZfLUt5qfhrbjY3Af6FfLR05AgAA
RABkAAAAAAAAAAIAAAAAAAAAAAAAAAAAtAoXAegD6AMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAA8ABPBCAAAAsgQK8AgAAAAIBAAAAAoAAFMAC/AeAAAABEEIAAAAPwEAAAYAgQERAAAQ
vwEMAB8A/wEAAAgAAAAQ8AQAAAAHAACAMgAH8KMBAAADBC5ltmJwO1bRX9Ny+EzIPBT/AH8BAAAB
AAAA/GEAAAAAbgBgIRvwdwEAAC5ltmJwO1bRX9Ny+EzIPBQ+AgAAAAAAAAAAAAAgEQAAwAEAAGiM
GgBItQIARQEAAAD+eJxjZOBkYGCWZ2RgYGKQYQABViDmZIKxmBgZoSxGpv///4NZeowSUDFDJpgs
N1wHD9MBRgVBISBLjY2fQYrhP0gbgwCQfwDIOgbED4CcNqBGbqgaHgbfxJKMkMqCVAYGA7ArfjMp
/Ac7hmECyAIGFiYGgZDM3NRiBb/UcoWg/NzEPAatprflB9Lflx9h5wpgYOBiYAGq0wWqBvqHwYgr
gbGYnxnIys3MS4WJyHOCRRIrUiF2NPyD2cFIwI6N7FxGCDsYwfQHJLsecINEPANCXGAiPazoIm4M
EBGXMHTbQcEMhALBlblJ+TkMDEAfBSoCbUbyYSCyDyG2MzJwQE3ewgUyQjcAxvdgAfFt2bmg4csF
jgNwQEJDV4CBHczbA441RiYmpeDK4pLUXIby1expBewMXYwg+9iAcjA2us+ZwfoBS7BgrTQGAABE
AGQAAAAAAAAAAgAAAAAAAAAAAAAAAAD3HlAW6APoAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAADwAE8DwAAACyBArwCAAAAAkEAAAACgAAQwAL8BgAAAAEQQkAAACBAREAABC/AQAAEAD/
AQAACAAAABDwBAAAAAgAAIAyAAfwpAUAAAMEPazxE9jWW6EebqKqvFNqDv8AgAUAAAEAAAA1ZAAA
AABuAGAhG/B4BQAAPazxE9jWW6EebqKqvFNqDp4XAAD//wAAAgAAAOYMAQBOCQAAmM9MAPhXNwBG
BQAAAP54nK1YX0wcRRj/9t/s7uzt7VXQHkEqqQWiLQ3yYqs1KaEUq6UibQNKMSIe5ghw9e5oqfHh
HqRNNEaNxhprExqfTGrjg40vPpRotJKSNkaMD2ramNikgZQaXtqK+M3OLpS7Xe4Pu2Rv9ua+/X5/
5tudYQTQAaTLBmBbAewox7OWWLABFvGQ7e+dieSrYWiL9yUTqUR/upp9V7DfEEWMYlchca9+PVSG
V3dFyD6E5sRIMh5LVu+LHcWvMp71AkDEQXrARgL4Dz+xG66HAJ5jtPB6gx29FbsZCrVzsyt96UoQ
2c0qXv0rCg4gRxCYNrgjKnYfi9ro/CLarSRowFV0iQMyVzGr9YXWObyiDq8IDGB4FyJOIeUW2yse
odkRjMp6p+dhx7VKOLCvvb0cLs5Bg+vqLvOIw4860dSOAhBhXlqZk2m3nJ5yO0qGEDB9rsZlvkyL
LJieHkiOBwCEd4uuB/I92tmdUbnSqLJ6xBmF5+GOuXmUpTzu4eYhdjuH+VYi5rou2wwr5a1GpZWh
/WE3s5vHzK0eQV76rBfU5ZG3s5fbsffbd40v8hveF1ztB+JDsRSruOqOxFDvMEArz6I5fL2z8WqL
2q3oVFAjvU3HwyxxB+x0IgQnQlzRrua36qhvMuo81bus3DzZnp2JZGitlX2Xl4ZCdEUcXS9bjGdH
YiQdS+7EUm3Ayt0M1WtUGZWH6fPhKukCyacyX55z+mnzDymj+uXJfocsYKITeOt3eLZp4OPmNu28
+jZCBOUmrxJJe0INqkqe1SY8Gbq6NUc3sXULOT68gAE/YvKHEOhd1c+HUXWdPkkOacH60Kx+rAXl
wztqlSfDQn2YQoCPkPCH+Mp9kfj50ELG6Enlih6sDxFCaVA+dJEPPBkW6sMjOGt9jclvYvuGbz3E
1GvGN2SLEawPDWq/EZQPo+qsJ8NCfdgT4vVgmavXg2CeVPaGgq6H46Hg6sH0ZFioD9tR/wSmWsT2
hO97MqndMr9Xd5jB+vCUdsQMyocxbcGToZ8P3joN6aDRIwb3/PPZ9VeRUsa7qa8vlkq14LzK/mrw
L5/qlez+lK4ZDdKpwNhV2Oy+kKZ1fBhgVzyVTsZfGUnHE8MtOPvX4FmNJ18L8LY4vr/J9caj8kJg
fE2b7+fy45T1NCeSMbZSqUYv/XhlV/sg/vADDsUtBLlMILuqYLmqXEWsbmokEQ7Lk2RGmSTe6xcl
73OWRsQ9CHcboTr0YpBHlTZ9nrTppSJ/Rrjm13FQ3lOLQR4nk2QQVx+lIr+JaLsxaAzbf7RikDPq
M1pGndVKRb6IiMfx7MXAm0VpvqTeUA9ppWuOItR+hJnWi62wB3F9c0XvLLnCfjc48gg+zN8WhXwV
Z9LDodKRM5QjP2YUi7wFkd+ipSNrJkduwvanosZ5B84WIbN05BlELEPEg2GAn4tCbg+vV+fMqdIr
zOLP8+lI0RVmTZJPIqW/wxpR60mE240MeqjfWuFp2mp9qjfm/F9b6luf7ZE00jI6GGY/t3a2QPea
VwvdtA45+v/vnc+JTejEa5h8GzpR77uKjqrbrQGyKWAn/iIvBejEZrUCOXYV7IS30m56KfKlLgS2
K3GfrbSWPmmx/K296djR3mPAVk5sV4K1/muR7LE6q/CxukBWH6sJMkDOKkGP1d9KkGN1BjlezeFY
aNUyB25g0C+Y7ivdz4lT+jTOvLk7Nmtzol+/Q4Jz4px+HjnO++4qeVft8s4kc+auGLGz4ZzFeYvi
xv3HUunYECyh8Xyaxw7svcfKHVvB8WDO4ZN/z7ROWFz0Zsz3vgH+B+iQTqxbDgAARABkAAAAAAAA
AAIAAAAAAAAAAAAAAAAAryGMEegD6AMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8A
BPA8AAAAsgQK8AgAAAAKBAAAAAoAAEMAC/AYAAAABEEKAAAAgQERAAAQvwEAABAA/wEAAAgAAAAQ
8AQAAAAJAACAMgAH8MsNAAADBH9s0dkTxv74v+AiW1PxurL/AKcNAAABAAAAaWoAAAAAbgBgIRvw
nw0AAH9s0dkTxv74v+AiW1PxurJ0LwAAAAAAAAAAAAAJDgAAUAcAABCNUwAghysAbQ0AAAD+eJy9
Wgt0VMUZvnNn5p97977WyGMhOXBBgShGAr4NSBAjhueiQcRGTIxLm0Cykk0IEAoY4TQHowlqBWtV
pMUHooKWAhYU66EtGjFKRQVsoxSkvlhPxXqAks59bGIeG3c32+6e2dk7M3f+7/vmn//OnXuRIAsC
fqWvICjCM0jgn148DQVDGCC08A+xj2cGy+/UhSnFReXBUHBOhWkdU16uiNYZ1j9V9DNZP5f/O22X
tfug8cHK8uJAuTk1UMUPCU8ZyMlFhITe9lnPtziNG2wUJFtIySsuDYSsc8wbg6WFZa1nItuibNvB
PA0QGP/tQywEVpnXZdDHZiDYv2d5OofX+lnkHKuvi5GD3tPKQ279h0TrZKvnMyJyiTj2RUsz4ZRI
7TKr1WC3Bts5RpJ9XgpHZGHy6o5W/dEqV6sa6TbvOS5Kn4vSK6ziJf24qc84gUe5CdltIdktLGB9
3ZLz3LFJFfKm+v29hL+EhczI2F2nLXDRetzWHrsV11r4Frfv01LCcEt62a2IoAoW2wjjNrwWM4K0
LhUhURWhQht368xU8jh5SwzjZuT047SO9ANuP22uE+mHCVpn30Kk9TeDa946fjaOXnZbx7fWtfct
njr5lun0Itu14Si9OT7ja/VcS+FRnmLSX7Sq83KyhCy3DXLbiO3yNqUEARxIYoSh5Oqzhbxr6xNR
JMI/gqujd0/mnCbzyqM8n0GEjv0Lbf1HEEg8H4JFwY/8pJmnjhYiliXXEtiWUCfLjaJj+SSO13KT
6CdhHLvlyPkRn4p40h+MMG7SOyrV1cjFM5oeI5mj+XqXGKON5mHN0fR9PV5NmzU/adITH82dhmN5
hjdey7sNP/F7E7dcx4+/4j50kudHSceYEk1bHxlEPhLC+BkhVm138uM0XrmH5yvjY8jDw25heY8Y
LiFtDKPV73HrY0fWIDT3CNnODsji0WQ5CXPrsVqORaM0F0l8/tcg8GjCRyhZSJZ4HX886o3XH/d6
w3itN1Z/3OR1GG/1xuuPm70m2exNfNQthtaoRxhGq9/qjdcrlnube4RsUwdk8WiynDR7k+ePS9zR
ORp3PFzOY2GzN3F/jNXfetP1tAqHcTR/i7WfJ+l+RcCj5J73s00ScB+I1f8H8jmWylcty/i1rgpi
Udi6Qzkfvydk8bXD9XgMycMXkADuRRbi/+D78VH8FG7Er+GX8CG8Fn+Pf477kkJ8JcnBs0g6XkJU
/AQ5IR4nW8VL6BJxGc0R36TniCfo9+hcaEaXw140C15Gi+EJ9CuoQ9thMXofStA3kI88zI8Gs+vR
1WwMms4uRz9jmWgpuwg9yC5Az7JhaBcbit7j6RhLR5qUgUZJl6KbpWvQIikXPSrNQDulAnRYmotO
SxWon1yNrpCXoRx5Ocrj6S55KVolL0Lr5Qq0Qy5F78gBdETOR4pnIsr0XIXGe0aimz3DUbFnCFrq
GYwe9JjoWZ4OeM5DWBmG+ikXohFKBrpeGYVuU65ElUo2uk/JRRuUPPSaUog+Uuajk8o96Bx1LRqh
bkZj1V3IrzaiIvUQWqB+idaphvi2erl4Ri0QL9LqxHxth3ivdlzcrvnwEW0C/rd2O/boVThNvx9n
6E/hMfouPEnfj2fqn+M79BY8V+9F5usXkAX6GLKIrz8W60Vkob6AVOqryF36Y6RY30IK9T1kpv4R
max/RcbqiI7Ue9Pz9HR6rj6ahrUi+pZWS3+rbaLV2j46XfuapmsKtKhD4UN1DLys+mG9OgtWqwVw
tzoH5qtzoUAtA786H8aq5TCCJ00NwhdKCexVCuFpZSasVCZBtjISBihD4IynHxz0GLDDw2CtR4SF
HgFu8SC4ykMg1eOBM7IX/ib7YLc8CFbKl0CunAPD5SmgyXlwQroVmqTZsEUqgNU8zZduA780C0ZI
N4ImTYQvWDbsZZfBSjYAshnAGQjTg3CM7oCP6Vo4QBdCE70F3qZXQiPty/N/03foB/Q9uo3yOvp3
OoseoVfTYzSNHqdnyXH6KTlG/0Q+oRvJQdpAmug95E1aQd6gM8hWeinZQFPIQ/RrfDdtxKV0I55J
V+FsWoqH0QLcn+ZhjebiFjIWf0OuwEdIJv4rGY73kGF4KxmKN/D0Sz4LVpCLcIiMwneQrDjW352i
NJ+HX/JpCnwGD2WxzNx0OzamCJtRGLagU/ASwmwrUth2lMJ2IR97HaWxP6OBrBGZ7B+iyT4XB7IT
Yhr7l+hj34sp7LSosLMiZi3iKRBwGBJFbkX0fA6zkt8GPBxTzIkgN0kBDCIlMJiEYAiphnRSAxmk
FkaSOriC1MNo0gA30QaYRethNq2DO2gt/JTWQAmthlIagjJaAkFakDDyG8BB/oAUL/LJUABToAT8
EII8qIZboQYKoRaKoQ7KoR6WQAPkSw0wR6qHoFQHVVItLJVqYIVUDbVSCO6VSqBOShx5luwgX6nE
i3ysXADZcgmMl0MwQa6GKXIN5Mm1kC/XQUDmaOUGmKZwzZV6uEOpgxKlFuYrNVClVEO1EoKlPCYs
UxJHPlp3/PxhI14/z9bDME4/BdfqmOXoCrtBT2FTdB+brqexmfpAlq+brMIw2WJjIFtmpLF7DB+r
NVLYvYbC7jcwqzdOQYORuJ9fhB3kffRYkV9nIzeFTD67RuKTcBk+BVfjs3AtxmwyZuwWrLAANlgF
TmErcW/2MPaxjbg/exWnsf14APsnHsh8xGTpmslmagNZqTaA1WhpbI3Wn23UfGyn1ps1ainskGaw
45rCvtUYO6thBvpZULhShn4SvHrijA/zmHSYMw3wsToaE+PWO2fUzAqMZtaTaLiJW/yY580xWe5l
W5aED9BBtg99yPagA+xVtJ/9Hu1jL6HX2Ba0nW1GmxNGlG84iO4z4kVUYBxkJcaHrNw4wBYZ+9nd
xj620niN/cLYzlPsiCL9Onlkx+Ya1szjzKe04wox0R2bAYK1YyOzNLB2MacGKqqC5XPNmwJFFcXB
MiFHGC6k8t9MgXu14BMu48dWSSo/yvzRnZ32yPexMarJnkwa8jE28kfYIXo+/5dTdmcGT2aEQfq1
gcLyQDlnUr6guChgTp920wVZNmpTcHJfJ3amkG3zM+3ksLVqUu1Sq30OLzPj5D2IYX7VeLfTPUai
vPvYvL8EhVi7bVODZRm5fot2jsvO5Bgj3OJDeg3bz68E70vJ9i1D/t/7Vi6Pmw8JyUI+zPWtffbu
9/jKUEWwlDtTblmoonDevEIbfzZHOcRGO8n1F9MtcVgkzuUDr8kGa8nmkq/9/7ncLz2iNrNg0uZ8
hs1llvQs7cf/zQgFyjMqghlWbo4PlpU5nmWmc68aYvMwbdRm67HPZmp9f+hrvi7mdCxo+rloNsoq
/5cXmBcIudEmy+59uGu1LYIkYkVzrSxTrBIrjiUWh5bKp8UmySsmayycvf5ceWISn9yslhHuCmP7
a2VHZivkHXBAeiVpXuYwmyZ/S63qcRMsvXvKbI38NMd4rBPG7pktlY/QJum7pI3ZAHfMMrFhe2x5
aXFZ4TwzZ35l8V0XC1m2t06yZ4Xlvz73Splqz5H4vG2FvE06IC3utJOVKPLe7pj8DiylxxUVBUIh
c8JM+yoy3J5pQ+yr3k96OFI+YtAWcTfeHPXpYdd83+dnDaN7Op2VKF/V5ruOtiDrCfPkcVP5WPTc
Dy12nxm78dqoT9OisfvMGEafT9pzwgi7z/T42LVHNV9c6XkD+VmyUA20UY0WVzHrbsBZVdlLlvHz
gpV3/nBd1bZqyXavIfFeGYeQ1bgKb0tyNA7jb+xoPDU3p5vrQ+S9AecT8Y9onuNxEd9NRmKTCFH2
yj1ReX6uV2Fvkp8wh/FE/cd5xs5slW6SWVHmRDRmWfI87T7pATW5zEBuVJPHbI2sapfLhzph7J5Z
UJ7tfV26MGkr0EE2s6vlOzXrjZ3IpMotqwiUzyksCnRxH+asmEz7Tsz6RtOh4137p9R57tjMBXmZ
CFH4PU4+gTBO3j105K2HNOj5eiEyclvIBxxjtCdBnh/dv3iBOUpsk7pXYrsUxi8kLYJqrhLH7R5N
M3eCzx7PZOjxG470005IY9UDyY4eHk/3eig8tqBOz/F6qkeWnHw9vpPD+LIoTxx/XI+3PY4ebynd
69GohPHbnmTPFKYkc6b8kWNESqxKxNav9Wz4E60Kj4gaOzsqeqvq7NG/rHW/R98WdSM73bPVArhd
LYECNQRFajXMUWtgrloLQbUOKtV6WKw2wGqtAdZo9fBrrQ7WabWwQauBZ7RqeE4LwSatBJ7XOu7R
R+zEurM4iI3TQ2Ak7XoW2afKVRPfp+qo8WPUecMqFbp/o6BN48gO9ZPUT/pAx+d10TXqaPk5ybF8
nRyv5RclPxkrJ255n+JYHqfGa/k9xU9Gq7Fb7tovVsgPyQek9UnbFXTW/tPkw5K19uchMUkRcY1c
z3Hu64Sz+7XOUvlBtUmqTFrEd/aEcuUX7T0he41T5i54Wlc1me3WOx15x65hrrxOsTXk98Gx3PvS
Vg0sHzstem0NBGGnY0MUB9+0KFQRKBXaeVSYXzo7v+H8w0/7N6KRizfsat/9O8lWPgy1tHTli1Z5
hLHT3nnzXBD+C+h1eCxjEwAARABkAAAAAAAAAAIAAAAAAAAAAAAAAAAAHi1NHNICygIAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8ABPBUAAAAsgQK8AgAAAALBAAAAAoAAIMAC/AwAAAA
AAE9HgAAAQHZBgAAAgGzBAAAAwHUHQAABEELAAAAgQERAAAQvwEAABAA/wEAAAgAAAAQ8AQAAAAK
AACAMgAH8LsSAAADBACHTWd7IowAa7Etjd73ljn/AJcSAAABAAAAxHgAAAAAbgBgIRvwjxIAAACH
TWd7IowAa7Etjd73ljnwcwAAAAAAAAAAAAACAwAA4wEAAIjpbwDgM0YAXRIAAAD+eJzdnQt4VNW1
x9c6mRAyPC1IlWdAsAiiBIig4ANK9HI/HxVsCQJCgBACgQQCJbEC4WEJivIGeYkQIEhVaKtoBREo
tdei4WmFzxcCVS8oWC1cQTT3f2afvWYmnNkSana/D/2Gs/Z/1t7nf9bZ58zvnMnMMCUSxX1zM1F1
+iW5/wXwiOOqFI9lNcdV3Ki6c5SdODdKFI2dsrKyUBTgGp7msPt0HB6NQyP9jMvK/FrR/cNjqpGq
4nEupJF4asNECVieh+720yrHyHZ8s+N8XLlj6DX4+dLj/SdHcLelXuAIs9uFGuLxrfN1mdre2ext
eFLXMVnp2QhqxQer/mrBF+MH4LEn89R4t00U9NYQKNd/i9RO9z8dCCZE9nfb4f7xFyxjjCd+/hUI
Voscz22Hx6tykcuA9aXartPl6yx1OhQIVoncLrcd3q6EGMvwPFDj1w7tXV03dpxmvQryxmaMJGoW
H2wUOb7bDo9f1Xce6bVUZD75H0GJoeWXMY478p5lb1Q9Ppc7lsNnBXeUBoEP+bwTT/EX1OJitins
LHpNau3R2+R/rtBbpLY4nvQujd6mRF//NfFojnNgKnWneY77WMGp5D66R1Vw27ZtURWs6FbyRWxl
Mc9z7oATV6/r5HPqD5yR3agO8uY5qkdPr0cdRFprLVpr0eJFixftQ9Lah6S1V0R7RbQ5os0RbYRo
I0TrLppb0x+jYuG5fuG8qKzxV/Ai+O9KeptKDPthBZdIXpC1piJXyxYtW7RS0UpFS3a0liy1nCda
5ddSz3r3KCosLPR6BqOOovD+9a9FtGMdhWdE6g+cnYIU7qPP21r5L8/BTBlvpmj5ouWLliFahmiR
R4rWbhftdtEijx6tXSXaVaJFHlFa+0qOgK9Ia5FHmdZ2ibZLtMgjT2urRVstWuTRqLWJok0ULfII
1Vpv0XqLFnnUai2831ZwD586ay2ypj186tfDp1Y9fOrSw6cGPXy2t4fPtvXw2Y4eMeZa+RkduZ36
LBbWlnGq5PURrY9o2aJli1YoWqFo80WbL1qJaCWibRZts2i7Rdst2hHRjoh2RrQzoukz0jI5I63g
RqI1Ei1ZtGTRUkVLFS1NtDTRskXLFq1QtELR5ok2T7QS0UpE2yzaZtFKRSsV7YhoR0Q7I9oZ0RId
rSXK/m0kWiPRkkVLFq27aN1FSxMtTbRs0bJFmyTaJNHmiabnWrHMtaUy14plbiyVuVEs+3Kp7Mti
qf1SqX2x1Gqp1KpYtm2pbFuxeFlawVeXQLlXl6Dh1eWDSyDEioy/hpc4XalbpY2/CiTgjq8INJow
9asWR712glLLEWrQ24NrqY/htXMr6XPJXtJnkMOkzxsnSc+Is6TPEQE5M9SQ80E9OQs0kvnSWo7u
LjJfesosGSRzI0fmZD7pc910cTVPXC0XV2vF1QZx9TLtli3Srv5C2tVbwkgHSbv6VBjpeyGj2uKq
ibjKFFdjxNXD4mqKuJohrmaLq4Xiapm4Wimu1oqrjeLqNXG1R1x9LJR2Soh3gLjKFFejxNVYcVUg
riaJq2niqkhcPSGu5oirxeJqtbh6SVz9WVztFVcPiquB4mqouBohrnLE1VhxlS+uHhFXheJqqrh6
TFzNF1erxNUGcbVZXPUSV2niqp+4GiiuhoirTHE1XFyNFFe54ipPXOWLq0ni6nFxtSDM2eLqPnHV
U1z9UlyliasHxVV/cTVAXKWLq8HiKkNcZYmrHHGVL64KxdV0uWqKviavixnSR6I0uSJ2zzbhK+Lq
5F7VBqg3Tad+NJMeoifQq8jr9wT196JZlC65A+lJyqB5lIntHESzvIz5NNSLFlGW5A6jp1ChpTSS
FkNd6GUsQVtH2VFXHK4y4gJ3wzFCLq2g0bQczy72Mp9GW0XP0FjJzaOVVEBr6GEqhrrCy1iNtopK
aKLkTqB12GvraTKWE2mtl/Es2joqLOfuWZp0gbuJGGEavUCP0nN4dp2X+TzaKtpAMyS3iDaien9E
1f4AdYOX8Qep4os0V3Ln0Euo8Mu0AMu56KMyNqGto/nl3G3CXinvbi5GeIpeRdX+hGc3eZl/kipu
Rk117jLaQqtoGyq3FeqrXsbraKtoO+azzi2h7dhW97ED8Q7JWBeRG30fJOxpLfKfo7/Q87QzNI7q
sRNtFb1Bv5fcjfRXuP4btuJNqG94GW+iraJdOLJiredVeguj78baSpG1y+tRKm73wIPO3Ul7kXEA
PfZD3eNl7EdbRQcwTqz1lNI7+P8g/Z3eRdYBr8e7aKvoIB2SXDf+iN6nw/QeooNexntoq+h9nBVi
redj+oA+Q+b/YoQjGEP1+AhtFR2mzyX3BLK/omP0NR2Fqkc/iraKjuGcE2s9p+kfdJ4+pe/oE2Qd
83p8graKPgO46NwyrL0Kn6AEPg71My/jONoqOoEzWqz1JPLnVJtP0hX8BbJOeH2/QFtFp6iurKcO
f0n1+StqwP+EesrL/SfaKvqamkhuY/4XtQDXXMunoeotPo22is7QdZLbkv+PbuRz1JbPQtXXQWfR
1lFyTP9t0a8jn6dO/C2yznp9v0VbReepi6ynM39HXbmMuvH3UM97ud+jraIyulNyU5n4bnb4Hma+
k8u8XEZbRQ7fL7m/4DjuzfG4ugpAdbyMgFxtxXM/ye3LVTidq/IgToAa72UkoK2iqjxUcjM4kUdw
NfBfEGpVLyOIdqxquNljuAbncfVQL9WjOto6Gi+j/xp5E7gWT+Sarupl1ERbRbV4iuRO5to8na/g
IiynoI/KqI22iq7gmZL7OP+E53JdXC/WgarnUR25fqzLiyR3IV/Jy7keP43lIvRRGVeiraJ6vEpy
V/JPeR1fzc/yVVDreRlXoa2iq/l5yX2O6/MfuQG/iOXz6KMy6qOtogb8suRu4ob8Gq6qt2L5Muu5
3BBtFTXiHZK7nRvz/3ASv8lNoOor8SZoqyiJ35bct5FXGno0hdpUMkpj7j036wA343ewdHuqHk3R
VlEzPiSjH+Rr+CNuzoexPIQ+KuMatFXUnI9J7lFuwcf5Z3yCr4Xa3Mu4Fm0dnZLck8g7zTgKuSVU
fbS2lCvzlnxOcs8ir4xbMzmtoLb0MlqhraOAo3PjcEUTdNpwNed6qK283OvRVlEbriW5NZ0b+Ern
Rq6HZS2njZd7A9oqupHrS+7VTltOcpK5KZb18YzKaIu2ipK5heQ2d9pxa6c9X49lC0ffM2mHtora
c1vJbYtWcujRAWoH1hnJTswzEbI6OincCUu3p+rRAW0VpXAXGb2zcxN3czryz7HsgmdUxk1o6+gu
yb0Tefc4nfheLO/CMyqjI9oq6sQ9Jfd+52ZOc27hPlj2dPQ58Ga0VXQL95fcfk5nHoSry8FY9scz
KqMz2jrKlNyhyBvp3MqjsMzEMyqjC9oqupXHSO5o5zbOd27nAizH4BmVcRvaKrqdJ0juI84dPNXp
ytOwnIBnVMYdaOuoSHKnI+9JpxvPwrIIz6iMrmirqJvcEdEs5l67+zF3MMa1f7Vy76i5z7gRyzt2
DQIl4PE1GPdS7l0EZT3hUcNrir53obZA31/wfyfvdRD5a0Lvle1F3+Hw97IP/L1HWL2yveh7LP5e
PgZtfyRkXtleTsZ4p0l5OUW/oy+Ewyvbi77P5O/lHL1O3wirV7YXfafL30s876c43m3Ji77X5u+l
Jn9C1fmIJS/6bp+/l5+CZ6/kM5a86PuN/l4agwwbsr52qGwv+o6nv5frOYVbcbIlL/qeq7+XWzmX
OwuFV7YXfdfX30sv3odrjlJLXvR9Z38vgznFSRdCqmwv+s63v5dc5I66xPdIKu4lP8a7BMpLAZhh
vDVmmG5khiIww2+tMYN+/8Hfy3www1xrzLDcyAxPgxmWWWOGtUZmKAEzrLHGDBuMzLARzPCCNWbQ
70P5e3mF9tMmssUM+p2wWOz9CdjbFjPo9+L8vbxB52gn2WIG/W6gv5e3qSbvIlvMoN+P9PdyiFL4
XbLFDPodUX8vn1EuKNMWM+j3ZP29lNE+/o5sMUNtIzNcAWaoZY0ZmhiZIQm5ja0xQ6aRGYaBGYZa
Y4YxRmbIAzOMtsYM+q8D/L38BsxQYI0ZphiZYSqYYbI1ZphhZIbHwAxF1phhtpEZ5oAZZlljhoVG
ZlgEZlhgjRmWGZlhOZhhqTVmWGlkhlVghmesMcNaIzOUgBnWWGOGjUZm+D2YYYM1ZnjNyAxbwQxb
rDHDHiMz7AUz7LbGDPpvtvy9HKEU5zDZYgb9V2P+Xr6kRc7JCn5q4tK9DDAyw0Aww0PWmCHTyAzD
wAxDrTGD/ts9fy85YIaR1phhrJEZxoEZ8qwxQ4GRGR4GM+RbY4ZJRmYoBDNMtMYM04zM8CiYYao1
ZigyMsMMMMN0a8zwhJEZngQzzLTGDHOMzDAXzDDbGjMsNjLDEjDDU9aYYbWRGdaAGYqtMcNLRmbY
BGZ40Roz/NnIDDvBDDusMcNeIzPsAzPsscYMDxqZoS+YoY81ZhhoZIZ0MMMAa8yg/7Le30smmCHD
GjOMMDJDNphhuDVmyDEyQy6YYZQ1ZhhrZIZxYIY8a8yQb2SGAjDDeGvM8IiRGSaAGX5jjRkKjcww
GcwwyRozTDUywzQwwxRrzPCYkRkeBzPMsMYM843MsADMMM8aM6wyMkMxmGGlNWbYYGSGjWCGF6wx
w2YjM2wBM7xqjRl6GZnhATBDT2vMkGZkhj5ght7WmEF/7s3fS38wQ19rzDDQyAzpYIYB1phhiJEZ
MsAMg60xQ6aRGYaBGYZaY4bhRmYYAWbIssYMI43MMArMkG2NGXKNzDAazJBjjRnyjMwwFswwxhoz
5BuZoQDMMN4aM0wyMkMhmGGiNWZ43MgMM8EMj1ljhgVGZlgIZphvjRlWGJnhGTDD09aY4T4jM/wC
zHCvNWboaWSGXmCG+60xg/5Uur+XX4EZHrDGDGlGZugDZuhtjRkeNDJDXzBDH2vM0N/IDA+BGfpZ
Y4YBRmYYCGZ4yBozpBuZYRCYYaA1ZhhsZIYhYIZB1pghw8gMQ8EMQ6wxQ5aRGYaDGYZZY4YcIzPk
ghlGWWOGfCMzFIAZxltjhkIjM0wGM0yyxgzTjcxQBGb4rTVmKDIywwwww3RrzLDEyAzut58stsYM
zxqZwf2uk3XWmGGTkRncbzZ5yRozbDcyww4wwzZrzLDLyAxvgRn+Zo0ZDhiZ4R0ww35rzPC+kRk+
ADO8Z40ZjhmZ4R9ghqPWmOGEkRk+BzMct8YMZ43McA7M8I01ZggaP2tZjXM50dpnLZOMn7Vsyvu4
ibXPWrY3fm6iA6c47ax9bqKb8XMTP3dzLXxuorLG/3e+j/Jixo/+5usLv72/IuuNr8B6B9Ojzt2k
vgc2UTL8v6Pc/SYM9/cn2gXvo7u4A6KWyW2SU9u0vy5p9Lj0UWOzsjOScoYizhiXNSozaUhGdnpB
Usv07Oyk7KxRI/KSej1wT5vk6wLkfot1AlUlFQUQqf8DXivgxWE9+t8EyQtInwRyf4EgEVE1GffH
q5zpe/ntjB+Isfz3ZqLfenvyKe7sc45z936N0N6/jfeEzm/JSSPz3EpXo4RKd2Wuxo+/vu/pFH/q
c3UYrsJxUlVodxlXYT+qsMVYhde9KrS/jKuwGVVYbaxCiVeFDpdxFdaiCrOMVZjrVSHlMq7CbDrJ
BfS2oQqP0O5QFTpexlXIpzOcHmMu1ApVYQjmgqslt0UZ0Os/U4kf/nUf03oTKrDeZvw11+DdvhWp
HapIbd7LVdyK3OAeH1UojtxHVapS6d78Z0fl1d6vBsFQDRZxG3JCs8KdEUrL9bR2Edp/e1r7CO0a
T+sQoX1HSkuJ0P7uaTdFaBs9rWOENsPTOkVogz3t5pBWPaR1oWtDv5WW3LZtaB5XbD9d+ty1u38S
Q9u6nruFvu/O3VKtrA4pKVKj9RzH5ffhes5QWkqk9lcuv1/XcysnpEXlzXTC+9pObWP9etnFrbdK
Bdb7Dj/DW7mT73mhYWj7t/Mt7P5q1b3jRg7KGONeQA3Lyc1zr2Sqh6543GuGyOuhyvdsrtWPv74M
bkoFFPSdl+FfrZsWNy3O+9W62uFfrcsKBJdE/vqa2w7/+hpTaqjGgzHqdYjuxnVoUnZO+hC3zKHr
0zZ5GaPyssZm/TojaWh2zvi8pL4t+iclJZW70kyIuipV16/6X52lNZUT9OLqFL5KDdflS/mNClt7
sfLG9/81Hv0bGdW8dvQvQVX8l+jc1nkneh3BqG3TNQ1vU/m7Hv6/M2bO/+EMv+2J9Of2Vv7iPJ8B
bxnvLRO8ZdXQ6wzR/wNUrQ93ywAAAEQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA0Mnqefm6zhGMggCqAEupCwIAAAAXAAAAEgAA
AHIAYwBhAG4AYQBkAGEAeQBAAGEAdAB0AC4AYwBvAG0AOwAAAODJ6nn5us4RjIIAqgBLqQsyAAAA
bQBhAGkAbAB0AG8AOgByAGMAYQBuAGEAZABhAHkAQABhAHQAdAAuAGMAbwBtADsAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUARABvAGMAdQBt
AGUAbgB0AFMAdQBtAG0AYQByAHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAAAAA4AAIB
////////////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKAAAAAQCAAAA
AAAAAQBDAG8AbQBwAE8AYgBqAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAABIAAgD///////////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAxAAAAagAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP///////////////wAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA////////////////AAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/v8AAAQAAgAAAAAA
AAAAAAAAAAAAAAAAAgAAAALVzdWcLhsQk5cIACss+a5EAAAABdXN1ZwuGxCTlwgAKyz5rlABAAAM
AQAADQAAAAEAAABwAAAADwAAAHgAAAAEAAAAhAAAAAUAAACMAAAABgAAAJQAAAARAAAAnAAAABcA
AACkAAAACwAAAKwAAAAQAAAAtAAAABMAAAC8AAAAFgAAAMQAAAANAAAAzAAAAAwAAADuAAAAAgAA
AOQEAAAeAAAABAAAAElUVQADAAAAACALAAMAAAC4AQAAAwAAAGkAAAADAAAAvf0AAAMAAAAyEQkA
CwAAAAAAAAALAAAAAAAAAAsAAAAAAAAACwAAAAAAAAAeEAAAAQAAABYAAABSZWMgWS4xNTQxICgx
MC8wMy8wMSkADBAAAAIAAAAeAAAABgAAAFRpdGxlAAMAAAABAAAAtAAAAAMAAAAAAAAAIAAAAAEA
AAA4AAAAAgAAAEAAAAABAAAAAgAAAAwAAABfUElEX0hMSU5LUwACAAAA5AQAAEEAAABsAAAABgAA
AAMAAABBAD8AAwAAAAAAAAADAAAAAAAAAAMAAAAFAAAAHwAAABkAAABtAGEAaQBsAHQAbwA6AHIA
YwBhAG4AYQBkAGEAeQBAAGEAdAB0AC4AYwBvAG0AOwAAAAAAHwAAAAEAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQD+/wMK
AAD/////BgkCAAAAAADAAAAAAAAARhgAAABNaWNyb3NvZnQgV29yZCBEb2N1bWVudAAKAAAATVNX
b3JkRG9jABAAAABXb3JkLkRvY3VtZW50LjgA9DmycQAAAAAAAAAAAAAAAAkIc0gJCHRICQRcAAFA
AQACAFwADAAJAEgAZQBhAGQAaQBuAGcAIAAxAAAAMwABAAMkAAUkAQYkAQomAAtGGgANxhQDpwQ0
BsEHBE8IaglpC70MwMDAwBOk4AFAJgBhJAAAAwA1CIEANAACQBEAAgA0AAwACQBIAGUAYQBkAGkA
bgBnACAAMgAAABAAAgAKJgELRhoAE6RAAUAmAQAANAADQBEAAgA0AAwACQBIAGUAYQBkAGkAbgBn
ACAAMwAAABAAAwAKJgILRhoAE6TIAEAmAgAAOgAEADEAAgA6AAwACQBIAGUAYQBkAGkAbgBnACAA
NAAAABYABAAKJgMLRhoAQCYDDcYHARoDAacEwAAAOgAFADEAAgA6AAwACQBIAGUAYQBkAGkAbgBn
ACAANQAAABYABQAKJgQLRhoAQCYEDcYHARoDAacEwAAAOgAGADEAAgA6AAAAGWoAABpqAAAkagAA
LmoAAC9qAACcagAArGoAAOtqAADsagAA/WoAAAZrAAAHawAAEmsAABlrAAAaawAAG2sAAO1rAABh
bAAAqWwAAKpsAAC2bAAAxGwAAPtsAAD8bAAAhG0AABpuAABdbgAAlG4AAPFuAABFbwAAdW8AAI5v
AACVbwAA2W8AABBwAAARcAAAFHEAABVxAABGcgAAR3IAAGJyAADIcgAAhXMAAJ5zAACfcwAApnMA
AOlzAAAsdAAALXQAABB2AAARdgAAEnYAACB2AAAudgAAgHYAANN3AAC3eAAAenoAAHt6AACcegAA
3HoAAKx7AAAXfAAAGXwAAGJ8AAA1fQAAgX0AANh9AADdfQAA8X0AAA9+AAAffgAAIH4AAC9+AAA1
fgAAO34AADx+AABUfgAAWX4AAF5+AABffgAAbH4AAHF+AAB2fgAAd34AAHx+AACBfgAAhn4AAId+
AADxfgAAP38AAF+AAABggAAAZ4AAAGiAAABxgAAAcoAAAH6AAAB/gAAAsoAAALOAAADJgAAAyoAA
AN6AAADfgAAA44AAAOSAAADogAAA6YAAAOyAAADtgAAA8IAAAPGAAADygAAAAYEAAAKBAAADgQAA
ToEAAE+BAABogQAABIMAACaDAABqgwAAa4MAALODAADngwAAv4QAABKFAAAjhQAAYIUAAJ+FAABY
hgAAE4cAAD2HAADXhwAA2YcAACiIAADRiAAA3ogAAFWJAACbiQAA4okAABuKAAAdigAAXooAAGaK
AABnigAAaIoAAHGKAAByigAAc4oAAHyKAAB9igAAhooAAIuKAACOigAAj4oAAJCKAACRigAAkooA
AJOKAACZigAAoIoAAKOKAACmigAAp4oAAKiKAACpigAAqooAAKuKAACsigAArYoAAK6KAACvigAA
sIoAALGKAACyigAAwYoAAMWKAADLigAAzYoAANKKAADdigAA3ooAAN+KAADgigAA4YoAAOKKAADj
igAA5IoAAOWKAADmigAA54oAAPSKAAD1igAA9ooAAPmKAAD6igAA+4oAAP2KAAD+igAA/4oAAACL
AAABiwAAAosAAAOLAAAEiwAABYsAAAaLAAAPiwAAEYsAABuLAAAciwAAHYsAACaLAAAniwAAKIsA
ADOLAAA1iwAAOIsAADuLAAA8iwAAP4sAAEKLAABDiwAAVIsAAFaLAABYiwAAWosAAFuLAABdiwAA
X4sAAGCLAABpiwAAa4sAAG2LAABviwAAcIsAAHKLAAB0iwAAdYsAAImLAACLiwAAjYsAAI+LAACQ
iwAAkosAAJSLAACViwAAlosAAJeLAACYiwAAmYsAAJqLAACbiwAAnIsAAJ2LAACmiwAAqIsAALKL
AACziwAAtIsAAL2LAAC+iwAAv4sAAMqLAADMiwAAz4sAANKLAADTiwAA1osAANmLAADaiwAA64sA
AO2LAADviwAA8YsAAPKLAAD0iwAA9osAAPeLAAAAjAAAAowAAASMAAAGjAAAB4wAAAmMAAAMjAAA
DYwAACGMAAAjjAAAJYwAACeMAAAojAAAKowAACyMAAAtjAAALowAAC+MAAAwjAAAMYwAADKMAAAz
jAAANIwAADWMAABCjAAAQ4wAAESMAABHjAAASIwAAEmMAABLjAAATIwAAE2MAABOjAAAT4wAAFCM
AABRjAAAUowAAFOMAABUjAAAXowAAF+MAABgjAAAZIwAAGWMAABmjAAAaYwAAGqMAABrjAAA4I0A
AKSOAAD3jgAA+I4AADCPAAAxjwAAO48AAEGPAABCjwAAU48AAFaPAAB7jwAAfI8AAJCPAACTjwAA
qY8AAKqPAAC/jwAAwo8AANKPAADTjwAA1I8AANWPAADWjwAA148AAOGPAADkjwAA5Y8AAOaPAADn
jwAAH5IAAISTAACFkwAAhpMAAJCTAACWkwAAl5MAAKiTAACrkwAA0JMAANGTAADokwAA65MAAAGU
AAAClAAAF5QAABmUAABJlAAASpQAAFqUAABclAAAXZQAAF6UAABolAAAa5QAAGyUAABtlAAAbpQA
AG+UAACflAAAPpUAAISVAACMlQAAjZUAAI6VAACXlQAAmJUAAJmVAACilQAAo5UAAKyVAACtlQAA
sJUAALGVAACylQAAs5UAALSVAAC1lQAAu5UAAMGVAADElQAAyJUAAMmVAADKlQAAy5UAAMyVAADN
lQAAzpUAAM+VAADQlQAA0ZUAANKVAADTlQAA1JUAAOOVAADnlQAA7ZUAAO+VAAD0lQAAAJYAAAGW
AAAClgAAA5YAAASWAAAFlgAABpYAAAeWAAAIlgAACZYAAAqWAAAXlgAAGJYAABmWAAAclgAAHZYA
AB6WAAAglgAAIZYAACKWAAAjlgAAJJYAACWWAAAmlgAAJ5YAACiWAAAplgAAMpYAADSWAAA+lgAA
P5YAAECWAABJlgAASpYAAEuWAABWlgAAWJYAAFuWAABelgAAX5YAAGKWAABllgAAZpYAAHeWAAB5
lgAAe5YAAH2WAAB+lgAAgJYAAIKWAACDlgAAjJYAAI6WAACQlgAAkpYAAJOWAACVlgAAl5YAAJiW
AACslgAArpYAALCWAACylgAAs5YAALWWAAC3lgAAuJYAALmWAAC6lgAAu5YAALyWAAC9lgAAvpYA
AL+WAADAlgAAyZYAAMuWAADVlgAA1pYAANeWAADglgAA4ZYAAOKWAADzlgAA9ZYAAPeWAAD5lgAA
+pYAAPyWAAD+lgAA/5YAAAiXAAAKlwAADJcAAA6XAAAPlwAAEZcAABSXAAAVlwAAKZcAACuXAAAt
lwAAL5cAADCXAAAylwAANJcAADWXAAA2lwAAN5cAADiXAAA5lwAAOpcAADuXAAA8lwAAPZcAAEaX
AABIlwAAUpcAAFOXAABUlwAAXZcAAF6XAABflwAAapcAAGyXAABvlwAAcpcAAHOXAAB2lwAAeZcA
AHqXAACLlwAAjZcAAI+XAACRlwAAkpcAAJSXAACWlwAAl5cAAKCXAACilwAApJcAAKaXAACnlwAA
qZcAAKyXAACtlwAAwZcAAMOXAADFlwAAx5cAAMiXAADKlwAAzJcAAM2XAADOlwAAz5cAANCXAADR
lwAA0pcAANOXAADUlwAA1ZcAAOKXAADjlwAA5JcAAOeXAADolwAA6ZcAAOuXAADslwAA7ZcAAO6X
AADvlwAA8JcAAPGXAADylwAA85cAAPSXAAD1lwAA9pcAAPeXAAD4lwAA+ZcAAPqXAAD7lwAA/JcA
AAaYAAAHmAAACJgAAAyYAAANmAAADpgAABGYAAASmAAAu5gAALyYAAD5mAAApZkAAPCZAAD1mQAA
CZoAACeaAAAomgAAN5oAAD6aAAA/mgAAV5oAAF2aAABemgAAa5oAAHGaAABymgAAd5oAAHyaAAB9
mgAAfpoAABObAAAUmwAAMZsAAPmbAAAnnAAAWJ0AAL2dAAACnwAAS6AAAEygAABNoAAATqAAAFqg
AABooAAAm6AAAHOhAAABpQAAb6YAAJ6mAAA3pwAA26cAAEmoAADmqAAANakAAGOpAAA9qgAATawA
ACytAABFrgAAf64AAPivAACWsQAALLMAAFu0AABdtAAAQbUAAN62AACtuAAA6rgAABG6AACnuwAA
r70AAPG9AAB1vgAA/b4AAFm/AADlwAAArMIAAMbCAAA3wwAAf8MAAP7DAABexAAAfsQAAH/FAADC
xQAAOsYAAKLGAAD6xgAAJ8cAAL/IAAACyQAAeckAAOXJAAA+ygAAaMoAACvMAABuzAAA1swAAEfN
AACfzQAAUc8AAMHQAAAk0gAAGNMAAG7TAAAl1AAATNQAAAzWAACC2QAAg9kAAI7ZAACc2QAA1NkA
AOraAABK2wAAb9sAAJfbAAAx3AAARdwAAGXcAACD3AAApNwAAM7cAADi3AAAB90AABbdAAAt3QAA
St0AAFzdAAB+3QAApd0AALjdAADX3QAAEd4AAB3eAAAr3gAAcN4AALTfAACc4gAAg+MAAITjAACW
4wAA3uMAAPLjAAD/4wAAB+QAAAjkAAAY5AAAJOQAADDkAACS5BQAYgAKAAEAaQAPAAMABAAAAAQA
AABcAABA8f8CAFwADAAGAE4AbwByAG0AYQBsAAAAHQAAAAMkAw3GDgAEGgOnBDQGwQfAwMDAE6R4
AGEkAwAgAENKGABPSgAAUUoAAF9IAQRrSOQEbUgJCHNICQh0SAkEXAABQAEAAgBcAAwACQBIAGUA
YQBkAGkAbgBnACAAMQAAADMAAQADJAAFJAEGJAEKJgALRhoADcYUA6cENAbBBwRPCGoJaQu9DMDA
wMATpOABQCYAYSQAAAMANQiBADQAAkARAAIANAAMAAkASABlAGEAZABpAG4AZwAgADIAAAAQAAIA
CiYBC0YaABOkQAFAJgEAADQAA0ARAAIANAAMAAkASABlAGEAZABpAG4AZwAgADMAAAAQAAMACiYC
C0YaABOkyABAJgIAADoABAAxAAIAOgAMAAkASABlAGEAZABpAG4AZwAgADQAAAAWAAQACiYDC0Ya
AEAmAw3GBwEaAwGnBMAAADoABQAxAAIAOgAMAAkASABlAGEAZABpAG4AZwAgADUAAAAWAAUACiYE
C0YaAEAmBA3GBwEaAwGnBMAAADoABgAxAAIAOgAMAAkASABlAGEAZABpAG4AZwAgADYAAAAWAAYA
CiYFC0YaAEAmBQ3GBwEaAwGnBMAAADoABwAxAAIAOgAMAAkASABlAGEAZABpAG4AZwAgADcAAAAW
AAcACiYGC0YaAEAmBg3GBwEaAwGnBMAAADAACABxAAIAMAAMAAkASABlAGEAZABpAG4AZwAgADgA
AAAMAAgACiYHC0YaAEAmBwAAOgAJADEAAgA6AAwACQBIAGUAYQBkAGkAbgBnACAAOQAAABYACQAK
JggLRhoAQCYIDcYHARoDAacEwAAAPABBQPL/oQA8AAwAFgBEAGUAZgBhAHUAbAB0ACAAUABhAHIA
YQBnAHIAYQBwAGgAIABGAG8AbgB0AAAAAAAAAAAAAAAAADYA/k8BAAIBNgAMAAkAQQBuAG4AZQB4
AF8AUgBlAGYAAAASAA8AAyQBBSQBBiQBE6QAAGEkAQAAQgD+TwEAEgFCAAwACwBBAG4AbgBlAHgA
XwBUAGkAdABsAGUAAAAWABAAAyQBBSQBBiQBE6RQABSkFABhJAEDADUIgQA8AP5PAQACADwADAAS
AE4AbwByAG0AYQBsACAAYQBmAHQAZQByACAAdABpAHQAbABlAAAABgARABOkQAEAADoA/k8BAPIA
OgAMAAcAQQBuAG4AZQB4AF8AIwAAABYAEgADJAEFJAEGJAETpOABFKRQAGEkAQMAOwiBADgAFEBB
ATIBOAAMAAUAVABPAEMAIAAyAAAAEgATAA+E8AATpAAAFKQAAF6E8AAJADUIgToIgTsIgQBAABNA
AQBCAUAADAAFAFQATwBDACAAMQAAABkAFAADJAANxgoEGgOnBDQGwQcAFKR4AGEkAAAKADUIgTsI
gUNKFAAsABVAMQFSASwADAAFAFQATwBDACAAMwAAAAoAFQAPhOABXoTgAQYANgiBOgiBKgAQAAEA
AgAqAAwABwBJAG4AZABlAHgAIAA3AAAACgAWAA+EogZehKIGAAAqAA8AAQACACoADAAHAEkAbgBk
AGUAeAAgADYAAAAKABcAD4SHBV6EhwUAACoADgABAAIAKgAMAAcASQBuAGQAZQB4ACAANQAAAAoA
GAAPhGwEXoRsBAAAKgANAAEAAgAqAAwABwBJAG4AZABlAHgAIAA0AAAACgAZAA+EUQNehFEDAAAq
AAwAAQACACoADAAHAEkAbgBkAGUAeAAgADMAAAAKABoAD4Q2Al6ENgIAACoACwABAAIAKgAMAAcA
SQBuAGQAZQB4ACAAMgAAAAoAGwAPhBsBXoQbAQAAIgAKQAEAAgAiAAwABwBJAG4AZABlAHgAIAAx
AAAAAgAcAAAAJgAoQKIA0QEmAAwACwBMAGkAbgBlACAATgB1AG0AYgBlAHIAAAAAAC4AIQABAMIB
LgAMAA0ASQBuAGQAZQB4ACAASABlAGEAZABpAG4AZwAAAAIAHgAAAEgAIEABAPIBSAAMAAYARgBv
AG8AdABlAHIAAAAiAB8AAyQADcYTBBoDpwQ0BsEHA4sDVSIYJgACAhOkAABhJAAHADUIgUNKFgAA
PAAfQAEAAgI8AAwABgBIAGUAYQBkAGUAcgAAABkAIAADJAENxgoEGgOnBDQGwQcAE6QAAGEkAQAE
AENKFgA8ACZAogARAjwADAASAEYAbwBvAHQAbgBvAHQAZQAgAFIAZQBmAGUAcgBlAG4AYwBlAAAA
CABDShAARUgGAE4AHQABACICTgAMAA0ARgBvAG8AdABuAG8AdABlACAAVABlAHgAdAAAAB0AIgAF
JAENxgUAAQABwA+E/wARhAH/XoT/AGCEAf8ABABDShYANgAcAAEAMgI2AAwADQBOAG8AcgBtAGEA
bAAgAEkAbgBkAGUAbgB0AAAACgAjAA+EGgNehBoDAABwAP5PAQBCAnAADAAKAFQAYQBiAGwAZQBf
AFQAZQB4AHQAAABFACQAAyQADcYyAxoDpwQ0Bg4cATcCUwNuBIoFpQbBB9wI+AkTCy8MSg1mDoEP
AAAAAAAAAAAAAAAAAAATpCgAFKQoAGEkAAAEAENKFgBCAP5PAQBCAkIADAALAFQAYQBiAGwAZQBf
AFQAaQB0AGwAZQAAABYAJQADJAEFJAEGJAETpOABFKR4AGEkAQMANQiBADgA/k8BAGICOAAMAAgA
ZQBuAHUAbQBsAGUAdgAxAAAAFgAmAA+EGgMRhOb8E6RQAF6EGgNghOb8AAA0AP4PYQJyAjQADAAI
AGUAbgB1AG0AbABlAHYAMgAAABIAJwAPhKcEEYRz/l6EpwRghHP+AAAsAP4PcQKCAiwADAAIAGUA
bgB1AG0AbABlAHYAMwAAAAoAKAAPhDQGXoQ0BgAAPgD+T0ECkgI+AAwACgBUAGEAYgBsAGUAXwBI
AGUAYQBkAAAAEAApAAMkAROkUAAUpFAAYSQBBwA1CIFDShYAAH4A/k8BAKICfgAMAA0ARgBpAGcA
dQByAGUAXwBMAGUAZwBlAG4AZAAAAE4AKgAGJAENxjIDGgOnBDQGDhwBNwJTA24EigWlBsEH3Aj4
CRMLLwxKDWYOgQ8AAAAAAAAAAAAAAAAAAA+EHAERhOT+E6QoAF6EHAFghOT+BABDShQAOgD+DwEA
wgI6AAwACABGAGkAZwB1AHIAZQBfACMAAAATACsAAyQBBiQBE6TgARSkeABhJAEAAwA7CIEAOAD+
D1ECAgA4AAwADABGAGkAZwB1AHIAZQBfAFQAaQB0AGwAZQAAAA0ALAAGJAATpHgAFKTgAQAAACgA
/k8hAeICKAAMAAoAQQBwAHAAZQBuAGQAaQB4AF8AIwAAAAIALQAAACwA/k/xAPICLAAMAAwAQQBw
AHAAZQBuAGQAaQB4AF8AUgBlAGYAAAACAC4AAAAwAP5PAQESATAADAAOAEEAcABwAGUAbgBkAGkA
eABfAFQAaQB0AGwAZQAAAAIALwAAADQA/g8BABIDNAAMAAkAUgBlAGYAXwBUAGkAdABsAGUAAAAM
ADAAAyQBE6TgAWEkAQMAOwiBADQA/k8BABIDNAAMAAgAUgBlAGYAXwBUAGUAeAB0AAAAEgAxAA+E
GgMRhOb8XoQaA2CE5vwAADwA/k8BACIDPAAMAAgARQBxAHUAYQB0AGkAbwBuAAAAGQAyAAMkAA3G
DgOnBDQGwQcCDBMYJsHCYSQAAAAAMAD+DwEAMgMwAAwABABIAGUAYQBkAAAAFgAzABOkAAANxg0E
GgOnBDQGwQcBBxrAAAA8AP5PAQBCAzwADAAJAFIAZQBjAF8AVABpAHQAbABlAAAAEgA0AAMkAQUk
AQYkAROk8ABhJAEGADUIgTsIgTAA/g8BAAIAMAAMAAQAYwBhAGwAbAAAABEANQAGJAEPhBoDE6Sg
AF6EGgMAAwA2CIEAMgD+TwEAQgMyAAwABQBSAGUAYwBfACMAAAASADYAAyQABSQBBiQBE6TgAWEk
AAMANQiBADgA/g8BAEIBOAAMAAUAdABvAGMAIAAwAAAAGAA3AAMkAA3GDQQaA6cENAbBBwFtJsJh
JAADADUIgQBAAC8AAQCCA0AADAAEAEwAaQBzAHQAAAAlADgADcYQBBoDpwQ0BsEHAqUGTwjAwA+E
TwgRhLH3XoRPCGCEsfcAAABGAP5PAQCSA0YADAAHAEkAbgBmAG8AZABvAGMAAAAmADkADcYNBBoD
pwQ0BsEHAYoFwA+EigURhHb6E6QAAF6EigVghHb6AABIAP4PAQCiA0gADAAEAFAAYQByAHQAAAAp
ADoADcYQBBoDpwQ0BsEHAvwEpQbAwA+EpQYRhFv5E6TIAF6EpQZghFv5AAMAOwiBAD4A/g8BALID
PgAMAAcAQQBkAGQAcgBlAHMAcwAAAB0AOwANxhAEGgOnBDQGwQcC1BKZFcDAD4QaA16EGgMAAAAu
AP4PEQACAC4ADAAJAGgAZQBhAGQAaQBuAGcAIAAwAAAACQA8ABOk8ABAJgkAAAA+AP4PAQDSAz4A
DAAIAEsAZQB5AHcAbwByAGQAcwAAABsAPQANxgYCpwQ0BgAPhBoDEYTm/F6EGgNghOb8AAAAYgD+
DwEA4gNiAAwADwBFAHEAdQBhAHQAaQBvAG4AXwBMAGUAZwBlAG4AZAAAADIAPgADJAANxhMEGgOn
BDQGwQcD+wWlBtwIwsDAD4SlBhGEW/kTpFAAXoSlBmCEW/lhJAAAAEYA/g8BAPIDRgAMAAUAUQBs
AGkAcwB0AAAAJQA/AA3GEAQaA6cENAbBBwIzB9wIwMAPhNwIEYQk916E3AhghCT3AAMANQiBAC4A
/g8xAzIDLgAMAAcAbQBlAGUAdABpAG4AZwAAAA4AQAAUpDACDcYFAAHLHAAAADYAJ0CiABEENgAM
ABEAQwBvAG0AbQBlAG4AdAAgAFIAZQBmAGUAcgBlAG4AYwBlAAAABABDShAAMgD+DwEAEgAyAAwA
BwBSAGUAYwBfAFIAZQBmAAAADgBCAAMkAQUkAQYkAWEkAQMANgiBACAA/k8BADIEIAAMAAQATgBv
AHQAZQAAAAIAQwAEAENKFgAmAClAogBBBCYADAALAFAAYQBnAGUAIABOAHUAbQBiAGUAcgAAAAAA
MAAeAAEAUgQwAAwADABDAG8AbQBtAGUAbgB0ACAAVABlAHgAdAAAAAIARQAEAENKFABQAP5PAQBi
BFAADAALAFIAZQBjAF8AQwBDAEkAVABUAF8AIwAAAB8ARgADJAAFJAEGJAENxgoEGgOnBDQGwQcA
E6QAAGEkAAAHADUIgUNKFAAAQAD+T6IAcQRAAAQACQBBAFMATgAxAF8AdwBvAHIAZAAAAB4AQioC
Q0oWAE9KAABRSgAAa0jkBG1IAARuSAAEdQgBagD+DwEAggRqAAwADABBAFMATgAxAF8AQwBvAG0A
bQBlAG4AdAAAADcASAADJAANxigEGgOnBDQGwQcKNwJuBKUG3AgTC0oNgQ+4Ee8TJhbAwMDAwMDA
wMDAE6TIAGEkAAAHADYIgUNKFgAAOgA+AAEAAgA6AAwABQBUAGkAdABsAGUAAAAZAEkAAyQBDcYO
AAQaA6cENAbBBwAAAABhJAEAAwA1CIEAZgD+DwEAogRmAAQABQBBAFMATgAuADEAAAA3AEoAAyQA
DcYoBBoDpwQ0BsEHCjcCbgSlBtwIEwtKDYEPuBHvEyYWwMDAwMDAwMDAwBOkAABhJAAAEgA1CIFD
ShQAbUgABG5IAAR1CAEuABYAUQGyBC4ADAAFAFQATwBDACAANAAAAAoASwAPhNACXoTQAgcANgiB
Q0oSAAAuABcAUQHCBC4ADAAFAFQATwBDACAANQAAAAoATAAPhMADXoTAAwcANgiBQ0oSAAAuABgA
UQHSBC4ADAAFAFQATwBDACAANgAAAAoATQAPhLAEXoSwBAcANgiBQ0oSAAAuABkAUQHiBC4ADAAF
AFQATwBDACAANwAAAAoATgAPhKAFXoSgBQcANgiBQ0oSAAAuABoAUQHyBC4ADAAFAFQATwBDACAA
OAAAAAoATwAPhJAGXoSQBgcANgiBQ0oSAAAuABsAUQECBS4ADAAFAFQATwBDACAAOQAAAAoAUAAP
hIAHXoSABwcANgiBQ0oSAACcADkAAQASBZwADAANAEwAaQBzAHQAIABCAHUAbABsAGUAdAAgADUA
AABwAFEACiYKC0b/Bw+EhwURhOX+PsZU/wEACAAAAgAAAAEAGwEAAAAAAAC38AAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAXoSHBWCE
5f4AAFwA/g8BABIAXAAMAA0AUwBlAGMAdABpAG8AbgBfAFQAaQB0AGwAZQAAACAAUgADJAAHJAEN
xgoEGgOnBDQGwQcAD4SKBV6EigVhJAAQAENKIABPSgIAUUoCAGtI5AQ2AP4PAQAiADYADAAJAEMA
aABhAHAAdABlAHIAXwAjAAAACQBTAAckAROk4AEABwA7CIFDShwAADgAWQABAEIFOAAMAAwARABv
AGMAdQBtAGUAbgB0ACAATQBhAHAAAAAGAFQALUQgAQgAT0oFAFFKBQBaAP5PAQBSBVoADAANAGEA
YgBiAHIAZQB2AGkAYQB0AGkAbwBuAHMAAAAWAFUAE6QAAA3GDQQaA6cENAbBBwHwAwAXAENKFABP
SgIAUUoCAG1ICQRzSAkEdQgAAGgA/k8BAAIAaAAMABAAYQB0AHQAYQBjAGgAbQBlAG4AdAAgAHQA
aQB0AGwAZQAAACAAVgADJAEGJAENxgoEGgOnBDQGwQcAE6QAABSkyABhJAEWADUIgU9KAgBRSgIA
bUgJBHNICQR1CABIAP5PYQViBUgADAAUAGEAdAB0AGEAYwBoAG0AZQBuAHQAIABzAHUAYgB0AGkA
dABpAGwAZQAAAAYAVwAUpCwBBwA1CIFDShQAAEQA/g9hBXIFRAAMABIAQQB0AHQAYQBjAGgAbQBl
AG4AdAAgAGgAZQBhAGQAaQBuAGcAAAANAFgAByQBE6RYAhSkAAAAAABOAFBAAQCSBU4ADAALAEIA
bwBkAHkAIABUAGUAeAB0ACAAMgAAABkAWQADJAANxgoEGgOnBDQGwQcAE6QAAGEkAAALAG1ICQRz
SAkEdQgAACwAQkABAKIFLAAMAAkAQgBvAGQAeQAgAFQAZQB4AHQAAAACAFoABgA1CIE2CIFaAP5P
oQWyBVoADAAOAEUAZABpAHQAbwByACcAcwAgAE4AbwB0AGUAOgAAABoAWwAOhNACD4TQAhOk8AAU
pHgAXYTQAl6E0AISADUIgUNKHABtSAkEc0gJBHUIAFwALgABAAIAXAAMAAsAVABPAEEAIABIAGUA
YQBkAGkAbgBnAAAAIwBcACokAROkAAAUpFAADcYTBBoDpwQ0BsEHAzD9KCOQJAAAAgAPAENKFABt
SAkEc0gJBHUIAABSAEMAAQDSBVIADAAQAEIAbwBkAHkAIABUAGUAeAB0ACAASQBuAGQAZQBuAHQA
AAAcAF0AAyQAD4SABBGEgPsUpKAAXoSABGCEgPthJAAEAECI/f9cACJAAQACAFwADAAHAEMAYQBw
AHQAaQBvAG4AAAArAF4AAyQBDcYKBBoDpwQ0BsEHABSk8AAYhPz/GYQBABsmICMkAS+EuwBhJAEA
DwBDShQAbUgJBHNICQR1CAAAKABVQKIA8QUoAAwACQBIAHkAcABlAHIAbABpAG4AawAAAAYAPioB
QioCMAD+TwEAwgIwAAwABgBGAGkAZwB1AHIAZQAAABIAYAADJAEFJAEGJAEUpHgAYSQBAABMAP5P
AQASBkwADAANAEwAaQBzAHQAXwBiAHUAbABsAGUAdABfADEAAAAcAGEAAyQACiYAC0YYAA3GCgQa
A6cENAbBBwBhJAAEAENKFgAAAAAAJwAAAMD7AAABAAAAAAAAAAAA/////wIEAAAAAAAA/////wAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAnAAAAKgAAAAAAAAAACP//AAAAAAAAAAAHAgAAigMAAJMIAAD5
DQAA+g0AAE6gAADA+wAADAAAFgIAAAD/////DAA0FgIAAAD/////DABoFgIAAAD/////DACfFgIA
AAD/////DADWFgIAAAD/////DAAKFwIAAAD/////DABBFwIAAAD/////AAAAADkAAABoAAAAoAAA
AKEAAADMAAAAzQAAANwAAADdAAAA8QAAAPcAAAAJAQAACgEAABoBAAAbAQAAkgEAAKYBAACvAQAA
8QEAAPIBAAAGAgAABwIAAAkCAAALAgAADAIAADQCAAA1AgAANgIAADcCAAA4AgAAPgIAAEUCAABG
AgAAeAIAAIkCAACKAgAAiwIAAIwCAACNAgAAjgIAAI8CAAC7AgAAvAIAAL0CAAC+AgAA9AIAAPUC
AAAZAwAAPQMAAIkDAACKAwAAqAMAAKkDAADeAwAA3wMAAOcDAAASBQAAOAgAADkIAABACAAAkAgA
AJEIAACSCAAAkwgAAJwIAADUCAAAAQkAADEJAACMCQAAzQkAAAsKAAA7CgAAjgoAANgKAAASCwAA
XgsAAMgLAAAfDAAATwwAAJQMAADuDAAANQ0AAJ8NAADbDQAA9w0AAPgNAAD5DQAA+g0AABAOAABF
DgAASw4AAAgTAABnEwAAWxQAAGYUAAAxFgAAbBYAAMYWAABjFwAAtxcAADsYAADHGAAANBkAANsZ
AABBGgAAQhoAAFAaAACGGgAApRoAALsaAADRGgAA6hoAAP8aAAATGwAAJxsAAEIbAABXGwAAhxsA
ALQbAADMGwAA5RsAAAAcAAASHAAANhwAAFYcAAB3HAAAnBwAALEcAADQHAAA6xwAAAUdAAAtHQAA
Ux0AAG0dAACLHQAAqR0AAAAeAABCHgAAlR4AAKoeAADOHgAA+h4AACIfAABaHwAAbx8AAIIfAACf
HwAAvB8AANofAADzHwAAGyAAADEgAABVIAAAeyAAAJcgAACuIAAAtyAAAM8gAADyIAAAEyEAADUh
AABPIQAAXyEAAGwhAACcIQAAySEAABUiAABwIgAAhSIAAKciAADKIgAA3iIAAO8iAAAKIwAAIyMA
ACQjAAByIwAAgyQAAIsmAADMKQAA5SoAAG8sAACaLQAAmy0AALotAAB9LwAAri8AABQxAADZMQAA
fzIAADg0AABaNAAAQTUAAEE4AABDOAAAkjgAAPQ5AAAjOgAAjToAABg7AAC8OwAADDwAAF48AABO
PQAAWj0AAIo+AAC3PgAAeT8AAPo/AABPQQAAy0QAAOhFAAAYRgAA20YAAFBHAACsRwAAcUgAALVI
AADESgAA4EoAAHNNAACXTQAAGU8AAOxPAABYUAAAWVAAAGlQAACxUAAAslAAALNQAAC/UAAAwFAA
AN5QAAAGUQAADlEAAA9RAAAXUQAAGVEAABpRAAAiUQAAI1EAACtRAAAsUQAANFEAADVRAAA9UQAA
S1EAAExRAABRUQAAd1EAAH1RAACDUQAAiVEAAI9RAACTUQAAlVEAAJZRAACbUQAA51EAAPVRAAAD
UgAABVIAAAdSAAAJUgAAC1IAAAxSAAARUgAAPFIAAExSAABcUgAAY1IAAGpSAABxUgAAc1IAAHRS
AAB5UgAAhVIAAJVSAACXUgAAmFIAAKdSAACoUgAAglQAAINUAAALVQAADFUAAHNVAAB0VQAA11YA
ANhWAADZVgAAYlcAACBaAACLWgAAi1sAAENcAADXXAAA2FwAANlcAAD7XAAAeWAAAE9hAABnYQAA
ymEAANphAAD2YQAAAGIAABhiAAAoYgAAO2IAADxiAAA+YgAAd2IAALRiAADVYgAA1mIAANhiAAAO
YwAAD2MAADZjAAA3YwAAOWMAAGtjAACJYwAAqmMAAKtjAACtYwAAzGMAAM1jAAD0YwAA9WMAAPdj
AAA2ZAAAUGQAAF9kAABgZAAAYmQAAJNkAAC0ZAAAw2QAAMRkAADFZAAADGUAAGRlAAB8ZQAAWWYA
AIRmAAAFZwAABmcAABFnAAAfZwAAQWcAAEJnAAAUaQAAFWkAALRpAADCaQAA1GkAAOZpAAD1aQAA
9mkAAPhpAAACagAADGoAABZqAAAXagAAk+QAALTkAAC15AAAtuQAAMjkAAAq5QAAS+UAAEzlAABv
5QAAcOUAAHHlAACF5QAAhuUAAIflAACI5QAAleUAAKPlAADR5QAAg+YAAEfoAABt6gAAz+0AAHHv
AADF7wAAxu8AAMfvAADV7wAA4+8AAPDvAAAf8AAAWvAAAJDwAADC8AAAD/EAAD7xAACB8QAAp/EA
AO3xAAAe8gAATvIAAH7yAADh8gAAGPMAAEDzAABn8wAAk/MAAMXzAAD08wAAXPQAAJn0AAAT9QAA
ZfUAAKv2AABV9wAAVvcAAGL3AABw9wAArfcAABT4AABt+QAAcPoAAHH6AACU+gAAlfoAAK36AADA
+gAAwfoAAFD7AABR+wAAUvsAAFP7AABU+wAAVfsAAFb7AABX+wAAWvsAAFv7AABu+wAAb/sAAHT7
AACE+wAAhfsAAJX7AACX+wAAmPsAAJn7AACa+wAAovsAAL37AADB+wAAmAAAAAAAAAAAAAAAAIAA
AACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACA
mAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAA
AAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAA
AAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAADkAAAAAAAAAAIAAAACAmAAAADkAAAAA
AAAAAIAAAACAmAAAADkAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAA
AIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAA
AACAmAAAYAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAqQAAABEAAAAAAAAAAIAAAACA
qQAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAmAAA
AAAwAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAqQAAAAAA
AAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAmAAAAAAwAAAAAAAA
AIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAA
AACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACA
mAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACACAAAAAAAAAAAAAAAAIAAAACAmAAA
AAAAAAAAAAAAAIC+AgAAmAAAAAAAAAAAAAAAAIC+AgAAmAAAAAAAAAAAAAAAAIC+AgAAmAAAAAAA
AAAAAAAAAIC+AgAAmAAAYEYAAAAAAAAAAIC+AgAAqQAAAEYAAAAAAAAAAIC+AgAAqQAAAEYAAAAA
AAAAAIC+AgAAqQAAADQAAAAAAAAAAIC+AgAAmQAAAAAwAAAAAAAAAIC+AgAAqQAAAAAwAAAAAAAA
AIC+AgAAqQAAAAAwAAAAAAAAAIC+AgAAqQAAAAAwAAAAAAAAAIC+AgAAmQAAAAAwAAAAAAAAAIC+
AgAAqQAAAAAwAAAAAAAAAIC+AgAAqQAAAAAwAAAAAAAAAIC+AgAAmQAAAAAwAAAAAAAAAIC+AgAA
mAAAAAAwAAAAAAAAAIC+AgAAmAAAYAAAAAAAAAAAAIC+AgAACAAAAAAAAAAAAAAAAIAAAACAkAAA
ABQwAAAAAAAAAICTCAAAkAAAABQwAAAAAAAAAICTCAAAkAAAABQwAAAAAAAAAICTCAAAkAAAABQw
AAAAAAAAAICTCAAAkAAAABQwAAAAAAAAAICTCAAAkAAAABMwAAAAAAAAAICTCAAAkAAAABMwAAAA
AAAAAICTCAAAkAAAABUwAAAAAAAAAICTCAAAkAAAABUwAAAAAAAAAICTCAAAkAAAABQwAAAAAAAA
AICTCAAAkAAAABQwAAAAAAAAAICTCAAAkAAAABMwAAAAAAAAAICTCAAAkAAAABMwAAAAAAAAAICT
CAAAkAAAABQAAAAAAAAAAICTCAAAkAAAABQAAAAAAAAAAICTCAAAkAAAABQAAAAAAAAAAICTCAAA
kAAAABQAAAAAAAAAAICTCAAAkAAAABQAAAAAAAAAAICTCAAAkAAAABQAAAAAAAAAAICTCAAAkAAA
ABQAAAAAAAAAAICTCAAAkAAAABQAAAAAAAAAAICTCAAACAAAYDYAAAAAAAAAAIAAAACACAAAYDYA
AAAAAAAAAIAAAACACAAAADYAAAAAAAAAAIAAAACACAAAADQAAAAAAAAAAIAAAACACAAaIAEAAAAA
AAAAAIAAAACAmAAAAAAAAAAAAAAAAIBFDgAAmAAAAAAAAAAAAAAAAIBFDgAAmAAAAAAAAAAAAAAA
AIBFDgAACAAaIAEAAQAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIBbFAAAmAAAADEAAAAAAAAAAIBb
FAAAmAAAADEAAAAAAAAAAIBbFAAAmAAAADEAAAAAAAAAAIBbFAAAmAAAADEAAAAAAAAAAIBbFAAA
mAAAADEAAAAAAAAAAIBbFAAAmAAAADEAAAAAAAAAAIBbFAAAmAAAADEAAAAAAAAAAIBbFAAAmAAA
ADEAAAAAAAAAAIBbFAAAmAAAADEAAAAAAAAAAIBbFAAAmAAAADEAAAAAAAAAAIBbFAAACAAaIAEA
AgAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAA
AAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAA
AIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBC
GgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAA
mAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAA
AFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUA
AAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAA
AAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAA
AIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBC
GgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAA
mAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAA
AFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUA
AAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAA
AAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAA
AIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBC
GgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAA
mAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAA
AFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUA
AAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAA
AAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAA
AIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBC
GgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAAmAAAAFUAAAAAAAAAAIBCGgAA
CAAaIAEAAwAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAkIwAAmAAAAAAAAAAAAAAAAIAkIwAAmAAA
AAAAAAAAAAAAAIAkIwAAmAAAAAAAAAAAAAAAAIAkIwAAmAAAAAAAAAAAAAAAAIAkIwAAmAAAAAAA
AAAAAAAAAIAkIwAAmAAAAAAAAAAAAAAAAIAkIwAACAAaIAEABAAAAAAAAIAAAACAmAAAAAAAAAAA
AAAAAICbLQAAGAEaIAIAAAAAAJstAACbLQAAmAAAAAAAAAAAAAAAAIB9LwAAmAAAAAAAAAAAAAAA
AIB9LwAAmAAAAAAAAAAAAAAAAIB9LwAAmAAAAAAAAAAAAAAAAIB9LwAAGAEaIAIAAQAAAJstAACb
LQAAmAAAAAAAAAAAAAAAAIA4NAAAmAAAAAAAAAAAAAAAAIA4NAAAmAAAAAAAAAAAAAAAAIA4NAAA
kAAAAF4wAAAAAAAAAIA4NAAAkAAAAAAAAAAAAAAAAIA4NAAAkAAAAAAAAAAAAAAAAIA4NAAAkAAR
IAAAAAAAAAAAAIA4NAAAkAARIAAAAQAAAAAAAIA4NAAAkAARIAAAAgAAAAAAAIA4NAAAkAARIAAA
AwAAAAAAAIA4NAAAkAARIAAABAAAAAAAAIA4NAAAkAARIAAABQAAAAAAAIA4NAAAGAEaIAIAAgAA
AJstAACbLQAAmAAAAAAAAAAAAAAAAIBOPQAAKAIaIAMAAAAAAE49AABOPQAAmAAAAAAAAAAAAAAA
AICKPgAAmAAAAAAAAAAAAAAAAICKPgAAmAAAAAAAAAAAAAAAAICKPgAAmAAAAAAAAAAAAAAAAICK
PgAAmAAAAAAAAAAAAAAAAICKPgAAKAIaIAMAAQAAAE49AABOPQAAmAAAAAAAAAAAAAAAAIDoRQAA
mAATIAAAAAAAAAAAAIDoRQAAmAATIAAAAQAAAAAAAIDoRQAAmAATIAAAAgAAAAAAAIDoRQAAmAAT
IAAAAwAAAAAAAIDoRQAAmAAAAAAAAAAAAAAAAIDoRQAAKAIaIAMAAgAAAE49AABOPQAAmAAAAAAA
AAAAAAAAAIDESgAAKAIaIAMAAwAAAE49AABOPQAAmAAAAAAAAAAAAAAAAIBzTQAAmAAAAAAAAAAA
AAAAAIBzTQAAmAAAAEMAAAAAAAAAAIBzTQAAmAAAAAAAAAAAAAAAAIBzTQAAmAAAACkAAAAAAAAA
AIBzTQAAmAAAACUAAAAAAAAAAIBzTQAAqQAAAAAAAAAAAAAAAIBzTQAAqQAAAAAAAAAAAAAAAIBz
TQAAqQAAABAAAAAAAAAAAIBzTQAAmQAAAAAwAAAAAAAAAIBzTQAAqQAAAA8wAAAAAAAAAIBzTQAA
qQAAAA8wAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAA
AAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAw
AAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAA
AAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAA
AIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAmQAAAAAwAAAAAAAAAIBzTQAAqQAAABAwAAAAAAAAAIBz
TQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAA8wAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAA
qQAAAA8wAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAABAwAAAAAAAAAIBzTQAAqQAA
AAAwAAAAAAAAAIBzTQAAmQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAw
AAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAA
AAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAA
AIBzTQAAmQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBz
TQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAA
qQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAmQAA
AAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAqQAAAAAw
AAAAAAAAAIBzTQAAqQAAAAAwAAAAAAAAAIBzTQAAmQAAAAAwAAAAAAAAAIBzTQAAqQAAAEMwAAAA
AAAAAIBzTQAAmQAAAAAwAAAAAAAAAIBzTQAAqQAAACQwAAAAAAAAAIBzTQAAmQAAAAAwAAAAAAAA
AIBzTQAAqQAAACQwAAAAAAAAAIBzTQAAmQAAAAAwAAAAAAAAAIBzTQAAqQAAACQwAAAAAAAAAIBz
TQAAmQAAAAAwAAAAAAAAAIBzTQAAqQAAACQwAAAAAAAAAIBzTQAAmQAAAAAwAAAAAAAAAIBzTQAA
mAAAACQwAAAAAAAAAIBzTQAAmAAAACQAAAAAAAAAAIBzTQAAqQAAAEMAAAAAAAAAAIBzTQAAqQAA
AEMAAAAAAAAAAIBzTQAAqQAAAEMAAAAAAAAAAIBzTQAAqQAAAEMAAAAAAAAAAIBzTQAAqQAAAEMA
AAAAAAAAAIBzTQAAqQAAAEMAAAAAAAAAAIBzTQAAmQAAAAAwAAAAAAAAAIBzTQAAKAIaIAMwBAAA
AE49AABOPQAAmAAAAAAAAAAAAAAAAIDZXAAAmAAAAAAAAAAAAAAAAIDZXAAAKAIaIAMABQAAAE49
AABOPQAAmAAAAAAAAAAAAAAAAIBPYQAAmAAAACkAAAAAAAAAAIBPYQAAmAAAACUAAAAAAAAAAIBP
YQAAqQAAAAAAAAAAAAAAAIBPYQAAqQAAAAAAAAAAAAAAAIBPYQAAqQAAAAAAAAAAAAAAAIBPYQAA
qQAAAAAAAAAAAAAAAIBPYQAAmQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAqQAA
AAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAmQAAAAAw
AAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAA
AAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAmQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAA
AIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBP
YQAAmQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAA
qQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAmQAAAAAwAAAAAAAAAIBPYQAAqQAA
AAAwAAAAAAAAAIBPYQAAqQAAADIwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAw
AAAAAAAAAIBPYQAAmQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAA
AAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAqQAAAAAwAAAAAAAAAIBPYQAAmQAAAAAwAAAAAAAA
AIBPYQAAmAAAAAAwAAAAAAAAAIBPYQAAmAAAAAAAAAAAAAAAAIBPYQAAmAAAAAAAAAAAAAAAAIBP
YQAACAAaIAEABQAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIBkZQAACAAaIAEABgAAAAAAAIAAAACA
mAAAAAAAAAAAAAAAAIBZZgAAmAAAAAAAAAAAAAAAAIBZZgAACAAAABIAAAAAAAAAAIAAAACAmAAA
AA8AAAAAAAAAAIAGZwAAmAAAAC8AAAAAAAAAAIAGZwAAmAAAAAAAAAAAAAAAAIAGZwAAmAAAAAAA
AAAAAAAAAIAGZwAAmAAAAAAAAAAAAAAAAIAGZwAAmAAAACUAAAAAAAAAAIAGZwAAqQAAAAAAAAAA
AAAAAIAGZwAAqQAAAAAAAAAAAAAAAIAGZwAAqQAAAAAAAAAAAAAAAIAGZwAAqQAAAAAAAAAAAAAA
AIAGZwAAmQAAAAAwAAAAAAAAAIAGZwAAqQAAAAAwAAAAAAAAAIAGZwAAqQAAAAAwAAAAAAAAAIAG
ZwAAqQAAAAAwAAAAAAAAAIAGZwAAqQAAAAAwAAAAAAAAAIAGZwAAmQAAAAAwAAAAAAAAAIAGZwAA
qQAAAAAwAAAAAAAAAIAGZwAAqQAAAAAwAAAAAAAAAIAGZwAAqQAAAAAwAAAAAAAAAIAGZwAAqQAA
AAAwAAAAAAAAAIAGZwAAmQAAAAAwAAAAAAAAAIAGZwAAmAAAACUwAAAAAAAAAIAGZwAAqQAAAAAA
AAAAAAAAAIAGZwAAqQAAAAAAAAAAAAAAAIAGZwAAmQAAAAAwAAAAAAAAAIAGZwAAqQAAAAAwAAAA
AAAAAIAGZwAAqQAAAA8wAAAAAAAAAIAGZwAAmQAAAAAwAAAAAAAAAIAGZwAAqQAAAAAwAAAAAAAA
AIAGZwAAqQAAAAAwAAAAAAAAAIAGZwAAmQAAAAAwAAAAAAAAAIAGZwAAmAAAAAAwAAAAAAAAAIAG
ZwAAmAAAAAAAAAAAAAAAAIAGZwAAmAAAAAAAAAAAAAAAAIAGZwAAmAAAAAAAAAAAAAAAAIAGZwAA
mAAAAAAAAAAAAAAAAIAGZwAACAAAAC0AAAAAAAAAAIAAAACAmAAAAC4AAAAAAAAAAICqbAAAmAAA
AC8AAAAAAAAAAICqbAAAmAAAAC4AAAAAAAAAAICqbAAAmAAAAC4AAAAAAAAAAICqbAAAmAAAAAAA
AAAAAAAAAICqbAAAmAACIFkAAAAAAAAAAICqbAAAmAACIFkAAQAAAAAAAICqbAAAmAACIFkAAgAA
AAAAAICqbAAAmAACIFkAAwAAAAAAAICqbAAAmAAAAAAAAAAAAAAAAICqbAAAmAAAAAAAAAAAAAAA
AICqbAAAmAAAAFkAAAAAAAAAAICqbAAAmAABIFkAAAAAAAAAAICqbAAAmAABIFkAAQAAAAAAAICq
bAAAmAAAAFkAAAAAAAAAAICqbAAAmAAAAFkAAAAAAAAAAICqbAAAmAAAAFkAAAAAAAAAAICqbAAA
mAAAAFkAAAAAAAAAAICqbAAAmAAAAFkAAAAAAAAAAICqbAAAmAAAAFkAAAAAAAAAAICqbAAAmAAA
AF4wAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAA
AAAAAAAAAICqbAAAkAAAAFkAAAAAAAAAAICqbAAAkAABIFkAAgAAAAAAAICqbAAAkAABIFkAAwAA
AAAAAICqbAAAkAAAAFkAAAAAAAAAAICqbAAAkAAAAFkAAAAAAAAAAICqbAAAkAAAAFkAAAAAAAAA
AICqbAAAkAAAABwAAAAAAAAAAICqbAAAkAAAAC0AAAAAAAAAAICqbAAAkAAAAC4AAAAAAAAAAICq
bAAAkAAAAC8AAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAA
kAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAABQAAAAAAAAAAICqbAAAkAAA
AAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAA
AAAAAAAAAICqbAAAmAAAAAAwAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAA
AAAAAICqbAAAmAAAAF4wAAAAAAAAAICqbAAAqQAAAAAAAAAAAAAAAICqbAAAqQAAAAAAAAAAAAAA
AICqbAAAqQAAAAAAAAAAAAAAAICqbAAAqQAAAA8AAAAAAAAAAICqbAAAmQAAAAAwAAAAAAAAAICq
bAAAqQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAA
mQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAqQAA
AAAwAAAAAAAAAICqbAAAmQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAqQAAAAAw
AAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAmQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAA
AAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAmQAAAAAwAAAAAAAA
AICqbAAAkAAAAAAwAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICq
bAAAkAAAAAAAAAAAAAAAAICqbAAAqQAAAAAAAAAAAAAAAICqbAAAqQAAAAAAAAAAAAAAAICqbAAA
qQAAAAAAAAAAAAAAAICqbAAAmQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAqQAA
AAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAmQAAAAAwAAAAAAAAAICqbAAAqQAAAAAw
AAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAmQAAAAAwAAAA
AAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAA
AICqbAAAmQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICq
bAAAqQAAAAAwAAAAAAAAAICqbAAAmQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAA
qQAAAAAwAAAAAAAAAICqbAAAqQAAAAAwAAAAAAAAAICqbAAAmQAAAAAwAAAAAAAAAICqbAAAmAAA
AF4wAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAA
AAAAAAAAAICqbAAAkAAAABUAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAA
AAAAAICqbAAAkAAAABQAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAA
AICqbAAAkAAAADIAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAACYAAAAAAAAAAICq
bAAAkAAAACYAAAAAAAAAAICqbAAAkAAAACYAAAAAAAAAAICqbAAAkAAAACYAAAAAAAAAAICqbAAA
kAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAmAAA
AAAwAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAAAAAAAAAAAAAAAAICqbAAAkAASIAAA
AAAAAAAAAICqbAAAkAASIAAAAQAAAAAAAICqbAAAkAASIAAAAgAAAAAAAICqbAAAkAASIAAAAwAA
AAAAAICqbAAAkAAAAAAAAAAAAAAAAIAAAACAmAAAAF4wAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAA
AIAAAACAqQAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAA
AACAqQAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACA
nAAAAAAAAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
mQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAkAAAAAAw
AAAAAAAAAIAAAACAkAAAAAAAAAAAAAAAAIAAAACAkAAAAAAAAAAAAAAAAIAAAACAkAAAAAAAAAAA
AAAAAIAAAACAkAAAAAAAAAAAAAAAAIAAAACAmAAAAF4wAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAA
AIAAAACAqQAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAnAAAAAAAAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
mQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAmQAAAAAwAAAAAAAAAIAAAACAkAAAAAAwAAAAAAAAAIAAAACAkAAAAAAAAAAAAAAAAIAAAACA
kAAAAAAAAAAAAAAAAIAAAACAkAAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAqQAA
AAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAnAAAAAAAAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAw
AAAAAAAAAIAAAACAmAAAAAAwAAAAAAAAAIAAAACAkAAAAAAAAAAAAAAAAIAAAACAkAAAAAAAAAAA
AAAAAIAAAACAkAAAAAAAAAAAAAAAAIAAAACAmAAAAF4wAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAA
AIAAAACAqQAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAA
AACAqQAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACA
nAAAAAAAAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
mQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAA
AAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAA
AACAkAAAAAAwAAAAAAAAAIAAAACAkAAAAAAAAAAAAAAAAIAAAACAkAAAABQAAAAAAAAAAIAAAACA
kAAAACYAAAAAAAAAAIAAAACAmAAAAF4wAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAqQAA
AAAAAAAAAAAAAIAAAACAqQAAAAAAAAAAAAAAAIAAAACAnAAAAAAAAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAmAAAACYwAAAAAAAAAIAAAACA
mAAAACYAAAAAAAAAAIAAAACAmAAAACYAAAAAAAAAAIAAAACAmAAAABQAAAAAAAAAAIAAAACAmAAA
AAAAAAAAAAAAAIAAAACAmAAAABQAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAA
AAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAABQAAAAA
AAAAAIAAAACAmAAAAFsAAAAAAAAAAIAAAACAnAAAAAAAAAAAAAAAAIAAAACAmAAAAC4AAAAAAAAA
AIAAAACAmAAAAC8AAAAAAAAAAIAAAACAmAAAAC8AAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAA
AACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAGAAAAAIAAAAAAAAAAIAAAACA
mAAAAAAAAAAAAAAAAIAAAACAmAAXIAAAAAAAAAAAAIAAAACAmAAXIAAAAAAAAAAAAIAAAACAmAAX
IAAAAAAAAAAAAIAAAACAGAAAAAIAAAAAAAAAAIAAAACAKAAAAAMAAAAAAAAAAIAAAACAmAAAAAAA
AAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAA
AAAAAIAAAACAKAAAAAMAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAA
AIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAGAAAAAAAAAAAIAA
AACAmAAAACoAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACA
KAAAAAMAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAA
AAAAAAAAAAAAAIAAAACAKAAAAAMAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAA
AAAAAAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACAmAAYIGEAAAAA
AAAAAIAAAACAGAAAAAIAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAA
AIAAAACAmAAYIGEAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACAGAAAAAIAAAAAAAAAAIAA
AACAmAAAAAAAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACA
mAAYIGEAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAGAAAAAIAAAAAAAAAAIAAAACAmAAA
AAAAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACAmAAYIGEA
AAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAGAAAAAIAAAAAAAAAAIAAAACAmAAAAAAAAAAA
AAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAA
AIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAA
AACAmAAAAAAAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACAmAAYIGEAAAAAAAAAAIAAAACA
mAAAAAAAAAAAAAAAAIAAAACAGAAAAAIAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAA
AAAAAAAAAAAAAIAAAACACAAAAC0AAAAAAAAAAIAAAACACAAAAC0AAAAAAAAAAIAAAACAmAAAAFcA
AAAAAAAAAIAAAACAmAAAAFYAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAA
AAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAFIAAAAAAAAAAAAIAAAACAmAAGIAAAAAAAAAAA
AIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAHIAAAAAAAAAAAAIAAAACAmAAIIAAAAAAAAAAAAIAA
AACAmAAAAAAAAAAAAAAAAIAAAACAmAAJIAAAAAAAAAAAAIAAAACAmAAKIAAAAAAAAAAAAIAAAACA
mAALIAAAAAAAAAAAAIAAAACAmAAMIAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAN
IAAAAAAAAAAAAIAAAACAmAANIAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAOIAAA
AAAAAAAAAIAAAACAmAAOIAAAAAAAAAAAAIAAAACAmAAPIAAAAAAAAAAAAIAAAACAmAAPIAAAAAAA
AAAAAIAAAACAmAAAAC4AAAAAAAAAAIAAAACAmAAAAC8AAAAAAAAAAIAAAACAmAAAAC8AAAAAAAAA
AIAAAACAmAAAAFkAAAAAAAAAAIAAAACAmAAAAFkAAAAAAAAAAIAAAACAmAAAAFkAAAAAAAAAAIAA
AACAmAAAABAAAAAAAAAAAIAAAACAmAAAACkAAAAAAAAAAIAAAACAmAAAACUAAAAAAAAAAIAAAACA
qQAAABAAAAAAAAAAAIAAAACAqQAAABAAAAAAAAAAAIAAAACAqQAAABAAAAAAAAAAAIAAAACAnAAA
AAAAAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAw
AAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAA
AAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAA
AIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAAAAAwAAAAAAAAAIAA
AACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACA
qQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAqQAAAAAwAAAAAAAAAIAAAACAmQAA
AAAwAAAAAAAAAIAAAACAmAAAAC4wAAAAAAAAAIAAAACAmAAAAC8AAAAAAAAAAIAAAACAmAAAAC8A
AAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAA
AAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAA
AIAAAACAmAAAAFkAAAAAAAAAAIAAAACAmAAAAFkAAAAAAAAAAIAAAACAmAAAAC0AAAAAAAAAAIAA
AACAmAAAAFcAAAAAAAAAAIAAAACAmAAAAFYAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACA
mAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAA
AAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAA
AAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAA
AAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAA
AIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAA
AACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACA
mAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAA
AAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAFkAAAAAAAAAAIAAAACAmAAAAC0A
AAAAAAAAAIAAAACAmAAAAFcAAAAAAAAAAIAAAACAmAAAAFYAAAAAAAAAAIAAAACAmAAAABEAAAAA
AAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAA
AIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAwAAAAAAAAAIAAAACAmkAAAAAAAAAAAAAAAIAA
AACAmEAAACAAAAAAAAAAAIAAAACAmEAAACAAAAAAAAAAAIAAAACAmkAAAAAAAAAAAAAAAIAAAACA
mEAAAB8AAAAAAAAAAIAAAACAmkAAAAAAAAAAAAAAAIAAAACAmEAAACAAAAAAAAAAAIAAAACAmkAA
AAAAAAAAAAAAAIAAAACAmEAAAB8AAAAAAAAAAIAAAACAmkAAAAAAAAAAAAAAAIAAAACAmEAAAB8A
AAAAAAAAAIAAAACAmkAAAAAAAAAAAAAAAIAAAACAmEAAAAAAAAAAAAAAAIAAAACAmkAAAAAAAAAA
AAAAAIAAAACAmEAAAB8AAAAAAAAAAIAAAACAmkAAAAAAAAAAAAAAAIAAAACAmkAAAB8wAAAAAAAA
AIAAAACAmkAAAAAAAAAAAAAAAIAAAACAmkAAAB8wAAAAAAAAAIAAAACACgAAAAAAAAAAAAAAAAAA
AAAAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACA
mAAAAAAAAAAAAAAAAIAAAACAmAAAAAAAAAAAAAAAAIAAAACAmgAAAAAAAAAAAAAAAIAAAACAAAAA
ABYAAAAWAAAAFgAAABYAAAAWAAAAFgAAABgAAAAtAAAALQAAAL0AAAC9AAAAvQAAAL0AAAC/AAAA
vwAAAMEAAADBAAAAwQAAAMEAAADBAAAAwQAAAMMAAADDAAAAwwAAAMUAAADHAAAA2QAAANsAAADd
AAAA3wAAAN8AAADfAAAA3wAAAPAAAADwAAAA8AAAAPAAAADwAAAA8AAAAAEBAAABAQAAAQEAAAEB
AAABAQAAAQEAAAEBAAABAQAAAQEAAAQBAAAABAAAjwYAABINAAANDwAAkTMAAGJbAACBdgAADYcA
APiLAACimQAA/JsAAC/KAACx9QAAgf8AAMD/AACKAAAAjwAAAJIAAACTAAAAmQAAAKgAAAC1AAAA
vQAAAL8AAADbAAAA+AAAAP4AAAAGAQAACQEAAAAEAAAMBgAAeAYAAPUGAAA4DAAAyA8AADscAADQ
IAAAzyQAALoxAADLSAAAv1QAACxVAABLVQAATFUAAJVVAACbVQAAC1YAABFWAABzVgAAeVYAAKdW
AAAMWQAA2FoAAPZlAADVZgAANmcAAKpnAAD0ZwAAX2gAAGRpAAD1bQAAFm4AAC5uAADrbgAAtnAA
AOl3AAAPggAAO4IAAHaCAABxhAAAsoQAAPGEAADnhwAAc44AAJGOAACojgAAsY4AAN2OAADmjgAA
/Y4AAAaPAAAojwAAQ48AAGCPAAB1jwAAlY8AAJ2PAAC/jwAA2o8AAPePAAANkAAALZAAADWQAABM
kAAAVJAAAGqQAACTkwAAhJcAAEmYAACMmQAArJkAALuZAADNmQAA45kAAAKaAAAKmgAAIZoAACma
AABLmgAAZpoAAIOaAACYmgAAuJoAAMCaAADimgAA/5oAABWbAAA1mwAAPZsAAF+bAAB6mwAAl5sA
AK2bAADNmwAA1ZsAAOybAAD1mwAABpwAALucAAA+ngAAcZ4AAAKjAABbuAAAv8wAAErfAAAt4QAA
/+cAALboAACH6QAAx/MAAFX7AABT/wAAmf8AAMD/AACLAAAAjQAAAI4AAACQAAAAkQAAAJQAAACV
AAAAlgAAAJcAAACYAAAAmgAAAJsAAACcAAAAnQAAAJ4AAACfAAAAoAAAAKEAAACiAAAAowAAAKQA
AAClAAAApgAAAKcAAACpAAAAqgAAAKsAAACsAAAArQAAAK4AAACvAAAAsAAAALEAAACyAAAAswAA
ALQAAAC2AAAAtwAAALgAAAC5AAAAugAAALsAAAC8AAAAvgAAAMAAAADBAAAAwgAAAMMAAADEAAAA
xQAAAMYAAADHAAAAyAAAAMkAAADKAAAAywAAAMwAAADNAAAAzgAAAM8AAADQAAAA0QAAANIAAADT
AAAA1AAAANUAAADWAAAA1wAAANgAAADZAAAA2gAAANwAAADdAAAA3gAAAN8AAADgAAAA4QAAAOIA
AADjAAAA5AAAAOUAAADmAAAA5wAAAOgAAADpAAAA6gAAAOsAAADsAAAA7QAAAO4AAADvAAAA8AAA
APEAAADyAAAA8wAAAPQAAAD1AAAA9gAAAPcAAAD5AAAA+gAAAPsAAAD8AAAA/QAAAP8AAAAAAQAA
AQEAAAIBAAADAQAABAEAAAUBAAAHAQAACAEAAAoBAAAABAAAv/8AAIwAAACcCAAAqwgAALQIAADQ
CAAA0ggAAOEIAAD9CAAA/wgAABEJAAAtCQAALwkAAGwJAACICQAAigkAAK0JAADJCQAAywkAAOsJ
AAAHCgAACQoAABsKAAA3CgAAOQoAAG4KAACKCgAAjAoAALgKAADUCgAA1goAAPIKAAAOCwAAEAsA
AD0LAABZCwAAXAsAAI4LAACpCwAAxgsAAOULAAAADAAAHQwAAB8MAAB9LwAAkS8AAJMvAABKOAAA
YTgAAGM4AAB1bwAAiW8AAItvAABHcgAAXnIAAGByAABpcgAAgHIAAIJyAACFcwAAmXMAAJtzAAAg
fAAAN3wAADl8AACHfQAAnX0AAJ99AAAKgQAAIYEAACOBAADghwAA94cAAPmHAAAjigAAOYoAADuK
AAD+jgAAFI8AABaPAABElQAAWpUAAFyVAACrmQAAwZkAAMOZAADA+wAAEw3U/xMlNP+VwBMlNP+V
wBMlNP+VwBMlNP+VwBMlNP+VwBMlNP+VwBMlNP+VwBMlNP+VwBMlNP+VwBMlNP+VwBMlNP+VwBMl
NP+VwBMlNP+VwJWMEzqU/5WAEwyU/5WAEzqU/5WEEzqU/5WEEwzU/5WAEzqU/5WEEwzU/5WAEwz0
/5WAEwz0/5WAEwzU/5WAEwzU/5WAEwzU/5WAEwzU/5WAEwz0/5WAXAAAAIIAAACUAAAAzAAAANMA
AADWAAAA5AAAAOsAAADtAAAA9QAAAPwAAAD+AAAABAEAABNYFP8VjBMh1P+VgBMhFP+VgBMhFP+V
gA8AAPBsAAAAAAAG8BgAAAACCAAAAgAAAAQAAAABAAAAAQAAAAUAAAAfAAHwLAAAACIAB/AkAAAA
AgRpCupnzNuBkcyEfe9u1GD+/wA1BgAAAAAAAP////8AAJcBQAAe8RAAAAD//wAAAAD/AICAgAD3
AAAQAA8AAvDwAAAAEAAI8AgAAAACAAAABAQAAA8AA/COAAAADwAE8CgAAAABAAnwEAAAAAAAAAAA
AAAAAAAAAAAAAAACAArwCAAAAAAEAAAFAAAADwAE8FYAAACiDArwCAAAAAIEAAAACgAAIwAL8AwA
AACAAAAAAQD/AQAACAATACLxBgAAAL8DAAAAgAAAEPAEAAAAAAAAAAAAEfAEAAAADAAAAAAADfAE
AAAAAAABAA8ABPBCAAAAEgAK8AgAAAABBAAAAA4AAFMAC/AeAAAAvwEAABAAywEAAAAA/wEAAAgA
BAMJAAAAPwMBAAEAAAAR8AQAAAABAAAABwIAAMD7AAACBAAAOwwAALr7//+7GQAAWgEAAHQAAAAA
AP//dgAAAAUAZABuAHUAbQBlAAYAZABkAGEAdABlAGUABQBkAHMAZQBjAGUABgBjADEAdABpAHQA
ZQAGAGQAbgB1AG0AMgBlAA0AXwBUAG8AYwAzADgAOQA5ADgANQA1ADYANwANAF8AVABvAGMAMwA5
ADUANQA4ADEAMgA2ADUADQBfAFQAbwBjADMAOQA1ADUAOAAxADMANgAzAA0AXwBUAG8AYwAzADkA
NwA0ADAANQAyADIAMgANAF8AVABvAGMAMwA5ADcANAA4ADcANAA2ADkADQBfAFQAbwBjADMAOQA3
ADQAOQA1ADYANAA0AA0AXwBUAG8AYwA0ADcANgA3ADcAOAA5ADYAMwANAF8AVABvAGMAMwA4ADkA
OQA4ADUANQA2ADgADQBfAFQAbwBjADMAOQA1ADUAOAAxADIANgA2AA0AXwBUAG8AYwAzADkANQA1
ADgAMQAzADYANAANAF8AVABvAGMAMwA5ADcANAAwADUAMgAyADMADQBfAFQAbwBjADMAOQA3ADQA
OAA3ADQANwAwAA0AXwBUAG8AYwAzADkANwA0ADkANQA2ADQANQANAF8AVABvAGMANAA3ADYANwA3
ADgAOQA2ADQADQBfAFQAbwBjADMAOAA5ADkAOAA1ADUANgA5AA0AXwBUAG8AYwAzADkANQA1ADgA
MQAyADYANwANAF8AVABvAGMAMwA5ADUANQA4ADEAMwA2ADUADQBfAFQAbwBjADMAOQA3ADQAMAA1
ADIAMgA0AA0AXwBUAG8AYwAzADkANwA0ADgANwA0ADcAMQANAF8AVABvAGMAMwA5ADcANAA5ADUA
NgA0ADYADQBfAFQAbwBjADQANwA2ADcANwA4ADkANgA1AA0AXwBUAG8AYwA0ADcANgA3ADcAOAA5
ADYANgANAF8AVABvAGMAMwA4ADkAOQA4ADUANQA5ADAADQBfAFQAbwBjADMAOQA1ADUAOAAxADIA
OAA4AA0AXwBUAG8AYwAzADkANQA1ADgAMQAzADgANgANAF8AVABvAGMAMwA5ADcANAAwADUAMgA0
ADUADQBfAFQAbwBjADMAOQA3ADQAOAA3ADQAOQAyAA0AXwBUAG8AYwAzADkANwA0ADkANQA2ADYA
NwANAF8AVABvAGMAMwA4ADkAOQA4ADUANgAwADEADQBfAFQAbwBjADMAOQA1ADUAOAAxADIAOQA5
AA0AXwBUAG8AYwAzADkANQA1ADgAMQAzADkANwANAF8AVABvAGMAMwA5ADcANAAwADUAMgA1ADYA
DQBfAFQAbwBjADMAOQA3ADQAOAA3ADUAMAAzAA0AXwBUAG8AYwAzADkANwA0ADkANQA2ADcAOAAN
AF8AVABvAGMANAA3ADYANwA3ADgAOQA2ADcADQBfAFQAbwBjADQANwA2ADcANwA4ADkANgA4AA0A
XwBUAG8AYwAzADgAOQA5ADgANQA2ADAAMwANAF8AVABvAGMAMwA5ADUANQA4ADEAMwAwADEADQBf
AFQAbwBjADMAOQA1ADUAOAAxADMAOQA5AA0AXwBUAG8AYwAzADkANwA0ADAANQAyADUAOAANAF8A
VABvAGMAMwA5ADcANAA4ADcANQAwADUADQBfAFQAbwBjADMAOQA3ADQAOQA1ADYAOAAwAA0AXwBU
AG8AYwA0ADcANgA3ADcAOAA5ADYAOQANAF8AVABvAGMAMwA4ADkAOQA4ADUANgAwADQADQBfAFQA
bwBjADMAOQA1ADUAOAAxADMAMAAyAA0AXwBUAG8AYwAzADkANQA1ADgAMQA0ADAAMAANAF8AVABv
AGMAMwA5ADcANAAwADUAMgA1ADkADQBfAFQAbwBjADMAOQA3ADQAOAA3ADUAMAA2AA0AXwBUAG8A
YwAzADkANwA0ADkANQA2ADgAMQANAF8AVABvAGMANAA3ADYANwA3ADgAOQA3ADAADQBfAFQAbwBj
ADMAOAA5ADkAOAA1ADYAMAA1AA0AXwBUAG8AYwAzADkANQA1ADgAMQAzADAAMwANAF8AVABvAGMA
MwA5ADUANQA4ADEANAAwADEADQBfAFQAbwBjADMAOQA3ADQAMAA1ADIANgAwAA0AXwBUAG8AYwAz
ADkANwA0ADgANwA1ADAANwANAF8AVABvAGMAMwA5ADcANAA5ADUANgA4ADIADQBfAFQAbwBjADQA
NwA2ADcANwA4ADkANwAxAA0AXwBUAG8AYwAzADgAOQA5ADgANQA2ADAANgANAF8AVABvAGMAMwA5
ADUANQA4ADEAMwAwADQADQBfAFQAbwBjADMAOQA1ADUAOAAxADQAMAAyAA0AXwBUAG8AYwAzADkA
NwA0ADAANQAyADYAMQANAF8AVABvAGMAMwA5ADcANAA4ADcANQAwADgADQBfAFQAbwBjADMAOQA3
ADQAOQA1ADYAOAAzAA0AXwBUAG8AYwAzADgAOQA5ADgANQA2ADEAMAANAF8AVABvAGMAMwA5ADUA
NQA4ADEAMwAwADgADQBfAFQAbwBjADMAOQA1ADUAOAAxADQAMAA2AA0AXwBUAG8AYwAzADkANwA0
ADAANQAyADYANQANAF8AVABvAGMAMwA5ADcANAA4ADcANQAxADIADQBfAFQAbwBjADMAOQA3ADQA
OQA1ADYAOAA3AA0AXwBUAG8AYwA0ADcANgA3ADcAOAA5ADcAMgANAF8AVABvAGMANAA3ADYANwA3
ADgAOQA3ADMADQBfAFQAbwBjADMAOAA5ADkAOAA1ADYANAA1AA0AXwBUAG8AYwAzADkANQA1ADgA
MQAzADQAMwANAF8AVABvAGMAMwA5ADUANQA4ADEANAA0ADEADQBfAFQAbwBjADMAOQA3ADQAMAA1
ADMAMAAwAA0AXwBUAG8AYwAzADkANwA0ADgANwA1ADQANwANAF8AVABvAGMAMwA5ADcANAA5ADUA
NwAyADIADQBfAFQAbwBjADMAOAA5ADkAOAA1ADYANAA2AA0AXwBUAG8AYwAzADkANQA1ADgAMQAz
ADQANAANAF8AVABvAGMAMwA5ADUANQA4ADEANAA0ADIADQBfAFQAbwBjADMAOQA3ADQAMAA1ADMA
MAAxAA0AXwBUAG8AYwAzADkANwA0ADgANwA1ADQAOAANAF8AVABvAGMAMwA5ADcANAA5ADUANwAy
ADMADQBfAFQAbwBjADMAOAA5ADkAOAA1ADYANAA3AA0AXwBUAG8AYwAzADkANQA1ADgAMQAzADQA
NQANAF8AVABvAGMAMwA5ADUANQA4ADEANAA0ADMADQBfAFQAbwBjADMAOQA3ADQAMAA1ADMAMAAy
AA0AXwBUAG8AYwAzADkANwA0ADgANwA1ADQAOQANAF8AVABvAGMAMwA5ADcANAA5ADUANwAyADQA
DQBfAFQAbwBjADMAOAA5ADkAOAA1ADYANAA4AA0AXwBUAG8AYwAzADkANQA1ADgAMQAzADQANgAN
AF8AVABvAGMAMwA5ADUANQA4ADEANAA0ADQADQBfAFQAbwBjADMAOQA3ADQAMAA1ADMAMAAzAA0A
XwBUAG8AYwAzADkANwA0ADgANwA1ADUAMAANAF8AVABvAGMAMwA5ADcANAA5ADUANwAyADUADQBf
AFQAbwBjADMAOAA5ADkAOAA1ADYANAA5AA0AXwBUAG8AYwAzADkANQA1ADgAMQAzADQANwANAF8A
VABvAGMAMwA5ADUANQA4ADEANAA0ADUADQBfAFQAbwBjADMAOQA3ADQAMAA1ADMAMAA0AA0AXwBU
AG8AYwAzADkANwA0ADgANwA1ADUAMQANAF8AVABvAGMAMwA5ADcANAA5ADUANwAyADYADQBfAFQA
bwBjADMAOAA5ADkAOAA1ADYANQAwAA0AXwBUAG8AYwAzADkANQA1ADgAMQAzADQAOAANAF8AVABv
AGMAMwA5ADUANQA4ADEANAA0ADYADQBfAFQAbwBjADMAOQA3ADQAMAA1ADMAMAA1AA0AXwBUAG8A
YwAzADkANwA0ADgANwA1ADUAMgANAF8AVABvAGMAMwA5ADcANAA5ADUANwAyADcADQBfAFQAbwBj
ADMAOAA5ADkAOAA1ADYANQAyAA0AXwBUAG8AYwAzADkANQA1ADgAMQAzADUAMAANAF8AVABvAGMA
MwA5ADUANQA4ADEANAA0ADgADQBfAFQAbwBjADMAOQA3ADQAMAA1ADMAMAA3AA0AXwBUAG8AYwAz
ADkANwA0ADgANwA1ADUANAANAF8AVABvAGMAMwA5ADcANAA5ADUANwAyADkAPgIAAHgCAACPAgAA
vgIAAPUCAABFDgAARQ4AAEUOAABFDgAARQ4AAEUOAABFDgAAWxQAAFsUAABbFAAAWxQAAFsUAABb
FAAAWxQAAEIaAABCGgAAQhoAAEIaAABCGgAAQhoAAEIaAAAkIwAAJCMAACQjAAAkIwAAJCMAACQj
AAAkIwAAmy0AAJstAACbLQAAmy0AAJstAACbLQAAmy0AAH0vAAA4NAAAODQAADg0AAA4NAAAODQA
ADg0AAA4NAAAij4AAIo+AACKPgAAij4AAIo+AACKPgAAij4AAMRKAADESgAAxEoAAMRKAADESgAA
xEoAAMRKAABzTQAAc00AAHNNAABzTQAAc00AAHNNAADZXAAA2VwAANlcAADZXAAA2VwAANlcAADZ
XAAAWWYAAKpsAACqbAAAqmwAAKpsAACqbAAAqmwAAC52AAAudgAALnYAAC52AAAudgAALnYAAHt6
AAB7egAAe3oAAHt6AAB7egAAe3oAALyYAAC8mAAAvJgAALyYAAC8mAAAvJgAABSbAAAUmwAAFJsA
ABSbAAAUmwAAFJsAAPmbAAD5mwAA+ZsAAPmbAAD5mwAA+ZsAAE2gAABNoAAATaAAAE2gAABNoAAA
TaAAAMH7AAAAAAAAAQAAAAIAAAADAAAABAAAAAUAAAAGAAAABwAAAAgAAAAJAAAACgAAAAsAAAAM
AAAADQAAAA4AAAAPAAAAEAAAABEAAAASAAAAEwAAABQAAAAVAAAAFgAAABcAAAAYAAAAGQAAABoA
AAAbAAAAHAAAAB0AAAAeAAAAHwAAACAAAAAhAAAAIgAAACMAAAAkAAAAJQAAACYAAAAnAAAAKAAA
ACkAAAAqAAAAKwAAACwAAAAtAAAALgAAAC8AAAAwAAAAMQAAADIAAAAzAAAANAAAADUAAAA2AAAA
NwAAADgAAAA5AAAAOgAAADsAAAA8AAAAPQAAAD4AAAA/AAAAQAAAAEEAAABCAAAAQwAAAEUAAABG
AAAARwAAAEgAAABJAAAASgAAAEQAAABLAAAATAAAAE0AAABOAAAATwAAAFAAAABRAAAAUgAAAFMA
AABUAAAAVQAAAFYAAABXAAAAWAAAAFkAAABaAAAAWwAAAFwAAABdAAAAXgAAAF8AAABgAAAAYQAA
AGIAAABjAAAAZAAAAGUAAABmAAAAZwAAAGgAAABpAAAAagAAAGsAAABsAAAAbQAAAG4AAABvAAAA
cAAAAHEAAAByAAAAcwAAAHQAAAB1AAAAPgIAAHgCAACPAgAAvgIAAPUCAABKDgAASg4AAEoOAABK
DgAASg4AAEoOAABKDgAAZRQAAGUUAABlFAAAZRQAAGUUAABlFAAAZRQAAE8aAABPGgAATxoAAE8a
AABPGgAATxoAAE8aAABxIwAAcSMAAHEjAABxIwAAcSMAAHEjAABxIwAAuS0AALktAAC5LQAAuS0A
ALktAAC5LQAAuS0AAK0vAABZPQAAWT0AAFk9AABZPQAAWT0AAFk9AABZPQAAtj4AALY+AAC2PgAA
tj4AALY+AAC2PgAAtj4AAHNNAABzTQAAc00AAHNNAABzTQAAc00AAJZNAACWTQAAlk0AAJZNAACW
TQAAlk0AAJZNAAB7ZQAAg2YAAINmAACDZgAAg2YAAINmAACDZgAAg2YAALVsAAC1bAAAtWwAALVs
AAC1bAAAtWwAAH92AAB/dgAAf3YAAH92AAB/dgAAf3YAAJt6AACbegAAm3oAAJt6AACbegAAm3oA
APiYAAD4mAAA+JgAAPiYAAD4mAAA+JgAADCbAAAwmwAAMJsAADCbAAAwmwAAMJsAACacAAAmnAAA
JpwAACacAAAmnAAAJpwAAIzZAACM2QAAjNkAAIzZAACM2QAAjNkAAMH7AAAAAAAAoAAAANYAAADb
AAAAKgQAAC0EAABTBgAAVgYAAIkPAACMDwAA5A8AAOcPAADgEAAA4xAAABMRAAAWEQAADBMAAA8T
AAA0GAAAORgAAEIeAABFHgAA9x8AAAggAAB7IAAAfiAAAIIgAACKIAAAySEAAM0hAAAVIgAAGCIA
APgiAAAAIwAAZSMAAGgjAAAyJAAANSQAAKYkAACpJAAAIScAACQnAAAQKAAAGSgAAMEpAADEKQAA
nyoAAKUqAAC4KgAAuyoAAH0vAACbLwAAnC8AAKYvAACnLwAAqS8AAKovAACtLwAAsi8AALUvAADg
MQAA4zEAAFYyAABaMgAAnDIAAJ8yAABWNAAAWTQAAM81AADUNQAAgjgAAIU4AABOPQAAUT0AAF89
AABoPQAA7j0AAPc9AAC6QQAAwkEAAABCAAAIQgAALEIAAC9CAADPQgAA10IAAENDAABLQwAA4kMA
AOpDAAA7RwAAREcAAExQAABWUAAAeFAAAHtQAACzUAAAtlAAALVRAAC9UQAAslgAALVYAAC+XwAA
wV8AALxhAAC/YQAA6mEAAO1hAAD2YQAA+WEAAGBjAABpYwAAWGkAAFtpAACSaQAAmWkAAI1rAACU
awAAoWsAAKhrAADyawAA/msAAKFuAACqbgAAlW8AAJ5vAACtbwAAtW8AANlvAADgbwAANXEAAD1x
AAAVcgAAHnIAAJ5yAACncgAApnMAAK1zAADpcwAA8HMAAEV5AABKeQAAnHoAAKB6AAB2ewAAensA
AJSCAACXggAACYMAAAyDAAAVgwAAGIMAACKDAAAlgwAA2YQAANyEAAAlhQAAKIUAAGOFAABmhQAA
HIgAAB+IAAAdiwAAIIsAALSLAAC3iwAAi48AAI6PAACTjwAAmY8AAFiRAABbkQAAeZEAAIGRAACR
kQAAlpEAAOOTAADmkwAA65MAAPGTAABAlgAAQ5YAANeWAADalgAAVJcAAFeXAAChmwAApZsAAHOc
AAB3nAAAspwAALacAAC3nQAAu50AABufAAAfnwAADqEAABGhAABZoQAAXKEAANWhAADYoQAA8KEA
APOhAAB/ogAAgqIAAMeiAADKogAAI6MAACajAADorQAA9a0AAHCyAAB4sgAApLIAAKyyAAD9sgAA
CLMAAIuzAACTswAAXbQAAGS0AABntAAAb7QAAHC0AABytAAAf7QAAIe0AAB/vAAAh7wAALO8AAC7
vAAALb0AADW9AACJvQAAkb0AABO/AAAbvwAAT78AAFe/AAAowQAALMEAAFDEAABUxAAAvMcAAMDH
AADaygAA3soAABvSAAAf0gAAJNYAACjWAACb3QAApN0AAN/fAADn3wAACOAAAAvgAABM4QAAUOEA
AG3hAAB14QAA7OEAAPDhAADS4gAA1eIAALXjAAC44wAAJOQAACfkAACT5AAAl+QAALbkAAC55AAA
TOUAAFDlAABx5QAAdOUAACzoAAA56AAAVeoAAGLqAAAH8AAAD/AAALjwAADB8AAA6vAAAPPwAABa
8QAAZPEAAIz0AACP9AAA9fQAAP30AAD/9AAABPUAAHP1AAB69QAAfPUAAID1AACF9QAAiPUAAIn1
AACM9QAAkvUAAJf1AACZ9QAAn/UAAKD1AACr9QAArvYAALT2AAC59gAAv/YAAMT2AADL9gAAlfoA
AJX6AACq+gAAqvoAAKv6AAC6+gAAv/oAAMz6AADW+gAAYfsAAGz7AAB5+wAAg/sAAIr7AACU+wAA
lvsAAJf7AAC++wAAwfsAAAUABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAc
AAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwA
BwADAAcAAwAHAAMABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAH
ABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcA
HAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAc
AAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwA
BwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAH
ABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcA
BQAHAAUABwAFAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAc
AAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwA
BwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAHABwABwAcAAcAHAAH
ABwABwAcAAcAHAAHABwABwAcAAcABAAHAAQAAgAHAAQABwAcAAcABwAHAAcABwAHAAcAAgAHAAcA
AAAAANQAAADbAAAADAIAACwCAABYAgAAbwIAAP8CAAAQAwAAGgMAACsDAACOAwAAnwMAAB0FAAAl
BQAAJwgAAC0IAAChFAAAsRQAADEWAABrFgAAwxYAAMUWAADRGwAA2RsAACgfAABPHwAAVSAAAGAg
AAB7IAAAfiAAACEoAAArKAAAfS8AAK0vAABzTwAAdk8AAL5RAADGUQAA+FYAABhXAABgYgAAbGIA
AMJpAADLaQAA1GkAAN1pAADmaQAA72kAAGBrAABjawAA6WsAAOxrAAAxbAAAVGwAABNuAAAZbgAA
Gm4AACFuAACUbgAAnG4AAI5vAACTbwAAmHEAAKBxAACDcgAAi3IAAJ9zAACkcwAAOnwAAEB8AADy
fQAA9X0AAJeAAACggAAAsoAAAAqBAAAkgQAA4IcAAPqHAAAjigAAPIoAAP6OAAAXjwAARJUAAF2V
AACrmQAAxJkAAJT6AACV+gAAlfoAAKr6AACq+gAAYfsAAGz7AAB5+wAAg/sAAIr7AACU+wAAwfsA
AAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMA
BwAzAAcAMwAHAAMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAH
ADMABwAzAAcAMwAHADMABwAzAAcAMwAHADMABwAzAAcAMwAHAAMABwADAAcAAwAHAAMABwADAAcA
AwAHAAMAAgAEAAIABAACAAcAAgAHAAIABwACAAAAAACU+gAAlfoAAJX6AACq+gAAqvoAAHn7AACD
+wAAivsAAJT7AADB+wAAAwAHAAQAAgAEAAIABwACAAcAAgD//xQAAAAJAEEAbAAgAE0AbwByAHQA
bwBuADkAQwA6AFwAVwBJAE4ARABPAFcAUwBcAFQARQBNAFAAXABBAHUAdABvAFIAZQBjAG8AdgBl
AHIAeQAgAHMAYQB2AGUAIABvAGYAIABZAF8AMQA1ADQAMQBfADEAMAAwADMAYwBsAGUAYQBuAC4A
YQBzAGQACQBBAGwAIABNAG8AcgB0AG8AbgA4AEMAOgBcAE0AeQAgAEQAbwBjAHUAbQBlAG4AdABz
AFwATQBNAHMAdABkAFwAUwBlAHAAdAAyADAAMAAxACAAVAAxAEEAMQBcAFkAXwAxADUANAAxAF8A
MQAwADAAMwBjAGwAZQBhAG4ALgBkAG8AYwAJAEEAbAAgAE0AbwByAHQAbwBuADgAQwA6AFwATQB5
ACAARABvAGMAdQBtAGUAbgB0AHMAXABNAE0AcwB0AGQAXABTAGUAcAB0ADIAMAAwADEAIABUADEA
QQAxAFwAWQBfADEANQA0ADEAXwAxADAAMAAzAGMAbABlAGEAbgAuAGQAbwBjAAkAQQBsACAATQBv
AHIAdABvAG4AOQBDADoAXABXAEkATgBEAE8AVwBTAFwAVABFAE0AUABcAEEAdQB0AG8AUgBlAGMA
bwB2AGUAcgB5ACAAcwBhAHYAZQAgAG8AZgAgAFkAXwAxADUANAAxAF8AMQAwADAAMwBjAGwAZQBh
AG4ALgBhAHMAZAAJAEEAbAAgAE0AbwByAHQAbwBuADgAQwA6AFwATQB5ACAARABvAGMAdQBtAGUA
bgB0AHMAXABNAE0AcwB0AGQAXABTAGUAcAB0ADIAMAAwADEAIABUADEAQQAxAFwAWQBfADEANQA0
ADEAXwAxADAAMAAzAGMAbABlAGEAbgAuAGQAbwBjAAkAQQBsACAATQBvAHIAdABvAG4AOABDADoA
XABNAHkAIABEAG8AYwB1AG0AZQBuAHQAcwBcAE0ATQBzAHQAZABcAFMAZQBwAHQAMgAwADAAMQAg
AFQAMQBBADEAXABZAF8AMQA1ADQAMQBfADEAMAAwADMAYwBsAGUAYQBuAC4AZABvAGMACQBBAGwA
IABNAG8AcgB0AG8AbgAwAEMAOgBcAE0AeQAgAEQAbwBjAHUAbQBlAG4AdABzAFwATQBNAHMAdABk
AFwAUwBlAHAAdAAyADAAMAAxACAAVAAxAEEAMQBcADEAYQAxADMAMAAzADUAMQAuAGQAbwBjAAkA
QQBsACAATQBvAHIAdABvAG4AMABDADoAXABNAHkAIABEAG8AYwB1AG0AZQBuAHQAcwBcAE0ATQBz
AHQAZABcAFMAZQBwAHQAMgAwADAAMQAgAFQAMQBBADEAXAAxAGEAMQAzADAAMwA1ADEALgBkAG8A
YwAOAEEAcgB0AGgAdQByACAAVwBlAGIAcwB0AGUAcgA3AE0AOgBcAGEAcgB0AGgAdQByAFwAUwBU
AEEATgBEAEEAUgBEAFMAXAB0ADEAYQAxAF8AbQBpAHMAYwBcAG8AdAB0AGEAdwBhAF8AbwBjAHQA
MAAyAFwAMQBhADEAMwAwADMANQAxAC4AZABvAGMABwBEAEkAUwBBAE4AZQB0ABQARAA6AFwAdAAx
AGEAMQBcADEAYQAxADMAMAAzADUAMQAuAGQAbwBjABoAYFQEAIqnDn//D/8P/w//D/8P/w//D/8P
/w8AAOEB4gjIWo7KAQACAAMABAAFAAYABwAIAAkAAAC+X0sWKC96Jf8PAAAAAAAAAAAAAAAAAAAA
AAEAkFN+H7ZFeB7/D/8P/w//D/8P/w//D/8P/w8AAAlTMCIoL3ol/w8AAAAAAAAAAAAAAAAAAAAA
AQCSMb4lDwAJBP8PAAAAAAAAAAAAAAAAAAAAAAEAPSQLJg8ACQT/DwAAAAAAAAAAAAAAAAAAAAAB
AHN/liYoL3ol/w8AAAAAAAAAAAAAAAAAAAAAAQDYY9YzAQAJBP8PAAAAAAAAAAAAAAAAAAAAAAEA
uw58NQUACQT/DwAAAAAAAAAAAAAAAAAAAAABAEQj6DooL3ol/w8AAAAAAAAAAAAAAAAAAAAAAQBY
NK9AKC96Jf8PAAAAAAAAAAAAAAAAAAAAAAEAyG0bQQUACQT/DwAAAAAAAAAAAAAAAAAAAAABAGZZ
sUkoL3ol/w8AAAAAAAAAAAAAAAAAAAAAAQCqfsBNcmeMeWEAAAAAAAAAAAAAAAAAAAAAAAEAsVQb
UAEACQT/DwAAAAAAAAAAAAAAAAAAAAABAD1fXVcPAAkE/w8AAAAAAAAAAAAAAAAAAAAAAQCmG4VZ
KC96Jf8PAAAAAAAAAAAAAAAAAAAAAAEAAWypWSgveiX/DwAAAAAAAAAAAAAAAAAAAAABALZY4Vko
L3ol/w8AAAAAAAAAAAAAAAAAAAAAAQBZM+FeKC96Jf8PAAAAAAAAAAAAAAAAAAAAAAEAKFaqagUA
CQT/DwAAAAAAAAAAAAAAAAAAAAABAJV15GrYN4JL/w//D/8P/w//D/8P/w//D/8PAQDlQbFrAQAJ
BP8PAAAAAAAAAAAAAAAAAAAAAAEA8Fe0bSgveiX/DwAAAAAAAAAAAAAAAAAAAAABAIgdJXsSzVgy
/w//D/8P/w//D/8P/w//D/8PAAAFAAAAAAABAAAAAAAAAAAAAAAAAAAAAAADGAAAD4QbAxGE5fwV
xgUAARsDBl6EGwNghOX8bygAAQAAAAIAAAAAAAEDAAAAAAAAAAAAAAAAAAAAAAMYAAAPhBsDEYTl
/BXGBQABGwMGXoQbA2CE5fxvKAADAAAALgABAAMAAAAAAAEDBQAAAAAAAAAAAAAAAAAAAAMYAAAP
hBsDEYTl/BXGBQABGwMGXoQbA2CE5fxvKAAFAAAALgABAC4AAgABAAAAAAABAwUHAAAAAAAAAAAA
AAAAAAADGAAAD4QbAxGE5fwVxgUAARsDBl6EGwNghOX8bygABwAAAC4AAQAuAAIALgADAAEAAAAA
AAEDBQcJAAAAAAAAAAAAAAAAAAMYAAAPhDgEEYTI+xXGBQABOAQGXoQ4BGCEyPtvKAAJAAAALgAB
AC4AAgAuAAMALgAEAAEAAAAAAAEDBQcJCwAAAAAAAAAAAAAAAAMYAAAPhDgEEYTI+xXGBQABOAQG
XoQ4BGCEyPtvKAALAAAALgABAC4AAgAuAAMALgAEAC4ABQABAAAAAAABAwUHCQsNAAAAAAAAAAAA
AAADGAAAD4SgBRGEYPoVxgUAAaAFBl6EoAVghGD6bygADQAAAC4AAQAuAAIALgADAC4ABAAuAAUA
LgAGAAEAAAAAAAEDBQcJCw0PAAAAAAAAAAAAAAMYAAAPhKAFEYRg+hXGBQABoAUGXoSgBWCEYPpv
KAAPAAAALgABAC4AAgAuAAMALgAEAC4ABQAuAAYALgAHAAEAAAAAAAEDBQcJCw0PEQAAAAAAAAAA
AAMYAAAPhAgHEYT4+BXGBQABCAcGXoQIB2CE+PhvKAARAAAALgABAC4AAgAuAAMALgAEAC4ABQAu
AAYALgAHAC4ACAABAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAGAAAD4SwARGEUP4VxgUAAbABBl6E
sAFghFD+AQAAAAEAAAAAAAEDAAAAAAAAAAAAAAAAAAAAAAAYAAAPhEACEYTA/RXGBQABQAIGXoRA
AmCEwP0DAAAALgABAAEAAAAAAAEDBQAAAAAAAAAAAAAAAAAAAAAYAAAPhAAAEYQAABXGBQAB0AIG
XoQAAGCEAAAFAAAALgABAC4AAgABAAAAAAABAwUHAAAAAAAAAAAAAAAAAAAAGAAAD4RgAxGEoPwV
xgUAAWADBl6EYANghKD8BwAAAC4AAQAuAAIALgADAAEAAAAAAAEDBQcJAAAAAAAAAAAAAAAAAAAY
AAAPhPADEYQQ/BXGBQAB8AMGXoTwA2CEEPwJAAAALgABAC4AAgAuAAMALgAEAAEAAAAAAAEDBQcJ
CwAAAAAAAAAAAAAAAAAYAAAPhIAEEYSA+xXGBQABgAQGXoSABGCEgPsLAAAALgABAC4AAgAuAAMA
LgAEAC4ABQABAAAAAAABAwUHCQsNAAAAAAAAAAAAAAAAGAAAD4QQBRGE8PoVxgUAARAFBl6EEAVg
hPD6DQAAAC4AAQAuAAIALgADAC4ABAAuAAUALgAGAAEAAAAAAAEDBQcJCw0PAAAAAAAAAAAAAAAY
AAAPhKAFEYRg+hXGBQABoAUGXoSgBWCEYPoPAAAALgABAC4AAgAuAAMALgAEAC4ABQAuAAYALgAH
AAEAAAAAAAEDBQcJCw0PEQAAAAAAAAAAAAAYAAAPhDAGEYTQ+RXGBQABMAYGXoQwBmCE0PkRAAAA
LgABAC4AAgAuAAMALgAEAC4ABQAuAAYALgAHAC4ACAAAAAAAFwAAAAAAAAAAAAAAAAAAAAAAAAAD
GAAAD4RoARGEmP4VxgUAAWgBBl6EaAFghJj+bygAAQATIAUAAAAAAAEAAAAAAAAAAAAAAAAAAAAA
AAMYAAAPhKQBEYRc/hXGBQABpAEGXoSkAWCEXP5vKAABAAAAAQAAAAAAAQMAAAAAAAAAAAAAAAAA
AAAAAxgAAA+EpAERhFz+FcYFAAGkAQZehKQBYIRc/m8oAAMAAAAuAAEAAQAAAAAAAQMFAAAAAAAA
AAAAAAAAAAAAAxgAAA+E0AIRhDD9FcYFAAHQAgZehNACYIQw/W8oAAUAAAAuAAEALgACAAEAAAAA
AAEDBQcAAAAAAAAAAAAAAAAAAAMYAAAPhNACEYQw/RXGBQAB0AIGXoTQAmCEMP1vKAAHAAAALgAB
AC4AAgAuAAMAAQAAAAAAAQMFBwkAAAAAAAAAAAAAAAAAAxgAAA+EOAQRhMj7FcYFAAE4BAZehDgE
YITI+28oAAkAAAAuAAEALgACAC4AAwAuAAQAAQAAAAAAAQMFBwkLAAAAAAAAAAAAAAAAAxgAAA+E
OAQRhMj7FcYFAAE4BAZehDgEYITI+28oAAsAAAAuAAEALgACAC4AAwAuAAQALgAFAAEAAAAAAAED
BQcJCw0AAAAAAAAAAAAAAAMYAAAPhKAFEYRg+hXGBQABoAUGXoSgBWCEYPpvKAANAAAALgABAC4A
AgAuAAMALgAEAC4ABQAuAAYAAQAAAAAAAQMFBwkLDQ8AAAAAAAAAAAAAAxgAAA+EoAURhGD6FcYF
AAGgBQZehKAFYIRg+m8oAA8AAAAuAAEALgACAC4AAwAuAAQALgAFAC4ABgAuAAcAAQAAAAAAAQMF
BwkLDQ8RAAAAAAAAAAAAAxgAAA+ECAcRhPj4FcYFAAEIBwZehAgHYIT4+G8oABEAAAAuAAEALgAC
AC4AAwAuAAQALgAFAC4ABgAuAAcALgAIAAAAAAAXAAAAAAAAAAAAAAAAAAAAAAAAAAMYAAAPhGgB
EYSY/hXGBQABaAEGXoRoAWCEmP5vKAABABMgAQAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAABgAAA+E
aAERhJj+FcYFAAFoAQZehGgBYISY/gIAAAAuAAEAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAYAAAP
hGgBEYSY/hXGBQABaAEGXoRoAWCEmP4CAAAALgAAAAAAFwAAAAAAAAAAAAAAAAAAAAAAAAADGAAA
D4RoARGEmP4VxgUAAWgBBl6EaAFghJj+bygAAQATIAEAAAAXAAAAAAAAAAAAAAAAAAAAAAAAAAsY
AAAPhGgBEYSY/hXGBQABaAEGXoRoAWCEmP5PSgEAUUoBAG8oAAEAt/ABAAAAFwAAAAAAAAAAAAAA
AAAAAAAAAAALGAAAD4RoARGEmP4VxgUAAWgBBl6EaAFghJj+T0oGAFFKBgBvKAABAKfwAAAAABcA
AAAAAAAAAAAAAAAAAAAAAAAAAxgAAA+EaAERhJj+FcYFAAFoAQZehGgBYISY/m8oAAEAEyAAAAAA
FwAAAAAAAAAAAAAAAAAAAAAAAAADGAAAD4RoARGEmP4VxgUAAWgBBl6EaAFghJj+bygAAQATIAEA
AAAXAAAAAAAAAAAAAAAAAAAAAAAAAAsYAAAPhGgBEYSY/hXGBQABaAEGXoRoAWCEmP5PSgYAUUoG
AG8oAAEAp/AAAAAAFwAAAAAAAAAAAAAAAAAAAAAAAAADGAAAD4RoARGEmP4VxgUAAWgBBl6EaAFg
hJj+bygAAQATIAEAAAAXAAAAAAAAAAAAAAAAAAAAAAAAAAsYAAAPhDcCEYSs/hXGBQABSwIGXoQ3
AmCErP5PSgEAUUoBAG8oAAEAt/ABAAAAFwAAAAAAAAAAAAAAAAAAAAAAAAALGAAAD4RoARGEmP4V
xgUAAWgBBl6EaAFghJj+T0oBAFFKAQBvKAABALfwAQAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAABgA
AA+EaAERhJj+FcYFAAFoAQZehGgBYISY/gIAAAAuAAAAAAAXAAAAAAAAAAAAAAAAAAAAAAAAAAMY
AAAPhGgBEYSY/hXGBQABaAEGXoRoAWCEmP5vKAABABMgAAAAABcAAAAAAAAAAAAAAAAAAAAAAAAA
AxgAAA+EaAERhJj+FcYFAAFoAQZehGgBYISY/m8oAAEAEyAAAAAAFwAAAAAAAAAAAAAAAAAAAAAA
AAADGAAAD4RoARGEmP4VxgUAAWgBBl6EaAFghJj+bygAAQATIAAAAAAXAAAAAAAAAAAAAAAAAAAA
AAAAAAMYAAAPhGgBEYSY/hXGBQABaAEGXoRoAWCEmP5vKAABABMgAQAAABcAAAAAAAAAAAAAAAAA
AAAAAAAACxgAAA+EaAERhJj+FcYFAAFoAQZehGgBYISY/k9KBgBRSgYAbygAAQCn8AYAAAAAAAEA
AAAAAAAAAAAAAAAAAAAAAAMYAAAPhBsDEYTl/BXGBQABGwMGXoQbA2CE5fxvKAABAAAAAQAAABcA
AAAAAAAAAAAAAAAAAAAAAAAACxgAAA+EaAERhJj+FcYFAAFoAQZehGgBYISY/k9KAQBRSgEAbygA
AQC38AAAAAAXAAAAAAAAAAAAAAAAAAAAAAAAAAMYAAAPhGgBEYSY/hXGBQABaAEGXoRoAWCEmP5v
KAABABMgBQAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAxgAAA+E4AERhCD+FcYFAAHgAQZehOABYIQg
/m8oAAEAAAADAAAAAAABAwAAAAAAAAAAAAAAAAAAAAADGAAAD4TgARGEIP4VxgUAAeABBl6E4AFg
hCD+bygAAwAAAC4AAQADAAAAAAABAwUAAAAAAAAAAAAAAAAAAAADGAAAD4TQAhGEMP0VxgUAAdAC
Bl6E0AJghDD9bygABQAAAC4AAQAuAAIAAQAAAAAAAQMFBwAAAAAAAAAAAAAAAAAAAxgAAA+E0AIR
hDD9FcYFAAHQAgZehNACYIQw/W8oAAcAAAAuAAEALgACAC4AAwABAAAAAAABAwUHCQAAAAAAAAAA
AAAAAAADGAAAD4Q4BBGEyPsVxgUAATgEBl6EOARghMj7bygACQAAAC4AAQAuAAIALgADAC4ABAAB
AAAAAAABAwUHCQsAAAAAAAAAAAAAAAADGAAAD4Q4BBGEyPsVxgUAATgEBl6EOARghMj7bygACwAA
AC4AAQAuAAIALgADAC4ABAAuAAUAAQAAAAAAAQMFBwkLDQAAAAAAAAAAAAAAAxgAAA+EoAURhGD6
FcYFAAGgBQZehKAFYIRg+m8oAA0AAAAuAAEALgACAC4AAwAuAAQALgAFAC4ABgABAAAAAAABAwUH
CQsNDwAAAAAAAAAAAAADGAAAD4SgBRGEYPoVxgUAAaAFBl6EoAVghGD6bygADwAAAC4AAQAuAAIA
LgADAC4ABAAuAAUALgAGAC4ABwABAAAAAAABAwUHCQsNDxEAAAAAAAAAAAADGAAAD4QIBxGE+PgV
xgUAAQgHBl6ECAdghPj4bygAEQAAAC4AAQAuAAIALgADAC4ABAAuAAUALgAGAC4ABwAuAAgAGgAA
AChWqmoAAAAAAAAAAAAAAADlQbFrAAAAAAAAAAAAAAAAyG0bQQAAAAAAAAAAAAAAALsOfDUAAAAA
AAAAAAAAAABEI+g6AAAAAAAAAAAAAAAAc3+WJgAAAAAAAAAAAAAAAAlTMCIAAAAAAAAAAAAAAAAB
bKlZAAAAAAAAAAAAAAAAWDSvQAAAAAAAAAAAAAAAAGZZsUkAAAAAAAAAAAAAAACmG4VZAAAAAAAA
AAAAAAAA8Fe0bQAAAAAAAAAAAAAAAFkz4V4AAAAAAAAAAAAAAAC+X0sWAAAAAAAAAAAAAAAAtljh
WQAAAAAAAAAAAAAAAJV15GoAAAAAAAAAAAAAAAA9JAsmAAAAAAAAAAAAAAAAkjG+JQAAAAAAAAAA
AAAAANhj1jMAAAAAAAAAAAAAAACQU34fAAAAAAAAAAAAAAAAPV9dVwAAAAAAAAAAAAAAAGBUBAAA
AAAAAAAAAAAAAACxVBtQAAAAAAAAAAAAAAAAqn7ATQAAAAAAAAAAAAAAAIgdJXsAAAAAAAAAAAAA
AADhAeIIAAAAAAAAAAAAAAAA////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////////xoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAA//8aAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAHAgAACQIAAAsCAAA0AgAANQIAADYCAAA3AgAAOAIAAD4CAABFAgAARgIA
AHgCAACJAgAAigIAAIkDAACKAwAA3gMAAN8DAAA4CAAAOQgAAJAIAACRCAAAaVAAALFQAACyUAAA
s1AAAL9QAADAUAAA3lAAAAZRAAAPUQAAGlEAACNRAAAsUQAANVEAAEtRAABMUQAAUVEAAHdRAAB9
UQAAg1EAAIlRAACPUQAAk1EAAJVRAACWUQAAm1EAAOdRAAD1UQAAA1IAAAVSAAAHUgAACVIAAAtS
AAAMUgAAEVIAADxSAABMUgAAXFIAAGNSAABqUgAAcVIAAHNSAAB0UgAAeVIAAIVSAACVUgAAl1IA
AJhSAACnUgAAqFIAAIJUAACDVAAAC1UAAAxVAABzVQAAdFUAANdWAADYVgAA2VYAAGJXAADYXAAA
2VwAANphAAD2YQAAAGIAABhiAAAoYgAAO2IAADxiAAA+YgAAd2IAALRiAADVYgAA1mIAANhiAAAO
YwAAD2MAADZjAAA3YwAAOWMAAGtjAACJYwAAqmMAAKtjAACtYwAAzGMAAM1jAAD0YwAA9WMAAPdj
AAA2ZAAAUGQAAF9kAABgZAAAYmQAAJNkAAC0ZAAAw2QAAMRkAAAUaQAAFWkAALRpAADCaQAA1GkA
AOZpAAD1aQAA9mkAAPhpAAACagAADGoAABZqAAAXagAAGWoAABpqAAAkagAALmoAAC9qAACcagAA
rGoAAOtqAADsagAA/WoAAAZrAAAHawAAEmsAABlrAAAaawAAgX0AANh9AADdfQAAD34AAB9+AAAg
fgAAL34AADV+AAA7fgAAPH4AAFR+AABZfgAAXn4AAF9+AABsfgAAcX4AAHZ+AAB3fgAAfH4AAIF+
AACGfgAAh34AAF+AAABggAAAZ4AAAGiAAABxgAAAcoAAAH6AAAB/gAAAsoAAALOAAADJgAAAyoAA
AN6AAADfgAAA44AAAOSAAADogAAA6YAAAOyAAADtgAAA8IAAAPGAAADygAAAAYEAAAKBAAADgQAA
HYoAAF6KAABmigAAZ4oAAGiKAABxigAAcooAAHOKAAB8igAAfYoAAIaKAACLigAAjooAAI+KAACQ
igAAkYoAAJKKAACTigAAmYoAAKCKAACjigAApooAAKeKAACoigAAqYoAAKqKAACrigAArIoAAK2K
AACuigAAr4oAALCKAACxigAAsooAAMGKAADFigAAy4oAAM2KAADSigAA3YoAAN6KAADfigAA4IoA
AOGKAADiigAA44oAAOSKAADligAA5ooAAOeKAAD0igAA9YoAAPaKAAD5igAA+ooAAPuKAAD9igAA
/ooAAP+KAAAAiwAAAYsAAAKLAAADiwAABIsAAAWLAAAGiwAAD4sAABGLAAAbiwAAHIsAAB2LAAAm
iwAAJ4sAACiLAAAziwAANYsAADiLAAA7iwAAPIsAAD+LAABCiwAAQ4sAAFSLAABWiwAAWIsAAFqL
AABbiwAAXYsAAF+LAABgiwAAaYsAAGuLAABtiwAAb4sAAHCLAAByiwAAdIsAAHWLAACJiwAAi4sA
AI2LAACPiwAAkIsAAJKLAACUiwAAlYsAAJaLAACXiwAAmIsAAJmLAACaiwAAm4sAAJyLAACdiwAA
posAAKiLAACyiwAAs4sAALSLAAC9iwAAvosAAL+LAADKiwAAzIsAAM+LAADSiwAA04sAANaLAADZ
iwAA2osAAOuLAADtiwAA74sAAPGLAADyiwAA9IsAAPaLAAD3iwAAAIwAAAKMAAAEjAAABowAAAeM
AAAJjAAADIwAAA2MAAAhjAAAI4wAACWMAAAnjAAAKIwAACqMAAAsjAAALYwAAC6MAAAvjAAAMIwA
ADGMAAAyjAAAM4wAADSMAAA1jAAAQowAAEOMAABEjAAAR4wAAEiMAABJjAAAS4wAAEyMAABNjAAA
TowAAE+MAABQjAAAUYwAAFKMAABTjAAAVIwAAF6MAABfjAAAYIwAAGSMAABljAAAZowAAGmMAABq
jAAA+I4AADCPAAAxjwAAO48AAEGPAABCjwAAU48AAFaPAAB7jwAAfI8AAJCPAACTjwAAqY8AAKqP
AAC/jwAAwo8AANKPAADTjwAA1I8AANWPAADWjwAA148AAOGPAADkjwAA5Y8AAOaPAACEkwAAhZMA
AIaTAACQkwAAlpMAAJeTAACokwAAq5MAANCTAADRkwAA6JMAAOuTAAABlAAAApQAABeUAAAZlAAA
SZQAAEqUAABalAAAXJQAAF2UAABelAAAaJQAAGuUAABslAAAbZQAAD6VAACElQAAjJUAAI2VAACO
lQAAl5UAAJiVAACZlQAAopUAAKOVAACslQAArZUAALCVAACxlQAAspUAALOVAAC0lQAAtZUAALuV
AADBlQAAxJUAAMiVAADJlQAAypUAAMuVAADMlQAAzZUAAM6VAADPlQAA0JUAANGVAADSlQAA05UA
/f///wICAAADAgAABAIAAAUCAAAGAgAABwIAAAgCAAAJAgAACgIAAAsCAAAMAgAA/v//////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////////////8A
1JUAAOOVAADnlQAA7ZUAAO+VAAD0lQAAAJYAAAGWAAAClgAAA5YAAASWAAAFlgAABpYAAAeWAAAI
lgAACZYAAAqWAAAXlgAAGJYAABmWAAAclgAAHZYAAB6WAAAglgAAIZYAACKWAAAjlgAAJJYAACWW
AAAmlgAAJ5YAACiWAAAplgAAMpYAADSWAAA+lgAAP5YAAECWAABJlgAASpYAAEuWAABWlgAAWJYA
AFuWAABelgAAX5YAAGKWAABllgAAZpYAAHeWAAB5lgAAe5YAAH2WAAB+lgAAgJYAAIKWAACDlgAA
jJYAAI6WAACQlgAAkpYAAJOWAACVlgAAl5YAAJiWAACslgAArpYAALCWAACylgAAs5YAALWWAAC3
lgAAuJYAALmWAAC6lgAAu5YAALyWAAC9lgAAvpYAAL+WAADAlgAAyZYAAMuWAADVlgAA1pYAANeW
AADglgAA4ZYAAOKWAADzlgAA9ZYAAPeWAAD5lgAA+pYAAPyWAAD+lgAA/5YAAAiXAAAKlwAADJcA
AA6XAAAPlwAAEZcAABSXAAAVlwAAKZcAACuXAAAtlwAAL5cAADCXAAAylwAANJcAADWXAAA2lwAA
N5cAADiXAAA5lwAAOpcAADuXAAA8lwAAPZcAAEaXAABIlwAAUpcAAFOXAABUlwAAXZcAAF6XAABf
lwAAapcAAGyXAABvlwAAcpcAAHOXAAB2lwAAeZcAAHqXAACLlwAAjZcAAI+XAACRlwAAkpcAAJSX
AACWlwAAl5cAAKCXAACilwAApJcAAKaXAACnlwAAqZcAAKyXAACtlwAAwZcAAMOXAADFlwAAx5cA
AMiXAADKlwAAzJcAAM2XAADOlwAAz5cAANCXAADRlwAA0pcAANOXAADUlwAA1ZcAAOKXAADjlwAA
5JcAAOeXAADolwAA6ZcAAOuXAADslwAA7ZcAAO6XAADvlwAA8JcAAPGXAADylwAA85cAAPSXAAD1
lwAA9pcAAPeXAAD4lwAA+ZcAAPqXAAD7lwAA/JcAAAaYAAAHmAAACJgAAAyYAAANmAAADpgAABGY
AAASmAAApZkAAPCZAAD1mQAAJ5oAACiaAAA3mgAAPpoAAD+aAABXmgAAXZoAAF6aAABrmgAAcZoA
AHKaAAB3mgAAfJoAAH2aAACW4wAA3uMAAPLjAAD/4wAAB+QAAAjkAAAY5AAAMOQAAJLkAACT5AAA
teQAAMjkAABL5QAATOUAAHDlAACG5QAAh+UAAIjlAACV+gAAqvoAAJb7AADB+wAAAQAAAAEAAAAI
AAAAAgEAAAIBAACWAQABAAAAAAAAAAAIAAAAAgEAAAIBAACeAQABAgEAAAIBAACWAQABAQAAAAgA
AAACAQAAngEAAQIBAACeAQABAgEAAJYBAAEBAAAACAAAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEA
AAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAA
AgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAAC
AQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAngEAAQIBAACeAQABAgEAAJ4B
AAECAQAAngEAAQIBAACeAQABAgEAAJYBAAEAAAAACAAAAAIBAACWAQABAQAAAAgAAAACAQAAAgEA
AAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAA
AgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEAAJ4BAAEC
AQAAAgEAAAIBAAACAQAAlgEAAQAAAAAAAAAACAAAAAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIB
AAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAlgEAAQgAAAACAQAAAgEAAJ4BAAECAQAAAgEA
AJ4BAAECAQAAAgEAAJYBAAEBAAAACAAAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAACeAQAB
AgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAACWAQABAQAAAAgAAAAC
AQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIB
AACeAQABAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAJYBAAEBAAAACAAAAAIBAAACAQAAAgEA
AAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAA
AgEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIBAACe
AQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEAAAIB
AAACAQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEA
AAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAACAQAA
AgEAAAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAEC
AQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIB
AACeAQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEA
AAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAA
AgEAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAAC
AQAAAgEAAAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4B
AAECAQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEA
AAIBAACeAQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJYBAAEBAAAACAAAAAIBAAACAQAA
AgEAAJ4BAAECAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAJ4BAAEC
AQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAlgEAAQEAAAAIAAAAAgEAAAIBAAACAQAAngEAAQIB
AAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEA
AJ4BAAECAQAAAgEAAAIBAACWAQABAQAAAAgAAAACAQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAA
ngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEAAAIBAAAC
AQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIB
AAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEA
AAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIBAACeAQAB
AgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEAAAIBAAAC
AQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEAAAIB
AAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEA
AAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAA
AgEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIBAACe
AQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEAAAIB
AAACAQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEA
AAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAACAQAA
AgEAAAIBAAACAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAEC
AQAAAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIB
AACeAQABAgEAAAIBAAACAQAAAgEAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAAACAQAAAgEA
AAIBAAACAQAAngEAAQIBAAACAQAAAgEAAAIBAAACAQAAAgEAAAIBAACWAQABAQAAAAgAAAACAQAA
AgEAAJ4BAAECAQAAAgEAAJ4BAAECAQAAAgEAAJ4BAAECAQAAAgEAAJ4BAAECAQAAAgEAAJYBAAEB
AAAACAAAAAIBAAACAQAAAgEAAJ4BAAECAQAAAgEAAAIBAACeAQABAgEAAAIBAAACAQAAngEAAQIB
AAACAQAAAgEAAJYBAAEAAAAAAQAAAAEAAAD/QFxcSFFTMVxIUVMxUFI0MwBOZTAwOgB3aW5zcG9v
bABIUCBMYXNlckpldCA1TQBcXEhRUzFcSFFTMVBSNDMAAAAAAAAAAAAAAAAAAAAAAAEEAQOcAHAA
A3MBAAEAAQAAAAAAAAABAA8AWAICAAEAWAICAAAATGV0dGVyAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAgAP////85AwAAAAAAAP//////////AAANAAYANgAAAAAA//8AAAEA//8BAAEAAAD//wEAAwD/
//////////////////////////////////////8AAAAAGAAAAAAAECcQJxAnAAAQJwAAAAAAAAAA
XFxIUVMxXEhRUzFQUjQzAAAAAAAAAAAAAAAAAAAAAAABBAEDnABwAANzAQABAAEAAAAAAAAAAQAP
AFgCAgABAFgCAgAAAExldHRlcgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAD/////OQMAAAAAAAD/
/////////wAADQAGADYAAAAAAP//AAABAP//AQABAAAA//8BAAMA////////////////////////
////////////////AAAAABgAAAAAABAnECcQJwAAECcAAAAAAAAAAACAAQAAAAAAAAAAAGBYnQQB
AAEAAAAAAAAAAwAAAAAAlP9uBAIQAAAAAAAAAMD7AADAAAAIAEAAAP//AQAAAAcAVQBuAGsAbgBv
AHcAbgD//wEACAAAAAAAAAAAAAAA//8BAAAAAAD//wAAAgD//wAAAAD//wAAAgD//wAAAAAHAAAA
RxaQAQAAAgIGAwUEBQIDBIc6ACAAAAAAAAAAAAAAAAD/AQAAAAAAAFQAaQBtAGUAcwAgAE4AZQB3
ACAAUgBvAG0AYQBuAAAANRaQAQIABQUBAgEHBgIFBwAAAAAAAAAQAAAAAAAAAAAAAACAAAAAAFMA
eQBtAGIAbwBsAAAAMyaQAQAAAgsGBAICAgICBIc6ACAAAAAAAAAAAAAAAAD/AQAAAAAAAEEAcgBp
AGEAbAAAADsikAEAAAILBgQCAgICAgQDAAAAAAAAAAAAAAAAAAAAAQAAAAAAAABIAGUAbAB2AGUA
dABpAGMAYQAAADkWkAHuAAICBgMFBAUCAwQFAAAAAAAAAAAAAAAAAAAAAgAAAAAAAABDAEcAIABU
AGkAbQBlAHMAAAA1JpABAAACCwYEAwUEBAIEh3oAIQAAAIAIAAAAAAAAAP8BAQAAAAAAVABhAGgA
bwBtAGEAAAA7BpABAgAFAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAIAAAAAAVwBpAG4AZwBk
AGkAbgBnAHMAAAAiAQQAAQQIGFb80AIAAGgBAAAAABM7aiYTO2omcWpbRgIAAgAAAD8kAACezgAA
AQBpAAAABACDALgBAAD/DgAAfFUAAAEAKwAAALYAAAAAAAAAIQNW/BCEAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAApQbAB7QAtACAABIwAAAQABkAZAAAABkAAAC9/QAAe2QAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAG4oAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAA
AAAAMoMRVvwQhN8DAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA//8SAAAAAAApAEMAOgBc
AE0AUwBPAGYAZgBpAGMAZQBcAFQAZQBtAHAAbABhAHQAZQBzAFwAUQBVAEkAQwBLAFAAVQBCAFwA
RgBMAEEAUwBIAEUALgBEAE8AVAAVAFIAZQBjACAAWQAuADEANQA0ADEAIAAoADEAMAAvADAAMwAv
ADAAMQApAAAAAAAAAAcASwBDAEcALwBBAEMATQAHAEQASQBTAEEATgBlAHQAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

------_=_NextPart_000_01C281DE.9AED4900--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  2 15:05:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAB11603
	for <ieprep-archive@odin.ietf.org>; Sat, 2 Nov 2002 15:05:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA2K7Os18015
	for ieprep-archive@odin.ietf.org; Sat, 2 Nov 2002 15:07:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2K7Ov18012
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 2 Nov 2002 15:07:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11597
	for <ieprep-web-archive@ietf.org>; Sat, 2 Nov 2002 15:04:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2K6Mv17417;
	Sat, 2 Nov 2002 15:06:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2K5cv17381
	for <ieprep@optimus.ietf.org>; Sat, 2 Nov 2002 15:05:38 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11591
	for <ieprep@ietf.org>; Sat, 2 Nov 2002 15:03:06 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA2Jxdd19254;
	Sat, 2 Nov 2002 11:59:39 -0800 (PST)
Date: Sat, 2 Nov 2002 11:59:38 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Scott  Bradner <sob@harvard.edu>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-Reply-To: <200211021639.gA2Gdjaq007031@newdev.harvard.edu>
Message-ID: <Pine.GSO.4.44.0211020857410.11694-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > User Requirements - 1-5
    >   1  Users should be able to use public telecommunication
    >      resources for supporting emergency communications to help
    >      organize and coordinate immediate disaster recovery
    >      operations.

This is a statement which appears to be of the form "Toast should exist."
It's confused, however, by the use of a number of phrases which appear to
have ambiguous meanings, as used by the authors.  I generally think of the
phrase "users" as meaning "members of the general computer-using public,"
whereas the authors seem to think "users" is synonymous with "NCS".  As
Scott points out, "public telecommunications resources" might or might not
mean the Internet, or the PSTN, or something else.  "Disaster recovery
operations" might mean my concept of a disaster, which would be packets
not being delivered, or it might mean NCS's concept of a disaster which
would presumably be something to do with middle-aged white Republicans in
funny hats fretting about something on the other side of the globe.

    >   2  Users that access emergency telecommunications service must
    >      be authenticated.  This should be accomplished in a timely
    >      manner.

This appears to bring one potential definition of "user" into conflict
with one of the other goals, which as I understood it, required anonymity
for the answering party.  What the heck does "timely manner" mean?  Before
the end of the telco's monthly billing cycle?  Before data begins to flow?
Before it stops flowing?

Why would authentication be a requirement, anyway?  The content of the
call must not be very important, if it's less important than the identity
of the caller.  I don't think I want to clog up my network with
unimportant data.  I'd rather fill it with revenue-generating gamers and
porn-viewers and so forth.

    >   3  When networks reach traffic saturation emergency
    >      communication sessions should be provided with a
    >      higher probability of completion over non-emergency
    >      communications.

Network saturation and emergency communication sessions exist in
completely different, and relatively orthoganal temporal frames of
reference.  I would presume that emergency communication sessions (if
they're voice) would last seconds, or maybe even minutes.  This seems to
me sort of like requiring an elephant to interact with an electron.  Yes,
they'll interact, but not in a manner which is likely to be easily
governed by notional rules, rather than physical ones.

Besides, "emergency communications sessions" seems only to be defined as
"communications between authorized users," which itself is completely
undefined.  My authorized users may be completely different than your
authorized users.  My perception of an emergency is _quite likely_ to be
very different than your perception of an emergency.  In the unlikely
event of network congestion of a scale which would be addressable in the
manner posited here, it's likely that quite a lot of people's incompatible
notions of emergency would be simultaneously applicable.  If the Bahai'i
are paying me, and the RCMP are not, I think you know whose emergency will
receive priority service, in the event that such service exists.

    >    3 We assume the presence of a service level
    >      agreement to accomplish this latter case.

Yeah, so this sentence needs to go away, since we're a technical body.

    >    3 Sessions identified as emergency communication could be
    >      processed as normal traffic along with all non-emergency
    >      traffic...

Replace "identified as" with "which someone considers to be" and we're
doing okay so far...

    >    3 ...when sufficient network bandwidth and resources are
    >      available.

By what definition?

    >   4  Once an emergency communications session is established,
    >      the user should be able to complete the session without
    >      being interrupted

"Toast SHOULD fly, though it won't."

Whether the session terminates at the behest of one of the parties, or
sooner, is not under the control of the users.  That would be a question
of luck.  Luck is unfortunately not swayed by the existence of IETF
documents.

    >   3  or having the quality of the communications be degraded
           excessively.

Ditto.

    >   5  There must exist a mapping association between labels
    >      defined by various standards bodies.  This mapping will
    >      help facilitate inter-working of services in cases where
    >      gateways and networks support emergency telecommunications
    >      services.

"Toast MUST fly!"  This MUST is outside the capability of the IETF to
autonomously actualize, though it would be nice.

                                -Bill






_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  2 16:14:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12485
	for <ieprep-archive@odin.ietf.org>; Sat, 2 Nov 2002 16:14:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA2LG4h20879
	for ieprep-archive@odin.ietf.org; Sat, 2 Nov 2002 16:16:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2LG4v20875
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 2 Nov 2002 16:16:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12482
	for <ieprep-web-archive@ietf.org>; Sat, 2 Nov 2002 16:13:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2LFAv20847;
	Sat, 2 Nov 2002 16:15:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2LEov20815
	for <ieprep@optimus.ietf.org>; Sat, 2 Nov 2002 16:14:50 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12430
	for <ieprep@ietf.org>; Sat, 2 Nov 2002 16:12:18 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA2LE3Si007615
	for ieprep@ietf.org; Sat, 2 Nov 2002 16:14:03 -0500 (EST)
Date: Sat, 2 Nov 2002 16:14:03 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211022114.gA2LE3Si007615@newdev.harvard.edu>
To: ieprep@ietf.org
Subject: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

ieprep-requirements-01requirements 6 - 10 

comments requested

Scott
-
  6 Emergency traffic should be able to transit multiple
    service providers.  The existence of service level
    agreements determines the extent by which this can be
    accomplished.

>> at one level this is a given (i.e. emergency services provided
>> over best effort IP services) but for any other service (e.g.,
>> a defined QoS service) it is not possible today - for both 
>> technical and business reasons - it does not seem to be a 
>> good idea to have requirements that just can not be met
>> note that "service level agreements", where they exist, are 
>> between customers of an ISP and that ISP, not between ISPs
>> so I do not know how SLAs relate to the proposed requirement

  7 Networks should be able to support a variety of user
    applications including telephony, video, database access,
    messaging, telemetry, and web browsing to support emergency
    operations.
   
>> I'm not sure what this means 

>> IP networks forward IP packets - they do not do anything
>> that is application specific unless they are running a
>> application server and even then there is no requirement for 
>> individual users to use the ISPs server, the users could have 
>> their own server or use a server provided by a 3rd party

>> by forwarding IP packets ISPs support all of these applications
>> and many other applications but never know what the applications
>> are so can not do any application-specific special handling

>> this requirement could be written that emergency services
>> should be defined at the IP-packet level so that any 
>> application can make use of them or it could be directed
>> at providers of application-level services (like web servers)
>> which, as a general rule, have no particular
>> relationship to an ISP (and certainly not to all ISPs 
>> between a user and the server they might be using)  

  8 Authorized emergency communications should be protected
    from intrusion or interference, such as, spoofing, change
    of content, and denial of service.  If the protection
    cannot be accomplished, then users must be able to detect
    this failure.

>> In IP applications these functions are normally done end-to-
>> end at the applications layer - the ISP is not involved -
>> so I'm not sure what specific requirement can be directed at 
>> ISPs here

  9 Users should have the option protecting certain sensitive
    traffic from eavesdropping and the source/destination of
    some traffic.
   
>> see #8 - protecting sensitive traffic is an application 
>> layer issue, not a network one - for example, the end to end 
>> traffic can be encrypted by the application itself

>> I'm not sure how one can do protection of source and
>> destination network-layer addresses since they are needed
>> to deliver the packets (there are some anonymizing technologies
>> that can be used at the application layer or even packet layer
>> but these are services run over IP networks not functions that
>> are part of an ISP (for example)

 10 Users should have the option of requesting degraded quality
    of service when normal or expected QoS cannot be achieved.

>> see previous set of requirements about QoS - this requirement 
>> is not specific enough - does it refer to an enterprise net
>> (such as the internal IP network at a telephone company), a
>> single ISP or the Internet

>> also - since there is not yet a clear definition as to what 
>> particular QoS technologies is implied by the QoS requirements 
>> it is hard to say what it means to ask for degraded service
>> - at one level, the user can always fall back to plain best
>> effort service 

>> it is not clear that this requirement is needed in many cases - 
>> if ieprep traffic is prioritized in some way, this degrading
>> will automatically happen if there is more emergency traffic
>> than network capacity allocated by the ISP to providing 
>> emergency services

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  2 20:16:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16439
	for <ieprep-archive@odin.ietf.org>; Sat, 2 Nov 2002 20:16:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA31Ieq00836
	for ieprep-archive@odin.ietf.org; Sat, 2 Nov 2002 20:18:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA31Iev00833
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 2 Nov 2002 20:18:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16435
	for <ieprep-web-archive@ietf.org>; Sat, 2 Nov 2002 20:16:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA31HJv00755;
	Sat, 2 Nov 2002 20:17:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA31GBv00712
	for <ieprep@optimus.ietf.org>; Sat, 2 Nov 2002 20:16:11 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16400
	for <ieprep@ietf.org>; Sat, 2 Nov 2002 20:13:37 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 1889Ml-0005tk-00; Sat, 02 Nov 2002 20:15:51 -0500
Date: Sat, 2 Nov 2002 20:15:51 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: ieprep@ietf.org
Subject: RE: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework
 -02.txt
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3CD7@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211021919050.22656-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Fri, 1 Nov 2002, Nguyen, An wrote:
> While still on this QoS topic, is anyone aware of the ITU-T Y.1541 which
> defines QoS parameters in the IP networks?

As the saying goes, the great thing about standards is there are so many
to choose from.

Yep, ITU-T Y.1541 has come up at the IP Performance Measurement WG's.  In
the 1990's ANSI ATIS/T1A1 also wrote several technical reports about what
Internet performance "should" be.  Remember just because you write a
standard doesn't mean anyone must (or will) follow it.

How many folks are familar with James Burton's book The Pentagon Wars?


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov  3 05:27:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03002
	for <ieprep-archive@odin.ietf.org>; Sun, 3 Nov 2002 05:27:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA3AT5N05578
	for ieprep-archive@odin.ietf.org; Sun, 3 Nov 2002 05:29:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA3AT5v05575
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 3 Nov 2002 05:29:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02999
	for <ieprep-web-archive@ietf.org>; Sun, 3 Nov 2002 05:26:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA3ASJv05559;
	Sun, 3 Nov 2002 05:28:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA3ARKv05536
	for <ieprep@optimus.ietf.org>; Sun, 3 Nov 2002 05:27:20 -0500
Received: from bootstrap.agcs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02996
	for <ieprep@ietf.org>; Sun, 3 Nov 2002 05:24:53 -0500 (EST)
Received: from pxmail1.agcs.com (pxmail1.agcs.com [130.131.52.9])
	by bootstrap.agcs.com (Pro-8.9.3/8.9.3) with ESMTP id DAA11679
	for <ieprep@ietf.org>; Sun, 3 Nov 2002 03:27:17 -0700 (MST)
Received: from mkultra ([130.131.166.68]) by pxmail1.agcs.com
          (Netscape Messaging Server 4.15 pxmail1 Mar  5 2002 15:11:07)
          with SMTP id H4ZX1H00.KN3 for <ieprep@ietf.org>; Sun, 3 Nov 2002
          03:27:17 -0700 
Received: FROM agcs.com BY mkultra ; Sun Nov 03 03:27:16 2002 -0700
Message-ID: <3DC4FA04.49F67B1@agcs.com>
Date: Sun, 03 Nov 2002 03:27:16 -0700
From: "Stuart (Stu) Goldman" <goldmans@agcs.com>
Reply-To: goldmans@agcs.com
Organization: AG Communication Systems
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: gthom@delta-info.com
CC: ieprep@ietf.org
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
References: <NDBBKMIGCLLNAOGKKDDPEEDGDDAA.gthom@delta-info.com>
Content-Type: multipart/mixed;
 boundary="------------33B3FD9D63872E794698C6BB"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.
--------------33B3FD9D63872E794698C6BB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Gary,

Well said.

Gary Thom wrote:

> Is anyone else getting tired of listenning to this mis-conceived,
> self-serving, never ending argument????

--------------33B3FD9D63872E794698C6BB
Content-Type: text/x-vcard; charset=us-ascii;
 name="goldmans.vcf"
Content-Description: Card for Stuart (Stu) Goldman
Content-Disposition: attachment;
 filename="goldmans.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Goldman;-Stuart
tel;cell:623 582 7136
tel;fax:623 582 7111
tel;home:602 493 8438  
tel;work:623 582 7136
x-mozilla-html:TRUE
org:AG Communication Systems
adr:;;P.O. Box 52179;Phoenix;AZ;85072-2179;USA
version:2.1
email;internet:goldmans@agcs.com
x-mozilla-cpt:;-12184
fn:Stuart Goldman
end:vcard

--------------33B3FD9D63872E794698C6BB--

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 13:25:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27223
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 13:25:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4IRBE13012
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 13:27:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4IRBv13009
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 13:27:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27171
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 13:24:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4IQAv12958;
	Mon, 4 Nov 2002 13:26:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4IP3v12914
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 13:25:03 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27008
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 13:22:29 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Mon, 4 Nov 2002 10:22:00 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gA4IN5b9027829;
	Mon, 4 Nov 2002 10:23:05 -0800 (PST)
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
From: Rex Buddenberg <budden@nps.navy.mil>
To: Scott Bradner <sob@harvard.edu>
Cc: ieprep@ietf.org
In-Reply-To: <200211022114.gA2LE3Si007615@newdev.harvard.edu>
References: <200211022114.gA2LE3Si007615@newdev.harvard.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 04 Nov 2002 10:21:43 -0800
Message-Id: <1036434106.2801.44.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Sat, 2002-11-02 at 13:14, Scott Bradner wrote:
> ieprep-requirements-01requirements 6 - 10 
> 
> comments requested
> 
> Scott
Comments herewith; in line.
> 
>   7 Networks should be able to support a variety of user
>     applications including telephony, video, database access,
>     messaging, telemetry, and web browsing to support emergency
>     operations.

Some comments on this newsgroup indicate that we need to keep reminding
ourselves of this.  
>  
> 

Security

>   8 Authorized emergency communications should be protected
>     from intrusion or interference, such as, spoofing, change
>     of content, and denial of service.  If the protection
>     cannot be accomplished, then users must be able to detect
>     this failure.
> 
Good.  It may help if you abstract the security problem into three
categories:
  - data security (for which object level security solutions are
appropriate)
  - enclaving and resistance to denial of service attacks
  - link security issues such as traffic analysis, interceptability,
jammability


> 
>   9 Users should have the option protecting certain sensitive
>     traffic from eavesdropping and the source/destination of
>     some traffic.

My experience in DoD says that stating the right requirement to the
wrong union is just as bad as stating the wrong requirement.

1.  Confidentiality is important in emergency traffic.  I'd rank
authenticity even higher (see spoofing in #8 above) -- if I were
building an application, I'd insist that all official business traffic
be authenticated.  But this tends to be no-nevermind because the
authenticity and confidentiality tools are the same at the application
layer.


> >> see #8 - protecting sensitive traffic is an application 
> >> layer issue, not a network one - for example, the end to end 
> >> traffic can be encrypted by the application itself
> 

2.  Authenticity and confidentiality requirements should be 
levied at Layer 7.  Part of applications, not plumbing. Good.
>    

QoS control
> 
>  10 Users should have the option of requesting degraded quality
>     of service when normal or expected QoS cannot be achieved.
> 
'Degraded service' at the expense of _____?  No service?

Assuming voice app, if I'm in an emergency situation I don't care about
tonal quality -- the voice conversation needs to be intelligible.  If
the 'net is congested, I'll live with seconds of latency if the message
comes through such that I can understand it.  

The floor should be best effort service -- I may want routing options
that normal traffic might not take.  But this is an operations plan
issue (e.g. changing firewall and static routing tables, bringing up a
radio-based altroute, etc), not a standards one.  What's important is
that our extra plumbing (paid for by the emergency services) not
immediately get clogged with non-emergent traffic.  What makes this hard
is the EMS-customer (taxpayer) interface: what a minute ago was Woody's
revenue-generating gamer is no a citizen reporting a fire on a
neighbor's house and a legit user of a better-than-best-effort QoS.

You need three parts of a complete mechanism and they're not all
susceptible to protocol fixes:
  - the net must react appropriately (to use diff-serv as example,
routers must read the DS byte and enqueue properly)
  - applications must state their requirements (e.g. set the DS byte or,
to jump to app layer, tell the VOIP SIP server that this is an emergency
call)
  - some kind of bandwidth brokering system so that non-emergent traffic
doesn't abuse the emergency privs.  (Perish the thought, but this may
require a legal remedy similar to the laws proscribing false emergency
phone calls).





_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 16:59:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09260
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 16:59:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4M13m08620
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:01:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4M13v08617
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:01:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09231
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 16:58:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4M09v08401;
	Mon, 4 Nov 2002 17:00:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Lxpv08169
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 16:59:51 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09103
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 16:57:16 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 282C167103; Mon,  4 Nov 2002 13:20:09 -0500 (EST)
Date: Mon, 4 Nov 2002 16:59:43 -0500
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DC2D339.8050004@cs.columbia.edu>
Message-Id: <B956FCC5-F040-11D6-812C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 1, 2002, at 14:17 America/Montreal, Henning Schulzrinne 
wrote:
> If you're objecting to having the IETF discuss interconnection with 
> the PSTN,

In draft-carlberg-ets-*, one of the suggestions I made was to 
editorially
clarify the scope of things by adding some words.  Things that might 
help
with regard to the above topic could look like (for example):

	IP Carriers who choose to offer IEprep services, choose to offer VoIP
	services (as an application-layer service, not just normal IP 
packets), and
	who choose to interconnect their VoIP service with the PSTN 
should...[whatever]

Words like that reassure operators who don't choose to offer one of the
required services of the IF clause, clarify the actual intent, and don't
remove any value, IMHO.

Editing several of our documents to have more words like that would be
generally helpful.  Putting words like "This document only applies to
operators who choose to offer [x], [y], and [z]." in a scoping paragraph
at the beginning of a document would also be helpful.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:04:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09489
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:04:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4M6o809002
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:06:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4M6ov08999
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:06:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09450
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:04:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4M61v08917;
	Mon, 4 Nov 2002 17:06:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4M2av08782
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:02:36 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09314
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:00:02 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 16F8C67103; Mon,  4 Nov 2002 13:22:57 -0500 (EST)
Date: Mon, 4 Nov 2002 17:02:30 -0500
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211011113070.28183-100000@paixhost.pch.net>
Message-Id: <1D2A9A68-F041-11D6-812C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 1, 2002, at 14:19 America/Montreal, Bill Woodcock wrote:
> The question is one of _mandating_ interconnection,
> which is clearly _not_ within the purview of the IETF, and 
> unfortunately
> _exactly_ the sort of thing that the U.S. government tries to do all 
> the
> time.  If that's _really not the intent here_, the document can be
> withdrawn, and there won't be a problem.

...or edited so that the real intent (no mandates) is crystal clear
to everyone who might read the document.  Kindly recall that most
folks who read an RFC do NOT read the charter of the WG that created
the RFC -- they ONLY read the actual RFC (and if you're lucky, maybe
some cross-referenced RFCs).

If the intent does not include levying mandates (funded or unfunded),
then PLEASE edit the documents to make that clear xor remove the
documents that say otherwise.

Thanks,

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:06:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09667
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:06:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4M8fP09703
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:08:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4M8fv09700
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:08:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09652
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:06:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4M81v09663;
	Mon, 4 Nov 2002 17:08:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4M7sv09637
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:07:54 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09540
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:05:20 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id EA9DA67103; Mon,  4 Nov 2002 13:28:14 -0500 (EST)
Date: Mon, 4 Nov 2002 17:07:48 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DC2D5C3.70702@cs.columbia.edu>
Message-Id: <DABE58AE-F041-11D6-812C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Re: QoS
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 1, 2002, at 14:28 America/Montreal, Henning Schulzrinne 
wrote:
> (I would be curious what concrete QoS routing has been deployed, 
> tested and discarded, given that none was ever really standardized in 
> the IETF, as far as I can tell. RFC 2386 seems to be the only output 
> of the QOSR working group that concluded in early 1999.)

OSPFv2 in Proteon's implementation (and a couple others, probably 
including
ACC's implementation) supported QoS routing using the IP ToS bits 
(RFC-791
definitions, not DiffServ definitions).  The DELAY bit actually worked 
quite
well trans-Pacific for selecting copper cable vs SATCOM hop in my own 
experience.

The precedence bits worked as designed -- though the design for them 
explicitly
meant that FLASH was intended to starve lower precedence values 
whenever necessary
to make sure the FLASH packets really got through.  This design might 
have
limited applicability in a commercial network than it did in the DDN.

It would be interesting to hear from Sean/Woody about which particular 
QoS
mechanisms they were referring to, but it isn't clear to me how much 
that
would be on topic here...

To Scott's point, I am not aware of any large-scale production IP 
network
today with any deployed QoS -- this includes the DISA IP networks (which
do not have deployed QoS and will not unless JCS grants explicit 
permission
to DISA in advance; I wouldn't hold my breath waiting for that either).

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:10:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09942
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:10:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4MClK09927
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:12:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MCkv09924
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:12:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09924
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:10:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MC2v09898;
	Mon, 4 Nov 2002 17:12:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MBEv09865
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:11:14 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09828
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:08:40 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id C956B67103; Mon,  4 Nov 2002 13:31:34 -0500 (EST)
Date: Mon, 4 Nov 2002 17:11:08 -0500
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: <gthom@delta-info.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPEEDGDDAA.gthom@delta-info.com>
Message-Id: <51DDB30F-F042-11D6-812C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 1, 2002, at 15:24 America/Montreal, Gary Thom wrote:
> First, there is no intent to mandate anything for anyone. If the 
> wording in
> the document gives you that impression, PLEASE someone change the 
> wording so
> we can get passed this point and not have to hear this argument again.

That change was requested by several people many months ago, but does 
not
appear to have permeated all the documents.  Now would be a fine time
to make those edits all over the place.

I think that draft-carlberg-ets-* largely have those edits in place 
today
(if not, someone please cite section/page/offending text in email to at 
least
Ken/me so the text can be fixed in that pair of documents).

> Second, the intent IS to provide information on the functionality that 
> is
> necessary (hence the term requirements) to support emergency 
> communications,
> when desired, on IP networks. This information will be provided to the
> people who develop the protocols (SIP in particular) so that they can 
> add
> the necessary OPTIONAL parameters and OPTIONAL procedures to the 
> protocol to
> support the the desired functionality.

Which document(s) are you specifically referring to above ?
Henning's only ?

> If a user wants this OPTIONAL functionality, the user will have to pay 
> for
> it. If the service provider does not want to provide it, the user can 
> go
> somewhere else.

Could we please state that more clearly several places in several 
documents ?
It would really help improve consensus here.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:12:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10003
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:12:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4MEfI10014
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:14:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MEfv10011
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:14:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09982
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:12:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4ME3v09992;
	Mon, 4 Nov 2002 17:14:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MDev09971
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:13:40 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09966
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:11:06 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id BA05E67103; Mon,  4 Nov 2002 13:34:00 -0500 (EST)
Date: Mon, 4 Nov 2002 17:13:34 -0500
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E778BF@mcl-its-exs01>
Message-Id: <A8C63480-F042-11D6-812C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 1, 2002, at 15:39 America/Montreal, King, Kimberly S. 
wrote:
> So they could increase their
> bandwidth to the exchange if that turned out to be a problem.  It 
> didn't
> sound like it was one.

	Most larger ISPs shun exchange points and strongly prefer private 
peering
-- in order to engineer congestion out of their networks (and out of 
their
access links with peers)  So the above is a bit of a misapprehension of 
the
deployed situation.  Exchange points aren't going to disappear entirely,
but most of the traffic growth is in private peering links (generally
these are bi-lateral pipes from A's core router to B's core router --
and generally there are N of them with geographic diversity).

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:15:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10224
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:15:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4MHe210197
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:17:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MHev10194
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:17:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10160
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:15:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MH1v10148;
	Mon, 4 Nov 2002 17:17:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MG2v10094
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:16:02 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10070
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:13:28 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP id B2D3267103
	for <ieprep@ietf.org>; Mon,  4 Nov 2002 13:36:22 -0500 (EST)
Date: Mon, 4 Nov 2002 17:15:56 -0500
Mime-Version: 1.0 (Apple Message framework v546)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: RJ Atkinson <rja@extremenetworks.com>
To: ieprep <ieprep@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <FD74F3C2-F042-11D6-812C-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Atlanta meeting agenda request
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Scott,

	I'd like to draft Sean/Woody to make a presentation on what a typical
ISP backbone network looks like today.  I think there is a lot of 
confusion
about what a typical network looks like.  A short 15-20 minute slot to
present one, discuss it, and field questions about it really might help
the WG get onto the same understanding of deployed reality.  Converging
understandings of reality (in both directions) might help improve WG
consensus.

	I'm willing to help with the above if desired, though I'm not operating
a largish backbone myself these days (though I was involved in a 
multi-continent
network engineering group in the past).

	What do you think ?

Thanks,

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:23:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10607
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:23:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4MPCG10555
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:25:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MPCv10552
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:25:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10576
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:22:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MO2v10515;
	Mon, 4 Nov 2002 17:24:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MNav10487
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:23:36 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10496
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:21:02 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 08DFA67103; Mon,  4 Nov 2002 13:43:57 -0500 (EST)
Date: Mon, 4 Nov 2002 17:23:29 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: "Nguyen, An" <nguyena@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3CD9@emshqs1.ncr.disa.mil>
Message-Id: <0B9741A7-F044-11D6-812C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Existing deployed networks...
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 1, 2002, at 17:41 America/Montreal, Nguyen, An wrote:
> There is no problem now with the core, I agree. But the picture might 
> look
> different later on.

Things might vary.  So far it has been a lot cheaper to throw bandwidth
at the problem than to increase the operational costs (deploying 
ANYTHING
extra increases operational costs; so QoS is not zero cost to deploy).

And there are tremendous amounts of spare fibre capacity today in most 
places
with significant IP deployment -- and that fibre is often lower cost to
purchase now than it was to originally build out.  So capacity is 
getting
cheaper, not more expensive, even today.

> Are you saying if there is any problem with the access node, the 
> network
> operators will solve the problem by throwing more equipment at it? The
> question is that how dynamic is that bandwidth increasing in response 
> to
> congestions?

The speed of the access link is normally controlled by the customer
behind that link.  This is normally a commercial/economic decision
by that customer.  For example, "do I pay the $ N+M for a T3 uplink
to ISP A or do I pay $N for a T1 uplink to ISP A ?"  And when I say
customer, that might be a home, a small office, a large office,
a campus, or a private network (e.g. GE's corporate WAN).

Inter-provider connectivity is increasingly performed via private
peering, not at exchange points.  Terminology varies, but I would
not call an exchange point an "access link".  And the exchange
points have mostly migrated to use 1 Gbps Ethernet and nearly
always on non-blocking switch fabrics [1].  I expect 10 GigE to
start deployment in exchange points during 2003.

Ran
rja@extremenetworks.com

[1] The old DEC GigaSwitch FDDI switches had a blocking switch fabric,
which caused significant operational grief throughout their lifetime.
Operators learn quickly -- so they always ask for non-blocking switches
for use in the exchange point situation.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:27:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10962
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:27:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4MTpK10764
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:29:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MTpv10761
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:29:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10940
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:27:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MT2v10731;
	Mon, 4 Nov 2002 17:29:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4MSev10703
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:28:40 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10879
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:26:06 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 338DF67103; Mon,  4 Nov 2002 13:49:00 -0500 (EST)
Date: Mon, 4 Nov 2002 17:28:32 -0500
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework -02.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: "Nguyen, An" <nguyena@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3CD7@emshqs1.ncr.disa.mil>
Message-Id: <C04A68B5-F044-11D6-812C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 1, 2002, at 14:41 America/Montreal, Nguyen, An wrote:

> While still on this QoS topic, is anyone aware of the ITU-T Y.1541 
> which
> defines QoS parameters in the IP networks?

Irrelevant.  ITU does not have any role in defining IP;
that is an IETF function.

Stuff that is implemented in real IP products or networks will nearly
always be specified in an RFC.  A few things exist that aren't well
specified anyplace.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:36:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11430
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:36:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4Mchl11836
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:38:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mchv11833
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:38:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11414
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:36:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mc1v11812;
	Mon, 4 Nov 2002 17:38:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mbov11779
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:37:50 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11387
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:35:16 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 65F7867103; Mon,  4 Nov 2002 13:58:10 -0500 (EST)
Date: Mon, 4 Nov 2002 17:37:43 -0500
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Rex Buddenberg <budden@nps.navy.mil>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <1036434106.2801.44.camel@localhost.localdomain>
Message-Id: <08415D9F-F046-11D6-812C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, Nov 4, 2002, at 13:21 America/Montreal, Rex Buddenberg wrote:
>>   8 Authorized emergency communications should be protected
>>     from intrusion or interference, such as, spoofing, change
>>     of content, and denial of service.  If the protection
>>     cannot be accomplished, then users must be able to detect
>>     this failure.
>>
> Good.  It may help if you abstract the security problem into three
> categories:
>   - data security (for which object level security solutions are
> appropriate)
>   - enclaving and resistance to denial of service attacks
>   - link security issues such as traffic analysis, interceptability,
> jammability

It is impossible to prevent denial-of-service attacks.  Terribly
sorry, but that is just the reality of the situation.  And it
won't be changing soon.

Given that, the earliest quoted text (not Rex's) is a lot like
one of Bill's "toast" comments.  Rex's suggestion is generally
on-target.  I would also like to see more clarity in which security
services are end-user responsibility (e.g. confidentiality) and
which (if any) are the VoIP/SIP/application-service-provider's
responsibility and which (if any) are the IP datgram forwarder's
responsibility.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:40:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11769
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:40:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4Mh2U12073
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:43:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mh2v12070
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:43:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11750
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:40:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mg2v12016;
	Mon, 4 Nov 2002 17:42:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mf9v11979
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:41:09 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11610
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:38:35 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP id E158A67103
	for <ieprep@ietf.org>; Mon,  4 Nov 2002 14:01:29 -0500 (EST)
Date: Mon, 4 Nov 2002 17:41:02 -0500
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
From: RJ Atkinson <rja@extremenetworks.com>
To: ieprep <ieprep@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <200211022114.gA2LE3Si007615@newdev.harvard.edu>
Message-Id: <7F20E63E-F046-11D6-812C-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


The general problem with most (all ?) of the listed "requirements"
is that they are what the IETF might call "goals" or "objectives".

Its true that in the DoD, such things are commonly called 
"requirements",
but that DoD-centric usage has clearly been causing a lot of grief here.

As "goals" or "objectives", some of the operator concerns are mitigated
because, for example, any implicit assumptions that real networks can 
violate
the laws of physics are made clear (and are removed from the document
reader's mind).

There really are problems with a number of the documents here.  In a 
whole
lot of cases, these problems are fixable with a heavy editorial pass.
At this point, I think we need to have such editing occur before the
group will be able to gauge consensus on moving forward.

Thanks,

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:48:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12234
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:48:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4Mo9H12360
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:50:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mo9v12357
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:50:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12218
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:47:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mn4v12281;
	Mon, 4 Nov 2002 17:49:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mm7v12241
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:48:07 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12096
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:45:33 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Mon, 4 Nov 2002 14:45:05 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gA4MkFb9011239;
	Mon, 4 Nov 2002 14:46:15 -0800 (PST)
Subject: Re: [Ieprep] Existing deployed networks...
From: Rex Buddenberg <budden@nps.navy.mil>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: "Nguyen, An" <nguyena@ncs.gov>, ieprep <ieprep@ietf.org>
In-Reply-To: <0B9741A7-F044-11D6-812C-00039357A82A@extremenetworks.com>
References: <0B9741A7-F044-11D6-812C-00039357A82A@extremenetworks.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 04 Nov 2002 14:44:52 -0800
Message-Id: <1036449893.2801.136.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Mon, 2002-11-04 at 14:23, RJ Atkinson wrote:
> 
> On Friday, Nov 1, 2002, at 17:41 America/Montreal, Nguyen, An wrote:
> > There is no problem now with the core, I agree. But the picture might 
> > look
> > different later on.
> 
> Things might vary.  So far it has been a lot cheaper to throw bandwidth
> at the problem than to increase the operational costs (deploying 
> ANYTHING
> extra increases operational costs; so QoS is not zero cost to deploy).
> 
> And there are tremendous amounts of spare fibre capacity today in most 
> places
> with significant IP deployment -- and that fibre is often lower cost to
> purchase now than it was to originally build out.  So capacity is 
> getting
> cheaper, not more expensive, even today.
>

Ran, you're right regarding the core of the network.  We've been
overprovisioning rather than controlling QoS almost universally for most
of the life of the Internet.

But the scenario we need to account for here is that the emergency
customers who need the priority services are at least a couple hops away
from the core.  IMHO, the best scenario is when one end of a connection
is on a wireless net at the edge of the internet fabric.  The second
best scenario is where we have a radio-WAN somewhere in the interior of
the network that is at least a router away from the customers (the
reason for the radio-WAN is either reach to mobile platforms or as
bridge across damaged connectivity, suit yourself).  It's network
plumbing that includes these features that we need to be engineering
for.



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:54:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12578
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:54:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4Mu7m12610
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 17:56:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mu7v12607
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 17:56:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12542
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:53:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mt2v12543;
	Mon, 4 Nov 2002 17:55:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Ms2v12497
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:54:02 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12449
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:51:28 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP id 12D8367103
	for <ieprep@ietf.org>; Mon,  4 Nov 2002 14:14:23 -0500 (EST)
Date: Mon, 4 Nov 2002 17:53:55 -0500
Mime-Version: 1.0 (Apple Message framework v546)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: RJ Atkinson <rja@extremenetworks.com>
To: ieprep <ieprep@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <4BD5ECF1-F048-11D6-812C-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Moving forward:  draft-carlberg-ets-*.txt
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi,

1) I appreciate Hal's note suggesting that draft-carlberg-ets-*.txt be 
made
WG documents.  I would ask that they be targeted as the standards-track
requirements [1] documents for those aspects of the current charter,
subject to whatever editing turns out to be necessary to get them into
a form congruent with WG Rough Consensus.

2) I would also ask Scott that we have *discussion* time for those
two documents in Atlanta on the IEprep Agenda. [1]

3) I'd like to ask that folks here please take time now, before Atlanta,
to read and critique the documents from Ken Carlberg (I kibbutzed, but 
the work
and words are mostly Ken's).  They are short documents (and I hope also
sweet :-).

General IP Carrier Requirements:
	draft-carlberg-ets-general-00.txt

Application-specific Requirements for IP Telephony:
	draft-carlberg-ets-telephony-00.txt


3B) I'm looking for slightly different kinds of review from our two 
segments
of participants.  From the folks worried about GETS-like stuff, please
focus on whether the core essentials did get documented clearly in those
two documents.  From the operators, is the verbage clear enough that 
there
is no intent for unfunded mandates or that an operator has to deploy any
of this stuff ?  Of course, feel free to comment on anything, but those
two questions are my core concern for the above documents at this time.

Thanks,

Ran
rja@extremenetworks.com

NOTES:
[1] IETF-definition for "requirements", not DoD-definition.  (I'd like 
to keep
Hal's document on what he thinks a GETS-like service might look like 
translated
into the global Internet, but that document doesn't contain 
IETF-requirements).
[2] I hate lots of presentations at IETF meetings, so I'm deliberately
asking for discussion time rather than presentation time.  I'd like to 
assume
that reasonable people will have read the drafts and that others will 
either
do so in real-time or keep quiet.



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 17:58:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12833
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 17:58:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4N09f12817
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 18:00:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4N08v12814
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 18:00:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12803
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 17:57:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mx1v12737;
	Mon, 4 Nov 2002 17:59:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Mwdv12720
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 17:58:39 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12710
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 17:56:05 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP id E639067103
	for <ieprep@ietf.org>; Mon,  4 Nov 2002 14:18:59 -0500 (EST)
Date: Mon, 4 Nov 2002 17:58:32 -0500
Mime-Version: 1.0 (Apple Message framework v546)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: RJ Atkinson <rja@extremenetworks.com>
To: ieprep <ieprep@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <F0D5ED5C-F048-11D6-812C-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] status of current "framework" draft
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

	I think that the "framework" draft is hopeless to edit into
an IETF-style requirements draft.  I think that it IS useful,
if edited into being an (obviously) purely informational document
on what might be done and how diverse pieces might fit together.

	In my view, this would be published as an Informational status
document, not standards-track, and would have the word "requirement"
edited out throughout the document.

	My preference would be that we focus on draft-carlberg-ets-*.txt as
the candidate standards-track IETF-requirements documents to be
produced by this WG.

	(The above intentionally makes no comment on Henning's draft, which is
focused on SIP-specific requirements rather than general Telephony 
service
requirements.)

Thanks,

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 19:20:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15919
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 19:20:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA50MLO17576
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 19:22:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50MLv17573
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 19:22:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15911
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 19:19:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50L7v17530;
	Mon, 4 Nov 2002 19:21:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50Kkv17498
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 19:20:46 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15890
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 19:18:11 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA50K1Wg014723;
	Mon, 4 Nov 2002 19:20:01 -0500 (EST)
Date: Mon, 4 Nov 2002 19:20:01 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211050020.gA50K1Wg014723@newdev.harvard.edu>
To: ieprep@ietf.org, rja@extremenetworks.com
Subject: Re: [Ieprep] Moving forward:  draft-carlberg-ets-*.txt
In-Reply-To: <4BD5ECF1-F048-11D6-812C-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> I would ask that they be targeted as the standards-track
> requirements [1] documents for those aspects of the current charter,

as a general rule the IETF does not make requirements documents 
standards track (other than router/host requirements which
were standards track but might be BCP today) - requirements
for future software development (see RFC 1726) are generally
published as Informational RFCs

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 21:08:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18816
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 21:08:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA52AAK24927
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 21:10:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA52AAv24924
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 21:10:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18813
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 21:07:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5294v24871;
	Mon, 4 Nov 2002 21:09:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA528ev24833
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 21:08:40 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18774
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 21:06:05 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 5B7FD67103; Mon,  4 Nov 2002 17:29:00 -0500 (EST)
Date: Mon, 4 Nov 2002 21:08:30 -0500
Subject: Re: [Ieprep] Moving forward:  draft-carlberg-ets-*.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Scott Bradner <sob@harvard.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211050020.gA50K1Wg014723@newdev.harvard.edu>
Message-Id: <7ADA4EDA-F063-11D6-B984-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, Nov 4, 2002, at 19:20 America/Montreal, Scott Bradner wrote:
> as a general rule the IETF does not make requirements documents
> standards track (other than router/host requirements which
> were standards track but might be BCP today) - requirements
> for future software development (see RFC 1726) are generally
> published as Informational RFCs
>
> Scott

OK, then rephrase my request to be that draft-carlberg-ets-*.txt be
considered the WG's "requirements" document output (possibly also
including Henning's draft in that set) in the charter, replacing
the current draft in that role.

<opinion>
The existing documents draft-ietf-ieprep-* seem to be too far away
editorially to be worth editing into IETF-style requirements documents,
but are potentially useful as informational documents describing
the services from an NCS perspective or describing a possible (but
not mandated) deployment framework.
</opinion>

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov  4 23:48:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23142
	for <ieprep-archive@odin.ietf.org>; Mon, 4 Nov 2002 23:48:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA54oxV00474
	for ieprep-archive@odin.ietf.org; Mon, 4 Nov 2002 23:50:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA54oxv00471
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 23:50:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23129
	for <ieprep-web-archive@ietf.org>; Mon, 4 Nov 2002 23:48:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA54o4v00448;
	Mon, 4 Nov 2002 23:50:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA54nCv00401
	for <ieprep@optimus.ietf.org>; Mon, 4 Nov 2002 23:49:12 -0500
Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23098
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 23:46:35 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 4 Nov 2002 22:49:03 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
Date: Mon, 4 Nov 2002 22:49:03 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9AFE1@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
Thread-Index: AcKEhqnNOw/h56yqSiiZcX/q+BekrQ==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Atkinson" <rja@extremenetworks.com>,
        "Rex Buddenberg" <budden@nps.navy.mil>
Cc: "ieprep" <ieprep@ietf.org>
X-OriginalArrivalTime: 05 Nov 2002 04:49:03.0262 (UTC) FILETIME=[AA0343E0:01C28486]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA54nCv00402
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> > It may help if you abstract the security problem 
> > into three categories:
> >  - data security (for which object level security
> >   solutions are appropriate)
> >  - enclaving and resistance to denial of service
> >    attacks
> >  - link security issues such as traffic analysis,
> >   interceptability,jammability
> 
> It is impossible to prevent denial-of-service
> attacks.  Terribly
> sorry, but that is just the reality of the
> situation.  And it
> won't be changing soon.
  DDoS attacks are more harmful. Though, we have 
methods to prevent DoS attacks on TCP/routing 
sessions and Routing table, resistance to DDoS  
against routing and root servers infrastructure
is nil. In the wake of DDoS attacks on the root 
server last month, it is important to pay attention 
to them. 

  Compared to DDoS, flash crowd is a legitimate 
request. On days like 9/11, it is very important to 
distinguish flash crowds and DDoS traffic. 
though, it is hard to distinguish flash crowds/DDoS
traffic as both are of aggregate traffic type.

 So, the requirement doc should clearly mention 
the need for differentiating DDoS and flash crowd 
problem.


 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 02:01:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27839
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 02:01:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA573Vk08287
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 02:03:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA573Uv08284
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 02:03:30 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27131
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 02:00:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5728v08053;
	Tue, 5 Nov 2002 02:02:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA56xkv07816
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 01:59:46 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25971
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 01:57:09 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA56rhd12804
	for <ieprep@ietf.org>; Mon, 4 Nov 2002 22:53:43 -0800 (PST)
Date: Mon, 4 Nov 2002 22:53:43 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: ieprep@ietf.org
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <A8C63480-F042-11D6-812C-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211042247540.12110-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Mon, 4 Nov 2002, RJ Atkinson wrote:
    > Most larger ISPs shun exchange points and strongly prefer private
    > peering -- in order to engineer congestion out of their networks
    > (and out of their access links with peers)  So the above is a bit
    > of a misapprehension of the deployed situation.

Mmm, I wouldn't put it that way...  All traffic that exceeds what's
reasonable to put through a switch port does take private interconnects,
but those are nearly all in exchange facilities, now.  I don't see much
private peering occurring outside exchange facilities at this point.

Back to the point that Ms. King was making, I think, if you look at what
Time Warner Telecom is doing with their INOC-DBA phones, they're building
out separate dedicated infrastructure to handle the emergency calls, and
handing off across separate crossconnects at exchanges, so that if they
were to actually suffer some sort of catastrophic collapse of their entire
backbone, they'd still be able to chat with people about it on the phone.

That's going much further than anyone else, so far, but it does show that
it's perfectly possible to do, without any of the "requirements" and at a
far lower cost and higher reliability than would be offered by following
these "requirements."

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 08:24:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17351
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 08:24:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5DQZx10081
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 08:26:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5DQZv10078
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 08:26:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17339
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 08:24:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5DKEv09800;
	Tue, 5 Nov 2002 08:20:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5DJBv09690
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 08:19:11 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17078
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 08:16:42 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id B25E667103; Tue,  5 Nov 2002 04:39:42 -0500 (EST)
Date: Tue, 5 Nov 2002 08:19:08 -0500
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: "ieprep" <ieprep@ietf.org>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9AFE1@KC-MAIL2.kc.umkc.edu>
Message-Id: <2AAE68CC-F0C1-11D6-9D8D-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, Nov 4, 2002, at 23:49 America/Montreal, Ayyasamy, 
Senthilkumar (UMKC-Student) wrote:
>   DDoS attacks are more harmful.

Agree.

> Though, we have
> methods to prevent DoS attacks on TCP/routing
> sessions and Routing table,

Please cite reference or explain.  I don't think we
can prevent all DoS attacks on TCP/routing sessions
and the routing tables.

> resistance to DDoS
> against routing and root servers infrastructure
> is nil. In the wake of DDoS attacks on the root
> server last month, it is important to pay attention
> to them.

Agree to both.

>   Compared to DDoS, flash crowd is a legitimate
> request. On days like 9/11, it is very important to
> distinguish flash crowds and DDoS traffic.
> though, it is hard to distinguish flash crowds/DDoS
> traffic as both are of aggregate traffic type.

If someone has a method to distinguish an unexpected
crowd from DDOS that is proven to work, I'd be surprised
but would be happy to hear about it.

There is one misapprehension above.  Traffic graphs from
9/11/01 indicate that there was NOT a significant surge
in IP traffic.  There was a modest surge, but much less
than is regularly seen for non-calamity events (e.g.
much less than for the Mars lander).

>  So, the requirement doc should clearly mention
> the need for differentiating DDoS and flash crowd
> problem.

I don't want to have any requirements that can't be met
(with currently visible technology).  I think this is
just that.  If you think that it can be met, please explain how.

Thanks,

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 08:25:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17394
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 08:25:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5DRCn10103
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 08:27:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5DRCv10100
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 08:27:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17367
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 08:24:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5DQ4v10057;
	Tue, 5 Nov 2002 08:26:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5DPlv10012
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 08:25:47 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17319
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 08:23:17 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 34C1967103; Tue,  5 Nov 2002 04:46:14 -0500 (EST)
Date: Tue, 5 Nov 2002 08:25:39 -0500
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211042247540.12110-100000@paixhost.pch.net>
Message-Id: <137319DE-F0C2-11D6-9D8D-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 5, 2002, at 01:53 America/Montreal, Bill Woodcock wrote:
> Mmm, I wouldn't put it that way...  All traffic that exceeds what's
> reasonable to put through a switch port does take private 
> interconnects,
> but those are nearly all in exchange facilities, now.  I don't see much
> private peering occurring outside exchange facilities at this point.

I was told at the time that UUnet and several other big ISPs pretty much
required that we *not* exchange traffic at an exchange point once we 
were
facilities-based.   The typical thing was to run a metro link (usually 
SONET)
between one core router from each ISP within some metropolitan area.  
In a small
number of cases, there was a SONET point-to-point link inside a shared 
facility.
The exchange  points (e.g. MAE-East) were used for exchanging traffic 
with smaller
ISPs, though point to point links (i.e. not through a switch fabric)
was not uncommon even in that case.

It sounds like either your sample space is different or things have
changed.  Interesting either way.

I'd still like to see you all give a short presentation about the 
actual nature
of deployed ISP networks today in Atlanta, though I haven't seen Scott 
comment
on that idea yet (its only been a few hours since I made the 
suggestion, so
this is not a gripe about Scott :-).

Cheers,

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 09:48:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20987
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 09:48:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5Eo8f16543
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 09:50:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Eo7v16538
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 09:50:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20984
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 09:47:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5En3v16460;
	Tue, 5 Nov 2002 09:49:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5EmBv16425
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 09:48:11 -0500
Received: from cpmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20917
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 09:45:40 -0500 (EST)
Received: from cp-its-ieg01.mail.saic.com by cpmx.mail.saic.com for ieprep@ietf.org; Tue, 5 Nov 2002 06:47:52 -0800
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by cp-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002110506475019530
 ; Tue, 05 Nov 2002 06:47:50 -0800
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WBZ4NBPZ>; Tue, 5 Nov 2002 09:47:42 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E778E5@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "Ieprep (E-mail)" <ieprep@ietf.org>
Cc: "Allison Mankin (E-mail)" <mankin@psg.com>,
        "'Scott Bradner ' (E-mail)" <sob@harvard.edu>
Date: Tue, 5 Nov 2002 09:47:48 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Ieprep] WG Last Call draft-ietf-ieprep-sip-reqs-01.txt
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

This message is to announce WG last call for Requirements for Resource
Priority Mechanisms for the Session Initiation Protocol
(draft-ietf-ieprep-sip-reqs-01.txt).  The intension is for this draft to
have information RFC status.

This version of draft-ietf-ieprep-sip-reqs-01.txt has been modified based on
the mailing list discussion.  Due to the upcoming IETF, the normal 2-week
last call period is being extended to November 26, 2002.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 14:11:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06206
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 14:11:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5JDSr02496
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 14:13:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5JDSv02493
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 14:13:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06189
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 14:10:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5JCTv02440;
	Tue, 5 Nov 2002 14:12:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5JAwv02385
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 14:10:58 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06048
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 14:08:25 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA5J1Xd24158;
	Tue, 5 Nov 2002 11:01:33 -0800 (PST)
Date: Tue, 5 Nov 2002 11:01:33 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: ieprep@ietf.org
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <137319DE-F0C2-11D6-9D8D-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211051100020.23949-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 5 Nov 2002, RJ Atkinson wrote:
    > I was told at the time that UUnet and several other big ISPs pretty much
    > required that we *not* exchange traffic at an exchange point once we
    > were facilities-based.

Yeah, that was definitely the case during the period you were at @Home...
A lot of the old-school telco carriers had been getting bad PR surrounding
latency and loss where they connected to exchanges, and that was their
reaction.  They've actually examined the dollar cost of that reaction
since then, and corrected it.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 14:11:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06227
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 14:11:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5JDms02512
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 14:13:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5JDmv02509
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 14:13:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06198
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 14:11:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5JD0v02482;
	Tue, 5 Nov 2002 14:13:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5JCWv02443
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 14:12:32 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06131
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 14:09:59 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA5J32d24200;
	Tue, 5 Nov 2002 11:03:02 -0800 (PST)
Date: Tue, 5 Nov 2002 11:03:02 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>,
        ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
In-Reply-To: <2AAE68CC-F0C1-11D6-9D8D-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211051102021.23949-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 5 Nov 2002, RJ Atkinson wrote:
    > There is one misapprehension above.  Traffic graphs from
    > 9/11/01 indicate that there was NOT a significant surge
    > in IP traffic.  There was a modest surge, but much less
    > than is regularly seen for non-calamity events (e.g.
    > much less than for the Mars lander).

Correct.  There was a significant increase in traffic to the CNN web site,
and a few other news sites, but it was insignificant relative to the
Internet generally.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 14:13:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06462
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 14:13:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5JFij02641
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 14:15:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5JFiv02638
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 14:15:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06313
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 14:13:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5JF1v02578;
	Tue, 5 Nov 2002 14:15:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5JE4v02530
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 14:14:04 -0500
Received: from cmsoutbound.mx.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA06220
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 14:11:31 -0500 (EST)
Message-Id: <200211051911.OAA06220@ietf.org>
Received: from uadvg132.cms.usa.net (HELO localhost) (165.212.11.132)
  by cmsoutbound.mx.net with SMTP; 5 Nov 2002 19:13:54 -0000
Received: from gw.smtp.postoffice.net [165.212.8.17] by uadvg132.cms.usa.net via mtad (CM.0402.2.02C) 
	with ESMTP id 827gkeTNz0932M32; Tue, 05 Nov 2002 19:13:52 GMT
Received: from 207.124.15.65 [207.124.15.65] by uwdvg017.cms.usa.net 
	(USANET web-mailer CM.0402.4.07); Tue, 05 Nov 2002 19:13:49 -0000
Date: Tue, 05 Nov 2002 14:13:49 -0500
From: Daniel Sullivan
 <daniel.t.sullivan@usa.net>
To: RJ Atkinson
 <rja@extremenetworks.com>,
        "Ayyasamy, Senthilkumar  (UMKC-Student)"
 <saq66@umkc.edu>
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
CC: "ieprep"
 <ieprep@ietf.org>
X-Mailer: USANET web-mailer (CM.0402.4.07)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA5JE4v02531
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

I think this group is working on stuff for the future. If we didn't need to
make changes, we could shut down the IETF.  How boring that would be! :-))

Steve Silverman   who can't read his email because his computer died.





RJ Atkinson <rja@extremenetworks.com> wrote:

I don't want to have any requirements that can't be met
(with currently visible technology).  I think this is
just that.  If you think that it can be met, please explain how.

Thanks,

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 15:30:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11966
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 15:30:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5KWCH06932
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 15:32:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5KWCv06929
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 15:32:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11846
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 15:29:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5KV4v06875;
	Tue, 5 Nov 2002 15:31:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5KURv06834
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 15:30:27 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11690
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 15:27:50 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 828BB67103; Tue,  5 Nov 2002 11:50:50 -0500 (EST)
Date: Tue, 5 Nov 2002 15:30:09 -0500
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: "ieprep" <ieprep@ietf.org>
To: Daniel Sullivan <daniel.t.sullivan@usa.net>
From: RJ Atkinson <rja@extremenetworks.com>
Content-Transfer-Encoding: 7bit
Message-Id: <609C2844-F0FD-11D6-8244-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 5, 2002, at 14:13 America/Montreal, Daniel Sullivan 
wrote:
> I think this group is working on stuff for the future. If we didn't 
> need to
> make changes, we could shut down the IETF.  How boring that would be! 
> :-))

I remain a little befuddled about the charter language, despite a couple
of attempts by Scott to clarify.  No doubt Scott will clarify the below
if I err greatly.

However, *this particular group* is supposed to focus on how one could 
deploy
IEprep services *using existing mechanisms*.  The group is specifically 
NOT
supposed to work on protocol design or changes to IETF protocol specs.
So the focus of this group is how can we do IEprep stuff *today* (not
in some indefinite future) using *existing* mechanisms.

So work on changing things is legitimate for the IETF, but not 
particularly
the focus of this particular working group.  As an example, this group
is offering input to SIP WG.  SIP WG can then choose whether or not to
make any changes and also which changes it wants to make.

So I'd say that if there are particular changes one wants to make to 
IETF
protocols, then one should take those up in the *normal* IETF manner:
	- show up at the applicable other WG
	- explain what one wants and why one wants it
	- write an Internet-Draft outlining one's proposal
	- try to persuade that WG community to make those changes
	- work with the normal process of the IETF

No doubt Scott will correct any confusion in the above.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 16:31:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16188
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 16:31:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5LXqR10742
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 16:33:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5LXpv10739
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 16:33:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16145
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 16:31:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5LX3v10703;
	Tue, 5 Nov 2002 16:33:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5LWXv10623
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 16:32:33 -0500
Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16069
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 16:29:59 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 5 Nov 2002 15:32:26 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
Date: Tue, 5 Nov 2002 15:32:26 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9AFE2@KC-MAIL2.kc.umkc.edu>
Thread-Topic: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
Thread-Index: AcKEze249GvQG4RMTO6hkKVZpwSBUAANBe6w
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "RJ Atkinson" <rja@extremenetworks.com>
Cc: "ieprep" <ieprep@ietf.org>
X-OriginalArrivalTime: 05 Nov 2002 21:32:26.0897 (UTC) FILETIME=[D62CF010:01C28512]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA5LWXv10624
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> > Though, we have
> > methods to prevent DoS attacks on TCP/routing
> > sessions and Routing table,
> 
> Please cite reference or explain.  I don't think we
> can prevent all DoS attacks on TCP/routing sessions
> and the routing tables.
  I should have been more clear. 
 One can trace the source of the DoS attack by means
of many identification methods like ICMP 
traceback, Hash-base IP traceback, tight samplers 
across passive measurement collectors, IDS systems 
like Bro. Then, we can use packet filtering (sometimes 
distributed)/rate-limiting to nullify them. Other
than major vendors, many companies like arbor 
networks, packetdesign and asta networks has 
targeted products relating to DoS identification.
  The security loop holes in some operating systems 
is another major source. So, we can take precautionary 
measures by adding the respective patches (though, 
prevention is still difficult.) The important point 
here is, OS developers should follow robust coding
schemes to avoid security vulnerability. Sand boxing
(giving restricted access to resources) and use of 
safe languages (which allows taint mode) for coding 
is also another prevention method.
  what i could not understand is:  Though,Govt 
organizations, ICANN ,many open bodies, and Nanog 
(which has a mimimum of one discussion relating 
to DoS every month) discuss and work on 
DoS/DDoS, we still could not find a solution 
to this problem.
 
 
 There are many solutions from research labs too.
But, I am not aware of the deployment details. 

1. ratul, sally floyd & steve bellovin's work on
RED-PD, ACC and pushback schemes. The pushback 
scheme has a linux implementation too.

2. John Heidemann's mitigation scheme by means of
connection admission control.

3. Kihong Park and Heejo Lee DPF scheme.

4. Passive packet based sampling measurement 
 schemes ( UCSD Varghese et all and ATT duffield 
et all)

 I can  get into the above methods, but will
not be germane to the present discussion. Of the 
above, 1,3 and 4 are easier to deploy. RED or RED-PD
just need some little code modification at per-router
level. Operators generally employ flow/pkt passive
measurement tools like Netflow/sflo and so, it will
be easy to deploy 4 with some tight sampling methods. 


> >   Compared to DDoS, flash crowd is a legitimate
> > request. On days like 9/11, it is very important to
> > distinguish flash crowds and DDoS traffic.
> > though, it is hard to distinguish flash crowds/DDoS
> > traffic as both are of aggregate traffic type.
> 
> If someone has a method to distinguish an unexpected
> crowd from DDOS that is proven to work, I'd be surprised
> but would be happy to hear about it.
Paul barford and Dave planks has worked on this aspect
and have some results. They have used measurement based
approach by using flowscan.

http://www.icir.org/vern/imw-2001/imw2001-papers/47.pdf
( Look at fig 4 and 5)
http://www.icir.org/vern/imw-2002/imw2002-papers/173.pdf
( a follow-up work but using wavelets)

We can go into these too, but will be more relevant if 
this is a IMRG/nanog discussion.


>       On Tue, 5 Nov 2002, RJ Atkinson wrote:
>     > There is one misapprehension above.  Traffic graphs from
>     > 9/11/01 indicate that there was NOT a significant surge
>     > in IP traffic.  There was a modest surge, but much less
>     > than is regularly seen for non-calamity events (e.g.
>     > much less than for the Mars lander).

I accept. Fred Baker has actually pointed me to cowie's presentaion
which showed the robustness of BGP system on 9/11.
http://www.netsys.com/library/papers/renesys-030502-NRC-911.pdf

> 
> Correct.  There was a significant increase in traffic to the 
> CNN web site,
> and a few other news sites, but it was insignificant relative to the
> Internet generally.

yes again. http://www.tcsa.org/lisa2001/cnn.txt
Even with all their akamisation, anycast and CDN, CNN couldnot
withstand on 9/11.


> >  So, the requirement doc should clearly mention
> > the need for differentiating DDoS and flash crowd
> > problem.
> 
> I don't want to have any requirements that can't be met
> (with currently visible technology).  I think this is
> just that.  If you think that it can be met, please explain how.

All in the research stage - RED-PD, application level Network 
clustering based methods. 

But, if you ask about their deployment..sorry, I don't know. I have
not heard of even Diffserv/ RED deployment except for some RED 
deployment details from sean doran.


Atleast, the requirement doc should mention that "emergency traffic
should be distinguised from DDoS/flashcrowd traffic at the access"
One can do this by giving lower priority to flash crowd pkts 
thereby leaving way for emergency traffic. This can be done by 
configuring VPN or using RED/ECN 
or
https://www1.ietf.org/mail-archive/working-groups/ieprep/current/msg00015.html
https://www1.ietf.org/mail-archive/working-groups/ieprep/current/msg00016.html




 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 16:48:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17340
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 16:48:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5Lp2G12194
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 16:51:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Lp1v12191
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 16:51:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17319
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 16:48:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Lo4v12133;
	Tue, 5 Nov 2002 16:50:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Ln7v12058
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 16:49:07 -0500
Received: from imo-d02.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17230
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 16:46:33 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d02.mx.aol.com (mail_out_v34.13.) id j.ac.3076c0ad (3940);
	Tue, 5 Nov 2002 16:48:51 -0500 (EST)
Message-ID: <ac.3076c0ad.2af996c3@aol.com>
Date: Tue, 5 Nov 2002 16:48:51 EST
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
To: rja@extremenetworks.com, daniel.t.sullivan@usa.net
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_ac.3076c0ad.2af996c3_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_ac.3076c0ad.2af996c3_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/5/2002 3:31:57 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> I remain a little befuddled about the charter language, despite a couple
> of attempts by Scott to clarify.  No doubt Scott will clarify the below
> if I err greatly.
> 
> However, *this particular group* is supposed to focus on how one could 
> deploy
> IEprep services *using existing mechanisms*.  The group is specifically NOT
> supposed to work on protocol design or changes to IETF protocol specs.
> So the focus of this group is how can we do IEprep stuff *today* (not
> in some indefinite future) using *existing* mechanisms.
> 



[MAP] I don't know why this continues to cause confusion. In his Oct 24 
e-mail, Scott wrote:

"I do not see anything in the charter that restricts this WG to 
only producing requirements that describe existing IP protocol functions"

I thought that was pretty clear.

> So work on changing things is legitimate for the IETF, but not particularly
> the focus of this particular working group.  As an example, this group
> is offering input to SIP WG.  SIP WG can then choose whether or not to
> make any changes and also which changes it wants to make.
> 
> So I'd say that if there are particular changes one wants to make to IETF
> protocols, then one should take those up in the *normal* IETF manner:
>     - show up at the applicable other WG
>     - explain what one wants and why one wants it
>     - write an Internet-Draft outlining one's proposal
>     - try to persuade that WG community to make those changes
>     - work with the normal process of the IETF
> 



[MAP] What you''ve described above is exactly correct. The applicable WG to 
show up at with an explanation of what one wants and why is IEPREP. We all 
agree that it is not the place to propose specific changes to specific 
protocols, but if possibilites can't be mentioned, then we'll never get 
there. Nor can one go directly to SIP or DiffServ, or whatever WG and claim 
to need something. We already agreed that doesn't work.

> No doubt Scott will correct any confusion in the above.
> 

Mike Pierce
Artel



--part1_ac.3076c0ad.2af996c3_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/5/2002 3:31:57 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">I remain a little befuddled about the charter language, despite a couple
<BR>of attempts by Scott to clarify. &nbsp;No doubt Scott will clarify the below
<BR>if I err greatly.
<BR>
<BR>However, *this particular group* is supposed to focus on how one could deploy
<BR>IEprep services *using existing mechanisms*. &nbsp;The group is specifically NOT
<BR>supposed to work on protocol design or changes to IETF protocol specs.
<BR>So the focus of this group is how can we do IEprep stuff *today* (not
<BR>in some indefinite future) using *existing* mechanisms.
<BR></BLOCKQUOTE>
<BR>
<BR>
<BR>
<BR>[MAP] I don't know why this continues to cause confusion. In his Oct 24 e-mail, Scott wrote:
<BR>
<BR>"I do not see anything in the charter that restricts this WG to 
<BR>only producing requirements that describe existing IP protocol functions"
<BR>
<BR>I thought that was pretty clear.
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">So work on changing things is legitimate for the IETF, but not particularly
<BR>the focus of this particular working group. &nbsp;As an example, this group
<BR>is offering input to SIP WG. &nbsp;SIP WG can then choose whether or not to
<BR>make any changes and also which changes it wants to make.
<BR>
<BR>So I'd say that if there are particular changes one wants to make to IETF
<BR>protocols, then one should take those up in the *normal* IETF manner:
<BR> &nbsp;&nbsp;&nbsp;- show up at the applicable other WG
<BR> &nbsp;&nbsp;&nbsp;- explain what one wants and why one wants it
<BR> &nbsp;&nbsp;&nbsp;- write an Internet-Draft outlining one's proposal
<BR> &nbsp;&nbsp;&nbsp;- try to persuade that WG community to make those changes
<BR> &nbsp;&nbsp;&nbsp;- work with the normal process of the IETF
<BR></BLOCKQUOTE>
<BR>
<BR>
<BR>
<BR>[MAP] What you''ve described above is exactly correct. The applicable WG to show up at with an explanation of what one wants and why is IEPREP. We all agree that it is not the place to propose specific changes to specific protocols, but if possibilites can't be mentioned, then we'll never get there. Nor can one go directly to SIP or DiffServ, or whatever WG and claim to need something. We already agreed that doesn't work.
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">No doubt Scott will correct any confusion in the above.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>Mike Pierce
<BR>Artel
<BR>
<BR></FONT></HTML>

--part1_ac.3076c0ad.2af996c3_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 17:13:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19592
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 17:13:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5MFvS14224
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 17:15:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MFvv14221
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 17:15:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19550
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 17:13:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MF4v14175;
	Tue, 5 Nov 2002 17:15:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MEsv14143
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 17:14:54 -0500
Received: from imo-m05.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19453
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 17:12:19 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m05.mx.aol.com (mail_out_v34.13.) id j.8c.20aa6c7e (25914);
	Tue, 5 Nov 2002 17:14:40 -0500 (EST)
Message-ID: <8c.20aa6c7e.2af99cd0@aol.com>
Date: Tue, 5 Nov 2002 17:14:40 EST
Subject: Re: [Ieprep] Moving forward:  draft-carlberg-ets-*.txt
To: rja@extremenetworks.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_8c.20aa6c7e.2af99cd0_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_8c.20aa6c7e.2af99cd0_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/4/2002 5:55:46 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> 3) I'd like to ask that folks here please take time now, before Atlanta,
> to read and critique the documents from Ken Carlberg (I kibbutzed, but 
> the work
> and words are mostly Ken's).  They are short documents (and I hope also
> sweet :-).
> 
> Application-specific Requirements for IP Telephony:
>     draft-carlberg-ets-telephony-00.txt
> 

[MAP] Following comments were sent in Sept, but I don't know if/how they were 
dealt with. I haven't seen an update.

1.1 Reference should be T1.631 (not 693).

3. Since the title and purpose of this document is to address the 
requirements for "IP-telephony", it should address the requirements for 
end-to-end provision of a telephony service. Therefore, the statement that 
"the following requirements explicitly do not relate to IP-layer mechanisms" 
should be removed. In fact, it should not state requirements for the non-IP 
protocols (SS7, DSS1), since the IETF has no control of those protocols. It 
should refer to what non-IP protocols do, and state the requirements for what 
the IP-protocols must do and how they must interwork.

1) IP signaling (SIP) MUST be able to carry labels.

Mike Pierce
Artel



--part1_8c.20aa6c7e.2af99cd0_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/4/2002 5:55:46 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">3) I'd like to ask that folks here please take time now, before Atlanta,
<BR>to read and critique the documents from Ken Carlberg (I kibbutzed, but 
<BR>the work
<BR>and words are mostly Ken's). &nbsp;They are short documents (and I hope also
<BR>sweet :-).
<BR>
<BR>Application-specific Requirements for IP Telephony:
<BR> &nbsp;&nbsp;&nbsp;draft-carlberg-ets-telephony-00.txt
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>[MAP] Following comments were sent in Sept, but I don't know if/how they were dealt with. I haven't seen an update.
<BR>
<BR>1.1 Reference should be T1.631 (not 693).
<BR>
<BR>3. Since the title and purpose of this document is to address the requirements for "IP-telephony", it should address the requirements for end-to-end provision of a telephony service. Therefore, the statement that "the following requirements explicitly do not relate to IP-layer mechanisms" should be removed. In fact, it should not state requirements for the non-IP protocols (SS7, DSS1), since the IETF has no control of those protocols. It should refer to what non-IP protocols do, and state the requirements for what the IP-protocols must do and how they must interwork.
<BR>
<BR>1) IP signaling (SIP) MUST be able to carry labels.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR></FONT></HTML>

--part1_8c.20aa6c7e.2af99cd0_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 17:13:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19605
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 17:13:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5MFxd14242
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 17:15:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MFxv14236
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 17:15:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19556
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 17:13:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MF5v14192;
	Tue, 5 Nov 2002 17:15:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MEtv14147
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 17:14:55 -0500
Received: from imo-m03.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19461
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 17:12:21 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m03.mx.aol.com (mail_out_v34.13.) id j.67.17b3df3 (25914);
	Tue, 5 Nov 2002 17:14:38 -0500 (EST)
Message-ID: <67.17b3df3.2af99cce@aol.com>
Date: Tue, 5 Nov 2002 17:14:38 EST
Subject: Re: [Ieprep] Moving forward:  draft-carlberg-ets-*.txt
To: rja@extremenetworks.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_67.17b3df3.2af99cce_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_67.17b3df3.2af99cce_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/4/2002 5:55:46 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> 3) I'd like to ask that folks here please take time now, before Atlanta,
> to read and critique the documents from Ken Carlberg (I kibbutzed, but the 
> work
> and words are mostly Ken's).  They are short documents (and I hope also 
> sweet :-).
> 

[MAP] There has been discussion the past 6 weeks on several issues, some 
prompted by my initial set of comments on Sept 18. I was waiting for an 
update to be posted by the author to see how he had dealt with the results of 
those discusions. There was a significant discussion on "Policy vs labels" 
begun by a comment on these drafts, but I don't know if there is a 
satisfactory resulution in the text.

It may be that these should move forward as WG drafts, but it's hard to say 
when we haven't seen the -01 version after all the discussion.

Mike Pierce
Artel



--part1_67.17b3df3.2af99cce_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/4/2002 5:55:46 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">3) I'd like to ask that folks here please take time now, before Atlanta,
<BR>to read and critique the documents from Ken Carlberg (I kibbutzed, but the work
<BR>and words are mostly Ken's). &nbsp;They are short documents (and I hope also sweet :-).
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>[MAP] There has been discussion the past 6 weeks on several issues, some prompted by my initial set of comments on Sept 18. I was waiting for an update to be posted by the author to see how he had dealt with the results of those discusions. There was a significant discussion on "Policy vs labels" begun by a comment on these drafts, but I don't know if there is a satisfactory resulution in the text.
<BR>
<BR>It may be that these should move forward as WG drafts, but it's hard to say when we haven't seen the -01 version after all the discussion.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR></FONT></HTML>

--part1_67.17b3df3.2af99cce_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 17:20:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20247
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 17:20:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5MMo514669
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 17:22:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MMov14666
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 17:22:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20231
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 17:20:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MM4v14645;
	Tue, 5 Nov 2002 17:22:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MKCv14501
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 17:20:12 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19981
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 17:17:37 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 608F267103; Tue,  5 Nov 2002 13:40:43 -0500 (EST)
Date: Tue, 5 Nov 2002 17:20:04 -0500
Subject: Re: [Ieprep] DDOS prevention
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: "ieprep" <ieprep@ietf.org>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9AFE2@KC-MAIL2.kc.umkc.edu>
Message-Id: <BBE4D5AF-F10C-11D6-8244-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 5, 2002, at 16:32 America/Montreal, Ayyasamy, 
Senthilkumar (UMKC-Student) wrote:
>  One can trace the source of the DoS attack by means
> of many identification methods like ...

Unfortunately, a good DDOS attack packet looks identical to
legitimate traffic.  We've seen that sort of DDOS attack within
the past fortnight.  So I don't think we can *prevent*
DDOS attacks.  You did describe a number of ways to track
down DDOS attackers that aren't clever -- and those methods
are useful.  They just aren't totally effective at preventing
DDOS.

>    what i could not understand is:  Though,Govt
> organizations, ICANN ,many open bodies, and Nanog
> (which has a mimimum of one discussion relating
> to DoS every month) discuss and work on
> DoS/DDoS, we still could not find a solution
> to this problem.

I don't think it is solvable, at least not in the
sense where we all do <x> and after that, no
DDOS attack can happen.

A point Mike O'Dell mentioned earlier today is that deployment
of DiffServ actually *creates* a new potential DDOS vulnerability
for the ISP that deploys DiffServ.  He's right about that, too.

Sigh.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 17:24:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20516
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 17:24:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5MQqm14812
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 17:26:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MQqv14809
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 17:26:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20485
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 17:24:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MQ3v14783;
	Tue, 5 Nov 2002 17:26:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MPfv14747
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 17:25:41 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20427
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 17:23:06 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 5066267103; Tue,  5 Nov 2002 13:46:12 -0500 (EST)
Date: Tue, 5 Nov 2002 17:25:33 -0500
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <ac.3076c0ad.2af996c3@aol.com>
Message-Id: <7FCB95C2-F10D-11D6-8244-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 5, 2002, at 16:48 America/Montreal, Mpierce1@aol.com 
wrote:
> [MAP] What you''ve described above is exactly correct. The applicable 
> WG to show up at with an explanation of what one wants and why is 
> IEPREP. We all agree that it is not the place to propose specific 
> changes to specific protocols,

I was talking about "specific changes to specific protocols" as the 
work that
seems to be out of scope for this WG.  You misread my note -- but that's
OK because you're really 100% consistent in misreading my notes so I 
expect
it these days.

> but if possibilites can't be mentioned, then we'll never get there.


> Nor can one go directly to SIP or DiffServ, or whatever WG and claim
> to need something. We already agreed that doesn't work.

You might think that, but I know of a lot of folks who have been VERY 
VERY successful
in doing just that with those WGs and with others.  It *does* require 
that one present
a sound *technical* case -- which is often missing from NCS and its 
contractors.

And there is most assuredly NOT WG consensus on the last two sentences 
from you above,
so "we" must mean "NCS and its contractors" in your sentence.  It does 
NOT mean
"this WG".

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 17:36:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21384
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 17:36:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5McsU15853
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 17:38:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Mcsv15850
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 17:38:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21352
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 17:36:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5McAv15803;
	Tue, 5 Nov 2002 17:38:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Mbnv15782
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 17:37:50 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21253
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 17:35:14 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA5Mb5BC020957;
	Tue, 5 Nov 2002 17:37:05 -0500 (EST)
Date: Tue, 5 Nov 2002 17:37:05 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211052237.gA5Mb5BC020957@newdev.harvard.edu>
To: daniel.t.sullivan@usa.net, rja@extremenetworks.com
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Cc: ieprep@ietf.org
In-Reply-To: <609C2844-F0FD-11D6-8244-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> No doubt Scott will correct any confusion in the above.

the 1st deliverable of this group is a requirements doc to SIPPING
that doc will, by definition, be talking about things that are not
present in SIP

the 2nd deliverable is a document that says what we can and can 
not do in ISPs and the Internet with existing Internet technology 

a number of IDs have been submitted to the WG that go beyond
what is doable in today's Internet

I think that the 1st pass on these documents have to reflect
what is possible with today's Internet technology -

after we have that we can start looking at requirements that imply 
changes in IETF protocols (aside from SIP which we are already doing) - 
any such requirements will have to be delt with in the way that
the SIP requirements are being delt with - writing a document that
describes specific requirements for a specific IETF protocol (more
than one document if there are more thna one IETF protocol) which
would then be forwarded to the working group responsibe for the
protocol (if any, if there is no such working group, one might
have to be formed)

there is a bigger problem with developing requirements that imply
rearchitecting ISPs or the Internet - that seems unrealistic, and
requirements that define business practices for ISPs - that is
an area that the IETF specifically avoids

Scott

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov  5 18:08:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23558
	for <ieprep-archive@odin.ietf.org>; Tue, 5 Nov 2002 18:08:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5NAK617904
	for ieprep-archive@odin.ietf.org; Tue, 5 Nov 2002 18:10:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5NAKv17901
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 18:10:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23516
	for <ieprep-web-archive@ietf.org>; Tue, 5 Nov 2002 18:07:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5N63v17194;
	Tue, 5 Nov 2002 18:06:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5N5Dv17158
	for <ieprep@optimus.ietf.org>; Tue, 5 Nov 2002 18:05:13 -0500
Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23295
	for <ieprep@ietf.org>; Tue, 5 Nov 2002 18:02:37 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 5 Nov 2002 17:05:06 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Ieprep] DDOS prevention
Date: Tue, 5 Nov 2002 17:04:47 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9AFE4@KC-MAIL2.kc.umkc.edu>
Thread-Topic: [Ieprep] DDOS prevention
Thread-Index: AcKFGawEULp5dJgITGew4kwl6DMUNAAAwiiA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "RJ Atkinson" <rja@extremenetworks.com>
Cc: "ieprep" <ieprep@ietf.org>
X-OriginalArrivalTime: 05 Nov 2002 23:05:06.0039 (UTC) FILETIME=[C7AEB070:01C2851F]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA5N5Dv17159
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> >  One can trace the source of the DDoS attack by means
> > of many identification methods like ...
> 
> Unfortunately, a good DDOS attack packet looks identical to
> legitimate traffic.  We've seen that sort of DDOS attack within
> the past fortnight.  So I don't think we can *prevent*
> DDOS attacks.  You did describe a number of ways to track
> down DDOS attackers that aren't clever -- and those methods
> are useful.  They just aren't totally effective at preventing
> DDOS.

 Yes. First of all, we are lacking in proper deployable methods
for identifying and characterizing DDoS attacks. Some DDoS attacks 
are really surprising and it is really hard to get the 
fingerprint/signature of the DDoS traffic trace. In some cases, it 
is very difficult to distinguish DDoS pkts from normal aggregate 
traffic. It needs some kind of backscatter analysis (caida's work)
to indentify them.
 Although, this might sound philosophical but only way to avoid 
this problem is to have a "epidemic center" which maintains 
various signatures of DoS traces/ patterns of worms like Code RED
etc/ and other things. If anyone has any views on this point, I am 
not responsible as its the idea of vern paxson 
( look for his work on "How to 0wn the Internet in Your Spare Time" 
presented at recent USENIX/Nanog sessions)

> A point Mike O'Dell mentioned earlier today is that deployment
> of DiffServ actually *creates* a new potential DDOS vulnerability
> for the ISP that deploys DiffServ.  He's right about that, too.

 I would be interested in knowing about the vulnerability.
Any pointers/details? 



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 03:45:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09315
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 03:45:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA68lkw26597
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 03:47:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68ljv26594
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 03:47:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09306
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 03:45:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68l4v26558;
	Wed, 6 Nov 2002 03:47:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68iVv26442
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 03:44:31 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09268
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 03:41:52 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA68cPd06311;
	Wed, 6 Nov 2002 00:38:26 -0800 (PST)
Date: Wed, 6 Nov 2002 00:38:25 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
cc: RJ Atkinson <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9AFE2@KC-MAIL2.kc.umkc.edu>
Message-ID: <Pine.GSO.4.44.0211060031260.23949-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 5 Nov 2002, Ayyasamy, Senthilkumar  (UMKC-Student) wrote:
    >  One can trace the source of the DoS attack by means
    > of many identification methods...

None of which are likely to be deployed over a sufficient portion of the
Internet to actually be useful for at least another three or four years.
At the _very_ least.  Much as we'd all like to have those tools useful
sooner.

    > The security loop holes in some operating systems
    > is another major source.

Yes, it is.

    >   what i could not understand is:  Though,Govt
    > organizations, ICANN ,many open bodies, and Nanog
    > (which has a mimimum of one discussion relating
    > to DoS every month) discuss and work on
    > DoS/DDoS, we still could not find a solution
    > to this problem.

Get rid of users.  They cause trouble.

See, it's simple.  :-)

Short of that solution, it's not so easy.  These aren't engineering
problems, they're human-factors problems.  That makes them somewhat less
tractable.

    > I am not aware of the deployment details.

There are none to be aware of, speaking broadly.

    > Operators generally employ flow/pkt passive
    > measurement tools like Netflow...

No, they don't.

    > Atleast, the requirement doc should mention that "emergency traffic
    > should be distinguised from DDoS/flashcrowd traffic at the access"

Thereby giving attackers yet another path into our CPUs.  What attack
wouldn't categorize itself as emergency traffic?

Not sure any of this is particularly germane, in any event.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 03:48:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09421
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 03:48:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA68oeE26812
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 03:50:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68oev26809
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 03:50:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09407
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 03:48:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68o1v26779;
	Wed, 6 Nov 2002 03:50:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68nrv26727
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 03:49:53 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09376
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 03:47:14 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA68e0d06333;
	Wed, 6 Nov 2002 00:40:00 -0800 (PST)
Date: Wed, 6 Nov 2002 00:40:00 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: rja@extremenetworks.com, <daniel.t.sullivan@usa.net>, <ieprep@ietf.org>
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <ac.3076c0ad.2af996c3@aol.com>
Message-ID: <Pine.GSO.4.44.0211060039250.23949-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 5 Nov 2002 Mpierce1@aol.com wrote:
    > Nor can one go directly to SIP or DiffServ, or whatever WG and claim
    > to need something. We already agreed that doesn't work.

Care to speculate on the reasons why?

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 06:12:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11514
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 06:12:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6BElQ03087
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 06:14:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6BEkv03084
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 06:14:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11511
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 06:12:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6BE4v03068;
	Wed, 6 Nov 2002 06:14:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6BDhv03044
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 06:13:43 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11505
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 06:11:13 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA6B7md08235;
	Wed, 6 Nov 2002 03:07:48 -0800 (PST)
Date: Wed, 6 Nov 2002 03:07:48 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Scott  Bradner <sob@harvard.edu>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
In-Reply-To: <200211022114.gA2LE3Si007615@newdev.harvard.edu>
Message-ID: <Pine.GSO.4.44.0211060250490.7728-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 2 Nov 2002, Scott  Bradner wrote:
    >   6 Emergency traffic should be able to transit multiple
    >     service providers.

All traffic should be able to transit multiple service providers, provided
that transit agreements exist between them.  Emergency traffic does not
differ from production traffic in this respect.

    >   6 The existence of service level agreements determines the extent
    >     by which this can be accomplished.

False.

    >   7 Networks should be able to support a variety of user
    >     applications including telephony, video, database access,
    >     messaging, telemetry, and web browsing to support emergency
    >     operations.

Yes, they should, and do.  This doesn't need to be in a requirements draft
any more than saying that ISPs should route IP, or diners should serve
breakfast, does.

    >   8 Authorized emergency communications should be protected
    >     from intrusion or interference, such as, spoofing, change
    >     of content, and denial of service.

All traffic SHOULD be protected.  Again, emergency traffic does not differ
from production traffic in this regard.  Whether traffic is _actually_
protected in any particular way is a different matter, and dependent upon
the business model and product offerings of each ISP.

    >   6 If the protection cannot be accomplished, then users must be
    >     able to detect this failure.

I'm not sure how service providers are supposed to affect the
perceptiveness of users.  Selective-breeding programs have proven
ineffectual thus far.

You used the word MUST there, also...  was that an editorial mistake, or
are we supposed to take that at face value?

    >   9 Users should have the option protecting certain sensitive
    >     traffic from eavesdropping and the source/destination of
    >     some traffic.

If the destination of the traffic is anonymized, how am I supposed to get
this "emergency" message through when the system is broken?  I mean, how
do I deliver it, if nobody can tell me where it's supposed to go?

Oooooh, I get it...  This is a _joke_!  You'll tell me where to send the
packet, _but then you'll have to kill me!_  Ha!  Shoot the messenger with
the bad news!  Good one.

    >  10 Users should have the option of requesting degraded quality
    >     of service when normal or expected QoS cannot be achieved.

I'll let my previous critique of this one stand, since my sense of irony
was about exhausted for the evening on #9.


                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 08:46:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17795
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 08:46:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6DmbF13248
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 08:48:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Dmbv13245
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 08:48:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17783
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 08:46:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6DlRv13198;
	Wed, 6 Nov 2002 08:47:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6DkEv13101
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 08:46:14 -0500
Received: from cpmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17683
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 08:43:43 -0500 (EST)
Received: from cp-its-ieg01.mail.saic.com by cpmx.mail.saic.com for ieprep@ietf.org; Wed, 6 Nov 2002 05:45:57 -0800
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by cp-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002110605455511117
 ; Wed, 06 Nov 2002 05:45:56 -0800
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WBZXQNQM>; Wed, 6 Nov 2002 08:47:19 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E778F4@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "Ieprep (E-mail)" <ieprep@ietf.org>
Cc: "Allison Mankin (E-mail)" <mankin@psg.com>,
        "'Scott Bradner ' (E-mail)" <sob@harvard.edu>
Date: Wed, 6 Nov 2002 08:46:01 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Ieprep] WG last call for IEPREP Topology Scenarios
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

This message is to announce WG last call for IEPREP Topology Scenarios
(draft-polk-ieprep-scenarios-01.txt).  The intention is for this draft to
become an informational RFC.  The draft can be found at
http://www.ietf.org/internet-drafts/draft-polk-ieprep-scenarios-01.txt .

Due to the upcoming IETF, the normal 2-week last call period is being
extended to November 26, 2002.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 11:28:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00330
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 11:28:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6GUMr25608
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 11:30:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6GUMv25605
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 11:30:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00317
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 11:27:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6GTCv25537;
	Wed, 6 Nov 2002 11:29:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6GQbv25270
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 11:26:37 -0500
Received: from imo-d02.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00104
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 11:24:05 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d02.mx.aol.com (mail_out_v34.13.) id j.194.fc82301 (3940);
	Wed, 6 Nov 2002 11:26:30 -0500 (EST)
Message-ID: <194.fc82301.2afa9cb6@aol.com>
Date: Wed, 6 Nov 2002 11:26:30 EST
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
To: rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_194.fc82301.2afa9cb6_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_194.fc82301.2afa9cb6_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/5/2002 5:24:36 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> On Tuesday, Nov 5, 2002, at 16:48 America/Montreal, Mpierce1@aol.com 
> wrote:
> > [MAP] What you''ve described above is exactly correct. The applicable 
> > WG to show up at with an explanation of what one wants and why is 
> > IEPREP. We all agree that it is not the place to propose specific 
> > changes to specific protocols,
> 
> I was talking about "specific changes to specific protocols" as the work 
> that
> seems to be out of scope for this WG.  You misread my note -- but that's
> OK because you're really 100% consistent in misreading my notes so I expect
> it these days.
> 
> > but if possibilites can't be mentioned, then we'll never get there.
> 
> 
> > Nor can one go directly to SIP or DiffServ, or whatever WG and claim
> > to need something. We already agreed that doesn't work.
> 
> You might think that, but I know of a lot of folks who have been VERY VERY 
> successful
> in doing just that with those WGs and with others.  It *does* require that 
> one present
> a sound *technical* case -- which is often missing from NCS and its 
> contractors.
> 
> And there is most assuredly NOT WG consensus on the last two sentences from 
> you above,
> so "we" must mean "NCS and its contractors" in your sentence.  It does NOT 
> mean
> "this WG".
> 


[MAP] I don't understand why you continue to be so abusive in your responses 
to me (and others) on this list. It is totally uncalled for.

Let me clarify one thing first: I am not "NCS and its contractors". To be 
open, which I wish everyone would be, I am a contractor supported by DISA, 
which is responsible for standards and policies for the US Defense 
communications networks. My purpose is to push for support of emergency 
services in IP so that the US Defense communications networks can use IP for 
its voice and other traffic. (NCS has a different mission, but I believe any 
protocol changes can and must support both sets of requirements.)

As I clearly stated, I completely agree with your statement that "specific 
changes to specific protocols" are out of scope for IEPREP. But there seems 
to be a continuing disagreement/confusion on what IEPREP exists for and how 
"we (DISA)" are supposed to bring forward proposed requirements for emergency 
services. My statement was "The applicable WG to show up at with an 
explanation of what one wants and why is IEPREP".

Further, I stated that: "Nor can one go directly to SIP or DiffServ, or 
whatever WG and claim to need something. We already agreed that doesn't 
work." Yes, please read everything I write as if it is preceeded by "IMHO". I 
would like to hear from anyone who doesn't believe that statement. You didn't 
say that you didn't agree with my statement, only that there are "a lot of 
folks" who don't follow it. I know there are, and that's one of the things I 
thought "we (WG)" are trying to fix.

I thought the point of draft-ietf-sip-guidelines-05 was that requirements had 
to be agreed in SIPPING before specific protocol changes were proposed to 
SIP. And for the emergency work, I thought "we (WG)" had agreed that IEPREP 
had to agree on requirements before anything was brought to SIPPING (or other 
WGs).

If I have misunderstood the process that "we (WG and DISA)" are attempting to 
follow, I hope Scott or Allison or Kimberly will set me (and others) straight.

Mike Pierce
Artel


--part1_194.fc82301.2afa9cb6_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/5/2002 5:24:36 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">On Tuesday, Nov 5, 2002, at 16:48 America/Montreal, Mpierce1@aol.com 
<BR>wrote:
<BR>&gt; [MAP] What you''ve described above is exactly correct. The applicable 
<BR>&gt; WG to show up at with an explanation of what one wants and why is 
<BR>&gt; IEPREP. We all agree that it is not the place to propose specific 
<BR>&gt; changes to specific protocols,
<BR>
<BR>I was talking about "specific changes to specific protocols" as the work that
<BR>seems to be out of scope for this WG. &nbsp;You misread my note -- but that's
<BR>OK because you're really 100% consistent in misreading my notes so I expect
<BR>it these days.
<BR>
<BR>&gt; but if possibilites can't be mentioned, then we'll never get there.
<BR>
<BR>
<BR>&gt; Nor can one go directly to SIP or DiffServ, or whatever WG and claim
<BR>&gt; to need something. We already agreed that doesn't work.
<BR>
<BR>You might think that, but I know of a lot of folks who have been VERY VERY successful
<BR>in doing just that with those WGs and with others. &nbsp;It *does* require that one present
<BR>a sound *technical* case -- which is often missing from NCS and its contractors.
<BR>
<BR>And there is most assuredly NOT WG consensus on the last two sentences from you above,
<BR>so "we" must mean "NCS and its contractors" in your sentence. &nbsp;It does NOT mean
<BR>"this WG".
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] I don't understand why you continue to be so abusive in your responses to me (and others) on this list. It is totally uncalled for.
<BR>
<BR>Let me clarify one thing first: I am not "NCS and its contractors". To be open, which I wish everyone would be, I am a contractor supported by DISA, which is responsible for standards and policies for the US Defense communications networks. My purpose is to push for support of emergency services in IP so that the US Defense communications networks can use IP for its voice and other traffic. (NCS has a different mission, but I believe any protocol changes can and must support both sets of requirements.)
<BR>
<BR>As I clearly stated, I completely agree with your statement that "specific changes to specific protocols" are out of scope for IEPREP. But there seems to be a continuing disagreement/confusion on what IEPREP exists for and how "we (DISA)" are supposed to bring forward proposed requirements for emergency services. My statement was "The applicable WG to show up at with an explanation of what one wants and why is IEPREP".
<BR>
<BR>Further, I stated that: "Nor can one go directly to SIP or DiffServ, or whatever WG and claim to need something. We already agreed that doesn't work." Yes, please read everything I write as if it is preceeded by "IMHO". I would like to hear from anyone who doesn't believe that statement. You didn't say that you didn't agree with my statement, only that there are "a lot of folks" who don't follow it. I know there are, and that's one of the things I thought "we (WG)" are trying to fix.
<BR>
<BR>I thought the point of draft-ietf-sip-guidelines-05 was that requirements had to be agreed in SIPPING before specific protocol changes were proposed to SIP. And for the emergency work, I thought "we (WG)" had agreed that IEPREP had to agree on requirements before anything was brought to SIPPING (or other WGs).
<BR>
<BR>If I have misunderstood the process that "we (WG and DISA)" are attempting to follow, I hope Scott or Allison or Kimberly will set me (and others) straight.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_194.fc82301.2afa9cb6_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 12:11:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02331
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 12:11:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6HDr329453
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 12:13:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6HDrv29450
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 12:13:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02321
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 12:11:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6HD4v29409;
	Wed, 6 Nov 2002 12:13:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6HCJv29375
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 12:12:19 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02266
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 12:09:45 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA6H6Id13192;
	Wed, 6 Nov 2002 09:06:18 -0800 (PST)
Date: Wed, 6 Nov 2002 09:06:18 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: rja@extremenetworks.com, <ieprep@ietf.org>
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <194.fc82301.2afa9cb6@aol.com>
Message-ID: <Pine.GSO.4.44.0211060840040.8520-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 6 Nov 2002 Mpierce1@aol.com wrote:
    > I don't understand why you continue to be so abusive in your
    > responses to me (and others) on this list.

Ran hasn't been abusive.  Ran has been a remarkable model of restraint and
decorous moderation.  Ran has simply been asking you questions which
you're ignoring or refusing to answer.

    > My purpose is to push for support of emergency services in IP so
    > that the US Defense communications networks can use IP for
    > its voice and other traffic.

How many times do you need to be told that THIS IS NOT OKAY?  If you don't
have the intellectual honesty and strength of conviction to say something
because YOU believe it, THERE IS NO PLACE FOR YOU IN THE IETF.

You are participating as an INDIVIDUAL, not representing an organization.

We want to know what YOU think.  We already know that organizations are
incapable of thought.

    > There seems to be a continuing disagreement/confusion on
    > what IEPREP exists for...

"The working group will devlop a Requirements for Internet Emergency
Preparedness in the Internet RFC which will detail the specific functions
and technologies needed to provide support for Emergency Preparedness
systems in the Internet" and "a BCP to identify mechanisms to provide
deterministic behavior of applications, mechanisms for authentication and
authorization, and recommendations for application design with existing
protocols."  Specifically:

   "Deliverables

    Best Current Practice: IETF Recommendations for the Emergency
    Telecommunications Service using existing protocols - what can be done
    with existing protcols and what can not be done.

    Informational: Requirements for Internet Emergency Preparedness in the
    Internet. Framework for Supporting Internet Emergency Preparedness in
    IP Telephony."

It also contains the remarkably unfortunate phrase "The international
community needs advice," and fails to provide for a needs analysis before
launching into requirements.  And both of these documents, though actually
in early draft stage presently, were due three months ago.

Some of that seems pretty ill-conceived, but I don't see where the
ambiguity you're finding in it lies.

    > ...and how "we (DISA)" are supposed to bring forward proposed
    > requirements for emergency services.

Sorry, who asked DISA, or any portion of the DoD of the US or any country
to bring anything forward?

    > I stated that: "Nor can one go directly to SIP or DiffServ, or
    > whatever WG and claim to need something. We already agreed that
    > doesn't work."  I would like to hear from anyone who doesn't believe
    > that statement.

Of course that's false.  SIPPING and DIFFSERV exist for the purpose of
development within their areas.  That's what they're there for.  They do
work at each IETF, brought to them by responsible individuals within the
IETF, in exactly the manner that Ran, or I, or any other individual with
relevant business would do so.  SIPPING, at any rate, actually completes
that work and produces standards which are implemented in the actual
production network.  Every day.

The problem isn't SIPPING or DIFFSERV.  The issue is that they're
successfully defending themselves against a violation of the IETF
standards process, and you're whining about it.

    > I thought the point of draft-ietf-sip-guidelines-05 was that
    > requirements had to be agreed in SIPPING before specific protocol
    > changes were proposed to SIP.

And where exactly do you see a "SIP Guidelines" in the deliverables for
this working group?  I see two deliverables, both well overdue, and no
contribution to either of them from you.  In this mailing list, please
discuss the deliverables for this working group, before wandering off to
tell other working groups what they should be doing.

    > And for the emergency work, I thought "we (WG)" had agreed that
    > IEPREP had to agree on requirements before anything was brought to
    > SIPPING (or other WGs).

Amen to that.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 12:29:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03133
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 12:29:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6HW0n30222
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 12:32:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6HW0v30219
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 12:32:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03128
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 12:29:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6HQFv29972;
	Wed, 6 Nov 2002 12:26:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6HPbv29933
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 12:25:37 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02874
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 12:23:04 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Wed, 6 Nov 2002 12:25:18 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002110612252130329
 ; Wed, 06 Nov 2002 12:25:21 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMFW821C>; Wed, 6 Nov 2002 12:26:39 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77902@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, rja@extremenetworks.com
Cc: ieprep@ietf.org
Date: Wed, 6 Nov 2002 12:25:15 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Ieprep] What is ieprep?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

There have been several questions about the scope/context/process/etc. of
this working group.  For clarity, I've aggregated several of Scott's guiding
words (below).

On deliverables:

"the 1st deliverable of this group is a requirements doc to SIPPING
that doc will, by definition, be talking about things that are not
present in SIP

the 2nd deliverable is a document that says what we can and can 
not do in ISPs and the Internet with existing Internet technology 

a number of IDs have been submitted to the WG that go beyond
what is doable in today's Internet

I think that the 1st pass on these documents have to reflect
what is possible with today's Internet technology -

after we have that we can start looking at requirements that imply 
changes in IETF protocols (aside from SIP which we are already doing) - 
any such requirements will have to be delt with in the way that
the SIP requirements are being delt with - writing a document that
describes specific requirements for a specific IETF protocol (more
than one document if there are more thna one IETF protocol) which
would then be forwarded to the working group responsibe for the
protocol (if any, if there is no such working group, one might
have to be formed)

there is a bigger problem with developing requirements that imply
rearchitecting ISPs or the Internet - that seems unrealistic, and
requirements that define business practices for ISPs - that is
an area that the IETF specifically avoids"
____________
On the context of the work:

"Henning sez:
> While your view certainly represents the "traditional" Internet view and 
> current operational practice, one should not forget that there has been 
> a large body of more recent research work related to QoS routing.

this brings up two questions to me

1/ how close is that research to being deployed in ISPs?

and more importantally

2/ should this WG be talking about what the Internet can be expected
   to be able to do now or in the immediate future (see 1st deliverable
   in the WG charter) of speculate on what might be possible at some
   point in the future?

(my feeling, if its not clear, is that we should stick to the world
of today and the near future)"
_______________

On requirements:

"I think that we need to be quite careful
to specify whether we are talking about what requirements can be met on the
Internet (and private IP networks) with existing or near-term technology
and what would require significant new technology development.

I think that we also need to be careful to say what requirements can be met
with the current Internet architectural model (of autonomous
interconnecting with no particular service guarantees) and what would
require a change in this architectural model.  Along this line, we should
also be careful to say which requirements are targeted at use within an
enterprise (such as a telephone company using IP internally), at a single
ISP and which are expected to be able to be met for traffic spanning ISPs
in the open Internet."
_____________
On working with SIP and SIPPING...

"this group can say that there are problems X & Y that need to be
solved for ieprep to work with SIP - it can not tell SIPPING
(which gets the requirement 1st)  that solving the problems means 
that a new header is needed - i.e., defining how to meet the requirement is
not IEPREP's job 

SIPPING  will then take a look at the requirement to see if it:
1/ can be met in some way with SIP as-is that the ieprep did not figure out,
   even if the solution is not as "efficient" as IEPREP might like
2/ can be combined with other resuirements that SIPPING has received
   from other WGs or individuals, and can be reworked to make the
requirement
   more general to solve a wider class of problems, (SIPPING
   might on its own do this w/o the need for specific other requirements
   being submitted)
3/ does not make sense
4/ deals with too narrow a situation to warrent changing SIP ("you can't
   always get what you want, but you generally get what you need")
5/ makes sense as-is

in case 1 SIPPING responds to ieprep - 'here is how to do it'
in case 3 it sends back a "huh?" message
in case 4 it sends back a 'no, and here is why' messgae
in case 2 & 5 SIPPING sends the requirement on to SIP which
then figures out how best to meet the requirement

IEPREP can make a suggestion on how to meet the requirement but SIP
can reject the suggestion if SIP thinks that the ieprep
suggestion is the wrong way to meet the requirement (I do not suggest that
IEPREP should spend time coming up with such suggestions)"

_________
On capacity/context

"this WG does have to think about the case where there is not enough
capacity in the IP network on the path that a data stream will use

the lack of capacity might be restricted to tail circuits, as might
be the general case in US wireline ISPs, or in the infrastructure - the
WG should not worry about the case where the IP path spans multiple ISPs

but the current deliverable is to say what in this space can be
supported using existing IP protocols - it is not to invent new ones"


Thus, we are converging on a more defined understanding of ieprep.  This is
good.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 12:46:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03868
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 12:46:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6Hn1r31584
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 12:49:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Hn1v31581
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 12:49:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03842
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 12:46:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Hm7v31539;
	Wed, 6 Nov 2002 12:48:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6HlSv31499
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 12:47:28 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03726
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 12:44:55 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA6Hbgd13516;
	Wed, 6 Nov 2002 09:37:42 -0800 (PST)
Date: Wed, 6 Nov 2002 09:37:42 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
cc: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, <rja@extremenetworks.com>,
        <ieprep@ietf.org>
Subject: Re: [Ieprep] What is ieprep?
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77902@mcl-its-exs01>
Message-ID: <Pine.GSO.4.44.0211060932100.8520-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 6 Nov 2002, King, Kimberly  S. wrote:
    > There have been several questions about the scope/context/process/etc. of
    > this working group.  For clarity, I've aggregated several of Scott's guiding
    > words (below).
    > On deliverables:
    > "the 1st deliverable of this group is a requirements doc to SIPPING
    > that doc will, by definition, be talking about things that are not
    > present in SIP
    > _____________
    > On working with SIP and SIPPING...
    > "this group can say that there are problems X & Y that need to be
    > solved for ieprep to work with SIP - it can not tell SIPPING
    > (which gets the requirement 1st)  that solving the problems means
    > that a new header is needed.

Okay, these seem very clear.  Particularly, they seem clearer than
"Informational: Requirements for Internet Emergency Preparedness in the
Internet. Framework for Supporting Internet Emergency Preparedness in IP
Telephony."  Perhaps that sentence of the charter should be updated?
Maybe something like "Informational: Desired Features Supporting Emergency
Telephony in a SIP Environment."

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 12:50:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04091
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 12:50:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6HqqY31809
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 12:52:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Hqqv31806
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 12:52:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04069
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 12:50:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Hq0v31758;
	Wed, 6 Nov 2002 12:52:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Hp3v31688
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 12:51:03 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03965
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 12:48:29 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA6Hj6d13612
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 09:45:06 -0800 (PST)
Date: Wed, 6 Nov 2002 09:45:06 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: ieprep@ietf.org
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9AFD3@KC-MAIL2.kc.umkc.edu>
Message-ID: <Pine.GSO.4.44.0211060940090.8520-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


      On Fri, 1 Nov 2002, Ayyasamy, Senthilkumar  (UMKC-Student) wrote:
    > Scalability is not the only issue for lack of interest
    > in Integrated services. Intserv expects reservation to cross
    > administrative boundaries without any hurdle( which is highly
    > impractical!!!)
    > Also, many of the QoS routing schemes are load-insensitive and
    > assumes connection-oriented nature, which is again impractical.
    > QoS routing researchers assume many things which practical network
    > doesn't support ( e.g. unequal splitting.) To be frank, most of the
    > QoS routing schemes will be overkill for the network ( even if the
    > operators are ready to deploy.)
    > Lack of necessary business models. For example, Diffserv is
    > supported only edge to edge ( not e2e) due to lack of proper
    > inter-domain economic models.
    > It high time that we look back and restrategise ourself wrt QoS
    > research. Though, its totally out of scope for ieprep, it is
    > _necessary_ for IETF to look into the issues of
    > complexity/overloading/arch in many of the QoS proposals.
    > Thats said, lets stop the QoS/bandwidth/deployment discussion and worry about
    > other important issues.

I heartily agree with each of Senthilkumar's points in this email, and I
believe they represent the consensus view of operators generally.

			-Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 12:56:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04319
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 12:56:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6Hwwr32062
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 12:58:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Hwwv32059
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 12:58:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04294
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 12:56:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Hw2v32005;
	Wed, 6 Nov 2002 12:58:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6HvJv31969
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 12:57:19 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04229
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 12:54:45 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA6Hp7d13741;
	Wed, 6 Nov 2002 09:51:11 -0800 (PST)
Date: Wed, 6 Nov 2002 09:51:07 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: ieprep@ietf.org
Subject: RE: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework
 -02.txt
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3CD9@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211060948090.8520-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 1 Nov 2002, Nguyen, An wrote:
    > Are you saying if there is any problem with the access node, the network
    > operators will solve the problem by throwing more equipment at it? The
    > question is that how dynamic is that bandwidth increasing in response to
    > congestions?

Not exactly...  If there's a congestion problem within a customer network,
ISPs are not able to resolve that problem.  ISPs cannot autonomously
increase the capacity of a customer tail-circuit, since the customer-owned
CPE must be simultaneously upgraded, nor can ISPs implement QoS on
customer-owned devices, even if it were the case that QoS were beneficial.

Fortunately, none of that is an issue, since the demands which VoIP places
on the network are so small.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 12:59:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04388
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 12:59:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6I13i32257
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 13:01:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6I13v32254
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 13:01:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04369
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 12:58:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6I04v32194;
	Wed, 6 Nov 2002 13:00:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Hxsv32132
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 12:59:54 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04350
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 12:57:20 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 814DA67103; Wed,  6 Nov 2002 09:20:35 -0500 (EST)
Date: Wed, 6 Nov 2002 12:59:48 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <194.fc82301.2afa9cb6@aol.com>
Message-Id: <8A02FB74-F1B1-11D6-9573-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Re: IETF process
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 6, 2002, at 11:26 America/Montreal, Mpierce1@aol.com 
wrote:
> Let me clarify one thing first: I am not "NCS and its contractors". To 
> be open, which I wish everyone would be, I am a contractor supported 
> by DISA, which is responsible for standards and policies for the US 
> Defense communications networks. My purpose is to push for support of 
> emergency services in IP so that the US Defense communications 
> networks can use IP for its voice and other traffic. (NCS has a 
> different mission, but I believe any protocol changes can and must 
> support both sets of requirements.)

Openness is much appreciated.  Given current JCS restrictions on US 
Defence
communications IP networks, not clear to me that things being discussed 
here
(e.g. VoIP, DiffServ) has much applicability to those.  Clarity and 
openness
are always good.

> Further, I stated that: "Nor can one go directly to SIP or DiffServ, 
> or whatever WG and claim to need something. We already agreed that 
> doesn't work." Yes, please read everything I write as if it is 
> preceeded by "IMHO". I would like to hear from anyone who doesn't 
> believe that statement. You didn't say that you didn't agree with my 
> statement, only that there are "a lot of folks" who don't follow it. I 
> know there are, and that's one of the things I thought "we (WG)" are 
> trying to fix.

I disagree with it entirely and I don't believe it.  I know a LOT of 
folks who go
direct to other WGs with their needs, desires, proposals -- because 
that is the
proper normal IETF way of doing things.  And MOST of those folks who do 
that
are successful with that approach, at least to the extent that their 
proposals
are sensible, feasible, and clearly presented.

This WG does NOT exist to prohibit folks from taking their needs, 
desires, and
goals direct to other WGs (provided those items are within the other 
WG's charter).
For example, it is ENTIRELY proper for me to take my 
needs/goals/desires/proposals
for SIP changes directly to the SIP WG.  This WG is NOT trying to 
change that --
in fact if this WG tried to change that it would be violating IETF 
process rules.
Openness of IETF *requires* that anyone can take any 
concern/issue/idea/proposal
to any WG (within that WG's charter, so one does not take proposed 
changes to OSPF
into the SIP WG for example) AND requires that such an approach be 
valid/proper.

> I thought the point of draft-ietf-sip-guidelines-05 was that 
> requirements
> had to be agreed in SIPPING before specific protocol changes were 
> proposed to SIP.
> And for the emergency work, I thought "we (WG)" had agreed that IEPREP 
> had
> to agree on requirements before anything was brought to SIPPING (or 
> other WGs).

I certainly understand that if I had changes to propose to SIP I can 
take them
direct to SIPPING.   SIPPING might or might not act on those proposals, 
just
as it might or might not act on proposals from here.  As it happens, I 
don't have
any changes to propose to SIP, so for me personally that is irrelevant.

And attempts by any AD or WG Chair to stop one from doing that would 
certainly be
appealable (and such an AD action would be very likely to be overturned 
on appeal,
in my own reading of the tea leaves, on grounds that it is contrary to 
IETF openness
as a standards-body).

This group got created because DISA/NCS wanted to BYPASS the normal 
IETF way
of doing things and have its own WG.  I was at all of the BOFs and that 
goal
was quite clear (and remains VERY objectionable in my own views and 
those
of some few others).  I will get publicly upset about that every time 
the topic
comes up, guaranteed, because I think it is flat out wrong.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 13:50:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06571
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 13:50:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6Ir0P03518
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 13:53:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Iqxv03515
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 13:52:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06558
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 13:50:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Iq4v03486;
	Wed, 6 Nov 2002 13:52:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6IpXv03455
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 13:51:33 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06515
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 13:48:59 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 6 Nov 2002 12:51:28 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
Date: Wed, 6 Nov 2002 12:51:27 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9AFE6@KC-MAIL2.kc.umkc.edu>
Thread-Topic: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
Thread-Index: AcKFcLLUrSj7+2D6RICADBLWxGokuQAUeepA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Bill Woodcock" <woody@pch.net>
Cc: "RJ Atkinson" <rja@extremenetworks.com>, "ieprep" <ieprep@ietf.org>
X-OriginalArrivalTime: 06 Nov 2002 18:51:28.0122 (UTC) FILETIME=[838295A0:01C285C5]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA6IpXv03456
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


>     > Operators generally employ flow/pkt passive
>     > measurement tools like Netflow...
> 
> No, they don't.

Operators do need some tools for accounting, capacity 
planning and backbone measurements. They cannot totally 
rely on SNMP/MRTG for monitoring. Flow/pkt passive 
monitoring tools are used in ATT backbone and sprint 
IPMON for recording flow details. I see lot of presentations 
in nanog sessions on these topics. 

But, I must accept your views as you have rich operational
experience.

> Not sure any of this is particularly germane, in any event.

Noted.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 15:53:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11834
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 15:53:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6KtO411264
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 15:55:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6KtOv11261
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 15:55:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11806
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 15:52:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6KsOv11198;
	Wed, 6 Nov 2002 15:54:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Krkv11173
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 15:53:46 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11733
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 15:51:12 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA6Kr9GP026289;
	Wed, 6 Nov 2002 15:53:09 -0500 (EST)
Date: Wed, 6 Nov 2002 15:53:09 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211062053.gA6Kr9GP026289@newdev.harvard.edu>
To: Mpierce1@aol.com, rja@extremenetworks.com
Subject: Re: [Ieprep] Re: IETF process
Cc: ieprep@ietf.org
In-Reply-To: <8A02FB74-F1B1-11D6-9573-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> For example, it is ENTIRELY proper for me to take my 
> needs/goals/desires/proposals
> for SIP changes directly to the SIP WG

nit - we (the TSV area) set up the SIPPING WG to be a gatekeeper
for SIP so the needs/goals/desires/proposals would need to go there 

I basically agree with Ran on the paths here but will disagree with his last
paragraph.  When Allison & I got this group chartered we wanted
to have a place where folks with various needs/assumptions/backgrounds
could have a discussion to see 
	1/ what can be done with the net of today (as Dave Crocker
	   so clearly suggested in an early BOF)
	2/ what sort of realistic requirements might be developed
	   for changes in IETF protocols that would make things
	   better for the support of ieprep traffic (the sip
	   requirements are an example of this)
	3/ produce a "helpful hints' document (maybe BCP) to
	   help organizations who want to purchase ieprep services
	   understand what is reasonable to ask for considering
	   the Intrenet of today (and maybe near future)

We wanted this process to provide a reality check for people who 
might have unrealistic expectations of what can be done in the 
Internet and to better understand what sorts of things are
seen as needed by the people who want to purchase such services
and, maybe, explore ways to bridge the gap in some places.

This group will not modify any protocols on its own but
that does not mean that it can not think about areas where 
changes could be useful as long as there is an understanding 
of what is a protocol change (which the IETF might do) and a
ISP business model or architecture change (which we can not do)

Scott

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 16:07:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12482
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 16:07:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6L9if12595
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 16:09:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6L9iv12592
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 16:09:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12456
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 16:07:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6L91v12517;
	Wed, 6 Nov 2002 16:09:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6L89v12473
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 16:08:10 -0500
Received: from beamer.mchh.siemens.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12413
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 16:05:34 -0500 (EST)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id WAA18841
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 22:08:02 +0100 (MET)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id WAA12075
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 22:08:02 +0100 (MET)
Received: by MCHH274E with Internet Mail Service (5.5.2656.59)
	id <V6ATNB8Z>; Wed, 6 Nov 2002 22:07:27 +0100
Message-ID: <47D438A0510BD611B9470002A58EDAE7AD2B9B@mchh2a6e.mchh.siemens.de>
From: Ottensmeyer Joerg <joerg.ottensmeyer@siemens.com>
To: "Ieprep (E-mail)" <ieprep@ietf.org>
Date: Wed, 6 Nov 2002 22:07:27 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA6L8Av12474
Subject: [Ieprep] Comment for WG Last Call on draft-ietf-ieprep-sip-reqs-01.txt
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Dear all,

in my draft (draft-otty-ieprep-pstn-features-00.txt), I outlined the emergency services implemented in PSTN. As the charter of this WG says, "...consider how it (the Internet) can best support emergency management...", we should have a look how these services can be modeled using SIP. And as the SIP requirements draft covers the requirements for just this modelling, I tried to match those services with SIP.

In short, those services which I called "user-dependent/authenticated emergency call service" and "origin-dependent emergency call service" are (I believe) covered by the SIP requirements document. In my opinion, in the Internet context these services fall together: as there is no "trust by wire model" in the Internet, the origin-dependent call has to be authenticated and authorized as well, to set the appropriate flag(s) according the "SIP priority scheme". 

However, the (basic) emergency call service (or 911 call) has additional requirements. This are:
- for this service, the SIP server needs be able to resolve the dialed URI (e.g. sip:ambulance@closest) to the address of the nearest Emergency Response Center. 
- it must be possible to place this call must from all SIP phones and the user does not need to be authenticated or even not registered.
- then, the call must be able to receive the same priority levels as the other emergency calls to ensure that the call is processed in the SIP proxies and servers when a "catastrophe level" is activated, i.e. the overall service has to be restricted.

I feel, that those requirements have to be reflected somehow in the document under last call.

best regards
-Jörg                                     
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 16:27:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13045
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 16:27:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6LTq213318
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 16:29:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6LTpv13315
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 16:29:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13031
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 16:27:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6LT7v13301;
	Wed, 6 Nov 2002 16:29:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6LSVv13277
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 16:28:31 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA13000
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 16:25:56 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 6 Nov 2002 21:26:11 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WM4KC8B5>; Wed, 6 Nov 2002 16:29:32 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3CFB@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock'" <woody@pch.net>
Cc: ieprep@ietf.org
Subject: RE: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework
	 -02.txt
Date: Wed, 6 Nov 2002 14:07:42 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Bill,

As of now there are no automated ways of increasing bandwidth to combat
congestions. But capabilities to do it might be available later. 

I still have concerns with emergency traffic when congestions occur on
access and egress nodes if it does not get any preferential treatment. I
agree with you that IP voice packets are small compared to others. But when
it comes to congestions small and/or large packets have to get in line to go
through queue(s). If the queue is full, I am afraid that emergency traffic
packets would be dropped. Another (maybe related) issue is that when large
packets (e.g., data, streaming, etc.) are ahead of voice packets in the
queues, then the QoS (Jitters, delays) for voice would be affected because
it would take longer to process large packets.

Regards,

An


-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Wednesday, November 06, 2002 12:51 PM
To: Nguyen, An
Cc: ieprep@ietf.org
Subject: RE: Congestion avoidance Re: [Ieprep]
draft-ietf-ieprep-framework -02.txt


      On Fri, 1 Nov 2002, Nguyen, An wrote:
    > Are you saying if there is any problem with the access node, the
network
    > operators will solve the problem by throwing more equipment at it? The
    > question is that how dynamic is that bandwidth increasing in response
to
    > congestions?

Not exactly...  If there's a congestion problem within a customer network,
ISPs are not able to resolve that problem.  ISPs cannot autonomously
increase the capacity of a customer tail-circuit, since the customer-owned
CPE must be simultaneously upgraded, nor can ISPs implement QoS on
customer-owned devices, even if it were the case that QoS were beneficial.

Fortunately, none of that is an issue, since the demands which VoIP places
on the network are so small.

                                -Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 16:44:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13824
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 16:44:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6LkiR14541
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 16:46:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Lkiv14538
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 16:46:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13816
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 16:44:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Lk2v14509;
	Wed, 6 Nov 2002 16:46:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6LjWv14486
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 16:45:32 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13773
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 16:42:57 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 16CBA67103; Wed,  6 Nov 2002 13:06:10 -0500 (EST)
Date: Wed, 6 Nov 2002 16:45:20 -0500
Subject: Re: [Ieprep] Re: IETF process
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Scott Bradner <sob@harvard.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211062053.gA6Kr9GP026289@newdev.harvard.edu>
Message-Id: <0BBC4466-F1D1-11D6-9573-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 6, 2002, at 15:53 America/Montreal, Scott Bradner 
wrote:

>> For example, it is ENTIRELY proper for me to take my
>> needs/goals/desires/proposals
>> for SIP changes directly to the SIP WG
>
> nit - we (the TSV area) set up the SIPPING WG to be a gatekeeper
> for SIP so the needs/goals/desires/proposals would need to go there

Nit accepted.

> I basically agree with Ran on the paths here but will disagree with 
> his last
> paragraph.

Are you saying that I could NOT (i.e. would not be permitted) to take
proposals that I (quite hypothetically) have directly to SIPPING ?

(NB: As noted before, I do not happen to have any proposals relating
to SIP or SIPPING.  I rarely work much above layer-3).

If yes, that seems like a really huge violation of IETF openness
and one that would be objectionable to most of the IETF community.

(And if the answer is yes, I'm likely to take this up on the ietf
discussion mailing list for broader community discussion because
it would be so radical a change in our ways.)

My suspicion is that you created IEprep as an alternative path,
for a particular community, not proscriptively to block other normal
IETF paths of discussion/progress -- but the above sentence makes
this far from clear.

Please clarify.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 16:52:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14184
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 16:52:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6Lt1M14942
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 16:55:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Lt1v14939
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 16:55:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14167
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 16:52:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Ls2v14907;
	Wed, 6 Nov 2002 16:54:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Lrbv14884
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 16:53:37 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14150
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 16:51:02 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 3262067103; Wed,  6 Nov 2002 13:14:15 -0500 (EST)
Date: Wed, 6 Nov 2002 16:53:25 -0500
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework -02.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: "Nguyen, An" <nguyena@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3CFB@emshqs1.ncr.disa.mil>
Message-Id: <2CC9E2FE-F1D2-11D6-9573-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 6, 2002, at 14:07 America/Montreal, Nguyen, An wrote:

> Bill,
>
> As of now there are no automated ways of increasing bandwidth to combat
> congestions. But capabilities to do it might be available later.

I think Bill wasn't talking about automation, but about the fact that
the size of the access link from ISP to customer is controlled by the
customer's willingness to pay for a larger pipe.  That is, if customer
packets are congested on the access link then it can only be true
because the customer *chose* not to have a faster link (or the ISP
doesn't offer a faster link, which is pretty uncommon -- and might
mean it is time to change ISPs).

> I still have concerns with emergency traffic when congestions occur on
> access and egress nodes if it does not get any preferential treatment. 
> I
> agree with you that IP voice packets are small compared to others. But 
> when
> it comes to congestions small and/or large packets have to get in line 
> to go
> through queue(s). If the queue is full, I am afraid that emergency 
> traffic
> packets would be dropped. Another (maybe related) issue is that when 
> large
> packets (e.g., data, streaming, etc.) are ahead of voice packets in the
> queues, then the QoS (Jitters, delays) for voice would be affected 
> because
> it would take longer to process large packets.

Bill's other point is that even if the ISP were to configure (some kind
of) QoS on its side of the access link, it won't help packets 
originating
on the customer side because the congestion/buffer issue would live in
the customer-premise router not the ISP router.  It varies whether the
ISP manages the CPE router, but in Bill's text he implies that the 
customer
might be managing their own CPE router (so the ISP could not enable QoS
on that box or otherwise alter its configuration).

Finally, Bill seems to be saying that in his operational experience, 
such
congestion either does not occur or it occurs in so modest a manner that
it does not adversely affect VoIP traffic.  It might be helpful to 
understand
more about the configuration of Bill's VoIP application-layer gorp,
since he seems to have a setup that works reasonably well.

The experience of former colleagues running voice/IP/HF Radio (which is
often congested because HF radio is very low bandwidth) was that if one
had the right vocoder, one didn't have any problems.  If one did not 
have
the right vocoder, nothing could fix the problems.  I'm not a vocoder
expert, so can't comment myself on which ones worked better/worse.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 17:00:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14544
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 17:00:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6M2To15658
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 17:02:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6M2Tv15655
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 17:02:29 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14514
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 16:59:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6M1Gv15551;
	Wed, 6 Nov 2002 17:01:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6M0sv15379
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 17:00:54 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14457
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 16:58:19 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA6M0cm6015645;
	Wed, 6 Nov 2002 17:00:38 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA6M0aH9007821
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 6 Nov 2002 17:00:37 -0500 (EST)
Message-ID: <3DC9915B.5000706@cs.columbia.edu>
Date: Wed, 06 Nov 2002 17:02:03 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ottensmeyer Joerg <joerg.ottensmeyer@siemens.com>
CC: "Ieprep (E-mail)" <ieprep@ietf.org>
Subject: Re: [Ieprep] Comment for WG Last Call on draft-ietf-ieprep-sip-reqs-01.txt
References: <47D438A0510BD611B9470002A58EDAE7AD2B9B@mchh2a6e.mchh.siemens.de>
In-Reply-To: <47D438A0510BD611B9470002A58EDAE7AD2B9B@mchh2a6e.mchh.siemens.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Since charter discussions seem all the rage these days, it might be 
worth noting that we have, I believe, several times reached the 
conclusion that 911/112-style calls are out of scope. However, I've been 
working on this very topic for a while. You can find a detailed 
description of the issues in the draft draft-schulzrinne-sipping-sos-02 
and draft-ietf-sip-emergency-00. (If they are expired, you can find them 
at http://www.cs.columbia.edu/sip/drafts/).

We have been building a system locally that solves the first of the 
problem you list below. The second and third appear to be operational 
ones that does not seem to require any additional protocol capabilities. 
With the *sos* draft, a proxy can detect that the call is destined for a 
PSAP and thus modify normal AAA procedures and elevate call priority 
should local operating procedures call for that.

A number of BOFs have been held under the auspices of the SIP(PING) 
working group, but not enough people seem to care about this topic, so 
it seems to always be displaced by more urgent things like ISUP 
interworking :-)

I'll be glad to get into more details, but my interpretation is that at 
least the first two issues are considered out of scope of IEPREP.

Ottensmeyer Joerg wrote:

> Dear all,
>
>
> - for this service, the SIP server needs be able to resolve the dialed 
> URI (e.g. sip:ambulance@closest) to the address of the nearest 
> Emergency Response Center.
> - it must be possible to place this call must from all SIP phones and 
> the user does not need to be authenticated or even not registered.
> - then, the call must be able to receive the same priority levels as 
> the other emergency calls to ensure that the call is processed in the 
> SIP proxies and servers when a "catastrophe level" is activated, i.e. 
> the overall service has to be restricted.
>
> I feel, that those requirements have to be reflected somehow in the 
> document under last call.
>
> best regards
> -Jörg
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 17:58:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16214
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 17:58:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6N05G19157
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 18:00:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6N05v19154
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 18:00:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16209
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 17:57:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Mx7v19098;
	Wed, 6 Nov 2002 17:59:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6MwNv19059
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 17:58:23 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16158
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 17:55:47 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA6MmYd18437;
	Wed, 6 Nov 2002 14:48:34 -0800 (PST)
Date: Wed, 6 Nov 2002 14:48:34 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
cc: RJ Atkinson <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9AFE6@KC-MAIL2.kc.umkc.edu>
Message-ID: <Pine.GSO.4.44.0211061445100.14087-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 6 Nov 2002, Ayyasamy, Senthilkumar  (UMKC-Student) wrote:
    > Operators do need some tools for accounting, capacity
    > planning and backbone measurements. They cannot totally
    > rely on SNMP/MRTG for monitoring.

The unfortunate fact is that a significant number don't do _either_.  The
vast majority use SNMP counters, often just at the edges.  A tiny handful
of ISPs run netflow or equivalent, and an even smaller fraction of those
(fewer than a dozen globally, by several estimates) actually analyze the
netflow data to understand their traffic flows.

    > I see lot of presentations
    > in nanog sessions on these topics.

Unfortunately it's the same bunch of us pushing it every time...  those
who get it are already doing it, and those who don't get it don't seem to
be rushing to pick up clue.

This is very unfortunate, but it's true despite the best efforts of quite
a few folks.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 18:32:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16945
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 18:32:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6NYuM20865
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 18:34:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6NYtv20862
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 18:34:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16942
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 18:32:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6NY2v20820;
	Wed, 6 Nov 2002 18:34:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6NXav20772
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 18:33:36 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16903
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 18:31:00 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA6NWwxA026919;
	Wed, 6 Nov 2002 18:32:58 -0500 (EST)
Date: Wed, 6 Nov 2002 18:32:58 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211062332.gA6NWwxA026919@newdev.harvard.edu>
To: rja@extremenetworks.com, sob@harvard.edu
Subject: Re: [Ieprep] Re: IETF process
Cc: ieprep@ietf.org
In-Reply-To: <0BBC4466-F1D1-11D6-9573-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> Are you saying that I could NOT (i.e. would not be permitted) to take
> proposals that I (quite hypothetically) have directly to SIPPING ?

nope - any individual can do that

> My suspicion is that you created IEprep as an alternative path,

its my opinion that any WG can do what an individual can do (take 
ideas to an IETF working group)

this WG is a place to discuss a particular set of topics so that 
maybe consensus ideas can be taken to other groups rather than
bunches of people taking their individual ideas

but that would not stop an individual from doing what they thought best

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 18:55:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17400
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 18:55:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6Nw1r22182
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 18:58:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Nw1v22179
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 18:58:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17354
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 18:55:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Nv1v22142;
	Wed, 6 Nov 2002 18:57:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Nuhv22119
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 18:56:43 -0500
Received: from imo-r07.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17321
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 18:54:07 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r07.mx.aol.com (mail_out_v34.13.) id a.55.30ab8380 (4262);
	Wed, 6 Nov 2002 18:56:34 -0500 (EST)
Message-ID: <55.30ab8380.2afb0632@aol.com>
Date: Wed, 6 Nov 2002 18:56:34 EST
Subject: Re: [Ieprep] WG last call for IEPREP Topology Scenarios
To: KIMBERLY.S.KING@saic.com, ieprep@ietf.org
CC: mankin@psg.com, sob@harvard.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_55.30ab8380.2afb0632_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_55.30ab8380.2afb0632_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Comments:

The table of contents identifies the scenarios with letters A-D, while the 
actual sections do not. Is it the intention to use these letters?

2.1 delete reference to "sessions", since the CSN knows nothing about this. 
If this was addressing SIP specifically in the core, the reference to 
"session" could be moved to later in the same sentence in relation to the 
mention of the core, for example: "... initiates (dials) a call to another 
CSN phone with a session being established through an IP core between the two 
CSNs."

2.2 The statement about "One key espect ..." concerning prioritization should 
apply to all four scenarios. This becomes one of the important discussion 
points for all four scenarios (beginning with "is it needed?").

Mike Pierce
Artel




--part1_55.30ab8380.2afb0632_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>Comments:
<BR>
<BR>The table of contents identifies the scenarios with letters A-D, while the actual sections do not. Is it the intention to use these letters?
<BR>
<BR>2.1 delete reference to "sessions", since the CSN knows nothing about this. If this was addressing SIP specifically in the core, the reference to "session" could be moved to later in the same sentence in relation to the mention of the core, for example: "... initiates (dials) a call to another CSN phone with a session being established through an IP core between the two CSNs."
<BR>
<BR>2.2 The statement about "One key espect ..." concerning prioritization should apply to all four scenarios. This becomes one of the important discussion points for all four scenarios (beginning with "is it needed?").
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR>
<BR></FONT></HTML>

--part1_55.30ab8380.2afb0632_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 18:57:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17511
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 18:57:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6Nxvb22319
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 18:59:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Nxvv22316
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 18:59:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17470
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 18:57:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Nx1v22287;
	Wed, 6 Nov 2002 18:59:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6NwWv22261
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 18:58:32 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17401
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 18:55:55 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA6Nvtg0027039;
	Wed, 6 Nov 2002 18:57:55 -0500 (EST)
Date: Wed, 6 Nov 2002 18:57:55 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211062357.gA6Nvtg0027039@newdev.harvard.edu>
To: hgs@cs.columbia.edu, joerg.ottensmeyer@siemens.com
Subject: Re: [Ieprep] Comment for WG Last Call on draft-ietf-ieprep-sip-reqs-01.txt
Cc: ieprep@ietf.org
In-Reply-To: <3DC9915B.5000706@cs.columbia.edu>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> I'll be glad to get into more details, but my interpretation is that at 
> least the first two issues are considered out of scope of IEPREP.

I agree with Hanning, this is not in IEPREP's charter

I do think that we (the IETF) should think about this space at some point
but not in this WG

(also note that one requirement of e911 is missing, which is location
determination)

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov  6 19:15:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17856
	for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 19:15:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA70H9K23531
	for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 19:17:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA70H9v23528
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 19:17:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17846
	for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 19:14:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA70GGv23507;
	Wed, 6 Nov 2002 19:16:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA70F7v23472
	for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 19:15:07 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17818
	for <ieprep@ietf.org>; Wed, 6 Nov 2002 19:12:30 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 90CA967103; Wed,  6 Nov 2002 15:35:47 -0500 (EST)
Date: Wed, 6 Nov 2002 19:14:57 -0500
Subject: Re: [Ieprep] Re: IETF process
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Scott Bradner <sob@harvard.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211062332.gA6NWwxA026919@newdev.harvard.edu>
Message-Id: <F27D7FFC-F1E5-11D6-BD02-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Thanks for the clarification.
That seems quite normal and reasonable to me.

Ran

On Wednesday, Nov 6, 2002, at 18:32 America/Montreal, Scott Bradner 
wrote:

>> Are you saying that I could NOT (i.e. would not be permitted) to take
>> proposals that I (quite hypothetically) have directly to SIPPING ?
>
> nope - any individual can do that
>
>> My suspicion is that you created IEprep as an alternative path,
>
> its my opinion that any WG can do what an individual can do (take
> ideas to an IETF working group)
>
> this WG is a place to discuss a particular set of topics so that
> maybe consensus ideas can be taken to other groups rather than
> bunches of people taking their individual ideas
>
> but that would not stop an individual from doing what they thought best
>
> Scott
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov  7 07:49:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18803
	for <ieprep-archive@odin.ietf.org>; Thu, 7 Nov 2002 07:49:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7Cpbr14343
	for ieprep-archive@odin.ietf.org; Thu, 7 Nov 2002 07:51:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Cpbv14340
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 07:51:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18758
	for <ieprep-web-archive@ietf.org>; Thu, 7 Nov 2002 07:49:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Co7v14293;
	Thu, 7 Nov 2002 07:50:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Cn2v14254
	for <ieprep@optimus.ietf.org>; Thu, 7 Nov 2002 07:49:02 -0500
Received: from imo-m05.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18619
	for <ieprep@ietf.org>; Thu, 7 Nov 2002 07:46:30 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m05.mx.aol.com (mail_out_v34.13.) id b.19d.b8d7652 (25914);
	Thu, 7 Nov 2002 07:48:44 -0500 (EST)
Message-ID: <19d.b8d7652.2afbbb2b@aol.com>
Date: Thu, 7 Nov 2002 07:48:43 EST
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
To: woody@pch.net
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_19d.b8d7652.2afbbb2b_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_19d.b8d7652.2afbbb2b_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

[In response to my comments about what the Defense Department (who I am being 
paid to attend the IETF) wants:]

In a message dated 11/6/2002 12:12:29 PM Eastern Standard Time, woody@pch.net 
writes:


> How many times do you need to be told that THIS IS NOT OKAY?  If you don't
> have the intellectual honesty and strength of conviction to say something
> because YOU believe it, THERE IS NO PLACE FOR YOU IN THE IETF.
> 
> You are participating as an INDIVIDUAL, not representing an organization.
> 
> We want to know what YOU think.  We already know that organizations are
> incapable of thought.
> 


[MAP] I'm getting very mixed messages. When I say what I think is required, 
you (and others) jump on me for not identifying what organization I 
"represent" that wants (or thinks they need) something or that other 
"organizations" should represent themselves. Examples:

On Oct 24 Ran wrote (in response to my claim that the Defense Dept. needed 
something):

If DoD does require this (and your lack of identification of affiliation
begs the question of whether you speak officially on the record for the
entire DoD), then I believe what you want is more like these words ...

On Oct 31 Woody wrote to Hal (in response to his statements about 
requirements for NCS):

Until such time as you get other organisations and other countries
to represent themselves here and present their perspectives, preferably
in their own documents about what services they use today and plan
to use in the future, the rest of us (who aren't monetarily or contractually
beholden to NCS) can only realistically know that the document represents
your views based on your experience at NCS.

So what is the real answer? Are you ready to seriously discuss what I or 
others personally think is needed, or do you want "organizations" to speak up 
first? Please make up your mind, since I haven't yet figured out which is the 
correct (or safe) path.

(I apologize to the others on this list who continue to see this continuing 
discussion, but I feel that all need to understand the ongoing difficulty we 
are having in this WG with moving things forward because the legitimate 
discussion of the issues is being overshadowed by such petty comments.)

Mike Pierce
Artel


--part1_19d.b8d7652.2afbbb2b_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>[In response to my comments about what the Defense Department (who I am being paid to attend the IETF) wants:]
<BR>
<BR>In a message dated 11/6/2002 12:12:29 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">How many times do you need to be told that THIS IS NOT OKAY? &nbsp;If you don't
<BR>have the intellectual honesty and strength of conviction to say something
<BR>because YOU believe it, THERE IS NO PLACE FOR YOU IN THE IETF.
<BR>
<BR>You are participating as an INDIVIDUAL, not representing an organization.
<BR>
<BR>We want to know what YOU think. &nbsp;We already know that organizations are
<BR>incapable of thought.
<BR></BLOCKQUOTE>
<BR>
<BR>
<BR>[MAP] I'm getting very mixed messages. When I say what I think is required, you (and others) jump on me for not identifying what organization I "represent" that wants (or thinks they need) something or that other "organizations" should represent themselves. Examples:
<BR>
<BR>On Oct 24 Ran wrote (in response to my claim that the Defense Dept. needed something):
<BR>
<BR>If DoD does require this (and your lack of identification of affiliation
<BR>begs the question of whether you speak officially on the record for the
<BR>entire DoD), then I believe what you want is more like these words ...
<BR>
<BR>On Oct 31 Woody wrote to Hal (in response to his statements about requirements for NCS):
<BR>
<BR>Until such time as you get other organisations and other countries
<BR>to represent themselves here and present their perspectives, preferably
<BR>in their own documents about what services they use today and plan
<BR>to use in the future, the rest of us (who aren't monetarily or contractually
<BR>beholden to NCS) can only realistically know that the document represents
<BR>your views based on your experience at NCS.
<BR>
<BR>So what is the real answer? Are you ready to seriously discuss what I or others personally think is needed, or do you want "organizations" to speak up first? Please make up your mind, since I haven't yet figured out which is the correct (or safe) path.
<BR>
<BR>(I apologize to the others on this list who continue to see this continuing discussion, but I feel that all need to understand the ongoing difficulty we are having in this WG with moving things forward because the legitimate discussion of the issues is being overshadowed by such petty comments.)
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_19d.b8d7652.2afbbb2b_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov  7 09:51:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26504
	for <ieprep-archive@odin.ietf.org>; Thu, 7 Nov 2002 09:51:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7Er8V22512
	for ieprep-archive@odin.ietf.org; Thu, 7 Nov 2002 09:53:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Er8v22509
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 09:53:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26497
	for <ieprep-web-archive@ietf.org>; Thu, 7 Nov 2002 09:50:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7EqOv22457;
	Thu, 7 Nov 2002 09:52:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Epbv22432
	for <ieprep@optimus.ietf.org>; Thu, 7 Nov 2002 09:51:37 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26459
	for <ieprep@ietf.org>; Thu, 7 Nov 2002 09:49:05 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 59EFC67103; Thu,  7 Nov 2002 06:12:29 -0500 (EST)
Date: Thu, 7 Nov 2002 09:51:33 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <19d.b8d7652.2afbbb2b@aol.com>
Message-Id: <685BCF4F-F260-11D6-8E9D-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Re: more process discussion
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 7, 2002, at 07:48 America/Montreal, Mpierce1@aol.com 
wrote:
> So what is the real answer? Are you ready to seriously discuss what I 
> or others personally think is needed, or do you want "organizations" 
> to speak up first? Please make up your mind, since I haven't yet 
> figured out which is the correct (or safe) path.

	We are interested in each person's personal views, but we also want 
each
person to be open about the source of their interests in this topic 
(e.g. the fact
that someone is being funded by DISA/NCS is relevant to the readers).  
This is
particularly relevant to the broader IETF community for folks who do 
not participate
in the IETF unless they get specifically funded to do so in a 
particular WG or
for a particular private agenda (such as the DISA/NCS agenda in this 
case),
less relevant for folks who participate despite lack of such directed 
funding
(e.g. jnc, who not everyone here knows and probably is not subscribed 
to IEprep,
though he does actively participate elsewhere).

	It is customary, but not required, for folks to use email addresses 
that
indicate such relationships.  For example, while someone in the IETF 
was employed
in the mid90s as a support contractor to NRL (which is a civil service 
lab,
not GOCO like NASA/JPL),  that person routinely used an email address 
which indicated
that the person worked at NRL for <particular contractor name>.  
Woody's email
clearly indicates he is with PCH and one can trivially go find out what 
PCH
does by looking at their web site.  An email like <foo@yahoo.com> is 
totally
opaque and (absent clear identification of relationships), begs that 
question.
When a different long-time IETF participant was employed by a part of 
DoD that
did not have a very good email service to the public Internet, he used 
an account
at a nearby university, but clearly indicated that he was with DoD and 
which part
of DoD as best he could, so everything was in the open.

	So woody is right that the IETF's hope is that one will represent 
one's own
views -- particularly when those conflict directly with sponsor's 
views, the
community is also looking for full openness about what the potential 
sources of bias
are in any given person's stated views.  Direct funding to participate 
in an effort
on <foo> is a potential bias.  We all hope it does not actually 
translate into an
actual bias, at least within the IETF's scope.

	Hal's seeming reluctance to participate directly and respond in a 
timely manner
to questions directly relating to his employer's goals has not helped 
things at all,
IMNVHO.  It sure looks from the outside that Hal is trying to cover up 
his
financial relationships with various DISA contractors who are 
participating in
this WG and that appears that he's trying to use that obscurity to 
further his
private agenda.  This fosters widespread suspicion and mistrust, 
whereas openness
from the get go would have done quite the opposite.  An's participation 
has been helpful
in part because he's been very open about where he's coming from, by 
contrast, and
mostly because he is consistently an active participant here.

Sincerely,

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov  7 11:28:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01019
	for <ieprep-archive@odin.ietf.org>; Thu, 7 Nov 2002 11:28:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7GUtT29405
	for ieprep-archive@odin.ietf.org; Thu, 7 Nov 2002 11:30:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7GUsv29402
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 11:30:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00941
	for <ieprep-web-archive@ietf.org>; Thu, 7 Nov 2002 11:28:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7GU4v29307;
	Thu, 7 Nov 2002 11:30:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7GNsv29031
	for <ieprep@optimus.ietf.org>; Thu, 7 Nov 2002 11:23:54 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00627
	for <ieprep@ietf.org>; Thu, 7 Nov 2002 11:21:21 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Thu, 7 Nov 2002 11:23:31 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002110711233221354
 ; Thu, 07 Nov 2002 11:23:32 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMF7XP80>; Thu, 7 Nov 2002 11:23:19 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77917@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>, Mpierce1@aol.com
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: more process discussion
Date: Thu, 7 Nov 2002 11:23:30 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> the
> community is also looking for full openness about what the potential 
> sources of bias
> are in any given person's stated views.  Direct funding to 
> participate 
> in an effort
> on <foo> is a potential bias.  We all hope it does not actually 
> translate into an
> actual bias, at least within the IETF's scope.

I have supported DISA in the past and NCS operations in the present.  My
co-chair duties are funded by SAIC overhead.  I strive to maintain
impartiality and provide my personal best in this co-chair role.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov  7 14:32:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07428
	for <ieprep-archive@odin.ietf.org>; Thu, 7 Nov 2002 14:32:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7JYm710394
	for ieprep-archive@odin.ietf.org; Thu, 7 Nov 2002 14:34:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7JYlv10391
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 14:34:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07333
	for <ieprep-web-archive@ietf.org>; Thu, 7 Nov 2002 14:32:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7JW9v10166;
	Thu, 7 Nov 2002 14:32:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7JVHv10129
	for <ieprep@optimus.ietf.org>; Thu, 7 Nov 2002 14:31:17 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07176
	for <ieprep@ietf.org>; Thu, 7 Nov 2002 14:28:38 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA7JPDd21380;
	Thu, 7 Nov 2002 11:25:13 -0800 (PST)
Date: Thu, 7 Nov 2002 11:25:13 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: ieprep@ietf.org
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <19d.b8d7652.2afbbb2b@aol.com>
Message-ID: <Pine.GSO.4.44.0211071114260.21181-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 7 Nov 2002 Mpierce1@aol.com wrote:
    > ...the Defense Department (who I am being paid to attend the IETF) wants:
    > [MAP] I'm getting very mixed messages. When I say what I think is required,

No, it's us who are getting mixed messages.  You've repeated many times
that you're representing DoD interests and positions.  We've said that we
recognize that, and that that's not acceptable within the standards of
intellectual integrity which we hold ourselves to.  Now you're complaining
that we're treating you as though you're not speaking for yourself.

If you are indeed representing a position of the DoD, we can relate to
that, and deal with it accordingly.  The IETF reacts to outside events
continuously; events of political as well as technological nature.

If, on the other hand, you're representing yourself, and not the DoD,
you're very welcome to participate within the IETF process, including
other working groups like DIFFSERV and SIPPING.

However if you masquerade as an individual, and try to take DoD interests
before those working groups directly, they'll toss you out on your ear
again.

Which is why (and Scott, please excuse me for trying to paraphrase your
earlier statements) this working group exists: to work with the political
fact that the DoD's position is that it has requirements of the Internet
which it doesn't understand, and can't articulate in packet-switched
terms, but apparently feels strongly about.  That appears to me to be the
work of this working group: to try to understand what the DoD's perceived
needs are, and try to intepret them in some sort of actual quantitative
way that can be evaluated, and perhaps passed along for consideration to
specific protocol working groups if they're worthy of the attention of
those bodies.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov  7 15:19:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09769
	for <ieprep-archive@odin.ietf.org>; Thu, 7 Nov 2002 15:19:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7KLui14729
	for ieprep-archive@odin.ietf.org; Thu, 7 Nov 2002 15:21:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7KLtv14726
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 15:21:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09760
	for <ieprep-web-archive@ietf.org>; Thu, 7 Nov 2002 15:19:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7KL2v14679;
	Thu, 7 Nov 2002 15:21:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7KK5v14639
	for <ieprep@optimus.ietf.org>; Thu, 7 Nov 2002 15:20:05 -0500
Received: from wells.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09574
	for <ieprep@ietf.org>; Thu, 7 Nov 2002 15:17:31 -0500 (EST)
Received: from JMPOLK-W2K (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id MAA09766; Thu, 7 Nov 2002 12:19:55 -0800 (PST)
Message-Id: <4.1.20021107140808.02dd7738@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 07 Nov 2002 14:19:54 -0600
To: Mpierce1@aol.com, KIMBERLY.S.KING@saic.com, ieprep@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Ieprep] WG last call for IEPREP Topology Scenarios
Cc: mankin@psg.com, sob@harvard.edu
In-Reply-To: <55.30ab8380.2afb0632@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

At 06:56 PM 11/6/2002 -0500, Mpierce1@aol.com wrote: 
>
> Comments: 
>
> The table of contents identifies the scenarios with letters A-D, while the
> actual sections do not. Is it the intention to use these letters? 


Good catch, I thought I removed all the Letter (A,B,C,D) references


>
> 2.1 delete reference to "sessions", since the CSN knows nothing about this.
> If this was addressing SIP specifically in the core, the reference to
> "session" could be moved to later in the same sentence in relation to the
> mention of the core, for example: "... initiates (dials) a call to another
> CSN phone with a session being established through an IP core between the two
> CSNs." 


I think I'll remove the word "sessions" from the sentence


>
> 2.2 The statement about "One key espect ..." concerning prioritization should
> apply to all four scenarios. This becomes one of the important discussion
> points for all four scenarios (beginning with "is it needed?"). 


The intent here is to directly address a list concern/discussion regarding
whether or not the IP portion (at the GW) of this Topology is ETS aware, and
whether there was one or two authentication mechanisms used (with the latter
likely requiring different user behavior if they are on an IP phone vs. a CSN
phone).

Should the paragraph after Figure 2 be removed (and likely included within the
Topology Implications ID that's coming)?


>
> Mike Pierce 
> Artel 
>




cheers,
James 

              *************************************
"People generally demand more respect for their own rights than 
                         they are willing to allow for others"


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov  7 15:41:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11093
	for <ieprep-archive@odin.ietf.org>; Thu, 7 Nov 2002 15:41:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7KhPd17547
	for ieprep-archive@odin.ietf.org; Thu, 7 Nov 2002 15:43:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7KhPv17544
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 15:43:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11058
	for <ieprep-web-archive@ietf.org>; Thu, 7 Nov 2002 15:40:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7KgBv17410;
	Thu, 7 Nov 2002 15:42:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7KdFv17173
	for <ieprep@optimus.ietf.org>; Thu, 7 Nov 2002 15:39:15 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10914
	for <ieprep@ietf.org>; Thu, 7 Nov 2002 15:36:40 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Thu, 7 Nov 2002 15:38:52 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002110715385506010
 ; Thu, 07 Nov 2002 15:38:55 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMF7YPX4>; Thu, 7 Nov 2002 15:38:43 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E7791B@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'James M. Polk '" <jmpolk@cisco.com>,
        "'Mpierce1@aol.com '" <Mpierce1@aol.com>,
        "'KIMBERLY.S.KING@saic.com '" <KIMBERLY.S.KING@saic.com>,
        "'ieprep@ietf.org '" <ieprep@ietf.org>
Cc: "'mankin@psg.com '" <mankin@psg.com>,
        "'sob@harvard.edu '" <sob@harvard.edu>
Subject: RE: [Ieprep] WG last call for IEPREP Topology Scenarios
Date: Thu, 7 Nov 2002 15:38:49 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>Should the paragraph after Figure 2 be removed 
>(and likely included within the Topology Implications 
> ID that's coming)?

That sounds reasonable to me.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov  7 15:42:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11248
	for <ieprep-archive@odin.ietf.org>; Thu, 7 Nov 2002 15:42:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7Kice17746
	for ieprep-archive@odin.ietf.org; Thu, 7 Nov 2002 15:44:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Kicv17743
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 15:44:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11186
	for <ieprep-web-archive@ietf.org>; Thu, 7 Nov 2002 15:42:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Khbv17596;
	Thu, 7 Nov 2002 15:43:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7KZ2v15430
	for <ieprep@optimus.ietf.org>; Thu, 7 Nov 2002 15:35:02 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08965
	for <1timer>; Thu, 7 Nov 2002 15:11:40 -0500 (EST)
Message-Id: <200211072011.PAA08965@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
To: All IETF Working Groups: ;
x-msg: NoteWell
Date: Thu, 07 Nov 2002 15:11:40 -0500
Subject: [Ieprep] Note Well Statement
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


>From time to time, especially just before a meeting, this statement is to
be sent to each and every IETF working group mailing list.
===========================================================================

				NOTE WELL

All statements related to the activities of the IETF and addressed to the
IETF are subject to all provisions of Section 10 of RFC 2026, which grants
to the IETF and its participants certain licenses and rights in such
statements.

Such statements include verbal statements in IETF meetings, as well as
written and electronic communications made at any time or place, which are
addressed to

    - the IETF plenary session,
    - any IETF working group or portion thereof,
    - the IESG, or any member thereof on behalf of the IESG,
    - the IAB or any member thereof on behalf of the IAB,
    - any IETF mailing list, including the IETF list itself,
      any working group or design team list, or any other list
      functioning under IETF auspices,
    - the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other function,
that are clearly not intended to be input to an IETF activity, group or
function, are not subject to these provisions.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov  7 16:22:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13705
	for <ieprep-archive@odin.ietf.org>; Thu, 7 Nov 2002 16:22:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7LOds21429
	for ieprep-archive@odin.ietf.org; Thu, 7 Nov 2002 16:24:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7LOdv21426
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 16:24:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13688
	for <ieprep-web-archive@ietf.org>; Thu, 7 Nov 2002 16:22:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7LN8v21322;
	Thu, 7 Nov 2002 16:23:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7LMLv21281
	for <ieprep@optimus.ietf.org>; Thu, 7 Nov 2002 16:22:21 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13601
	for <ieprep@ietf.org>; Thu, 7 Nov 2002 16:19:47 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 7 Nov 2002 15:22:15 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 7 Nov 2002 15:22:15 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD4331610234EF5D@KC-MAIL2.kc.umkc.edu>
Thread-Topic: CSTB report
Thread-Index: AcKGo74vosZR26VUQ1u7ChW1N4oSwg==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: <ieprep@ietf.org>
X-OriginalArrivalTime: 07 Nov 2002 21:22:15.0592 (UTC) FILETIME=[BEA2B280:01C286A3]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA7LMMv21282
Subject: [Ieprep] CSTB report
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

CSTB have been working on a project 
"Internet Under Crisis Conditions: Learning from September 11"
for past 8 months. More details:
http://www7.nationalacademies.org/cstb/project_crisisconditions.html

They are releasing the final document on Nov 21 2002. Their will be
a public seminar by the committee members Craig Partridge, David 
Clark, and Sean Donelan on that day. Other committee members 
include Jennifer Rexford, Vern Paxson, Paul Barford and Mary 
Vernon.

I presume, this document may help in avoiding the present 
confusion ( what can be done with the present technology etc.) 
and also, focus some of our future work in this WG. 

Stay tuned :)

- Senthil.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 03:34:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10515
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 03:34:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA88b8O05382
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 03:37:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA88b8v05370
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 03:37:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10511
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 03:34:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA88aBv05237;
	Fri, 8 Nov 2002 03:36:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA88Wfv05016
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 03:32:41 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10414
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 03:29:59 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA88QWd08266;
	Fri, 8 Nov 2002 00:26:32 -0800 (PST)
Date: Fri, 8 Nov 2002 00:26:32 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: ieprep@ietf.org
Subject: RE: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework 
 -02.txt
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3CFB@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211080014490.5579-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 6 Nov 2002, Nguyen, An wrote:
    > As of now there are no automated ways of increasing bandwidth to combat
    > congestions. But capabilities to do it might be available later.

This has been tried in the past, but with limited success...  The problem
is that there is a high cost in the capacity of the local loop and CPE,
and even if all of the upgrade procedure can be automated, no customer
will willingly pay for the unused capacity of the headroom in the local
loop.

For example, let's say that a customer has an average of 300kbps of
traffic, and peaks at about a megabit.  They're obviously going to buy a
single T1.  What's their upgrade path?  Normally it would be a second T1,
generally to a different provider, if possible.  But hypothetically, you
could have provisioned that T1 as a channel of a DS3, and when they needed
more bandwidth (perhaps their average utilization had exceeded a megabit
for ten days out of the prior fourteen, or something like that) you could
have dynamically negotiated the turn-up of a second channel.

The problem is that the customer would have to be paying for the entire
DS3, and amortizing a DS3-capable router, in order for that instantanaity
to be possible.  That's a twenty-fold increase in both the one-time and
recurring costs.  All being paid for capacity which is by its very
definition unused.

Outside of the DoD, there aren't too many customers who snap up deals like
that.  :-)

    > When it comes to congestions small and/or large packets have to get
    > in line to go through queue(s). If the queue is full, I am afraid
    > that emergency traffic packets would be dropped.

Perhaps you might acquaint yourself with the infrequency with which this
happens, and thereby reassure yourself in this regard.

    > Another (maybe related) issue is that when large packets (e.g.,
    > data, streaming, etc.) are ahead of voice packets in the queues,
    > then the QoS (Jitters, delays) for voice would be affected because
    > it would take longer to process large packets.

This is quite true as well...  There's no argument over whether jitter
exists in the network, just as there's no argument over whether congestion
exists in the network.  What operators are telling you is that it's so
far from being a problem as to be utterly unworth anyone's attention, much
less that of smart people who could be using their intelligence to solve
problems.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 08:26:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18251
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 08:26:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8DSrl24302
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 08:28:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DSrv24299
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 08:28:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18165
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 08:26:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DS5v24139;
	Fri, 8 Nov 2002 08:28:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DRFv24083
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 08:27:15 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA18050
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 08:24:41 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.01623-0@bells.cs.ucl.ac.uk>; Fri, 8 Nov 2002 13:27:06 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: RJ Atkinson <rja@extremenetworks.com>
cc: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] draft-ietf-ieprep-framework-02.txt
In-reply-to: Your message of "Sat, 02 Nov 2002 07:08:22 EST." <C8633ACD-EE5B-11D6-9F10-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 08 Nov 2002 13:27:06 +0000
Message-ID: <857.1036762026@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ran,

> My other point is that if the intent really is *application-layer* 
> routing,
> then that precision was not obvious in my reading of the current text.
> Though I do basically share the belief that relying on normal IP dynamic
> routing is probably the more successful strategy overall...

the intent was to raise awareness to the reader of another form of
routing (application level) and of work being done within a more
constrained context of intra-domain routing (MPLS).  however, neither
is presented as a solution or even approaches that must be taken.  

> Editing several of our documents to have more words like that would be
> generally helpful.  Putting words like "This document only applies to
> operators who choose to offer [x], [y], and [z]." in a scoping paragraph
> at the beginning of a document would also be helpful.

yes, words to this effect will be added to the Framework document.

as for your comments on the status of the Framework draft...

> I think that the "framework" draft is hopeless to edit into
> an IETF-style requirements draft.  

agreed, and just for clarity, was never the intent by the authors

> I think that it IS useful,
> if edited into being an (obviously) purely informational document
> on what might be done and how diverse pieces might fit together.
>
> In my view, this would be published as an Informational status
> document, not standards-track, and would have the word "requirement"
> edited out throughout the document.

right.  as stated previously, the word "requirement" in the draft was
an unfortunate choice and can be easily edited out.  given the charter 
stating that the drafts are to be Informational, that was the original
intent by the authors.


in addition to the above, two other items need to be edited out.
the first is a suggested set of new attributes for TRIP.  the second
is suggested Namespace.Value for SIP.  both of these cross the line 
and becomes too specific as solutions.

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 08:27:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18295
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 08:27:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8DTPU24436
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 08:29:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DTPv24433
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 08:29:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18256
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 08:26:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DSdv24217;
	Fri, 8 Nov 2002 08:28:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DRWv24105
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 08:27:32 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA18072
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 08:24:59 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.01637-0@bells.cs.ucl.ac.uk>; Fri, 8 Nov 2002 13:27:16 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Mpierce1@aol.com
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Moving forward: draft-carlberg-ets-*.txt
In-reply-to: Your message of "Tue, 05 Nov 2002 17:14:40 EST." <8c.20aa6c7e.2af99cd0@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 08 Nov 2002 13:27:14 +0000
Message-ID: <859.1036762034@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> 1.1 Reference should be T1.631 (not 693). 

yes.  it will be changed.

> 3. Since the title and purpose of this document is to address the 
> requirements for "IP-telephony", it should address the requirements 
> for end-to-end provision of a telephony service. Therefore, the statement 
> that "the following requirements explicitly do not relate to IP-layer 
> mechanisms" should be removed. 

actually, the term end-to-end generally relates to layer 4 and up.
we took the approach that IP telephony is simply an application and
one can isolate requirements accordingly.

> In fact, it should not state requirements
> for the non-IP protocols (SS7, DSS1), since the IETF has no control of 
> those protocols. It should refer to what non-IP protocols do, and state
>  the requirements for what the IP-protocols must do and how they must 
> interwork. 

yes, agreed.  references to non-IP protocols will be removed.

> 1) IP signaling (SIP) MUST be able to carry labels. 

if this is a suggested change for 

     1) Telephony signalling applications used with Internet-based
     telephony MUST be able to carry labels.

then i would prefer not to change the wording.  even with the enclosure
of the term SIP, the wording of "IP signaling" is too closely linked
with RSVP.  further, i don't see the gain in changing the original
wording.

> [MAP] There has been discussion the past 6 weeks on several issues, some 
> prompted by my initial set of comments on Sept 18. I was waiting for an 
> update to be posted by the author to see how he had dealt with the results
> of those discusions. There was a significant discussion on "Policy vs 
> labels" begun by a comment on these drafts, but I don't know if there is
> a satisfactory resulution in the text. 

the section on the separation of "policy & labels" will be expanded to
provide more clarity.

> It may be that these should move forward as WG drafts, but it's hard to
> say when we haven't seen the -01 version after all the discussion. 

understood.  i believe one of the things Ran was alluding to was
whether the approach taken by us is acceptable to the group and
should be migrated to official working group documents.  this is
with the understanding that comments and clarifications will be made
to the next version of the document.

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 09:45:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20151
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 09:45:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8ElKk30415
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 09:47:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8ElKv30412
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 09:47:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20145
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 09:44:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8EkGv30355;
	Fri, 8 Nov 2002 09:46:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Ejqv30334
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 09:45:52 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20104
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 09:43:16 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id EA0AF67103; Fri,  8 Nov 2002 06:06:52 -0500 (EST)
Date: Fri, 8 Nov 2002 09:45:45 -0500
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework  -02.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: "Nguyen, An" <nguyena@ncs.gov>, ieprep@ietf.org
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211080014490.5579-100000@paixhost.pch.net>
Message-Id: <C363218C-F328-11D6-BC9C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 03:26 America/Montreal, Bill Woodcock wrote:
>       On Wed, 6 Nov 2002, Nguyen, An wrote:
>> As of now there are no automated ways of increasing bandwidth to 
>> combat
>> congestions. But capabilities to do it might be available later.
>
> This has been tried in the past, but with limited success...  The 
> problem
> is that there is a high cost in the capacity of the local loop and CPE,
> and even if all of the upgrade procedure can be automated, no customer
> will willingly pay for the unused capacity of the headroom in the local
> loop.

The exception to this is when one has fibre-to-the-{home,office}.
I'm aware of MAN operators in a few parts of the US, many parts
of Sweden, and many parts of Japan, who are using GigE as the
last mile.  The operator purchases equipment capable of performing
traffic shaping on the GigE interface that connects to the customer,
then sells "bandwidth on demand".  The customer can increase the
provisioned capacity up to the physical limit via a web page
(and is billed for the time * provisioned-capacity).

Obviously there is a cap at the max deployed link bandwidth,
but deploying GigE is not a lot more expensive than 100 Mbps
Ethernet once the fibre is in place.  Right now, 10 GigE is
a whole lot more expensive than GigE (mainly due to cost of
optical components), but even that should improve with time.

FTTH/FTTO is not that common in the US today.  It is not uncommon
in some other countries.  It is very uncommon in most countries.
So it is not a general solution to the issue, but rather an
interesting special case.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 10:52:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24246
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 10:52:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8FsSu05263
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 10:54:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8FsSv05260
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 10:54:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24223
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 10:51:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8FrRv05156;
	Fri, 8 Nov 2002 10:53:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Fqbv05068
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 10:52:37 -0500
Received: from mail3.mx.voyager.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24029
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 10:50:04 -0500 (EST)
Received: from mail.delta-info.com (clyde.delta-info.com [146.145.21.34])
	by mail3.mx.voyager.net (8.11.6/8.10.2) with ESMTP id gA8FqWf31155
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 10:52:32 -0500 (EST)
Received: from ([])
        by mail.delta-info.com (Merak 4.00.100) with SMTP id DVB36921;
        Fri, 08 Nov 2002 10:40:15 -0500
Reply-To: <gthom@delta-info.com>
From: "Gary Thom" <gthom@delta-info.com>
To: "Bill Woodcock" <woody@pch.net>, <Mpierce1@aol.com>
Cc: <ieprep@ietf.org>
Subject: RE: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Date: Fri, 8 Nov 2002 10:52:43 -0500
Message-ID: <NDBBKMIGCLLNAOGKKDDPOEGEDDAA.gthom@delta-info.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <Pine.GSO.4.44.0211071114260.21181-100000@paixhost.pch.net>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> .... That appears to me to be the
> work of this working group: to try to understand what the DoD's perceived
> needs are, and try to intepret them in some sort of actual quantitative
> way that can be evaluated, and perhaps passed along for consideration to
> specific protocol working groups if they're worthy of the attention of
> those bodies.

If you understand this, then why do we continue to have these same inane
discussions, instead of discussing the technical issues and passing along
the needs to the other WGs???

Also, realize that Hal's work is not specifically DoD centric, but will be
used to support federal, state and local emergency management personnel,
police, fire and medical personnel who are trying to communicate in
emergency situations.

Speaking for MYSELF, if the world begins to use IP transport for public
telephony, I (personnally) think it would be important to support priority
access to the system for emergency communications. That way, when the Ivory
Tower begins to crumble, emergency personnel can coordinate rescue efforts
inspite of our continuing waste of bandwidth on this circular, sandbagging
trivia.

Gary Thom
Speaking on behalf of and for myself.

 --------------------------------------------
 Name   : Gary A. Thom
 Company: Delta Information Systems, Inc.
 Address: 300 Welsh Rd., Bldg 3
          Horsham, PA 19044 USA
 Phone  : +1-215-657-5270 x123
 Fax    : +1-215-657-5273
 E-mail : gthom@delta-info.com
 Website: www.delta-info.com
--------------------------------------------


> -----Original Message-----
> From: ieprep-admin@ietf.org [mailto:ieprep-admin@ietf.org]On Behalf Of
> Bill Woodcock
> Sent: Thursday, November 07, 2002 2:25 PM
> To: Mpierce1@aol.com
> Cc: ieprep@ietf.org
> Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 -
> discussion request]
>
>
>       On Thu, 7 Nov 2002 Mpierce1@aol.com wrote:
>     > ...the Defense Department (who I am being paid to attend
> the IETF) wants:
>     > [MAP] I'm getting very mixed messages. When I say what I
> think is required,
>
> No, it's us who are getting mixed messages.  You've repeated many times
> that you're representing DoD interests and positions.  We've said that we
> recognize that, and that that's not acceptable within the standards of
> intellectual integrity which we hold ourselves to.  Now you're complaining
> that we're treating you as though you're not speaking for yourself.
>
> If you are indeed representing a position of the DoD, we can relate to
> that, and deal with it accordingly.  The IETF reacts to outside events
> continuously; events of political as well as technological nature.
>
> If, on the other hand, you're representing yourself, and not the DoD,
> you're very welcome to participate within the IETF process, including
> other working groups like DIFFSERV and SIPPING.
>
> However if you masquerade as an individual, and try to take DoD interests
> before those working groups directly, they'll toss you out on your ear
> again.
>
>
>                                 -Bill
>
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 11:13:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25139
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 11:13:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8GF6F06986
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 11:15:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8GF6v06983
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 11:15:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25097
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 11:12:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8GE2v06940;
	Fri, 8 Nov 2002 11:14:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8GCsv06852
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 11:12:54 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24995
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 11:10:20 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Fri, 8 Nov 2002 11:12:29 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002110811123432233
 ; Fri, 08 Nov 2002 11:12:34 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMF753LQ>; Fri, 8 Nov 2002 11:12:21 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77921@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "Ieprep (E-mail)" <ieprep@ietf.org>
Cc: "'Scott Bradner ' (E-mail)" <sob@harvard.edu>
Date: Fri, 8 Nov 2002 11:12:32 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Ieprep] Atlanta ieprep Agenda
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

The ieprep WG is scheduled to meet Monday, November 18 from 1530-1730.  

Proposed ieprep Agenda

agenda bashing                                           5 minutes
Chairs

The ISP backbone of today		 		20 minutes
Discussion on deployed networks followed by question/answer period. 
Ran Atkinson

draft-ietf-ieprep-sip-reqs-01.txt		  	25 minutes
Document is in WG last-call.  The WG should discuss any remaining issues.
Henning Schulzrinne

draft-ietf-ieprep-requirements-01.txt		25 minutes
Requirements will be discussed one by one. 
Hal Folts

draft-ietf-ieprep-framework-02.txt			10 minutes      
Clarification on any outstanding issues.
Ken Carlberg

Accounting		   	             			10 minutes
Should Accounting be an ieprep requirement?
Mike Pierce 

draft-polk-ieprep-scenarios-01.txt 	 		5 minutes
Document is in WG last-call. The WG should discuss any remaining issues.
James Polk

Total								100 minutes

It is assumed that the WG has read the documents in preparation for the
meeting.  
 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 12:37:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01073
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 12:37:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8Hdu514279
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 12:39:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Hduv14276
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 12:39:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01037
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 12:37:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8HdAv14237;
	Fri, 8 Nov 2002 12:39:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Hc7v14175
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 12:38:07 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA00874
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 12:35:30 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 8 Nov 2002 17:35:42 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WM4K1V9S>; Fri, 8 Nov 2002 12:22:53 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D06@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Gary Thom '" <gthom@delta-info.com>
Cc: "'ieprep@ietf.org '" <ieprep@ietf.org>
Subject: RE: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
	 request]
Date: Fri, 8 Nov 2002 12:21:40 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1252"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Gary,

I totally agree with you on this ...

An


Also, realize that Hal's work is not specifically DoD centric, but will
be
used to support federal, state and local emergency management personnel,
police, fire and medical personnel who are trying to communicate in
emergency situations.

Speaking for MYSELF, if the world begins to use IP transport for public
telephony, I (personnally) think it would be important to support
priority
access to the system for emergency communications. That way, when the
Ivory
Tower begins to crumble, emergency personnel can coordinate rescue
efforts
inspite of our continuing waste of bandwidth on this circular,
sandbagging
trivia.

Gary Thom
Speaking on behalf of and for myself.

 --------------------------------------------
 Name   : Gary A. Thom
 Company: Delta Information Systems, Inc.
 Address: 300 Welsh Rd., Bldg 3
          Horsham, PA 19044 USA
 Phone  : +1-215-657-5270 x123
 Fax    : +1-215-657-5273
 E-mail : gthom@delta-info.com
 Website: www.delta-info.com
--------------------------------------------
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 13:46:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07288
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 13:46:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8Imnk20574
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 13:48:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Imnv20571
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 13:48:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07185
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 13:46:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Im4v20487;
	Fri, 8 Nov 2002 13:48:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8IlYv20445
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 13:47:34 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07054;
	Fri, 8 Nov 2002 13:44:59 -0500 (EST)
Message-Id: <200211081844.NAA07054@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ieprep@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 08 Nov 2002 13:44:58 -0500
Subject: [Ieprep] I-D ACTION:draft-ietf-ieprep-reflexive-dscp-01.txt
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Emergency Preparedness Working Group of the IETF.

	Title		: Reflexive DSCP Policy
	Author(s)	: R. Atarashi, F. Baker
	Filename	: draft-ietf-ieprep-reflexive-dscp-01.txt
	Pages		: 9
	Date		: 2002-11-8
	
In reviewing the specific use of the Differentiated Services
Architecture for supporting the Internet Emergency Preparedness
System, we found what we believe is a general issue.  This is that
even though a client or peer can connect to a server or peer with a
predictable DSCP value, the response does not have a predictable DSCP
value.  We consider the issues, and recommend an approach to
application policy regarding the DSCP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ieprep-reflexive-dscp-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ieprep-reflexive-dscp-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ieprep-reflexive-dscp-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-11-8140046.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ieprep-reflexive-dscp-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ieprep-reflexive-dscp-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-11-8140046.I-D@ietf.org>

--OtherAccess--

--NextPart--


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 14:19:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09134
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 14:19:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8JLDv23117
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 14:21:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8JLDv23114
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 14:21:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09107
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 14:18:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8JKHv23067;
	Fri, 8 Nov 2002 14:20:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8JJBv22959
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 14:19:11 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09021
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 14:16:34 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id B131267103; Fri,  8 Nov 2002 10:40:11 -0500 (EST)
Date: Fri, 8 Nov 2002 14:19:02 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: "Ieprep (E-mail)" <ieprep@ietf.org>,
        "'Scott Bradner ' (E-mail)" <sob@harvard.edu>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77921@mcl-its-exs01>
Message-Id: <F0E12BAE-F34E-11D6-BC9C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 11:12 America/Montreal, King, Kimberly S. 
wrote:
> draft-ietf-ieprep-requirements-01.txt		25 minutes
> Requirements will be discussed one by one.
> Hal Folts

Seems to me like there needs to be a major document spin, based on 
existing
list feedback, before we waste another 25 minutes discussing an old 
document
that clearly needs a major editing pass before it goes anyplace.  And I 
do
NOT plan to repeat all my comments to date at the meeting (sound of 
cheers
in the background) because I expect them to be <#include list-feedback>
included by reference.

> draft-ietf-ieprep-framework-02.txt			10 minutes
> Clarification on any outstanding issues.
> Ken Carlberg

Not keen about discussing this absent a document spin either,
since it also quite clearly needs major editing, but at least
we will only waste 10 minutes not 25.

> Accounting		   	             			10 minutes
> Should Accounting be an ieprep requirement?
> Mike Pierce
>
> draft-polk-ieprep-scenarios-01.txt 	 		5 minutes
> Document is in WG last-call. The WG should discuss any remaining 
> issues.
> James Polk

Those seem reasonable.  It will probably help focus things a whole lot
if "accounting" is replaced by a much more precise term/definition.
Adding accounting to the overall Internet Architecture would represent
a huge change to the architecture so seems like a very bad idea.  I
hope/suspect something else is being proposed.  Clarity in what is
meant/intended/sought would be good.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 14:20:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09202
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 14:20:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8JMpg23228
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 14:22:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8JMpv23225
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 14:22:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09172
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 14:20:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8JM1v23160;
	Fri, 8 Nov 2002 14:22:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8JLRv23138
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 14:21:27 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09125
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 14:18:51 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 7512767103; Fri,  8 Nov 2002 10:42:30 -0500 (EST)
Date: Fri, 8 Nov 2002 14:21:21 -0500
Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: <gthom@delta-info.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPOEGEDDAA.gthom@delta-info.com>
Message-Id: <4386C35D-F34F-11D6-BC9C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 10:52 America/Montreal, Gary Thom wrote:
> Also, realize that Hal's work is not specifically DoD centric,

NCS is part of DoD (until reorg'd into DHS).
By its very definition it is DoD-centric.

Further, it is tremendously US-centric (e.g. compare with Japan,
where ISPs have done zero/zip/nothing to support IAA because the
Japanese Govt adapted the IAA activity to the Internet -- rather than
trying to make the Internet look like the PSTN).

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 15:03:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11278
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 15:03:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8K5vF25512
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 15:05:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8K5vv25509
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 15:05:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11249
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 15:03:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8K58v25464;
	Fri, 8 Nov 2002 15:05:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8K4bv25425
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 15:04:37 -0500
Received: from mail0.mx.voyager.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11191
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 15:02:00 -0500 (EST)
Received: from mail.delta-info.com (clyde.delta-info.com [146.145.21.34])
	by mail0.mx.voyager.net (8.11.6/8.10.2) with ESMTP id gA8K4Uq04074
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 15:04:30 -0500 (EST)
Received: from s15 ([])
        by mail.delta-info.com (Merak 4.00.100) with SMTP id DVB36921
        for <ieprep@ietf.org>; Fri, 08 Nov 2002 14:52:12 -0500
Reply-To: <gthom@delta-info.com>
From: "Gary Thom" <gthom@delta-info.com>
To: <ieprep@ietf.org>
Subject: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Date: Fri, 8 Nov 2002 15:04:43 -0500
Message-ID: <NDBBKMIGCLLNAOGKKDDPIEGIDDAA.gthom@delta-info.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: Gary Thom [mailto:gthom@delta-info.com]
> Sent: Friday, November 08, 2002 3:03 PM
> To: RJ Atkinson
> Subject: RE: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 -
> discussion request]
> 
> 
> Incorrect. NCS is an executive branch organization that sits 
> between the DOD and other federal agencies(including FEMA). They 
> are not a part of DISA and not a part of DoD. They do have 
> resposonsibility for coordinating communications between the DoD 
> and these other federal agencies, and state and local agencies. 
> You are correct though, it will be reorged into DHS.
> 
> The goal is not to make the internet to look like the PSTN. The 
> goal is to provide high probability of call completion in 
> telephone (IP OR Circuit switched) systems. It does not need to 
> be done the same way it is done in the PSTN.
> 
> Many people have these grand ideas that this will be used on the 
> "Public Internet". I personnally think it is more important and 
> more practical to consider this capability for use on IP networks 
> which are used to provide telephony services. These networks 
> generally interconnect with the PSTN because they are providing 
> public telephone services. My focus is on that application, but 
> like I said, others think it should extend to the public internet 
> and include priority for email, chat, etc. I beleive that this is 
> impractical and that the public internet can be used as in on a 
> best effort basis. But the IP and PSTN are different, and a lot 
> of good can come from being able to provide priority service for 
> disaster recovery.
> 
> The Japanese IAA is a different type of service, and is not 
> conversational, so the Internet may provide sufficient capability 
> without change.
> 
> As far as being US centric, maybe it is, but it is a good idea, 
> that will provide world wide benefit, and in fact, mast disaster 
> recovery operations are being supported internationally 
> (principally involving the US and a few western european 
> partners), and the ITU has acknowlegde the benefit of providing 
> international priority communications to support there global 
> efforts. So the fact that this is being driven by the US, does 
> not mean it only has a US benefit.
> 
> Again, my focus is on public telephony. I agree that there may be 
> some who are streaching this to other iP applications, and I 
> think they are misguided. However, this WG is focused on SIP 
> which does address telepony, so I think we should find a way to 
> develop this work in a technically efficient manner.
> 
> 
> Thanks
> Gary
> 
>  --------------------------------------------
>  Name   : Gary A. Thom
>  Company: Delta Information Systems, Inc.
>  Address: 300 Welsh Rd., Bldg 3
>           Horsham, PA 19044 USA
>  Phone  : +1-215-657-5270 x123
>  Fax    : +1-215-657-5273
>  E-mail : gthom@delta-info.com
>  Website: www.delta-info.com
> --------------------------------------------
>  
> 
> > -----Original Message-----
> > From: RJ Atkinson [mailto:rja@extremenetworks.com]
> > Sent: Friday, November 08, 2002 2:21 PM
> > To: gthom@delta-info.com
> > Cc: ieprep@ietf.org
> > Subject: Re: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 -
> > discussion request]
> > 
> > 
> > 
> > On Friday, Nov 8, 2002, at 10:52 America/Montreal, Gary Thom wrote:
> > > Also, realize that Hal's work is not specifically DoD centric,
> > 
> > NCS is part of DoD (until reorg'd into DHS).
> > By its very definition it is DoD-centric.
> > 
> > Further, it is tremendously US-centric (e.g. compare with Japan,
> > where ISPs have done zero/zip/nothing to support IAA because the
> > Japanese Govt adapted the IAA activity to the Internet -- rather than
> > trying to make the Internet look like the PSTN).
> > 
> > Ran
> > 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 15:22:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12235
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 15:22:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8KOnG26912
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 15:24:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8KOnv26909
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 15:24:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12193
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 15:22:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8KO7v26896;
	Fri, 8 Nov 2002 15:24:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8KNwv26878
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 15:23:58 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12164
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 15:21:21 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA8KHvd17058;
	Fri, 8 Nov 2002 12:17:57 -0800 (PST)
Date: Fri, 8 Nov 2002 12:17:57 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Gary Thom <gthom@delta-info.com>
cc: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPIEGIDDAA.gthom@delta-info.com>
Message-ID: <Pine.GSO.4.44.0211081216250.15290-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > The goal is to provide high probability of call completion in
    > telephone (IP) systems.

I missed the part in which someone presented some evidence to support your
misassumption that this goal hasn't been met.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 15:44:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13115
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 15:44:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8Kl0C28137
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 15:47:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Kl0v28134
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 15:47:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13066
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 15:44:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Kk9v28102;
	Fri, 8 Nov 2002 15:46:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Kjnv28067
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 15:45:49 -0500
Received: from mail0.mx.voyager.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13019
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 15:43:11 -0500 (EST)
Received: from mail.delta-info.com (clyde.delta-info.com [146.145.21.34])
	by mail0.mx.voyager.net (8.11.6/8.10.2) with ESMTP id gA8Kjgx43991
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 15:45:42 -0500 (EST)
Received: from s15 ([])
        by mail.delta-info.com (Merak 4.00.100) with SMTP id DVB36921;
        Fri, 08 Nov 2002 15:33:23 -0500
Reply-To: <gthom@delta-info.com>
From: "Gary Thom" <gthom@delta-info.com>
To: "Bill Woodcock" <woody@pch.net>
Cc: <ieprep@ietf.org>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Date: Fri, 8 Nov 2002 15:45:54 -0500
Message-ID: <NDBBKMIGCLLNAOGKKDDPCEGKDDAA.gthom@delta-info.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <Pine.GSO.4.44.0211081216250.15290-100000@paixhost.pch.net>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>
>     > The goal is to provide high probability of call completion in
>     > telephone (IP) systems.
>
> I missed the part in which someone presented some evidence to support your
> misassumption that this goal hasn't been met.
>

If it has been met, a simple statement of this capability will eliminate a
lot of continuing aggravation.

As I said before, there are two issues:

The first is whether the network (and associated elements such as routers
and switches) can provide priority transport of packets associated with an
emergency call. I am not qualified to address this, so I defer to others as
to whether this is a problem or not, but certainly there is a desire to give
some preferencial treatment to those packets in the event of congestion or
degrated operation.

The second is whether the telephony elements (such as SIP proxy servers,
redirect servers, etc) are informed that a particular call is an emergency
call so that those elements can take action to improve the proboability of
call completion. For example, to loosen addmission policy to allow an
emergency call even though other addmission criteria may not be satisfied.
The actual action to be taken is certainly a local matter and not subject to
standardization, however, the signalling within the protocol to indicate an
emergency call should be done in a standardized way. At least this part
should be communicated with the proper WG in order to enhance the SIP
protocol.

gary

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 16:16:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15123
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 16:16:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8LIAm30687
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 16:18:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LIAv30684
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 16:18:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15090
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 16:15:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LHAv30628;
	Fri, 8 Nov 2002 16:17:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LGEv30598
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 16:16:14 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15006
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 16:13:38 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 2C37D67103; Fri,  8 Nov 2002 12:37:16 -0500 (EST)
Date: Fri, 8 Nov 2002 16:16:06 -0500
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: "Bill Woodcock" <woody@pch.net>, <ieprep@ietf.org>
To: <gthom@delta-info.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPCEGKDDAA.gthom@delta-info.com>
Message-Id: <4B5B4DB3-F35F-11D6-BC9C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 15:45 America/Montreal, Gary Thom wrote:
> The first is whether the network (and associated elements such as 
> routers
> and switches) can provide priority transport of packets associated 
> with an
> emergency call. I am not qualified to address this, so I defer to 
> others as
> to whether this is a problem or not, but certainly there is a desire 
> to give
> some preferencial treatment to those packets in the event of 
> congestion or
> degrated operation.

They don't need priority transport.  Enough of them do need to get
through that the vocoder algorithm in use can maintain sync and
that the user can understand the converation.

Bill's VoIP network is pretty large.  He has consistently reported
that he isn't having problems -- with no special treatment needed.
I don't know what vocoder algorithm he's using and my own prior
life experience indicates that probably matters.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 16:19:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15342
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 16:19:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8LLgI30924
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 16:21:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LLgv30921
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 16:21:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15292
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 16:19:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LK1v30831;
	Fri, 8 Nov 2002 16:20:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LJKv30786
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 16:19:20 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15169
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 16:16:44 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 6458B67103; Fri,  8 Nov 2002 12:40:16 -0500 (EST)
Date: Fri, 8 Nov 2002 16:19:05 -0500
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: <gthom@delta-info.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPIEGIDDAA.gthom@delta-info.com>
Message-Id: <B5E4B033-F35F-11D6-BC9C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 15:04 America/Montreal, Gary Thom wrote:
>> Incorrect. NCS is an executive branch organization that sits
>> between the DOD and other federal agencies(including FEMA). They
>> are not a part of DISA and not a part of DoD.

The Director of DISA is now (and always has been since at least
the founding of DCA, which is the old name for DISA) concurrently
the Director of NCS.  NCS is run functionally as a component
of NCS, just as WHCA has been run functionally as a component of
DISA.  Bottom line is that NCS is part of DoD for all intents
and purposes here.

It does appear that NCS will be re-homed by Congress into DHS,
but that hasn't happened yet according to The Washington Post,
so my statement stands as originally made.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 16:28:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15702
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 16:28:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8LUmu31441
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 16:30:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LUmv31438
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 16:30:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15685
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 16:28:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LTAv31336;
	Fri, 8 Nov 2002 16:29:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LS8v31298
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 16:28:08 -0500
Received: from mail2.mx.voyager.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15577
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 16:25:32 -0500 (EST)
Received: from mail.delta-info.com (clyde.delta-info.com [146.145.21.34])
	by mail2.mx.voyager.net (8.11.6/8.10.2) with ESMTP id gA8LS0j42303
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 16:28:01 -0500 (EST)
Received: from s15 ([])
        by mail.delta-info.com (Merak 4.00.100) with SMTP id DVB36921;
        Fri, 08 Nov 2002 16:15:42 -0500
Reply-To: <gthom@delta-info.com>
From: "Gary Thom" <gthom@delta-info.com>
To: "RJ Atkinson" <rja@extremenetworks.com>
Cc: "Bill Woodcock" <woody@pch.net>, <ieprep@ietf.org>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Date: Fri, 8 Nov 2002 16:28:13 -0500
Message-ID: <NDBBKMIGCLLNAOGKKDDPAEGMDDAA.gthom@delta-info.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <4B5B4DB3-F35F-11D6-BC9C-00039357A82A@extremenetworks.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ran,

Thanks for your reply.

One thing to remember, is that we are really looking at operating under
non-normal conditions. This may be due to an unusually high load or with
degraded capability. During an emergency, such as a huricane or earthquake,
not only will you have everyone trying to find out if their loved ones are
ok, but you may have loss of bandwidth or or other error conditions due to
damaged equipment, fiber, etc. In this situation, we want to give emergency
communications an advantage.

gary

>
> On Friday, Nov 8, 2002, at 15:45 America/Montreal, Gary Thom wrote:
> > The first is whether the network (and associated elements such as
> > routers
> > and switches) can provide priority transport of packets associated
> > with an
> > emergency call. I am not qualified to address this, so I defer to
> > others as
> > to whether this is a problem or not, but certainly there is a desire
> > to give
> > some preferencial treatment to those packets in the event of
> > congestion or
> > degrated operation.
>
> They don't need priority transport.  Enough of them do need to get
> through that the vocoder algorithm in use can maintain sync and
> that the user can understand the converation.
>
> Bill's VoIP network is pretty large.  He has consistently reported
> that he isn't having problems -- with no special treatment needed.
> I don't know what vocoder algorithm he's using and my own prior
> life experience indicates that probably matters.
>
> Ran
> rja@extremenetworks.com
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 16:37:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16293
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 16:37:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8LdJU00316
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 16:39:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LdJv00311
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 16:39:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16266
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 16:36:42 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Lc5v32683;
	Fri, 8 Nov 2002 16:38:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LbHv32521
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 16:37:17 -0500
Received: from imo-r02.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16119
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 16:34:41 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r02.mx.aol.com (mail_out_v34.13.) id c.17b.113bc8f1 (4262);
	Fri, 8 Nov 2002 16:36:57 -0500 (EST)
Message-ID: <17b.113bc8f1.2afd8879@aol.com>
Date: Fri, 8 Nov 2002 16:36:57 EST
Subject: Re: [Ieprep] WG last call for IEPREP Topology Scenarios
To: jmpolk@cisco.com, KIMBERLY.S.KING@saic.com, ieprep@ietf.org
CC: mankin@psg.com, sob@harvard.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_17b.113bc8f1.2afd8879_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_17b.113bc8f1.2afd8879_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/7/2002 3:18:53 PM Eastern Standard Time, 
jmpolk@cisco.com writes:


> >
> > 2.2 The statement about "One key espect ..." concerning prioritization 
> should
> > apply to all four scenarios. This becomes one of the important discussion
> > points for all four scenarios (beginning with "is it needed?"). 
> 
> 
> The intent here is to directly address a list concern/discussion regarding
> whether or not the IP portion (at the GW) of this Topology is ETS aware, and
> whether there was one or two authentication mechanisms used (with the latter
> likely requiring different user behavior if they are on an IP phone vs. a 
> CSN
> phone).
> 
> Should the paragraph after Figure 2 be removed (and likely included within 
> the
> Topology Implications ID that's coming)?
> 

I would say that the definition of scenarios should be agnostic to any 
specific issues that might be discussed later based on those scenarios. I 
think we have different ideas of whether or not the IP portion needs to be 
"ETS aware" or it could change between now a several years from now.

Mike Pierce


--part1_17b.113bc8f1.2afd8879_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/7/2002 3:18:53 PM Eastern Standard Time, jmpolk@cisco.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt;
<BR>&gt; 2.2 The statement about "One key espect ..." concerning prioritization should
<BR>&gt; apply to all four scenarios. This becomes one of the important discussion
<BR>&gt; points for all four scenarios (beginning with "is it needed?"). 
<BR>
<BR>
<BR>The intent here is to directly address a list concern/discussion regarding
<BR>whether or not the IP portion (at the GW) of this Topology is ETS aware, and
<BR>whether there was one or two authentication mechanisms used (with the latter
<BR>likely requiring different user behavior if they are on an IP phone vs. a CSN
<BR>phone).
<BR>
<BR>Should the paragraph after Figure 2 be removed (and likely included within the
<BR>Topology Implications ID that's coming)?
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>I would say that the definition of scenarios should be agnostic to any specific issues that might be discussed later based on those scenarios. I think we have different ideas of whether or not the IP portion needs to be "ETS aware" or it could change between now a several years from now.
<BR>
<BR>Mike Pierce
<BR></FONT></HTML>

--part1_17b.113bc8f1.2afd8879_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 16:56:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17749
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 16:56:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8LwWS01787
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 16:58:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8LwWv01784
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 16:58:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17710
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 16:55:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Lv9v01707;
	Fri, 8 Nov 2002 16:57:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Lu2v01659
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 16:56:02 -0500
Received: from wells.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17475
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 16:53:25 -0500 (EST)
Received: from JMPOLK-W2K (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id NAA10921; Fri, 8 Nov 2002 13:55:51 -0800 (PST)
Message-Id: <4.1.20021108155456.0159df10@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Fri, 08 Nov 2002 15:55:47 -0600
To: Mpierce1@aol.com, KIMBERLY.S.KING@saic.com, ieprep@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Ieprep] WG last call for IEPREP Topology Scenarios
Cc: mankin@psg.com, sob@harvard.edu
In-Reply-To: <17b.113bc8f1.2afd8879@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

At 04:36 PM 11/8/2002 -0500, Mpierce1@aol.com wrote: 
>
> In a message dated 11/7/2002 3:18:53 PM Eastern Standard Time,
> jmpolk@cisco.com writes: 
>
>
>>
>> > 
>> > 2.2 The statement about "One key espect ..." concerning prioritization
>> should 
>> > apply to all four scenarios. This becomes one of the important discussion 
>> > points for all four scenarios (beginning with "is it needed?"). 
>>
>>
>> The intent here is to directly address a list concern/discussion regarding 
>> whether or not the IP portion (at the GW) of this Topology is ETS aware, and
>>
>> whether there was one or two authentication mechanisms used (with the latter
>>
>> likely requiring different user behavior if they are on an IP phone vs. a
>> CSN 
>> phone). 
>>
>> Should the paragraph after Figure 2 be removed (and likely included within
>> the 
>> Topology Implications ID that's coming)? 
>
>
>
> I would say that the definition of scenarios should be agnostic to any
> specific issues that might be discussed later based on those scenarios. I
> think we have different ideas of whether or not the IP portion needs to be
> "ETS aware" or it could change between now a several years from now. 


Fair statement. Anyone else care to comment on this point?


>
> Mike Pierce 




cheers,
James 

              *************************************
"People generally demand more respect for their own rights than 
                         they are willing to allow for others"


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 17:25:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19376
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 17:25:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8MR8U04369
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 17:27:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MR8v04366
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 17:27:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19368
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 17:24:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MQ7v04297;
	Fri, 8 Nov 2002 17:26:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MPtv04245
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 17:25:55 -0500
Received: from imo-m04.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19309
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 17:23:19 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m04.mx.aol.com (mail_out_v34.13.) id j.73.28cb9c71 (4262);
	Fri, 8 Nov 2002 17:25:41 -0500 (EST)
Message-ID: <73.28cb9c71.2afd93e4@aol.com>
Date: Fri, 8 Nov 2002 17:25:40 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: rja@extremenetworks.com, KIMBERLY.S.KING@saic.com
CC: ieprep@ietf.org, sob@harvard.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_73.28cb9c71.2afd93e4_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_73.28cb9c71.2afd93e4_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/8/2002 2:21:13 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> Those seem reasonable.  It will probably help focus things a whole lot
> if "accounting" is replaced by a much more precise term/definition.
> Adding accounting to the overall Internet Architecture would represent
> a huge change to the architecture so seems like a very bad idea.  I
> hope/suspect something else is being proposed.  Clarity in what is
> meant/intended/sought would be good.
> 


Please see draft-ietf-sipping-aaa-req-01.txt and the charter of the AAA WG. 
The term "accounting" is the accepted one for what we are talking about.

Mike Pierce



--part1_73.28cb9c71.2afd93e4_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/8/2002 2:21:13 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Those seem reasonable. &nbsp;It will probably help focus things a whole lot
<BR>if "accounting" is replaced by a much more precise term/definition.
<BR>Adding accounting to the overall Internet Architecture would represent
<BR>a huge change to the architecture so seems like a very bad idea. &nbsp;I
<BR>hope/suspect something else is being proposed. &nbsp;Clarity in what is
<BR>meant/intended/sought would be good.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>Please see draft-ietf-sipping-aaa-req-01.txt and the charter of the AAA WG. The term "accounting" is the accepted one for what we are talking about.
<BR>
<BR>Mike Pierce
<BR>
<BR></FONT></HTML>

--part1_73.28cb9c71.2afd93e4_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 17:25:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19395
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 17:25:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8MRLF04384
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 17:27:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MRLv04381
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 17:27:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19372
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 17:24:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MQ4v04265;
	Fri, 8 Nov 2002 17:26:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MPnv04236
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 17:25:49 -0500
Received: from imo-m04.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19293
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 17:23:12 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m04.mx.aol.com (mail_out_v34.13.) id c.a3.31e3b405 (4262);
	Fri, 8 Nov 2002 17:25:39 -0500 (EST)
Message-ID: <a3.31e3b405.2afd93e3@aol.com>
Date: Fri, 8 Nov 2002 17:25:39 EST
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
To: gthom@delta-info.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_a3.31e3b405.2afd93e3_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_a3.31e3b405.2afd93e3_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/8/2002 3:06:21 PM Eastern Standard Time, 
gthom@delta-info.com writes:


> > Incorrect. NCS is an executive branch organization that sits 
> > between the DOD and other federal agencies(including FEMA). They 
> > are not a part of DISA and not a part of DoD.


Just a note. Last I understood, NCS was officially part of DoD, sort of for 
administrative purposes, I think, since everyone has to be someplace. But, as 
I noted before, their mission is very much different from DISA, which really 
is a part of DoD. (And as soon as the Republicans get control, NCS will be 
moved anyway.) Whether it is or is not a part of DoD today is not important. 
It functions as a separate agency (from DISA) under executive branch control. 

Mike Pierce



--part1_a3.31e3b405.2afd93e3_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/8/2002 3:06:21 PM Eastern Standard Time, gthom@delta-info.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt; Incorrect. NCS is an executive branch organization that sits 
<BR>&gt; between the DOD and other federal agencies(including FEMA). They 
<BR>&gt; are not a part of DISA and not a part of DoD.</FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>Just a note. Last I understood, NCS was officially part of DoD, sort of for administrative purposes, I think, since everyone has to be someplace. But, as I noted before, their mission is very much different from DISA, which really is a part of DoD. (And as soon as the Republicans get control, NCS will be moved anyway.) Whether it is or is not a part of DoD today is not important. It functions as a separate agency (from DISA) under executive branch control. 
<BR>
<BR>Mike Pierce
<BR>
<BR></FONT></HTML>

--part1_a3.31e3b405.2afd93e3_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 17:25:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19518
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 17:25:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8MRsA04416
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 17:27:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MRsv04413
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 17:27:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19411
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 17:25:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MR1v04338;
	Fri, 8 Nov 2002 17:27:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MQev04311
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 17:26:40 -0500
Received: from imo-m02.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19338
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 17:24:03 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m02.mx.aol.com (mail_out_v34.13.) id b.11a.19cf68e8 (4262);
	Fri, 8 Nov 2002 17:25:38 -0500 (EST)
Message-ID: <11a.19cf68e8.2afd93e1@aol.com>
Date: Fri, 8 Nov 2002 17:25:37 EST
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework  -02.txt
To: woody@pch.net, nguyena@ncs.gov
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_11a.19cf68e8.2afd93e1_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_11a.19cf68e8.2afd93e1_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/8/2002 3:36:55 AM Eastern Standard Time, woody@pch.net 
writes:


> This is quite true as well...  There's no argument over whether jitter
> exists in the network, just as there's no argument over whether congestion
> exists in the network.  What operators are telling you is that it's so
> far from being a problem as to be utterly unworth anyone's attention, much
> less that of smart people who could be using their intelligence to solve
> problems.
> 

And as Ran writes:
Bill's VoIP network is pretty large.  He has consistently reported
that he isn't having problems -- with no special treatment needed.

[MAP] I (and apparently others) are completely at a loss as to why you can't 
just accept the fact that some of us are not talking about a big, fat 
commercial network, with lots of excess bandwidth, always in a condition of 
no major failues or causes of totally unexpected traffic volumes. Your 
comments and arguments keep coming back to a situation of excess bandwidth 
always being available so there's no problem to solve.

The rest of us are not arguing that your case doesn't exist or that you can't 
choose to operate your network on that presumption. But you keep arguing that 
others can't operate their network the way they want to (like with barely 
enough bandwidth available on good days and a serious shortage on bad days).

Mike Pierce

--part1_11a.19cf68e8.2afd93e1_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/8/2002 3:36:55 AM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">This is quite true as well... &nbsp;There's no argument over whether jitter
<BR>exists in the network, just as there's no argument over whether congestion
<BR>exists in the network. &nbsp;What operators are telling you is that it's so
<BR>far from being a problem as to be utterly unworth anyone's attention, much
<BR>less that of smart people who could be using their intelligence to solve
<BR>problems.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>And as Ran writes:
<BR>Bill's VoIP network is pretty large. &nbsp;He has consistently reported
<BR>that he isn't having problems -- with no special treatment needed.
<BR>
<BR>[MAP] I (and apparently others) are completely at a loss as to why you can't just accept the fact that some of us are not talking about a big, fat commercial network, with lots of excess bandwidth, always in a condition of no major failues or causes of totally unexpected traffic volumes. Your comments and arguments keep coming back to a situation of excess bandwidth always being available so there's no problem to solve.
<BR>
<BR>The rest of us are not arguing that your case doesn't exist or that you can't choose to operate your network on that presumption. But you keep arguing that others can't operate their network the way they want to (like with barely enough bandwidth available on good days and a serious shortage on bad days).
<BR>
<BR>Mike Pierce</FONT></HTML>

--part1_11a.19cf68e8.2afd93e1_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 17:29:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19827
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 17:29:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8MW5404609
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 17:32:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MW5v04606
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 17:32:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19788
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 17:29:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MQ6v04281;
	Fri, 8 Nov 2002 17:26:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8MPpv04241
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 17:25:51 -0500
Received: from imo-r09.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19301
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 17:23:14 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r09.mx.aol.com (mail_out_v34.13.) id i.10f.19c7f7d2 (4262);
	Fri, 8 Nov 2002 17:25:36 -0500 (EST)
Message-ID: <10f.19c7f7d2.2afd93e0@aol.com>
Date: Fri, 8 Nov 2002 17:25:36 EST
Subject: Re: [Ieprep] Moving forward: draft-carlberg-ets-*.txt
To: K.Carlberg@cs.ucl.ac.uk
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_10f.19c7f7d2.2afd93e0_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_10f.19c7f7d2.2afd93e0_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/8/2002 8:27:47 AM Eastern Standard Time, 
K.Carlberg@cs.ucl.ac.uk writes:


> understood.  i believe one of the things Ran was alluding to was
> whether the approach taken by us is acceptable to the group and
> should be migrated to official working group documents.  this is
> with the understanding that comments and clarifications will be made
> to the next version of the document.
> 


It sounds like the approach is okay, but it is necesary to see -01 before one 
can say for sure about moving it to WG status.

Mike Pierce
Artel


--part1_10f.19c7f7d2.2afd93e0_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/8/2002 8:27:47 AM Eastern Standard Time, K.Carlberg@cs.ucl.ac.uk writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">understood. &nbsp;i believe one of the things Ran was alluding to was
<BR>whether the approach taken by us is acceptable to the group and
<BR>should be migrated to official working group documents. &nbsp;this is
<BR>with the understanding that comments and clarifications will be made
<BR>to the next version of the document.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>It sounds like the approach is okay, but it is necesary to see -01 before one can say for sure about moving it to WG status.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_10f.19c7f7d2.2afd93e0_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 20:14:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25333
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 20:14:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA91GQA14318
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 20:16:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91GQv14315
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 20:16:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25328
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 20:13:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91FBv14269;
	Fri, 8 Nov 2002 20:15:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91EAv14229
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 20:14:10 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25294
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 20:11:30 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 2E4606710D; Fri,  8 Nov 2002 16:35:11 -0500 (EST)
Date: Fri, 8 Nov 2002 20:13:58 -0500
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: "Bill Woodcock" <woody@pch.net>, <ieprep@ietf.org>
To: <gthom@delta-info.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPAEGMDDAA.gthom@delta-info.com>
Message-Id: <86164E3F-F380-11D6-8AB8-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 16:28 America/Montreal, Gary Thom wrote:
> One thing to remember, is that we are really looking at operating under
> non-normal conditions. This may be due to an unusually high load or 
> with
> degraded capability. During an emergency, such as a huricane or 
> earthquake,
> not only will you have everyone trying to find out if their loved ones 
> are
> ok, but you may have loss of bandwidth or or other error conditions 
> due to
> damaged equipment, fiber, etc. In this situation, we want to give 
> emergency
> communications an advantage.

Gary,

	Would you consider 9/11/2001 to be "non-normal conditions" ?
As someone with a number of friends who work daily in the Pentagon,
and several parish members who died that day, I'd say that day was
pretty unusual.

	During that day, a few content providers had problems delivering
all the requested content.  In at least some cases, this was server
overload.  However, careful analysis of traffic logs by large ISPs
afterwards confirms that the Internet performed brilliantly.  Despite
fibre cuts in lower Manhatten and numerous environmental problems at
Hudson Street, the Internet automatically re-routed around the damage
and kept going.  And the large ISPs did NOT (repeat did NOT) start
dropping packets because of the cut fibres -- their backbones were
carefully over-engineered so the traffic was re-routed around the
lost links.

	Access to the US NASA feeds of the mars lander landing was a bigger
problem in Internet terms, yet even then the problems were on NASA's
access links and its servers, rather than in any large ISPs network.

	To me, the key thing is that the critical traffic gets through.
Saying that it must be "prioritised" implies a specific mechanism for
prioritisation.  It is better for us to focus on the real requirement
of the traffic getting through, than on specific mechanisms (in your 
words,
prioritisation) which might not be (probably aren't) needed, create new 
attack
vectors on the ISP network, and increase operational complexity.   There
is a significant body of evidence that a better (and lower-cost) 
approach
is to over-engineer the network so that the network simply can handle 
all
the offered load.

	I spent a fair bit of time yesterday talking with folks from major
ISPs.  One is a large inter-continental ISP with POPs located in 
Asia/Pacific,
North America, and Europe.  Another is based in Japan.  (etc.).  In
each case, they indicated that their backbone links are significantly
overprovisioned (max load << (50% link capacity)).  A typical number 
that
was mentioned was that links have a "max load" equal to 30-35% of link 
capacity.
They also noted that they have significant path diversity in their 
networks,
specifically including physical fibre path diversity.  This was 
originally
done as defence against back-hoe equipment, but it happens to work 
really
well during other kinds of natural/unnatural problems as well.  To give
another example, there was a fibre cut near Baltimore a while back.  It
cut several fibre bundles from different carriers.  The IP routing 
system
just automatically detected the link-down state and routed around the 
cut links
-- and there was enough spare capacity in the other links that there 
was no 
significant loss of service.

	Claims of the form "the Internet gets congested and drops packets
when an emergency happens" currently lack credibility, because they are
contrary to the measured, scientific data that we happen to have.  I'd
be much more inclined to take those claims seriously if someone would 
show
up with specific measured data about an actual incident.  And in that 
case,
it would be important to have enough specifics to actually sit down and
analyse precisely what happened -- without a great deal of detail this 
WG
is unlikely to correctly and clearly characterise the issue so that 
another
IETF WG to figure out what the correct protocol change(s) might be or 
for ISPs
to figure out which existing mechanisms might be candidates for broader
deployment.

	It would also be helpful if going forward we could clearly separate our
sundry concerns into the different layers of the Internet Architecture 
(Physical,
Link, IP, Transport, Application).[1]

Ran
rja@extremenetworks.com

[1] The Internet Architecture is not identical to ISO OSI Model.  For 
example,
we have no Session Layer in the Internet.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 20:20:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25461
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 20:20:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA91MmL14588
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 20:22:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91Mmv14585
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 20:22:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25453
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 20:20:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91M1v14553;
	Fri, 8 Nov 2002 20:22:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91LIv14523
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 20:21:18 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25439
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 20:18:38 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 331C66710D; Fri,  8 Nov 2002 16:42:17 -0500 (EST)
Date: Fri, 8 Nov 2002 20:21:04 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <73.28cb9c71.2afd93e4@aol.com>
Message-Id: <8400E704-F381-11D6-8AB8-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 17:25 America/Montreal, Mpierce1@aol.com 
wrote:
> Please see draft-ietf-sipping-aaa-req-01.txt and the charter of the 
> AAA WG. The term "accounting" is the accepted one for what we are 
> talking about.

There are MANY different definitions for "accounting" in the IETF.
It would help further the discussion A Whole Lot if one were much
more clear about which (sub)set of those definitions is intended
by the proponent of the idea.

For example, packet accounting is an IP-layer function.  Voice Call
Accounting might be an application-layer function for a telephony
application.  In AAA, such as RADIUS/DIAMETER, accounting really means
creating log entries for which user logged into which server at which 
date/time,
for how long, on what port, from where, and so forth.  Each of those
is very substantially different from the other.  The implementation
code of these examples exists is in different layers and/or in different
applications.  Depending on the kind of packet accounting desired, there
might not even exist appropriate instrumentation in widespread 
implementations.
Also, the deployment cost and on-going operational burden of each of
these different kinds of "accounting" is quite different.

Absent additional clarification, I do not see why people here are likely
to avoid continuing to talk past each other on the topic rather than
communicate effectively.  Even if people disagree, it is pleasant
if they clearly and correctly understand what each other are saying.

Ran


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 20:27:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25569
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 20:27:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA91U0q14805
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 20:30:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91U0v14791
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 20:30:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25556
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 20:27:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91T2v14763;
	Fri, 8 Nov 2002 20:29:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91Scv14743
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 20:28:38 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25534
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 20:25:59 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id B63236710D; Fri,  8 Nov 2002 16:49:40 -0500 (EST)
Date: Fri, 8 Nov 2002 20:28:28 -0500
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: gthom@delta-info.com, ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <a3.31e3b405.2afd93e3@aol.com>
Message-Id: <8C72F176-F382-11D6-8AB8-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 17:25 America/Montreal, Mpierce1@aol.com 
wrote:
> Whether it is or is not a part of DoD today is not important. It 
> functions
> as a separate agency (from DISA) under executive branch control.

Since for a very very long time, including back when DISA was DCA, it is
always the case that ((Director of NCS) == (Director of DISA)).   Since
NCS is always run by the Director of DISA, it is pretty hard to claim 
that
is very separate from DISA.  So, I find the above characterisation
to be misleading at best.

It does seem likely that NCS will be moved on paper into DHS in the 
impending
re-organisation.  How this plays out is unclear to me and depends on 
what
Congress ultimately decides to pass in legislation.

This is now pretty far off-charter, so maybe we can return to the more
customary threads.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 20:32:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25682
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 20:32:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA91YhS15012
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 20:34:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91Yhv15009
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 20:34:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25666
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 20:32:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91Y1v14977;
	Fri, 8 Nov 2002 20:34:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA91XEv14951
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 20:33:14 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25630
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 20:30:35 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 6AB276710D; Fri,  8 Nov 2002 16:54:16 -0500 (EST)
Date: Fri, 8 Nov 2002 20:33:03 -0500
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework  -02.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <11a.19cf68e8.2afd93e1@aol.com>
Message-Id: <3088A695-F383-11D6-8AB8-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 17:25 America/Montreal, Mpierce1@aol.com 
wrote:
> The rest of us are not arguing that your case doesn't exist or that 
> you can't choose to operate your network on that presumption. But you 
> keep arguing that others can't operate their network the way they want 
> to (like with barely enough bandwidth available on good days and a 
> serious shortage on bad days).

Which others are you speaking of who have problems ?
Please give specific examples.  What does their network look like ?

I know of folks who run life-critical voice over IP over 2.4 Kbps HF 
Radio.[1]
They don't have QoS either.  Is that low enough bandwidth to count as 
"barely enough
available on a good day" ?

Ran

[1] The voice quality can't be called "PSTN toll quality" at 2.4 Kbps,
but it is intelligible.  If you give the same folks 9.6 Kbps, they think
they are in heaven and the voice quality increases more than linearly.
They probably aren't using an ITU vocoder algorithm either, but I'm not
100% sure either way.  My guess would be some form of CELP with FEC.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 20:59:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26208
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 20:59:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9221V16351
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 21:02:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9221v16348
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 21:02:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26204
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 20:59:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9212v16330;
	Fri, 8 Nov 2002 21:01:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA920Bv16266
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 21:00:11 -0500
Received: from imo-m09.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26160
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 20:57:31 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m09.mx.aol.com (mail_out_v34.13.) id j.5f.2fbeac40 (25914);
	Fri, 8 Nov 2002 21:00:00 -0500 (EST)
Message-ID: <5f.2fbeac40.2afdc620@aol.com>
Date: Fri, 8 Nov 2002 21:00:00 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_5f.2fbeac40.2afdc620_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_5f.2fbeac40.2afdc620_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/8/2002 8:21:27 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> There are MANY different definitions for "accounting" in the IETF.
> It would help further the discussion A Whole Lot if one were much
> more clear about which (sub)set of those definitions is intended
> by the proponent of the idea.
> 

Yes, I'm sure there are. Have you read 
draft-pierce-ieprep-assured-service-req-00.txt?

Mike Pierce


--part1_5f.2fbeac40.2afdc620_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/8/2002 8:21:27 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">There are MANY different definitions for "accounting" in the IETF.
<BR>It would help further the discussion A Whole Lot if one were much
<BR>more clear about which (sub)set of those definitions is intended
<BR>by the proponent of the idea.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>Yes, I'm sure there are. Have you read draft-pierce-ieprep-assured-service-req-00.txt?
<BR>
<BR>Mike Pierce
<BR></FONT></HTML>

--part1_5f.2fbeac40.2afdc620_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 21:53:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28307
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 21:53:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA92tqQ19642
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 21:55:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA92tqv19639
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 21:55:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28304
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 21:53:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA92t8v19614;
	Fri, 8 Nov 2002 21:55:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA92snv19593
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 21:54:49 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28258
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 21:52:08 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 41A1F67103; Fri,  8 Nov 2002 18:15:51 -0500 (EST)
Date: Fri, 8 Nov 2002 21:54:38 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <5f.2fbeac40.2afdc620@aol.com>
Message-Id: <95FA00BA-F38E-11D6-8AB8-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 21:00 America/Montreal, Mpierce1@aol.com 
wrote:
> In a message dated 11/8/2002 8:21:27 PM Eastern Standard Time, 
> rja@extremenetworks.com writes:
>> There are MANY different definitions for "accounting" in the IETF.
>> It would help further the discussion A Whole Lot if one were much
>> more clear about which (sub)set of those definitions is intended
>> by the proponent of the idea.
>
> Yes, I'm sure there are. Have you read 
> draft-pierce-ieprep-assured-service-req-00.txt?

Yes.

It is unclear what you are looking for in Section 4.8 (and also
in a number of other places).  One interpretation is that you want
packet accounting for how many packets marked X were forwarded.
Another is that you want to have SIP always perform application-specific
accounting of some (unclear) sort.  Another is that you want to have
all of the above.  The final possibility seems to be that you have
something else in mind entirely.  Clarity would be good.

Anther major source of confusion is the repeated discussion in that 
draft
about "calls" as if they were stateful below the transport-layer, when 
the
Internet Architecture does not have such a concept.

In the Internet model, there is no session-layer, so no explicit 
session-state.

There is some transport state (more with TCP or SCTP than with UDP).  
There
is very little to no state in UDP (partly depending on whether one is 
speaking
architecturally or in terms of a particular implementation).  For 
example,
UDP in a 4.4 BSD implementation does have some slight state in a 
protocol
control block -- but conceptually/architecturally UDP has no state.  
Most
voice applications run over UDP.

The SIP application might have application-layer state, but that doesn't
imply or require the existence of lower-layer state.

At the IP-layer, the Internet provides an unreliable datagram service 
only.
The IP-layer does not have the *concept* of a call, nor should it have
that concept.  Such would violate the end-to-end principle.

So you see, I have read the draft, I find it confusing, and I believe
that we need much more clarity before/during Atlanta to have an 
effective
meeting.

Ran
rja@extremenetworks.com


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov  8 22:31:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29030
	for <ieprep-archive@odin.ietf.org>; Fri, 8 Nov 2002 22:31:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA93XCK21561
	for ieprep-archive@odin.ietf.org; Fri, 8 Nov 2002 22:33:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA93XCv21558
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 22:33:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28970
	for <ieprep-web-archive@ietf.org>; Fri, 8 Nov 2002 22:30:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA93WAv21499;
	Fri, 8 Nov 2002 22:32:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA93VVv21467
	for <ieprep@optimus.ietf.org>; Fri, 8 Nov 2002 22:31:31 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28905
	for <ieprep@ietf.org>; Fri, 8 Nov 2002 22:28:52 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 8 Nov 2002 21:31:20 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Date: Fri, 8 Nov 2002 21:31:20 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9AFF4@KC-MAIL2.kc.umkc.edu>
Thread-Index: AcKHkt2lGSLuLucQSFm5qISiQVOaowAAANeQ
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "RJ Atkinson" <rja@extremenetworks.com>, <gthom@delta-info.com>
Cc: "Bill Woodcock" <woody@pch.net>, <ieprep@ietf.org>
X-OriginalArrivalTime: 09 Nov 2002 03:31:20.0984 (UTC) FILETIME=[78BB1980:01C287A0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA93VVv21468
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> During that day, a few content providers had problems delivering
> all the requested content. In at least some cases, this was server
> overload. However, careful analysis of traffic logs by large ISPs
> afterwards confirms that the Internet performed brilliantly. Despite
> fibre cuts in lower Manhatten and numerous environmental problems at
> Hudson Street, the Internet automatically re-routed around the damage
> and kept going. And the large ISPs did NOT (repeat did NOT) start
> dropping packets because of the cut fibres -- their backbones were
> carefully over-engineered so the traffic was re-routed around the
> lost links.

 This is a comment from a service provider.
 "BGP stability was normal that day, or even better than normal since 
many companies sent their workers home (so there were probably fewer 
configuration changes on the 11th than on other days).  I've heard 
anecdotally that some backbone networks saw a decrease in traffic 
(probably because people were at home on low-bandwidth connections 
or watching TV, or were thwarted in their attempts to access to popular 
news sites)."
( other than cowie's presentation on 9/11)


But, we should also remember that telephone networks are the major
ones to be affected. One of the major reason for the robustness of 
Internet is the redundancy among ISP ( which is not the case in 
PSTN network.) In NY area, verizon was the hot spot/congestion point
as all carriers junction at verizon. 
(Note: I searched for NY article for refernce but couldn't find
 one.. Possibly, some nanoger can point, as it came under discussion.)


> 
> Access to the US NASA feeds of the mars lander landing was a bigger
> problem in Internet terms, yet even then the problems were on NASA's
> access links and its servers, rather than in any large ISPs network.

But, Code RED had major effect on the routing system than the above one..



> To give  another example, there was a fibre cut near 
> Baltimore a while back. It cut several fibre bundles from different 
> carriers. The IP  routing system
> just automatically detected the link-down state and routed 
> around the cut links
> -- and there was enough spare capacity in the other links 
> that there was no significant loss of service.

Although, I accept your point about reconvergence, fiber cut due
to Baltimore train wreck had some major effect partly. Since,
it is a train wreck, telecommunication repairs took some extra
time to repair than normal. 

http://www.cs.berkeley.edu/~randy/Courses/cs294.s02/baltimore_train-071901.doc
( Sorry for the word Doc ref. I could not find archives in Keynote/traffic
health site)


> The IP  routing system
> just automatically detected the link-down state and routed 
> around the cut links
> -- and there was enough spare capacity in the other links 
> that there was no significant loss of service.

A network can become overloaded for three reasons: Unexpected and major event 
leading to simultaneously access of the network,Link/router failures/outages 
and  Asymmetry at various levels. Of all this, link failures due to fiber
cut is a major contributor. So, a measurement study on them will be 
really useful.

Although, failure analysis in BGP was well studied by Ahuja/labovitz, it was
not done for intra-domain(link state) network ( as reconvergence time is less
when compared to inter-domain.) But It is necessary to study them, both for
helping researchers/operators.

- "Service availability" is a common term in telephone networks. But, with
the advent of VoIP/ priority traffic, it is necessary to define service
availability in Internet too. For doing such things, failure modeling is
the base step ( studying rate/CDF of failures etc.)
( It will help operators to define terms for SLA )

- Learning Objective functions for OSPF weight optimization
  ( helps researchers/operators)


 
> It would also be helpful if going forward we could clearly 
> separate our
> sundry concerns into the different layers of the Internet 
> Architecture (Physical,
> Link, IP, Transport, Application).

This is very important for this group.. 
For example:
 - when your talking about Japan-IAA system ..It is application
layer and IETF has nothing to say about a data base unless they
want to load balance like content distribution networks.

- Recently, alternate routing - In application layer, it is 
feasible (TRIP ) but in Network layer, not possible in near future.

But, once the SIP requirement was shipped to Sipping group, we should
only be talking in network layer realm.



 
 
> 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 04:45:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14895
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 04:45:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA99lcJ14636
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 04:47:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA99lbv14633
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 04:47:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14890
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 04:44:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA99kNv14608;
	Sat, 9 Nov 2002 04:46:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA99jgv14563
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 04:45:42 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14870
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 04:43:00 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA99dUd27864;
	Sat, 9 Nov 2002 01:39:30 -0800 (PST)
Date: Sat, 9 Nov 2002 01:39:30 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: nguyena@ncs.gov, <ieprep@ietf.org>
Subject: Re: Congestion avoidance Re: [Ieprep] draft-ietf-ieprep-framework 
 -02.txt
In-Reply-To: <11a.19cf68e8.2afd93e1@aol.com>
Message-ID: <Pine.GSO.4.44.0211090136450.27291-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 8 Nov 2002 Mpierce1@aol.com ludicrously characterized
      several thousand 9600bps dialup  users sharing a 384K satellite
      link as:
    > a big, fat commercial network, with lots of excess bandwidth,
    > always in a condition of no major failues or causes of totally
    > unexpected traffic volumes.

Uh, do I even need to comment?

    > Your comments and arguments keep coming back to a situation of
    > excess bandwidth always being available so there's no problem to
    > solve.

Correct.  If you can refute reality, you'll have my attention.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 04:46:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14988
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 04:46:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA99n3F14761
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 04:49:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA99n3v14758
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 04:49:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14961
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 04:46:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA99m1v14662;
	Sat, 9 Nov 2002 04:48:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA99lOv14628
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 04:47:24 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14887
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 04:44:42 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA99fDd27885;
	Sat, 9 Nov 2002 01:41:13 -0800 (PST)
Date: Sat, 9 Nov 2002 01:41:13 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Atlanta ieprep Agenda
In-Reply-To: <73.28cb9c71.2afd93e4@aol.com>
Message-ID: <Pine.GSO.4.44.0211090139490.27291-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 8 Nov 2002 Mpierce1@aol.com wrote:
    > The term "accounting" is the accepted one for what we are talking about.
                ^^^^^^^^^^

You misspelled "waste of money."  This is the Internet, not the PSTN.
We'd rather deliver the traffic than fail to deliver the traffic in favor
of delivering a bill instead.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 08:02:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17771
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 08:02:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9D4EB23480
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 08:04:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9D4Ev23477
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 08:04:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17758
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 08:01:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9D3Bv23441;
	Sat, 9 Nov 2002 08:03:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9D2rv23419
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 08:02:53 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17723
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 08:00:19 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 7214967103; Sat,  9 Nov 2002 04:24:06 -0500 (EST)
Date: Sat, 9 Nov 2002 08:02:50 -0500
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9AFF4@KC-MAIL2.kc.umkc.edu>
Message-Id: <8CE1F5B9-F3E3-11D6-A484-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 8, 2002, at 22:31 America/Montreal, Ayyasamy, 
Senthilkumar (UMKC-Student) wrote:
> But, we should also remember that telephone networks are the major
> ones to be affected. One of the major reason for the robustness of
> Internet is the redundancy among ISP ( which is not the case in
> PSTN network.) In NY area, verizon was the hot spot/congestion point
> as all carriers junction at verizon.

Hmm.  Not sure what you mean by "carriers" and what you mean by 
"verizon".
"carrier" could mean either telephone company or ISP given the preceding
text.  Verizon is a firm, not a location.

There are several ISP interconnects in lower Manhatten.  The most
significant one is on Hudson Street, but others do exist.

>> Access to the US NASA feeds of the mars lander landing was a bigger
>> problem in Internet terms, yet even then the problems were on NASA's
>> access links and its servers, rather than in any large ISPs network.
>
> But, Code RED had major effect on the routing system than the above 
> one..

That impact varied directly with (1) which firm's routers one had 
installed
and (2) one's configuration for those routers.  Folks with 
hardware-based
ACLs didn't have big problems.  Folks using CPU-based ACLs had problems,
because the CPU became over-burdened.  This is not a systemic issue or
a protocol issue, but rather an equipment selection/deployment issue.

> Although, failure analysis in BGP was well studied by Ahuja/labovitz, 
> it was
> not done for intra-domain(link state) network ( as reconvergence time 
> is less
> when compared to inter-domain.) But It is necessary to study them, 
> both for
> helping researchers/operators.

	Inside an ISP, I-BGP is used internally in addition to an IGP -- and 
I-BGP
is more significant to the convergence of the routing system as 
perceived
by customers/users.

> - "Service availability" is a common term in telephone networks. But, 
> with
> the advent of VoIP/ priority traffic, it is necessary to define service
> availability in Internet too. For doing such things, failure modeling 
> is
> the base step ( studying rate/CDF of failures etc.)
> ( It will help operators to define terms for SLA )

	Several operators have defined both "service availability" and "SLA".
The current definitions vary among carriers.  Customers who don't read
their SLAs closely might be disappointed by what the SLAs actually 
promise.

> - Learning Objective functions for OSPF weight optimization
>   ( helps researchers/operators)

Not clear what you mean by "Learning Objective functions".

> This is very important for this group..
> For example:
>  - when your talking about Japan-IAA system ..It is application
> layer and IETF has nothing to say about a data base unless they
> want to load balance like content distribution networks.

"Voice over IP" and "SIP" are also examples of application-layer 
services.

> - Recently, alternate routing - In application layer, it is
> feasible (TRIP ) but in Network layer, not possible in near future.

I do not understand your meaning.

> But, once the SIP requirement was shipped to Sipping group, we should
> only be talking in network layer realm.

I would not object to that proposal.

	As Ken explains much better than I do, the reason there are 2 separate
documents is to separate issues architecturally.  His 
draft-carlberg-ets-general-*
is focused on concerns relating to the IP-layer, while 
draft-carlberg-ets-telephony-*
is focused on concerns relating to VoIP applications (at the 
application-layer).

	Clearly some folks will want to use IEprep for VoIP stuff, so having 
that
documented is helpful.  However, other folks will not want to use IEprep
for VoIP, so the VoIP-related stuff needs to be separated out cleanly 
from
generic IEprep stuff.

	And it would still help if we could get more specific, clear 
documentation
on the GETS-like or IEprep-like services in use or contemplated for use 
in
countries other than US and JP.  This needs to come from folks in the 
relevant
country, rather than being claims by person in country X about country 
Y's
needs.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 09:40:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19602
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 09:40:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9Eh0x29066
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 09:43:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Eh0v29063
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 09:43:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19583
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 09:40:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Eb7v28593;
	Sat, 9 Nov 2002 09:37:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Eawv28288
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 09:36:58 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19506
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 09:34:23 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP id 972CD67103
	for <ieprep@ietf.org>; Sat,  9 Nov 2002 05:58:11 -0500 (EST)
Date: Sat, 9 Nov 2002 09:36:50 -0500
Mime-Version: 1.0 (Apple Message framework v546)
Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed
From: RJ Atkinson <rja@extremenetworks.com>
To: ieprep <ieprep@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <AEFFD14C-F3F0-11D6-A484-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] architectural considerations
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


	My assessment is that part of the communication problems
that recur on this list relate to different perceptions of the
Internet Architecture.  This email provides a list of selected
references on Internet Architecture, in hope that folks might
read all/most/some of these.

	There is at the end an addendum on congestion avoidance in
the Internet, since there are widely disparate views expressed on
this list about how much of an issue congestion is in the deployed
Internet.

	I encourage everyone here to read any of these items that
one is not already familiar with.

Ran
rja@extremenetworks.com

---------------------------------------------------------------
The following IAB documents might be helpful background
reading for folks concerned with IEprep work:

	RFC-1958:		Architectural Principles of the Internet
	RFC-2990:		Next Steps for the IP QoS Architecture
	RFC-3221:		Commentary on Inter-Domain Routing

---------------------------------------------------------------
These documents might also be helpful as they provide
context on the Internet Architecture, why the Internet
has evolved the way it has, or other Internet issues:

End to End Arguments in System Design (PDF)
	http://web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf

Design Philosophy of the DARPA Internet Protocols
	http://www.acm.org/sigcomm/ccr/archive/1995/jan95/ccr-9501-clark.html

Will the Real End-to-End Principle Please Stand Up ?
	http://users.exis.net/~jnc/tech/end_end.html

"Soft" and "Hard" State
	http://users.exis.net/~jnc/tech/hard_soft.html

Architectural Principles of the Internet (PDF), as seen by Bob Braden
	http://www.isi.edu/newarch/DOCUMENTS/rtb.IPAM.mar02.pdf

----------------------------------------------------------------------
These next documents talk about Congestion Avoidance
as it relates to the deployed Internet:

Congestion Avoidance & Control (PDF)
	http://www-nrg.ee.lbl.gov/papers/congavoid.pdf

RED Gateways for Congestion Avoidance (PDF)
	http://www.icir.org/floyd/papers/red/red.html

Recommendations on Queue Management and Congestion Avoidance
in the Internet
	RFC-2309
------------------------------------------------------------------------ 
---

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 10:35:19 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20430
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 10:35:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9FbNB31704
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 10:37:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9FbNv31701
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 10:37:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20408
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 10:34:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9FaLv31100;
	Sat, 9 Nov 2002 10:36:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9FZsv31084
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 10:35:55 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20394
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 10:33:19 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA9FXSfQ011026;
	Sat, 9 Nov 2002 10:33:28 -0500 (EST)
Date: Sat, 9 Nov 2002 10:33:28 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211091533.gA9FXSfQ011026@newdev.harvard.edu>
To: gthom@delta-info.com
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Cc: ieprep@ietf.org
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPCEGKDDAA.gthom@delta-info.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

this is a bit long but I hope will make some things clearer

gthom sez:

> As I said before, there are two issues:
> 
> The first is whether the network (and associated elements such as routers
> and switches) can provide priority transport of packets associated with an
> emergency call. I am not qualified to address this, so I defer to others as
> to whether this is a problem or not, but certainly there is a desire to give
> some preferencial treatment to those packets in the event of congestion or
> degrated operation.

making the assumption that for whatever reason there is not enough capacity
in an ISP's network to deal with all of the offered traffic load during an
emergency - the likelihood of this being the case will be different in
different parts of the world and for different ISPs

and making the assumption that we are talking about a single ISP (dealing
with the issues of coordinating any kind of support for non-best-effort
traffic between ISPs is a very hard problem that will not be solved in the
ieprep WG)

the simple answer to the first part of the first issue is that routers can
provide priority transport of packets, they have been able to do so  for
quite a while.

Routers can use the precedence bits in the header of IP packets to find out
what relative priority specific traffic should be processed at

But it is far from clear that this is what an ISP would want to do with
ieprep traffic - ISPs have regular customers which need to be able to
continue to communicate in cases of emergency - a strict priority-based
system where the ieprep traffic got absolute priority could easily starve
the traffic from the ISPs regular customers - 

it is my opinion that those ISPs who decide to offer ieprep service (for
lack of a better term) will set aside *some* of their capacity to support
this service offering - if the ieprep demand exceeds the capacity reserved
for it then there will be degraded service - exactly the same as if the ISP
were to dedicate all of their capacity  and the demand exceeded the
physical capacity  of the ISP's network

because of this I do not think that "priority" is even the correct concept
to be talking about - I think that "special handling" is about as close as
we can get to what might happen in the real world

In addition, any pure priority-based service is *very* vulnerable to denial
of service attacks - an attacker can send lots of traffic marked as ieprep
traffic which will result in the ISP not being able to delever any traffic
at all

 some routers can also use RSVP to reserve capacity for particular flows or
diffserv to differentiate traffic into different classes (note that most
difserv classes are not strictly priority) - these technologies may be a
far better bet to support ieprep that a pure priority-based approach

the simple answer to the second part of the first issue is that the routers
do not know what applications are transmitting packets  so the *router* can
not tell which packets are associated with an emergency call - something
will have to tell the router which packets are associated with a particular
flow (using RSVP for example) or mark the packets associated with an
emergency call in some special way (using diffserv for example)


gthom also sez:
> The second is whether the telephony elements (such as SIP proxy servers, 
> redirect servers, etc) are informed that a particular call is an emergency
> call so that those elements can take action to improve the proboability of
> call completion. For example, to loosen addmission policy to allow an    
> emergency call even though other addmission criteria may not be satisfied.
> The actual action to be taken is certainly a local matter and not subject to
> standardization, however, the signalling within the protocol to indicate an
> emergency call should be done in a standardized way. At least this part  
> should be communicated with the proper WG in order to enhance the SIP    
> protocol.

as far the second issue:  I do not understand what SIP proxies etc would do
differently if they were told that a call was an ieprep call - I expect
that SIP servers/proxies etc will have plenty of processing capacity to
deal with processing all SIP calling requests that they receive (I suppose
the operator of a SIP network could decide to use old 33MHz 286 DOS
machines for their SIP servers but aside from that possibility it does not
seem realistic to think that SIP servers would need to pay attention to any
ieprep indication in terms of avoiding overload.

The suggestion is made that admission policy could be loosened for
emergency calls - this seems particularly risky in terms of providing
opportunities for denial of service attacks - unless one postulates a
totally reliable and unbreakable authentication mechanism for the users of
ieprep services which users will reliability have with tem when they need
to make an ieprep call.

I am not sure what one would change in SIP to deal with this issue beyond
what is already in Hennings SIP requirements document

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 11:33:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21112
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 11:33:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9GZot01326
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 11:35:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9GZov01323
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 11:35:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21068
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 11:33:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9GZAv01274;
	Sat, 9 Nov 2002 11:35:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9GRav01111
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 11:27:36 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20963
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 11:25:02 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA9GLYd02539;
	Sat, 9 Nov 2002 08:21:34 -0800 (PST)
Date: Sat, 9 Nov 2002 08:21:34 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Scott  Bradner <sob@harvard.edu>
cc: gthom@delta-info.com, <ieprep@ietf.org>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <200211091533.gA9FXSfQ011026@newdev.harvard.edu>
Message-ID: <Pine.GSO.4.44.0211090813220.27946-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 9 Nov 2002, Scott  Bradner wrote:
    > I do not understand what SIP proxies etc would do differently if
    > they were told that a call was an ieprep call.

I can't imagine any different handling would be needed within the SIP
infrastructure, however the receiving SIP end-station quite likely would
want to handle the calls differently.  Un-mute the ringer and set it to
maximum volume, dump the last low-priority call-appearance in the event
that the phone is limited to a specific number of simultaneous
call-appearances, and use some more intrusive form of call-waiting
notification than is usual.  If the end-station is an auto-attendant,
perhaps provide operator notification that an emergency call is being
progressed, and give the operator the option of breaking in to handle it
personally.  Move emergency calls to the head of any hold queues.  Provide
a different (and presumably simplified) user-specified option tree.  If
the end-station is voicemail, have it mail the result with a higher SMTP
priority, and exercise all delivery options simultaneously and at once.

But all of this is vendor-specific, and up at the application layer.

This is the sort of stuff User Services was particularly good at, and
exactly the reason I think it shouldn't have been shut down.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 11:40:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21210
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 11:40:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9Gg7B02156
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 11:42:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Gg7v02153
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 11:42:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21201
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 11:39:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9GfDv02122;
	Sat, 9 Nov 2002 11:41:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9GeIv02077
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 11:40:18 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21164
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 11:37:43 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP id 86A0967103
	for <ieprep@ietf.org>; Sat,  9 Nov 2002 08:01:31 -0500 (EST)
Date: Sat, 9 Nov 2002 11:40:09 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
From: RJ Atkinson <rja@extremenetworks.com>
To: ieprep <ieprep@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <200211091533.gA9FXSfQ011026@newdev.harvard.edu>
Message-Id: <E8EBB5AE-F401-11D6-A484-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Re: QoS in the network
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 9, 2002, at 10:33 America/Montreal, Scott Bradner 
wrote:
> the simple answer to the first part of the first issue is that routers 
> can
> provide priority transport of packets, they have been able to do so  
> for
> quite a while.
>
> Routers can use the precedence bits in the header of IP packets to 
> find out
> what relative priority specific traffic should be processed at

No disagreement with the above from me.[2]  It does carefully sidestep 
discussion
of operational considerations, which I'll try to address briefly in 
this note.

There are some unresolved issues with using IP ToS bits to sort out 
packet
precdence or drop preference.  I am unable to locate any *confirmed*
large-scale deployment of DiffServ by a commercial ISP.[1]  There are 
some
limited scale deployments, mostly in campus or research networks.  So
there are a bunch of operational/deployment issues with DiffServ that
appear to be unresolved.  Those would need to be fully resolved before
one could reasonably expect DiffServ to be widely deployed by commercial
ISPs.

[1] Of press releases or news accounts claiming such, none that I've 
been
able to track down in detail have turned out to really be DiffServ.  
There
are a couple that I'm currently trying to track down in detail to see if
they might be real DiffServ in a real production large-scale commercial 
ISP.

[2] Scalability of the implementation of this feature in a particular 
router
does vary greatly from router to router.  To deploy this, an operator 
would
need to perform appropriate equipment tests and might need to change 
some
routers for others that are better able to forward traffic while this 
feature
is enabled.  CPU-based routers are at a disadvantage to ASIC-based 
routers,
for example, though CPU-based routers are sometimes lower capital cost.

> In addition, any pure priority-based service is *very* vulnerable to 
> denial
> of service attacks - an attacker can send lots of traffic marked as 
> ieprep
> traffic which will result in the ISP not being able to delever any 
> traffic
> at all

And per-packet cryptographic authentication prior to forwarding is not
computationally feasible in an IP router today -- and certainly not 
anytime
soon for any large or medium percentage of packets.

>  some routers can also use RSVP to reserve capacity for particular 
> flows or
> diffserv to differentiate traffic into different classes (note that 
> most
> difserv classes are not strictly priority) - these technologies may be 
> a
> far better bet to support ieprep that a pure priority-based approach

The operational experience with RSVP is that it creates too much flow
state in routers, decreasing reliability/availability of the network
overall.  Given the operational experience in the limited deployments
of RSVP so far, RSVP seems unlikely to ever be widely deployed by a
commercial ISP as a regular (i.e. non experimental) service.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 11:51:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21423
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 11:51:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9GreA02462
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 11:53:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Grev02459
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 11:53:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21414
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 11:51:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Gr2v02435;
	Sat, 9 Nov 2002 11:53:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Gqov02419
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 11:52:50 -0500
Received: from brazilnut.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21405
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 11:50:15 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(user=hgs10 mech=PLAIN bits=0)
	by brazilnut.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gA9Gqjbj003044
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 11:52:46 -0500 (EST)
Message-ID: <3DCD3CE7.6010805@cs.columbia.edu>
Date: Sat, 09 Nov 2002 11:50:47 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
References: <4B5B4DB3-F35F-11D6-BC9C-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Since magic miracle vocoders come up all the time, it might be useful to 
   refer to the published literature on the topic. We have done a fair 
amount of listener evaluation of commonly used codecs and their 
sensitivity to (bursty) packet loss. See 
http://www.cs.columbia.edu/~wenyu for some papers on the subject. 
References therein will lead to a large number of related studies. I 
would appreciate pointers to published studies that provide additional 
or conflicting data.

By simple logic, no vocoder, however evolved, can cover losses that are 
long enough to delete significant portions of a syllable or word, unless 
you're willing to tolerate delays that turn interactive voice 
communications into voice messaging. Anybody is obviously free to 
operate their network in a way that offers only 
email-with-voice-attachments under overload; I don't think it is helpful 
to say that nobody should be operating a network that offers service 
that it better than that or that it is illegitimate to look at 
techniques that improve the quality of high-value communications at the 
expense of lower-value communications. I think it is useful to evaluate 
tools even if not everybody wants to use them or if they are not 
appropriate everywhere.

If a particular technique is never helpful, has been superceded by 
better tools or has severe "side-effects", we should document those 
issues and then leave it up to operators to make operational judgements 
that weigh the pros and cons.

As admirable as the PCH network is, it is rather small and homogeneous 
in the global scheme of things, with O(100) nodes. All available 
evidence indicates (see Infocom 2002 paper "Assessment of VoIP quality 
over Internet Backbones" 
[http://www.ieee-infocom.org/2002/papers/355.pdf], papers by Maxemchuk 
and Lo in ICC 1997 and any number of "Internet weather" sites) that 
congestion-induced impairments of network quality are common and real. 
Just saying that "most" conversations work just fine isn't particularly 
helpful in environments that have little tolerance for failure.

Rather than reasoning by anecdote, it might be helpful if participants 
in this conversation cited verifiable and peer-reviewed evidence.

Henning

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 12:19:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21831
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 12:19:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9HLuh04289
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 12:21:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9HLuv04286
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 12:21:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21820
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 12:19:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9HL3v04257;
	Sat, 9 Nov 2002 12:21:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9HKdv04231
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 12:20:39 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21800
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 12:18:04 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA9HEcd03229;
	Sat, 9 Nov 2002 09:14:38 -0800 (PST)
Date: Sat, 9 Nov 2002 09:14:38 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <3DCD3CE7.6010805@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211090902540.27946-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 9 Nov 2002, Henning Schulzrinne wrote:
    > As admirable as the PCH network is, it is rather small and homogeneous
    > in the global scheme of things, with O(100) nodes.

That's nice.  Show me a larger inter-carrier production VoIP network, and
you'll be well on your way to being taken seriously.

    > All available evidence...
      ^^^^^^^^^^^^^^^^^^^^^^

You appear to have misspelled "three armchair theoreticians."

    > ...indicates...

"speculate"

    > (see Infocom 2002 paper "Assessment of VoIP quality over Internet
    > Backbones" [http://www.ieee-infocom.org/2002/papers/355.pdf]

Did you even read that paper?  They didn't measure anything, and they
didn't try any VoIP.  Nor did they assess VoIP, quality, or the
Internet. How could it possibly be relevant to anything? All they did was
re-publish a _vendor's_ claims about observed network behavior without
verification or review.

    > papers by Maxemchuk and Lo in ICC 1997

...at about which time, dinosaurs roamed the earth...

    > and any number of "Internet weather" sites)

...you've GOT to be joking.

    > Rather than reasoning by anecdote, it might be helpful if participants
    > in this conversation cited verifiable and peer-reviewed evidence.

Quite the opposite.  Rather than presenting circular chains of mutual
citations between equally uninformed academics, it might be helpful if a
few other participants in this conversation DID SOME VERIFICATION.  Since
Peter and I are the only ones who have, so far, a few of the rest of you
might spend a little bit of your excess time getting started on that.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 12:44:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22153
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 12:44:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9HkBY05571
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 12:46:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9HkBv05568
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 12:46:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22144
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 12:43:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9HjBv05514;
	Sat, 9 Nov 2002 12:45:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Hi2v05481
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 12:44:02 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22122
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 12:41:27 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA9Hc0d03479;
	Sat, 9 Nov 2002 09:38:00 -0800 (PST)
Date: Sat, 9 Nov 2002 09:38:00 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <3DCD3CE7.6010805@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211090933550.27946-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Oh, and another thing:

      On Sat, 9 Nov 2002, Henning Schulzrinne wrote:
    > As admirable as the PCH network is, it is rather small and homogeneous
    > in the global scheme of things, with O(100) nodes.

Aside from being personally insulting, since I have to assume you're
capable of running wc -l and typing the number of zeros you intend to
type, I can only conclude that you're attempting to intentionally mislead
participants in the working group.  Neither of which are reasonable
behavior.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 13:08:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22367
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 13:08:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9IA8r06714
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 13:10:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IA8v06711
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 13:10:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22364
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 13:07:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9I94v06678;
	Sat, 9 Nov 2002 13:09:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9I8jv06659
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 13:08:45 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA22358
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 13:06:09 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.25703-0@bells.cs.ucl.ac.uk>; Sat, 9 Nov 2002 18:08:37 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Mpierce1@aol.com
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Moving forward: draft-carlberg-ets-*.txt
In-reply-to: Your message of "Fri, 08 Nov 2002 17:25:36 EST." <10f.19c7f7d2.2afd93e0@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 09 Nov 2002 18:08:36 +0000
Message-ID: <27274.1036865316@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> It sounds like the approach is okay, but it is necesary to see -01 before
> one can say for sure about moving it to WG status. 

the co-chairs will correct me if I'm wrong, but the document(s) do
not have to be fully baked to be working group items.  there are
specific items that need to be addressed, but there have not been
disagreements with the structure of the draft nor of the approach
taken.  

moving forward is not a final call, just a progression of its status.

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 13:21:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22508
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 13:21:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9INjC06992
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 13:23:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9INiv06989
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 13:23:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22500
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 13:21:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IN3v06972;
	Sat, 9 Nov 2002 13:23:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IM3v06948
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 13:22:03 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22491
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 13:19:27 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA9ILYui011491;
	Sat, 9 Nov 2002 13:21:34 -0500 (EST)
Date: Sat, 9 Nov 2002 13:21:34 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211091821.gA9ILYui011491@newdev.harvard.edu>
To: K.Carlberg@cs.ucl.ac.uk, Mpierce1@aol.com
Subject: Re: [Ieprep] Moving forward: draft-carlberg-ets-*.txt
Cc: ieprep@ietf.org
In-Reply-To: <27274.1036865316@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> the co-chairs will correct me if I'm wrong, 

:-)

> but the document(s) do
> not have to be fully baked to be working group items.  there are
> specific items that need to be addressed, but there have not been
> disagreements with the structure of the draft nor of the approach
> taken. 

a doc needs to address a specific topic in the WG charter and be
generally seen as being in the same quadrent as WG consensus so
that, with aditional work, it can be made to articulate WG consensus

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 13:30:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22597
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 13:30:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9IWV107196
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 13:32:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IWUv07192
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 13:32:30 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22578
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 13:29:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IV2v07165;
	Sat, 9 Nov 2002 13:31:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IUQv07133
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 13:30:26 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA22561
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 13:27:50 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.26512-0@bells.cs.ucl.ac.uk>; Sat, 9 Nov 2002 18:30:13 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: RJ Atkinson <rja@extremenetworks.com>
cc: ieprep <ieprep@ietf.org>
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion 
         request]
In-reply-to: Your message of "Sat, 09 Nov 2002 08:02:50 EST." <8CE1F5B9-F3E3-11D6-A484-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 09 Nov 2002 18:30:12 +0000
Message-ID: <28224.1036866612@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


just a small nit.

>	As Ken explains much better than I do, the reason there are 2 separate
> documents is to separate issues architecturally.  His 
> draft-carlberg-ets-general-*
> is focused on concerns relating to the IP-layer, while 
> draft-carlberg-ets-telephony-*
> is focused on concerns relating to VoIP applications (at the 
> application-layer).

I would rephrase this just to say that the former can apply to the
network and application layers since no further qualifiers to
'signaling' and 'labels' are mentioned int ets-general.

> And it would still help if we could get more specific, clear documentation
> on the GETS-like or IEprep-like services in use or contemplated for use in
> countries other than US and JP.  This needs to come from folks in the 
> relevant country, rather than being claims by person in country X about 
> country Y's needs.

an attempt has been made to do this with the Framework document with 
respect
to the system in use by the UK.  In addition, its been reviewed by the UK 
govt (ie, the customer/user of the service) and this review has been 
acknowledged in the draft.  I think think this is one appropriate approach 
to take

-ken



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 13:34:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22643
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 13:34:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9IaEM07289
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 13:36:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IaDv07286
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 13:36:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22636
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 13:33:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IZ2v07259;
	Sat, 9 Nov 2002 13:35:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IZ0v07239
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 13:35:00 -0500
Received: from brazilnut.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22630
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 13:32:24 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(user=hgs10 mech=PLAIN bits=0)
	by brazilnut.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gA9IYqbj012943
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 9 Nov 2002 13:34:55 -0500 (EST)
Message-ID: <3DCD54D6.1050101@cs.columbia.edu>
Date: Sat, 09 Nov 2002 13:32:54 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Woodcock <woody@pch.net>, ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
References: <Pine.GSO.4.44.0211090933550.27946-100000@paixhost.pch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

My numbers come from 
http://www.pch.net/about/news/pressreleases/pressrelease10.28.02.html, 
where 120 and 150 are mentioned. I'm sorry if I read the wrong press 
release.

> Aside from being personally insulting, since I have to assume you're
> capable of running wc -l and typing the number of zeros you intend to
> type, I can only conclude that you're attempting to intentionally mislead
> participants in the working group.  Neither of which are reasonable
> behavior.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 13:51:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23281
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 13:51:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9Irdg08550
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 13:53:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Irdv08547
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 13:53:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23270
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 13:51:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IqEv08490;
	Sat, 9 Nov 2002 13:52:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Ioiv08313
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 13:50:44 -0500
Received: from marionberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23002
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 13:48:08 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(user=hgs10 mech=PLAIN bits=0)
	by marionberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gA9IoaLY002358
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 9 Nov 2002 13:50:39 -0500 (EST)
Message-ID: <3DCD5886.60200@cs.columbia.edu>
Date: Sat, 09 Nov 2002 13:48:38 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Woodcock <woody@pch.net>
CC: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
References: <Pine.GSO.4.44.0211090902540.27946-100000@paixhost.pch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>     > All available evidence...
>       ^^^^^^^^^^^^^^^^^^^^^^

I look forward to citations of peer-reviewed data that contradicts these 
assessments.

> 
> You appear to have misspelled "three armchair theoreticians."

Your ad-hominem arguments are not particularly helpful.

> Did you even read that paper?  They didn't measure anything, and they
> didn't try any VoIP.  Nor did they assess VoIP, quality, or the
> Internet. How could it possibly be relevant to anything? All they did was
> re-publish a _vendor's_ claims about observed network behavior without
> verification or review.

The authors are presumably not on this mailing list to defend 
themselves. Section IV.A describes the analysis of data performed by the 
authors. What concrete indications do you have that the measurement data 
is incorrect, unreliable or otherwise untrustworthy?

The data pattern does represent at least one reasonable representation 
of VoIP traffic.

> 
>     > papers by Maxemchuk and Lo in ICC 1997
> 
> ...at about which time, dinosaurs roamed the earth...

As mentioned, I would value pointers to published evidence that 
contradicts their conclusion. The evidence that I have (cited in the 
references of the paper mentioned, for example) is all fairly 
consistent, indicating that the changes in observed performance over the 
5-year horizon have been marginal.

> 
>     > and any number of "Internet weather" sites)
> 
> ...you've GOT to be joking.
> 
>     > Rather than reasoning by anecdote, it might be helpful if participants
>     > in this conversation cited verifiable and peer-reviewed evidence.
> 
> Quite the opposite.  Rather than presenting circular chains of mutual
> citations between equally uninformed academics, it might be helpful if a
> few other participants in this conversation DID SOME VERIFICATION.  Since
> Peter and I are the only ones who have, so far, a few of the rest of you
> might spend a little bit of your excess time getting started on that.

We are indeed looking for places to put measurement probes right now and 
would be grateful for sites willing to host our test software. We're 
interested in sites beyond the usual academic network sites, so sites on 
your network would be particularly helpful.

> 
>                                 -Bill
> 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 13:51:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23308
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 13:51:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9Irqk08571
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 13:53:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Irpv08568
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 13:53:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23274
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 13:51:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IqAv08450;
	Sat, 9 Nov 2002 13:52:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Indv08232
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 13:49:39 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22962
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 13:47:03 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA9Ihbd04356;
	Sat, 9 Nov 2002 10:43:37 -0800 (PST)
Date: Sat, 9 Nov 2002 10:43:37 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Gary Thom <gthom@delta-info.com>
cc: ieprep@ietf.org
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPCEGKDDAA.gthom@delta-info.com>
Message-ID: <Pine.GSO.4.44.0211091041150.4133-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 8 Nov 2002, Gary Thom wrote:
    > >     > The goal is to provide high probability of call completion in
    > >     > telephone (IP) systems.
    > > I missed the part in which someone presented some evidence to support your
    > > misassumption that this goal hasn't been met.
    > If it has been met, a simple statement of this capability will eliminate a
    > lot of continuing aggravation.

To reiterate, for the Nth time:

The Internet provides high probability of call completion in telephone
(IP) systems.

    > As I said before, there are two issues:
    > The first is whether the network can provide priority transport
    > The second is whether telephony elements are informed that a
    > particular call is an emergency call

Neither of which have anything to do with your stated requirement.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 13:51:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23321
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 13:51:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9IrrL08586
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 13:53:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Irrv08583
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 13:53:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23278
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 13:51:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IqDv08470;
	Sat, 9 Nov 2002 13:52:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IoMv08277
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 13:50:22 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA22986
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 13:47:45 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.27661-0@bells.cs.ucl.ac.uk>; Sat, 9 Nov 2002 18:50:12 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Scott Bradner <sob@harvard.edu>
cc: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion 
         request]
In-reply-to: Your message of "Sat, 09 Nov 2002 10:33:28 EST." <200211091533.gA9FXSfQ011026@newdev.harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 09 Nov 2002 18:50:10 +0000
Message-ID: <29341.1036867810@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> as far the second issue:  I do not understand what SIP proxies etc would do
> differently if they were told that a call was an ieprep call - I expect
> that SIP servers/proxies etc will have plenty of processing capacity to
> deal with processing all SIP calling requests that they receive (I suppose
> the operator of a SIP network could decide to use old 33MHz 286 DOS
> machines for their SIP servers but aside from that possibility it does not
> seem realistic to think that SIP servers would need to pay attention to any
> ieprep indication in terms of avoiding overload.

just a thought to consider.  there are voip systems in enterprise nets
that switch calls to the PSTN if the internal data net cannot support
PSTN toll-quality for the call(s).  my understanding is that some of
these systems essentially use counts as a rough estimate of load for
segmented traffic.  i wouldn't recommend this approach with SIP, but 
I wouldn't discount someone from doing this at some point either.

> The suggestion is made that admission policy could be loosened for
> emergency calls - this seems particularly risky in terms of providing
> opportunities for denial of service attacks - unless one postulates a
> totally reliable and unbreakable authentication mechanism for the users of
> ieprep services which users will reliability have with tem when they need
> to make an ieprep call.

actually, I would postulate that once the contracted measure of 'loosened'
admission control is reached (be it through valid users or DoS attack),
users that attempt labeled emergency calls gets the same service as the
common (non-labeled) user.

> I am not sure what one would change in SIP to deal with this issue beyond
> what is already in Hennings SIP requirements document

even with what I said above, i agree.

-ken



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 13:56:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23409
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 13:56:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9IwDT08756
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 13:58:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9IwDv08753
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 13:58:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23403
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 13:55:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Iv1v08685;
	Sat, 9 Nov 2002 13:57:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Iu9v08643
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 13:56:09 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23359
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 13:53:28 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA9IkHd04399;
	Sat, 9 Nov 2002 10:46:17 -0800 (PST)
Date: Sat, 9 Nov 2002 10:46:17 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Gary Thom <gthom@delta-info.com>
cc: RJ Atkinson <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPAEGMDDAA.gthom@delta-info.com>
Message-ID: <Pine.GSO.4.44.0211091044540.4133-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 8 Nov 2002, Gary Thom wrote:
    > One thing to remember, is that we are really looking at operating under
    > non-normal conditions.  In this situation, we want to give emergency
    > communications an advantage.

What possible greater advantage could they have than travelling the
best-supported path?  Why would you want to disadvantage them by making
them travel a path which was QoS-dependent, and would thus fail all the
time?

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:09:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23576
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:09:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JBXd09665
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:11:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JBWv09662
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:11:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23547
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:08:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JA2v09623;
	Sat, 9 Nov 2002 14:10:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9J9Rv09578
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:09:27 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23510
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:06:50 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id D19C467103; Sat,  9 Nov 2002 10:30:40 -0500 (EST)
Date: Sat, 9 Nov 2002 14:09:20 -0500
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DCD3CE7.6010805@cs.columbia.edu>
Message-Id: <C04A4E66-F416-11D6-849A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 9, 2002, at 11:50 America/Montreal, Henning 
Schulzrinne wrote:
> By simple logic, no vocoder, however evolved, can cover losses that 
> are long enough to delete significant portions of a syllable or word, 
> unless you're willing to tolerate delays that turn interactive voice 
> communications into voice messaging.

No question.  That agreed to, there are vocoders that are more tolerant
of adverse network conditions and vocoders that are less tolerant of
adverse network conditions.  One will tend to be more successful over IP
with the former than with the latter.

> All available evidence indicates (see Infocom 2002 paper "Assessment 
> of VoIP quality over Internet Backbones" 
> [http://www.ieee-infocom.org/2002/papers/355.pdf], papers by Maxemchuk 
> and Lo in ICC 1997 and any number of "Internet weather" sites) that 
> congestion-induced impairments of network quality are common and real.

I'm not terribly impressed by a lot of the published papers on Internet 
measurement
-- simply because in many cases the measurement did not use enough 
controls to
understand what was really being measured.  There is some work by folks 
at ICIR
on how hard it really is to measure stuff accurately, for example.

And many of the "Internet weather" sites don't bother trying to have 
good controls,
hence yield uninterpretable graphs.  If you have a specific good such 
site in mind,
please share it with us.

That noted, It would be pleasant if we could talk about the merits (or 
lack of them)
for specific papers.  Is that the main paper you suggest looking at, or 
did
you want to suggest a broader set for this discussion (URLs 
particularly welcomed) ??

And I'd definitely not be so bold as to claim "All available 
evidence..."
as you did.  At a minimum, the evidence is mixed.

Thanks,

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:11:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23635
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:11:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JDDI09798
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:13:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JDDv09795
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:13:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23619
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:10:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JC1v09695;
	Sat, 9 Nov 2002 14:12:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JBhv09679
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:11:43 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23557
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:09:07 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA9JBEmL011656;
	Sat, 9 Nov 2002 14:11:14 -0500 (EST)
Date: Sat, 9 Nov 2002 14:11:14 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211091911.gA9JBEmL011656@newdev.harvard.edu>
To: K.Carlberg@cs.ucl.ac.uk, sob@harvard.edu
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Cc: ieprep@ietf.org
In-Reply-To: <29341.1036867810@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> > as far the second issue:  I do not understand what SIP proxies etc would do
> > differently if they were told that a call was an ieprep call - I expect
> > that SIP servers/proxies etc will have plenty of processing capacity to
> > deal with processing all SIP calling requests that they receive (I suppose
> > the operator of a SIP network could decide to use old 33MHz 286 DOS
> > machines for their SIP servers but aside from that possibility it does not
> > seem realistic to think that SIP servers would need to pay attention to any
> > ieprep indication in terms of avoiding overload.
> 
> just a thought to consider.  there are voip systems in enterprise nets
> that switch calls to the PSTN if the internal data net cannot support
> PSTN toll-quality for the call(s).  my understanding is that some of
> these systems essentially use counts as a rough estimate of load for
> segmented traffic.  i wouldn't recommend this approach with SIP, but 
> I wouldn't discount someone from doing this at some point either.

note that SIP servers & proxies do not deal with the data stream, they just
deal with signaling so I do not know how this would work with SIP 

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:12:13 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23805
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:12:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JEIc09827
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:14:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JEIv09824
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:14:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23649
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:11:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JD3v09783;
	Sat, 9 Nov 2002 14:13:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JCGv09729
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:12:16 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23608
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:09:40 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 58A4D67103; Sat,  9 Nov 2002 10:33:30 -0500 (EST)
Date: Sat, 9 Nov 2002 14:12:10 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211090902540.27946-100000@paixhost.pch.net>
Message-Id: <254E1A3E-F417-11D6-849A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Measurement of Internet Congestion
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


{Aside: 	I fixed the subject to be more accurate.  We should
be doing that more often, IMHO. :-}

On Saturday, Nov 9, 2002, at 12:14 America/Montreal, Bill Woodcock 
wrote:
>  it might be helpful if a
> few other participants in this conversation DID SOME VERIFICATION.  
> Since
> Peter and I are the only ones who have, so far, a few of the rest of 
> you
> might spend a little bit of your excess time getting started on that.

Bill,

	You at least owe us a URL or bibliographic citation to your own work
if you are using it as your justification.  Henning was good enough to
provide a specific URL and bibliographic citation, which helped focus
things a great deal.

	Maybe you could find some presentations from NANOG, RIPE, or APRICOT
that are online and relevant to the discussion ?

Thanks,

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:13:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24164
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:13:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JFtE09909
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:15:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JFtv09906
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:15:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24156
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:13:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JF1v09867;
	Sat, 9 Nov 2002 14:15:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JEYv09843
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:14:34 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23707
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:11:57 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 948CB67103; Sat,  9 Nov 2002 10:35:47 -0500 (EST)
Date: Sat, 9 Nov 2002 14:14:27 -0500
Subject: Re: [Ieprep] Moving forward: draft-carlberg-ets-*.txt
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Scott Bradner <sob@harvard.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211091821.gA9ILYui011491@newdev.harvard.edu>
Message-Id: <771426A8-F417-11D6-849A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 9, 2002, at 13:21 America/Montreal, Scott Bradner 
wrote:
>> but the document(s) do
>> not have to be fully baked to be working group items.  there are
>> specific items that need to be addressed, but there have not been
>> disagreements with the structure of the draft nor of the approach
>> taken.
>
> a doc needs to address a specific topic in the WG charter and be
> generally seen as being in the same quadrent as WG consensus so
> that, with aditional work, it can be made to articulate WG consensus

Those 2 documents are at least as much "in the same quadrant as WG
consensus" as the draft-ietf-ieprep-* documents are.

If you have specific issues with the documents that make you think
they cannot, with additional work, be made to articulate WG consensus,
please share so we can edit accordingly.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:17:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24202
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:17:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JJtn10025
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:19:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JJtv10022
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:19:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24199
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:17:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JJ1v09996;
	Sat, 9 Nov 2002 14:19:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JIwv09981
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:18:58 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24185
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:16:21 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 2867467103; Sat,  9 Nov 2002 10:40:10 -0500 (EST)
Date: Sat, 9 Nov 2002 14:18:49 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <29341.1036867810@cs.ucl.ac.uk>
Message-Id: <132AA114-F418-11D6-849A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Re: VoIP in Enterprise LANs
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 9, 2002, at 13:50 America/Montreal, Ken Carlberg wrote:
> just a thought to consider.  there are voip systems in enterprise nets
> that switch calls to the PSTN if the internal data net cannot support
> PSTN toll-quality for the call(s).  my understanding is that some of
> these systems essentially use counts as a rough estimate of load for
> segmented traffic.  i wouldn't recommend this approach with SIP, but
> I wouldn't discount someone from doing this at some point either.

That is roughly congruent with what I hear about VoIP in Enterprise 
LANs.
I'll also note that my (non-scientific) sample of VoIP use in Enterprise
LANs leads me to believe that many such deployments deliberately put
the IP phones on dedicated Ethernet segments (for whichever reason;
could well be administrative convenience).

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:21:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24267
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:21:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JNce10197
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:23:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JNcv10194
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:23:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24263
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:21:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JN1v10178;
	Sat, 9 Nov 2002 14:23:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JLDv10102
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:21:13 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24225
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:18:36 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA9JF6d04792;
	Sat, 9 Nov 2002 11:15:06 -0800 (PST)
Date: Sat, 9 Nov 2002 11:15:06 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <3DCD5886.60200@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211091047290.4133-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 9 Nov 2002, Henning Schulzrinne wrote:
    > Section IV.A describes the analysis of data performed by the authors.

Yes.  They created a theoretical model, applied it to someone else's
completely unrelated and unverified data, didn't verify that their
results had anything to do with reality, and published it.

That would seem to me to put them deep in the cusions of armchair
theoreticality.

    > What concrete indications do you have that the measurement data
    > is incorrect, unreliable or otherwise untrustworthy?

No reason to think that the measurement data was faulty.  It wasn't
collected with VoIP in mind, of course, but it might be generally
applicable enough to be useful.  Of course one has no way of knowing,
since it's simply one vendor's information which is presumably
principally being used in support of sales of their product.

The issue is that the model, when applied to the data, produced a result
which contradicts observed reality.  But since the authors didn't bother
to observe reality, they didn't notice this.  Since you're citing them
rather than observing reality, and urging other people to ignore reality
in favor of circular chains of unverified mutually-citing papers, I have a
hard time figuring out what you're getting at.

    > We are indeed looking for places to put measurement probes right now and
    > would be grateful for sites willing to host our test software. We're
    > interested in sites beyond the usual academic network sites, so sites on
    > your network would be particularly helpful.

You're quite welcome to go ahead and ask them.  And if there's any
chance at all that your measurements will get people to stop
asking for things they don't want, I'm all in favor of it.  However, I'd
guess that since networks are run by operators, they'll probably ask you
whether there's some problem you're trying to solve before they dedicate
any resources to your project.  So you probably want to think about how
you're going to answer that.

Wouldn't it be a lot more direct to just use the phones, rather than
"measurement probes" and "test software?"

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:28:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24383
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:28:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JUw010404
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:30:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JUwv10401
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:30:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24373
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:28:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JU2v10370;
	Sat, 9 Nov 2002 14:30:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JT5v10335
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:29:05 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24308
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:26:29 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA9JN4d04909;
	Sat, 9 Nov 2002 11:23:04 -0800 (PST)
Date: Sat, 9 Nov 2002 11:23:04 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Measurement of Internet Congestion
In-Reply-To: <254E1A3E-F417-11D6-849A-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211091117590.4133-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 9 Nov 2002, RJ Atkinson wrote:
    > 	You at least owe us a URL or bibliographic citation to your own work
    > if you are using it as your justification.  Henning was good enough to
    > provide a specific URL and bibliographic citation, which helped focus
    > things a great deal.
    > 	Maybe you could find some presentations from NANOG, RIPE, or APRICOT
    > that are online and relevant to the discussion ?

The slide-set from NANOG is at:

http://www.pch.net/inoc-dba/INOC-DBA-announcement.htm

Slide 9 has a chart with calls-per-day in yellow and number of phones in
use in red.  Of course, they're out-of-date now, since we're into
November.

Slide 8 is PAF's nephew, setting up his phone.  Which worked fine, by the
way.  :-)

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:29:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24407
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:29:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JVcR10469
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:31:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JVcv10466
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:31:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24400
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:29:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JV1v10448;
	Sat, 9 Nov 2002 14:31:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JUnv10392
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:30:49 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24370
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:28:12 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA9JOjd04936;
	Sat, 9 Nov 2002 11:24:45 -0800 (PST)
Date: Sat, 9 Nov 2002 11:24:45 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: VoIP in Enterprise LANs
In-Reply-To: <132AA114-F418-11D6-849A-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211091123420.4133-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 9 Nov 2002, RJ Atkinson wrote:
    > I'll also note that my (non-scientific) sample of VoIP use in Enterprise
    > LANs leads me to believe that many such deployments deliberately put
    > the IP phones on dedicated Ethernet segments (for whichever reason;
    > could well be administrative convenience).

The PoE switch ports are really expensive, so you don't want to waste them
on things other than phones and WAPs.

Also, DHCP options can be pretty different for phones than for other
things.

Those are the two main reasons.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:32:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24495
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:32:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JYvm10650
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:34:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JYvv10647
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:34:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24485
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:32:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JY1v10600;
	Sat, 9 Nov 2002 14:34:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JX9v10581
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:33:09 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24444
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:30:32 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA9JR7d04965;
	Sat, 9 Nov 2002 11:27:07 -0800 (PST)
Date: Sat, 9 Nov 2002 11:27:06 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <Pine.GSO.4.44.0211090902540.27946-100000@paixhost.pch.net>
Message-ID: <Pine.GSO.4.44.0211091126050.4133-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

       On Sat, 9 Nov 2002, Henning Schulzrinne wrote:
    > As admirable as the PCH network is, it is rather small and homogeneous
    > in the global scheme of things, with O(100) nodes.

My apologies.  Henning informs me that I should have interpreted 0(100) as
meaning the range 50-499, which should still be accurate for another three
weeks or so.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:32:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24508
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:32:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JYwu10666
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:34:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JYwv10663
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:34:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24489
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:32:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JY2v10616;
	Sat, 9 Nov 2002 14:34:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JXIv10585
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:33:18 -0500
Received: from marionberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24449
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:30:42 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(user=hgs10 mech=PLAIN bits=0)
	by marionberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gA9JX7LY012857
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 9 Nov 2002 14:33:08 -0500 (EST)
Message-ID: <3DCD627D.40904@cs.columbia.edu>
Date: Sat, 09 Nov 2002 14:31:09 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
References: <C04A4E66-F416-11D6-849A-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> No question.  That agreed to, there are vocoders that are more tolerant
> of adverse network conditions and vocoders that are less tolerant of
> adverse network conditions.  One will tend to be more successful over IP
> with the former than with the latter.

I don't think there's any disagreement about this. Indeed, certain 
companies mentioned in one of our papers strive to add robustness to 
standard codecs like G.711. Generally speaking, codec design is a 
trade-off between robustness to packet loss, quality and robustness to 
other impairments and a host of competing objectives (robustness to 
multiple talkers, background noise, available CPU resources in 
large-scale gateways, tandeming performance, ability to deal with DTMF, 
etc.).

> That noted, It would be pleasant if we could talk about the merits (or 
> lack of them)
> for specific papers.  Is that the main paper you suggest looking at, or did
> you want to suggest a broader set for this discussion (URLs particularly 
> welcomed) ??

The papers cited in the Infocom 2002 paper are a good beginning. 
Unfortunately, due to copyright reasons, you may need to be a subscriber 
to the ACM Digital Library or IEEE Xplore to obtain some of the papers. 
Not much I can do about that.

> 
> And I'd definitely not be so bold as to claim "All available evidence..."
> as you did.  At a minimum, the evidence is mixed.

I should have said "all published evidence that I have seen". As I've 
said a few times, I would be sincerely interested in quantitative 
evidence to the contrary.

All measurements are limited and, indeed, are getting to be increasingly 
difficult to make for a variety of practical reasons; I don't think 
falling back to "it works for me" arguments is a suitable replacement 
for measurements, however limited. Also, in some sense, it is sufficient 
to show that reasonable measurements found problems, not that all 
networks have problems all the time. We're not talking about average 
performance here, but rather the tail of the distribution. We can argue 
about whether we care about the 99th or 99.9th or whatever percentile. 
Since most measurements are, by their nature, short, even a single 
observed problem will likely put usability beyond many reasonable 
reliability requirements.

Since we may have different expectations, it might be helpful to get 
feedback on what people would consider reasonable reliability. Is it ok 
if 1% of calls fail (where "fail" may mean "sufficient disruption to 
cause users to abandon the call")? 0.1%? Even lower?

(As a side note, I suspect that plain reachability problems contribute 
the vast majority of "QoS" problems, something that DiffServ and kin are 
unlikely to fix. See the papers by Labovitz et al. on observed Internet 
reliability [e.g., UMich TR 382-98])

> 
> Thanks,
> 
> Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:34:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24555
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:34:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9Jas710772
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:36:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Jasv10769
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:36:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24543
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:34:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Ja3v10751;
	Sat, 9 Nov 2002 14:36:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9JZiv10707
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:35:44 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24525
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:33:08 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA9JYmXW011787;
	Sat, 9 Nov 2002 14:34:48 -0500 (EST)
Date: Sat, 9 Nov 2002 14:34:48 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211091934.gA9JYmXW011787@newdev.harvard.edu>
To: hgs@cs.columbia.edu, woody@pch.net
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Cc: ieprep@ietf.org
In-Reply-To: <Pine.GSO.4.44.0211091126050.4133-100000@paixhost.pch.net>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> I should have interpreted 0(100) as
> meaning the range 50-499,

crypto?

:-)

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 14:51:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24906
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 14:51:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9JriU11881
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 14:53:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Jriv11878
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 14:53:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24900
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 14:51:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Jm2v11778;
	Sat, 9 Nov 2002 14:48:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9Jlpv11757
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 14:47:51 -0500
Received: from brazilnut.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24851
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 14:45:14 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(user=hgs10 mech=PLAIN bits=0)
	by brazilnut.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gA9Jlhbj021319
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 9 Nov 2002 14:47:44 -0500 (EST)
Message-ID: <3DCD65E9.5020507@cs.columbia.edu>
Date: Sat, 09 Nov 2002 14:45:45 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott Bradner <sob@harvard.edu>
CC: gthom@delta-info.com, ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
References: <200211091533.gA9FXSfQ011026@newdev.harvard.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> as far the second issue:  I do not understand what SIP proxies etc would do
> differently if they were told that a call was an ieprep call - I expect
> that SIP servers/proxies etc will have plenty of processing capacity to
> deal with processing all SIP calling requests that they receive (I suppose
> the operator of a SIP network could decide to use old 33MHz 286 DOS
> machines for their SIP servers but aside from that possibility it does not
> seem realistic to think that SIP servers would need to pay attention to any
> ieprep indication in terms of avoiding overload.

This has been discussed a few times, but may be based on a somewhat 
limited view of what SIP proxies can do. I think a fair comparison is 
that a SIP proxy is in many ways similar to a web or email server. In 
particular, SIP proxies do execute per-call user code (sip-cgi, 
servlets, CPL, etc.), which can put a significant burden on any CPU. 
Also, a SIP proxy may need to consult an external database for call 
filtering (check for callee in "known telemarketers list") or AAA reasons.

Just like news web servers switched to static, non-image pages after 
9/11 to deal with the flash crowds, SIP servers may well decide to 
change their operating characteristics under call handling overload. 
This could involve no longer invoking CPU-intensive per-call processing 
tasks or reserving a certain request handling capacity to high-value 
calls. This is very similar to the remarks you made about networks 
earlier in your message, i.e., simple, absolute and unconstrained 
priority may not be sufficient.

Most of this can be done locally and without protocol support; in some 
cases, SIP signaling information may provide additional useful input 
into such algorithms.

In general, it might be helpful to differentiate (1) behavior that can 
be done locally based on already available information, (2) can use 
additional mechanisms to improve performance, and (3) absolutely needs 
additional protocol indications to make any sense.

> 
> The suggestion is made that admission policy could be loosened for
> emergency calls - this seems particularly risky in terms of providing
> opportunities for denial of service attacks - unless one postulates a
> totally reliable and unbreakable authentication mechanism for the users of
> ieprep services which users will reliability have with tem when they need
> to make an ieprep call.

There might be a wrinkle here that differentiates this from normal 
operation. For example, given other constraints, I may not care that 
somebody can break a key by one week computational brute force, since 
the emergency is likely to last much shorter than that.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 15:03:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24988
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 15:03:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9K61t12094
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 15:06:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9K61v12091
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 15:06:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24983
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 15:03:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9K54v12073;
	Sat, 9 Nov 2002 15:05:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9K4rv12052
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 15:04:53 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24975
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 15:02:16 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 15DFF67103; Sat,  9 Nov 2002 11:26:07 -0500 (EST)
Date: Sat, 9 Nov 2002 15:04:46 -0500
Subject: Re: [Ieprep] Measurement of Internet Congestion
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211091117590.4133-100000@paixhost.pch.net>
Message-Id: <7E9C82D5-F41E-11D6-849A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 9, 2002, at 14:23 America/Montreal, Bill Woodcock 
wrote:
> The slide-set from NANOG is at:

That helps with regards to the phones.

Are there other more generic presentations on congestion (or lack of it)
in real production networks that have been presented at ARIN/NANOG/RIPE
recently ?  Is there data that CAIDA has that is public enough to be
useful ?

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 15:05:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25015
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 15:05:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9K7iG12734
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 15:07:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9K7iv12731
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 15:07:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25009
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 15:05:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9K71v12177;
	Sat, 9 Nov 2002 15:07:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9K6hv12117
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 15:06:43 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25002
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 15:04:07 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id A918367103; Sat,  9 Nov 2002 11:27:57 -0500 (EST)
Date: Sat, 9 Nov 2002 15:06:36 -0500
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DCD627D.40904@cs.columbia.edu>
Message-Id: <C07E8868-F41E-11D6-849A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 9, 2002, at 14:31 America/Montreal, Henning 
Schulzrinne wrote:
> (As a side note, I suspect that plain reachability problems contribute 
> the vast majority of "QoS" problems, something that DiffServ and kin 
> are unlikely to fix. See the papers by Labovitz et al. on observed 
> Internet reliability [e.g., UMich TR 382-98])

This would not surprise me a bit.  And I suspect Bill will also agree 
with this.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 15:23:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25150
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 15:23:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9KPtC13133
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 15:25:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9KPtv13130
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 15:25:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25145
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 15:23:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9KP3v13099;
	Sat, 9 Nov 2002 15:25:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9KOjv13067
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 15:24:45 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25139
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 15:22:04 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gA9KEsd05707;
	Sat, 9 Nov 2002 12:14:54 -0800 (PST)
Date: Sat, 9 Nov 2002 12:14:54 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Henning Schulzrinne <hgs@cs.columbia.edu>, <ieprep@ietf.org>
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <C07E8868-F41E-11D6-849A-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211091211500.5607-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > On Saturday, Nov 9, 2002, at 14:31 America/Montreal, Henning
    > Schulzrinne wrote:
    > > (As a side note, I suspect that plain reachability problems contribute
    > > the vast majority of "QoS" problems, something that DiffServ and kin
    > > are unlikely to fix. See the papers by Labovitz et al. on observed
    > > Internet reliability [e.g., UMich TR 382-98])
    >
    > This would not surprise me a bit.  And I suspect Bill will also agree
    > with this.

Yes, agreed.  In general, what I and most other operators I know observed
while running QoS on production networks, was that it didn't help
anything, since there generally either existed an uncongested path, or no
path.  In the extrordinarily rare cases when congestion exists, it
typically exists because of some definite, temporary, intentional reason,
and QoS wouldn't change typical reasons.

QoS isn't a hammer you can use to force packets you think are important
through someone else's network.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 15:25:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25182
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 15:25:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9KRdF13191
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 15:27:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9KRdv13188
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 15:27:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25178
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 15:25:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9KR2v13171;
	Sat, 9 Nov 2002 15:27:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9KQVv13153
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 15:26:31 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25164
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 15:23:54 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gA9KQ4LI011967;
	Sat, 9 Nov 2002 15:26:04 -0500 (EST)
Date: Sat, 9 Nov 2002 15:26:04 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211092026.gA9KQ4LI011967@newdev.harvard.edu>
To: hgs@cs.columbia.edu, rja@extremenetworks.com
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Cc: ieprep@ietf.org
In-Reply-To: <3DCD627D.40904@cs.columbia.edu>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> Since most measurements are, by their nature, short, even a single 
> observed problem will likely put usability beyond many reasonable 
> reliability requirements.

I'd change "usability" to "recorded usability" - i.e., an observed 
problem on a short measurement my not be easily able to be translated into
what it actually would mean to VoIP users on the net - would the disruption
hit many of the users, would it hit for long enough to be a problem (i.e.
the hang up phone level)

not - not all tests are short or show major issues see
http://www.nanog.org/mtg-0105/casner.html

these tests were about a week long and at a reasonable speed
and they showed few problems - mostly rerouting timeouts

yes they were just within an ISP an did not deal with
tail circuits but even so can say someting about the base reliability
of some ISP backbones

VoIP users in this environment would see a few 300 sec or so outages a week
if they were quite unlucky to be calling when there was a routing funny

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 16:14:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25676
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 16:14:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA9LDAH15322
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 16:13:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9LDAv15319
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 16:13:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25646
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 16:10:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9LCBv15300;
	Sat, 9 Nov 2002 16:12:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA9LBfv15271
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 16:11:41 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25622
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 16:09:03 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 5EF5767103; Sat,  9 Nov 2002 12:32:55 -0500 (EST)
Date: Sat, 9 Nov 2002 16:11:33 -0500
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211091211500.5607-100000@paixhost.pch.net>
Message-Id: <D33BEEC9-F427-11D6-849A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 9, 2002, at 15:14 America/Montreal, Bill Woodcock 
wrote:
> Yes, agreed.  In general, what I and most other operators I know 
> observed
> while running QoS on production networks, was that it didn't help
> anything, since there generally either existed an uncongested path, or 
> no
> path.  In the extrordinarily rare cases when congestion exists, it
> typically exists because of some definite, temporary, intentional 
> reason,
> and QoS wouldn't change typical reasons.

	Maybe it would be informative if you outlined some examples of why
congestion might exist for a "definite, temporary, intentional reason".
Those might be obvious to you, but not necessarily as obvious to 
everyone.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 20:04:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27953
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 20:04:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAA177F24798
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 20:07:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA177v24795
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 20:07:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27949
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 20:04:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA11Gv24411;
	Sat, 9 Nov 2002 20:01:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA10ev24381
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 20:00:40 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27873
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 19:58:01 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 10 Nov 2002 00:55:01 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WM4F3M4X>; Sat, 9 Nov 2002 20:00:36 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D08@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'RJ Atkinson'" <rja@extremenetworks.com>, gthom@delta-info.com
Cc: Bill Woodcock <woody@pch.net>, ieprep@ietf.org, gthom@delta-info.com
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discus
	sion request]
Date: Sat, 9 Nov 2002 20:00:27 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ran,

When the 9/11 happened last year, the internet traffic was fine in general
according to you and others. Do you have any rough number on how much of it
was time-sensitive ( e.g., voiceIP, video, etc.) traffic? I guess the
percentage of time-sensitive must have been very little compared to
time-insensitive data traffic such as web, email, and others. My thinking is
when people surf the web or send an email, they don't care much if there are
congestions in the networks because they commonly accept it as the way the
internet works. But when it comes to voice traffic, it is a totally
different matter ( very noticeable as you and I experience it with the
cellular phone). This leads me to ask you, Bill, and others another
question: do you foresee that the Internet will be use to  transport most of
voice traffic and other time-sensitive applications and eventually will
replace POTS network because of its ubiquity? If the answer is "yes" then
the "future" Internet will have to carry much more time sensitive traffic
and congestions will be an issue. 

NCSs's mission is to ensure that communications are available during
emergency and crisis. We need to communicate with others when emergency
occurs. And when emergency happens in an area, traffic congestions are
likely to occur. So, without some sort of priority treatment for NS/EP
traffic, it's extremely hard for us to fulfill our mission.

Regards,

An


-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Friday, November 08, 2002 8:14 PM
To: gthom@delta-info.com
Cc: Bill Woodcock; ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 -
discussion request]



On Friday, Nov 8, 2002, at 16:28 America/Montreal, Gary Thom wrote:
> One thing to remember, is that we are really looking at operating under
> non-normal conditions. This may be due to an unusually high load or 
> with
> degraded capability. During an emergency, such as a huricane or 
> earthquake,
> not only will you have everyone trying to find out if their loved ones 
> are
> ok, but you may have loss of bandwidth or or other error conditions 
> due to
> damaged equipment, fiber, etc. In this situation, we want to give 
> emergency
> communications an advantage.

Gary,

	Would you consider 9/11/2001 to be "non-normal conditions" ?
As someone with a number of friends who work daily in the Pentagon,
and several parish members who died that day, I'd say that day was
pretty unusual.

	During that day, a few content providers had problems delivering
all the requested content.  In at least some cases, this was server
overload.  However, careful analysis of traffic logs by large ISPs
afterwards confirms that the Internet performed brilliantly.  Despite
fibre cuts in lower Manhatten and numerous environmental problems at
Hudson Street, the Internet automatically re-routed around the damage
and kept going.  And the large ISPs did NOT (repeat did NOT) start
dropping packets because of the cut fibres -- their backbones were
carefully over-engineered so the traffic was re-routed around the
lost links.

	Access to the US NASA feeds of the mars lander landing was a bigger
problem in Internet terms, yet even then the problems were on NASA's
access links and its servers, rather than in any large ISPs network.

	To me, the key thing is that the critical traffic gets through.
Saying that it must be "prioritised" implies a specific mechanism for
prioritisation.  It is better for us to focus on the real requirement
of the traffic getting through, than on specific mechanisms (in your 
words,
prioritisation) which might not be (probably aren't) needed, create new 
attack
vectors on the ISP network, and increase operational complexity.   There
is a significant body of evidence that a better (and lower-cost) 
approach
is to over-engineer the network so that the network simply can handle 
all
the offered load.

	I spent a fair bit of time yesterday talking with folks from major
ISPs.  One is a large inter-continental ISP with POPs located in 
Asia/Pacific,
North America, and Europe.  Another is based in Japan.  (etc.).  In
each case, they indicated that their backbone links are significantly
overprovisioned (max load << (50% link capacity)).  A typical number 
that
was mentioned was that links have a "max load" equal to 30-35% of link 
capacity.
They also noted that they have significant path diversity in their 
networks,
specifically including physical fibre path diversity.  This was 
originally
done as defence against back-hoe equipment, but it happens to work 
really
well during other kinds of natural/unnatural problems as well.  To give
another example, there was a fibre cut near Baltimore a while back.  It
cut several fibre bundles from different carriers.  The IP routing 
system
just automatically detected the link-down state and routed around the 
cut links
-- and there was enough spare capacity in the other links that there 
was no 
significant loss of service.

	Claims of the form "the Internet gets congested and drops packets
when an emergency happens" currently lack credibility, because they are
contrary to the measured, scientific data that we happen to have.  I'd
be much more inclined to take those claims seriously if someone would 
show
up with specific measured data about an actual incident.  And in that 
case,
it would be important to have enough specifics to actually sit down and
analyse precisely what happened -- without a great deal of detail this 
WG
is unlikely to correctly and clearly characterise the issue so that 
another
IETF WG to figure out what the correct protocol change(s) might be or 
for ISPs
to figure out which existing mechanisms might be candidates for broader
deployment.

	It would also be helpful if going forward we could clearly separate
our
sundry concerns into the different layers of the Internet Architecture 
(Physical,
Link, IP, Transport, Application).[1]

Ran
rja@extremenetworks.com

[1] The Internet Architecture is not identical to ISO OSI Model.  For 
example,
we have no Session Layer in the Internet.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 21:13:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29007
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 21:13:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAA2Fdo28681
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 21:15:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2Fdv28678
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 21:15:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29001
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 21:12:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2E1v28632;
	Sat, 9 Nov 2002 21:14:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2DBv28605
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 21:13:11 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28941
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 21:10:31 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Sat, 9 Nov 2002 20:13:03 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Date: Sat, 9 Nov 2002 20:13:02 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9AFFB@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Ieprep digest, Vol 1 #205 - 25 msgs
Thread-Index: AcKIJY07ZBSHRIW9QK+OQUmzgkiXWgANDdeg
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "RJ Atkinson" <rja@extremenetworks.com>,
        "Henning Schulzrinne" <hgs@cs.columbia.edu>
Cc: <ieprep@ietf.org>
X-OriginalArrivalTime: 10 Nov 2002 02:13:03.0027 (UTC) FILETIME=[B2F18030:01C2885E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAA2DCv28606
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> I'm not terribly impressed by a lot of the published papers 
> on Internet  measurement -- simply because in many cases the 
> measurement did not use enough  controls to  understand what 
> was really being measured.  
  I don't think, this is the case for measurement works. It is 
more common to simulation works, where topoplogy models doesn't
exactly reflect practical network scenarios. Even if thats the 
case, researchers are not to be blamed. They are forced to
anonymize the traces, which sometimes doesn't contain full 
details. Some of the important Server location problems remains
unsolved due to this factor . But, researchers still use heuristics
to find their way out. I know of works which can exactly tell the
places where akamai have kept their servers.
( One would not have imagined, people can find a topology of a
backbone without the help of the particular ISP..
http://www.cs.washington.edu/research/networking/rocketfuel/interactive/
Reason: BGP data/ whois servers are publicaly available.)

 
> There is some work by folks  at ICIR  on how hard it 
> really is to measure stuff accurately, for example.

  Your probably referring to vern's talk at NRDM. But, vern's
points were more addressed to sceintific process of measurements.
But, some of those concerns are presently being worked out within
IMRG.

> "three armchair theoreticians."
 Sorry ..But, SIP, RTP and many other things came from a research
lab only. So, it is mostly interdependent.


> Are there other more generic presentations on congestion (or lack of it)
> in real production networks that have been presented at ARIN/NANOG/RIPE
> recently ?  Is there data that CAIDA has that is public enough to be
> useful ?

Studying path properties is difficult for various reasons.. Understanding the
congestion nature( where? when? why? ..) are currenly underway. In a way, I am
also studying some of these path properties/traffic nature..

But, you can get some pointers from 
http://www.icir.org/models/
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 21:14:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29026
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 21:14:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAA2GE828721
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 21:16:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2GDv28718
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 21:16:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29021
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 21:13:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2C8v28560;
	Sat, 9 Nov 2002 21:12:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2Brv28529
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 21:11:53 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28930
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 21:09:12 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Sat, 9 Nov 2002 20:11:44 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Re: [Ieprep] architectural considerations
Date: Sat, 9 Nov 2002 20:11:43 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD4331610234EF84@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Re: [Ieprep] architectural considerations
Thread-Index: AcKIXoOBUyy7Ox00RkOxZ3OLrsPyYA==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "RJ Atkinson" <rja@extremenetworks.com>, "ieprep" <ieprep@ietf.org>
X-OriginalArrivalTime: 10 Nov 2002 02:11:44.0052 (UTC) FILETIME=[83DEDF40:01C2885E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAA2Brv28530
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

I addition to Ran's list, these are some recent 
additions, which  revisits some of the past architectural
design criteria...

---------------------------------------

Internet is now filled with people of conflicting interests which 
David Clark calls as "tussle in cyberspace"

Sorry..but ieprep community is a perfect example of people
with conflicting interests.

Telephone folks, pure VoIP, IP world, Distributed systems(IAA),
standardization organizations, operators, vendors, researchers&
students, and policy makers. 
although its common in other IETF groups too..

I request you all to read David Clark's recent work (from Newarch 
project), for how to make Internet function inspite of all these
conflicting tussles.

http://www.acm.org/sigs/sigcomm/sigcomm2002/papers/tussle.html

--------------------------------------------------

The recent IAB document is very important in knowing the current problems
in some working groups, which ieprep shouln't repeat..

particularly..

- Overloading ( e.g.. Since groups like MPLS are vendor driven, people try
to increase the waist line of architecture clock )

- complexity at various levels, anything on anything at various layers

- Lack of robustness due to minor problems ( e.g. misconfiguration in BGP)

- Butterfly effect ..local change leading to problems because of lack in global
 picture

- Scott Bradner's recent mail about architectural/business model concerns
 
and much more ...

http://www.ietf.org/internet-drafts/draft-iab-considerations-03.txt
( Sections relevant to ieprep:
    4.  Justifying the Solution
    6.  Long-term vs. Short-term Solutions
    7.  Looking at the whole picture vs. making a building block
    8.  Weighing architectural benefits against architectural costs
   10.  Avoiding Tragedy of the Commons
   11.  Balancing Competing Interests
   12.  Designing for Choice vs. Avoiding Unnecessary Complexity
   13.2.  Discussion: overloading
   14.  Internationalization
   15.  Deployability
 oops!!! ..but seems everything is relevant ..)


when this documented is updated next time, it should add a section on
"policy and labels".. a lesson from ieprep to other groups.


http://www.ietf.org/internet-drafts/draft-ymbk-arch-guidelines-05.txt
( Sections relevant to ieprep (Must for telephone folks):
    5. Packet versus Circuit Switching: Fundamental Differences
    6. The Myth of Over-Provisioning
    7. The Myth of Five Nines  )
----------------------------------------------------------------------

Other than that, if you have time/cycles get into:
http://www.ana.lcs.mit.edu/anaweb/papers.html
http://www.isi.edu/newarch/docs.html
http://www.icir.org/floyd/layers.html
http://www.icir.org/floyd/evolution.html
http://www.maoz.com/~dmm/complexity_and_the_internet/
http://netlab.caltech.edu/internet/
http://www.reed.com/dprpapers.html

-------------------------------------------------------------------





_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 21:15:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29054
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 21:15:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAA2I2828744
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 21:18:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2I2v28741
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 21:18:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29048
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 21:15:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2C6v28544;
	Sat, 9 Nov 2002 21:12:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2Bnv28524
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 21:11:49 -0500
Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28927
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 21:09:09 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Sat, 9 Nov 2002 20:11:40 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Date: Sat, 9 Nov 2002 20:11:39 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD4331610234EF83@KC-MAIL2.kc.umkc.edu>
Thread-Topic: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Thread-Index: AcKH8FAT2YKlcCUkTQmD2nQjVr748AAVlH7g
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "RJ Atkinson" <rja@extremenetworks.com>
Cc: <ieprep@ietf.org>
X-OriginalArrivalTime: 10 Nov 2002 02:11:40.0258 (UTC) FILETIME=[819BF420:01C2885E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAA2Bnv28525
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> > But, we should also remember that telephone networks are the major
> > ones to be affected. One of the major reason for the robustness of
> > Internet is the redundancy among ISP ( which is not the case in
> > PSTN network.) In NY area, verizon was the hot spot/congestion point
> > as all carriers junction at verizon.
> 
> Hmm.  Not sure what you mean by "carriers" and what you mean by 
> "verizon".
> "carrier" could mean either telephone company or ISP given 
> the preceding
> text.  Verizon is a firm, not a location.

Sorry for mis-interpreting the terms.

After a long search, I got the link..
Please go through 
http://www.merit.edu/mail.archives/nanog/2002-08/msg00131.html
http://www.nytimes.com/2002/08/06/nyregion/06TELE.html
>From the NY times article

" Telecommunications networks in Lower Manhattan remain vulnerable to 
major failures in the event of a disaster, even if it were to occur on a 
smaller scale than the World Trade Center attack, according to a report 
scheduled to be released today.The report, compiled by a group of downtown 
executives, concludes that a lack of redundant telephone and digital 
communication networks was a factor in the loss of telephone service to 
thousands of residents and businesses after the attack.
<snipped>
The report urges landlords and businesses to establish backup systems that 
would include a wireless network. It also encourages telephone carriers to 
set up systems that do not connect with the Verizon network, which provides 
most of the major communication links in the city.

Before Sept. 11, the report says, many of the 34,000 customers who would 
lose telephone and Internet service on the day of the attack were convinced 
they would not suffer a communications blackout in a major disaster because 
they did business with multiple carriers. 
But those customers did not realize that most of their lines, regardless of 
the carrier, ran through a Verizon central office on West Street that was 
damaged by the collapse of 7 World Trade Center.

Verizon operates the largest telephone and data communications network in 
the city. State deregulation has allowed competitors to enter the market, but 
most of those companies lease lines from Verizon, which means almost all the 
lines in the city run through the same conduits and switching offices. 
The report recommends that other carriers build large networks completely 
separate from Verizon's. One company, Con Ed Communications, has already 
installed a fiber optic telecommunications network in conduits controlled by 
its parent, Consolidated Edison Company. But most other competitors have said 
such a move would be too costly."

I guess, no one have seen the report till now..thats the good thing 
about press.



> > Although, failure analysis in BGP was well studied by 
> Ahuja/labovitz, 
> > it was
> > not done for intra-domain(link state) network ( as 
> reconvergence time 
> > is less
> > when compared to inter-domain.) But It is necessary to study them, 
> > both for
> > helping researchers/operators.
> 
> 	Inside an ISP, I-BGP is used internally in addition to 
> an IGP -- and 
> I-BGP
> is more significant to the convergence of the routing system as 
> perceived
> by customers/users.

This is an active area of research too.
 - studying the interaction of I-BGP and IS-IS 
 - Correlating I-BGP/IS-IS updates with routing dynamics(churn)
Actually, studying the difference in propagation behaviour of I-BGP 
and E-BGP will help in creating a better BGP. But, everything 
is speculative at present stage..

Coming to your observation, I don't know which is more
significant to convergence as perceived by an user. But,convergence
of IGP system is also important ( which they call as milli-second
convergence..) Especially  studying the impact of HELLO timers and 
route computation on IS-IS convergence...pkt design Alaettinoglu and 
van Jacobson worked on milli-second convergence sometime back.

> 	Several operators have defined both "service 
> availability" and "SLA".

I always have this doubt. Do people really see all this 5 9s
(availability) issue?


> > - Learning Objective functions for OSPF weight optimization
> >   ( helps researchers/operators)
> 
> Not clear what you mean by "Learning Objective functions".

I was referring to the objective function, which is used for
optimizing OSPF weights. Studying some of the failure cases will
throw light into service availability ( namely rate of failures 
and things.) This information may form the basis for indentifying
the "correct" objective function, which truely reflects the
network condition.

For example, ATT's Netscope does traffic engineering by optimizing
OSPF weights. They got the objective funtion by talking with their
network engineers..
(http://www.research.att.com/~jrex/papers/ieeecomm02.long.pdf
Look for the objective function listed in section 3.2. It was 
obtained on discussion with ATT backbone engineers.)

I guess, we had a discussion in e2e mailing list about this issue.



> > - Recently, alternate routing - In application layer, it is
> > feasible (TRIP ) but in Network layer, not possible in near future.
> 
> I do not understand your meaning.


Dynamic routing in application layer( TRIP) is feasible, while it
is not possible in Network layer(QoS routing) at present.



> 	And it would still help if we could get more specific, clear 
> documentation
> on the GETS-like or IEprep-like services in use or 
> contemplated for use 
> in
> countries other than US and JP.  

The IAA system will be very useful at times. We can even help
them standardize the meta-data records/querying&searching formats
to be used in a IAA distributed database. But, scalability of IAA 
system is still questionable.



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov  9 21:20:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29113
	for <ieprep-archive@odin.ietf.org>; Sat, 9 Nov 2002 21:20:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAA2McF28921
	for ieprep-archive@odin.ietf.org; Sat, 9 Nov 2002 21:22:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2Mcv28918
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 9 Nov 2002 21:22:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29104
	for <ieprep-web-archive@ietf.org>; Sat, 9 Nov 2002 21:19:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2M1v28891;
	Sat, 9 Nov 2002 21:22:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA2Lsv28871
	for <ieprep@optimus.ietf.org>; Sat, 9 Nov 2002 21:21:54 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29088
	for <ieprep@ietf.org>; Sat, 9 Nov 2002 21:19:14 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18AhjM-0003qG-00; Sat, 09 Nov 2002 21:21:44 -0500
Date: Sat, 9 Nov 2002 21:21:44 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: ieprep@ietf.org
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D08@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211092006530.14711-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] Dolby-quality cell phones versus IP telephony
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Sat, 9 Nov 2002, Nguyen, An wrote:
> My thinking is when people surf the web or send an email, they don't
> care much if there are congestions in the networks because they commonly
> accept it as the way the internet works.
[...]
> NCSs's mission is to ensure that communications are available during
> emergency and crisis. We need to communicate with others when emergency
> occurs. And when emergency happens in an area, traffic congestions are
> likely to occur. So, without some sort of priority treatment for NS/EP
> traffic, it's extremely hard for us to fulfill our mission.

My cell phone tends to drop calls, has annoying dropouts, and doesn't
work at all in my kitchen.  Is NCS's mission to make cell phones have
perfect stereo quality sound, work everywhere, under every possible
condition? From what I've read, the proposed cell phone priority system
does not include "improving" the quality of the cell phone system,
requiring carriers to make cell phones work under every conceivable
condition, as well as wireline phones, or any of the other wish list
items. Cell phones work about as well as cell phones work.

Then why expect anything different of IP telephony?

IP telephony will work about as well as IP telephony works.  Adding an
method for transporting the emergency flag data will not change the
quality of service during an emergency.

There may be conditions where a priority flag may be needed.  But without
real-life experience its difficult to know where the bottlenecks will be.
Bill Woodcock's INOC-DBA phones haven't really tested this condition yet.

Traditional wireline phone switches do not handle a large number of call
attempts from non-wireline sources such as cell phone or IP telephony
gateways well. Gateways tend to concentrate a lot of traffic in a few
limited connections. To keep the POTS switch from crashing, the gateways
may need to rate limit the number of call attempts on the near side.
When gateways are rate-limiting to protect the POTS network it creates a
blocking queue on the IP or Cellular side.  IP folks will recognize this
as the traditional Head Of Line Blocking problem.  IP folks have worked
hard to get rid of HOLB on the Internet, but we probably can't fix the
POTS system.

Is this a real problem? I don't know.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 04:06:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13477
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 04:06:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAA98k221906
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 04:08:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA98kv21903
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 04:08:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13474
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 04:06:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA97lv21866;
	Sun, 10 Nov 2002 04:07:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAA96wv21252
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 04:06:58 -0500
Received: from sparcticus.sysctl.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13465
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 04:04:14 -0500 (EST)
Received: from localhost (scott@localhost)
	by sparcticus.sysctl.net (8.10.1/8.10.1) with ESMTP id gAA95g411459;
	Sun, 10 Nov 2002 09:05:42 GMT
Date: Sun, 10 Nov 2002 09:05:41 +0000 (GMT)
From: Scott Madley <scott@xgcic.net>
X-X-Sender:  <scott@sparcticus.sysctl.net>
To: Sean Donelan <sean@donelan.com>
cc: "Nguyen, An" <nguyena@ncs.gov>, <ieprep@ietf.org>
Subject: Re: [Ieprep] Dolby-quality cell phones versus IP telephony
In-Reply-To: <Pine.GSO.4.44.0211092006530.14711-100000@clifden.donelan.com>
Message-ID: <Pine.BSO.4.33.0211100740510.17866-100000@sparcticus.sysctl.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



On Sat, 9 Nov 2002, Sean Donelan wrote:

> Traditional wireline phone switches do not handle a large number of call
> attempts from non-wireline sources such as cell phone or IP telephony
> gateways well. Gateways tend to concentrate a lot of traffic in a few
> limited connections. To keep the POTS switch from crashing, the gateways
> may need to rate limit the number of call attempts on the near side.
> When gateways are rate-limiting to protect the POTS network it creates a
> blocking queue on the IP or Cellular side.  IP folks will recognize this
> as the traditional Head Of Line Blocking problem.  IP folks have worked
> hard to get rid of HOLB on the Internet, but we probably can't fix the
> POTS system.

How so, and what is defined as a large number of call attempts?  While not
up to RBOC traffic levels, there are a few dedicated VoIP companies that
are pushing millions of calls a month onto the PSTN.  Port densities on
VoIP aren't exactly the greatest, so you actually tend to have a lot of
traffic on a lot of connections, spread out across alot of boxes.
Sound engineering also dictates that you'll have connections into several
different switches depending on the amount of traffic PSTN bound traffic
your pushing.

Gateways don't control access to the media, rather they just faciliatate
it.  Softswitches control access to the media, so there needs to be an
intelligent element within that determines who gets access and who gets
preempted during congestion conditions.  The underlying fact is there are
two elements which are critical to completing telephone calls,
availability of signalling (SS7) and availability of media (trunking)
irregardless of the network type.  If either isn't available your call
isn't going thru.

I'm slightly confused as to whether your talking about packet
rate-limiting or resource contention with the far-end (signalling)?  I've
yet to see a 5E crash from high-call volume (setup/teardown), I have however seen
them become useless due to signalling failures (hitting priority level 3
isn't fun).  Which brings up the question, is it better to setup the call
and lose a few packets, or ensure packet delivery but be unable to setup
the call?


Cheers
-Madley

>
> Is this a real problem? I don't know.
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 05:36:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14212
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 05:36:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAActV30038
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 05:38:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAActv30035
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 05:38:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14209
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 05:36:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAAc9v30006;
	Sun, 10 Nov 2002 05:38:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAAbNv29982
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 05:37:23 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14186
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 05:34:52 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18ApSz-0004CZ-00; Sun, 10 Nov 2002 05:37:21 -0500
Date: Sun, 10 Nov 2002 05:37:21 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: Scott Madley <scott@xgcic.net>
cc: "Nguyen, An" <nguyena@ncs.gov>, <ieprep@ietf.org>
Subject: Re: [Ieprep] Dolby-quality cell phones versus IP telephony
In-Reply-To: <Pine.BSO.4.33.0211100740510.17866-100000@sparcticus.sysctl.net>
Message-ID: <Pine.GSO.4.44.0211100510410.16141-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Sun, 10 Nov 2002, Scott Madley wrote:
> I'm slightly confused as to whether your talking about packet
> rate-limiting or resource contention with the far-end (signalling)?  I've
> yet to see a 5E crash from high-call volume (setup/teardown), I have however seen
> them become useless due to signalling failures (hitting priority level 3
> isn't fun).  Which brings up the question, is it better to setup the call
> and lose a few packets, or ensure packet delivery but be unable to setup
> the call?

You'll need to talk to the ATIS folks why network reliability of the PSTN
is impacted by large numbers of call-attempts from Next Generation
Networks.

http://www.atis.org/pub/clc/niif/issues/0189.doc


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 06:37:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14682
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 06:37:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAABd9a32336
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 06:39:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAABd9v32333
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 06:39:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14679
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 06:36:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAABc9v32309;
	Sun, 10 Nov 2002 06:38:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAABbEv32182
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 06:37:14 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14654
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 06:34:42 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Sun, 10 Nov 2002 06:37:05 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111006371020455
 ; Sun, 10 Nov 2002 06:37:10 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMF77ZKW>; Sun, 10 Nov 2002 06:36:57 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77930@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Scott Bradner '" <sob@harvard.edu>,
        "'hgs@cs.columbia.edu '" <hgs@cs.columbia.edu>,
        "'woody@pch.net '" <woody@pch.net>
Cc: "'ieprep@ietf.org '" <ieprep@ietf.org>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Date: Sun, 10 Nov 2002 06:37:10 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>> I should have interpreted 0(100) as
>> meaning the range 50-499,

>crypto?

I don't know, could be Big-O notation.

Maybe if f(n) is the number of users at time n then the assertion is there
are positive numbers c and N such that for all n >= N then

f(n) <= c*100.

Some people might consider this crypto. :-)

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 06:43:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14733
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 06:43:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAABjk732512
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 06:45:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAABjjv32509
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 06:45:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14727
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 06:43:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAABj1v32486;
	Sun, 10 Nov 2002 06:45:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAABi6v32456
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 06:44:06 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14721
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 06:41:34 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAABbhd15903;
	Sun, 10 Nov 2002 03:37:43 -0800 (PST)
Date: Sun, 10 Nov 2002 03:37:43 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: "'RJ Atkinson'" <rja@extremenetworks.com>, <gthom@delta-info.com>,
        <ieprep@ietf.org>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discus
 sion request]
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D08@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211100322150.5607-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 9 Nov 2002, Nguyen, An wrote:
    > When the 9/11 happened last year, the internet traffic was fine in general
    > according to you and others. Do you have any rough number on how much of it
    > was time-sensitive ( e.g., voiceIP, video, etc.) traffic? I guess the
    > percentage of time-sensitive must have been very little compared to
    > time-insensitive data traffic such as web, email, and others.

Correct.  Most traffic across many measurement points is peer-to-peer file
sharing.  Voice, video, and other time-sensitive traffic is a miniscule
and diminishing portion of the total, and that trend will likely continue.

    > My thinking is when people surf the web or send an email, they
    > don't care much if there are congestions in the networks because
    > they commonly accept it as the way the internet works.

Actually, I'd say that they don't care because it's not appreciable to
them.  People don't generally pay too much attention to a tenth of a
second here or there.

    > But when it comes to voice traffic, it is a totally different matter.

How so?  Please elaborate.  I'd say that people don't care about
congestion on the Internet when using VoIP because, like when using TCP,
it's unnoticable to humans without measurement tools.

    > (very noticeable as you and I experience it with the
    > cellular phone).

Agreed, congestion on the PSTN is very noticable, in that it results in a
failure to complete a call, or a dropped call.  That's the critical
failure of circuit switching, and one of the principal reasons it's being
deprecated.

    > This leads me to ask you, Bill, and others another
    > question: do you foresee that the Internet will be use to  transport most of
    > voice traffic and other time-sensitive applications and eventually will
    > replace POTS network because of its ubiquity?

Yes, I do believe that.  Although that's a _long_ ways off.  The dinosaurs
didn't die overnight.

    > If the answer is "yes" then the "future" Internet will have to
    > carry much more time sensitive traffic...

Yes, but it'll be a much more miniscure portion even than it is today.

    > ...and congestions will be an issue.

This seems to me to be a completely unsupported statement...  How are you
arriving at this conclusion?

    > NCSs's mission is to ensure that communications are available during
    > emergency and crisis.

You might want to come up with a new mission, then, since that one's
unachievable, whether by circuit switching or packet switching.

    > We need to communicate with others when emergency occurs.

Yes, of course.

    > And when emergency happens in an area, traffic congestions are
    > likely to occur.

Well, I can see how you'd draw that conclusion from looking at the PSTN...
The PSTN is incredibly fragile, and the slightest failure results in
problems which are very obvious to users.  However if you look at the
Internet, the effects that the types of things NCS is likely to call an
emergency have on it are relatively miniscule, and the visibility of those
effects to the users are still more miniscule.  So this hasn't proven to
be a problem area.  NATs, particularly those with dynamic outside
addresses, are a huge problem area, by contrast.  Those create a total
failure of connectivity, not an audio-quality degredation that's temporary
and beneath the threshold of noticability for users.

    > So, without some sort of priority treatment for NS/EP
    > traffic, it's extremely hard for us to fulfill our mission.

In fact, without traffic prioritization, it's _impossible_ for you to
fulfill your mission.  And _with_ traffic prioritization, it's impossible
to fulfill your mission.  This has to do with your definition of your
mission, not traffic prioritization.  I'm guessing that someone somewhere
in NCS has a more conservative statement of your mission which is actually
achievable, and is similarly orthoganal to traffic prioritization.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 06:53:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14830
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 06:53:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAABtuL00318
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 06:55:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAABtuv00315
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 06:55:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14824
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 06:53:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAABt2v32760;
	Sun, 10 Nov 2002 06:55:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAABsiv32723
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 06:54:44 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14812
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 06:52:12 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAABmhd16028;
	Sun, 10 Nov 2002 03:48:43 -0800 (PST)
Date: Sun, 10 Nov 2002 03:48:43 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Scott Madley <scott@xgcic.net>
cc: Sean Donelan <sean@donelan.com>, "Nguyen, An" <nguyena@ncs.gov>,
        <ieprep@ietf.org>
Subject: Re: [Ieprep] Dolby-quality cell phones versus IP telephony
In-Reply-To: <Pine.BSO.4.33.0211100740510.17866-100000@sparcticus.sysctl.net>
Message-ID: <Pine.GSO.4.44.0211100341400.5607-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sun, 10 Nov 2002, Scott Madley wrote:
    >> IP folks have worked hard to get rid of HOLB on the Internet, but
    >> we probably can't fix the POTS system.
    > How so, and what is defined as a large number of call attempts?

My experience with intra-PSTN-telco interconnects is admittedly quite
limited, but what of it that I've observed has been fairly heavily
dependent upon Nx chan-DS1 interconnects, at 24 call appearances each.  By
comparison, Internet peering connections are typically GigE, which,
running at 70% capacity, would carry about 65,000 call appearances each.

My experience with PSTN-to-VoIP interconnects is direct and current, and
I'm observing PSTN telcos doing Nx PRI handoffs at 23 call appearances
each, where N is typically not more than four.

    > The underlying fact is there are two elements which are critical to
    > completing telephone calls, availability of signalling (SS7)

Or SIP.

    > and availability of media (trunking) irregardless of the network
    > type.

Fortunately GigE is dirt cheap, which is why so much of the network is
getting built out of it nowadays.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 07:02:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14963
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 07:02:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAC4fg00566
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 07:04:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAC4fv00563
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 07:04:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14941
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 07:02:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAC41v00532;
	Sun, 10 Nov 2002 07:04:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAC3Fv00499
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 07:03:15 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14894
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 07:00:43 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAABvHd16106;
	Sun, 10 Nov 2002 03:57:17 -0800 (PST)
Date: Sun, 10 Nov 2002 03:57:17 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <D33BEEC9-F427-11D6-849A-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211100352510.5607-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 9 Nov 2002, RJ Atkinson wrote:
    > Maybe it would be informative if you outlined some examples of why
    > congestion might exist for a "definite, temporary, intentional reason".

- User site might be undergoing some sort of move or transition in which
temporary bottlenecks (temporary L2 bridge between old site and new site)
appear, across which things like routing packets and SMTP/IMAP need to
flow, but nothing else is deemed particularly important.

- User site might be hosting a webcast, and might want all available
bandwidth to go to a large number of fixed-size streams, with no bursty
interruptions.

- User site might be going bankrupt, and decrease tail-circuit size to
preserve cash.

- User site might be using aggregated dial-on-demand channels (ISDN,
satcom, et cetera) for their tail-circuit, and have very specific ideas
about what types of traffic may validly trigger the addition of channels.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 07:29:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15354
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 07:29:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAACVxN01743
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 07:31:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAACVwv01740
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 07:31:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15350
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 07:29:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAACV4v01709;
	Sun, 10 Nov 2002 07:31:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAACUuv01684
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 07:30:56 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15337
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 07:28:23 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Sun, 10 Nov 2002 07:30:34 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111007303910267
 ; Sun, 10 Nov 2002 07:30:39 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMF775JA>; Sun, 10 Nov 2002 07:30:26 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77932@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Bill Woodcock '" <woody@pch.net>, "'Nguyen, An '" <nguyena@ncs.gov>
Cc: "''RJ Atkinson' '" <rja@extremenetworks.com>,
        "'gthom@delta-info.com '" <gthom@delta-info.com>,
        "'ieprep@ietf.org '" <ieprep@ietf.org>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Date: Sun, 10 Nov 2002 07:30:39 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

 
>a more conservative 
>statement of your mission which is actually achievable, and is similarly >
orthoganal to traffic prioritization.

http://www.ncs.gov/ncs/html/EO12472.htm 

and

http://www.whitehouse.gov/news/releases/2001/10/20011016-12.html

"Sec. 11. National Communications System. Changes in technology are causing
the convergence of much of telephony, data relay, and internet
communications networks into an interconnected network of networks. The NCS
and its National Coordinating Center shall support use of telephony,
converged information, voice networks, and next generation networks for
emergency preparedness and national security communications functions
assigned to them in Executive Order 12472. All authorities and assignments
of responsibilities to departments and agencies in that order, including the
role of the Manager of NCS, remain unchanged except as explicitly modified
by this order. " 

offers insight into the mission of the NCS.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 08:27:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15938
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 08:27:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAADTxA04178
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 08:29:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADTxv04175
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 08:29:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15933
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 08:27:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADT9v04145;
	Sun, 10 Nov 2002 08:29:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADS9v04119
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 08:28:09 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15910
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 08:25:35 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 4BAA367103; Sun, 10 Nov 2002 04:49:33 -0500 (EST)
Date: Sun, 10 Nov 2002 08:28:05 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: "Nguyen, An" <nguyena@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D08@emshqs1.ncr.disa.mil>
Message-Id: <3E827F28-F4B0-11D6-B65C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] network congestion, VoIP, NCS contracting approach, etc.
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 9, 2002, at 20:00 America/Montreal, Nguyen, An wrote:
> When the 9/11 happened last year, the internet traffic was fine in 
> general
> according to you and others. Do you have any rough number on how much 
> of it
> was time-sensitive ( e.g., voiceIP, video, etc.) traffic?

I haven't seen any *good* measured statistics on which applications 
consume
what % of (packets, bytes) since I stopped working for an ISP.

> I guess the percentage of time-sensitive must have been very little 
> compared to
> time-insensitive data traffic such as web, email, and others. My 
> thinking is
> when people surf the web or send an email, they don't care much if 
> there are
> congestions in the networks because they commonly accept it as the way 
> the
> internet works.

Ah.   The measured data from 9/11 did measure potential congestion.  It 
was
miniscule inside the Internet.  The measured data indicates that there 
WERE
problems with server performance of some popular web servers; -- those 
content
providers ripped graphics off their web pages moving to HTML only, then
reconfigured/added servers, and eventually solved those content server 
issues
on that day.

> But when it comes to voice traffic, it is a totally
> different matter ( very noticeable as you and I experience it with the
> cellular phone).

I used inter-domain VoIP on the morning of 9/11 and did not experience
any problems.  Note that one end of that link was in the Reston area,
transiting MAE-East on its way to MAE-West, with the other end in 
Silicon
Valley.  That's only one sample, admittedly, but it is a sample that is
entirely consistent with the actual measured data on network behaviour
during 9/11.

If the Internet had broken on 9/11, which it emphatically did not (as
measured data clearly shows), then an argument to change the way ISPs
deploy their network might be more persuasive.  Since that did NOT 
happen,
there is very good reason to continue to use what clearly worked well
under unusual circumstances.   (Since it isn't broken, why change it.)

> This leads me to ask you, Bill, and others another
> question: do you foresee that the Internet will be use to  transport 
> most of
> voice traffic and other time-sensitive applications and eventually will
> replace POTS network because of its ubiquity?

I seriously doubt that the PSTN will ever be replaced by a VoIP network.
I think VoIP is more likely to be used within a campus or to build
relatively small-scale (compared with PSTN) intra-organisational 
cost-optimised
toll bypass.  And I think those campus phone switches will continue
to have traditional PSTN interfaces.  If nothing else, that will be 
needed
to contact folks who are off-the-VoIP-network (e.g. customers, mobile 
phone
users) and take incoming calls from the PSTN.

My employer uses VoIP and lease-lines to bypass long-distance toll 
charges
on some intra-company links, but we use a huge amount of PSTN also.  
The DoD's
AutoVON/DSN does the same (no VoIP, due to JCS directive, but private 
connectivity
for sure), yet DoD still uses a huge amount of PSTN.  So does GE's 
corporate
phone network.  Bypasses such as the one that GE built/uses have been 
around
for many many years, yet have not affected growth of the PSTN.

[Aside:	I'm aware of DISA's use of VoIP at Skyline and also that not all
residents of Skyline like it;  (ironic quote of the day from earlier in 
2002
from someone who works there:  "The beauty of VoIP is that when the 
data network
is down, one can't report the outage to the network support staff.")]

The PSTN has the advantage that it is overwhelmingly one application, 
voice,
which is well characterised and predictable, so it can (and does) 
optimise its
network design/deployment for that one application.

The Internet will never have the luxury of only supporting a single 
application
in that way, so the Internet will need to continue to have a different 
kind
of design approach.

> NCSs's mission is to ensure that communications are available during
> emergency and crisis. We need to communicate with others when emergency
> occurs. And when emergency happens in an area, traffic congestions are
> likely to occur. So, without some sort of priority treatment for NS/EP
> traffic, it's extremely hard for us to fulfill our mission.

Prioritisation is a mechanism.  The NCS mission, as you state, is to
ensure communications availability.  NCS ought not care which mechanism
is used, provided that communications remain available.

Over-provisioning is a different mechanism, commonly used today (max 
link
utilisation equal to 30% of link capacity is typical among the ISPs I 
was talking
with last Thursday),  to ensure that packets don't get lost in the 
network,
because it is cheaper than deploying something like DiffServ.  Other 
mechanisms
also exist.

[ASIDE:		So far, each time there has been a press release or article
claiming that ISP <x> has deployed DiffServ throughout its network, 
when I
have tracked down the facts of the matter it has turned out to be 
marketing
or press confusion unrelated to the actual operational network.  It 
would be
VERY helpful if any ISP would make a public presentation at NANOG/RIPE 
about
their deployment.  So if anyone is at such a place and is listening, 
please
consider making such a public presentation in detail.]

An alternative perspective is that NCS ought to focus on talking with 
ISPs about
contracts that have *performance-based* metrics for ensuring network 
availability,
rather than contracts that require particular mechanisms to be deployed
(whether or not those mechanisms work in a particular situation).

After all, as long as an ISP that has chosen to provide contracted 
services
to NCS can provide those services, why should NCS care which 
mechanism(s)
are used to provide those services ?

This alternative view is consistent with more recent USG contracting 
practices,
such as the USN outsourcing of its LANs to EDS, where EDS is given 
performance
metrics to achieve, but has total flexibility in how to meet those 
metrics.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 08:37:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16223
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 08:37:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAADe1q05086
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 08:40:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADe1v05083
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 08:40:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16220
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 08:37:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADd2v05034;
	Sun, 10 Nov 2002 08:39:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADaev04397
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 08:36:40 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16017
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 08:34:06 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id C0F5567107; Sun, 10 Nov 2002 04:58:04 -0500 (EST)
Date: Sun, 10 Nov 2002 08:36:36 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <A29143A40AEAE3459FF829D1DD4331610234EF83@KC-MAIL2.kc.umkc.edu>
Message-Id: <6F5742AA-F4B1-11D6-B65C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] last-mile connectivity, link-state optimisation, IAA, etc
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 9, 2002, at 21:11 America/Montreal, Ayyasamy, 
Senthilkumar (UMKC-Student) wrote:
> Before Sept. 11, the report says, many of the 34,000 customers who 
> would
> lose telephone and Internet service on the day of the attack were 
> convinced
> they would not suffer a communications blackout in a major disaster 
> because
> they did business with multiple carriers.
> But those customers did not realize that most of their lines, 
> regardless of
> the carrier, ran through a Verizon central office on West Street that 
> was
> damaged by the collapse of 7 World Trade Center.

This sounds like an issue where any RBOC has most of the last-mile 
connectivity
and that connectivity is normally concentrated in the RBOC's central 
office.

If that's a correct reading of the quoted text, one alternative is to 
use a
facilities-based CLEC (traditional US examples include MFNX, Yipes, 
Telseon)
and to ensure true path diversity.

[Aside:  The ISPs I was talking with last Thursday go to a lot of 
trouble
to ensure that they have true physical path diversity for their 
long-haul fibre.
Since those are facilities-based carriers, they have certain knowledge 
of where
their fibre runs.  Even so, there can be choke points.  See the 
Baltimore fibre
cut of a while back for one example of a choke point.]

> I was referring to the objective function, which is used for
> optimizing OSPF weights. Studying some of the failure cases will
> throw light into service availability ( namely rate of failures
> and things.) This information may form the basis for indentifying
> the "correct" objective function, which truely reflects the
> network condition.
>
> For example, ATT's Netscope does traffic engineering by optimizing
> OSPF weights. They got the objective funtion by talking with their
> network engineers..
> (http://www.research.att.com/~jrex/papers/ieeecomm02.long.pdf
> Look for the objective function listed in section 3.2. It was
> obtained on discussion with ATT backbone engineers.)

My impression has been that few ISPs actually optimise their link-state
routing weights (ISIS or OSPF).  My previous employer did do this.  It
worked well, but it is not trivial to get the weights right.

> Dynamic routing in application layer( TRIP) is feasible, while it
> is not possible in Network layer(QoS routing) at present.

I'm sure I don't understand that sentence.  Network-layer routing,
such as RIP/OSPF/ISIS/BGP is the epitome of dynamic routing.  That's
one of the main reasons the network behaved so well on 9/11.  You
must be meaning something different that I can't understand from
the above sentence.  Terribly sorry.


> The IAA system will be very useful at times. We can even help
> them standardize the meta-data records/querying&searching formats
> to be used in a IAA distributed database. But, scalability of IAA
> system is still questionable.

One can question anything.  What is your particular concern and what
is the basis for that concern ?

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 08:41:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16283
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 08:41:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAADhev05215
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 08:43:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADhev05212
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 08:43:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16278
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 08:41:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADh1v05196;
	Sun, 10 Nov 2002 08:43:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADgcv05178
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 08:42:38 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16264
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 08:40:04 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 452A067103; Sun, 10 Nov 2002 05:04:02 -0500 (EST)
Date: Sun, 10 Nov 2002 08:42:34 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9AFFB@KC-MAIL2.kc.umkc.edu>
Message-Id: <443B67D8-F4B2-11D6-B65C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] quality of measurement/simulation, reverse-engineering backbone topology
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 9, 2002, at 21:13 America/Montreal, Ayyasamy, 
Senthilkumar (UMKC-Student) wrote:

>> I'm not terribly impressed by a lot of the published papers
>> on Internet  measurement -- simply because in many cases the
>> measurement did not use enough  controls to  understand what
>> was really being measured.
>   I don't think, this is the case for measurement works. It is
> more common to simulation works, where topoplogy models doesn't
> exactly reflect practical network scenarios.

I would agree that most simulation work is much worse, but it
is the case in much of the published measurement work I've seen.

> Even if thats the case, researchers are not to be blamed.

I disagree on why researchers can't get good measurement.  I think the
main reason is (1) lack of good no-cost attachment points for 
measurement
devices and (2) lack of money to pay for a good attachment point at
an exchange.  There are exceptions of course.  RIPE probably has a good
data set.  I understand that someone else on this list is currently 
looking
at the RIPE data set to see what it shows.

> I know of works which can exactly tell the
> places where akamai have kept their servers.

A combination of routing traces and traffic analysis could yield that
kind of data pretty quickly, but it is orthogonal to whether the 
measurements
are accurate.

> ( One would not have imagined, people can find a topology of a
> backbone without the help of the particular ISP..

Many people reverse-engineer their provider's backbone topology 
regularly. :-)
I do it with my provider at my home pretty often. :-)

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 08:44:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16345
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 08:44:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAADl2R05353
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 08:47:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADl2v05350
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 08:47:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16335
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 08:44:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADk1v05284;
	Sun, 10 Nov 2002 08:46:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADjLv05265
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 08:45:21 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16311
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 08:42:47 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 66CA267103; Sun, 10 Nov 2002 05:06:46 -0500 (EST)
Date: Sun, 10 Nov 2002 08:45:18 -0500
Subject: Re: [Ieprep] Dolby-quality cell phones versus IP telephony
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: Scott Madley <scott@xgcic.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.BSO.4.33.0211100740510.17866-100000@sparcticus.sysctl.net>
Message-Id: <A632200E-F4B2-11D6-B65C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


There are multiple defintions of "gateway" in this conversation.
It would help if folks were more specific... :-)

Two Quick Examples:
	gateway == VoIP PBX with a T1 voice uplink to PSTN
	gateway == VoIP server inside the Internet to connect VoIP users


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 08:55:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16447
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 08:55:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAADvfW05615
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 08:57:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADvfv05612
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 08:57:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16441
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 08:55:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADq2v05498;
	Sun, 10 Nov 2002 08:52:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADpkv05481
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 08:51:46 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16398
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 08:49:13 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 0BBBB67103; Sun, 10 Nov 2002 05:13:12 -0500 (EST)
Date: Sun, 10 Nov 2002 08:51:44 -0500
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discus sion request]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211100322150.5607-100000@paixhost.pch.net>
Message-Id: <8C116A6E-F4B3-11D6-B65C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Sunday, Nov 10, 2002, at 06:37 America/Montreal, Bill Woodcock wrote:
>> But when it comes to voice traffic, it is a totally different matter.
>
> How so?  Please elaborate.  I'd say that people don't care about
> congestion on the Internet when using VoIP because, like when using 
> TCP,
> it's unnoticable to humans without measurement tools.

Bill,
	That depends A LOT on the vocoder.  Some vocoders are brittle and
will not provide intelligible speech if they encounter small amounts of
delay/jitter/pkt-loss.  Other vocoders are more robust in the same 
circumstance.
The latter are more sensible for use in VoIP systems.  ITU's set of
standard vocoders contain examples of both.

	And I think An is thinking about non-trivial amounts of congestion
(hypothetically) existing in the network, while you are thinking about
the (currently) trivial amounts of congestion in the network.  Different
implicit assumptions will yield different conclusions.

>> NCSs's mission is to ensure that communications are available during
>> emergency and crisis.
>
> You might want to come up with a new mission, then, since that one's
> unachievable, whether by circuit switching or packet switching.

	To be fair, GETS worked VERY well on 9/11/01.  To also be fair,
the demand for Iridium phones probably peaked on 9/12/01, so GETS
isn't and wasn't the only possible approach to continued connectivity.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 08:56:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16486
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 08:56:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAADwtB05664
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 08:58:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADwtv05661
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 08:58:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16473
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 08:56:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADw2v05644;
	Sun, 10 Nov 2002 08:58:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAADvKv05606
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 08:57:20 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16438
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 08:54:46 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id AEA5D67103; Sun, 10 Nov 2002 05:18:45 -0500 (EST)
Date: Sun, 10 Nov 2002 08:57:17 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211100341400.5607-100000@paixhost.pch.net>
Message-Id: <52D79E6F-F4B4-11D6-B65C-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] QoS & GigE
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Sunday, Nov 10, 2002, at 06:48 America/Montreal, Bill Woodcock wrote:
> Fortunately GigE is dirt cheap, which is why so much of the network is
> getting built out of it nowadays.

Most GigE products (from any mainstream vendor) will have some level of
support for 802.1P precedence.  Those that are also IP routers will
have some level of support for DiffServ as well.  Important details
of implementations DO vary from one vendor to another.  But it is
definitely the case that (some level of) equipment support for
DiffServ/IP ToS/802.1p is pretty common today.

And 10 GigE is very expensive today, primarily due to optics component
costs.  Those are coming down.  After some time period, 10 GigE
will become more affordable.  And 10 GigE products *mostly* have
support for the above as well (there are a larger number of
exceptions right now with 10 GigE, including at least one widely used
vendor's implementation).

What seems to be missing is the actual experience with large-scale
deployment of QoS in the WAN of an ISP.  As noted several times before,
RIPE/NANOG would probably love to see presentations from anyone with 
such
experience.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 10:33:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18324
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 10:33:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAFa3L09330
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 10:36:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAFa3v09327
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 10:36:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18315
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 10:33:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAFZKv09309;
	Sun, 10 Nov 2002 10:35:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAFYWv09282
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 10:34:32 -0500
Received: from dewberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18307
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 10:31:57 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(user=hgs10 mech=PLAIN bits=0)
	by dewberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gAAFYS5n029322
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sun, 10 Nov 2002 10:34:28 -0500 (EST)
Message-ID: <3DCE7C0C.5070504@cs.columbia.edu>
Date: Sun, 10 Nov 2002 10:32:28 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
References: <D33BEEC9-F427-11D6-849A-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

At least from my local operational experience, the three most common 
reasons for excessive losses and delays are:
(1) failure of one of our outbound circuits or router interfaces 
(Columbia has a "commodity" Internet connection and an Internet2 
connection, with automatic failover from I2 to "commodity", each OC-3)
(2) severe congestion on the peering link between Sprint (upstream 
provider of Applied Theory, the [prior-to-Chapter-7/11] ISP for 
Columbia) and AT&T;
(3) denial of service attack, either inbound or outbound.

Recently, (3) has been the most common, followed by (2) and one incident 
of (1).

I have the traces and mail to our NOC for examples for each :-)

RJ Atkinson wrote:
> 
> On Saturday, Nov 9, 2002, at 15:14 America/Montreal, Bill Woodcock wrote:
> 
>> Yes, agreed.  In general, what I and most other operators I know observed
>> while running QoS on production networks, was that it didn't help
>> anything, since there generally either existed an uncongested path, or no
>> path.  In the extrordinarily rare cases when congestion exists, it
>> typically exists because of some definite, temporary, intentional reason,
>> and QoS wouldn't change typical reasons.
> 
> 
>     Maybe it would be informative if you outlined some examples of why
> congestion might exist for a "definite, temporary, intentional reason".
> Those might be obvious to you, but not necessarily as obvious to everyone.
> 
> Ran
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 11:07:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18735
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 11:07:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAG9DR11103
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 11:09:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAG9Cv11100
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 11:09:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18732
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 11:06:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAG8Dv11068;
	Sun, 10 Nov 2002 11:08:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAG7uv11035
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 11:07:56 -0500
Received: from brazilnut.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18715
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 11:05:20 -0500 (EST)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(user=hgs10 mech=PLAIN bits=0)
	by brazilnut.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gAAG7pbj015701
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sun, 10 Nov 2002 11:07:52 -0500 (EST)
Message-ID: <3DCE83E0.5090908@cs.columbia.edu>
Date: Sun, 10 Nov 2002 11:05:52 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: "Nguyen, An" <nguyena@ncs.gov>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach,
 etc.
References: <3E827F28-F4B0-11D6-B65C-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> there is very good reason to continue to use what clearly worked well
> under unusual circumstances.   (Since it isn't broken, why change it.)

Except that almost none of the real-time load used the Internet that 
day, so that this doesn't tell us much should such load-shift occur.

> I seriously doubt that the PSTN will ever be replaced by a VoIP network.

This, I believe, depends on the definition of "replace". There are at 
least three possible versions of that:

- use the same commodity Internet for all voice traffic;
- use some form of VPN, possibly at L 2.5 (MPLS), so that you share 
facilities and 'switches', but have clear traffic separation;
- set up physically separate networks, at least at the wavelength layer.

We probably also need to distinguish between existing IXCs and LECs and 
greenfield deployments. For example, there is very strong interest in 
all-IP radio access networks for 3G and later wireless carriers. 
Similarly, there have been stories that when a carrier went into a new 
country (BT and Spain, I believe), they didn't bother with a CS network 
and used a (separate) IP network.

This does not mean that voice traffic will dominate Internet traffic. It 
would only do this if you moved all local calling traffic to the 
Internet. However, that makes life easier, since the impact of 
prioritization on the rest of the traffic, say, is much less if you 
rate-limit the high-priority traffic.

> I think VoIP is more likely to be used within a campus or to build
> relatively small-scale (compared with PSTN) intra-organisational 
> cost-optimised
> toll bypass.  And I think those campus phone switches will continue
> to have traditional PSTN interfaces.  If nothing else, that will be needed
> to contact folks who are off-the-VoIP-network (e.g. customers, mobile phone
> users) and take incoming calls from the PSTN.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 12:07:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19704
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 12:07:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAH96x13707
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 12:09:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAH95v13704
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 12:09:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19697
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 12:06:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAH8Av13681;
	Sun, 10 Nov 2002 12:08:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAH7Mv13612
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 12:07:22 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19662
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 12:04:47 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAAH1Md19359;
	Sun, 10 Nov 2002 09:01:22 -0800 (PST)
Date: Sun, 10 Nov 2002 09:01:22 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: ieprep@ietf.org
cc: "'Nguyen, An '" <nguyena@ncs.gov>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77932@mcl-its-exs01>
Message-ID: <Pine.GSO.4.44.0211100856360.16112-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sun, 10 Nov 2002, King, Kimberly  S. wrote:
    > "Sec. 11. National Communications System. Changes in technology are causing
    > the convergence of much of telephony, data relay, and internet
    > communications networks into an interconnected network of networks. The NCS
    > and its National Coordinating Center shall support use of telephony,
    > converged information, voice networks, and next generation networks for
    > emergency preparedness and national security communications functions
    > assigned to them in Executive Order 12472. All authorities and assignments
    > of responsibilities to departments and agencies in that order, including the
    > role of the Manager of NCS, remain unchanged except as explicitly modified
    > by this order. "

See, that's not nearly so bad as you guys were making it out to be.
Doesn't say one word about NCS being responsible for fixing the world's
problems, or eliminating backhoes, or anything even remotely similar.

And it's completely feasible.  I knew nobody with any political sense
would have let themselves get signed up for the responsibilities you guys
were claiming to have been stuck with.  See?  The world's not so bad.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 12:07:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19706
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 12:07:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAH96x13722
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 12:09:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAH96v13719
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 12:09:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19699
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 12:06:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAH85v13653;
	Sun, 10 Nov 2002 12:08:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAH3gv12712
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 12:03:42 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19647
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 12:01:07 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 2023D67103; Sun, 10 Nov 2002 08:25:07 -0500 (EST)
Date: Sun, 10 Nov 2002 12:03:37 -0500
Subject: Re: [Ieprep] network congestion, VoIP, etc.
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DCE83E0.5090908@cs.columbia.edu>
Message-Id: <5A715E34-F4CE-11D6-99FD-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Sunday, Nov 10, 2002, at 11:05 America/Montreal, Henning Schulzrinne 
wrote:

>> there is very good reason to continue to use what clearly worked well
>> under unusual circumstances.   (Since it isn't broken, why change it.)
>
> Except that almost none of the real-time load used the Internet that 
> day,
> so that this doesn't tell us much should such load-shift occur.

Very little of the PSTN load uses the Internet on any day, including 
that one.
I think the normal real-time load on the Internet (real-time is MUCH 
broader
than PSTN-like voice) was still present by and large (perhaps even a bit
more usage -- making outbound calls from Northern VA via PSTN was 
problematic
but dialing 4-digit extension to our other offices over IP worked fine;
guess which one I used more).

>> I seriously doubt that the PSTN will ever be replaced by a VoIP 
>> network.
>
> This, I believe, depends on the definition of "replace". There are at 
> least
> three possible versions of that:

Good catch.

> - use the same commodity Internet for all voice traffic;
> - use some form of VPN, possibly at L 2.5 (MPLS), so that you share 
> facilities and 'switches', but have clear traffic separation;
> - set up physically separate networks, at least at the wavelength 
> layer.

I think option (1) above won't ever happen.

With Option 2, I'd be surprised if such an MPLS approach did not also 
include
explicit bandwidth provisioning for the MPLS "circuits".  I don't see 
this
as likely to soon "replace" the PSTN.  I do think this will get used 
for some
private voice services (not PSTN).

Option 3 is essentially re-engineering the PSTN, rather than using the 
public
global Internet.  Ask the phone guys what they think; it seems 
counter-intuitive
to do this, but I'm not informed either way.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 13:38:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21401
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 13:38:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAIe6817164
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 13:40:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAIe6v17161
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 13:40:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21394
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 13:37:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAIcDv17079;
	Sun, 10 Nov 2002 13:38:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAIbHv17056
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 13:37:17 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21373
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 13:34:41 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Sun, 10 Nov 2002 13:37:03 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111013370818559
 ; Sun, 10 Nov 2002 13:37:08 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMF7798J>; Sun, 10 Nov 2002 13:36:55 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77934@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Bill Woodcock '" <woody@pch.net>, "'ieprep@ietf.org '" <ieprep@ietf.org>
Cc: "''Nguyen, An ' '" <nguyena@ncs.gov>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussionrequest]
Date: Sun, 10 Nov 2002 13:37:08 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>See, that's not nearly so bad as you guys were making it out to be.

Did you read http://www.ncs.gov/ncs/html/EO12472.htm ?

It includes the words

"(c) The NCS shall seek to ensure that a national telecommunications
infrastructure is developed which: 

...

(2) Is capable of satisfying priority telecommunications requirements under
all circumstances through use of commercial, government and privately owned
telecommunications resources; 

(3) Incorporates the necessary combination of hardness, redundancy,
mobility, connectivity, interoperability, restorability and security to
obtain, to the maximum extent practicable, the survivability of national
security and emergency preparedness telecommunications in all circumstances,
including conditions of crisis or emergency".

Notice the word "priority" in the segment "priority telecommunications
requirements".  I don't find a definition of priority in that document.
Priority also has a meaning associated with IP networks (e.g., terms like a
priority queue).  Have the two ideas been blended?

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 14:11:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21862
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 14:11:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAJDlI18309
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 14:13:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAJDlv18306
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 14:13:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21854
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 14:11:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAJD4v18288;
	Sun, 10 Nov 2002 14:13:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAJCLv18269
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 14:12:21 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21831
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 14:09:44 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Sun, 10 Nov 2002 13:12:15 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Sun, 10 Nov 2002 13:12:15 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9AFFD@KC-MAIL2.kc.umkc.edu>
Thread-Topic: last-mile connectivity, link-state optimisation, IAA, etc
Thread-Index: AcKIvjKqNe8uUIIaSluVIT1UxEtOWAAKj4Zw
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "RJ Atkinson" <rja@extremenetworks.com>
Cc: <ieprep@ietf.org>
X-OriginalArrivalTime: 10 Nov 2002 19:12:15.0811 (UTC) FILETIME=[14D7D130:01C288ED]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAAJCLv18270
Subject: [Ieprep] RE: last-mile connectivity, link-state optimisation, IAA, etc
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> > I was referring to the objective function, which is used for
> > optimizing OSPF weights. Studying some of the failure cases will
> > throw light into service availability ( namely rate of failures
> > and things.) This information may form the basis for indentifying
> > the "correct" objective function, which truely reflects the
> > network condition.
> >
> > For example, ATT's Netscope does traffic engineering by optimizing
> > OSPF weights. They got the objective funtion by talking with their
> > network engineers..
> > (http://www.research.att.com/~jrex/papers/ieeecomm02.long.pdf
> > Look for the objective function listed in section 3.2. It was
> > obtained on discussion with ATT backbone engineers.)
> 
> My impression has been that few ISPs actually optimise their 
> link-state
> routing weights (ISIS or OSPF).
your correct.. Even if they do, it is done only when a new router is
added to the network or during a maintenance window. Other major
assumption is that the network is over-provisioned.

> >  Dynamic routing in application layer( TRIP) is feasible, while it
> > is not possible in Network layer(QoS routing) at present.
> I'm sure I don't understand that sentence.  

I was mentioning about the alternate path routing. While BGP/OSPF are 
dynamic, it is no so dynamic as QoS routing. QoS routing
is an alternative, but is not currently feasible. 

https://www1.ietf.org/mail-archive/working-groups/ieprep/current/msg00789.html
https://www1.ietf.org/mail-archive/working-groups/ieprep/current/msg00793.html
https://www1.ietf.org/mail-archive/working-groups/ieprep/current/msg00831.html


> 
> 
> > The IAA system will be very useful at times. We can even help
> > them standardize the meta-data records/querying&searching formats
> > to be used in a IAA distributed database. But, scalability of IAA
> > system is still questionable.
> 
> One can question anything.  
> what  is the basis for that concern ?

http://www.isoc.org/inet2000/cdproceedings/8l/8l_3.htm and the reference
quoted in that isoc presentation.

> What is your particular concern 

while i think that such a system will be useful,their needs to be lot of
work to be done before such a system is depolyed widely..

- Make it more scalable.
- Architecture changes ( A peer to peer based solution will make the system
robust, scalable and authentic to use.)
- need for querying/searching formats (making it light weight)
- need for Meta-data entries standardization.
- lack of Load balancing 
- lack of Proximity routing/ topology-aware techniques
 I can list more concerns but these are the main problems with that system.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 14:50:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22923
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 14:50:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAJq8C19727
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 14:52:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAJq8v19724
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 14:52:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22919
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 14:49:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAJp8v19696;
	Sun, 10 Nov 2002 14:51:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAJokv19677
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 14:50:46 -0500
Received: from mail1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22908
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 14:48:09 -0500 (EST)
Received: from bgreenew2k (dhcp-10-24-19-69.cisco.com [10.24.19.69]) by mail1.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA22357; Sun, 10 Nov 2002 11:50:30 -0800 (PST)
Reply-To: <bgreene@cisco.com>
From: "Barry Raveendran Greene" <bgreene@cisco.com>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>,
        "'Bill Woodcock '" <woody@pch.net>, <ieprep@ietf.org>
Cc: "''Nguyen, An ' '" <nguyena@ncs.gov>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussionrequest]
Date: Sun, 10 Nov 2002 11:50:26 -0800
Message-ID: <LNEHJBNJAPFNLEGJHCPEEEELKCAA.bgreene@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77934@mcl-its-exs01>
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



>
> "(c) The NCS shall seek to ensure that a national telecommunications
> infrastructure is developed which:

We do not have "national" boundaries on the Internet. We have AS boundaries.
So perhaps there is a mismatch of expectations. IETF has to think of the
Internet. NCS has to think of US interest. Sometimes the agenda can match.
Sometimes they cannot.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 15:07:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23056
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 15:07:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAK9n420667
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 15:09:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAK9nv20664
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 15:09:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23053
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 15:07:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAK42v19949;
	Sun, 10 Nov 2002 15:04:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAK3Dv19923
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 15:03:13 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23014
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 15:00:36 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAAJvBd21235;
	Sun, 10 Nov 2002 11:57:11 -0800 (PST)
Date: Sun, 10 Nov 2002 11:57:11 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
cc: "'ieprep@ietf.org '" <ieprep@ietf.org>,
        "''Nguyen, An ' '" <nguyena@ncs.gov>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 -
 discussionrequest]
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77934@mcl-its-exs01>
Message-ID: <Pine.GSO.4.44.0211101155180.16112-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sun, 10 Nov 2002, King, Kimberly  S. wrote:
    > (2) Is capable of satisfying priority telecommunications requirements under
    > all circumstances

Ouch.  So did they leave themselves a loophole in the definition of
requirements?  Or is one of the requirements that calls be completed?

    > obtain, to the maximum extent practicable, the survivability
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Good, somebody was thinking clearly.


                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 15:19:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23396
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 15:19:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAKL9S20900
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 15:21:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAKL9v20897
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 15:21:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23383
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 15:18:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAKK6v20873;
	Sun, 10 Nov 2002 15:20:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAKJrv20817
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 15:19:53 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23377
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 15:17:15 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Sun, 10 Nov 2002 14:19:47 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discus sion request]
Date: Sun, 10 Nov 2002 14:19:46 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9AFFF@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Ieprep digest, Vol 1 #207 - 13 msgs
Thread-Index: AcKIvUbVO7wcR+7cSX204SUxeo7xBAANVMMw
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Bill Woodcock" <woody@pch.net>, "Nguyen, An" <nguyena@ncs.gov>
Cc: "RJ Atkinson" <rja@extremenetworks.com>, <gthom@delta-info.com>,
        <ieprep@ietf.org>
X-OriginalArrivalTime: 10 Nov 2002 20:19:47.0300 (UTC) FILETIME=[83B7FA40:01C288F6]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAAKJrv20818
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


>     > When the 9/11 happened last year, the internet traffic was fine in general
>     > according to you and others. Do you have any rough  number on how much of it
>     > was time-sensitive ( e.g., voiceIP, video, etc.)  traffic? I guess the
>     > percentage of time-sensitive must have been very little  compared to
>     > time-insensitive data traffic such as web, email, and others.
> 
> Correct.  Most traffic across many measurement points is 
> peer-to-peer file
> sharing.  

  But, you can see change in trend in coming years. Many Universities 
have sent warning to students for copy-right infringement. But, it is 
difficult to identify inbound ports which host peer servers. But, various 
kind of resource management/accountability techniques (making students 
accountable and micro-payments etc..) will help mitigate this situation. 



>     > My thinking is when people surf the web or send an email, they
>     > don't care much if there are congestions in the networks because
>     > they commonly accept it as the way the internet works.
> 
> Actually, I'd say that they don't care because it's not appreciable to
> them.  People don't generally pay too much attention to a tenth of a
> second here or there.


  I have a question. Big corporations have long been prioritizing 
their ERP/business related traffic. So, why can't the same techniques be
used for giving preference to emergency traffic too?

> 
>     > But when it comes to voice traffic, it is a totally  different matter.
> 
> How so?  Please elaborate.  I'd say that people don't care about
> congestion on the Internet when using VoIP because, like when 
> using TCP,
> it's unnoticable to humans without measurement tools.

  Its a general requirement from the IETF that new protocols be congestion
aware ( RFC 2914.) With the advent of online games like quake, it is very
important to make them congestion-aware. So, either use TCP, or SCTP/DCCP
or UDP with your own congestion-aware schemes(but IETF should accept that 
scheme.)
 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 16:05:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24162
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 16:05:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAL81x22915
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 16:08:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAL81v22912
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 16:08:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24053
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 16:05:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAL7Jv22869;
	Sun, 10 Nov 2002 16:07:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAL6hv22256
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 16:06:43 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23983
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 16:04:05 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Sun, 10 Nov 2002 15:06:37 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Sun, 10 Nov 2002 15:06:36 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9B000@KC-MAIL2.kc.umkc.edu>
Thread-Topic: quality of measurement/simulation, reverse-engineering backbone topology
Thread-Index: AcKIvwdnVN8b6L7ATqSesr+Xq1quGgAPMZgg
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "RJ Atkinson" <rja@extremenetworks.com>
Cc: <ieprep@ietf.org>
X-OriginalArrivalTime: 10 Nov 2002 21:06:37.0381 (UTC) FILETIME=[0EA84F50:01C288FD]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAAL6hv22257
Subject: [Ieprep] RE: quality of measurement/simulation, reverse-engineering backbone topology
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> >> I'm not terribly impressed by a lot of the published papers
> >> on Internet  measurement -- simply because in many cases the
> >> measurement did not use enough  controls to  understand what
> >> was really being measured.
> >   I don't think, this is the case for measurement works. It is
> > more common to simulation works, where topoplogy models doesn't
> > exactly reflect practical network scenarios.
> 
> I would agree that most simulation work is much worse, but it
> is the case in much of the published measurement work I've seen.
> 
> > Even if thats the case, researchers are not to be blamed.
> 
> I disagree on why researchers can't get good measurement.  I think the
> main reason is (1) lack of good no-cost attachment points for 
> measurement  devices and (2) lack of money to pay for a good attachment point at
> an exchange.  
  Lack of geographical distribution in placing the Monitors is also one of the 
reason. Traffic characterization across networks in Asia and other parts are not 
well studied except for some studies from caida and Stanford SLAC ( which is 
drastly outdated.) 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 17:32:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25603
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 17:32:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAMYsp26273
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 17:34:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAMYsv26270
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 17:34:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25600
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 17:32:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAMYAv26254;
	Sun, 10 Nov 2002 17:34:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAMXJv26233
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 17:33:19 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25522
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 17:30:40 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18B0dk-0004IU-00; Sun, 10 Nov 2002 17:33:12 -0500
Date: Sun, 10 Nov 2002 17:33:12 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
cc: ieprep@ietf.org
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discus
 sion request]
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9AFFF@KC-MAIL2.kc.umkc.edu>
Message-ID: <Pine.GSO.4.44.0211101642380.16499-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Sun, 10 Nov 2002, Ayyasamy, Senthilkumar  (UMKC-Student) wrote:
>   I have a question. Big corporations have long been prioritizing
> their ERP/business related traffic. So, why can't the same techniques be
> used for giving preference to emergency traffic too?

Enterprises pre-define their business related traffic and statically
configure their network. Enterprises are less concerned about
discriminating against non-favored traffic on their internal networks
because everything is "owned" by a single organization.  A bank might
favor financial transaction traffic on its enterprise network, but a
hospital might favor patient medical traffic on its enterprise network.
If we don't care about making things worse for non-favored traffic and
know which traffic to favor, we could use the same techniques.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 17:51:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26172
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 17:51:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAAMrxU27330
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 17:53:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAMrwv27327
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 17:53:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26168
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 17:51:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAMr6v27307;
	Sun, 10 Nov 2002 17:53:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAAMqlv27251
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 17:52:47 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26145
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 17:50:08 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18B0wa-0004Ih-00; Sun, 10 Nov 2002 17:52:40 -0500
Date: Sun, 10 Nov 2002 17:52:40 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: Bill Woodcock <woody@pch.net>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Dolby-quality cell phones versus IP telephony
In-Reply-To: <Pine.GSO.4.44.0211100341400.5607-100000@paixhost.pch.net>
Message-ID: <Pine.GSO.4.44.0211101734400.16499-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Sun, 10 Nov 2002, Bill Woodcock wrote:
> My experience with intra-PSTN-telco interconnects is admittedly quite
> limited, but what of it that I've observed has been fairly heavily
> dependent upon Nx chan-DS1 interconnects, at 24 call appearances each.  By
> comparison, Internet peering connections are typically GigE, which,
> running at 70% capacity, would carry about 65,000 call appearances each.

As I understand the problem, its not the number of calls which is limited
by the trunking capacity, but the number of call attempts and not
implementing congestion controls on the NGN side.  Its like when concert
tickets go on sale in a major city, and everyone starts calling the box
office at the same time swamping the PSTN.  Even though 99% of the calls
don't go through, the call attempts still disrupt PSTN service elsewhere.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 18:36:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26795
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 18:36:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAANd4A29313
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 18:39:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAANd3v29310
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 18:39:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26792
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 18:36:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAANc9v29287;
	Sun, 10 Nov 2002 18:38:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAANbMv29253
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 18:37:22 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26712
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 18:34:44 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 2E0F567103; Sun, 10 Nov 2002 14:58:47 -0500 (EST)
Date: Sun, 10 Nov 2002 18:37:14 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9AFFD@KC-MAIL2.kc.umkc.edu>
Message-Id: <57531518-F505-11D6-B36B-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Re: last-mile connectivity, link-state optimisation, IAA, etc
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Sunday, Nov 10, 2002, at 14:12 America/Montreal, Ayyasamy, 
Senthilkumar (UMKC-Student) wrote:
>>> The IAA system will be very useful at times. We can even help
>>> them standardize the meta-data records/querying&searching formats
>>> to be used in a IAA distributed database. But, scalability of IAA
>>> system is still questionable.
>>
>> One can question anything.
>> what  is the basis for that concern ?
>
> http://www.isoc.org/inet2000/cdproceedings/8l/8l_3.htm and the 
> reference
> quoted in that isoc presentation.

I have trouble extrapolating a particular "scalability" issue about
IAA from that INET conference presentation.  Seems to me that they
are making good progress on scaling and haven't hit any wall so far.

>> What is your particular concern
>
> while i think that such a system will be useful,their needs to be lot 
> of
> work to be done before such a system is depolyed widely..
>
> - Make it more scalable.
> - Architecture changes ( A peer to peer based solution will make the 
> system
> robust, scalable and authentic to use.)
> - need for querying/searching formats (making it light weight)
> - need for Meta-data entries standardization.
> - lack of Load balancing
> - lack of Proximity routing/ topology-aware techniques
>  I can list more concerns but these are the main problems with that 
> system.

I don't think those things are necessarily necessary for IAA,
based on their experience to date (from public reporting via
the published literature and talking with individuals with WIDE).
Now that is not to say that some of the above aren't nice optimisations,
just that they don't seem obviously *necessary* for IAA to work 
adequately

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 18:59:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27028
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 18:59:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAB025A29774
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 19:02:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB025v29771
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 19:02:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27021
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 18:59:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAANu2v29658;
	Sun, 10 Nov 2002 18:56:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAANtov29642
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 18:55:50 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27003
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 18:53:12 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Sun, 10 Nov 2002 17:55:42 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Sun, 10 Nov 2002 17:55:42 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9B001@KC-MAIL2.kc.umkc.edu>
Thread-Topic: last-mile connectivity, link-state optimisation, IAA, etc
Thread-Index: AcKJEhqn4ZWkTCEZS2238jxY8G6ScAAAL78Q
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "RJ Atkinson" <rja@extremenetworks.com>
Cc: <ieprep@ietf.org>
X-OriginalArrivalTime: 10 Nov 2002 23:55:42.0557 (UTC) FILETIME=[ADA750D0:01C28914]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAANttv29643
Subject: [Ieprep] RE: last-mile connectivity, link-state optimisation, IAA, etc
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> >>> The IAA system will be very useful at times. We can even help
> >>> them standardize the meta-data records/querying&searching formats
> >>> to be used in a IAA distributed database. But, scalability of IAA
> >>> system is still questionable.
> >>
> >> One can question anything.
> >> what  is the basis for that concern ?
> >
> > http://www.isoc.org/inet2000/cdproceedings/8l/8l_3.htm and the 
> > reference
> > quoted in that isoc presentation.
> 
> I have trouble extrapolating a particular "scalability" issue about
> IAA from that INET conference presentation. 

 while they have done some disaster drills, I couldn't exactly figure
out the factors used for calibration( as it is in japanese 
language.) Scalability is one of the major factor which has to be 
studied for such kind of Database. As you have conversed with WIDE 
folks, you might be the better judge.


> > - need for Meta-data entries standardization.
> 
> I don't think those things are necessarily necessary for IAA,
> based on their experience to date (from public reporting via
> the published literature and talking with individuals with WIDE).

Meta-data entries standardization is important.
The fields in http://www.iaa.wide.ad.jp/DB/IAA-1998/ENGLISH/registry.html
doesn't seem to represent full details. Such standardization will help to 
educate community on what to enter in-priori.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 19:01:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27117
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 19:01:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAB03or29832
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 19:03:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB03ov29829
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 19:03:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27073
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 19:01:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB033v29810;
	Sun, 10 Nov 2002 19:03:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB02Iv29786
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 19:02:18 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27025
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 18:59:40 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAANuCd24745;
	Sun, 10 Nov 2002 15:56:13 -0800 (PST)
Date: Sun, 10 Nov 2002 15:56:12 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: RJ Atkinson <rja@extremenetworks.com>, "Nguyen, An" <nguyena@ncs.gov>,
        ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach,
 etc.
In-Reply-To: <3DCE83E0.5090908@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211101554550.16112-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sun, 10 Nov 2002, Henning Schulzrinne wrote:
    > This does not mean that voice traffic will dominate Internet traffic.
    > It would only do this if you moved all local calling traffic to the
    > Internet.

Mmm, no, wouldn't do it then, either.  The global volume of calls is
infinitesmally tiny relative to Internet traffic.  Dumping all of it on
the Internet wouldn't make any appreciable difference to the Internet.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 19:06:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27159
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 19:06:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAB093v30508
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 19:09:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB093v30505
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 19:09:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27156
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 19:06:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB082v30482;
	Sun, 10 Nov 2002 19:08:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB076v30085
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 19:07:06 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27147
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 19:04:28 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAB00xd24811;
	Sun, 10 Nov 2002 16:00:59 -0800 (PST)
Date: Sun, 10 Nov 2002 16:00:59 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
cc: "Nguyen, An" <nguyena@ncs.gov>, RJ Atkinson <rja@extremenetworks.com>,
        <gthom@delta-info.com>, <ieprep@ietf.org>
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discus
 sion request]
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9AFFF@KC-MAIL2.kc.umkc.edu>
Message-ID: <Pine.GSO.4.44.0211101558250.16112-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sun, 10 Nov 2002, Ayyasamy, Senthilkumar  (UMKC-Student) wrote:
    >> Most traffic across many measurement points is peer-to-peer file
    >> sharing.
    > But, you can see change in trend in coming years. Many Universities
    > have sent warning to students for copy-right infringement.

Which has no appreciable effect on the growth of peer-to-peer file sharing
as a fraction of the total.  The growth rate will obviously taper off as
it nears 100%, since everything else won't go away, by any means, and
eventually some new fad will take its place, but we don't know what
that'll be, or when.  So no, I can't see a change in the trend in coming
years.  I can only surmise that there'll be one eventually, and that it
won't mean less traffic, since it never does.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 20:56:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28560
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 20:56:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAB1wC902435
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 20:58:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB1wBv02432
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 20:58:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28540
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 20:55:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB1vGv02391;
	Sun, 10 Nov 2002 20:57:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB1uBv02357
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 20:56:11 -0500
Received: from mtiwmhc13.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28534
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 20:53:32 -0500 (EST)
Received: from cs.columbia.edu ([12.85.1.198])
          by mtiwmhc13.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP
          id <20021111015602.EVTW24110.mtiwmhc13.worldnet.att.net@cs.columbia.edu>;
          Mon, 11 Nov 2002 01:56:02 +0000
Message-ID: <3DCF0DBB.2040508@cs.columbia.edu>
Date: Sun, 10 Nov 2002 20:54:03 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Woodcock <woody@pch.net>
CC: RJ Atkinson <rja@extremenetworks.com>, "Nguyen, An" <nguyena@ncs.gov>,
        ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach,
 etc.
References: <Pine.GSO.4.44.0211101554550.16112-100000@paixhost.pch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Indications are that this is a common misperception. Read Odlyzko's 
papers on the topic for an attempt to estimate Internet traffic; local 
US call volume is a well-known quantity (see FCC documents). If you have 
a better estimate of Internet traffic volume, please provide a reference.

Bill Woodcock wrote:
>       On Sun, 10 Nov 2002, Henning Schulzrinne wrote:
>     > This does not mean that voice traffic will dominate Internet traffic.
>     > It would only do this if you moved all local calling traffic to the
>     > Internet.
> 
> Mmm, no, wouldn't do it then, either.  The global volume of calls is
> infinitesmally tiny relative to Internet traffic.  Dumping all of it on
> the Internet wouldn't make any appreciable difference to the Internet.
> 
>                                 -Bill
> 
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 10 21:18:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28884
	for <ieprep-archive@odin.ietf.org>; Sun, 10 Nov 2002 21:18:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAB2Ku803580
	for ieprep-archive@odin.ietf.org; Sun, 10 Nov 2002 21:20:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB2Kuv03577
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 21:20:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28872
	for <ieprep-web-archive@ietf.org>; Sun, 10 Nov 2002 21:18:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB2K4v03535;
	Sun, 10 Nov 2002 21:20:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB2JOv03483
	for <ieprep@optimus.ietf.org>; Sun, 10 Nov 2002 21:19:24 -0500
Received: from mtiwmhc13.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28846
	for <ieprep@ietf.org>; Sun, 10 Nov 2002 21:16:44 -0500 (EST)
Received: from cs.columbia.edu ([12.85.1.198])
          by mtiwmhc13.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP
          id <20021111021914.FIIH24110.mtiwmhc13.worldnet.att.net@cs.columbia.edu>
          for <ieprep@ietf.org>; Mon, 11 Nov 2002 02:19:14 +0000
Message-ID: <3DCF132C.70804@cs.columbia.edu>
Date: Sun, 10 Nov 2002 21:17:16 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach,
 etc.
References: <Pine.GSO.4.44.0211101554550.16112-100000@paixhost.pch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

FWIW, http://www.cs.columbia.edu/~hgs/internet/traffic.html has some 
data sources.

Bill Woodcock wrote:
>       On Sun, 10 Nov 2002, Henning Schulzrinne wrote:
>     > This does not mean that voice traffic will dominate Internet traffic.
>     > It would only do this if you moved all local calling traffic to the
>     > Internet.
> 
> Mmm, no, wouldn't do it then, either.  The global volume of calls is
> infinitesmally tiny relative to Internet traffic.  Dumping all of it on
> the Internet wouldn't make any appreciable difference to the Internet.
> 
>                                 -Bill
> 
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 02:27:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12786
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 02:27:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAB7TrM25149
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 02:29:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB7Trv25146
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 02:29:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12774
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 02:27:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB7T9v25124;
	Mon, 11 Nov 2002 02:29:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB7SAv25076
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 02:28:10 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12739
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 02:25:27 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAB7Lwd00646;
	Sun, 10 Nov 2002 23:21:59 -0800 (PST)
Date: Sun, 10 Nov 2002 23:21:58 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: RJ Atkinson <rja@extremenetworks.com>, "Nguyen, An" <nguyena@ncs.gov>,
        ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach,
 etc.
In-Reply-To: <3DCF0DBB.2040508@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211102321140.16112-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > Indications are that this is a common misperception. Read Odlyzko's
    > papers on the topic for an attempt to estimate Internet traffic; local
    > US call volume is a well-known quantity (see FCC documents). If you have
    > a better estimate of Internet traffic volume, please provide a reference.

Andrew's numbers are the best-supported.  Are the call-volume numbers on
your web page at 64k, 11k, or 7k?

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 04:12:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13995
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 04:12:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAB9EHk30871
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 04:14:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB9EHv30868
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 04:14:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13971
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 04:11:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB9DDv30798;
	Mon, 11 Nov 2002 04:13:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB9Cav30752
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 04:12:36 -0500
Received: from cygnus.degree2.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13945
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 04:09:49 -0500 (EST)
Received: from calypso (calypso.degree2.com [172.30.40.49])
	by cygnus.degree2.com (8.11.6/8.11.6) with ESMTP id gAB9CIY31981;
	Mon, 11 Nov 2002 09:12:18 GMT
From: "Alistair Munro" <alistair.munro@degree2.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>,
        "'Bill Woodcock'" <woody@pch.net>
Cc: <ieprep@ietf.org>
Subject: RE: [Ieprep] QoS & GigE
Date: Mon, 11 Nov 2002 09:16:04 -0000
Message-ID: <003001c28962$f644cea0$31281eac@degree2.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <52D79E6F-F4B4-11D6-B65C-00039357A82A@extremenetworks.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Ran,

> 
> What seems to be missing is the actual experience with 
> large-scale deployment of QoS in the WAN of an ISP.  As noted 
> several times before, RIPE/NANOG would probably love to see 
> presentations from anyone with 
> such
> experience.
> 

Would you count the experiences with Premium service on Abilene,
recently reported by the Internet2 QoS WG, as useful input? I haven't
got the reference to hand but you can find it via www.internet2.edu.

Regards,

Alistair
 
--
Dr. Alistair Munro,
Chief Systems Engineer, Degree2 Innovations Ltd.
Regus House, 1 Friary, Temple Quay, Bristol, BS1 6EA, U.K.
E-mail: Alistair.Munro@degree2.com
Tel: (work) +44-117-900-8114, (home) +44-1275-462707, (mobile)
+44-7974-922-442;
Fax: +44-117-900-8151
Web: http://www.u4eagroup.com


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 06:09:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15282
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 06:09:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABBB6i04081
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 06:11:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABBB6v04078
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 06:11:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15277
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 06:08:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABBAFv04056;
	Mon, 11 Nov 2002 06:10:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABB9rv04014
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 06:09:53 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15265
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 06:07:18 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 764EE67103; Mon, 11 Nov 2002 02:31:18 -0500 (EST)
Date: Mon, 11 Nov 2002 06:09:41 -0500
Subject: Re: [Ieprep] QoS & GigE
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: "Alistair Munro" <alistair.munro@degree2.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <003001c28962$f644cea0$31281eac@degree2.com>
Message-Id: <13431EEA-F566-11D6-889F-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, Nov 11, 2002, at 04:16 America/Montreal, Alistair Munro 
wrote:
>> What seems to be missing is the actual experience with
>> large-scale deployment of QoS in the WAN of an ISP.  As noted
>> several times before, RIPE/NANOG would probably love to see
>> presentations from anyone with
>> such
>> experience.
>>
>
> Would you count the experiences with Premium service on Abilene,
> recently reported by the Internet2 QoS WG, as useful input? I haven't
> got the reference to hand but you can find it via www.internet2.edu.

Any data beats no data.

That noted, Abiliene/Internet2 have a number of properties that are 
very very
different from a commercial ISP WAN.  Their mission explicitly includes
applied research, so they necessarily run their network differently than
a Tier-1 commercial ISP.  Also, their customer base is very different 
in mixture
from a Tier-1 commercial ISP.  For what its worth, ESnet and NASA 
Science
Internet are in the same bucket as Abilene/Internet2 in this particular 
aspect.

Do they have a paper on the operational problems they found with 
turning on QoS,
what QoS they turned on, etc.  ?

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 06:33:01 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15647
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 06:33:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABBZ3i04731
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 06:35:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABBZ3v04728
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 06:35:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15644
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 06:32:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABBY9v04690;
	Mon, 11 Nov 2002 06:34:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABBXuv04669
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 06:33:56 -0500
Received: from cygnus.degree2.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15620
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 06:31:23 -0500 (EST)
Received: from calypso (calypso.degree2.com [172.30.40.49])
	by cygnus.degree2.com (8.11.6/8.11.6) with ESMTP id gABBXrY01515;
	Mon, 11 Nov 2002 11:33:53 GMT
From: "Alistair Munro" <alistair.munro@degree2.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: <ieprep@ietf.org>
Subject: RE: [Ieprep] QoS & GigE
Date: Mon, 11 Nov 2002 11:37:40 -0000
Message-ID: <001401c28976$bdf15050$31281eac@degree2.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <13431EEA-F566-11D6-889F-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Ran,

> 
> Do they have a paper on the operational problems they found with 
> turning on QoS,
> what QoS they turned on, etc.  ?
> 

The complete picture can be got from http://qbone.internet2.edu/bb/. 

While Internet2/Abilene is, as you point out, not a typical ISP model,
it's the only one I know about where a large-scale QoS experiment has
been done.

I've been keeping an eye on the VoIP/congestion discussions. For what
it's worth:

1. I was advised to run VoIP services on a separate physical segment
from IT services. Having ignored this advice, I have found that, unless
there are a lot of long-lived TCP transfers (not the case in general),
the grade of service is fine for a small number of VoIP phones. If we
depended on VoIP internally I would definitely run it in a separate
physical network. 802.1q and 802.1d might be an alternative (is 802.1p
not absorbed into these two other standards now?) but I haven't
evaluated any products - I believe the Siemens Skyport range uses LAN
priority and bandwidth management for VoIP;
2. I'm sure loss/delay sensitive applications will run quite happily on
low bandwidth media. However, they don't always work well if they have
to coexist with a lot of other services and users, especially long-lived
TCP flows.

Regards,

Alistair

--
Dr. Alistair Munro,
Chief Systems Engineer, Degree2 Innovations Ltd.
Regus House, 1 Friary, Temple Quay, Bristol, BS1 6EA, U.K.
E-mail: Alistair.Munro@degree2.com
Tel: (work) +44-117-900-8114, (home) +44-1275-462707, (mobile)
+44-7974-922-442;
Fax: +44-117-900-8151
Web: http://www.u4eagroup.com


 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 07:56:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16691
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 07:56:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABCwO708825
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 07:58:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABCwNv08822
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 07:58:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16677
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 07:55:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABCvMv08807;
	Mon, 11 Nov 2002 07:57:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABCutv08787
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 07:56:55 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16664
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 07:54:21 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Mon, 11 Nov 2002 07:56:35 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111107564008739
 ; Mon, 11 Nov 2002 07:56:40 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMFW9Y27>; Mon, 11 Nov 2002 07:58:01 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77937@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>,
        Alistair Munro <alistair.munro@degree2.com>
Cc: ieprep@ietf.org
Subject: RE: [Ieprep] QoS & GigE
Date: Mon, 11 Nov 2002 07:56:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> 
> Do they have a paper on the operational problems they found with 
> turning on QoS,
> what QoS they turned on, etc.  ?

I found this a while back...
http://qbone.internet2.edu/presentations/teitelbaum-terenaAntalya-5.01.pdf .

and http://www.ics.uci.edu/relations/develop/rs2001/teitelbaum/sld020.htm.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 08:12:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16905
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 08:12:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABDEAZ09808
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 08:14:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABDEAv09805
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 08:14:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16899
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 08:11:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABDD3v09743;
	Mon, 11 Nov 2002 08:13:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABDCiv09723
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 08:12:44 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16865
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 08:10:10 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gABDCdm6023046;
	Mon, 11 Nov 2002 08:12:39 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gABDCYH9009264
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 11 Nov 2002 08:12:35 -0500 (EST)
Message-ID: <3DCFACC2.6090206@cs.columbia.edu>
Date: Mon, 11 Nov 2002 08:12:34 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: Alistair Munro <alistair.munro@degree2.com>, ieprep@ietf.org
Subject: Re: [Ieprep] QoS & GigE
References: <13431EEA-F566-11D6-889F-00039357A82A@extremenetworks.com>
In-Reply-To: <13431EEA-F566-11D6-889F-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

See http://qbone.internet2.edu/

>
> Do they have a paper on the operational problems they found with turning
> on QoS,
> what QoS they turned on, etc.  ?
>
> Ran


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 10:26:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22201
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 10:26:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABFSrU16674
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 10:28:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABFSrv16671
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 10:28:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22142
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 10:26:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABFSBv16518;
	Mon, 11 Nov 2002 10:28:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABFJdv16174
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 10:19:39 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA21737
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 10:17:02 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.12459-0@bells.cs.ucl.ac.uk>; Mon, 11 Nov 2002 15:19:10 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: RJ Atkinson <rja@extremenetworks.com>
cc: "Ayyasamy, Senthilkumar (UMKC-Student)" <saq66@umkc.edu>,
        ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] quality of measurement/simulation, reverse-engineering 
         backbone topology
In-reply-to: Your message of "Sun, 10 Nov 2002 08:42:34 EST." <443B67D8-F4B2-11D6-B65C-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 11 Nov 2002 15:19:09 +0000
Message-ID: <1216.1037027949@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ran,

> > Even if thats the case, researchers are not to be blamed.
> 
> I disagree on why researchers can't get good measurement.  I think the
> main reason is (1) lack of good no-cost attachment points for measurement
> devices and (2) lack of money to pay for a good attachment point at
> an exchange.  There are exceptions of course.  RIPE probably has a good
> data set.  I understand that someone else on this list is currently 
> looking at the RIPE data set to see what it shows.

the above is valid for many.  a third reason, and one I experience on 
occasion, is non-disclosure agreements.  some researchers can and do 
get really nice material from US and non-US ISPs, but simply can't 
disclose it because the research is kept in-house to the folks that 
funded the effort.

-ken




_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 10:26:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22214
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 10:26:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABFSxI16689
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 10:28:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABFSxv16686
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 10:28:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22146
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 10:26:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABFS8v16494;
	Mon, 11 Nov 2002 10:28:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABFCIv15908
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 10:12:18 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA21453
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 10:09:41 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.11680-0@bells.cs.ucl.ac.uk>; Mon, 11 Nov 2002 15:12:06 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Scott Bradner <sob@harvard.edu>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-reply-to: Your message of "Sat, 02 Nov 2002 11:39:45 EST." <200211021639.gA2Gdjaq007031@newdev.harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 11 Nov 2002 15:12:05 +0000
Message-ID: <1202.1037027525@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Scott,

(sidenote, my apologies for the tardy response.  i was away on travel
most of last week).  I'll speak below in the form of a contributer and 
not the primary author to try and provide some additional comments to 
help clarify the issues & questions you bring up.

one observation taken from your comments and others.  it may be worth
considering changing the title of the document and replace the word
"requirements" to "expectations".  also, while the term is touched upon,
perhaps a more direct discussion of who the user is or can be expected to
be would be helpful.
______________________________

>  The basic user requirements that need to be considered in providing
>  emergency telecommunication capabilities to support recovery
>  operations from serious disaster situations are summarized as
>  follows.  Note that we assume the presence of Service Level
>  Agreements in cases where user requirements cover expectations of  
>  service providers:
>
> >> see above - I'm not sure what the context is for the last
> >> sentence - are we talking about the customer of a single ISP
> >> using only that ISP for the emergency communications to other
> >> sites on the same ISP?  If so I can see how a SLA could be 
> >> used, otherwise I do not know what SLA is being referred to

this relates to the issue that Ran and I have brought up separately
about avoiding confusion that the document be misconstrued as an
IETF statement that X, Y, and Z must be done.  Rather, we wanted to 
reinforce the notion that if a service is available it is because
a business contract in some form exists -- ie, there is no such thing
as a free lunch.  Having stated that, we can make another pass at 
trying to further clarify this intent.

>  1  Users should be able to use public telecommunication
>     resources for supporting emergency communications to help
>     organize and coordinate immediate disaster recovery
>     operations.
> >> I do not know what is meant by "public telecommunication 
> >> resources " - does this refer to the PSTN or to the Internet?
> 
> >> This seems more of a goal than a requirement.
> >> Requirements should be specific enough to know if they are being 
> >> met, use within an enterprise network, or within a single ISP
> >> is quite different than use of the general Internet where
> >> there is no guarantee where the other end of the communication
> >> may be.

understood.

>  2  Users that access emergency telecommunications service must
>     be authenticated.  This should be accomplished in a timely
>     manner.
> >> see above, this does not seem specific enough to know if
> >> its being met - for example, I can see a case where no 
> >> authentication is needed over the IP part of an emergency
> >> call because there are no facilities for authentication or
> >> because the is no need to authenticate because there are 
> >> adequate resources but that authentication might well be needed
> >> with the PSTN side of a IP-to-PSTN gateway - maybe this needs
> >> to say something like 'users of emergency telecommunications
> >> services which require special allocation of network resources
> >> must be authenticated'  

yes, agreed.  the original intent was to assume that a label was
used to convey a request for distinguishing traffic and requesting
a particular resource (be it at a gateway, or along the network).
this should be made clearer in the next version.

> >> also there is no reason to think that authentication to one 
> >> part of a communications path means authentication to the
> >> rest of the path - for example, I have to go through an
> >> authentication process to access part of the Harvard network
> >> but that authentication is not forwarded to a IP-to-PSTN
> >> gateway I might be using, nor would the Harvard authentication 
> >> make any sense to the gateway 

understood.  further explanation should be applied to the passage to
convey that authentication can be expected to operate within a given
context.  I should probably include this clarification in the 
carlberg-ets-* drafts as well.

>  3  When networks reach traffic saturation emergency
>     communication sessions should be provided with a
>     higher probability of completion over non-emergency  
>     communications.  We assume the presence of a service level
>     agreement to accomplish this latter case. (Note: Sessions
>     identified as emergency communication could be processed as
>     normal traffic along with all non-emergency traffic when
>     sufficient network bandwidth and resources are available.)
> >> see above - this is very different within an enterprise, within
> >> a single ISP and across the Internet

the understanding is that if it occurs, it would only be with those
providers that have been contracted to support the service.  outside
of that, its best effort the rest of the way.  

> >> also - I would think that each ISP would decide how
> >> to eet any emergency service requirement - in a few cases
> >> this could mean prioritizing emergency traffic at the expense
> >> of their normal customer traffic but I would expect that
> >> would not be the normal case - I doubt that most ISPs

agreed.  the word "probability" was meant to avoid the direction or
the notion of absolute or guaranteed.  and as you point out, there can
be several solutions of how that could be achieved.  we have constant
reminders that these documents are not aimed at specific solutions, and
our hope was that this passage would reflect that.

> >> will be willing to starve their regular customers, who may be
> >> trying to respond to the same emergency, I would expect that
> >> it sis far more likely that an ISP will set aside some set
> >> amount of network capacity to provide this service on

understood.  using the word "probability" should discourage the notion
that other resources would be starved.  we could add verbage to clarify
this some more.

>  4  Once an emergency communications session is established,
>     the user should be able to complete the session without
>     being interrupted or having the quality of the
>     communications be degraded excessively.
> >> I'm not sure what this means - what happens if the tail
> >> circuit gets cut and there is no connectivity - or what 
> >> happens if there is too much emergency traffic for the 
> >> available resources?

understood.  if the above stays it will need additional clarity. 

>  5  There must exist a mapping association between labels
>     defined by various standards bodies.  This mapping will   
>     help facilitate inter-working of services in cases where 
>     gateways and networks support emergency telecommunications 
>     services.
> >> does this imply that the function of bridging two PSTN networks
> >> over the Internet has to be able to translate between
> >> two, potentially incompatible, label types?
> >> it would seem to me that this would be a problem for a
> >> standards organization that develops a new set of 
> >> label set and not of the IP-based technology used to do 
> >> bridging - i.e. it is a gateway not a transport problem

there would seem to be a statement missing in the original passage.
we should convey the notion that a mapping must exist if there is
an expectation that services defined by different standards bodies
are expected to interoperate.  further, that this mapping can be
either in the form of internal policy within the gateway, or from
additional standards documents.

finally, as for items 6-10 in your subsequent email, I'll wait for
Hal to provide more incite/comments (and obviously others have 
provided their comments).

-ken


-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 10:31:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22391
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 10:31:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABFXnl16995
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 10:33:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABFXnv16992
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 10:33:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22364
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 10:31:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABFX6v16910;
	Mon, 11 Nov 2002 10:33:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABFH1v16074
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 10:17:01 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21622
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 10:14:25 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gABFGedc015885;
	Mon, 11 Nov 2002 10:16:40 -0500 (EST)
Date: Mon, 11 Nov 2002 10:16:40 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211111516.gABFGedc015885@newdev.harvard.edu>
To: K.Carlberg@cs.ucl.ac.uk, sob@harvard.edu
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
Cc: ieprep@ietf.org
In-Reply-To: <1202.1037027525@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ken - thanks for the thoughtful responses to my notes - I expect
a revised version of this document after the dicussion in Atlanta
will be a very helpful contribution to the understanding of
the ieprep issues

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 11:06:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23324
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 11:06:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABG88F19628
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 11:08:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABG88v19625
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 11:08:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23302
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 11:05:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABG77v19245;
	Mon, 11 Nov 2002 11:07:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABG6Xv18986
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 11:06:33 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23279
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 11:03:56 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gABG6Mm6006800;
	Mon, 11 Nov 2002 11:06:22 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gABG6LH9014741
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 11 Nov 2002 11:06:21 -0500 (EST)
Message-ID: <3DCFD57C.2050905@cs.columbia.edu>
Date: Mon, 11 Nov 2002 11:06:20 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Woodcock <woody@pch.net>
CC: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach,
 etc.
References: <Pine.GSO.4.44.0211102321140.16112-100000@paixhost.pch.net>
In-Reply-To: <Pine.GSO.4.44.0211102321140.16112-100000@paixhost.pch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Andrew's numbers are the best-supported.  Are the call-volume numbers on
> your web page at 64k, 11k, or 7k?


64 kb/s, since compression isn't used on US landline circuits, as far as 
I know.

>
>
>                                 -Bill
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 12:35:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25501
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 12:35:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABHbrR25174
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 12:37:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABHbqv25171
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 12:37:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25484
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 12:35:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABHaqv24532;
	Mon, 11 Nov 2002 12:36:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABHZqv24467
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 12:35:52 -0500
Received: from mail1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25452
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 12:33:16 -0500 (EST)
Received: from bgreenew2k (dhcp-10-24-19-69.cisco.com [10.24.19.69]) by mail1.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id JAA25941; Mon, 11 Nov 2002 09:35:33 -0800 (PST)
Reply-To: <bgreene@cisco.com>
From: "Barry Raveendran Greene" <bgreene@cisco.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>,
        "RJ Atkinson" <rja@extremenetworks.com>
Cc: "Alistair Munro" <alistair.munro@degree2.com>, <ieprep@ietf.org>
Subject: RE: [Ieprep] QoS & GigE
Date: Mon, 11 Nov 2002 09:35:27 -0800
Message-ID: <LNEHJBNJAPFNLEGJHCPEGEIFKCAA.bgreene@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <3DCFACC2.6090206@cs.columbia.edu>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Please put this into perspective. Qbone is really a tool to test the QOS
functions, not to test if oversubscription+QOS is going to work.

> See http://qbone.internet2.edu/
>
> >
> > Do they have a paper on the operational problems they found with turning
> > on QoS,
> > what QoS they turned on, etc.  ?
> >
> > Ran
>
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 13:02:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26191
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 13:02:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABI51o26080
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 13:05:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABI51v26077
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 13:05:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26168
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 13:02:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABI46v26032;
	Mon, 11 Nov 2002 13:04:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABI3sv26015
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 13:03:54 -0500
Received: from wells.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26135
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 13:01:17 -0500 (EST)
Received: from JMPOLK-W2K (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id KAA21787; Mon, 11 Nov 2002 10:03:39 -0800 (PST)
Message-Id: <4.1.20021111114600.030c2de8@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Mon, 11 Nov 2002 12:03:33 -0600
To: RJ Atkinson <rja@extremenetworks.com>, Mpierce1@aol.com
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Cc: ieprep@ietf.org
In-Reply-To: <8400E704-F381-11D6-8AB8-00039357A82A@extremenetworks.com>
References: <73.28cb9c71.2afd93e4@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

At 08:21 PM 11/8/2002 -0500, RJ Atkinson wrote:
>
>On Friday, Nov 8, 2002, at 17:25 America/Montreal, Mpierce1@aol.com 


>Absent additional clarification, I do not see why people here are likely
>to avoid continuing to talk past each other on the topic rather than
>communicate effectively.  Even if people disagree, it is pleasant
>if they clearly and correctly understand what each other are saying.

One observation here is this is a great opportunity for those that believe
there should be accounting (of some form) in IEPREP/ETS services and of
this WG, to write a single topic ID explaining exactly how they define that
topic and their perceived requirements of this function.

Opening up discussion on this topic would seem to be better served if there
were a written reference (not just a series of emails) all could comment on.

The discussion time Mike has on the agenda in Atlanta could be the start of
that (writing) effort.

Does this seem reasonable?

BTW - this isn't Latin of the middle ages (where only the rich get the
education to be able to read the laws and scripture), this is the IETF
where anyone can comment, where anyone should have a specific place to be
pointed to the explanation of a thing (feature/function, why/why not).

>
>Ran
>
>
>_______________________________________________
>Ieprep mailing list
>Ieprep@ietf.org
>https://www1.ietf.org/mailman/listinfo/ieprep


cheers,
James 

              *************************************
"People generally demand more respect for their own rights than 
                         they are willing to allow for others"


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 13:36:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27018
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 13:36:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABIcAS28406
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 13:38:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABIcAv28403
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 13:38:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27006
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 13:35:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABIb6v27978;
	Mon, 11 Nov 2002 13:37:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABIalv27745
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 13:36:47 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26976
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 13:34:10 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gABIUfd09944;
	Mon, 11 Nov 2002 10:30:41 -0800 (PST)
Date: Mon, 11 Nov 2002 10:30:41 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
cc: Scott Bradner <sob@harvard.edu>, <ieprep@ietf.org>
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-Reply-To: <1202.1037027525@cs.ucl.ac.uk>
Message-ID: <Pine.GSO.4.44.0211111021530.9508-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Mon, 11 Nov 2002, Ken Carlberg wrote:
    > this relates to the issue that Ran and I have brought up separately
    > about avoiding confusion that the document be misconstrued as an
    > IETF statement that X, Y, and Z must be done.  Rather, we wanted to
    > reinforce the notion that if a service is available it is because
    > a business contract in some form exists -- ie, there is no such thing
    > as a free lunch.  Having stated that, we can make another pass at
    > trying to further clarify this intent.

One thing you might look at as a way of defining the relationship is to
discuss it in terms of the business relationships which flow from the
Internet topology.  You're trying to get this into the ISP-customer
interface, it sounds like, in cases where the customer wants it; the
expectations of that interface are formalized in the transit contract.  So
saying something like "these suggestions may be of use to customers who
wish to receive GETS-like services, when negotiating their Internet
service provider's deliverables under the transit contract between ISP and
customer."

    > understood.  further explanation should be applied to the passage to
    > convey that authentication can be expected to operate within a given
    > context.

By context, do you mean at the application layer, or within one ASN?

    > the understanding is that if it occurs, it would only be with those
    > providers that have been contracted to support the service.  outside
    > of that, its best effort the rest of the way.

That should be stated explicitly, so that customers who read the document
understand that their ISP cannot sell them an end-to-end service, no
matter how much they'd like to.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 13:45:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27245
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 13:45:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABIl7V28668
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 13:47:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABIl7v28665
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 13:47:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27238
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 13:44:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABIf3v28545;
	Mon, 11 Nov 2002 13:41:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABIeBv28512
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 13:40:11 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27056
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 13:37:34 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gABIXxd09994;
	Mon, 11 Nov 2002 10:33:59 -0800 (PST)
Date: Mon, 11 Nov 2002 10:33:59 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach,
 etc.
In-Reply-To: <3DCFD57C.2050905@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211111031220.9508-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > > Andrew's numbers are the best-supported.  Are the call-volume numbers on
    > > your web page at 64k, 11k, or 7k?
    > 64 kb/s, since compression isn't used on US landline circuits, as far as
    > I know.

That was my assumption as well.  Which makes all voice traffic somewhat
less than 1.5% of the size of the Internet, and dropping really quickly.
I think I was justified in discribing that as minute, or miniscule, or
whatever word I used.  The basic point was that the Internet, with
typically anywhere between 60% and 99.9% unused headroom, isn't going to
keel over or behave radically differently, if another 1.5% more traffic
were dropped on it.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 13:58:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27751
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 13:58:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABJ0D829152
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 14:00:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABJ0Dv29149
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 14:00:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27740
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 13:57:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABIx4v29079;
	Mon, 11 Nov 2002 13:59:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABIwZv29044
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 13:58:35 -0500
Received: from imo-r02.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27725
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 13:55:58 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r02.mx.aol.com (mail_out_v34.13.) id b.81.24367161 (4262);
	Mon, 11 Nov 2002 13:58:03 -0500 (EST)
Message-ID: <81.24367161.2b0157ba@aol.com>
Date: Mon, 11 Nov 2002 13:58:02 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: woody@pch.net
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_81.24367161.2b0157ba_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_81.24367161.2b0157ba_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/9/2002 4:48:35 AM Eastern Standard Time, woody@pch.net 
writes:


>       On Fri, 8 Nov 2002 Mpierce1@aol.com wrote:
>     > The term "accounting" is the accepted one for what we are talking 
> about.
>                 ^^^^^^^^^^
> 
> You misspelled "waste of money."  This is the Internet, not the PSTN.
> We'd rather deliver the traffic than fail to deliver the traffic in favor
> of delivering a bill instead.
> 


[MAP] We're not neccessarily talking about "billing" or "money" when we 
identify a requirement for "accounting" for emergency services. The 
requirement for "accounting" is to be able to detect who used the service in 
order to provide for dectection of misuse as well as to understand the 
pattern of use for future administration of the service.

Besides, just because you don't want to "bill" for service in your network, 
doesn't mean that others shouldn't be able to do it. The PSTN always operated 
on the basis that delivering the traffic was more important, so if the 
billing recording capability was lost, the switch still set up calls (free). 
But no carrier could stay in business if it did that for too long. I can't 
imagine that any Internet-based telephony service is going to be any 
different, but you can try if you want.

Mike Pierce
Artel


--part1_81.24367161.2b0157ba_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/9/2002 4:48:35 AM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;On Fri, 8 Nov 2002 Mpierce1@aol.com wrote:
<BR> &nbsp;&nbsp;&nbsp;&gt; The term "accounting" is the accepted one for what we are talking about.
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;^^^^^^^^^^
<BR>
<BR>You misspelled "waste of money." &nbsp;This is the Internet, not the PSTN.
<BR>We'd rather deliver the traffic than fail to deliver the traffic in favor
<BR>of delivering a bill instead.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] We're not neccessarily talking about "billing" or "money" when we identify a requirement for "accounting" for emergency services. The requirement for "accounting" is to be able to detect who used the service in order to provide for dectection of misuse as well as to understand the pattern of use for future administration of the service.
<BR>
<BR>Besides, just because you don't want to "bill" for service in your network, doesn't mean that others shouldn't be able to do it. The PSTN always operated on the basis that delivering the traffic was more important, so if the billing recording capability was lost, the switch still set up calls (free). But no carrier could stay in business if it did that for too long. I can't imagine that any Internet-based telephony service is going to be any different, but you can try if you want.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_81.24367161.2b0157ba_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 13:59:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27794
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 13:59:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABJ21K29245
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 14:02:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABJ21v29242
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 14:02:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27789
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 13:59:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABJ11v29211;
	Mon, 11 Nov 2002 14:01:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABJ0av29171
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 14:00:36 -0500
Received: from imo-r08.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27749
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 13:57:59 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r08.mx.aol.com (mail_out_v34.13.) id j.49.265b0a53 (4262);
	Mon, 11 Nov 2002 14:00:22 -0500 (EST)
Message-ID: <49.265b0a53.2b015845@aol.com>
Date: Mon, 11 Nov 2002 14:00:21 EST
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach, etc.
To: rja@extremenetworks.com, nguyena@ncs.gov
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_49.265b0a53.2b015845_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_49.265b0a53.2b015845_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/10/2002 8:30:12 AM Eastern Standard Time, 
rja@extremenetworks.com writes:


> Prioritisation is a mechanism.  The NCS mission, as you state, is to
> ensure communications availability.  NCS ought not care which mechanism
> is used, provided that communications remain available.
> 


In a message dated 11/10/2002 1:38:58 PM Eastern Standard Time, 
KIMBERLY.S.KING@saic.com writes:


> Notice the word "priority" in the segment "priority telecommunications
> requirements".  I don't find a definition of priority in that document.
> Priority also has a meaning associated with IP networks (e.g., terms like a
> priority queue).  Have the two ideas been blended?
> 



I'm sure that the word "priority" (such as in the NCS mission) is being used 
in the more general sense, and certainly shouldn't be interpreted to mean 
that there must be a "priority queue" for packets or any other specific 
mechanism. Yes, I'm afraid the two ideas have been blended, resulting in 
immediate objection (to functional requirements or goals) being made by those 
who seem to jump to the conclusion that someone is proposing multiple 
priority queues for voice packets.

That's why I used the term "preferential treatment" in my drafts, and only 
give "prioritisation" as an example of how "preferential treatment" may be 
provided. Examples of "prioritisation" (in the sense of handling one thing in 
front of something else) would be a device that queues new call attempts and 
processes them in a priority order as resources become available.

Priority for transporting voice packets ahead of data is already defined in 
EF. My examples includes a mechanism of multiple drop precedences for EF, but 
do not propose "priority" as a mechanism in the sense of one voice packet 
having priority being sent ahead of others.

Mike Pierce
Artel


--part1_49.265b0a53.2b015845_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/10/2002 8:30:12 AM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Prioritisation is a mechanism. &nbsp;The NCS mission, as you state, is to
<BR>ensure communications availability. &nbsp;NCS ought not care which mechanism
<BR>is used, provided that communications remain available.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>In a message dated 11/10/2002 1:38:58 PM Eastern Standard Time, KIMBERLY.S.KING@saic.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Notice the word "priority" in the segment "priority telecommunications
<BR>requirements". &nbsp;I don't find a definition of priority in that document.
<BR>Priority also has a meaning associated with IP networks (e.g., terms like a
<BR>priority queue). &nbsp;Have the two ideas been blended?
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>
<BR>I'm sure that the word "priority" (such as in the NCS mission) is being used in the more general sense, and certainly shouldn't be interpreted to mean that there must be a "priority queue" for packets or any other specific mechanism. Yes, I'm afraid the two ideas have been blended, resulting in immediate objection (to functional requirements or goals) being made by those who seem to jump to the conclusion that someone is proposing multiple priority queues for voice packets.
<BR>
<BR>That's why I used the term "preferential treatment" in my drafts, and only give "prioritisation" as an example of how "preferential treatment" may be provided. Examples of "prioritisation" (in the sense of handling one thing in front of something else) would be a device that queues new call attempts and processes them in a priority order as resources become available.
<BR>
<BR>Priority for transporting voice packets ahead of data is already defined in EF. My examples includes a mechanism of multiple drop precedences for EF, but do not propose "priority" as a mechanism in the sense of one voice packet having priority being sent ahead of others.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_49.265b0a53.2b015845_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 14:16:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28351
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 14:16:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABJJ2V30287
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 14:19:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABJJ1v30284
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 14:19:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28347
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 14:16:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABJI5v30259;
	Mon, 11 Nov 2002 14:18:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABJHUv30229
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 14:17:30 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28321
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 14:14:52 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gABJBQd10583;
	Mon, 11 Nov 2002 11:11:26 -0800 (PST)
Date: Mon, 11 Nov 2002 11:11:26 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Atlanta ieprep Agenda
In-Reply-To: <81.24367161.2b0157ba@aol.com>
Message-ID: <Pine.GSO.4.44.0211111110240.10051-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Mon, 11 Nov 2002 Mpierce1@aol.com wrote:
    > Just because you don't want to "bill" for service in your network,
    > doesn't mean that others shouldn't be able to do it.

That would make it "permitted" not a "requirement."  Even if you don't
realize it, I think you're beginning to see my point.  :-)

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 14:35:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28889
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 14:35:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABJbxk31435
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 14:37:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABJbxv31432
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 14:37:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28879
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 14:35:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABJb4v30942;
	Mon, 11 Nov 2002 14:37:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABJatv30804
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 14:36:55 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28805
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 14:34:18 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18BKMZ-0004rh-00; Mon, 11 Nov 2002 14:36:47 -0500
Date: Mon, 11 Nov 2002 14:36:47 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: Bill Woodcock <woody@pch.net>
cc: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>, Scott Bradner <sob@harvard.edu>,
        <ieprep@ietf.org>
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-Reply-To: <Pine.GSO.4.44.0211111021530.9508-100000@paixhost.pch.net>
Message-ID: <Pine.GSO.4.44.0211111425490.18635-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


On Mon, 11 Nov 2002, Bill Woodcock wrote:
> That should be stated explicitly, so that customers who read the document
> understand that their ISP cannot sell them an end-to-end service, no
> matter how much they'd like to.

Once a standard exists, will the FCC be asked to assit in gaining
compliance with the standard?

http://www.atis.org/pub/clc/niif/issues/0207.doc

Although words like voluntary are used, unless the capability is widely
deployed, it won't be very useful.  Its probably better to read the drafts
with the understanding you will be implementing them, one way or another.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 17:00:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03610
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 17:00:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABM36S07751
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 17:03:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABM36v07748
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 17:03:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03562
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 17:00:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABM2Nv07732;
	Mon, 11 Nov 2002 17:02:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABM13v07586
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 17:01:03 -0500
Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03511
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 16:58:23 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 11 Nov 2002 16:00:54 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Mon, 11 Nov 2002 16:00:53 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD4331610234EF8A@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Ieprep digest, Vol 1 #210 - 17 msgs
Thread-Index: AcKJpXRKmAEcFMR6SYCj2Vu3Xw58kQAHoGIA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: <ieprep@ietf.org>
X-OriginalArrivalTime: 11 Nov 2002 22:00:54.0250 (UTC) FILETIME=[CE50D4A0:01C289CD]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gABM13v07589
Subject: [Ieprep] RE: QoS & GigE
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> Would you count the experiences with Premium service on Abilene,
> recently reported by the Internet2 QoS WG, as useful input? 
   Premium service on abilene was a failed mission. 

My views:
 - They have adapted the virtual-wire PDB (Per-domain Behavior) 
  ( collection of EF PHBs - but a domain view )for supporting 
  VoIP applications. IMO, VW PDB is a theoretical framework and is
  necessary for jitter-adaptive services ( but application doesn't
  have such a tight requirement)
 
 - One of the major reason for the failure is that they tried for
   inter-domain QoS, without taking architectural factors into 
   account.

 - Abilene come under the category of HPC research networks(along
   with vBNS, ESnet-which serves the HENP community), also has a 
   remarkable utilization (http://loadrunner.uits.iu.edu/weathermaps/abilene/)
   So, i2 serves a better place to keep passive measurement listeners,
   run video broadcast sessions for other communities in i2 participating
   schools (e.g. Medicine, Nuclear Physics..) than QoS based services.

 - I have been following some of the activities of i2 and am a member of 
   p2p group in i2. All activities in QoS related projects are more or less
   dormant...as their is no necessity ( BB implementation for Diffserv was 
   contributed by Ukansas but deployment was not so successful.. same case
   for scavenger based services.) But, some of the application based 
   groups are highly successful and offers service to other communities too.

 - Qbone is a collection of tools to calibrate QoS, rather than total 
   Diffserv stack.

shalunov views:
( Has answers for Ran's questions on QoS deployment.)

 shalunov write-up (http://qbone.internet2.edu/papers/non-architectural-problems.txt)
Possibly, iepg should include a talk on this too.


 Their are successful implementations by TEQUILA, DANTE and some other 
European organizations. They have built Diffserv stacks, have deployed
and have even _tried_ for some BoF in IETF. But, they are more into testing
than into use for practical applications.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 17:38:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04765
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 17:38:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABMehD10241
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 17:40:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMegv10238
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 17:40:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04742
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 17:38:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMe3v10212;
	Mon, 11 Nov 2002 17:40:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMdov10163
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 17:39:50 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04735
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 17:37:09 -0500 (EST)
Received: from extremenetworks.com (unknown [10.255.52.14])
	by gnat.inet.org (Postfix) with ESMTP
	id 9C31967103; Mon, 11 Nov 2002 14:01:24 -0500 (EST)
Date: Mon, 11 Nov 2002 17:39:41 -0500
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach, etc.
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: nguyena@ncs.gov, ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <49.265b0a53.2b015845@aol.com>
Message-Id: <779C9E78-F5C6-11D6-B1C0-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, Nov 11, 2002, at 14:00 America/Montreal, Mpierce1@aol.com 
wrote:
> That's why I used the term "preferential treatment" in my drafts, and 
> only give "prioritisation" as an example of how "preferential 
> treatment" may be provided. Examples of "prioritisation" (in the sense 
> of handling one thing in front of something else) would be a device 
> that queues new call attempts and processes them in a priority order 
> as resources become available.

A major issue with even that is that it isn't the functional need of 
GETS or
NCS.  The functional need is to get the emergency calls through.  If an 
ISP
can do that with only "best effort" and explicitly no support for 
"preferential
treatment", the ISP has met the need completely.  If one talks about 
"preferential
treatment" then by definition it means the ISP is offering something 
other than
pure "best effort" service, so even that gets down into mechanism 
somewhat
(though it is fuzzy about which mechanism(s) provide the "preferential 
treatment").

So there are still issues with that wording and that conceptual 
approach.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 17:42:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04865
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 17:42:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABMijB10379
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 17:44:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMijv10376
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 17:44:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04853
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 17:42:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMi0v10339;
	Mon, 11 Nov 2002 17:44:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMhYv10303
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 17:43:34 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04821
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 17:40:53 -0500 (EST)
Received: from extremenetworks.com (unknown [10.255.52.14])
	by gnat.inet.org (Postfix) with ESMTP
	id 0B18F67103; Mon, 11 Nov 2002 14:04:57 -0500 (EST)
Date: Mon, 11 Nov 2002 17:43:11 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: woody@pch.net, ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <81.24367161.2b0157ba@aol.com>
Message-Id: <F4F1EEBA-F5C6-11D6-B1C0-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, Nov 11, 2002, at 13:58 America/Montreal, Mpierce1@aol.com 
wrote:
> Besides, just because you don't want to "bill" for service in your 
> network,

ISPs bill for service.  They bill based solely on IP layer properties 
(or lower layer
ones, like what speed physical link does the customer have in place 
from that ISP).
Most ISPs perform flat-rate billing, tiered by link access max 
bandwidth.  Some
offer a kind of usage-based billing (e.g. 90th percentile of the 
traffic measurements
where instantaneous bandwidth on the customer link is measured via SNMP 
counters
every N minutes).  None of that gets into *upper-layer* services such 
as VoIP
or FTP or EMAIL.

> doesn't mean that others shouldn't be able to do it. The PSTN always 
> operated on the basis that delivering the traffic was more important, 
> so if the billing recording capability was lost, the switch still set 
> up calls (free). But no carrier could stay in business if it did that 
> for too long. I can't imagine that any Internet-based telephony 
> service is going to be any different, but you can try if you want.

So your real requirement is that the specs *not preclude* a carrier 
from billing,
not that the specs *support* billing.

But please don't increase the capital costs for all carriers just so 
that NCS,
which is NOT a carrier at all, can be happy that it changed the 
Internet architecture.

Mumble.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 17:42:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04878
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 17:42:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABMikp10394
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 17:44:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMikv10391
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 17:44:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04858
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 17:42:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMi1v10355;
	Mon, 11 Nov 2002 17:44:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMhgv10314
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 17:43:42 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04831
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 17:41:02 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gABMbSd14316;
	Mon, 11 Nov 2002 14:37:29 -0800 (PST)
Date: Mon, 11 Nov 2002 14:37:28 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Mpierce1@aol.com, <nguyena@ncs.gov>, <ieprep@ietf.org>
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach,
 etc.
In-Reply-To: <779C9E78-F5C6-11D6-B1C0-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211111435520.11958-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Mon, 11 Nov 2002, RJ Atkinson wrote:
    > A major issue with even that is that ["preferential treatment"]
    > isn't the functional need of GETS or NCS.  The functional need is to
    > get the emergency calls through.

Ran has accurately summarized my objection, as well.

"Preferential treatment" or call completion.  ISPs can provide either one,
but not both.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 21:42:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09475
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 21:42:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC2j7V22237
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 21:45:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2j7v22234
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 21:45:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09471
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 21:42:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2iBv22167;
	Mon, 11 Nov 2002 21:44:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2hQv22132
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 21:43:26 -0500
Received: from imo-m05.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09427
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 21:40:45 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m05.mx.aol.com (mail_out_v34.13.) id 7.11d.1a2593d8 (3940);
	Mon, 11 Nov 2002 21:42:47 -0500 (EST)
Message-ID: <11d.1a2593d8.2b01c4a7@aol.com>
Date: Mon, 11 Nov 2002 21:42:47 EST
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
To: hgs@cs.columbia.edu, rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_11d.1a2593d8.2b01c4a7_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_11d.1a2593d8.2b01c4a7_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/9/2002 2:34:37 PM Eastern Standard Time, 
hgs@cs.columbia.edu writes:


> Since we may have different expectations, it might be helpful to get 
> feedback on what people would consider reasonable reliability. Is it ok 
> if 1% of calls fail (where "fail" may mean "sufficient disruption to 
> cause users to abandon the call")? 0.1%? Even lower?
> 



[MAP] Yes, this is a major issue for VoIP (not even considering the 
needs/desires of IEPREP). There are clearly a set of participants of the IETF 
who expect that VoIP should provide the same performance in this regard as 
the currenttly accepted standards for telephony (sometimes called 
"toll-quality", although that term is usually only applied to the audio 
quality, not other things like lost call rate). The requirements (at least in 
the US) for lost call rate are a lot better than 1%. Other counties tolerate 
worse.

Interesting issue, since just 10 days ago, An Nguyen asked "is anyone aware 
of the ITU-T Y.1541 which defines QoS parameters in the IP networks" to which 
one of the usual participants in this IETF list responded: "Irrelevant. ITU 
does not have any role in defining IP".

(In fact, Y.1541 does not actually define IP, it defines parameters for 
services which use IP.)

There is no possibility of agreeing on the requirements for performance 
parameters (reliability and others) for VoIP unless there is an attempt by 
the IETF at cooperation with other recognized standards bodies that are very 
qualified to deal with this issue.

Y.1541 deals with the transmission parameters (packet loss, delay, variation, 
etc.) that would case "failure" of a conenction. Draft Y.1530 deals with 
failure to setup calls, premature disconnect, probability of wrong 
connections, etc. The SG13 meeting just last week revised this draft. So far, 
the numbers for these are "for further study".

MIke Pierce
Artel


--part1_11d.1a2593d8.2b01c4a7_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/9/2002 2:34:37 PM Eastern Standard Time, hgs@cs.columbia.edu writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Since we may have different expectations, it might be helpful to get 
<BR>feedback on what people would consider reasonable reliability. Is it ok 
<BR>if 1% of calls fail (where "fail" may mean "sufficient disruption to 
<BR>cause users to abandon the call")? 0.1%? Even lower?
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>
<BR>[MAP] Yes, this is a major issue for VoIP (not even considering the needs/desires of IEPREP). There are clearly a set of participants of the IETF who expect that VoIP should provide the same performance in this regard as the currenttly accepted standards for telephony (sometimes called "toll-quality", although that term is usually only applied to the audio quality, not other things like lost call rate). The requirements (at least in the US) for lost call rate are a lot better than 1%. Other counties tolerate worse.
<BR>
<BR>Interesting issue, since just 10 days ago, An Nguyen asked "is anyone aware of the ITU-T Y.1541 which defines QoS parameters in the IP networks" to which one of the usual participants in this IETF list responded: "Irrelevant. ITU does not have any role in defining IP".
<BR>
<BR>(In fact, Y.1541 does not actually define IP, it defines parameters for services which use IP.)
<BR>
<BR>There is no possibility of agreeing on the requirements for performance parameters (reliability and others) for VoIP unless there is an attempt by the IETF at cooperation with other recognized standards bodies that are very qualified to deal with this issue.
<BR>
<BR>Y.1541 deals with the transmission parameters (packet loss, delay, variation, etc.) that would case "failure" of a conenction. Draft Y.1530 deals with failure to setup calls, premature disconnect, probability of wrong connections, etc. The SG13 meeting just last week revised this draft. So far, the numbers for these are "for further study".
<BR>
<BR>MIke Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_11d.1a2593d8.2b01c4a7_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 21:43:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09502
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 21:43:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC2jiP22260
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 21:45:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2jiv22257
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 21:45:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09489
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 21:43:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2j2v22214;
	Mon, 11 Nov 2002 21:45:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2iXv22177
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 21:44:33 -0500
Received: from imo-d10.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09462
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 21:41:51 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d10.mx.aol.com (mail_out_v34.13.) id b.f.1fc01d0 (3940);
	Mon, 11 Nov 2002 21:44:01 -0500 (EST)
Message-ID: <f.1fc01d0.2b01c4f1@aol.com>
Date: Mon, 11 Nov 2002 21:44:01 EST
To: woody@pch.net, jmpolk@cisco.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_f.1fc01d0.2b01c4f1_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Subject: [Ieprep] Requirements for Accounting
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_f.1fc01d0.2b01c4f1_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/11/2002 2:17:48 PM Eastern Standard Time, woody@pch.net 
writes:

      On Mon, 11 Nov 2002 Mpierce1@aol.com wrote:
    > Just because you don't want to "bill" for service in your network,
    > doesn't mean that others shouldn't be able to do it.

That would make it "permitted" not a "requirement."  Even if you don't
realize it, I think you're beginning to see my point.  :-)

[MAP] I have seen your point from the very beginning, that you don't want to 
be told what you must do in your network. I accepted this from the beginning 
and only ask that you accept the same for others.

The "requirements" documents that IEPREP is trying to write do not set 
requirements on anyone to do anything in their network or to design it into 
their equipment. It is only the "requirements" to be passed to other WGs as 
the basis of their work. That is, if "Accounting" or "X" or "Y" is included 
in the IEPREP doc as a "requirement", it only means that some other WG must 
figure out a way to support it. When (and if) the resulting protocol document 
is written that describes how to perform "accounting" or "X" or "Y", I 
certainly expect that it will clearly says that it is "permitted", not 
"required".

------------------------------------------------------------------------------

------------------------------------------------------------------------------

--------
In a message dated 11/11/2002 10:29:12 AM Eastern Standard Time, 
K.Carlberg@cs.ucl.ac.uk writes:

this relates to the issue that Ran and I have brought up separately
about avoiding confusion that the document be misconstrued as an
IETF statement that X, Y, and Z must be done.  Rather, we wanted to 
reinforce the notion that if a service is available it is because
a business contract in some form exists -- ie, there is no such thing
as a free lunch.  Having stated that, we can make another pass at 
trying to further clarify this intent.


[MAP] I certainly thought that it was understood and agreed across the board 
that no IETF document ever placed an actual requirement on any carrier or 
vendor to do anything. If that is not the case, then we have a bigger 
problem. It must be generally understood that all IETF documents by 
themselves do not require anyone to do anything. I'm confused by this belief 
that we need to make extra strong statements for this case. If this is 
needed, then it should be in a common statement in the beginning of every 
RFC. Perhaps the IAB should address this.

------------------------------------------------------------------------------

------------------------------------------------------------------------------
-
In a message dated 11/11/2002 1:04:05 PM Eastern Standard Time, 
jmpolk@cisco.com writes:

One observation here is this is a great opportunity for those that believe
there should be accounting (of some form) in IEPREP/ETS services and of
this WG, to write a single topic ID explaining exactly how they define that
topic and their perceived requirements of this function.

Opening up discussion on this topic would seem to be better served if there
were a written reference (not just a series of emails) all could comment on.

The discussion time Mike has on the agenda in Atlanta could be the start of
that (writing) effort.


[MAP] In draft-pierce-ieprep-assured-service-req-01, in Section 4, Functional 
Requirements, I wrote:

        Proper administration of the Assured Service capability requires 
        that use of the service can be reviewed after the fact for potential 
        abuse. Therefore, it is required that appropriate records be kept of 
        calls made, including the calling and called parties' identity, time 
        of the call, and the precedence level used. This is similar to the 
        requirements for Call Detail Recording (CDR) for billing purposes 
        for other services in a commercial environment. 

and in Section 6, Possible Approaches, I wrote:

        Call detail records (CDR) can be maintained by the proxy, since it 
        knows which users are authorized to place Assured Service calls and 
        knows when they do. Since not actually done to support billing 
        functions, it is not expected that a record of call duration is 
        required. 

I have received no comments directly on either statement.

Yes, I agree that more can and should be written to clarify this requirement, 
based on e-mail discussions, but so far, the only e-mails seem to be 
arguments that, since one carrier doesn't want to do billing, then no carrier 
should need or have the capability that I've described (which isn't really 
for "billing"). Oh, and some argument that, since the Internet architecture 
and philosophy don't support it, then it can't be a requirement. I'm hoping 
for some substantive comments. Maybe this could become a separate ID, but I 
see it as just a small section in a "requirements" ID.

Mike Pierce
Artel


--part1_f.1fc01d0.2b01c4f1_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/11/2002 2:17:48 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;On Mon, 11 Nov 2002 Mpierce1@aol.com wrote:
<BR> &nbsp;&nbsp;&nbsp;&gt; Just because you don't want to "bill" for service in your network,
<BR> &nbsp;&nbsp;&nbsp;&gt; doesn't mean that others shouldn't be able to do it.
<BR>
<BR>That would make it "permitted" not a "requirement." &nbsp;Even if you don't
<BR>realize it, I think you're beginning to see my point. &nbsp;:-)
<BR>
<BR>[MAP] I have seen your point from the very beginning, that you don't want to be told what you must do in your network. I accepted this from the beginning and only ask that you accept the same for others.
<BR>
<BR>The "requirements" documents that IEPREP is trying to write do not set requirements on anyone to do anything in their network or to design it into their equipment. It is only the "requirements" to be passed to other WGs as the basis of their work. That is, if "Accounting" or "X" or "Y" is included in the IEPREP doc as a "requirement", it only means that some other WG must figure out a way to support it. When (and if) the resulting protocol document is written that describes how to perform "accounting" or "X" or "Y", I certainly expect that it will clearly says that it is "permitted", not "required".
<BR>
<BR>--------------------------------------------------------------------------------------------------------------------------------------------------------------------
<BR>In a message dated 11/11/2002 10:29:12 AM Eastern Standard Time, K.Carlberg@cs.ucl.ac.uk writes:
<BR>
<BR>this relates to the issue that Ran and I have brought up separately
<BR>about avoiding confusion that the document be misconstrued as an
<BR>IETF statement that X, Y, and Z must be done. &nbsp;Rather, we wanted to 
<BR>reinforce the notion that if a service is available it is because
<BR>a business contract in some form exists -- ie, there is no such thing
<BR>as a free lunch. &nbsp;Having stated that, we can make another pass at 
<BR>trying to further clarify this intent.
<BR>
<BR>
<BR>[MAP] I certainly thought that it was understood and agreed across the board that no IETF document ever placed an actual requirement on any carrier or vendor to do anything. If that is not the case, then we have a bigger problem. It must be generally understood that all IETF documents by themselves do not require anyone to do anything. I'm confused by this belief that we need to make extra strong statements for this case. If this is needed, then it should be in a common statement in the beginning of every RFC. Perhaps the IAB should address this.
<BR>
<BR>-------------------------------------------------------------------------------------------------------------------------------------------------------------
<BR>In a message dated 11/11/2002 1:04:05 PM Eastern Standard Time, jmpolk@cisco.com writes:
<BR>
<BR>One observation here is this is a great opportunity for those that believe
<BR>there should be accounting (of some form) in IEPREP/ETS services and of
<BR>this WG, to write a single topic ID explaining exactly how they define that
<BR>topic and their perceived requirements of this function.
<BR>
<BR>Opening up discussion on this topic would seem to be better served if there
<BR>were a written reference (not just a series of emails) all could comment on.
<BR>
<BR>The discussion time Mike has on the agenda in Atlanta could be the start of
<BR>that (writing) effort.
<BR>
<BR>
<BR>[MAP] In draft-pierce-ieprep-assured-service-req-01, in Section 4, Functional Requirements, I wrote:
<BR>
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Proper administration of the Assured Service capability requires 
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;that use of the service can be reviewed after the fact for potential 
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;abuse. Therefore, it is required that appropriate records be kept of 
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;calls made, including the calling and called parties' identity, time 
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;of the call, and the precedence level used. This is similar to the 
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;requirements for Call Detail Recording (CDR) for billing purposes 
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;for other services in a commercial environment. 
<BR>
<BR>and in Section 6, Possible Approaches, I wrote:
<BR>
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Call detail records (CDR) can be maintained by the proxy, since it 
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;knows which users are authorized to place Assured Service calls and 
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;knows when they do. Since not actually done to support billing 
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;functions, it is not expected that a record of call duration is 
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;required. 
<BR>
<BR>I have received no comments directly on either statement.
<BR>
<BR>Yes, I agree that more can and should be written to clarify this requirement, based on e-mail discussions, but so far, the only e-mails seem to be arguments that, since one carrier doesn't want to do billing, then no carrier should need or have the capability that I've described (which isn't really for "billing"). Oh, and some argument that, since the Internet architecture and philosophy don't support it, then it can't be a requirement. I'm hoping for some substantive comments. Maybe this could become a separate ID, but I see it as just a small section in a "requirements" ID.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_f.1fc01d0.2b01c4f1_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 23:22:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11493
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 23:22:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC4OL827497
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 23:24:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC4OLv27493
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 23:24:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11486
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 23:21:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC4NIv27447;
	Mon, 11 Nov 2002 23:23:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC4K9v27313
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 23:20:09 -0500
Received: from mtiwmhc14.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11416
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 23:17:26 -0500 (EST)
Received: from cs.columbia.edu ([12.91.126.20])
          by mtiwmhc14.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP
          id <20021112041959.JVUE21264.mtiwmhc14.worldnet.att.net@cs.columbia.edu>;
          Tue, 12 Nov 2002 04:19:59 +0000
Message-ID: <3DD080F6.60609@cs.columbia.edu>
Date: Mon, 11 Nov 2002 23:17:58 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mpierce1@aol.com
CC: rja@extremenetworks.com, ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
References: <11d.1a2593d8.2b01c4a7@aol.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

http://www.softarmor.com/sipwg/meets/interim-nov-1999/991107%20dcs%20resource.pdf 
claims a permissible call defect rate of 0.00001%. Doesn't say whether 
this is an FCC requirement or just a business requirement. (Call 
blocking during busy hour is a different issue. From 
http://www.cis.state.mi.us/mpsc/comm/271/271attcorecomperformmeas.pdf, 
1% seems a common number; http://www.panix.com/~oppedahl/lads/mcc.htm 
confirms 1% as "busiest hour during the busiest day".)

Mpierce1@aol.com wrote:
> In a message dated 11/9/2002 2:34:37 PM Eastern Standard Time, 
> hgs@cs.columbia.edu writes:
> 
> 
>> Since we may have different expectations, it might be helpful to get
>> feedback on what people would consider reasonable reliability. Is it ok
>> if 1% of calls fail (where "fail" may mean "sufficient disruption to
>> cause users to abandon the call")? 0.1%? Even lower?
> 
> 
> 
> 
> 
> [MAP] Yes, this is a major issue for VoIP (not even considering the 
> needs/desires of IEPREP). There are clearly a set of participants of the 
> IETF who expect that VoIP should provide the same performance in this 
> regard as the currenttly accepted standards for telephony (sometimes 
> called "toll-quality", although that term is usually only applied to the 
> audio quality, not other things like lost call rate). The requirements 
> (at least in the US) for lost call rate are a lot better than 1%. Other 
> counties tolerate worse.
> 
> Interesting issue, since just 10 days ago, An Nguyen asked "is anyone 
> aware of the ITU-T Y.1541 which defines QoS parameters in the IP 
> networks" to which one of the usual participants in this IETF list 
> responded: "Irrelevant. ITU does not have any role in defining IP".
> 
> (In fact, Y.1541 does not actually define IP, it defines parameters for 
> services which use IP.)
> 
> There is no possibility of agreeing on the requirements for performance 
> parameters (reliability and others) for VoIP unless there is an attempt 
> by the IETF at cooperation with other recognized standards bodies that 
> are very qualified to deal with this issue.
> 
> Y.1541 deals with the transmission parameters (packet loss, delay, 
> variation, etc.) that would case "failure" of a conenction. Draft Y.1530 
> deals with failure to setup calls, premature disconnect, probability of 
> wrong connections, etc. The SG13 meeting just last week revised this 
> draft. So far, the numbers for these are "for further study".
> 
> MIke Pierce
> Artel

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 23:33:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11599
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 23:33:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC4ZeW27792
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 23:35:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC4Zev27789
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 23:35:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11594
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 23:32:57 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC4Z3v27765;
	Mon, 11 Nov 2002 23:35:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC4Y6v27731
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 23:34:06 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11582
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 23:31:23 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAC4XeR2018368;
	Mon, 11 Nov 2002 23:33:40 -0500 (EST)
Date: Mon, 11 Nov 2002 23:33:40 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211120433.gAC4XeR2018368@newdev.harvard.edu>
To: hgs@cs.columbia.edu, Mpierce1@aol.com
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Cc: ieprep@ietf.org, rja@extremenetworks.com
In-Reply-To: <3DD080F6.60609@cs.columbia.edu>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> a permissible call defect rate of 0.00001%

1/ I've not heard of an FCC requirement but maybe 

2/ what is a defect - in the context of the Internet?
	I would doubt that it is a dropped packet

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 11 23:44:01 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11787
	for <ieprep-archive@odin.ietf.org>; Mon, 11 Nov 2002 23:44:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC4kDb28757
	for ieprep-archive@odin.ietf.org; Mon, 11 Nov 2002 23:46:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC4kDv28754
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 23:46:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11784
	for <ieprep-web-archive@ietf.org>; Mon, 11 Nov 2002 23:43:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC4j3v28703;
	Mon, 11 Nov 2002 23:45:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC4iuv28659
	for <ieprep@optimus.ietf.org>; Mon, 11 Nov 2002 23:44:56 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11755
	for <ieprep@ietf.org>; Mon, 11 Nov 2002 23:42:13 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAC4iUrl018403;
	Mon, 11 Nov 2002 23:44:30 -0500 (EST)
Date: Mon, 11 Nov 2002 23:44:30 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211120444.gAC4iUrl018403@newdev.harvard.edu>
To: hgs@cs.columbia.edu, Mpierce1@aol.com
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
Cc: ieprep@ietf.org, rja@extremenetworks.com
In-Reply-To: <3DD080F6.60609@cs.columbia.edu>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>  a permissible call defect rate of 0.00001%

a search on the FCC web site does not find any thing with "call defect rate"
or "call defect" - 1189 hits for "defect"

google finds
http://www.informatik.unibw-muenchen.de/PMCCS5/papers/mendiratta.pdf
for "call defect rate"

this says that the "call defect rate" is the number of lost calls
per million calls


Scott

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 03:34:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24981
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 03:34:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC8aLE16037
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 03:36:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8aKv16034
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 03:36:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24963
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 03:33:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8Z8v16000;
	Tue, 12 Nov 2002 03:35:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8Y3v15956
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 03:34:09 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24931
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 03:31:09 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAC8Rfd23523;
	Tue, 12 Nov 2002 00:27:41 -0800 (PST)
Date: Tue, 12 Nov 2002 00:27:41 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: jmpolk@cisco.com, <ieprep@ietf.org>
Subject: Re: [Ieprep] Requirements for Accounting
In-Reply-To: <f.1fc01d0.2b01c4f1@aol.com>
Message-ID: <Pine.GSO.4.44.0211120022270.16502-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Mon, 11 Nov 2002 Mpierce1@aol.com wrote:
    > I have seen your point from the very beginning, that you don't want to
    > be told what you must do in your network.

No, that's not my point at all.  It's irrelevant what other people say
about what I must do in my network, since what I must do, I will perforce
do anyway.  The problem is when someone else _wants_ me to do something
that I don't need to do, and attempts to _require_ me to do it.

    > The "requirements" documents that IEPREP is trying to write do not set
    > requirements on anyone to do anything in their network or to design it into
    > their equipment.

So as soon as draft authors HURRY UP AND EDIT THEIR DOCUMENTS TO REFLECT
THIS CLARIFICATION we can stop arguing about it.

    > If "Accounting" or "X" or "Y" is included in the IEPREP doc as a
    > "requirement", it only means that some other WG must figure out a
    > way to support it.

No, it _most certainly does not_ mean that.  And if you really think it
does, get ready for them to toss you out on your ear again.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 03:41:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25098
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 03:41:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC8hiL16917
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 03:43:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8hiv16914
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 03:43:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25073
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 03:40:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8h1v16892;
	Tue, 12 Nov 2002 03:43:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8gsv16869
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 03:42:54 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25063
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 03:40:10 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAC8add23632;
	Tue, 12 Nov 2002 00:36:39 -0800 (PST)
Date: Tue, 12 Nov 2002 00:36:39 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: jmpolk@cisco.com, <ieprep@ietf.org>
Subject: Re: [Ieprep] Requirements for Accounting
In-Reply-To: <f.1fc01d0.2b01c4f1@aol.com>
Message-ID: <Pine.GSO.4.44.0211120029110.16502-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Mon, 11 Nov 2002 Mpierce1@aol.com wrote:
    > Proper administration of the Assured Service capability requires
    > that use of the service can be reviewed after the fact for potential
    > abuse...
    > Call detail records (CDR) can be maintained by the proxy, since it
    > knows which users are authorized to place Assured Service calls and
    > knows when they do.
    > I have received no comments directly on either statement.

Perhaps because they are uncontroversial, and seem clear and logical.
They're basically just saying that you need the proxy to log these calls,
which is no burden, since proxies are already logging everything to a much
greater level of detail than you desire, anyway.  Correct?

I think that these work well because they're clearly stated needs, which
apply directly to a single layer of the protocol stack which is clearly
identified, and they don't exceed the abiility of technology to satisfy.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 04:02:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25473
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 04:02:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC951a17940
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 04:05:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC951v17937
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 04:05:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25452
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 04:02:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC944v17841;
	Tue, 12 Nov 2002 04:04:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8orv17148
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 03:50:53 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25304
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 03:48:09 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18BWkr-0005KY-00; Tue, 12 Nov 2002 03:50:41 -0500
Date: Tue, 12 Nov 2002 03:50:41 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: Scott  Bradner <sob@harvard.edu>
cc: ieprep@ietf.org
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
In-Reply-To: <200211120444.gAC4iUrl018403@newdev.harvard.edu>
Message-ID: <Pine.GSO.4.44.0211120329520.20460-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Mon, 11 Nov 2002, Scott  Bradner wrote:
> >  a permissible call defect rate of 0.00001%
>
> a search on the FCC web site does not find any thing with "call defect rate"
> or "call defect" - 1189 hits for "defect"

This is usually the province of NARUC and the state PUCs.  If you start
with the NARUC Telephone Service Quality Handbook or the Bell(Telcordia)
Notes on the Network they'll point you to the underlying requirements.
Of course this is very circular.  Which came first the tariff or the
practice?

And, by the way, the state legislation, regulation or tariff always
excludes operations during "emergency" conditions no matter what are
service quality requirements.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 04:14:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25747
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 04:14:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC9Gx919031
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 04:16:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC9Gxv19028
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 04:16:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25741
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 04:14:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC9GBv19008;
	Tue, 12 Nov 2002 04:16:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC9Fjv18980
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 04:15:45 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA25734
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 04:13:00 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.07186-0@bells.cs.ucl.ac.uk>; Tue, 12 Nov 2002 09:15:25 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Bill Woodcock <woody@pch.net>
cc: Scott Bradner <sob@harvard.edu>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-reply-to: Your message of "Mon, 11 Nov 2002 10:30:41 PST." <Pine.GSO.4.44.0211111021530.9508-100000@paixhost.pch.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 12 Nov 2002 09:15:24 +0000
Message-ID: <518.1037092524@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>  So
> saying something like "these suggestions may be of use to customers who
> wish to receive GETS-like services, when negotiating their Internet
> service provider's deliverables under the transit contract between ISP and
> customer."

ok, thanks.  small nit: it may be best to generalize the term "GETS-like
service" to take into account approaches like GTPS.


>    > understood.  further explanation should be applied to the passage to
>    > convey that authentication can be expected to operate within a given
>    > context.
>
> By context, do you mean at the application layer, or within one ASN?

the context by which the authentication is being accomplished.  if at 
the application layer, then clearly an end-to-end issue.  we'll make 
sure this is clear in the next draft.

>    > the understanding is that if it occurs, it would only be with those
>    > providers that have been contracted to support the service.  outside
>    > of that, its best effort the rest of the way.
>
> That should be stated explicitly, so that customers who read the document
> understand that their ISP cannot sell them an end-to-end service, no
> matter how much they'd like to.

most definitely.

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 04:59:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26208
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 04:59:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACA1nN20923
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 05:01:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACA1nv20920
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 05:01:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26204
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 04:59:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACA0qv20896;
	Tue, 12 Nov 2002 05:00:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACA0Pv20862
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 05:00:25 -0500
Received: from cygnus.degree2.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26192
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 04:57:51 -0500 (EST)
Received: from calypso (calypso.degree2.com [172.30.40.49])
	by cygnus.degree2.com (8.11.6/8.11.6) with ESMTP id gAC9xmY16453;
	Tue, 12 Nov 2002 09:59:48 GMT
From: "Alistair Munro" <alistair.munro@degree2.com>
To: <bgreene@cisco.com>, "'Henning Schulzrinne'" <hgs@cs.columbia.edu>,
        "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: <ieprep@ietf.org>
Subject: RE: [Ieprep] QoS & GigE
Date: Tue, 12 Nov 2002 10:03:36 -0000
Message-ID: <000a01c28a32$c46e8350$31281eac@degree2.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <LNEHJBNJAPFNLEGJHCPEGEIFKCAA.bgreene@cisco.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi All,

To remove doubt: nobody said any of the I2/Qbone work was an operational
model for an ISP. It exposed a lot of useful issues that remain
unresolved in the IP QoS area.

Regards,

Alistair


--
Dr. Alistair Munro,
Chief Systems Engineer, Degree2 Innovations Ltd.
Regus House, 1 Friary, Temple Quay, Bristol, BS1 6EA, U.K.
E-mail: Alistair.Munro@degree2.com
Tel: (work) +44-117-900-8114, (home) +44-1275-462707, (mobile)
+44-7974-922-442;
Fax: +44-117-900-8151
Web: http://www.u4eagroup.com




> -----Original Message-----
> From: Barry Raveendran Greene [mailto:bgreene@cisco.com] 
> Sent: 11 November 2002 17:35
> To: Henning Schulzrinne; RJ Atkinson
> Cc: Alistair Munro; ieprep@ietf.org
> Subject: RE: [Ieprep] QoS & GigE
> 
> 
> 
> Please put this into perspective. Qbone is really a tool to 
> test the QOS functions, not to test if oversubscription+QOS 
> is going to work.
> 
> > See http://qbone.internet2.edu/
> >
> > >
> > > Do they have a paper on the operational problems they found with 
> > > turning on QoS, what QoS they turned on, etc.  ?
> > >
> > > Ran
> >
> >
> > _______________________________________________
> > Ieprep mailing list
> > Ieprep@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ieprep
> >
> 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 05:03:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26318
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 05:03:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACA5nY21041
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 05:05:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACA5nv21038
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 05:05:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26315
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 05:03:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC9xsv20845;
	Tue, 12 Nov 2002 04:59:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC9xpv20800
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 04:59:51 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA26180
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 04:57:06 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.10479-0@bells.cs.ucl.ac.uk>; Tue, 12 Nov 2002 09:59:34 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Mpierce1@aol.com
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Requirements for Accounting
In-reply-to: Your message of "Mon, 11 Nov 2002 21:44:01 EST." <f.1fc01d0.2b01c4f1@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Date: Tue, 12 Nov 2002 09:59:33 +0000
Message-ID: <595.1037095173@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAC9xpv20801
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> > this relates to the issue that Ran and I have brought up separately 
> > about avoiding confusion that the document be misconstrued as an 
> > IETF statement that X, Y, and Z must be done.  Rather, we wanted to 
> > reinforce the notion that if a service is available it is because 
> > a business contract in some form exists -- ie, there is no such thing 
> > as a free lunch.  Having stated that, we can make another pass at 
> > trying to further clarify this intent. 
>
> 
> [MAP] I certainly thought that it was understood and agreed across the
> board that no IETF document ever placed an actual requirement on any
> carrier or vendor to do anything.

yes, it is understood by those that participate in the IETF, or have read 
various drafts/RFCs produced by the body.  

> If that is not the case, then we have
> a bigger problem. It must be generally understood that all IETF documents
> by themselves do not require anyone to do anything. I'm confused by this
> belief that we need to make extra strong statements for this case. If
> this is needed, then it should be in a common statement in the beginning
> of every RFC. Perhaps the IAB should address this. 

we've talked about this a few weeks ago.  the IEPREP is a rather 
different group than the others within the IETF in both the wide 
variety of backgrounds participating, and those that will be reading
the documents produced by it.  normally, I would agree that there is
no need to make any extra strong statement that IETF documents are not to 
be confused as mandates that must be followed by the comunity or vendors.
however, I think its important to take into account non-technical folks,
and more importantly people unfamiliar with the IETF, and go the extra
mile to point out things.  this also means being a bit more descriptive
than normal in drafts to make sure all technical participants understand 
whats being accomplished.

so yes, the strong statements are abnormal, but this sort of an abnormal
group :-)

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 06:02:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27104
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 06:02:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACB4xt23969
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 06:04:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACB4wv23966
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 06:04:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27101
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 06:02:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACB45v23941;
	Tue, 12 Nov 2002 06:04:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACB36v23908
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 06:03:06 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA27067
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 06:00:31 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.16414-0@bells.cs.ucl.ac.uk>; Tue, 12 Nov 2002 11:02:59 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Sean Donelan <sean@donelan.com>
cc: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-reply-to: Your message of "Mon, 11 Nov 2002 14:36:47 EST." <Pine.GSO.4.44.0211111425490.18635-100000@clifden.donelan.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 12 Nov 2002 11:02:57 +0000
Message-ID: <741.1037098977@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> http://www.atis.org/pub/clc/niif/issues/0207.doc
> 
> Although words like voluntary are used, unless the capability is widely
> deployed, it won't be very useful.  Its probably better to read the drafts
> with the understanding you will be implementing them, one way or another.

it depends on the capability and objectives one is speaking of.

folks running GETS will correct me on the following, but my understanding 
is that the NCS has business contracts with just a subset of telco 
carriers
to support additional functionality.  no contract, no special service.  
also, the current GETS system doesn't offer any special service within 
a land-line exchange.  finally, GETS doesn't allow preemption, just an 
increase in the probability that the call gets through -- with I believe 
caps on how many calls can receive the additional service.

taking a step back, this represents a nice design philosophy in that
added service does not have to span from end-to-end nor does it need
to be ubiquitous -- just try and focus on the perceived "hot spots".  
I would like to keep this philosophy in at least some of the drafts.

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 07:06:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28376
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 07:06:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACC8hj27987
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 07:08:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACC8hv27984
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 07:08:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28364
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 07:06:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACC84v27968;
	Tue, 12 Nov 2002 07:08:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACC7Vv27951
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 07:07:31 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28320
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 07:04:57 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Tue, 12 Nov 2002 07:07:06 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111207071225973
 ; Tue, 12 Nov 2002 07:07:12 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMFW0HL4>; Tue, 12 Nov 2002 07:08:33 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64231E536@mcl-its-exs01>
From: "Garrity, Jack" <JOHN.J.GARRITY@saic.com>
To: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>,
        Sean Donelan <sean@donelan.com>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
Date: Tue, 12 Nov 2002 07:07:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ken,

I'll try to evaluate your message content after you expand a bit on your
statement about "the current GETS system doesn't offer any special service
within a land-line exchange."  

 ~~~ Jack ~~~
Work: 703/676-2358 | Fax: 703/484-0299
Home: 703/278-9250 | Cell: 703/508-0065
Email: garrityj@saic.com

-----Original Message-----
From: Ken Carlberg [mailto:K.Carlberg@cs.ucl.ac.uk]
Sent: Tuesday, November 12, 2002 6:03 AM
To: Sean Donelan
Cc: ieprep
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion
request



> http://www.atis.org/pub/clc/niif/issues/0207.doc
> 
> Although words like voluntary are used, unless the capability is widely
> deployed, it won't be very useful.  Its probably better to read the drafts
> with the understanding you will be implementing them, one way or another.

it depends on the capability and objectives one is speaking of.

folks running GETS will correct me on the following, but my understanding 
is that the NCS has business contracts with just a subset of telco 
carriers
to support additional functionality.  no contract, no special service.  
also, the current GETS system doesn't offer any special service within 
a land-line exchange.  finally, GETS doesn't allow preemption, just an 
increase in the probability that the call gets through -- with I believe 
caps on how many calls can receive the additional service.

taking a step back, this represents a nice design philosophy in that
added service does not have to span from end-to-end nor does it need
to be ubiquitous -- just try and focus on the perceived "hot spots".  
I would like to keep this philosophy in at least some of the drafts.

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 07:28:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28680
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 07:28:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACCUwU28707
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 07:30:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCUwv28704
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 07:30:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28666
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 07:28:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCU3v28690;
	Tue, 12 Nov 2002 07:30:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCTWv28664
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 07:29:32 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA28645
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 07:26:58 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.25163-0@bells.cs.ucl.ac.uk>; Tue, 12 Nov 2002 12:29:16 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: "Garrity, Jack" <JOHN.J.GARRITY@saic.com>
cc: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-reply-to: Your message of "Tue, 12 Nov 2002 07:07:02 EST." <B8030EB94AF1D51196D70002A589D64231E536@mcl-its-exs01>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 12 Nov 2002 12:29:16 +0000
Message-ID: <892.1037104156@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> I'll try to evaluate your message content after you expand a bit on your
> statement about "the current GETS system doesn't offer any special service
> within a land-line exchange."  

by this I meant that if one were to make a 'local' call within a LEC 
(eg, Brooklyn NY, to Manhattan NY), the NS/EP code point and HPC
services don't take effect until the call signaling goes from the 
origin LEC to the IXC.  further, that the NS/EP call doesn't extend
to the destination end-office.  so things like extended trunk queuing
is not done along the entire path between the originator and the 
destination in the US PSTN.  have I got that right?

-ken



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 07:36:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28835
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 07:36:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACCcgG29569
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 07:38:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCcgv29566
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 07:38:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28824
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 07:36:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCc4v29530;
	Tue, 12 Nov 2002 07:38:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCbiv29509
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 07:37:44 -0500
Received: from mail.san.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28775
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 07:35:09 -0500 (EST)
Received: from pack1 (68.84.53.108) by mail.san.yahoo.com (6.5.029)
        id 3DD0C3880000B969; Tue, 12 Nov 2002 04:36:22 -0800
Message-ID: <00d701c28a48$44848890$6400a8c0@sumt01.nj.comcast.net>
From: "Krishnan Padmanabhan, Packet Strategies LLC" <krishnan@packetstrategies.com>
To: "RJ Atkinson" <rja@extremenetworks.com>
Cc: <ieprep@ietf.org>
References: <F4F1EEBA-F5C6-11D6-B1C0-00039357A82A@extremenetworks.com>
Date: Tue, 12 Nov 2002 07:37:30 -0500
Organization: Packet Strategies, LLC
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00D4_01C28A1E.5B080760"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Ieprep] Billing for VoIp service
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_00D4_01C28A1E.5B080760
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Via Windows Messenger or MSN Messenger, you can subscribe to the VoIP =
services offered by several service providers. At least two of these (I =
haven't tried the others) provide per minute billing for the IP =
Telephony calls, call details, history, etc. They also appear to offer, =
in addition to IP telephony, the usual internet access services. Would =
these offer a counter-example to the point you make here?
Krishnan.
  ----- Original Message -----=20
  From: RJ Atkinson=20
  To: Mpierce1@aol.com=20
  Cc: woody@pch.net ; ieprep@ietf.org=20
  Sent: Monday, November 11, 2002 5:43 PM
  Subject: Re: [Ieprep] Atlanta ieprep Agenda



  On Monday, Nov 11, 2002, at 13:58 America/Montreal, Mpierce1@aol.com=20
  wrote:
  > Besides, just because you don't want to "bill" for service in your=20
  > network,

  ISPs bill for service.  They bill based solely on IP layer properties=20
  (or lower layer
  ones, like what speed physical link does the customer have in place=20
  from that ISP).
  Most ISPs perform flat-rate billing, tiered by link access max=20
  bandwidth.  Some
  offer a kind of usage-based billing (e.g. 90th percentile of the=20
  traffic measurements
  where instantaneous bandwidth on the customer link is measured via =
SNMP=20
  counters
  every N minutes).  None of that gets into *upper-layer* services such=20
  as VoIP
  or FTP or EMAIL.


  Ran


------=_NextPart_000_00D4_01C28A1E.5B080760
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3D"Tw Cen MT" size=3D2>Via Windows Messenger or MSN =
Messenger, you=20
can subscribe to the VoIP services offered by&nbsp;several service =
providers. At=20
least two of these (I haven't tried the others) provide per minute =
billing for=20
the IP Telephony calls, call details, history, etc. They also appear to =
offer,=20
in addition to IP telephony, the usual internet access services. Would=20
these&nbsp;offer a counter-example to the point you make =
here?</FONT></DIV>
<DIV><FONT face=3D"Tw Cen MT" size=3D2>Krishnan.</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Drja@extremenetworks.com =
href=3D"mailto:rja@extremenetworks.com">RJ=20
  Atkinson</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3DMpierce1@aol.com =

  href=3D"mailto:Mpierce1@aol.com">Mpierce1@aol.com</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A title=3Dwoody@pch.net=20
  href=3D"mailto:woody@pch.net">woody@pch.net</A> ; <A =
title=3Dieprep@ietf.org=20
  href=3D"mailto:ieprep@ietf.org">ieprep@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, November 11, 2002 =
5:43=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [Ieprep] Atlanta =
ieprep=20
  Agenda</DIV>
  <DIV><BR></DIV><BR>On Monday, Nov 11, 2002, at 13:58 America/Montreal, =
<A=20
  href=3D"mailto:Mpierce1@aol.com">Mpierce1@aol.com</A> =
<BR>wrote:<BR>&gt;=20
  Besides, just because you don't want to "bill" for service in your =
<BR>&gt;=20
  network,<BR><BR>ISPs bill for service.&nbsp; They bill based solely on =
IP=20
  layer properties <BR>(or lower layer<BR>ones, like what speed physical =
link=20
  does the customer have in place <BR>from that ISP).<BR>Most ISPs =
perform=20
  flat-rate billing, tiered by link access max <BR>bandwidth.&nbsp;=20
  Some<BR>offer a kind of usage-based billing (e.g. 90th percentile of =
the=20
  <BR>traffic measurements<BR>where instantaneous bandwidth on the =
customer link=20
  is measured via SNMP <BR>counters<BR>every N minutes).&nbsp; None of =
that gets=20
  into *upper-layer* services such <BR>as VoIP<BR>or FTP or=20
  EMAIL.<BR><BR><BR>Ran<BR><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_00D4_01C28A1E.5B080760--


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 07:39:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28892
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 07:39:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACCfdK29703
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 07:41:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCfdv29700
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 07:41:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28869
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 07:39:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCf3v29672;
	Tue, 12 Nov 2002 07:41:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCeov29654
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 07:40:50 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28862
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 07:38:15 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Tue, 12 Nov 2002 07:40:33 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111207403810634
 ; Tue, 12 Nov 2002 07:40:38 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMFW0H42>; Tue, 12 Nov 2002 07:41:59 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64231E537@mcl-its-exs01>
From: "Garrity, Jack" <JOHN.J.GARRITY@saic.com>
To: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
Date: Tue, 12 Nov 2002 07:40:30 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ken,

For the scenario you describe, the NS/EP codepoint and NS/EP features take
effect at GETS-capable local exchanges.  Those exchanges serve over X
percent of US-based access lines, where X is on the order of 85 percent or
greater.

Once the call reaches a GETS-capable local exchange or a GETS interexchange
carrier, the NS/EP treatment is carried through to the terminating local
exchanges.  If the terminating local exchange is GETS-capable (same switches
as in the first paragraph), NS/EP features have effect.

I won't guarantee this description entirely.  If this description suffices,
I'll be ready to try to evaluate the content in your original message.

~~~ Jack ~~~
Work: 703/676-2358 | Fax: 703/848-0299
Home: 703/278-9250 | Cell: 703/508-0065
E-mail: garrityj@saic.com


-----Original Message-----
From: Ken Carlberg [mailto:K.Carlberg@cs.ucl.ac.uk]
Sent: Tuesday, November 12, 2002 7:29 AM
To: Garrity, Jack
Cc: ieprep
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion
request



> I'll try to evaluate your message content after you expand a bit on your
> statement about "the current GETS system doesn't offer any special service
> within a land-line exchange."  

by this I meant that if one were to make a 'local' call within a LEC 
(eg, Brooklyn NY, to Manhattan NY), the NS/EP code point and HPC
services don't take effect until the call signaling goes from the 
origin LEC to the IXC.  further, that the NS/EP call doesn't extend
to the destination end-office.  so things like extended trunk queuing
is not done along the entire path between the originator and the 
destination in the US PSTN.  have I got that right?

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 07:41:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28954
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 07:41:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACChh329813
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 07:43:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACChhv29810
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 07:43:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28929
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 07:41:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCg1v29738;
	Tue, 12 Nov 2002 07:42:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCf6v29687
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 07:41:06 -0500
Received: from mtiwmhc13.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28866
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 07:38:32 -0500 (EST)
Received: from cs.columbia.edu ([12.91.168.47])
          by mtiwmhc13.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP
          id <20021112124103.ONMZ24110.mtiwmhc13.worldnet.att.net@cs.columbia.edu>;
          Tue, 12 Nov 2002 12:41:03 +0000
Message-ID: <3DD0F667.1030207@cs.columbia.edu>
Date: Tue, 12 Nov 2002 07:39:03 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott Bradner <sob@harvard.edu>
CC: Mpierce1@aol.com, ieprep@ietf.org, rja@extremenetworks.com
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion
 request]
References: <200211120433.gAC4XeR2018368@newdev.harvard.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Scott Bradner wrote:
>>a permissible call defect rate of 0.00001%
> 
> 
> 1/ I've not heard of an FCC requirement but maybe 

I'm inquiring with sources within the FCC.

> 
> 2/ what is a defect - in the context of the Internet?
> 	I would doubt that it is a dropped packet

There are at least three possible defects:
- Call rings, callee picks up and then there's no conversation (due to 
failure of local resource reservation; this is the problem the 
PacketCable folks worried about since they need to manage the very 
limited upstream bandwidth)

- sufficient duration of excessive packet drops that users abandon the 
call (somewhere around 10s, half of the callers are likely to drop the 
call, says a study)

- sufficient sustained packet loss that the MOS drops below an 
acceptable threshold for the call


> 
> Scott

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 07:47:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29087
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 07:47:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACCnnY29994
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 07:49:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCnnv29991
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 07:49:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29076
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 07:47:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCn1v29968;
	Tue, 12 Nov 2002 07:49:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCm4v29944
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 07:48:04 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29029
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 07:45:28 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Tue, 12 Nov 2002 07:47:44 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111207475020954
 ; Tue, 12 Nov 2002 07:47:50 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WMFW0HX3>; Tue, 12 Nov 2002 07:49:11 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64231E539@mcl-its-exs01>
From: "Garrity, Jack" <JOHN.J.GARRITY@saic.com>
To: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>
Cc: "'ieprep'" <ieprep@ietf.org>
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
Date: Tue, 12 Nov 2002 07:47:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ken,

ADDENDUM

Some suggested that I add the point that the transit carriers, local
exchange carriers and interexchange carriers, are paid for providing the
NS/EP services. 

~~~ Jack ~~~
Work: 703/676-2358 | Fax: 703/848-0299
Home: 703/278-9250 | Cell: 703/508-0065
E-mail: garrityj@saic.com


-----Original Message-----
From: Garrity, Jack 
Sent: Tuesday, November 12, 2002 7:41 AM
To: 'Ken Carlberg'
Cc: ieprep
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion
request


Ken,

For the scenario you describe, the NS/EP codepoint and NS/EP features take
effect at GETS-capable local exchanges.  Those exchanges serve over X
percent of US-based access lines, where X is on the order of 85 percent or
greater.

Once the call reaches a GETS-capable local exchange or a GETS interexchange
carrier, the NS/EP treatment is carried through to the terminating local
exchanges.  If the terminating local exchange is GETS-capable (same switches
as in the first paragraph), NS/EP features have effect.

I won't guarantee this description entirely.  If this description suffices,
I'll be ready to try to evaluate the content in your original message.

~~~ Jack ~~~
Work: 703/676-2358 | Fax: 703/848-0299
Home: 703/278-9250 | Cell: 703/508-0065
E-mail: garrityj@saic.com


-----Original Message-----
From: Ken Carlberg [mailto:K.Carlberg@cs.ucl.ac.uk]
Sent: Tuesday, November 12, 2002 7:29 AM
To: Garrity, Jack
Cc: ieprep
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion
request



> I'll try to evaluate your message content after you expand a bit on your
> statement about "the current GETS system doesn't offer any special service
> within a land-line exchange."  

by this I meant that if one were to make a 'local' call within a LEC 
(eg, Brooklyn NY, to Manhattan NY), the NS/EP code point and HPC
services don't take effect until the call signaling goes from the 
origin LEC to the IXC.  further, that the NS/EP call doesn't extend
to the destination end-office.  so things like extended trunk queuing
is not done along the entire path between the originator and the 
destination in the US PSTN.  have I got that right?

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 07:52:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29193
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 07:52:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACCs6h30176
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 07:54:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCs6v30173
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 07:54:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29184
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 07:51:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCr7v30122;
	Tue, 12 Nov 2002 07:53:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACCqOv30091
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 07:52:24 -0500
Received: from bootstrap.agcs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29126
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 07:49:43 -0500 (EST)
Received: from pxmail1.agcs.com (pxmail1.agcs.com [130.131.52.9])
	by bootstrap.agcs.com (Pro-8.9.3/8.9.3) with ESMTP id FAA15658
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 05:52:14 -0700 (MST)
Received: from mkultra ([130.131.166.68]) by pxmail1.agcs.com
          (Netscape Messaging Server 4.15 pxmail1 Mar  5 2002 15:11:07)
          with SMTP id H5GRR200.SVV for <ieprep@ietf.org>; Tue, 12 Nov
          2002 05:52:14 -0700 
Received: FROM agcs.com BY mkultra ; Tue Nov 12 05:52:11 2002 -0700
Message-ID: <3DD0F975.BD52DFA@agcs.com>
Date: Tue, 12 Nov 2002 05:52:05 -0700
From: "Stuart (Stu) Goldman" <goldmans@agcs.com>
Reply-To: goldmans@agcs.com
Organization: AG Communication Systems
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Sean Donelan <sean@donelan.com>
CC: ieprep@ietf.org, MARIA ESTEFANIA <MESTEFANIA@ATIS.ORG>,
        Frank Suraci <suracif@ncs.gov>,
        leonard chun <leonard.chun@mail.sprint.com>,
        Bob Amling <ramling@telcordia.com>,
        David Bench <dbench@nortelnetworks.com>
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
References: <Pine.GSO.4.44.0211111425490.18635-100000@clifden.donelan.com>
Content-Type: multipart/mixed;
 boundary="------------6B01B6C2CA3BC8D150BF1781"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.
--------------6B01B6C2CA3BC8D150BF1781
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Sean,

I am the Moderator of the NIIF. I was confused by your reference to NIIF issue
0207, as this issue is not asking the FCC for assistance.

Issue 0207 is part of a collection of related issues that are addressing call
failures. They seem to have some common characteristics such as wireless,
roaming, and toll free. We are in the process of working the issues by first
trying to get a better understanding of the failure mechanism and if there is a
common root cause. One high runner theory at the moment is that correct
population of the various SS7 IAM fields including the JIP may resolve the bulk
of the failures, although such a conclusion would be premature.

The NIIF invites contributions to help resolve our issues. The next meeting is
the week of Jan. 12, 2003. Please contact me or Maria Estefania directly if any
of you  have any interest.

Sean Donelan wrote:

> On Mon, 11 Nov 2002, Bill Woodcock wrote:
> > That should be stated explicitly, so that customers who read the document
> > understand that their ISP cannot sell them an end-to-end service, no
> > matter how much they'd like to.
>
> Once a standard exists, will the FCC be asked to assit in gaining
> compliance with the standard?
>
> http://www.atis.org/pub/clc/niif/issues/0207.doc
>
> Although words like voluntary are used, unless the capability is widely
> deployed, it won't be very useful.  Its probably better to read the drafts
> with the understanding you will be implementing them, one way or another.
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

--------------6B01B6C2CA3BC8D150BF1781
Content-Type: text/x-vcard; charset=us-ascii;
 name="goldmans.vcf"
Content-Description: Card for Stuart (Stu) Goldman
Content-Disposition: attachment;
 filename="goldmans.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Goldman;-Stuart
tel;cell:623 582 7136
tel;fax:623 582 7111
tel;home:602 493 8438  
tel;work:623 582 7136
x-mozilla-html:TRUE
org:AG Communication Systems
adr:;;P.O. Box 52179;Phoenix;AZ;85072-2179;USA
version:2.1
email;internet:goldmans@agcs.com
x-mozilla-cpt:;3944
fn:Stuart Goldman
end:vcard

--------------6B01B6C2CA3BC8D150BF1781--

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 08:06:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29450
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 08:06:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACD8QC31201
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 08:08:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACD8Qv31198
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 08:08:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29434
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 08:05:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACD7Qv31135;
	Tue, 12 Nov 2002 08:07:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACD62v30523
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 08:06:02 -0500
Received: from bootstrap.agcs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29378
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 08:03:26 -0500 (EST)
Received: from pxmail1.agcs.com (pxmail1.agcs.com [130.131.52.9])
	by bootstrap.agcs.com (Pro-8.9.3/8.9.3) with ESMTP id GAA17148
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 06:05:58 -0700 (MST)
Received: from mkultra ([130.131.166.68]) by pxmail1.agcs.com
          (Netscape Messaging Server 4.15 pxmail1 Mar  5 2002 15:11:07)
          with SMTP id H5GSDY00.VSI for <ieprep@ietf.org>; Tue, 12 Nov
          2002 06:05:58 -0700 
Received: FROM agcs.com BY mkultra ; Tue Nov 12 06:05:57 2002 -0700
Message-ID: <3DD0FCAF.F0CFD69E@agcs.com>
Date: Tue, 12 Nov 2002 06:05:51 -0700
From: "Stuart (Stu) Goldman" <goldmans@agcs.com>
Reply-To: goldmans@agcs.com
Organization: AG Communication Systems
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Garrity Jack" <JOHN.J.GARRITY@saic.com>
CC: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
References: <B8030EB94AF1D51196D70002A589D64231E537@mcl-its-exs01>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ken,

Jack's description matches my understanding. Once the NS/EP value is set in the
SS7 IAM CPC, the call is identified as an HPC (High Probability of Completion)
call.


"Garrity, Jack" wrote:

> Ken,
>
> For the scenario you describe, the NS/EP codepoint and NS/EP features take
> effect at GETS-capable local exchanges.  Those exchanges serve over X
> percent of US-based access lines, where X is on the order of 85 percent or
> greater.
>
> Once the call reaches a GETS-capable local exchange or a GETS interexchange
> carrier, the NS/EP treatment is carried through to the terminating local
> exchanges.  If the terminating local exchange is GETS-capable (same switches
> as in the first paragraph), NS/EP features have effect.
>
> I won't guarantee this description entirely.  If this description suffices,
> I'll be ready to try to evaluate the content in your original message.
>
> ~~~ Jack ~~~
> Work: 703/676-2358 | Fax: 703/848-0299
> Home: 703/278-9250 | Cell: 703/508-0065
> E-mail: garrityj@saic.com
>
> -----Original Message-----
> From: Ken Carlberg [mailto:K.Carlberg@cs.ucl.ac.uk]
> Sent: Tuesday, November 12, 2002 7:29 AM
> To: Garrity, Jack
> Cc: ieprep
> Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion
> request
>
> > I'll try to evaluate your message content after you expand a bit on your
> > statement about "the current GETS system doesn't offer any special service
> > within a land-line exchange."
>
> by this I meant that if one were to make a 'local' call within a LEC
> (eg, Brooklyn NY, to Manhattan NY), the NS/EP code point and HPC
> services don't take effect until the call signaling goes from the
> origin LEC to the IXC.  further, that the NS/EP call doesn't extend
> to the destination end-office.  so things like extended trunk queuing
> is not done along the entire path between the originator and the
> destination in the US PSTN.  have I got that right?
>
> -ken
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 09:00:16 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00568
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 09:00:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACE2KX01438
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 09:02:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACE2Kv01435
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 09:02:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00561
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 08:59:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACE19v01378;
	Tue, 12 Nov 2002 09:01:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8PXv15610
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 03:25:33 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24825
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 03:22:44 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAC8JKd23420
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 00:19:20 -0800 (PST)
Date: Tue, 12 Nov 2002 00:19:20 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: ieprep@ietf.org
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting  approach,
 etc. (fwd)
Message-ID: <Pine.GSO.4.44.0211120016290.16502-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


Here's some data.  The only person I know who deals with congested links
routinely is the engineering manager for a bandwidth-manager product.
Here's what he had to say about the prevalence of real-time traffic on
the Internet, versus file sharing.

                                -Bill


---------- Forwarded message ----------
Date: Mon, 11 Nov 2002 21:00:24 -0800
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting  approach,
     etc. (fwd)

Interactive video conferencing or VoIP is so small it doesn't even hit our
radar - a couple percent at most.

On unmanaged links we typically see 60%-80% peer to peer, 10% web and
volume goes down from that.  The P2P volume is so immense it dwarfs FTP,
News, Mail, and even Web which are traditional large bandwidth consumers.

The biggest live video components are probably Yahoo Messenger Webcam's,
WebCam32 traffic over HTTP, NetMeeting, maybe PalTalk.  Internet Radio over
RealPlayer is probably the other large realtime consumer if you consider
that VoIP.

Here is data from a couple of our clients boxes that might help you make an
analysis.  If you see applications that are clearly not widely deployed
like "MCK-VoIP" gateways by MCK it is probably some other app, likely
filesharing, using the MCK ports which has been mis-identified (but which a
router filter on the same ports would make the same
mis-identification).  Each release less of our code uses by-port analysis,
especially now that KaZaA 2.0 lets users pick their serving port and so has
effectively obsoleted port-based strategies for controlling/limiting
applications.

I'll let you do the aggregation when they have a "folder" in their tree
with some subnet that replicates counts for apps that are also matching
other addresses.  I'm including a list of what partitions (bandwidth
limits) they put in place as well as bytes transferred per-application.  If
a site has lots of "default" traffic it is likely from port-based
applications PacketShaper does not recognize.

-Richard

Site one - major university serving as path between a statewide network
that includes thousands of K12 schools and the Internet.

PacketShaper# part show

Partition name          Size          Grntd       Prior       Curr  1-Min
                         Min /  Max          Excess      Usage       Avg   Peak
-------------------------------------------------------------------------------
/Inbound               200.0M 200.0M     0     0 126.4M126.4M119.9M116.0M181.7M
  /Inbound/ICMP             0    1.0M     0     0   119k  119k  116k  148k
354k
  /Inbound/Dorm             0   50.0M     0     0  25.5M 25.5M 26.8M 26.6M
40.5M
   /Inbound/Dorm/ICMP       0    1.0M     0     0  9984  9984  4505  3455
995k
   /Inbound/Dorm/HBRec      0   20.0M     0     0  20.0M 20.0M 19.8M 19.7M
20.1M
  /Inbound/Campus/HBRec     0   20.0M     0     0  20.0M 20.0M 19.9M 19.9M
20.2M

-------------------------------------------------------------------------------
/Outbound              200.0M 200.0M     0     0 153.8M153.8M156.1M149.0M206.8M
  /Outbound/ICMP            0    1.0M     0     0  27.1k 27.1k 39.8k
76.8k  1.0M
  /Outbound/Dorm            0   50.0M     0     0  24.8M 24.8M 24.1M 24.7M
51.3M
   /Outbound/Dorm/HBRec     0   20.0M     0     0  20.0M 20.0M 19.1M 19.4M
20.1M
  /Outbound/Campus/HBRec    0   20.0M     0     0  20.0M 20.0M 19.8M 19.6M
20.2M

PacketShaper# me dump class all inbound by element 30d bytes
"time:12-Oct-2002 23:00:00"
"class","bytes"
"/Inbound/Mirror_Servers/ScavengerService/FTP",210810713
"/Inbound/Mirror_Servers/ScavengerService/HTTP",220487542
"/Inbound/Mirror_Servers/ScavengerService/rsync",428617384
"/Inbound/Mirror_Servers/ScavengerService/DNS",736475
"/Inbound/Mirror_Servers/ScavengerService/ICMP",4208705
"/Inbound/Mirror_Servers/ScavengerService/Default",1696215
"/Inbound/Mirror_Servers/Citrix/Default",13433
"/Inbound/Mirror_Servers/FTP",42883093490
"/Inbound/Mirror_Servers/Half-Life",23910
"/Inbound/Mirror_Servers/HTTP",36533866881
"/Inbound/Mirror_Servers/Ident",109843
"/Inbound/Mirror_Servers/lockd",2672
"/Inbound/Mirror_Servers/MPEG-Video",2134064
"/Inbound/Mirror_Servers/NTP",151476
"/Inbound/Mirror_Servers/QuickTime",15513022
"/Inbound/Mirror_Servers/rsync",88229768737
"/Inbound/Mirror_Servers/SMTP",250000
"/Inbound/Mirror_Servers/SSH",14829079
"/Inbound/Mirror_Servers/WinMedia",96717
"/Inbound/Mirror_Servers/DNS",115412763
"/Inbound/Mirror_Servers/ISAKMP",409584
"/Inbound/Mirror_Servers/Kontiki",950865
"/Inbound/Mirror_Servers/ICMP",37406164
"/Inbound/Mirror_Servers/Default",1691121388
"/Inbound/Dorm/Soribada",60524
"/Inbound/Dorm/HBRec/WinMX",64173632532
"/Inbound/Dorm/HBRec/Soulseek",2976958820
"/Inbound/Dorm/HBRec/Aimster",4559243
"/Inbound/Dorm/HBRec/Audiogalaxy",11293276
"/Inbound/Dorm/HBRec/DirectConnect",2642730026
"/Inbound/Dorm/HBRec/eDonkey",32920419006
"/Inbound/Dorm/HBRec/Gnutella/Gnutella-Download",33876822334
"/Inbound/Dorm/HBRec/Gnutella/Gnutella-Upload",1391389393
"/Inbound/Dorm/HBRec/Gnutella/Default",118785746125
"/Inbound/Dorm/HBRec/Hotline",188349418
"/Inbound/Dorm/HBRec/KaZaA/KaZaA-Download",4885506429032
"/Inbound/Dorm/HBRec/KaZaA/KaZaA-Upload",174420649506
"/Inbound/Dorm/HBRec/KaZaA/Default",163401867474
"/Inbound/Dorm/HBRec/Napster",4695135634
"/Inbound/Dorm/HBRec/ScourExchange",611
"/Inbound/Dorm/HBRec/Shoutcast",29379325649
"/Inbound/Dorm/HBRec/Blubster",838666524
"/Inbound/Dorm/Apache_OpenSSL_worm",0
"/Inbound/Dorm/AFS",44478369
"/Inbound/Dorm/AsheronsCall",203076355
"/Inbound/Dorm/ATSTCP",106258620
"/Inbound/Dorm/BackWeb",72931295
"/Inbound/Dorm/ccMail",78107467
"/Inbound/Dorm/CIFS-TCP",94119505
"/Inbound/Dorm/Citrix/Default",2340264686
"/Inbound/Dorm/CitrixIMA",1128826271
"/Inbound/Dorm/CUSeeMe",5674
"/Inbound/Dorm/CVSpserver",167271
"/Inbound/Dorm/DHCP",2448
"/Inbound/Dorm/DLS",1333746707
"/Inbound/Dorm/Doom",653531681
"/Inbound/Dorm/FileMaker",31907938
"/Inbound/Dorm/FileRouge",0
"/Inbound/Dorm/Finger",8448204
"/Inbound/Dorm/FTP",136895796920
"/Inbound/Dorm/Furthurnet",29802689155
"/Inbound/Dorm/Gopher",82607
"/Inbound/Dorm/Groupwise",29827486
"/Inbound/Dorm/Half-Life",20943847053
"/Inbound/Dorm/HTTP",582864156901
"/Inbound/Dorm/Ident",4647344783
"/Inbound/Dorm/IMAP",252569128
"/Inbound/Dorm/IRC",193802170025
"/Inbound/Dorm/Kali",135609221
"/Inbound/Dorm/Kerberos",153757
"/Inbound/Dorm/L2TP",16942546
"/Inbound/Dorm/LDAP",1779932
"/Inbound/Dorm/lockd",9491
"/Inbound/Dorm/LotusNotes",1160520431
"/Inbound/Dorm/LucasArts",1179005927
"/Inbound/Dorm/Marimba",729552943
"/Inbound/Dorm/MCK-Signaling",280950246
"/Inbound/Dorm/Micom-VIP",0
"/Inbound/Dorm/MPEG-Audio",18848970449
"/Inbound/Dorm/MPEG-Video",25622855714
"/Inbound/Dorm/MSN-Messenger",3780896706
"/Inbound/Dorm/MSN-Zone",0
"/Inbound/Dorm/MSSQL",1059446343
"/Inbound/Dorm/NNTP",152059491
"/Inbound/Dorm/NTP",1424249
"/Inbound/Dorm/NW5-CMD",2601111
"/Inbound/Dorm/Oracle",4230930744
"/Inbound/Dorm/OracleEM",201561929
"/Inbound/Dorm/PEPGate",243679874
"/Inbound/Dorm/Persona",1012309396
"/Inbound/Dorm/POP3",4701345548
"/Inbound/Dorm/PPTP",492728307
"/Inbound/Dorm/Quake",973096764
"/Inbound/Dorm/QuickTime",34367005571
"/Inbound/Dorm/RADIUS",8271533
"/Inbound/Dorm/RC5DES",2000239639
"/Inbound/Dorm/RDP",1401008055
"/Inbound/Dorm/Real",23118311267
"/Inbound/Dorm/rsync",1899312
"/Inbound/Dorm/RTCP-I",43774503
"/Inbound/Dorm/RTP-I",5316174773
"/Inbound/Dorm/rwho",43142
"/Inbound/Dorm/SHARESUDP",8172742
"/Inbound/Dorm/SMTBF",39689534
"/Inbound/Dorm/SMTP",853030015
"/Inbound/Dorm/SNMP",28286
"/Inbound/Dorm/SOCKS",205012
"/Inbound/Dorm/SSDP",1993765
"/Inbound/Dorm/SSH",79396803
"/Inbound/Dorm/SSL",6721787529
"/Inbound/Dorm/Syslog",48
"/Inbound/Dorm/T.120",69441741
"/Inbound/Dorm/Telnet",34840760576
"/Inbound/Dorm/Timbuktu",6364544098
"/Inbound/Dorm/Tripnosis",0
"/Inbound/Dorm/Unreal",2859950608
"/Inbound/Dorm/VNC",21389408
"/Inbound/Dorm/Webshots",34226554
"/Inbound/Dorm/WHOIS",471013
"/Inbound/Dorm/WinMedia",33773206752
"/Inbound/Dorm/XWindows",54106156
"/Inbound/Dorm/YahooGames",417396348
"/Inbound/Dorm/YahooMsg",174133806
"/Inbound/Dorm/AOL-IM-ICQ",33604389794
"/Inbound/Dorm/Battle.net",980856121
"/Inbound/Dorm/CU-DEV",0
"/Inbound/Dorm/CVSup",2476477
"/Inbound/Dorm/Day-Time",816819017
"/Inbound/Dorm/DNS",18723093327
"/Inbound/Dorm/Echo",178995
"/Inbound/Dorm/H.323",1554490491
"/Inbound/Dorm/INFOC-RTMS",14239
"/Inbound/Dorm/ISAKMP",26736772
"/Inbound/Dorm/Kontiki",94762065
"/Inbound/Dorm/MeetingMaker",0
"/Inbound/Dorm/MSSQ",3761642065
"/Inbound/Dorm/Mythic",954653075
"/Inbound/Dorm/NetBIOS-IP",4970822
"/Inbound/Dorm/NFS",6433185
"/Inbound/Dorm/NW5-NCP",532522
"/Inbound/Dorm/pcANYWHERE",3182747
"/Inbound/Dorm/RTSP",175291847
"/Inbound/Dorm/SLP",3060
"/Inbound/Dorm/SMS",2236163314
"/Inbound/Dorm/SonyOnline",1363273132
"/Inbound/Dorm/StreamWorks",327284374
"/Inbound/Dorm/TimeServer",1003455
"/Inbound/Dorm/Tribes",103253020
"/Inbound/Dorm/Unavailable",0
"/Inbound/Dorm/WINS",16300
"/Inbound/Dorm/ICMP",1193892271
"/Inbound/Dorm/Protocol_102",3329
"/Inbound/Dorm/Protocol_41",4403
"/Inbound/Dorm/Protocol_54",31966
"/Inbound/Dorm/RSVP",8134
"/Inbound/Dorm/DiscoveredPorts/TCP_Port_1214",2727001065
"/Inbound/Dorm/DiscoveredPorts/TCP_Port_5750",3520
"/Inbound/Dorm/DiscoveredPorts/TCP_Port_6667",1212709
"/Inbound/Dorm/DiscoveredPorts/UDP_Port_1556",752981
"/Inbound/Dorm/DiscoveredPorts/UDP_Port_1626",139849
"/Inbound/Dorm/DiscoveredPorts/UDP_Port_1689",144647
"/Inbound/Dorm/DiscoveredPorts/UDP_Port_1943",282407
"/Inbound/Dorm/DiscoveredPorts/UDP_Port_27926",1245627
"/Inbound/Dorm/DiscoveredPorts/UDP_Port_2861",57326653
"/Inbound/Dorm/DiscoveredPorts/UDP_Port_2993",22258
"/Inbound/Dorm/DiscoveredPorts/UDP_Port_3090",26733069
"/Inbound/Dorm/DiscoveredPorts/UDP_Port_3674",308338
"/Inbound/Dorm/Default",855904671679
"/Inbound/Localhost",27549999
"/Inbound/SameSide",3756390
"/Inbound/Campus/HBRec/WinMX",47262266253
"/Inbound/Campus/HBRec/Soulseek",121145932337
"/Inbound/Campus/HBRec/Aimster",385629790
"/Inbound/Campus/HBRec/Audiogalaxy",70585549
"/Inbound/Campus/HBRec/DirectConnect",4524961731
"/Inbound/Campus/HBRec/eDonkey",119015286370
"/Inbound/Campus/HBRec/Gnutella/Gnutella-Download",28276909188
"/Inbound/Campus/HBRec/Gnutella/Gnutella-Upload",1871323856
"/Inbound/Campus/HBRec/Gnutella/Default",102465608437
"/Inbound/Campus/HBRec/Hotline",38427899
"/Inbound/Campus/HBRec/KaZaA/KaZaA-Download",4892818077973
"/Inbound/Campus/HBRec/KaZaA/KaZaA-Upload",233784488046
"/Inbound/Campus/HBRec/KaZaA/Default",109488498657
"/Inbound/Campus/HBRec/Napster",15867526878
"/Inbound/Campus/HBRec/ScourExchange",3021072
"/Inbound/Campus/HBRec/Shoutcast",314144717454
"/Inbound/Campus/HBRec/Blubster",3115319873
"/Inbound/ScavengerService",85254586508
"/Inbound/GRE",1780146821
"/Inbound/TC2-Netflow-Export",265306832505
"/Inbound/Multicast/L2TP",0
"/Inbound/Multicast/NTP",8735542
"/Inbound/Multicast/RTCP-I",63773558
"/Inbound/Multicast/RTP-I",35917933007
"/Inbound/Multicast/SNMP",0
"/Inbound/Multicast/SSDP",29455730
"/Inbound/Multicast/SLP",49354240
"/Inbound/Multicast/WINS",54784
"/Inbound/Multicast/ICMP",6488
"/Inbound/Multicast/IGMP",3337
"/Inbound/Multicast/OSPF",0
"/Inbound/Multicast/PIM",21903488
"/Inbound/Multicast/Default",216580446473
"/Inbound/Apache_OpenSSL_worm",0
"/Inbound/Soribada",514926352
"/Inbound/AFP",119300
"/Inbound/AFS",24949086
"/Inbound/AsheronsCall",239802362
"/Inbound/ATSTCP",2723254379
"/Inbound/Attachmate-GW",218948
"/Inbound/BackWeb",242556929
"/Inbound/BGP",32357031
"/Inbound/ccMail",1277089724
"/Inbound/Chaincast",178239463
"/Inbound/CIFS-TCP",2166267281
"/Inbound/Citrix/Citrix-AFOATS_MAIL",10117387
"/Inbound/Citrix/Citrix-AFW_ONLINE",0
"/Inbound/Citrix/Citrix-CRYSTAL_REPORTS",262233
"/Inbound/Citrix/Citrix-E-net",383297
"/Inbound/Citrix/Citrix-ERM_305_VIA_METAFRAME",1266260
"/Inbound/Citrix/Citrix-EXTERNAL_800X600",0
"/Inbound/Citrix/Citrix-MICROSOFT_EXCEL",0
"/Inbound/Citrix/Citrix-Outlook_2000",7163667
"/Inbound/Citrix/Citrix-PEOPLESOFT_PRODUCTION_DA",19658892
"/Inbound/Citrix/Citrix-SABREVIEWAA1",0
"/Inbound/Citrix/Citrix-TSTEST",0
"/Inbound/Citrix/Default",3353009250
"/Inbound/CitrixIMA",6870044421
"/Inbound/Clarent-CC",0
"/Inbound/Clarent-Mgmt",0
"/Inbound/CORBA",561738
"/Inbound/CRS",106591
"/Inbound/CUSeeMe",286599288
"/Inbound/CVSpserver",1407344505
"/Inbound/DHCP",145365
"/Inbound/DICOM/Default",60249762
"/Inbound/DLS",1789013430
"/Inbound/Doom",793333458
"/Inbound/DPA",10908
"/Inbound/EntryPoint",178174959
"/Inbound/FileMaker",1363663743
"/Inbound/Finger",184087561
"/Inbound/FTP",1156108031970
"/Inbound/Furthurnet",73757823415
"/Inbound/Gopher",23463125
"/Inbound/Groupwise",2117877792
"/Inbound/Half-Life",48946035343
"/Inbound/HL7",0
"/Inbound/HTTP",6526814231970
"/Inbound/Ident",16870254485
"/Inbound/IMAP",15205608702
"/Inbound/iMesh",0
"/Inbound/IPP",14699444
"/Inbound/IRC",317440978305
"/Inbound/JavaRMI",371870992
"/Inbound/Kali",91334707
"/Inbound/Kerberos",78316151
"/Inbound/L2TP",82802399
"/Inbound/LDAP",30309713
"/Inbound/lockd",17090361
"/Inbound/LotusNotes",2956418136
"/Inbound/LucasArts",173857354
"/Inbound/Marimba",3486605952
"/Inbound/MATIP",1184
"/Inbound/MCK-Signaling",1478575143
"/Inbound/MPEG-Audio",135935166075
"/Inbound/MPEG-Video",236733555334
"/Inbound/MSN-Messenger",10282312754
"/Inbound/MSSQL",3160723489
"/Inbound/Net2Phone",24497831
"/Inbound/NewsStand",73905
"/Inbound/NNTP",1774728822480
"/Inbound/NTP",4250952593
"/Inbound/NW5-CMD",16137328
"/Inbound/Oracle",15713456748
"/Inbound/OracleClient",85468
"/Inbound/OracleEM",1531307508
"/Inbound/PEPGate",1214806373
"/Inbound/Persona",2551145718
"/Inbound/POP3",20958375616
"/Inbound/PPTP",740445011
"/Inbound/Progress",8786763
"/Inbound/Quake",5956143306
"/Inbound/QuickTime",177441220785
"/Inbound/RADIUS",81597929
"/Inbound/RC5DES",3719087160
"/Inbound/RDP",3773367836
"/Inbound/Real",406835565552
"/Inbound/rexec",560
"/Inbound/rlogin",12119529
"/Inbound/rsh",12156998
"/Inbound/rsync",4721149567
"/Inbound/RTCP-I",191990699
"/Inbound/RTP-I",22495336802
"/Inbound/rwho",200027
"/Inbound/SHARESUDP",16019407
"/Inbound/SMTBF",1015186668
"/Inbound/SMTP",276488347555
"/Inbound/SNMP",2189438346
"/Inbound/SOCKS",688634687
"/Inbound/SSDP",6660685
"/Inbound/SSH",135598970476
"/Inbound/SSL",225421152342
"/Inbound/Syslog",762299
"/Inbound/T.120",4793924980
"/Inbound/TACACS",787
"/Inbound/Telnet",12135919253
"/Inbound/TFTP",2971867
"/Inbound/Timbuktu",14531085088
"/Inbound/tn3270",3197548
"/Inbound/tn5250",16417732
"/Inbound/tn5250p",391394
"/Inbound/Tripnosis",0
"/Inbound/Unreal",10737545778
"/Inbound/VDOPhone",161844562
"/Inbound/VNC",3907744639
"/Inbound/WebEx",356071565
"/Inbound/Webshots",356894418
"/Inbound/WHOIS",54083762
"/Inbound/WinMedia",680503794207
"/Inbound/XWindows",1309373733
"/Inbound/YahooGames",2819811728
"/Inbound/YahooMsg",1755788955
"/Inbound/Battle.net",7335236719
"/Inbound/CU-DEV",5948
"/Inbound/CVSup",3089293117
"/Inbound/Day-Time",979943342
"/Inbound/DCOM",390740
"/Inbound/Dialpad",181496
"/Inbound/DNS/CampusDNSservers",13516568527
"/Inbound/DNS/Default",37437581098
"/Inbound/AOL-IM-ICQ/AOL-IM-File",49782797554
"/Inbound/AOL-IM-ICQ/AOL-IM-IMAGE",2800035304
"/Inbound/AOL-IM-ICQ/Default",81786471165
"/Inbound/Echo",84578271
"/Inbound/FNAonTCP",198
"/Inbound/Groove",3441518
"/Inbound/H.323",5651558355
"/Inbound/INFOC-RTMS",801521
"/Inbound/ISAKMP",682961094
"/Inbound/Kontiki",753083782
"/Inbound/MeetingMaker",111121537
"/Inbound/Microsoft-ds",71911729
"/Inbound/MSSQ",27791304433
"/Inbound/Mythic",637229204
"/Inbound/NetBIOS-IP",200482346
"/Inbound/NFS",9225533
"/Inbound/NW5-NCP",3496739409
"/Inbound/pcANYWHERE",5434160394
"/Inbound/Printer",3494742
"/Inbound/RIP",1878458
"/Inbound/RTSP",5316789435
"/Inbound/SLP",21287190
"/Inbound/SMS",8160951904
"/Inbound/SonyOnline",6440087323
"/Inbound/StreamWorks",1089590643
"/Inbound/SunRPC",42332
"/Inbound/TimeServer",642036601
"/Inbound/Tribes",1327952624
"/Inbound/Unavailable",0
"/Inbound/WINS",699963
"/Inbound/CBT",3396
"/Inbound/ICMP",35084113498
"/Inbound/IGMP",44072
"/Inbound/IPSec",18681285969
"/Inbound/OSPF",0
"/Inbound/PIM",0
"/Inbound/Protocol_102",141
"/Inbound/Protocol_255",0
"/Inbound/Protocol_4",36954872
"/Inbound/Protocol_41",11288
"/Inbound/Protocol_54",314440
"/Inbound/RSVP",1354306
"/Inbound/DiscoveredPorts/RMT-maybe",21031671
"/Inbound/DiscoveredPorts/TCP_Port_1086",5661627
"/Inbound/DiscoveredPorts/TCP_Port_1214",2084597522
"/Inbound/DiscoveredPorts/TCP_Port_1327",2326934
"/Inbound/DiscoveredPorts/TCP_Port_1481",242963168
"/Inbound/DiscoveredPorts/TCP_Port_1496",214365665
"/Inbound/DiscoveredPorts/TCP_Port_17111",3723602317
"/Inbound/DiscoveredPorts/TCP_Port_1938",4142975
"/Inbound/DiscoveredPorts/TCP_Port_1984",6583437
"/Inbound/DiscoveredPorts/TCP_Port_2039",4148005
"/Inbound/DiscoveredPorts/TCP_Port_21",11380316348
"/Inbound/DiscoveredPorts/TCP_Port_2112",54870101
"/Inbound/DiscoveredPorts/TCP_Port_2214",112718
"/Inbound/DiscoveredPorts/TCP_Port_2235",2718965028
"/Inbound/DiscoveredPorts/TCP_Port_251",3166647964
"/Inbound/DiscoveredPorts/TCP_Port_3403",16327266
"/Inbound/DiscoveredPorts/TCP_Port_3632",44119387
"/Inbound/DiscoveredPorts/TCP_Port_4034",7112560
"/Inbound/DiscoveredPorts/TCP_Port_44445",50062065
"/Inbound/DiscoveredPorts/TCP_Port_49",17115099
"/Inbound/DiscoveredPorts/TCP_Port_5013",32139427
"/Inbound/DiscoveredPorts/TCP_Port_5100",585244393
"/Inbound/DiscoveredPorts/TCP_Port_5625",19529741
"/Inbound/DiscoveredPorts/TCP_Port_5992",34586461
"/Inbound/DiscoveredPorts/TCP_Port_6016",12338317
"/Inbound/DiscoveredPorts/TCP_Port_6080",73954896
"/Inbound/DiscoveredPorts/TCP_Port_6567",10473597
"/Inbound/DiscoveredPorts/TCP_Port_6669",7727536919
"/Inbound/DiscoveredPorts/TCP_Port_6891",4243295461
"/Inbound/DiscoveredPorts/TCP_Port_6928",2011609043
"/Inbound/DiscoveredPorts/TCP_Port_7290",378963758156
"/Inbound/DiscoveredPorts/TCP_Port_7700",71482527
"/Inbound/DiscoveredPorts/TCP_Port_7879",8212808
"/Inbound/DiscoveredPorts/TCP_Port_80",2403655696
"/Inbound/DiscoveredPorts/TCP_Port_8989",8455686
"/Inbound/DiscoveredPorts/TCP_Port_9833",251520151
"/Inbound/DiscoveredPorts/TCP_Port_9931",1011188920
"/Inbound/DiscoveredPorts/TCP_Port_9999",516485106
"/Inbound/DiscoveredPorts/UDP_Port_13139",158321713
"/Inbound/DiscoveredPorts/UDP_Port_1434",10797627
"/Inbound/DiscoveredPorts/UDP_Port_15003",187638
"/Inbound/DiscoveredPorts/UDP_Port_1971",32088552
"/Inbound/DiscoveredPorts/UDP_Port_2200",12577161
"/Inbound/DiscoveredPorts/UDP_Port_2203",116519861
"/Inbound/DiscoveredPorts/UDP_Port_2223",405573
"/Inbound/DiscoveredPorts/UDP_Port_23000",195873403
"/Inbound/DiscoveredPorts/UDP_Port_2606",9047238
"/Inbound/DiscoveredPorts/UDP_Port_27016",8154578
"/Inbound/DiscoveredPorts/UDP_Port_2859",76432073
"/Inbound/DiscoveredPorts/UDP_Port_2868",1798327
"/Inbound/DiscoveredPorts/UDP_Port_3468",17964922
"/Inbound/DiscoveredPorts/UDP_Port_375",62449
"/Inbound/DiscoveredPorts/UDP_Port_37852",113549815
"/Inbound/DiscoveredPorts/UDP_Port_4110",19130305
"/Inbound/DiscoveredPorts/UDP_Port_4224",216656
"/Inbound/DiscoveredPorts/UDP_Port_6970",33411419188
"/Inbound/DiscoveredPorts/UDP_Port_7674",102172836
"/Inbound/DiscoveredPorts/UDP_Port_7778",4108815
"/Inbound/DiscoveredPorts/UDP_Port_7787",51507063
"/Inbound/DiscoveredPorts/UDP_Port_8344",24240670
"/Inbound/DiscoveredPorts/UDP_Port_9000",24805620
"/Inbound/DiscoveredPorts/UDP_Port_9665",2975550
"/Inbound/Default",2192603208620

PacketShaper# me dump class all outbound by element 30d bytes
"time:12-Oct-2002 23:00:00"
"class","bytes"
"/Outbound/Mirror_Servers/ScavengerService/HTTP",460753651549
"/Outbound/Mirror_Servers/ScavengerService/rsync",618223794899
"/Outbound/Mirror_Servers/ScavengerService/SMTP",16667
"/Outbound/Mirror_Servers/ScavengerService/SSH",881282
"/Outbound/Mirror_Servers/ScavengerService/DNS",291926
"/Outbound/Mirror_Servers/ScavengerService/ICMP",2264705
"/Outbound/Mirror_Servers/ScavengerService/Default",27769760023
"/Outbound/Mirror_Servers/BackWeb",0
"/Outbound/Mirror_Servers/Citrix/Default",18040
"/Outbound/Mirror_Servers/FTP",1991378204256
"/Outbound/Mirror_Servers/Half-Life",75175
"/Outbound/Mirror_Servers/HTTP",1229339277328
"/Outbound/Mirror_Servers/lockd",7840
"/Outbound/Mirror_Servers/MPEG-Video",95542124
"/Outbound/Mirror_Servers/NTP",153504
"/Outbound/Mirror_Servers/QuickTime",744338502
"/Outbound/Mirror_Servers/Real",26725059
"/Outbound/Mirror_Servers/rsync",133500407843
"/Outbound/Mirror_Servers/SMTP",30113
"/Outbound/Mirror_Servers/SSH",134799523
"/Outbound/Mirror_Servers/WinMedia",771626
"/Outbound/Mirror_Servers/DNS",460093460
"/Outbound/Mirror_Servers/Kontiki",40084956
"/Outbound/Mirror_Servers/ICMP",20175171
"/Outbound/Mirror_Servers/Default",35089567911
"/Outbound/Dorm/HBRec/WinMX",51354327229
"/Outbound/Dorm/HBRec/Soulseek",14206995361
"/Outbound/Dorm/HBRec/Aimster",2304371
"/Outbound/Dorm/HBRec/Audiogalaxy",15298722
"/Outbound/Dorm/HBRec/DirectConnect",1573545139
"/Outbound/Dorm/HBRec/eDonkey",34918803531
"/Outbound/Dorm/HBRec/Gnutella/Gnutella-Download",1060585396
"/Outbound/Dorm/HBRec/Gnutella/Gnutella-Upload",26478141710
"/Outbound/Dorm/HBRec/Gnutella/Default",95367140173
"/Outbound/Dorm/HBRec/Hotline",6967336
"/Outbound/Dorm/HBRec/KaZaA/KaZaA-Download",122252032605
"/Outbound/Dorm/HBRec/KaZaA/KaZaA-Upload",4997197470941
"/Outbound/Dorm/HBRec/KaZaA/Default",186623803180
"/Outbound/Dorm/HBRec/Napster",19065669346
"/Outbound/Dorm/HBRec/ScourExchange",470
"/Outbound/Dorm/HBRec/Shoutcast",766725960
"/Outbound/Dorm/HBRec/Blubster",909180373
"/Outbound/Dorm/GRE",33705
"/Outbound/Dorm/Apache_OpenSSL_worm",0
"/Outbound/Dorm/AFP",4615
"/Outbound/Dorm/AFS",720547
"/Outbound/Dorm/AsheronsCall",696598
"/Outbound/Dorm/ATSTCP",157695543
"/Outbound/Dorm/BackWeb",24647972
"/Outbound/Dorm/ccMail",433044789
"/Outbound/Dorm/CIFS-TCP",62572946
"/Outbound/Dorm/Citrix/Default",554732181
"/Outbound/Dorm/CitrixIMA",583209705
"/Outbound/Dorm/Clarent-CC",0
"/Outbound/Dorm/Clarent-Mgmt",0
"/Outbound/Dorm/CVSpserver",6863
"/Outbound/Dorm/DHCP",4576
"/Outbound/Dorm/DLS",395950946
"/Outbound/Dorm/Doom",235896028
"/Outbound/Dorm/FileMaker",4012590
"/Outbound/Dorm/FileRouge",0
"/Outbound/Dorm/Finger",92066754
"/Outbound/Dorm/FTP",51797917774
"/Outbound/Dorm/Furthurnet",40132408343
"/Outbound/Dorm/Gopher",47502
"/Outbound/Dorm/Groupwise",32184057
"/Outbound/Dorm/Half-Life",16817361211
"/Outbound/Dorm/HTTP",108412938152
"/Outbound/Dorm/Ident",931105919
"/Outbound/Dorm/IMAP",55606438
"/Outbound/Dorm/IRC",73081902108
"/Outbound/Dorm/Kali",172270951
"/Outbound/Dorm/Kerberos",84664
"/Outbound/Dorm/L2TP",8331380
"/Outbound/Dorm/LDAP",152636
"/Outbound/Dorm/lockd",519175
"/Outbound/Dorm/LotusNotes",2076395495
"/Outbound/Dorm/LucasArts",572756280
"/Outbound/Dorm/Marimba",21728396
"/Outbound/Dorm/MCK-Signaling",94637126262
"/Outbound/Dorm/Micom-VIP",0
"/Outbound/Dorm/MPEG-Audio",1170108240
"/Outbound/Dorm/MPEG-Video",1654813264
"/Outbound/Dorm/MSN-Messenger",1560902486
"/Outbound/Dorm/MSN-Zone",0
"/Outbound/Dorm/MSSQL",1390227262
"/Outbound/Dorm/NNTP",15186571
"/Outbound/Dorm/NTP",1862141
"/Outbound/Dorm/NW5-CMD",4903064
"/Outbound/Dorm/Oracle",12670486154
"/Outbound/Dorm/OracleEM",483562328
"/Outbound/Dorm/PEPGate",226252281
"/Outbound/Dorm/Persona",6269181425
"/Outbound/Dorm/POP3",413510023
"/Outbound/Dorm/PPTP",313279296
"/Outbound/Dorm/Quake",903908597
"/Outbound/Dorm/QuickTime",663551942
"/Outbound/Dorm/RADIUS",8251055
"/Outbound/Dorm/RC5DES",115639333
"/Outbound/Dorm/RDP",19740854676
"/Outbound/Dorm/Real",521369212
"/Outbound/Dorm/rsync",1582295
"/Outbound/Dorm/RTCP-I",42781862
"/Outbound/Dorm/RTP-I",6746757024
"/Outbound/Dorm/rwho",22666
"/Outbound/Dorm/SHARESUDP",4759238
"/Outbound/Dorm/SMTBF",66273386
"/Outbound/Dorm/SMTP",1217250062
"/Outbound/Dorm/SNMP",1493170
"/Outbound/Dorm/SOCKS",0
"/Outbound/Dorm/SSDP",20787984
"/Outbound/Dorm/SSH",205975448
"/Outbound/Dorm/SSL",1921043735
"/Outbound/Dorm/Syslog",143
"/Outbound/Dorm/T.120",79383063
"/Outbound/Dorm/Telnet",6979644370
"/Outbound/Dorm/TFTP",423
"/Outbound/Dorm/Timbuktu",11357205406
"/Outbound/Dorm/Tripnosis",0
"/Outbound/Dorm/Unreal",1393343836
"/Outbound/Dorm/VNC",32448603
"/Outbound/Dorm/Webshots",2924371
"/Outbound/Dorm/WHOIS",133546
"/Outbound/Dorm/WinMedia",1231229953
"/Outbound/Dorm/XWindows",41307371
"/Outbound/Dorm/YahooGames",276508226
"/Outbound/Dorm/YahooMsg",97024196
"/Outbound/Dorm/AOL-IM-ICQ",46475828963
"/Outbound/Dorm/Battle.net",593584867
"/Outbound/Dorm/CU-DEV",0
"/Outbound/Dorm/CVSup",3076303
"/Outbound/Dorm/Day-Time",62499591
"/Outbound/Dorm/DNS",814573464
"/Outbound/Dorm/Echo",213216
"/Outbound/Dorm/H.323",710996348
"/Outbound/Dorm/INFOC-RTMS",47
"/Outbound/Dorm/ISAKMP",88627
"/Outbound/Dorm/Kontiki",270389160
"/Outbound/Dorm/MeetingMaker",75691971
"/Outbound/Dorm/MSSQ",5267428380
"/Outbound/Dorm/Mythic",214261812
"/Outbound/Dorm/NetBIOS-IP",54509670
"/Outbound/Dorm/NFS",6580922
"/Outbound/Dorm/NW5-NCP",174929
"/Outbound/Dorm/pcANYWHERE",955295
"/Outbound/Dorm/RTSP",4870662
"/Outbound/Dorm/SLP",10628530
"/Outbound/Dorm/SMS",888524864
"/Outbound/Dorm/SonyOnline",322606980
"/Outbound/Dorm/StreamWorks",289546485
"/Outbound/Dorm/TimeServer",999393
"/Outbound/Dorm/Tribes",38977482
"/Outbound/Dorm/Unavailable",0
"/Outbound/Dorm/WINS",26687
"/Outbound/Dorm/ICMP",4505564757
"/Outbound/Dorm/Protocol_41",2590
"/Outbound/Dorm/Protocol_54",134190
"/Outbound/Dorm/RSVP",123311
"/Outbound/Dorm/DiscoveredPorts/TCP_Port_1214",1570606067
"/Outbound/Dorm/DiscoveredPorts/UDP_Port_1227",2257343
"/Outbound/Dorm/DiscoveredPorts/UDP_Port_20100",145615291
"/Outbound/Dorm/DiscoveredPorts/UDP_Port_27015",5833153
"/Outbound/Dorm/DiscoveredPorts/UDP_Port_27016",6640140
"/Outbound/Dorm/DiscoveredPorts/UDP_Port_2929",5859
"/Outbound/Dorm/DiscoveredPorts/UDP_Port_3090",38882678
"/Outbound/Dorm/DiscoveredPorts/UDP_Port_3674",1218566
"/Outbound/Dorm/DiscoveredPorts/UDP_Port_3987",13353
"/Outbound/Dorm/Default",2310455123084
"/Outbound/Localhost",284322881
"/Outbound/SameSide",6504159
"/Outbound/Campus/HBRec/WinMX",14799622325
"/Outbound/Campus/HBRec/Soulseek",61071186438
"/Outbound/Campus/HBRec/Audiogalaxy",57806786
"/Outbound/Campus/HBRec/DirectConnect",3147779655
"/Outbound/Campus/HBRec/eDonkey",159433206479
"/Outbound/Campus/HBRec/Gnutella/Gnutella-Download",1869112853
"/Outbound/Campus/HBRec/Gnutella/Gnutella-Upload",14308891080
"/Outbound/Campus/HBRec/Gnutella/Default",102118383725
"/Outbound/Campus/HBRec/Hotline",3396913
"/Outbound/Campus/HBRec/KaZaA/KaZaA-Download",177006040455
"/Outbound/Campus/HBRec/KaZaA/KaZaA-Upload",4820831617937
"/Outbound/Campus/HBRec/KaZaA/Default",120746374453
"/Outbound/Campus/HBRec/Napster",29868365464
"/Outbound/Campus/HBRec/ScourExchange",7207318
"/Outbound/Campus/HBRec/Shoutcast",367884097213
"/Outbound/Campus/HBRec/Blubster",2835219465
"/Outbound/ScavengerService",10736729787
"/Outbound/GRE",2115990534
"/Outbound/TC2-Netflow-Export",0
"/Outbound/Multicast/RTCP-I",11014816
"/Outbound/Multicast/SSDP",6737262
"/Outbound/Multicast/SLP",68517951
"/Outbound/Multicast/WINS",436
"/Outbound/Multicast/IGMP",1822989
"/Outbound/Multicast/OSPF",0
"/Outbound/Multicast/PIM",151570979
"/Outbound/Multicast/Default",1982653344
"/Outbound/test",2377115
"/Outbound/Apache_OpenSSL_worm",0
"/Outbound/Soribada",544827079
"/Outbound/AFP",155940
"/Outbound/AFS",12069045
"/Outbound/Aimster",259659389
"/Outbound/AsheronsCall",49336764
"/Outbound/ATSTCP",1274679433
"/Outbound/Attachmate-GW",10422493
"/Outbound/AURP",0
"/Outbound/BackWeb",160933251
"/Outbound/BGP",14853633
"/Outbound/ccMail",506789730
"/Outbound/Chaincast",515372123
"/Outbound/CIFS-TCP",476684024
"/Outbound/Citrix/Citrix-AFOATS_MAIL",5439469
"/Outbound/Citrix/Citrix-AFW_ONLINE",0
"/Outbound/Citrix/Citrix-CRYSTAL_REPORTS",208061
"/Outbound/Citrix/Citrix-E-net",114431
"/Outbound/Citrix/Citrix-ERM_305_VIA_METAFRAME",1258513
"/Outbound/Citrix/Citrix-EXTERNAL_800X600",0
"/Outbound/Citrix/Citrix-MICROSOFT_EXCEL",0
"/Outbound/Citrix/Citrix-Outlook_2000",6237654
"/Outbound/Citrix/Citrix-PEOPLESOFT_PRODUCTION_DA",19622114
"/Outbound/Citrix/Citrix-SABREVIEWAA1",0
"/Outbound/Citrix/Citrix-TSTEST",0
"/Outbound/Citrix/Default",1287052278
"/Outbound/CitrixIMA",1706399082
"/Outbound/CORBA",240538
"/Outbound/CRS",22570
"/Outbound/CUSeeMe",147921959
"/Outbound/CVSpserver",961706086
"/Outbound/DHCP",9387553
"/Outbound/DICOM/Default",1435115
"/Outbound/DLS",929780992
"/Outbound/Doom",583823729
"/Outbound/EntryPoint",13588261
"/Outbound/FileMaker",289647453
"/Outbound/Finger",42992912
"/Outbound/FTP",2537332581801
"/Outbound/Furthurnet",134787110913
"/Outbound/Gopher",210391038
"/Outbound/Groupwise",1979145596
"/Outbound/Half-Life",34999071713
"/Outbound/HL7",0
"/Outbound/HTTP",2621829597603
"/Outbound/Ident",1733176777
"/Outbound/IMAP",15199704300
"/Outbound/IPP",28719058
"/Outbound/IRC",422551798763
"/Outbound/JavaRMI",419271583
"/Outbound/Kali",51269949
"/Outbound/Kerberos",47741145
"/Outbound/L2TP",23562707
"/Outbound/LDAP",29173412
"/Outbound/lockd",17603920
"/Outbound/LotusNotes",4548682344
"/Outbound/LucasArts",114771537
"/Outbound/Marimba",220162550
"/Outbound/MCK-Signaling",456805648
"/Outbound/Micom-VIP",0
"/Outbound/MPEG-Audio",16245155538
"/Outbound/MPEG-Video",34965041535
"/Outbound/MSN-Messenger",4849563544
"/Outbound/MSSQL",914672381
"/Outbound/Net2Phone",18571723
"/Outbound/NewsStand",78643
"/Outbound/NNTP",2155275368866
"/Outbound/NTP",3501115157
"/Outbound/NW5-CMD",9834130
"/Outbound/Oracle",32746702462
"/Outbound/OracleClient",4934
"/Outbound/OracleEM",889206230
"/Outbound/PEPGate",899004917
"/Outbound/Persona",867928088
"/Outbound/POP3",109219488671
"/Outbound/PPTP",790530098
"/Outbound/Progress",27918678
"/Outbound/Quake",10323604804
"/Outbound/QuickTime",63068385087
"/Outbound/RADIUS",21340981
"/Outbound/RC5DES",1374773818
"/Outbound/RDP",7020591002
"/Outbound/Real",199617369814
"/Outbound/rexec",1076
"/Outbound/rlogin",18234850
"/Outbound/rsh",441910
"/Outbound/rsync",135374887
"/Outbound/RTCP-I",183839924
"/Outbound/RTP-I",18087146643
"/Outbound/rwho",26976
"/Outbound/SHARESUDP",7850840
"/Outbound/SMTBF",715098161
"/Outbound/SMTP",208231815831
"/Outbound/SNMP",1674713230
"/Outbound/SOCKS",1708664956
"/Outbound/SSDP",44703742
"/Outbound/SSH",322143741029
"/Outbound/SSL",322932482916
"/Outbound/Syslog",203076
"/Outbound/T.120",1176300486
"/Outbound/TACACS",1737
"/Outbound/Telnet",12390203031
"/Outbound/TFTP",35502148
"/Outbound/Timbuktu",4759800111
"/Outbound/tn3270",14357010
"/Outbound/tn5250",151841393
"/Outbound/tn5250p",3719771
"/Outbound/Unreal",8618772013
"/Outbound/VDOPhone",48738470
"/Outbound/VNC",4681097961
"/Outbound/WebEx",164497222
"/Outbound/Webshots",13402212
"/Outbound/WHOIS",17199676
"/Outbound/WinMedia",31680663047
"/Outbound/XWindows",6189416589
"/Outbound/YahooGames",1859632750
"/Outbound/YahooMsg",925907604
"/Outbound/AOL-IM-ICQ",142316004160
"/Outbound/Battle.net",3926312865
"/Outbound/CU-DEV",23020
"/Outbound/CVSup",5082449848
"/Outbound/Day-Time",191607633
"/Outbound/DCOM",2703448
"/Outbound/Dialpad",218340
"/Outbound/DNS/CampusDNSservers",16830441220
"/Outbound/DNS/Default",15104974374
"/Outbound/Echo",147702083
"/Outbound/FNAonTCP",12193
"/Outbound/Groove",131368
"/Outbound/H.323",1866434199
"/Outbound/INFOC-RTMS",10004740
"/Outbound/ISAKMP",1019874578
"/Outbound/Kontiki",406305679
"/Outbound/MeetingMaker",194364478
"/Outbound/Microsoft-ds",10638940
"/Outbound/MSSQ",246434268900
"/Outbound/Mythic",100207410
"/Outbound/NetBIOS-IP",7189740339
"/Outbound/NFS",8984667
"/Outbound/NW5-NCP",3452926681
"/Outbound/pcANYWHERE",8380860335
"/Outbound/Printer",28535600
"/Outbound/RIP",1077755
"/Outbound/RTSP",4551558885
"/Outbound/SLP",75323828
"/Outbound/SMS",3303639240
"/Outbound/SonyOnline",1311691748
"/Outbound/StreamWorks",464866912
"/Outbound/SunRPC",948673
"/Outbound/TimeServer",623495014
"/Outbound/Tribes",504446259
"/Outbound/Unavailable",0
"/Outbound/WINS",463811
"/Outbound/ICMP",20563452619
"/Outbound/IGMP",5226
"/Outbound/IPSec",18256120058
"/Outbound/OSPF",0
"/Outbound/PIM",90271529
"/Outbound/Protocol_4",103952538
"/Outbound/Protocol_41",10380
"/Outbound/Protocol_54",25233670
"/Outbound/RSVP",3677984
"/Outbound/DiscoveredPorts/RMT-maybe",24128623
"/Outbound/DiscoveredPorts/TCP_Port_1214",1381003234
"/Outbound/DiscoveredPorts/TCP_Port_1535",19128581
"/Outbound/DiscoveredPorts/TCP_Port_17111",5868352
"/Outbound/DiscoveredPorts/TCP_Port_1839",8046748017
"/Outbound/DiscoveredPorts/TCP_Port_2091",12570452
"/Outbound/DiscoveredPorts/TCP_Port_21",20832979065
"/Outbound/DiscoveredPorts/TCP_Port_2112",673660989
"/Outbound/DiscoveredPorts/TCP_Port_2121",35361151
"/Outbound/DiscoveredPorts/TCP_Port_27243",1478931
"/Outbound/DiscoveredPorts/TCP_Port_2909",42060923
"/Outbound/DiscoveredPorts/TCP_Port_446",7612685
"/Outbound/DiscoveredPorts/TCP_Port_4989",1498442610
"/Outbound/DiscoveredPorts/TCP_Port_5101",43425247
"/Outbound/DiscoveredPorts/TCP_Port_52649",5805602
"/Outbound/DiscoveredPorts/TCP_Port_5625",2014574380
"/Outbound/DiscoveredPorts/TCP_Port_6016",1326044695
"/Outbound/DiscoveredPorts/TCP_Port_6595",67376419
"/Outbound/DiscoveredPorts/TCP_Port_7687",7379735145
"/Outbound/DiscoveredPorts/TCP_Port_80",3375512630
"/Outbound/DiscoveredPorts/TCP_Port_8184",130795214
"/Outbound/DiscoveredPorts/TCP_Port_82",606779
"/Outbound/DiscoveredPorts/UDP_Port_192",80728680
"/Outbound/DiscoveredPorts/UDP_Port_2004",3252964
"/Outbound/DiscoveredPorts/UDP_Port_20100",17820184
"/Outbound/DiscoveredPorts/UDP_Port_23000",16130087
"/Outbound/DiscoveredPorts/UDP_Port_2332",12252118
"/Outbound/DiscoveredPorts/UDP_Port_27015",39989775
"/Outbound/DiscoveredPorts/UDP_Port_2859",2218908
"/Outbound/DiscoveredPorts/UDP_Port_2923",280307821
"/Outbound/DiscoveredPorts/UDP_Port_376",73253928
"/Outbound/DiscoveredPorts/UDP_Port_4000",52039778
"/Outbound/DiscoveredPorts/UDP_Port_4246",972258
"/Outbound/DiscoveredPorts/UDP_Port_47624",51537750
"/Outbound/DiscoveredPorts/UDP_Port_5555",20707594
"/Outbound/DiscoveredPorts/UDP_Port_6112",39607331
"/Outbound/DiscoveredPorts/UDP_Port_6127",39389202
"/Outbound/DiscoveredPorts/UDP_Port_6669",121629259
"/Outbound/DiscoveredPorts/UDP_Port_6770",17861222
"/Outbound/DiscoveredPorts/UDP_Port_6970",14706204179
"/Outbound/DiscoveredPorts/UDP_Port_7674",69275497
"/Outbound/DiscoveredPorts/UDP_Port_8084",4402796
"/Outbound/Default",4105623519032

-------------

Client 2 - major university

PacketShaper# part show

Partition name          Size          Grntd       Prior       Curr  1-Min
                         Min /  Max          Excess      Usage       Avg   Peak
-------------------------------------------------------------------------------
/Inbound               140.0M 140.0M     0  50.0M 68.6M118.6M 94.9M 95.3M148.6M
  /Inbound/traceroute_de10
                          250k
140.0M*    0     0     0     0     0     0     0
  /Inbound/File-Sharing     0   50.0M     0  50.0M    0  50.0M 43.5M 43.5M
51.4M
  /Inbound/GRE            5.0M 140.0M*    0     0  62.0k 62.0k 70.3k 66.7k
10.5M
  /Inbound/PPTP           5.0M 140.0M*    0     0  53.2k 53.2k 14.4k
23.2k  4.5M
  /Inbound/ICMP           250k 140.0M*    0     0   129k  129k 96.0k
47.7k  4.5M
  /Inbound/Telnet        10.0M 140.0M*    0     0  18.9k 18.9k 16.2k
14.7k  6.9M
  /Inbound/SSH           10.0M 140.0M*    0     0  52.7k 52.7k 32.6k 47.7k
10.0M

-------------------------------------------------------------------------------
/Outbound              140.0M 140.0M     0  52.0M 86.9M138.9M 91.4M 91.8M145.3M
  /Outbound/traceroute_de10
                          250k
140.0M*    0     0     0     0     0     0   136
  /Outbound/File-Sharing    0   45.0M     0   1.1M    0   1.1M  6.6M  6.9M
45.7M
  /Outbound/Default         0   50.0M     0     0  47.9M 47.9M 41.6M 42.0M
51.4M
  /Outbound/GRE          10.0M
140.0M*    0     0   233k  233k  371k  202k  8.4M
  /Outbound/PPTP          5.0M
140.0M*    0     0  1024  1024  1151  1716   1.9M
  /Outbound/ICMP/Default  250k
140.0M*    0     0   3.9M  3.9M  3.0M  3.1M  6.4M
  /Outbound/Telnet       10.0M 140.0M*    0     0  25.6k 25.6k 19.4k
20.2k  1.6M
  /Outbound/SSH          10.0M 140.0M*    0     0   147k  147k 39.0k 51.5k
11.9M

PacketShaper# me dump class all inbound by element 30d bytes
"time:13-Oct-2002 00:00:00"
"class","bytes"
"/Inbound/Localhost",5269190
"/Inbound/SameSide",1927216
"/Inbound/GRE",24887467708
"/Inbound/localRouterMgmt",3102
"/Inbound/salsa",1812080316
"/Inbound/traceroute_de10",5595643
"/Inbound/SideCar",1275756764
"/Inbound/AFP",3018778582
"/Inbound/AFS",1217349049
"/Inbound/ATSTCP",2515156473
"/Inbound/BackWeb",74102497
"/Inbound/BGP",31161
"/Inbound/ccMail",2211179787
"/Inbound/Chaincast",2363587925
"/Inbound/CORBA",126642928
"/Inbound/FileMaker",1414257525
"/Inbound/Quake/Quake_kvr5",58313294
"/Inbound/Quake/Default",4658757675
"/Inbound/HTTP/request",289755852177
"/Inbound/HTTP/Internet",6808853903014
"/Inbound/Ident",3130017404
"/Inbound/IPP",597450
"/Inbound/IRC",280767200363
"/Inbound/L2TP",167748532
"/Inbound/LDAP",308178139
"/Inbound/Marimba",1508028740
"/Inbound/MCK-Signaling",1274244079
"/Inbound/MPEG-Audio",53735644106
"/Inbound/MPEG-Video",136863047765
"/Inbound/MSN-Messenger",4241822375
"/Inbound/MSSQL",4752083119
"/Inbound/Net2Phone",143883829
"/Inbound/NNTP",951229032356
"/Inbound/Oracle",9767323681
"/Inbound/POP3",25452832310
"/Inbound/Citrix/Default",2840219110
"/Inbound/CitrixIMA",18501137481
"/Inbound/DHCP",0
"/Inbound/Doom",54440981
"/Inbound/EntryPoint",64811421
"/Inbound/Finger",167520208
"/Inbound/FTP",1115085958256
"/Inbound/Groupwise",1532542750
"/Inbound/Half-Life",30774688490
"/Inbound/IMAP",2686392441
"/Inbound/Kerberos",698175137
"/Inbound/lockd",86289875
"/Inbound/NTP",12516133849
"/Inbound/PPTP",483878661
"/Inbound/QuickTime",144016541564
"/Inbound/RADIUS",193842621
"/Inbound/RC5DES",701836772
"/Inbound/RDP",9509733512
"/Inbound/Real",259880783051
"/Inbound/rexec",7083180
"/Inbound/RTCP-I",329221103
"/Inbound/RTP-I",25698893119
"/Inbound/SHARESUDP",29827246
"/Inbound/Shoutcast",353544939979
"/Inbound/SMTP",357527215341
"/Inbound/SNMP",410044818
"/Inbound/SOCKS",3175489380
"/Inbound/SSH",46372537769
"/Inbound/SSL",98508902739
"/Inbound/T.120",1411371401
"/Inbound/Telnet",6116909572
"/Inbound/Timbuktu",19232478273
"/Inbound/tn3270",19075062
"/Inbound/VNC",7228096876
"/Inbound/Webshots",2862921801
"/Inbound/WHOIS",184238433
"/Inbound/WinMedia",740020265296
"/Inbound/XWindows",962671000
"/Inbound/YahooGames",1909069694
"/Inbound/YahooMsg",887350395
"/Inbound/AOL-IM-ICQ",275990817052
"/Inbound/Battle.net",13154790490
"/Inbound/Day-Time",209053254
"/Inbound/DCOM",6972025906
"/Inbound/DNS",26743599855
"/Inbound/Echo",213611551
"/Inbound/File-Sharing/WinMX_de10",25567515346
"/Inbound/File-Sharing/Wnn6",3745944779
"/Inbound/File-Sharing/KDX_custom",19656732952
"/Inbound/File-Sharing/Aimster",883896398
"/Inbound/File-Sharing/Audiogalaxy",17836564
"/Inbound/File-Sharing/DirectConnect",400541554642
"/Inbound/File-Sharing/eDonkey",431990620801
"/Inbound/File-Sharing/Gnutella",1010072138337
"/Inbound/File-Sharing/Hotline",47945464713
"/Inbound/File-Sharing/KaZaA/download",7273784359179
"/Inbound/File-Sharing/KaZaA/upload",52862071118
"/Inbound/File-Sharing/KaZaA/Default",2086320927210
"/Inbound/File-Sharing/Napster",624288999030
"/Inbound/File-Sharing/Blubster",9164357409
"/Inbound/File-Sharing/Groove",6100599
"/Inbound/H.323",2731767802
"/Inbound/ISAKMP",127148597
"/Inbound/Kontiki",454391662
"/Inbound/MeetingMaker",57048197
"/Inbound/Microsoft-ds",104262861914
"/Inbound/Mythic",2171254745
"/Inbound/NetBIOS-IP",65323647751
"/Inbound/NFS",952984820
"/Inbound/NW5-NCP",33856227
"/Inbound/pcANYWHERE",3427344338
"/Inbound/Printer",29168226
"/Inbound/RTSP",54674710341
"/Inbound/SLP",4355290
"/Inbound/SMS",3263302347
"/Inbound/SonyOnline",1650632345
"/Inbound/StreamWorks",1206328982
"/Inbound/SunRPC",73788271
"/Inbound/TimeServer",2570233027
"/Inbound/WINS",5469639
"/Inbound/ICMP",17393701116
"/Inbound/IGMP",0
"/Inbound/IPSec",12645912684
"/Inbound/OSPF",0
"/Inbound/PIM",0
"/Inbound/Protocol_169-AMP",16207998
"/Inbound/Protocol_41",2746503436
"/Inbound/Protocol_54",191760
"/Inbound/RSVP",4399756
"/Inbound/DiscoveredPorts/Kerberos_msw4",150531625
"/Inbound/DiscoveredPorts/TCP_Port_5001",345143936
"/Inbound/CiscoDiscovery",0
"/Inbound/Protocol_170",8074835
"/Inbound/Protocol_2004",7581913
"/Inbound/SpanningTree",0
"/Inbound/Default",3266222037717

PacketShaper# me dump class all outbound by element 30d bytes
"time:13-Oct-2002 00:00:00"
"class","bytes"
"/Outbound/Localhost",55918120
"/Outbound/SameSide",3474920
"/Outbound/GRE",33283299569
"/Outbound/localRouterMgmt",7567
"/Outbound/salsa",34601312380
"/Outbound/traceroute_de10",1351344
"/Outbound/SideCar",1180141932
"/Outbound/AFP",7359235383
"/Outbound/AFS",881227536
"/Outbound/ATSTCP",1526563677
"/Outbound/BackWeb",57167091
"/Outbound/BGP",28433
"/Outbound/ccMail",1846744784
"/Outbound/Chaincast",73535820
"/Outbound/CitrixIMA",41118231994
"/Outbound/CORBA",464812513
"/Outbound/DHCP",0
"/Outbound/Doom",76202836
"/Outbound/EntryPoint",4790661
"/Outbound/FileMaker",605087494
"/Outbound/Finger",657574595
"/Outbound/FTP",3924586514261
"/Outbound/Groupwise",1235085825
"/Outbound/Half-Life",19578806341
"/Outbound/Quake/Quake_kvr5",0
"/Outbound/Quake/Default",4222317204
"/Outbound/HTTP/reply/res_halls",0
"/Outbound/HTTP/reply/Default",940813753912
"/Outbound/HTTP/Internet",698432097235
"/Outbound/Ident",440608796
"/Outbound/IMAP",5291853854
"/Outbound/L2TP",42470383
"/Outbound/LDAP",792003477
"/Outbound/Marimba",63942118
"/Outbound/MCK-Signaling",1873885225
"/Outbound/MPEG-Audio",10855000342
"/Outbound/MPEG-Video",24142514255
"/Outbound/MSN-Messenger",8154283679
"/Outbound/MSSQL",20341862706
"/Outbound/Net2Phone",124566016
"/Outbound/NNTP",31386951031
"/Outbound/Oracle",18655410798
"/Outbound/POP3",271406521229
"/Outbound/Citrix/Default",3761969711
"/Outbound/IPP",911529
"/Outbound/Kerberos",677986786
"/Outbound/lockd",12302560
"/Outbound/NTP",12476514865
"/Outbound/PPTP",802484066
"/Outbound/QuickTime",21768158684
"/Outbound/RADIUS",55583927
"/Outbound/RC5DES",2374821472
"/Outbound/RDP",13521550631
"/Outbound/Real",16764124516
"/Outbound/rexec",3102866
"/Outbound/RTCP-I",361309026
"/Outbound/RTP-I",24367860635
"/Outbound/SHARESUDP",19745927
"/Outbound/Shoutcast",13048866134
"/Outbound/SMTP",266388221717
"/Outbound/SNMP",355755460
"/Outbound/SOCKS",40889846855
"/Outbound/SSH",96359125886
"/Outbound/SSL",56951437707
"/Outbound/Syslog",738659
"/Outbound/T.120",6669972719
"/Outbound/Telnet",8947249062
"/Outbound/Timbuktu",92062021437
"/Outbound/tn3270",160750338
"/Outbound/VNC",29615386202
"/Outbound/Webshots",62064550
"/Outbound/WHOIS",45028222
"/Outbound/WinMedia",27362529189
"/Outbound/XWindows",6672458162
"/Outbound/YahooGames",1223411541
"/Outbound/YahooMsg",444760490
"/Outbound/AOL-IM-ICQ",287538661666
"/Outbound/Battle.net",6990224435
"/Outbound/Day-Time",106416992
"/Outbound/DCOM",27038633363
"/Outbound/DNS",26615697048
"/Outbound/Echo",521868086
"/Outbound/File-Sharing/WinMX_de10",27160845561
"/Outbound/File-Sharing/Wnn6",3516523506
"/Outbound/File-Sharing/KDX_custom",424609553560
"/Outbound/File-Sharing/Aimster",270192676
"/Outbound/File-Sharing/Audiogalaxy",20686147
"/Outbound/File-Sharing/DirectConnect",551165400354
"/Outbound/File-Sharing/eDonkey",586174798625
"/Outbound/File-Sharing/Gnutella",964510081653
"/Outbound/File-Sharing/Hotline",51908033554
"/Outbound/File-Sharing/IRC",2917420684590
"/Outbound/File-Sharing/KaZaA/download",162461483374
"/Outbound/File-Sharing/KaZaA/upload",1177800829675
"/Outbound/File-Sharing/KaZaA/Default",3438397155521
"/Outbound/File-Sharing/Napster",612844823508
"/Outbound/File-Sharing/Blubster",12993031493
"/Outbound/File-Sharing/Groove",6984224
"/Outbound/H.323",5359509819
"/Outbound/ISAKMP",283534578
"/Outbound/Kontiki",1683612343
"/Outbound/MeetingMaker",900292254
"/Outbound/Microsoft-ds",138505869360
"/Outbound/Mythic",378062025
"/Outbound/NetBIOS-IP",51521655350
"/Outbound/NFS",2820045314
"/Outbound/NW5-NCP",146655029
"/Outbound/pcANYWHERE",2708993997
"/Outbound/Printer",17200365
"/Outbound/RTSP",6700437003
"/Outbound/SLP",5008430
"/Outbound/SMS",5954632358
"/Outbound/SonyOnline",433398181
"/Outbound/StreamWorks",3829366287
"/Outbound/SunRPC",40216318
"/Outbound/TimeServer",2843282610
"/Outbound/WINS",5495031
"/Outbound/ICMP/ICMP-bulk",7320578
"/Outbound/ICMP/Default",97978223622
"/Outbound/IGMP",12462326
"/Outbound/IPSec",4616617259
"/Outbound/OSPF",0
"/Outbound/PIM",0
"/Outbound/Protocol_169-AMP",1310244
"/Outbound/Protocol_41",9972322251
"/Outbound/RSVP",3722998
"/Outbound/DiscoveredPorts/Kerberos_msw4",221659301
"/Outbound/DiscoveredPorts/TCP_Port_21",327056152
"/Outbound/DiscoveredPorts/Slapper_UDP_2002",3264114041
"/Outbound/CiscoDiscovery",0
"/Outbound/MOP-RC",1115595
"/Outbound/Protocol_170",8076057
"/Outbound/Protocol_2004",7582406
"/Outbound/SpanningTree",0
"/Outbound/Default",8027415402786

Client 3 - major university


PacketShaper# part show

Partition name          Size          Grntd       Prior       Curr  1-Min
                         Min /  Max          Excess      Usage       Avg   Peak
-------------------------------------------------------------------------------
/Inbound               200.0M 200.0M     0  41.9M 78.1M120.0M 99.3M 99.9M136.2M
  /Inbound/P2P1/Gnutella-Init
                          2.0M   2.0M*    0     0  20.0k 20.0k 47.0k
44.3k  1.3M
  /Inbound/P2P1/Gnutella-Download
                         10.0M  10.0M*    0   4.0M    0   4.0M  803k  743k
8.0M
  /Inbound/P2P1/KaZaA-Cmd
                          3.0M   3.0M*    0     0   2.8M  2.8M  2.1M  2.1M
4.1M
  /Inbound/P2P1/Gnutella-Cmd
                          3.0M   3.0M*    0     0   3.0M  3.0M  2.8M  2.8M
4.0M
  /Inbound/P2P2           9.0M   9.0M*    0   9.0M 1792   9.0M  4.4M  4.4M
10.5M

-------------------------------------------------------------------------------
/Outbound              200.0M 200.0M     0  14.9M 36.8M 51.7M 59.4M 57.4M207.4M
  /Outbound/P2P1/Gnutella-Init
                          2.0M   2.0M*    0     0  9728  9728  38.4k
35.7k  840k
  /Outbound/P2P1/Gnutella-Upload
                          2.0M   2.0M*    0   2.0M    0   2.0M  2.0M  2.0M
3.0M
  /Outbound/P2P1/Gnutella-Cmd
                          3.0M   3.0M*    0     0   3.0M  3.0M  3.0M  3.0M
4.0M
  /Outbound/P2P1/KaZaA-Cmd
                          3.0M   3.0M*    0     0   2.6M  2.6M  2.7M  2.9M
5.0M
  /Outbound/P2P2          3.0M   3.0M*    0   3.0M
4352   3.0M  2.6M  2.5M  4.0M

PacketShaper# me dump class all inbound by element 14d bytes
"time:28-Oct-2002 23:00:01"
"class","bytes"
"/Inbound/Localhost",4603556
"/Inbound/SameSide",37959102
"/Inbound/Critical_Applications/FTP",451603780217
"/Inbound/Critical_Applications/HTTP",2374318201372
"/Inbound/Critical_Applications/SSL",47252299924
"/Inbound/Mail/ccMail",1010870952
"/Inbound/Mail/IMAP",535187034
"/Inbound/Mail/POP3",9675375807
"/Inbound/Mail/SMTP",35628598035
"/Inbound/P2P1/Gnutella-Cmd",264555565312
"/Inbound/P2P1/Gnutella-Download",61372722537
"/Inbound/P2P1/Gnutella-Init",5814075924
"/Inbound/P2P1/Gnutella-Upload",3960215417
"/Inbound/P2P1/KaZaA-Cmd",95353221320
"/Inbound/P2P1/KaZaA-Download",1596535302870
"/Inbound/P2P1/KaZaA-Query",11320677338
"/Inbound/P2P1/KaZaA-Upload",211055232272
"/Inbound/P2P3/Aimster-Cmd",64564376
"/Inbound/P2P3/Aimster-Data",375970439
"/Inbound/P2P3/Aimster-Init",125854
"/Inbound/P2P3/Audiogalaxy",180108197
"/Inbound/P2P3/DirectConnect",107825404509
"/Inbound/P2P3/FileRogue",0
"/Inbound/P2P3/Hotline-TCP",861473645
"/Inbound/P2P3/Hotline-UDP",13287
"/Inbound/P2P3/iMesh",0
"/Inbound/P2P3/Scour-CSC",7379315
"/Inbound/P2P3/Scour-Web",10105
"/Inbound/Voice-Video-R/MPEG-Audio",49152746262
"/Inbound/Voice-Video-R/MPEG-Video",93925086670
"/Inbound/Voice-Video-R/QuickTime",65552955509
"/Inbound/Voice-Video-R/Real",168927336530
"/Inbound/Voice-Video-R/Shoutcast",126889664561
"/Inbound/Voice-Video-R/WinMedia",261459733953
"/Inbound/Games/AsheronsCall",2213298529
"/Inbound/Games/Half-Life",22228715113
"/Inbound/Games/Kali",81060328
"/Inbound/Games/LucasArts",235664428
"/Inbound/Games/Quake",968668314
"/Inbound/Games/Unreal",4101069519
"/Inbound/Games/YahooGames",1174995894
"/Inbound/Games/Battle.net",2222908729
"/Inbound/Games/Mythic",2780960709
"/Inbound/Games/SonyOnline",2281291527
"/Inbound/Games/Tribes",908119508
"/Inbound/Messaging/AOL-IM-File",65857215425
"/Inbound/Messaging/IRC",2870010169
"/Inbound/Messaging/IRC-DCC",113893424582
"/Inbound/Messaging/MSN-Messenger",2730811580
"/Inbound/Messaging/YahooMsg",256450421
"/Inbound/Messaging/AOL-IM-ICQ",116674271510
"/Inbound/P2P2/eDonkey-Ping",52250878
"/Inbound/P2P2/eDonkey-TCP",56845953478
"/Inbound/P2P2/Furthurnet",22227361865
"/Inbound/P2P2/Napster-Cmd",251389466
"/Inbound/P2P2/Napster-Data",237125842455
"/Inbound/P2P2/Napster-Init",17214
"/Inbound/P2P2/Blubster",10264093045
"/Inbound/Terminal_Services/ATSTCP",42784765
"/Inbound/Terminal_Services/RDP",1374633723
"/Inbound/Terminal_Services/rlogin",11644202
"/Inbound/Terminal_Services/rsh",8384
"/Inbound/Terminal_Services/Telnet",5484559900
"/Inbound/Terminal_Services/Timbuktu",3416984369
"/Inbound/Terminal_Services/tn3270",55003849
"/Inbound/Terminal_Services/tn5250",0
"/Inbound/Terminal_Services/VNC",149975073
"/Inbound/Terminal_Services/XWindows",172661464
"/Inbound/Terminal_Services/pcANYWHERE",563339708
"/Inbound/Voice-Video-NR/CUSeeMe",53504552
"/Inbound/Voice-Video-NR/Net2Phone",31292594
"/Inbound/Voice-Video-NR/RTP-I",12884000059
"/Inbound/Voice-Video-NR/T.120",1210989899
"/Inbound/Voice-Video-NR/VDOPhone",5805713
"/Inbound/Voice-Video-NR/Dialpad",267797
"/Inbound/Voice-Video-NR/H.323",1553280634
"/Inbound/Voice-Video-NR/RTSP",1192753338
"/Inbound/Voice-Video-NR/StreamWorks",303276705
"/Inbound/Mgmt-Config/DHCP",199456
"/Inbound/Mgmt-Config/Finger",161358010
"/Inbound/Mgmt-Config/Gopher",19767154
"/Inbound/Mgmt-Config/Ident",3623912937
"/Inbound/Mgmt-Config/LDAP",17738909
"/Inbound/Mgmt-Config/NTP",37189109
"/Inbound/Mgmt-Config/rwho",816106
"/Inbound/Mgmt-Config/SNMP",258365063
"/Inbound/Mgmt-Config/SSDP",5410276
"/Inbound/Mgmt-Config/WHOIS",27594742
"/Inbound/Mgmt-Config/DNS",7160927105
"/Inbound/Mgmt-Config/RIP",940
"/Inbound/Mgmt-Config/TimeServer",40068210
"/Inbound/Mgmt-Config/WINS",2033834
"/Inbound/Mgmt-Config/ICMP",4915621504
"/Inbound/Mgmt-Config/IGMP",4182013
"/Inbound/Mgmt-Config/PIM",2774971
"/Inbound/Mgmt-Config/RSVP",110842
"/Inbound/Other/AFP",3261755738
"/Inbound/Other/AFS",20149893
"/Inbound/Other/BackWeb",68923333
"/Inbound/Other/CIFS-TCP",1070910074
"/Inbound/Other/Citrix/Citrix-PEOPLESOFT_PRODUCTION_DA",1432935
"/Inbound/Other/Citrix/Default",1254622907
"/Inbound/Other/DLS",422361044
"/Inbound/Other/EntryPoint",306163563
"/Inbound/Other/FileMaker",419281730
"/Inbound/Other/Groupwise",171144212
"/Inbound/Other/IPP",6133630
"/Inbound/Other/JavaRMI",250210653
"/Inbound/Other/lockd",15256654
"/Inbound/Other/LotusNotes",243453067
"/Inbound/Other/Marimba",1663752640
"/Inbound/Other/MCK-Signaling",3147468916
"/Inbound/Other/MSSQL",4934473941
"/Inbound/Other/NNTP",165197409450
"/Inbound/Other/NW5-CMD",193272579
"/Inbound/Other/Oracle",6439139954
"/Inbound/Other/OracleClient",1850262
"/Inbound/Other/OracleEM",781280692
"/Inbound/Other/PEPGate",75526543
"/Inbound/Other/Persona",1407059954
"/Inbound/Other/RTCP-I",100031287
"/Inbound/Other/SHARESUDP",22626230
"/Inbound/Other/SMS",2015088000
"/Inbound/Other/Syslog",158154
"/Inbound/Other/WebEx",16375494
"/Inbound/Other/Webshots",225729690
"/Inbound/Other/CU-DEV",8582064
"/Inbound/Other/CVSup",135652966
"/Inbound/Other/Day-Time",457296360
"/Inbound/Other/DCOM",243349498
"/Inbound/Other/Echo",66498263
"/Inbound/Other/Groove",0
"/Inbound/Other/Kontiki",262235573
"/Inbound/Other/Microsoft-ds",2448955998
"/Inbound/Other/MSSQ",3136758804
"/Inbound/Other/NetBIOS-IP",10578716436
"/Inbound/Other/NFS",4563586138
"/Inbound/Other/NW5-NCP",685715
"/Inbound/Other/Printer",509311
"/Inbound/Other/SLP",5361827
"/Inbound/Other/SunRPC",20601707
"/Inbound/Other/Protocol_169",154688786
"/Inbound/Other/Protocol_54",19650
"/Inbound/Secure_Services/GRE",698221509
"/Inbound/Secure_Services/Kerberos",6740318
"/Inbound/Secure_Services/L2TP",45452570
"/Inbound/Secure_Services/PPTP",159828631
"/Inbound/Secure_Services/RADIUS",79169233
"/Inbound/Secure_Services/RC5DES",886491949
"/Inbound/Secure_Services/SSH",7067717369
"/Inbound/Secure_Services/ISAKMP",91169932
"/Inbound/Secure_Services/IPSec",1354534608
"/Inbound/DiscoveredPorts/Mcast2",110659904373
"/Inbound/DiscoveredPorts/Mcast1",2914334549589
"/Inbound/Default",865118208331


PacketShaper# me dump class all outbound by element 14d bytes
"time:28-Oct-2002 23:00:01"
"class","bytes"
"/Outbound/Localhost",14198894
"/Outbound/SameSide",13155495
"/Outbound/Critical_Applications/FTP",159401337555
"/Outbound/Critical_Applications/HTTP",705941567579
"/Outbound/Critical_Applications/SSL",44009854795
"/Outbound/Mail/ccMail",13139129198
"/Outbound/Mail/IMAP",1797914739
"/Outbound/Mail/POP3",11685778046
"/Outbound/Mail/SMTP",33806379893
"/Outbound/P2P1/Gnutella-Cmd",278224811847
"/Outbound/P2P1/Gnutella-Download",1785967822
"/Outbound/P2P1/Gnutella-Init",5482315153
"/Outbound/P2P1/Gnutella-Upload",139227207983
"/Outbound/P2P1/KaZaA-Cmd",135458453344
"/Outbound/P2P1/KaZaA-Download",48175541015
"/Outbound/P2P1/KaZaA-Query",9645843514
"/Outbound/P2P1/KaZaA-Upload",2698416692078
"/Outbound/P2P3/Aimster-Cmd",47752928
"/Outbound/P2P3/Aimster-Data",516471222
"/Outbound/P2P3/Aimster-Init",91244
"/Outbound/P2P3/Audiogalaxy",49475045
"/Outbound/P2P3/DirectConnect",85999241138
"/Outbound/P2P3/FileRogue",0
"/Outbound/P2P3/Hotline-TCP",128545654
"/Outbound/P2P3/Hotline-UDP",44388
"/Outbound/P2P3/iMesh",0
"/Outbound/P2P3/Scour-CSC",24749143
"/Outbound/P2P3/Scour-Web",12805
"/Outbound/Voice-Video-R/MPEG-Audio",4457607886
"/Outbound/Voice-Video-R/MPEG-Video",5429672257
"/Outbound/Voice-Video-R/QuickTime",24608217860
"/Outbound/Voice-Video-R/Real",9241093420
"/Outbound/Voice-Video-R/Shoutcast",8815243651
"/Outbound/Voice-Video-R/WinMedia",13078855054
"/Outbound/Games/AsheronsCall",729297960
"/Outbound/Games/Half-Life",16766466096
"/Outbound/Games/Kali",13637492
"/Outbound/Games/LucasArts",146672792
"/Outbound/Games/Quake",722884583
"/Outbound/Games/Unreal",3026783769
"/Outbound/Games/YahooGames",777825438
"/Outbound/Games/Battle.net",1259995159
"/Outbound/Games/Mythic",515990629
"/Outbound/Games/SonyOnline",491783925
"/Outbound/Games/Tribes",1033421305
"/Outbound/Messaging/AOL-IM-File",124982598262
"/Outbound/Messaging/IRC",802178325
"/Outbound/Messaging/IRC-DCC",193715086500
"/Outbound/Messaging/MSN-Messenger",1386353439
"/Outbound/Messaging/YahooMsg",130472695
"/Outbound/Messaging/AOL-IM-ICQ",41319025869
"/Outbound/P2P2/eDonkey-Ping",179635282
"/Outbound/P2P2/eDonkey-TCP",58939538563
"/Outbound/P2P2/Furthurnet",18919044613
"/Outbound/P2P2/Napster-Cmd",127819141
"/Outbound/P2P2/Napster-Data",187973086595
"/Outbound/P2P2/Napster-Init",9142
"/Outbound/P2P2/Blubster",15553891452
"/Outbound/Terminal_Services/ATSTCP",65349387
"/Outbound/Terminal_Services/RDP",1841530538
"/Outbound/Terminal_Services/rlogin",8139631
"/Outbound/Terminal_Services/rsh",6921
"/Outbound/Terminal_Services/Telnet",2740337650
"/Outbound/Terminal_Services/Timbuktu",2869905944
"/Outbound/Terminal_Services/tn3270",103053680
"/Outbound/Terminal_Services/tn5250",0
"/Outbound/Terminal_Services/VNC",286801914
"/Outbound/Terminal_Services/XWindows",583468837
"/Outbound/Terminal_Services/pcANYWHERE",1380988898
"/Outbound/Voice-Video-NR/CUSeeMe",44294395
"/Outbound/Voice-Video-NR/Net2Phone",16521949
"/Outbound/Voice-Video-NR/RTP-I",11565149219
"/Outbound/Voice-Video-NR/T.120",1274733567
"/Outbound/Voice-Video-NR/VDOPhone",31913037
"/Outbound/Voice-Video-NR/Dialpad",320676
"/Outbound/Voice-Video-NR/H.323",1398552398
"/Outbound/Voice-Video-NR/RTSP",30824299
"/Outbound/Voice-Video-NR/StreamWorks",259466827
"/Outbound/Mgmt-Config/DHCP",187226
"/Outbound/Mgmt-Config/Finger",46933433
"/Outbound/Mgmt-Config/Gopher",12158005
"/Outbound/Mgmt-Config/Ident",1022086235
"/Outbound/Mgmt-Config/LDAP",37414658
"/Outbound/Mgmt-Config/NTP",45333565
"/Outbound/Mgmt-Config/rwho",643075
"/Outbound/Mgmt-Config/SNMP",245673903
"/Outbound/Mgmt-Config/SSDP",4455344
"/Outbound/Mgmt-Config/WHOIS",11296617
"/Outbound/Mgmt-Config/DNS",5013694369
"/Outbound/Mgmt-Config/RIP",2115
"/Outbound/Mgmt-Config/TimeServer",22610473
"/Outbound/Mgmt-Config/WINS",1934785
"/Outbound/Mgmt-Config/ICMP",4402154519
"/Outbound/Mgmt-Config/IGMP",47
"/Outbound/Mgmt-Config/PIM",20038759
"/Outbound/Mgmt-Config/RSVP",4018640
"/Outbound/Other/AFP",5758205932
"/Outbound/Other/AFS",1329119
"/Outbound/Other/BackWeb",46629700
"/Outbound/Other/CIFS-TCP",5493656659
"/Outbound/Other/Citrix/Citrix-PEOPLESOFT_PRODUCTION_DA",1043542
"/Outbound/Other/Citrix/Default",6549402393
"/Outbound/Other/DLS",351288673
"/Outbound/Other/EntryPoint",22829385
"/Outbound/Other/FileMaker",19612477
"/Outbound/Other/Groupwise",197184078
"/Outbound/Other/IPP",7966920
"/Outbound/Other/JavaRMI",772115683
"/Outbound/Other/lockd",7477052
"/Outbound/Other/LotusNotes",444379993
"/Outbound/Other/Marimba",41286924
"/Outbound/Other/MCK-Signaling",522352061
"/Outbound/Other/MSSQL",1450217652
"/Outbound/Other/NNTP",4385415598
"/Outbound/Other/NW5-CMD",146933443
"/Outbound/Other/Oracle",12248175121
"/Outbound/Other/OracleClient",458100
"/Outbound/Other/OracleEM",935022106
"/Outbound/Other/PEPGate",33915851
"/Outbound/Other/Persona",5657514773
"/Outbound/Other/RTCP-I",90980936
"/Outbound/Other/SHARESUDP",10069919
"/Outbound/Other/SMS",3450585966
"/Outbound/Other/Syslog",3113597
"/Outbound/Other/WebEx",6890878
"/Outbound/Other/Webshots",13242133
"/Outbound/Other/CU-DEV",3707084
"/Outbound/Other/CVSup",170607389
"/Outbound/Other/Day-Time",121763417
"/Outbound/Other/DCOM",360778893
"/Outbound/Other/Echo",32334156
"/Outbound/Other/Groove",0
"/Outbound/Other/Kontiki",2155729412
"/Outbound/Other/Microsoft-ds",2716185498
"/Outbound/Other/MSSQ",7853181085
"/Outbound/Other/NetBIOS-IP",5909575896
"/Outbound/Other/NFS",4259797440
"/Outbound/Other/NW5-NCP",1697189
"/Outbound/Other/Printer",1359127
"/Outbound/Other/SLP",2332423
"/Outbound/Other/SunRPC",882013
"/Outbound/Other/Protocol_169",162564754
"/Outbound/Other/Protocol_54",1329230
"/Outbound/Secure_Services/GRE",2021284179
"/Outbound/Secure_Services/Kerberos",6307162
"/Outbound/Secure_Services/L2TP",55637355
"/Outbound/Secure_Services/PPTP",200182016
"/Outbound/Secure_Services/RADIUS",28323008
"/Outbound/Secure_Services/RC5DES",8658857277
"/Outbound/Secure_Services/SSH",10545423361
"/Outbound/Secure_Services/ISAKMP",89158267
"/Outbound/Secure_Services/IPSec",551933351
"/Outbound/DiscoveredPorts/UDP_Port_8481",98394209
"/Outbound/Default",912266811316

At 08:47 AM 11/10/2002 -0800, Bill Woodcock wrote:

>Any really rough guess what portion of Internet traffic is VoIP or live
>video?
>
>                                 -Bill
>
>
>---------- Forwarded message ----------
>Date: Sun, 10 Nov 2002 08:28:05 -0500
>From: RJ Atkinson <rja@extremenetworks.com>
>To: "Nguyen, An" <nguyena@ncs.gov>
>Cc: ieprep <ieprep@ietf.org>
>Subject: [Ieprep] network congestion, VoIP, NCS contracting approach, etc.
>
>
>On Saturday, Nov 9, 2002, at 20:00 America/Montreal, Nguyen, An wrote:
> > When the 9/11 happened last year, the internet traffic was fine in
> > general
> > according to you and others. Do you have any rough number on how much
> > of it
> > was time-sensitive ( e.g., voiceIP, video, etc.) traffic?
>
>I haven't seen any *good* measured statistics on which applications
>consume
>what % of (packets, bytes) since I stopped working for an ISP.
>
> > I guess the percentage of time-sensitive must have been very little
> > compared to
> > time-insensitive data traffic such as web, email, and others. My
> > thinking is
> > when people surf the web or send an email, they don't care much if
> > there are
> > congestions in the networks because they commonly accept it as the way
> > the
> > internet works.
>
>Ah.   The measured data from 9/11 did measure potential congestion.  It
>was
>miniscule inside the Internet.  The measured data indicates that there
>WERE
>problems with server performance of some popular web servers; -- those
>content
>providers ripped graphics off their web pages moving to HTML only, then
>reconfigured/added servers, and eventually solved those content server
>issues
>on that day.
>
> > But when it comes to voice traffic, it is a totally
> > different matter ( very noticeable as you and I experience it with the
> > cellular phone).
>
>I used inter-domain VoIP on the morning of 9/11 and did not experience
>any problems.  Note that one end of that link was in the Reston area,
>transiting MAE-East on its way to MAE-West, with the other end in
>Silicon
>Valley.  That's only one sample, admittedly, but it is a sample that is
>entirely consistent with the actual measured data on network behaviour
>during 9/11.
>
>If the Internet had broken on 9/11, which it emphatically did not (as
>measured data clearly shows), then an argument to change the way ISPs
>deploy their network might be more persuasive.  Since that did NOT
>happen,
>there is very good reason to continue to use what clearly worked well
>under unusual circumstances.   (Since it isn't broken, why change it.)
>
> > This leads me to ask you, Bill, and others another
> > question: do you foresee that the Internet will be use to  transport
> > most of
> > voice traffic and other time-sensitive applications and eventually will
> > replace POTS network because of its ubiquity?
>
>I seriously doubt that the PSTN will ever be replaced by a VoIP network.
>I think VoIP is more likely to be used within a campus or to build
>relatively small-scale (compared with PSTN) intra-organisational
>cost-optimised
>toll bypass.  And I think those campus phone switches will continue
>to have traditional PSTN interfaces.  If nothing else, that will be
>needed
>to contact folks who are off-the-VoIP-network (e.g. customers, mobile
>phone
>users) and take incoming calls from the PSTN.
>
>My employer uses VoIP and lease-lines to bypass long-distance toll
>charges
>on some intra-company links, but we use a huge amount of PSTN also.
>The DoD's
>AutoVON/DSN does the same (no VoIP, due to JCS directive, but private
>connectivity
>for sure), yet DoD still uses a huge amount of PSTN.  So does GE's
>corporate
>phone network.  Bypasses such as the one that GE built/uses have been
>around
>for many many years, yet have not affected growth of the PSTN.
>
>[Aside: I'm aware of DISA's use of VoIP at Skyline and also that not all
>residents of Skyline like it;  (ironic quote of the day from earlier in
>2002
>from someone who works there:  "The beauty of VoIP is that when the
>data network
>is down, one can't report the outage to the network support staff.")]
>
>The PSTN has the advantage that it is overwhelmingly one application,
>voice,
>which is well characterised and predictable, so it can (and does)
>optimise its
>network design/deployment for that one application.
>
>The Internet will never have the luxury of only supporting a single
>application
>in that way, so the Internet will need to continue to have a different
>kind
>of design approach.
>
> > NCSs's mission is to ensure that communications are available during
> > emergency and crisis. We need to communicate with others when emergency
> > occurs. And when emergency happens in an area, traffic congestions are
> > likely to occur. So, without some sort of priority treatment for NS/EP
> > traffic, it's extremely hard for us to fulfill our mission.
>
>Prioritisation is a mechanism.  The NCS mission, as you state, is to
>ensure communications availability.  NCS ought not care which mechanism
>is used, provided that communications remain available.
>
>Over-provisioning is a different mechanism, commonly used today (max
>link
>utilisation equal to 30% of link capacity is typical among the ISPs I
>was talking
>with last Thursday),  to ensure that packets don't get lost in the
>network,
>because it is cheaper than deploying something like DiffServ.  Other
>mechanisms
>also exist.
>
>[ASIDE:         So far, each time there has been a press release or article
>claiming that ISP <x> has deployed DiffServ throughout its network,
>when I
>have tracked down the facts of the matter it has turned out to be
>marketing
>or press confusion unrelated to the actual operational network.  It
>would be
>VERY helpful if any ISP would make a public presentation at NANOG/RIPE
>about
>their deployment.  So if anyone is at such a place and is listening,
>please
>consider making such a public presentation in detail.]
>
>An alternative perspective is that NCS ought to focus on talking with
>ISPs about
>contracts that have *performance-based* metrics for ensuring network
>availability,
>rather than contracts that require particular mechanisms to be deployed
>(whether or not those mechanisms work in a particular situation).
>
>After all, as long as an ISP that has chosen to provide contracted
>services
>to NCS can provide those services, why should NCS care which
>mechanism(s)
>are used to provide those services ?
>
>This alternative view is consistent with more recent USG contracting
>practices,
>such as the USN outsourcing of its LANs to EDS, where EDS is given
>performance
>metrics to achieve, but has total flexibility in how to meet those
>metrics.
>
>Ran
>rja@extremenetworks.com
>
>_______________________________________________
>Ieprep mailing list
>Ieprep@ietf.org
>https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 11:10:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04652
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 11:10:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACGCD610903
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 11:12:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACGCDv10900
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 11:12:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04648
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 11:09:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACGBDv10882;
	Tue, 12 Nov 2002 11:11:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACGA5v10855
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 11:10:05 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04626
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 11:07:27 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACG43d00358;
	Tue, 12 Nov 2002 08:04:03 -0800 (PST)
Date: Tue, 12 Nov 2002 08:04:03 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Krishnan Padmanabhan, Packet Strategies LLC" <krishnan@packetstrategies.com>
cc: RJ Atkinson <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: Re: [Ieprep] Billing for VoIp service
In-Reply-To: <00d701c28a48$44848890$6400a8c0@sumt01.nj.comcast.net>
Message-ID: <Pine.GSO.4.44.0211120757100.178-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002, Krishnan Padmanabhan, wrote:
    > Via Windows Messenger or MSN Messenger, you can subscribe to the
    > VoIP services offered by several service providers. At least two of
    > these (I haven't tried the others) provide per minute billing for
    > the IP Telephony calls, call details, history, etc. They also appear
    > to offer, in addition to IP telephony, the usual internet access
    > services. Would these offer a counter-example to the point you make
    > here?

Yes.  This more demonstrates that we live in a large and diverse world
than demonstrating anything in particular about business models which
bundle L3 and L7 services, however.  There are also database application
service providers who would happily sell their customers ISP services, and
ISPs who would happily sell their customers db ASP services, but that
business model is also not taking the world by storm.

You're absolutely correct that you've provided a valid specific
counterexample, however Ran was characterizing business practices
generally, and there would be far more people in the world giving away
these services for free, for example, than there are bundling them
together to bill for them.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 11:15:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04902
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 11:15:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACGHnm11129
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 11:17:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACGHnv11126
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 11:17:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04885
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 11:15:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACGH1v11090;
	Tue, 12 Nov 2002 11:17:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACGGav11062
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 11:16:36 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04848
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 11:13:57 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACGARd00463;
	Tue, 12 Nov 2002 08:10:27 -0800 (PST)
Date: Tue, 12 Nov 2002 08:10:27 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Garrity, Jack" <JOHN.J.GARRITY@saic.com>
cc: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-Reply-To: <B8030EB94AF1D51196D70002A589D64231E537@mcl-its-exs01>
Message-ID: <Pine.GSO.4.44.0211120804520.178-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002, Garrity, Jack wrote:
    > For the scenario you describe, the NS/EP codepoint and NS/EP features take
    > effect at GETS-capable local exchanges.  Those exchanges serve over X
    > percent of US-based access lines, where X is on the order of 85 percent or
    > greater.
    > If the terminating local exchange is GETS-capable (same switches
    > as in the first paragraph), NS/EP features have effect.

So about 70% of U.S. domestic source-destination pairs are covered.  Since
as has been pointed out many times recently, there's no practical way of
distinguishing national borders on the Internet, I don't have
U.S.-specific figures.  However, if the DoD purchased GETS-like services
from the dozen or so usual suspects globally, they'd have only about 4%
coverage.  (20% of 20%, rather than 85% of 85%).  There are a _lot_ of
ISPs, and the large ones aren't that large relative to the whole.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 11:41:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05829
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 11:41:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACGhkQ12836
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 11:43:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACGhkv12833
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 11:43:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05782
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 11:41:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACGh1v12771;
	Tue, 12 Nov 2002 11:43:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACGaBv11935
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 11:36:11 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA05563
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 11:33:34 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 12 Nov 2002 16:33:40 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WYQLGG5T>; Tue, 12 Nov 2002 11:37:20 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D23A4B8@emshqs1.ncr.disa.mil>
From: "Folts, Harold" <foltsh@ncs.gov>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: "'ieprep'" <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: more process discussion
Date: Tue, 12 Nov 2002 11:36:05 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> -----Original Message-----
> From: ieprep-admin@ietf.org [mailto:ieprep-admin@ietf.org] On Behalf 
> Of RJ Atkinson
> Sent: Thursday, November 07, 2002 3:52 PM
> To: Mpierce1@aol.com
> Cc: ieprep
> Subject: [Ieprep] Re: more process discussion
> 


 	So woody is right that the IETF's hope is that one will
> represent
> one's own
> views -- particularly when those conflict directly with sponsor's 
> views, the
> community is also looking for full openness about what the potential 
> sources of bias
> are in any given person's stated views.  Direct funding to 
> participate 
> in an effort
> on <foo> is a potential bias.  We all hope it does not actually 
> translate into an
> actual bias, at least within the IETF's scope.
> 
> 	Hal's seeming reluctance to participate directly and
> respond in a
> timely manner
> to questions directly relating to his employer's goals has not helped 
> things at all,
> IMNVHO.  It sure looks from the outside that Hal is trying to 
> cover up 
> his
> financial relationships with various DISA contractors who are 
> participating in
> this WG and that appears that he's trying to use that obscurity to 
> further his
> private agenda. This fosters widespread suspicion and mistrust, 
> whereas openness
> from the get go would have done quite the opposite.

Ran,

First let me apologize for my silence over the past week in responding to
the list. I have been on travel and my Internet access was very limited and
extremely slow (very high error rate) - to the point of being totally
unusable. I did manage to receive most of the traffic, but timely responses
have not been possible. I now have some 200 emails from the list to catch up
with, so I hope to provide some response in the next day or so as I plow
through these along with my other workload.

The issue of who represents who and the notion of personal agenda is an
unnecessary diversion from the discussions. You could say that anybody
expressing views on the list has a personal agenda. All this pissing contest
does is detract from substantive discussion.

I do not represent any "personal" agenda. I do not in any way have
'financial relationships with any DISA contactors". I am on detail to the
NCS from NASA, who issues my paycheck. NCS is a confederation of 22 Federal
Departments and Agencies - visit http://www.ncs.gov/ for details. DoD is one
of those 22, as is NASA. 

NCS was given this task as a result of a recommendation to the President
from telecommunications industry through the National Security
Telecommunications Advisory Committee (NSTAC), which is includes many
prominent telecommunication service providers - visit
http://www.ncs.gov/NSTAC/nstac.htm for more details. I was assigned this
task to work with industry worldwide and other nations to establish a list
of requirements and seek establishment of industry standards to fulfill the
requirements. I have been working the project for over three years now. The
IETF is only one of the organizations that I am working with. I have been
collaborating and working with many governments and telecommunications
industry representatives worldwide in addressing the many issues associated
with provision of communication capabilities for emergency and disaster
relief in FUTURE networks.

The "requirements" that are presented in the ID are really better
characterized as "objectives" to be considered. Some may already be
accommodated with existing provisions. Others may be fulfilled with new work
or additions. And some may not ever be possible. The ID is intended to be a
basic "wish list" without bias as to how they might be fulfilled. The
"requirements" presented have evolved from considerable research,
collaboration, and input from prominent telecommunications industry
organizations, disaster relief organizations, and governments around the
world.

Unfortunately, many other countries do not consider IETF an international
activity. I have argued against this view and aggressively defended the IETF
on this issue. I have encountered little interest elsewhere in recognition
of the important role of the IETF for addressing the technical issues of the
Internet. This is most likely the reason that there has been little input
from other areas of the world.

I hope that we can get on with this work in a constructive context and reach
agreement of meaningful and effective solutions using Internet technology
that will enable provision of public telecommunication capabilities in
FUTURE networks for emergency and disaster relief operations for saving
lives and restoring the community living conditions.

Hal
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 12:02:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06547
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 12:02:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACH52m14322
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 12:05:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACH52v14319
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 12:05:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06543
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 12:02:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACH41v14238;
	Tue, 12 Nov 2002 12:04:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACH1lv13823
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 12:01:47 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06449
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 11:59:08 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Tue, 12 Nov 2002 08:58:24 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gACGxQb9007393;
	Tue, 12 Nov 2002 08:59:26 -0800 (PST)
Subject: RE: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 -
	discussion request]
From: Rex Buddenberg <budden@nps.navy.mil>
To: "Ayyasamy, Senthilkumar   ""(UMKC-Student)" <saq66@umkc.edu>
Cc: RJ Atkinson <rja@extremenetworks.com>, ieprep@ietf.org
In-Reply-To: <A29143A40AEAE3459FF829D1DD4331610234EF83@KC-MAIL2.kc.umkc.edu>
References: <A29143A40AEAE3459FF829D1DD4331610234EF83@KC-MAIL2.kc.umkc.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 12 Nov 2002 08:57:25 -0800
Message-Id: <1037120246.3604.308.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Sat, 2002-11-09 at 18:11, Ayyasamy, Senthilkumar (UMKC-Student)
wrote:
<snip>
> > 	Several operators have defined both "service 
> > availability" and "SLA".
> 
> I always have this doubt. Do people really see all this 5 9s
> (availability) issue?
>
What do you mean by 'do people really see'?  If you are speculating that
this is an unrecognized requirement, then YES.  

Indeed, I'm suspecting that the fog is here in this WG too -- if an ISP
got the Ao right, a lot of the congestion issues would be NOPs. That's
certainly my experience in my former life (USCG).  

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 12:15:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07057
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 12:15:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACHI7t15469
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 12:18:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHI7v15466
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 12:18:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07035
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 12:15:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHH7v15413;
	Tue, 12 Nov 2002 12:17:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHGpv15394
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 12:16:51 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06992
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 12:14:13 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Tue, 12 Nov 2002 12:16:27 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111212163301560
 ; Tue, 12 Nov 2002 12:16:33 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WYJXPCG6>; Tue, 12 Nov 2002 12:16:20 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E7795B@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Folts, Harold'" <foltsh@ncs.gov>,
        "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: "'ieprep'" <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: more process discussion
Date: Tue, 12 Nov 2002 12:16:31 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Hal,

> I hope that we can get on with this work in a constructive 
> context and reach
> agreement of meaningful and effective solutions using 
> Internet technology
> that will enable provision of public telecommunication capabilities in
> FUTURE networks for emergency and disaster relief operations 
> for saving
> lives and restoring the community living conditions.

You made a point of twice stating "FUTURE networks".  It might be worth
elaborating what you mean by this.

Scott has mentioned as related aspect of context previously:
"should this WG be talking about what the Internet can be expected
   to be able to do now or in the immediate future (see 1st deliverable
   in the WG charter) of speculate on what might be possible at some
   point in the future?

(my feeling, if its not clear, is that we should stick to the world
of today and the near future)"

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 12:48:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07989
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 12:48:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACHolx17285
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 12:50:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHolv17282
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 12:50:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07978
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 12:48:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHn2v17145;
	Tue, 12 Nov 2002 12:49:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHkWv17030
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 12:46:32 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07804
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 12:43:53 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACHeQd02071;
	Tue, 12 Nov 2002 09:40:26 -0800 (PST)
Date: Tue, 12 Nov 2002 09:40:26 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Garrity, Jack" <JOHN.J.GARRITY@saic.com>
cc: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-Reply-To: <Pine.GSO.4.44.0211120804520.178-100000@paixhost.pch.net>
Message-ID: <Pine.GSO.4.44.0211120934580.857-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002, Bill Woodcock wrote:
    > So about 70% of U.S. domestic source-destination pairs are covered.
    > If the DoD purchased GETS-like services from the dozen or so usual
    > [ISP] suspects globally, they'd have only about 4% coverage.  (20%
    > of 20%, rather than 85% of 85%).  There are a _lot_ of ISPs, and the
    > large ones aren't that large relative to the whole.

Oop, sorry, posted that pretty early in the morning, my time; well before
my brain was in gear.  Average AS path length is between 3.5 and 6,
depending where you look at the table, with most measurements clustering
at or a little above 4.  So if you want L3 QoS for the path, it's actually
0.16% (20% of 20% of 20% of 20%).  You could increase that a little by
constraining your target population to U.S.-only, but it wouldn't help
that much, since the U.S. is still a relatively representative subset of
the whole.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 12:48:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08003
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 12:48:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACHp7A17307
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 12:51:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHp7v17304
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 12:51:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07983
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 12:48:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHo1v17263;
	Tue, 12 Nov 2002 12:50:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHnev17226
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 12:49:40 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07895
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 12:47:01 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 12 Nov 2002 17:47:08 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WYQLGKDT>; Tue, 12 Nov 2002 12:50:48 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D0D@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock'" <woody@pch.net>, RJ Atkinson <rja@extremenetworks.com>
Cc: ieprep@ietf.org
Subject: RE: [Ieprep] Measurement of Internet Congestion
Date: Tue, 12 Nov 2002 12:49:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


Bill,

I went through your presentation slides in one of those you said "Sound
quality far exceeds
that of PSTN". I don't technically agree with it. The reasons are as
follows:

1. If your network does support G.711 voice codec at all, then QoS in your
network might be as good as G.711 in the PSTN given that there are no
hick-ups or congestions in your networks. If your network only supports much
narrower voice band such as G.729, G.723.1 or GSM, the QoS is obviously
noticeable as we all experience with low bit rate codecs in the cellular
wireless networks. According to the ITU Means of Score (MoS) , G.711 is
about 4.3 and other low bit rate codecs are in the 3.0 ~3.5 range.  In
short, G.711 is G.711 regardless of the transport layer. If your network
supports wide-band audio codecs for telephony ( which I doubt) , then I
would sincerely like to withdraw this comment.

2. Let me tell the experience with the VoiceIP deployment I have been
involved with. NCS had a project to build a private packet-based network
supporting VoiceIP and videoconferencing traffic for closed groups of users
that are geographically dispersed. Basically, this private network was built
based on Frame Relay for access and ATM for transport. After the request for
information on the project was put out on the web, we got five or six
LARGEST vendors' responses. None of them wanted to guarantee end-to-end High
Availability of 99.999 ( as currently provided in PSTN) for this service.
They said the max they could provide was 99.9 because they can't control the
access points which generally are owned by different service providers.  

Let's say your network has no problem whatsoever because of its unique
architecture. But the rest of the ISPs, I can imagine,  would have this kind
of problem: access. And NCS has to deal with many ISPs to address this issue
in order to get ubiquitous.


Regards,

An 


From: Bill Woodcock [mailto:woody@pch.net]
Sent: Saturday, November 09, 2002 2:23 PM
To: RJ Atkinson
Cc: ieprep@ietf.org
Subject: Re: [Ieprep] Measurement of Internet Congestion


      On Sat, 9 Nov 2002, RJ Atkinson wrote:
    > 	You at least owe us a URL or bibliographic citation to your own work
    > if you are using it as your justification.  Henning was good enough to
    > provide a specific URL and bibliographic citation, which helped focus
    > things a great deal.
    > 	Maybe you could find some presentations from NANOG, RIPE, or APRICOT
    > that are online and relevant to the discussion ?

The slide-set from NANOG is at:

http://www.pch.net/inoc-dba/INOC-DBA-announcement.htm

Slide 9 has a chart with calls-per-day in yellow and number of phones in
use in red.  Of course, they're out-of-date now, since we're into
November.

Slide 8 is PAF's nephew, setting up his phone.  Which worked fine, by the
way.  :-)

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:06:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08632
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:06:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACI8ZU18757
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:08:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACI8Zv18754
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:08:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08618
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:05:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACI11v17872;
	Tue, 12 Nov 2002 13:01:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACI0Tv17782
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:00:29 -0500
Received: from imo-m07.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08341
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 12:57:50 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m07.mx.aol.com (mail_out_v34.13.) id b.102.1ea27f49 (4262);
	Tue, 12 Nov 2002 12:58:29 -0500 (EST)
Message-ID: <102.1ea27f49.2b029b45@aol.com>
Date: Tue, 12 Nov 2002 12:58:29 EST
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
To: woody@pch.net, JOHN.J.GARRITY@saic.com
CC: K.Carlberg@cs.ucl.ac.uk, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_102.1ea27f49.2b029b45_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_102.1ea27f49.2b029b45_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/12/2002 11:21:08 AM Eastern Standard Time, 
woody@pch.net writes:


>     On Tue, 12 Nov 2002, Garrity, Jack wrote:
>     > For the scenario you describe, the NS/EP codepoint and NS/EP features 
> take
>     > effect at GETS-capable local exchanges.  Those exchanges serve over X
>     > percent of US-based access lines, where X is on the order of 85 
> percent or
>     > greater.
>     > If the terminating local exchange is GETS-capable (same switches
>     > as in the first paragraph), NS/EP features have effect.
> 
> So about 70% of U.S. domestic source-destination pairs are covered.  Since
> as has been pointed out many times recently, there's no practical way of
> distinguishing national borders on the Internet, I don't have
> U.S.-specific figures.  However, if the DoD purchased GETS-like services
> from the dozen or so usual suspects globally, they'd have only about 4%
> coverage.  (20% of 20%, rather than 85% of 85%).  There are a _lot_ of
> ISPs, and the large ones aren't that large relative to the whole.
> 


The math above that arrives at 70% and 4% is really not significant. The 
orginating (85%) and terminating (85%) are distinct parts of the capabilities 
desired. They are not both required to do anything. The calculation of .85 x 
.85 = .70 only tells you what percentage of the calls get both the 
originating exchange and the terminating exchange functionality. It's still 
true that 85% of calls get each, and 97.75% get one or the other.

And NCS (please stop referring to DoD) can purchase GETS-like services from 
any number of carriers that offer it.

Mike Pierce
Artel


--part1_102.1ea27f49.2b029b45_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/12/2002 11:21:08 AM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&nbsp;On Tue, 12 Nov 2002, Garrity, Jack wrote:
<BR> &nbsp;&nbsp;&nbsp;&gt; For the scenario you describe, the NS/EP codepoint and NS/EP features take
<BR> &nbsp;&nbsp;&nbsp;&gt; effect at GETS-capable local exchanges. &nbsp;Those exchanges serve over X
<BR> &nbsp;&nbsp;&nbsp;&gt; percent of US-based access lines, where X is on the order of 85 percent or
<BR> &nbsp;&nbsp;&nbsp;&gt; greater.
<BR> &nbsp;&nbsp;&nbsp;&gt; If the terminating local exchange is GETS-capable (same switches
<BR> &nbsp;&nbsp;&nbsp;&gt; as in the first paragraph), NS/EP features have effect.
<BR>
<BR>So about 70% of U.S. domestic source-destination pairs are covered. &nbsp;Since
<BR>as has been pointed out many times recently, there's no practical way of
<BR>distinguishing national borders on the Internet, I don't have
<BR>U.S.-specific figures. &nbsp;However, if the DoD purchased GETS-like services
<BR>from the dozen or so usual suspects globally, they'd have only about 4%
<BR>coverage. &nbsp;(20% of 20%, rather than 85% of 85%). &nbsp;There are a _lot_ of
<BR>ISPs, and the large ones aren't that large relative to the whole.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>The math above that arrives at 70% and 4% is really not significant. The orginating (85%) and terminating (85%) are distinct parts of the capabilities desired. They are not both required to do anything. The calculation of .85 x .85 = .70 only tells you what percentage of the calls get both the originating exchange and the terminating exchange functionality. It's still true that 85% of calls get each, and 97.75% get one or the other.
<BR>
<BR>And NCS (please stop referring to DoD) can purchase GETS-like services from any number of carriers that offer it.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_102.1ea27f49.2b029b45_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:08:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08705
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:08:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACIACq18815
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:10:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIACv18812
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:10:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08691
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:07:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACI02v17738;
	Tue, 12 Nov 2002 13:00:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHxPv17688
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 12:59:25 -0500
Received: from imo-d06.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08257
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 12:56:47 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d06.mx.aol.com (mail_out_v34.13.) id b.ac.30f90393 (4262);
	Tue, 12 Nov 2002 12:58:41 -0500 (EST)
Message-ID: <ac.30f90393.2b029b51@aol.com>
Date: Tue, 12 Nov 2002 12:58:41 EST
Subject: Re: [Ieprep] Requirements for Accounting
To: woody@pch.net
CC: jmpolk@cisco.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_ac.30f90393.2b029b51_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_ac.30f90393.2b029b51_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/12/2002 3:33:59 AM Eastern Standard Time, woody@pch.net 
writes:


>    > If "Accounting" or "X" or "Y" is included in the IEPREP doc as a
>     > "requirement", it only means that some other WG must figure out a
>     > way to support it.
> 
> No, it _most certainly does not_ mean that.  And if you really think it
> does, get ready for them to toss you out on your ear again.
> 


[MAP] Perhaps I am blind, naive, or both. But I didn't think that I had been 
"tossed out on my ear" yet (by the WG). I haven't gotten any indication from 
the Chair or ADs that I was off-base. And if I did, I guess I could apply the 
procedure described by Ran 6 days ago as follows:

And attempts by any AD or WG Chair to stop one from doing that would 
certainly be
appealable (and such an AD action would be very likely to be overturned on 
appeal,
in my own reading of the tea leaves, on grounds that it is contrary to IETF 
openness
as a standards-body).

As Scott wrote on Oct 14:

the primary task on the WG's plate right now is to come to consensus 
on a requirements document to be forwarded to the sipping working group
(obviously that document needs to be  SIP-specific)

Mike Pierce
Artel



--part1_ac.30f90393.2b029b51_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/12/2002 3:33:59 AM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&gt; If "Accounting" or "X" or "Y" is included in the IEPREP doc as a
<BR> &nbsp;&nbsp;&nbsp;&gt; "requirement", it only means that some other WG must figure out a
<BR> &nbsp;&nbsp;&nbsp;&gt; way to support it.
<BR>
<BR>No, it _most certainly does not_ mean that. &nbsp;And if you really think it
<BR>does, get ready for them to toss you out on your ear again.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] Perhaps I am blind, naive, or both. But I didn't think that I had been "tossed out on my ear" yet (by the WG). I haven't gotten any indication from the Chair or ADs that I was off-base. And if I did, I guess I could apply the procedure described by Ran 6 days ago as follows:
<BR>
<BR>And attempts by any AD or WG Chair to stop one from doing that would certainly be
<BR>appealable (and such an AD action would be very likely to be overturned on appeal,
<BR>in my own reading of the tea leaves, on grounds that it is contrary to IETF openness
<BR>as a standards-body).
<BR>
<BR>As Scott wrote on Oct 14:
<BR>
<BR>the primary task on the WG's plate right now is to come to consensus 
<BR>on a requirements document to be forwarded to the sipping working group
<BR>(obviously that document needs to be &nbsp;SIP-specific)
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR></FONT></HTML>

--part1_ac.30f90393.2b029b51_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:08:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08730
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:08:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACIAdA18842
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:10:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIAcv18839
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:10:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08702
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:08:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACI41v17993;
	Tue, 12 Nov 2002 13:04:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACI32v17949
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:03:02 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08419
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 13:00:23 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACHuxd02512;
	Tue, 12 Nov 2002 09:56:59 -0800 (PST)
Date: Tue, 12 Nov 2002 09:56:59 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: RJ Atkinson <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: RE: [Ieprep] Measurement of Internet Congestion
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D0D@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211120947070.857-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002, Nguyen, An wrote:
    > In short, G.711 is G.711 regardless of the transport layer.

Yes, of course.  However, on the PSTN, that's switch-to-switch.  Several
miles of bridge-tapped 28-gauge junk away from each user, in nearly the
best case.  In an ideal world, you'd have ISDN desk-sets in front of every
POTS user, but I don't hear anyone suggesting that.

    > Let me tell the experience with the VoiceIP deployment...
    > None of [the RFP-respondents] wanted to guarantee end-to-end High
    > Availability of 99.999

That's not deployment experience, that's you talking to a salesperson.
Which has exactly nothing to do with networks or operational reality, or
voice quality.

    > They said the max they could provide was 99.9

Okay, hypothetically, let's say they really are as bad as the worst that
they were actually willing to guarantee in writing.  If they lose one
packet in a thousand, do you really think that VoIP will fall apart at the
seams?  Do you think that'll even have an effect which could be measured
in the lab?  Much less noticed by happy users?  VoIP seems to me to work
pretty darned well at 96%-97%.

    > ATM for transport

Ouch.  Yeah, well, if you actually did build the network and had problems,
there's your source.  Fortunately the Internet hasn't used any significant
quantity of ATM since it was deprecated a few years ago.

    > NCS has to deal with many ISPs to address this issue
    > in order to get ubiquitous.

Yes, tens of thousands.  I'm still having a bit of a hard time with the
notion that NCS really wants to enter into and manage SLA contracts with
tens of thousands of ISPs.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:08:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08747
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:08:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACIAvL18885
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:10:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIAvv18882
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:10:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08722
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:08:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACI0mv17819;
	Tue, 12 Nov 2002 13:00:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACHxev17698
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 12:59:40 -0500
Received: from imo-m03.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08286
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 12:57:01 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m03.mx.aol.com (mail_out_v34.13.) id j.36.31374b7d (4262);
	Tue, 12 Nov 2002 12:59:01 -0500 (EST)
Message-ID: <36.31374b7d.2b029b64@aol.com>
Date: Tue, 12 Nov 2002 12:59:00 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: rja@extremenetworks.com
CC: woody@pch.net, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_36.31374b7d.2b029b64_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_36.31374b7d.2b029b64_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/11/2002 5:43:53 PM Eastern Standard Time, 
rja@extremenetworks.com writes:

So your real requirement is that the specs *not preclude* a carrier from 
billing,
not that the specs *support* billing.

[MAP] My requirement is that the specs "allow" a carrier to keep records 
related to individual calls by providing the necessary functionality. It does 
not address "billng", since I don't care what they do with the detailed call 
records.

But please don't increase the capital costs for all carriers just so that NCS,
which is NOT a carrier at all, can be happy that it changed the Internet 
architecture.

[MAP] I guess if NCS feels that accounting is required in order to administer 
GETS, then the added cost to the carriers will be part of what NCS pays to 
get the service. And if it costs too much, then that will be one more reason 
for not using IP as the transport for regular voice service.

Yes, this might increase the capital costs for any carrier that wants to 
support this customer (NCS), just as many other capabilites might. So what is 
so different about this one?

But, I am also arguing this point in support of DISA, which is the operator 
of a large network, which may one day migrate to supporting voice over IP 
(although I'm beginning to think that is a long way off!)

Mike Pierce
Artel


--part1_36.31374b7d.2b029b64_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/11/2002 5:43:53 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>So your real requirement is that the specs *not preclude* a carrier from billing,
<BR>not that the specs *support* billing.
<BR>
<BR>[MAP] My requirement is that the specs "allow" a carrier to keep records related to individual calls by providing the necessary functionality. It does not address "billng", since I don't care what they do with the detailed call records.
<BR>
<BR>But please don't increase the capital costs for all carriers just so that NCS,
<BR>which is NOT a carrier at all, can be happy that it changed the Internet architecture.
<BR>
<BR>[MAP] I guess if NCS feels that accounting is required in order to administer GETS, then the added cost to the carriers will be part of what NCS pays to get the service. And if it costs too much, then that will be one more reason for not using IP as the transport for regular voice service.
<BR>
<BR>Yes, this might increase the capital costs for any carrier that wants to support this customer (NCS), just as many other capabilites might. So what is so different about this one?
<BR>
<BR>But, I am also arguing this point in support of DISA, which is the operator of a large network, which may one day migrate to supporting voice over IP (although I'm beginning to think that is a long way off!)
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_36.31374b7d.2b029b64_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:09:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08781
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:09:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACIBbr18929
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:11:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIBbv18926
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:11:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08761
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:09:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACI81v18736;
	Tue, 12 Nov 2002 13:08:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACI7Tv18641
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:07:29 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08603
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 13:04:52 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACI0Ud02585;
	Tue, 12 Nov 2002 10:00:30 -0800 (PST)
Date: Tue, 12 Nov 2002 10:00:30 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: jmpolk@cisco.com, <ieprep@ietf.org>
Subject: Re: [Ieprep] Requirements for Accounting
In-Reply-To: <ac.30f90393.2b029b51@aol.com>
Message-ID: <Pine.GSO.4.44.0211120958550.857-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    >>> If "Accounting" or "X" or "Y" is included in the IEPREP doc as a
    >>> "requirement", it only means that some other WG must figure out a
    >>> way to support it.                              ^^^^
    >> No, it _most certainly does not_ mean that.

    > As Scott wrote on Oct 14:
    > the primary task on the WG's plate right now is to come to consensus
    > on a requirements document to be forwarded to the sipping working group

Do you really not see the (underlined for your convenience) difference
between these two statements?

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:13:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09029
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:13:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACIG3d19267
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:16:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIG3v19264
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:16:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09014
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:13:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIF2v19224;
	Tue, 12 Nov 2002 13:15:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIEGv19154
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:14:16 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08884
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 13:11:39 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACI8Cd02729;
	Tue, 12 Nov 2002 10:08:12 -0800 (PST)
Date: Tue, 12 Nov 2002 10:08:12 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: rja@extremenetworks.com, <ieprep@ietf.org>
Subject: Re: [Ieprep] Atlanta ieprep Agenda
In-Reply-To: <36.31374b7d.2b029b64@aol.com>
Message-ID: <Pine.GSO.4.44.0211121006260.857-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002 Mpierce1@aol.com wrote:
    > [MAP] My requirement is that the specs "allow" a carrier to keep records
    > related to individual calls by providing the necessary functionality. It does
    > not address "billng", since I don't care what they do with the detailed call
    > records.

You might also take care to make clear that you're not asking for
functionality which would support carriers performing accounting on this
traffic, but instead for functionality which would support proxy operators
performing accounting, which already exists and is uncontroversial.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:16:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09109
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:16:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACII8419368
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:18:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACII8v19365
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:18:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09101
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:15:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIH1v19318;
	Tue, 12 Nov 2002 13:17:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIGSv19290
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:16:28 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA09026
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 13:13:51 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 12 Nov 2002 18:13:56 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WYQLGM0D>; Tue, 12 Nov 2002 13:17:35 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D23A4BA@emshqs1.ncr.disa.mil>
From: "Folts, Harold" <foltsh@ncs.gov>
To: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>
Cc: "'ieprep'" <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: more process discussion
Date: Tue, 12 Nov 2002 13:16:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> -----Original Message-----
> From: King, Kimberly S. [mailto:KIMBERLY.S.KING@saic.com]
> Sent: Tuesday, November 12, 2002 12:17 PM
> To: 'Folts, Harold'; 'RJ Atkinson'
> Cc: 'ieprep'
> Subject: RE: [Ieprep] Re: more process discussion
> 
> 
> You made a point of twice stating "FUTURE networks".  It 
> might be worth
> elaborating what you mean by this.
> 

I am not interested in addressing today's PSTN. It provides a very good
service in the US and other countries for emergency and disaster relief
operations. 

The Internet technology offers an excellent protential to support emergency
communications in times of disaster. With the Internet being widely
available and also with the Internet technology being integrated into public
telecommunication networks in the future, there is a good opportunity to
leverage these capabilies for use in emergency and disaster relief
operations for the benefit of the public at large.

Therefore, I an seeking to bring technical provisions into Internet
technology that will provide highly reliable and available communication
capabilities in times of serious disaster and limited bandwidth.

The only issue that I see with the PSTN is the need for an interface with
some IP-based networks to pass telephony traffic. The more important issue
is to have the capability using IP technology to convey any type of
communication (not just voice) that would be beneficial to disaster relief.

Hal
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:19:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09170
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:19:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACIL9T19601
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:21:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIL9v19598
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:21:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09156
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:18:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACII4v19357;
	Tue, 12 Nov 2002 13:18:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIHqv19338
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:17:52 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09074
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 13:15:14 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACIBjd02823;
	Tue, 12 Nov 2002 10:11:45 -0800 (PST)
Date: Tue, 12 Nov 2002 10:11:45 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: JOHN.J.GARRITY@saic.com, <K.Carlberg@cs.ucl.ac.uk>, <ieprep@ietf.org>
Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-Reply-To: <102.1ea27f49.2b029b45@aol.com>
Message-ID: <Pine.GSO.4.44.0211121009130.857-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002 Mpierce1@aol.com wrote:
    > The math above that arrives at 70% and 4% is really not significant. The
    > orginating (85%) and terminating (85%) are distinct parts of the capabilities
    > desired. They are not both required to do anything. The calculation of .85 x
    > .85 = .70 only tells you what percentage of the calls get both the
    > originating exchange and the terminating exchange functionality. It's still
    > true that 85% of calls get each, and 97.75% get one or the other.

Uh, sorry, you're making my head hurt.  Could you slow down and explain
that one?  If 85% of the endpoints are covered, then 70% of calls have two
covered endpoints, not 85%, and 85% != 97.75% last I checked.  What am I
missing?

    > NCS can purchase GETS-like services from any number of carriers that offer it.

That's a ludicrous claim on the face of it.  Perhaps you'd care to
moderate it somewhat.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:21:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09273
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:21:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACINvt19725
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:23:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACINvv19722
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:23:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09236
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:21:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIN1v19690;
	Tue, 12 Nov 2002 13:23:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIMqv19676
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:22:52 -0500
Received: from imo-m10.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09205
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 13:20:16 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m10.mx.aol.com (mail_out_v34.13.) id b.159.175d2c40 (4262);
	Tue, 12 Nov 2002 13:20:49 -0500 (EST)
Message-ID: <159.175d2c40.2b02a081@aol.com>
Date: Tue, 12 Nov 2002 13:20:49 EST
Subject: Re: [Ieprep] Requirements for Accounting
To: woody@pch.net
CC: jmpolk@cisco.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_159.175d2c40.2b02a081_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_159.175d2c40.2b02a081_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/12/2002 3:33:59 AM Eastern Standard Time, woody@pch.net 
writes:


>       On Mon, 11 Nov 2002 Mpierce1@aol.com wrote:
>     > I have seen your point from the very beginning, that you don't want to
>     > be told what you must do in your network.
> 
> No, that's not my point at all.  It's irrelevant what other people say
> about what I must do in my network, since what I must do, I will perforce
> do anyway.  The problem is when someone else _wants_ me to do something
> that I don't need to do, and attempts to _require_ me to do it.
> 


[MAP] Could someone else please explain to me what the difference is between 
my statement above, and Woody's interpretation of it and his final statement? 
I'm at a loss to understand what this disagreement is.

Mike Pierce
Artel


--part1_159.175d2c40.2b02a081_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/12/2002 3:33:59 AM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;On Mon, 11 Nov 2002 Mpierce1@aol.com wrote:
<BR> &nbsp;&nbsp;&nbsp;&gt; I have seen your point from the very beginning, that you don't want to
<BR> &nbsp;&nbsp;&nbsp;&gt; be told what you must do in your network.
<BR>
<BR>No, that's not my point at all. &nbsp;It's irrelevant what other people say
<BR>about what I must do in my network, since what I must do, I will perforce
<BR>do anyway. &nbsp;The problem is when someone else _wants_ me to do something
<BR>that I don't need to do, and attempts to _require_ me to do it.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] Could someone else please explain to me what the difference is between my statement above, and Woody's interpretation of it and his final statement? I'm at a loss to understand what this disagreement is.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_159.175d2c40.2b02a081_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:25:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09369
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:25:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACIRDf19892
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:27:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIRDv19889
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:27:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09360
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:24:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIM1v19656;
	Tue, 12 Nov 2002 13:22:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACILcv19636
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:21:38 -0500
Received: from imo-m06.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09168
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 13:19:01 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m06.mx.aol.com (mail_out_v34.13.) id j.73.28f59bd3 (4262);
	Tue, 12 Nov 2002 13:20:07 -0500 (EST)
Message-ID: <73.28f59bd3.2b02a057@aol.com>
Date: Tue, 12 Nov 2002 13:20:07 EST
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach, etc.
To: rja@extremenetworks.com
CC: nguyena@ncs.gov, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_73.28f59bd3.2b02a057_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_73.28f59bd3.2b02a057_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/11/2002 5:40:15 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> On Monday, Nov 11, 2002, at 14:00 America/Montreal, Mpierce1@aol.com 
> wrote:
> > That's why I used the term "preferential treatment" in my drafts, and 
> > only give "prioritisation" as an example of how "preferential 
> > treatment" may be provided. Examples of "prioritisation" (in the sense 
> > of handling one thing in front of something else) would be a device 
> > that queues new call attempts and processes them in a priority order 
> > as resources become available.
> 
> A major issue with even that is that it isn't the functional need of GETS or
> NCS.  The functional need is to get the emergency calls through.  If an ISP
> can do that with only "best effort" and explicitly no support for 
> "preferential
> treatment", the ISP has met the need completely.  If one talks about 
> "preferential
> treatment" then by definition it means the ISP is offering something other 
> than
> pure "best effort" service, so even that gets down into mechanism somewhat
> (though it is fuzzy about which mechanism(s) provide the "preferential 
> treatment").
> 
> So there are still issues with that wording and that conceptual approach.
> 



[MAP] The only "issue" I was raising/commenting on with the above was that we 
should not use the term "prioritization" when we are talking about what 
should be a more generic requirement. Everyone has been correct from the 
beginning that strict "prioritization" of anything (packets, call setup, etc) 
is not a requirement, but rather a possible way to provide "preferenetial 
treatment" for high "priority" calls.

Yes, it is a functional requirement of GETS to provide preferential treatment 
in the case of congestion. The drafts have made this point that it only 
applies if there is congestion. So, if a network can guarantee no congestion, 
that it clearly has no need for any preferential treatment mechanisms.

(I'd like to see a carrier guarantee "no congestion" in a contract with the 
government for GETS!)


Mike Pierce
Artel


--part1_73.28f59bd3.2b02a057_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/11/2002 5:40:15 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">On Monday, Nov 11, 2002, at 14:00 America/Montreal, Mpierce1@aol.com 
<BR>wrote:
<BR>&gt; That's why I used the term "preferential treatment" in my drafts, and 
<BR>&gt; only give "prioritisation" as an example of how "preferential 
<BR>&gt; treatment" may be provided. Examples of "prioritisation" (in the sense 
<BR>&gt; of handling one thing in front of something else) would be a device 
<BR>&gt; that queues new call attempts and processes them in a priority order 
<BR>&gt; as resources become available.
<BR>
<BR>A major issue with even that is that it isn't the functional need of GETS or
<BR>NCS. &nbsp;The functional need is to get the emergency calls through. &nbsp;If an ISP
<BR>can do that with only "best effort" and explicitly no support for "preferential
<BR>treatment", the ISP has met the need completely. &nbsp;If one talks about "preferential
<BR>treatment" then by definition it means the ISP is offering something other than
<BR>pure "best effort" service, so even that gets down into mechanism somewhat
<BR>(though it is fuzzy about which mechanism(s) provide the "preferential treatment").
<BR>
<BR>So there are still issues with that wording and that conceptual approach.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>
<BR>[MAP] The only "issue" I was raising/commenting on with the above was that we should not use the term "prioritization" when we are talking about what should be a more generic requirement. Everyone has been correct from the beginning that strict "prioritization" of anything (packets, call setup, etc) is not a requirement, but rather a possible way to provide "preferenetial treatment" for high "priority" calls.
<BR>
<BR>Yes, it is a functional requirement of GETS to provide preferential treatment in the case of congestion. The drafts have made this point that it only applies if there is congestion. So, if a network can guarantee no congestion, that it clearly has no need for any preferential treatment mechanisms.
<BR>
<BR>(I'd like to see a carrier guarantee "no congestion" in a contract with the government for GETS!)
<BR>
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_73.28f59bd3.2b02a057_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:29:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09571
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:29:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACIW4G20084
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:32:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIW4v20081
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:32:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09526
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:29:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIV2v20030;
	Tue, 12 Nov 2002 13:31:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIUov19993
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:30:50 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09494
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 13:28:12 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACIOAd03086;
	Tue, 12 Nov 2002 10:24:10 -0800 (PST)
Date: Tue, 12 Nov 2002 10:24:10 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: rja@extremenetworks.com, <nguyena@ncs.gov>, <ieprep@ietf.org>
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach,
 etc.
In-Reply-To: <73.28f59bd3.2b02a057@aol.com>
Message-ID: <Pine.GSO.4.44.0211121022530.857-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002 Mpierce1@aol.com wrote:
    > (I'd like to see a carrier guarantee "no congestion" in a contract with the
    > government for GETS!)

I think we can do that just as soon as one of you channel-switched guys
defines "congestion."  Anybody care to step up to the plate, since that
appears to be prerequisite to the rest of the conversation?

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:30:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09587
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:30:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACIWFH20099
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:32:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIWFv20096
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:32:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09530
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:29:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIP2v19819;
	Tue, 12 Nov 2002 13:25:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIO1v19741
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:24:01 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09241
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 13:21:23 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACIHud02986;
	Tue, 12 Nov 2002 10:17:56 -0800 (PST)
Date: Tue, 12 Nov 2002 10:17:56 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Folts, Harold" <foltsh@ncs.gov>
cc: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        "'ieprep'" <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: more process discussion
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D23A4BA@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211121016060.857-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002, Folts, Harold wrote:
    > The Internet technology offers an excellent protential to support
    > emergency communications in times of disaster.

Uh, this isn't "potential," this is actual fact.  The question at hand is
whether there's a problem that needs to be fixed.  Is there a problem
which needs to be fixed?  If so, can you articulate it, quantify it, and
describe the process you went through to discover and identify it?

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 13:47:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10035
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 13:47:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACInrs21250
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 13:49:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACInrv21247
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 13:49:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10018
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 13:47:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIn8v21224;
	Tue, 12 Nov 2002 13:49:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACIm1v21189
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 13:48:01 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09974
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 13:45:23 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Tue, 12 Nov 2002 13:47:34 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111213473930480
 ; Tue, 12 Nov 2002 13:47:39 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WYJVRLVR>; Tue, 12 Nov 2002 13:49:00 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E7795F@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, woody@pch.net
Cc: jmpolk@cisco.com, ieprep@ietf.org
Subject: RE: [Ieprep] Requirements for Accounting
Date: Tue, 12 Nov 2002 13:47:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C28A7B.F886CEB0"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C28A7B.F886CEB0
Content-Type: text/plain;
	charset="ISO-8859-1"

Mike,
 

In a message dated 11/12/2002 3:33:59 AM Eastern Standard Time,
woody@pch.net writes: 




     On Mon, 11 Nov 2002 Mpierce1@aol.com wrote: 
   > I have seen your point from the very beginning, that you don't want to 
   > be told what you must do in your network. 

No, that's not my point at all.  It's irrelevant what other people say 
about what I must do in my network, since what I must do, I will perforce 
do anyway.  The problem is when someone else _wants_ me to do something 
that I don't need to do, and attempts to _require_ me to do it. 





[MAP] Could someone else please explain to me what the difference is between
my statement above, and Woody's interpretation of it and his final
statement? I'm at a loss to understand what this disagreement is.   
 
I believe Bill doesn't care what people "say" about what he must do but
rather what they "require" him to do.  One is desire potentially without
anything to enforce the want and the other is mandated.
 
This is a consistent theme and it appears to be reaching resolution on the
list.  (Correct me if I'm wrong.)  Network operators have expressed concerns
that ieprep would appear as requirements to the Internet community.
Meanwhile, the draft authors such as Ken Carlberg have expressed that they
will modify the drafts to explicitly point out ieprep "services" exist, if
they exist, due to a business contract relationship.
 
Ken:  "Rather, we wanted to 
reinforce the notion that if a service is available it is because
a business contract in some form exists -- ie, there is no such thing
as a free lunch.  Having stated that, we can make another pass at 
trying to further clarify this intent."
 
Kimberly
 
 

------_=_NextPart_001_01C28A7B.F886CEB0
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">


<META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Tahoma size=2><SPAN 
class=968424118-12112002>Mike,</SPAN></FONT></DIV>
<DIV><FONT face=Tahoma size=2><SPAN 
class=968424118-12112002></SPAN></FONT>&nbsp;</DIV><FONT face=Tahoma 
size=2><SPAN class=968424118-12112002>
<DIV><BR><FONT face=Arial>In a message dated 11/12/2002 3:33:59 AM Eastern 
Standard Time, woody@pch.net writes: <BR><BR><BR></FONT>
<BLOCKQUOTE 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px" 
TYPE="CITE">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;On Mon, 11 Nov 2002 Mpierce1@aol.com 
  wrote: <BR>&nbsp;&nbsp;&nbsp;&gt; I have seen your point from the very 
  beginning, that you don't want to <BR>&nbsp;&nbsp;&nbsp;&gt; be told what you 
  must do in your network. <BR><BR>No, that's not my point at all. &nbsp;It's 
  irrelevant what other people say <BR>about what I must do in my network, since 
  what I must do, I will perforce <BR>do anyway. &nbsp;The problem is when 
  someone else _wants_ me to do something <BR>that I don't need to do, and 
  attempts to _require_ me to do it. <BR><FONT lang=0 face=Arial size=3 
  FAMILY="SANSSERIF"></BLOCKQUOTE>
<DIV><BR></FONT><FONT lang=0 face=Arial size=2 FAMILY="SANSSERIF"><BR><BR>[MAP] 
Could someone else please explain to me what the difference is between my 
statement above, and Woody's interpretation of it and his final statement? I'm 
at a loss to understand what this disagreement is.&nbsp;</FONT><FONT lang=0 
face=Arial size=2 FAMILY="SANSSERIF"><SPAN 
class=968424118-12112002>&nbsp;</SPAN></FONT><FONT lang=0 face=Arial size=2 
FAMILY="SANSSERIF"><SPAN 
class=968424118-12112002>&nbsp;</SPAN></FONT></DIV></DIV>
<DIV><FONT lang=0 face=Arial size=2 FAMILY="SANSSERIF"><SPAN 
class=968424118-12112002></SPAN></FONT></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Tahoma size=2><SPAN class=968424118-12112002>
<DIV><FONT lang=0 face=Arial size=2 FAMILY="SANSSERIF"><SPAN 
class=968424118-12112002><EM><FONT face="Times New Roman" color=#0000ff size=3>I 
believe&nbsp;Bill doesn't care what people "say" about what he must do but 
rather what they "require" him to do.&nbsp; One is desire potentially without 
anything to enforce the want and the other is 
mandated.</FONT></EM></SPAN></FONT></DIV>
<DIV><FONT lang=0 face="Times New Roman" color=#0000ff size=3 
FAMILY="SANSSERIF"><SPAN 
class=968424118-12112002><EM></EM></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT lang=0 face="Times New Roman" color=#0000ff size=3 
FAMILY="SANSSERIF"><SPAN class=968424118-12112002><EM>This&nbsp;is a consistent 
theme and it appears to be reaching resolution on the list.&nbsp; (Correct me if 
I'm wrong.)&nbsp; Network operators have expressed concerns that ieprep would 
appear as requirements to the Internet community.&nbsp; Meanwhile, the draft 
authors such as Ken Carlberg have expressed that they will modify the drafts to 
explicitly point out ieprep "services" exist, if they exist,&nbsp;due to a 
business contract relationship.</EM></SPAN></FONT></DIV>
<DIV><FONT lang=0 face="Times New Roman" color=#0000ff size=3 
FAMILY="SANSSERIF"><SPAN 
class=968424118-12112002><EM></EM></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT lang=0 face="Times New Roman" color=#0000ff size=3 
FAMILY="SANSSERIF"><SPAN class=968424118-12112002><EM>Ken:&nbsp; "</EM><FONT 
color=#000000>Rather, we wanted to <BR>reinforce the notion that if a service is 
available it is because<BR>a business contract in some form exists -- ie, there 
is no such thing<BR>as a free lunch.&nbsp; Having stated that, we can make 
another pass at <BR>trying to further clarify this 
intent.</FONT><EM>"</EM></SPAN></FONT></DIV>
<DIV><FONT lang=0 face=Arial size=2 FAMILY="SANSSERIF"><SPAN 
class=968424118-12112002><EM><FONT face="Times New Roman" color=#0000ff 
size=3></FONT></EM></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT lang=0 face=Arial size=2 FAMILY="SANSSERIF"><SPAN 
class=968424118-12112002><EM><FONT face="Times New Roman" color=#0000ff 
size=3>Kimberly</FONT></EM></SPAN></FONT></DIV>
<DIV><FONT lang=0 face=Arial size=2 FAMILY="SANSSERIF"><SPAN 
class=968424118-12112002><EM><FONT face="Times New Roman" color=#0000ff 
size=3></FONT></EM></SPAN></FONT>&nbsp;</DIV>
<DIV><EM><FONT face="Times New Roman" color=#0000ff 
size=3></FONT></EM></SPAN></FONT><FONT face=arial,helvetica><FONT lang=0 
face=Arial size=2 FAMILY="SANSSERIF"><SPAN class=968424118-12112002><EM><FONT 
face="Times New Roman" color=#0000ff 
size=3></FONT></EM></SPAN>&nbsp;</DIV></DIV></FONT></FONT></BODY></HTML>

------_=_NextPart_001_01C28A7B.F886CEB0--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 14:23:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11146
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 14:23:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACJQ0c23325
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 14:26:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACJQ0v23322
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 14:26:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11087
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 14:23:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACJPCv23250;
	Tue, 12 Nov 2002 14:25:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACJKdv23056
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 14:20:39 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10845
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 14:18:00 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Tue, 12 Nov 2002 11:17:15 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gACJIDb9015488;
	Tue, 12 Nov 2002 11:18:13 -0800 (PST)
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
From: Rex Buddenberg <budden@nps.navy.mil>
To: "Garrity, Jack" <JOHN.J.GARRITY@saic.com>
Cc: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>, "'ieprep'" <ieprep@ietf.org>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64231E539@mcl-its-exs01>
References: <B8030EB94AF1D51196D70002A589D64231E539@mcl-its-exs01>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 12 Nov 2002 11:16:13 -0800
Message-Id: <1037128573.1095.383.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Any real world emergency services operation will be transiting multiple
ISPs -- especially counting the local (likely at both ends)
infrastructure where my EMS outfit is its own ISP.  

Consider a municipal fire/police lashup: I have a command center in the
fire department dispatching office that has a LAN with workstations on
it -- situation awareness and command & control is the name of the
game.  Either in-band or out-of-band is a means of in-access for the
public (such as 911 relay).  Being sensible and reading the yet-to-be
drafted BCPs from IEPREP, I make my network redundant (no single points
of failure) and I preserve the connectionless IP layer (making reliable
crossover work).  And I have both an SNMP management system in place to
detect failures as they occur and a trouble ticket system to track
them.  There, I've met the three principles of high availability
engineering.
	Secondly, I've provisioned the police department across town the same
way so I have a backup command center.  

At the router(s), I meet the commercial ISP.  The first thing I want is
diverse paths between the two command centers to complete that high Ao
exercise.  How do I spec that?  In this case, high Ao would probably
trump any QoS requirements -- by the time you meet the Ao needs we have
overprovisioned and Bill W's comments apply.  And this is the analogy
that, I think, Ran is fishing for.  [??]

Now in order to do the fire/police department's emergency services work,
I need to reach my mobile platforms -- in particular the deployed
engines.  To get there, I have my ISP provide wireless POPs around town
(heaven forbid that they be for my exclusive use -- my taxpayers don't
have that kind of money.  Besides, I want the stuff used daily so we all
know how ... not just in emergencies).  The terrestrial WAN can again be
easily overprovisioned.

But now we get to the squeeze.  Off the wireless POPs, I'm running radio
circuits and they are orders of magnitude less bandwidth than everything
I've described so far.  Overprovisioning also gets problematic -- there
are very few offsets.  And, as the adage goes, God only made so much
spectrum (there are a lot of good propagation reasons to stay in the
low-band VHF part of the spectrum where EMS has traditionally been --
but not a lot of capacity there).  
	Exactly how I arrange my priority service need not be visible to my
municipal ISP.  Let's assume I use some kind of diff-serv arrangement --
what's important is that the ISP not mangle the DSCP by routers enroute
to and from my enclaves attached to that ISP's net.  Diff-serv here is a
good example because it addresses per hop behaviors.  My ISP already
Does the Right Thing over his segment, so let's not pay tax money to
overkill that part -- I'm particularly interested in the radio-WAN per
hop behavior where certain traffic needs precedence over other.  
	For example, I may be running a video feed for situation awareness
(e.g. a web-cam mounted on the fire engine) and this data may be relayed
to the press.  I may be running medical telemetry from the EMTs to the
hospital as they work an injury.  And I may be running a scene-leader
<--> command center voice discussion.  These applications bear different
QoS needs TO MY LOCAL parts of the internet but not to my ISP because
he's more than met them through the overprov.  


On Tue, 2002-11-12 at 01:59, Ken Carlberg wrote:

> 
> we've talked about this a few weeks ago.  the IEPREP is a rather 
> different group than the others within the IETF in both the wide 
> variety of backgrounds participating, and those that will be reading
> the documents produced by it.  normally, I would agree that there is
> no need to make any extra strong statement that IETF documents are not
to 
> be confused as mandates that must be followed by the comunity or
vendors.
> however, I think its important to take into account non-technical
folks,
> and more importantly people unfamiliar with the IETF, and go the extra
> mile to point out things.  this also means being a bit more
descriptive
> than normal in drafts to make sure all technical participants
understand 
> whats being accomplished.
> 
In this respect, we probably ought to look farther than the
protocol-only IETF view.  The problems we're trying to tangle with have
to do with provisioning, policy, and practices as much as they do with
protocols.  We can't mean ANY of the Ao, security, QoS control or reach
to mobile platforms without attention to all.  


On Tue, 2002-11-12 at 04:47, Garrity, Jack wrote:
> Ken,
> 
> ADDENDUM
> 
> Some suggested that I add the point that the transit carriers, local
> exchange carriers and interexchange carriers, are paid for providing the
> NS/EP services. 
> 
> ~~~ Jack ~~~
> Work: 703/676-2358 | Fax: 703/848-0299
> Home: 703/278-9250 | Cell: 703/508-0065
> E-mail: garrityj@saic.com
> 
> 
> -----Original Message-----
> From: Garrity, Jack 
> Sent: Tuesday, November 12, 2002 7:41 AM
> To: 'Ken Carlberg'
> Cc: ieprep
> Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion
> request
> 
> 
> Ken,
> 
> For the scenario you describe, the NS/EP codepoint and NS/EP features take
> effect at GETS-capable local exchanges.  Those exchanges serve over X
> percent of US-based access lines, where X is on the order of 85 percent or
> greater.
> 
> Once the call reaches a GETS-capable local exchange or a GETS interexchange
> carrier, the NS/EP treatment is carried through to the terminating local
> exchanges.  If the terminating local exchange is GETS-capable (same switches
> as in the first paragraph), NS/EP features have effect.
> 
> I won't guarantee this description entirely.  If this description suffices,
> I'll be ready to try to evaluate the content in your original message.
> 
> ~~~ Jack ~~~
> Work: 703/676-2358 | Fax: 703/848-0299
> Home: 703/278-9250 | Cell: 703/508-0065
> E-mail: garrityj@saic.com
> 
> 
> -----Original Message-----
> From: Ken Carlberg [mailto:K.Carlberg@cs.ucl.ac.uk]
> Sent: Tuesday, November 12, 2002 7:29 AM
> To: Garrity, Jack
> Cc: ieprep
> Subject: Re: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion
> request
> 
> 
> 
> > I'll try to evaluate your message content after you expand a bit on your
> > statement about "the current GETS system doesn't offer any special service
> > within a land-line exchange."  
> 
> by this I meant that if one were to make a 'local' call within a LEC 
> (eg, Brooklyn NY, to Manhattan NY), the NS/EP code point and HPC
> services don't take effect until the call signaling goes from the 
> origin LEC to the IXC.  further, that the NS/EP call doesn't extend
> to the destination end-office.  so things like extended trunk queuing
> is not done along the entire path between the originator and the 
> destination in the US PSTN.  have I got that right?
> 
> -ken
> 
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 14:48:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11762
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 14:48:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACJoqg24975
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 14:50:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACJoqv24972
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 14:50:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11738
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 14:48:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACJo4v24909;
	Tue, 12 Nov 2002 14:50:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACJnEv24864
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 14:49:14 -0500
Received: from volta.tazznetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11708
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 14:46:36 -0500 (EST)
Received: from volta.tazznetworks.com (localhost.tazznetworks.com [127.0.0.1])
	by volta.tazznetworks.com (8.12.6/8.12.3) with ESMTP id gACJksgf000678;
	Tue, 12 Nov 2002 14:46:54 -0500 (EST)
	(envelope-from idb@volta.tazznetworks.com)
Message-Id: <200211121946.gACJksgf000678@volta.tazznetworks.com>
To: Bill Woodcock <woody@pch.net>
cc: Mpierce1@aol.com, rja@extremenetworks.com, nguyena@ncs.gov,
        ieprep@ietf.org
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach, etc. 
In-Reply-To: Your message of "Tue, 12 Nov 2002 10:24:10 PST."
             <Pine.GSO.4.44.0211121022530.857-100000@paixhost.pch.net> 
User-Agent: EMH/1.10.0 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?UTF-8?B?VW5l?=
 =?UTF-8?B?Ymlnb3J58m1hZQ==?=) APEL/10.3 Emacs/21.2 (i386--freebsd) (with
 unibyte mode)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
X-Mailer: mh-e 6.1; nmh 1.0.4; Emacs 21.2
Date: Tue, 12 Nov 2002 14:46:54 -0500
From: Dean <idb@tazznetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

I believe that congestion can be defined pretty good for VoIP
Two years ago I was working for a VoIP vendor and when we were
implementing the system, this 3 parameters were used to define network
congestion. 

1. packet drop rate 
different vocoders have different treshold, but in general
more then 3% of packetloss, the voice conversation is becomming pretty
not understandable.

2. latency - should be lower then 150ms one way. If it is higher, the
echo cancelation algorythms can not do the work

3. jitter ideally should be 0, but up to 60 msec can be tolerated.

Also, the main problem in implenting VoIP GETS-like services will be
in access not on the backbone.

So far I have not seen much talk about access side. From experience I
can say, when the access was resolved the backbone was comming along
with no problem.

So Bill
you might be right that now VoIP traffic is insignificant, but lets
say there is a disaster and lot of people are trying to reach friends
and realtives from the disaster site, can you image what will happen
on the access loops near the site (inbound and outbound)? And now the
emergency workers need access too. How can we guaranty that?

I believe that this group has to take worst case scenarios and
try to come up with requirements for such cases.


Dean
idb@tazznetworks.com

===============================================
I like to share my ignorance. I have it enough.


>       On Tue, 12 Nov 2002 Mpierce1@aol.com wrote:
>     > (I'd like to see a carrier guarantee "no congestion" in a contract with
>  the
>     > government for GETS!)
> 
> I think we can do that just as soon as one of you channel-switched guys
> defines "congestion."  Anybody care to step up to the plate, since that
> appears to be prerequisite to the rest of the conversation?
> 
>                                 -Bill
> 
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 15:20:13 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13422
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 15:20:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACKMKT27060
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 15:22:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKMKv27057
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 15:22:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13414
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 15:19:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKL5v27003;
	Tue, 12 Nov 2002 15:21:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKKgv26987
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 15:20:42 -0500
Received: from seahorse.shentel.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13374
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 15:18:03 -0500 (EST)
Received: from steves (ha30s474.d.shentel.net [204.111.30.218])
	by seahorse.shentel.net (8.11.6/8.11.6) with SMTP id gACKKYM11883;
	Tue, 12 Nov 2002 15:20:34 -0500
From: "Steve Silverman" <steves@shentel.net>
To: <ieprep@ietf.org>
Cc: <jmpolk@cisco.com>, "Bill Woodcock" <woody@pch.net>, <Mpierce1@aol.com>
Subject: RE: [Ieprep] Requirements for Accounting
Date: Tue, 12 Nov 2002 15:20:35 -0500
Message-ID: <KMEJKAPHBBCMCDDGMBLOMEDFCAAA.steves@shentel.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <Pine.GSO.4.44.0211120958550.857-100000@paixhost.pch.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Perhaps instead of accounting, we should call it call tracking?  (I don't
think the name is very important.) Would this be more acceptable to some
people?

I don't think that charging users for emergency calls is projected to become
a major source of income for any SP.
I would like to avoid the situation in which more money is spent billing
users than providing the desired service.

I view this as a requirement to track who uses a service especially in the
light of the recent DDOS attack with enough info to identify users
(especially those who make major demands).
Even if some network does not want to defend itself, I think we should
provide a mechanism so that a network CAN
protect itself from such attacks.  (I don't think any SP would deploy a
defenseless network in the future.)
I believe that this function requires that enough records be kept so that
some diagnostic work can be done after the fact. It seems as though the
world is becoming a nastier place and in such an environment, too much trust
does not work very well.

Steve Silverman


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 15:24:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13578
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 15:24:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACKQlt27268
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 15:26:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKQlv27265
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 15:26:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13560
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 15:24:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKQ8v27253;
	Tue, 12 Nov 2002 15:26:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKPWv27216
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 15:25:32 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13541
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 15:22:52 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACKI9d05839;
	Tue, 12 Nov 2002 12:18:09 -0800 (PST)
Date: Tue, 12 Nov 2002 12:18:09 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Dean <idb@tazznetworks.com>
cc: Mpierce1@aol.com, <rja@extremenetworks.com>, <nguyena@ncs.gov>,
        <ieprep@ietf.org>
Subject: Re: [Ieprep] network congestion, VoIP, NCS contracting approach,
 etc. 
In-Reply-To: <200211121946.gACJksgf000678@volta.tazznetworks.com>
Message-ID: <Pine.GSO.4.44.0211121156150.857-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002, Dean wrote:
    > 1. packet drop rate different vocoders have different treshold, but in general
    > more then 3% of packetloss, the voice conversation is becomming pretty
    > not understandable.

Okay, so 97% packet delivery is a pretty easy target to hit, no problem to
be solved there, that I see.

    > 2. latency - should be lower then 150ms one way. If it is higher,
    > the echo cancelation algorythms can not do the work

Well, us ISPs have been asking for faster light for quite a while now, but
the ITU just hasn't delivered it yet.  I'm not sure that's something we
want to start trying to standardize in the IETF, though...  There'd be too
much argument.  Besides, that's down at layer 1.  :-)

I guess in my experience higher latency has certainly been noticable, but
less so than on the PSTN, since you don't get shoved across satellite
links quite so frequently, it seems like, and the latency isn't quite as
annoying if it's not accompanied by lousy sound quality.  300ms is
certainly tolerable, though obviously increasingly weird.

    > lets say there is a disaster and lot of people are trying to reach
    > friends and realtives from the disaster site, can you image what
    > will happen on the access loops near the site?

Yep.  They may go from single-digit utilization percentages to
double-digit utilization.  Thereby better amortizing their Internet
service fees.  What's being postulated here isn't problematic.  Let's say
that a company has a thousand employees sitting in an office.  Their old
circuit-switched PBX-raised voice services manager says "Ah ha!  If we
have a thousand users, that means we need to be able to support 120
simultaneous conversations, and as everyone knows, a conversation is
64kbps!  Therefore, I will REQUIRE that the Internet service group
MUST give me 7.68mbps capacity for MY EXCLUSIVE HIGH PRIORITY use, and
mark everyone else's packets with a special header which denotes
insignificance, lowliness, and fecklessness."  The Internet service
manager would then receive this report, make a snide joke to her
underlings about people whois heads ring when they're knocked on, assume
that the voice guy was dramatically overestimating his use, and actually
budgets for, say, 1mbps.  Knowing that voice constitutes somewhere between
1% and 10% of her peak traffic mix, and that the sweet spot for pricing is
a DS3, she does what everybody else in his situation does, which is get a
redundant pair of DS3s.

Now, an emergency occurs.  Zillions of really scary clowns surround the
building, trapping all the occupants inside, and making faces at them
through the windows.  The thousand terrified occupants are not, however,
too discombobulated to all simultantously and continuously ring all their
friends elswhere to spread the panic.  1000 x 11kbps = 11mbps = 12%
utilization.  This continues to not be a problem when the clowns get wise
and cut the first DS3.  However, no amount of QoS will fight off the
vicious clowns when their backhoes reach the second DS3, now will it?

    > And now the emergency workers need access too. How can we guaranty
    > that?

Can't.  No requirements document will create bandwidth where none exists.

                           -Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 15:31:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13941
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 15:31:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACKXqM27680
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 15:33:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKXqv27677
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 15:33:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13923
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 15:31:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKX1v27632;
	Tue, 12 Nov 2002 15:33:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKWwv27614
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 15:32:58 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13867
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 15:30:18 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gACKQnd06190;
	Tue, 12 Nov 2002 12:26:49 -0800 (PST)
Date: Tue, 12 Nov 2002 12:26:49 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Steve Silverman <steves@shentel.net>
cc: ieprep@ietf.org, <jmpolk@cisco.com>, <Mpierce1@aol.com>
Subject: RE: [Ieprep] Requirements for Accounting
In-Reply-To: <KMEJKAPHBBCMCDDGMBLOMEDFCAAA.steves@shentel.net>
Message-ID: <Pine.GSO.4.44.0211121219170.857-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002, Steve Silverman wrote:
    > Perhaps instead of accounting, we should call it call tracking?

I don't know that there's a problem with the name...  Accounting is a
widely-used and perfectly acceptable name for the procedure, and doesn't
inherently imply a billing relationship.

I think that the underlying issue vis-a-vis accounting is whether we're
looking for L3 accounting or L7 accounting.  As long as the definition is
L7, we've already got it, and everybody can go home happy, the work is
already done.  If you want L3 accounting, you're not going to get it, you
don't need it, nobody's specified a reason for doing it, and everybody's
going to go home upset.

    > I view this as a requirement to track who uses a service especially in the
    > light of the recent DDOS attack with enough info to identify users
    > (especially those who make major demands).

>From a diagnostic point of view, as a system operator, I agree with this
whole-heartedly.  However it's my understanding that one of the drafts
currently specifies exactly the opposite...  that users be given the
opportunity to operate with anonymity, which seems to me to be a basic
conflict with the need for reliability.

    > I think we should provide a mechanism so that a network CAN
    > protect itself from such attacks.

For what value of "we?"  There are lots of smart people working in that
field, but it's typically an L3/L4 problem, not an L7 problem, and we
generally think of it as an operational practices and procedures problem
rather than a protocol one.

    > I don't think any SP would deploy a defenseless network in the
    > future.

Heh, heh.  I'll take that bet.  :-)

    > I believe that this function requires that enough records be kept so that
    > some diagnostic work can be done after the fact. It seems as though the
    > world is becoming a nastier place and in such an environment, too much trust
    > does not work very well.

Yes, so we all save SIP proxy logs, and whatever you can get the SIP
product vendors to log, we'll have for a long, long time.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 15:41:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14415
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 15:41:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACKhuo28823
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 15:43:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKhuv28820
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 15:43:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14343
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 15:41:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKh8v28780;
	Tue, 12 Nov 2002 15:43:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKgHv28745
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 15:42:17 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA14283
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 15:39:38 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 12 Nov 2002 20:36:32 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WM4FPAFC>; Tue, 12 Nov 2002 15:42:12 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D15@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock'" <woody@pch.net>, "Nguyen, An" <nguyena@ncs.gov>
Cc: RJ Atkinson <rja@extremenetworks.com>, ieprep@ietf.org
Subject: RE: [Ieprep] Measurement of Internet Congestion
Date: Tue, 12 Nov 2002 15:42:07 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Tuesday, November 12, 2002 12:57 PM
To: Nguyen, An
Cc: RJ Atkinson; ieprep@ietf.org
Subject: RE: [Ieprep] Measurement of Internet Congestion


      On Tue, 12 Nov 2002, Nguyen, An wrote:
    > In short, G.711 is G.711 regardless of the transport layer.

Yes, of course.  However, on the PSTN, that's switch-to-switch.  Several
miles of bridge-tapped 28-gauge junk away from each user, in nearly the
best case.  In an ideal world, you'd have ISDN desk-sets in front of every
POTS user, but I don't hear anyone suggesting that.

    > Let me tell the experience with the VoiceIP deployment...
    > None of [the RFP-respondents] wanted to guarantee end-to-end High
    > Availability of 99.999

That's not deployment experience, that's you talking to a salesperson.
Which has exactly nothing to do with networks or operational reality, or
voice quality.


No, actually we had several conference calls with the network design and
engineering folks on the issue. And they all said the same things. They also
said in order to boost 3 nines to four nines we have to add a parallel
(access) circuit to each of the endpoint, which is not economical at all to
us. And we only get 99.99 if we chose to go down that route. 

    > They said the max they could provide was 99.9

Okay, hypothetically, let's say they really are as bad as the worst that
they were actually willing to guarantee in writing.  If they lose one
packet in a thousand, do you really think that VoIP will fall apart at the
seams?  Do you think that'll even have an effect which could be measured
in the lab?  Much less noticed by happy users?  VoIP seems to me to work
pretty darned well at 96%-97%. 

     99.9 means 8.76 hrs/yr in down time and 99.99 means 52.56 min/yr.
     Three nines could be a big problem for emergency personnel specially
when they are in
     a disaster area and want to communicate with their counterparts. These
three nines are  
     given with the assumption that there is absolutely nothing wrong with
the networks.



    > ATM for transport

Ouch.  Yeah, well, if you actually did build the network and had problems,
there's your source.  Fortunately the Internet hasn't used any significant
quantity of ATM since it was deprecated a few years ago.

     It's not pure ATM as you thought. It's actually IP over ATM AAL5.



    > NCS has to deal with many ISPs to address this issue
    > in order to get ubiquitous.

Yes, tens of thousands.  I'm still having a bit of a hard time with the
notion that NCS really wants to enter into and manage SLA contracts with
tens of thousands of ISPs.

     Our goal is to be ubiquitous (as technically and financially as
possible). We hope in dealing with large ISPs they will give us better
coverage.

                                -Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 15:54:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15222
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 15:54:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACKv2U29757
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 15:57:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKv2v29754
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 15:57:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15192
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 15:54:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKu3v29633;
	Tue, 12 Nov 2002 15:56:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKtav29529
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 15:55:36 -0500
Received: from imo-r02.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15081
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 15:52:56 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r02.mx.aol.com (mail_out_v34.13.) id 5.15c.16d0af52 (3940);
	Tue, 12 Nov 2002 15:55:11 -0500 (EST)
Message-ID: <15c.16d0af52.2b02c4af@aol.com>
Date: Tue, 12 Nov 2002 15:55:11 EST
Subject: Re: FW: [Re: [Ieprep] ieprep-requirements-01 - reqs 6-10 - discussion request]
To: sob@harvard.edu, hgs@cs.columbia.edu
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_15c.16d0af52.2b02c4af_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_15c.16d0af52.2b02c4af_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/11/2002 11:34:14 PM Eastern Standard Time, 
sob@harvard.edu writes:


> > a permissible call defect rate of 0.00001%
> 
> 1/ I've not heard of an FCC requirement but maybe 
> 
> 2/ what is a defect - in the context of the Internet?
>     I would doubt that it is a dropped packet
> 


[MAP] This relates to my comment yesterday about (draft) ITU-T Y.1530 which 
defines a number of "call defects" for voice over IP. I suggest that 
reference be made to that draft for formal definitions of end-to-end 
performance, including "defects". Then this group can carry on easier 
discussions of what the numbers should be for various situations. I'm sure we 
can get the okay to make a copy of the latest draft (from last week) 
available.

Briefly, Y.1530 (draft) defines:

Connection Setup Delay
Connection Post-Selection Delay
Connection Answer Signal Delay
Connection Disconnect Delay
Connection Release Delay
Connection Set-up Error Probability
Connection Set-up Failure Probability
Connection Premature Disconnect Probability
Connection Clearing Failure Probability

Although ITU-T in the past dealt with circuit switched, the end-to-end 
performance parameters defined in this draft have been modified to apply to 
packet technology. If anything, the use of IP introduces the need for 
additional parameters, since it introduces additional degradations of 
quality. One thing that is missing seems to be the notion that a call can be 
successfully set up, the party answers, and then there is no media path 
available. (Didn't happen in the circuit switched world.) This is what 
Henning commented about on Nov 11 with:

- Call rings, callee picks up and then there's no conversation (due to 
failure of local resource reservation; this is the problem the 
PacketCable folks worried about since they need to manage the very 
limited upstream bandwidth)

Separately, Y.1541 covers transmission parameters of:

Packet Transfer Delay
Packet Delay Variation
Packet Loss Ratio
Packet Error Ratio

I suppose that the case Henning mentioned could simply be thought of as 
Packet loss ratio = 100%.

Mike Pierce
Artel


--part1_15c.16d0af52.2b02c4af_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/11/2002 11:34:14 PM Eastern Standard Time, sob@harvard.edu writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt; a permissible call defect rate of 0.00001%
<BR>
<BR>1/ I've not heard of an FCC requirement but maybe 
<BR>
<BR>2/ what is a defect - in the context of the Internet?
<BR> &nbsp;&nbsp;&nbsp;I would doubt that it is a dropped packet
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] This relates to my comment yesterday about (draft) ITU-T Y.1530 which defines a number of "call defects" for voice over IP. I suggest that reference be made to that draft for formal definitions of end-to-end performance, including "defects". Then this group can carry on easier discussions of what the numbers should be for various situations. I'm sure we can get the okay to make a copy of the latest draft (from last week) available.
<BR>
<BR>Briefly, Y.1530 (draft) defines:
<BR>
<BR>Connection Setup Delay
<BR>Connection Post-Selection Delay
<BR>Connection Answer Signal Delay
<BR>Connection Disconnect Delay
<BR>Connection Release Delay
<BR>Connection Set-up Error Probability
<BR>Connection Set-up Failure Probability
<BR>Connection Premature Disconnect Probability
<BR>Connection Clearing Failure Probability
<BR>
<BR>Although ITU-T in the past dealt with circuit switched, the end-to-end performance parameters defined in this draft have been modified to apply to packet technology. If anything, the use of IP introduces the need for additional parameters, since it introduces additional degradations of quality. One thing that is missing seems to be the notion that a call can be successfully set up, the party answers, and then there is no media path available. (Didn't happen in the circuit switched world.) This is what Henning commented about on Nov 11 with:
<BR>
<BR>- Call rings, callee picks up and then there's no conversation (due to 
<BR>failure of local resource reservation; this is the problem the 
<BR>PacketCable folks worried about since they need to manage the very 
<BR>limited upstream bandwidth)
<BR>
<BR>Separately, Y.1541 covers transmission parameters of:
<BR>
<BR>Packet Transfer Delay
<BR>Packet Delay Variation
<BR>Packet Loss Ratio
<BR>Packet Error Ratio
<BR>
<BR>I suppose that the case Henning mentioned could simply be thought of as Packet loss ratio = 100%.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_15c.16d0af52.2b02c4af_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 15:58:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15475
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 15:58:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACL0vI29972
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 16:00:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACL0vv29969
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 16:00:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15472
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 15:58:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACL08v29919;
	Tue, 12 Nov 2002 16:00:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACKv4v29770
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 15:57:04 -0500
Received: from imo-m03.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15200
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 15:54:25 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m03.mx.aol.com (mail_out_v34.13.) id b.164.16fa2086 (3940);
	Tue, 12 Nov 2002 15:55:47 -0500 (EST)
Message-ID: <164.16fa2086.2b02c4d2@aol.com>
Date: Tue, 12 Nov 2002 15:55:46 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: woody@pch.net
CC: rja@extremenetworks.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_164.16fa2086.2b02c4d2_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_164.16fa2086.2b02c4d2_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/12/2002 1:14:35 PM Eastern Standard Time, woody@pch.net 
writes:


>      On Tue, 12 Nov 2002 Mpierce1@aol.com wrote:
>     > [MAP] My requirement is that the specs "allow" a carrier to keep 
> records
>     > related to individual calls by providing the necessary functionality. 
> It does
>     > not address "billng", since I don't care what they do with the 
> detailed call
>     > records.
> 
> You might also take care to make clear that you're not asking for
> functionality which would support carriers performing accounting on this
> traffic, but instead for functionality which would support proxy operators
> performing accounting, which already exists and is uncontroversial.
> 


[MAP]
In draft-pierce-ieprep-assured-service-req-00, Section 6.8, I wrote:

Call Detail records (CDR) can be maintained by the proxy...

In draft-pierce-ieprep-assured-service-arch-00, Section 3, I identified that 
the "Assured Service" requires a network architecture in which a proxy 
provides the capabilities related to originating an "Assured Service" call. 
Part of these capabilities would be "accounting".

I'm glad we agree that this "already exists and is uncontroversial." The 
discussion on this list would have lead one to believe otherwise.

Mike Pierce
Artel


--part1_164.16fa2086.2b02c4d2_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/12/2002 1:14:35 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&nbsp;&nbsp;On Tue, 12 Nov 2002 Mpierce1@aol.com wrote:
<BR> &nbsp;&nbsp;&nbsp;&gt; [MAP] My requirement is that the specs "allow" a carrier to keep records
<BR> &nbsp;&nbsp;&nbsp;&gt; related to individual calls by providing the necessary functionality. It does
<BR> &nbsp;&nbsp;&nbsp;&gt; not address "billng", since I don't care what they do with the detailed call
<BR> &nbsp;&nbsp;&nbsp;&gt; records.
<BR>
<BR>You might also take care to make clear that you're not asking for
<BR>functionality which would support carriers performing accounting on this
<BR>traffic, but instead for functionality which would support proxy operators
<BR>performing accounting, which already exists and is uncontroversial.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP]
<BR>In draft-pierce-ieprep-assured-service-req-00, Section 6.8, I wrote:
<BR>
<BR>Call Detail records (CDR) can be maintained by the proxy...
<BR>
<BR>In draft-pierce-ieprep-assured-service-arch-00, Section 3, I identified that the "Assured Service" requires a network architecture in which a proxy provides the capabilities related to originating an "Assured Service" call. Part of these capabilities would be "accounting".
<BR>
<BR>I'm glad we agree that this "already exists and is uncontroversial." The discussion on this list would have lead one to believe otherwise.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_164.16fa2086.2b02c4d2_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 19:23:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20733
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 19:23:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD0PJa09552
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 19:25:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0PJv09549
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 19:25:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20729
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 19:22:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0OFv09481;
	Tue, 12 Nov 2002 19:24:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0Npv09455
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 19:23:51 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20684
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 19:21:11 -0500 (EST)
Received: from extremenetworks.com (unknown [10.255.52.14])
	by gnat.inet.org (Postfix) with ESMTP
	id 41EC867103; Tue, 12 Nov 2002 15:45:37 -0500 (EST)
Date: Tue, 12 Nov 2002 19:23:42 -0500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: "Krishnan Padmanabhan, Packet Strategies LLC" <krishnan@packetstrategies.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <00d701c28a48$44848890$6400a8c0@sumt01.nj.comcast.net>
Message-Id: <2A2C6C7A-F69E-11D6-9E61-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAD0Npv09456
Subject: [Ieprep] Re: Billing for VoIp service
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


On Tuesday, Nov 12, 2002, at 07:37 America/Montreal, Krishnan 
Padmanabhan, Packet Strategies LLC wrote:

> Via Windows Messenger or MSN Messenger, you can subscribe to the VoIP 
> services offered by several service providers. At least two of these 
> (I haven't tried the others) provide per minute billing for the IP 
> Telephony calls, call details, history, etc. They also appear to 
> offer, in addition to IP telephony, the usual internet access 
> services. Would these offer a counter-example to the point you make 
> here?

While very interesting, they aren't a counter-example.  My example was 
talking
about traditional ISPs, for which the only real services are (1) unicast
best-effort forwarding of IP packets and in some cases also (2) 
multicast
forwarding (usually with some additional constraints).  Such 
traditional ISPs
aren't even *aware* of what applications above IP that a given user 
might
be using at a given instant of time, normally.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 19:32:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20837
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 19:32:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD0Yua09845
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 19:34:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0Yuv09842
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 19:34:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20833
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 19:32:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0Y1v09818;
	Tue, 12 Nov 2002 19:34:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0Xgv09799
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 19:33:42 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20814
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 19:31:02 -0500 (EST)
Received: from extremenetworks.com (unknown [10.255.52.14])
	by gnat.inet.org (Postfix) with ESMTP
	id 6248A67103; Tue, 12 Nov 2002 15:55:27 -0500 (EST)
Date: Tue, 12 Nov 2002 19:33:32 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <36.31374b7d.2b029b64@aol.com>
Message-Id: <89CC7709-F69F-11D6-9E61-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 12, 2002, at 12:59 America/Montreal, Mpierce1@aol.com 
wrote:
> Yes, this might increase the capital costs for any carrier that wants 
> to support this customer (NCS), just as many other capabilites might. 
> So what is so different about this one?

The problem is that it probably increases the costs for carriers that 
CHOOSE NOT TO
support NCS as a customer.

> But, I am also arguing this point in support of DISA, which is the 
> operator of a large network, which may one day migrate to supporting 
> voice over IP (although I'm beginning
> to think that is a long way off!)

DISA does operate a large network.  The DISN technical staff (i.e. the 
folks who
actually do operate those IP networks) seem to be taking a different 
posture than you
when I talk with DISN folks directly.  Not sure where the disconnect 
lies in that...

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 19:35:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20885
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 19:35:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD0bwL10572
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 19:37:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0bwv10569
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 19:37:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20876
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 19:35:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0b1v09987;
	Tue, 12 Nov 2002 19:37:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0aCv09896
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 19:36:12 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20854
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 19:33:32 -0500 (EST)
Received: from extremenetworks.com (unknown [10.255.52.14])
	by gnat.inet.org (Postfix) with ESMTP
	id 2436467103; Tue, 12 Nov 2002 15:57:58 -0500 (EST)
Date: Tue, 12 Nov 2002 19:36:03 -0500
Subject: Re: [Ieprep] Measurement of Internet Congestion
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211120947070.857-100000@paixhost.pch.net>
Message-Id: <E3C4EAE6-F69F-11D6-9E61-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 12, 2002, at 12:56 America/Montreal, Bill Woodcock 
wrote:
> Ouch.  Yeah, well, if you actually did build the network and had 
> problems,
> there's your source.  Fortunately the Internet hasn't used any 
> significant
> quantity of ATM since it was deprecated a few years ago.

Bill forgets that a large UK-owned ISP is still built out primarily
upon wide-area ATM infrastructure.  ATM is not particularly growing
among the IP oriented community and Ethernet is killing off ATM in
the LAN/MAN, but there is still a fair bit of ATM around in the world.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 19:45:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21067
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 19:45:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD0lEb10905
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 19:47:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0lEv10902
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 19:47:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21041
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 19:44:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0kEv10836;
	Tue, 12 Nov 2002 19:46:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0j4v10800
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 19:45:04 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20997
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 19:42:23 -0500 (EST)
Received: from extremenetworks.com (unknown [10.255.52.14])
	by gnat.inet.org (Postfix) with ESMTP
	id 9799E67103; Tue, 12 Nov 2002 16:06:49 -0500 (EST)
Date: Tue, 12 Nov 2002 19:44:54 -0500
Subject: Re: [Ieprep] access links
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Dean <idb@tazznetworks.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211121946.gACJksgf000678@volta.tazznetworks.com>
Message-Id: <2082AE25-F6A1-11D6-9E61-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 12, 2002, at 14:46 America/Montreal, Dean wrote:

> I believe that congestion can be defined pretty good for VoIP
> Two years ago I was working for a VoIP vendor and when we were
> implementing the system, this 3 parameters were used to define network
> congestion.
>
> 1. packet drop rate
> different vocoders have different treshold, but in general
> more then 3% of packetloss, the voice conversation is becomming pretty
> not understandable.
>
> 2. latency - should be lower then 150ms one way. If it is higher, the
> echo cancelation algorythms can not do the work
>
> 3. jitter ideally should be 0, but up to 60 msec can be tolerated.

It would be useful to get some citations to the published literature
or other more detailed (ideally math) explanations of where those
numbers come from.  I think it would help to be talking about some
concrete numbers.

> Also, the main problem in implenting VoIP GETS-like services will be
> in access not on the backbone.

Agree, and please note that the presence/absence of QoS (or bandwidth or
anything else) on the access link is often not under the control of the 
ISP.

> So far I have not seen much talk about access side. From experience I
> can say, when the access was resolved the backbone was comming along
> with no problem.

Sounds plausible enough.

> So Bill
> you might be right that now VoIP traffic is insignificant, but lets
> say there is a disaster and lot of people are trying to reach friends
> and realtives from the disaster site, can you image what will happen
> on the access loops near the site (inbound and outbound)? And now the
> emergency workers need access too. How can we guaranty that?

It is up to each end site to configure their access router and access 
links
appropriately.  The ISP can't affect much on the last mile access link. 
  Given
the percentage of end sites that don't secure their routers, I would 
rather
rely on Iridium working myself.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 19:45:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21102
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 19:45:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD0lsu10937
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 19:47:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0lsv10934
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 19:47:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21081
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 19:45:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0l1v10890;
	Tue, 12 Nov 2002 19:47:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0ktv10875
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 19:46:55 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21029
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 19:44:15 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAD0end19075;
	Tue, 12 Nov 2002 16:40:49 -0800 (PST)
Date: Tue, 12 Nov 2002 16:40:49 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: RJ Atkinson <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: RE: [Ieprep] Measurement of Internet Congestion 
Message-ID: <Pine.GSO.4.44.0211121640220.17722-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


      On Tue, 12 Nov 2002, Nguyen, An wrote:
    > No, actually we had several conference calls with the network design and
    > engineering folks on the issue. And they all said the same things.

Correct.  That's _talk_, not _deployment experience_.  We're in violent
agreement, I think.

    >> If they lose one packet in a thousand, do you really think that
    >> VoIP will fall apart at the seams?
    > 99.9 means 8.76 hrs/yr in down time and 99.99 means 52.56 min/yr.

Okay, that's if taken together, rather than evenly distributed.  In point
of fact, you'll have a little bit of both.  But since you suggest it, what
are the odds of an emergency occurring at a specific site within any
arbitrary single 9-hour window, each year?  Since you say that it wasn't
worth the cost of a second local loop to reduce that to one hour,
presumably the odds are already awfully low.

    > It's not pure ATM as you thought. It's actually IP over ATM AAL5.

Correct...  Voice directly over ATM isn't a bad thing, particularly, if
you know how to run an ATM network...  It's when you try to run data over
ATM that it doesn't particularly work.  And of course, it's irrelevant
now, since there haven't been ATM products that could keep up with
production network speeds in the last few years.  But this is taking
the conversation off into the weeds.

    >> I'm still having a bit of a hard time with the notion that NCS
    >> really wants to enter into and manage SLA contracts with tens of
    >> thousands of ISPs.
    > Our goal is to be ubiquitous (as technically and financially as
    > possible). We hope in dealing with large ISPs they will give us better
    > coverage.

Yes, slightly, but not significantly.  That's one of the major ways in
which the Internet differs from the PSTN.  And it's something you guys
really need to analyze, in order to determine whether you're asking for a
product that you're not going to be able to afford to buy.

                                -Bill



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 19:50:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21285
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 19:50:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD0qvZ11144
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 19:52:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0qvv11141
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 19:52:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21272
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 19:50:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0q0v11120;
	Tue, 12 Nov 2002 19:52:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0pNv11078
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 19:51:23 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21206
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 19:48:42 -0500 (EST)
Received: from extremenetworks.com (unknown [10.255.52.14])
	by gnat.inet.org (Postfix) with ESMTP
	id 4ECF267103; Tue, 12 Nov 2002 16:13:08 -0500 (EST)
Date: Tue, 12 Nov 2002 19:51:13 -0500
Subject: Re: [Ieprep] Requirements for Accounting
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: <ieprep@ietf.org>
To: "Steve Silverman" <steves@shentel.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <KMEJKAPHBBCMCDDGMBLOMEDFCAAA.steves@shentel.net>
Message-Id: <0246FEAE-F6A2-11D6-9E61-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 12, 2002, at 15:20 America/Montreal, Steve Silverman 
wrote:
> Perhaps instead of accounting, we should call it call tracking?  (I 
> don't
> think the name is very important.) Would this be more acceptable to 
> some
> people?

The name matters only to make the meaning clear.  Right now, I think
there are a bunch of different meanings in different heads on this
list.

If one were proposing "call accounting inside SIP servers" and 
explicitly
NOT any form of accounting performed by IP-layer-only service providers,
then I would be a lot more comfortable with the proposal.  Is that in
fact what folks mean ?

> I don't think that charging users for emergency calls is projected to 
> become
> a major source of income for any SP.

I'd agree that is likely for ISPs, not sure about PSTN SPs.

> I would like to avoid the situation in which more money is spent 
> billing
> users than providing the desired service.

So would ISPs, particularly the majority of ISPs who only offer "best 
effort
IP-layer forwarding" as a service offering (and ignore whether the 
traffic
is VoIP or not, and ignore any attempts to request QoS).

> I view this as a requirement to track who uses a service especially in 
> the
> light of the recent DDOS attack with enough info to identify users
> (especially those who make major demands).

We need to define clearly which "service" is meant by the above.
	IP access ?
	SIP server connection ?
	something else ?

> Even if some network does not want to defend itself, I think we should
> provide a mechanism so that a network CAN
> protect itself from such attacks.  (I don't think any SP would deploy a
> defenseless network in the future.)
> I believe that this function requires that enough records be kept so 
> that
> some diagnostic work can be done after the fact. It seems as though the
> world is becoming a nastier place and in such an environment, too much 
> trust
> does not work very well.

The problem is that keeping records of some kinds of events CREATES new
vulnerabilities, which vulnerabilities I hope we agree would be a bad 
thing
to mandate or suggest for deployment.  Since IP networks are 
connectionless,
there is no record of connections normally available at the IP-layer.  
And
most ISPs only offer IP-layer services.  So I don't see where 
"accounting"
fits into the picture for ISPs.  Disagree ?

Also, Can we please define meanings more clearly (see questions above) ?

Thanks,

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 19:56:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21370
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 19:56:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD0x0q11363
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 19:59:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0x0v11360
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 19:59:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21335
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 19:56:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0w2v11330;
	Tue, 12 Nov 2002 19:58:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD0vgv11315
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 19:57:42 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21324
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 19:55:02 -0500 (EST)
Received: from extremenetworks.com (unknown [10.255.52.14])
	by gnat.inet.org (Postfix) with ESMTP
	id 6195267103; Tue, 12 Nov 2002 16:19:28 -0500 (EST)
Date: Tue, 12 Nov 2002 19:57:33 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: woody@pch.net, ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <164.16fa2086.2b02c4d2@aol.com>
Message-Id: <E4B7B9E4-F6A2-11D6-9E61-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 12, 2002, at 15:55 America/Montreal, Mpierce1@aol.com 
wrote:
> In draft-pierce-ieprep-assured-service-arch-00, Section 3, I 
> identified that the "Assured Service" requires a network architecture 
> in which a proxy provides the capabilities related to originating an 
> "Assured Service" call.

At best, I don't understand what the above means.  If someone can 
translate,
please feel free to do so.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 21:25:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23956
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 21:25:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD2S4i17624
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 21:28:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2S4v17621
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 21:28:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23953
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 21:25:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2R7v17535;
	Tue, 12 Nov 2002 21:27:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2Qwv17431
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 21:26:58 -0500
Received: from mtiwmhc11.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23914
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 21:24:17 -0500 (EST)
Received: from cs.columbia.edu ([12.91.138.6])
          by mtiwmhc11.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP
          id <20021113022648.JRAS20682.mtiwmhc11.worldnet.att.net@cs.columbia.edu>;
          Wed, 13 Nov 2002 02:26:48 +0000
Message-ID: <3DD1B7EF.9000204@cs.columbia.edu>
Date: Tue, 12 Nov 2002 21:24:47 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: Steve Silverman <steves@shentel.net>, ieprep@ietf.org
Subject: Re: [Ieprep] Requirements for Accounting
References: <0246FEAE-F6A2-11D6-9E61-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

"Auditing" has been mentioned in a number of (IETF) documents as one 
function of usage tracking; I assume the goal here is mostly to track 
usage of certain services, e.g., for system sizing or detection of abuse 
("Sergeant Shultz seems to be making a lot of emergency calls to a 
private number listed under Mary Smith"), not to send bills.

As a side-note, byte-based billing is apparently quite common in 
Australia and New Zealand, not to mention in wireless networks (GPRS). 
See http://www.bigpond.com/broadband/products/adsl/pricing.asp for an 
example of a volume-based plan.

Btw, once you charge per-byte on a wireless link, there is a good 
argument to be made that you need to charge for call setup, too. 
Otherwise, you end up encourage sending voice packets embedded in 
signaling messages... (ISDN UU had the same problem.)


RJ Atkinson wrote:
> 
> On Tuesday, Nov 12, 2002, at 15:20 America/Montreal, Steve Silverman wrote:
> 
>> Perhaps instead of accounting, we should call it call tracking?  (I don't
>> think the name is very important.) Would this be more acceptable to some
>> people?
> 
> 
> The name matters only to make the meaning clear.  Right now, I think
> there are a bunch of different meanings in different heads on this
> list.
> 
> If one were proposing "call accounting inside SIP servers" and explicitly
> NOT any form of accounting performed by IP-layer-only service providers,
> then I would be a lot more comfortable with the proposal.  Is that in
> fact what folks mean ?

> The problem is that keeping records of some kinds of events CREATES new
> vulnerabilities, which vulnerabilities I hope we agree would be a bad thing
> to mandate or suggest for deployment.  Since IP networks are 
> connectionless,
> there is no record of connections normally available at the IP-layer.  And
> most ISPs only offer IP-layer services.  So I don't see where "accounting"
> fits into the picture for ISPs.  Disagree ?

Effectively, you do have "connections" at many access points, as long as 
there's an identifiable connection between some identifier (interface, 
PPP session, etc.) in a small number of places. Thus, this seems to be a 
question of granularity. Accounting within a backbone ISP for an 
individual modem user or user-level session doesn't make sense, but 
counting in/out bytes for the customer or peer ISP does.

Apparently, some universities have started per-user byte counts to more 
fairly allocate resources 
(http://www.riverstonenet.com/technology/accounting_for_profitability.shtml)
Indeed, there's the IPFIX WG...

Also, if there is resource reservation (recall the PacketCable DOCSIS 
remarks), you can easily count bytes or packets on a per-session basis.

The Internet is getting big enough that a tiny application niche can 
have more traffic than the whole Internet ten years ago :-)

Thus, I think we'd all avoid a lot of wasted discussion if "requirements 
for X" were silently or explicitly substituted by "If you decide to do 
X, these are things X should do to be useful". A second step is then the 
"applicability" part. There, the only real distinctions are "never, ever 
useful (and likely harmful)" or "a tool that has some use". Documenting 
the risks and costs of tools is clearly useful.

> 
> Also, Can we please define meanings more clearly (see questions above) ?
> 
> Thanks,
> 
> Ran
> rja@extremenetworks.com
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 22:35:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25730
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 22:35:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD3c6521738
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 22:38:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD3c6v21735
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 22:38:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25700
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 22:35:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD3b7v21320;
	Tue, 12 Nov 2002 22:37:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD3aqv21095
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 22:36:52 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25688
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 22:34:09 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAD3Ubd21121;
	Tue, 12 Nov 2002 19:30:37 -0800 (PST)
Date: Tue, 12 Nov 2002 19:30:36 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: RJ Atkinson <rja@extremenetworks.com>,
        Steve Silverman <steves@shentel.net>, <ieprep@ietf.org>
Subject: Re: [Ieprep] Requirements for Accounting
In-Reply-To: <3DD1B7EF.9000204@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211121929490.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 12 Nov 2002, Henning Schulzrinne wrote:
    > As a side-note, byte-based billing is apparently quite common in
    > Australia and New Zealand, not to mention in wireless networks (GPRS).

Yep, and pray that it doesn't spread, else you won't be able to afford to
web-browse anymore either.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 12 22:51:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26086
	for <ieprep-archive@odin.ietf.org>; Tue, 12 Nov 2002 22:51:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD3s4G22338
	for ieprep-archive@odin.ietf.org; Tue, 12 Nov 2002 22:54:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD3s4v22335
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 22:54:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26069
	for <ieprep-web-archive@ietf.org>; Tue, 12 Nov 2002 22:51:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD3r2v22254;
	Tue, 12 Nov 2002 22:53:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD3qgv22230
	for <ieprep@optimus.ietf.org>; Tue, 12 Nov 2002 22:52:42 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA26011
	for <ieprep@ietf.org>; Tue, 12 Nov 2002 22:50:00 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 13 Nov 2002 03:50:05 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WYQLG7Q6>; Tue, 12 Nov 2002 22:53:46 -0500
Message-ID: <B3FE60C05AD31D4C96E07EBC5000639E1D7F7A@EMSHQS2>
From: "Choi, Don" <choid@ncr.disa.mil>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>, Mpierce1@aol.com
Subject: RE: [Ieprep] Atlanta ieprep Agenda
Date: Tue, 12 Nov 2002 22:52:30 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ran, 

You are right that the current DISN IP networks do not have many of the
requirements we are discussing here. And this may change for the DISN IP
networks.

However, an important point is that DSN (voice network) has all these
requirements right now, and these requirements have to be supported for DSN
to migrate from TDM to IP. 

Hope this explains the disconnect.

Don

-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Tuesday, November 12, 2002 7:34 PM
To: Mpierce1@aol.com
Cc: ieprep
Subject: Re: [Ieprep] Atlanta ieprep Agenda



On Tuesday, Nov 12, 2002, at 12:59 America/Montreal, Mpierce1@aol.com 
wrote:
> Yes, this might increase the capital costs for any carrier that wants 
> to support this customer (NCS), just as many other capabilites might. 
> So what is so different about this one?

The problem is that it probably increases the costs for carriers that 
CHOOSE NOT TO
support NCS as a customer.

> But, I am also arguing this point in support of DISA, which is the 
> operator of a large network, which may one day migrate to supporting 
> voice over IP (although I'm beginning
> to think that is a long way off!)

DISA does operate a large network.  The DISN technical staff (i.e. the 
folks who
actually do operate those IP networks) seem to be taking a different 
posture than you
when I talk with DISN folks directly.  Not sure where the disconnect 
lies in that...

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 10:32:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04899
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 10:32:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADFYXN05420
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 10:34:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADFYXv05416
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 10:34:33 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04891
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 10:31:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADFXMv05379;
	Wed, 13 Nov 2002 10:33:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADFWGv05290
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 10:32:16 -0500
Received: from volta.tazznetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04772
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 10:29:39 -0500 (EST)
Received: from volta.tazznetworks.com (localhost.tazznetworks.com [127.0.0.1])
	by volta.tazznetworks.com (8.12.6/8.12.3) with ESMTP id gADFU0tY000686;
	Wed, 13 Nov 2002 10:30:00 -0500 (EST)
	(envelope-from idb@volta.tazznetworks.com)
Message-Id: <200211131530.gADFU0tY000686@volta.tazznetworks.com>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Dean <idb@tazznetworks.com>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] access links 
In-Reply-To: Your message of "Tue, 12 Nov 2002 19:44:54 EST."
             <2082AE25-F6A1-11D6-9E61-00039357A82A@extremenetworks.com> 
User-Agent: EMH/1.10.0 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?UTF-8?B?VW5l?=
 =?UTF-8?B?Ymlnb3J58m1hZQ==?=) APEL/10.3 Emacs/21.2 (i386--freebsd) (with
 unibyte mode)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
X-Mailer: mh-e 6.1; nmh 1.0.4; Emacs 21.2
Date: Wed, 13 Nov 2002 10:30:00 -0500
From: Dean <idb@tazznetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> On Tuesday, Nov 12, 2002, at 14:46 America/Montreal, Dean wrote:
> 
> > I believe that congestion can be defined pretty good for VoIP
> > Two years ago I was working for a VoIP vendor and when we were
> > implementing the system, this 3 parameters were used to define network
> > congestion.
> >
> > 1. packet drop rate
> > different vocoders have different treshold, but in general
> > more then 3% of packetloss, the voice conversation is becomming pretty
> > not understandable.
> >
> > 2. latency - should be lower then 150ms one way. If it is higher, the
> > echo cancelation algorythms can not do the work
> >
> > 3. jitter ideally should be 0, but up to 60 msec can be tolerated.
> 
> It would be useful to get some citations to the published literature
> or other more detailed (ideally math) explanations of where those
> numbers come from.  I think it would help to be talking about some
> concrete numbers.

I have to dig out the test results that we did at my previous
employer. We did internal testing for 4 different codecs
G711
G729a
G723 (ADPCM 32)
G725 (ADPCM 24)

I have to say that the testing was done with our internal sales,
marketing and engineering people. Engineering had a higher tolerance that
sales people.

Different codecs have different network tolerance.

G729a is more flexible on the network, then G711. Here is why:
G729a generates a 10 byte voice frame every 10msec vs
G711 which generates a 64 byte frame every 8 msec. 

Now you can packetize multiple frames into one IP packet. VoIP packets
should be smaller, so that the loss of one (or multiple) packets will
not loose a significant part of the voice information, but also big
enough that jitter in the network can be mitigated.  It is hard to
support, at the access side, an outgoing packet of 48/80 bytes
(G729a/G711 with compressed RTP header) every 8 or 10 msec.  Even in
the backbone, some variations (that will be present in crisis
situations) can cause jitter, which will result in dropped packets at
the destination because the packet(s) timed out.

If multiple voice-frames are packetized (up to a certain point), the
bandwidth requirement for voice conversation will go down (because of
less overhead), but packets are bigger. G729a can grow up to 12 voice
frames per packet (120 bytes + IP/UDP/RTP header) where G711 is
problematic with more than 3 voice frame per packet (192 bytes +
IP/UDP/RTP header).  Waiting for serialization and serialization times
on slower access links impact latency budget for the whole
connection and the interarrival times between packets are still at 24
msec.  If G729a has 4 voice frames per IP packet, we are creating 
more flexible network characteristics for voice conversation.  Every 40
msec one packet of 77 bytes (RTP header compressed to 5 bytes)
is transmitted from the sender, which results in 15.4 kbps bandwidth
per voice call.  Instead of delivering a packet every 10 msec, we can
deliver a packet every 40 msec. If we add a jitter buffer in the picture
the voice frame delivery can be smoothened out.
(usually it is recommended to size the jitter buffer minimum as number
of voice frames per packet + 1 or 2 voice frames, in this case jitter
buffer would be between 40 and 60 msec).

Anyway, I will try to find documents that pertain to your question
(internal test results) and will also try to see what I can find on Google.

However, I believe that GETS service user (e.g., DISA) should tell
this working group what constitues acceptable voice quality (i.e.,
which codecs) and then it would be much easier to specify the
requirements.  For example, cell phones, POTS lines and radio
communications have different voice quality which translates to
different network requirements.


Dean
idb@tazznetworks.com

===============================================
I like to share my ignorance. I have enough.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 10:48:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05459
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 10:48:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADFp4K06855
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 10:51:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADFp4v06852
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 10:51:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05386
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 10:48:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADFo7v06766;
	Wed, 13 Nov 2002 10:50:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADFlEv06601
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 10:47:14 -0500
Received: from dewberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05240
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 10:44:37 -0500 (EST)
Received: from cs.columbia.edu (5thnat.cise-nsf.gov [192.12.209.8])
	(user=hgs10 mech=PLAIN bits=0)
	by dewberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gADFl7mu001259
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 10:47:10 -0500 (EST)
Message-ID: <3DD27383.3000704@cs.columbia.edu>
Date: Wed, 13 Nov 2002 10:45:07 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ieprep@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Voice quality metrics
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

We have looked at the QOS issue for audio in depth. See 
http://www.cs.columbia.edu/~wenyu for a set of papers. Summary: it's not 3%.

The ITU e-model (cited in the papers) combines delay and codec 
distortions into a single metric and provides bounds on acceptable 
quality. Many of the metrics are relevant for analog transmission 
distortions (such as various frequency or noise distortions).

The delay bound is also described in ITU Rec. G.114, based on a fair 
number of human-subject measurements.

I think the jitter bound is largely immaterial; playout buffers 
translate jitter into absolute delay, so it's not an independent 
quantity (assuming well-functioning playout algorithms).

My first-order approximation is that a network that has usable telnet 
performance works well for voice. With high losses, you're not going to 
be enjoying your telnet session due to TCP retransmission delay. (The 
only difference is that temporary telnet delay spikes are probably more 
tolerable than for audio.)

Henning

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 11:16:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06586
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 11:16:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADGIk409206
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 11:18:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGIkv09203
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 11:18:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06508
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 11:16:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGI4v09182;
	Wed, 13 Nov 2002 11:18:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGH4v09147
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 11:17:04 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06467
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 11:14:26 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Wed, 13 Nov 2002 11:14:00 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111310573504186
 ; Wed, 13 Nov 2002 10:57:35 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <WYJVRZ6P>; Wed, 13 Nov 2002 10:58:57 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64231E541@mcl-its-exs01>
From: "Garrity, Jack" <JOHN.J.GARRITY@saic.com>
To: "'Bill Woodcock'" <woody@pch.net>
Cc: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
Date: Wed, 13 Nov 2002 10:57:35 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Bill,

I'll stick with the >85 percent yardstick, although you raise an interesting
point.  To extend it, I might calculate the percentage of three-party
conferences.  But that won't dilute the fact that more than 85 percent of
the access lines are served.  Some (a lot?) of those lines serve many
people.  Someone might want to calculate how many people-pairs are served.
Huge percentage, no doubt.

 ~~~ Jack ~~~
Work: 703/676-2358 | Fax: 703/484-0299
Home: 703/278-9250 | Cell: 703/508-0065
Email: garrityj@saic.com

-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Tuesday, November 12, 2002 11:10 AM
To: Garrity, Jack
Cc: 'Ken Carlberg'; ieprep
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion
request


      On Tue, 12 Nov 2002, Garrity, Jack wrote:
    > For the scenario you describe, the NS/EP codepoint and NS/EP features
take
    > effect at GETS-capable local exchanges.  Those exchanges serve over X
    > percent of US-based access lines, where X is on the order of 85
percent or
    > greater.
    > If the terminating local exchange is GETS-capable (same switches
    > as in the first paragraph), NS/EP features have effect.

So about 70% of U.S. domestic source-destination pairs are covered.  Since
as has been pointed out many times recently, there's no practical way of
distinguishing national borders on the Internet, I don't have
U.S.-specific figures.  However, if the DoD purchased GETS-like services
from the dozen or so usual suspects globally, they'd have only about 4%
coverage.  (20% of 20%, rather than 85% of 85%).  There are a _lot_ of
ISPs, and the large ones aren't that large relative to the whole.

                                -Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 11:40:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07586
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 11:40:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADGggD11461
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 11:42:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGggv11458
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 11:42:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07545
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 11:40:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGg3v11425;
	Wed, 13 Nov 2002 11:42:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGfUv11394
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 11:41:30 -0500
Received: from imo-m02.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07511
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 11:38:52 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m02.mx.aol.com (mail_out_v34.13.) id j.3b.2fa3dc1e (4394);
	Wed, 13 Nov 2002 11:41:10 -0500 (EST)
Message-ID: <3b.2fa3dc1e.2b03daa5@aol.com>
Date: Wed, 13 Nov 2002 11:41:09 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_3b.2fa3dc1e.2b03daa5_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_3b.2fa3dc1e.2b03daa5_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/12/2002 7:33:58 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> DISA does operate a large network.  The DISN technical staff (i.e. the folks 
> who
> actually do operate those IP networks) seem to be taking a different 
> posture than you
> when I talk with DISN folks directly.  Not sure where the disconnect lies 
> in that...
> 



[MAP] I suppose that the disconnect is that those who are operating the 
present DISN are concerned with the "here-and-now", that is, what can be done 
with what the vendors already offer (and a little of what they promise in the 
near future), while the group I am supported by is a little more concerned 
about what changes are needed in standards to be used a little farther in the 
future than "now". Also, I believe the disconnect is that voice over IP is 
not part of their current focus, since no one has really haven't figured out 
how to do it properly. (Reference your comment about the JCS directive 
preventing use of VoIP in the backbone.)

I hope I've characterizied this correctly, since I must admit I don't have 
the big picture of all of DoD.

Mike Pierce
Artel


--part1_3b.2fa3dc1e.2b03daa5_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/12/2002 7:33:58 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">DISA does operate a large network. &nbsp;The DISN technical staff (i.e. the folks who
<BR>actually do operate those IP networks) seem to be taking a different posture than you
<BR>when I talk with DISN folks directly. &nbsp;Not sure where the disconnect lies in that...
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>
<BR>[MAP] I suppose that the disconnect is that those who are operating the present DISN are concerned with the "here-and-now", that is, what can be done with what the vendors already offer (and a little of what they promise in the near future), while the group I am supported by is a little more concerned about what changes are needed in standards to be used a little farther in the future than "now". Also, I believe the disconnect is that voice over IP is not part of their current focus, since no one has really haven't figured out how to do it properly. (Reference your comment about the JCS directive preventing use of VoIP in the backbone.)
<BR>
<BR>I hope I've characterizied this correctly, since I must admit I don't have the big picture of all of DoD.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_3b.2fa3dc1e.2b03daa5_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 11:53:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08149
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 11:53:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADGtiD12331
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 11:55:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGtiv12327
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 11:55:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08126
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 11:53:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGt2v12140;
	Wed, 13 Nov 2002 11:55:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGpav11925
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 11:51:36 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07804
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 11:48:57 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Wed, 13 Nov 2002 08:48:11 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gADGmvb9001170;
	Wed, 13 Nov 2002 08:48:57 -0800 (PST)
Subject: Re: [Ieprep] Requirements for Accounting
From: Rex Buddenberg <budden@nps.navy.mil>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: RJ Atkinson <rja@extremenetworks.com>,
        Steve Silverman
	 <steves@shentel.net>, ieprep@ietf.org
In-Reply-To: <3DD1B7EF.9000204@cs.columbia.edu>
References: <0246FEAE-F6A2-11D6-9E61-00039357A82A@extremenetworks.com> 
	<3DD1B7EF.9000204@cs.columbia.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 13 Nov 2002 08:46:50 -0800
Message-Id: <1037206010.3604.473.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Operational uses.

Law enforcement.  In the circuit-switched telephone system and in the
United States, the call detail records are readily available to law
enforcement.  Unlike wiretapping the content of a conversation (requires
probable cause), simply looking at the telephone numbers of who talks
with whom is open.  I've seen Customs investigators put together really
persuasive association charts of narcotics criminal enterprises using
this data (with the property tax records at the county treasurer as
corroboration).  
	In our terminology, this is Layer 7 accounting.  

Emergency services.  A 'call back' capability is consistently needed and
for several purposes.  If someone calls in reporting some kind of
emergency, it's often necessary to reconnect with that person later --
more information, check for hoax, or simply to trace location so the
dispatcher can direct the ambulance (this is a data point that got lost
in the cellphone phenomenon and has lots of legislatures exercised in
trying to get it back).  
	This is also Layer 7 accounting.  It matters not how the call was
routed, only _where_ it was routed from.

Internet variant.  If you're investigating a child porn case over the
internet, you sieze one of the perps' computer and look at his mail
files.  In particular, look at the e-mail headers (which are routinely
masked off by most user agents these days -- but the data is still
there).  This tells you what MTAs the mail was routed through and can
tell you quite a bit of useful information about who's trading dirty
pictures with whom.  Again, Layer 7 accounting.

In all of these cases, I can find no reason to want to know the Layer 3
routing information -- that's entirely irrelevant.  

On Tue, 2002-11-12 at 18:24, Henning Schulzrinne wrote:
> "Auditing" has been mentioned in a number of (IETF) documents as one 

Both the SNMP and CMIP standards documents mention
	fault management
	security management
	performance management
	configuration management
	accounting management
as the abstract reasons for network management systems.  Once it's in
one of these base documents, the list is parroted and the original
definitions often get lost ... or changed.  You see this phenomenon in
the networking textbooks worst of all.  




Recommendation.  I'd find some practicing law enforcement and emergency
services folks and consult with them to find out what useful accounting
information they'd want.  Leaven with somebody who's familiar with both
the 1st and 4th Amendments.  Makes a lot of sense to do this before
rather than try to glue on some fixes later.



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 12:09:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08851
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 12:09:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADHBgS14244
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 12:11:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHBgv14241
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 12:11:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08812
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 12:09:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADH92v14044;
	Wed, 13 Nov 2002 12:09:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADH4vv13075
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 12:04:57 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08507
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 12:02:18 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 13 Nov 2002 17:02:23 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WYQLHMNF>; Wed, 13 Nov 2002 12:06:05 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D1D@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>
Date: Wed, 13 Nov 2002 12:04:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Ieprep] RE: network congestion, VoIP, NCS contracting approach, etc.
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ran,

>Prioritisation is a mechanism.  The NCS mission, as you state, is to
>ensure communications availability.  NCS ought not care which mechanism
>is used, provided that communications remain available.

>Over-provisioning is a different mechanism, commonly used today (max 
>link
>utilisation equal to 30% of link capacity is typical among the ISPs I 
>was talking
>with last Thursday),  to ensure that packets don't get lost in the 
>network,
>because it is cheaper than deploying something like DiffServ.  Other 
>mechanisms
a>lso exist.

Don't know if you are aware of these: GETS has priority trunk queuing for
access and priority egress in addition to HPC. Telecommunication Service
Priority (TSP) provides circuits restorations based on "priority" during an
emergency. 


>[ASIDE:		So far, each time there has been a press release or
article
>claiming that ISP <x> has deployed DiffServ throughout its network, 
>when I
>have tracked down the facts of the matter it has turned out to be 
>marketing
>or press confusion unrelated to the actual operational network.  It 
>would be
>VERY helpful if any ISP would make a public presentation at NANOG/RIPE 
>about
>their deployment.  So if anyone is at such a place and is listening, 
>please
>consider making such a public presentation in detail.]

>An alternative perspective is that NCS ought to focus on talking with 
>ISPs about
>contracts that have *performance-based* metrics for ensuring network 
>availability,
>rather than contracts that require particular mechanisms to be deployed
>(whether or not those mechanisms work in a particular situation).

Reliability for emergency traffic is something NCS would like to work on
next.



>After all, as long as an ISP that has chosen to provide contracted 
>services
>to NCS can provide those services, why should NCS care which 
>mechanism(s)
>are used to provide those services ?

All NCS needs is something better than what non-emergency calls get when
congestions occur to ensure high probability of completion for NS/EP calls.
Under normal conditions, we would not care at all.

Regards,

An
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 12:15:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09079
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 12:15:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADHHtn14603
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 12:17:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHHsv14600
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 12:17:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09065
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 12:15:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHH1v14524;
	Wed, 13 Nov 2002 12:17:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHGhv14486
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 12:16:43 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08996
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 12:14:04 -0500 (EST)
Received: from mcl-its-ieg02.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Wed, 13 Nov 2002 12:15:59 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg02.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111312151606276
 ; Wed, 13 Nov 2002 12:15:16 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <W5WFAGX3>; Wed, 13 Nov 2002 12:17:25 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77967@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Dean'" <idb@tazznetworks.com>, RJ Atkinson <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
Date: Wed, 13 Nov 2002 12:16:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> However, I believe that GETS service user (e.g., DISA) should tell
> this working group what constitues acceptable voice quality (i.e.,
> which codecs) and then it would be much easier to specify the
> requirements.  For example, cell phones, POTS lines and radio
>communications have different voice quality which translates to
>different network requirements.

Let's try to focus here.  

The "voice quality" discussion, I believe, is restricted to voice quality
over access links.  I take it we are assuming an ETS location has contracted
with an ISP and there is an access link between them.  It has been pointed
out that ISPs don't often control QoS on this link.  

Problem statement????  Everyone at the ETS location wants to make calls at
the same time and the access link can't handle all that voice traffic so
conversations degrade so much as to be unusable.  

Potential solutions for problem...define the appropriate codecs, get a big
enough access link, provision QoS on CPE or more drastically pay for QoS to
be deployed on ISP router that faces the customer site, etc.

Defining the problem to be solved with appropriate context information would
be helpful.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 12:21:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09344
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 12:21:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADHNlf15007
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 12:23:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHNlv15004
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 12:23:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09334
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 12:21:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHN2v14975;
	Wed, 13 Nov 2002 12:23:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHM0v14902
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 12:22:00 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09242
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 12:19:21 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADHFvd29764;
	Wed, 13 Nov 2002 09:15:57 -0800 (PST)
Date: Wed, 13 Nov 2002 09:15:57 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: "'RJ Atkinson'" <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] RE: network congestion, VoIP, NCS contracting approach,
 etc.
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D1D@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211130911210.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002, Nguyen, An wrote:
    > All NCS needs is something better than what non-emergency calls get when
    > congestions occur to ensure high probability of completion for NS/EP calls.

I think we're zeroing in on the heart of the misunderstanding here.  If
you have something _different_ (which is what you're asking for
when you say "better") than the production path, it will always have a
_lower_ probability of call completion.  You _don't want to be different_
than best-effort.  Different than best-effort is _not-best-effort_.  As I
understand it, your whole focus here is to avoid being not-best!  :-)

    > Reliability for emergency traffic is something NCS would like to
    > work on next.

Wrong order of approach.  You don't want to create a problem and then fix
it.  If you take on reliability first, you'll never create a hole to dig
yourself out of.


                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 12:41:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10034
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 12:41:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADHi8S16604
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 12:44:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHi7v16601
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 12:44:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10018
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 12:41:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHh5v16509;
	Wed, 13 Nov 2002 12:43:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHg3v16422
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 12:42:03 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09858
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 12:39:24 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 13 Nov 2002 17:36:17 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WM4FP7RQ>; Wed, 13 Nov 2002 12:42:00 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D23A4F3@emshqs1.ncr.disa.mil>
From: "Folts, Harold" <foltsh@ncs.gov>
To: "'Bill Woodcock'" <woody@pch.net>
Cc: "'ieprep'" <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: more process discussion
Date: Wed, 13 Nov 2002 12:41:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> -----Original Message-----
> From: Bill Woodcock [mailto:woody@pch.net]
> Sent: Tuesday, November 12, 2002 1:18 PM
> To: Folts, Harold
> Cc: 'King, Kimberly S.'; 'ieprep'
> Subject: RE: [Ieprep] Re: more process discussion
> 
> 
>       On Tue, 12 Nov 2002, Folts, Harold wrote:
>     > The Internet technology offers an excellent protential 
> to support
>     > emergency communications in times of disaster.
> 
> Uh, this isn't "potential," this is actual fact.  The 
> question at hand is
> whether there's a problem that needs to be fixed.  Is there a problem
> which needs to be fixed?  If so, can you articulate it, 
> quantify it, and
> describe the process you went through to discover and identify it?
> 
>                                 -Bill

The ieprep working group is "preparedness" not "repair"

Hal 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:02:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10747
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:02:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADI49p17573
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:04:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADI49v17570
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:04:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10741
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:01:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADI34v17547;
	Wed, 13 Nov 2002 13:03:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADI2cv17516
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:02:38 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10690
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 12:59:58 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADHuXd00121;
	Wed, 13 Nov 2002 09:56:33 -0800 (PST)
Date: Wed, 13 Nov 2002 09:56:33 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77967@mcl-its-exs01>
Message-ID: <Pine.GSO.4.44.0211130916560.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002, King, Kimberly  S. wrote:
    > Problem statement????  Everyone at the ETS location wants to make calls at
    > the same time and the access link can't handle all that voice traffic so
    > conversations degrade so much as to be unusable.

A case such as the above, where the local loop is saturated _purely with
voice_ seems like it might be quite an outlier, since the voice just
doesn't add up that fast relative to the size of local loops...  However
several people have postulated a problem when the combination increased
voice use (likely) and a simultaneous hypothetical increase in data use
(unlikely) combine to make the local loop unusable for voice.

    > Potential solutions for problem...define the appropriate codecs, get a big
    > enough access link, provision QoS on CPE or more drastically pay for QoS to
    > be deployed on ISP router that faces the customer site, etc.

Yes, these are all appropriate responses.  Adding capacity dynamically
through a dial-on-demand link would fall under the "get a big enough link"
category.  Unplug non-voice VLANs would be a manual version of Qos...  I
can't think of any other solutions than those you've mentioned.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:06:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10867
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:06:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADI8ws18301
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:08:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADI8vv18298
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:08:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10839
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:06:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADI81v18282;
	Wed, 13 Nov 2002 13:08:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADI73v17760
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:07:03 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10797
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:04:23 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADI10d00173;
	Wed, 13 Nov 2002 10:01:00 -0800 (PST)
Date: Wed, 13 Nov 2002 10:01:00 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Folts, Harold" <foltsh@ncs.gov>
cc: "'ieprep'" <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: more process discussion
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D23A4F3@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211130959370.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002, Folts, Harold wrote:
    > The ieprep working group is "preparedness" not "repair"

So we're preparing a solution for a problem which we acknowledge doesn't
exist?

Can we delay smacking the Internet upside the head with the solution until
the problem actually manifests itself, perhaps?

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:10:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11082
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:10:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADICvV18596
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:12:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADICvv18593
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:12:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11069
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:10:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIC3v18526;
	Wed, 13 Nov 2002 13:12:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIBav18459
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:11:36 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10985
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:08:56 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADI5Ud00205;
	Wed, 13 Nov 2002 10:05:30 -0800 (PST)
Date: Wed, 13 Nov 2002 10:05:30 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Garrity, Jack" <JOHN.J.GARRITY@saic.com>
cc: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion request
In-Reply-To: <B8030EB94AF1D51196D70002A589D64231E541@mcl-its-exs01>
Message-ID: <Pine.GSO.4.44.0211131001570.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002, Garrity, Jack wrote:
    > I'll stick with the >85 percent yardstick, although you raise an interesting
    > point.  To extend it, I might calculate the percentage of three-party
    > conferences.  But that won't dilute the fact that more than 85 percent of
    > the access lines are served.  Some (a lot?) of those lines serve many
    > people.  Someone might want to calculate how many people-pairs are served.
    > Huge percentage, no doubt.

Yes, that's exactly my point.

Whereas under the PSTN, this model works really well, and you get a huge
percentage of coverage at the (relatively) low cost of dealing with a
small number of large providers, AND I AGREE THAT THE NUMBERS BEAR THIS
OUT, you don't have similar leverage in the Internet, where you'd have to
deal with a huge number of mom & pop shops, and you still would only have
single-digit percentage coverage, which hardly seems worthwhile.
Particularly since nobody's established yet that a problem exists.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:16:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11329
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:16:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADIJ6U19017
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:19:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIJ6v19014
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:19:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11286
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:16:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADII6v18942;
	Wed, 13 Nov 2002 13:18:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIHYv18813
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:17:34 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11196
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:14:55 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id E63F17A10; Wed, 13 Nov 2002 10:17:26 -0800 (PST)
Date: Wed, 13 Nov 2002 13:07:36 -0500
Subject: Re: [Ieprep] Re: more process discussion
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: "'Bill Woodcock'" <woody@pch.net>, "'ieprep'" <ieprep@ietf.org>
To: "Folts, Harold" <foltsh@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D23A4F3@emshqs1.ncr.disa.mil>
Message-Id: <C9CC93C5-F732-11D6-91CD-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 12:41 America/Montreal, Folts, Harold 
wrote:
> The ieprep working group is "preparedness" not "repair"

Hal,

	On 9/11/01 the Internet created an existence proof that it is
already fully prepared.  The Internet has demonstrated this also in
other countries (e.g. Japan during/after earthquakes, California
during/after earthquakes).

	Sounds to me and others like we are already prepared.

	Can we please shut down the WG and go home now ?

Quite Seriously Yours,

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:17:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11342
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:17:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADIJAS19032
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:19:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIJAv19029
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:19:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11292
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:16:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADII5v18926;
	Wed, 13 Nov 2002 13:18:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIHYv18809
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:17:34 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11194
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:14:54 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 8A2257A14; Wed, 13 Nov 2002 10:17:26 -0800 (PST)
Date: Wed, 13 Nov 2002 13:04:43 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: "Nguyen, An" <nguyena@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D1D@emshqs1.ncr.disa.mil>
Message-Id: <62EBB625-F732-11D6-91CD-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Re: network congestion, VoIP, NCS contracting approach, etc.
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 12:04 America/Montreal, Nguyen, An wrote:
> All NCS needs is something better than what non-emergency calls get 
> when
> congestions occur to ensure high probability of completion for NS/EP 
> calls.

NCS wants the emergency calls to get through and be intelligible.
This is achievable without adding ANY mechanisms.  In fact, it can
be achieved without providing any different service for NCS than
is provided for other customers -- if the network operator chooses
to engineer their network in that manner.  Many network operators
ALREADY do this.

If NCS would use performance-based metrics RATHER THAN trying to 
standardise
specific mechanisms (e.g. lower drop probability through precedence), 
then
NCS would be able to ensure that the emergency calls get through and
work, operators would not have to go through strange contortions (e.g. 
if
a network drops no packets, then it is impossible for the network
to provide emergency calls with lower drop probability: catch-22), and
taxpayer dollars would probably also be conserved.

An operator who drops no packets cannot provide lower drop probability
OR higher probability of packet transport for NCS.  It is a logical
contradiction.  So the definition you use above penalises operators who
design and operate a network that is better suited for NCS purposes.
That seems like an outcome contrary to NCS's mission as defined in
law and policy.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:17:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11350
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:17:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADIJB319051
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:19:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIJBv19048
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:19:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11294
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:16:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADII2v18843;
	Wed, 13 Nov 2002 13:18:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIHVv18788
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:17:31 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11181
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:14:51 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 82B627A0A; Wed, 13 Nov 2002 10:17:23 -0800 (PST)
Date: Wed, 13 Nov 2002 12:24:50 -0500
Subject: Re: [Ieprep] Requirements for Accounting
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DD1B7EF.9000204@cs.columbia.edu>
Message-Id: <D0780CD6-F72C-11D6-91CD-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 12, 2002, at 21:24 America/Montreal, Henning 
Schulzrinne wrote:
> Effectively, you do have "connections" at many access points, as long 
> as there's an identifiable connection between some identifier 
> (interface, PPP session, etc.) in a small number of places.

  You changed layers on me.  PPP itself is a link-layer technology.  PPP 
also
does not imply use of any kind of user login (e.g. PPP over SONET).

My claim remains valid -- the IP layer is connectionless and so does 
not have
connections that can be tracked.   Some other layers have some kinds of
connections, where the details materially differ depending on which 
layer
(and protocol) one considers.

What was the meaning of the original commenter that I replied to ?
That remains entirely unclear, making it hard to understand the
intended meaning and have a constructive conversation.

> Thus, this seems to be a question of granularity. Accounting within a 
> backbone ISP for an individual modem user or user-level session 
> doesn't make sense, but counting in/out bytes for the customer or peer 
> ISP does.

Counting in/out bytes on an *interface* or in/out packets on an 
*interface*
(where I mean the values precisely as defined in the widely implemented 
IETF
Interface MIB standards) is fine.

It is important that there is NO expection or requirement for 
finer-grained
byte/packet counting (e.g. per-flow is not available, per-end site is 
not
available, per IP-ToS-bit-pattern is not available).

> Also, if there is resource reservation (recall the PacketCable DOCSIS 
> remarks), you can easily count bytes or packets on a per-session > basis.

	So far, PacketCable is vapour.  The cable folks (e.g. Cox) are 
currently actually
deploying their telephony services using a different technology that 
uses different
frequencies on the HFC, and is unrelated to IP, DOCSIS, or PacketCable. 
  PacketCable
or DOCSIS are also inherently access technologies.

	Most current cable network operators purchase IP transit from one or 
more larger
carriers and basically are Tier-2 ISPs.  Exceptions exist outside North 
America,
but are very few even outside North America.

> Thus, I think we'd all avoid a lot of wasted discussion if 
> "requirements for X" were silently or explicitly substituted by "If 
> you decide to do X, these are things X should do to be useful". A 
> second step is then the "applicability" part. There, the only real 
> distinctions are "never, ever useful (and likely harmful)" or "a tool 
> that has some use". Documenting the risks and costs of tools is 
> clearly useful.

It is still important to be very CLEAR about what is mean by X or by 
"things
X should do to be useful".  So far, clarity remains a big problem -- 
and your
note did not entirely clarify the original note's ambiguity.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:17:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11368
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:17:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADIJEM19066
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:19:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIJEv19063
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:19:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11301
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:16:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADII3v18861;
	Wed, 13 Nov 2002 13:18:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIHWv18792
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:17:32 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11184
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:14:52 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 8CFB27A10; Wed, 13 Nov 2002 10:17:24 -0800 (PST)
Date: Wed, 13 Nov 2002 12:32:02 -0500
Subject: Re: [Ieprep] access links 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>
To: Dean <idb@tazznetworks.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211131530.gADFU0tY000686@volta.tazznetworks.com>
Message-Id: <D23C17AA-F72D-11D6-91CD-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 10:30 America/Montreal, Dean wrote:
> However, I believe that GETS service user (e.g., DISA) should tell
> this working group what constitues acceptable voice quality (i.e.,
> which codecs) and then it would be much easier to specify the
> requirements.

It would be useful to hear what they think.  I'd much rather see
an abstract technical specification than a specification of certain
existing CODECs.  One option of IETF would be for IETF to standardise
a new CODEC (e.g. one that hypothetically would be better suited for
real world deployed IP networks).

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:17:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11381
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:17:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADIJHa19082
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:19:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIJGv19079
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:19:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11305
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:16:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADII3v18879;
	Wed, 13 Nov 2002 13:18:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIHXv18796
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:17:33 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11188
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:14:53 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id EEF2F7A11; Wed, 13 Nov 2002 10:17:24 -0800 (PST)
Date: Wed, 13 Nov 2002 12:41:10 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3b.2fa3dc1e.2b03daa5@aol.com>
Message-Id: <18B7AF72-F72F-11D6-91CD-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 11:41 America/Montreal, Mpierce1@aol.com 
wrote:
> [MAP] I suppose that the disconnect is that those who are operating 
> the present DISN are concerned with the "here-and-now", that is, what 
> can be done with what the vendors already offer (and a little of what 
> they promise in the near future), while the group I am supported by is 
> a little more concerned about what changes are needed in standards to 
> be used a little farther in the future than "now". Also, I believe the 
> disconnect is that voice over IP is not part of their current focus, 
> since no one has really haven't figured out how to do it properly. 
> (Reference your comment about the JCS directive preventing use of VoIP 
> in the backbone.)

So, normally, IETF standardises technology AFTER we have "figured out 
how
to do it properly".  This is one reason why a specification can't 
proceed
to Draft Standard without multiple interoperable implementations, for 
example.

Given that the community haven't "figured out how to do VoIP properly",
it seems premature to standardise changes to that stuff.  A preferred 
approach
might be for the community to figure out how to do it properly, write 
that up,
and then look into standardising stuff that actually works.  This has 
to do
with the traditional "running code" part of the IETF mantra.

Approaches where an organisation's "standards activity" is as decoupled 
from
the line network engineering/operations activity tend to lead towards 
standards
that have significant deployment and operations issues.  Approaches 
where the
operators are the ones who are active in the standards WGs tend to be 
approaches
where the results are deployable and reasonable to operate.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:17:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11394
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:17:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADIJK219098
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:19:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIJKv19095
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:19:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11323
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:16:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADII6v18958;
	Wed, 13 Nov 2002 13:18:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIHZv18817
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:17:35 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11197
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:14:55 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 067687A0F; Wed, 13 Nov 2002 10:17:24 -0800 (PST)
Date: Wed, 13 Nov 2002 12:29:15 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: ieprep <ieprep@ietf.org>, Mpierce1@aol.com
To: "Choi, Don" <choid@ncr.disa.mil>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <B3FE60C05AD31D4C96E07EBC5000639E1D7F7A@EMSHQS2>
Message-Id: <6EB31EF6-F72D-11D6-91CD-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


That helps, but the DISN IP folks also claim that JCS has explicitly
prohibited them from deploying those kinds of features until DISA
can prove to satisfaction of JCS that such is reasonable/appropriate.

Other folks in the DSN part of DISA are quick to point out that JCS
has also said that DoD is not permitted to deploy VoIP except if a
specific case-by-case waiver is obtained from JCS -- and they also
tell me that such waivers are extremely rare (Skyline being the primary
example of a waiver being granted -- and the negative parts of the
Skyline experience apparently have been heard clearly at JCS).

My concern is that a lot of the things being discussed here have very
significant implications in the operational IP network world.  It would
be better for everyone if some of the actual DISA IP network operations
folks were participating here on their own -- instead of having the
somewhat disconnected DISA Centre for Standards folks doing all/most
of the interactions.  Based on my conversations with those folks, they
seem to share the exact concerns that Bill, Sean, and other operators
here share.

Ran

On Tuesday, Nov 12, 2002, at 22:52 America/Montreal, Choi, Don wrote:
> You are right that the current DISN IP networks do not have many of the
> requirements we are discussing here. And this may change for the DISN 
> IP
> networks.
>
> However, an important point is that DSN (voice network) has all these
> requirements right now, and these requirements have to be supported 
> for DSN
> to migrate from TDM to IP.
>
> Hope this explains the disconnect.
>
> Don

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:24:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11601
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:24:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADIQUp19447
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:26:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIQUv19444
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:26:30 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11585
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:23:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIPEv19382;
	Wed, 13 Nov 2002 13:25:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADINiv19249
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:23:44 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11501
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:21:03 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Wed, 13 Nov 2002 10:20:17 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gADILKb9005897;
	Wed, 13 Nov 2002 10:21:20 -0800 (PST)
Subject: Re: [Ieprep] RE: network congestion, VoIP, NCS contracting
	approach, etc.
From: Rex Buddenberg <budden@nps.navy.mil>
To: "Nguyen, An" <nguyena@ncs.gov>
Cc: "'RJ Atkinson'" <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D1D@emshqs1.ncr.disa.mil>
References: <7F18415E4D63CB45BB9B3A591F68D12D5B3D1D@emshqs1.ncr.disa.mil>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 13 Nov 2002 10:19:12 -0800
Message-Id: <1037211552.1091.515.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Wed, 2002-11-13 at 09:04, Nguyen, An wrote:
<snip>
> 
> Reliability for emergency traffic is something NCS would like to work on
> next.
> 
> 
I believe you have your priorities in the wrong order.  

First, is it ok to translate 'reliability' into availability (up time /
total time) and survivability?  

The engineering solution to the availability problems involve multiple
threading (elimination of single points of failure).  In most cases,
this tends to result in overprovision which overtake the QoS issues.  

I routinely tell my students to tackle the Ao problem _first_; then see
what QoS issues remain.

Existence proof.  The new buoy tenders that USCG is commissioning now
(about half way through the overall procurement) are replacing the
1942-43 tenders.  The sponsor wanted a dynamic positioning system in it
-- take me to an X in the ocean and keep me there while I work the
buoy.  Since we routinely set the buoy next to the rock, this is a
mission-critical exercise properly requiring Ao that cannot be met in a
single-threaded system.  So we spec'd FDDI Dual Attach Stations; the
Juniper class has 6 nodes on an FDDI LAN including the nav sensors on
the bridge, a navigator's workstation and the engine room controller
(wheels and rudder).  
	Every time somebody reviewed and said we needed to do some data flow
analysis, we'd figure out the capacity loads (e.g. a Loran receiver
produces a fix every 4 seconds resulting in 3 dozen bytes of payload),
double everything for redundancy ... and couldn't get above 1% loading
of the network.  End of capacity load analysis.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:28:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11743
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:28:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADIV2q19771
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:31:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIV2v19768
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:31:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11732
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:28:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADITtv19687;
	Wed, 13 Nov 2002 13:29:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIQrv19468
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:26:53 -0500
Received: from mail2.mx.voyager.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11599
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:24:13 -0500 (EST)
Received: from mail.delta-info.com (clyde.delta-info.com [146.145.21.34])
	by mail2.mx.voyager.net (8.11.6/8.10.2) with ESMTP id gADIQkD78321
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:26:46 -0500 (EST)
Received: from s15 ([])
        by mail.delta-info.com (Merak 4.00.100) with SMTP id DVB36921
        for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:14:42 -0500
Reply-To: <gthom@delta-info.com>
From: "Gary Thom" <gthom@delta-info.com>
To: "ieprep" <ieprep@ietf.org>
Subject: RE: [Ieprep] RE: network congestion, VoIP, NCS contracting approach, etc.
Date: Wed, 13 Nov 2002 13:26:53 -0500
Message-ID: <NDBBKMIGCLLNAOGKKDDPCEKFDDAA.gthom@delta-info.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <Pine.GSO.4.44.0211130911210.21062-100000@paixhost.pch.net>
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

If there is no distinction, then when there is not enough bandwidth for all
of the _best-effort_ traffic (due to congestion or damage), how does the
emergency traffic get through? Is it ok to just treat it like all the other
_best-effort_ traffic. At this point, doesn't best effort mean you settle
for whatever you can get? Isn't there a way, under these circumstances to
"better" than everyone else?

Gary


>       On Wed, 13 Nov 2002, Nguyen, An wrote:
>     > All NCS needs is something better than what non-emergency
> calls get when
>     > congestions occur to ensure high probability of completion
> for NS/EP calls.
>
> I think we're zeroing in on the heart of the misunderstanding here.  If
> you have something _different_ (which is what you're asking for
> when you say "better") than the production path, it will always have a
> _lower_ probability of call completion.  You _don't want to be different_
> than best-effort.  Different than best-effort is _not-best-effort_.  As I
> understand it, your whole focus here is to avoid being not-best!  :-)
>

 --------------------------------------------
 Name   : Gary A. Thom
 Company: Delta Information Systems, Inc.
 Address: 300 Welsh Rd., Bldg 3
          Horsham, PA 19044 USA
 Phone  : +1-215-657-5270 x123
 Fax    : +1-215-657-5273
 E-mail : gthom@delta-info.com
 Website: www.delta-info.com
--------------------------------------------


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:57:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12685
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:57:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADIxLE21874
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 13:59:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIxLv21871
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 13:59:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12676
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:56:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIwAv21829;
	Wed, 13 Nov 2002 13:58:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIvUv21804
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:57:30 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA12621
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:54:52 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 13 Nov 2002 18:54:56 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WYQLHQRH>; Wed, 13 Nov 2002 13:58:38 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D1E@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock'" <woody@pch.net>
Cc: "'RJ Atkinson'" <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] RE: network congestion, VoIP, NCS contracting approa
	ch, etc.
Date: Wed, 13 Nov 2002 13:57:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Bill,


    > Reliability for emergency traffic is something NCS would like to
    > work on next.

>Wrong order of approach.  You don't want to create a problem and then fix
>it.  If you take on reliability first, you'll never create a hole to dig
>yourself out of.

Well, I am not talking for the IETF organization. I am talking the effort
being worked in the T1 organization on behalf on the NCS. Sorry for not
stating it clearly.

Regards,

An

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 13:58:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12763
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 13:58:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADJ0x421985
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 14:00:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJ0xv21982
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 14:00:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12749
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 13:58:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJ02v21940;
	Wed, 13 Nov 2002 14:00:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADIxov21898
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 13:59:50 -0500
Received: from mail1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12683
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 13:57:11 -0500 (EST)
Received: from bgreenew2k (dhcp-10-24-19-69.cisco.com [10.24.19.69]) by mail1.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id KAA23325; Wed, 13 Nov 2002 10:58:58 -0800 (PST)
Reply-To: <bgreene@cisco.com>
From: "Barry Raveendran Greene" <bgreene@cisco.com>
To: "Folts, Harold" <foltsh@ncs.gov>,
        "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>
Cc: "'ieprep'" <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: more process discussion
Date: Wed, 13 Nov 2002 10:58:51 -0800
Message-ID: <LNEHJBNJAPFNLEGJHCPEAEJKKDAA.bgreene@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D23A4BA@emshqs1.ncr.disa.mil>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



> Therefore, I an seeking to bring technical provisions into Internet
> technology that will provide highly reliable and available communication
> capabilities in times of serious disaster and limited bandwidth.

And this is the point were people are not hearing each other. ISPs who have
any clue do _not_ build a network that is vulnerable to "serious disaster
and limited bandwidth." This is especially true for the top ten players
(using Skitter as the metric for the top ten). ISPs have to design for
_DAILY_ disasters! Floods, storms, equipment failure, back hoe failure,
maintenance injected human error (the biggest cause of 'network disasters'),
earthquakes, anchor pulls (cutting trans-oceanic cables), wars (spilling
over into cyber attacks), and a wide range of there "real world" factors
impact ISP's networks every day. It is a _business imperative_ that you
design you network to cope with these global disasters.

Watching the conversation for the past week, I see the ISP operations side
saying that "ISPs design for disaster today - requiring zero packet loose on
the links and the ability to flap traffic over to backup paths without
circuit saturation - what's the problem?"

On the other side I see people who think the ISPs do not have any clue,
require QOS, require someone to tell them how to run their network, and do
not know how to build their networks to cope with disasters. Yes, there are
many ISPs out there who are clueless. There are lots of others ISPs who have
an unbelievable insight of how the Internet really operates - designing
networks that cope with all sorts of "disasters" - disaster that most of the
people on this group never ever see. Why? Cause the reliability of these ISP
network hide these outage from the masses.

History proves that the many ISPs know how to plan and design for these
everyday disasters. New "technical provisions" are being provided (speaking
as a vendor), but are driven by the people designing, running, building,
selling these networks. What I see is people projecting their own
perceptions on these designers/builders/operators and these people pushing
back. Not

At the same time we have people throwing the customer tail circuits into the
zone of "ISP's control." From as ISP design point of view, the tail circuit
between them and their customer is a DMZ - a place of limited control - a
place where the outside world or the customer can saturate at any moment.
This has been a place where all sorts of "technical provision" are applied.
This is the place where customer SLA is applied to keep two parties in sync
with the real congestion problems (people who think it is the ISPs who is
required to meet SLA agreements, think again).

Honestly, from what I've seen over the past three weeks demonstrates that
this WG is dead. The way correspondence is flowing shows me that rough
consensus is not going to be reached. At best, some informational RFCs will
be published which could be used for RFPs. But those would be little
different from the work done already to support contractual SLAs.

ADs - please make sure your at the meeting.




_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 14:04:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13082
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 14:04:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADJ6v822223
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 14:06:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJ6vv22220
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 14:06:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13073
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 14:04:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJ62v22194;
	Wed, 13 Nov 2002 14:06:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJ5mv22173
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 14:05:48 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13043
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 14:03:09 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADIxid00827;
	Wed, 13 Nov 2002 10:59:44 -0800 (PST)
Date: Wed, 13 Nov 2002 10:59:44 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Gary Thom <gthom@delta-info.com>
cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] RE: network congestion, VoIP, NCS contracting approach,
 etc.
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPCEKFDDAA.gthom@delta-info.com>
Message-ID: <Pine.GSO.4.44.0211131054190.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002, Gary Thom wrote:
    > If there is no distinction, then when there is not enough bandwidth for all
    > of the _best-effort_ traffic (due to congestion or damage), how does the
    > emergency traffic get through? Is it ok to just treat it like all the other
    > _best-effort_ traffic. At this point, doesn't best effort mean you settle
    > for whatever you can get? Isn't there a way, under these circumstances to
    > "better" than everyone else?

Only at the expense of likelihood of call completion.  Look at it this
way: Under a pure best-effort situation, you can have four parties sharing
a pie of size forty units, and each will receive a slice of size ten.
Alternatively, under a QoS regime, four parties can share a pie of size
eight, where one gets a slice of size eight, and three others get a slice
of size zero.

If you're the guy who gets priority, and gets to choose which slice to
take, would you rather choose from the set (10,10,10,10) or the set
(8,0,0,0)?  That's what's at issue.  If you FIRST define the overall size
of the pie as 8 (by requiring QoS) and SECOND define yourself as the guy
who gets selection priority, you wind up with a slice (probability of call
success) of 8.  If you FIRST define the overall size of the pie as 40 (by
using the Internet) and SECOND take your fair share, you wind up with a
slice of size 10, and are happier in the long run.

That assumes, however, that the ultimate goal is call success.  If the
ultimate goal is just to feel "special" the other way around works better.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 14:12:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13491
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 14:12:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADJEwm23090
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 14:14:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJEwv23087
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 14:14:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13459
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 14:12:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJE2v23057;
	Wed, 13 Nov 2002 14:14:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJDcv23036
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 14:13:38 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA13376
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 14:11:00 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 13 Nov 2002 19:11:03 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WYQLHQZ9>; Wed, 13 Nov 2002 14:14:46 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D1F@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Rex Buddenberg'" <budden@nps.navy.mil>
Cc: "'RJ Atkinson'" <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] RE: network congestion, VoIP, NCS contracting approa
	ch, etc.
Date: Wed, 13 Nov 2002 14:13:29 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Rex,


>-----Original Message-----
>From: Rex Buddenberg [mailto:budden@nps.navy.mil]
>Sent: Wednesday, November 13, 2002 1:19 PM
>To: Nguyen, An
>Cc: 'RJ Atkinson'; ieprep
>Subject: Re: [Ieprep] RE: network congestion, VoIP, NCS contracting
>approach, etc.



> 
> 
>I believe you have your priorities in the wrong order.  

>First, is it ok to translate 'reliability' into availability (up time /
>total time) and survivability?  

>The engineering solution to the availability problems involve multiple
>threading (elimination of single points of failure).  In most cases,
>this tends to result in overprovision which overtake the QoS issues.  

Actually, since reliability/availability/survivability and priority are
related to QoS in Y.1541, they will be addressed somewhat concurrently in
the T1 organization. At least that is the plan agreed to at the last
meeting.

Regards,

An

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 14:15:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13583
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 14:15:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADJHAU23230
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 14:17:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJHAv23227
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 14:17:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13576
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 14:14:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJG8v23186;
	Wed, 13 Nov 2002 14:16:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJFpv23150
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 14:15:51 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13513
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 14:13:11 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Wed, 13 Nov 2002 11:12:23 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gADJDOb9008775;
	Wed, 13 Nov 2002 11:13:24 -0800 (PST)
Subject: Re: [Ieprep] Re: more process discussion
From: Rex Buddenberg <budden@nps.navy.mil>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: "Folts, Harold" <foltsh@ncs.gov>, "'Bill Woodcock'" <woody@pch.net>,
        "'ieprep'"
	 <ieprep@ietf.org>
In-Reply-To: <C9CC93C5-F732-11D6-91CD-00039357A82A@extremenetworks.com>
References: <C9CC93C5-F732-11D6-91CD-00039357A82A@extremenetworks.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 13 Nov 2002 11:11:18 -0800
Message-Id: <1037214678.3604.541.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Wed, 2002-11-13 at 10:07, RJ Atkinson wrote:
  The Internet has demonstrated this also in
> other countries (e.g. Japan during/after earthquakes, California
> during/after earthquakes).
> 
Aha, my packrat tendencies are occasionally useful.  Attached below is
an after-action on the Kobe earthquake -- 1995.  

The Kobe earthquake has several lessons worth reviewing; here are a few
points that I've picked up:
	- note that this mentality is pre-internet but you should note the
'networked bulletin boards' notions that appear
	- Kobe, like Loma Prieta and Northridge, happened at an hour when
family reunification problems are at their nadir.  None of these three
happened while school was in session.  Picture the 'I'm alive' issue if
the quake had occurred at 1000 local.
	- note that the voice vs other data feel is a bit different.
	- there's a whole lot of what the software geeks call open source
running around here -- the reporters don't have much nice to say about
the higher-than-local government.




To: Rex Buddenberg <budden@nps.navy.mil>
From: ENOAM@research.gsb.columbia.edu
Date:         26 May 95 10:03:28 EST
Subject:      Re: Kobe earthquake article

KOBE'S LESSON:
DIAL 711 FOR "OPEN" EMERGENCY COMMUNICATIONS

Eli M. Noam and Harumasa Sato

_______________________________
Tranquility and routine were abruptly shattered on January 17 in
the Japanese port city of Kobe, when an earthquake struck at
dawn, killing more than five thousand people and leaving many
more homeless.  The dazed survivors, together with their families
and public safety agencies, immediately faced an information
problem.  What was going on?  How could help be organized?  What
was the fate of their loved ones?  A few months later, we are
able to assess how helpful modern communications and information
technology was in producing answers to these questions.  The
experience of Kobe, as well as those of the less severe quakes of
Los Angeles and San Francisco, are important for a world that is
always at the edge of natural or manmade disaster.
     The basic lesson from Kobe is that the usual approach of
disaster communications, traditionally based on military-style
public safety agencies that are operating in a top-down manner
and share information with "civilians" only on a "need-to-know"
basis, should be replaced. Instead, we should set up an open-
access emergency system -- open to inputs from a wide variety of
public and private participants and with open to access to that
information. Not only would such a system be more efficient as a
tool of information and organization, but it would also be more
resilient to the shocks of disaster.
     There are always two ways to protect vital information. One
is to design and build elaborate and hardened technical systems.
This is expensive and will always miss unforeseen mishaps. The
other approach is to decentralize the information system so that
even if many of its parts are damaged the whole will continues to
function.
     A historic analogy: in the early days of the American
republic, important public documents were protected in archives
and other storage facilities.  Thomas Jefferson, here also ahead
of his time, argued instead for protection by decentralization:
     "Our experience has proved to us that a single copy, or
     a few, deposited in MS in the public offices cannot be
     relied on for any great length of time.  The ravages of
     fire and of ferocious enemies have had but too much
     part in producing the very loss we now deplore. . .
     This leads us then to the only means of preserving. . .
     that is, a multiplication of printed copies."

Today, electronic information and communications technology makes
it possible to organize emergency communications in a similarly
decentralized fashion.  To explore this approach, let us look at
the experience of Kobe, both the positive and the negative.
     1.  Phone networks are not so much destroyed as congested
into uselessness. In Kobe, most lines and switches kept on going.
Service was temporarily interrupted to about 20% of subscribers
in the damaged areas, mostly due to power outages (285,000
subscriber lines), destruction of buildings (100,000 lines), and
cut transmission links mostly above-ground (about 100,000 lines).
For long-distance service, the trunks of NTT, Japan's
traditionally dominant domestic carrier, were fairly resilient.
Among competing carriers, DDI's microwave transmission proved
robust, while the fiber links of Teleway Japan (using its highway
rights-of-way) were temporarily cut when the roads were
destroyed.
     One of the first things that needed fixing were ATM cash
machines and financial networks. It turned out that survivors
needed money to buy food; credit cards needed verification; and
interbank transfers were urgently needed. Almost 500 ATM host
computers and terminals, as well as the system management itself,
were damaged, and their restorations proved difficult.
     The main problem, however, was congestion rather than
destruction.  Because everyone was trying to call at the same
time, nobody got through. Networks are designed to handle about
ten percent of their subscribers at one time. In Kobe, traffic
volume on the first day was 50 times the usual peak---way above
capacity.  Next day, network demand was still 20 times normal
peak. This is not a short-term problem for disaster areas.
Experience shows that after a crisis the volume of calls stays
heavy for a long time.
     In Kobe, as before in California, most incoming long-
distance calls were blocked in favor of outgoing calls.
Emergency service (911, known in Japan as 119 and 110) received
priority, but it congested almost immediately and became more of
a source of frustration than help.
     Mobile communications proved helpful in bypassing destroyed
landlines. But they, too, were vulnerable and congested. Traffic
volume was seven times normal. In heavily damaged areas, one
third of NTT's transmission towers were damaged or stopped
working for lack of electricity.  Emergency batteries proved
inadequate.  Adjacent towers often maintained coverage, but at
the expense of capacity.
      Disaster mitigation meets the prepared. Long in advance of
disasters, the public should be educated on using telephones only
minimally in such situations, and encouraged to pick a "message
meeting point." Congestion control should receive priority.
Collaborative multi-aid agreements among otherwise competing
carriers, such as already exist in New York, should be reached
and tested in advance. Inbound 800 numbers could let some long-
distance calls though even while most are blocked.  But no
network can be designed economically to withstand the gravest and
rarest of disasters and congestions. One must be realistic about
the limitations of advanced planning.
     2.  Television provided the big picture, often from the
over-dramatized perspective of hovering helicopters, but not the
little-picture details which people on the scene really need.  TV
networks  released only verified official information on the
number of the dead and the magnitude of the earthquake, and
because these figures were underestimates, public recognition of
the catastrophe was long delayed.  A Kobe congressman called
several members of the Japanese Diet in Tokyo, pleading for a
declaration of national emergency and the dispatch of troops, but
was disbelieved for hours, because early TV reports were much
less disturbing.
     Radio proved again very useful in emergencies. (The humble
battery becomes critical in emergencies. If seems impossible to
have too many.) In California, the much-maligned talk radio shows
provided a tension-reducing two-way link and countered false
rumors. In Japan, too, the number of calls to radio stations was
large--20,000 calls to FM Kobe, and 30,000 to NHK in four days.
     3.  The major lesson from Kobe is that computer networks and
bulletin boards are more effective than voice phone networks and
broadcasting, once the immediate calamity is over.
     In Kobe, the "Nifty" computer network quickly became a major
meeting point. Nifty (as well as its rival PC-Van) established a
special earthquake bulletin board on the earthquake. During its
first week, 5,000 messages were posted, and accessed 650,000 by
140,000 subscribers.  Usage of the board was free, and Nifty
matched charitable donations.
     The first messages posted were about disaster and
transportation conditions. Soon, inquiries appeared by friends
and families outside of Kobe. Initially only few messages were
sent by survivors since many of them  had lost computers, phones,
and power. But some Nifty members soon reached an access point in
an adjacent prefecture.
     One of the most interesting things to happen in Kobe was the
emergence of "information volunteers."  These were mostly
outsiders who came into Kobe carrying their portable computers.
They visited shelters, collected messages about survivors (some
taken from handwritten notes attached to ruins), and sent out the
specifics about needs.  They created a meeting point between
needs and help and coordinated supplies among shelters. They
obtained regional data about food, water, and hot bath
opportunities, and put it on a regional map.  Later, they offered
information about jobs, schooling, and housing.
     Many of the volunteers organized themselves over the
network. For instance, a Nifty forum for railway enthusiasts
delivered a message  "Let's meet at the Osaka station at 8
O'Clock this weekend and then go to Kobe to help.  Each member
should bring food and other supplies for survivors." A forum for
motorcycle owners organized its members to move into the damaged
neighborhoods to help as well as to obtain information which was
put on the network.
One software company designed an information system to track and
register survivors. This system was first ignored by official
agencies but received 3-4,000 inquiries within one day.
     It is often feared that "unofficial" information is
inaccurate and not updated. However, once the Nifty bulletin
board information grew in volume, it tended to be self-verifying.
While some messages may have been inaccurate, their sum-total
offered a better picture than the official information collected
in the traditional way. Information was periodically reviewed by
a Nifty monitoring committee, the messages seems to have been
generally informative, responsible, and often quite interesting.
Feedback among network members, as well as messages of thanks by
those benefitted, further encouraged reliability.
     4. Government authorities are just as much in the dark in a
catastrophe as individuals are.  During the Los Angeles quake,
President Clinton's early information sources were his brother
and the TV news.  In Japan, at its noontime meeting, the
government still believed the number of dead to be only about
200.  To get a first-hand report, the military sent a helicopter
to videotape the damage, but it lacked telecommunications
facilities to send the recording to Tokyo. Most information
travelled up the hierarchical chains-of-command of rival
ministries and were slowly coordinated to assemble a full
official picture. Public notification was correspondingly late
and incomplete.
     Emergency communications often failed. At the Ashiya fire
department, only two telephones out of six functioned, so that
most incoming calls got a busy signal. Fire fighters could not
reach their own department, doctors, or hospitals.
     The usual response to problems of this sort is the call for
a technological fix, such as the design of a still better
communications system. Kobe illustrates the ultimate futility of
this approach. Kobe's Prefecture had installed, at considerable
expense ($80 million), a satellite communication system to
connect it to local and national government, offices and public
safety agencies.  But in the crunch the costly system was
useless. It quickly stopped working when the backup batteries ran
out, and the back-up generators overheated due to the failure of
water cooling. And the public safety organizations did not know
how to take care of the system. For example, they had no training
in how to adjust the angle of the satellite dishes once they had
been upset by the quake.  Only two calls were logged in on the
entire system on the morning of the calamity.
     5. None of this should be surprising. Governments usually
get an incomplete and often slow picture from their field agents.
Emergency systems can never be built to be fool- and disaster
proof. If anything, modern communications become more vulnerable
as their electronics are hard to fix in the field, and as they
become more dependent on outside power supply.  It is time to
learn from these experiences and revise the basic philosophy of
emergency communication. Emergencies are no time to maintain the
attitude of military-style emergency operations that keep
information close to the official vest.
     Instead of high-tech constructions, another approach is
needed -- a decentralized and open system of interconnected
computer servers, where individuals and emergency workers can
deposit and collect information about the state of their
neighborhood, family, business, and whereabouts. It would be used
by public safety agencies and insurance companies an a planning
tool, and could send messages and instructions to targeted
individuals, or areas.
     Such a "711" emergency information system (the number is
available) would permit access to an "emergency dial tone,"
enabling the access of interlincked emergency computer bulletin
boards on a priority basis, with automatic cutoff after a few
minutes. Because of its decentralization, including sites remote
from the disaster area, and "inter-net working" among multiple
carriers, the system would be less vulnerable to shock. There
could be a
schematic display of a city, block by block.  Individuals,
rescuers, non-profit organizations, and information volunteers
would log in information, whether by phone-lines, or over the
air. Much of the information would also be available to distant
parties.  The system would give news organizations detailed
information, link world-wide donors with actual needs, provide
"how-to" information, and reach specialized data bases, for
example about toxic substances.  Certain communications could
have to remain confidential or private and  require special
levels of access authorization, but that could be easily
accomplished.
     Of course, most people today do not have access to
computers, especially in an emergency. But once the immediate
calamity is over and problems of coordination displace those of
physical survival, they could call in by regular or mobile phones
to talk to volunteers supported by automatic equipment.
     In Kobe, the beginnings of such an information system are
being introduced by equipping shelters and other public places
with access to computer networks.  (Schools, in general, make
excellent emergency nodes for people services and communications-
-one reason to give them effective network links.) The Kobe city
government is now providing  public information on housing,
transportation, and schooling on the network.  Kobe residents
communicate with the world. A high school class in New York
collected donations and sent them to Kobe, after seeing pictures
of the damage on the internet.
     Who could set up such systems?  Commercial and non-profit
software developers would provide the shell that would be put by
computer networks on the net; telecommunication carriers would
offer access points and links; information volunteers would
update the system once a disaster strikes; municipalities,
community groups, and volunteer rescue organizations would
provide the basic municipal grid information which is the main
expense. Unlike the 911 service (which would continue), a 711
system requires no costly operators on duty because it would not
be a dispatch service but simply an information meeting place
into which emergency agencies can plug in.
     What is important is that, unlike the 911 system, the 711
system would not be a one-way, top-down, communications system
but a genuine interactive and horizontal communications medium
connecting citizens, their friends and relatives, and rescue
efforts.  The technology is available and affordable;  the user
base is strong and growing. And the time is here and now.


Columbia Institute for Tele-Information
Columbia Business School
809 Uris Hall
New York, NY 10027

[T] 212 854 4222
[F] 212 932 7816



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 14:18:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13755
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 14:18:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADJKwM23441
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 14:20:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJKwv23438
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 14:20:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13743
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 14:18:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJK4v23378;
	Wed, 13 Nov 2002 14:20:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJJOv23319
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 14:19:24 -0500
Received: from mail1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13687
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 14:16:46 -0500 (EST)
Received: from bgreenew2k (dhcp-10-24-19-69.cisco.com [10.24.19.69]) by mail1.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA19209; Wed, 13 Nov 2002 11:19:15 -0800 (PST)
Reply-To: <bgreene@cisco.com>
From: "Barry Raveendran Greene" <bgreene@cisco.com>
To: "RJ Atkinson" <rja@extremenetworks.com>, "Dean" <idb@tazznetworks.com>
Cc: "ieprep" <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
Date: Wed, 13 Nov 2002 11:19:08 -0800
Message-ID: <LNEHJBNJAPFNLEGJHCPEGEJNKDAA.bgreene@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <D23C17AA-F72D-11D6-91CD-00039357A82A@extremenetworks.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


What's funny is that many of the people who have been defining "voice
quality" in the standards worlds have never had to:

- talked on the phone get next to power generators and coordinate supply
delivery to a disaster area
- talked on the phone on a active evac runway working on eval logistics with
plane take off and landing
- talked on the phone next to a triage site with everyone doing their best
to keep people from dying while there is screaming and shouting trying to
get the work done

This digression on the miniscule percentage of "voice quality" in a WG
looking at insured communications during a disaster is ludicrous.

I say this as I'm talking on a INOC phone with a PG&E generator running next
to my house running device that is blowing out the water from the power
conduit. Volume and a good headset are far more important in an emergency
than a couple of packets being dropped.

> -----Original Message-----
> From: ieprep-admin@ietf.org [mailto:ieprep-admin@ietf.org]On Behalf Of
> RJ Atkinson
> Sent: Wednesday, November 13, 2002 9:32 AM
> To: Dean
> Cc: ieprep
> Subject: Re: [Ieprep] access links
>
>
>
> On Wednesday, Nov 13, 2002, at 10:30 America/Montreal, Dean wrote:
> > However, I believe that GETS service user (e.g., DISA) should tell
> > this working group what constitues acceptable voice quality (i.e.,
> > which codecs) and then it would be much easier to specify the
> > requirements.
>
> It would be useful to hear what they think.  I'd much rather see
> an abstract technical specification than a specification of certain
> existing CODECs.  One option of IETF would be for IETF to standardise
> a new CODEC (e.g. one that hypothetically would be better suited for
> real world deployed IP networks).
>
> Ran
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 14:19:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13791
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 14:19:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADJM5823559
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 14:22:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJM4v23556
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 14:22:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13787
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 14:19:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJL3v23487;
	Wed, 13 Nov 2002 14:21:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJKFv23401
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 14:20:15 -0500
Received: from marionberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13721
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 14:17:36 -0500 (EST)
Received: from cs.columbia.edu (5thnat.cise-nsf.gov [192.12.209.8])
	(user=hgs10 mech=PLAIN bits=0)
	by marionberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gADJK2qV024516
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 13 Nov 2002 14:20:03 -0500 (EST)
Message-ID: <3DD2A569.3040001@cs.columbia.edu>
Date: Wed, 13 Nov 2002 14:18:01 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Woodcock <woody@pch.net>
CC: Gary Thom <gthom@delta-info.com>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] RE: network congestion, VoIP, NCS contracting approach,
 etc.
References: <Pine.GSO.4.44.0211131054190.21062-100000@paixhost.pch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

You're assuming that the user utility function is linear. It has been 
argued that voice (and video) communications have a step utility 
function: below a certain threshold, there is zero utility. In those 
scenarios, it is indeed more effective to have fewer people each get 
above threshold than all get below the threshold.

As an example, assume that the minimum acceptable bandwidth for usable 
voice service is 10 kb/s (never mind the actual number). Assume 100 kb/s 
total. If 12 people share the bandwidth, each gets roughly 8 kb/s. 
Getting 8 kb/s isn't 80% as good as 10 kb/s, it's useless. Thus, in that 
case, it's better that you tell the two with the least valuable 
communication to wait or send email.

Bill Woodcock wrote:
>       On Wed, 13 Nov 2002, Gary Thom wrote:
>     > If there is no distinction, then when there is not enough bandwidth for all
>     > of the _best-effort_ traffic (due to congestion or damage), how does the
>     > emergency traffic get through? Is it ok to just treat it like all the other
>     > _best-effort_ traffic. At this point, doesn't best effort mean you settle
>     > for whatever you can get? Isn't there a way, under these circumstances to
>     > "better" than everyone else?
> 
> Only at the expense of likelihood of call completion.  Look at it this
> way: Under a pure best-effort situation, you can have four parties sharing
> a pie of size forty units, and each will receive a slice of size ten.
> Alternatively, under a QoS regime, four parties can share a pie of size
> eight, where one gets a slice of size eight, and three others get a slice
> of size zero.
> 
> If you're the guy who gets priority, and gets to choose which slice to
> take, would you rather choose from the set (10,10,10,10) or the set
> (8,0,0,0)?  That's what's at issue.  If you FIRST define the overall size
> of the pie as 8 (by requiring QoS) and SECOND define yourself as the guy
> who gets selection priority, you wind up with a slice (probability of call
> success) of 8.  If you FIRST define the overall size of the pie as 40 (by
> using the Internet) and SECOND take your fair share, you wind up with a
> slice of size 10, and are happier in the long run.
> 
> That assumes, however, that the ultimate goal is call success.  If the
> ultimate goal is just to feel "special" the other way around works better.
> 
>                                 -Bill
> 
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 14:45:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14752
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 14:45:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADJm2q25393
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 14:48:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJm2v25390
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 14:48:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14731
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 14:45:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJl8v25345;
	Wed, 13 Nov 2002 14:47:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJiCv25178
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 14:44:12 -0500
Received: from imo-d03.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14583
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 14:41:33 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d03.mx.aol.com (mail_out_v34.13.) id a.c9.2b948b30 (4394);
	Wed, 13 Nov 2002 14:43:27 -0500 (EST)
Message-ID: <c9.2b948b30.2b04055f@aol.com>
Date: Wed, 13 Nov 2002 14:43:27 EST
Subject: Re: [Ieprep] access links 
To: KIMBERLY.S.KING@saic.com, idb@tazznetworks.com, rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_c9.2b948b30.2b04055f_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_c9.2b948b30.2b04055f_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/13/2002 12:19:55 PM Eastern Standard Time, 
KIMBERLY.S.KING@saic.com writes:


> > However, I believe that GETS service user (e.g., DISA) should tell
> > this working group what constitues acceptable voice quality (i.e.,
> > which codecs) and then it would be much easier to specify the
> > requirements.  For example, cell phones, POTS lines and radio
> >communications have different voice quality which translates to
> >different network requirements.
> 
> Let's try to focus here.  
> 


[MAP] Yes lets address the right issue. One issue for the IETF (not IEPREP) 
is "What constitutes acceptable voice quality for general telephony users?"

For IEPREP, there should then be an understanding that the emergency user 
would usually accept a worse quality (speech transmission, as well as other 
QoS factors as mentioned in my e-mail of Nov 12), rather than have a call 
blocked. One could ask "what constitutes acceptable voice quality" for an 
emergency, but I don't think the specific numbers have any impact on the work 
of IEPREP. Only the notion that it can be worse matters. My 
draft-pierce-ieprep-pref-treat-examples describes one method by which they 
could be provided better call setup probablity while possibly trading-off 
voice quality.

Mike Pierce
Artel


--part1_c9.2b948b30.2b04055f_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/13/2002 12:19:55 PM Eastern Standard Time, KIMBERLY.S.KING@saic.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt; However, I believe that GETS service user (e.g., DISA) should tell
<BR>&gt; this working group what constitues acceptable voice quality (i.e.,
<BR>&gt; which codecs) and then it would be much easier to specify the
<BR>&gt; requirements. &nbsp;For example, cell phones, POTS lines and radio
<BR>&gt;communications have different voice quality which translates to
<BR>&gt;different network requirements.
<BR>
<BR>Let's try to focus here. &nbsp;
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] Yes lets address the right issue. One issue for the IETF (not IEPREP) is "What constitutes acceptable voice quality for general telephony users?"
<BR>
<BR>For IEPREP, there should then be an understanding that the emergency user would usually accept a worse quality (speech transmission, as well as other QoS factors as mentioned in my e-mail of Nov 12), rather than have a call blocked. One could ask "what constitutes acceptable voice quality" for an emergency, but I don't think the specific numbers have any impact on the work of IEPREP. Only the notion that it can be worse matters. My draft-pierce-ieprep-pref-treat-examples describes one method by which they could be provided better call setup probablity while possibly trading-off voice quality.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_c9.2b948b30.2b04055f_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 14:49:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14926
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 14:49:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADJq6S25661
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 14:52:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJq6v25658
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 14:52:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14904
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 14:49:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJp9v25619;
	Wed, 13 Nov 2002 14:51:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJoSv25525
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 14:50:28 -0500
Received: from imo-m07.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14818
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 14:47:49 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m07.mx.aol.com (mail_out_v34.13.) id j.120.195eb651 (4394);
	Wed, 13 Nov 2002 14:49:02 -0500 (EST)
Message-ID: <120.195eb651.2b0406ae@aol.com>
Date: Wed, 13 Nov 2002 14:49:02 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: rja@extremenetworks.com, choid@ncr.disa.mil
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_120.195eb651.2b0406ae_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_120.195eb651.2b0406ae_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/13/2002 1:17:56 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> My concern is that a lot of the things being discussed here have very
> significant implications in the operational IP network world.  It would
> be better for everyone if some of the actual DISA IP network operations
> folks were participating here on their own -- instead of having the
> somewhat disconnected DISA Centre for Standards folks doing all/most
> of the interactions.  Based on my conversations with those folks, they
> seem to share the exact concerns that Bill, Sean, and other operators
> here share.
> 


[MAP] And being a contractor for DISA rather than an employee, I hope I can 
get away with partly agreeing with you about the apparent "disconnect" 
between DISA Center for Standards and the network operations people. But I'm 
sure this is no different than in any other large carrier/network operator. 
The two organizations have different short-term missions, while the long-term 
missions are the same.

If things being discussed/proposed have very significant implications in the 
operational IP network world, I would certainly like to hear about them. I 
don't profess to know a lot about the IP world, but I can assure you that I 
don't want to push for anything that would be extremely hard to do, since I 
realize that it is unlikely to ever be completed. But so far, it seems to me 
that the comments have consisted mostly of attacks on peoples' intentions or 
intelligence, rather than simply comments on particular technical aspects of 
what was being proposed. There have also been implications of a number of 
concerns which are unfounded since no one (that I know of) was actually 
proposing some of the things being objected to.

I remain hopeful that we can address specific technical concerns with actual 
proposals that have been made.

Mike Pierce
Artel


--part1_120.195eb651.2b0406ae_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/13/2002 1:17:56 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">My concern is that a lot of the things being discussed here have very
<BR>significant implications in the operational IP network world. &nbsp;It would
<BR>be better for everyone if some of the actual DISA IP network operations
<BR>folks were participating here on their own -- instead of having the
<BR>somewhat disconnected DISA Centre for Standards folks doing all/most
<BR>of the interactions. &nbsp;Based on my conversations with those folks, they
<BR>seem to share the exact concerns that Bill, Sean, and other operators
<BR>here share.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] And being a contractor for DISA rather than an employee, I hope I can get away with partly agreeing with you about the apparent "disconnect" between DISA Center for Standards and the network operations people. But I'm sure this is no different than in any other large carrier/network operator. The two organizations have different short-term missions, while the long-term missions are the same.
<BR>
<BR>If things being discussed/proposed have very significant implications in the operational IP network world, I would certainly like to hear about them. I don't profess to know a lot about the IP world, but I can assure you that I don't want to push for anything that would be extremely hard to do, since I realize that it is unlikely to ever be completed. But so far, it seems to me that the comments have consisted mostly of attacks on peoples' intentions or intelligence, rather than simply comments on particular technical aspects of what was being proposed. There have also been implications of a number of concerns which are unfounded since no one (that I know of) was actually proposing some of the things being objected to.
<BR>
<BR>I remain hopeful that we can address specific technical concerns with actual proposals that have been made.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_120.195eb651.2b0406ae_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 15:27:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16414
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 15:27:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADKTvs27877
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 15:29:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKTvv27874
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 15:29:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16393
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 15:27:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKT3v27801;
	Wed, 13 Nov 2002 15:29:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKSZv27751
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 15:28:35 -0500
Received: from seahorse.shentel.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16299
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 15:25:55 -0500 (EST)
Received: from steves (ha96s316.d.shentel.net [204.111.97.60])
	by seahorse.shentel.net (8.11.6/8.11.6) with SMTP id gADKSOM24456;
	Wed, 13 Nov 2002 15:28:25 -0500
From: "Steve Silverman" <steves@shentel.net>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>,
        "'Dean'" <idb@tazznetworks.com>,
        "RJ Atkinson" <rja@extremenetworks.com>
Cc: "ieprep" <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
Date: Wed, 13 Nov 2002 15:28:28 -0500
Message-ID: <KMEJKAPHBBCMCDDGMBLOEEEICAAA.steves@shentel.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77967@mcl-its-exs01>
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The problem is that in a sudden emergency, there may be no time to change
codecs (so you can't talk to anyone), no time to replace or upgrade the
access link, or no additional bandwidth to purchase.  In an emergency, you
may have minutes to react. Emergencies often happen to unexpected locations
at inopportune times.
In this situation, selected users require priority so their calls are
usable.  This is the focus of some of us.

Some locations do not have access to fiber optic trunks and have limited
bandwidth.

Steve Silverman


Problem statement????  Everyone at the ETS location wants to make calls at
the same time and the access link can't handle all that voice traffic so
conversations degrade so much as to be unusable.

Potential solutions for problem...define the appropriate codecs, get a big
enough access link, provision QoS on CPE or more drastically pay for QoS to
be deployed on ISP router that faces the customer site, etc.

Defining the problem to be solved with appropriate context information would
be helpful.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 15:46:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17001
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 15:46:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADKmup29101
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 15:48:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKmuv29098
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 15:48:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16996
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 15:46:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKm3v29082;
	Wed, 13 Nov 2002 15:48:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKlwv29048
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 15:47:58 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16976
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 15:45:19 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADKfnd01858;
	Wed, 13 Nov 2002 12:41:49 -0800 (PST)
Date: Wed, 13 Nov 2002 12:41:49 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: rja@extremenetworks.com, <choid@ncr.disa.mil>, <ieprep@ietf.org>
Subject: Re: [Ieprep] Atlanta ieprep Agenda
In-Reply-To: <120.195eb651.2b0406ae@aol.com>
Message-ID: <Pine.GSO.4.44.0211131237320.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002 Mpierce1@aol.com wrote:
    > If things being discussed/proposed have very significant implications in the
    > operational IP network world, I would certainly like to hear about them. I
    > don't profess to know a lot about the IP world, but I can assure you that I
    > don't want to push for anything that would be extremely hard to do, since I
    > realize that it is unlikely to ever be completed.

This is what we've all been telling you, over, and over, and over.

QoS was a fad for about eighteen months, several years ago.  It was
excruciatingly painful, had exactly the opposite effect that its
protagonists predicted, and wasted a huge amount of everyone's effort.
Thankfully, it's well behind us, and we have a functional network again.
Except that you're attempting to bring it back to life, and staggering
around under the weight of its decaying corpse, flapping its arms and
crowing "It MUST live again!"

Yes, trashing our networks with QoS again would have significant effects.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 15:49:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17094
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 15:49:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADKpx029232
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 15:51:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKpxv29229
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 15:51:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17082
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 15:49:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKp3v29193;
	Wed, 13 Nov 2002 15:51:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKoKv29162
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 15:50:20 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17039
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 15:47:40 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADKi5d01946;
	Wed, 13 Nov 2002 12:44:05 -0800 (PST)
Date: Wed, 13 Nov 2002 12:44:05 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Steve Silverman <steves@shentel.net>
cc: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>,
        "'Dean'" <idb@tazznetworks.com>, RJ Atkinson <rja@extremenetworks.com>,
        ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
In-Reply-To: <KMEJKAPHBBCMCDDGMBLOEEEICAAA.steves@shentel.net>
Message-ID: <Pine.GSO.4.44.0211131242210.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002, Steve Silverman wrote:
    > The problem is that in a sudden emergency, there may be no time to change
    > codecs (so you can't talk to anyone), no time to replace or upgrade the
    > access link, or no additional bandwidth to purchase.  In an emergency, you
    > may have minutes to react. Emergencies often happen to unexpected locations
    > at inopportune times.
    > In this situation, selected users require priority so their calls are
    > usable.

No, some users require priority so they can feel special.  Other users
require the best-effort Internet so their calls are usable.  Which camp do
you really want to be in?

    > Some locations do not have access to fiber optic trunks and have
    > limited bandwidth.

Yes, but those people don't seem to be in yoru camp, they seem to be in
the "we'd prefer our calls to complete" camp.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 15:52:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17137
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 15:51:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADKs8V29327
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 15:54:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKs8v29324
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 15:54:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17131
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 15:51:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKm2v29066;
	Wed, 13 Nov 2002 15:48:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKluv29043
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 15:47:56 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA16973
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 15:45:16 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 13 Nov 2002 20:42:08 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WM4FQ1CR>; Wed, 13 Nov 2002 15:47:48 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D25@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        "'Dean'"
	 <idb@tazznetworks.com>,
        RJ Atkinson <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
Date: Wed, 13 Nov 2002 15:47:39 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



-----Original Message-----
From: King, Kimberly S. [mailto:KIMBERLY.S.KING@saic.com]
Sent: Wednesday, November 13, 2002 12:16 PM
To: 'Dean'; RJ Atkinson
Cc: ieprep
Subject: RE: [Ieprep] access links 



>Let's try to focus here.  

>The "voice quality" discussion, I believe, is restricted to voice quality
>over access links.  I take it we are assuming an ETS location has
contracted
>with an ISP and there is an access link between them.  It has been pointed
>out that ISPs don't often control QoS on this link.  

>Problem statement????  Everyone at the ETS location wants to make calls at
>the same time and the access link can't handle all that voice traffic so
>conversations degrade so much as to be unusable.  

>Potential solutions for problem...define the appropriate codecs, get a big
>enough access link, provision QoS on CPE or more drastically pay for QoS to
>be deployed on ISP router that faces the customer site, etc.

>Defining the problem to be solved with appropriate context information
would
>be helpful.

The problem with this is that you don't know the locations where emergency
occurs  in advance. You can't provision your access links everywhere around
the country. And that is not at all cost effective. If there is no way of
differentiating traffic, then the best effort traffic is best effort.

An
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 15:53:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17188
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 15:53:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADKu6629464
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 15:56:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKu6v29461
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 15:56:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17167
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 15:53:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKt1v29399;
	Wed, 13 Nov 2002 15:55:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADKshv29363
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 15:54:43 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17151
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 15:52:03 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 13 Nov 2002 20:52:07 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WYQLHVN5>; Wed, 13 Nov 2002 15:55:50 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D26@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock'" <woody@pch.net>, Mpierce1@aol.com
Cc: rja@extremenetworks.com, "Choi, Don" <choid@ncr.disa.mil>, ieprep@ietf.org
Subject: RE: [Ieprep] Atlanta ieprep Agenda
Date: Wed, 13 Nov 2002 15:54:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Bill,

Have you been to the NANOG web site lately? They are several presentations
on QoS given from the big guns on the last NANOG meeting. I think those guys
have problems because they choose to address it. They should copy your
network architecture as a good model when it comes to providing VoiceIP with
QoS.

Regards,

An

http://www.nanog.org

-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Wednesday, November 13, 2002 3:42 PM
To: Mpierce1@aol.com
Cc: rja@extremenetworks.com; choid@ncr.disa.mil; ieprep@ietf.org
Subject: Re: [Ieprep] Atlanta ieprep Agenda


      On Wed, 13 Nov 2002 Mpierce1@aol.com wrote:
    > If things being discussed/proposed have very significant implications
in the
    > operational IP network world, I would certainly like to hear about
them. I
    > don't profess to know a lot about the IP world, but I can assure you
that I
    > don't want to push for anything that would be extremely hard to do,
since I
    > realize that it is unlikely to ever be completed.

This is what we've all been telling you, over, and over, and over.

QoS was a fad for about eighteen months, several years ago.  It was
excruciatingly painful, had exactly the opposite effect that its
protagonists predicted, and wasted a huge amount of everyone's effort.
Thankfully, it's well behind us, and we have a functional network again.
Except that you're attempting to bring it back to life, and staggering
around under the weight of its decaying corpse, flapping its arms and
crowing "It MUST live again!"

Yes, trashing our networks with QoS again would have significant effects.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 16:17:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17892
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 16:17:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADLJx531100
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 16:19:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLJxv31097
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 16:19:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17872
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 16:17:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLJ3v31044;
	Wed, 13 Nov 2002 16:19:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLGev30877
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 16:16:40 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17736
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 16:14:00 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADLAVd02268;
	Wed, 13 Nov 2002 13:10:31 -0800 (PST)
Date: Wed, 13 Nov 2002 13:10:31 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: Mpierce1@aol.com, <rja@extremenetworks.com>,
        "Choi, Don" <choid@ncr.disa.mil>, <ieprep@ietf.org>
Subject: RE: [Ieprep] Atlanta ieprep Agenda
In-Reply-To: <Pine.GSO.4.44.0211131300420.21062-100000@paixhost.pch.net>
Message-ID: <Pine.GSO.4.44.0211131309390.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002, Bill Woodcock wrote:
    > There were no talks on QoS.

Oh, and while I'm at it, there were no talks on QoS at RIPE, APRICOT,
AfNOG, or NordNOG, either.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 16:17:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17905
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 16:17:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADLK0j31115
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 16:20:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLK0v31112
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 16:20:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17878
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 16:17:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLJ2v31024;
	Wed, 13 Nov 2002 16:19:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLEnv30819
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 16:14:49 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17722
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 16:12:08 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADL8gd02253;
	Wed, 13 Nov 2002 13:08:42 -0800 (PST)
Date: Wed, 13 Nov 2002 13:08:42 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: Mpierce1@aol.com, <rja@extremenetworks.com>,
        "Choi, Don" <choid@ncr.disa.mil>, <ieprep@ietf.org>
Subject: RE: [Ieprep] Atlanta ieprep Agenda
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D26@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211131300420.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002, Nguyen, An wrote:
    > Have you been to the NANOG web site lately?

Uh, yes, I have.  http://www.nanog.org/pc.html

    > They are several presentations on QoS given from the big guns on the
    > last NANOG meeting.

No there weren't.  I was there, and I approved each talk.  There were no
talks on QoS.

We had talks on v6, BGP stability, security, HA, metrics, tools, and
complexity reduction.  No talks on QoS.

If QoS were taken seriously by anyone, we'd have had talks on QoS.  I
think it's notable that there were four different talks on v6, and none on
QoS.  Think about the number of people for whom v6 is actually real.
Perhaps that gives you some idea of the degree to which QoS is a dead
issue.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 16:29:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18299
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 16:29:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADLW4231748
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 16:32:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLW3v31745
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 16:32:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18279
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 16:29:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLV3v31699;
	Wed, 13 Nov 2002 16:31:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLUFv31633
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 16:30:15 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18268
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 16:27:35 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Wed, 13 Nov 2002 13:26:48 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gADLRmb9015612;
	Wed, 13 Nov 2002 13:27:48 -0800 (PST)
Subject: RE: [Ieprep] RE: network congestion, VoIP, NCS contracting approa
	ch, etc.
From: Rex Buddenberg <budden@nps.navy.mil>
To: "Nguyen, An" <nguyena@ncs.gov>
Cc: "'RJ Atkinson'" <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D1F@emshqs1.ncr.disa.mil>
References: <7F18415E4D63CB45BB9B3A591F68D12D5B3D1F@emshqs1.ncr.disa.mil>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 13 Nov 2002 13:25:40 -0800
Message-Id: <1037222741.3604.584.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Wed, 2002-11-13 at 11:13, Nguyen, An wrote:

> > 
> >I believe you have your priorities in the wrong order.  
> 
> >First, is it ok to translate 'reliability' into availability (up time /
> >total time) and survivability?  
> 
> >The engineering solution to the availability problems involve multiple
> >threading (elimination of single points of failure).  In most cases,
> >this tends to result in overprovision which overtake the QoS issues.  
> 
> Actually, since reliability/availability/survivability and priority are
> related to QoS in Y.1541, they will be addressed somewhat concurrently in
> the T1 organization. At least that is the plan agreed to at the last
> meeting.


Order of business is important; if you discuss concurrently, you're
likely to get into the paralysis by analysis loop you see going on here.

Availability and survivability properly belong in one bin.  And, IMHO,
it should be the first bin.  The tools to counter Ao vulnerabilities and
those to counter survivability vulnerabilities are pretty much the
same.  The only real difference is with survivability, some Bad Guy is
killing your equipment and with Ao, you're equipment is killing itself
(maintenance-induced failures are a lesser included offense here).
  
QoS control, on the other hand, requires a different toolset.  From your
para above, it's not clear whether priority is the problem or the
solution.  If you're predetermined that it's the problem, then implement
diff-serv and caveat emptor -- you've got some folks out here warning
you that the cure may be worse than the disease.  
	What I'm suggesting is that if you appropriately solve your Ao and
survivability problems, this one may or may not exist.  


(Precise language warning: if you read, say, the Defense Science Board
literature, they lump All Of The Above into a bin called 'Security'.)  


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 16:36:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18589
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 16:36:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADLd1800333
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 16:39:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLd1v00328
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 16:39:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18572
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 16:36:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLc3v32692;
	Wed, 13 Nov 2002 16:38:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLYPv31891
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 16:34:25 -0500
Received: from imo-d08.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18390
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 16:31:45 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d08.mx.aol.com (mail_out_v34.13.) id b.12c.1b1cd6e5 (4568);
	Wed, 13 Nov 2002 16:33:38 -0500 (EST)
Message-ID: <12c.1b1cd6e5.2b041f32@aol.com>
Date: Wed, 13 Nov 2002 16:33:38 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: woody@pch.net
CC: rja@extremenetworks.com, choid@ncr.disa.mil, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_12c.1b1cd6e5.2b041f32_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_12c.1b1cd6e5.2b041f32_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/13/2002 3:48:18 PM Eastern Standard Time, woody@pch.net 
writes:


> QoS was a fad for about eighteen months, several years ago.  It was
> excruciatingly painful, had exactly the opposite effect that its
> protagonists predicted, and wasted a huge amount of everyone's effort.
> Thankfully, it's well behind us, and we have a functional network again.
> Except that you're attempting to bring it back to life, and staggering
> around under the weight of its decaying corpse, flapping its arms and
> crowing "It MUST live again!"
> 



And there have been clear comments from others who do not believe that "QoS 
is well behind us". (I presume you mean "attempts to improve QoS".) There are 
clearly others who think that efforts still need to be made to provide better 
QoS than that available from the mis-named "best effort". (See AN's e-mail of 
today.)

Mike Pierce
Artel


--part1_12c.1b1cd6e5.2b041f32_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/13/2002 3:48:18 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">QoS was a fad for about eighteen months, several years ago. &nbsp;It was
<BR>excruciatingly painful, had exactly the opposite effect that its
<BR>protagonists predicted, and wasted a huge amount of everyone's effort.
<BR>Thankfully, it's well behind us, and we have a functional network again.
<BR>Except that you're attempting to bring it back to life, and staggering
<BR>around under the weight of its decaying corpse, flapping its arms and
<BR>crowing "It MUST live again!"
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>
<BR>And there have been clear comments from others who do not believe that "QoS is well behind us". (I presume you mean "attempts to improve QoS".) There are clearly others who think that efforts still need to be made to provide better QoS than that available from the mis-named "best effort". (See AN's e-mail of today.)
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_12c.1b1cd6e5.2b041f32_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 16:41:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18846
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 16:41:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADLhfA00675
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 16:43:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLhfv00672
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 16:43:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18835
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 16:41:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLh2v00631;
	Wed, 13 Nov 2002 16:43:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADLgsv00602
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 16:42:54 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18800
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 16:40:13 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADLacd02524;
	Wed, 13 Nov 2002 13:36:38 -0800 (PST)
Date: Wed, 13 Nov 2002 13:36:38 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: rja@extremenetworks.com, <choid@ncr.disa.mil>, <ieprep@ietf.org>
Subject: Re: [Ieprep] Atlanta ieprep Agenda
In-Reply-To: <12c.1b1cd6e5.2b041f32@aol.com>
Message-ID: <Pine.GSO.4.44.0211131330570.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002 Mpierce1@aol.com wrote:
    > And there have been clear comments from others who do not believe that "QoS
    > is well behind us".

Right, they're saying "it's the future, all over again!" while holding
their noses and pretending it doesn't smell, well, a little past its
best-served-by date.

    > (I presume you mean "attempts to improve QoS".)

No, I mean that many of us implemented the regime of practices and
protocols referred to as QoS on our networks.  This did not
improve lower-case-q quality; quite the opposite.

    > There are clearly others who think that efforts still need to be
    > made to provide better QoS

Do you mean "There are clearly others who think that efforts need to be
made again to provide QoS" or "There are clearly others who think that
efforts still need to be made to provide better quality?"  These are, of
course, both true, and in opposition.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 17:14:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20128
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 17:14:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADMGh403447
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 17:16:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADMGhv03444
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 17:16:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20120
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 17:14:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADMG3v03415;
	Wed, 13 Nov 2002 17:16:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADMFJv03377
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 17:15:19 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20094
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 17:12:38 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Wed, 13 Nov 2002 14:11:52 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gADMBNb9017747;
	Wed, 13 Nov 2002 14:11:23 -0800 (PST)
Subject: Re: [Ieprep] Atlanta ieprep Agenda
From: Rex Buddenberg <budden@nps.navy.mil>
To: Mpierce1@aol.com
Cc: woody@pch.net, rja@extremenetworks.com, choid@ncr.disa.mil,
        ieprep@ietf.org
In-Reply-To: <12c.1b1cd6e5.2b041f32@aol.com>
References: <12c.1b1cd6e5.2b041f32@aol.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 13 Nov 2002 14:09:14 -0800
Message-Id: <1037225355.3604.589.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

You're confusing:

QoS -- experienced quality of service which can be measured by
parameters such as jitter, latency, determinism and throughput.

and

QoS control -- which is a means to optimizing one of the QoS terms ...
inevitably at the expense of at least one of the others.

---

On Wed, 2002-11-13 at 13:33, Mpierce1@aol.com wrote:

<snip>
> 
> 
> And there have been clear comments from others who do not believe that "QoS 
> is well behind us". (I presume you mean "attempts to improve QoS".) There are 
> clearly others who think that efforts still need to be made to provide better 
> QoS than that available from the mis-named "best effort". (See AN's e-mail of 
> today.)
> 


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 18:34:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21784
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 18:34:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADNb7o07407
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 18:37:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADNb7v07404
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 18:37:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21762
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 18:34:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADNa6v07124;
	Wed, 13 Nov 2002 18:36:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADNZsv07109
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 18:35:54 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21732
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 18:33:12 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gADNTnd03395
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 15:29:49 -0800 (PST)
Date: Wed, 13 Nov 2002 15:29:49 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: ieprep@ietf.org
Message-ID: <Pine.GSO.4.44.0211131522520.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] Qualitative statement about quality
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


For what it's worth, the CALREN2 folks asked us to talk about the INOC-DBA
phones at their meeting this afternoon, and we presented the talk by phone
from Nairobi.  The CALREN2 guys did a qualitative comparison between voice
quality on the VoIP phones between San Luis Obispo and Nairobi versus
voice quality on PSTN phones between San Luis Obispo and Berkeley, and
determined that the VoIP connection was far better, qualitatively.
Latency on the VoIP connection was hovering in the 600ms range, with about
6% loss.  Conversation was about 30 minutes long.  These were their
measurements and evaluation, not mine, and these are people who know what
they're talking about in both data and voice arenas.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 18:37:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21829
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 18:37:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADNe1V07871
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 18:40:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADNe1v07868
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 18:40:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21822
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 18:37:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADNd2v07797;
	Wed, 13 Nov 2002 18:39:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADNcLv07769
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 18:38:21 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21799
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 18:35:39 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Wed, 13 Nov 2002 18:37:52 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111318375832582
 ; Wed, 13 Nov 2002 18:37:58 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <W5YTX1GD>; Wed, 13 Nov 2002 18:39:20 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77978@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Nguyen, An '" <nguyena@ncs.gov>,
        "''King, Kimberly  S.' '" <KIMBERLY.S.KING@saic.com>,
        "''Dean' '" <idb@tazznetworks.com>,
        "'RJ Atkinson '" <rja@extremenetworks.com>
Cc: "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
Date: Wed, 13 Nov 2002 18:37:58 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

An said:
>The problem with this is that you don't know the locations where
>emergency occurs  in advance. You can't provision your access links
>everywhere around the country. And that is not at all cost effective. 
>If there is no way of differentiating traffic, then the best effort
>traffic is best effort.

I read this statement as best effort transport is sufficient due to the
infeasibility of providing anything different.  

Those apposing the statement, please provide a feasible alternative.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 20:09:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23405
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 20:09:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAE1Bcp12470
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 20:11:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE1Bcv12467
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 20:11:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23401
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 20:08:57 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE1AJv12444;
	Wed, 13 Nov 2002 20:10:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE19Fv12394
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 20:09:15 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23375
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 20:06:33 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 14 Nov 2002 01:03:24 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WM4FQKBW>; Wed, 13 Nov 2002 20:09:08 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D28@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Rex Buddenberg'" <budden@nps.navy.mil>
Cc: "'RJ Atkinson'" <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
Date: Wed, 13 Nov 2002 20:09:03 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Ieprep] RE: [I prep] RE: network congestion, VoIP, NCS contracting approa
 ch, etc.
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Rex,

Agreed with you on this. What I meant to say was that T1 attempts to address
some of the fourteen requirements for ETS in the 
NSTAC(National Security Telecommunications Advisory Committee to the
President) report. Reliability, availability and priority are some of those
requirements. We have not addressed any of those yet, and have not assigned
any priority to them yet. Your comments are well-taken.

Thanks,

An
-----Original Message-----
From: Rex Buddenberg [mailto:budden@nps.navy.mil]
Sent: Wednesday, November 13, 2002 4:26 PM
To: Nguyen, An
Cc: 'RJ Atkinson'; ieprep
Subject: RE: [Ieprep] RE: network congestion, VoIP, NCS contracting
approa ch, etc.


On Wed, 2002-11-13 at 11:13, Nguyen, An wrote:

> > 
> >I believe you have your priorities in the wrong order.  
> 
> >First, is it ok to translate 'reliability' into availability (up time /
> >total time) and survivability?  
> 
> >The engineering solution to the availability problems involve multiple
> >threading (elimination of single points of failure).  In most cases,
> >this tends to result in overprovision which overtake the QoS issues.  
> 
> Actually, since reliability/availability/survivability and priority are
> related to QoS in Y.1541, they will be addressed somewhat concurrently in
> the T1 organization. At least that is the plan agreed to at the last
> meeting.


Order of business is important; if you discuss concurrently, you're
likely to get into the paralysis by analysis loop you see going on here.

Availability and survivability properly belong in one bin.  And, IMHO,
it should be the first bin.  The tools to counter Ao vulnerabilities and
those to counter survivability vulnerabilities are pretty much the
same.  The only real difference is with survivability, some Bad Guy is
killing your equipment and with Ao, you're equipment is killing itself
(maintenance-induced failures are a lesser included offense here).
  
QoS control, on the other hand, requires a different toolset.  From your
para above, it's not clear whether priority is the problem or the
solution.  If you're predetermined that it's the problem, then implement
diff-serv and caveat emptor -- you've got some folks out here warning
you that the cure may be worse than the disease.  
	What I'm suggesting is that if you appropriately solve your Ao and
survivability problems, this one may or may not exist.  


(Precise language warning: if you read, say, the Defense Science Board
literature, they lump All Of The Above into a bin called 'Security'.)  

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 20:38:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23995
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 20:38:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAE1etM14194
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 20:40:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE1etv14191
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 20:40:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23991
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 20:38:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE1e5v14158;
	Wed, 13 Nov 2002 20:40:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE1dGv14080
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 20:39:16 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23969
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 20:36:35 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <QXJ5FW96>; Wed, 13 Nov 2002 20:36:57 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A414959@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Bill Woodcock'" <woody@pch.net>,
        "Garrity, Jack"
	 <JOHN.J.GARRITY@saic.com>
Cc: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion reque
	st
Date: Wed, 13 Nov 2002 20:36:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

I'm wading through a weeks's worth of email, so this may have already been
addressed.

I think the initial concern is about IP networks within the core of networks
offered by the IXC carriers with whom the NCS already has contractual
relationships for GETS and GETS-like services.

-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Tuesday, November 12, 2002 11:10 AM
To: Garrity, Jack
Cc: 'Ken Carlberg'; ieprep
Subject: RE: [Ieprep] ieprep-requirements-01 - reqs 1-5 - discussion
request


      On Tue, 12 Nov 2002, Garrity, Jack wrote:
    > For the scenario you describe, the NS/EP codepoint and NS/EP features
take
    > effect at GETS-capable local exchanges.  Those exchanges serve over X
    > percent of US-based access lines, where X is on the order of 85
percent or
    > greater.
    > If the terminating local exchange is GETS-capable (same switches
    > as in the first paragraph), NS/EP features have effect.

So about 70% of U.S. domestic source-destination pairs are covered.  Since
as has been pointed out many times recently, there's no practical way of
distinguishing national borders on the Internet, I don't have
U.S.-specific figures.  However, if the DoD purchased GETS-like services
from the dozen or so usual suspects globally, they'd have only about 4%
coverage.  (20% of 20%, rather than 85% of 85%).  There are a _lot_ of
ISPs, and the large ones aren't that large relative to the whole.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 21:13:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24686
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 21:13:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAE2GAc16253
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 21:16:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE2GAv16249
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 21:16:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24681
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 21:13:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE2F8v16218;
	Wed, 13 Nov 2002 21:15:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE2EPv16180
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 21:14:25 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24644
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 21:11:43 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <QXJ5FW02>; Wed, 13 Nov 2002 21:12:06 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A41495B@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Dean'" <idb@tazznetworks.com>, RJ Atkinson <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
Date: Wed, 13 Nov 2002 21:11:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Whether or not you believe that NCS should be considered part of DoD, it
should be VERY clear that:

The vast majority of GETS service users have NOTHING to do with DoD or DISA.
In fact, I heard some numbers recently that indicate that a very tiny
proportion of the issued GETS cards have gone to DoD.

-----Original Message-----
From: Dean [mailto:idb@tazznetworks.com]
Sent: Wednesday, November 13, 2002 10:30 AM
To: RJ Atkinson
Cc: Dean; ieprep
Subject: Re: [Ieprep] access links 

However, I believe that GETS service user (e.g., DISA)...

Dean
idb@tazznetworks.com

===============================================
I like to share my ignorance. I have enough.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 21:39:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25609
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 21:39:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAE2fmA17877
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 21:41:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE2fmv17874
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 21:41:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25606
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 21:39:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE2f5v17842;
	Wed, 13 Nov 2002 21:41:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE2eOv17808
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 21:40:24 -0500
Received: from volta.tazznetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25573
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 21:37:41 -0500 (EST)
Received: from volta.tazznetworks.com (localhost.tazznetworks.com [127.0.0.1])
	by volta.tazznetworks.com (8.12.6/8.12.3) with ESMTP id gAE2bvFf000566;
	Wed, 13 Nov 2002 21:37:57 -0500 (EST)
	(envelope-from idb@volta.tazznetworks.com)
Message-Id: <200211140237.gAE2bvFf000566@volta.tazznetworks.com>
To: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>
cc: "'Nguyen, An '" <nguyena@ncs.gov>, "''Dean' '" <idb@tazznetworks.com>,
        "'RJ Atkinson '" <rja@extremenetworks.com>,
        "'ieprep '" <ieprep@ietf.org>
Subject: Re: [Ieprep] access links 
In-Reply-To: Your message of "Wed, 13 Nov 2002 18:37:58 EST."
             <B8030EB94AF1D51196D70002A589D64207E77978@mcl-its-exs01> 
User-Agent: EMH/1.10.0 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?UTF-8?B?VW5l?=
 =?UTF-8?B?Ymlnb3J58m1hZQ==?=) APEL/10.3 Emacs/21.2 (i386--freebsd) (with
 unibyte mode)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
X-Mailer: mh-e 6.1; nmh 1.0.4; Emacs 21.2
Date: Wed, 13 Nov 2002 21:37:57 -0500
From: Dean <idb@tazznetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Here is a document which is showing some analysis on codec and
packetloss.

http://www.globalipsound.com/newsroom/white_papers/gips_evaluation.pdf


Dean
idb@tazznetworks.com

===============================================
I like to share my ignorance. I have enough.

> An said:
> >The problem with this is that you don't know the locations where
> >emergency occurs  in advance. You can't provision your access links
> >everywhere around the country. And that is not at all cost effective. 
> >If there is no way of differentiating traffic, then the best effort
> >traffic is best effort.
> 
> I read this statement as best effort transport is sufficient due to the
> infeasibility of providing anything different.  
> 
> Those apposing the statement, please provide a feasible alternative.
> 
> Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 22:15:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26084
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 22:15:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAE3I9U19637
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 22:18:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE3I9v19634
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 22:18:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26074
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 22:15:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE3HCv19593;
	Wed, 13 Nov 2002 22:17:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE3G4v19568
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 22:16:04 -0500
Received: from sparcticus.sysctl.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26047
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 22:13:21 -0500 (EST)
Received: from localhost (scott@localhost)
	by sparcticus.sysctl.net (8.10.1/8.10.1) with ESMTP id gAE3EkG16446;
	Thu, 14 Nov 2002 03:14:47 GMT
Date: Thu, 14 Nov 2002 03:14:45 +0000 (GMT)
From: Scott Madley <scott@xgcic.net>
X-X-Sender:  <scott@sparcticus.sysctl.net>
To: Sean Donelan <sean@donelan.com>
cc: Bill Woodcock <woody@pch.net>, <ieprep@ietf.org>
Subject: Re: [Ieprep] Dolby-quality cell phones versus IP telephony
In-Reply-To: <Pine.GSO.4.44.0211101734400.16499-100000@clifden.donelan.com>
Message-ID: <Pine.BSO.4.33.0211140156200.6745-100000@sparcticus.sysctl.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



On Sun, 10 Nov 2002, Sean Donelan wrote:

> On Sun, 10 Nov 2002, Bill Woodcock wrote:
> > My experience with intra-PSTN-telco interconnects is admittedly quite
> > limited, but what of it that I've observed has been fairly heavily
> > dependent upon Nx chan-DS1 interconnects, at 24 call appearances each.  By
> > comparison, Internet peering connections are typically GigE, which,
> > running at 70% capacity, would carry about 65,000 call appearances each.
>

Typical interconnects are of the DS1 variety, however depending on the
trunking need and the desired call-routing architecture ILEC's do hand
off on the DS3 level towards each other.  Individual DS0's in a trunk-grp are
referred to a members, and a DS1 compromised of 24 DS0's is referred to as
a span.  High-Capacity Trunk Groups between tandem locations usually
compromise 20+ individual T1's.

The beauty of the Internet is that we have an in-band messaging system to
exchange routing information via BGP4.  The PSTN still operates on a 56K
based system.  So if I can't send an IAM to the far-end switch I can't set
up the end to end circuit in order to complete the call.  Which brings up
the premise if you can't signal, you can't connect.

> As I understand the problem, its not the number of calls which is limited
> by the trunking capacity, but the number of call attempts and not
> implementing congestion controls on the NGN side.  Its like when concert
> tickets go on sale in a major city, and everyone starts calling the box
> office at the same time swamping the PSTN.  Even though 99% of the calls
> don't go through, the call attempts still disrupt PSTN service elsewhere.

The problem isn't trunking or lack of trunking, but rather saturation to a
particular DN that is being called.  A properly engineered PSTN network
will have main trunk groups to each CO homed off a tandem location, in
addition to alternate routing that will use additional trunk-groups
transversing different CO's in the event of saturation.  I don't know if I
would consider a scenario such as the above, a real-world case of
congestion or degradation of the PSTN.  During an emergency scenario,
outbound/inbound calling would increase to a variety of DN's, not just one
in particular, thus taxing all trunk-grps, not just the one's associated
(primary/secondary/tertiary/etc) with routing to a select DN.

-Scott


>
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 13 23:57:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29744
	for <ieprep-archive@odin.ietf.org>; Wed, 13 Nov 2002 23:57:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAE4xuq24693
	for ieprep-archive@odin.ietf.org; Wed, 13 Nov 2002 23:59:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE4xtv24690
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 23:59:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29727
	for <ieprep-web-archive@ietf.org>; Wed, 13 Nov 2002 23:57:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE4xDv24681;
	Wed, 13 Nov 2002 23:59:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE4wJv24643
	for <ieprep@optimus.ietf.org>; Wed, 13 Nov 2002 23:58:19 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA29720
	for <ieprep@ietf.org>; Wed, 13 Nov 2002 23:55:34 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 14 Nov 2002 04:55:39 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WYQLH95A>; Wed, 13 Nov 2002 23:59:22 -0500
Message-ID: <B3FE60C05AD31D4C96E07EBC5000639E1D7F7C@EMSHQS2>
From: "Choi, Don" <choid@ncr.disa.mil>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>, Mpierce1@aol.com
Subject: RE: [Ieprep] Atlanta ieprep Agenda
Date: Wed, 13 Nov 2002 23:58:05 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ran,

The requirement is valid. It came from JCS. I do know what more I can say
about this to convince you.
Lack of VOIP standards that support "assured service (MLPP)" is one of the
major reasons why VOIP is not permitted to be deployed. 

I do not think there is anyone in DISA, DISN IP folks or DSN folks, who
believe assured service is not a requirement. And this "Assured Service"
requirement is being expanded to all DISN, including DISN IP. So, please
check your sources in DISA again on this.  

We are not working in vacuum. We are working with Network Services folks,
who are responsible for DISN.
We participate in DSN VOIP Working Group meetings, DoD VOIP Summit meetings
and DoD QoS/CoS Working Group meetings to update on our progress in VOIP
standards. They are aware what is going on in IETF and expect IETF to
develop VOIP standards that support our needs.

And this requirement is not just for U.S. Our NATO allies have a similar
requirement. I believe other countries have this requirement also.

Don



-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Wednesday, November 13, 2002 12:29 PM
To: Choi, Don
Cc: ieprep; Mpierce1@aol.com
Subject: Re: [Ieprep] Atlanta ieprep Agenda



That helps, but the DISN IP folks also claim that JCS has explicitly
prohibited them from deploying those kinds of features until DISA
can prove to satisfaction of JCS that such is reasonable/appropriate.

Other folks in the DSN part of DISA are quick to point out that JCS
has also said that DoD is not permitted to deploy VoIP except if a
specific case-by-case waiver is obtained from JCS -- and they also
tell me that such waivers are extremely rare (Skyline being the primary
example of a waiver being granted -- and the negative parts of the
Skyline experience apparently have been heard clearly at JCS).

My concern is that a lot of the things being discussed here have very
significant implications in the operational IP network world.  It would
be better for everyone if some of the actual DISA IP network operations
folks were participating here on their own -- instead of having the
somewhat disconnected DISA Centre for Standards folks doing all/most
of the interactions.  Based on my conversations with those folks, they
seem to share the exact concerns that Bill, Sean, and other operators
here share.

Ran

On Tuesday, Nov 12, 2002, at 22:52 America/Montreal, Choi, Don wrote:
> You are right that the current DISN IP networks do not have many of the
> requirements we are discussing here. And this may change for the DISN 
> IP
> networks.
>
> However, an important point is that DSN (voice network) has all these
> requirements right now, and these requirements have to be supported 
> for DSN
> to migrate from TDM to IP.
>
> Hope this explains the disconnect.
>
> Don
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 04:21:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13827
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 04:21:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAE9O1J14895
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 04:24:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE9O1v14892
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 04:24:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13823
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 04:21:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE9N5v14866;
	Thu, 14 Nov 2002 04:23:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE9Mpv14845
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 04:22:51 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13813
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 04:20:04 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAE9Gdd08347;
	Thu, 14 Nov 2002 01:16:39 -0800 (PST)
Date: Thu, 14 Nov 2002 01:16:39 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: Gary Thom <gthom@delta-info.com>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] RE: network congestion, VoIP, NCS contracting approach,
 etc.
In-Reply-To: <3DD2A569.3040001@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211140113000.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002, Henning Schulzrinne wrote:
    > As an example, assume that the minimum acceptable bandwidth for usable
    > voice service is 10 kb/s (never mind the actual number). Assume 100 kb/s
    > total. If 12 people share the bandwidth, each gets roughly 8 kb/s.
    > Getting 8 kb/s isn't 80% as good as 10 kb/s, it's useless. Thus, in that
    > case, it's better that you tell the two with the least valuable
    > communication to wait or send email.

You miss my point.  The point is that in running QoS in an attempt to be
special, you destroy so much of the resource through fragility that there
isn't enough left for even one user to get a call through.  The resource
here isn't capacity, it's availability.  You guys keep arguing about
capacity, as though it's in short supply, but indestructible, when in fact
the opposite is the case: it's plentiful, but fragile.  The way you make
it go away completely (i.e. no calls get completed at all, regardless of
"specialness") is to complexify the delivery system.  If you don't throw
QoS into the mix, there'll be plenty of bandwidth for everyone.  If you
do throw it in, nobody gets anything.  Simplifying radically for
rhetorical purpose here, of course.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 05:31:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14933
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 05:31:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEAXs418511
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 05:33:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEAXrv18508
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 05:33:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14929
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 05:31:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEAX4v18491;
	Thu, 14 Nov 2002 05:33:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEAWtv18462
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 05:32:55 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA14907
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 05:30:19 -0500 (EST)
Received: from posh.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.15106-0@bells.cs.ucl.ac.uk>; Thu, 14 Nov 2002 10:32:47 +0000
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: bgreene <bgreene@cisco.com>
cc: "'ieprep'" <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: more process discussion
In-reply-to: Your message of "Wed, 13 Nov 2002 10:58:51 PST." <LNEHJBNJAPFNLEGJHCPEAEJKKDAA.bgreene@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 14 Nov 2002 10:32:46 +0000
Message-ID: <666.1037269966@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> Honestly, from what I've seen over the past three weeks demonstrates that
> this WG is dead. The way correspondence is flowing shows me that rough
> consensus is not going to be reached. At best, some informational RFCs will
> be published which could be used for RFPs. But those would be little
> different from the work done already to support contractual SLAs.

<non-technical-comments>...feel free to hit the delete key

there are 3 basic discussions going on.  the first involves actual 
drafts, and there is agreement that various amounts of work need to 
be done to some of these.  thats normal.  hopefully, we can reach
consensus on Henning's SIP requirements draft and wave bon voyage as
we send it packing to SIPPING :-).  as for some of the other drafts,
some clarifications (and in one or two cases, possibly major surgery)
needs to be done.  regardless, all these other drafts are to be 
Informational and are not to offer a specific solution (see previous 
N messages in the Archive on what the charter is).

the second set of discussions revolve around what I would consider are
solutions.  here the contention level increases dramatically and some
of the comments/arguements are looking a bit circular (ie, deja vu), but 
one can still extract nuggets of good/inciteful information.  i tend to
keep thinking "one size does not fit all" when reading a number of these
messages, but everyone can take from it what they will.

the third set of messages, are the ones that don't apply to the first
two above, and I shall leave it at that.  for those that are newbies, 
this happens on occasion.

in the end, the main output and concern of the ADs/Chairs/group are
the Informational drafts.  everything else is a bonus :-)

</non-technical-comments>

cheers,

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 07:37:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17254
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 07:37:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAECe1F25813
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 07:40:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAECe1v25810
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 07:40:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17237
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 07:37:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAECd6v25753;
	Thu, 14 Nov 2002 07:39:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAECcgv25695
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 07:38:42 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17215
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 07:36:05 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAECWdd10047;
	Thu, 14 Nov 2002 04:32:39 -0800 (PST)
Date: Thu, 14 Nov 2002 04:32:39 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
cc: "'Dean'" <idb@tazznetworks.com>, RJ Atkinson <rja@extremenetworks.com>,
        ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
In-Reply-To: <CBED705A7FD2D311865500508B1089410A41495B@chntex02.is.dyncorp.com>
Message-ID: <Pine.GSO.4.44.0211131816430.21062-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 13 Nov 2002, Gunn, Janet wrote:
    > The vast majority of GETS service users have NOTHING to do with DoD or DISA.
    > In fact, I heard some numbers recently that indicate that a very tiny
    > proportion of the issued GETS cards have gone to DoD.

Unfortunately, GETS users are unrepresented here, a point which I believe
Rex has been making.  What we've got instead is the GETS purchasing agent,
in effect, which may or may not have radically different values than the
users themselves.

I think part of Rex's point is that if the GETS users had a voice here,
they'd be asking for a less expensive solution that would provide
functionality more of the time..

                                -Bill




_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 08:45:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18626
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 08:45:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEDllS29774
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 08:47:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEDlkv29771
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 08:47:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18616
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 08:45:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEDl4v29757;
	Thu, 14 Nov 2002 08:47:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEDk4v29681
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 08:46:04 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18578
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 08:43:28 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Thu, 14 Nov 2002 08:45:38 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111408454527180
 ; Thu, 14 Nov 2002 08:45:45 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <W5YTXHT8>; Thu, 14 Nov 2002 08:47:07 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64231E550@mcl-its-exs01>
From: "Garrity, Jack" <JOHN.J.GARRITY@saic.com>
To: "'Choi, Don'" <choid@ncr.disa.mil>
Cc: ieprep <ieprep@ietf.org>, Mpierce1@aol.com,
        "'RJ Atkinson'" <rja@extremenetworks.com>
Subject: RE: [Ieprep] Atlanta ieprep Agenda
Date: Thu, 14 Nov 2002 08:45:44 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Don,

Words matter, especially on this discussion list.  A JCS-validated
requirement is not necessarily a valid requirement.

~~~ Jack ~~~
Work: 703/676-2358 | Fax: 703/848-0299
Home: 703/278-9250 | Cell: 703/508-0065
E-mail: garrityj@saic.com


-----Original Message-----
From: Choi, Don [mailto:choid@ncr.disa.mil]
Sent: Wednesday, November 13, 2002 11:58 PM
To: 'RJ Atkinson'
Cc: ieprep; Mpierce1@aol.com
Subject: RE: [Ieprep] Atlanta ieprep Agenda


Ran,

The requirement is valid. It came from JCS. I do know what more I can say
about this to convince you.
Lack of VOIP standards that support "assured service (MLPP)" is one of the
major reasons why VOIP is not permitted to be deployed. 

I do not think there is anyone in DISA, DISN IP folks or DSN folks, who
believe assured service is not a requirement. And this "Assured Service"
requirement is being expanded to all DISN, including DISN IP. So, please
check your sources in DISA again on this.  

We are not working in vacuum. We are working with Network Services folks,
who are responsible for DISN.
We participate in DSN VOIP Working Group meetings, DoD VOIP Summit meetings
and DoD QoS/CoS Working Group meetings to update on our progress in VOIP
standards. They are aware what is going on in IETF and expect IETF to
develop VOIP standards that support our needs.

And this requirement is not just for U.S. Our NATO allies have a similar
requirement. I believe other countries have this requirement also.

Don



-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Wednesday, November 13, 2002 12:29 PM
To: Choi, Don
Cc: ieprep; Mpierce1@aol.com
Subject: Re: [Ieprep] Atlanta ieprep Agenda



That helps, but the DISN IP folks also claim that JCS has explicitly
prohibited them from deploying those kinds of features until DISA
can prove to satisfaction of JCS that such is reasonable/appropriate.

Other folks in the DSN part of DISA are quick to point out that JCS
has also said that DoD is not permitted to deploy VoIP except if a
specific case-by-case waiver is obtained from JCS -- and they also
tell me that such waivers are extremely rare (Skyline being the primary
example of a waiver being granted -- and the negative parts of the
Skyline experience apparently have been heard clearly at JCS).

My concern is that a lot of the things being discussed here have very
significant implications in the operational IP network world.  It would
be better for everyone if some of the actual DISA IP network operations
folks were participating here on their own -- instead of having the
somewhat disconnected DISA Centre for Standards folks doing all/most
of the interactions.  Based on my conversations with those folks, they
seem to share the exact concerns that Bill, Sean, and other operators
here share.

Ran

On Tuesday, Nov 12, 2002, at 22:52 America/Montreal, Choi, Don wrote:
> You are right that the current DISN IP networks do not have many of the
> requirements we are discussing here. And this may change for the DISN 
> IP
> networks.
>
> However, an important point is that DSN (voice network) has all these
> requirements right now, and these requirements have to be supported 
> for DSN
> to migrate from TDM to IP.
>
> Hope this explains the disconnect.
>
> Don
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 09:17:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19804
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 09:17:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEEJPV31541
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 09:19:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEJPv31538
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 09:19:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19799
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 09:16:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEIDv31478;
	Thu, 14 Nov 2002 09:18:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEECJv31247
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 09:12:19 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19355
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 09:09:43 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAEEC6eS013001;
	Thu, 14 Nov 2002 09:12:06 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAEEC5H9007271
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 14 Nov 2002 09:12:06 -0500 (EST)
Message-ID: <3DD3AF24.9070900@cs.columbia.edu>
Date: Thu, 14 Nov 2002 09:11:48 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>
CC: "'ieprep '" <ieprep@ietf.org>
Subject: Re: [Ieprep] access links
References: <B8030EB94AF1D51196D70002A589D64207E77978@mcl-its-exs01>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77978@mcl-its-exs01>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> I read this statement as best effort transport is sufficient due to the
> infeasibility of providing anything different.
>
> Those apposing the statement, please provide a feasible alternative.


It is pretty clear that there are alternatives. The alternatives may not 
be deployed, due to engineering trade-offs or may only be feasible in 
certain parts of the network (generally, access links). As has been 
noted before, like all tools, one has to select the appropriate area of 
application. What may be helpful for a T1 link may be deadly for an 
OC-192 backbone link. For example, IntServ and DiffServ may not scale or 
may operationally infeasible in a backbone network. This says little 
about a link controlled by a single organization. This should all be 
patently obvious, but we seem to go in circles of "I don't need it, so 
nobody needs it" or "I think I need it, so everybody needs to do it".

http://www.cisco.com/en/US/tech/tk652/tk698/technologies_tech_note09186a0080094660.shtml
http://www.nwfusion.com/news/2002/129521_01-28-2002.html
http://www.sprintlink.net/faq/CoS_FAQ.htm  (Sprint access link 
prioritization)
http://www.juniper.net/techcenter/techpapers/200011-05.html
http://www.bcr.com/access/2000/03/p20s1.asp
http://newsroom.cisco.com/dlls/ts_092702.html
http://www.fcw.com/fcw/articles/2000/0918/tec-voip-09-18-00.asp (Navy VoIP)
http://www.networking.ibm.com/voice/integration.html
http://www1.avaya.com/enterprise/whitepapers/r300cisco.pdf
http://www.oecd.org/pdf/M00003000/M00003121.pdf (QoS mentioned by a 
provider - must be marketing :-))
http://www.genuity.com/announcements/news/press_release_20021023-01.xml 
("Genuity Inc., a leading provider of enterprise Internet Protocol (IP) 
networking services, today announced the availability of its Quality of 
Service (QoS) offering, a managed solution that enhances the performance 
of high-speed Internet access. This new Differentiated Services-based 
(DiffServ) QoS solution allows an enterprise to prioritize the delivery 
of voice, data, and interactive media traffic between its physical 
office locations that are connected to Genuity's IP-based network.")

are random Google-induced examples that are not academic. From a quick 
read, all of them, except possibly the Genuity example, are either for 
access links or VPNs. This is a pretty random selection, so my apologies 
if I left out your favorite equipment or service provider.

>
>
> Kimberly
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 09:20:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19974
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 09:20:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEEN3031863
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 09:23:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEN3v31860
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 09:23:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19963
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 09:20:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEM4v31750;
	Thu, 14 Nov 2002 09:22:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEKhv31609
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 09:20:43 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA19838
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 09:18:07 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 14 Nov 2002 14:18:09 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <W7MR3KLT>; Thu, 14 Nov 2002 09:21:54 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D2A@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock'" <woody@pch.net>,
        Henning Schulzrinne
	 <hgs@cs.columbia.edu>
Cc: Gary Thom <gthom@delta-info.com>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] RE: network congestion, VoIP, NCS contracting approa
	ch, etc.
Date: Thu, 14 Nov 2002 09:20:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Thursday, November 14, 2002 4:17 AM
To: Henning Schulzrinne
>If you don't throw
>QoS into the mix, there'll be plenty of bandwidth for everyone.  If you
>do throw it in, nobody gets anything.  Simplifying radically for
>rhetorical purpose here, of course.


I don't understand your logic here. Suppose you have a T1 pipe (~1.5
Mbits/sec)and you want to carry G.711 voiceIP calls. With overhead, each
call takes ~ 80 Kbits. You can serve roughly 1540/80 = 19 calls. So you have
QoS implemented in your network, you can still have 19 calls worth of
revenue. You indicated that with QoS your T1 pipe gets smaller; thereby,
supporting less voice calls. 

By the way, you can charge your customers more if they want QoS for their
service. You can always charge more for emergency personnel when they use
you priority service.  Attached is the link you should check it out for
yourself. http://www.genuity.com/services/access/ia/qos.htm

Regards,

An
    
                             


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 09:21:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20008
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 09:21:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEENuW31913
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 09:23:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEENtv31910
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 09:23:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19992
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 09:21:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEN2v31852;
	Thu, 14 Nov 2002 09:23:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEMvv31830
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 09:22:57 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19956
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 09:20:20 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAEEGjd11294;
	Thu, 14 Nov 2002 06:16:45 -0800 (PST)
Date: Thu, 14 Nov 2002 06:16:45 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: Henning Schulzrinne <hgs@cs.columbia.edu>,
        Gary Thom <gthom@delta-info.com>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] RE: network congestion, VoIP, NCS contracting approa
 ch, etc.
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D2A@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211140615500.11206-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 14 Nov 2002, Nguyen, An wrote:
    > You indicated that with QoS your T1 pipe gets smaller

No, I said that it stays the same size, but is less likely to function.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 09:33:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20380
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 09:33:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEEZkC32405
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 09:35:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEZkv32402
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 09:35:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20375
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 09:33:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEZ2v32384;
	Thu, 14 Nov 2002 09:35:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEYfv32343
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 09:34:41 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA20331
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 09:32:04 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 14 Nov 2002 14:32:07 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <W7MR3KSF>; Thu, 14 Nov 2002 09:35:52 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D2C@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>
Cc: "'ieprep '" <ieprep@ietf.org>, "''Dean' '" <idb@tazznetworks.com>,
        "'RJ Atkinson '" <rja@extremenetworks.com>
Subject: RE: [Ieprep] access links 
Date: Thu, 14 Nov 2002 09:34:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Sorry I did not make it clear! What I really meant was the best effort is
not enough for emergency traffic because of the "best effort" nature in the
IP networks.

An

-----Original Message-----
From: King, Kimberly S. [mailto:KIMBERLY.S.KING@saic.com]
Sent: Wednesday, November 13, 2002 6:38 PM
To: 'Nguyen, An '; ''King, Kimberly S.' '; ''Dean' '; 'RJ Atkinson '
Cc: 'ieprep '
Subject: RE: [Ieprep] access links 


An said:
>The problem with this is that you don't know the locations where
>emergency occurs  in advance. You can't provision your access links
>everywhere around the country. And that is not at all cost effective. 
>If there is no way of differentiating traffic, then the best effort
>traffic is best effort.

I read this statement as best effort transport is sufficient due to the
infeasibility of providing anything different.  

Those apposing the statement, please provide a feasible alternative.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 09:36:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20442
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 09:36:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEEcdm00632
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 09:38:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEcdv00629
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 09:38:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20436
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 09:36:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEc1v00608;
	Thu, 14 Nov 2002 09:38:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEbdv00586
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 09:37:39 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA20399
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 09:35:02 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 14 Nov 2002 14:31:52 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WM4FQXMJ>; Thu, 14 Nov 2002 09:37:38 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D55C170@emshqs1.ncr.disa.mil>
From: "Taylor, Carol-Lyn" <taylor3c@ncs.gov>
To: "'Steve Silverman'" <steves@shentel.net>,
        "King, Kimberly  S."
	 <KIMBERLY.S.KING@saic.com>,
        "'Dean'" <idb@tazznetworks.com>,
        RJ Atkinson
	 <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
Date: Thu, 14 Nov 2002 09:37:30 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Well said.

-----Original Message-----
From: Steve Silverman [mailto:steves@shentel.net]
Sent: Wednesday, November 13, 2002 3:28 PM
To: King, Kimberly S.; 'Dean'; RJ Atkinson
Cc: ieprep
Subject: RE: [Ieprep] access links 


The problem is that in a sudden emergency, there may be no time to change
codecs (so you can't talk to anyone), no time to replace or upgrade the
access link, or no additional bandwidth to purchase.  In an emergency, you
may have minutes to react. Emergencies often happen to unexpected locations
at inopportune times.
In this situation, selected users require priority so their calls are
usable.  This is the focus of some of us.

Some locations do not have access to fiber optic trunks and have limited
bandwidth.

Steve Silverman


Problem statement????  Everyone at the ETS location wants to make calls at
the same time and the access link can't handle all that voice traffic so
conversations degrade so much as to be unusable.

Potential solutions for problem...define the appropriate codecs, get a big
enough access link, provision QoS on CPE or more drastically pay for QoS to
be deployed on ISP router that faces the customer site, etc.

Defining the problem to be solved with appropriate context information would
be helpful.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 09:37:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20471
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 09:37:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEEddo00679
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 09:39:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEddv00676
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 09:39:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20459
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 09:37:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEd1v00654;
	Thu, 14 Nov 2002 09:39:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEEcHv00616
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 09:38:17 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20406
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 09:35:40 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAEEVid11456;
	Thu, 14 Nov 2002 06:31:44 -0800 (PST)
Date: Thu, 14 Nov 2002 06:31:44 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        "'ieprep '" <ieprep@ietf.org>, "''Dean' '" <idb@tazznetworks.com>,
        "'RJ Atkinson '" <rja@extremenetworks.com>
Subject: RE: [Ieprep] access links 
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D2C@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211140630230.11206-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 14 Nov 2002, Nguyen, An wrote:
    > Sorry I did not make it clear! What I really meant was the best effort is
    > not enough for emergency traffic because of the "best effort" nature in the
    > IP networks.

Sorry, this is still far from clear.

Because of _what about_ the "best effort" nature of IP networks?

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 10:08:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21231
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 10:08:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEFA7L02533
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 10:10:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEFA7v02530
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 10:10:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21223
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 10:07:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEF95v02456;
	Thu, 14 Nov 2002 10:09:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEF4pv01734
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 10:04:51 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA21106
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 10:02:14 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 14 Nov 2002 15:02:17 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <W7MR3LLV>; Thu, 14 Nov 2002 10:06:02 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D2E@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock'" <woody@pch.net>
Cc: Mpierce1@aol.com, rja@extremenetworks.com,
        "Choi, Don"
	 <choid@ncr.disa.mil>, ieprep@ietf.org
Subject: RE: [Ieprep] Atlanta ieprep Agenda
Date: Thu, 14 Nov 2002 10:04:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Bill,

I was not there at the meeting. But these are what I found related to QoS. 

http://www.nanog.org/mtg-0210/sanjay.html
http://www.nanog.org/mtg-0210/shankar.html
http://www.nanog.org/mtg-0210/telkamp.html
http://www.nanog.org/mtg-0210/complexity.html

Regards,

An
-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Wednesday, November 13, 2002 4:11 PM
To: Nguyen, An
Cc: Mpierce1@aol.com; rja@extremenetworks.com; Choi, Don;
ieprep@ietf.org
Subject: RE: [Ieprep] Atlanta ieprep Agenda


      On Wed, 13 Nov 2002, Bill Woodcock wrote:
    > There were no talks on QoS.

Oh, and while I'm at it, there were no talks on QoS at RIPE, APRICOT,
AfNOG, or NordNOG, either.

                                -Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 10:38:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21910
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 10:38:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEFeGj04251
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 10:40:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEFeGv04248
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 10:40:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21902
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 10:37:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEFdRv04176;
	Thu, 14 Nov 2002 10:39:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEFcTv04142
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 10:38:29 -0500
Received: from seahorse.shentel.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21845
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 10:35:52 -0500 (EST)
Received: from steves (ha30s313.d.shentel.net [204.111.30.57])
	by seahorse.shentel.net (8.11.6/8.11.6) with SMTP id gAEFbrM00933;
	Thu, 14 Nov 2002 10:37:53 -0500
From: "Steve Silverman" <steves@shentel.net>
To: "Bill Woodcock" <woody@pch.net>, "Nguyen, An" <nguyena@ncs.gov>,
        "'ieprep '" <ieprep@ietf.org>
Cc: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        "''Dean' '" <idb@tazznetworks.com>,
        "'RJ Atkinson '" <rja@extremenetworks.com>
Subject: RE: [Ieprep] access links 
Date: Thu, 14 Nov 2002 10:37:52 -0500
Message-ID: <KMEJKAPHBBCMCDDGMBLOAEFGCAAA.steves@shentel.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <Pine.GSO.4.44.0211140630230.11206-100000@paixhost.pch.net>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Bill,

You appear to have a difficult time understanding what we ("we
represents the DOD, many NATO defense ministries, and IMHO most of
the public network) need.  Let me make one more attempt to explain.

Some locations DO NOT have high bandwidth available (e.g., mobile
platforms on radio links).  Emergencies can happen anywhere  and in
such emergencies it is common for the offered traffic load to exceed
the network capability and it is necessary for selected users to get
priority.  This is a functional requirement, independent of the
technology of IP or any other network technology.  It is a JCS
requirement which means that the DOD (and various other
organizations can not deploy equipment that can not satisfy this
requirement.

While some have made a point that IETF attendees represent
themselves as individuals rather than the organization they work
for, it is also a fact that few of the attendees, pay their own way
to the meetings.  I currently am paid by the DOD and because I take
their money, and since I have considerable experience in meeting
their needs, I tend to focus on those subjects that they want.
Since I personally consider these needs to be legitimate
requirements, I have no conflict representing their views.  I doubt
that many of the attendees in Atlanta are without organizational
support and few if any organizations would support someone who
opposed their requirements.

The DOD has certain functional requirements.  Whether or not a few
people think these are "valid", if the DOD says it wants something
and is willing to pay for it, then they have a right to attempt to
buy it.
Since the DOD tries to maintain a multi-vendor environment (as a
taxpayer, I applaud this preference.) they try to get
standards to support their requirements.  If there are no such
standards, they have to write their own or stick to one supplier.
Many of us think that a public standard, even if optional and not
supported by some vendors and some networks, is preferable.

Many companies would like to be able to sell their equipment to the
DOD.  Some companies might not be interested in this buisiness.
That's fine.  We just want enough of a standard so that multiple
vendors can meet our requirements in an interoperable way.

As to the lack of a possible way to provide better service, Houston
Associates has built and tested a way to provide some users higher
priority. We intend to submit an Internet Draft (Multi-Level
Expedited Forwarding) for a new optional PHB that has been shown to
solve some of this problem.  Considerable work remains to be done in
terms of security but it will work well on a T1.  We are not worried
about lines at optical rates (above E1). These don't generally share
the problem of lack of  bandwidth.

I think this function MIGHT be useful for the public network but my
priority is to get this function available for special private
networks, not the public net.

Steve Silverman
Houston Associates


-


      On Thu, 14 Nov 2002, Nguyen, An wrote:
    > Sorry I did not make it clear! What I really meant was the
best effort is
    > not enough for emergency traffic because of the "best effort"
nature in the
    > IP networks.

Sorry, this is still far from clear.

Because of _what about_ the "best effort" nature of IP networks?

                                -Bill


_______________________________________________
I


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 11:01:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22509
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 11:01:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEG3xr05263
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 11:03:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEG3xv05260
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 11:03:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22499
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 11:01:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEG33v05220;
	Thu, 14 Nov 2002 11:03:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEG2Lv05186
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 11:02:21 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22452
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 10:59:43 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAEFtwd12180;
	Thu, 14 Nov 2002 07:55:58 -0800 (PST)
Date: Thu, 14 Nov 2002 07:55:58 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: Mpierce1@aol.com, <rja@extremenetworks.com>,
        "Choi, Don" <choid@ncr.disa.mil>, <ieprep@ietf.org>
Subject: RE: [Ieprep] Atlanta ieprep Agenda
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D2E@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211140752100.11206-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 14 Nov 2002, Nguyen, An wrote:
    > I was not there at the meeting. But these are what I found related to QoS.
    > http://www.nanog.org/mtg-0210/sanjay.html

That one's about HA, and has nothing whatsoever to do with QoS.

    > http://www.nanog.org/mtg-0210/shankar.html

That one's about Fast Reroute, and has nothing whatsoever to do with QoS.

    > http://www.nanog.org/mtg-0210/telkamp.html

That one's about capacity planning, _specifically in opposition to QoS_.

    > http://www.nanog.org/mtg-0210/complexity.html

That one explains why a wide range of failed technologies were deprecated,
and mentions QoS in that context.

What point are you trying to make?

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 11:14:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22901
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 11:14:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEGGlN06305
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 11:16:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGGlv06302
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 11:16:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22871
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 11:14:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGG4v06269;
	Thu, 14 Nov 2002 11:16:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGDuv06150
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 11:13:56 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22737
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 11:11:17 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAEG7id12332;
	Thu, 14 Nov 2002 08:07:44 -0800 (PST)
Date: Thu, 14 Nov 2002 08:07:44 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Steve Silverman <steves@shentel.net>
cc: "Nguyen, An" <nguyena@ncs.gov>, "'ieprep '" <ieprep@ietf.org>,
        "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        "''Dean' '" <idb@tazznetworks.com>,
        "'RJ Atkinson '" <rja@extremenetworks.com>
Subject: RE: [Ieprep] access links 
In-Reply-To: <KMEJKAPHBBCMCDDGMBLOAEFGCAAA.steves@shentel.net>
Message-ID: <Pine.GSO.4.44.0211140757090.11206-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 14 Nov 2002, Steve Silverman wrote:
    > You appear to have a difficult time understanding what we need.

No, I have a hard time understanding why it is you think I should care.

    > Some locations DO NOT have high bandwidth available (e.g., mobile
    > platforms on radio links).  Emergencies can happen anywhere  and in
    > such emergencies it is common for the offered traffic load to exceed
    > the network capability and it is necessary for selected users to get
    > priority.  This is a functional requirement, independent of the
    > technology of IP or any other network technology.

So why do you think that the experience you're referring to, which is
circuit switched, has any applicability at all in a packet-switched
environment?

Moreover, why should DoD "requirements" matter to me?

You guys keep repeating this "we've determined that we require foo" over
and over, seemingly without recognizing that it's making just as little
impact now as it did the first hundred times.  If you can show that
there's a problem, and that the problem is tractable, then someone might
take you seriously.  Until then, we're all just going to continue to
wonder why you keep repeating yourself.

    > It is a JCS requirement which means that the DOD (and various other
    > organizations can not deploy equipment that can not satisfy this
    > requirement.

Hey, if you're the one they're paying, then it sounds to me like their
requirements are your problem, not mine.

    > I doubt that many of the attendees in Atlanta are without
    > organizational support and few if any organizations would support
    > someone who opposed their requirements.

Then you'd be wrong on both counts, as numerous IETF folks have pointed
out on this list already.

You guys are in this tight loop with DoD procurement folks or whatever,
all trying to mutually justify each others' existence, and dragging us
into the middle of it just wastes everyone's time.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 11:29:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23511
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 11:29:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEGVwt06897
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 11:31:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGVwv06894
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 11:31:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23493
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 11:29:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGV4v06847;
	Thu, 14 Nov 2002 11:31:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGU2v06808
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 11:30:02 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA23431
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 11:27:23 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 14 Nov 2002 16:24:14 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WM4FQ9M1>; Thu, 14 Nov 2002 11:30:00 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D30@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock'" <woody@pch.net>
Cc: Mpierce1@aol.com, rja@extremenetworks.com,
        "Choi, Don"
	 <choid@ncr.disa.mil>, ieprep@ietf.org
Subject: RE: [Ieprep] Atlanta ieprep Agenda
Date: Thu, 14 Nov 2002 11:29:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

QoS is related to availability, survivability, and reliability. My
impression is that as far as high availability is concerned IP networks are
not there yet. Therefore, IP folks from NANOG are trying to provide four or
five nines just like what have been done with PSTN. 

On a related issue, what I've kept hearing is to resolve congestions and QoS
issues by throwing more equipment at them. One of these presentations ( I
believe from QWest) says that "Now capital is limited" . I think a lot of
ISPs would agree with this statement and I am not speaking for Qwest here.
It indicated that serious traffic engineering needs to done utilizing what
are being deployed.  

By the way, what do you think about Genuity offering priority and QoS?

Regards,

An

-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Thursday, November 14, 2002 10:56 AM
To: Nguyen, An
Cc: Mpierce1@aol.com; rja@extremenetworks.com; Choi, Don;
ieprep@ietf.org
Subject: RE: [Ieprep] Atlanta ieprep Agenda


      On Thu, 14 Nov 2002, Nguyen, An wrote:
    > I was not there at the meeting. But these are what I found related to
QoS.
    > http://www.nanog.org/mtg-0210/sanjay.html

That one's about HA, and has nothing whatsoever to do with QoS.

    > http://www.nanog.org/mtg-0210/shankar.html

That one's about Fast Reroute, and has nothing whatsoever to do with QoS.

    > http://www.nanog.org/mtg-0210/telkamp.html

That one's about capacity planning, _specifically in opposition to QoS_.

    > http://www.nanog.org/mtg-0210/complexity.html

That one explains why a wide range of failed technologies were deprecated,
and mentions QoS in that context.

What point are you trying to make?

                                -Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 11:39:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23832
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 11:39:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEGf9w07840
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 11:41:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGf9v07837
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 11:41:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23828
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 11:38:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGe1v07742;
	Thu, 14 Nov 2002 11:40:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGdEv07686
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 11:39:14 -0500
Received: from imo-m06.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23706
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 11:36:36 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m06.mx.aol.com (mail_out_v34.13.) id b.9.2378523 (3932);
	Thu, 14 Nov 2002 11:38:39 -0500 (EST)
Message-ID: <9.2378523.2b052b8f@aol.com>
Date: Thu, 14 Nov 2002 11:38:39 EST
Subject: Re: [Ieprep] Qualitative statement about quality
To: woody@pch.net, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_9.2378523.2b052b8f_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_9.2378523.2b052b8f_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/13/2002 6:37:23 PM Eastern Standard Time, woody@pch.net 
writes:


> 

We really need a clarification of this claim. What do you mean be "latency"?

Do you mean one-way or round-trip delay of the voice? Or something else.

Based on the same definition, what was the "latency" on the PSTN call between 
San Luis Obispo and Berkeley?

Mike Pierce


--part1_9.2378523.2b052b8f_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/13/2002 6:37:23 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Latency on the VoIP connection was hovering in the 600ms range, with about</BLOCKQUOTE>
<BR>
<BR>We really need a clarification of this claim. What do you mean be "latency"?
<BR>
<BR>Do you mean one-way or round-trip delay of the voice? Or something else.
<BR>
<BR>Based on the same definition, what was the "latency" on the PSTN call between San Luis Obispo and Berkeley?
<BR>
<BR>Mike Pierce
<BR></FONT></HTML>

--part1_9.2378523.2b052b8f_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 11:40:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23869
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 11:40:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEGgJ607900
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 11:42:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGgJv07897
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 11:42:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23860
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 11:39:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGf2v07826;
	Thu, 14 Nov 2002 11:41:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGeYv07792
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 11:40:34 -0500
Received: from imo-d08.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23794
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 11:37:55 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d08.mx.aol.com (mail_out_v34.13.) id b.bf.29c0f8a9 (3932);
	Thu, 14 Nov 2002 11:39:54 -0500 (EST)
Message-ID: <bf.29c0f8a9.2b052bda@aol.com>
Date: Thu, 14 Nov 2002 11:39:54 EST
Subject: Re: [Ieprep] access links 
To: woody@pch.net, Janet.Gunn@dyncorp.com
CC: idb@tazznetworks.com, rja@extremenetworks.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_bf.29c0f8a9.2b052bda_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_bf.29c0f8a9.2b052bda_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/14/2002 7:39:39 AM Eastern Standard Time, woody@pch.net 
writes:


>      On Wed, 13 Nov 2002, Gunn, Janet wrote:
>     > The vast majority of GETS service users have NOTHING to do with DoD 
> or DISA.
>     > In fact, I heard some numbers recently that indicate that a very tiny
>     > proportion of the issued GETS cards have gone to DoD.
> 
> Unfortunately, GETS users are unrepresented here, a point which I believe
> Rex has been making.  What we've got instead is the GETS purchasing agent,
> in effect, which may or may not have radically different values than the
> users themselves.
> 
> I think part of Rex's point is that if the GETS users had a voice here,
> they'd be asking for a less expensive solution that would provide
> functionality more of the time..
> 


I really don't see you point, not do I think a majority of those active on 
this list. NCS (and some of it's contractors) certainly "represent" GETS 
users (to the extent that you might let one person "represent" another.) You 
try to claim that NCS can't "represent" the GETS user, but at the same time, 
you seem to claim to "represent" their wishes ("a less expensive solution").

As a taxpayer, I can appreciate that goal of saving money, but as a potential 
benefactor of the GETS service (if there were an emergency in my 
neighborhood), I would rather have (near) guaranteed access for the emergency 
workers and "damn the expense".

Mike Pierce
Artel



--part1_bf.29c0f8a9.2b052bda_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/14/2002 7:39:39 AM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&nbsp;&nbsp;On Wed, 13 Nov 2002, Gunn, Janet wrote:
<BR> &nbsp;&nbsp;&nbsp;&gt; The vast majority of GETS service users have NOTHING to do with DoD or DISA.
<BR> &nbsp;&nbsp;&nbsp;&gt; In fact, I heard some numbers recently that indicate that a very tiny
<BR> &nbsp;&nbsp;&nbsp;&gt; proportion of the issued GETS cards have gone to DoD.
<BR>
<BR>Unfortunately, GETS users are unrepresented here, a point which I believe
<BR>Rex has been making. &nbsp;What we've got instead is the GETS purchasing agent,
<BR>in effect, which may or may not have radically different values than the
<BR>users themselves.
<BR>
<BR>I think part of Rex's point is that if the GETS users had a voice here,
<BR>they'd be asking for a less expensive solution that would provide
<BR>functionality more of the time..
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>I really don't see you point, not do I think a majority of those active on this list. NCS (and some of it's contractors) certainly "represent" GETS users (to the extent that you might let one person "represent" another.) You try to claim that NCS can't "represent" the GETS user, but at the same time, you seem to claim to "represent" their wishes ("a less expensive solution").
<BR>
<BR>As a taxpayer, I can appreciate that goal of saving money, but as a potential benefactor of the GETS service (if there were an emergency in my neighborhood), I would rather have (near) guaranteed access for the emergency workers and "damn the expense".
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR></FONT></HTML>

--part1_bf.29c0f8a9.2b052bda_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 11:54:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24293
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 11:54:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEGuCC08500
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 11:56:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGuCv08497
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 11:56:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24259
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 11:53:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGt3v08410;
	Thu, 14 Nov 2002 11:55:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGpMv08238
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 11:51:22 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24111
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 11:48:43 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <QXJ5FYJC>; Thu, 14 Nov 2002 11:49:06 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A41495F@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Bill Woodcock'" <woody@pch.net>
Cc: "'Dean'" <idb@tazznetworks.com>, RJ Atkinson <rja@extremenetworks.com>,
        ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
Date: Thu, 14 Nov 2002 11:48:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

I absolutely agree with the part of your reply copied below.  

In fact, the GETS users may not be willing to pay ANYTHING until some crisis
occurs in which important communications don't get through.  This is what
happened with wireless/mobile phones.  There had been, for several years, an
under funded, "back burner" project looking at extending GETS-like service
to mobile phones, with  5 year and 10 year objectives.  On and after
September 11,  various emergency personnel discovered that GETS worked great
on a landline phone, or on a mobile phone in an uncongested area, but a
mobile phone in a congested area never even got a chance to place the GETS
call.  Suddenly the user community was willing to pay for a Wireless
Priority Service, and the 5 and 10 year plans became 1 and 2 year plans.
Which it looks as if we are actually going to be able to do.

One of the main reasons we are able to do this rapid implementation is
because there are parameters already there in the  ISUP IAM (e.g.., the HPC
value for the CPC parameter, and the Precedence parameter) that we could
use.  There has been extensive software development by the switch vendors,
and a lot of effort from the carriers, but if the parameters had not already
been there in the protocol, we could not possibly meet the schedule.

I foresee that, at some point in the future, something similar will happen
with IP telephony, or other Internet functionality.  Some crisis will
happen- GETS will work fine for the regular phones.  WPS will work fine for
the mobile phones.  But the emergency users who try to use a SIP phone won't
get through.   Or an important video feed won't get through.  (Possibly
because of congestion in an IP network, but more likely because of
congestion in, or at the interface to, a circuit switched network which is
part of the end-to-end path).

When that happens, the user community (and/or the government on their
behalf) will be prepared to fund a project to solve that problem.  When that
happens, and whatever the exact nature of the problem, or the appropriate
solution, it will be A WHOLE LOT EASIER if there are already parameters in
the protocol suite to indicate which "calls" (or other services) are
entitled to priority service.

My perception is that at least PART of the objective of IEPREP is to make
sure that the parameters, or other "hooks" are already there in the protocol
suite, so that when we DO have a SPECIFIC problem, with a SPECIFIC solution,
we can rapidly implement the solution. (Scott, correct me if I am wrong
here.)

We can't see the future, so we can't tell EXACTLY what the problem will be.
And what we think will be problems in the future is heavily influenced by
what we have seen be problems in the past.  So we want to structure any
enhancements to the protocol suite in as generic a way as possible.

But I don't think it is wise to say "Lets not even think about how we can
prepare for it until the crisis occurs."

As I said in another message, I am MOST concerned with what happens at the
interface between the IP and the circuit switched network.  But let's
structure what we do there in such a way that IF some kind of "special
service" is needed within the IP network (including access links and private
networks, not just the ISP's core network), there will be parameters that
can be used in conjunction with that "special service".

-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Thursday, November 14, 2002 7:33 AM
To: Gunn, Janet
Cc: 'Dean'; RJ Atkinson; ieprep
Subject: RE: [Ieprep] access links 

I think part of Rex's point is that if the GETS users had a voice here,
they'd be asking for a less expensive solution that would provide
functionality more of the time..

                                -Bill



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 13:24:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26104
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 13:24:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEIR5u14129
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 13:27:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEIR5v14126
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 13:27:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26090
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 13:24:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEIQ8v14073;
	Thu, 14 Nov 2002 13:26:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEIPpv14053
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 13:25:51 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26056
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 13:23:11 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Thu, 14 Nov 2002 10:22:23 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gAEINFb9027085;
	Thu, 14 Nov 2002 10:23:15 -0800 (PST)
Subject: Re: [Ieprep] access links
From: Rex Buddenberg <budden@nps.navy.mil>
To: Mpierce1@aol.com
Cc: woody@pch.net, Janet.Gunn@dyncorp.com, idb@tazznetworks.com,
        rja@extremenetworks.com, ieprep@ietf.org
In-Reply-To: <bf.29c0f8a9.2b052bda@aol.com>
References: <bf.29c0f8a9.2b052bda@aol.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 14 Nov 2002 10:20:57 -0800
Message-Id: <1037298058.1091.631.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I've got a problem with the targeting here.  

Are we trying to provide service to 
	- emergency services workers, 
	- general public (e.g. inward 911 to use a circuit switch example) 
	- or GETS users?

I spent 20 years on active duty in USCG, significant portions of which
were in the search & rescue and related emergency response areas and
significant portions as a communications officer.  I never saw anything
like a GETS card or access.  None of my COs had such a thing because I
would have been the one handling the administrative. 
      Question.  What is the scale and what is the scalability of GETS? 
I.e. how many people carry the cards today?  Is that number anywhere
near the number of, say, fire department personnel across the country? 
Could it be?  (or would we bump against some scalability issues?)

In my USCG experience, what we _did_ have was the precedence system (for
the crusties among you, defined in JANAP 128) which is very analogous to
diff-serv.  It did work and work quite well*, except:
	- there was a discipline problem for which the symptom is precedence
creep.  Today the Navy never sends anything Routine precedence.
	- scalability limited.  We controlled the system by limiting message
releasing authority to the unit CO and a few folks he delegates to --
not every WWW user with a mouse.
      (I have several anecdotal stories where the precedence system
worked better in USCG than the other services).

*Here my mileage differs from Bill Wood's.  Caveat is that most
applications for over the comms system were connectionless, unlike the
interactive voice apps you're contemplating here.  

What's bothering me here is that a lot of the GETS history may not be
applicable to what we're trying to do.  The tragedy of the commons part
Janet recites  _is_ applicable.  But I'm highly suspicious of the scale
and scalability parallels.



On Thu, 2002-11-14 at 08:39, Mpierce1@aol.com wrote:
> In a message dated 11/14/2002 7:39:39 AM Eastern Standard Time, woody@pch.net 
> writes:
> 
> 
> >      On Wed, 13 Nov 2002, Gunn, Janet wrote:
> >     > The vast majority of GETS service users have NOTHING to do with DoD 
> > or DISA.
> >     > In fact, I heard some numbers recently that indicate that a very tiny
> >     > proportion of the issued GETS cards have gone to DoD.
> > 
> > Unfortunately, GETS users are unrepresented here, a point which I believe
> > Rex has been making.  What we've got instead is the GETS purchasing agent,
> > in effect, which may or may not have radically different values than the
> > users themselves.
> > 
> > I think part of Rex's point is that if the GETS users had a voice here,
> > they'd be asking for a less expensive solution that would provide
> > functionality more of the time..
> > 
> 
> 
> I really don't see you point, not do I think a majority of those active on 
> this list. NCS (and some of it's contractors) certainly "represent" GETS 
> users (to the extent that you might let one person "represent" another.) You 
> try to claim that NCS can't "represent" the GETS user, but at the same time, 
> you seem to claim to "represent" their wishes ("a less expensive solution").
> 
> As a taxpayer, I can appreciate that goal of saving money, but as a potential 
> benefactor of the GETS service (if there were an emergency in my 
> neighborhood), I would rather have (near) guaranteed access for the emergency 
> workers and "damn the expense".
> 
> Mike Pierce
> Artel
> 
> 


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 13:37:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26454
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 13:37:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEIe3515272
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 13:40:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEIe3v15269
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 13:40:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26450
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 13:37:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEId4v15197;
	Thu, 14 Nov 2002 13:39:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEIavv14537
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 13:36:57 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26343
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 13:34:17 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Thu, 14 Nov 2002 13:36:29 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111413363624320
 ; Thu, 14 Nov 2002 13:36:36 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <W5YTXQH4>; Thu, 14 Nov 2002 13:37:57 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E7797A@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Henning Schulzrinne'" <hgs@cs.columbia.edu>,
        "King, Kimberly S." <KIMBERLY.S.KING@saic.com>
Cc: "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] access links
Date: Thu, 14 Nov 2002 13:36:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Kimberly said:
> > I read this statement as best effort transport is 
> sufficient due to the
> > infeasibility of providing anything different.
> >
> > Those apposing the statement, please provide a feasible alternative.
> 
> 
Henning said:
> It is pretty clear that there are alternatives. 

Let me remind you of the chain of events.  I suggested:

"Problem statement????  Everyone at the ETS location wants to make calls at
the same time and the access link can't handle all that voice traffic so
conversations degrade so much as to be unusable. "

and 

"Potential solutions for problem...define the appropriate codecs, get a big
enough access link, provision QoS on CPE or more drastically pay for QoS to
be deployed on ISP router that faces the customer site, etc."

I was then informed that this was not an acceptable problem statement by An
and Steve.
An stated:
>The problem with this is that you don't know the locations where emergency
>occurs  in advance. You can't provision your access links everywhere around
>the country. And that is not at all cost effective. If there is no way of
>differentiating traffic, then the best effort traffic is best effort."

What this does is say that the access link in question is one that can not
be determined in advance.  This means one can't count on your CPE router
being provisioned for DiffServ or other QoS.  You can't even count on
knowing who the ISP is on the other end of that access link and whether they
provide any QoS.  Thus, I repeat my question about finding a feasible
alternative to layer 3 QoS besides best effort transport over an arbitrary
access link.

Something has happened here that is true in general.  Each constraint
(requirement) likely narrows the solution space.  If you ask for everything
under all conditions, the solutions space is likely to be nil.  

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 14:00:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27079
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 14:00:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEJ2xA16171
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 14:02:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEJ2xv16168
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 14:02:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27047
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 14:00:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEJ28v16132;
	Thu, 14 Nov 2002 14:02:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEJ18v16100
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 14:01:08 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26993
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 13:58:27 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAEIt4d14285;
	Thu, 14 Nov 2002 10:55:04 -0800 (PST)
Date: Thu, 14 Nov 2002 10:55:04 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Qualitative statement about quality
In-Reply-To: <9.2378523.2b052b8f@aol.com>
Message-ID: <Pine.GSO.4.44.0211141053200.11206-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 14 Nov 2002 Mpierce1@aol.com wrote:
    > We really need a clarification of this claim. What do you mean be "latency"?
    > Do you mean one-way or round-trip delay of the voice? Or something else.

Round-trip, same as anyone else means when they say latency.

    > Based on the same definition, what was the "latency" on the PSTN call between
    > San Luis Obispo and Berkeley?

Who knows.  Presumably there are audio time-domain reflectometers, but I
doubt the CALREN2 guys had one.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 14:22:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27656
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 14:22:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEJOCn17500
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 14:24:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEJOCv17497
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 14:24:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27644
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 14:21:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEJN4v17449;
	Thu, 14 Nov 2002 14:23:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEJMhv17434
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 14:22:43 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27608
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 14:20:02 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAEJMLpe002260;
	Thu, 14 Nov 2002 14:22:21 -0500 (EST)
Date: Thu, 14 Nov 2002 14:22:21 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211141922.gAEJMLpe002260@newdev.harvard.edu>
To: Janet.Gunn@DynCorp.com, woody@pch.net
Subject: RE: [Ieprep] access links
Cc: idb@tazznetworks.com, ieprep@ietf.org, rja@extremenetworks.com
In-Reply-To: <CBED705A7FD2D311865500508B1089410A41495F@chntex02.is.dyncorp.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> As I said in another message, I am MOST concerned with what happens at the
> interface between the IP and the circuit switched network.  But let's
> structure what we do there in such a way that IF some kind of "special
> service" is needed within the IP network (including access links and private
> networks, not just the ISP's core network), there will be parameters that
> can be used in conjunction with that "special service".

this fits my picture of what we should be focusing on

plus - developing a clear understanding on where doing something
specific to support for "special service" in an IP network may be
need and where is is not likly to be needed

e.g. - it is unlikly that one needs "special service" functions inside
of a big, fiber-based, mesh-based ISP since that part of the net
will provide the required service without any special handling of the
packets (data or signaling packets)

but it is unlikly that someone with a narrow tail circuit will
get the "required service" (quality that is - note that call 
completion is mostly a given ) as-is in times of heavy load, whatever
the cause of the heavy load

the inability of the tail circuit to support the load could be 
delt with by getting a fatter tail circuit or by handling packets
differently on the narrow link

figuing out if there are reasonable ways to do the latter should
come after we figure out a better description of the cases where
'don't do anything' is the right answer

Scott

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 14:43:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28290
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 14:43:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEJk8o20075
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 14:46:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEJk8v20072
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 14:46:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28283
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 14:43:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEJj5v19982;
	Thu, 14 Nov 2002 14:45:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEJhhv19813
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 14:43:43 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28209
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 14:41:02 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Thu, 14 Nov 2002 14:43:13 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111414432022535
 for <ieprep@ietf.org>; Thu, 14 Nov 2002 14:43:20 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <W5YTXR0N>; Thu, 14 Nov 2002 14:44:42 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E7797D@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "Ieprep (E-mail)" <ieprep@ietf.org>
Date: Thu, 14 Nov 2002 14:43:16 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Ieprep] Is this the service you are requesting?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


Correct me if I'm wrong.  This is what I believe I am hearing from a subset
of the WG.

Potential Desired Service:
ETS service would like to contract with a set of ISP(s) and service
providers.  Any ETS user would access ANY point where any of those ISPs have
presence (even connect via an arbitrary company's LAN who has an access link
to one of those ISPs), be authenticated and get priority in applications and
*QoS* priority in transport, especially over the access link. 

Potential Optional Enhancement over the above heard from subset of WG:
Should traffic traverse more than one ISP, that QoS status should be
maintained.  

If this is correct, then we can discuss the issues surrounding this.  If
not, we still need to be more concrete about what is being requested.

Kimberly






_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 15:20:01 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29424
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 15:20:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEKMA621981
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 15:22:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKMAv21977
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 15:22:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29405
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 15:19:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKLAv21916;
	Thu, 14 Nov 2002 15:21:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKKiv21888
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 15:20:44 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29389
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 15:18:04 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAEKEbd15262;
	Thu, 14 Nov 2002 12:14:37 -0800 (PST)
Date: Thu, 14 Nov 2002 12:14:37 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
cc: "'Dean'" <idb@tazznetworks.com>, RJ Atkinson <rja@extremenetworks.com>,
        ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
In-Reply-To: <CBED705A7FD2D311865500508B1089410A41495F@chntex02.is.dyncorp.com>
Message-ID: <Pine.GSO.4.44.0211141202230.14871-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 14 Nov 2002, Gunn, Janet wrote:
    > As I said in another message, I am MOST concerned with what happens at the
    > interface between the IP and the circuit switched network.

Currently, that handoff is most commonly NxPRI, according to the
couple of people who've commented, and my own admittedly limited
experience.  I'm assuming that GETS-like information is not currently, or
cannot be contained in PRI signalling, just SS7?  Or is it there in PRI as
well?

In the future, that SS7-to-SIP conversion will happen inside the legacy
telcos, and they'll hand off to the rest of the network as pure IP...  At
that point, we (the IETF) only care that they implement existing protocols
properly, we don't care what they do internally.

But my understanding is that you have a specific need for them to have
some reliable, interoperable way of making that transition
(IP-to-PSTN-to-IP or PSTN-to-IP-to-PSTN) internally, while retaining and
conveying any priority information which may be needed to get the call
through the PSTN portions of the path.  Is that a fair summary?

Presumably that can be standardized in such a way that it could be used
subsequently in the rest of the network, if needed.  Nothing there should
require touching anything other than SIP.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 15:22:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29496
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 15:22:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEKOKD22308
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 15:24:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKOKv22305
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 15:24:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29493
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 15:21:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKN1v22098;
	Thu, 14 Nov 2002 15:23:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKMAv21973
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 15:22:10 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29403
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 15:19:29 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Thu, 14 Nov 2002 12:18:40 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gAEKJfb9004237;
	Thu, 14 Nov 2002 12:19:42 -0800 (PST)
Subject: Re: [Ieprep] Is this the service you are requesting?
From: Rex Buddenberg <budden@nps.navy.mil>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
Cc: "Ieprep (E-mail)" <ieprep@ietf.org>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E7797D@mcl-its-exs01>
References: <B8030EB94AF1D51196D70002A589D64207E7797D@mcl-its-exs01>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 14 Nov 2002 12:17:24 -0800
Message-Id: <1037305045.3604.659.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Thu, 2002-11-14 at 11:43, King, Kimberly S. wrote:
> 
> Correct me if I'm wrong.  This is what I believe I am hearing from a subset
> of the WG.

Well, not this subset.

First a reiterate: QoS is a condition measurable in terms of latency,
jitter, determinism and throughput.  QoS _control_ is a means of
optimizing some of these parameters at the expense of others.
</definition>
> 
> Potential Desired Service:
> ETS service would like to contract with a set of ISP(s) and service
> providers.  Any ETS user would access ANY point where any of those ISPs have
> presence (even connect via an arbitrary company's LAN who has an access link
> to one of those ISPs), be authenticated and get priority in applications and
> *QoS* priority in transport, especially over the access link. 
> 
The user needs a certain QoS.  How the ISP(s) deliver it is a different
story.  If one of the intermediate ISPs is able to deliver the QoS I
need through overprovisioning, that's ok.  And clearly, for some core
segments of the network that's probably adequate and it certainly
conforms to the KISS principle.  What I want from those ISPs is a
Hippocratic assurance that they won't mangle a DS byte along the way.
	At that point, these ISPs have done their job -- they've delivered the
QoS I need (and done it without any explicit QoS control).


> Potential Optional Enhancement over the above heard from subset of WG:
> Should traffic traverse more than one ISP, that QoS status should be
> maintained.  

If you amend "QoS status" to something like 'undisturbed labels', (to
fit Ken Carlburg's language), then I'm happy.  

Aside.  The reasoning here is that routers can and do manipulate parts
of the IP datagram header.  For instance if your router is running NAT,
network address translation, it will replace IP addresses in the
header.  And some routers (usually border ones) will manipulate the DS
byte -- core routers generally do not since they're too busy drinking
from OC-48 pipes to fiddle with such nuisances.  We want a QoS control
pass-through with fidelity.  
	For the SIP worriers, this is a no-nevermind, routers do not fiddle
with the contents of an IP datagram which is where any application layer
special handling indicators would lie.


Page Two:

Scott wrote:

> 
> the inability of the tail circuit to support the load could be 
> delt with by getting a fatter tail circuit or by handling packets
> differently on the narrow link

Fatter tail circuits are problematic -- radios and all. 
Overprovisioning gets hard.  Therefore, the phrase after 'or' is
operative.  But it need only be operative over the tail circuit*. If the
datagrams arrive at the routers surrounding the tail circuit, then we
have a local problem for which we can devise local -- not Internet-wide
-- solutions.  

I think this triage is fairly important, else we have non-scaleable
solutions.



*in at least the Navy's case, the narrow links are in the interior of
the network, not at the edge which the term 'tail circuit' implies.  We
can overprovision both ashore and within the ship but not in the
ship-shore area.



> 
> If this is correct, then we can discuss the issues surrounding this.  If
> not, we still need to be more concrete about what is being requested.
> 
> Kimberly
> 
> 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 15:29:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29825
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 15:29:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEKW0O22667
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 15:32:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKW0v22664
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 15:32:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29799
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 15:29:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKV2v22606;
	Thu, 14 Nov 2002 15:31:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKTsv22506
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 15:29:54 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29707
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 15:27:14 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <QXJ5FZJQ>; Thu, 14 Nov 2002 15:27:36 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A414965@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Bill Woodcock'" <woody@pch.net>
Cc: "'Dean'" <idb@tazznetworks.com>, RJ Atkinson <rja@extremenetworks.com>,
        ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] access links 
Date: Thu, 14 Nov 2002 15:27:27 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Yes,

Not currently concerned about PRI, concerned about SIP.

If you add "IP to PSTN" (where we KNOW encapsulation can't help us) that is
a fair summary of the most immediate concern.

Longer term, I anticipate the need to do "something" about IP access
circuits and small private networks, but not sure just what "something" will
be.

-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Thursday, November 14, 2002 3:15 PM
To: Gunn, Janet
Cc: 'Dean'; RJ Atkinson; ieprep
Subject: RE: [Ieprep] access links 


      On Thu, 14 Nov 2002, Gunn, Janet wrote:
    > As I said in another message, I am MOST concerned with what happens at
the
    > interface between the IP and the circuit switched network.

Currently, that handoff is most commonly NxPRI, according to the
couple of people who've commented, and my own admittedly limited
experience.  I'm assuming that GETS-like information is not currently, or
cannot be contained in PRI signalling, just SS7?  Or is it there in PRI as
well?

In the future, that SS7-to-SIP conversion will happen inside the legacy
telcos, and they'll hand off to the rest of the network as pure IP...  At
that point, we (the IETF) only care that they implement existing protocols
properly, we don't care what they do internally.

But my understanding is that you have a specific need for them to have
some reliable, interoperable way of making that transition
(IP-to-PSTN-to-IP or PSTN-to-IP-to-PSTN) internally, while retaining and
conveying any priority information which may be needed to get the call
through the PSTN portions of the path.  Is that a fair summary?

Presumably that can be standardized in such a way that it could be used
subsequently in the rest of the network, if needed.  Nothing there should
require touching anything other than SIP.

                                -Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 16:46:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01996
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 16:46:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAELmOs27754
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 16:48:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAELmOv27751
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 16:48:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01993
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 16:45:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAELlEv27725;
	Thu, 14 Nov 2002 16:47:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAELkGv27699
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 16:46:16 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01969
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 16:43:34 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <QXJ5FZTT>; Thu, 14 Nov 2002 16:43:57 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A414967@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] Moving forward:  draft-carlberg-ets-*.txt
Date: Thu, 14 Nov 2002 16:43:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ran asked " From the folks worried about GETS-like stuff, please
focus on whether the core essentials did get documented clearly in those
two documents."

Here are my comments in response. Sorry it took so long.

Only a couple of comments on the "general" one.

On page 4, section 2.1,  There is a reference to "independent networks that
comprise the Internet".  I would like to see something somewhere (probably
section 2, Scope) that makes it clear that we may be interested in ANY
networks running the IP protocol suite, whether or not they are one of the
networks that "comprise the Internet".  In particular, the IP networks
within the "core" of a circuit switched network do not "comprise the
Internet".

Page 4 3. 2)
Labels from different layers are not required to be related to each other by
protocol, but there may be policies about their relationship.

In the "telephony" paper, some of the general requirement from the first
paper need to be expanded for telephony.

Page 2, section 2.1
What do you mean by "carriers"?  Does that include both ISPs and "common
carriers"?

Page 3 sec 3. 3)
This implies that we need translation of ALL "existing labels defined for
the PSTN".  I don't think we need that.  We DO need translation of "all
existing labels used to identify emergency and/or priority calls in the
PSTN".  And we WILL need translation of FUTURE labels used to identify
emergency or priority calls in the PSTN.

>From a GETS perspective, I would like to see CPC and Precedence mentioned by
name, but maybe that is too specific for this paper.

Page 3 3.1 1) Alternate paths

You might want to consider routing to an alternate IP/PSTN gateway if (for
whatever reason) you can't get to the originally specified IP/PSTN gateway.

Additional "Value Added"  points (not calling them "requirements" any more)

Increased probability of call set up (this is a telephony specific  example
of the "network Functionality" in the General paper).

Authorization is in the General paper.  It would make sense to include a
telephony specific version of authorization here.  E.g., the IP network
should accept authorization information from a trusted PSTN network element,
and vice versa.  The "trusted" part probably includes the existence of a
contractual relationship.

-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Monday, November 04, 2002 5:54 PM
To: ieprep
Subject: [Ieprep] Moving forward: draft-carlberg-ets-*.txt



Hi,

1) I appreciate Hal's note suggesting that draft-carlberg-ets-*.txt be 
made
WG documents.  I would ask that they be targeted as the standards-track
requirements [1] documents for those aspects of the current charter,
subject to whatever editing turns out to be necessary to get them into
a form congruent with WG Rough Consensus.

2) I would also ask Scott that we have *discussion* time for those
two documents in Atlanta on the IEprep Agenda. [1]

3) I'd like to ask that folks here please take time now, before Atlanta,
to read and critique the documents from Ken Carlberg (I kibbutzed, but 
the work
and words are mostly Ken's).  They are short documents (and I hope also
sweet :-).

General IP Carrier Requirements:
	draft-carlberg-ets-general-00.txt

Application-specific Requirements for IP Telephony:
	draft-carlberg-ets-telephony-00.txt


3B) I'm looking for slightly different kinds of review from our two 
segments
of participants.  From the folks worried about GETS-like stuff, please
focus on whether the core essentials did get documented clearly in those
two documents.  From the operators, is the verbage clear enough that 
there
is no intent for unfunded mandates or that an operator has to deploy any
of this stuff ?  Of course, feel free to comment on anything, but those
two questions are my core concern for the above documents at this time.

Thanks,

Ran
rja@extremenetworks.com

NOTES:
[1] IETF-definition for "requirements", not DoD-definition.  (I'd like 
to keep
Hal's document on what he thinks a GETS-like service might look like 
translated
into the global Internet, but that document doesn't contain 
IETF-requirements).
[2] I hate lots of presentations at IETF meetings, so I'm deliberately
asking for discussion time rather than presentation time.  I'd like to 
assume
that reasonable people will have read the drafts and that others will 
either
do so in real-time or keep quiet.



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:05:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09287
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:05:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF07EW03102
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:07:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF07Ev03099
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:07:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09274
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:04:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF069v02629;
	Thu, 14 Nov 2002 19:06:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF05sv02613
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:05:54 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09252
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:03:11 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id AEF1C67103; Thu, 14 Nov 2002 15:28:01 -0500 (EST)
Date: Thu, 14 Nov 2002 19:05:45 -0500
Subject: Re: [Ieprep] RE: network congestion, VoIP, NCS contracting approach, etc.
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "ieprep" <ieprep@ietf.org>
To: <gthom@delta-info.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <NDBBKMIGCLLNAOGKKDDPCEKFDDAA.gthom@delta-info.com>
Message-Id: <FD101D94-F82D-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 13:26 America/Montreal, Gary Thom wrote:

> If there is no distinction, then when there is not enough bandwidth 
> for all
> of the _best-effort_ traffic (due to congestion or damage),

Did not happen 9/11, does not happen inside the backbone, and ISPs can't
fix the access link -- only the access users can fix *their* links.
No amount of mechanism inside the core can fix the access issues, if any
exist.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:14:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09710
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:14:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0Gio03553
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:16:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0Ghv03550
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:16:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09687
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:14:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0G2v03507;
	Thu, 14 Nov 2002 19:16:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0Fvv03493
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:15:57 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09619
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:13:14 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 9E8C767103; Thu, 14 Nov 2002 15:38:04 -0500 (EST)
Date: Thu, 14 Nov 2002 19:15:48 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <120.195eb651.2b0406ae@aol.com>
Message-Id: <647ADDA1-F82F-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 14:49 America/Montreal, Mpierce1@aol.com 
wrote:
> [MAP] And being a contractor for DISA rather than an employee, I hope 
> I can get away with partly agreeing with you about the apparent 
> "disconnect" between DISA Center for Standards and the network 
> operations people. But I'm sure this is no different than in any other 
> large carrier/network operator. The two organizations have different 
> short-term missions, while the long-term missions are the same.

At @Home and at several other extant ISPs, it is the actual line 
network engineers
and network operations folks who are the ones participating in IETF.  
So the
"normal situation" IS actually different than at DISA, unfortunately.

> If things being discussed/proposed have very significant implications 
> in the operational IP network world, I would certainly like to hear 
> about them.

Gee whiz.  That's most of what Bill, Sean, Barry, and I have been 
talking about.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:18:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09861
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:18:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0Kke03716
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:20:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0Kkv03713
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:20:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09827
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:18:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0K2v03668;
	Thu, 14 Nov 2002 19:20:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0Jqv03622
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:19:52 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09792
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:17:09 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 25FB267103; Thu, 14 Nov 2002 15:41:56 -0500 (EST)
Date: Thu, 14 Nov 2002 19:19:40 -0500
Subject: Re: [Ieprep] access links 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>,
        "'Dean'" <idb@tazznetworks.com>, "ieprep" <ieprep@ietf.org>
To: "Steve Silverman" <steves@shentel.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <KMEJKAPHBBCMCDDGMBLOEEEICAAA.steves@shentel.net>
Message-Id: <EE5C38AB-F82F-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 15:28 America/Montreal, Steve Silverman 
wrote:

> The problem is that in a sudden emergency, there may be no time to 
> change
> codecs (so you can't talk to anyone), no time to replace or upgrade the
> access link, or no additional bandwidth to purchase.  In an emergency, 
> you
> may have minutes to react. Emergencies often happen to unexpected 
> locations
> at inopportune times.
> In this situation, selected users require priority so their calls are
> usable.  This is the focus of some of us.

Then I'd urge that they use the reslient low-bandwidth CODECs all the 
time,
since that is the approach that is most robust.

Dynamic routing recovers in local areas within milliseconds to seconds,
so minutes seems like a really long period of time (more than ample) to 
me.

And the ISP can't do *anything* about the access link's configuration,
since it is under the control of the end customer.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:30:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10236
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:30:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0WXB04136
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:32:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0WXv04133
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:32:33 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10223
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:29:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0Vav04080;
	Thu, 14 Nov 2002 19:31:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0OHv03827
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:24:17 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09951
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:21:35 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 4021367103; Thu, 14 Nov 2002 15:46:21 -0500 (EST)
Date: Thu, 14 Nov 2002 19:24:05 -0500
Subject: Re: [Ieprep] access links 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        "'Dean'" <idb@tazznetworks.com>, ieprep <ieprep@ietf.org>
To: "Nguyen, An" <nguyena@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D25@emshqs1.ncr.disa.mil>
Message-Id: <8C6232DA-F830-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 15:47 America/Montreal, Nguyen, An wrote:
> The problem with this is that you don't know the locations where 
> emergency
> occurs  in advance. You can't provision your access links everywhere 
> around
> the country. And that is not at all cost effective. If there is no way 
> of
> differentiating traffic, then the best effort traffic is best effort.

But there is *nothing* the ISPs can do to fix an issue in the access 
links.
The ISPs don't control the access links -- the end users do.

And I really don't see how NCS could even work the contract logistics 
to get
contracts in place with all of the "obvious" end users (e.g. hospitals, 
police stations)
to pay them for the cost of doing anything other than best-effort on the
bandwidth that fits into their budgets.

And this ignores the fact that Northridge and Kobe affected a lot more 
than
hospitals and police stations.  Is NCS proposing to require that cable 
modem
end users buy more capacity so that in an emergency, the police could 
use
VoIP over the cable modem system ?

Let me try again, the Internet is DE-centralised, so ISPs do NOT control
the end access links which is where things might get congested.  Levying
requirements on (or making contracts with) ISPs still cannot fix access 
link
issues -- because the ISPs don't control the critical pieces on the 
access
links.


Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:35:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10428
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:35:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0bNG04976
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:37:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0bMv04967
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:37:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10414
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:34:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0aUv04365;
	Thu, 14 Nov 2002 19:36:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0Tiv03980
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:29:44 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10143
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:27:02 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 5087E6711B; Thu, 14 Nov 2002 15:51:52 -0500 (EST)
Date: Thu, 14 Nov 2002 19:29:36 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: woody@pch.net, choid@ncr.disa.mil, ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <12c.1b1cd6e5.2b041f32@aol.com>
Message-Id: <51BD6080-F831-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 16:33 America/Montreal, Mpierce1@aol.com 
wrote:
> And there have been clear comments from others who do not believe that 
> "QoS is well behind us".

Which person who is actively engineering or operating a commercial ISP
has said anything like that on this list ?  I must not have received 
that email.

There have been no comments from folks with no experience or 
involvement with
operating a commercial ISP (or the DoD production IP networks, for that 
matter)
suggesting that QoS is not well behind us.  And a number of us didn't go
there even when it was the fad.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:35:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10445
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:35:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0bke05078
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:37:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0bkv05075
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:37:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10419
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:35:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0b2v04508;
	Thu, 14 Nov 2002 19:37:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0Z7v04277
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:35:07 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10309
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:32:24 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id CEC1C6711C; Thu, 14 Nov 2002 15:57:14 -0500 (EST)
Date: Thu, 14 Nov 2002 19:34:58 -0500
Subject: Re: [Ieprep] NCS contracts with voice IXCs
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: "Gunn, Janet" <Janet.Gunn@dyncorp.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <CBED705A7FD2D311865500508B1089410A414959@chntex02.is.dyncorp.com>
Message-Id: <11E846CE-F832-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 20:36 America/Montreal, Gunn, Janet 
wrote:
> I'm wading through a weeks's worth of email, so this may have already 
> been
> addressed.
>
> I think the initial concern is about IP networks within the core of 
> networks
> offered by the IXC carriers with whom the NCS already has contractual
> relationships for GETS and GETS-like services.

Ownership doesn't imply much of a relationship.  A large ISP whose 
parent
has lots of dark fibre was unable to get the Transmission folks (== 
SONET
and dark fibre) to let them have access to facilities.  This led the ISP
to go heavily into traffic engineering so they could glue together 
disparate
parallel links.

Most ISPs that are owned by voice IXCs are operated VERY separately
from the voice IXC subsidiary.  And in most cases that I'm familiar 
with,
the two business units are not on civil speaking terms.

So I don't think that those existing voice contracts relate to much 
probability
of getting an ISP contract with NCS for anything other than best-effort.

But it was a good topic to raise because I think that the stuff I've 
just
outlined might not have been obvious to everyone.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:39:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10592
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:39:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0fsx05257
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:41:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0fsv05254
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:41:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10572
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:39:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0f1v05226;
	Thu, 14 Nov 2002 19:41:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0e7v05203
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:40:07 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10534
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:37:24 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id A80406711C; Thu, 14 Nov 2002 16:02:14 -0500 (EST)
Date: Thu, 14 Nov 2002 19:39:58 -0500
Subject: Re: [Ieprep] MLPP in IP
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: "Choi, Don" <choid@ncr.disa.mil>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <B3FE60C05AD31D4C96E07EBC5000639E1D7F7C@EMSHQS2>
Message-Id: <C4B1CA11-F832-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 13, 2002, at 23:58 America/Montreal, Choi, Don wrote:
> I do not think there is anyone in DISA, DISN IP folks or DSN folks, who
> believe assured service is not a requirement. And this "Assured 
> Service"
> requirement is being expanded to all DISN, including DISN IP. So, 
> please
> check your sources in DISA again on this.

Several tell me that don't think that this is feasible or a real 
requirement,
though it is the subject of a lot of discussion and a lot of meetings.
Input I get is that it would be nice if toast could fly, but it doesn't 
fly
today and won't be able to fly anytime soon.

If someone there figures it out, please write an Internet-Draft (and
also put the running code up on an ftp site for folks to download
to see it working themselves).

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:41:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10630
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:41:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0hrx05339
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:43:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0hrv05336
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:43:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10621
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:41:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0h1v05301;
	Thu, 14 Nov 2002 19:43:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0gPv05275
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:42:25 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10591
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:39:42 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18CUYm-0007ME-00; Thu, 14 Nov 2002 19:42:12 -0500
Date: Thu, 14 Nov 2002 19:42:12 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: "'Bill Woodcock'" <woody@pch.net>,
        Henning Schulzrinne <hgs@cs.columbia.edu>,
        Gary Thom <gthom@delta-info.com>, ieprep <ieprep@ietf.org>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D2A@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211141940010.28260-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] What service providers say about Class/Quality of Service
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Thu, 14 Nov 2002, Nguyen, An wrote:
> By the way, you can charge your customers more if they want QoS for their
> service. You can always charge more for emergency personnel when they use
> you priority service.  Attached is the link you should check it out for
> yourself. http://www.genuity.com/services/access/ia/qos.htm

Here is a link you should also check out

http://www.sprintlink.net/policy/cos_guidelines.html

IMPORTANT: The sum of all bandwidth allocation on an interface cannot
exceed 75 percent of the total available interface bandwidth. The
remaining 25 percent is used for other overhead, including Layer 2
overhead, routing traffic and best-effort traffic.

Also, an overloaded service class will always yield poor service outcomes.
So the customer is advised not to consistently go beyond the bandwidth
allocations they.ve setup within their service class definitions (e.g.: an
overloaded LLQ priority queue for Voice Over IP traffic will yield either
poor voice quality or an inability to set new calls up).



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:43:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10704
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:43:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0jxH05430
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:45:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0jxv05427
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:45:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10685
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:43:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0j1v05392;
	Thu, 14 Nov 2002 19:45:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0iPv05358
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:44:25 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10644
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:41:42 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 5A5EA6711C; Thu, 14 Nov 2002 16:06:33 -0500 (EST)
Date: Thu, 14 Nov 2002 19:44:17 -0500
Subject: Re: [Ieprep] access links
Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>,
        "'ieprep '" <ieprep@ietf.org>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DD3AF24.9070900@cs.columbia.edu>
Message-Id: <5ED28444-F833-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 14, 2002, at 09:11 America/Montreal, Henning  
Schulzrinne wrote:
> http://www.cisco.com/en/US/tech/tk652/tk698/ 
> technologies_tech_note09186a0080094660.shtml
> http://www.nwfusion.com/news/2002/129521_01-28-2002.html
> http://www.sprintlink.net/faq/CoS_FAQ.htm  (Sprint access link  
> prioritization)
> http://www.juniper.net/techcenter/techpapers/200011-05.html
> http://www.bcr.com/access/2000/03/p20s1.asp
> http://newsroom.cisco.com/dlls/ts_092702.html
> http://www.fcw.com/fcw/articles/2000/0918/tec-voip-09-18-00.asp (Navy  
> VoIP)
> http://www.networking.ibm.com/voice/integration.html
> http://www1.avaya.com/enterprise/whitepapers/r300cisco.pdf
> http://www.oecd.org/pdf/M00003000/M00003121.pdf (QoS mentioned by a  
> provider - must be marketing :-))
> http://www.genuity.com/announcements/news/press_release_20021023-01.xml

I've read most of them.  I've followed up in detail with eng/ops folks
on most of them (Genuity is new enough that I haven't reached any  
closure
either way on that one).  So far, what I'm being told is that the  
marketing
is more substantial than the reality in most of the above URLs.

And if someone from Genuity is listening, it would be nice if you'd talk
with the chairs of IEprep about making a specific clear detailed  
technical
presentation on what you've done, how the deployment went, and what the
ops experience/costs are.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:45:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10783
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:45:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0lh405547
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:47:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0lhv05544
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:47:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10767
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:45:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0l2v05490;
	Thu, 14 Nov 2002 19:47:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0kRv05458
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:46:27 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10701
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:43:44 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id E17026711C; Thu, 14 Nov 2002 16:08:34 -0500 (EST)
Date: Thu, 14 Nov 2002 19:46:18 -0500
Subject: Re: [Ieprep] RE: network congestion, VoIP, NCS contracting approa ch, etc.
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: "Nguyen, An" <nguyena@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D2A@emshqs1.ncr.disa.mil>
Message-Id: <A73D0143-F833-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 14, 2002, at 09:20 America/Montreal, Nguyen, An wrote:
> By the way, you can charge your customers more if they want QoS for 
> their
> service. You can always charge more for emergency personnel when they 
> use
> you priority service.

That PR demonstrates the value of a PR.  What would be interesting would
be to discover what they've actually deployed, how it really behaves
both normally and under stress, and what the costs to them were.

If someone knows that first-hand, please do speak up.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:51:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10983
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:51:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0rnH05802
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:53:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0rnv05799
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:53:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10977
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:51:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0r2v05771;
	Thu, 14 Nov 2002 19:53:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0qhv05709
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:52:43 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10906
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:50:00 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 229E067103; Thu, 14 Nov 2002 16:14:51 -0500 (EST)
Date: Thu, 14 Nov 2002 19:52:34 -0500
Subject: Re: [Ieprep] representation & IETF culture
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep '" <ieprep@ietf.org>
To: "Steve Silverman" <steves@shentel.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <KMEJKAPHBBCMCDDGMBLOAEFGCAAA.steves@shentel.net>
Message-Id: <8779EF96-F834-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 14, 2002, at 10:37 America/Montreal, Steve Silverman 
wrote:
> While some have made a point that IETF attendees represent
> themselves as individuals rather than the organization they work
> for, it is also a fact that few of the attendees, pay their own way
> to the meetings.  I currently am paid by the DOD and because I take
> their money, and since I have considerable experience in meeting
> their needs, I tend to focus on those subjects that they want.
> Since I personally consider these needs to be legitimate
> requirements, I have no conflict representing their views.  I doubt
> that many of the attendees in Atlanta are without organizational
> support and few if any organizations would support someone who
> opposed their requirements.

Several of my employers, including NRL and DoD, have done so now and
in the past.  Giving away free crypto code was contrary to government
policy in the mid-90s, but I did just that under funding from ARPA
and SPAWAR, to give one example.[1]

> The DOD has certain functional requirements.

This is "requirements" in the meaning of "objectives or goals",
not "requirements" in the IETF sense of something one must
implement or deploy.  Getting our terminology differences straight
WILL help us all communicate better, IMHO.

> Whether or not a few
> people think these are "valid", if the DOD says it wants something
> and is willing to pay for it, then they have a right to attempt to
> buy it.

Please do.  Please don't use an IETF WG as political/marketing
air cover for that attempt.

> Many companies would like to be able to sell their equipment to the
> DOD.  Some companies might not be interested in this buisiness.

This is a good point for me to mention that my views are most
definitely NOT my employer's views on any number of topics.

> As to the lack of a possible way to provide better service, Houston
> Associates has built and tested a way to provide some users higher
> priority. We intend to submit an Internet Draft (Multi-Level
> Expedited Forwarding) for a new optional PHB that has been shown to
> solve some of this problem.  Considerable work remains to be done in
> terms of security but it will work well on a T1.  We are not worried
> about lines at optical rates (above E1). These don't generally share
> the problem of lack of  bandwidth.

That is a MUCH more helpful approach than *anything* happening in
this WG, IMHO.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 19:55:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11230
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:55:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0vrf05975
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 19:57:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0vrv05972
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:57:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11210
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 19:55:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0v1v05913;
	Thu, 14 Nov 2002 19:57:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0u8v05869
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 19:56:08 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11025
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:53:24 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 97EC067103; Thu, 14 Nov 2002 16:18:15 -0500 (EST)
Date: Thu, 14 Nov 2002 19:55:59 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'Bill Woodcock'" <woody@pch.net>, Mpierce1@aol.com,
        "Choi, Don" <choid@ncr.disa.mil>, ieprep@ietf.org
To: "Nguyen, An" <nguyena@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D30@emshqs1.ncr.disa.mil>
Message-Id: <01638656-F835-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 14, 2002, at 11:29 America/Montreal, Nguyen, An wrote:

> QoS is related to availability, survivability, and reliability.

Yes, normally deploying QoS in a packet network lowers all three of 
those.

> On a related issue, what I've kept hearing is to resolve congestions 
> and QoS
> issues by throwing more equipment at them. One of these presentations 
> ( I
> believe from QWest) says that "Now capital is limited" . I think a lot 
> of
> ISPs would agree with this statement and I am not speaking for Qwest 
> here.
> It indicated that serious traffic engineering needs to done utilizing 
> what
> are being deployed.

Most of the big ISPs already have their own facilities, and the fibres
are already lit up (often by large DWDM systems).

> By the way, what do you think about Genuity offering priority and QoS?

No way to tell from that press release what actually is deployed.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 20:01:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11570
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 20:01:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF13hc06335
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 20:03:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF13hv06332
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 20:03:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11507
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 20:00:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF133v06285;
	Thu, 14 Nov 2002 20:03:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF11gv06174
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 20:01:42 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11406
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:58:58 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 81B1B6711E; Thu, 14 Nov 2002 16:23:49 -0500 (EST)
Date: Thu, 14 Nov 2002 20:01:33 -0500
Subject: Re: [Ieprep] communications quality
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <bf.29c0f8a9.2b052bda@aol.com>
Message-Id: <C85F162A-F835-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 14, 2002, at 11:39 America/Montreal, Mpierce1@aol.com 
wrote:
> I really don't see you point, not do I think a majority of those 
> active on this list.

This is true for most points being made on this list by most people,
though I'd change "a majority" to "many".  The operators are 
understanding
the operators.  The NCS (and contractors) understand each other. I'm
not yet persuaded that either group has communicated *anything* to the
other group.

Sigh.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 20:01:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11583
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 20:01:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF13iF06351
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 20:03:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF13iv06348
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 20:03:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11520
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 20:01:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF133v06301;
	Thu, 14 Nov 2002 20:03:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF128v06193
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 20:02:08 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11425
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 19:59:24 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAF11hbd003992;
	Thu, 14 Nov 2002 20:01:43 -0500 (EST)
Date: Thu, 14 Nov 2002 20:01:43 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211150101.gAF11hbd003992@newdev.harvard.edu>
To: hgs@cs.columbia.edu, rja@extremenetworks.com
Subject: Re: [Ieprep] access links
Cc: ieprep@ietf.org, KIMBERLY.S.KING@saic.com
In-Reply-To: <5ED28444-F833-11D6-818A-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> And if someone from Genuity is listening, it would be nice if you'd talk
> with the chairs of IEprep about making a specific clear detailed  
> technical
> presentation on what you've done, how the deployment went, and what the
> ops experience/costs are.

please - that would be helpful

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 20:11:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11970
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 20:11:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF1Dxu07320
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 20:13:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1Dwv07317
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 20:13:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11966
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 20:11:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1D3v07289;
	Thu, 14 Nov 2002 20:13:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1BNv07237
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 20:11:23 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11887
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 20:08:39 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id C69A56711E; Thu, 14 Nov 2002 16:33:30 -0500 (EST)
Date: Thu, 14 Nov 2002 20:11:14 -0500
Subject: Re: [Ieprep] access router performance
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep '" <ieprep@ietf.org>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E7797A@mcl-its-exs01>
Message-Id: <22CA546F-F837-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 14, 2002, at 13:36 America/Montreal, King, Kimberly S. 
wrote:
> What this does is say that the access link in question is one that can 
> not
> be determined in advance.  This means one can't count on your CPE 
> router
> being provisioned for DiffServ or other QoS.

or even whether that CPE router has implemented *any* form of QoS that
could be enabled or whether the person with the privileged/config 
password
and appropriate clue is around to reconfigure it.

Most access routers are selected on the basis of lowest price.  This 
normally
means that they are implemented in a general purpose CPU (not ASIC, not 
NP).
CPU-based routers are the ones that are most likely to have forwarding
performance drops when more features (e.g. DiffServ, ACLs, RMON) are 
enabled.
One widely deployed T1 access router cannot forward at T1 line-rate once
QoS and ACLs and stuff are enabled.  It can forward at T1 line-rate if 
those
things are turned off.  Most users don't test for this before 
purchasing.

So the access routers are the ones MOST LIKELY to have degraded 
performance
(see Bill Woodcock's example) when QoS is enabled.[1]

Ran

[1] The two kinds of equipment LEAST likely to have degraded performance
with QoS enabled are core routers and gigabit switches -- because those
are most often (not always) built out of custom ASICs...

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 20:17:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12171
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 20:17:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF1JpE07543
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 20:19:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1Jpv07540
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 20:19:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12167
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 20:17:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1J0v07510;
	Thu, 14 Nov 2002 20:19:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1IKv07482
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 20:18:20 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12135
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 20:15:36 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAF1I6mw004077;
	Thu, 14 Nov 2002 20:18:06 -0500 (EST)
Date: Thu, 14 Nov 2002 20:18:06 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211150118.gAF1I6mw004077@newdev.harvard.edu>
To: rja@extremenetworks.com, steves@shentel.net
Subject: Re: [Ieprep] representation & IETF culture
Cc: ieprep@ietf.org
In-Reply-To: <8779EF96-F834-11D6-818A-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Thursday, Nov 14, 2002, at 10:37 America/Montreal, Steve Silverman 
wrote:
> While some have made a point that IETF attendees represent
> themselves as individuals rather than the organization they work
> for, it is also a fact that few of the attendees, pay their own way
> to the meetings.  I currently am paid by the DOD and because I take
> their money, and since I have considerable experience in meeting
> their needs, I tend to focus on those subjects that they want.
> Since I personally consider these needs to be legitimate
> requirements, I have no conflict representing their views.  I doubt
> that many of the attendees in Atlanta are without organizational
> support and few if any organizations would support someone who
> opposed their requirements.

I do not think the issue is who pays the hotel bill unless one   of the
conditions for getting the bill paid is to leave one's brain     on the
night stand back at home

it is *very* helpful to understand what organizations think their
requirements are in any IETF-related area - such organizations are the ones
that will be using (or trying to use) IETF protocols

but two things

1/ requirements need to be evaluated for their technical feasibility and
general usefulness - they not evaluated based on who said they  have the
requirements - requirements from individuals, small companies, big
companies, governments or the military will all get evaluated for their
technical feasibility and general usefulness

2/ it is very helpful if the people in the working group, including  those
people from organizations who have sent requirements to the IETF, are free
to openly discuss the issues around the technology and are not limited in
their mandate to just push a corporate line

when people say that people are here as individuals they mean that it will
not add to the strength of an argument (a technical point or requirement
for example) to say that big-co supports it - and is generally seen
as a sign of a poor technical position

to me the key phrase in the quote is "I personally consider these needs to
be legitimate requirements" - that should be the focus of the  discussion
not what the source of the requirements might be

requirements MUST NOT be dismissed just because they come from a
particular organization and they MUST NOT be accepted just for a similar
reason

 
Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 20:19:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12230
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 20:19:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF1Ld607663
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 20:21:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1Ldv07660
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 20:21:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12202
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 20:18:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1L1v07632;
	Thu, 14 Nov 2002 20:21:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1Kev07607
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 20:20:40 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12185
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 20:17:56 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 2774F6711E; Thu, 14 Nov 2002 16:42:44 -0500 (EST)
Date: Thu, 14 Nov 2002 20:20:27 -0500
Subject: Re: [Ieprep] Is this the service you are requesting?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "Ieprep (E-mail)" <ieprep@ietf.org>
To: Rex Buddenberg <budden@nps.navy.mil>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <1037305045.3604.659.camel@localhost.localdomain>
Message-Id: <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 14, 2002, at 15:17 America/Montreal, Rex Buddenberg 
wrote:
> What I want from those ISPs is a
> Hippocratic assurance that they won't mangle a DS byte along the way.

It is not very likely that a DS byte will survive an inter-domain
boundary intact.  Most likely it will get rewritten to DS == 0,
since the originating user is not a directly-attached customer of
the 2nd ISP.

We have a (really great) DiffServ implementation in our boxen.
THe main request from ISPs was the ability to rewrite the DS
byte of all packets received on an interface to a value specified
by the ISP.  When I asked why they wanted this, universal answer
was "to reset the IP ToS byte to zero" on all inbound interfaces.

> And some routers (usually border ones) will manipulate the DS
> byte -- core routers generally do not since they're too busy drinking
> from OC-48 pipes to fiddle with such nuisances.

Yes and yes.

> *in at least the Navy's case, the narrow links are in the interior of
> the network, not at the edge which the term 'tail circuit' implies.  We
> can overprovision both ashore and within the ship but not in the
> ship-shore area.

<humour>
Yeah.  They don't make spools of fibre long enough to stretch from
the pier at North Island to the carrier half-way to Pearl. :-)
</humour>

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 20:35:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12812
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 20:35:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF1bsT08844
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 20:37:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1brv08841
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 20:37:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12760
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 20:35:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1b1v08268;
	Thu, 14 Nov 2002 20:37:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1agv08210
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 20:36:42 -0500
Received: from mtiwmhc11.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12724
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 20:33:59 -0500 (EST)
Received: from cs.columbia.edu ([12.84.235.122])
          by mtiwmhc11.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP
          id <20021115013633.HVYD20682.mtiwmhc11.worldnet.att.net@cs.columbia.edu>;
          Fri, 15 Nov 2002 01:36:33 +0000
Message-ID: <3DD44F77.9030300@cs.columbia.edu>
Date: Thu, 14 Nov 2002 20:35:51 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: Rex Buddenberg <budden@nps.navy.mil>, "Ieprep (E-mail)" <ieprep@ietf.org>
Subject: Re: [Ieprep] Is this the service you are requesting?
References: <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

RJ Atkinson wrote:
> 

> It is not very likely that a DS byte will survive an inter-domain
> boundary intact.  Most likely it will get rewritten to DS == 0,
> since the originating user is not a directly-attached customer of
> the 2nd ISP.

Just curious: If no "real" ISP is using DSCPs, why would they care what 
value they have when entering or leaving their network?

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 20:53:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13271
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 20:53:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF1u1a09481
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 20:56:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1u1v09478
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 20:56:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13264
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 20:53:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1t4v09441;
	Thu, 14 Nov 2002 20:55:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF1s2v09408
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 20:54:02 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13233
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 20:51:18 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id ACA406711B; Thu, 14 Nov 2002 17:16:09 -0500 (EST)
Date: Thu, 14 Nov 2002 20:53:53 -0500
Subject: Re: [Ieprep] Is this the service you are requesting?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "Ieprep (E-mail)" <ieprep@ietf.org>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DD44F77.9030300@cs.columbia.edu>
Message-Id: <17EFD094-F83D-11D6-818A-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 14, 2002, at 20:35 America/Montreal, Henning 
Schulzrinne wrote:
> Just curious: If no "real" ISP is using DSCPs, why would they care
> what value they have when entering or leaving their network?

Not sure why they care about it.

Guess:	Defensive configuration of the network


Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 21:12:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13747
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 21:12:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF2EqV10619
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 21:14:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF2Eqv10616
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 21:14:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13734
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 21:12:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF2EDv10588;
	Thu, 14 Nov 2002 21:14:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF2Drv10569
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 21:13:53 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA13674
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 21:11:11 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 15 Nov 2002 02:11:13 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <W8NWNCLZ>; Thu, 14 Nov 2002 21:14:59 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D36@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock'" <woody@pch.net>, Mpierce1@aol.com
Cc: ieprep@ietf.org
Subject: RE: [Ieprep] Qualitative statement about quality
Date: Thu, 14 Nov 2002 21:13:39 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

I would imagine 600ms was for the route trip delay, not a one-way at all.
Because, otherwise, it would have a longer delay than satellite, which is
500ms it would take for the signal to bounce off a transponder (satellite
hop). Most of us notice that delay on TV when a news reporter speaks to a
news anchor back in the headquarters studio. There is always a long pause
between a caller and a callee; if they don't wait for each other to pause,
there will be a problem with the audio. According to the ITU recommendation
on voice, G.711 one-way delay does not exceed 200ms. Some codec experts need
to correct me if I am wrong on this.

By the way, 600ms is just the delay between San Luis Obispo and Berkley and
I assume this voice traffic stays within one AS.  The delay of this voice
call would go up if it has to traverse from 3 to 6 AS's (the average number
of AS's a call would go through.)

Regards,

An


-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Thursday, November 14, 2002 1:55 PM
To: Mpierce1@aol.com
Cc: ieprep@ietf.org
Subject: Re: [Ieprep] Qualitative statement about quality


      On Thu, 14 Nov 2002 Mpierce1@aol.com wrote:
    > We really need a clarification of this claim. What do you mean be
"latency"?
    > Do you mean one-way or round-trip delay of the voice? Or something
else.

Round-trip, same as anyone else means when they say latency.

    > Based on the same definition, what was the "latency" on the PSTN call
between
    > San Luis Obispo and Berkeley?

Who knows.  Presumably there are audio time-domain reflectometers, but I
doubt the CALREN2 guys had one.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 21:29:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14144
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 21:29:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF2W1Y11287
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 21:32:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF2W1v11284
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 21:32:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14131
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 21:29:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF2V7v11254;
	Thu, 14 Nov 2002 21:31:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF2Unv11168
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 21:30:49 -0500
Received: from mtiwmhc11.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14099
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 21:28:06 -0500 (EST)
Received: from cs.columbia.edu ([12.84.235.122])
          by mtiwmhc11.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP
          id <20021115023039.JDBN20682.mtiwmhc11.worldnet.att.net@cs.columbia.edu>;
          Fri, 15 Nov 2002 02:30:39 +0000
Message-ID: <3DD45C24.6020501@cs.columbia.edu>
Date: Thu, 14 Nov 2002 21:29:56 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Nguyen, An" <nguyena@ncs.gov>
CC: ieprep@ietf.org
Subject: Re: [Ieprep] Qualitative statement about quality
References: <7F18415E4D63CB45BB9B3A591F68D12D5B3D36@emshqs1.ncr.disa.mil>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

G.114 says 150 ms one way delay as upper limit for "regular" service; 
see my earlier note on this. The domestic PSTN delay is pretty much 0.6 
times speed of light, plus a few ms. There's nowhere for the voice to be 
buffered, except on the way to the geosync satellite... It's longer for 
PSTN wireless (we've measured up to 80 ms one way), due to transcoding 
and media access delays.

You probably won't notice 300 ms delay during a remote presentation, but 
it is very obvious during a true two-way interactive conversation. 
(Interestingly, humans adjust - apparently, talk spurts get longer as 
the delay increases, until the conversation becomes alternating monologues.)

Long delays significantly complicate the life of echo cancellers.

If you're interested: we've measured the one-way voice delay of a number 
of commercial VoIP phones (just the end-system induced part). There's a 
large difference across vendors.

Nguyen, An wrote:
> I would imagine 600ms was for the route trip delay, not a one-way at all.
> Because, otherwise, it would have a longer delay than satellite, which is
> 500ms it would take for the signal to bounce off a transponder (satellite
> hop). Most of us notice that delay on TV when a news reporter speaks to a
> news anchor back in the headquarters studio. There is always a long pause
> between a caller and a callee; if they don't wait for each other to pause,
> there will be a problem with the audio. According to the ITU recommendation
> on voice, G.711 one-way delay does not exceed 200ms. Some codec experts need
> to correct me if I am wrong on this.
> 
> By the way, 600ms is just the delay between San Luis Obispo and Berkley and
> I assume this voice traffic stays within one AS.  The delay of this voice
> call would go up if it has to traverse from 3 to 6 AS's (the average number
> of AS's a call would go through.)
> 
> Regards,
> 
> An
> 
> 
> -----Original Message-----
> From: Bill Woodcock [mailto:woody@pch.net]
> Sent: Thursday, November 14, 2002 1:55 PM
> To: Mpierce1@aol.com
> Cc: ieprep@ietf.org
> Subject: Re: [Ieprep] Qualitative statement about quality
> 
> 
>       On Thu, 14 Nov 2002 Mpierce1@aol.com wrote:
>     > We really need a clarification of this claim. What do you mean be
> "latency"?
>     > Do you mean one-way or round-trip delay of the voice? Or something
> else.
> 
> Round-trip, same as anyone else means when they say latency.
> 
>     > Based on the same definition, what was the "latency" on the PSTN call
> between
>     > San Luis Obispo and Berkeley?
> 
> Who knows.  Presumably there are audio time-domain reflectometers, but I
> doubt the CALREN2 guys had one.
> 
>                                 -Bill
> 
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 21:33:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14347
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 21:33:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF2Zsm11445
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 21:35:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF2Zsv11442
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 21:35:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14293
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 21:33:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF2Z1v11421;
	Thu, 14 Nov 2002 21:35:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF2YYv11383
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 21:34:34 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA14228
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 21:31:52 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 15 Nov 2002 02:28:40 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <WM4FRVVP>; Thu, 14 Nov 2002 21:34:28 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D37@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Sean Donelan'" <sean@donelan.com>
Cc: "'Bill Woodcock'" <woody@pch.net>,
        Henning Schulzrinne
	 <hgs@cs.columbia.edu>,
        Gary Thom <gthom@delta-info.com>, ieprep
	 <ieprep@ietf.org>
Date: Thu, 14 Nov 2002 21:34:20 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Ieprep] RE: What service providers say about Class/Quality of Service
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

As indicated in the earlier message that if the ISP don't do the right job
queuing their mixed ( voice and video) IP packets the voice would suffer
badly. The reason is voice packets in general are much shorter than video.
And it take much longer for   a router to process a video packet and a voice
packet. If voice packets don't stay ahead of video in the queue, then voice
traffic would get more delay. As a result, QoS for voice would suffer. 

My point in this is that every ISP has a different business model and a
different network architecture. I think it is wrong to declare that QoS is
not need at all IP networks. As you probably already saw an email early by
someone in which there is a long list of vendors that are interested in QoS.

Regards,

An
-----Original Message-----
From: Sean Donelan [mailto:sean@donelan.com]
Sent: Thursday, November 14, 2002 7:42 PM
To: Nguyen, An
Cc: 'Bill Woodcock'; Henning Schulzrinne; Gary Thom; ieprep
Subject: What service providers say about Class/Quality of Service


On Thu, 14 Nov 2002, Nguyen, An wrote:
> By the way, you can charge your customers more if they want QoS for their
> service. You can always charge more for emergency personnel when they use
> you priority service.  Attached is the link you should check it out for
> yourself. http://www.genuity.com/services/access/ia/qos.htm

Here is a link you should also check out

http://www.sprintlink.net/policy/cos_guidelines.html

IMPORTANT: The sum of all bandwidth allocation on an interface cannot
exceed 75 percent of the total available interface bandwidth. The
remaining 25 percent is used for other overhead, including Layer 2
overhead, routing traffic and best-effort traffic.

Also, an overloaded service class will always yield poor service outcomes.
So the customer is advised not to consistently go beyond the bandwidth
allocations they.ve setup within their service class definitions (e.g.: an
overloaded LLQ priority queue for Voice Over IP traffic will yield either
poor voice quality or an inability to set new calls up).


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 23:18:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17644
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 23:18:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF4L3R18192
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 23:21:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF4L3v18189
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 23:21:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17618
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 23:18:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF4K7v18129;
	Thu, 14 Nov 2002 23:20:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF4JKv18066
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 23:19:20 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17586
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 23:16:36 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18CXwW-0007U3-00; Thu, 14 Nov 2002 23:18:56 -0500
Date: Thu, 14 Nov 2002 23:18:56 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: "'Bill Woodcock'" <woody@pch.net>,
        Henning Schulzrinne <hgs@cs.columbia.edu>,
        Gary Thom <gthom@delta-info.com>, ieprep <ieprep@ietf.org>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D37@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211142255460.28737-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] RE: What service providers say about Class/Quality of Service
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Thu, 14 Nov 2002, Nguyen, An wrote:
> My point in this is that every ISP has a different business model and a
> different network architecture. I think it is wrong to declare that QoS is
> not need at all IP networks. As you probably already saw an email early by
> someone in which there is a long list of vendors that are interested in QoS.

Vendors sell what people buy, not what they need.  Remember tail fins on
cars?

There was a long list of vendors interested in OSI once upon a time too.
IBM, DEC, Burroughs, Tandem, Xerox, etc.  GOSIP was the law of the land
and government purchasing power meant something.

In an emergency, which is more like to work?  An OSI/GOSIP network or an
IP network? Something that works beats a requirement almost every time.
Why spend $10 million on a pen which will work in zero gravity, when a
pencil works?

As a vendor, I'm more than happy to take the government's money.  As a
citizen I have a hard time understanding why the government wants to spend
money fixing a problem when they don't even know if its a problem yet.
Why not try using a pencil?  Maybe you will find out it works.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 23:55:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18372
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 23:55:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF4vGt19817
	for ieprep-archive@odin.ietf.org; Thu, 14 Nov 2002 23:57:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF4vGv19814
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 23:57:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18364
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 23:54:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF4uGv19769;
	Thu, 14 Nov 2002 23:56:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF4tnv19745
	for <ieprep@optimus.ietf.org>; Thu, 14 Nov 2002 23:55:49 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18344
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 23:53:04 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAF4uSMU009000;
	Thu, 14 Nov 2002 20:56:28 -0800
Date: Thu, 14 Nov 2002 20:56:28 -0800
From: David Meyer <dmm@sprint.net>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: gthom@delta-info.com, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] RE: network congestion, VoIP, NCS contracting approach, etc.
Message-ID: <20021114205628.I8912@sprint.net>
References: <NDBBKMIGCLLNAOGKKDDPCEKFDDAA.gthom@delta-info.com> <FD101D94-F82D-11D6-818A-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <FD101D94-F82D-11D6-818A-00039357A82A@extremenetworks.com>; from rja@extremenetworks.com on Thu, Nov 14, 2002 at 07:05:45PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>> On Wednesday, Nov 13, 2002, at 13:26 America/Montreal, Gary Thom wrote:
>> 
>> > If there is no distinction, then when there is not enough bandwidth 
>> > for all
>> > of the _best-effort_ traffic (due to congestion or damage),
>> 
>> Did not happen 9/11, does not happen inside the backbone, and ISPs can't
>> fix the access link -- only the access users can fix *their* links.
>> No amount of mechanism inside the core can fix the access issues, if any
>> exist.

I completely agree with Ran here. And if there is an issue, it is on
the edge. Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 14 23:59:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18495
	for <ieprep-archive@odin.ietf.org>; Thu, 14 Nov 2002 23:59:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF524b20002
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 00:02:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF524v19999
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 00:02:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18485
	for <ieprep-web-archive@ietf.org>; Thu, 14 Nov 2002 23:59:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF515v19938;
	Fri, 15 Nov 2002 00:01:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF50Xv19911
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 00:00:33 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18445
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 23:57:48 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAF51D8i009014;
	Thu, 14 Nov 2002 21:01:13 -0800
Date: Thu, 14 Nov 2002 21:01:13 -0800
From: David Meyer <dmm@sprint.net>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: "Nguyen, An" <nguyena@ncs.gov>, "'Bill Woodcock'" <woody@pch.net>,
        Mpierce1@aol.com, "Choi, Don" <choid@ncr.disa.mil>, ieprep@ietf.org
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Message-ID: <20021114210113.J8912@sprint.net>
References: <7F18415E4D63CB45BB9B3A591F68D12D5B3D30@emshqs1.ncr.disa.mil> <01638656-F835-11D6-818A-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <01638656-F835-11D6-818A-00039357A82A@extremenetworks.com>; from rja@extremenetworks.com on Thu, Nov 14, 2002 at 07:55:59PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Thu, Nov 14, 2002 at 07:55:59PM -0500, RJ Atkinson wrote:
>> 
>> On Thursday, Nov 14, 2002, at 11:29 America/Montreal, Nguyen, An wrote:
>> 
>> > QoS is related to availability, survivability, and reliability.
>> 
>> Yes, normally deploying QoS in a packet network lowers all three of 
>> those.

Again, I agree with Ran, but would like Nguyen to explain his
statement. 

>> > On a related issue, what I've kept hearing is to resolve congestions 
>> > and QoS
>> > issues by throwing more equipment at them. One of these presentations 
>> > ( I
>> > believe from QWest) says that "Now capital is limited" . I think a lot 
>> > of
>> > ISPs would agree with this statement and I am not speaking for Qwest 
>> > here.
>> > It indicated that serious traffic engineering needs to done utilizing 
>> > what
>> > are being deployed.
>> 
>> Most of the big ISPs already have their own facilities, and the fibres
>> are already lit up (often by large DWDM systems).

Basically, the state of things is that the capital is already
spent (bandwidth), and (most) carriers have already gone though
the cost reduction exercise. It is true there is not new capital,
but who needs it (we've all already built out). It's about OPEX these
days. 

Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 00:07:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18717
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 00:07:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF59hD20851
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 00:09:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF59hv20848
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 00:09:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18696
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 00:06:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF592v20837;
	Fri, 15 Nov 2002 00:09:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF56gv20135
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 00:06:42 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18630
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 00:03:57 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAF57Ndg009064;
	Thu, 14 Nov 2002 21:07:23 -0800
Date: Thu, 14 Nov 2002 21:07:23 -0800
From: David Meyer <dmm@sprint.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: RJ Atkinson <rja@extremenetworks.com>,
        Rex Buddenberg <budden@nps.navy.mil>,
        "Ieprep (E-mail)" <ieprep@ietf.org>
Subject: Re: [Ieprep] Is this the service you are requesting?
Message-ID: <20021114210723.O8912@sprint.net>
References: <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com> <3DD44F77.9030300@cs.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3DD44F77.9030300@cs.columbia.edu>; from hgs@cs.columbia.edu on Thu, Nov 14, 2002 at 08:35:51PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Thu, Nov 14, 2002 at 08:35:51PM -0500, Henning Schulzrinne wrote:
>> RJ Atkinson wrote:
>> > 
>> 
>> > It is not very likely that a DS byte will survive an inter-domain
>> > boundary intact.  Most likely it will get rewritten to DS == 0,
>> > since the originating user is not a directly-attached customer of
>> > the 2nd ISP.
>> 
>> Just curious: If no "real" ISP is using DSCPs, why would they care what 
>> value they have when entering or leaving their network?

Because I might not honor the DSCP in my core, but I may on
egress (from my network).

Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 00:07:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18722
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 00:07:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF59i120866
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 00:09:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF59iv20863
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 00:09:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18699
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 00:06:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF590v20781;
	Fri, 15 Nov 2002 00:09:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF52Pv20018
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 00:02:25 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18489
	for <ieprep@ietf.org>; Thu, 14 Nov 2002 23:59:40 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAF5307R009032;
	Thu, 14 Nov 2002 21:03:00 -0800
Date: Thu, 14 Nov 2002 21:03:00 -0800
From: David Meyer <dmm@sprint.net>
To: Scott Bradner <sob@harvard.edu>
Cc: hgs@cs.columbia.edu, rja@extremenetworks.com, ieprep@ietf.org,
        KIMBERLY.S.KING@saic.com
Subject: Re: [Ieprep] access links
Message-ID: <20021114210300.L8912@sprint.net>
References: <5ED28444-F833-11D6-818A-00039357A82A@extremenetworks.com> <200211150101.gAF11hbd003992@newdev.harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <200211150101.gAF11hbd003992@newdev.harvard.edu>; from sob@harvard.edu on Thu, Nov 14, 2002 at 08:01:43PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Thu, Nov 14, 2002 at 08:01:43PM -0500, Scott Bradner wrote:
>> > And if someone from Genuity is listening, it would be nice if you'd talk
>> > with the chairs of IEprep about making a specific clear detailed  
>> > technical
>> > presentation on what you've done, how the deployment went, and what the
>> > ops experience/costs are.
>> 
>> please - that would be helpful

And what the opex buys you.

Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 00:07:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18745
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 00:07:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF59lw20882
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 00:09:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF59lv20879
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 00:09:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18705
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 00:07:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF591v20805;
	Fri, 15 Nov 2002 00:09:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF550v20081
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 00:05:01 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18570
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 00:02:16 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAF55ha1009045;
	Thu, 14 Nov 2002 21:05:43 -0800
Date: Thu, 14 Nov 2002 21:05:43 -0800
From: David Meyer <dmm@sprint.net>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: Rex Buddenberg <budden@nps.navy.mil>, "Ieprep (E-mail)" <ieprep@ietf.org>
Subject: Re: [Ieprep] Is this the service you are requesting?
Message-ID: <20021114210543.M8912@sprint.net>
References: <1037305045.3604.659.camel@localhost.localdomain> <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com>; from rja@extremenetworks.com on Thu, Nov 14, 2002 at 08:20:27PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Thu, Nov 14, 2002 at 08:20:27PM -0500, RJ Atkinson wrote:
>> 
>> On Thursday, Nov 14, 2002, at 15:17 America/Montreal, Rex Buddenberg 
>> wrote:
>> > What I want from those ISPs is a
>> > Hippocratic assurance that they won't mangle a DS byte along the way.
>> 
>> It is not very likely that a DS byte will survive an inter-domain
>> boundary intact. 

Right, like P(survival) == 0 if I offer a service based on the DS byte
(since I have to wipe it on ingress).

Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 01:50:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21188
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 01:50:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF6qRg25669
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 01:52:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF6qQv25666
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 01:52:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21173
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 01:49:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF6pkv25544;
	Fri, 15 Nov 2002 01:51:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF6mAv25285
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 01:48:10 -0500
Received: from sparcticus.sysctl.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21084
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 01:45:24 -0500 (EST)
Received: from localhost (scott@localhost)
	by sparcticus.sysctl.net (8.10.1/8.10.1) with ESMTP id gAF6l6g26996;
	Fri, 15 Nov 2002 06:47:06 GMT
Date: Fri, 15 Nov 2002 06:47:05 +0000 (GMT)
From: Scott Madley <scott@xgcic.net>
X-X-Sender:  <scott@sparcticus.sysctl.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: "Nguyen, An" <nguyena@ncs.gov>, <ieprep@ietf.org>
Subject: Re: [Ieprep] Qualitative statement about quality
In-Reply-To: <3DD45C24.6020501@cs.columbia.edu>
Message-ID: <Pine.BSO.4.33.0211150630530.4164-100000@sparcticus.sysctl.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

If any one has an interest, I'll see if I can dredge up some PSQM/MOS
results from about a year ago that I complied that compare/contrast voice
quality on both the PSTN and a dedicated VoIP network, and the associated
results when off-loading to either the PSTN or a NGN network.

-Scott

On Thu, 14 Nov 2002, Henning Schulzrinne wrote:

> G.114 says 150 ms one way delay as upper limit for "regular" service;
> see my earlier note on this. The domestic PSTN delay is pretty much 0.6
> times speed of light, plus a few ms. There's nowhere for the voice to be
> buffered, except on the way to the geosync satellite... It's longer for
> PSTN wireless (we've measured up to 80 ms one way), due to transcoding
> and media access delays.
>
> You probably won't notice 300 ms delay during a remote presentation, but
> it is very obvious during a true two-way interactive conversation.
> (Interestingly, humans adjust - apparently, talk spurts get longer as
> the delay increases, until the conversation becomes alternating monologues.)
>
> Long delays significantly complicate the life of echo cancellers.
>
> If you're interested: we've measured the one-way voice delay of a number
> of commercial VoIP phones (just the end-system induced part). There's a
> large difference across vendors.
>
> Nguyen, An wrote:
> > I would imagine 600ms was for the route trip delay, not a one-way at all.
> > Because, otherwise, it would have a longer delay than satellite, which is
> > 500ms it would take for the signal to bounce off a transponder (satellite
> > hop). Most of us notice that delay on TV when a news reporter speaks to a
> > news anchor back in the headquarters studio. There is always a long pause
> > between a caller and a callee; if they don't wait for each other to pause,
> > there will be a problem with the audio. According to the ITU recommendation
> > on voice, G.711 one-way delay does not exceed 200ms. Some codec experts need
> > to correct me if I am wrong on this.
> >
> > By the way, 600ms is just the delay between San Luis Obispo and Berkley and
> > I assume this voice traffic stays within one AS.  The delay of this voice
> > call would go up if it has to traverse from 3 to 6 AS's (the average number
> > of AS's a call would go through.)
> >
> > Regards,
> >
> > An
> >
> >
> > -----Original Message-----
> > From: Bill Woodcock [mailto:woody@pch.net]
> > Sent: Thursday, November 14, 2002 1:55 PM
> > To: Mpierce1@aol.com
> > Cc: ieprep@ietf.org
> > Subject: Re: [Ieprep] Qualitative statement about quality
> >
> >
> >       On Thu, 14 Nov 2002 Mpierce1@aol.com wrote:
> >     > We really need a clarification of this claim. What do you mean be
> > "latency"?
> >     > Do you mean one-way or round-trip delay of the voice? Or something
> > else.
> >
> > Round-trip, same as anyone else means when they say latency.
> >
> >     > Based on the same definition, what was the "latency" on the PSTN call
> > between
> >     > San Luis Obispo and Berkeley?
> >
> > Who knows.  Presumably there are audio time-domain reflectometers, but I
> > doubt the CALREN2 guys had one.
> >
> >                                 -Bill
> >
> >
> > _______________________________________________
> > Ieprep mailing list
> > Ieprep@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ieprep
> > _______________________________________________
> > Ieprep mailing list
> > Ieprep@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ieprep
>
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 02:28:19 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01532
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 02:28:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF7UZu03773
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 02:30:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF7UYv03770
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 02:30:34 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01517
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 02:27:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF7Tgv03691;
	Fri, 15 Nov 2002 02:29:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF7O9v03462
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 02:24:09 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01376
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 02:21:22 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <QXJ5F63M>; Fri, 15 Nov 2002 02:21:46 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A414969@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] NCS contracts with voice IXCs
Date: Fri, 15 Nov 2002 02:21:36 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Exactly my point.  

The (proposed, future) "IP packet switching core" within the VOICE IXC's
network is NOT going to be the ISP that runs under the same corporate name.
I am not talking about a contract with the ISP side of the business.  I am
talking about a contract with the VOICE side of the business, that will
include IP technology in its network.

Who knows whether THAT (sub)network will be over provisioned or not?  Since
it doesn't  exist yet, it WILL require new (now scarce) capital.

Who knows what other performance characteristics it will have?

-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Thursday, November 14, 2002 7:35 PM
To: Gunn, Janet
Cc: ieprep
Subject: Re: [Ieprep] NCS contracts with voice IXCs



On Wednesday, Nov 13, 2002, at 20:36 America/Montreal, Gunn, Janet 
wrote:
> I'm wading through a weeks's worth of email, so this may have already 
> been
> addressed.
>
> I think the initial concern is about IP networks within the core of 
> networks
> offered by the IXC carriers with whom the NCS already has contractual
> relationships for GETS and GETS-like services.

Ownership doesn't imply much of a relationship.  A large ISP whose 
parent
has lots of dark fibre was unable to get the Transmission folks (== 
SONET
and dark fibre) to let them have access to facilities.  This led the ISP
to go heavily into traffic engineering so they could glue together 
disparate
parallel links.

Most ISPs that are owned by voice IXCs are operated VERY separately
from the voice IXC subsidiary.  And in most cases that I'm familiar 
with,
the two business units are not on civil speaking terms.

So I don't think that those existing voice contracts relate to much 
probability
of getting an ISP contract with NCS for anything other than best-effort.

But it was a good topic to raise because I think that the stuff I've 
just
outlined might not have been obvious to everyone.

Ran
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 03:40:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02834
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 03:40:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF8gbo08339
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 03:42:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF8gYv08336
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 03:42:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02814
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 03:39:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF8fnv08289;
	Fri, 15 Nov 2002 03:41:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF8Yxv07440
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 03:34:59 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02705
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 03:32:09 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAF8Sdd21635;
	Fri, 15 Nov 2002 00:28:40 -0800 (PST)
Date: Fri, 15 Nov 2002 00:28:39 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Steve Silverman <steves@shentel.net>, "'ieprep '" <ieprep@ietf.org>
Subject: Re: [Ieprep] representation & IETF culture
In-Reply-To: <8779EF96-F834-11D6-818A-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211150023350.21526-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 14 Nov 2002, RJ Atkinson wrote:
    > > The DOD has certain functional requirements.
    > This is "requirements" in the meaning of "objectives or goals",
    > not "requirements" in the IETF sense of something one must
    > implement or deploy.  Getting our terminology differences straight
    > WILL help us all communicate better, IMHO.

Oh, come on, Ran, there's such a thing as being too conciliatory, you
know?  This is just ridiculous.  If someone doesn't know what a word
means, saying that you'll excuse them on the basis of cultural relativism
and coming to a compromise where you halfway-accept their misuse doesn't
do them a favor.

"Requirement" means something compulsory, requisite, necessary, compelled.
Not someone else's passing whim.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 03:43:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02888
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 03:43:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF8jLn08498
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 03:45:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF8jLv08495
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 03:45:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02879
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 03:42:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF8iiv08395;
	Fri, 15 Nov 2002 03:44:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF8e4v08209
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 03:40:05 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02750
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 03:37:19 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAF8Xqd21665;
	Fri, 15 Nov 2002 00:33:53 -0800 (PST)
Date: Fri, 15 Nov 2002 00:33:52 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: RJ Atkinson <rja@extremenetworks.com>,
        Rex Buddenberg <budden@nps.navy.mil>,
        "Ieprep (E-mail)" <ieprep@ietf.org>
Subject: Re: [Ieprep] Is this the service you are requesting?
In-Reply-To: <3DD44F77.9030300@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211150032170.21526-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 14 Nov 2002, Henning Schulzrinne wrote:
    > Just curious: If no "real" ISP is using DSCPs, why would they care what
    > value they have when entering or leaving their network?

Because the consequences of QoS control (to use Rex's distinction)
occurring on a production network are so dire that precautions must be
taken to avoid acidentally triggering little bits of it which may be
active through misconfiguration, implicit defaults, or vendor bugs.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 04:08:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03302
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 04:08:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF9B4Q10306
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 04:11:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF9B4v10303
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 04:11:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03275
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 04:08:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF9ARv10231;
	Fri, 15 Nov 2002 04:10:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF98iv10099
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 04:08:44 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03243
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 04:05:57 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAF92Jd21958;
	Fri, 15 Nov 2002 01:02:19 -0800 (PST)
Date: Fri, 15 Nov 2002 01:02:19 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: Mpierce1@aol.com, <ieprep@ietf.org>
Subject: RE: [Ieprep] Qualitative statement about quality
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D36@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211150034450.21526-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 14 Nov 2002, Nguyen, An wrote:
    > I would imagine 600ms was for the route trip delay, not a one-way at all.

Correct.  Latency on packet-switched networks is nearly universally
measured and denoted as round-trip times, since measuring one-way delay
requires active measurement equipment at both endpoints, which nearly
never exists.

    > By the way, 600ms is just the delay between San Luis Obispo and Berkley and
    > I assume this voice traffic stays within one AS.  The delay of this voice
    > call would go up if it has to traverse from 3 to 6 AS's (the average number
    > of AS's a call would go through.)

I can't quite make out what you're saying here.  600ms was the observed
latency between San Luis Obispo and Nairobi, at the time of the call.  The
observed latency between San Luis Obisbo and Berkeley was about 200ms
across four ASes.  As I trace Berkeley to Nairobi right now, I get about
950ms, 42% drop, and seven ASes in the path.  It's not peak use hours in
either location at the moment, and this is a path which we use many times
each day for routine calls, when it's qualitatively much worse than it is at
the moment.  The quality of the VoIP calls is much, much higher than that
of PSTN calls, and it's difficult to keep the PSTN calls up...  Initial
call-completion rate is only about 80%, and most calls are dropped within
twenty minutes.  We've never had a failed connection or a dropped call
between this pair of VoIP phones, by contrast.

router.brk#trace nbi.ispkenya.com
Translating "nbi.ispkenya.com"...domain server (131.161.3.1) [OK]

Type escape sequence to abort.
Tracing the route to nbi.ispkenya.com (212.49.87.2)

  1 131.13.22.157.zocalo.net (157.22.13.131) [AS715] 4 msec 4 msec 8 msec
  2 gige-g2-0.gsr12008.pao.he.net (64.71.128.117) [AS 6939] 4 msec 4 msec 0 msec
  3 interconnect-eng.SanJose1.Level3.net (209.245.146.201) [AS 3356] 0 msec 20 msec 4 msec
  4 GigabitEthernet3-0.core1.SanJose1.Level3.net (209.244.3.245) [AS 3356] 4 msec 4 msec 4 msec
  5 ae0-51.mp1.SanJose1.Level3.net (64.159.2.1) [AS 3356] 4 msec 4 msec 4 msec
  6 so-3-0-0.mp1.NewYork1.Level3.net (64.159.1.41) [AS 3356] 80 msec 80 msec 80 msec
  7 gige9-0-53.hsipaccess1.NewYork1.Level3.net (64.159.17.71) [AS 3356] 76 msec 76 msec 76 msec
  8 unknown.Level3.net (209.244.160.242) [AS 3356] 81 msec 92 msec 80 msec
  9 host-66-133-0-22.verestar.net (66.133.0.22) [AS 11908] 156 msec 156 msec 157 msec
 10 unknown.Level3.net (64.158.116.117) [AS 11908] 188 msec 184 msec 185 msec
 11 host-66-133-6-2.verestar.net (66.133.6.2) [AS 11908] 184 msec 184 msec 185 msec
 12  * host-66-133-6-10.verestar.net (66.133.6.10) [AS 11908] 725 msec 725 msec
 13 212.49.70.109 [AS 12455] 745 msec 741 msec 753 msec
 14  * 10.10.2.10 781 msec *
 15 64.86.231.2 [AS 6453] 978 msec 901 msec 1859 msec
router.brk#ping
Protocol [ip]:
Target IP address: 212.49.87.2
Repeat count [5]: 100
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 212.49.87.2, timeout is 2 seconds:
.!!!!!.!..!!!!.!!...!!!!.!!!.!!...!!!!!.!!...!...!.!!.!...!!.!!!!...!.
..!..!!.!.!!!!!!.!.!!!!!.!..!.
Success rate is 58 percent (58/100), round-trip min/avg/max = 774/959/1262 ms
router.brk#

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 07:45:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06878
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 07:45:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFClFj20965
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 07:47:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFClFv20962
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 07:47:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06852
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 07:44:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFCkAv20876;
	Fri, 15 Nov 2002 07:46:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFCf4v20689
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 07:41:04 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06720
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 07:38:26 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAFCf1l8017731
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Fri, 15 Nov 2002 07:41:01 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAFCexdG014866
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 15 Nov 2002 07:41:00 -0500 (EST)
Message-ID: <3DD4EB45.7080003@cs.columbia.edu>
Date: Fri, 15 Nov 2002 07:40:37 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Meyer <dmm@sprint.net>
CC: "Ieprep (E-mail)" <ieprep@ietf.org>
Subject: Re: [Ieprep] Is this the service you are requesting?
References: <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com> <3DD44F77.9030300@cs.columbia.edu> <20021114210723.O8912@sprint.net>
In-Reply-To: <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Are you saying your network is setting DSCP to a non-zero value for some 
packets? Otherwise, if you set all DSCPs to zero on ingress, there's 
nothing to honor on egress (since they'll all be zero anyway). I'm 
confused... Or are you keeping the DSCP of direct customers of yours?

>
> Because I might not honor the DSCP in my core, but I may on
> egress (from my network).
>
> Dave


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 07:46:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06930
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 07:46:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFCmrK21047
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 07:48:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFCmrv21044
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 07:48:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06923
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 07:46:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFCm0v21018;
	Fri, 15 Nov 2002 07:48:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFClTv20998
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 07:47:29 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06871
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 07:44:51 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAFCmIx3010069;
	Fri, 15 Nov 2002 04:48:18 -0800
Date: Fri, 15 Nov 2002 04:48:18 -0800
From: David Meyer <dmm@sprint.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: "Ieprep (E-mail)" <ieprep@ietf.org>
Subject: Re: [Ieprep] Is this the service you are requesting?
Message-ID: <20021115044818.A10062@sprint.net>
References: <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com> <3DD44F77.9030300@cs.columbia.edu> <20021114210723.O8912@sprint.net> <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com> <3DD4EB45.7080003@cs.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3DD4EB45.7080003@cs.columbia.edu>; from hgs@cs.columbia.edu on Fri, Nov 15, 2002 at 07:40:37AM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Let's see if I can clarify: If I have a service where customers
set (or I set for them) DSCP on ingress to my network, ingore
them in my core (becauses it doesn't matter there), then honor
them on egress (because that's where it matters), then I have to
wipe those  bits on every ingress (including peering links) that
doesn't subscribe to the service. Otherwise the service can be
stolen or DoS'ed (it can be anyway, but this is the minimin you
must do). 

Does this help?

Dave

On Fri, Nov 15, 2002 at 07:40:37AM -0500, Henning Schulzrinne wrote:
>> Are you saying your network is setting DSCP to a non-zero value for some 
>> packets? Otherwise, if you set all DSCPs to zero on ingress, there's 
>> nothing to honor on egress (since they'll all be zero anyway). I'm 
>> confused... Or are you keeping the DSCP of direct customers of yours?
>> 
>> >
>> > Because I might not honor the DSCP in my core, but I may on
>> > egress (from my network).
>> >
>> > Dave
>> 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 07:53:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07086
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 07:53:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFCu1b21294
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 07:56:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFCu1v21291
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 07:56:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07079
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 07:53:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFCt2v21268;
	Fri, 15 Nov 2002 07:55:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFCssv21242
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 07:54:54 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07052
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 07:52:16 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAFCsml8018658
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Fri, 15 Nov 2002 07:54:48 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAFCsldG015902
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 15 Nov 2002 07:54:48 -0500 (EST)
Message-ID: <3DD4EE81.1020808@cs.columbia.edu>
Date: Fri, 15 Nov 2002 07:54:25 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Meyer <dmm@sprint.net>
CC: "Ieprep (E-mail)" <ieprep@ietf.org>
Subject: Re: [Ieprep] Is this the service you are requesting?
References: <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com> <3DD44F77.9030300@cs.columbia.edu> <20021114210723.O8912@sprint.net> <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com> <3DD4EB45.7080003@cs.columbia.edu> <20021115044818.A10062@sprint.net>
In-Reply-To: <6CB0235D-F838-11D6-818A-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yes, thanks - so it's "you need to pay to get those bits across" :-)

I suspect that the conclusion is that for resource control on access 
links, you'll effectively need per-flow reservation since incoming "high 
value" bits in all likelihood won't get the access link treatment you 
want. About the only case where it might work would be some form of 
same-ISP VPN.

David Meyer wrote:

> Let's see if I can clarify: If I have a service where customers
> set (or I set for them) DSCP on ingress to my network, ingore
> them in my core (becauses it doesn't matter there), then honor
> them on egress (because that's where it matters), then I have to
> wipe those  bits on every ingress (including peering links) that
> doesn't subscribe to the service. Otherwise the service can be
> stolen or DoS'ed (it can be anyway, but this is the minimin you
> must do).
>
> Does this help?
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 08:06:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07394
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 08:06:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFD8eT22259
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 08:08:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFD8ev22256
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 08:08:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07374
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 08:06:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFD82v22239;
	Fri, 15 Nov 2002 08:08:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFD7gv22220
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 08:07:42 -0500
Received: from seahorse.shentel.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07342
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 08:05:04 -0500 (EST)
Received: from steves (ha96s342.d.shentel.net [204.111.97.86])
	by seahorse.shentel.net (8.11.6/8.11.6) with SMTP id gAFD7SM20212;
	Fri, 15 Nov 2002 08:07:29 -0500
From: "Steve Silverman" <steves@shentel.net>
To: "Bill Woodcock" <woody@pch.net>, "RJ Atkinson" <rja@extremenetworks.com>
Cc: "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] representation & IETF culture
Date: Fri, 15 Nov 2002 08:07:40 -0500
Message-ID: <KMEJKAPHBBCMCDDGMBLOOEGICAAA.steves@shentel.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <Pine.GSO.4.44.0211150023350.21526-100000@paixhost.pch.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Bill,
Thank you, you are correct.  These are necessary functions (which
already exist) without which, the new technology can not be adopted.

Steve

> -----Original Message-----
> From: Bill Woodcock [mailto:woody@pch.net]
> Sent: Friday, November 15, 2002 3:29 AM
> To: RJ Atkinson
> Cc: Steve Silverman; 'ieprep '
> Subject: Re: [Ieprep] representation & IETF culture
>
>
>       On Thu, 14 Nov 2002, RJ Atkinson wrote:
>     > > The DOD has certain functional requirements.
>     > This is "requirements" in the meaning of
> "objectives or goals",
>     > not "requirements" in the IETF sense of something one must
>     > implement or deploy.  Getting our terminology
> differences straight
>     > WILL help us all communicate better, IMHO.
>

.....
>
> "Requirement" means something compulsory, requisite,
> necessary, compelled.
> Not someone else's passing whim.
>
>                                 -Bill
>
>
>


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 08:13:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07504
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 08:13:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFDFrT22442
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 08:15:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDFrv22439
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 08:15:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07499
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 08:13:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDF1v22421;
	Fri, 15 Nov 2002 08:15:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDE6v22395
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 08:14:06 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07480
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 08:11:28 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAFDCSFg000554;
	Fri, 15 Nov 2002 08:12:28 -0500 (EST)
Date: Fri, 15 Nov 2002 08:12:28 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211151312.gAFDCSFg000554@newdev.harvard.edu>
To: hgs@cs.columbia.edu, rja@extremenetworks.com
Subject: Re: [Ieprep] Is this the service you are requesting?
Cc: ieprep@ietf.org
In-Reply-To: <17EFD094-F83D-11D6-818A-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Schulzrinne wrote:
> Just curious: If no "real" ISP is using DSCPs, why would they care
> what value they have when entering or leaving their network?

because many ISPs do use these bits to prioritize routing & management traffic 
in their net and they do not want incoming traffic to get prioritized
and overload the routing & management packets - they can do this
because they do not have to worry that this type of traffic will ever 
be enough to overload links on its own (and if this traffic does
not go through the net does not work)

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 08:15:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07570
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 08:15:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFDHrN22507
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 08:17:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDHrv22504
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 08:17:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07560
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 08:15:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDH3v22489;
	Fri, 15 Nov 2002 08:17:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDGev22472
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 08:16:40 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07526
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 08:14:02 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAFDEg22000567;
	Fri, 15 Nov 2002 08:14:42 -0500 (EST)
Date: Fri, 15 Nov 2002 08:14:42 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211151314.gAFDEg22000567@newdev.harvard.edu>
To: nguyena@ncs.gov, sean@donelan.com
Subject: Re: [Ieprep] RE: What service providers say about Class/Quality of Service
Cc: gthom@delta-info.com, hgs@cs.columbia.edu, ieprep@ietf.org, woody@pch.net
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D37@emshqs1.ncr.disa.mil>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> As indicated in the earlier message that if the ISP don't do the right job
> queuing their mixed ( voice and video) IP packets the voice would suffer
> badly.

I'm not sure I buy this for OC48 backbones and the like
the difference between a long & short packet is a few microseconds

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 13:52:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15323
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 13:52:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFIsaF07593
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 13:54:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFIsZv07590
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 13:54:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15308
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 13:51:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFIr6v07561;
	Fri, 15 Nov 2002 13:53:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFImav07412
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 13:48:36 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15197
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 13:45:55 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Fri, 15 Nov 2002 10:45:05 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gAFIk6b9019305;
	Fri, 15 Nov 2002 10:46:06 -0800 (PST)
Subject: Re: [Ieprep] representation & IETF culture
From: Rex Buddenberg <budden@nps.navy.mil>
To: Bill Woodcock <woody@pch.net>
Cc: RJ Atkinson <rja@extremenetworks.com>,
        Steve Silverman
	 <steves@shentel.net>, "'ieprep '" <ieprep@ietf.org>
In-Reply-To: <Pine.GSO.4.44.0211150023350.21526-100000@paixhost.pch.net>
References: <Pine.GSO.4.44.0211150023350.21526-100000@paixhost.pch.net>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 15 Nov 2002 10:43:36 -0800
Message-Id: <1037385817.1091.720.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Fri, 2002-11-15 at 00:28, Bill Woodcock wrote:

> "Requirement" means something compulsory, requisite, necessary, compelled.
> Not someone else's passing whim.
>

Not in the government, Bill.

You've obviously never had your government acquisition lobotomy.

The intellectual root (ignoring the cultural and legal aspects for a
moment) lies in the difficulty in defining requirements.  We're all
educated as problem solvers ... think of the last test question you
worked on.  
     Few people get the feel for looking at a set of symptoms and
divining the root problem(s) several layers deep.  This is a
particularly hard exercise when you're dealing with disruptive
technologies and this is an instance where Internet technology is
definitely disruptive.

In theory, DoD requirements are supposed to come from the field -- the
combatant commanders.  These then go to JCS who shepherds a set of
capstone requirements documents through the system that are supposed to,
top-down, drive several operational requirements documents.  If you
caught it, we just went through not one, but two many-to-many
relationship knotholes.  
	There are two egregious corruptions of the system that tend to occur
here:
	- the 'requirements' tend to come in the form of 'buy me this solution'
rather than 'solve this problem', opening the door for all kinds of
brochure-engineering. We're seeing it in the form of 'make GETS work
over the internet' rather than how can the internet support emergency
services better.  
	- the poor articulation of field requirements is 'compensated' by some
entity in DC (lobbyists included) ghosting the requirement.  The terms
'empire building' and 'self-licking ice cream cones' have appeared to
describe this phenomenon.  The result is that we solve problems we know
how to solve, not the ones that need to be solved. (reprise the
disruptive technology comment). To be fair, this synthesis is often
vital for scalability reasons so simply proscribing it won't help.

Government, unlike commercial business, doesn't have the profit/loss
correction mechanism on such behavior.  So we keep trying to reinvent
other means; so far,in the history of the republic, we've been
unsuccessful.  (You can observe that Stalin was markedly less successful
at the same game).


All this is compounded by the government's inability to maintain subject
matter experts in-house.  Without getting into the reasons why, one
solution to this problem is to hire engineering support contractors. 
The trap that occurs here is that the contractor ends up doing what it
says in his contract (he wants to be paid and he wants the contract to
be renewed so he gets paid next year too).  And that incentive can be
strong enough that the contractor will tell the government agent what he
wants to hear rather than what he needs to know (in the vernacular, the
contractor is in stoop&fetch mode). The system is not designed for
intellectual honesty, regardless of the integrity of the individuals
involved.  
	An additional impediment along the way is that the government doesn't
let just anybody spend the taxpayers' money -- you have to be a
Contracting Officer to do that (and have a 'warrant' -- apt term, don't
you think?) in your possession authorizing you to do so.  So when the
program manager latches onto a KO ('CO' means commanding officer, thus
the re-alphabetizing),who's had all the requisite acquisition training,
the one thing you can rely on is that the clue density between them will
not go up.  


Want an illustration (this is a sea story alert)?  Few years ago, one of
my thesis students was working on a mine warfare problem.  The first
need for countering sea mines is to know where they are.  Then 1) you
tell the rest of the world where not to go and 2) you can tell your mine
clearance guys where _to_ go.  The tactical means to do this is to drag
a side-scan sonar behind a helicopter and take pictures of the ocean
bottom -- if something goes BANG, it's the sonar, not the helo.  The
problem was that the data (in the form of TV pictures) stayed in the
helo until it landed and the videotapes were sneakernetted off to the
opcen to be reviewed.  
	After going through the DC requirements mill, the 'requirement' came to
my student as 'we need full motion video over the horizon'.  Which you
should recognize as rather expensive and impractical.  Fortunately, at
thesis time, we have about as many counters to the silly requirements
exercise in place as there are likely to be.  Once we got an actual
videotape (cleanup of Persian Gulf after the war -- densest minefield US
Navy has dealt with since Korea), we were able to peel off a couple
layers of the onion:
	The data isn't really full motion at all -- use of NTSC video was
simply an engineering convenience.  
	Further, about 90% of the ocean bottom was featureless sand -- zero
interest.  All we really need is snapshots of areas of interest (mines
and tolerance for a fairly high false alarm rate). 
	 That banged the bandwidth requirement down to a size that would fit
through the 3kHz HF radio that's already installed in the aircraft.  

So one of the ID exercises is to peel off the onion layers and figure
out what the problem is.  IETF is better than the average bear at this
-- the continuing opportunity for charter-bashing is one of the
artifacts.  Allows us to think about whether or not we're solving the
right problem.  

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 14:26:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16223
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 14:26:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFJSET09413
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 14:28:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJSEv09410
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 14:28:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16219
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 14:25:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJRGv09367;
	Fri, 15 Nov 2002 14:27:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJQOv09333
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 14:26:24 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16185
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 14:23:42 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAFJKDd26517;
	Fri, 15 Nov 2002 11:20:13 -0800 (PST)
Date: Fri, 15 Nov 2002 11:20:12 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Rex Buddenberg <budden@nps.navy.mil>
cc: RJ Atkinson <rja@extremenetworks.com>,
        Steve Silverman <steves@shentel.net>, "'ieprep '" <ieprep@ietf.org>
Subject: Re: [Ieprep] representation & IETF culture
In-Reply-To: <1037385817.1091.720.camel@localhost.localdomain>
Message-ID: <Pine.GSO.4.44.0211151115550.22350-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On 15 Nov 2002, Rex Buddenberg wrote:
    > > "Requirement" means something compulsory, requisite, necessary, compelled.
    > > Not someone else's passing whim.
    > Not in the government, Bill.

No, in the English lanugage, which is our one hope for bridging this gap.
If we don't share a common language, I'm hard-pressed to imagine a way of
discovering commonalities of understanding and belief.

A little REQUISITE reading for anyone who doesn't believe this is a
really serious problem:
http://dogbert.abebooks.com/servlet/BookDetailsPL?bi=74999286

...and then Rex went on to say about three more pages about the process
of scientific inquiry which I agreed with.


                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 14:34:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16441
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 14:34:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFJb4h10036
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 14:37:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJb4v10033
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 14:37:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16428
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 14:34:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJa2v09848;
	Fri, 15 Nov 2002 14:36:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJXov09674
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 14:33:50 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16353
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 14:31:08 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAFJRed26578;
	Fri, 15 Nov 2002 11:27:40 -0800 (PST)
Date: Fri, 15 Nov 2002 11:27:40 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Steve Silverman <steves@shentel.net>
cc: RJ Atkinson <rja@extremenetworks.com>, "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] representation & IETF culture
In-Reply-To: <KMEJKAPHBBCMCDDGMBLOOEGICAAA.steves@shentel.net>
Message-ID: <Pine.GSO.4.44.0211151127100.22350-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 15 Nov 2002, Steve Silverman wrote:
    > Thank you, you are correct.  These are necessary functions (which
    > already exist) without which, the new technology can not be adopted.

Okay, next step of the exercise: form whom are they necessary?

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 14:55:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17061
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 14:55:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFJvqM11250
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 14:57:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJvqv11247
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 14:57:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17007
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 14:55:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJv9v11127;
	Fri, 15 Nov 2002 14:57:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJciv10539
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 14:38:44 -0500
Received: from imo-d06.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16494
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 14:36:03 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d06.mx.aol.com (mail_out_v34.13.) id j.11f.19d8d666 (16484);
	Fri, 15 Nov 2002 14:38:22 -0500 (EST)
Message-ID: <11f.19d8d666.2b06a72e@aol.com>
Date: Fri, 15 Nov 2002 14:38:22 EST
To: rja@extremenetworks.com
CC: woody@pch.net, choid@ncr.disa.mil, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_11f.19d8d666.2b06a72e_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Subject: [Ieprep] Is QoS Dead?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_11f.19d8d666.2b06a72e_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/14/2002 7:30:18 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> On Wednesday, Nov 13, 2002, at 16:33 America/Montreal, Mpierce1@aol.com 
> wrote:
> > And there have been clear comments from others who do not believe that 
> > "QoS is well behind us".
> 
> Which person who is actively engineering or operating a commercial ISP
> has said anything like that on this list ?  I must not have received that 
> email.
> 
> There have been no comments from folks with no experience or involvement 
> with
> operating a commercial ISP (or the DoD production IP networks, for that 
> matter)
> suggesting that QoS is not well behind us.  And a number of us didn't go
> there even when it was the fad.
> 
> 

[MAP] Not on this list, since it isn't the scope of this WG (which is why I 
am somewhat embarrased to be posting this, but it seems to be at the heart of 
some of our issues.)

Am I understanding you to say that all attempts to improve the QoS of IP is 
dead? I'm confused, as I'm sure others are, then, why the following are on 
the agenda for the upcoming IETF:

NSIS (charter says "will develop requirements, architecture, protocols for 
... signaling QOS, ... evaluating RSVP as a starting point") is meeting for 
3.5 hours.
MPLS (isn't that one of the claimed ways to improve QoS) is meeting for 2.5 
hours

Are you saying that these WGs should be disbanded?

Mike Pierce
Artel



--part1_11f.19d8d666.2b06a72e_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/14/2002 7:30:18 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">On Wednesday, Nov 13, 2002, at 16:33 America/Montreal, Mpierce1@aol.com 
<BR>wrote:
<BR>&gt; And there have been clear comments from others who do not believe that 
<BR>&gt; "QoS is well behind us".
<BR>
<BR>Which person who is actively engineering or operating a commercial ISP
<BR>has said anything like that on this list ? &nbsp;I must not have received that email.
<BR>
<BR>There have been no comments from folks with no experience or involvement with
<BR>operating a commercial ISP (or the DoD production IP networks, for that matter)
<BR>suggesting that QoS is not well behind us. &nbsp;And a number of us didn't go
<BR>there even when it was the fad.
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>[MAP] Not on this list, since it isn't the scope of this WG (which is why I am somewhat embarrased to be posting this, but it seems to be at the heart of some of our issues.)
<BR>
<BR>Am I understanding you to say that all attempts to improve the QoS of IP is dead? I'm confused, as I'm sure others are, then, why the following are on the agenda for the upcoming IETF:
<BR>
<BR>NSIS (charter says "will develop requirements, architecture, protocols for ... signaling QOS, ... evaluating RSVP as a starting point") is meeting for 3.5 hours.
<BR>MPLS (isn't that one of the claimed ways to improve QoS) is meeting for 2.5 hours
<BR>
<BR>Are you saying that these WGs should be disbanded?
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR></FONT></HTML>

--part1_11f.19d8d666.2b06a72e_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 14:55:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17074
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 14:55:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFJvtj11267
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 14:57:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJvtv11264
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 14:57:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17013
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 14:55:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJvBv11163;
	Fri, 15 Nov 2002 14:57:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJeVv10613
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 14:40:31 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16516
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 14:37:48 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <QXJ5F8Q3>; Fri, 15 Nov 2002 14:38:08 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A41496E@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Bill Woodcock'" <woody@pch.net>, Rex Buddenberg <budden@nps.navy.mil>
Cc: RJ Atkinson <rja@extremenetworks.com>,
        Steve Silverman
	 <steves@shentel.net>, "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] representation & IETF culture
Date: Fri, 15 Nov 2002 14:37:55 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

And similar "stupid requirements" NEVER happen in the commercial world?

In my experience there is as much narrow focused "missing the point" in the
commercial world as in the government sector.

-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Friday, November 15, 2002 2:20 PM
To: Rex Buddenberg
Cc: RJ Atkinson; Steve Silverman; 'ieprep '
Subject: Re: [Ieprep] representation & IETF culture


      On 15 Nov 2002, Rex Buddenberg wrote:
    > > "Requirement" means something compulsory, requisite, necessary,
compelled.
    > > Not someone else's passing whim.
    > Not in the government, Bill.

No, in the English lanugage, which is our one hope for bridging this gap.
If we don't share a common language, I'm hard-pressed to imagine a way of
discovering commonalities of understanding and belief.

A little REQUISITE reading for anyone who doesn't believe this is a
really serious problem:
http://dogbert.abebooks.com/servlet/BookDetailsPL?bi=74999286

...and then Rex went on to say about three more pages about the process
of scientific inquiry which I agreed with.


                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 14:55:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17083
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 14:55:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFJvuL11297
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 14:57:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJvtv11294
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 14:57:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17017
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 14:55:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJvAv11143;
	Fri, 15 Nov 2002 14:57:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJd3v10554
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 14:39:03 -0500
Received: from imo-m09.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16499
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 14:36:21 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m09.mx.aol.com (mail_out_v34.13.) id b.1e.250931d (16484);
	Fri, 15 Nov 2002 14:36:41 -0500 (EST)
Message-ID: <1e.250931d.2b06a6c9@aol.com>
Date: Fri, 15 Nov 2002 14:36:41 EST
Subject: Re: [Ieprep] Qualitative statement about quality
To: woody@pch.net
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_1e.250931d.2b06a6c9_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_1e.250931d.2b06a6c9_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/14/2002 2:01:08 PM Eastern Standard Time, woody@pch.net 
writes:


>       On Thu, 14 Nov 2002 Mpierce1@aol.com wrote:
>     > We really need a clarification of this claim. What do you mean be 
> "latency"?
>     > Do you mean one-way or round-trip delay of the voice? Or something 
> else.
> 
> 



[MAP] Yes, I presumed that you were referring to round-trip speech path 
delay, but I had to check, since I can't imagine how anyone could claim that 
a voice conenction with 600 ms was "better" than the PSTN. I am quite certain 
that no where on the face of the earth does the PSTN have a round-trip speech 
path delay anywhere approaching 600 ms. (You can only get that with a 
satellite hop, which few use anymore.) As Henning correctly said, 'G.114 says 
150 ms one way delay as upper limit for "regular" service'. Further, I.380 
(Y.1530) defines a parameter for packet delay as one-way and Y.1541 gives 
100ms is the objective for "Class 0" and 400ms for "Class 1". Class 0 is for 
delay sensitive applications such as "high interactive speech and video 
teleconferencing", while Class 1 is for less interactive speech and VTC. As 
Henning pointed out, the application you were referring to sounded like an 
esentially one-way presentation, in which delay is less important.

In a message dated 11/15/2002 4:07:43 AM Eastern Standard Time, woody@pch.net 
writes:


>  The quality of the VoIP calls is much, much higher than that
> of PSTN calls, and it's difficult to keep the PSTN calls up...  Initial
> call-completion rate is only about 80%, and most calls are dropped within
> twenty minutes.  We've never had a failed connection or a dropped call
> between this pair of VoIP phones, by contrast.
> 


[MAP] Now I'm seeing it. You're comparing with the normal quality (Connection 
Setup Error Probability and Connestion Premature Disconnect, which are 
important) for calls to Nairobi. Yes, I'm sure there are local factors in 
Nairobi that cause higher failure rates than what is generally expected in 
other places. But please don't extrapolation that result to apply to the 
whole "PSTN".

And An - the delay for G.711 is practically non-existent. It samples the 
voice every 0.125 ms, turns it into 8 bits, and sends it on its way. The 
decode does the reverse in .125 ms. Any delay (in the PSTN) is due to time 
slot assignment in TDM multiplex systems and time switching in nodes. These 
are on the order of 10 ms per switch. Then there is the speed of light, which 
we can't change (yet). If you are talking of other delays, you are probably 
referring to a packetization delay, that is, time to gather up enough .125 ms 
samples to make a reasonably size packet (so that the IP overhead doesn't 
kill you). So typically this takes 20 ms for 160 samples (160 octets). This 
packatization (and delay), of course, does not occur in circuit switched.

How about the other part of the claim - that the IP connection had about 6% 
loss? I presume you mean packet loss ratio. My information tells me that many 
codecs fall apart at that loss rate, or at least the degradation in audio 
quality is very noticable. The criteria (which is normally met) for a digital 
connection through the PSTN is for a bit error rate much less than that, so 
again, I can not possibly imagine how one could claim that the Voice over IP 
connection you cited was better than the PSTN. Y.1541 suggests that the 
objective should be 0.1%.

You referred to the comparison being to a call from San Luis Obispo to 
Berkeley. I imagine that the one end is on the Berkely campus, i.e., probably 
not the "public" PSTN all the way. Maybe a lot of old, bad wiring or analog 
switches on campus with lots of interference. Yes, when you deal with some 
real long, old loops, the voice quality can be worse, but this is not a fair 
comparision. (I, like many others, have only several hundred feet of analog 
loop to the digital concentrator.)

I (and the world) would certainly be interested in any fair comparison that 
shows that a voice over IP call achieves better quality than the PSTN (taking 
into account all of the parameters defined in ITU-T Y.1530 and Y.1540).

Mike Pierce
Artel


--part1_1e.250931d.2b06a6c9_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/14/2002 2:01:08 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;On Thu, 14 Nov 2002 Mpierce1@aol.com wrote:
<BR> &nbsp;&nbsp;&nbsp;&gt; We really need a clarification of this claim. What do you mean be "latency"?
<BR> &nbsp;&nbsp;&nbsp;&gt; Do you mean one-way or round-trip delay of the voice? Or something else.
<BR>
<BR>Round-trip, same as anyone else means when they say latency.</BLOCKQUOTE>
<BR>
<BR>
<BR>
<BR>[MAP] Yes, I presumed that you were referring to round-trip speech path delay, but I had to check, since I can't imagine how anyone could claim that a voice conenction with 600 ms was "better" than the PSTN. I am quite certain that no where on the face of the earth does the PSTN have a round-trip speech path delay anywhere approaching 600 ms. (You can only get that with a satellite hop, which few use anymore.) As Henning correctly said, 'G.114 says 150 ms one way delay as upper limit for "regular" service'. Further, I.380 (Y.1530) defines a parameter for packet delay as one-way and Y.1541 gives 100ms is the objective for "Class 0" and 400ms for "Class 1". Class 0 is for delay sensitive applications such as "high interactive speech and video teleconferencing", while Class 1 is for less interactive speech and VTC. As Henning pointed out, the application you were referring to sounded like an esentially one-way presentation, in which delay is less important.
<BR>
<BR>In a message dated 11/15/2002 4:07:43 AM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> The quality of the VoIP calls is much, much higher than that
<BR>of PSTN calls, and it's difficult to keep the PSTN calls up... &nbsp;Initial
<BR>call-completion rate is only about 80%, and most calls are dropped within
<BR>twenty minutes. &nbsp;We've never had a failed connection or a dropped call
<BR>between this pair of VoIP phones, by contrast.
<BR></BLOCKQUOTE>
<BR>
<BR>
<BR>[MAP] Now I'm seeing it. You're comparing with the normal quality (Connection Setup Error Probability and Connestion Premature Disconnect, which are important) for calls to Nairobi. Yes, I'm sure there are local factors in Nairobi that cause higher failure rates than what is generally expected in other places. But please don't extrapolation that result to apply to the whole "PSTN".
<BR>
<BR>And An - the delay for G.711 is practically non-existent. It samples the voice every 0.125 ms, turns it into 8 bits, and sends it on its way. The decode does the reverse in .125 ms. Any delay (in the PSTN) is due to time slot assignment in TDM multiplex systems and time switching in nodes. These are on the order of 10 ms per switch. Then there is the speed of light, which we can't change (yet). If you are talking of other delays, you are probably referring to a packetization delay, that is, time to gather up enough .125 ms samples to make a reasonably size packet (so that the IP overhead doesn't kill you). So typically this takes 20 ms for 160 samples (160 octets). This packatization (and delay), of course, does not occur in circuit switched.
<BR>
<BR>How about the other part of the claim - that the IP connection had about 6% loss? I presume you mean packet loss ratio. My information tells me that many codecs fall apart at that loss rate, or at least the degradation in audio quality is very noticable. The criteria (which is normally met) for a digital connection through the PSTN is for a bit error rate much less than that, so again, I can not possibly imagine how one could claim that the Voice over IP connection you cited was better than the PSTN. Y.1541 suggests that the objective should be 0.1%.
<BR>
<BR>You referred to the comparison being to a call from San Luis Obispo to Berkeley. I imagine that the one end is on the Berkely campus, i.e., probably not the "public" PSTN all the way. Maybe a lot of old, bad wiring or analog switches on campus with lots of interference. Yes, when you deal with some real long, old loops, the voice quality can be worse, but this is not a fair comparision. (I, like many others, have only several hundred feet of analog loop to the digital concentrator.)
<BR>
<BR>I (and the world) would certainly be interested in any fair comparison that shows that a voice over IP call achieves better quality than the PSTN (taking into account all of the parameters defined in ITU-T Y.1530 and Y.1540).
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_1e.250931d.2b06a6c9_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 14:55:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17113
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 14:55:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFJw8511369
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 14:58:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJw8v11366
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 14:58:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17039
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 14:55:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJv8v11095;
	Fri, 15 Nov 2002 14:57:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJbxv10506
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 14:37:59 -0500
Received: from imo-d07.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16485
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 14:35:18 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d07.mx.aol.com (mail_out_v34.13.) id j.95.25aeb5eb (16484);
	Fri, 15 Nov 2002 14:37:46 -0500 (EST)
Message-ID: <95.25aeb5eb.2b06a709@aol.com>
Date: Fri, 15 Nov 2002 14:37:45 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_95.25aeb5eb.2b06a709_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_95.25aeb5eb.2b06a709_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

I wrote:

> If things being discussed/proposed have very significant implications 
> in the operational IP network world, I would certainly like to hear 
> about them.

In a message dated 11/14/2002 7:16:43 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> Gee whiz.  That's most of what Bill, Sean, Barry, and I have been 
> talking about.
> 


Sorry, there's been a lot of hand waving, name calling, sarcastic comments, 
and claims that "something" will break the Internet. But because of all the 
noise, we haven't yet been able to discuss specific mechanisms that might 
work or might "break" the Internet. Besides, we aren't supposed to be 
discussing mechanisms in this WG.

Please, can we discuss the requirements without anyone jumping to a 
conclusion about what mechanisms must be used or to claims that they can't 
ever work? And if someone really wants to discuss a proposed (or suggested) 
mechanism prematuraly (which we all tend to do), could you please provide 
some concrete technical statements concerning why it will not work. Not just 
statements that your network doesn't need it and therefore no one else does.

I would really like to have some technical meat to chew on, not all the fat 
that's flying around. If you have a comment, could you please address a 
specific proposal that I have made in one of the drafts I have submitted and 
make explicit statements of what is wrong with it. And leave out the sarcasm 
and we might be able to communicate effectively.

Mike Pierce
Artel


--part1_95.25aeb5eb.2b06a709_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>I wrote:
<BR>
<BR>&gt; If things being discussed/proposed have very significant implications 
<BR>&gt; in the operational IP network world, I would certainly like to hear 
<BR>&gt; about them.
<BR>
<BR>In a message dated 11/14/2002 7:16:43 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Gee whiz. &nbsp;That's most of what Bill, Sean, Barry, and I have been 
<BR>talking about.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>Sorry, there's been a lot of hand waving, name calling, sarcastic comments, and claims that "something" will break the Internet. But because of all the noise, we haven't yet been able to discuss specific mechanisms that might work or might "break" the Internet. Besides, we aren't supposed to be discussing mechanisms in this WG.
<BR>
<BR>Please, can we discuss the requirements without anyone jumping to a conclusion about what mechanisms must be used or to claims that they can't ever work? And if someone really wants to discuss a proposed (or suggested) mechanism prematuraly (which we all tend to do), could you please provide some concrete technical statements concerning why it will not work. Not just statements that your network doesn't need it and therefore no one else does.
<BR>
<BR>I would really like to have some technical meat to chew on, not all the fat that's flying around. If you have a comment, could you please address a specific proposal that I have made in one of the drafts I have submitted and make explicit statements of what is wrong with it. And leave out the sarcasm and we might be able to communicate effectively.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_95.25aeb5eb.2b06a709_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 14:56:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17126
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 14:56:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFJwDh11384
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 14:58:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJwDv11381
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 14:58:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17043
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 14:55:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJvIv11224;
	Fri, 15 Nov 2002 14:57:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFJsLv10948
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 14:54:21 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16895
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 14:51:39 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAFJmBd26880;
	Fri, 15 Nov 2002 11:48:12 -0800 (PST)
Date: Fri, 15 Nov 2002 11:48:11 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Steve Silverman <steves@shentel.net>
cc: RJ Atkinson <rja@extremenetworks.com>, "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] representation & IETF culture
In-Reply-To: <Pine.GSO.4.44.0211151127100.22350-100000@paixhost.pch.net>
Message-ID: <Pine.GSO.4.44.0211151146450.22350-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    >     > Thank you, you are correct.  These are necessary functions (which
    >     > already exist) without which, the new technology can not be adopted.
    >
    > Okay, next step of the exercise: form whom are they necessary?

Oh, and while we're at it, let's replace the phrase "These functions" with
some specific noun.  "QoS control?"  "Service level agreements?"
"Specialness?"

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 15:13:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17620
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 15:13:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFKFjW12960
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 15:15:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKFjv12957
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 15:15:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17603
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 15:13:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKF4v12882;
	Fri, 15 Nov 2002 15:15:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFK7Sv12523
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 15:07:28 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17453
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 15:04:46 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAFK1Hd27054;
	Fri, 15 Nov 2002 12:01:17 -0800 (PST)
Date: Fri, 15 Nov 2002 12:01:17 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: rja@extremenetworks.com, <choid@ncr.disa.mil>, <ieprep@ietf.org>
In-Reply-To: <11f.19d8d666.2b06a72e@aol.com>
Message-ID: <Pine.GSO.4.44.0211151148400.22350-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] Re: Is QoS Dead?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 15 Nov 2002 Mpierce1@aol.com wrote:
    > Am I understanding you to say that all attempts to improve the QoS of IP is
    > dead?  I'm confused.

You're confused because you're having trouble with language again.
Specifically, you're making the same mistake that we've corrected twice
before: you're conflating the word "quality" with the acronym "QoS".  The
former is generally thought to mean a property of goodness, while the
latter is an abbreviation of "Quality of Service," which is a proper noun
denoting a collection of protocols and practices which have the intention
of making some pigs more equal than others.

So, to clarify again:  In the Internet, we improved the quality of
service by abolishing QoS.

See?  A tip: you can distinguish proper nouns because they're denoted by
the use of _initial capitals_.  Boeing, Big Mac with Cheese, QoS, Mike;
these are all proper nouns, tokens which designate a thing, rather than
being parts of the language which carry intrinsic meaning.

Before you get carried away, though, remember that decapitalizing
something isn't a useful trick, since it _changes the meaning of the thing
drastically_, as in the case before us now.  The confusion which this
engenders in proles is why, for instance, the word acme has been so
frequently used in the names (which are proper nouns) of businesses.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 15:16:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17788
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 15:16:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFKIYO13291
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 15:18:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKIYv13288
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 15:18:34 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17737
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 15:15:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKHYv13061;
	Fri, 15 Nov 2002 15:17:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKDHv12657
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 15:13:17 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17514
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 15:10:35 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAFK7Bd27112;
	Fri, 15 Nov 2002 12:07:11 -0800 (PST)
Date: Fri, 15 Nov 2002 12:07:11 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: ieprep@ietf.org
Subject: Re: [Ieprep] Qualitative statement about quality
In-Reply-To: <1e.250931d.2b06a6c9@aol.com>
Message-ID: <Pine.GSO.4.44.0211151201540.22350-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 15 Nov 2002 Mpierce1@aol.com wrote:
    > I am quite certain that no where on the face of the earth does the
    > PSTN have a round-trip speech path delay anywhere approaching 600
    > ms.

Dang, you mean that all that faster light that ISPs have been clamoring
for has all been hoarded by the PSTN?  I knew this wasn't a level playing
field!

    > (You can only get that with a satellite hop, which few use anymore.)

Let me give you another hint, Mike, before Rex and some of your colleages
rip your head off: your use of the word "few" is perhaps, um, injudicious.

The prevalence of Satcom tail-circuits is one of the pillars of your
argument justifying your need to be special, remember?  You don't want to
downplay it.

    > The application you were referring to sounded like an
    > esentially one-way presentation, in which delay is less important.

I believe it was characterized by all parties concerned as a
"conversation."  It was fully interactive, as most telephone conversations
are.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 15:16:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17821
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 15:16:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFKIuU13339
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 15:18:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKIuv13336
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 15:18:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17776
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 15:16:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKI2v13196;
	Fri, 15 Nov 2002 15:18:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKFgv12950
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 15:15:42 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17598
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 15:13:00 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAFK9Hd27150;
	Fri, 15 Nov 2002 12:09:17 -0800 (PST)
Date: Fri, 15 Nov 2002 12:09:17 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
cc: Rex Buddenberg <budden@nps.navy.mil>,
        RJ Atkinson <rja@extremenetworks.com>,
        Steve Silverman <steves@shentel.net>, "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] representation & IETF culture
In-Reply-To: <CBED705A7FD2D311865500508B1089410A41496E@chntex02.is.dyncorp.com>
Message-ID: <Pine.GSO.4.44.0211151208010.22350-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 15 Nov 2002, Gunn, Janet wrote:
    > And similar "stupid requirements" NEVER happen in the commercial world?

The "two wrongs make a right" argument is orthoganal to the question of
whether we should let the very, very valuable time of the IETF be used as
a rubber-stamping mechanism for one customer's procurement process with
vendors they're already working with.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 15:24:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18176
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 15:24:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFKQnX13867
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 15:26:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKQnv13864
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 15:26:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18141
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 15:24:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKQ5v13792;
	Fri, 15 Nov 2002 15:26:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKMav13529
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 15:22:36 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA18021
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 15:19:54 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 15 Nov 2002 20:19:56 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <W8NWN41C>; Fri, 15 Nov 2002 15:23:45 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D44@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Mpierce1@aol.com'" <Mpierce1@aol.com>
Cc: ieprep@ietf.org, woody@pch.net
Subject: RE: [Ieprep] Qualitative statement about quality
Date: Fri, 15 Nov 2002 15:22:22 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C28CE4.B4644EE0"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C28CE4.B4644EE0
Content-Type: text/plain;
	charset="iso-8859-1"

        Mike,
 
        I meant G.711 being transported in IP networks. 
 
        An

-----Original Message-----
From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
Sent: Friday, November 15, 2002 2:37 PM
To: woody@pch.net
Cc: ieprep@ietf.org
Subject: Re: [Ieprep] Qualitative statement about quality


In a message dated 11/14/2002 2:01:08 PM Eastern Standard Time,
woody@pch.net writes: 




     On Thu, 14 Nov 2002 Mpierce1@aol.com wrote: 
   > We really need a clarification of this claim. What do you mean be
"latency"? 
   > Do you mean one-way or round-trip delay of the voice? Or something
else. 

Round-trip, same as anyone else means when they say latency.





[MAP] Yes, I presumed that you were referring to round-trip speech path
delay, but I had to check, since I can't imagine how anyone could claim that
a voice conenction with 600 ms was "better" than the PSTN. I am quite
certain that no where on the face of the earth does the PSTN have a
round-trip speech path delay anywhere approaching 600 ms. (You can only get
that with a satellite hop, which few use anymore.) As Henning correctly
said, 'G.114 says 150 ms one way delay as upper limit for "regular"
service'. Further, I.380 (Y.1530) defines a parameter for packet delay as
one-way and Y.1541 gives 100ms is the objective for "Class 0" and 400ms for
"Class 1". Class 0 is for delay sensitive applications such as "high
interactive speech and video teleconferencing", while Class 1 is for less
interactive speech and VTC. As Henning pointed out, the application you were
referring to sounded like an esentially one-way presentation, in which delay
is less important. 

In a message dated 11/15/2002 4:07:43 AM Eastern Standard Time,
woody@pch.net writes: 




The quality of the VoIP calls is much, much higher than that 
of PSTN calls, and it's difficult to keep the PSTN calls up...  Initial 
call-completion rate is only about 80%, and most calls are dropped within 
twenty minutes.  We've never had a failed connection or a dropped call 
between this pair of VoIP phones, by contrast. 





[MAP] Now I'm seeing it. You're comparing with the normal quality
(Connection Setup Error Probability and Connestion Premature Disconnect,
which are important) for calls to Nairobi. Yes, I'm sure there are local
factors in Nairobi that cause higher failure rates than what is generally
expected in other places. But please don't extrapolation that result to
apply to the whole "PSTN". 

And An - the delay for G.711 is practically non-existent. It samples the
voice every 0.125 ms, turns it into 8 bits, and sends it on its way. The
decode does the reverse in .125 ms. Any delay (in the PSTN) is due to time
slot assignment in TDM multiplex systems and time switching in nodes. These
are on the order of 10 ms per switch. Then there is the speed of light,
which we can't change (yet). If you are talking of other delays, you are
probably referring to a packetization delay, that is, time to gather up
enough .125 ms samples to make a reasonably size packet (so that the IP
overhead doesn't kill you). So typically this takes 20 ms for 160 samples
(160 octets). This packatization (and delay), of course, does not occur in
circuit switched. 

How about the other part of the claim - that the IP connection had about 6%
loss? I presume you mean packet loss ratio. My information tells me that
many codecs fall apart at that loss rate, or at least the degradation in
audio quality is very noticable. The criteria (which is normally met) for a
digital connection through the PSTN is for a bit error rate much less than
that, so again, I can not possibly imagine how one could claim that the
Voice over IP connection you cited was better than the PSTN. Y.1541 suggests
that the objective should be 0.1%. 

You referred to the comparison being to a call from San Luis Obispo to
Berkeley. I imagine that the one end is on the Berkely campus, i.e.,
probably not the "public" PSTN all the way. Maybe a lot of old, bad wiring
or analog switches on campus with lots of interference. Yes, when you deal
with some real long, old loops, the voice quality can be worse, but this is
not a fair comparision. (I, like many others, have only several hundred feet
of analog loop to the digital concentrator.) 

I (and the world) would certainly be interested in any fair comparison that
shows that a voice over IP call achieves better quality than the PSTN
(taking into account all of the parameters defined in ITU-T Y.1530 and
Y.1540). 

Mike Pierce 
Artel 



------_=_NextPart_001_01C28CE4.B4644EE0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=906091116-16072001><FONT face=Arial color=#0000ff 
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike,</FONT></SPAN></DIV>
<DIV><SPAN class=906091116-16072001><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=906091116-16072001><FONT face=Arial color=#0000ff 
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I meant G.711 being 
transported in IP networks.&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=906091116-16072001><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=906091116-16072001><FONT face=Arial color=#0000ff 
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; An</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Mpierce1@aol.com 
  [mailto:Mpierce1@aol.com]<BR><B>Sent:</B> Friday, November 15, 2002 2:37 
  PM<BR><B>To:</B> woody@pch.net<BR><B>Cc:</B> 
  ieprep@ietf.org<BR><B>Subject:</B> Re: [Ieprep] Qualitative statement about 
  quality<BR><BR></FONT></DIV><FONT face=arial,helvetica><FONT size=2>In a 
  message dated 11/14/2002 2:01:08 PM Eastern Standard Time, woody@pch.net 
  writes: <BR><BR><BR>
  <BLOCKQUOTE 
  style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px" 
  TYPE="CITE">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;On Thu, 14 Nov 2002 
    Mpierce1@aol.com wrote: <BR>&nbsp;&nbsp;&nbsp;&gt; We really need a 
    clarification of this claim. What do you mean be "latency"? 
    <BR>&nbsp;&nbsp;&nbsp;&gt; Do you mean one-way or round-trip delay of the 
    voice? Or something else. <BR><BR>Round-trip, same as anyone else means when 
    they say latency.</BLOCKQUOTE><BR><BR><BR><BR>[MAP] Yes, I presumed that you 
  were referring to round-trip speech path delay, but I had to check, since I 
  can't imagine how anyone could claim that a voice conenction with 600 ms was 
  "better" than the PSTN. I am quite certain that no where on the face of the 
  earth does the PSTN have a round-trip speech path delay anywhere approaching 
  600 ms. (You can only get that with a satellite hop, which few use anymore.) 
  As Henning correctly said, 'G.114 says 150 ms one way delay as upper limit for 
  "regular" service'. Further, I.380 (Y.1530) defines a parameter for packet 
  delay as one-way and Y.1541 gives 100ms is the objective for "Class 0" and 
  400ms for "Class 1". Class 0 is for delay sensitive applications such as "high 
  interactive speech and video teleconferencing", while Class 1 is for less 
  interactive speech and VTC. As Henning pointed out, the application you were 
  referring to sounded like an esentially one-way presentation, in which delay 
  is less important. <BR><BR>In a message dated 11/15/2002 4:07:43 AM Eastern 
  Standard Time, woody@pch.net writes: <BR><BR><BR>
  <BLOCKQUOTE 
  style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px" 
  TYPE="CITE">The quality of the VoIP calls is much, much higher than that 
    <BR>of PSTN calls, and it's difficult to keep the PSTN calls up... 
    &nbsp;Initial <BR>call-completion rate is only about 80%, and most calls are 
    dropped within <BR>twenty minutes. &nbsp;We've never had a failed connection 
    or a dropped call <BR>between this pair of VoIP phones, by contrast. 
  <BR></BLOCKQUOTE><BR><BR><BR>[MAP] Now I'm seeing it. You're comparing with 
  the normal quality (Connection Setup Error Probability and Connestion 
  Premature Disconnect, which are important) for calls to Nairobi. Yes, I'm sure 
  there are local factors in Nairobi that cause higher failure rates than what 
  is generally expected in other places. But please don't extrapolation that 
  result to apply to the whole "PSTN". <BR><BR>And An - the delay for G.711 is 
  practically non-existent. It samples the voice every 0.125 ms, turns it into 8 
  bits, and sends it on its way. The decode does the reverse in .125 ms. Any 
  delay (in the PSTN) is due to time slot assignment in TDM multiplex systems 
  and time switching in nodes. These are on the order of 10 ms per switch. Then 
  there is the speed of light, which we can't change (yet). If you are talking 
  of other delays, you are probably referring to a packetization delay, that is, 
  time to gather up enough .125 ms samples to make a reasonably size packet (so 
  that the IP overhead doesn't kill you). So typically this takes 20 ms for 160 
  samples (160 octets). This packatization (and delay), of course, does not 
  occur in circuit switched. <BR><BR>How about the other part of the claim - 
  that the IP connection had about 6% loss? I presume you mean packet loss 
  ratio. My information tells me that many codecs fall apart at that loss rate, 
  or at least the degradation in audio quality is very noticable. The criteria 
  (which is normally met) for a digital connection through the PSTN is for a bit 
  error rate much less than that, so again, I can not possibly imagine how one 
  could claim that the Voice over IP connection you cited was better than the 
  PSTN. Y.1541 suggests that the objective should be 0.1%. <BR><BR>You referred 
  to the comparison being to a call from San Luis Obispo to Berkeley. I imagine 
  that the one end is on the Berkely campus, i.e., probably not the "public" 
  PSTN all the way. Maybe a lot of old, bad wiring or analog switches on campus 
  with lots of interference. Yes, when you deal with some real long, old loops, 
  the voice quality can be worse, but this is not a fair comparision. (I, like 
  many others, have only several hundred feet of analog loop to the digital 
  concentrator.) <BR><BR>I (and the world) would certainly be interested in any 
  fair comparison that shows that a voice over IP call achieves better quality 
  than the PSTN (taking into account all of the parameters defined in ITU-T 
  Y.1530 and Y.1540). <BR><BR>Mike Pierce <BR>Artel 
<BR></BLOCKQUOTE></FONT></FONT></BODY></HTML>

------_=_NextPart_001_01C28CE4.B4644EE0--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 16:36:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20178
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 16:36:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFLcvb18804
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 16:38:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFLcvv18801
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 16:38:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20160
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 16:36:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFLc3v18764;
	Fri, 15 Nov 2002 16:38:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFLNXv17238
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 16:23:33 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19530
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 16:20:52 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <QXJ5F887>; Fri, 15 Nov 2002 16:21:14 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A41496F@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Bill Woodcock'" <woody@pch.net>
Cc: Rex Buddenberg <budden@nps.navy.mil>,
        RJ Atkinson
	 <rja@extremenetworks.com>,
        Steve Silverman <steves@shentel.net>, "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] representation & IETF culture
Date: Fri, 15 Nov 2002 16:20:58 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

And you think that crass generalizations and name calling are a USEFUL ways
of spending that "very, very valuable time"?

I enjoy the technical discussion, and I like to think I am learning
something from all the different perspectives.

But the name calling is getting VERY old.  Makes it hard to appreciate the
useful information that is SOMETIMES included in the same posts.

-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Friday, November 15, 2002 3:09 PM
To: Gunn, Janet
Cc: Rex Buddenberg; RJ Atkinson; Steve Silverman; 'ieprep '
Subject: RE: [Ieprep] representation & IETF culture


      On Fri, 15 Nov 2002, Gunn, Janet wrote:
    > And similar "stupid requirements" NEVER happen in the commercial
world?

The "two wrongs make a right" argument is orthoganal to the question of
whether we should let the very, very valuable time of the IETF be used as
a rubber-stamping mechanism for one customer's procurement process with
vendors they're already working with.

                                -Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 17:31:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21972
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 17:31:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFMXhn22529
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 17:33:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFMXhv22526
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 17:33:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21941
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 17:31:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFMX4v22418;
	Fri, 15 Nov 2002 17:33:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFMPGv22093
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 17:25:16 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21774
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 17:22:35 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18Coti-0001DO-00
	for ieprep@ietf.org; Fri, 15 Nov 2002 17:25:10 -0500
Date: Fri, 15 Nov 2002 17:25:10 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: ieprep@ietf.org
In-Reply-To: <CBED705A7FD2D311865500508B1089410A41496F@chntex02.is.dyncorp.com>
Message-ID: <Pine.GSO.4.44.0211151717260.4642-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] ERLINK
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


So what were the program results for ERLink (Emergency Response Link) the
NCS set up using the Internet (i.e. a "secure" web site) in the 1990's?

Where there problems?  Did it work?  Did emergency/first responders find
it useful? Was there a problem in the Internet which affected its
performance? Or was it cancelled because it didn't solve a useful problem?

If there were specific problems identified, perhaps we could fix them.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 20:46:24 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26426
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 20:46:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG1mbw32472
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 20:48:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG1mbv32469
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 20:48:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26404
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 20:45:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG1lcv32453;
	Fri, 15 Nov 2002 20:47:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG1kAv32419
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 20:46:10 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26363
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 20:43:25 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 5DB5567103; Fri, 15 Nov 2002 17:08:28 -0500 (EST)
Date: Fri, 15 Nov 2002 20:46:01 -0500
Subject: Re: [Ieprep] terminology
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep '" <ieprep@ietf.org>
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211151115550.22350-100000@paixhost.pch.net>
Message-Id: <28E2365E-F905-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 15, 2002, at 14:20 America/Montreal, Bill Woodcock wrote:
>      On 15 Nov 2002, Rex Buddenberg wrote:
>>> "Requirement" means something compulsory, requisite, necessary, 
>>> compelled.
>>> Not someone else's passing whim.
>> Not in the government, Bill.
>
> No, in the English lanugage, which is our one hope for bridging this 
> gap.
> If we don't share a common language, I'm hard-pressed to imagine a way 
> of
> discovering commonalities of understanding and belief.

We don't currently share a common language.  I can speak both languages,
as an artifact of a previous job for Navy, but the 2 communities here 
have
very different meanings associated with "requirement".

I tried to explain this earlier on.  Here's an attempt at a replay:

In IETF, "requirement" means something that an implementer MUST 
implement
and/or something that an operator MUST deploy.

In USG, "requirement" means something that the USG needs, seeks,
or desires.  In the government, it is often the case that someone comes
to the table with a "requirement", but is satisfied with something
entirely different or goes away with the "requirement" unmet.

In this WG, I'd suggest we all try hard to use the IETF definition, 
because
this is an IETF WG.  I understand that a large number of the documents
being discussed here will be edited to use IETF definitions (probably
won't appear online until after Atlanta due to I-D cutoff and lack of
time to do the editing just now).

Rex's story is very very good and is worth re-reading.  Part of what 
some
of us are trying to do is figure out if the priortisation is really
"full motion video" of Rex's story.  I'm currently strongly inclined to
think that it is and that we need to sort out what the equivalent of
the "selected still photos" of Rex's story might be in this context.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 20:55:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26576
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 20:55:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG1vdP32679
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 20:57:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG1vdv32676
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 20:57:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26573
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 20:54:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG1v2v32646;
	Fri, 15 Nov 2002 20:57:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG1uAv32610
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 20:56:10 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26518
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 20:53:25 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 36EB067103; Fri, 15 Nov 2002 17:18:28 -0500 (EST)
Date: Fri, 15 Nov 2002 20:56:00 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <95.25aeb5eb.2b06a709@aol.com>
Message-Id: <8E6DAF5C-F906-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 15, 2002, at 14:37 America/Montreal, Mpierce1@aol.com 
wrote:
> But because of all the noise, we haven't yet been able to discuss 
> specific mechanisms that might work or might "break" the Internet. 
> Besides, we aren't supposed to be discussing mechanisms in this WG.

I'll try to be more concrete.

Several ISPs that deployed "prioritisation" and/or "QoS" found that:
	(1) priority packets got worse treatment than best-effort packets,
	    particularly in times of network stress
	(2) deployment costs were intolerably high (i.e. money needed to deploy
	    was non-trivially high).
	(3) deployment was not feasible in a large-scale commercial backbone
	(4) operations costs (e.g. debugging) were insanely high
	(5) much of the currently deployed equipment did not behave very well
	    when lots of features (especially QoS) were enabled.  To be fair,
	    some equipment is robust when features are turned on.  The latter
          equipment generally has a hardware-based (e.g. ASIC, FPGA) 
implementation
          of the enabled features.

The details of why these things did not work are pretty ugly and require
an annoying amount of understanding of:
	(A) what an ISP network typically looks like
	(B) how IP routers or Ethernet switches work under the hood
	(C) the economics (grim as they are) of operating a commercial ISP
	(D) the day to day life of an operations person at a commercial ISP

For DISA/NCS folks, a starting point on A through D might be to talk 
with the
government folks who engineer and operate the DISN IP networks.  A trip 
to
southern Illinois is strongly recommended.

In an effort to help some with (A) and a tiny amount with (B), I'm 
putting
together a presentation.  With luck, I'll be able to present it at 
IEprep
in Atlanta.  Modulo my calendar, I'll happily wander down to Skyline or
Courthouse Road and give it again (whiteboard is also helpful) if 
desired.
My presentation is the work of a cast of many many ISP folks; I'm 
merely the
editor stuckee.

Cheers,

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:00:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26716
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:00:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG22k400439
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:02:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG22kv00436
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:02:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26705
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:00:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG221v00399;
	Fri, 15 Nov 2002 21:02:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG220v00377
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:02:00 -0500
Received: from seahorse.shentel.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26682
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 20:59:15 -0500 (EST)
Received: from steves (ha96s702.d.shentel.net [204.111.98.190])
	by seahorse.shentel.net (8.11.6/8.11.6) with SMTP id gAG21gM31790;
	Fri, 15 Nov 2002 21:01:42 -0500
From: "Steve Silverman" <steves@shentel.net>
To: "Bill Woodcock" <woody@pch.net>
Cc: "RJ Atkinson" <rja@extremenetworks.com>, "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] representation & IETF culture
Date: Fri, 15 Nov 2002 21:01:50 -0500
Message-ID: <KMEJKAPHBBCMCDDGMBLOGEHDCAAA.steves@shentel.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <Pine.GSO.4.44.0211151146450.22350-100000@paixhost.pch.net>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Bill,
As to the users who require these services, the DOD has had such a
system for 40 years and
they already have a way to determine the recipients of the service.
I don't worry about the details of this.

As the functions, while good voice quality is nice, it isn't
paramount.  They key function is high probability of
call completion in a congested environment.  Even if the offered
traffic load exceeds the network capability, the selected users
calls get through.  Even if the voice quality is less than normal,
if it is reasonably intelligible, it is sufficient.
High probability of completion is accomplished by MLPP in the CS
network.  As I understand it, this is essentially what GETS does in
the public network.

Steve Silverman

> -----Original Message-----
> From: ieprep-admin@ietf.org
> [mailto:ieprep-admin@ietf.org]On Behalf Of
> Bill Woodcock
> Sent: Friday, November 15, 2002 2:48 PM
> To: Steve Silverman
> Cc: RJ Atkinson; 'ieprep '
> Subject: RE: [Ieprep] representation & IETF culture
>
>
>     >     > Thank you, you are correct.  These are
> necessary functions (which
>     >     > already exist) without which, the new
> technology can not be adopted.
>     >
>     > Okay, next step of the exercise: form whom are they
> necessary?
>
> Oh, and while we're at it, let's replace the phrase
> "These functions" with
> some specific noun.  "QoS control?"  "Service level agreements?"
> "Specialness?"
>
>                                 -Bill
>
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>
>


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:06:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26824
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:06:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG28HC01256
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:08:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG28Gv01253
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:08:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26817
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:05:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG272v00686;
	Fri, 15 Nov 2002 21:07:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG26vv00578
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:06:57 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26791
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:04:12 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 7830C67106; Fri, 15 Nov 2002 17:29:14 -0500 (EST)
Date: Fri, 15 Nov 2002 21:06:47 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <11f.19d8d666.2b06a72e@aol.com>
Message-Id: <0FAC8FEA-F908-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Re: Is QoS Dead?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 15, 2002, at 14:38 America/Montreal, Mpierce1@aol.com 
wrote:
> Am I understanding you to say that all attempts to improve the QoS of 
> IP is dead? I'm confused, as I'm sure others are, then, why the 
> following are on the agenda for the upcoming IETF:
>
> NSIS (charter says "will develop requirements, architecture, protocols 
> for ... signaling

NSIS is working on an application-layer problem of telephony signalling 
applications,
not on IP-layer QoS.  ISPs generally only offer IP forwarding as a 
service, not
SIP or other application layer services.  I doubt anything done in NSIS 
will relate
to anything that actually gets deployed at the IP-layer.

>  QOS, ... evaluating RSVP as a starting point") is meeting for 3.5 
> hours.

RSVP was deployed in some limited ways.  It did not scale even to those 
very limited
deployments.  RSVP is pretty much abandoned as a QoS mechanism, based 
on that experience.

> MPLS (isn't that one of the claimed ways to improve QoS) is meeting 
> for 2.5 hours

At the moment, I think you can probably even find folks who claim that 
MPLS
is a "Ginzu Knife".  Most of the MPLS work these days seems to focus on 
its
use for:
	- Traffic Engineering
	- Virtual Private Networks, at layer-2 or layer-3
	- NOT for QoS, though it has an optional-to-implement DiffServ-like 
mechanism,
       that comes with all the issues that DiffServ has

> Are you saying that these WGs should be disbanded?

I'd suggest reading the recent IAB document on this topic:
	ftp://ftp.ietf.org/rfc/rfc2990.txt

I think Bill used a bit of hyperbole (but not a lot of hyperbole) in
calling QoS dead.  Folks wish they could find a way to make it 
deployable.
None such has been found yet and there are no obvious candidates in 
sight
just now.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:14:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26977
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:14:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2Gtq01527
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:16:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2Gtv01524
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:16:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26953
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:14:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2G2v01494;
	Fri, 15 Nov 2002 21:16:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2FLv01475
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:15:21 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26925
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:12:36 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id F388A67103; Fri, 15 Nov 2002 17:37:38 -0500 (EST)
Date: Fri, 15 Nov 2002 21:15:11 -0500
Subject: Re: [Ieprep] representation & IETF culture
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep '" <ieprep@ietf.org>
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <CBED705A7FD2D311865500508B1089410A41496E@chntex02.is.dyncorp.com>
Message-Id: <3C59495A-F909-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 15, 2002, at 14:37 America/Montreal, Gunn, Janet wrote:
> And similar "stupid requirements" NEVER happen in the commercial world?

Commercial customers of ISPs normally open their approach by asking
the ISPs to give them a quote for the specified service, not by asking
the IETF to create an anomalous WG that they can use to herd 
service/equipment
vendors.

Normally, (A) commercial customers tell equipment vendors that they 
will purchase
X million dollars of stuff if the vendor implements foo.  The vendor 
figures out
the cost (including opportunity cost) of implementing foo, compares 
with revenue
and ROI needs, then decides whether to implement foo for the customer.

Normally, (B) commercial customers tell ISPs that they want to purchase 
the
foo service and ask what price it is available at.  The ISP then decides
whether they want to offer foo (or not) and provides a quote (iff they
decide to offer foo).  @Home declined to offer a lot of the services 
that
we were asked to provide, normally because the opportunity cost was too 
high.

In the government sector, it is not unheard of to use (A).  Once upon a 
time,
DIA edited together a spec for a "Compartmented Mode Workstation" and 
told
workstation vendors that they wanted to by <very large quantity> of them
and put out an RFP.  Vendors did the math and some implemented to the 
spec.
A subset of those sold their CMW products to the government.

It is also not unheard of to use (B).  For example, DISA currently has 
an
RFI out on the street for long-haul fibre.  Usually, a government RFI
is followed up by a government RFP.

So, frankly, I'm pretty confused about why DISA/NCS isn't taking the 
commercial
contracting approaches outlined above.  I think it would be a lot more 
successful.
And it would let us shutdown this very strange and very painful WG.

> In my experience there is as much narrow focused "missing the point" 
> in the
> commercial world as in the government sector.

The profit motive turns out to be a highly effective mechanism in 
helping
the commercial sector re-focus itself naturally.  That mechanism is 
necessarily
absent from the government.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:18:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27056
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:18:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2KdY01693
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:20:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2Kcv01690
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:20:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27048
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:17:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2K1v01660;
	Fri, 15 Nov 2002 21:20:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2Jxv01626
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:19:59 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27039
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:17:14 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAG2Drd01358;
	Fri, 15 Nov 2002 18:13:53 -0800 (PST)
Date: Fri, 15 Nov 2002 18:13:53 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Steve Silverman <steves@shentel.net>
cc: RJ Atkinson <rja@extremenetworks.com>, "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] representation & IETF culture
In-Reply-To: <KMEJKAPHBBCMCDDGMBLOGEHDCAAA.steves@shentel.net>
Message-ID: <Pine.GSO.4.44.0211151757170.161-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 15 Nov 2002, Steve Silverman wrote:
    > The DoD has a way to determine the recipients of the service.
    > I don't worry about the details of this.

Mmmm, while I'm sure that's normally beneficial in reducing the number of
things you have to worry about, at the moment you need to be selling us on
the desirability of paying attention to these documents or desires or
whatever...  So if you don't know who it is that might actually need or
want the services the document describes, you might consider:

a) making up something plausible and running with it,
b) finding someone who does know, and have them tell us, or
c) adopting Rex's explanation of who the users should be.

    > They key function is high probability of
    > call completion in a congested environment.

Okay, that's a really good simple statement of a reasonable and
desirable goal, made in a style which is palatable to IETF folks.
If you can get consensus from your side, let's go with that for now.

    > These are necessary functions (which already exist) without which,
    > the new technology can not be adopted.

Okay, so this could now be refined to:

"High probability of call completion in a congested environment is a
necessary precondition of VoIP adoption by [a presently unidentified user
community known to the DoD]."

...but since the IETF doesn't care whether people use particular products
and services, per se, that would be at least as effective if further
simplified to:

"High probability of call completion in a congested environment is desired
by [a presently unidentified user community known to the DoD]."

This starts to be self-evidently a common good.  If you can present your
case in such a way that it's recognized by the recipients of your argument
as being a common good, one which they themselves will in fact benefit
from, everyone will be on your side, and you won't have to actually make
much of an argument.  Which is how you want to deal with the IETF.  It
doesn't stay that simple once people start hammering out the details of
protocol changes, but it's the best place to start.

I'm assuming for now that the phrase you choose to replace the presently-
unidentified-&c. will be something like "emergency services personnel."

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:23:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27127
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:23:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2PE001831
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:25:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2PEv01828
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:25:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27116
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:22:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2OYv01796;
	Fri, 15 Nov 2002 21:24:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2KSv01686
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:20:28 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27045
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:17:43 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id A42F167103; Fri, 15 Nov 2002 17:42:46 -0500 (EST)
Date: Fri, 15 Nov 2002 21:20:19 -0500
Subject: Re: [Ieprep] Qualitative statement about quality
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <1e.250931d.2b06a6c9@aol.com>
Message-Id: <F3A47B5C-F909-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 15, 2002, at 14:36 America/Montreal, Mpierce1@aol.com 
wrote:
> How about the other part of the claim - that the IP connection had 
> about 6% loss? I presume you mean packet loss ratio. My information 
> tells me that many codecs fall apart at that loss rate, or at least 
> the degradation in audio quality is very noticable. The criteria 
> (which is normally met) for a digital connection through the PSTN is 
> for a bit error rate much less than that, so again, I can not possibly 
> imagine how one could claim that the Voice over IP connection you 
> cited was better than the PSTN. Y.1541 suggests that the objective 
> should be 0.1%.

Bill,
	Which specific codec(s) were you using ?

Mike,
	I would not want my life depending on a codec that falls apart at 6%
packet loss.  Please don't deploy that one, pick something more robust.

> You referred to the comparison being to a call from San Luis Obispo to 
> Berkeley. I imagine that the one end is on the Berkely campus, i.e., 
> probably not the "public" PSTN all the way. Maybe a lot of old, bad 
> wiring or analog switches on campus with lots of interference. Yes, 
> when you deal with some real long, old loops, the voice quality can be 
> worse, but this is not a fair comparision. (I, like many others, have 
> only several hundred feet of analog loop to the digital concentrator.)

Mike,

I actually think it is a pretty fair comparison -- unless you want to 
agree that
the Internet should not include access links in its performance 
measurements
(since those are the equivalent of "not the public PSTN all the way" 
for the IP
world).

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:27:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27251
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:27:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2U6O02023
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:30:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2U6v02019
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:30:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27247
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:27:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2T2v01943;
	Fri, 15 Nov 2002 21:29:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2Svv01927
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:28:57 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27231
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:26:12 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAG2P6ME003466;
	Fri, 15 Nov 2002 21:25:06 -0500 (EST)
Date: Fri, 15 Nov 2002 21:25:06 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211160225.gAG2P6ME003466@newdev.harvard.edu>
To: Mpierce1@aol.com, rja@extremenetworks.com
Subject: Re: [Ieprep] Re: Is QoS Dead?
Cc: ieprep@ietf.org
In-Reply-To: <0FAC8FEA-F908-11D6-B9A5-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> NSIS is working on an application-layer problem of telephony signalling 
> applications
> not on IP-layer QoS.

clarification - nsis is working on a protocol to install state in
devices along a path - this could be used for installing QoS or other
information in routers

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:28:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27277
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:28:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2V1r02060
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:31:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2V1v02057
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:31:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27265
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:28:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2U2v02009;
	Fri, 15 Nov 2002 21:30:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2Twv01969
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:29:58 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27244
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:27:13 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAG2SKtK003482;
	Fri, 15 Nov 2002 21:28:20 -0500 (EST)
Date: Fri, 15 Nov 2002 21:28:20 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211160228.gAG2SKtK003482@newdev.harvard.edu>
To: Janet.Gunn@DynCorp.com, rja@extremenetworks.com
Subject: Re: [Ieprep] representation & IETF culture
Cc: ieprep@ietf.org
In-Reply-To: <3C59495A-F909-11D6-B9A5-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> The profit motive turns out to be a highly effective mechanism in 
> helping
> the commercial sector re-focus itself naturally.  That mechanism is 
> necessarily
> absent from the government.

but, as you point out,  not from vendors to the government 

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:29:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27301
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:29:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2Vmr02098
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:31:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2Vmv02095
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:31:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27292
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:29:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2U1v01993;
	Fri, 15 Nov 2002 21:30:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2Tiv01957
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:29:44 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27235
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:26:58 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAG2G5d01401;
	Fri, 15 Nov 2002 18:16:05 -0800 (PST)
Date: Fri, 15 Nov 2002 18:16:05 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Mpierce1@aol.com, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: Is QoS Dead?
In-Reply-To: <0FAC8FEA-F908-11D6-B9A5-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211151814540.161-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 15 Nov 2002, RJ Atkinson wrote:
    > Folks wish they could find a way to make it deployable.

Hm.  Perhaps.  If so, they're vastly outnumbered by the folks who wish
they could find a way to make everyone permanently forget it existed.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:30:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27346
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:30:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2XC502167
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:33:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2XCv02164
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:33:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27342
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:30:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2W1v02128;
	Fri, 15 Nov 2002 21:32:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2VOv02082
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:31:24 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27275
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:28:38 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAG2PGd01469;
	Fri, 15 Nov 2002 18:25:16 -0800 (PST)
Date: Fri, 15 Nov 2002 18:25:16 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Mpierce1@aol.com, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Qualitative statement about quality
In-Reply-To: <F3A47B5C-F909-11D6-B9A5-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211151820280.161-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > Which specific codec(s) were you using ?

g711ulaw both ends, which is the default for the Cisco phones.

    > You referred to the comparison being to a call from San Luis Obispo to
    > Berkeley. I imagine that the one end is on the Berkely campus, i.e.,
    > probably not the "public" PSTN all the way.

Actually the Berkeley end was in my house which, for voice, has a
seven or eight year old 26-gauge 50-pair back to the CO, about 4kfeet
away.  SLO end was on campus, and may well have been through analog
switches or wiring even worse than the PSTN.  Nairobi end was residential.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:33:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27505
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:33:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2ZaU02274
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:35:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2Zav02271
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:35:36 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27482
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:32:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2Y1v02216;
	Fri, 15 Nov 2002 21:34:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2Xxv02186
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:33:59 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27370
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:31:14 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAG2Rrd01515
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 18:27:53 -0800 (PST)
Date: Fri, 15 Nov 2002 18:27:53 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: ieprep@ietf.org
Subject: Re: [Ieprep] Qualitative statement about quality
In-Reply-To: <F3A47B5C-F909-11D6-B9A5-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211151826040.161-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > Mpierce1@aol.com wrote:
    > How about the other part of the claim - that the IP connection had
    > about 6% loss? I presume you mean packet loss ratio.

Correct.  If you look at the subsequent ping, you'll see a somewhat higher
loss rate.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:36:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27862
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:36:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2cwK02988
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:38:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2cwv02984
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:38:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27806
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:36:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2c3v02975;
	Fri, 15 Nov 2002 21:38:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2b4v02491
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:37:04 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27617
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:34:19 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 1633867103; Fri, 15 Nov 2002 17:59:23 -0500 (EST)
Date: Fri, 15 Nov 2002 21:36:55 -0500
Subject: Re: [Ieprep] Qualitative statement about quality
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: <ieprep@ietf.org>
To: Scott Madley <scott@xgcic.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.BSO.4.33.0211150630530.4164-100000@sparcticus.sysctl.net>
Message-Id: <4581EF2A-F90C-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 15, 2002, at 01:47 America/Montreal, Scott Madley wrote:
> If any one has an interest, I'll see if I can dredge up some PSQM/MOS
> results from about a year ago that I complied that compare/contrast 
> voice
> quality on both the PSTN and a dedicated VoIP network, and the 
> associated
> results when off-loading to either the PSTN or a NGN network.
>
> -Scott

More data is almost always better.  URL would be helpful,
or email if it is ASCII and reasonable length.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:39:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27900
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:39:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2fdu03117
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:41:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2fdv03114
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:41:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27895
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:38:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2f1v03102;
	Fri, 15 Nov 2002 21:41:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2eWv03078
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:40:32 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27892
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:37:47 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 1B98E67103; Fri, 15 Nov 2002 18:02:46 -0500 (EST)
Date: Fri, 15 Nov 2002 21:40:18 -0500
Subject: Re: [Ieprep] NCS contracts with voice IXCs
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <CBED705A7FD2D311865500508B1089410A414969@chntex02.is.dyncorp.com>
Message-Id: <BE5C9819-F90C-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 15, 2002, at 02:21 America/Montreal, Gunn, Janet wrote:
> Exactly my point.

Glad we're communicating.

> The (proposed, future) "IP packet switching core" within the VOICE 
> IXC's
> network is NOT going to be the ISP that runs under the same corporate 
> name.
> I am not talking about a contract with the ISP side of the business.  
> I am
> talking about a contract with the VOICE side of the business, that will
> include IP technology in its network.

That is helpful clarification.  It is missing from most (all ?) of
the documents being discussed.  Document editors please note this.

> Who knows whether THAT (sub)network will be over provisioned or not?  
> Since
> it doesn't  exist yet, it WILL require new (now scarce) capital.
>
> Who knows what other performance characteristics it will have?

The answer to those last 2 queries is that the operator knows.

And it is best to provide the operator with a performance metric
in the contract (e.g. no more than X % packet loss for our packets)
than to specify that they MUST deploy x, y, and z mechanisms.
That way they choose to overprovision or do something quite different,
depending on which is cheaper in their situation.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:42:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28046
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:42:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2iha03252
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:44:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2ihv03249
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:44:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28032
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:41:57 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2i1v03224;
	Fri, 15 Nov 2002 21:44:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2hhv03176
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:43:43 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27976
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:40:58 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 6E44967103; Fri, 15 Nov 2002 18:06:01 -0500 (EST)
Date: Fri, 15 Nov 2002 21:43:33 -0500
Subject: Re: [Ieprep] Is this the service you are requesting?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: David Meyer <dmm@sprint.net>, "Ieprep (E-mail)" <ieprep@ietf.org>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DD4EB45.7080003@cs.columbia.edu>
Message-Id: <32F0550D-F90D-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 15, 2002, at 07:40 America/Montreal, Henning Schulzrinne 
wrote:

> Are you saying your network is setting DSCP to a non-zero value for 
> some packets? Otherwise, if you set all DSCPs to zero on ingress, 
> there's nothing to honor on egress (since they'll all be zero anyway). 
> I'm confused... Or are you keeping the DSCP of direct customers of 
> yours?

Consider that BGP packets are super-critical, that many routers 
automatically
mark BGP packets with the IP ToS setting of Internet Control, and that
BGP packets are inter-domain.

Might be strongly desirable to prefer the BGP packets to anything else 
on egress
to another network -- in the interest of availability, reliability, etc.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:44:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28099
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:44:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2kfi03392
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:46:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2kfv03389
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:46:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28078
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:43:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2k2v03347;
	Fri, 15 Nov 2002 21:46:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2j6v03320
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:45:06 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28044
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:42:21 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id BE26D67103; Fri, 15 Nov 2002 18:07:24 -0500 (EST)
Date: Fri, 15 Nov 2002 21:44:55 -0500
Subject: Re: [Ieprep] representation & IETF culture
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep '" <ieprep@ietf.org>
To: "Steve Silverman" <steves@shentel.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <KMEJKAPHBBCMCDDGMBLOOEGICAAA.steves@shentel.net>
Message-Id: <63D34240-F90D-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 15, 2002, at 08:07 America/Montreal, Steve Silverman 
wrote:
> Thank you, you are correct.  These are necessary functions (which
> already exist) without which, the new technology can not be adopted.
>
> Steve

Does this mean we get lucky, you all give up now, and we can go back
to building a better Internet ?

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:53:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28323
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:53:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2tht03624
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:55:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2thv03621
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:55:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28306
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:52:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2t3v03593;
	Fri, 15 Nov 2002 21:55:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2s3v03556
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:54:03 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28221
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:51:17 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAG2i6d01660;
	Fri, 15 Nov 2002 18:44:06 -0800 (PST)
Date: Fri, 15 Nov 2002 18:44:06 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Steve Silverman <steves@shentel.net>, "'ieprep '" <ieprep@ietf.org>
Subject: Re: [Ieprep] representation & IETF culture
In-Reply-To: <63D34240-F90D-11D6-B9A5-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211151842380.161-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > > Thank you, you are correct.  These are necessary functions (which
    > > already exist) without which, the new technology can not be adopted.
    >
    > Does this mean we get lucky, you all give up now, and we can go back
    > to building a better Internet ?

I think he meant (and see the edited version of this sentence in a
different email) that these functions exist in the PSTN, and were believed
to also be necessary in the Internet before unidentified users could adopt
inter-domain VoIP.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:54:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28352
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:54:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2uaH03670
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:56:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2uav03667
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:56:36 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28339
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:53:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2t4v03609;
	Fri, 15 Nov 2002 21:55:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2sQv03567
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:54:26 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28228
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:51:40 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 0ABBC67103; Fri, 15 Nov 2002 18:16:44 -0500 (EST)
Date: Fri, 15 Nov 2002 21:54:16 -0500
Subject: Re: [Ieprep] Re: Is QoS Dead?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Scott Bradner <sob@harvard.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211160225.gAG2P6ME003466@newdev.harvard.edu>
Message-Id: <B1DE2037-F90E-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 15, 2002, at 21:25 America/Montreal, Scott Bradner wrote:

>> NSIS is working on an application-layer problem of telephony 
>> signalling
>> applications
>> not on IP-layer QoS.
>
> clarification - nsis is working on a protocol to install state in
> devices along a path - this could be used for installing QoS or other
> information in routers

That is helpful.

So for folks who missed the RSVP experiment, I should note that a major
problem with RSVP was that it created too much state in routers along
the path and depended too much on that state being present (even though
the path changes dynamically with time).  This NSIS stuff is likely to 
hit
the same wall at least as hard.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 15 21:54:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28366
	for <ieprep-archive@odin.ietf.org>; Fri, 15 Nov 2002 21:54:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAG2uef03686
	for ieprep-archive@odin.ietf.org; Fri, 15 Nov 2002 21:56:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2uev03683
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 21:56:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28343
	for <ieprep-web-archive@ietf.org>; Fri, 15 Nov 2002 21:53:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2u2v03654;
	Fri, 15 Nov 2002 21:56:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAG2tMv03617
	for <ieprep@optimus.ietf.org>; Fri, 15 Nov 2002 21:55:22 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28303
	for <ieprep@ietf.org>; Fri, 15 Nov 2002 21:52:37 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAG2riWx003561;
	Fri, 15 Nov 2002 21:53:44 -0500 (EST)
Date: Fri, 15 Nov 2002 21:53:44 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211160253.gAG2riWx003561@newdev.harvard.edu>
To: rja@extremenetworks.com, sob@harvard.edu
Subject: Re: [Ieprep] Re: Is QoS Dead?
Cc: ieprep@ietf.org
In-Reply-To: <B1DE2037-F90E-11D6-B9A5-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

one hopes that there has been learning going on

----
>From rja@extremenetworks.com  Fri Nov 15 21:52:55 2002
Date: Fri, 15 Nov 2002 21:54:16 -0500
Subject: Re: [Ieprep] Re: Is QoS Dead?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Scott Bradner <sob@harvard.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211160225.gAG2P6ME003466@newdev.harvard.edu>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)


On Friday, Nov 15, 2002, at 21:25 America/Montreal, Scott Bradner wrote:

>> NSIS is working on an application-layer problem of telephony 
>> signalling
>> applications
>> not on IP-layer QoS.
>
> clarification - nsis is working on a protocol to install state in
> devices along a path - this could be used for installing QoS or other
> information in routers

That is helpful.

So for folks who missed the RSVP experiment, I should note that a major
problem with RSVP was that it created too much state in routers along
the path and depended too much on that state being present (even though
the path changes dynamically with time).  This NSIS stuff is likely to 
hit
the same wall at least as hard.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 06:58:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16298
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 06:58:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGC12x02508
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 07:01:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGC12v02505
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 07:01:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16287
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 06:58:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGC0Bv02470;
	Sat, 16 Nov 2002 07:00:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGBxxv02419
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 06:59:59 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16262
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 06:57:21 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Sat, 16 Nov 2002 06:59:37 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111606594607373
 ; Sat, 16 Nov 2002 06:59:46 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <W9RA6LVK>; Sat, 16 Nov 2002 07:01:08 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77992@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Gunn, Janet '" <Janet.Gunn@dyncorp.com>
Cc: "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] NCS contracts with voice IXCs
Date: Sat, 16 Nov 2002 06:59:45 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

 
On Friday, Nov 15, 2002, at 02:21 America/Montreal, Gunn, Janet wrote:
> The (proposed, future) "IP packet switching core" within the VOICE 
> IXC's
> network is NOT going to be the ISP that runs under the same corporate 
> name.
> I am not talking about a contract with the ISP side of the business.  
> I am
> talking about a contract with the VOICE side of the business, that
will
> include IP technology in its network.

> Who knows whether THAT (sub)network will be over provisioned or not?  
> Since
> it doesn't  exist yet, it WILL require new (now scarce) capital.
>
> Who knows what other performance characteristics it will have?

This seems to address the IP bridging case.  Telco operators appear to like
the Media Gateway Controller/Gateway architecture using MGCP or Megaco to
communicate with media gateways*.  Hence this case will often have Call
Admission Control (CAC).  So NCS contracts with voice IXCs could continue to
provide increased probably of call completion.

With respect to call quality, it also seems Telco operators are the ones
most concerned with call quality and sometimes select ATM for this reason.
(Whether ATM is dead or not may have a lot to do with whether you are an ISP
or a Telco company.  Bill considers it somewhat dead and from his
perspective, I see his point.  But I'm not so sure companies like Cable &
Wireless see it the same way from the telco side of the house.)  Telco
softswitch class-4/class-5 replacement networks seem the most likely to
provide acceptable call quality so I'm not sure whether it makes sense to
worry if they may be under provisioned for transport given they probably
have CAC and are concerned with call quality.

Kimberly


*My guess on this comes from looking at vendor offerings aimed at
traditional telco operators and media sources announcing some contracts.
Packet voice is a huge space and no one architecture can be assumed to
really sum up the situation.  No need to provide exceptions, I know they
exist and I also know vendor solutions don't necessarly make for industry
solutions.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 07:12:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16505
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 07:12:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGCEsV03506
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 07:14:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGCEsv03503
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 07:14:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16497
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 07:12:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGCE3v03492;
	Sat, 16 Nov 2002 07:14:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGCDbv03464
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 07:13:37 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16489
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 07:10:59 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAGCELBZ015459;
	Sat, 16 Nov 2002 04:14:21 -0800
Date: Sat, 16 Nov 2002 04:14:21 -0800
From: David Meyer <dmm@sprint.net>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: Scott Bradner <sob@harvard.edu>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: Is QoS Dead?
Message-ID: <20021116041421.E15410@sprint.net>
References: <200211160225.gAG2P6ME003466@newdev.harvard.edu> <B1DE2037-F90E-11D6-B9A5-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <B1DE2037-F90E-11D6-B9A5-00039357A82A@extremenetworks.com>; from rja@extremenetworks.com on Fri, Nov 15, 2002 at 09:54:16PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


On Fri, Nov 15, 2002 at 09:54:16PM -0500, RJ Atkinson wrote:
>> 
>> On Friday, Nov 15, 2002, at 21:25 America/Montreal, Scott Bradner wrote:
>> 
>> >> NSIS is working on an application-layer problem of telephony 
>> >> signalling
>> >> applications
>> >> not on IP-layer QoS.
>> >
>> > clarification - nsis is working on a protocol to install state in
>> > devices along a path - this could be used for installing QoS or other
>> > information in routers
>> 
>> That is helpful.
>> 
>> So for folks who missed the RSVP experiment, I should note that a major
>> problem with RSVP was that it created too much state in routers along
>> the path and depended too much on that state being present (even though
>> the path changes dynamically with time).  This NSIS stuff is likely to 
>> hit
>> the same wall at least as hard.

As Ran said, we've seen this film before (INT-SERV, ATM per flow
state, etv). It hasn't been sucessful yet. Is there
something that makes us think it will be successful now? 

Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 07:31:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16696
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 07:31:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGCXeB03983
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 07:33:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGCXev03980
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 07:33:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16670
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 07:31:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGCX2v03961;
	Sat, 16 Nov 2002 07:33:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGCW2v03914
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 07:32:02 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16661
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 07:29:23 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAGCWoCV015519;
	Sat, 16 Nov 2002 04:32:50 -0800
Date: Sat, 16 Nov 2002 04:32:50 -0800
From: David Meyer <dmm@sprint.net>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: Mpierce1@aol.com, ieprep@ietf.org
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Message-ID: <20021116043250.C15465@sprint.net>
References: <95.25aeb5eb.2b06a709@aol.com> <8E6DAF5C-F906-11D6-B9A5-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <8E6DAF5C-F906-11D6-B9A5-00039357A82A@extremenetworks.com>; from rja@extremenetworks.com on Fri, Nov 15, 2002 at 08:56:00PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>> Several ISPs that deployed "prioritisation" and/or "QoS" found that:
>> 	(1) priority packets got worse treatment than best-effort packets,
>> 	    particularly in times of network stress
>> 	(2) deployment costs were intolerably high (i.e. money needed to deploy
>> 	    was non-trivially high).
>> 	(3) deployment was not feasible in a large-scale commercial backbone
>> 	(4) operations costs (e.g. debugging) were insanely high
>> 	(5) much of the currently deployed equipment did not behave very well
>> 	    when lots of features (especially QoS) were enabled.  To be fair,
>> 	    some equipment is robust when features are turned on.  The latter
>>           equipment generally has a hardware-based (e.g. ASIC, FPGA) implementation of the enabled features.

This was certainly my experience. Basically, there is no
"physics" that will let more complexity and mechanism result in
decreased OPEX (one has to find the tradeoffs there and work in
that space). There is also no practical way to keep such a
service from being DoS'ed.  

Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 09:53:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18464
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 09:53:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGEtFA10021
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 09:55:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGEtEv10018
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 09:55:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18461
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 09:52:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGEs8v09990;
	Sat, 16 Nov 2002 09:54:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGErhv09970
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 09:53:43 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18447
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 09:51:03 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAGEral8006275
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Sat, 16 Nov 2002 09:53:37 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAGErYdG019716
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 16 Nov 2002 09:53:35 -0500 (EST)
Message-ID: <3DD65BD2.3020308@cs.columbia.edu>
Date: Sat, 16 Nov 2002 09:53:06 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: Is QoS Dead?
References: <0FAC8FEA-F908-11D6-B9A5-00039357A82A@extremenetworks.com>
In-Reply-To: <0FAC8FEA-F908-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> NSIS is working on an application-layer problem of telephony signalling
> applications,
> not on IP-layer QoS.  ISPs generally only offer IP forwarding as a
> service, not
> SIP or other application layer services.  I doubt anything done in NSIS
> will relate
> to anything that actually gets deployed at the IP-layer.

John Loughney can speak for 'his' group, but I don't think this is 
correct. To cite the NSIS framework document 
http://www.ietf.org/internet-drafts/draft-ietf-nsis-fw-01.txt:

    NSIS will work on signaling from an end point that follows a path
    through the net that is determined by layer 3 routing and is used to
    convey information to the devices the signals pass through - the
    signaling can, for example, install soft state in the devices it
    passes through. A signaling end point could be a device along the
    path, which signals for a data flow that passes through it.
...
   The NSIS protocol is intended to be used as a signaling control plane
    for the variety of network resources required for data traffic across
    the Internet. The most common NSIS signaling applications are QoS
    resources, firewalls and NATs resources, etc. The NSIS signaling
    itself does not depend on the signaling application it is used for
    but the information it carries does. This section discusses the basic
    signaling entities of the protocol as well as interfaces between
    them.


>
> RSVP was deployed in some limited ways.  It did not scale even to those
> very limited
> deployments.  RSVP is pretty much abandoned as a QoS mechanism, based on
> that experience.

In fairness, it should be noted that the initial scaling problems were 
partially related to a "demo" implementation becoming a production 
implementation, and falling flat on its face. (Rumor has it that 
signaling state was searched by linear search, which works fine for a 
demo, but doesn't for real load.)

There are clear existence proofs (see the work at TU Darmstadt) for RSVP 
implementations that scale to several hundred thousand call setups a 
second on commodity platforms. Thus, even if every single phone call in 
the US would traverse a single RSVP router, you'd be easily be able to 
keep up with the signaling load itself.

We have done similar measurements on RSVP - even on a lowly 68020 router 
of five years ago, you're very unlikely to run out of CPU resources for 
reasonable assumptions.

I suspect that "scaling" is much more of a problem in terms of AAA and 
interdomain trust issues rather than state or CPU resources.

Henning

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 10:06:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18612
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 10:06:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGF8dG10929
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 10:08:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGF8dv10926
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 10:08:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18604
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 10:05:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGF81v10890;
	Sat, 16 Nov 2002 10:08:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGF7Pv10870
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 10:07:25 -0500
Received: from EXECDSL.COM (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18598
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 10:04:45 -0500 (EST)
Received: from [66.95.38.74] (HELO JLaptop.stevecrocker.com)
  by EXECDSL.COM (CommuniGate Pro SMTP 3.3)
  with ESMTP id 3975226; Sat, 16 Nov 2002 10:07:22 -0500
Message-Id: <5.1.0.14.0.20021116100025.018b3b80@mail.stevecrocker.com>
X-Sender: joel@stevecrocker.com@mail.stevecrocker.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 16 Nov 2002 10:07:02 -0500
To: "Gunn, Janet" <Janet.Gunn@dyncorp.com>
From: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: RE: [Ieprep] NCS contracts with voice IXCs
Cc: ieprep <ieprep@ietf.org>
In-Reply-To: <CBED705A7FD2D311865500508B1089410A414969@chntex02.is.dynco
 rp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

If there is a service that (one or more) telephone companies want to 
deliver using IP,
and if that service requires additional standardization that is suitable 
for the IETF (ie not the API between SIP and TCP, but new interoperable 
fields in SIP or a new standardized behavior in diffserv),
then I would expect to see email from folks at that telephone company 
indicating that they are trying to build their infrastructure, they have 
specific unmet requirements, and would like to see progress.

To some degree, we have part of that.  I believe that the NCS requirements 
are actually about what they would like to do on their own 
network.  However, the requests currently mix issues that are best done by 
contract, issues that are fully covered by current RFCs, and some issues 
which could probably use discussion.  It is also very important in such 
documents to be clear about what requests are application requests (a 
probably reasonable request for a SIP header field) and what requests are 
network layer requests.

However, we have not heard from Voice IXCs.  Given that the service you 
describe is used today, and works today, with conventional IP services 
using commercial product, I would need to see a clear problem description 
before concluding that IXCs need new standards.

Yours,
Joel M. Halpern

At 02:21 AM 11/15/2002 -0500, Gunn, Janet wrote:
>Exactly my point.
>
>The (proposed, future) "IP packet switching core" within the VOICE IXC's
>network is NOT going to be the ISP that runs under the same corporate name.
>I am not talking about a contract with the ISP side of the business.  I am
>talking about a contract with the VOICE side of the business, that will
>include IP technology in its network.
>
>Who knows whether THAT (sub)network will be over provisioned or not?  Since
>it doesn't  exist yet, it WILL require new (now scarce) capital.
>
>Who knows what other performance characteristics it will have?


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 10:06:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18625
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 10:06:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGF8fh10944
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 10:08:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGF8fv10941
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 10:08:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18608
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 10:06:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGF82v10906;
	Sat, 16 Nov 2002 10:08:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGF7Qv10874
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 10:07:26 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18595
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 10:04:40 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 16 Nov 2002 15:01:28 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <W9RLAJPA>; Sat, 16 Nov 2002 10:07:21 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D4C@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock '" <woody@pch.net>, "Nguyen, An" <nguyena@ncs.gov>
Cc: "'Mpierce1@aol.com '" <Mpierce1@aol.com>,
        "'ieprep@ietf.org '"
	 <ieprep@ietf.org>
Subject: RE: [Ieprep] Qualitative statement about quality
Date: Sat, 16 Nov 2002 10:07:14 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

 


>I can't quite make out what you're saying here.  600ms was the observed
l>atency between San Luis Obispo and Nairobi, at the time of the call.
>The
>observed latency between San Luis Obisbo and Berkeley was about 200ms
>across four ASes.  As I trace Berkeley to Nairobi right now, I get about
>950ms, 42% drop, and seven ASes in the path.  It's not peak use hours in
>either location at the moment, and this is a path which we use many
>times
>each day for routine calls, when it's qualitatively much worse than it
>is at
>the moment.  The quality of the VoIP calls is much, much higher than
>that
>of PSTN calls, and it's difficult to keep the PSTN calls up...  Initial
>call-completion rate is only about 80%, and most calls are dropped
>within
twenty minutes.  We've never had a failed connection or a dropped call
between this pair of VoIP phones, by contrast.

>router.brk#trace nbi.ispkenya.com
>Translating "nbi.ispkenya.com"...domain server (131.161.3.1) [OK]

>Type escape sequence to abort.
>Tracing the route to nbi.ispkenya.com (212.49.87.2)

>  1 131.13.22.157.zocalo.net (157.22.13.131) [AS715] 4 msec 4 msec 8
>msec
>  2 gige-g2-0.gsr12008.pao.he.net (64.71.128.117) [AS 6939] 4 msec 4
>msec 0 msec
>  3 interconnect-eng.SanJose1.Level3.net (209.245.146.201) [AS 3356] 0
>msec 20 msec 4 msec
>  4 GigabitEthernet3-0.core1.SanJose1.Level3.net (209.244.3.245) [AS
>3356] 4 msec 4 msec 4 msec
>  5 ae0-51.mp1.SanJose1.Level3.net (64.159.2.1) [AS 3356] 4 msec 4 msec
>4 msec
>  6 so-3-0-0.mp1.NewYork1.Level3.net (64.159.1.41) [AS 3356] 80 msec 80
>msec 80 msec
>  7 gige9-0-53.hsipaccess1.NewYork1.Level3.net (64.159.17.71) [AS 3356]
>76 msec 76 msec 76 msec
>  8 unknown.Level3.net (209.244.160.242) [AS 3356] 81 msec 92 msec 80
>msec
>  9 host-66-133-0-22.verestar.net (66.133.0.22) [AS 11908] 156 msec 156
>msec 157 msec
> 10 unknown.Level3.net (64.158.116.117) [AS 11908] 188 msec 184 msec 185
>msec
> 11 host-66-133-6-2.verestar.net (66.133.6.2) [AS 11908] 184 msec 184
>msec 185 msec
> 12  * host-66-133-6-10.verestar.net (66.133.6.10) [AS 11908] 725 msec
>725 msec
> 13 212.49.70.109 [AS 12455] 745 msec 741 msec 753 msec
> 14  * 10.10.2.10 781 msec *
> 15 64.86.231.2 [AS 6453] 978 msec 901 msec 1859 msec

When you did a trace route from 131.13.22.157 (local router) to 
64.86.231.2 [AS 6453], the trace route packet went through 
AS715  -  4 ms (one-way average delay)
AS6939 -  4 ms
AS3358 -  20ms
       -  4ms
       -  4ms
       -  80ms
       -  76ms
       -  92ms
AS11958-  156ms
       -  184ms
       -  184ms
       -  725ms
AS14255-  741ms
10.10.2.10 - 781ms
AS6453 -  901ms
-------------------
Total  = too much

If you add all the delay numbers from the orgination [aS715] to destination
[AS6443], the total will be too much of a delay to provide voiceIP or  any
time-sensitive, interactive applications objectively. The is a certain delay
allowed for a certain voice codec. In order to provide voiceIP service with
some QoS, you have to make sure that your parameters stay within bounds.

>router.brk#ping
>Protocol [ip]:
>Target IP address: 212.49.87.2
>Repeat count [5]: 100
>Datagram size [100]:
>Timeout in seconds [2]:
>Extended commands [n]:
>Sweep range of sizes [n]:
>Type escape sequence to abort.
>Sending 100, 100-byte ICMP Echos to 212.49.87.2, timeout is 2 seconds:
>.!!!!!.!..!!!!.!!...!!!!.!!!.!!...!!!!!.!!...!...!.!!.!...!!.!!!!...!.
>..!..!!.!.!!!!!!.!.!!!!!.!..!.
>Success rate is 58 percent (58/100), round-trip min/avg/max =
>774/959/1262 ms
>router.brk#

I assume you did an ICMP ping on a router you were on to this node
212.4987.2, the minumm round-trip delay is 774, average 959 , and the max
1262 ms. I don't know how far (or how many hops) this ICMP packet traveled,
but the round-trip delay seems a little too much for voiceIp.

Regards,

An

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 10:41:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19158
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 10:41:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGFhbX12466
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 10:43:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFhbv12463
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 10:43:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19146
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 10:40:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFh1v12449;
	Sat, 16 Nov 2002 10:43:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFgEv12422
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 10:42:14 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19107
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 10:39:35 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAGFaCd07053;
	Sat, 16 Nov 2002 07:36:12 -0800 (PST)
Date: Sat, 16 Nov 2002 07:36:12 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: RJ Atkinson <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: Is QoS Dead?
In-Reply-To: <3DD65BD2.3020308@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211160734230.6901-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 16 Nov 2002, Henning Schulzrinne wrote:
    > There are clear existence proofs (see the work at TU Darmstadt) for RSVP
    > implementations that scale to several hundred thousand call setups a
    > second on commodity platforms. Thus, even if every single phone call in
    > the US would traverse a single RSVP router, you'd be easily be able to
    > keep up with the signaling load itself.
    > We have done similar measurements on RSVP - even on a lowly 68020 router
    > of five years ago, you're very unlikely to run out of CPU resources for
    > reasonable assumptions.

The question is not whether people in labs think it's a neat idea, which
is quite clearly the case...  This kind of garbage always tickles lab
people pink.  The question is whether it has ever worked in the real
world, and the answer to that is no, it always falls apart under the
weight of its own complexity when it hits the real world.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 10:45:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19305
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 10:45:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGFltM12612
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 10:47:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFltv12609
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 10:47:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19284
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 10:45:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFl2v12588;
	Sat, 16 Nov 2002 10:47:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFkTv12565
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 10:46:29 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19200
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 10:43:50 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAGFkJl8009893
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Sat, 16 Nov 2002 10:46:20 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAGFkHdG020843
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 16 Nov 2002 10:46:18 -0500 (EST)
Message-ID: <3DD6682C.8090504@cs.columbia.edu>
Date: Sat, 16 Nov 2002 10:45:48 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: "'ieprep '" <ieprep@ietf.org>
Subject: Re: [Ieprep] terminology
References: <28E2365E-F905-11D6-B9A5-00039357A82A@extremenetworks.com>
In-Reply-To: <28E2365E-F905-11D6-B9A5-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>
> In IETF, "requirement" means something that an implementer MUST implement
> and/or something that an operator MUST deploy.
>
I think it's actually somewhat more subtle than that. We essentially 
have at least three requirements, even though the language of RFC 2119 
only covers one of these. This is partially due to the fact that the 
protocol development approach in the IETF has changed in practice, at 
least in high-activity or contentious WGs, without this having been 
formally documented.

One way to slice this is by looking at this as three levels of indirection:

(1) We have requirements in protocol definitions, generally expressed as 
MUST, MUST NOT (and maybe SHOULD), according to 2119, as in:

  MUST   This word, or the terms "REQUIRED" or "SHALL", mean that the
    definition is an absolute requirement of the specification.

These are requirements to implementors of the protocol.

(2) We have requirements that a protocol *definition* needs to fulfill. 
For an example I'm familiar with: All new protocol definitions for SIP 
now have to go through SIPPING, which simply writes a requirement 
document, which is then handed to SIP for the actual protocol work. This 
document may use the same MUST, MAY or SHOULD terminology in 2119, but 
this is a meta-requirement for the protocol, not for an implementor - 
there is no protocol yet to implement. A MUST simply means that every 
protocol candidate has to satisfy this requirement or it's out of the 
running. This level of requirement does not address the fundamental need 
or many of the surrounding assumptions. For example, the NSIS 
requirements assume it as a given that we'll need a protocol to 
establish layer-3 state in the network and the question is simply what 
consequence this goal has when translated into finer-grained questions. 
If you disagree with the goal, speaking up at WG charter time would have 
been the appropriate moment.

In IEPREP, I believe that my SIP-related document roughly falls into 
this category.

(3) We have requirements for certain functionality in the network. In a 
sense, this is one more step removed from (2). It simply says "if a 
network wants to support this user-level functionality, it should have 
the following properties or offer the following services". This is not 
something that the IETF has done much of. It leaves the solution space 
relatively open, although in reality the requirements may constrain the 
space to a fairly narrow one. Some of these are BCPs, but some are more 
forward looking, in that there is no "best" and no "current" practice to 
document yet.

In searching for "requirements" in existing recent RFCs, we get a pretty 
good sampling of all of these; below, I labeled them with (2) or (3) 
according to the above. Clearly, most are in the (2) category. Every 
protocol spec citing 2119 is in category (1).

3386 Network Hierarchy and Multilayer Survivability (3)

This document presents a proposal of the near-term and
practical requirements for network survivability and hierarchy in
current service provider environments.

3384 Lightweight Directory Access Protocol (version 3) Replication
Requirements (2)

3379 Delegated Path Validation and Delegated Path Discovery Protocol
Requirements (2)

3375 Generic Registry-Registrar Protocol Requirements (2)

3365 Strong Security Requirements for Internet Engineering Task Force
Standard Protocols (2)

3354 Internet Open Trading Protocol Version 2 Requirements (2)

3351 User Requirements for the Session Initiation Protocol (SIP) in
Support of Deaf, Hard of Hearing and Speech-impaired Individuals (3)

3304 Middlebox Communications (midcom) Protocol Requirements (2)

3327 Requirements for Reliable Server Pooling (2 or 3)

3172 Management Guidelines & Operational Requirements for the Address
and Routing Parameter Area Domain ("arpa")

Maybe explicitly saying "user requirements" (3) and "protocol 
requirements" or "requirements for protocols" (2) might help to make 
this clearer.

We also have documents that then assess candidate protocols, 
particularly in areas that are contentious (midcom and AAA come to 
mind). I suspect that having us be explicitly aware of this three-step 
might at least help us to keep our document goals straight. For example, 
user requirements here might be
- use regular Internet service for emergency communications
- work with the full range of access speeds
- support VoIP at a certain quality level, citing relevant quantitative 
traceable requirements
- deal with situations where the network is under deliberate attack
- deal with situations of resource scarcity and applications that have 
different value (or different levels of authentication)
etc.

These are just examples to give a flavor of what I have in mind.

In a document then written by Ran and Bill (and hopefully others), 
possible tools/mechanisms/protocols can be assessed as to why they work 
or don't work (or, probably more often, where they might work and where 
not). Here, we probably have to distinguish between things that are 
implementable if somebody considered it important and limitations of 
today's equipment. (Random example: packet filtering for DOS attacks is 
probably not implementable on today's deployed routers, but this does 
not imply that we should stop working on the technology.)

If there's a gap, we go back to requirement (2), with a concrete 
protocol in mind. If there's an existing WG, it becomes input, if 
there's not, it becomes a BOF charter :-)

Does this make sense?

Henning

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 10:46:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19328
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 10:46:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGFmst12656
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 10:48:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFmrv12653
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 10:48:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19322
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 10:46:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFm1v12637;
	Sat, 16 Nov 2002 10:48:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFlCv12602
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 10:47:12 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19280
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 10:44:33 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAGFf9d07113;
	Sat, 16 Nov 2002 07:41:09 -0800 (PST)
Date: Sat, 16 Nov 2002 07:41:09 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: "'Mpierce1@aol.com '" <Mpierce1@aol.com>,
        "'ieprep@ietf.org '" <ieprep@ietf.org>
Subject: RE: [Ieprep] Qualitative statement about quality
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D4C@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211160737370.6901-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 16 Nov 2002, Nguyen, An wrote:
    > When you did a trace route from 131.13.22.157 (local router)

Actually that's the next-hop router...  I did the trace from the router
which the phone is behind, not the phone.  The phone is not a BGP-speaker
itself.

    > If you add all the delay numbers from the orgination to
    > destination, the total will be too much of a delay to provide
    > voiceIP.

I'm not asking you whether it _would_ work.  I'm telling you that it
_does_ work, absolutely repeatably, day in and day out, and it _does_ work
_substantially better than the PSTN_, which nearly inevitably fails on any
call longer than a few minutes duration for the same pair of endpoints.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 10:50:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19375
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 10:50:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGFqfk12775
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 10:52:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFqfv12772
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 10:52:41 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19368
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 10:50:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFq1v12754;
	Sat, 16 Nov 2002 10:52:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGFpbv12728
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 10:51:37 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19359
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 10:48:58 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAGFjXd07169;
	Sat, 16 Nov 2002 07:45:33 -0800 (PST)
Date: Sat, 16 Nov 2002 07:45:33 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Joel M. Halpern" <joel@stevecrocker.com>
cc: "Gunn, Janet" <Janet.Gunn@dyncorp.com>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] NCS contracts with voice IXCs
In-Reply-To: <5.1.0.14.0.20021116100025.018b3b80@mail.stevecrocker.com>
Message-ID: <Pine.GSO.4.44.0211160741550.6901-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



    > joel@stevecrocker.com

Wow, that email address is a little scary to contemplate.  :-)

      On Sat, 16 Nov 2002, Joel M. Halpern wrote:
    > If there is a service that (one or more) telephone companies want
    > to deliver using IP, and if that service requires additional
    > standardization, then I would expect to see email from folks at that
    > telephone company indicating that they are trying to build their
    > infrastructure, they have specific unmet requirements, and would
    > like to see progress.
    > However, we have not heard from Voice IXCs.  Given that the service you
    > describe is used today, and works today, with conventional IP services
    > using commercial product, I would need to see a clear problem description
    > before concluding that IXCs need new standards.

Actually, that's why Peter Lothberg and I are supposed to be here.  We're
the two folks operating international VoIP internetworks.  And we'd dearly
love to keep these folks from breaking them.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 11:02:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19648
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 11:02:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGG52f13216
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 11:05:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGG52v13213
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 11:05:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19640
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 11:02:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGG44v13175;
	Sat, 16 Nov 2002 11:04:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGG3kv13147
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 11:03:46 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19619
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 11:01:07 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAGG3el8010687
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Sat, 16 Nov 2002 11:03:40 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAGG3cdG021179
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 16 Nov 2002 11:03:39 -0500 (EST)
Message-ID: <3DD66C3E.7010806@cs.columbia.edu>
Date: Sat, 16 Nov 2002 11:03:10 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Joel M. Halpern" <joel@stevecrocker.com>
CC: "Gunn, Janet" <Janet.Gunn@dyncorp.com>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] NCS contracts with voice IXCs
References: <5.1.0.14.0.20021116100025.018b3b80@mail.stevecrocker.com>
In-Reply-To: <5.1.0.14.0.20021116100025.018b3b80@mail.stevecrocker.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> However, we have not heard from Voice IXCs.  Given that the service you
> describe is used today, and works today, with conventional IP services
> using commercial product, I would need to see a clear problem
> description before concluding that IXCs need new standards.
>
We don't know how many voice IXCs are on this list, but given the 
architecture discussions we've had, there are at least three possible 
interpretations:

(1) Voice IXCs mix voice and commodity Internet service ("data") on the 
same infrastructure, with no DiffServ, IntServ or other QoS (black) 
magic. They find no problem using existing technology. At best, it might 
be helpful to document operational experience if these carriers are 
willing to share it.

(2) Voice IXCs run a logically separate network for voice, probably via 
ATM VCs or MPLS paths at layer 2 or 2.5. Case A: They are happy with 
that and see no need to go to (1). Case B: If they'd like to go to (1), 
but are missing functionality, there's work to do.

On a separate L2/2.5 "network", the problem becomes much simpler, 
particularly if the capacity limit is primarily given by PSTN gateway 
capacity. Traditional Erlang-style engineering will do a pretty good job 
there, without worrying about the packet level.

(3) Voice IXCs run a completely separate network infrastructure, at 
fiber or wavelength level. Integration is at best at conduit level 
("layer 0"?). Again, they can either have decided that that's cheapest 
or would at least like to explore (2) or (1). I think most traditional 
IXCs currently full into this camp; almost all of them are exploring (1) 
or (2), from what I know.

We seem to have real-time integration at layer 1, 2/2.5 and 3. Ran seems 
to argue that carriers are well-advised to stay with (3), Bill says (1) 
works just find (but there's insufficient voice volume to care in any 
event) and I'm sure somebody else is a proponent of (2).

Given that all major telecom equipment vendors are active in NSIS, 
there's at least some indication of interest in moving from (2) to (1), 
even if primarily for the wireless access space. (Very few wireless 
carriers participate in the IETF, from what I can tell, regardless of 
the area.)

Henning

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 11:13:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19973
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 11:13:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGGFpE14088
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 11:15:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGFpv14085
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 11:15:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19956
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 11:13:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGF1v14069;
	Sat, 16 Nov 2002 11:15:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGEtv14049
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 11:14:55 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19923
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 11:12:16 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 4E20A67103; Sat, 16 Nov 2002 07:37:24 -0500 (EST)
Date: Sat, 16 Nov 2002 11:14:50 -0500
Subject: Re: [Ieprep] NCS contracts with voice IXCs
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211160741550.6901-100000@paixhost.pch.net>
Message-Id: <88826B2D-F97E-11D6-A2AE-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 16, 2002, at 10:45 America/Montreal, Bill Woodcock 
wrote:

> Actually, that's why Peter Lothberg and I are supposed to be here.  
> We're
> the two folks operating international VoIP internetworks.  And we'd 
> dearly
> love to keep these folks from breaking them.

Bill,
	As you keep pointing out, your VoIP deployment does not interconnect
with the PSTN, so it does not qualify as an IXC.  Peter's kind of does
interconnect, but in a small and curious way that is definitely not an 
IXC network.

	So Joel's point was on target.  One thing we need here are folks 
equivalent
to "Long Lines folks with IP clue who are moving from phone switches to 
VoIP".

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 11:18:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20071
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 11:18:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGGKu514270
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 11:20:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGKuv14267
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 11:20:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20061
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 11:18:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGK2v14243;
	Sat, 16 Nov 2002 11:20:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGJ7v14198
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 11:19:07 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20045
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 11:16:28 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id B78CC67103; Sat, 16 Nov 2002 07:41:36 -0500 (EST)
Date: Sat, 16 Nov 2002 11:19:03 -0500
Subject: Re: [Ieprep] NCS contracts with voice IXCs
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DD66C3E.7010806@cs.columbia.edu>
Message-Id: <1F01AA49-F97F-11D6-A2AE-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 16, 2002, at 11:03 America/Montreal, Henning 
Schulzrinne wrote:
>  Ran seems to argue that carriers are well-advised to stay with (3), 
> ...

"Carrier" is ambiguous.  I agree with the sentence above iff one edits 
that
"carriers" to be "PSTN/Voice carriers".

And note that my position, while different from Bill's, does not 
contradict
Bill's position.  One can believe that (1) will work properly in a well 
engineered
network, while still believing that phone carriers will be more 
successful
if they run with (3) for a long while.  My root belief, based on 
deployment,
is that selecting the right codec is a large part of the engineering 
needed
for emergency voice services.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 11:21:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20132
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 11:21:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGGNcT14406
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 11:23:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGNcv14403
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 11:23:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20112
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 11:20:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGN1v14372;
	Sat, 16 Nov 2002 11:23:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGM8v14348
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 11:22:08 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20088
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 11:19:28 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAGGG2d07416;
	Sat, 16 Nov 2002 08:16:02 -0800 (PST)
Date: Sat, 16 Nov 2002 08:16:02 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
cc: "Joel M. Halpern" <joel@stevecrocker.com>,
        "Gunn, Janet" <Janet.Gunn@dyncorp.com>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] NCS contracts with voice IXCs
In-Reply-To: <3DD66C3E.7010806@cs.columbia.edu>
Message-ID: <Pine.GSO.4.44.0211160813560.6901-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 16 Nov 2002, Henning Schulzrinne wrote:
    > there are at least three possible interpretations:
    > (1) Voice IXCs mix voice and commodity Internet service
    > (2) Voice IXCs run a logically separate network for voice
    > (3) Voice IXCs run a completely separate network infrastructure

Each of which are possible, but then there's the common case, which will
always outnumber all of those three put together, which is

(4) Voice IXCs don't do or know anything about data, since they ride
several layers higher in the stack, and the underlying data is
assumed to be present due to the customer's arrangement with an ISP.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 11:24:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20234
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 11:24:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGGQtp14537
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 11:26:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGQtv14534
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 11:26:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20231
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 11:24:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGQ2v14499;
	Sat, 16 Nov 2002 11:26:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGGQ1v14485
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 11:26:01 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20171
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 11:23:21 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAGGJxd07450;
	Sat, 16 Nov 2002 08:19:59 -0800 (PST)
Date: Sat, 16 Nov 2002 08:19:59 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] NCS contracts with voice IXCs
In-Reply-To: <88826B2D-F97E-11D6-A2AE-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211160816380.6901-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Sat, 16 Nov 2002, RJ Atkinson wrote:
    > 	As you keep pointing out, your VoIP deployment does not interconnect
    > with the PSTN, so it does not qualify as an IXC.

"Inter-exchange carrier?"  Perhaps we should examine the definition, then,
if it doesn't cover a network with nodes in four continents.

Besides, the PSTN _does_ interconnect with my network, I just continue to
make the case that since that doesn't scale, the PSTN operators won't
_generally_ interconnect with the rest of the network.  I mean, there's
just no way they could afford to.  I may be a nice guy and not charge them
above cost, but most network operators will look at PSTN dinosaurs and not
be so generous; they'll look at them as potential customers, rather than
retarded half-wits deserving sympathy, and charge them big interconnect
fees, which they won't be able to afford to pay.

So in the general case, the PSTN won't be able to afford to connect.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 12:34:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21261
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 12:34:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGHajK17772
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 12:36:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGHajv17769
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 12:36:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21249
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 12:34:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGHV5v17607;
	Sat, 16 Nov 2002 12:31:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGHUNv17559
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 12:30:23 -0500
Received: from imo-r06.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21145
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 12:27:43 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r06.mx.aol.com (mail_out_v34.13.) id j.16.28640eb8 (3932);
	Sat, 16 Nov 2002 12:30:07 -0500 (EST)
Message-ID: <16.28640eb8.2b07da9f@aol.com>
Date: Sat, 16 Nov 2002 12:30:07 EST
Subject: Re: [Ieprep] terminology
To: rja@extremenetworks.com, woody@pch.net
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_16.28640eb8.2b07da9f_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_16.28640eb8.2b07da9f_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/15/2002 8:48:39 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> In IETF, "requirement" means something that an implementer MUST implement
> and/or something that an operator MUST deploy.
> 


[MAP] If you believe this, exactly as you've stated, then we all have a very 
serious problem, and I can see why all the fuss. Henning pointed out very 
well, I think, that it is not that simple.

If it isn't clearly understood up front that no IETF "requirement" (as 
indicated by "MUST" in an RFC) actually places a requirement on an 
implementor or operator, then there is a major issue that must be addressed 
by the IAB before any progress can be made on anything important. As I 
believe you have been arguing, the only "requirements" are contractual: for 
an implementor, what the buyer of the equipment says they "must" have in 
order to be able to buy it. And for an operator, what their contract with the 
customer says that they "must" provide. (And, oh yes, in some environments, 
there may actually be government laws to mandate some things - like safety.)

I really can' t understand this continued argument that, just because 
something is written in an RFC, that every implementor and operator is 
required to support it. We must adopt a clear policy that all Proposed 
Standards are voluntary. (I presume it is already assumed.)

Scott, please clarify this. If I am wrong, then I guess that "MUST" can't be 
used anywhere in any document again

MIke Pierce
Artel



--part1_16.28640eb8.2b07da9f_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/15/2002 8:48:39 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">In IETF, "requirement" means something that an implementer MUST implement
<BR>and/or something that an operator MUST deploy.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] If you believe this, exactly as you've stated, then we all have a very serious problem, and I can see why all the fuss. Henning pointed out very well, I think, that it is not that simple.
<BR>
<BR>If it isn't clearly understood up front that no IETF "requirement" (as indicated by "MUST" in an RFC) actually places a requirement on an implementor or operator, then there is a major issue that must be addressed by the IAB before any progress can be made on anything important. As I believe you have been arguing, the only "requirements" are contractual: for an implementor, what the buyer of the equipment says they "must" have in order to be able to buy it. And for an operator, what their contract with the customer says that they "must" provide. (And, oh yes, in some environments, there may actually be government laws to mandate some things - like safety.)
<BR>
<BR>I really can' t understand this continued argument that, just because something is written in an RFC, that every implementor and operator is required to support it. We must adopt a clear policy that all Proposed Standards are voluntary. (I presume it is already assumed.)
<BR>
<BR>Scott, please clarify this. If I am wrong, then I guess that "MUST" can't be used anywhere in any document again
<BR>
<BR>MIke Pierce
<BR>Artel
<BR>
<BR></FONT></HTML>

--part1_16.28640eb8.2b07da9f_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 12:34:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21274
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 12:34:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGHakr17788
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 12:36:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGHakv17785
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 12:36:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21253
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 12:34:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGHV7v17639;
	Sat, 16 Nov 2002 12:31:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGHUbv17564
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 12:30:37 -0500
Received: from imo-m09.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21148
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 12:27:57 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m09.mx.aol.com (mail_out_v34.13.) id j.9c.2978ea38 (3932);
	Sat, 16 Nov 2002 12:30:28 -0500 (EST)
Message-ID: <9c.2978ea38.2b07dab4@aol.com>
Date: Sat, 16 Nov 2002 12:30:28 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_9c.2978ea38.2b07dab4_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_9c.2978ea38.2b07dab4_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/15/2002 8:57:41 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> Several ISPs that deployed "prioritisation" and/or "QoS" found that:
>     (1) priority packets got worse treatment than best-effort packets,
>         particularly in times of network stress
>     (2) deployment costs were intolerably high (i.e. money needed to deploy
>         was non-trivially high).
>     (3) deployment was not feasible in a large-scale commercial backbone
>     (4) operations costs (e.g. debugging) were insanely high
>     (5) much of the currently deployed equipment did not behave very well
>         when lots of features (especially QoS) were enabled.  To be fair,
>         some equipment is robust when features are turned on.  The latter
>           equipment generally has a hardware-based (e.g. ASIC, FPGA) 
> implementation
>           of the enabled features.
> 


What particular "prioritisation and/or QoS" schemes are you referring to? Are 
you talking about DiffServ AF with multiple drop precednences, or something 
else? Yes, I'm sure that some are really bad, a conclusion I came to the 
first time I studied them.

Mike Pierce
Artel


--part1_9c.2978ea38.2b07dab4_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/15/2002 8:57:41 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Several ISPs that deployed "prioritisation" and/or "QoS" found that:
<BR> &nbsp;&nbsp;&nbsp;(1) priority packets got worse treatment than best-effort packets,
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;particularly in times of network stress
<BR> &nbsp;&nbsp;&nbsp;(2) deployment costs were intolerably high (i.e. money needed to deploy
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;was non-trivially high).
<BR> &nbsp;&nbsp;&nbsp;(3) deployment was not feasible in a large-scale commercial backbone
<BR> &nbsp;&nbsp;&nbsp;(4) operations costs (e.g. debugging) were insanely high
<BR> &nbsp;&nbsp;&nbsp;(5) much of the currently deployed equipment did not behave very well
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;when lots of features (especially QoS) were enabled. &nbsp;To be fair,
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;some equipment is robust when features are turned on. &nbsp;The latter
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;equipment generally has a hardware-based (e.g. ASIC, FPGA) 
<BR>implementation
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;of the enabled features.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>What particular "prioritisation and/or QoS" schemes are you referring to? Are you talking about DiffServ AF with multiple drop precednences, or something else? Yes, I'm sure that some are really bad, a conclusion I came to the first time I studied them.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_9c.2978ea38.2b07dab4_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 13:29:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21977
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 13:29:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGIVEL20237
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 13:31:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGIVEv20234
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 13:31:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21970
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 13:28:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGIUEv20133;
	Sat, 16 Nov 2002 13:30:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGIT4v20070
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 13:29:04 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21932
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 13:26:23 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 851BE67103; Sat, 16 Nov 2002 09:51:27 -0500 (EST)
Date: Sat, 16 Nov 2002 13:28:52 -0500
Subject: Re: [Ieprep] terminology
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <16.28640eb8.2b07da9f@aol.com>
Message-Id: <41E99766-F991-11D6-A2AE-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 16, 2002, at 12:30 America/Montreal, Mpierce1@aol.com 
wrote:
> If it isn't clearly understood up front that no IETF "requirement" (as 
> indicated by "MUST" in an RFC) actually places a requirement on an 
> implementor or operator, then there is a major issue that must be 
> addressed by the IAB before any progress can be made on anything 
> important.

Two points:
	- IAB has virtually no role in the IETF standards process.  See 
RFC-2026.
	- You likely mean the IETF community when you talk about changing 
things,
		since our processes are pretty much all bottom-up.

And that is definitely NOT "clearly understood up front".  It is 
particularly
NOT understood when USG officials visit ISPs and tell them that the USG 
plans
to mandate deployment of the forthcoming IEprep standards from IETF (and
that HAS happened to more than one US ISP according to what the ISPs 
tell me).

> As I believe you have been arguing, the only "requirements" are 
> contractual: for an implementor, what the buyer of the equipment says 
> they "must" have in order to be able to buy it. And for an operator, 
> what their contract with the customer says that they "must" provide. 
> (And, oh yes, in some environments, there may actually be government 
> laws to mandate some things - like safety.)

I've been trying to say that what you all keep erroneously calling 
"requirements"
are in fact contractual objectives of you all.  If you all could switch 
to other
words than "requirement" it would lower the temperature of this 
conversation
VERY considerably.

> I really can' t understand this continued argument that, just because 
> something is written in an RFC, that every implementor and operator is 
> required to support it. We must adopt a clear policy that all Proposed 
> Standards are voluntary. (I presume it is already assumed.)

Actually, we still have mandatory specs and elective specs on the IETF 
standards-track.
This won't be changing anytime soon.  Further, IETF standards need to 
apply to
*all* places on the globe.  So even an optional spec ought only talk in 
terms of
global requirements (e.g. Japan's IEprep does not include voice), not 
those belonging
to a subset of countries.

In the draft-carlberg-ets-* documents, a lot of effort was made to very 
clearly state
the very limited applicability of each draft.  That kind of effort 
needs to be
undertaken with all the documents -- and the conversations also need to 
use words
(such as "requirement", "MUST", "SHOULD", or "MAY") very thoughtfully.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 13:29:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21999
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 13:29:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGIVbj20255
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 13:31:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGIVbv20252
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 13:31:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21974
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 13:28:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGIV1v20193;
	Sat, 16 Nov 2002 13:31:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGIUEv20141
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 13:30:14 -0500
Received: from imo-r03.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21950
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 13:27:33 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r03.mx.aol.com (mail_out_v34.13.) id b.18.286aad14 (4560);
	Sat, 16 Nov 2002 13:29:39 -0500 (EST)
Message-ID: <18.286aad14.2b07e893@aol.com>
Date: Sat, 16 Nov 2002 13:29:39 EST
Subject: Re: [Ieprep] NCS contracts with voice IXCs
To: woody@pch.net, hgs@cs.columbia.edu
CC: joel@stevecrocker.com, Janet.Gunn@dyncorp.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_18.286aad14.2b07e893_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_18.286aad14.2b07e893_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/16/2002 11:23:20 AM Eastern Standard Time, 
woody@pch.net writes:


>       On Sat, 16 Nov 2002, Henning Schulzrinne wrote:
>     > there are at least three possible interpretations:
>     > (1) Voice IXCs mix voice and commodity Internet service
>     > (2) Voice IXCs run a logically separate network for voice
>     > (3) Voice IXCs run a completely separate network infrastructure
> 
> Each of which are possible, but then there's the common case, which will
> always outnumber all of those three put together, which is
> 
> (4) Voice IXCs don't do or know anything about data, since they ride
> several layers higher in the stack, and the underlying data is
> assumed to be present due to the customer's arrangement with an ISP.
> 


And I'll give you the answer (to why we haven't heard from the voice IXCs) I 
got from individuals from two large carriers currently in the "PSTN" world 
which naturally have a "voice IXC" function:

(5) They are not actively participating in this activity (IETF in general, 
and SIP in specific) because they believe that any meaningful, useful 
capability is so far off in the future that they don't see it as worthwhile 
to waste their time on it.

Mike Pierce
Artel
(speking personnally)

--part1_18.286aad14.2b07e893_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/16/2002 11:23:20 AM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;On Sat, 16 Nov 2002, Henning Schulzrinne wrote:
<BR> &nbsp;&nbsp;&nbsp;&gt; there are at least three possible interpretations:
<BR> &nbsp;&nbsp;&nbsp;&gt; (1) Voice IXCs mix voice and commodity Internet service
<BR> &nbsp;&nbsp;&nbsp;&gt; (2) Voice IXCs run a logically separate network for voice
<BR> &nbsp;&nbsp;&nbsp;&gt; (3) Voice IXCs run a completely separate network infrastructure
<BR>
<BR>Each of which are possible, but then there's the common case, which will
<BR>always outnumber all of those three put together, which is
<BR>
<BR>(4) Voice IXCs don't do or know anything about data, since they ride
<BR>several layers higher in the stack, and the underlying data is
<BR>assumed to be present due to the customer's arrangement with an ISP.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>And I'll give you the answer (to why we haven't heard from the voice IXCs) I got from individuals from two large carriers currently in the "PSTN" world which naturally have a "voice IXC" function:
<BR>
<BR>(5) They are not actively participating in this activity (IETF in general, and SIP in specific) because they believe that any meaningful, useful capability is so far off in the future that they don't see it as worthwhile to waste their time on it.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>(speking personnally)</FONT></HTML>

--part1_18.286aad14.2b07e893_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 13:32:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22063
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 13:32:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGIYgA20362
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 13:34:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGIYgv20359
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 13:34:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22060
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 13:32:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGIY2v20349;
	Sat, 16 Nov 2002 13:34:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGIXZv20322
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 13:33:35 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22046
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 13:30:54 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 86ECD67103; Sat, 16 Nov 2002 09:56:04 -0500 (EST)
Date: Sat, 16 Nov 2002 13:33:29 -0500
Subject: Re: [Ieprep] QoS in deployed IP networks
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <9c.2978ea38.2b07dab4@aol.com>
Message-Id: <E708AC70-F991-11D6-A2AE-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Saturday, Nov 16, 2002, at 12:30 America/Montreal, Mpierce1@aol.com 
wrote:
> What particular "prioritisation and/or QoS" schemes are you referring 
> to? Are you talking about DiffServ AF with multiple drop precednences, 
> or something else?

A wide range of them.  An incomplete list (off the top of my head) 
includes:
	Diffserv (with AF, EF, or some more experimental approaches)
	ATM
	RSVP/IntServ

Dave Meyer and other ISP folks should feel free to add to the above 
list.

Older DoD IP networks once upon a time had MLPP implemented per RFC-791 
IP ToS bits.
It worked well enough on that equipment (mostly Proteons or so I'm 
told),
iff one considered strict precedence with starvation to be the right 
policy.
It *did* regularly starve non-priority users, due to reliance on QoS 
rather than
provisioning enough bandwidth, which led to the priority creep that Rex 
Buddenburg
previously discussed.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 18:28:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26271
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 18:28:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAGNV7a01450
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 18:31:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGNV7v01447
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 18:31:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26266
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 18:28:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGNRJv01319;
	Sat, 16 Nov 2002 18:27:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAGNQHv01299
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 18:26:17 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26234
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 18:23:34 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18DCKI-00028C-00
	for ieprep@ietf.org; Sat, 16 Nov 2002 18:26:10 -0500
Date: Sat, 16 Nov 2002 18:26:10 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: ieprep@ietf.org
Subject: Re: [Ieprep] NCS contracts with voice IXCs
In-Reply-To: <18.286aad14.2b07e893@aol.com>
Message-ID: <Pine.GSO.4.44.0211161819120.8178-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Sat, 16 Nov 2002 Mpierce1@aol.com wrote:
> And I'll give you the answer (to why we haven't heard from the voice IXCs) I
> got from individuals from two large carriers currently in the "PSTN" world
> which naturally have a "voice IXC" function:
>
> (5) They are not actively participating in this activity (IETF in general,
> and SIP in specific) because they believe that any meaningful, useful
> capability is so far off in the future that they don't see it as worthwhile
> to waste their time on it.

TOKYO (Reuters) - Internet service provider (ISP) units of Japanese
electronics giant Sony Corp (news - web sites) and two other companies
said on Thursday they would jointly launch a trial operation for Internet
protocol (IP) phone service.

The two other firms are NTT Communications Corp, a wholly owned
long-distance unit of Nippon Telegraph and Telephone Corp, Japan's top
telecoms operator, and Nifty Corp, which is Fujitsu Ltd's ISP arm.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 16 22:37:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00728
	for <ieprep-archive@odin.ietf.org>; Sat, 16 Nov 2002 22:37:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAH3eED13634
	for ieprep-archive@odin.ietf.org; Sat, 16 Nov 2002 22:40:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAH3eEv13631
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 22:40:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00722
	for <ieprep-web-archive@ietf.org>; Sat, 16 Nov 2002 22:37:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAH3d4v13570;
	Sat, 16 Nov 2002 22:39:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAH3Zlv12921
	for <ieprep@optimus.ietf.org>; Sat, 16 Nov 2002 22:35:47 -0500
Received: from imo-d05.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00629
	for <ieprep@ietf.org>; Sat, 16 Nov 2002 22:33:01 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d05.mx.aol.com (mail_out_v34.13.) id b.93.264829b5 (4560);
	Sat, 16 Nov 2002 22:35:17 -0500 (EST)
Message-ID: <93.264829b5.2b086874@aol.com>
Date: Sat, 16 Nov 2002 22:35:16 EST
To: woody@pch.net
CC: rja@extremenetworks.com, choid@ncr.disa.mil, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_93.264829b5.2b086874_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Subject: [Ieprep] Re: Is QoS Dead?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_93.264829b5.2b086874_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/15/2002 3:08:03 PM Eastern Standard Time, woody@pch.net 
writes:


>       On Fri, 15 Nov 2002 Mpierce1@aol.com wrote:
>     > Am I understanding you to say that all attempts to improve the QoS of 
> IP is
>     > dead?  I'm confused.
> 
> You're confused because you're having trouble with language again.
> Specifically, you're making the same mistake that we've corrected twice
> before: you're conflating the word "quality" with the acronym "QoS".  The
> former is generally thought to mean a property of goodness, while the
> latter is an abbreviation of "Quality of Service," which is a proper noun
> denoting a collection of protocols and practices which have the intention
> of making some pigs more equal than others.
> 
> So, to clarify again:  In the Internet, we improved the quality of
> service by abolishing QoS.
> 
> See?  A tip: you can distinguish proper nouns because they're denoted by
> the use of _initial capitals_.  Boeing, Big Mac with Cheese, QoS, Mike;
> these are all proper nouns, tokens which designate a thing, rather than
> being parts of the language which carry intrinsic meaning.
> 
> Before you get carried away, though, remember that decapitalizing
> something isn't a useful trick, since it _changes the meaning of the thing
> drastically_, as in the case before us now.  The confusion which this
> engenders in proles is why, for instance, the word acme has been so
> frequently used in the names (which are proper nouns) of businesses.
> 


[MAP] Really, Bill, I for one, and I believe a large number on this list (if 
there are many left), are getting sick and tired of your sarcasm (or is it 
your attempt at humor, and I'm missing it?). We would rather see an honest 
attempt to address the issues.

I am well aware that there is different terminolgy used in different places. 
Unlike you, I don't claim that one group's terminology is right and the 
other's is wrong and should be ignored, and I am making a serious attempt to 
bridge the difference between the two backgrounds. The IETF can use "QoS" to 
mean "the collection of protocols and practices..." if it wants. Personnally, 
that doesn't seem like good use of English to me, and I suspect that this 
meaning is not universally used in the IETF either (see below).

On the other hand, there are other recognized, competent standards bodies in 
the world who use "QoS" differently. For example, the American National 
Standard T1.523, Telecom Glossary, defines Quality of Service (QOS)  as "1. 
The performance specification of a communications channel or system. 2. A 
subjective rating of telephone communications quality..."

I can show you numerous references in ITU-T Recommendations to the use of 
"Quality of Service" and "QoS" to refer to the performance requirements and 
parameters, not to the protocol or procedures used to achieve that 
performance. G.1000 (and several others) define "Quality of Service" as "The 
collective effect of service performances, which determines the degree of 
satisfaction of a user of the service". (Not the best definition, in my 
opinion, but clearly not talking about the protocol.)

TIPHON document TR 101 329, General Aspects of Quality of Service, uses the 
term in the same way as ITU-T.

And I can cite others.

Please save your typing - I already know what your opinion is of other groups 
such as T1 and ITU-T, so you don't need to elaborate.

Concerning the use of "QoS" in the IETF, I agree that it seems to be often 
used as you indicated. Can you point to an actual definition in an RFC of 
"QoS" that I could use as a reference? I note that RFC 2216 contains the 
following definition:

"Quality of Service - In the context of this document, quality of service 
refers to the nature of the packet delivery service provided, as described by 
paramaters such as achieved bandwidth, packet delay, and packet loss rates." 
It then goes on to talk about "control of QoS parameters". I'm sure that I 
could find other RFCs that use "QoS" in this way, i.e., the same way that 
ITU-T and T1 and others use the term.

The bottom line is that none of us should be using a multi-defined term like 
"QoS" without carefully identifying the context, which is why I included the 
words "attempts to improve" in the above. If this isn't sufficient to clearly 
indicate my meaning, please tell me, but don't tell me I am "having trouble 
with langauge again."

Mike Pierce
Artel



--part1_93.264829b5.2b086874_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/15/2002 3:08:03 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;On Fri, 15 Nov 2002 Mpierce1@aol.com wrote:
<BR> &nbsp;&nbsp;&nbsp;&gt; Am I understanding you to say that all attempts to improve the QoS of IP is
<BR> &nbsp;&nbsp;&nbsp;&gt; dead? &nbsp;I'm confused.
<BR>
<BR>You're confused because you're having trouble with language again.
<BR>Specifically, you're making the same mistake that we've corrected twice
<BR>before: you're conflating the word "quality" with the acronym "QoS". &nbsp;The
<BR>former is generally thought to mean a property of goodness, while the
<BR>latter is an abbreviation of "Quality of Service," which is a proper noun
<BR>denoting a collection of protocols and practices which have the intention
<BR>of making some pigs more equal than others.
<BR>
<BR>So, to clarify again: &nbsp;In the Internet, we improved the quality of
<BR>service by abolishing QoS.
<BR>
<BR>See? &nbsp;A tip: you can distinguish proper nouns because they're denoted by
<BR>the use of _initial capitals_. &nbsp;Boeing, Big Mac with Cheese, QoS, Mike;
<BR>these are all proper nouns, tokens which designate a thing, rather than
<BR>being parts of the language which carry intrinsic meaning.
<BR>
<BR>Before you get carried away, though, remember that decapitalizing
<BR>something isn't a useful trick, since it _changes the meaning of the thing
<BR>drastically_, as in the case before us now. &nbsp;The confusion which this
<BR>engenders in proles is why, for instance, the word acme has been so
<BR>frequently used in the names (which are proper nouns) of businesses.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] Really, Bill, I for one, and I believe a large number on this list (if there are many left), are getting sick and tired of your sarcasm (or is it your attempt at humor, and I'm missing it?). We would rather see an honest attempt to address the issues.
<BR>
<BR>I am well aware that there is different terminolgy used in different places. Unlike you, I don't claim that one group's terminology is right and the other's is wrong and should be ignored, and I am making a serious attempt to bridge the difference between the two backgrounds. The IETF can use "QoS" to mean "the collection of protocols and practices..." if it wants. Personnally, that doesn't seem like good use of English to me, and I suspect that this meaning is not universally used in the IETF either (see below).
<BR>
<BR>On the other hand, there are other recognized, competent standards bodies in the world who use "QoS" differently. For example, the American National Standard T1.523, Telecom Glossary, defines Quality of Service (QOS) &nbsp;as "1. The performance specification of a communications channel or system. 2. A subjective rating of telephone communications quality..."
<BR>
<BR>I can show you numerous references in ITU-T Recommendations to the use of "Quality of Service" and "QoS" to refer to the performance requirements and parameters, not to the protocol or procedures used to achieve that performance. G.1000 (and several others) define "Quality of Service" as "The collective effect of service performances, which determines the degree of satisfaction of a user of the service". (Not the best definition, in my opinion, but clearly not talking about the protocol.)
<BR>
<BR>TIPHON document TR 101 329, General Aspects of Quality of Service, uses the term in the same way as ITU-T.
<BR>
<BR>And I can cite others.
<BR>
<BR>Please save your typing - I already know what your opinion is of other groups such as T1 and ITU-T, so you don't need to elaborate.
<BR>
<BR>Concerning the use of "QoS" in the IETF, I agree that it seems to be often used as you indicated. Can you point to an actual definition in an RFC of "QoS" that I could use as a reference? I note that RFC 2216 contains the following definition:
<BR>
<BR>"Quality of Service - In the context of this document, quality of service refers to the nature of the packet delivery service provided, as described by paramaters such as achieved bandwidth, packet delay, and packet loss rates." It then goes on to talk about "control of QoS parameters". I'm sure that I could find other RFCs that use "QoS" in this way, i.e., the same way that ITU-T and T1 and others use the term.
<BR>
<BR>The bottom line is that none of us should be using a multi-defined term like "QoS" without carefully identifying the context, which is why I included the words "attempts to improve" in the above. If this isn't sufficient to clearly indicate my meaning, please tell me, but don't tell me I am "having trouble with langauge again."
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR></FONT></HTML>

--part1_93.264829b5.2b086874_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 17 10:32:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19936
	for <ieprep-archive@odin.ietf.org>; Sun, 17 Nov 2002 10:32:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAHFYVV22458
	for ieprep-archive@odin.ietf.org; Sun, 17 Nov 2002 10:34:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHFYUv22455
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 17 Nov 2002 10:34:30 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19929
	for <ieprep-web-archive@ietf.org>; Sun, 17 Nov 2002 10:31:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHFXWv22390;
	Sun, 17 Nov 2002 10:33:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHFWCv22311
	for <ieprep@optimus.ietf.org>; Sun, 17 Nov 2002 10:32:12 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19875
	for <ieprep@ietf.org>; Sun, 17 Nov 2002 10:29:32 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 63F937A0A; Sun, 17 Nov 2002 07:32:07 -0800 (PST)
Date: Sun, 17 Nov 2002 10:32:08 -0500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <93.264829b5.2b086874@aol.com>
Message-Id: <BBB13EEB-FA41-11D6-A9CE-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAHFWCv22312
Subject: [Ieprep] Re: Is QoS Dead?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


On Saturday, Nov 16, 2002, at 22:35 America/Montreal, Mpierce1@aol.com 
wrote:
> On the other hand, there are other recognized, competent standards 
> bodies in the world who use "QoS" differently. For example, the 
> American National Standard T1.523, Telecom Glossary, defines Quality 
> of Service (QOS)  as "1. The performance specification of a 
> communications channel or system. 2. A subjective rating of telephone 
> communications quality..."

IETF aggressively questions the competence of ITU and ANSI on the topic 
of the Internet,
and quite regularly does so.

If one wants to play in an IETF forum, one needs to follow IETF 
terminology.
Fair play, if one wants to play over in ITU, then one needs to use 
their terminology
while over there.

> I can show you numerous references in ITU-T Recommendations

All of which are irrelevant, because this is IETF, not ITU.

> TIPHON document TR 101 329, General Aspects of Quality of Service, 
> uses the term in the same way as ITU-T.

And those are equally irrelevant, because this is IETF, not ETSI.

If folks here would use clear language, the list would be more 
successful
in communicating with each other.  "QoS" refers to a mechanism.  
"Service
Quality" refers to whether the provided service is good, bad, or 
sideways.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 17 14:58:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24269
	for <ieprep-archive@odin.ietf.org>; Sun, 17 Nov 2002 14:58:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAHK0xZ01467
	for ieprep-archive@odin.ietf.org; Sun, 17 Nov 2002 15:00:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHK0xv01464
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 17 Nov 2002 15:00:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24266
	for <ieprep-web-archive@ietf.org>; Sun, 17 Nov 2002 14:58:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHK06v01444;
	Sun, 17 Nov 2002 15:00:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHJthv01314
	for <ieprep@optimus.ietf.org>; Sun, 17 Nov 2002 14:55:43 -0500
Received: from imo-m06.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24228
	for <ieprep@ietf.org>; Sun, 17 Nov 2002 14:53:01 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m06.mx.aol.com (mail_out_v34.13.) id j.152.178efc90 (3699);
	Sun, 17 Nov 2002 14:53:18 -0500 (EST)
Message-ID: <152.178efc90.2b094dae@aol.com>
Date: Sun, 17 Nov 2002 14:53:18 EST
Subject: Re: [Ieprep] access links 
To: rja@extremenetworks.com, nguyena@ncs.gov
CC: KIMBERLY.S.KING@saic.com, idb@tazznetworks.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_152.178efc90.2b094dae_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_152.178efc90.2b094dae_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/14/2002 7:32:23 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> Is NCS proposing to require that cable modem
> end users buy more capacity so that in an emergency, the police could
> use VoIP over the cable modem system ?
> 


[MAP] NCS (and the DoD) are certainly not proposing this. In fact, it seems 
to me that several of the opponents of doing anything in IEPREP are arguing 
something along the lines of "Just make sure you have plenty of excess 
bandwidth before an emergency occurs."

The whole point from the beginning for both NCS and DoD was to define ways to 
deal with the situation in which there is not enough bandwidth, but some 
continue to argue that this is not the purpose of this effort and that, in 
fact, this situation can never occur.

It certainly appears to me that the most important things to agree on at this 
week's meeting, are that:

1. Congestion can sometimes occur in some places
2. IEPREP (and then other WGs) are tasked to try to figure out how to deal 
with it.

Mike Pierce
Artel, under contract to support DISA



--part1_152.178efc90.2b094dae_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/14/2002 7:32:23 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Is NCS proposing to require that cable modem
<BR>end users buy more capacity so that in an emergency, the police could
<BR>use VoIP over the cable modem system ?
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>[MAP] NCS (and the DoD) are certainly not proposing this. In fact, it seems to me that several of the opponents of doing anything in IEPREP are arguing something along the lines of "Just make sure you have plenty of excess bandwidth before an emergency occurs."
<BR>
<BR>The whole point from the beginning for both NCS and DoD was to define ways to deal with the situation in which there is not enough bandwidth, but some continue to argue that this is not the purpose of this effort and that, in fact, this situation can never occur.
<BR>
<BR>It certainly appears to me that the most important things to agree on at this week's meeting, are that:
<BR>
<BR>1. Congestion can sometimes occur in some places
<BR>2. IEPREP (and then other WGs) are tasked to try to figure out how to deal with it.
<BR>
<BR>Mike Pierce
<BR>Artel, under contract to support DISA
<BR>
<BR></FONT></HTML>

--part1_152.178efc90.2b094dae_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 17 16:29:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25768
	for <ieprep-archive@odin.ietf.org>; Sun, 17 Nov 2002 16:29:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAHLW5u05329
	for ieprep-archive@odin.ietf.org; Sun, 17 Nov 2002 16:32:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHLW5v05326
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 17 Nov 2002 16:32:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25747
	for <ieprep-web-archive@ietf.org>; Sun, 17 Nov 2002 16:29:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHLV4v05260;
	Sun, 17 Nov 2002 16:31:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHLUrv05221
	for <ieprep@optimus.ietf.org>; Sun, 17 Nov 2002 16:30:53 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25717
	for <ieprep@ietf.org>; Sun, 17 Nov 2002 16:28:09 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by gnat.inet.org (Postfix) with ESMTP
	id 7E3C267103; Sun, 17 Nov 2002 12:53:09 -0500 (EST)
Date: Sun, 17 Nov 2002 16:30:22 -0500
Subject: Re: [Ieprep] access links 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <152.178efc90.2b094dae@aol.com>
Message-Id: <C707BE36-FA73-11D6-B90D-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Sunday, Nov 17, 2002, at 14:53 America/Montreal, Mpierce1@aol.com 
wrote:
> It certainly appears to me that the most important things to agree on
> at this week's meeting, are that:
>
> 1. Congestion can sometimes occur in some places

I think there is broad agreement that congestion can occur on access 
links
(e.g. end user's T1/E1 to their ISP).

> 2. IEPREP (and then other WGs) are tasked to try to figure out how to 
> deal with it.

Operators generally think the fix for access link congestion, where it 
occurs,
does not need to involve any IETF standards, existing or new.

Sprint's new CoS service offering uses vendor-proprietary mechanisms
inside the pair of routers on the access link -- and is an existence
proof that IETF standards aren't needed to address access link issues.
(For more on Sprint's CoS product, please see Sean Donelan's email,
which included a URL for how the service is configured, including
configuration file fragments).

I'd like to add some other things to agree on at this meeting:

(3) Congestion is not a problem within ISPs, even during natural 
disasters
(e.g. Kobe earthquake, Northridge earthquake) or terrorist attacks 
(e.g. 9/11/01).
Instead, congestion is a concern focused on access links.

(4) No amount of money (or mandate) applied to ISPs can fully resolve 
the
access link congestion issues, because the access link is controlled
by the end-user, rather than being controlled unilaterally by the ISP.

(5) QoS deployment creates new vulnerabilities for the ISPs that deploy 
QoS.

Ran
rja@extremenetworks.com


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 17 16:35:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25907
	for <ieprep-archive@odin.ietf.org>; Sun, 17 Nov 2002 16:35:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAHLbEj05912
	for ieprep-archive@odin.ietf.org; Sun, 17 Nov 2002 16:37:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHLbEv05901
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 17 Nov 2002 16:37:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25884
	for <ieprep-web-archive@ietf.org>; Sun, 17 Nov 2002 16:34:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHLa2v05510;
	Sun, 17 Nov 2002 16:36:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAHLZ4v05452
	for <ieprep@optimus.ietf.org>; Sun, 17 Nov 2002 16:35:04 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25853
	for <ieprep@ietf.org>; Sun, 17 Nov 2002 16:32:20 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAHLZnOE028175;
	Sun, 17 Nov 2002 13:35:49 -0800
Date: Sun, 17 Nov 2002 13:35:49 -0800
From: David Meyer <dmm@sprint.net>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: Mpierce1@aol.com, ieprep@ietf.org
Subject: Re: [Ieprep] access links
Message-ID: <20021117133549.A28165@sprint.net>
References: <152.178efc90.2b094dae@aol.com> <C707BE36-FA73-11D6-B90D-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <C707BE36-FA73-11D6-B90D-00039357A82A@extremenetworks.com>; from rja@extremenetworks.com on Sun, Nov 17, 2002 at 04:30:22PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Sorry, just catching up (I just got in):

>> Sprint's new CoS service offering uses vendor-proprietary mechanisms
>> inside the pair of routers on the access link -- and is an existence
>> proof that IETF standards aren't needed to address access link issues.
>> (For more on Sprint's CoS product, please see Sean Donelan's email,
>> which included a URL for how the service is configured, including
>> configuration file fragments).

This is true.

>> I'd like to add some other things to agree on at this meeting:
>> 
>> (3) Congestion is not a problem within ISPs, even during natural 
>> disasters
>> (e.g. Kobe earthquake, Northridge earthquake) or terrorist attacks 
>> (e.g. 9/11/01).
>> Instead, congestion is a concern focused on access links.

Correct.

>> (4) No amount of money (or mandate) applied to ISPs can fully resolve 
>> the
>> access link congestion issues, because the access link is controlled
>> by the end-user, rather than being controlled unilaterally by the ISP.

This is true as well, but it's worse. Some congestion is a
designed business decision (consider peering).

>> (5) QoS deployment creates new vulnerabilities for the ISPs that deploy 
>> QoS.

Huge.

Dave

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 18 09:47:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22302
	for <ieprep-archive@odin.ietf.org>; Mon, 18 Nov 2002 09:47:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAIEnAd28461
	for ieprep-archive@odin.ietf.org; Mon, 18 Nov 2002 09:49:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIEnAv28458
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 18 Nov 2002 09:49:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22291
	for <ieprep-web-archive@ietf.org>; Mon, 18 Nov 2002 09:46:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIEmHv28401;
	Mon, 18 Nov 2002 09:48:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIElWv28354
	for <ieprep@optimus.ietf.org>; Mon, 18 Nov 2002 09:47:32 -0500
Received: from imo-d03.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22256
	for <ieprep@ietf.org>; Mon, 18 Nov 2002 09:44:52 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d03.mx.aol.com (mail_out_v34.13.) id j.3e.27bf2559 (30960);
	Mon, 18 Nov 2002 09:47:27 -0500 (EST)
Message-ID: <3e.27bf2559.2b0a577f@aol.com>
Date: Mon, 18 Nov 2002 09:47:27 EST
To: rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_3e.27bf2559.2b0a577f_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 10500
Subject: [Ieprep] Re: Is QoS Dead?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_3e.27bf2559.2b0a577f_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/17/2002 10:32:31 AM Eastern Standard Time, 
rja@extremenetworks.com writes:

> 
> All of which are irrelevant, because this is IETF, not ITU.
> 


> And those are equally irrelevant, because this is IETF, not ETSI.
> 
> If folks here would use clear language, the list would be more successful
> in communicating with each other.  "QoS" refers to a mechanism.  "Service
> Quality" refers to whether the provided service is good, bad, or sideways.
> 
> 

[MAP] Thanks for reconfirming to me and the group that you have no intention 
of trying to cooperate with other "recognized" standards bodies. (I already 
knew that you do not "recognize" them.)

You didn't comment on my quote from an IETF RFC that also appears to use the 
term "Quality of Service" the same way as ITU-T does. I'm certain I can find 
lots of other IETF documents that are also consistent with the ITU-T 
definition of the term. So there may be a terminology conflict within the 
IETF itself. Do we need to try to fix or change this?

Mike Pierce
Artel





--part1_3e.27bf2559.2b0a577f_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/17/2002 10:32:31 AM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<BR>All of which are irrelevant, because this is IETF, not ITU.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">And those are equally irrelevant, because this is IETF, not ETSI.
<BR>
<BR>If folks here would use clear language, the list would be more successful
<BR>in communicating with each other. &nbsp;"QoS" refers to a mechanism. &nbsp;"Service
<BR>Quality" refers to whether the provided service is good, bad, or sideways.
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>[MAP] Thanks for reconfirming to me and the group that you have no intention of trying to cooperate with other "recognized" standards bodies. (I already knew that you do not "recognize" them.)
<BR>
<BR>You didn't comment on my quote from an IETF RFC that also appears to use the term "Quality of Service" the same way as ITU-T does. I'm certain I can find lots of other IETF documents that are also consistent with the ITU-T definition of the term. So there may be a terminology conflict within the IETF itself. Do we need to try to fix or change this?
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR>
<BR>
<BR></FONT></HTML>

--part1_3e.27bf2559.2b0a577f_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 18 09:47:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22318
	for <ieprep-archive@odin.ietf.org>; Mon, 18 Nov 2002 09:47:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAIEnbC28494
	for ieprep-archive@odin.ietf.org; Mon, 18 Nov 2002 09:49:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIEnbv28491
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 18 Nov 2002 09:49:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22299
	for <ieprep-web-archive@ietf.org>; Mon, 18 Nov 2002 09:46:57 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIEn0v28443;
	Mon, 18 Nov 2002 09:49:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIEmUv28421
	for <ieprep@optimus.ietf.org>; Mon, 18 Nov 2002 09:48:30 -0500
Received: from imo-r02.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22286
	for <ieprep@ietf.org>; Mon, 18 Nov 2002 09:45:50 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r02.mx.aol.com (mail_out_v34.13.) id j.16b.1741aa6b (30960);
	Mon, 18 Nov 2002 09:48:12 -0500 (EST)
Message-ID: <16b.1741aa6b.2b0a57ac@aol.com>
Date: Mon, 18 Nov 2002 09:48:12 EST
Subject: Re: [Ieprep] access links 
To: rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_16b.1741aa6b.2b0a57ac_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 10500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_16b.1741aa6b.2b0a57ac_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/17/2002 4:31:40 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> I'd like to add some other things to agree on at this meeting:
> 
> (3) Congestion is not a problem within ISPs, even during natural disasters
> (e.g. Kobe earthquake, Northridge earthquake) or terrorist attacks (e.g. 
> 9/11/01).
> Instead, congestion is a concern focused on access links.
> 
> (4) No amount of money (or mandate) applied to ISPs can fully resolve the
> access link congestion issues, because the access link is controlled
> by the end-user, rather than being controlled unilaterally by the ISP.
> 
> (5) QoS deployment creates new vulnerabilities for the ISPs that deploy QoS.
> 

:
[MAP] Comments on above:

(3) I fail to see how this group, or anyone, could "agree" that absolutely no 
ISP currently or ever in the near future has or will have a problem with 
congestion.

(4) I don't think the issue here is whether or not an ISP can "control" the 
access link, and therefore, the congestion. The issue is whether or not we 
need standards to allow anyone to control it.

(5) Absolutely true, so it needs to be taken into account, but we don't 
refuse to do work just because it "creates new vulnerabilities". If we did, 
there would certainly be no Internet.

Mike Pierce
Artel


--part1_16b.1741aa6b.2b0a57ac_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/17/2002 4:31:40 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">I'd like to add some other things to agree on at this meeting:
<BR>
<BR>(3) Congestion is not a problem within ISPs, even during natural disasters
<BR>(e.g. Kobe earthquake, Northridge earthquake) or terrorist attacks (e.g. 9/11/01).
<BR>Instead, congestion is a concern focused on access links.
<BR>
<BR>(4) No amount of money (or mandate) applied to ISPs can fully resolve the
<BR>access link congestion issues, because the access link is controlled
<BR>by the end-user, rather than being controlled unilaterally by the ISP.
<BR>
<BR>(5) QoS deployment creates new vulnerabilities for the ISPs that deploy QoS.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>:
<BR>[MAP] Comments on above:
<BR>
<BR>(3) I fail to see how this group, or anyone, could "agree" that absolutely no ISP currently or ever in the near future has or will have a problem with congestion.
<BR>
<BR>(4) I don't think the issue here is whether or not an ISP can "control" the access link, and therefore, the congestion. The issue is whether or not we need standards to allow anyone to control it.
<BR>
<BR>(5) Absolutely true, so it needs to be taken into account, but we don't refuse to do work just because it "creates new vulnerabilities". If we did, there would certainly be no Internet.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_16b.1741aa6b.2b0a57ac_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 18 17:26:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05951
	for <ieprep-archive@odin.ietf.org>; Mon, 18 Nov 2002 17:26:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAIMTBC24270
	for ieprep-archive@odin.ietf.org; Mon, 18 Nov 2002 17:29:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIMTBv24267
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 18 Nov 2002 17:29:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05943
	for <ieprep-web-archive@ietf.org>; Mon, 18 Nov 2002 17:26:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIMS9v24235;
	Mon, 18 Nov 2002 17:28:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIMRFv24207
	for <ieprep@optimus.ietf.org>; Mon, 18 Nov 2002 17:27:15 -0500
Received: from imo-m04.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05918
	for <ieprep@ietf.org>; Mon, 18 Nov 2002 17:24:31 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m04.mx.aol.com (mail_out_v34.13.) id j.c9.2bd6dbb0 (3842);
	Mon, 18 Nov 2002 17:26:48 -0500 (EST)
Message-ID: <c9.2bd6dbb0.2b0ac328@aol.com>
Date: Mon, 18 Nov 2002 17:26:48 EST
Subject: Re: [Ieprep] Atlanta ieprep Agenda
To: rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_c9.2bd6dbb0.2b0ac328_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 10500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_c9.2bd6dbb0.2b0ac328_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/14/2002 7:16:43 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> At @Home and at several other extant ISPs, it is the actual line 
> network engineers
> and network operations folks who are the ones participating in IETF.  
> 

Question for clarification. Since @home is extinct, not extant, is your 
reference to "several other ISPs" intended to refer to others that are also 
no longer in existance? How are their operations folks participating in the 
IETF if they no longer exist?

Mike Pierce
Artel


--part1_c9.2bd6dbb0.2b0ac328_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/14/2002 7:16:43 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">At @Home and at several other extant ISPs, it is the actual line 
<BR>network engineers
<BR>and network operations folks who are the ones participating in IETF. &nbsp;
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>Question for clarification. Since @home is extinct, not extant, is your reference to "several other ISPs" intended to refer to others that are also no longer in existance? How are their operations folks participating in the IETF if they no longer exist?
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_c9.2bd6dbb0.2b0ac328_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 18 20:02:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09372
	for <ieprep-archive@odin.ietf.org>; Mon, 18 Nov 2002 20:02:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJ14IY32395
	for ieprep-archive@odin.ietf.org; Mon, 18 Nov 2002 20:04:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ14Iv32392
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 18 Nov 2002 20:04:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09361
	for <ieprep-web-archive@ietf.org>; Mon, 18 Nov 2002 20:01:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ13Kv32355;
	Mon, 18 Nov 2002 20:03:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ12dv32333
	for <ieprep@optimus.ietf.org>; Mon, 18 Nov 2002 20:02:39 -0500
Received: from kc-msxproto4.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09319
	for <ieprep@ietf.org>; Mon, 18 Nov 2002 19:59:55 -0500 (EST)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 18 Nov 2002 19:02:31 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Date: Mon, 18 Nov 2002 19:02:31 -0600
Message-ID: <A29143A40AEAE3459FF829D1DD43316101D9B024@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Code-Red
Thread-Index: AcKPX/X9qdwciMa9RYWahiolQXKWRQ==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: <ieprep@ietf.org>
X-OriginalArrivalTime: 19 Nov 2002 01:02:31.0955 (UTC) FILETIME=[56BEE630:01C28F67]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAJ12dv32334
Subject: [Ieprep] Code-Red
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

During Ran's presentation, their was a question regarding 
effect of code-red on the Backbone. 


As for referencee, take a peek at the caida plots which shows
the no of infected hosts. 
http://www.caida.org/dynamic/analysis/security/code-red/

Points relevant to ieprep:

- code-red primarily preyed upon small business users rather
than large corporate networks.

- If you look at the geographical distribution of the 
attack/loss statistics, one can conclude that backbone
will sustain such large scale effects.

(Moore. D., Shannon. C., claffy. k., "Code-Red: a case study 
on the spread and victims of an Internet worm," IMW -2002.
  http://www.icir.org/vern/imw-2002/program.html)

- Code-red and other worms are a continuing mystery. It is 
hard to predict their traffic pattern, attack tree
or come up with a solution. Their is nothing that a IETF group 
can do.

- BGP stability was affected to some degree. But, due to its
dynamic nature, routes reconverges eventually (although its 
take some time which lead to some prefix miss.)

Thus said, code-red/NIMDA is a non-issue for ieprep as

   *  Solutions to avoid code-red is nill. So, nothing can be 
      done except for patching your kernels with some security 
      fixes (if you use a ISS server)

   * If you are thinking of using QoS to prioritize emergency
     traffic, it provides better chance for worms to target the
     high-priority traffic i.e.emergency traffic.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 18 20:14:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09561
	for <ieprep-archive@odin.ietf.org>; Mon, 18 Nov 2002 20:14:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJ1GsC00983
	for ieprep-archive@odin.ietf.org; Mon, 18 Nov 2002 20:16:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ1Gsv00980
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 18 Nov 2002 20:16:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09558
	for <ieprep-web-archive@ietf.org>; Mon, 18 Nov 2002 20:14:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ1G2v00947;
	Mon, 18 Nov 2002 20:16:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ1FMv00915
	for <ieprep@optimus.ietf.org>; Mon, 18 Nov 2002 20:15:22 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09552
	for <ieprep@ietf.org>; Mon, 18 Nov 2002 20:12:37 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAJ1G6sE003553;
	Mon, 18 Nov 2002 17:16:06 -0800
Date: Mon, 18 Nov 2002 17:16:06 -0800
From: David Meyer <dmm@sprint.net>
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
Cc: ieprep@ietf.org
Subject: Re: [Ieprep] Code-Red
Message-ID: <20021118171606.A3534@sprint.net>
References: <A29143A40AEAE3459FF829D1DD43316101D9B024@KC-MAIL2.kc.umkc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <A29143A40AEAE3459FF829D1DD43316101D9B024@KC-MAIL2.kc.umkc.edu>; from saq66@umkc.edu on Mon, Nov 18, 2002 at 07:02:31PM -0600
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>> Points relevant to ieprep:
>> 
>> - code-red primarily preyed upon small business users rather
>> than large corporate networks.
>> 
>> - If you look at the geographical distribution of the 
>> attack/loss statistics, one can conclude that backbone
>> will sustain such large scale effects.

Please explain how "one can conclude that backbone will sustain
such large scale effects" and what those effects might be.

>> - BGP stability was affected to some degree. But, due to its
>> dynamic nature, routes reconverges eventually (although its 
>> take some time which lead to some prefix miss.)
>> 

Please explain.

>> Thus said, code-red/NIMDA is a non-issue for ieprep as
>> 
>>    * If you are thinking of using QoS to prioritize emergency
>>      traffic, it provides better chance for worms to target the
>>      high-priority traffic i.e.emergency traffic.

Please explain how.


Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 02:05:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25201
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 02:05:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJ781d23034
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 02:08:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ781v23027
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 02:08:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24487
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 02:05:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ77Dv22250;
	Tue, 19 Nov 2002 02:07:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ762v21485
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 02:06:02 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21935
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 02:03:15 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18E2SG-0003gf-00
	for ieprep@ietf.org; Tue, 19 Nov 2002 02:05:52 -0500
Date: Tue, 19 Nov 2002 02:05:52 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: ieprep@ietf.org
In-Reply-To: <20021118171606.A3534@sprint.net>
Message-ID: <Pine.GSO.4.44.0211190152040.14121-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] Select Committee on Technology in Government
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


http://www.council.nyc.ny.us/pdf_files/reports/9_11techreport.pdf
   Perhaps the most significant technology lesson learned after 9/11 was
   the greater durability and usefulness of the Internet compared to the
   traditional telephone network. According to Brian Cohen, a Deputy
   Commissioner at DoITT, "We'd never thought we'd lose the phones. But
   when we lost the phones, we still had the Internet." IT became a whole
   new medium of communication.
[...]
   VoIP, wireless networks, text-messaging systems such as Blackberries,
   and the Internet in general offered cost-effective, relatively stable
   platforms for information dissemination, multi-directional
   communication, and command and control after 9/11  to the point where
   the Mayors Office has kept its VoIP network instead of returning to
   Verizons telephone network. Indeed, these systems should not only serve
   a more integral role in emergency response planning, but they should
   also be incorporated into ongoing agency  practice. In the case of
   VoIP, the city of Houston has already begun deploying the technology
   and expects to eventually convert all 25,000 municipal phones to
   VoIP.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 08:51:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05317
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 08:51:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJDrwi18449
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 08:53:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJDrwv18446
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 08:53:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05291
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 08:51:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJDqvv18380;
	Tue, 19 Nov 2002 08:52:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJDLUv16376
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 08:21:30 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04476
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 08:18:50 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by gnat.inet.org (Postfix) with ESMTP
	id 4DBBB67103; Tue, 19 Nov 2002 04:44:31 -0500 (EST)
Date: Tue, 19 Nov 2002 08:21:25 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <c9.2bd6dbb0.2b0ac328@aol.com>
Message-Id: <CDCF9F6F-FBC1-11D6-9DDE-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, Nov 18, 2002, at 17:26 America/Montreal, Mpierce1@aol.com 
wrote:
> Question for clarification. Since @home is extinct, not extant, is 
> your reference to "several other ISPs" intended to refer to others 
> that are also no longer in existance? How are their operations folks 
> participating in the IETF if they no longer exist?

And they have been actively participating in this WG also...

We could have had a mass presentation with a crowd standing at the 
front,
because folks WERE in the room, but the WG Chairs asked that instead 
there
be a single stuckee to take the pot shots from the audience.

I was drafted to take the incoming shells.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 12:08:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10076
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 12:08:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJHB7M31475
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 12:11:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHB7v31472
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 12:11:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10073
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 12:08:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHAGv31445;
	Tue, 19 Nov 2002 12:10:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJH5gv30576
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 12:05:42 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09952
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 12:02:59 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by gnat.inet.org (Postfix) with ESMTP id ACA2167103
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 08:28:43 -0500 (EST)
Date: Tue, 19 Nov 2002 12:05:36 -0500
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
From: RJ Atkinson <rja@extremenetworks.com>
To: ieprep <ieprep@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <11.28aeac3.2b0bbc64@aol.com>
Message-Id: <1F24B692-FBE1-11D6-8E90-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 19, 2002, at 11:10 America/Montreal, Mpierce1@aol.com 
wrote:
> When you referred to "several other ISPs", did you mean "several 
> others that still exist" (which is what I believe you meant)

Yes.

Maybe Dave Meyer and other operators on this list can clarify whether
they think the presentation is roughly accurate or substantially wrong
-- and if wrong, in which directions reality lies.

Ran



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 12:12:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10154
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 12:12:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJHEjh31603
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 12:14:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHEjv31600
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 12:14:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10134
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 12:12:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHE1v31567;
	Tue, 19 Nov 2002 12:14:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHDqv31548
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 12:13:52 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10117
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 12:11:09 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by gnat.inet.org (Postfix) with ESMTP
	id CE62D67103; Tue, 19 Nov 2002 08:36:53 -0500 (EST)
Date: Tue, 19 Nov 2002 12:13:46 -0500
Subject: Re: [Ieprep] Re: Is QoS Dead?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Fred Baker <fred@cisco.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <5.2.0.9.2.20021119063059.0238d7d0@mira-sjcm-4.cisco.com>
Message-Id: <4341F3E6-FBE2-11D6-8E90-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Fred,

	Did you see the Sprint results presented yesterday by Dave Meyer that,
among other things, noted that the backbone traffic is NOT self-similar
above <specified> speed ?  I didn't see you in the room, but maybe that
was an oversight on my part.  I believe his presentation is available 
online
(maybe he can post the URL here ?).

	My memory is not perfect, but I think <specified> was around OC-12
in his presentation.

	Deploying QoS *in the core* seems unlikely to fix issues that 
fundamentally
live in the access links.  And Dave's presentation also described 
specific
interesting/useful approaches to improving the properties of access 
links
-- and those approaches do NOT require any IETF standards work, RSVP, 
DiffServ,
or NSIS.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 12:22:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10368
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 12:22:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJHOno31999
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 12:24:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHOnv31996
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 12:24:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10333
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 12:22:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHO1v31964;
	Tue, 19 Nov 2002 12:24:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHKsv31807
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 12:20:54 -0500
Received: from sj-msg-core-4.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10263
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 12:18:10 -0500 (EST)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id gAJHKm5X000530;
	Tue, 19 Nov 2002 09:20:49 -0800 (PST)
Received: from FRED-W2K6.cisco.com (dhcp-128-107-163-90.cisco.com [128.107.163.90])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.2.0-GA)
	with ESMTP id ABO92657;
	Tue, 19 Nov 2002 09:20:27 -0800 (PST)
Message-Id: <5.2.0.9.2.20021119091623.0249c200@mira-sjcm-4.cisco.com>
X-Sender: fred@mira-sjcm-4.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 19 Nov 2002 09:20:45 -0800
To: RJ Atkinson <rja@extremenetworks.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] Re: Is QoS Dead?
Cc: ieprep <ieprep@ietf.org>
In-Reply-To: <4341F3E6-FBE2-11D6-8E90-00039357A82A@extremenetworks.com>
References: <5.2.0.9.2.20021119063059.0238d7d0@mira-sjcm-4.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

At 12:13 PM 11/19/2002 -0500, RJ Atkinson wrote:
>Deploying QoS *in the core* seems unlikely to fix issues that fundamentally
>live in the access links.

I'm at home (mostly) this week, for the first IETF meeting since Nov 1989, 
and at this instant writing from San Jose. No, I'll be interested to review 
his results.

I agree that the core is (at least mostly if not entirely) not at issue, as 
shown in the RIPE measurements etc; I do, however, refer you to Athina's 
paper and wonder what thoughts you might have.

My problem is that my traffic doesn't live only in the core - it goes end 
to end, through the cores of several networks, and through at least one 
access network that gives me fits. Telling me that the core has no problem 
doesn't convince me that my traffic will experience no problems. I can 
measure, and have given you pointers to graphic versions of those 
measurements, that this is simply untrue. 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 12:47:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11021
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 12:47:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJHniV01005
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 12:49:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHniv01002
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 12:49:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11011
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 12:47:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHn2v00986;
	Tue, 19 Nov 2002 12:49:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJHmCv00913
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 12:48:12 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10922
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 12:45:28 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by gnat.inet.org (Postfix) with ESMTP
	id 4563467103; Tue, 19 Nov 2002 09:11:11 -0500 (EST)
Date: Tue, 19 Nov 2002 12:48:03 -0500
Subject: Re: [Ieprep] Re: Is QoS Dead?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Fred Baker <fred@cisco.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <5.2.0.9.2.20021119091623.0249c200@mira-sjcm-4.cisco.com>
Message-Id: <0D2B4F8A-FBE7-11D6-8E90-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 19, 2002, at 12:20 America/Montreal, Fred Baker wrote:
> My problem is that my traffic doesn't live only in the core - it goes 
> end to end,
> through the cores of several networks, and through at least one access 
> network that
> gives me fits. Telling me that the core has no problem doesn't 
> convince me that
> my traffic will experience no problems. I can measure, and have given 
> you pointers
> to graphic versions of those measurements, that this is simply untrue.

It would be pleasant (and seems to be the case) if we can simply agree 
here
that the primary problem lives in the access links, and hence the 
access links
should be the focus of efforts to improve service quality.

It would also be pleasant if we could agree that some mechanisms 
already exist
(referring specifically to the Class-of-Service implementation that Dave
Meyer outlined yesterday; see also the note from Sean Donelan that has 
the
public URL at sprint.net with the details) that do not use existing 
IETF standards
or need new IETF standards work.

Ran
rja@extremenetworks.com

PS:	Entirely as an aside, the quality of DOCSIS cable modem 
implementations varies
significantly with regards to traffic shaping of packets (when either 
upstream
or downstream rate-limiting is in place).  At one time, a large 
operator systematically
tested these things and herded implementers to improve the quality of 
their
traffic shaping.  It is not clear to me whether anyone is 
systematically testing
this aspect of DOCSIS CMs these days.  My own cable modem, which has 
rate-limiting
similar to yours and is operating in an unfortunate upstream frequency 
range, seems
to behave a bit better than yours has been behaving.  This might be due 
to variance
in CM implementation or in CMTS implementation or other variables.

PPS:  DOCSIS specifications include support for a kind of link-layer 
QoS.  It is
likely that enabling/using that mechanism within that link type would 
be the most
successful approach to improving service quality on those kinds of 
links.  Note
that such link-layer QoS mechanisms don't require any IETF standards 
either.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 13:09:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11628
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 13:09:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJIC8D02860
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 13:12:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIC8v02857
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 13:12:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11612
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 13:09:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIBMv02604;
	Tue, 19 Nov 2002 13:11:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIA9v02552
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 13:10:09 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11470
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 13:07:25 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAJIAuwD016418;
	Tue, 19 Nov 2002 10:10:56 -0800
Date: Tue, 19 Nov 2002 10:10:56 -0800
From: David Meyer <dmm@sprint.net>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Atlanta ieprep Agenda
Message-ID: <20021119101056.B16401@sprint.net>
References: <11.28aeac3.2b0bbc64@aol.com> <1F24B692-FBE1-11D6-8E90-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1F24B692-FBE1-11D6-8E90-00039357A82A@extremenetworks.com>; from rja@extremenetworks.com on Tue, Nov 19, 2002 at 12:05:36PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

FTR, I was in agreement and had no problems with what Ran said.

Dave

On Tue, Nov 19, 2002 at 12:05:36PM -0500, RJ Atkinson wrote:
>> 
>> On Tuesday, Nov 19, 2002, at 11:10 America/Montreal, Mpierce1@aol.com 
>> wrote:
>> > When you referred to "several other ISPs", did you mean "several 
>> > others that still exist" (which is what I believe you meant)
>> 
>> Yes.
>> 
>> Maybe Dave Meyer and other operators on this list can clarify whether
>> they think the presentation is roughly accurate or substantially wrong
>> -- and if wrong, in which directions reality lies.
>> 
>> Ran
>> 
>> 
>> 
>> _______________________________________________
>> Ieprep mailing list
>> Ieprep@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 13:10:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11654
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 13:10:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJICgj02892
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 13:12:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJICgv02889
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 13:12:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11642
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 13:09:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIC2v02793;
	Tue, 19 Nov 2002 13:12:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIBgv02676
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 13:11:42 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11575
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 13:08:58 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAJIC8tg016430;
	Tue, 19 Nov 2002 10:12:08 -0800
Date: Tue, 19 Nov 2002 10:12:08 -0800
From: David Meyer <dmm@sprint.net>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: Fred Baker <fred@cisco.com>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: Is QoS Dead?
Message-ID: <20021119101208.C16401@sprint.net>
References: <5.2.0.9.2.20021119063059.0238d7d0@mira-sjcm-4.cisco.com> <4341F3E6-FBE2-11D6-8E90-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <4341F3E6-FBE2-11D6-8E90-00039357A82A@extremenetworks.com>; from rja@extremenetworks.com on Tue, Nov 19, 2002 at 12:13:46PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Tue, Nov 19, 2002 at 12:13:46PM -0500, RJ Atkinson wrote:
>> 
>> Fred,
>> 
>> 	Did you see the Sprint results presented yesterday by Dave Meyer that,
>> among other things, noted that the backbone traffic is NOT self-similar
>> above <specified> speed ?  I didn't see you in the room, but maybe that

It looks like above OC12 (so 48 and above)

>> was an oversight on my part.  I believe his presentation is available 
>> online
>> (maybe he can post the URL here ?).
>> 
http://www.maoz.com/~dmm/IETF55/ieprep

>> 	My memory is not perfect, but I think <specified> was around OC-12
>> in his presentation.

Yes.

Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 13:11:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11709
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 13:11:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJIDid03020
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 13:13:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIDiv03017
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 13:13:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11684
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 13:11:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJID1v03001;
	Tue, 19 Nov 2002 13:13:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJICXv02883
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 13:12:33 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11620
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 13:09:49 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Tue, 19 Nov 2002 13:12:07 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.1.19) with SMTP id M2002111913121627846
 ; Tue, 19 Nov 2002 13:12:16 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <XHBN1C76>; Tue, 19 Nov 2002 13:13:41 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E779A4@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'RJ Atkinson '" <rja@extremenetworks.com>,
        "'Fred Baker '" <fred@Cisco.com>
Cc: "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: Is QoS Dead?
Date: Tue, 19 Nov 2002 13:12:11 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Tuesday, Nov 19, 2002, at 12:20 America/Montreal, Fred Baker wrote:
> My problem is that my traffic doesn't live only in the core - it goes 
> end to end,
> through the cores of several networks, and through at least one access

> network that
> gives me fits. Telling me that the core has no problem doesn't 
> convince me that
> my traffic will experience no problems. I can measure, and have given 
> you pointers
> to graphic versions of those measurements, that this is simply untrue.

Ran said:
>It would be pleasant (and seems to be the case) if we can simply agree 
>here that the primary problem lives in the access links, and hence the 
>access links should be the focus of efforts to improve service quality.

It seems a reasonable place to start is at the end systems and on access
links.  I do not feel there is any dispute that congestion is potentially a
problem within the Internet but I also know the probably of ieprep solving
that problem end-to-end.  So, let's focus on the most typical bottlenecks
where we have a good chance of success.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 13:16:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11843
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 13:16:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJIIbE03306
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 13:18:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIIbv03303
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 13:18:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11804
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 13:15:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIHgv03206;
	Tue, 19 Nov 2002 13:17:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIDiv03032
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 13:13:44 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11692
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 13:11:02 -0500 (EST)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id gAJIDQsA016020;
	Tue, 19 Nov 2002 10:13:26 -0800 (PST)
Received: from FRED-W2K6.cisco.com (dhcp-171-71-250-95.cisco.com [171.71.250.95])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.2.0-GA)
	with ESMTP id ABO97009;
	Tue, 19 Nov 2002 10:13:18 -0800 (PST)
Message-Id: <5.2.0.9.2.20021119100510.03a3dc88@mira-sjcm-4.cisco.com>
X-Sender: fred@mira-sjcm-4.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 19 Nov 2002 10:11:37 -0800
To: RJ Atkinson <rja@extremenetworks.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] Re: Is QoS Dead?
Cc: ieprep <ieprep@ietf.org>
In-Reply-To: <0D2B4F8A-FBE7-11D6-8E90-00039357A82A@extremenetworks.com>
References: <5.2.0.9.2.20021119091623.0249c200@mira-sjcm-4.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

At 12:48 PM 11/19/2002 -0500, RJ Atkinson wrote:
>It would be pleasant (and seems to be the case) if we can simply agree 
>here that the primary problem lives in the access links, and hence the 
>access links should be the focus of efforts to improve service quality.

Within the United States, Australia, Western Europe, and parts of Asia, 
that is probably true. I was in Uganda last week... Bill Woodcock would be 
well qualified to discuss their networks, which use a bizarre mixture of 
tens of kilobits and unit gigabit links. Say VSAT, 802.11b, and so on.

>It would also be pleasant if we could agree that some mechanisms already 
>exist (referring specifically to the Class-of-Service implementation that 
>Dave Meyer outlined yesterday; see also the note from Sean Donelan that 
>has the public URL at sprint.net with the details) that do not use 
>existing IETF standards or need new IETF standards work.

If you're referring to DOCSIS, that's what I'm having to work around in 
Cox's network. Yes, link layer technologies exist that can change network 
behavior on those specific links; the change may be positive or negative, 
depending on to what purpose it is used, and is not end to end. If you want 
something end to end, I'm not prone to discuss link layer technologies. 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 13:16:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11858
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 13:16:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJIIiR03322
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 13:18:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIIiv03319
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 13:18:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11808
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 13:16:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIHhv03222;
	Tue, 19 Nov 2002 13:17:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIDjv03036
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 13:13:45 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11693
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 13:11:02 -0500 (EST)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id gAJIDQsC016020
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 10:13:26 -0800 (PST)
Received: from FRED-W2K6.cisco.com (dhcp-171-71-250-95.cisco.com [171.71.250.95])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.2.0-GA)
	with ESMTP id ABO97011;
	Tue, 19 Nov 2002 10:13:18 -0800 (PST)
Message-Id: <5.2.0.9.2.20021119101234.03a3f1c0@mira-sjcm-4.cisco.com>
X-Sender: fred@mira-sjcm-4.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 19 Nov 2002 10:13:33 -0800
To: ieprep@ietf.org
From: Fred Baker <fred@cisco.com>
Subject: Fwd: Re: [Ieprep] Re: Is QoS Dead?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

I have no idea how the ieprep list address got transmuted as it did. Ran's 
reply to me an hour or so ago was in response to this message.

>To: Bill Woodcock <woody@pch.net>
>From: Fred Baker <fred@cisco.com>
>Subject: Re: [Ieprep] Re: Is QoS Dead?
>Cc: Mpierce1@aol.com, rja@extremenetworks.com, <choid@ncr.disa.mil>, 
>Internet Emergency Preparedness Working Group <ieprep.ietf.org@cisco.com>
>Bcc:
>X-Eudora-Signature: <<No Default>>
>
>At 09:01 AM 11/15/2002 -0800, Bill Woodcock wrote:
>>So, to clarify again:  In the Internet, we improved the quality of 
>>service by abolishing QoS.
>
>Bill, maybe you should call my IP Phone Number (+1-408-526-4257) tomorrow 
>when I am at home, and have me randomly turn on and off the QoS settings 
>during the call while sending competing traffic. Cox Cable limits my input 
>to their network to 128 KBPS (I have a choice of two SLAs: 128/128, or 
>792/128; either has the same effect on what I input), and absent specific 
>work-arounds of their cable modem configuration it can be pretty bad. 
>Geoff Huston, author of the theory that "just increase the bandwidth" 
>fixes all problems, makes nasty remarks about my quality of service when I 
>do that. You can look at some ad hoc measurements in 
>ftp://ftpeng.cisco.com/fred/common/
>NCHC_2002.pdf, slides 4-8.
>
>
>It's true that in the core of the top 100-or-so ISP networks and many 
>Fortune 500 enterprises, 10:1 overprovisioning coupled with strict input 
>limiting in the access paths has reduced the issues in the core. I haven't 
>seen measurements that suggest that the end to end (eg, PC to PC) behavior 
>is as much improved; it simply doesn't have issues in the core. The thing 
>is (a) not all networks own their own fiber or consider 10:1 
>overprovisioning to be the solution of choice, and (b) not all end users 
>or enterprises have the option of 10:1 overprovisioning at any price.
>
>You might be interested to look up Athina Markopoulou's recent 
>measurements of the backbone on that score, however; I think she has a 
>pointer to her recent report on VoIP performance in the Internet Backbone 
>in http://www.stanford.edu/~amarko/projects.html. Bottom line, as ingress 
>to the backbone is limited in the access networks (creating quality issues 
>in the access), the backbone is perfectly stable. Open the access networks 
>up to higher bandwidth, and she measures fractal behavior in the backbone. 
>Surprise.
>
>At 04:36 AM 11/16/2002 -0800, Bill Woodcock wrote:
>>The question is whether it has ever worked in the real world, and the 
>>answer to that is no, it always falls apart under the weight of its own 
>>complexity when it hits the real world.
>
>At 06:53 PM 11/15/2002 -0500, Scott  Bradner wrote:
>>So for folks who missed the RSVP experiment, I should note that a major 
>>problem with RSVP was that it created too much state in routers along the 
>>path and depended too much on that state being present (even though the 
>>path changes dynamically with time).  This NSIS stuff is likely to hit 
>>the same wall at least as hard.
>
>Actually, I *was* there for that experiment, and consider both of these to 
>be something of an overstatement. RFC 2206 worried about that as an issue. 
>A person (whose name I have, but in this forum will remain nameless) at 
>BBN tested it, and couldn't be convinced that trying to run 1.544 MBPS of 
>reserved IP traffic over a 1.544 MBPS link that also had to carry the HDLC 
>framing around that traffic, T-1 framing, routing, and btw RSVP might be a 
>bad idea. An equally nameless-in-this-forum person (unless she chooses to 
>identify herself) at MCI tested it for the vBNS backbone, made thoughtful 
>remarks, and requested (and got) specific developments done for mating 
>RSVP sessions to individual ATM SVCs across her network. Neither could 
>justify asking their company to roll out a service based on it, as there 
>was little or no demand for toll quality VoIP or Video/IP in the backbone 
>in 1995-1996. Neither mentioned complexity or scaling factors as feeding 
>into her decision.
>
>Maybe you could point me to published or unpublished research that 
>establishes that the RFC 2206 concerns materialized in reality?
>
>
>Mike and I have our differences of opinion, but on this point he and I are 
>in the same camp. The level of sarcasm and misinformation being expressed 
>on this topic is inappropriate given the published data on the subject. 
>You can measure (RIPE measures) that jitter within and between ISPs is 
>very nominal. That doesn't make it so end to end, and the infinite 
>bandwidth option doesn't exist end to end. Until it does, we're going to 
>have to deal with applications with specific QoS requirements in places 
>that are not blessed with infinite bandwidth.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 13:16:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11871
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 13:16:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJIIkl03337
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 13:18:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIIkv03334
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 13:18:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11814
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 13:16:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJII2v03247;
	Tue, 19 Nov 2002 13:18:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJIEcv03088
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 13:14:38 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11726
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 13:11:56 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAJIFLCm016472;
	Tue, 19 Nov 2002 10:15:21 -0800
Date: Tue, 19 Nov 2002 10:15:21 -0800
From: David Meyer <dmm@sprint.net>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: Fred Baker <fred@cisco.com>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: Is QoS Dead?
Message-ID: <20021119101521.F16401@sprint.net>
References: <5.2.0.9.2.20021119091623.0249c200@mira-sjcm-4.cisco.com> <0D2B4F8A-FBE7-11D6-8E90-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <0D2B4F8A-FBE7-11D6-8E90-00039357A82A@extremenetworks.com>; from rja@extremenetworks.com on Tue, Nov 19, 2002 at 12:48:03PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Tue, Nov 19, 2002 at 12:48:03PM -0500, RJ Atkinson wrote:
>> 
>> On Tuesday, Nov 19, 2002, at 12:20 America/Montreal, Fred Baker wrote:
>> > My problem is that my traffic doesn't live only in the core - it goes 
>> > end to end,
>> > through the cores of several networks, and through at least one access 
>> > network that
>> > gives me fits. Telling me that the core has no problem doesn't 
>> > convince me that
>> > my traffic will experience no problems. I can measure, and have given 
>> > you pointers
>> > to graphic versions of those measurements, that this is simply untrue.
>> 
>> It would be pleasant (and seems to be the case) if we can simply agree 
>> here
>> that the primary problem lives in the access links, and hence the 
>> access links
>> should be the focus of efforts to improve service quality.

This is the way I (we) see it.

>> 
>> It would also be pleasant if we could agree that some mechanisms 
>> already exist
>> (referring specifically to the Class-of-Service implementation that Dave
>> Meyer outlined yesterday; see also the note from Sean Donelan that has 
>> the
>> public URL at sprint.net with the details) that do not use existing 
>> IETF standards
>> or need new IETF standards work.

http://www.sprintlink.net/policy/cos_guidelines.html

Dave


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 19 17:19:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18904
	for <ieprep-archive@odin.ietf.org>; Tue, 19 Nov 2002 17:19:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJMLTL19971
	for ieprep-archive@odin.ietf.org; Tue, 19 Nov 2002 17:21:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJMLTv19968
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 17:21:29 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18863
	for <ieprep-web-archive@ietf.org>; Tue, 19 Nov 2002 17:18:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJMKBv19903;
	Tue, 19 Nov 2002 17:20:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJMJ7v19818
	for <ieprep@optimus.ietf.org>; Tue, 19 Nov 2002 17:19:07 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18800
	for <ieprep@ietf.org>; Tue, 19 Nov 2002 17:16:21 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by gnat.inet.org (Postfix) with ESMTP
	id 9DC8F67103; Tue, 19 Nov 2002 13:42:07 -0500 (EST)
Date: Tue, 19 Nov 2002 17:18:57 -0500
Subject: Re: [Ieprep] Re: Is QoS Dead?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Fred Baker <fred@cisco.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <5.2.0.9.2.20021119100510.03a3dc88@mira-sjcm-4.cisco.com>
Message-Id: <E578AFE0-FC0C-11D6-8C27-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 19, 2002, at 13:11 America/Montreal, Fred Baker wrote:

> At 12:48 PM 11/19/2002 -0500, RJ Atkinson wrote:
>> It would also be pleasant if we could agree that some mechanisms 
>> already exist (referring specifically to the Class-of-Service 
>> implementation that Dave Meyer outlined yesterday; see also the note 
>> from Sean Donelan that has the public URL at sprint.net with the 
>> details) that do not use existing IETF standards or need new IETF 
>> standards work.
>
> If you're referring to DOCSIS, ...

No, I was referring to Sprint's CoS offering.  He just posted a URL for 
their
CoS offering in another email to this list.

I don't know whether Cox has enabled DOCSIS QoS (or even whether their 
deployed
CMTS and your cable modem support DOCSIS QoS).  My guess is that they 
have
not enabled DOCSIS QoS simply because it is a relatively new feature of 
DOCSIS.
Rate-limits were in DOCSIS 1.0.  QoS was not part of DOCSIS 1.0.  Most 
DOCSIS
deployed today seems to be based on 1.0, not 1.1 or 2.x.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 20 10:04:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21158
	for <ieprep-archive@odin.ietf.org>; Wed, 20 Nov 2002 10:04:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKF6YD19926
	for ieprep-archive@odin.ietf.org; Wed, 20 Nov 2002 10:06:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKF6Yv19923
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 10:06:34 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21142
	for <ieprep-web-archive@ietf.org>; Wed, 20 Nov 2002 10:03:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKF2Dv19660;
	Wed, 20 Nov 2002 10:02:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKF1Ov19624
	for <ieprep@optimus.ietf.org>; Wed, 20 Nov 2002 10:01:24 -0500
Received: from pfwhqs1.ncr.disa.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA20931
	for <ieprep@ietf.org>; Wed, 20 Nov 2002 09:58:42 -0500 (EST)
Received: from mtahqs3.ncr.disa.mil by pfwhqs1.ncr.disa.mil
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 20 Nov 2002 14:58:36 UT
Received: by mtahqs3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XGSM0AGF>; Wed, 20 Nov 2002 10:02:39 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D5A@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Fred Baker'" <fred@cisco.com>, ieprep@ietf.org
Subject: RE: Re: [Ieprep] Re: Is QoS Dead?
Date: Wed, 20 Nov 2002 10:01:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

I have been on travel and had quite a lot of email messages to go through. 
Anyway, is it fair to say that QoS problems exist between the endpoints and
edge nodes of the Internet(provided that the Internet backbone is perfectly
stable)? We all acknowledge them, but don't know how or want to solve them
because ,as some ops folks mentioned early on, RSVP and Diff-Serv are not
scalable.

Question: Do we have any standard that provides a QoS traffic mapping
mechanism between endpoints (i.e., 802.1q/q) and edge nodes (i.e., diff-serv
and mpls)? In order to have end-to-end QoS, we need to have such a
mechanism.

An


-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Tuesday, November 19, 2002 1:14 PM
To: ieprep@ietf.org
Subject: Fwd: Re: [Ieprep] Re: Is QoS Dead?


I have no idea how the ieprep list address got transmuted as it did. Ran's 
reply to me an hour or so ago was in response to this message.

>To: Bill Woodcock <woody@pch.net>
>From: Fred Baker <fred@cisco.com>
>Subject: Re: [Ieprep] Re: Is QoS Dead?
>Cc: Mpierce1@aol.com, rja@extremenetworks.com, <choid@ncr.disa.mil>, 
>Internet Emergency Preparedness Working Group <ieprep.ietf.org@cisco.com>
>Bcc:
>X-Eudora-Signature: <<No Default>>
>
>At 09:01 AM 11/15/2002 -0800, Bill Woodcock wrote:
>>So, to clarify again:  In the Internet, we improved the quality of 
>>service by abolishing QoS.
>
>Bill, maybe you should call my IP Phone Number (+1-408-526-4257) tomorrow 
>when I am at home, and have me randomly turn on and off the QoS settings 
>during the call while sending competing traffic. Cox Cable limits my input 
>to their network to 128 KBPS (I have a choice of two SLAs: 128/128, or 
>792/128; either has the same effect on what I input), and absent specific 
>work-arounds of their cable modem configuration it can be pretty bad. 
>Geoff Huston, author of the theory that "just increase the bandwidth" 
>fixes all problems, makes nasty remarks about my quality of service when I 
>do that. You can look at some ad hoc measurements in 
>ftp://ftpeng.cisco.com/fred/common/
>NCHC_2002.pdf, slides 4-8.
>
>
>It's true that in the core of the top 100-or-so ISP networks and many 
>Fortune 500 enterprises, 10:1 overprovisioning coupled with strict input 
>limiting in the access paths has reduced the issues in the core. I haven't 
>seen measurements that suggest that the end to end (eg, PC to PC) behavior 
>is as much improved; it simply doesn't have issues in the core. The thing 
>is (a) not all networks own their own fiber or consider 10:1 
>overprovisioning to be the solution of choice, and (b) not all end users 
>or enterprises have the option of 10:1 overprovisioning at any price.
>
>You might be interested to look up Athina Markopoulou's recent 
>measurements of the backbone on that score, however; I think she has a 
>pointer to her recent report on VoIP performance in the Internet Backbone 
>in http://www.stanford.edu/~amarko/projects.html. Bottom line, as ingress 
>to the backbone is limited in the access networks (creating quality issues 
>in the access), the backbone is perfectly stable. Open the access networks 
>up to higher bandwidth, and she measures fractal behavior in the backbone. 
>Surprise.
>
>At 04:36 AM 11/16/2002 -0800, Bill Woodcock wrote:
>>The question is whether it has ever worked in the real world, and the 
>>answer to that is no, it always falls apart under the weight of its own 
>>complexity when it hits the real world.
>
>At 06:53 PM 11/15/2002 -0500, Scott  Bradner wrote:
>>So for folks who missed the RSVP experiment, I should note that a major 
>>problem with RSVP was that it created too much state in routers along the 
>>path and depended too much on that state being present (even though the 
>>path changes dynamically with time).  This NSIS stuff is likely to hit 
>>the same wall at least as hard.
>
>Actually, I *was* there for that experiment, and consider both of these to 
>be something of an overstatement. RFC 2206 worried about that as an issue. 
>A person (whose name I have, but in this forum will remain nameless) at 
>BBN tested it, and couldn't be convinced that trying to run 1.544 MBPS of 
>reserved IP traffic over a 1.544 MBPS link that also had to carry the HDLC 
>framing around that traffic, T-1 framing, routing, and btw RSVP might be a 
>bad idea. An equally nameless-in-this-forum person (unless she chooses to 
>identify herself) at MCI tested it for the vBNS backbone, made thoughtful 
>remarks, and requested (and got) specific developments done for mating 
>RSVP sessions to individual ATM SVCs across her network. Neither could 
>justify asking their company to roll out a service based on it, as there 
>was little or no demand for toll quality VoIP or Video/IP in the backbone 
>in 1995-1996. Neither mentioned complexity or scaling factors as feeding 
>into her decision.
>
>Maybe you could point me to published or unpublished research that 
>establishes that the RFC 2206 concerns materialized in reality?
>
>
>Mike and I have our differences of opinion, but on this point he and I are 
>in the same camp. The level of sarcasm and misinformation being expressed 
>on this topic is inappropriate given the published data on the subject. 
>You can measure (RIPE measures) that jitter within and between ISPs is 
>very nominal. That doesn't make it so end to end, and the infinite 
>bandwidth option doesn't exist end to end. Until it does, we're going to 
>have to deal with applications with specific QoS requirements in places 
>that are not blessed with infinite bandwidth.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 20 10:12:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21352
	for <ieprep-archive@odin.ietf.org>; Wed, 20 Nov 2002 10:12:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKFF0U20928
	for ieprep-archive@odin.ietf.org; Wed, 20 Nov 2002 10:15:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFF0v20921
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 10:15:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21321
	for <ieprep-web-archive@ietf.org>; Wed, 20 Nov 2002 10:12:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFB2v20729;
	Wed, 20 Nov 2002 10:11:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKF6Vv19919
	for <ieprep@optimus.ietf.org>; Wed, 20 Nov 2002 10:06:31 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA21139
	for <ieprep@ietf.org>; Wed, 20 Nov 2002 10:03:49 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.18351-0@bells.cs.ucl.ac.uk>; Wed, 20 Nov 2002 15:06:05 +0000
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
cc: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Moving forward: draft-carlberg-ets-*.txt
In-reply-to: Your message of "Thu, 14 Nov 2002 16:43:48 EST." <CBED705A7FD2D311865500508B1089410A414967@chntex02.is.dyncorp.com>
Date: Wed, 20 Nov 2002 15:06:05 +0000
Message-ID: <8562.1037804765@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



> On page 4, section 2.1, There is a reference to "independent networks
> that comprise the Internet".  I would like to see something somewhere
> (probably section 2, Scope) that makes it clear that we may be
> interested in ANY networks running the IP protocol suite, whether or not
> they are one of the networks that "comprise the Internet".  In
> particular, the IP networks within the "core" of a circuit switched
> network do not "comprise the Internet".

ok, we can add some text that will make it clear that we are not excluding
private IP networks.

> Page 4 3. 2)
> Labels from different layers are not required to be related to each other by
> protocol, but there may be policies about their relationship.\

ok.  there is agreement that this item needs to be expanded to clarify
what is meant.  We'll use some of the exchange on the subject of
policies & labels of a few weeks ago to do this.

> In the "telephony" paper, some of the general requirement from the first
> paper need to be expanded for telephony.
> 
> Page 2, section 2.1
> What do you mean by "carriers"?  Does that include both ISPs and "common
> carriers"?

ISPs what the target of that passage.  I'll use the ISP instead in the
next version.

> Page 3 sec 3. 3)
> This implies that we need translation of ALL "existing labels defined for
> the PSTN".  I don't think we need that.  We DO need translation of "all
> existing labels used to identify emergency and/or priority calls in the
> PSTN".  And we WILL need translation of FUTURE labels used to identify
> emergency or priority calls in the PSTN.

ok, agreed that we don't need a mapping of ALL possible labels.  we'll
make it clear that the passage applies to labels used for or related to
emergencies.


> From a GETS perspective, I would like to see CPC and Precedence
> mentioned by name, but maybe that is too specific for this paper.

to specific for this document :-).  CPC is mentioned in the framework
document, and that is probably the best place for mentioning it.

> Page 3 3.1 1) Alternate paths
> 
> You might want to consider routing to an alternate IP/PSTN gateway if
> (for whatever reason) you can't get to the originally specified IP/PSTN
> gateway.

ok

> Additional "Value Added"  points (not calling them "requirements" any more)
> 
> Increased probability of call set up (this is a telephony specific  example
> of the "network Functionality" in the General paper).

i'll give this some more thought.

> Authorization is in the General paper.  It would make sense to include a
> telephony specific version of authorization here.  E.g., the IP network
> should accept authorization information from a trusted PSTN network
> element, and vice versa.  The "trusted" part probably includes the
> existence of a contractual relationship.

this seems to be a specific approach, and so crosses the line of what is
in scope.  if you feel strongly about the item, we could consider putting
it in the Framework document.

-ken

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 20 11:30:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24062
	for <ieprep-archive@odin.ietf.org>; Wed, 20 Nov 2002 11:30:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKGWGl26929
	for ieprep-archive@odin.ietf.org; Wed, 20 Nov 2002 11:32:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKGWGv26926
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 11:32:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24039
	for <ieprep-web-archive@ietf.org>; Wed, 20 Nov 2002 11:29:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKGS5v26713;
	Wed, 20 Nov 2002 11:28:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKGROv26679
	for <ieprep@optimus.ietf.org>; Wed, 20 Nov 2002 11:27:24 -0500
Received: from sj-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23831
	for <ieprep@ietf.org>; Wed, 20 Nov 2002 11:24:40 -0500 (EST)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gAKGRJNf024190;
	Wed, 20 Nov 2002 08:27:19 -0800 (PST)
Received: from FRED-W2K6.cisco.com (stealth-10-32-253-236.cisco.com [10.32.253.236])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.2.0-GA)
	with SMTP id ABP69452;
	Wed, 20 Nov 2002 08:26:53 -0800 (PST)
Message-Id: <5.2.0.9.2.20021120082357.018909e8@mira-sjcm-4.cisco.com>
X-Sender: fred@mira-sjcm-4.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 20 Nov 2002 08:25:11 -0800
To: "Nguyen, An" <nguyena@ncs.gov>
From: Fred Baker <fred@cisco.com>
Subject: RE: Re: [Ieprep] Re: Is QoS Dead?
Cc: ieprep@ietf.org
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D5A@emshqs1.ncr.disa.mi
 l>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

At 10:01 AM 11/20/2002 -0500, Nguyen, An wrote:
>Do we have any standard that provides a QoS traffic mapping
>mechanism between endpoints (i.e., 802.1q/q) and edge nodes (i.e., diff-serv
>and mpls)? In order to have end-to-end QoS, we need to have such a
>mechanism.

802.1q is a link layer technology, and therefore does not scale to the 
internet. If you think diffserv is unscalable, replacing it with a set of 
link layer priorities on only one of the many types of interfaces that are 
used in the internet is not going to be an improvement. 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 20 12:07:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25030
	for <ieprep-archive@odin.ietf.org>; Wed, 20 Nov 2002 12:07:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKH9Mt30047
	for ieprep-archive@odin.ietf.org; Wed, 20 Nov 2002 12:09:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKH9Mv30044
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 12:09:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25008
	for <ieprep-web-archive@ietf.org>; Wed, 20 Nov 2002 12:06:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKH5Vv29240;
	Wed, 20 Nov 2002 12:05:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKGuLv28662
	for <ieprep@optimus.ietf.org>; Wed, 20 Nov 2002 11:56:21 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA24560
	for <ieprep@ietf.org>; Wed, 20 Nov 2002 11:53:37 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 20 Nov 2002 16:50:15 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <X2SRJQZN>; Wed, 20 Nov 2002 11:56:18 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D62@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Fred Baker '" <fred@cisco.com>
Cc: "'ieprep@ietf.org '" <ieprep@ietf.org>
Subject: RE: Re: [Ieprep] Re: Is QoS Dead?
Date: Wed, 20 Nov 2002 11:56:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Fred,

I am not in a position to say that Diff-Serv is unscalable. I just repeated
some scalability concerns with Diff-Serv raised by someone early on. 

So back to the QoS issue, Fred, is there a need to provide end-to-end QoS?
what are the existing machanisms (e.g., RSVP, Diff-Serv, NSIS)? Can we use
them to provide QoS? Is there a need to work on a new machanism? Or can we
say that IP was designed to tranport data and that is the end of the QoS
story.

Regards,

An 


-----Original Message-----
From: Fred Baker
To: Nguyen, An
Cc: ieprep@ietf.org
Sent: 11/20/02 11:25 AM
Subject: RE: Re: [Ieprep] Re: Is QoS Dead?

At 10:01 AM 11/20/2002 -0500, Nguyen, An wrote:
>Do we have any standard that provides a QoS traffic mapping
>mechanism between endpoints (i.e., 802.1q/q) and edge nodes (i.e.,
diff-serv
>and mpls)? In order to have end-to-end QoS, we need to have such a
>mechanism.

802.1q is a link layer technology, and therefore does not scale to the 
internet. If you think diffserv is unscalable, replacing it with a set
of 
link layer priorities on only one of the many types of interfaces that
are 
used in the internet is not going to be an improvement. 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 20 12:57:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25031
	for <ieprep-archive@odin.ietf.org>; Wed, 20 Nov 2002 12:07:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKH9Ma30062
	for ieprep-archive@odin.ietf.org; Wed, 20 Nov 2002 12:09:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKH9Mv30057
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 12:09:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25009
	for <ieprep-web-archive@ietf.org>; Wed, 20 Nov 2002 12:06:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKH5Wv29276;
	Wed, 20 Nov 2002 12:05:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKGwiv28806
	for <ieprep@optimus.ietf.org>; Wed, 20 Nov 2002 11:58:44 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24618
	for <ieprep@ietf.org>; Wed, 20 Nov 2002 11:56:00 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <XDXAFR0D>; Wed, 20 Nov 2002 11:56:23 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410BC9609E@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: RJ Atkinson <rja@extremenetworks.com>, Fred Baker <fred@cisco.com>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: Is QoS Dead?
Date: Wed, 20 Nov 2002 11:56:11 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]

>It would be pleasant (and seems to be the case) if we can simply agree 
>here
>that the primary problem lives in the access links, and hence the 
>access links
>should be the focus of efforts to improve service quality.

JPG-
I am certainly willing to agree that the primary problem is not in the core
of the major ISPs.  In fact, I THOUGHT that had been accepted at the interim
meeting this spring (not necessarily agreed to by everyone, but accepted
that it wasn't the issue we needed to address at this point).  The primary
problem seems to be in the access links, in gateways,  in small (typically
private) networks, and in "islands" of IP that are NOT part of the "Big I"
Internet (though the Internet protocols are still applicable), such as
within landline and mobile telecom networks. 

>It would also be pleasant if we could agree that some mechanisms 
>already exist
>(referring specifically to the Class-of-Service implementation that Dave
>Meyer outlined yesterday; see also the note from Sean Donelan that has 
>the
>public URL at sprint.net with the details) that do not use existing 
>IETF standards
>or need new IETF standards work.

JPG- 
Yes, it is very encouraging that a mechanism exists.

Maybe one way of putting it is that WHERE such mechanisms exist, it would be
nice to have a uniform way of indicating "authorized" emergency (as opposed
to 911) traffic.  It would seen to me that a "label" somewhere in the TCP/IP
protocol stack would be the simplest way of providing a UNIFORM indication
(even if the labeled traffic is treated differently by each proprietary
mechanism).  If there is no uniform label, there would need to be a separate
label for each mechanism, and a method for recognizing/translating labels.
Which would increase the cost and complexity for everyone  

>PPS:  DOCSIS specifications include support for a kind of link-layer 
>QoS.  It is
>likely that enabling/using that mechanism within that link type would 
>be the most
>successful approach to improving service quality on those kinds of 
>links.  Note
>that such link-layer QoS mechanisms don't require any IETF standards 
>either.

Several times, people have suggested that "the problem" is better addressed
either at the application level or the link level (both of which
conveniently take it out of the  domain of IETF).

First, as a general principle, I am always suspicious when one group says
"they" (another group/layer/technology) can solve the problem better than
"we" can.  This is often a result of understanding "our" stuff better than
we understand "their" stuff.  When asked, "they" often say that "we" can
address the problem better than "they" can.

Second, even if their IS a good solution (or several good solutions) at the
link level, the link level is not the same end-to-end.  There needs to be an
end-to-end way of IDENTIFYING the traffic that is entitled to "special
treatment".  It still seems to me that the TCP/IP protocol stack is the
"right" place  for this identification. 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 20 14:44:16 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28809
	for <ieprep-archive@odin.ietf.org>; Wed, 20 Nov 2002 14:44:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKJkTK08600
	for ieprep-archive@odin.ietf.org; Wed, 20 Nov 2002 14:46:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKJkTv08597
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 14:46:29 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28782
	for <ieprep-web-archive@ietf.org>; Wed, 20 Nov 2002 14:43:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKJgMv08415;
	Wed, 20 Nov 2002 14:42:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKJf2v08371
	for <ieprep@optimus.ietf.org>; Wed, 20 Nov 2002 14:41:02 -0500
Received: from sj-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28590
	for <ieprep@ietf.org>; Wed, 20 Nov 2002 14:38:18 -0500 (EST)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gAKJetNf018364;
	Wed, 20 Nov 2002 11:40:55 -0800 (PST)
Received: from FRED-W2K6.cisco.com (stealth-10-32-253-236.cisco.com [10.32.253.236])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.2.0-GA)
	with SMTP id ABP85657;
	Wed, 20 Nov 2002 11:40:29 -0800 (PST)
Message-Id: <5.2.0.9.2.20021120085714.0188e958@mira-sjcm-4.cisco.com>
X-Sender: fred@mira-sjcm-4.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 20 Nov 2002 11:39:45 -0800
To: "Nguyen, An" <nguyena@ncs.gov>
From: Fred Baker <fred@cisco.com>
Subject: RE: Re: [Ieprep] Re: Is QoS Dead?
Cc: "'ieprep@ietf.org '" <ieprep@ietf.org>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D62@emshqs1.ncr.disa.mi
 l>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

At 11:56 AM 11/20/2002 -0500, Nguyen, An wrote:
>So back to the QoS issue, Fred, is there a need to provide end-to-end QoS?
>what are the existing machanisms (e.g., RSVP, Diff-Serv, NSIS)? Can we use
>them to provide QoS? Is there a need to work on a new machanism? Or can we
>say that IP was designed to tranport data and that is the end of the QoS
>story.

"provide end to end qos" is an interesting description.

I'm told that I sometimes speak in code; let me pass along the code that I 
am using when I describe something as "interesting". I have taken school 
groups out to the Catalina Island Marine Institute to learn something about 
marine science. They are invariably given the opportunity to disect a 
squid, and (being sixth graders) are told that there is one thing that they 
are not allowed to say during the process: "yechh! gross!". They are 
instructed, instead, to say "in-ter-est-ing"...

As Ran and others pointed out yesterday, "provide end to end qos" can mean 
a number of things:
  - "make sure that packets get through with certain delay/jitter/loss 
characteristics
    end to end"
  - "install specific queues for specific data streams with specific 
characteristics"
  - "place circuit-like calls for specific data streams"
  - "ensure that there is capacity in a call-like basis, and then handle as an
    aggregate in the data plane"
and so on

I think, if you listen carefully to Ran, Bill, and Dave, they would say 
that it is important in the Internet to ensure that packets get from here 
to there with predictable latency etc. Ran's fifth slide makes that point 
strongly: he wants to drop no packets *and* deliver predictable delays. 
 From that perspective, it is a business imperative that the top ISPs 
deliver predictable service to their customers, and they take delivery of 
predictability very seriously. End to end QoS, by that definition, is very 
important. (Guys, correct me if I am wrong on your viewpoints)

Some of those ISPs will also tell you that a customer's ability to run 
specific applications over their service is also important, and some will 
tell you that this is the customer's problem. Without naming names - it's 
not my place and there are confidentiality issues - I can tell you that my 
company has worked with some ISPs specifically to ensure that voice will 
work well in their backbones, and some of those represented in this 
discussion are among those who have taken Voice on IP seriously. If you 
look at Athina's paper, which I posted a pointer to yesterday, she points 
out that some US ISPs (the kind that are being represented as "without 
problems" and instructing those of us who are "without clue") experience 
interesting (see "code" above) problems with respect to specific 
applications requiring detailed quality, especially voice. They don't all 
exhibit the behavior in the same way: some do pretty well, and others 
measurably don't.

There is research in progress (early reports available in the literature, 
more detailed reports in progress) on the hypothesis that at during the 
9/11 stuff, there were snap losses of BGP connectivity between major ISPs 
that were not related to link loss, but to BGP session loss due to link 
swamping. I don't know about you, but I consider losing routing to be 
rather an impediment to delivering a reliable internet service.

Yesterday afternoon, soon after interacting in this exchange, I had a 
telephone call with an ISP (whom I cannot name for obvious reasons, but it 
is not a US ISP; it lives in a part of the world where it pretty much has 
to lease its fiber from a semi-government telco that runs a competing ISP, 
and is therefore quite expensive) that has gone through and deployed 
several classes of traffic and WRED on its links with the objective of (a) 
using them at > 70% capacity and simultaneously (b) providing predictable 
service to its customers. They would agree, I think, with Ran's comment on 
slide 3 that the viewpoint he stated "is a little US-centric". I have had 
customers walk up after I give talks and thank me for taking into account 
that not everyone owns their own fiber, not everyone is governed by US 
telecom law, and bandwidth, when you have to buy it from a competitor who 
also happens to be the local telecom+ISP monopoly, is not free or even 
cheap. The fact that these companies don't come to the IETF and announce 
that they are delivering service under interesting conditions (see "code" 
above, and Ran's slide 13) doesn't mean they don't exist. It means that 
they don't want to publicly hand their competitor a weapon and put on a 
"kick me" sign. Discounting their experience as irrelevant to the clueful 
doesn't help.

Do we need end to end explicit assurance of a certain quality, in the sense 
of per-call reservations, specified queues for fine-grained behavior 
aggregates, and so on? No, we don't, and even if we did, that approach has 
interesting (see "code" above) scaling properties.

There are some applications that have specific requirements, and if one 
wants to run those applications over the backbone, their requirements need 
to be met. In the core of the top 100 ISPs globally and Fortune 500 
companies, we have been able to meet most of those issues by supplying 
bandwidth. In at least some cases, this has meant gerrymandering the use of 
that bandwidth in specific ways to reduce the overall cost of running a 
network, which is where MPLS Traffic Engineering enters the picture. 
Frankly, if bandwidth was as cheap and available as the presentations on 
Monday made it sound, there would be no interest in that technology. But at 
the same time, the fact that traffic engineering technology materially 
addresses many of the issues argues equally effectively that finer grain 
considerations are not obviously warranted.

Many of the applications that run over the Internet are essentially 
elastic. On this point, I would strongly suggest that you stop reading this 
email, read http://www.ietf.org/rfc/rfc1633.txt, sections 3.1.1 and 3.1.2, 
which define the terms I am about to use, and then come back.

         <pause>

Having now read that, you are well aware that providing appropriate service 
for these applications is not about providing hard delay bounds or specific 
rates to individual sessions. It is about getting the messages through with 
high probability and humanly-acceptable levels of delay. For example, 
consider instant messaging. If you have ever sat in a chat room or its 
"blackberry" equivalent, you are well aware that message deliver is not 
snappy. The fact that it gets through at all is quite sufficient - and is 
what has been put forward as making internet chat a desirable and effective 
tool for emergency services support. Asking service providers to do 
interesting (see "code") things to make this service "wonderful" doesn't 
meet any specific objective in Harald's requirements document, as long as 
the service works at all.

Not all applications are elastic. For those that, in RFC 1633's terms, 
require "real time" service, and which I call "inelastic" by comparison to 
"elastic" applications, there are other issues. Specifically, I am 
referring to voice and video; there are probably other applications with 
these characteristics, but they don't come quickly to mind. The first issue 
is the assurance of the availability of bandwidth when the bandwidth is 
needed, which implies a policy comparing amount of bandwidth needed, amount 
of bandwidth available, and the authorization of the potential user of the 
bandwidth. If bandwidth is infinite when compared to the potential load, 
this falls out: in my home, I have one IP phone, and enough bandwidth to 
handle it, so I personally don't need extensive authorization machinery. If 
I have a large number of IP phones and the sum of the bandwidth they could 
imaginably use exceeds the available capacity, that is another issue. 
Generally, it is a valid assumption that only a certain proportion of users 
can be expected to use the phone at any given time. If it is reasonable to 
expect that under extraordinary conditions they might literally all attempt 
to place a call, then those policy considerations are real. note that I 
haven't told you how to solve the problem - there are many ways, including 
spending infinite budget to procure infinite bandwidth, SIP polcy, RSVP 
policy, and so on; my point is that someone has to somehow ensure that the 
people who need the bandwidth and are authorized to use it have access to 
it, by whatever means is chosen. The second is that, given the availability 
of bandwidth, the BER and variation in delay is within bounds acceptable to 
the application. Anyone who has seen little squares on a TV screen or has 
had the equivalent of a bad telephone circuit in a VoIP conversation can 
tell you why this is important. Again, I'm not telling you how to solve it, 
but the fact is that the issue is measurably real and does indeed require a 
solution.


>So back to the QoS issue, Fred, is there a need to provide end-to-end QoS? 
>What are the mechanisms...?

We are involved, here, in what amounts to a discussion of technological 
religion, business issues, and user requirements.

The user requirements, I think you would agree, are that specific 
applications work when the chips are down to support emergency workers. If 
you are dealing with a specific link layer issue on a specific link, link 
layer facilities such as DOCSIS and 802.1q (now part of 802.1d, I believe) 
can be helpful. In the case of my VoIP services, which run over a VPN 
running over at least two service providers and two edge networks (Cisco's 
and my home), they can be helpful but don't address the issues end to end. 
Working around them involves identifying the application and ensuring that 
the voice traffic (which is encrypted and inside an IP datagram) gets the 
right service from the DOCSIS modem or the routers surrounding it. That 
winds up meaning handling the issues at an IP layer in the router in my 
office and a router at Cisco, because I am working around a service 
provider which is not Bill Woodcock, Ran Atkinson, or Dave Meyer, and 
(judging from its external behavior) appears to think that following their 
principles of service deployment conflict with its business plans or 
realities.

The possible technical alternatives are bandwidth, signaled QoS policy, and 
provisioned QoS configurations at the IP layer to work around the very 
different provisions in place at the link layer. The technical choice will 
be made by some combination of the religion and business viewpoints of the 
various folks involved. I'm 23,000 feet from the CO, so changing to a DSL 
provider (which would be cheaper and give me much more bandwidth) is not an 
option. So for me, the only available option is to use some form of QoS 
technology to work around the provider. Arguing that because the provider 
has not deployed it himself there is no requirement for the technology is, 
therefore, an interesting (see "code" above) argument to make...

Is there a need for end to end QoS? I dunno, I think there's only a need if 
you want your inelastic applications to reliably work end to end. Is that 
important? 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 20 18:17:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04483
	for <ieprep-archive@odin.ietf.org>; Wed, 20 Nov 2002 18:17:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKNJb423735
	for ieprep-archive@odin.ietf.org; Wed, 20 Nov 2002 18:19:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKNJbv23732
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 18:19:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04465
	for <ieprep-web-archive@ietf.org>; Wed, 20 Nov 2002 18:16:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKNF8v23604;
	Wed, 20 Nov 2002 18:15:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKNENv23571
	for <ieprep@optimus.ietf.org>; Wed, 20 Nov 2002 18:14:23 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04420
	for <ieprep@ietf.org>; Wed, 20 Nov 2002 18:11:21 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id D40A17A0A; Wed, 20 Nov 2002 15:13:58 -0800 (PST)
Date: Wed, 20 Nov 2002 18:14:01 -0500
Subject: [Ieprep] End-to-end QoS
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <CBED705A7FD2D311865500508B1089410BC9609E@chntex02.is.dyncorp.com>
Message-Id: <C1048628-FCDD-11D6-B1E5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 20, 2002, at 11:56 America/Montreal, Gunn, Janet 
wrote:
> Maybe one way of putting it is that WHERE such mechanisms exist, it 
> would be
> nice to have a uniform way of indicating "authorized" emergency (as 
> opposed
> to 911) traffic.  It would seen to me that a "label" somewhere in the 
> TCP/IP
> protocol stack would be the simplest way of providing a UNIFORM 
> indication
> (even if the labeled traffic is treated differently by each proprietary
> mechanism).  If there is no uniform label, there would need to be a 
> separate
> label for each mechanism, and a method for recognizing/translating 
> labels.
> Which would increase the cost and complexity for everyone

A significant challenge with having a "uniform label" that is 
transmitted
inter-domain is that it creates a new, large DDOS vulnerability.

That aside for the moment, the *policy* applicable to the customer-side
router on a given access link is generally the exclusive and local 
policy
decision of the customer on that link.  The policy on the ISP-side 
router
of a given access link is generally the customer's policy, but probably
within some ISP-specific constraints (e.g. see Sprint's web page for one
example of such constraints).

In short, since the access customer is paying for the link, it is their
policy choice for CoS/QoS on their links.

> Several times, people have suggested that "the problem" is better 
> addressed
> either at the application level or the link level (both of which
> conveniently take it out of the  domain of IETF).
>
> First, as a general principle, I am always suspicious when one group 
> says
> "they" (another group/layer/technology) can solve the problem better 
> than
> "we" can.  This is often a result of understanding "our" stuff better 
> than
> we understand "their" stuff.  When asked, "they" often say that "we" 
> can
> address the problem better than "they" can.

Thanks for sharing the perspective.  It is helpful to understand 
alternate
perspectives.

> Second, even if their IS a good solution (or several good solutions) 
> at the
> link level, the link level is not the same end-to-end.  There needs to 
> be an
> end-to-end way of IDENTIFYING the traffic that is entitled to "special
> treatment".  It still seems to me that the TCP/IP protocol stack is the
> "right" place  for this identification.

Proposals for end-to-end QoS should start by talking about how 
deploying them
inter-domain will avoid creating a very large new DDOS vulnerability.  
A huge
advantage of link-layer or link-specific (e.g. Sprint's CoS) QoS is that
it generally does not create such a DDOS vulnerability for the ISPs.

Ran
rja@extremenetworks.com


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 20 18:42:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05163
	for <ieprep-archive@odin.ietf.org>; Wed, 20 Nov 2002 18:42:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKNj8425177
	for ieprep-archive@odin.ietf.org; Wed, 20 Nov 2002 18:45:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKNj8v25174
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 18:45:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05150
	for <ieprep-web-archive@ietf.org>; Wed, 20 Nov 2002 18:42:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKNf5v25044;
	Wed, 20 Nov 2002 18:41:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKNcsv24925
	for <ieprep@optimus.ietf.org>; Wed, 20 Nov 2002 18:38:54 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04967
	for <ieprep@ietf.org>; Wed, 20 Nov 2002 18:35:52 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 40C857A0A; Wed, 20 Nov 2002 15:38:26 -0800 (PST)
Date: Wed, 20 Nov 2002 18:38:28 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep@ietf.org '" <ieprep@ietf.org>
To: Fred Baker <fred@cisco.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <5.2.0.9.2.20021120085714.0188e958@mira-sjcm-4.cisco.com>
Message-Id: <2BBFE6BA-FCE1-11D6-B1E5-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] MPLS
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 20, 2002, at 14:39 America/Montreal, Fred Baker wrote:
>  In at least some cases, this has meant gerrymandering the use of that 
> bandwidth
> in specific ways to reduce the overall cost of running a network, 
> which is
> where MPLS Traffic Engineering enters the picture. Frankly, if 
> bandwidth was
> as cheap and available as the presentations on Monday made it sound,
> there would be no interest in that technology.

Au contraire.  You totally discount the power of marketing and that 
power is
not trivial.  And at least two significant vendors of large routers 
have been
pushing MPLS in a huge way, often to customers who don't need or want 
it.

Please lets not confuse marketing with engineering or at least admit
that marketing often has a big impact on what gorp gets deployed
in at least some networks.

Ran Atkinson
rja@extremenetworks.com

PS:	Unless memory failes me, the mpls-haters list is run by Sean Doran
	of sprint.net.  So I suspect he doesn't use any MPLS in his network.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 20 19:52:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06363
	for <ieprep-archive@odin.ietf.org>; Wed, 20 Nov 2002 19:52:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAL0sR628637
	for ieprep-archive@odin.ietf.org; Wed, 20 Nov 2002 19:54:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAL0sRv28634
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 19:54:27 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06351
	for <ieprep-web-archive@ietf.org>; Wed, 20 Nov 2002 19:51:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAL0o7v28403;
	Wed, 20 Nov 2002 19:50:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAL0j1v28238
	for <ieprep@optimus.ietf.org>; Wed, 20 Nov 2002 19:45:01 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA06154
	for <ieprep@ietf.org>; Wed, 20 Nov 2002 19:42:13 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.10149-0@bells.cs.ucl.ac.uk>; Thu, 21 Nov 2002 00:44:12 +0000
To: RJ Atkinson <rja@extremenetworks.com>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] MPLS
In-reply-to: Your message of "Wed, 20 Nov 2002 18:38:28 EST." <2BBFE6BA-FCE1-11D6-B1E5-00039357A82A@extremenetworks.com>
Date: Thu, 21 Nov 2002 00:44:11 +0000
Message-ID: <16466.1037839451@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



> Please lets not confuse marketing with engineering or at least admit
> that marketing often has a big impact on what gorp gets deployed
> in at least some networks.

there are two types of marketing -- one to build mass, and the other
to build on existing mass.  the initial one should be taken with a
skeptical eye

> PS:	Unless memory failes me, the mpls-haters list is run by Sean Doran
> 	of sprint.net.  So I suspect he doesn't use any MPLS in his network.

on the other side of the coin, my understanding was that uunet has been
running (and marketing :-) MPLS for a while (perhaps 1 to 2 years?) for
TE.  that of course is not an endorsement of MPLS, but just that someone
has decided its satisfactory for them

-ken

ps, as a side note, one ISP engineer working on MPLS told me that its
really just beneficial for a couple of dozen ISPs, period.  And that its
not an excuse for grossly poor capacity planning. ie, its not a panacea.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 07:12:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29067
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 07:12:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALCEIh10406
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 07:14:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALCEIv10403
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 07:14:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29064
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 07:11:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALCADv10310;
	Thu, 21 Nov 2002 07:10:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALC9Pv10254
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 07:09:25 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29005
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 07:06:28 -0500 (EST)
Received: from mcl-its-ieg02.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Thu, 21 Nov 2002 07:08:42 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg02.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2002112107081003689
 ; Thu, 21 Nov 2002 07:08:10 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <XJ37DA6D>; Thu, 21 Nov 2002 07:08:40 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E779AD@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Fred Baker '" <fred@cisco.com>, "'Nguyen, An '" <nguyena@ncs.gov>
Cc: "''ieprep@ietf.org ' '" <ieprep@ietf.org>
Subject: RE: Re: [Ieprep] Re: Is QoS Dead?
Date: Thu, 21 Nov 2002 07:08:50 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

An asked:
>So back to the QoS issue, Fred, is there a need to provide end-to-end QoS? 

Fred said:
>Is there a need for end to end QoS? I dunno, I think there's only a 
>need if you want your inelastic applications to reliably work end to 
>end. Is that important? 

It is also important to ask the right questions.  Is world peace important?
Yes, I believe it is but what chance do we have solving it (were it within
the charter) in ieprep? 

We need to understand the wonderful knowledge of Fred but we also need to
keep our bearings about that which we can change, and that, for which we
might want to change more than anything else in the world, but are helpless.
Let's think about what we can do to improve service quality focusing on
access links and end systems. I've been talking with some folks here and
I'll be posting some ideas soon.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 09:26:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03908
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 09:26:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALESDu17871
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 09:28:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALESDv17868
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 09:28:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03892
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 09:25:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALEOCv17729;
	Thu, 21 Nov 2002 09:24:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALENmv17706
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 09:23:48 -0500
Received: from marionberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03655
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 09:21:06 -0500 (EST)
Received: from cs.columbia.edu (cta.ietf55.ops.ietf.org [204.42.73.38])
	(user=hgs10 mech=PLAIN bits=0)
	by marionberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gALENbUJ025587
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 21 Nov 2002 09:23:37 -0500 (EST)
Message-ID: <3DDCEBED.4030208@cs.columbia.edu>
Date: Thu, 21 Nov 2002 09:21:33 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>
CC: "'Fred Baker '" <fred@cisco.com>,
        "''ieprep@ietf.org ' '" <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: Is QoS Dead?
References: <B8030EB94AF1D51196D70002A589D64207E779AD@mcl-its-exs01>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> We need to understand the wonderful knowledge of Fred but we also need to
> keep our bearings about that which we can change, and that, for which we
> might want to change more than anything else in the world, but are helpless.
> Let's think about what we can do to improve service quality focusing on
> access links and end systems. I've been talking with some folks here and
> I'll be posting some ideas soon.

A possibly productive approach would be to take a look going on within 
NSIS. They are in the requirements phase right now, so maybe 
contributing to that work could be useful. Whether and where NSIS output 
will be deployed is another question, but there's not much we can do 
about that. We'll always be in a situation where nothing is universal 
and the IETF can't mandate deployment of anything in any event, so it 
seems more productive to enable the tools we do have. This is all about 
increasing the "*probability* of service success", not waiting until 
perfection.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 10:51:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07220
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 10:51:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALFrIZ23766
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 10:53:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFrIv23763
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 10:53:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07162
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 10:50:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFnAv23391;
	Thu, 21 Nov 2002 10:49:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFGrv21281
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 10:16:53 -0500
Received: from dewberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06236
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 10:14:11 -0500 (EST)
Received: from cs.columbia.edu (cta.ietf55.ops.ietf.org [204.42.73.38])
	(user=hgs10 mech=PLAIN bits=0)
	by dewberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gALFGnWS019657
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 10:16:50 -0500 (EST)
Message-ID: <3DDCF864.5050900@cs.columbia.edu>
Date: Thu, 21 Nov 2002 10:14:44 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ieprep@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] NSIS
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

[My previous message apparently lacked clarity. Let me try again...]

- Instead of worrying about speculating what may or may not get deployed 
in what networks by whom and when (which is, at best, an RFP issue, not 
an IETF issue), let's make sure that emerging, IEPREP-relevant protocols 
have the necessary functionality.

- NSIS seems related to IEPREP and is in the requirements phase.

- IEPREP (or individuals) may want to look at the NSIS requirements 
document and provide input from an IEPREP perspective.

To add more technical content: for NSIS and similar resource control 
protocols, granting resources to a designated group of individuals is 
actually probably somewhat easier than the usual "random roaming 
consumer wants services, but who knows whether his credit card number is 
stolen and whether we can collect". In some cases, one could imagine a 
mode that does not require an on-line AAA mechanism at all, removing one 
of the failure modes and scaling limitations.

NSIS is specifically looking at the edge-to-edge deployment issue.

Henning

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 11:16:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08519
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 11:16:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALGIIl26129
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 11:18:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGIIv26126
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 11:18:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08482
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 11:15:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGEFv25563;
	Thu, 21 Nov 2002 11:14:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFoOv23526
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 10:50:24 -0500
Received: from imo-r02.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07083
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 10:47:27 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r02.mx.aol.com (mail_out_v34.13.) id a.141.3355ed3 (4254);
	Thu, 21 Nov 2002 10:49:27 -0500 (EST)
Message-ID: <141.3355ed3.2b0e5a86@aol.com>
Date: Thu, 21 Nov 2002 10:49:26 EST
Subject: Re: [Ieprep] Re: Is QoS Dead?
To: KIMBERLY.S.KING@saic.com, fred@cisco.com, nguyena@ncs.gov
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_141.3355ed3.2b0e5a86_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 10500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_141.3355ed3.2b0e5a86_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/21/2002 7:11:13 AM Eastern Standard Time, 
KIMBERLY.S.KING@saic.com writes:


> An asked:
> >So back to the QoS issue, Fred, is there a need to provide end-to-end QoS? 
> 
> Fred said:
> >Is there a need for end to end QoS? I dunno, I think there's only a 
> >need if you want your inelastic applications to reliably work end to 
> >end. Is that important? 
> 
> It is also important to ask the right questions.  Is world peace important?
> Yes, I believe it is but what chance do we have solving it (were it within
> the charter) in ieprep? 
> 



[MAP] Since previous e-mail exchanges on this list indicated out that there 
is a difference of opinion on what "QoS" means, as used in the above several 
sentences (both valid meanings), could I suggest that there are separate 
questions as follows:

1. "Is there a need to worry about the quality of an end-to-end service?"
2. "Is there a need to figure out ways to improve the quality of an 
end-to-end service?"
3. "Is there a need to provide an end-to-end protocol to support the 
improvement in the end-to-end quality of a service?"
4. "Is there a need to guarantee perfect end-to-end quality?"

These are very different questions. I believe the answers are:

1. Absolutely yes.
2. Yes, at least in some cases.
3. Maybe.
4. No, trying to do this would be like getting total world peace.

Mike Pierce
Artel


--part1_141.3355ed3.2b0e5a86_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/21/2002 7:11:13 AM Eastern Standard Time, KIMBERLY.S.KING@saic.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">An asked:
<BR>&gt;So back to the QoS issue, Fred, is there a need to provide end-to-end QoS? 
<BR>
<BR>Fred said:
<BR>&gt;Is there a need for end to end QoS? I dunno, I think there's only a 
<BR>&gt;need if you want your inelastic applications to reliably work end to 
<BR>&gt;end. Is that important? 
<BR>
<BR>It is also important to ask the right questions. &nbsp;Is world peace important?
<BR>Yes, I believe it is but what chance do we have solving it (were it within
<BR>the charter) in ieprep? 
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>
<BR>[MAP] Since previous e-mail exchanges on this list indicated out that there is a difference of opinion on what "QoS" means, as used in the above several sentences (both valid meanings), could I suggest that there are separate questions as follows:
<BR>
<BR>1. "Is there a need to worry about the quality of an end-to-end service?"
<BR>2. "Is there a need to figure out ways to improve the quality of an end-to-end service?"
<BR>3. "Is there a need to provide an end-to-end protocol to support the improvement in the end-to-end quality of a service?"
<BR>4. "Is there a need to guarantee perfect end-to-end quality?"
<BR>
<BR>These are very different questions. I believe the answers are:
<BR>
<BR>1. Absolutely yes.
<BR>2. Yes, at least in some cases.
<BR>3. Maybe.
<BR>4. No, trying to do this would be like getting total world peace.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_141.3355ed3.2b0e5a86_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 11:17:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08647
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 11:17:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALGJxT26288
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 11:19:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGJxv26285
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 11:19:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08622
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 11:17:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGG4v25947;
	Thu, 21 Nov 2002 11:16:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGEWv25759
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 11:14:32 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08171
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 11:11:49 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 21 Nov 2002 16:08:25 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XKBY6P2G>; Thu, 21 Nov 2002 11:13:56 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D6D@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Henning Schulzrinne '" <hgs@cs.columbia.edu>
Cc: "'ieprep@ietf.org'" <ieprep@ietf.org>
Subject: RE: [Ieprep] NSIS
Date: Thu, 21 Nov 2002 11:13:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



>NSIS is specifically looking at the edge-to-edge deployment issue.

I read the NSIS framework in which, I thought, Section 3.2.3 includes
End-to-End, Edge-to-Edge, and End-to-Edge. Correct me if my interpretation
on the document is wrong. 

Regards,

An

   
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 11:27:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09154
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 11:27:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALGU1127045
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 11:30:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGU1v27042
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 11:30:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09146
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 11:27:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGQ4v26848;
	Thu, 21 Nov 2002 11:26:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGNcv26673
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 11:23:38 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08819
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 11:20:54 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gALGHQd25072;
	Thu, 21 Nov 2002 08:17:26 -0800 (PST)
Date: Thu, 21 Nov 2002 08:17:26 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: KIMBERLY.S.KING@saic.com, <fred@cisco.com>, <nguyena@ncs.gov>,
        <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: Is QoS Dead?
In-Reply-To: <141.3355ed3.2b0e5a86@aol.com>
Message-ID: <Pine.GSO.4.44.0211210816070.24965-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 21 Nov 2002 Mpierce1@aol.com wrote:
    > 1. "Is there a need to worry about the quality of an end-to-end service?"
    > 2. "Is there a need to figure out ways to improve the quality of an
    > end-to-end service?"
    > 3. "Is there a need to provide an end-to-end protocol to support the
    > improvement in the end-to-end quality of a service?"
    > 4. "Is there a need to guarantee perfect end-to-end quality?"
    >
    > These are very different questions. I believe the answers are:
    >
    > 1. Absolutely yes.
    > 2. Yes, at least in some cases.
    > 3. Maybe.
    > 4. No, trying to do this would be like getting total world peace.

If you're using "end-to-end" in the IETF sense of "between the application
layers at the endpoints" then we're in complete agreement.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 11:37:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09667
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 11:37:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALGe0Q28230
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 11:40:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGe0v28227
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 11:40:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09614
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 11:37:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGX1v27340;
	Thu, 21 Nov 2002 11:33:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGW2v27271
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 11:32:02 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09222
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 11:29:18 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gALGWj9I025250;
	Thu, 21 Nov 2002 08:32:45 -0800
Date: Thu, 21 Nov 2002 08:32:45 -0800
From: David Meyer <dmm@sprint.net>
To: Bill Woodcock <woody@pch.net>
Cc: Mpierce1@aol.com, KIMBERLY.S.KING@saic.com, fred@cisco.com,
        nguyena@ncs.gov, ieprep@ietf.org
Subject: Re: [Ieprep] Re: Is QoS Dead?
Message-ID: <20021121083245.A25246@sprint.net>
References: <141.3355ed3.2b0e5a86@aol.com> <Pine.GSO.4.44.0211210816070.24965-100000@paixhost.pch.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.GSO.4.44.0211210816070.24965-100000@paixhost.pch.net>; from woody@pch.net on Thu, Nov 21, 2002 at 08:17:26AM -0800
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>> If you're using "end-to-end" in the IETF sense of "between the application
>> layers at the endpoints" then we're in complete agreement.

I was about to ask for the same clarification with the same
conclusion. 

Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 11:38:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09693
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 11:38:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALGeSn28299
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 11:40:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGeSv28296
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 11:40:28 -0500
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09638
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 11:37:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGV3v27143;
	Thu, 21 Nov 2002 11:31:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGQrv26893
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 11:26:53 -0500
Received: from marionberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08964
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 11:24:05 -0500 (EST)
Received: from cs.columbia.edu (cta.ietf55.ops.ietf.org [204.42.73.38])
	(user=hgs10 mech=PLAIN bits=0)
	by marionberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gALGQgUJ015390
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 21 Nov 2002 11:26:45 -0500 (EST)
Message-ID: <3DDD08C5.6080303@cs.columbia.edu>
Date: Thu, 21 Nov 2002 11:24:37 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Nguyen, An" <nguyena@ncs.gov>
CC: "'ieprep@ietf.org'" <ieprep@ietf.org>
Subject: Re: [Ieprep] NSIS
References: <7F18415E4D63CB45BB9B3A591F68D12D5B3D6D@emshqs1.ncr.disa.mil>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I believe your interpretation is correct. One has to be somewhat careful 
with the definitions, as 'edge' is sometimes taken to refer to the 
originator of a resource request and sometimes as the target of such 
request (i.e., the edge router that processes the request).

Note that end-to-end does *not* mean that every router or every network 
supports NSIS capabilities.

It simply means that the NSIS request originates at the end system 
sending user data rather than at some proxy (in the generic sense, not 
the SIP sense).

Nguyen, An wrote:
> 
>>NSIS is specifically looking at the edge-to-edge deployment issue.
> 
> 
> I read the NSIS framework in which, I thought, Section 3.2.3 includes
> End-to-End, Edge-to-Edge, and End-to-Edge. Correct me if my interpretation
> on the document is wrong. 
> 
> Regards,
> 
> An
> 
>    

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 14:01:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15762
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 14:01:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALJ3NI06728
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 14:03:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALJ3Nv06725
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 14:03:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15738
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 14:00:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALIx6v06525;
	Thu, 21 Nov 2002 13:59:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALIwbv06500
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 13:58:37 -0500
Received: from imo-m09.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15564
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 13:55:52 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m09.mx.aol.com (mail_out_v34.13.) id b.148.31fb0a5 (4238);
	Thu, 21 Nov 2002 13:55:36 -0500 (EST)
Message-ID: <148.31fb0a5.2b0e8628@aol.com>
Date: Thu, 21 Nov 2002 13:55:36 EST
Subject: Re: [Ieprep] Re: Is QoS Dead?
To: woody@pch.net
CC: KIMBERLY.S.KING@saic.com, fred@cisco.com, nguyena@ncs.gov, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_148.31fb0a5.2b0e8628_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 10500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_148.31fb0a5.2b0e8628_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/21/2002 11:23:40 AM Eastern Standard Time, 
woody@pch.net writes:


> If you're using "end-to-end" in the IETF sense of "between the application
> layers at the endpoints" then we're in complete agreement.
> 
What is ultimately important to the user is end-to-end quality where, for 
voice, would be from one person's mouth to the other's ear. Of course, the 
IETF is not responsible for quite that entire path. So I suppose I meant from 
the user's device to the other device. In this sense, the "application" would 
be the stuff in the user's device that handles the telephony functions, e.g., 
turns bits in packets into sound and vice versa.

Mike Pierce


--part1_148.31fb0a5.2b0e8628_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/21/2002 11:23:40 AM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">If you're using "end-to-end" in the IETF sense of "between the application
<BR>layers at the endpoints" then we're in complete agreement.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">What is ultimately important to the user is end-to-end quality where, for voice, would be from one person's mouth to the other's ear. Of course, the IETF is not responsible for quite that entire path. So I suppose I meant from the user's device to the other device. In this sense, the "application" would be the stuff in the user's device that handles the telephony functions, e.g., turns bits in packets into sound and vice versa.
<BR>
<BR>Mike Pierce
<BR></FONT></HTML>

--part1_148.31fb0a5.2b0e8628_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 14:06:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15932
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 14:06:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALJ8d507520
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 14:08:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALJ8dv07517
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 14:08:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15893
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 14:05:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALJ42v06773;
	Thu, 21 Nov 2002 14:04:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALJ3rv06749
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 14:03:53 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15759
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 14:01:08 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gALIvfd26406;
	Thu, 21 Nov 2002 10:57:42 -0800 (PST)
Date: Thu, 21 Nov 2002 10:57:41 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: KIMBERLY.S.KING@saic.com, <fred@cisco.com>, <nguyena@ncs.gov>,
        <ieprep@ietf.org>
Subject: Re: [Ieprep] Re: Is QoS Dead?
In-Reply-To: <148.31fb0a5.2b0e8628@aol.com>
Message-ID: <Pine.GSO.4.44.0211211053110.26179-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 21 Nov 2002 Mpierce1@aol.com wrote:
    > What is ultimately important to the user is end-to-end quality where, for
    > voice, would be from one person's mouth to the other's ear. Of course, the
    > IETF is not responsible for quite that entire path. So I suppose I meant from
    > the user's device to the other device. In this sense, the "application" would
    > be the stuff in the user's device that handles the telephony functions, e.g.,
    > turns bits in packets into sound and vice versa.

The IETF does take responsibility for the vast majority of that path, it's
just different parts of the IETF, and categorizing the problem so that we
can route it to the correct part of the IETF to deal with it is an
important first step.  The end-to-end (application, layer 7) portion of
the IETF is where the SIP and SIPPING working groups reside, and it's my
contention that we get the greatest benefit if we work on these issues
within SIPPING, where other similar work is being done,a nd where people
have a lot of experience with voice.  IP routing, on the other hand, is
dealt with in the routing area, under Bill and Alex, where you wouldn't
get the time of day, and nobody cares about voice, since that's way down
deep inside packets, and they have, um, a not-inconsiderable disdain for
"payload" like voice or porn or chat or whatever.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 14:59:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17976
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 14:59:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALK1Qd10939
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 15:01:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALK1Pv10936
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 15:01:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17932
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 14:58:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALJv8v10755;
	Thu, 21 Nov 2002 14:57:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALJu7v10702
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 14:56:07 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17822
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 14:53:08 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 323967A0A; Thu, 21 Nov 2002 11:55:44 -0800 (PST)
Date: Thu, 21 Nov 2002 14:55:44 -0500
Subject: Re: [Ieprep] Re: Is QoS Dead?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <148.31fb0a5.2b0e8628@aol.com>
Message-Id: <387E8F08-FD8B-11D6-BDFC-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 21, 2002, at 13:55 America/Montreal, Mpierce1@aol.com 
wrote:
> What is ultimately important to the user is end-to-end quality where, 
> for voice, would be from one person's mouth to the other's ear. Of 
> course, the IETF is not responsible for quite that entire path. So I 
> suppose I meant from the user's device to the other device. In this 
> sense, the "application" would be the stuff in the user's device that 
> handles the telephony functions, e.g., turns bits in packets into 
> sound and vice versa.

In some cases, it would be an IETF issue.  In a lot of cases, this 
stuff is not
strictly within the IETF's writ.  An example of the latter is the CoS 
queueing
that Sprint described is something that might well be very useful, but 
is outside
the scope of IETF specifications for routers.

The low hanging fruit would likely be the stuff similar to what Sprint 
is using
-- and deploying that would seem largely a business/contractual matter 
with the
folks who control the relevant access links.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 21 18:43:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26497
	for <ieprep-archive@odin.ietf.org>; Thu, 21 Nov 2002 18:43:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALNjJC26568
	for ieprep-archive@odin.ietf.org; Thu, 21 Nov 2002 18:45:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALNjJv26565
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 18:45:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26491
	for <ieprep-web-archive@ietf.org>; Thu, 21 Nov 2002 18:42:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALNfAv26412;
	Thu, 21 Nov 2002 18:41:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALNeuv26378
	for <ieprep@optimus.ietf.org>; Thu, 21 Nov 2002 18:40:56 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26345
	for <ieprep@ietf.org>; Thu, 21 Nov 2002 18:38:09 -0500 (EST)
Received: from mcl-its-ieg02.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Thu, 21 Nov 2002 18:40:12 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg02.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2002112118394104851
 for <ieprep@ietf.org>; Thu, 21 Nov 2002 18:39:41 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <XJ37F30C>; Thu, 21 Nov 2002 18:40:11 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E779AF@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'ieprep@ietf.org'" <ieprep@ietf.org>
Date: Thu, 21 Nov 2002 18:40:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Ieprep] problem context
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

The context of "Internet Preparedness" is vast.  Some of the most heated
debates involve people with one context in mind talking to someone else with
a different one.  So, they talk past each other.  

Below is a beginning that I invite the WG to refine.  The purpose is to
facilitate problem solving.  One can state "here is the context and here is
a problem where the default situation is insufficient to solve emergency
service X".

1.	N ETS locations with access links into the same ISP where the ISP
offers CoS. Note that the particular ISP, access link bandwidth, and local
configurations can be determined in advance of the emergency.

2.	Emergency Worker accesses Internet via arbitrary connection (e.g.,
Internet Cafe).  Note that the ISP providing connectivity to the Internet
cannot be determined in advance.

3.	A predetermined network is connected to a privately managed IP WAN
over a predetermined constrained bandwidth connection (e.g., military ship
to Government owned IP network over Satellite) 

4.	A database available on the public Internet supporting emergency
services/recovery (e.g., Japan's IAA)

5.	James Polk's topology scenarios 


While each case potentially involves some form of emergency communications,
there are very different problems and ways to approach these problems. For
example, in case 1, it might be reasonable for something to track bandwidth
usage across that access link, authenticate/authorize users and apply policy
for how that bandwidth is divided up so inelastic applications perform well.
However, if you walk into an arbitrary enterprise and convince the staff
that they should let you use their network, then assuming they will have a
policy server that can authenticate you and make sure you get bandwidth over
the rest of their business users is just not too reasonable.

We need to define the problem and the context to make progress.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 22 04:02:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20783
	for <ieprep-archive@odin.ietf.org>; Fri, 22 Nov 2002 04:02:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAM95EX02017
	for ieprep-archive@odin.ietf.org; Fri, 22 Nov 2002 04:05:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM95Ev02014
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 22 Nov 2002 04:05:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20780
	for <ieprep-web-archive@ietf.org>; Fri, 22 Nov 2002 04:02:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM949v01957;
	Fri, 22 Nov 2002 04:04:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM93fv01893
	for <ieprep@optimus.ietf.org>; Fri, 22 Nov 2002 04:03:41 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA20734
	for <ieprep@ietf.org>; Fri, 22 Nov 2002 04:00:35 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 22 Nov 2002 08:57:08 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XKBY7FC5>; Fri, 22 Nov 2002 04:03:17 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D72@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'ieprep@ietf.org'" <ieprep@ietf.org>
Subject: RE: [Ieprep] Re: Is QoS Dead?
Date: Fri, 22 Nov 2002 04:03:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

I found the below article from Network World today and I think it is
interesting and relavant to what has been discussed in this WG.

---------------------------------------------
Today's focus: Taming UDP 

 By Steve Taylor and Joanie Wexler 

 The User Datagram Protocol is used for transporting traffic 
 types that depend more on speedy packet delivery than on 
 reliable delivery.  As noted in our last newsletter, UDP 
 differs greatly from the other IP transport protocol, TCP, in 
 this respect. 

 One notable application that depends on UDP, of course, is 
 voice over IP. 

 UDP, while it does not generate the network overhead associated 
 with the highly reliable, connection-oriented TCP transport, 
 lacks any form of congestion control. This means that it does 
 not receive any feedback about real-time network conditions and 
 will just continue sending packets merrily along regardless of 
 whether they are moving at a snail's pace or are falling on the 
 floor. 

 In this way, UDP, ironically, can actually make a network 
 congestion problem worse and impact the performance of all 
 protocols on the network. At some point, VoIP delays could 
 degrade a conversation beyond salvation. 

 So what are you to do to "tame" UDP's behavior under these 
 circumstances? There are some traffic management products, 
 which we've covered in this newsletter before, that manage 
 problem children such as UDP. 

 For example, Packeteer says it has built in some controls for 
 outbound UDP traffic into its PacketShaper bandwidth-management 
 device. Upon an Internet client request from a server, 
 PacketShaper steps in to regulate the pace of the UDP packet 
 flow at the sending side. This rate regulation takes place 
 before packets traverse a WAN access link, where congestion is 
 most likely to occur. 

 The controls function in way that seem analogous to a jitter 
 buffers, which "smooth out" the delivery of VoIP packets - 
 albeit at the receiving end - for a more predictable, and 
 better-quality, conversation. 

-----Original Message-----
From: Mpierce1@aol.com
To: KIMBERLY.S.KING@saic.com; fred@cisco.com; nguyena@ncs.gov
Cc: ieprep@ietf.org
Sent: 11/21/02 10:49 AM
Subject: Re: [Ieprep] Re: Is QoS Dead?

In a message dated 11/21/2002 7:11:13 AM Eastern Standard Time,
KIMBERLY.S.KING@saic.com writes: 




An asked: 
>So back to the QoS issue, Fred, is there a need to provide end-to-end
QoS? 

Fred said: 
>Is there a need for end to end QoS? I dunno, I think there's only a 
>need if you want your inelastic applications to reliably work end to 
>end. Is that important? 

It is also important to ask the right questions.  Is world peace
important? 
Yes, I believe it is but what chance do we have solving it (were it
within 
the charter) in ieprep? 






[MAP] Since previous e-mail exchanges on this list indicated out that
there is a difference of opinion on what "QoS" means, as used in the
above several sentences (both valid meanings), could I suggest that
there are separate questions as follows: 

1. "Is there a need to worry about the quality of an end-to-end
service?" 
2. "Is there a need to figure out ways to improve the quality of an
end-to-end service?" 
3. "Is there a need to provide an end-to-end protocol to support the
improvement in the end-to-end quality of a service?" 
4. "Is there a need to guarantee perfect end-to-end quality?" 

These are very different questions. I believe the answers are: 

1. Absolutely yes. 
2. Yes, at least in some cases. 
3. Maybe. 
4. No, trying to do this would be like getting total world peace. 

Mike Pierce 
Artel 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 22 07:37:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23868
	for <ieprep-archive@odin.ietf.org>; Fri, 22 Nov 2002 07:37:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAMCdpS13639
	for ieprep-archive@odin.ietf.org; Fri, 22 Nov 2002 07:39:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMCdpv13636
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 22 Nov 2002 07:39:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23855
	for <ieprep-web-archive@ietf.org>; Fri, 22 Nov 2002 07:37:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMCcvv13611;
	Fri, 22 Nov 2002 07:38:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMCbsv13574
	for <ieprep@optimus.ietf.org>; Fri, 22 Nov 2002 07:37:54 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23845
	for <ieprep@ietf.org>; Fri, 22 Nov 2002 07:34:56 -0500 (EST)
Received: from extremenetworks.com (ssh.extremenetworks.com [10.0.1.139])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id E9E3A7A0E; Fri, 22 Nov 2002 04:37:34 -0800 (PST)
Date: Fri, 22 Nov 2002 07:37:35 -0500
Subject: Re: [Ieprep] problem context
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep@ietf.org'" <ieprep@ietf.org>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E779AF@mcl-its-exs01>
Message-Id: <2DAA6EB4-FE17-11D6-AC93-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 21, 2002, at 18:40 America/Montreal, King, Kimberly S. 
wrote:
> The context of "Internet Preparedness" is vast.  Some of the most 
> heated
> debates involve people with one context in mind talking to someone 
> else with
> a different one.  So, they talk past each other.

This is without question the case.

> Below is a beginning that I invite the WG to refine.  The purpose is to
> facilitate problem solving.  One can state "here is the context and 
> here is
> a problem where the default situation is insufficient to solve 
> emergency
> service X".
>
> 1.	N ETS locations with access links into the same ISP where the ISP
> offers CoS. Note that the particular ISP, access link bandwidth, and 
> local
> configurations can be determined in advance of the emergency.
>
> 2.	Emergency Worker accesses Internet via arbitrary connection (e.g.,
> Internet Cafe).  Note that the ISP providing connectivity to the 
> Internet
> cannot be determined in advance.
>
> 3.	A predetermined network is connected to a privately managed IP WAN
> over a predetermined constrained bandwidth connection (e.g., military 
> ship
> to Government owned IP network over Satellite)

This (3) is not an IEprep scenario.  It is a real-world military 
scenario,
just not an IEprep scenario.  And IEprep is NOT the MLPP WG.

(Aside: A suggestion I have made to the IESG is that they create a 
DiffServ Ops
WG that would be a home for evaluation/documentation of how the current
DiffServ protocol specs line up in practice with real-world operational 
networks.
Based on the output of that hypothetical WG, one could imagine that 
DiffServ specs
might be enhanced/tweaked/fixed based on real-world experience.  
DiffServ is
the obvious mechanism for item (3) above since it was used, albeit 
under another name,
some years back by US DoD to provide that capability [using Proteon 
routers if
memory serves].)

> 4.	A database available on the public Internet supporting emergency
> services/recovery (e.g., Japan's IAA)
>
> 5.	James Polk's topology scenarios
>
>
> While each case potentially involves some form of emergency 
> communications,

Item (3) describes military communications rather than emergency 
communications.
Military communications might (and do) have varying degrees of urgency
and precedence, but they aren't emergency communications.  Examples of
emergency communications would be from civilian organisations such as
Fire, Police, or FEMA.  Military networks might happen to carry some
messages related to a natural disaster, but that does not make such 
networks
IEprep networks.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 22 09:52:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26140
	for <ieprep-archive@odin.ietf.org>; Fri, 22 Nov 2002 09:52:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAMEt3321118
	for ieprep-archive@odin.ietf.org; Fri, 22 Nov 2002 09:55:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMEt2v21115
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 22 Nov 2002 09:55:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26131
	for <ieprep-web-archive@ietf.org>; Fri, 22 Nov 2002 09:52:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMEs9v21066;
	Fri, 22 Nov 2002 09:54:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMErGv21031
	for <ieprep@optimus.ietf.org>; Fri, 22 Nov 2002 09:53:16 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26083
	for <ieprep@ietf.org>; Fri, 22 Nov 2002 09:50:33 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 22 Nov 2002 14:47:06 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XKBY7MGZ>; Fri, 22 Nov 2002 09:53:16 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D23A531@emshqs1.ncr.disa.mil>
From: "Folts, Harold" <foltsh@ncs.gov>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: "'ieprep@ietf.org'" <ieprep@ietf.org>
Subject: RE: [Ieprep] problem context
Date: Fri, 22 Nov 2002 09:53:09 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> -----Original Message-----
> From: RJ Atkinson [mailto:rja@extremenetworks.com]
> Sent: Friday, November 22, 2002 7:38 AM
> To: King, Kimberly S.
> Cc: 'ieprep@ietf.org'
> Subject: Re: [Ieprep] problem context
> 
> Item (3) describes military communications rather than emergency 
> communications.
> Military communications might (and do) have varying degrees of urgency
> and precedence, but they aren't emergency communications.  Examples of
> emergency communications would be from civilian organisations such as
> Fire, Police, or FEMA.  Military networks might happen to carry some
> messages related to a natural disaster, but that does not make such 
> networks
> IEprep networks.
> 

Ran,

I agree that ieprep should be only considering emergency communications in
direct support of emergency and disaster relief operations. This has been
defined as ETS (emergency telecommunications service).

Hal 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 22 10:07:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26659
	for <ieprep-archive@odin.ietf.org>; Fri, 22 Nov 2002 10:07:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAMF9x322394
	for ieprep-archive@odin.ietf.org; Fri, 22 Nov 2002 10:09:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMF9xv22391
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 22 Nov 2002 10:09:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26650
	for <ieprep-web-archive@ietf.org>; Fri, 22 Nov 2002 10:07:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMF94v22354;
	Fri, 22 Nov 2002 10:09:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMF8Zv22318
	for <ieprep@optimus.ietf.org>; Fri, 22 Nov 2002 10:08:35 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26627
	for <ieprep@ietf.org>; Fri, 22 Nov 2002 10:05:37 -0500 (EST)
Received: from mcl-its-ieg02.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Fri, 22 Nov 2002 10:07:47 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg02.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2002112210071706262
 ; Fri, 22 Nov 2002 10:07:17 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <XK59C4HY>; Fri, 22 Nov 2002 10:09:24 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E779B3@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "''RJ Atkinson' '" <rja@extremenetworks.com>
Cc: "''ieprep@ietf.org' '" <ieprep@ietf.org>
Subject: RE: [Ieprep] problem context
Date: Fri, 22 Nov 2002 10:07:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

 
> -----Original Message-----
> From: RJ Atkinson [mailto:rja@extremenetworks.com]
> Sent: Friday, November 22, 2002 7:38 AM
> To: King, Kimberly S.
> Cc: 'ieprep@ietf.org'
> Subject: Re: [Ieprep] problem context
> 
> Item (3) describes military communications rather than emergency 
> communications.
> Military communications might (and do) have varying degrees of urgency
> and precedence, but they aren't emergency communications.  Examples of
> emergency communications would be from civilian organisations such as
> Fire, Police, or FEMA.  Military networks might happen to carry some
> messages related to a natural disaster, but that does not make such 
> networks
> IEprep networks.
> 

Ran,

The context situation is good but the example should be changed.  I'll
change the example of that context to a FEMA-like mobile router with its RF
connection.

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 22 20:02:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08382
	for <ieprep-archive@odin.ietf.org>; Fri, 22 Nov 2002 20:02:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAN14cQ20213
	for ieprep-archive@odin.ietf.org; Fri, 22 Nov 2002 20:04:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAN14bv20210
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 22 Nov 2002 20:04:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08376
	for <ieprep-web-archive@ietf.org>; Fri, 22 Nov 2002 20:01:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAN13Dv20171;
	Fri, 22 Nov 2002 20:03:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAN127v20148
	for <ieprep@optimus.ietf.org>; Fri, 22 Nov 2002 20:02:07 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08314
	for <ieprep@ietf.org>; Fri, 22 Nov 2002 19:59:17 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Fri, 22 Nov 2002 20:01:37 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2002112220014929495
 for <ieprep@ietf.org>; Fri, 22 Nov 2002 20:01:49 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <XNTT4ZXK>; Fri, 22 Nov 2002 20:01:36 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E779B8@mcl-its-exs01>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'ieprep@ietf.org'" <ieprep@ietf.org>
Date: Fri, 22 Nov 2002 20:01:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Ieprep] ieprep Atlanta meeting minutes
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

18-Novmber-2002, 1530 
IEPrep meeting in Salon B 
Kimberly King and Scott Bradner chairing 


Agenda Review - Chairs 

ISP Backbone of Today - Ran Atkinson 
[James Polk made the point that disparaging information sources is not
helpful.  Ran indicated that the people who reviewed his slides were mostly
in the room and that he was not claiming to represent them and accepted
potential errors as his own.]
Several points from the ISP presentation:
The description is of common properties, not of any specific ISP. 
Many operators have a prime directive to NEVER drop a packet.
Traffic exchanged according to business agreements.
Enabling QoS can cause packets to receive worse treatment.

Comments/Questions from the audience:
After some packet loss statistics were quoted, Janet Gunn asked about packet
loss due to Virus' as distinct from no loss due to cable cuts; she was told
there was no available answer.
Brian Carpenter noted that Diffserv was designed to allow diffserv in the
fast path.

David Meyer presented "Sprint & CoS" 
The slides included:
What Sprint is doing - Edge QoS using egress (to the customer) access
control lists (ACLs), not ToS bits.  (Avoiding ToS bits for this
functionality ensures they don't have to remark other packets entering the
network from Internet connections, for example.)  One possible exception
(perhaps) is for IPSec protected VPNs.
David noted their core traffic (trunks at or over OC48) is uncorrelated,
meaning it does not exhibit self-similar behavior.  (Thus they may be more
confident that traffic loads over their core is smoother and hence feel more
confident that sufficient capacity is available even during times of what
might be considered a surge.)
Their backbone has been measured to handle VoIP at 90 grade MoS (R factor?),
better than PSTN. 

Comments/Questions from the audience:
Dave Oran asked what happens in a major disaster. Dave Meyer indicated that
even in the loss of large numbers of fibers, there was no effect on
services. 
Peter Lothberg commented that internal topologies are even more complex (and
therefore more diverse with additional capacity) than portrayed in Ran's
slides.  He also emphasized customer management of the customer egress
traffic treatment and that ISPs generally do not control customer egress
traffic.  Meanwhile, customers "don't worry about the backbone." 
Susan Harris(?) asked about the meaning of "uncorrelated".  Dave responded
clarifying the effect of aggregation and smoothing at high speeds. Rohan
Mahy paraphrased saying that burstiness is dampened.
Henning Schulzrinne hypothesized it was possible that so much damage could
be caused that the network would actually operate at or over the viable
range.
Mike St. Johns asked about the factors that caused the 90 grade on the MoS
score (rather than 100) and asked about whether truly pathological traffic
behavior had been exhibited. Dave Meyer said he had not seen any. 
Pat Cain from Genuity talked about their recently offered QOS service.  This
is again an edge service on the local access link only.  The purpose is to
manage capacity of narrow pipes. He noted that core congestion is generally
self-inflicted although very large customers connections (e.g., those
connecting with OC-48) can cause some difficulty.

The next presentation "PCH; VoIP experience" was by Bill Woodcock. 
They offer VoIP from end nodes, often on narrow pipes.  A demonstration of a
VoIP call was established between an VoIP phone sitting in front of Scott
Bradner and one in Nairobi, Kenya.  Local PTT quality in Nairobi is much
worse than VoIP. NAT was (and is) a problem for VoIP.

Questions/Comments from the audience:
Kathy Nichols - One of the cite article authors also does use QoS 
Sally Floyd mentioned the current time in Kenya and wondered how many
concurrent TCP connections were occurring over the last mile.
The discussion of current circumstances are highly provisioned and Henning
Schulzrinne commenting that we need to be careful about generalizing the
current circumstances to true disaster utilization and effects. 
Ran Atkinson indicated that they could lose almost any capacity and deliver
service to what remained connected.
Peter Lothberg commented that if you really had that bad an outage, other
things would break that would have far more serious effects.  He also
believes if we have "important traffic" and "normal traffic" then important
traffic must be authenticated if it is to be given priority.  Such a
function requires crypto checksums, timestamps and the capability to check
its validity at line rate.  This then involves solving key management, and
to traverse several jurisdictions, each packet has to carry multiple such
headers.  Without inventing a way to do this, any priority mechanism is just
opening up another attack vector for the 'bad boys'. 
Pat Cain suggested that we need a lot of other things separate from the QoS
issues, and we need to spend cycles on that.

Hal Folts presented "IEPrep Requirements"
draft-ietf-ieprep-requirements-01.txt 
Hal said:
The draft is about Objectives for emergency communication using IP
technology.
Not all the objectives may be simultaneously possible, lets see what we can
do. 
He would like any place / any time access a by authorized emergency users. 
Want preferential treatment for emergency communication 
[Scott Bradner asked if what was being requested was for emergency workers
to be able to plug into any jack anywhere, authenticate themselves, and
receive preferential treatment.  Hal indicated this was desirable.]
The draft objectives also request international / interconnected service 
SLAs are relevant to this 
Request for security capabilities 
Keep the connection up, even in DoS situations 
Hal ended by asking how to move forward.

Questions/Comments from the audience:
Dave Crocker - After commenting on the value of general objectives, Dave
asked for specific short-term scenarios describing what specific items are
needed.
Unknown speaker - Discussion of whether these requirements apply to all
services, or only to regulated services (PCH does not provide E911
connectivity.) Bill Woodcock responded that there is no consumer requirement
to provide E911 services. He doesn't believe there's a legal requirement
placed upon users of peer-to-peer devices that they magically make them do
anything special when someone dials "911". 
Dave Oran paraphrased Hal's request as asking for authorized emergency users
to be authorized to perform DoS attacks on other users. 
Scott Bradner rephrased the preferential treatment request as a request for
definable probability of successful communication.
Scott Bradner suggested that SLAs are an implementation detail.
Scott Bradner and Ran Atkinson pointed out that confidentiality, integrity,
etc are end-to-end problems, not network problems.
Peter Lothberg said that the network cannot do anything about keeping up a
"connection" that it does not know about.  The network knows about packets,
not connections. 
Scott Bradner pointed out that whether or not we can meet Hal's objectives,
it is helpful to know about the objectives 
Bill Woodcock suggested that the PSTN cannot be made to meet the security
requirements proposed in this draft.
Unknown speaker suggested that TDM is subject to significant DoS, so why
does IEPrep need something special? 
Another unknown speaker emphasized the value in separating the end system
issues from the network issues since they are mixed in the draft.
Dave Crocker suggested that there may be things that may need to be done in
the network.  And we should concentrate on those things that can be done in
the near term.  Emphasis on end-point only and end-point / access solutions
may be useful in the near term. 
Unknown speaker suggested a requirement on the emergency handling of email,
and particularly with the interaction with SPAM filters.

Ken Carlberg presented "IEPrep Framework"
This is a document on IP Telephony emergency needs; some rewording will
occur and example solutions removed. 

Mike Pierce presented "Accounting" 
Accounting Requirements for Priority Services is not about packet level
accounting.
However, he did not restrict this to just SIP.  
There was discussion of the meaning of "requirement".
Particularly interested in auditing, verifying conformance to usage policy
ARCH slide actually is referencing RFC 3334.

Questions/Comments from the audience.
Henning Schulzrinne asked whether this is a SIP call accounting issue.
There is ongoing work in SIPPING on accounting related issues. 
Peter Lothberg chimed in on the unreasonableness of packet level accounting.

Scott Bradner suggested looking at the SIPPING and AAA work to see if that
meets the needs. 

Scott Bradner wrapped up. WG chairs and ADs will get together to discuss
next steps. Henning Schulzrinne's document is almost ready to ship to
SIPPING.
 
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 22 21:39:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10450
	for <ieprep-archive@odin.ietf.org>; Fri, 22 Nov 2002 21:39:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAN2gAi24564
	for ieprep-archive@odin.ietf.org; Fri, 22 Nov 2002 21:42:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAN2gAv24561
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 22 Nov 2002 21:42:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10436
	for <ieprep-web-archive@ietf.org>; Fri, 22 Nov 2002 21:39:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAN2a8v23798;
	Fri, 22 Nov 2002 21:36:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAN2Zjv23784
	for <ieprep@optimus.ietf.org>; Fri, 22 Nov 2002 21:35:45 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10001
	for <ieprep@ietf.org>; Fri, 22 Nov 2002 21:32:40 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 5E35E67103; Fri, 22 Nov 2002 17:59:03 -0500 (EST)
Date: Fri, 22 Nov 2002 21:35:21 -0500
Subject: Re: [Ieprep] ieprep Atlanta meeting minutes
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep@ietf.org'" <ieprep@ietf.org>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E779B8@mcl-its-exs01>
Message-Id: <36668D04-FE8C-11D6-A3E3-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 22, 2002, at 20:01 America/Montreal, King, Kimberly S. 
wrote:
> Ran Atkinson indicated that they could lose almost any capacity and 
> deliver
> service to what remained connected.

s/they/@Home/
s/capacity/backbone capacity/

:-)

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sun Nov 24 18:20:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04348
	for <ieprep-archive@odin.ietf.org>; Sun, 24 Nov 2002 18:20:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAONMJj17919
	for ieprep-archive@odin.ietf.org; Sun, 24 Nov 2002 18:22:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAONMJv17916
	for <ieprep-web-archive@optimus.ietf.org>; Sun, 24 Nov 2002 18:22:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04345
	for <ieprep-web-archive@ietf.org>; Sun, 24 Nov 2002 18:19:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAONGUv17705;
	Sun, 24 Nov 2002 18:16:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAONFRv17673
	for <ieprep@optimus.ietf.org>; Sun, 24 Nov 2002 18:15:27 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04138
	for <ieprep@ietf.org>; Sun, 24 Nov 2002 18:12:38 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Sun, 24 Nov 2002 18:15:02 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2002112418151514395
 for <ieprep@ietf.org>; Sun, 24 Nov 2002 18:15:15 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <XNSVD4AY>; Sun, 24 Nov 2002 18:16:41 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E779BF@mcl-its-exs01.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'ieprep@ietf.org'" <ieprep@ietf.org>
Date: Sun, 24 Nov 2002 18:15:14 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Ieprep] The Internet Under Crisis Conditions: Learning from September 11 (2002)
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



http://www.nap.edu/books/0309087023/html/



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 25 12:53:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13119
	for <ieprep-archive@odin.ietf.org>; Mon, 25 Nov 2002 12:53:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAPHtb418007
	for ieprep-archive@odin.ietf.org; Mon, 25 Nov 2002 12:55:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPHtav18004
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 25 Nov 2002 12:55:36 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13049
	for <ieprep-web-archive@ietf.org>; Mon, 25 Nov 2002 12:52:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPHrgv17936;
	Mon, 25 Nov 2002 12:53:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPHqsv17910
	for <ieprep@optimus.ietf.org>; Mon, 25 Nov 2002 12:52:54 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA12920
	for <ieprep@ietf.org>; Mon, 25 Nov 2002 12:50:08 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 25 Nov 2002 17:46:34 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XKBY9AFN>; Mon, 25 Nov 2002 12:52:50 -0500
Message-ID: <B3FE60C05AD31D4C96E07EBC5000639E1D7FAC@EMSHQS2>
From: "Choi, Don" <choid@ncr.disa.mil>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: "'ieprep@ietf.org'" <ieprep@ietf.org>,
        "King, Kimberly  S."
	 <KIMBERLY.S.KING@saic.com>
Subject: RE: [Ieprep] problem context
Date: Mon, 25 Nov 2002 12:52:36 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ran,

The requirement for MLPP like service in internet (IP-based network) has
been part of IEPREP WG all along. The requirement exists for emergency
situations, and it should work over an IP-based network. 

Don


Don
-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Friday, November 22, 2002 7:38 AM
To: King, Kimberly S.
Cc: 'ieprep@ietf.org'
Subject: Re: [Ieprep] problem context



On Thursday, Nov 21, 2002, at 18:40 America/Montreal, King, Kimberly S. 
wrote:
> The context of "Internet Preparedness" is vast.  Some of the most 
> heated
> debates involve people with one context in mind talking to someone 
> else with
> a different one.  So, they talk past each other.

This is without question the case.

> Below is a beginning that I invite the WG to refine.  The purpose is to
> facilitate problem solving.  One can state "here is the context and 
> here is
> a problem where the default situation is insufficient to solve 
> emergency
> service X".
>
> 1.	N ETS locations with access links into the same ISP where the ISP
> offers CoS. Note that the particular ISP, access link bandwidth, and 
> local
> configurations can be determined in advance of the emergency.
>
> 2.	Emergency Worker accesses Internet via arbitrary connection (e.g.,
> Internet Cafe).  Note that the ISP providing connectivity to the 
> Internet
> cannot be determined in advance.
>
> 3.	A predetermined network is connected to a privately managed IP WAN
> over a predetermined constrained bandwidth connection (e.g., military 
> ship
> to Government owned IP network over Satellite)

This (3) is not an IEprep scenario.  It is a real-world military 
scenario,
just not an IEprep scenario.  And IEprep is NOT the MLPP WG.

(Aside: A suggestion I have made to the IESG is that they create a 
DiffServ Ops
WG that would be a home for evaluation/documentation of how the current
DiffServ protocol specs line up in practice with real-world operational 
networks.
Based on the output of that hypothetical WG, one could imagine that 
DiffServ specs
might be enhanced/tweaked/fixed based on real-world experience.  
DiffServ is
the obvious mechanism for item (3) above since it was used, albeit 
under another name,
some years back by US DoD to provide that capability [using Proteon 
routers if
memory serves].)

> 4.	A database available on the public Internet supporting emergency
> services/recovery (e.g., Japan's IAA)
>
> 5.	James Polk's topology scenarios
>
>
> While each case potentially involves some form of emergency 
> communications,

Item (3) describes military communications rather than emergency 
communications.
Military communications might (and do) have varying degrees of urgency
and precedence, but they aren't emergency communications.  Examples of
emergency communications would be from civilian organisations such as
Fire, Police, or FEMA.  Military networks might happen to carry some
messages related to a natural disaster, but that does not make such 
networks
IEprep networks.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 25 13:16:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14842
	for <ieprep-archive@odin.ietf.org>; Mon, 25 Nov 2002 13:16:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAPIIIC19767
	for ieprep-archive@odin.ietf.org; Mon, 25 Nov 2002 13:18:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPIIHv19764
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 25 Nov 2002 13:18:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14828
	for <ieprep-web-archive@ietf.org>; Mon, 25 Nov 2002 13:15:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPIH2v19731;
	Mon, 25 Nov 2002 13:17:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPIG2v19689
	for <ieprep@optimus.ietf.org>; Mon, 25 Nov 2002 13:16:02 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14671
	for <ieprep@ietf.org>; Mon, 25 Nov 2002 13:13:16 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18GNlh-0000OI-00; Mon, 25 Nov 2002 13:15:37 -0500
Date: Mon, 25 Nov 2002 13:15:37 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: "Choi, Don" <choid@ncr.disa.mil>
cc: "'RJ Atkinson'" <rja@extremenetworks.com>,
        "'ieprep@ietf.org'" <ieprep@ietf.org>,
        "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
Subject: RE: [Ieprep] problem context
In-Reply-To: <B3FE60C05AD31D4C96E07EBC5000639E1D7FAC@EMSHQS2>
Message-ID: <Pine.GSO.4.44.0211251314570.1495-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Mon, 25 Nov 2002, Choi, Don wrote:
> The requirement for MLPP like service in internet (IP-based network) has
> been part of IEPREP WG all along. The requirement exists for emergency
> situations, and it should work over an IP-based network.

At the BOF forming this working group, I thought MLPP was decided to be
out of scope of this working group.



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 25 13:18:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14983
	for <ieprep-archive@odin.ietf.org>; Mon, 25 Nov 2002 13:18:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAPIKIN19877
	for ieprep-archive@odin.ietf.org; Mon, 25 Nov 2002 13:20:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPIKIv19874
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 25 Nov 2002 13:20:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14959
	for <ieprep-web-archive@ietf.org>; Mon, 25 Nov 2002 13:17:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPIJ1v19821;
	Mon, 25 Nov 2002 13:19:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPIIIv19779
	for <ieprep@optimus.ietf.org>; Mon, 25 Nov 2002 13:18:18 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14829
	for <ieprep@ietf.org>; Mon, 25 Nov 2002 13:15:31 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.105])
	by gnat.inet.org (Postfix) with ESMTP
	id 1074167103; Mon, 25 Nov 2002 09:42:23 -0500 (EST)
Date: Mon, 25 Nov 2002 13:18:11 -0500
Subject: Re: [Ieprep] problem context
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep@ietf.org'" <ieprep@ietf.org>
To: "Choi, Don" <choid@ncr.disa.mil>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <B3FE60C05AD31D4C96E07EBC5000639E1D7FAC@EMSHQS2>
Message-Id: <4192A3BC-00A2-11D7-8F34-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, Nov 25, 2002, at 12:52 America/Montreal, Choi, Don wrote:
> The requirement for MLPP like service in internet (IP-based network) 
> has
> been part of IEPREP WG all along.

	Disagree.  It has NOT been here "all along".   It is an example
of "feature creep" or "charter creep".  I've been at each IEprep BOF
or WG meeting.  MLPP hasn't even been discussed at most of them.

	Also work specifying an MLPP mechanism is outside charter, since IEprep
does not do protocol design.

> The requirement exists for emergency
> situations, and it should work over an IP-based network.

	No.  That is also wrong. The requirement for emergency situations is 
that
the packets actually get delivered, NOT that anyone have, implement, or 
deploy
MLPP (or any other particular mechanism).

	The WG to address MLPP is probably DiffServ.  I infer that DoD/NCS 
folks haven't
succeeded (yet ?) in persuading DiffServ to specify something that 
DoD/NCS folks like.
None the less, DiffServ is the WG where MLPP mechanisms are most likely 
actually
to get specified and where desires for MLPP need to get expressed 
(assuming folks
want MLPP to actually happen inside IETF specs).  Earlier it sounded 
like you all
grasped this fact and were trying to work within DiffServ; I must have 
misunderstood.

	Given absence of much (any ?) present/likely future deployment of 
inter-domain
DiffServ, it is actually a good thing that emergency communications 
over the Internet
does not need or rely on MLPP.

Ran
rja@extremenetworks.com


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 25 15:48:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24635
	for <ieprep-archive@odin.ietf.org>; Mon, 25 Nov 2002 15:48:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAPKpGn28992
	for ieprep-archive@odin.ietf.org; Mon, 25 Nov 2002 15:51:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPKpGv28989
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 25 Nov 2002 15:51:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24613
	for <ieprep-web-archive@ietf.org>; Mon, 25 Nov 2002 15:48:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPKo6v28965;
	Mon, 25 Nov 2002 15:50:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPKnSv28933
	for <ieprep@optimus.ietf.org>; Mon, 25 Nov 2002 15:49:28 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA24584
	for <ieprep@ietf.org>; Mon, 25 Nov 2002 15:46:40 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 25 Nov 2002 20:43:07 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XKBY9HAP>; Mon, 25 Nov 2002 15:49:24 -0500
Message-ID: <B3FE60C05AD31D4C96E07EBC5000639E1D7FAE@EMSHQS2>
From: "Choi, Don" <choid@ncr.disa.mil>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: "'ieprep@ietf.org'" <ieprep@ietf.org>
Subject: RE: [Ieprep] problem context
Date: Mon, 25 Nov 2002 15:49:15 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ran,

Please check the minutes of the IEPREP BOF at SLC.

Don

-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Monday, November 25, 2002 1:18 PM
To: Choi, Don
Cc: 'ieprep@ietf.org'
Subject: Re: [Ieprep] problem context



On Monday, Nov 25, 2002, at 12:52 America/Montreal, Choi, Don wrote:
> The requirement for MLPP like service in internet (IP-based network) 
> has
> been part of IEPREP WG all along.

	Disagree.  It has NOT been here "all along".   It is an example
of "feature creep" or "charter creep".  I've been at each IEprep BOF
or WG meeting.  MLPP hasn't even been discussed at most of them.

	Also work specifying an MLPP mechanism is outside charter, since
IEprep
does not do protocol design.

> The requirement exists for emergency
> situations, and it should work over an IP-based network.

	No.  That is also wrong. The requirement for emergency situations is

that
the packets actually get delivered, NOT that anyone have, implement, or 
deploy
MLPP (or any other particular mechanism).

	The WG to address MLPP is probably DiffServ.  I infer that DoD/NCS 
folks haven't
succeeded (yet ?) in persuading DiffServ to specify something that 
DoD/NCS folks like.
None the less, DiffServ is the WG where MLPP mechanisms are most likely 
actually
to get specified and where desires for MLPP need to get expressed 
(assuming folks
want MLPP to actually happen inside IETF specs).  Earlier it sounded 
like you all
grasped this fact and were trying to work within DiffServ; I must have 
misunderstood.

	Given absence of much (any ?) present/likely future deployment of 
inter-domain
DiffServ, it is actually a good thing that emergency communications 
over the Internet
does not need or rely on MLPP.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 25 16:31:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26711
	for <ieprep-archive@odin.ietf.org>; Mon, 25 Nov 2002 16:31:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAPLY5331326
	for ieprep-archive@odin.ietf.org; Mon, 25 Nov 2002 16:34:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPLY5v31323
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 25 Nov 2002 16:34:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26656
	for <ieprep-web-archive@ietf.org>; Mon, 25 Nov 2002 16:31:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPLX1v31309;
	Mon, 25 Nov 2002 16:33:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPLWmv31231
	for <ieprep@optimus.ietf.org>; Mon, 25 Nov 2002 16:32:48 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26553
	for <ieprep@ietf.org>; Mon, 25 Nov 2002 16:29:59 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAPLVeae004685;
	Mon, 25 Nov 2002 16:31:40 -0500 (EST)
Date: Mon, 25 Nov 2002 16:31:40 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211252131.gAPLVeae004685@newdev.harvard.edu>
To: choid@ncr.disa.mil, rja@extremenetworks.com
Subject: RE: [Ieprep] problem context
Cc: ieprep@ietf.org, KIMBERLY.S.KING@saic.com
In-Reply-To: <B3FE60C05AD31D4C96E07EBC5000639E1D7FAC@EMSHQS2>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> The requirement for MLPP like service in internet (IP-based network) has
> been part of IEPREP WG all along. The requirement exists for emergency
> situations, and it should work over an IP-based network. 

there are two cases here

1/ convey PSTN-service specific info from a SIP node on an IP network
   to a IP-to-PSTN gateway for its use in signaling within the PSTN 
   network - this would include binary-indicators like GETS and
   multi-level ones like MLPP 

2/ use something other than best-effort service within an IP network
   (for example, on the access links)

#1 is part of the SIPPING requirements ID that is in WG last call

the need for #2 has been the object of vigorous discussion on this list 
but I think that it is in-scope to look at specific requirements
and at how those requirements could be met with existing IETF technology

note that existing IETF QoS-related technology is not limited to
best-effort and one other service so I do not think that any
chnages would be needed in such technology to support a 5-level
service like MLPP if that turns out to be useful in an IP network

(I have my doubts that there is much meaning to more than two
or three different services (best effort and one or two others) 
considering the nature of packet data networks) but I doubt that any limit 
in levels would be dictated by the technology itself)

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Mon Nov 25 16:40:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27096
	for <ieprep-archive@odin.ietf.org>; Mon, 25 Nov 2002 16:40:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAPLh0i32247
	for ieprep-archive@odin.ietf.org; Mon, 25 Nov 2002 16:43:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPLh0v32244
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 25 Nov 2002 16:43:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27044
	for <ieprep-web-archive@ietf.org>; Mon, 25 Nov 2002 16:40:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPLg1v32215;
	Mon, 25 Nov 2002 16:42:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPLfNv32183
	for <ieprep@optimus.ietf.org>; Mon, 25 Nov 2002 16:41:23 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27003
	for <ieprep@ietf.org>; Mon, 25 Nov 2002 16:38:35 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAPLeKbS004759
	for ieprep@ietf.org; Mon, 25 Nov 2002 16:40:20 -0500 (EST)
Date: Mon, 25 Nov 2002 16:40:20 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211252140.gAPLeKbS004759@newdev.harvard.edu>
To: ieprep@ietf.org
Subject: [Ieprep] this might be of interest to ieprep
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


From mailnull@www1.ietf.org  Mon Nov 25 16:41:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27141
	for <ieprep-archive@odin.ietf.org>; Mon, 25 Nov 2002 16:41:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAPLi2F32281
	for ieprep-archive@odin.ietf.org; Mon, 25 Nov 2002 16:44:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPLi2v32278
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 25 Nov 2002 16:44:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27124
	for <ieprep-web-archive@ietf.org>; Mon, 25 Nov 2002 16:41:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPLc0v32070;
	Mon, 25 Nov 2002 16:38:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPLblv32051
	for <ieprep@optimus.ietf.org>; Mon, 25 Nov 2002 16:37:47 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26886
	for <ieprep@ietf.org>; Mon, 25 Nov 2002 16:34:58 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAPLagrh004718;
	Mon, 25 Nov 2002 16:36:42 -0500 (EST)
Date: Mon, 25 Nov 2002 16:36:42 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211252136.gAPLagrh004718@newdev.harvard.edu>
To: choid@ncr.disa.mil, rja@extremenetworks.com
Subject: Re: [Ieprep] problem context
Cc: ieprep@ietf.org
In-Reply-To: <4192A3BC-00A2-11D7-8F34-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> The WG to address MLPP is probably DiffServ.

diffserv already can "support" MLPP if all that is wanted is 5 levels
of priority - as I just mentioned, I do not think that it makes much
sense to have 5 levels of priority in packet networks - I've not
seen any research that there is any useful differentation of services
as seen by the user

Scott



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 11:08:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08467
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 11:08:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQGAr404691
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 11:10:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQGArv04688
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 11:10:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08449
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 11:08:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQG9Ov04416;
	Tue, 26 Nov 2002 11:09:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQG8kv04333
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 11:08:46 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08190
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 11:05:58 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAQG9U2Q025440;
	Tue, 26 Nov 2002 08:09:30 -0800
Date: Tue, 26 Nov 2002 08:09:30 -0800
From: David Meyer <dmm@sprint.net>
To: Ottensmeyer Joerg <joerg.ottensmeyer@siemens.com>
Cc: ieprep@ietf.org
Message-ID: <20021126080930.K25275@sprint.net>
References: <47D438A0510BD611B9470002A58EDAE7CD4F7B@mchh2a6e.mchh.siemens.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <47D438A0510BD611B9470002A58EDAE7CD4F7B@mchh2a6e.mchh.siemens.de>; from joerg.ottensmeyer@siemens.com on Tue, Nov 26, 2002 at 03:30:02PM +0100
Content-Transfer-Encoding: 8bit
Subject: [Ieprep] Re: your presentation at IEPREP WG in Atlanta
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

	Joerg (copying the last as I've received a few requests),

	It is/has been at http://www.maoz.com/~dmm/IETF55/ieprep.

	Let me know if you have any proplems getting to it.

	Dave

On Tue, Nov 26, 2002 at 03:30:02PM +0100, Ottensmeyer Joerg wrote:
>> David,
>> 
>> could you please place your presentation at http://www.maoz.com/
>> as promised? 
>> 
>> Thanks in advance,
>> -Jörg
>> 
>>   
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 12:07:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11174
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 12:07:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQH9lg09877
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 12:09:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQH9lv09874
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 12:09:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11150
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 12:06:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQH8rv09786;
	Tue, 26 Nov 2002 12:08:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQH4Av08768
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 12:04:10 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10942
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 12:01:21 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAQH3Amo008694
	for ieprep@ietf.org; Tue, 26 Nov 2002 12:03:10 -0500 (EST)
Date: Tue, 26 Nov 2002 12:03:10 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211261703.gAQH3Amo008694@newdev.harvard.edu>
To: ieprep@ietf.org
Subject: [Ieprep] from the US homeland security bill (just signed into law)
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

these could be related to the work of ieprep (at least in the US)

------------------------
SEC. 508. USE OF NATIONAL PRIVATE SECTOR NETWORKS IN EMERGENCY RESPONSE.

  To the maximum extent practicable, the Secretary shall use national private
  sector networks and infrastructure for emergency response to chemical,   
  biological, radiological, nuclear, or explosive disasters, and other major
  disasters.

SEC. 509. USE OF COMMERCIALLY AVAILABLE TECHNOLOGY, GOODS, AND SERVICES.
It is the sense of Congress that--

(1) the Secretary should, to the maximum extent possible, use off-the-shelf
    commercially developed technologies to ensure that the Department's
    information technology systems allow the Department to collect, manage,
    share, analyze, and disseminate information securely over multiple channels
    of communication; and
(2) in order to further the policy of the United States to avoid competing
    commercially with the private sector, the Secretary should rely on
    commercial sources to supply the goods and services needed by the
    Department.

the whole bill is at http://thomas.loc.gov - search for HR 5005 and
select the ENR version

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 12:57:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13574
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 12:57:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQI0Ei12621
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 13:00:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQI0Ev12618
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 13:00:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13508
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 12:55:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQHvKv12472;
	Tue, 26 Nov 2002 12:57:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQHuWv12432
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 12:56:32 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13448
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 12:53:41 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <XDXAGAJ6>; Tue, 26 Nov 2002 12:54:04 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410AEB123A@chntex02.is.dyncorp.com>
From: "Berg, Dennis" <Dennis.Berg@DynCorp.com>
To: "'Scott  Bradner'" <sob@harvard.edu>, ieprep@ietf.org
Subject: RE: [Ieprep] from the US homeland security bill (just signed into
	 law)
Date: Tue, 26 Nov 2002 12:53:54 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Yes, these sections are a strong endorsement of the approach taken in GETS
and continued in Wireless Priority Service (WPS) extension of GETS that is
currently under development and deployment.  The National Communications
System, the agency that "owns" these programs, is now part of Homeland
Security.   

Dennis Berg
GETS IC Deputy Program Manager, Engineering
DynCorp IS
703-818-4608

 -----Original Message-----
From: 	Scott  Bradner [mailto:sob@harvard.edu] 
Sent:	Tuesday, November 26, 2002 12:03 PM
To:	ieprep@ietf.org
Subject:	[Ieprep] from the US homeland security bill (just signed
into law)

these could be related to the work of ieprep (at least in the US)

------------------------
SEC. 508. USE OF NATIONAL PRIVATE SECTOR NETWORKS IN EMERGENCY RESPONSE.

  To the maximum extent practicable, the Secretary shall use national
private
  sector networks and infrastructure for emergency response to chemical,   
  biological, radiological, nuclear, or explosive disasters, and other major
  disasters.

SEC. 509. USE OF COMMERCIALLY AVAILABLE TECHNOLOGY, GOODS, AND SERVICES.
It is the sense of Congress that--

(1) the Secretary should, to the maximum extent possible, use off-the-shelf
    commercially developed technologies to ensure that the Department's
    information technology systems allow the Department to collect, manage,
    share, analyze, and disseminate information securely over multiple
channels
    of communication; and
(2) in order to further the policy of the United States to avoid competing
    commercially with the private sector, the Secretary should rely on
    commercial sources to supply the goods and services needed by the
    Department.

the whole bill is at http://thomas.loc.gov - search for HR 5005 and
select the ENR version

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 16:02:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20529
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 16:02:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQL4sF25531
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 16:04:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQL4sv25528
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 16:04:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20517
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 16:02:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQL47v25457;
	Tue, 26 Nov 2002 16:04:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQL3Nv25379
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 16:03:23 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20454
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 16:00:33 -0500 (EST)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id gAQL2rsA003980;
	Tue, 26 Nov 2002 13:02:53 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ABI61542;
	Tue, 26 Nov 2002 13:00:44 -0800 (PST)
Date: Tue, 26 Nov 2002 13:03:07 -0800
Subject: Re: [Ieprep] problem context
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>,
        "'ieprep@ietf.org'" <ieprep@ietf.org>, Scott Bradner <sob@harvard.edu>
To: RJ Atkinson <rja@extremenetworks.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <2DAA6EB4-FE17-11D6-AC93-00039357A82A@extremenetworks.com>
Message-Id: <7639C35B-0182-11D7-BC8B-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ran,

[snip]
> This (3) is not an IEprep scenario.  It is a real-world military 
> scenario, just not an IEprep scenario.  And IEprep is NOT the MLPP WG.

I don't think I agree with your definition of an emergency, but your 
comment raises several important questions. One very important question 
is whether the scope of the IEPREP working group includes military 
emergencies/requirements. The charter is currently so vague that it can 
easily be interpreted either way. Hal seems to think the scope of the 
charter is just civilian emergencies (finally we find something for the 
two of you to agree about ;-).  Meanwhile, the ADs have blocked 
(military emergency) requirements work in SIPPING from progressing 
because "this requirements work should happen in IEPREP", and a WG item 
now in WGLC (draft-ietf-ieprep-sip-reqs) mentions both.

I don't feel there is anything especially sinister about dealing with 
military networking requirements provided the participants understand 
that the military will have to pay for their services just like 
everyone else. Certainly many of the requirements are similar, but I 
really don't care as long as we get a decision from the ADs or a 
consensus from the WG.  Whatever the outcome, I think the charter needs 
to get clarified.  My proposed text (for both possible outcomes) is 
below.

thanks,
-rohan


Civilian only:

> Effective telecommunications capabilities are imperative to facilitate 
> immediate recovery operations for serious disaster events, such as, 
> hurricanes, floods, earthquakes, and terrorist attacks. Disasters can 
> happen any time, any place, unexpectedly. Quick response for civilian 
> recovery operations requires immediate access to any public 
> telecommunications capabilities at hand. These capabilities include: 
> conventional telephone, cellular phones, and Internet access via 
> online terminals, IP telephones, and wireless PDAs. The commercial 
> telecommunications infrastructure is rapidly evolving to 
> Internet-based technology. Therefore, the Internet community needs to 
> consider how it can best support emergency management and recovery 
> operations.
>
> Three examples of emergency communications include:
>
> 1. Conveying information about the priority of specific phone calls 
> that originate in a VoIP environment through gateways to the PSTN.
>
> 2. Access and transport for database and information distribution 
> applications relevant to managing the crisis. One example of this is 
> the I am Alive (IAA) system that can be used by people in a disaster 
> zone to register the fact that they are alive so that their friends 
> and family can check on their health.
>
> 3. Interpersonal communication among crisis management personnel using 
> electronic mail and instant messaging.
>
> Initial documents will describe the problem space and its salient 
> characteristics. In particular the working group will develop a 
> Requirements for Internet Emergency Preparedness in the Internet RFC 
> which will detail the specific functions and technologies needed to 
> provide support for civilian Emergency Preparedness systems in the 
> Internet. Note that this Working Group will not address (possibly 
> similar) requirements for emergency communication in a military 
> environment. The working group may also develop a Framework for 
> Supporting Internet Emergency Preparedness in IP Telephony RFC if it 
> is determined that IP telephony requires special treatment above what 
> would be in the requirements document.
>
> The international community needs advice as to what standards to rely 
> on, in the form of a BCP. This BCP needs to identify mechanisms to 
> provide deterministic behavior of applications, mechanisms for 
> authentication and authorization, and recommendations for application 
> design with existing protocols. In the IETF considerations for 
> treatment and security of emergency communications stretch across a 
> number of Areas and Working Groups, notably including the various 
> telephony signaling working groups, Differentiated Services, Protocol 
> for carrying Authentication for Network Access (pana), and various 
> operational groups, so the IEPREP working group will have to cooperate 
> closely with these groups and with groups outside of the IETF such as 
> various ITU-T study groups.
>
> The working group will develop a BCP RFC or set of RFCs, regarding 
> operational implementation of services for Emergency Preparedness 
> using existing Internet protocols. The RFC may include identification 
> of gaps in existing protocols and requirements for use in new protocol 
> or protocol feature design. It is out of scope for this working group 
> to do protocol or protocol feature development. The working group will 
> not focus on particular national regulations.

Military too:

> Effective telecommunications capabilities are imperative to facilitate 
> immediate recovery operations for serious disaster events, such as, 
> hurricanes, floods, earthquakes, war, and terrorist attacks. Disasters 
> can happen any time, any place, unexpectedly. Quick response for 
> recovery operations requires immediate access to any public 
> telecommunications capabilities at hand. These capabilities include: 
> conventional telephone, cellular phones, privately-built emergency 
> communications networks, and Internet access via online terminals, IP 
> telephones, and wireless PDAs. The commercial telecommunications 
> infrastructure is rapidly evolving to Internet-based technology. 
> Therefore, the Internet community needs to consider how it can best 
> support emergency management and recovery operations in both civilian 
> and military settings.
>
> Three examples of emergency communications include:
>
> 1. Conveying information about the priority of specific phone calls 
> that originate in a VoIP environment through gateways to the PSTN.
>
> 2. Access and transport for database and information distribution 
> applications relevant to managing the crisis. One example of this is 
> the I am Alive (IAA) system that can be used by people in a disaster 
> zone to register the fact that they are alive so that their friends 
> and family can check on their health.
>
> 3. Interpersonal communication among crisis management personnel using 
> electronic mail and instant messaging.
>
> Initial documents will describe the problem space and its salient 
> characteristics. In particular the working group will devlop a 
> Requirements for Internet Emergency Preparedness in the Internet RFC 
> which will detail the specific functions and technologies needed to 
> provide support for Emergency Preparedness systems in the Internet. 
> The working group may also develop a Framework for Supporting Internet 
> Emergency Preparedness in IP Telephony RFC if it is determined that IP 
> telephony requires special treatment above what would be in the 
> requirements document.
>
> The international community needs advice as to what standards to rely 
> on, in the form of a BCP. This BCP needs to identify mechanisms to 
> provide deterministic behavior of applications, mechanisms for 
> authentication and authorization, and recommendations for application 
> design with existing protocols. In the IETF considerations for 
> treatment and security of emergency communications stretch across a 
> number of Areas and Working Groups, notably including the various 
> telephony signaling working groups, Differentiated Services, Protocol 
> for carrying Authentication for Network Access (pana), and various 
> operational groups, so the IEPREP working group will have to cooperate 
> closely with these groups and with groups outside of the IETF such as 
> various ITU-T study groups.
>
> The working group will develop a BCP RFC or set of RFCs, regarding 
> operational implementation of services for Emergency Preparedness 
> using existing Internet protocols. The RFC may include identification 
> of gaps in existing protocols and requirements for use in new protocol 
> or protocol feature design. It is out of scope for this working group 
> to do protocol or protocol feature development. The working group will 
> not focus on particular national regulations.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 16:13:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20981
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 16:13:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQLFjt26749
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 16:15:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLFjv26746
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 16:15:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20959
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 16:12:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLF5v26735;
	Tue, 26 Nov 2002 16:15:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLBkv26539
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 16:11:46 -0500
Received: from sj-msg-core-4.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20848
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 16:08:56 -0500 (EST)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id gAQLBXKc015612;
	Tue, 26 Nov 2002 13:11:33 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ABI61653;
	Tue, 26 Nov 2002 13:09:08 -0800 (PST)
Date: Tue, 26 Nov 2002 13:11:26 -0800
Subject: Re: [Ieprep] problem context
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: choid@ncr.disa.mil, rja@extremenetworks.com, ieprep@ietf.org
To: Scott  Bradner <sob@harvard.edu>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <200211252136.gAPLagrh004718@newdev.harvard.edu>
Message-Id: <9FE8CFF0-0183-11D7-BC8B-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

Along those lines, I don't think the goal of an MLPP service is to 
throw away bits according to diffserv-style priorities.  I think levels 
in a scheme like MLPP only make sense in an application specific 
context, possibly only in the context of audio media even....

thanks,
-rohan


On Monday, November 25, 2002, at 01:36 PM, Scott Bradner wrote:

>> The WG to address MLPP is probably DiffServ.
>
> diffserv already can "support" MLPP if all that is wanted is 5 levels
> of priority - as I just mentioned, I do not think that it makes much
> sense to have 5 levels of priority in packet networks - I've not
> seen any research that there is any useful differentation of services
> as seen by the user
>
> Scott
>
>
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 16:17:24 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21199
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 16:17:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQLJh827072
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 16:19:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLJhv27069
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 16:19:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21179
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 16:16:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLJ2v27019;
	Tue, 26 Nov 2002 16:19:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLIUv26978
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 16:18:30 -0500
Received: from sj-msg-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21063
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 16:15:40 -0500 (EST)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id gAQLIKu4004998
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 13:18:20 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ABI61755;
	Tue, 26 Nov 2002 13:16:00 -0800 (PST)
Date: Tue, 26 Nov 2002 13:18:22 -0800
Mime-Version: 1.0 (Apple Message framework v548)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: Rohan Mahy <rohan@cisco.com>
To: ieprep@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <97D97434-0184-11D7-BC8B-0003938AF740@cisco.com>
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] any commercial usage for "emergency QoS"?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

<soapbox>
One goal of IEPREP is to make applications used by emergency workers 
more likely to work in the event of an emergency. I am assuming that 
overall the group thinks disabling spam filters is out of scope  ;-). 
The core of the Internet would not be made faster at any time 
(especially during an emergency) by adding QoS there. In addition, most 
networks do not require QoS during ordinary usage, as their edges 
already work quite well by giving users their fair share of an ample 
amount of bandwidth.  During emergencies, there may be network outages 
and/or network congestion--specifically IP network congestion at access 
aggregation points such as DSLAMs, Cable Head End Routers, and Edge 
Aggregation Routers. If some very simple QoS scheme was applied at 
these points, this would improve the probability that applications with 
specific flows would continue to work well even under extraordinary 
congestion situations. For ISPs to deploy this type of QoS however, 
they need a financial incentive. Historically, demanding ISPs to deploy 
new services (such as QoS) by force or by moral suasion are unlikely to 
succeed. Therefore, a good way to test if a service is deployable is to 
see if there are multiple classes of consumer who might request that 
service.  In the case of emergency deployed QoS, certain governments 
may request such a service, but also possibly insurance companies, the 
press, and relief organizations.

In addition, any successful approach will probably start small and 
simple. If it is incrementally useful to get emergency QoS just at the 
first aggregation router from a handful of popular ISPs at the 
granularity of one week for one IP address or subnet, that is probably 
a good place to start.  That is much much much more likely to get 
deployed than per flow QoS end to end.
</soapbox>

I think it might be useful to ask ISPs how much they would have to 
charge (or how much it would cost them) to turn on something very 
simple at their aggregation routers only. You might be surprised by how 
much it will cost (a lot), and how far toward your goal that will 
probably get you (quite a long way).  I envision some large insurance 
company putting a few million dollars into an escrow account and paying 
a fixed price per IP address per week of usage, or prepaying every 
month or year with some "free" incidents each year and covering extra 
usage as needed (the cell phone model).

I also think it would be useful to evaluate the various qos tools in 
our rather dusty arsenal for *ease of implementation*. To put another 
way, considering one of Ran's messages from Nov 15th (snipped below), 
we probably want to only consider approach (B) where the actual 
mechanism the ISP would use to do this is already implemented in 
frequently deployed routers.

> Normally, (A) commercial customers tell equipment vendors that they 
> will purchase
> X million dollars of stuff if the vendor implements foo.  The vendor 
> figures out
> the cost (including opportunity cost) of implementing foo, compares 
> with revenue
> and ROI needs, then decides whether to implement foo for the customer.
>
> Normally, (B) commercial customers tell ISPs that they want to 
> purchase the
> foo service and ask what price it is available at.  The ISP then 
> decides
> whether they want to offer foo (or not) and provides a quote (iff they
> decide to offer foo).  @Home declined to offer a lot of the services 
> that
> we were asked to provide, normally because the opportunity cost was 
> too high.

thanks,
-rohan

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 16:27:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21707
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 16:27:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQLTQ327593
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 16:29:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLTQv27590
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 16:29:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21685
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 16:26:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLSgv27465;
	Tue, 26 Nov 2002 16:28:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLQTv27367
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 16:26:29 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21600
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 16:23:40 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAQLP5Sn009693;
	Tue, 26 Nov 2002 16:25:05 -0500 (EST)
Date: Tue, 26 Nov 2002 16:25:05 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211262125.gAQLP5Sn009693@newdev.harvard.edu>
To: rohan@cisco.com, sob@harvard.edu
Subject: Re: [Ieprep] problem context
Cc: choid@ncr.disa.mil, ieprep@ietf.org, rja@extremenetworks.com
In-Reply-To: <9FE8CFF0-0183-11D7-BC8B-0003938AF740@cisco.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> Along those lines, I don't think the goal of an MLPP service is to 
> throw away bits according to diffserv-style priorities.  I think levels 
> in a scheme like MLPP only make sense in an application specific 
> context, possibly only in the context of audio media even....

I expect you are right

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 16:31:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21833
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 16:31:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQLXjZ27833
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 16:33:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLXjv27830
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 16:33:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21814
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 16:30:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLX1v27802;
	Tue, 26 Nov 2002 16:33:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLWmv27730
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 16:32:48 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21765
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 16:29:58 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAQLUK56009732;
	Tue, 26 Nov 2002 16:30:20 -0500 (EST)
Date: Tue, 26 Nov 2002 16:30:20 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211262130.gAQLUK56009732@newdev.harvard.edu>
To: rja@extremenetworks.com, rohan@cisco.com
Subject: Re: [Ieprep] problem context
Cc: ieprep@ietf.org, KIMBERLY.S.KING@saic.com, sob@harvard.edu
In-Reply-To: <7639C35B-0182-11D7-BC8B-0003938AF740@cisco.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

rohan sez:
>  Whatever the outcome, I think the charter needs 
> to get clarified.  My proposed text (for both possible outcomes) is 
> below

> . . . 

kinda a long charter  :-)

but I do not see MLPP as meaning "military" - MLPP is an ITU
standard that could be used in a number of places - I just see
it as multi-level special handling

as far as progressing something in sipping, it would seem to be good to
wait to get the ieprep doc (soon now) then have sipping
think about the problem all at once (for SIP that is)

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 16:42:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22188
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 16:42:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQLiaZ28879
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 16:44:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLiav28876
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 16:44:36 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22184
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 16:41:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLi1v28864;
	Tue, 26 Nov 2002 16:44:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLhsv28850
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 16:43:54 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22172
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 16:41:04 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.105])
	by gnat.inet.org (Postfix) with ESMTP
	id 30B9267103; Tue, 26 Nov 2002 13:08:10 -0500 (EST)
Date: Tue, 26 Nov 2002 16:43:47 -0500
Subject: Re: [Ieprep] problem context
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Scott Bradner <sob@harvard.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211262125.gAQLP5Sn009693@newdev.harvard.edu>
Message-Id: <24850B44-0188-11D7-B29D-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 16:25 America/Montreal, Scott Bradner 
wrote:
>> Along those lines, I don't think the goal of an MLPP service is to
>> throw away bits according to diffserv-style priorities.  I think 
>> levels
>> in a scheme like MLPP only make sense in an application specific
>> context, possibly only in the context of audio media even....
>
> I expect you are right

	MLPP as implemented today in DSN ("AutoVon") actually throws away
existing live calls (the "pre-emption" part) if a trunk is out of
capacity and a higher precedence call appears on the scene.  MLPP
as formerly implemented in some DoD IP networks (~10 years back)
dropped lower precedence packets in order to avoid dropping higher
precedence packets when a link was underprovisioned relative to
offered load.

	It would be useful if Don would clarify more precisely what he
is looking for.  It could be either the quoted approach up top,
my (poor quality) summary of current/past DoD deployment, or something
else entirely.

Ran


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 16:57:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22556
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 16:57:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQLxNI29458
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 16:59:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLxMv29455
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 16:59:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22547
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 16:56:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLq0v29152;
	Tue, 26 Nov 2002 16:52:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLpJv29122
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 16:51:19 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22348
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 16:48:29 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.105])
	by gnat.inet.org (Postfix) with ESMTP
	id 9342267103; Tue, 26 Nov 2002 13:15:33 -0500 (EST)
Date: Tue, 26 Nov 2002 16:51:09 -0500
Subject: Re: [Ieprep] problem context
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep@ietf.org'" <ieprep@ietf.org>
To: "Choi, Don" <choid@ncr.disa.mil>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <B3FE60C05AD31D4C96E07EBC5000639E1D7FAE@EMSHQS2>
Message-Id: <2C15484A-0189-11D7-B29D-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, Nov 25, 2002, at 15:49 America/Montreal, Choi, Don wrote:
> Please check the minutes of the IEPREP BOF at SLC.

Don,

	One instance does not contradict my claim of "most".  There were
at least 3 separate BOFs for IEprep, which itself was a violation of the
normal IESG custom of only allowing 2 BOFs to any given proposal.  And
at SLC, that notion was shot up pretty broadly by IETF folks.

Mind, several IAB members at SLC each came away with the understanding 
that
"no WG would be created since there was clear community consensus to 
NOT create
this WG".  Obviously community input from the BOF was not the basis of 
the
IESG decision to charter this WG.

Mumble.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 16:59:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22676
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 16:59:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQM22g30010
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 17:02:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQM22v30003
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 17:02:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22667
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 16:59:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLn1v29043;
	Tue, 26 Nov 2002 16:49:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLm7v29010
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 16:48:07 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22278
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 16:45:17 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.105])
	by gnat.inet.org (Postfix) with ESMTP
	id ED8F767103; Tue, 26 Nov 2002 13:12:22 -0500 (EST)
Date: Tue, 26 Nov 2002 16:47:59 -0500
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Rohan Mahy <rohan@cisco.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <97D97434-0184-11D7-BC8B-0003938AF740@cisco.com>
Message-Id: <BB0C3FBA-0188-11D7-B29D-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 16:18 America/Montreal, Rohan Mahy wrote:
> I think it might be useful to ask ISPs how much they would have to 
> charge (or how much it would cost them) to turn on something very 
> simple at their aggregation routers only. You might be surprised by 
> how much it will cost (a lot), and how far toward your goal that will 
> probably get you (quite a long way).  I envision some large insurance 
> company putting a few million dollars into an escrow account and 
> paying a fixed price per IP address per week of usage, or prepaying 
> every month or year with some "free" incidents each year and covering 
> extra usage as needed (the cell phone model).

Did you see the presentations in Atlanta ?

 From them, one comes away with the understanding that Genuity and 
Sprint permit
class-based-queuing to be enabled on access routers at the request of 
the access
customer.  I imagine their existing pricing for this is public data.

Note well that IP ToS bits are likely to be zero'd whilst transiting a 
commercial
backbone, so marking packets' ToS bits is unlikely to be a widely 
deployable
approach.

> I also think it would be useful to evaluate the various qos tools in 
> our rather dusty arsenal for *ease of implementation*. To put another 
> way, considering one of Ran's messages from Nov 15th (snipped below), 
> we probably want to only consider approach (B) where the actual 
> mechanism the ISP would use to do this is already implemented in 
> frequently deployed routers.
>
>> Normally, (A) commercial customers tell equipment vendors that they 
>> will purchase
>> X million dollars of stuff if the vendor implements foo.  The vendor 
>> figures out
>> the cost (including opportunity cost) of implementing foo, compares 
>> with revenue
>> and ROI needs, then decides whether to implement foo for the customer.
>>
>> Normally, (B) commercial customers tell ISPs that they want to 
>> purchase the
>> foo service and ask what price it is available at.  The ISP then 
>> decides
>> whether they want to offer foo (or not) and provides a quote (iff they
>> decide to offer foo).  @Home declined to offer a lot of the services 
>> that
>> we were asked to provide, normally because the opportunity cost was 
>> too high.

Obviously I still take that posture.  However, I see that as a purely 
contractual
matter between USG and its (potential) suppliers -- not as an IETF 
matter.
It is a bad idea for IETF to get involved in business contractual 
issues like
this.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 17:05:01 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22853
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 17:05:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQM7Ku30713
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 17:07:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQM7Kv30710
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 17:07:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22838
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 17:04:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQM1Av29950;
	Tue, 26 Nov 2002 17:01:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQM0Lv29765
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 17:00:21 -0500
Received: from EXECDSL.COM (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22655
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 16:57:30 -0500 (EST)
Received: from [63.113.114.131] (HELO JLaptop.stevecrocker.com)
  by EXECDSL.COM (CommuniGate Pro SMTP 3.3)
  with ESMTP id 3996315 for ieprep@ietf.org; Tue, 26 Nov 2002 17:00:13 -0500
Message-Id: <5.1.0.14.0.20021126165219.017c0cc8@mail.stevecrocker.com>
X-Sender: joel@stevecrocker.com@mail.stevecrocker.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 26 Nov 2002 16:59:58 -0500
To: ieprep@ietf.org
From: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <97D97434-0184-11D7-BC8B-0003938AF740@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

I suspect I am misunderstanding the point you are getting at.  To the 
degree that we are talking about stuff in already deployed routers (which I 
think we are, and you suggest at the end of your note) there is nothing 
that IEPREP needs to do.


There are two different cases which need to be addressed in quite different 
ways:

1) The ability to enable Differentiated traffic treatment on an access link 
to a customer who wants it.  This is a well defined service.  It can be 
delivered with current technologies.  The user needs to negotiate with the 
access connected service provider, and may need some tech support from the 
CPE vendor (for directly purchased CPE).  Unless one can show a need for a 
new kind of treatment, we are done.

2) The ability to enable Differentiated traffic treatment on an arbitrary 
link at the time of an emergency.  While I can understand this 
conceptually, I can not imagine how it would be rolled out.  There is no 
contract between the emergency workers and the service provider controlling 
the access link.  There is no practical way to fund in advance the 
provisioning capabilities at every mom and pop ISP, wireless access 
provider, DSL provider, ... to provide this kind of capability.


I am missing how one could "start small".  There is no small set of folks 
who have access links that will happen to be in the vicinity of an 
emergency and probably not damaged by that emergency.  Someone probably has 
such links, but predicting who appears to be mathematically and financially 
intractable.

Note that all of this is about network level issues.  There may well be 
some useful application level enhancements for ubiquitous emergency services.

Yours,
Joel M. Halpern

At 01:18 PM 11/26/2002 -0800, Rohan Mahy wrote:
>Hi,
>
><soapbox>
>One goal of IEPREP is to make applications used by emergency workers more 
>likely to work in the event of an emergency. I am assuming that overall 
>the group thinks disabling spam filters is out of scope  ;-). The core of 
>the Internet would not be made faster at any time (especially during an 
>emergency) by adding QoS there. In addition, most networks do not require 
>QoS during ordinary usage, as their edges already work quite well by 
>giving users their fair share of an ample amount of bandwidth.  During 
>emergencies, there may be network outages and/or network 
>congestion--specifically IP network congestion at access aggregation 
>points such as DSLAMs, Cable Head End Routers, and Edge Aggregation 
>Routers. If some very simple QoS scheme was applied at these points, this 
>would improve the probability that applications with specific flows would 
>continue to work well even under extraordinary congestion situations. For 
>ISPs to deploy this type of QoS however, they need a financial incentive. 
>Historically, demanding ISPs to deploy new services (such as QoS) by force 
>or by moral suasion are unlikely to succeed. Therefore, a good way to test 
>if a service is deployable is to see if there are multiple classes of 
>consumer who might request that service.  In the case of emergency 
>deployed QoS, certain governments may request such a service, but also 
>possibly insurance companies, the press, and relief organizations.
>
>In addition, any successful approach will probably start small and simple. 
>If it is incrementally useful to get emergency QoS just at the first 
>aggregation router from a handful of popular ISPs at the granularity of 
>one week for one IP address or subnet, that is probably a good place to 
>start.  That is much much much more likely to get deployed than per flow 
>QoS end to end.
></soapbox>
>
>I think it might be useful to ask ISPs how much they would have to charge 
>(or how much it would cost them) to turn on something very simple at their 
>aggregation routers only. You might be surprised by how much it will cost 
>(a lot), and how far toward your goal that will probably get you (quite a 
>long way).  I envision some large insurance company putting a few million 
>dollars into an escrow account and paying a fixed price per IP address per 
>week of usage, or prepaying every month or year with some "free" incidents 
>each year and covering extra usage as needed (the cell phone model).
>
>I also think it would be useful to evaluate the various qos tools in our 
>rather dusty arsenal for *ease of implementation*. To put another way, 
>considering one of Ran's messages from Nov 15th (snipped below), we 
>probably want to only consider approach (B) where the actual mechanism the 
>ISP would use to do this is already implemented in frequently deployed routers.
>
>>Normally, (A) commercial customers tell equipment vendors that they will 
>>purchase
>>X million dollars of stuff if the vendor implements foo.  The vendor 
>>figures out
>>the cost (including opportunity cost) of implementing foo, compares with 
>>revenue
>>and ROI needs, then decides whether to implement foo for the customer.
>>
>>Normally, (B) commercial customers tell ISPs that they want to purchase the
>>foo service and ask what price it is available at.  The ISP then decides
>>whether they want to offer foo (or not) and provides a quote (iff they
>>decide to offer foo).  @Home declined to offer a lot of the services that
>>we were asked to provide, normally because the opportunity cost was too high.
>
>thanks,
>-rohan
>
>_______________________________________________
>Ieprep mailing list
>Ieprep@ietf.org
>https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 17:22:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23538
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 17:22:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQMOe831722
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 17:24:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMOev31719
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 17:24:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23533
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 17:21:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMO5v31663;
	Tue, 26 Nov 2002 17:24:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMKJv31509
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 17:20:19 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23369
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 17:17:28 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.105])
	by gnat.inet.org (Postfix) with ESMTP
	id 9CA2567103; Tue, 26 Nov 2002 13:44:33 -0500 (EST)
Date: Tue, 26 Nov 2002 17:20:10 -0500
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: "Joel M. Halpern" <joel@stevecrocker.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <5.1.0.14.0.20021126165219.017c0cc8@mail.stevecrocker.com>
Message-Id: <39D3862C-018D-11D7-B29D-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 16:59 America/Montreal, Joel M. Halpern 
wrote:
> Note that all of this is about network level issues.  There may well 
> be some useful application level enhancements for ubiquitous emergency 
> services.

Everything in Joel's note makes sense to me.  The last bit also applies 
to me
and I should mention it more often.  I'm pretty indifferent about what 
useless
gorp folks choose to put into SIP or other applications -- provided 
there is not
an increased in implemented/deployed gorp at the layers below the 
Application Layer.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 17:25:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23636
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 17:25:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQMRhM31853
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 17:27:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMRhv31849
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 17:27:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23628
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 17:24:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMR1v31829;
	Tue, 26 Nov 2002 17:27:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMQfv31810
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 17:26:41 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23607
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 17:23:50 -0500 (EST)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id gAQMQHsA027779;
	Tue, 26 Nov 2002 14:26:17 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ABI62787;
	Tue, 26 Nov 2002 14:24:08 -0800 (PST)
Date: Tue, 26 Nov 2002 14:26:30 -0800
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: RJ Atkinson <rja@extremenetworks.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <BB0C3FBA-0188-11D7-B29D-00039357A82A@extremenetworks.com>
Message-Id: <1CB4F5F4-018E-11D7-BC8B-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, November 26, 2002, at 01:47 PM, RJ Atkinson wrote:

>
> On Tuesday, Nov 26, 2002, at 16:18 America/Montreal, Rohan Mahy wrote:
>> I think it might be useful to ask ISPs how much they would have to 
>> charge (or how much it would cost them) to turn on something very 
>> simple at their aggregation routers only. You might be surprised by 
>> how much it will cost (a lot), and how far toward your goal that will 
>> probably get you (quite a long way).  I envision some large insurance 
>> company putting a few million dollars into an escrow account and 
>> paying a fixed price per IP address per week of usage, or prepaying 
>> every month or year with some "free" incidents each year and covering 
>> extra usage as needed (the cell phone model).
>
> Did you see the presentations in Atlanta ?

some of them, I had a conflict with SIMPLE.

> From them, one comes away with the understanding that Genuity and 
> Sprint permit
> class-based-queuing to be enabled on access routers at the request of 
> the access
> customer.  I imagine their existing pricing for this is public data.

that's not an opportunistic service.  the kind of service i am thinking 
of would be more like an emergency worker walking into a random 
internet cafe, convincing the manager to help him or her, and then 
somehow telling SBC, "PG&E will give you $10,000 if you configure your 
DSLAM nearest San Wherever, California to drop less traffic from ip 
address x.x.x.x for one week."  (for the curious, in california, SBC 
and PG&E offer residential DSL service and natural gas and electricity 
respectively).

i don't care if this happens because of a cellphone call to the SBC 
NOC, or because a few packets where exchanged.  however if a few 
packets are exchanged, we will end up with better interop (someone can 
contract with more providers more easily if they all use the same 
mechanism) if we decide what those packets are.

> Note well that IP ToS bits are likely to be zero'd whilst transiting a 
> commercial
> backbone, so marking packets' ToS bits is unlikely to be a widely 
> deployable
> approach.

agree that setting ToS bits and doing nothing else isn't useful. are 
you familiar with the RSVP DCLASS object?  (ask for RSVP but instead 
get told what diffserv you can keep without getting re-marked) I'm not 
proposing that as the answer, but it seems like a reasonable candidate 
to consider.

>> I also think it would be useful to evaluate the various qos tools in 
>> our rather dusty arsenal for *ease of implementation*. To put another 
>> way, considering one of Ran's messages from Nov 15th (snipped below), 
>> we probably want to only consider approach (B) where the actual 
>> mechanism the ISP would use to do this is already implemented in 
>> frequently deployed routers.
>>
>>> Normally, (A) commercial customers tell equipment vendors that they 
>>> will purchase
>>> X million dollars of stuff if the vendor implements foo.  The vendor 
>>> figures out
>>> the cost (including opportunity cost) of implementing foo, compares 
>>> with revenue
>>> and ROI needs, then decides whether to implement foo for the 
>>> customer.
>>>
>>> Normally, (B) commercial customers tell ISPs that they want to 
>>> purchase the
>>> foo service and ask what price it is available at.  The ISP then 
>>> decides
>>> whether they want to offer foo (or not) and provides a quote (iff 
>>> they
>>> decide to offer foo).  @Home declined to offer a lot of the services 
>>> that
>>> we were asked to provide, normally because the opportunity cost was 
>>> too high.
>
> Obviously I still take that posture.  However, I see that as a purely 
> contractual
> matter between USG and its (potential) suppliers -- not as an IETF 
> matter.
> It is a bad idea for IETF to get involved in business contractual 
> issues like
> this.

agreed 100%

thx,
-r

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 17:35:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24010
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 17:35:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQMc0A00374
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 17:38:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMc0v00371
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 17:38:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23989
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 17:35:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMb2v32275;
	Tue, 26 Nov 2002 17:37:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMabv32209
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 17:36:37 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23908
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 17:33:47 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.105])
	by gnat.inet.org (Postfix) with ESMTP
	id B768267103; Tue, 26 Nov 2002 14:00:53 -0500 (EST)
Date: Tue, 26 Nov 2002 17:36:30 -0500
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Rohan Mahy <rohan@cisco.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <1CB4F5F4-018E-11D7-BC8B-0003938AF740@cisco.com>
Message-Id: <81FCC758-018F-11D7-B29D-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 17:26 America/Montreal, Rohan Mahy wrote:
> agree that setting ToS bits and doing nothing else isn't useful. are 
> you familiar with the RSVP DCLASS object?  (ask for RSVP but instead 
> get told what diffserv you can keep without getting re-marked) I'm not 
> proposing that as the answer, but it seems like a reasonable candidate 
> to consider.

Not deployable.  Issues with authentication.  Also issues with 
inter-domain
traffic.  Also issues with too much state inside a deployed router.  
Also
issues with relying on QoS over a path that changes with time (due to 
dynamic
routing).

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 17:53:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24530
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 17:53:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQMu2700961
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 17:56:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMu2v00958
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 17:56:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24505
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 17:53:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMt1v00907;
	Tue, 26 Nov 2002 17:55:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMpqv00818
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 17:51:52 -0500
Received: from sj-msg-core-4.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24416
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 17:49:01 -0500 (EST)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id gAQMpjKc002372;
	Tue, 26 Nov 2002 14:51:45 -0800 (PST)
Received: from FRED-W2K6.cisco.com (stealth-10-32-253-236.cisco.com [10.32.253.236])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.2.0-GA)
	with SMTP id ACA31543;
	Tue, 26 Nov 2002 14:51:30 -0800 (PST)
Message-Id: <5.2.0.9.2.20021126141154.0199d7d8@mira-sjcm-4.cisco.com>
X-Sender: fred@mira-sjcm-4.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 26 Nov 2002 14:43:20 -0800
To: RJ Atkinson <rja@extremenetworks.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Cc: ieprep@ietf.org
In-Reply-To: <BB0C3FBA-0188-11D7-B29D-00039357A82A@extremenetworks.com>
References: <97D97434-0184-11D7-BC8B-0003938AF740@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

At 04:47 PM 11/26/2002 -0500, RJ Atkinson wrote:
> From them, one comes away with the understanding that Genuity and Sprint 
> permit class-based-queuing to be enabled on access routers at the request 
> of the access customer.  I imagine their existing pricing for this is 
> public data.

As far as I know, that is correct. AT&T and BT both also have had publicly 
offered services of that type for several years. AT&T and BT, BTW, appear 
to be the principal contributors pushing the efforts in ITU to normalize IP 
QoS between service providers, as discussed in

     ftp://ftpeng.cisco.com/fred/ieprep/IP_QOS_Summary_Nov_2002.pdf
     ftp://ftpeng.cisco.com/fred/ieprep/IP_QOS_Summary_Nov_2002.ppt

(use the ppt if you support powerpoint; the pdf is Huge)

Which is to say, I think, that while it is quite correct that US service 
providers tend to use overprovisioning in their cores, it is quite 
incorrect to say that no ISP uses QoS facilities, that QoS facilities 
should be deprecated, or that no ISP is interested in end to end QoS 
guarantees in IP. There are some service providers that would appear to 
want to rebuild ATM's service classes in IP.

>Note well that IP ToS bits are likely to be zero'd whilst transiting a 
>commercial backbone, so marking packets' ToS bits is unlikely to be a 
>widely deployable approach.

So they not only don't choose to use them, they actively break other 
people's use of them. Now *that's* Clueful. That is really demonstrating an 
interest in providing robust services to their clients. Lovely.


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 18:21:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26069
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 18:21:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQNO3t02726
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 18:24:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQNO3v02723
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 18:24:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26040
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 18:21:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQNI6v02434;
	Tue, 26 Nov 2002 18:18:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQNEwv02181
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 18:14:58 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25785
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 18:12:06 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 68DD567103; Tue, 26 Nov 2002 14:39:10 -0500 (EST)
Date: Tue, 26 Nov 2002 18:14:47 -0500
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Fred Baker <fred@cisco.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <5.2.0.9.2.20021126141154.0199d7d8@mira-sjcm-4.cisco.com>
Message-Id: <DAEF65F0-0194-11D7-8014-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 17:43 America/Montreal, Fred Baker wrote:
> Which is to say, I think, that while it is quite correct that US 
> service providers tend to use overprovisioning in their cores,

It is broader than that.  Most Asia/Pacific ISPs also over-provision.  
And
smd (who is Irish working in London) and roll (who is Swedish) have 
asserted
in the IEprep meeting that European ISPs and multi-continent ISPs also
routinely over-provision.

> it is quite incorrect to say that no ISP uses QoS facilities, that QoS 
> facilities should be deprecated, or that no ISP is interested in end 
> to end QoS guarantees in IP. There are some service providers that 
> would appear to want to rebuild ATM's service classes in IP.

Please suggest that those ISPs show up here so their views are 
presented directly.
Broader operator participation would have to be a good thing for IETF.

>> Note well that IP ToS bits are likely to be zero'd whilst transiting 
>> a commercial backbone, so marking packets' ToS bits is unlikely to be 
>> a widely deployable approach.
>
> So they not only don't choose to use them, they actively break other 
> people's use of them. Now *that's* Clueful. That is really 
> demonstrating an interest in providing robust services to their 
> clients. Lovely.

No, they are demonstrating an interest in protecting their own network 
from trivially
implemented DDOS attacks (as has been discussed recently on other lists 
that we are both
on) on the IP ToS bits.  This was explained quite nicely by Dave Meyer 
and others in
Atlanta in IEprep.  The issues also came up during the IEPG meeting 
before IETF in
Atlanta.  It seems like quite prudent system engineering to me and many 
other folks
present in Atlanta.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 18:39:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26770
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 18:39:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQNfNa04249
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 18:41:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQNfNv04246
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 18:41:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26761
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 18:38:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQNZ3v03305;
	Tue, 26 Nov 2002 18:35:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQNYcv03272
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 18:34:38 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26508
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 18:31:46 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <XDXAGBWJ>; Tue, 26 Nov 2002 18:32:11 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A414993@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>,
        Scott Bradner
	 <sob@harvard.edu>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] problem context
Date: Tue, 26 Nov 2002 18:32:01 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

It seems to me that MLPP is a technical solution to solve a particular
problem in a (fixed) circuit switched network.

Just as eMLPP is a different technical solution to solve a similar problem
in a (mobile) circuit switched network.

I am not sure that it makes sense to REPLICATE either MLPP or eMLPP in an IP
network.

However, it may very well be useful to identify an (IP specific) technical
solution that solves the same basic problem.

And it would DEFINITELY be useful to identify ways of interoperating with
MLPP and eMLPP across the relevant gateways.

-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Tuesday, November 26, 2002 4:44 PM
To: Scott Bradner
Cc: ieprep
Subject: Re: [Ieprep] problem context



On Tuesday, Nov 26, 2002, at 16:25 America/Montreal, Scott Bradner 
wrote:
>> Along those lines, I don't think the goal of an MLPP service is to
>> throw away bits according to diffserv-style priorities.  I think 
>> levels
>> in a scheme like MLPP only make sense in an application specific
>> context, possibly only in the context of audio media even....
>
> I expect you are right

	MLPP as implemented today in DSN ("AutoVon") actually throws away
existing live calls (the "pre-emption" part) if a trunk is out of
capacity and a higher precedence call appears on the scene.  MLPP
as formerly implemented in some DoD IP networks (~10 years back)
dropped lower precedence packets in order to avoid dropping higher
precedence packets when a link was underprovisioned relative to
offered load.

	It would be useful if Don would clarify more precisely what he
is looking for.  It could be either the quoted approach up top,
my (poor quality) summary of current/past DoD deployment, or something
else entirely.

Ran


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 18:39:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26789
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 18:39:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQNg1r04291
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 18:42:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQNg1v04286
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 18:42:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26784
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 18:39:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQNf3v04200;
	Tue, 26 Nov 2002 18:41:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQNeiv04162
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 18:40:44 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26718
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 18:37:52 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gAQNfMkt029471;
	Tue, 26 Nov 2002 15:41:22 -0800
Date: Tue, 26 Nov 2002 15:41:22 -0800
From: David Meyer <dmm@sprint.net>
To: Fred Baker <fred@cisco.com>
Cc: RJ Atkinson <rja@extremenetworks.com>, ieprep@ietf.org
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Message-ID: <20021126154122.A29205@sprint.net>
References: <5.2.0.9.2.20021126141154.0199d7d8@mira-sjcm-4.cisco.com> <DAEF65F0-0194-11D7-8014-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <DAEF65F0-0194-11D7-8014-00039357A82A@extremenetworks.com>; from rja@extremenetworks.com on Tue, Nov 26, 2002 at 06:14:47PM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

	Fred,

>> > Which is to say, I think, that while it is quite correct that US 
>> > service providers tend to use overprovisioning in their cores,

	My experience is that anyone who can (i.e., who isn't
	capacity constrained) would approach the problem in this
	way. BTW, a point on terminology: The approach many
	carriers are taking (what you and many others are calling
	"over-provisioning") is no more over-provisioning than
	say, the SONET network was/is; in fact, very much less so
	(and even less so when you consider the fiber occupancy
	on something like 4 fiber BLSR). So if you're in the
	business of delivering all packets to all customers, you
	have to protect the traffic. If you do that, you get the
	QoS properties for "free" (where "free" means "without
	additional mechanism"). That is one of the beautiful
	things about the IP architecture, lest we forget...  

>> It is broader than that.  Most Asia/Pacific ISPs also over-provision.  
>> And
>> smd (who is Irish working in London) and roll (who is Swedish) have 
>> asserted
>> in the IEprep meeting that European ISPs and multi-continent ISPs also
>> routinely over-provision.
>> 
>> > it is quite incorrect to say that no ISP uses QoS facilities, that QoS 
>> > facilities should be deprecated, or that no ISP is interested in end 
>> > to end QoS guarantees in IP. There are some service providers that 
>> > would appear to want to rebuild ATM's service classes in IP.
>> 
>> Please suggest that those ISPs show up here so their views are 
>> presented directly.
>> Broader operator participation would have to be a good thing for IETF.

	Most certainly. 

>> >> Note well that IP ToS bits are likely to be zero'd whilst transiting 
>> >> a commercial backbone, so marking packets' ToS bits is unlikely to be 
>> >> a widely deployable approach.
>> >
>> > So they not only don't choose to use them, they actively break other 
>> > people's use of them. Now *that's* Clueful. That is really 
>> > demonstrating an interest in providing robust services to their 
>> > clients. Lovely.
>> 
>> No, they are demonstrating an interest in protecting their own network 
>> from trivially
>> implemented DDOS attacks (as has been discussed recently on other lists 
>> that we are both
>> on) on the IP ToS bits.  This was explained quite nicely by Dave Meyer 
>> and others in
>> Atlanta in IEprep.  The issues also came up during the IEPG meeting 
>> before IETF in
>> Atlanta.  It seems like quite prudent system engineering to me and many 
>> other folks
>> present in Atlanta.

	To summarize the point, unless you want to touch every
	packet (*including* peers), there seems to be no straight
	forward (or any other) way to use the ToS bits in a way
	that can't be trivially DoS'ed. The crucial point here is
	that mandating the need to touch arbitrary parts of every
	packet will put fundamental limitations on the scalability
	of the network (along several dimensions), and I think we
	can all agree limiting our scalability isn't something
	that we want to do.

	Dave
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 19:01:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27702
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 19:01:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR044a05402
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 19:04:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR044v05399
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 19:04:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27679
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 19:01:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR035v05353;
	Tue, 26 Nov 2002 19:03:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR02hv05327
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 19:02:43 -0500
Received: from sj-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27568
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 18:59:51 -0500 (EST)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gAR02Zoh012676;
	Tue, 26 Nov 2002 16:02:35 -0800 (PST)
Received: from FRED-W2K6.cisco.com (stealth-10-32-253-236.cisco.com [10.32.253.236])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.2.0-GA)
	with SMTP id ACA37683;
	Tue, 26 Nov 2002 16:02:18 -0800 (PST)
Message-Id: <5.2.0.9.2.20021126154245.018bd9b8@mira-sjcm-4.cisco.com>
X-Sender: fred@mira-sjcm-4.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 26 Nov 2002 15:47:36 -0800
To: RJ Atkinson <rja@extremenetworks.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Cc: ieprep@ietf.org
In-Reply-To: <DAEF65F0-0194-11D7-8014-00039357A82A@extremenetworks.com>
References: <5.2.0.9.2.20021126141154.0199d7d8@mira-sjcm-4.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

At 06:14 PM 11/26/2002 -0500, RJ Atkinson wrote:
>No, they are demonstrating an interest in protecting their own network 
>from trivially
>implemented DDOS attacks (as has been discussed recently on other lists 
>that we are both
>on) on the IP ToS bits.

interesting. If they are ignoring the DSCP/TOS Flags, how would the 
settings of the DSCP/TOS Flags result in a DOS attack?

Pick one: they are ignoring the DSCP/TOS Flags, so that all IP traffic is 
equal, or they are not. Which is it? 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 19:52:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28768
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 19:52:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR0t9f08388
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 19:55:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR0t9v08385
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 19:55:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28765
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 19:52:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR0s6v08354;
	Tue, 26 Nov 2002 19:54:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR0rov08319
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 19:53:50 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28752
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 19:50:59 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id ED3B267103; Tue, 26 Nov 2002 16:17:51 -0500 (EST)
Date: Tue, 26 Nov 2002 19:53:18 -0500
Subject: Re: [Ieprep] problem context
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <CBED705A7FD2D311865500508B1089410A414993@chntex02.is.dyncorp.com>
Message-Id: <9E4DA8BC-01A2-11D7-8014-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 18:32 America/Montreal, Gunn, Janet wrote:
> It seems to me that MLPP is a technical solution to solve a particular
> problem in a (fixed) circuit switched network.
>
> Just as eMLPP is a different technical solution to solve a similar 
> problem
> in a (mobile) circuit switched network.
>
> I am not sure that it makes sense to REPLICATE either MLPP or eMLPP in 
> an IP
> network.
>
> However, it may very well be useful to identify an (IP specific) 
> technical
> solution that solves the same basic problem.
>
> And it would DEFINITELY be useful to identify ways of interoperating 
> with
> MLPP and eMLPP across the relevant gateways.

There are at least 2 (maybe more) different layers that one can use to 
consider this
question:  application-layer (e.g. SIP servers) and IP-layer.  I am 
very unclear
which of these is meant.  Some folks use "gateway" to mean a SIP 
gateway,
some to mean another application-layer gateway, and some to mean an IP 
router.

If we look at this as an IP-layer issue, then DiffServ/IP-ToS is an 
approach that
can work *within a single administrative domain*.  The security issues 
(e.g.
DDOS attack using IP ToS bits) are primarily a problem on an 
inter-domain
boundary.  Within a single administrative domain, the authorities for 
that
domain can use domain-specific policies and mechanisms to mitigate their
operational risk.

If we look at this as a SIP issue, then it seems like the main concern 
might
be to ensure that whatever markings are associated with a telephone call
are preserved (or modified only as appropriate at an administrative
boundary -- example:  country X might by policy disregard/remove 
markings
originating on an international call from country Y).  Because of our
layered architecture, having a call marked with some bit pattern inside
SIP does NOT automatically imply any change from best-effort handling by
the IP-layer.  It would not prohibit it, but neither would it 
automatically
imply such.

I'm not quite sure which of these (or maybe some other items) is the 
focus
of the concern at NCS, and which of these is the focus of the concern at
DISA Centre for Standards.  It would help if those perspectives could 
be made
more clearly.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 20:00:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28965
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 20:00:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR134b08701
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 20:03:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR134v08698
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 20:03:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28937
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 20:00:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR120v08668;
	Tue, 26 Nov 2002 20:02:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR0x9v08540
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 19:59:09 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28862
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 19:56:19 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 54CD567103; Tue, 26 Nov 2002 16:23:25 -0500 (EST)
Date: Tue, 26 Nov 2002 19:59:01 -0500
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Fred Baker <fred@cisco.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <5.2.0.9.2.20021126154245.018bd9b8@mira-sjcm-4.cisco.com>
Message-Id: <6AC7EF3E-01A3-11D7-8014-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 18:47 America/Montreal, Fred Baker wrote:

> At 06:14 PM 11/26/2002 -0500, RJ Atkinson wrote:
>> No, they are demonstrating an interest in protecting their own 
>> network from trivially
>> implemented DDOS attacks (as has been discussed recently on other 
>> lists that we are both
>> on) on the IP ToS bits.
>
> interesting. If they are ignoring the DSCP/TOS Flags, how would the 
> settings of the DSCP/TOS Flags result in a DOS attack?

Some ISP folks said that they use ToS bits internally to mark their own 
iBGP/IS-IS/OSPF/SNMP
packets and clear all ToS bits on all incoming packets at the 
administrative boundaries.
Some routers can provide routing protocol performance optimisations by 
having the
routing protocol packets appropriately marked.  I'm uninformed whether 
your routers
are among those.  I believe this was mentioned during IEprep, though 
maybe it was
during IEPG instead.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 20:04:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29027
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 20:04:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR16wo08816
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 20:06:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR16wv08813
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 20:06:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29015
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 20:04:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR162v08794;
	Tue, 26 Nov 2002 20:06:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR15Gv08771
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 20:05:16 -0500
Received: from imo-m04.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28998
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 20:02:25 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m04.mx.aol.com (mail_out_v34.13.) id j.145.38eaa26 (25508);
	Tue, 26 Nov 2002 20:04:58 -0500 (EST)
Message-ID: <145.38eaa26.2b15743a@aol.com>
Date: Tue, 26 Nov 2002 20:04:58 EST
To: rja@extremenetworks.com
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_145.38eaa26.2b15743a_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Subject: [Ieprep] Use of ToS bits for "emergency" preferential treatment
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_145.38eaa26.2b15743a_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/26/2002 4:50:34 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> Note well that IP ToS bits are likely to be zero'd whilst transiting a 
> commercial
> backbone, so marking packets' ToS bits is unlikely to be a widely deployable
> approach.
> 


Perhaps you could comment on the applicability/correctness of the following 
requirement out of the DoD Joint Technical Architecture document:

"In addition, all implementations of IP must pass the 8-bit Type-of-Service
(TOS) byte transparently up and down through the transport layer
as defined in IETF Standard 3, Host Requirements."

Mike Pierce
Artel


--part1_145.38eaa26.2b15743a_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/26/2002 4:50:34 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Note well that IP ToS bits are likely to be zero'd whilst transiting a commercial
<BR>backbone, so marking packets' ToS bits is unlikely to be a widely deployable
<BR>approach.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>Perhaps you could comment on the applicability/correctness of the following requirement out of the DoD Joint Technical Architecture document:
<BR>
<BR>"In addition, all implementations of IP must pass the 8-bit Type-of-Service
<BR>(TOS) byte transparently up and down through the transport layer
<BR>as defined in IETF Standard 3, Host Requirements."
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_145.38eaa26.2b15743a_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 20:10:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29121
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 20:10:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR1Cvq09614
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 20:12:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR1Cvv09611
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 20:12:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29118
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 20:10:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR1C1v09582;
	Tue, 26 Nov 2002 20:12:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR1Bav09565
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 20:11:36 -0500
Received: from imo-r05.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29106
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 20:08:45 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r05.mx.aol.com (mail_out_v34.13.) id j.111.1c499a44 (25508);
	Tue, 26 Nov 2002 20:09:54 -0500 (EST)
Message-ID: <111.1c499a44.2b157561@aol.com>
Date: Tue, 26 Nov 2002 20:09:53 EST
Subject: Re: [Ieprep] problem context
To: rja@extremenetworks.com, choid@ncr.disa.mil
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_111.1c499a44.2b157561_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_111.1c499a44.2b157561_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/26/2002 4:53:01 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> On Monday, Nov 25, 2002, at 15:49 America/Montreal, Choi, Don wrote:
> > Please check the minutes of the IEPREP BOF at SLC.
> 
> Don,
> 
>     One instance does not contradict my claim of "most".  There were
> at least 3 separate BOFs for IEprep, which itself was a violation of the
> normal IESG custom of only allowing 2 BOFs to any given proposal.  And
> at SLC, that notion was shot up pretty broadly by IETF folks.
> 
> Mind, several IAB members at SLC each came away with the understanding that
> "no WG would be created since there was clear community consensus to NOT 
> create
> this WG".  Obviously community input from the BOF was not the basis of the
> IESG decision to charter this WG.
> 
> 

As Don stated, MLPP was included in the report of the Salt Lake City #52 
meeting (in a BOF).

The Minneapolis (March 2002) #53 meeting report has several references to 
MLPP in th IEPREP WG, including a presentation by James Polk that referenced 
how the MLPP requirement could be met by the proposed Resource Priority 
Header.

At Yokohama #54 meeting, I made a presentation on the requirements for DoD 
"Assured Service" (aka MLPP).

At Atlanta #55 meeting, I made a presentation on Accounting requirements for 
"Priority services", which includes MLPP.

Incidentally, I don't follow your statement about there being 3 BOFs. As 
reported in Salt Lake City by Scott "The first time was at IETF 48". There 
was none at IETF 49, 50, or 51 (according to the agenda). So Salt Lake City 
was the second and Minneapolis was a WG meeting. In any case, as the SLC 
minutes state "The September 11, 2001 incident has crystallized more interest 
in emergency services." So what if there were 3, 4 or 10 BOFs to get enough 
people to understand that this issue is important?

The minutes of SLC indicate a lot of interest in the subject (many speakers), 
but I do not see any hint that there was "clear community consensus to NOT 
create the WG". I don't really see much in the minutes at all that I would 
classify as "the notion was shot up pretty broadly".

Further, I am unaware that the IAB has any part in a decision by the IETF to 
create a WG. If "several IAB members" have an opinion on this matter, I trust 
that they will not be tempted to use their position on the IAB to further 
their private positions or opinions.

Mike Pierce
Artel





--part1_111.1c499a44.2b157561_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/26/2002 4:53:01 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">On Monday, Nov 25, 2002, at 15:49 America/Montreal, Choi, Don wrote:
<BR>&gt; Please check the minutes of the IEPREP BOF at SLC.
<BR>
<BR>Don,
<BR>
<BR> &nbsp;&nbsp;&nbsp;One instance does not contradict my claim of "most". &nbsp;There were
<BR>at least 3 separate BOFs for IEprep, which itself was a violation of the
<BR>normal IESG custom of only allowing 2 BOFs to any given proposal. &nbsp;And
<BR>at SLC, that notion was shot up pretty broadly by IETF folks.
<BR>
<BR>Mind, several IAB members at SLC each came away with the understanding that
<BR>"no WG would be created since there was clear community consensus to NOT create
<BR>this WG". &nbsp;Obviously community input from the BOF was not the basis of the
<BR>IESG decision to charter this WG.
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>As Don stated, MLPP was included in the report of the Salt Lake City #52 meeting (in a BOF).
<BR>
<BR>The Minneapolis (March 2002) #53 meeting report has several references to MLPP in th IEPREP WG, including a presentation by James Polk that referenced how the MLPP requirement could be met by the proposed Resource Priority Header.
<BR>
<BR>At Yokohama #54 meeting, I made a presentation on the requirements for DoD "Assured Service" (aka MLPP).
<BR>
<BR>At Atlanta #55 meeting, I made a presentation on Accounting requirements for "Priority services", which includes MLPP.
<BR>
<BR>Incidentally, I don't follow your statement about there being 3 BOFs. As reported in Salt Lake City by Scott "The first time was at IETF 48". There was none at IETF 49, 50, or 51 (according to the agenda). So Salt Lake City was the second and Minneapolis was a WG meeting. In any case, as the SLC minutes state "The September 11, 2001 incident has crystallized more interest in emergency services." So what if there were 3, 4 or 10 BOFs to get enough people to understand that this issue is important?
<BR>
<BR>The minutes of SLC indicate a lot of interest in the subject (many speakers), but I do not see any hint that there was "clear community consensus to NOT create the WG". I don't really see much in the minutes at all that I would classify as "the notion was shot up pretty broadly".
<BR>
<BR>Further, I am unaware that the IAB has any part in a decision by the IETF to create a WG. If "several IAB members" have an opinion on this matter, I trust that they will not be tempted to use their position on the IAB to further their private positions or opinions.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR>
<BR>
<BR></FONT></HTML>

--part1_111.1c499a44.2b157561_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 20:45:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00997
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 20:45:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR1m2m11677
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 20:48:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR1m2v11674
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 20:48:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00951
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 20:45:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR1l2v11638;
	Tue, 26 Nov 2002 20:47:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR1klv11621
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 20:46:47 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00938
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 20:43:55 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAR1eXd06239;
	Tue, 26 Nov 2002 17:40:33 -0800 (PST)
Date: Tue, 26 Nov 2002 17:40:33 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: rja@extremenetworks.com, <ieprep@ietf.org>
Subject: Re: [Ieprep] Use of ToS bits for "emergency" preferential treatment
In-Reply-To: <145.38eaa26.2b15743a@aol.com>
Message-ID: <Pine.GSO.4.44.0211261740010.5153-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 26 Nov 2002 Mpierce1@aol.com wrote:
    > Perhaps you could comment on the applicability/correctness of the following
    > requirement out of the DoD Joint Technical Architecture document:
    > "In addition, all implementations of IP must pass the 8-bit Type-of-Service
    > (TOS) byte transparently up and down through the transport layer
    > as defined in IETF Standard 3, Host Requirements."

That's a host requirement, not a service provider requirement.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 20:56:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01319
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 20:56:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR1xGL12159
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 20:59:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR1xGv12156
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 20:59:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01313
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 20:56:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR1w7v12117;
	Tue, 26 Nov 2002 20:58:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR1v3v12071
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 20:57:03 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01262
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 20:54:12 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAR1oid06306;
	Tue, 26 Nov 2002 17:50:44 -0800 (PST)
Date: Tue, 26 Nov 2002 17:50:44 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Fred Baker <fred@cisco.com>
cc: RJ Atkinson <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <5.2.0.9.2.20021126154245.018bd9b8@mira-sjcm-4.cisco.com>
Message-ID: <Pine.GSO.4.44.0211261745580.5153-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > Pick one: they are ignoring the DSCP/TOS Flags, so that all IP traffic is
    > equal, or they are not. Which is it?

Both.  The Internet isn't monolithic.  Currently, the best practice is to
zero at the borders, which means that anyone following the best practice
is vulnerable only to attacks from their own customer base, if at all,
and they can use TOS bits inside their own infrastructure.  Everyone
who's not following the best practice can't use TOS bits because they're
being set from the outside.

If some sort of requirement were imposed which mandated inter-provider
carriage of un-zeroed TOS flags, that would be requiring everyone to
ignore the best-practice, and would make it unsafe for anyone to pay
attention to the TOS bits for anything.  It would also find us a lot of
bugs in a lot of people's router code, the painful way.  So that would be
completely self-defeating.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 20:59:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01390
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 20:59:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR21xM12321
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 21:01:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR21xv12318
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 21:01:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01377
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 20:59:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR217v12298;
	Tue, 26 Nov 2002 21:01:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR20Sv12249
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 21:00:28 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01344
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 20:57:37 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAR1xNwo010933;
	Tue, 26 Nov 2002 20:59:23 -0500 (EST)
Date: Tue, 26 Nov 2002 20:59:23 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211270159.gAR1xNwo010933@newdev.harvard.edu>
To: rja@extremenetworks.com, rohan@cisco.com
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Cc: ieprep@ietf.org
In-Reply-To: <81FCC758-018F-11D7-B29D-00039357A82A@extremenetworks.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> On Tuesday, Nov 26, 2002, at 17:26 America/Montreal, Rohan Mahy wrote:
> > agree that setting ToS bits and doing nothing else isn't useful. are 
> > you familiar with the RSVP DCLASS object?  (ask for RSVP but instead 
> > get told what diffserv you can keep without getting re-marked) I'm not 
> > proposing that as the answer, but it seems like a reasonable candidate 
> > to consider.
> 
> Not deployable.  Issues with authentication.  

I'm told that Windows includes DCLASS 
the assumption is that a *local* router tells the host what
diffserv DSCP to put on an application's packets

> Also issues with too much state inside a deployed router.

I would think this depends on what its being used for - apparently there 
is now enough experience with RSVP to signal MPLS to know that
it can scale to at least small # (100s anyway) of sessions -
if rsvp wer eto be used with the DSCP as the flowspec it might
scale well enough

btw - it would be good to get some *real* idea of what the load might be 
for a random router in various parts of an  ISP under what
conditions - for example, how many GETS calls were made in the NYC
area around sep 11? (and how many at the same time?)

that does not mean that the authentication and inter-ISP issues
are not signiicant issues

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 21:17:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01792
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 21:17:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR2JvG13393
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 21:19:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2Jvv13390
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 21:19:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01788
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 21:17:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2E4v13223;
	Tue, 26 Nov 2002 21:14:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2D9v13198
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 21:13:09 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01535
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 21:10:17 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gAR2C4I3010984;
	Tue, 26 Nov 2002 21:12:04 -0500 (EST)
Date: Tue, 26 Nov 2002 21:12:04 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211270212.gAR2C4I3010984@newdev.harvard.edu>
To: Mpierce1@aol.com, rja@extremenetworks.com
Subject: Re: [Ieprep] Use of ToS bits for "emergency" preferential treatment
Cc: ieprep@ietf.org
In-Reply-To: <145.38eaa26.2b15743a@aol.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> Perhaps you could comment on the applicability/correctness of the following 
> requirement out of the DoD Joint Technical Architecture document:

> "In addition, all implementations of IP must pass the 8-bit Type-of-Service
> (TOS) byte transparently up and down through the transport layer
> as defined in IETF Standard 3, Host Requirements."

OBE
	the 8-bit TOS field is no more
	6 bits are the differv DSCP (see RFC 2474)
	2 bits are ECN (see RFC 3168)

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 21:22:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01903
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 21:22:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR2P3x13563
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 21:25:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2P3v13560
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 21:25:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01887
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 21:22:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2O1v13521;
	Tue, 26 Nov 2002 21:24:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2N5v13497
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 21:23:05 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01854
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 21:20:13 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 1630367103; Tue, 26 Nov 2002 17:47:21 -0500 (EST)
Date: Tue, 26 Nov 2002 21:22:56 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <145.38eaa26.2b15743a@aol.com>
Message-Id: <2408087A-01AF-11D7-8014-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Re: ToS bits in STD-3
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 20:04 America/Montreal, Mpierce1@aol.com 
wrote:
> Perhaps you could comment on the applicability/correctness of the 
> following requirement out of the DoD Joint Technical Architecture 
> document:
>
> "In addition, all implementations of IP must pass the 8-bit 
> Type-of-Service
> (TOS) byte transparently up and down through the transport layer
> as defined in IETF Standard 3, Host Requirements."

Standard 3 == {RFC-1122, RFC-1123} with some updates.

Parts of STD3 are in fact badly out of date.  Several parts of it are 
defunct,
but there has never been enough energy in IETF to revisit the documents.

I gather the quoted text is from the DoD JTA document, because I'm 
unable
to locate that text in either RFC-1122 or RFC-1123.  RFC-1122 Section 
3.2.1.6
might be related.  That part of RFC-1122 is definitely updated/modified 
by
the latest DiffServ specifications, since the DiffServ RFCs changed the 
semantics
of the bit values from the original (DoD-centric) values specified in 
RFC-791.

The quoted text (from JTA ?) appears (to me) to require that an 
implementation of
IPv4 inside a host must be able to receive a ToS byte value from 
TCP/UDP/SCTP/OSPF
for outbound packets and must be able to send a ToS byte value from IPv4
upwards to the applicable transport layer protocol (e.g. TCP, UDP, SCTP,
or OSPF[1]).

The quoted text does not appear to make any requirements on a router
or a network operator, as near as I can tell, since STD 3 is the
Host Requirements RFC (pair of RFCs really).

In practice, many host stacks don't have much support for 
application-layer
selection of IP ToS on outbound sessions/packets or for informing 
applications
about the IP ToS that is in use on received packets for those incoming
sessions.  Since the most common API in use is the BSD-style Sockets API
(which has numerous slightly different implementations), if this 
capability
is a matter of concern then the first place to check on host support
for IP ToS values likely would be the sockets(3) page in the 
programming manual
for the computer system in use.

I happen to use an Apple running MacOS X, which is a kind of UNIX (more 
precisely
a Mach 3.0 kernel + BSD-compatibility subsystem + 4.4 BSD network 
stack).
I checked the man page for setsockopt(2), which is used to set Socket 
options.
I'm unable to locate any way to either retrieve or set the IP ToS byte 
using
getsockopt()/setsockopt().  I also looked into 
/usr/include/sys/socket.h and
~/socketvar.h -- could not immediately find any way to set/retrieve the 
IP ToS
byte there either.  A quick check of a Solaris system seems to indicate 
that
they at least support setting IP ToS if one uses the XTI API.  Unclear 
to me
at quick glance whether their Sockets API support such.

Ran
rja@extremenetworks.com

[1] OSPF is a routing protocol, but it sits directly on top of IP,
rather than on top of UDP, for historical reasons.  So it would need
to have the same capability to send an IP ToS byte down on packets
being sent out from the node.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 21:30:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02065
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 21:30:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR2X8913847
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 21:33:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2X8v13844
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 21:33:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02062
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 21:30:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2W1v13802;
	Tue, 26 Nov 2002 21:32:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2Vov13783
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 21:31:50 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02035
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 21:28:59 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 7739667103; Tue, 26 Nov 2002 17:56:06 -0500 (EST)
Date: Tue, 26 Nov 2002 21:31:42 -0500
Subject: Re: [Ieprep] problem context
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <111.1c499a44.2b157561@aol.com>
Message-Id: <5D3F8348-01B0-11D7-8014-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 20:09 America/Montreal, Mpierce1@aol.com 
wrote:
> So what if there were 3, 4 or 10 BOFs to get enough people to 
> understand
> that this issue is important?

IETF custom is that no proposal gets more than 2 BOFs.

And the community did not agree that the issue is important.  Creation
of a WG is at the discretion of the IESG, which normally listens to
community input.  But please, lets not go there...

> Further, I am unaware that the IAB has any part in a decision by the 
> IETF to create a WG.

Correct.  It does not.  RFC-2026 is *very* clear on this point.  For my 
part,
I am repeatedly on the record as believing that it is a huge feature 
that IAB
does not make these decisions.  And I've repeatedly declined to stand 
for the IESG,
including declining a nomination to the IESG this very month.

> If "several IAB members" have an opinion on this matter, I trust that 
> they will not be tempted to use their position on the IAB to further 
> their private positions or opinions.

IAB has no power over the IETF standards process, except in the narrow 
situation
of hearing an appeal of IESG decisions.  I am also on the record 
repeatedly in
saying that this also is a huge feature for the IAB.  Further, there is 
a clear
track record that IAB members who were directly involved in an appeal 
chain recuse
themselves.[1]

So there is no mechanism via which someone on the IAB could further any 
IETF
position even if one should want to do so.  Now the IESG are in a 
somewhat
different situation since they *are* the ones who manage the IETF 
standards
process.

Ran
rja@extremenetworks.com

[1] A fine example would be the appeal by W.A. Simpson.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 21:33:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02249
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 21:33:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR2aHv13955
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 21:36:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2aHv13952
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 21:36:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02183
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 21:33:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2Z2v13905;
	Tue, 26 Nov 2002 21:35:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2YGv13877
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 21:34:16 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02096
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 21:31:23 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 0E41867103; Tue, 26 Nov 2002 17:58:13 -0500 (EST)
Date: Tue, 26 Nov 2002 21:33:35 -0500
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: <ieprep@ietf.org>
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211261745580.5153-100000@paixhost.pch.net>
Message-Id: <A0F11C38-01B0-11D7-8014-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Bill,

	By the way, during the Nairobi VoIP demo in Atlanta, was there any use
of IP ToS bits, DiffServ, or other QoS ?

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 21:36:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02488
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 21:36:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR2d0f14670
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 21:39:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2cxv14667
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 21:38:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02474
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 21:36:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2c1v14632;
	Tue, 26 Nov 2002 21:38:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2blv14612
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 21:37:47 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02367
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 21:34:55 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAR2VYd06706;
	Tue, 26 Nov 2002 18:31:34 -0800 (PST)
Date: Tue, 26 Nov 2002 18:31:34 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <A0F11C38-01B0-11D7-8014-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211261830490.6547-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > By the way, during the Nairobi VoIP demo in Atlanta, was there any
    > use of IP ToS bits, DiffServ, or other QoS ?

Nope.  We wanted it to work.  Demos which fail aren't as impressive.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 21:40:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02575
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 21:40:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR2h6l14789
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 21:43:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2h5v14786
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 21:43:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02565
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 21:40:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2b0v14034;
	Tue, 26 Nov 2002 21:37:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2aKv13967
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 21:36:20 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02190
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 21:33:28 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAR2U6d06683;
	Tue, 26 Nov 2002 18:30:06 -0800 (PST)
Date: Tue, 26 Nov 2002 18:30:06 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Rohan Mahy <rohan@cisco.com>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <97D97434-0184-11D7-BC8B-0003938AF740@cisco.com>
Message-ID: <Pine.GSO.4.44.0211261827530.6547-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Tue, 26 Nov 2002, Rohan Mahy wrote:
    > I think it might be useful to ask ISPs how much they would have to
    > charge (or how much it would cost them) to turn on something very
    > simple at their aggregation routers only. You might be surprised by how
    > much it will cost (a lot)...

Anyone who goes to the trouble to ask that question subsequently draws the
inescapable conclusion that spending less money to buy more bandwidth
solves the problem better.  With luck the guys with funny hats and guns
will ask the question soon, so we can get back to work.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 21:45:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02692
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 21:45:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR2m9515085
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 21:48:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2m9v15082
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 21:48:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02683
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 21:45:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2l1v15008;
	Tue, 26 Nov 2002 21:47:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2k3v14956
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 21:46:03 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02650
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 21:43:11 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 41CDB67103; Tue, 26 Nov 2002 18:10:18 -0500 (EST)
Date: Tue, 26 Nov 2002 21:45:53 -0500
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Scott Bradner <sob@harvard.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211270159.gAR1xNwo010933@newdev.harvard.edu>
Message-Id: <58DA2858-01B2-11D7-8014-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 20:59 America/Montreal, Scott Bradner 
wrote:
>> On Tuesday, Nov 26, 2002, at 17:26 America/Montreal, Rohan Mahy wrote:
>>> agree that setting ToS bits and doing nothing else isn't useful. are
>>> you familiar with the RSVP DCLASS object?  (ask for RSVP but instead
>>> get told what diffserv you can keep without getting re-marked) I'm 
>>> not
>>> proposing that as the answer, but it seems like a reasonable 
>>> candidate
>>> to consider.
>>
>> Not deployable.  Issues with authentication.
>
> I'm told that Windows includes DCLASS
> the assumption is that a *local* router tells the host what
> diffserv DSCP to put on an application's packets

Weird.  If the first-hop router is the source of the policy knowledge,
it would be much easier for the router to just modify the IP ToS bits.
A modern router or L3 switch ought to be able to do that rewriting
on every packet while still sustaining full line rate 
forwarding/bridging.
And the first-hop router/L3 switch would need to police the values
in any event.

>> Also issues with too much state inside a deployed router.
>
> I would think this depends on what its being used for - apparently 
> there
> is now enough experience with RSVP to signal MPLS to know that
> it can scale to at least small # (100s anyway) of sessions -
> if rsvp wer eto be used with the DSCP as the flowspec it might
> scale well enough

I'm a bit sceptical, but would be interested to learn more.  I'm unaware
of any commercial ISP with that much (RSVP-based MPLS) in operation in 
their
deployed network.  Is there a URL or paper supporting this claim ?

> btw - it would be good to get some *real* idea of what the load might 
> be
> for a random router in various parts of an  ISP under what
> conditions - for example, how many GETS calls were made in the NYC
> area around sep 11? (and how many at the same time?)

Yes.  Having real measured data of how a router performed with RSVP
enabled in such a situation would be helpful.  Of course, one would
also want to subject the router to one of the trivial RSVP-based attacks
at the same time, since routers being under attack in times of stress
is something one should plan for.

> that does not mean that the authentication and inter-ISP issues
> are not signiicant issues

Also, deploying RSVP itself creates new security issues.  Those are
a bit more tractable, since there is an MD5 authentication option
for RSVP, though key management remains its usual nightmare.  And
for an IP network based on commercial products, the sundry alternatives
used only in the military world aren't available to help with KM.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 21:47:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02735
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 21:47:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR2oF115165
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 21:50:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2oFv15162
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 21:50:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02722
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 21:47:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2nGv15126;
	Tue, 26 Nov 2002 21:49:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2mlv15103
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 21:48:47 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02706
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 21:45:55 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id A694D67103; Tue, 26 Nov 2002 18:13:02 -0500 (EST)
Date: Tue, 26 Nov 2002 21:48:38 -0500
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211261830490.6547-100000@paixhost.pch.net>
Message-Id: <BAD75957-01B2-11D7-8014-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 21:31 America/Montreal, Bill Woodcock 
wrote:

>> By the way, during the Nairobi VoIP demo in Atlanta, was there any
>> use of IP ToS bits, DiffServ, or other QoS ?
>
> Nope.  We wanted it to work.  Demos which fail aren't as impressive.

So the demo might be an existance proof that VoIP works fine over
a set of best-effort IP networks across 2-3 continents ?

Do you happen to have a traceroute handy for that to document how
many ASs, hops, and continents that the demo traversed ?  (Feel free
to omit the last few IP addresses since this list is permanently 
archived;
we don't want to accidentally encourage bored folks to attack the
innocent user in Nairobi).

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 21:55:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02915
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 21:55:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR2wL415377
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 21:58:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2wKv15374
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 21:58:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02883
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 21:55:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2v3v15345;
	Tue, 26 Nov 2002 21:57:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR2u9v15314
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 21:56:09 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02865
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 21:53:17 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAR2nvd06980;
	Tue, 26 Nov 2002 18:49:57 -0800 (PST)
Date: Tue, 26 Nov 2002 18:49:57 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <BAD75957-01B2-11D7-8014-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211261844030.6731-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > Do you happen to have a traceroute handy for that to document how
    > many ASs, hops, and continents that the demo traversed ?

We had the slide (which I'll put up permanently) showing how many hops,
AS path length, loss, and latency across a full-mesh of myself, Scott
Bradner, Patrik Faltstrom, and Brian Longwe.  We also have a traceroute
(attached) from the day before, showing the path from Nairobi to the
hotel.  Both times we were getting variable loss, up to about 40%.
Most of those outward-facing IPs seem to be ICMP-blocked, so that's a
little hard to replicate at the moment.

                                -Bill



  1     6 ms     3 ms     3 ms  192.168.14.1
  2    13 ms    15 ms    16 ms  64.86.232.121
  3    41 ms    54 ms    30 ms  64.86.231.9
  4    27 ms    70 ms    48 ms  64.86.231.1
  5   622 ms   636 ms   619 ms  212.49.70.105
  6   641 ms   618 ms   620 ms  216.129.151.150
  7   619 ms   593 ms   642 ms  216.129.151.149
  8   621 ms   627 ms   634 ms  216.129.150.249
  9   635 ms   613 ms   602 ms  66.133.0.45
 10   614 ms   602 ms   696 ms  209.244.160.241
 11   612 ms   645 ms   612 ms  64.159.17.38
 12   639 ms   609 ms   631 ms  209.244.160.150
 13   608 ms   621 ms   660 ms  129.250.3.48
 14   639 ms   620 ms   656 ms  129.250.5.99
 15   648 ms   641 ms   644 ms  129.250.2.180
 16   643 ms   628 ms   643 ms  129.250.2.49
 17   671 ms   636 ms   674 ms  129.250.26.227
 18   633 ms   641 ms   655 ms  157.238.161.202
 19   672 ms   639 ms   646 ms  204.42.70.246


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Nov 26 22:01:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03006
	for <ieprep-archive@odin.ietf.org>; Tue, 26 Nov 2002 22:01:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR348s15554
	for ieprep-archive@odin.ietf.org; Tue, 26 Nov 2002 22:04:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR348v15551
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 22:04:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03003
	for <ieprep-web-archive@ietf.org>; Tue, 26 Nov 2002 22:01:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR332v15511;
	Tue, 26 Nov 2002 22:03:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR32Lv15485
	for <ieprep@optimus.ietf.org>; Tue, 26 Nov 2002 22:02:21 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02948
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 21:59:29 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 29B9C67103; Tue, 26 Nov 2002 18:26:37 -0500 (EST)
Date: Tue, 26 Nov 2002 22:02:12 -0500
Subject: Re: [Ieprep] Use of ToS bits for "emergency" preferential treatment
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Scott Bradner <sob@harvard.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <200211270212.gAR2C4I3010984@newdev.harvard.edu>
Message-Id: <A05D6DE6-01B4-11D7-8014-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Tuesday, Nov 26, 2002, at 21:12 America/Montreal, Scott Bradner 
wrote:
> OBE
> 	the 8-bit TOS field is no more
> 	6 bits are the differv DSCP (see RFC 2474)
> 	2 bits are ECN (see RFC 3168)

Scott's comments are all true, where OBE == "Overtaken By Events".

Separately, at least some existing commercial IP routers can still be 
configured
to use the RFC-791 precedence bit settings.  And at least one router is 
still
available that supports the full RFC-791 IP ToS bit settings, including 
with IGP
support for ToS-based IP routing -- this last still has significantly 
deployment
by one US uniformed service for its WAN  tactical links, though I assume
that it is gradually fading away from the installed base of routers.

Many IP routers/L3 switches can be configured to set/clear/reset the IP 
ToS
or DiffServ byte, generally based on ACLs configured by the router 
administrator.
Of course, the details of the configuration method vary from vendor to 
vendor
and there are performance/other differences among various 
implementations.
The better L3 switches/routers can generally also map QoS values in 
either
direction between IP ToS bits and IEEE 802.1p precedence bits, 
honouring either
set of bits or the ACL for class based queuing inside the L3 
switch/router.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 00:14:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05719
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 00:14:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR5H2v21639
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 00:17:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR5H2v21636
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 00:17:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05706
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 00:14:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR5DGv21508;
	Wed, 27 Nov 2002 00:13:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR5Clv21476
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 00:12:47 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05652
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 00:09:53 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id gAR4xVAv008827
	for <ieprep@ietf.org>; Tue, 26 Nov 2002 23:11:29 -0600 (CST)
Received: from OCCLUST03EVS1.ugd.att.com (135.71.164.11) by attrh3i.attrh.att.com (6.5.019)
        id 3DDD63A100249FA0; Wed, 27 Nov 2002 00:11:27 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [Ieprep] any commercial usage for "emergency QoS"?
Date: Wed, 27 Nov 2002 00:10:50 -0500
Message-ID: <456FD0E7B215B24ABBAD711614E4A7A20160983A@OCCLUST03EVS1.ugd.att.com>
Thread-Topic: [Ieprep] any commercial usage for "emergency QoS"?
Thread-Index: AcKVsd6ofusIDjtvTrSacYxMC8WZhAABWhOA
From: "Dvorak, Charles A (Chuck), ALASO" <cdvorak@att.com>
To: "Fred Baker" <fred@cisco.com>
Cc: <ieprep@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAR5Clv21477
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Fred

You said: 

> (snip) AT&T and BT both also have had publicly 
> offered services of that type for several years. AT&T and BT, 
> BTW, appear 
> to be the principal contributors pushing the efforts in ITU 
> to normalize IP 
> QoS between service providers, as discussed in
> 
>      ftp://ftpeng.cisco.com/fred/ieprep/IP_QOS_Summary_Nov_2002.pdf
>      ftp://ftpeng.cisco.com/fred/ieprep/IP_QOS_Summary_Nov_2002.ppt
> 

I am not sure what you are trying to say in singling out AT&T and BT as
"pushing the efforts in ITU to normalize IP QoS between" service
providers, but as I see them here are the facts:

The contribution to the ITU proposing a requirements document for
end-to-end signaling of QoS for the IP layer was a USA position. True,
the initial contribution on these requirements was made by AT&T, but it
was actively edited and then the support for making it a USA position
was *unanimous*, with Cisco and many others in attendance and voicing no
objection. 

In any event, whether such a protocol is ever developed and/or used to
negotiate and deliver end-to-end QoS remains to be seen, but a service
provider needs to be able to deliver the requisite IP network
performance to support interactive voice and data applications, and do
so in a multi-carrier environment in which no one has control over all
bottlenecks in the end-to-end path. 

As per Sprint's presentation, our IP backbone is lightspeed and lossless
and we do some QoS stuff on access. While it works very well today, we
want a Plan B in case in the future it becomes necessary to use
end-to-end protocols to deliver the QoS users want. There are certainly
many issues. All this is being addressed in T1 and the ITU because the
IETF has been antagonistic to such a protocol (and we respect the
reasons articulated for such opposition, so we work this elsewhere).

Chuck Dvorak

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 02:46:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02682
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 02:46:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAR7mhI05536
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 02:48:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR7mgv05533
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 02:48:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02662
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 02:45:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR7m3v05510;
	Wed, 27 Nov 2002 02:48:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAR7lEv05468
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 02:47:14 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02629
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 02:44:20 -0500 (EST)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id gAR7kf0J014421;
	Tue, 26 Nov 2002 23:46:41 -0800 (PST)
Received: from FRED-W2K6.cisco.com (stealth-10-32-253-236.cisco.com [10.32.253.236])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.2.0-GA)
	with SMTP id ACA58362;
	Tue, 26 Nov 2002 23:46:42 -0800 (PST)
Message-Id: <5.2.0.9.2.20021126233249.018cab10@mira-sjcm-4.cisco.com>
X-Sender: fred@mira-sjcm-4.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 26 Nov 2002 23:34:19 -0800
To: Scott  Bradner <sob@harvard.edu>
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Cc: ieprep@ietf.org
In-Reply-To: <200211270159.gAR1xNwo010933@newdev.harvard.edu>
References: <81FCC758-018F-11D7-B29D-00039357A82A@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

At 08:59 PM 11/26/2002 -0500, Scott  Bradner wrote:
>I would think this depends on what its being used for - apparently there
>is now enough experience with RSVP to signal MPLS to know that
>it can scale to at least small # (100s anyway) of sessions -

actually, tens of thousands per router. How many edge routers surround an 
ISP? We have some customers that go CPE-CPE.

I'm not an MPLS advocate, but it does actually work... 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 05:25:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05086
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 05:25:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARAS5n14196
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 05:28:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARAS4v14193
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 05:28:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05077
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 05:25:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARAR5v14147;
	Wed, 27 Nov 2002 05:27:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARAPsv14100
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 05:25:54 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA05050
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 05:23:09 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 27 Nov 2002 10:19:33 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XKBY0WTY>; Wed, 27 Nov 2002 05:25:55 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D8E@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Bill Woodcock '" <woody@pch.net>,
        "'RJ Atkinson '"
	 <rja@extremenetworks.com>
Cc: "'ieprep@ietf.org '" <ieprep@ietf.org>
Subject: RE: [Ieprep] any commercial usage for "emergency QoS"?
Date: Wed, 27 Nov 2002 05:25:49 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Bill,

Sorry I was not there for the demos. I wondered if you took into account the
peak internet usage time when you gave the demos. I heard the demos were
given around 4:00PM EST( please correct me if I am wrong). That would have
been around 3:00 or 4:00 AM in Nairobi??? Do you consider those two time
zones are in the peak usage intervals? In other words, was the highway
basically empty when your traveled? What is the utilization factor of your
pipes when you VoiceIP calls traverse from one point to another? 

It would be nice if you could show us that given the traffic utilization
factor of , say, from .1 to 0.5, your voiceIP can still be good or something
to that extent. 

I truly believe that quality of the call is related to traffic utilization
and congestion of the network.

Regards,

An
-----Original Message-----
From: Bill Woodcock
To: RJ Atkinson
Cc: ieprep@ietf.org
Sent: 11/26/02 9:31 PM
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?

    > By the way, during the Nairobi VoIP demo in Atlanta, was there any
    > use of IP ToS bits, DiffServ, or other QoS ?

Nope.  We wanted it to work.  Demos which fail aren't as impressive.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 06:42:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06254
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 06:42:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARBjAM18874
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 06:45:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARBjAv18870
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 06:45:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06251
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 06:42:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARBiDv18844;
	Wed, 27 Nov 2002 06:44:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARBhCv18776
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 06:43:13 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06216
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 06:40:26 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP
	id 2173B67103; Wed, 27 Nov 2002 03:07:39 -0500 (EST)
Date: Wed, 27 Nov 2002 06:43:09 -0500
Subject: Re: [Ieprep] VoIP demo in Atlanta
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep@ietf.org '" <ieprep@ietf.org>
To: "Nguyen, An" <nguyena@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D8E@emshqs1.ncr.disa.mil>
Message-Id: <66F60FD2-01FD-11D7-9C68-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 27, 2002, at 05:25 America/Montreal, Nguyen, An wrote:
> Sorry I was not there for the demos. I wondered if you took into 
> account the
> peak internet usage time when you gave the demos. I heard the demos 
> were
> given around 4:00PM EST( please correct me if I am wrong). That would 
> have
> been around 3:00 or 4:00 AM in Nairobi???

	Bill gave the same demo on multiple occasions during that week, with 
the same
results each time.  The time of day for the various demos varied pretty 
widely
(e.g. the IEPG demo was mid-morning US EST).  The results of the demo 
did
not vary in terms of voice quality, though there were differences in 
the amount
of packet loss along the path at the different times.  [As to the 
choice of
the demo time for IEprep, Bill did not have any choice since he was 
asked to
do the demo during the IEprep meeting slot (and Bill wasn't involved in 
scheduling
that meeting time).]

> Do you consider those two time
> zones are in the peak usage intervals? In other words, was the highway
> basically empty when your traveled? What is the utilization factor of 
> your
> pipes when you VoiceIP calls traverse from one point to another?

	There was 40% packet loss along the path (mostly inside Kenya) during 
the
IEPG demo.  The demo quality remained unchanged (as compared with 
IEprep demo)

> It would be nice if you could show us that given the traffic 
> utilization
> factor of , say, from .1 to 0.5, your voiceIP can still be good or 
> something
> to that extent.

	What is a "traffic utilisation factor" ?  I'm thinking you have a 
specific
equation in mind, but am not sure what that equation might be.

> I truly believe that quality of the call is related to traffic 
> utilization
> and congestion of the network.

	Well maybe not really closely related.  VoIP is a UDP service that 
lacks
congestion avoidance mechanisms.[1]  TCP and SCTP have congestion 
avoidance.  So if UDP
flows were to consume a lot of bandwidth, then the TCP and SCTP 
sessions sharing
that path will tend to back off, which tends to yield more bandwidth 
available
for those UDP flows.  (As Sally Floyd pointed out during IEprep, this 
also means
that IETF should probably put more work into adding congestion 
avoidance mechanisms
into VoIP applications.[2])

	Dave Oran, who knows a fair bit about the internals of the IP phone 
that
Bill was using for the demos, said that the particular IP phone that 
was used
for the demo always adds substantial implementation-specific FEC 
beneath the
G.711 codec output and above UDP.  That is, this FEC is a normal 
property of that
particular IP phone in its default configuration.  Understanding that 
there was
FEC added (rather than pure G.711) does help me understand why an IP 
phone using G.711
was able to work so well despite 40% packet loss inside Kenya.  As 
noted earlier,
I'm not tremendously impressed by the robustness of the G.711 codec -- 
CELP would
seem like a better choice for VoIP.

Ran
rja@extremenetworks.com

[1] If VoIP were a TCP or SCTP service, then there would likely be more 
issues
with VoIP over a path with high packet loss (or very high delay).

[2] This is why in many WGs, folks hear the Transport ADs insist that 
TCP-like
congestion avoidance get deployed.  To pick a current example, NFSv4 
runs over
TCP *only*, not over UDP, and congestion avoidance is specifically 
listed as the
reason that UDP is disallowed.  Originally NFSv{1,2} ran over UDP.  
NFSv3 supported
both TCP and UDP, but preferred TCP transport.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 06:54:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06434
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 06:54:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARBusc19355
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 06:56:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARBusv19352
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 06:56:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06428
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 06:54:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARBu2v19309;
	Wed, 27 Nov 2002 06:56:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARBtkv19241
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 06:55:46 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06375
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 06:53:00 -0500 (EST)
Received: from extremenetworks.com (unknown [10.30.20.242])
	by gnat.inet.org (Postfix) with ESMTP id 9449167103
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 03:20:13 -0500 (EST)
Date: Wed, 27 Nov 2002 06:55:44 -0500
Mime-Version: 1.0 (Apple Message framework v548)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: RJ Atkinson <rja@extremenetworks.com>
To: ieprep <ieprep@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <28A4D5A8-01FF-11D7-9C68-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] a practical VoIP issue
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


	It appears (according to Bill and others) that the biggest problem
with being able to deploy VoIP more widely might actually be NAT
devices.  Apparently VoIP systems use a wide range of dynamically 
assigned
UDP ports, which most firewalls block and which most NATs cannot cope
with properly.

	If one really wants to be able to use Internet infrastructure during
an emergency, designing a VoIP system that can do NAT/Firewall traversal
might be a pretty important component.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 07:20:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07105
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 07:20:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARCMwx21387
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 07:22:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCMvv21384
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 07:22:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07097
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 07:20:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCH2v21200;
	Wed, 27 Nov 2002 07:17:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCGxv21186
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 07:16:59 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06996
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 07:14:13 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gARCG3Du012188;
	Wed, 27 Nov 2002 07:16:03 -0500 (EST)
Date: Wed, 27 Nov 2002 07:16:03 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211271216.gARCG3Du012188@newdev.harvard.edu>
To: rja@extremenetworks.com, woody@pch.net
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Cc: ieprep@ietf.org
In-Reply-To: <Pine.GSO.4.44.0211261844030.6731-100000@paixhost.pch.net>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

henning reported a 7% (if memory serves) loss right after the test

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 07:26:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07250
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 07:26:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARCSqB21722
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 07:28:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCSqv21719
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 07:28:52 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07226
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 07:26:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCS1v21693;
	Wed, 27 Nov 2002 07:28:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCRuv21669
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 07:27:56 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA07213
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 07:25:07 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.28702-0@bells.cs.ucl.ac.uk>; Wed, 27 Nov 2002 12:23:32 +0000
To: Bill Woodcock <woody@pch.net>
cc: RJ Atkinson <rja@extremenetworks.com>, ieprep@ietf.org
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
In-reply-to: Your message of "Tue, 26 Nov 2002 18:49:57 PST." <Pine.GSO.4.44.0211261844030.6731-100000@paixhost.pch.net>
Date: Wed, 27 Nov 2002 12:23:30 +0000
Message-ID: <6736.1038399810@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



> We had the slide (which I'll put up permanently) showing how many hops,
> AS path length, loss, and latency across a full-mesh of myself, Scott
> Bradner, Patrik Faltstrom, and Brian Longwe.  We also have a traceroute
> (attached) from the day before, showing the path from Nairobi to the
> hotel.  Both times we were getting variable loss, up to about 40%.
> Most of those outward-facing IPs seem to be ICMP-blocked, so that's a
> little hard to replicate at the moment.

one caveat to keep in mind.  some ISPs place ICMP messages on separate
queues that can experience worse treatment (loss/delay) than other
flows. the motivation being to protect other traffic (eg, TCP)
considered more important, and/or constrain DoS attacks based on
icmp-echo.

hence, traceroutes can be a bit deceptive at times.

and yes, i'll conceded that the tier-1 ISPs in the states don't do this
between their peers :-)

-ken
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 07:30:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07375
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 07:30:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARCWke21948
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 07:32:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCWkv21945
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 07:32:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07337
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 07:29:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCVtv21880;
	Wed, 27 Nov 2002 07:31:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCSwv21735
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 07:28:58 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA07230
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 07:26:10 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.29207-0@bells.cs.ucl.ac.uk>; Wed, 27 Nov 2002 12:28:41 +0000
To: RJ Atkinson <rja@extremenetworks.com>
cc: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] a practical VoIP issue
In-reply-to: Your message of "Wed, 27 Nov 2002 06:55:44 EST." <28A4D5A8-01FF-11D7-9C68-00039357A82A@extremenetworks.com>
Date: Wed, 27 Nov 2002 12:28:40 +0000
Message-ID: <7480.1038400120@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



> It appears (according to Bill and others) that the biggest
> problem with being able to deploy VoIP more widely might actually be NAT
> devices.  Apparently VoIP systems use a wide range of dynamically
> assigned UDP ports, which most firewalls block and which most NATs
> cannot cope with properly.
>
> If one really wants to be able to use Internet infrastructure during
> an emergency, designing a VoIP system that can do NAT/Firewall traversal
> might be a pretty important component.

yes, a good point. and its actually being worked on in another group,
as well as industry.  

-ken
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 07:41:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07644
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 07:41:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARChxx23078
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 07:43:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARChxv23075
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 07:43:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07641
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 07:41:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCh3v23044;
	Wed, 27 Nov 2002 07:43:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARCgxv22993
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 07:42:59 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07614
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 07:40:12 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gARCg44p012380
	for ieprep@ietf.org; Wed, 27 Nov 2002 07:42:04 -0500 (EST)
Date: Wed, 27 Nov 2002 07:42:04 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211271242.gARCg44p012380@newdev.harvard.edu>
To: ieprep@ietf.org
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>



some additional info on the diffserv (TOS) marking question

some routers can be used to do the following
	1/ change DSCP on packets entering ports from non-trusted
	   customers (or customers who have not purchased a 
	   speciifc service) to 000000

	2/ on ports connected to "trusted" customers
	   selectively change the DSCP on an incoming packet
	   e.g. reset code points 111000, 110000 and 101000 to 000000
		(these are the codepoints used for routing and 
		management in some ISPs)
	   and change all DSCP values not part of the service ofering
	   to 000000 but do not change (or map to non-zero values)
	   the DSCPs which are part of a service offering

	3/ rate limit traffic, on a per-DSCP per-customer basis
	   for traffic from trusted customers who have purchased
	   a different-than-best-effort service

It appears to me that the DOS opportunities are reduced in such designs

i.e. the router tools to do useful things are present

but, the fact that some routers can support such a system does not,
by itself, show that such a system could be easily operated or that it
is totally safe - the operations systems to control the router
configs might be more fun to use than I'd want to have and in
the simple case, the different-than-best-effort traffic has
to be small enough so that no convergence of such traffic 
will overload the smallest backbone link (since the above
scenario does not include doing destination-specific rate 
control it is not possible to know what internal paths the
traffic will take.

making this scenario work in a multi ISP environment would also
be "fun"

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 09:02:01 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09796
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 09:02:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARE4F727420
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 09:04:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARE4Fv27417
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 09:04:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09787
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 09:01:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARDwEv27200;
	Wed, 27 Nov 2002 08:58:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARDvtv27163
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 08:57:55 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09592
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 08:55:09 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Wed, 27 Nov 2002 08:57:26 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2002112708574025015
 ; Wed, 27 Nov 2002 08:57:40 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <XNSV17T3>; Wed, 27 Nov 2002 08:59:08 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E779C1@mcl-its-exs01.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Scott Bradner '" <sob@harvard.edu>,
        "'ieprep@ietf.org '" <ieprep@ietf.org>
Subject: RE: [Ieprep] any commercial usage for "emergency QoS"?
Date: Wed, 27 Nov 2002 08:57:39 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>making this scenario work in a multi ISP environment would also
>be "fun"

in-ter-est-ing
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 09:18:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10739
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 09:18:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAREL2k28797
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 09:21:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAREL2v28794
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 09:21:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10727
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 09:18:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAREK0v28708;
	Wed, 27 Nov 2002 09:20:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAREGWv28523
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 09:16:32 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10430
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 09:13:46 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.122])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 649487A0E; Wed, 27 Nov 2002 06:16:26 -0800 (PST)
Date: Wed, 27 Nov 2002 09:10:44 -0500
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <6736.1038399810@cs.ucl.ac.uk>
Message-Id: <052674AF-0212-11D7-9C68-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 27, 2002, at 07:23 America/Montreal, Ken Carlberg 
wrote:
> one caveat to keep in mind.  some ISPs place ICMP messages on separate
> queues that can experience worse treatment (loss/delay) than other
> flows. the motivation being to protect other traffic (eg, TCP)
> considered more important, and/or constrain DoS attacks based on
> icmp-echo.

Hmm.  I'm not aware of any ISP that has done that.  And traceroute
uses UDP to probe, the ICMP is only used for the return of the
ICMP Port Unreachable from the router.

What is true is that some *CPU-based routers* de-prioritise the
generation of ICMP error messages within the router, as compared
with spending CPU forwarding non-errorred packets, which can sometimes
mean that traceroute results are *slightly* (not dramatically) worse
than normal traffic.

The other thing is that Henning measured *after* the demo, meaning
that any competing TCP/SCTP-based flows probably had time to back off
-- so the packet loss at start of demo was probably a bit higher
than the measured number.

Bottom line is that it all washes out and so the measured packet loss
is probably accurate within some reasonable error bound.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 09:18:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10755
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 09:18:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAREL9r28817
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 09:21:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAREL9v28814
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 09:21:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10736
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 09:18:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAREJxv28691;
	Wed, 27 Nov 2002 09:19:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAREGTv28519
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 09:16:29 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10427
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 09:13:43 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.122])
	by smtp1.extremenetworks.com (Postfix) with ESMTP id C4F467A0A
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 06:16:23 -0800 (PST)
Date: Wed, 27 Nov 2002 08:21:15 -0500
Mime-Version: 1.0 (Apple Message framework v548)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: RJ Atkinson <rja@extremenetworks.com>
To: ieprep <ieprep@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <1B77A3AA-020B-11D7-9C68-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] Accounting
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


So I remain very confused about what the accounting advocates
are asking for.  I might be slower than most to puzzle some
stuff out, but what I got out of the Accounting presentation
was roughly this:

	- Accounting is a requirement.
	- We don't mean that packet accounting is a requirement.

Which begs the question of precisely which stuff folks think operators
need to perform accounting on.  Scott Bradner suggested that maybe
folks meant that there should be some form of accounting within SIP.
Is that suggestion correct ?

I'd really like to understand precisely what folks think is required.

When folks say that "accounting is a requirement" do they really
mean that " A SIP implementation must be able to perform accounting
for (some specific list of objects/events)" or mean something else ?

- If the quoted sentence above is close, could folks please be specific 
and
	enumerate which specific objects/events need to have accounting 
support ?
- If something else, then please be specific and tell us what exactly
	folks want to perform accounting on ?

I don't know off-hand whether a (draft) SIP MIB exists yet or not.
If folks are thinking about accounting within SIP and if a (draft)
SIP MIB exists, could those folks please check and see if the MIB
already has counters for the objects/events of concern ?  And if
the (draft) MIB exists and is missing objects/events, maybe those
particular objects could be requested from the WG that is working
on the MIB ?

Also, would it be consistent with the Accounting advocates desires to
say something like this:

	Network operators that do not operate (SIP servers) are not required
	to perform any accounting in order to support IEprep services.

If yes, then that is a good start and could we please document that
understanding some place.

If not, what edits to "(SIP servers)" would make that sentence true ?
In other words, what accounting do the accounting advocates want ISPs
to perform particularly to support IEprep services ?

Thanks,

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 10:16:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14013
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 10:16:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARFJ7p00571
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 10:19:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARFJ7v00568
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 10:19:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13985
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 10:16:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARFIBv00498;
	Wed, 27 Nov 2002 10:18:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARFHav00445
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 10:17:36 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13911
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 10:14:50 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <XDXAGC4Z>; Wed, 27 Nov 2002 10:15:10 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A414994@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] problem context
Date: Wed, 27 Nov 2002 10:15:00 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Well, I work on a program funded by NCS.  So that (the issues I deal with on
that program, not the fact that it is funded by NCS) has an influence on my
"point of view".  

But what I say is a reflection of the "concerns of Janet Gunn, private
individual".  I do NOT claim to represent the "concerns of NCS".

I thought that was SUPPOSED to be the premise of the IETF, that we express
our own opinions, not those of our employers, funders, etc.

-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Tuesday, November 26, 2002 7:53 PM
To: Gunn, Janet
Cc: ieprep
Subject: Re: [Ieprep] problem context



I'm not quite sure which of these (or maybe some other items) is the 
focus
of the concern at NCS, and which of these is the focus of the concern at
DISA Centre for Standards.  It would help if those perspectives could 
be made
more clearly.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 11:29:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17451
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 11:29:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARGW4P05577
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 11:32:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGW4v05574
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 11:32:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17435
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 11:29:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGV5v05490;
	Wed, 27 Nov 2002 11:31:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGSsv05249
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 11:28:54 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17278
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 11:26:06 -0500 (EST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.6/8.12.6) id gARGTYVW032306;
	Wed, 27 Nov 2002 08:29:34 -0800
Date: Wed, 27 Nov 2002 08:29:34 -0800
From: David Meyer <dmm@sprint.net>
To: Scott Bradner <sob@harvard.edu>
Cc: ieprep@ietf.org
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Message-ID: <20021127082934.C32212@sprint.net>
References: <200211271242.gARCg44p012380@newdev.harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <200211271242.gARCg44p012380@newdev.harvard.edu>; from sob@harvard.edu on Wed, Nov 27, 2002 at 07:42:04AM -0500
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>> It appears to me that the DOS opportunities are reduced in such designs

	s/are/might be

>> i.e. the router tools to do useful things are present

	The problem is really equivalent to ingress filtering for
	customers, but there is no really good analogy there for
	peers. That is (in part) where the problem really resides
	(at scale).  

>> but, the fact that some routers can support such a system does not,
>> by itself, show that such a system could be easily operated or that it
>> is totally safe - the operations systems to control the router
>> configs might be more fun to use than I'd want to have and in
>> the simple case, the different-than-best-effort traffic has
>> to be small enough so that no convergence of such traffic 
>> will overload the smallest backbone link (since the above
>> scenario does not include doing destination-specific rate 
>> control it is not possible to know what internal paths the
>> traffic will take.

	Again, the problem is that while all of this mechanism
	exists (along with quite a bit more), you can do none of
	this in the core of your network if you expect to (i). be
	able to operate it, and (ii). expect to be able to scale
	it.  

>> making this scenario work in a multi ISP environment would also
>> be "fun"

	Oh, yes, that too. Global coordination/conservation ToS
	bits? Have you tcpdumped on your local LAN lately? What
	bits does scp set, for example (rhetorical...
	% tcpdump | grep -i tos)?  

	BTW, what do I do if I have a customer who wants her ToS
	bits preserved across peerings? Do I need a service that
	is "ToS-bit invariant" now? Do I need another SLA that
	states that I won't touch fields X,Y and Z in a
	customer's IP header? What if I encapsulate the packet?
	You can see that this is going to quickly spiral out of
	the tractability space. 

	Dave

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 11:35:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17839
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 11:35:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARGbHl06467
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 11:37:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGbHv06463
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 11:37:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17825
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 11:34:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGa3v05897;
	Wed, 27 Nov 2002 11:36:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGZSv05823
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 11:35:28 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17685
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 11:32:40 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gARGYWR6013748;
	Wed, 27 Nov 2002 11:34:32 -0500 (EST)
Date: Wed, 27 Nov 2002 11:34:32 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211271634.gARGYWR6013748@newdev.harvard.edu>
To: dmm@sprint.net, sob@harvard.edu
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Cc: ieprep@ietf.org
In-Reply-To: <20021127082934.C32212@sprint.net>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

dmm sez:
	The problem is really equivalent to ingress filtering for
	customers, but there is no really good analogy there for
	peers. That is (in part) where the problem really resides
	(at scale).  

yup - multi-ISP cases are not usefully covered

dmm also sez:
	Again, the problem is that while all of this mechanism
	exists (along with quite a bit more), you can do none of
	this in the core of your network if you expect to (i). be
	able to operate it, and (ii). expect to be able to scale it.  

I think there is a real issue here and it would be good to know if
anyone has tried anything like this

dmm goes on to say:
	BTW, what do I do if I have a customer who wants her ToS
	bits preserved across peerings? Do I need a service that
	is "ToS-bit invariant" now? Do I need another SLA that
	states that I won't touch fields X,Y and Z in a
	customer's IP header? What if I encapsulate the packet?
	You can see that this is going to quickly spiral out of
	the tractability space. 

educate the customer? (and don't sign the SLA)


Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 11:36:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17966
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 11:36:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARGcs406768
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 11:38:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGcsv06765
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 11:38:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17919
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 11:36:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGc1v06705;
	Wed, 27 Nov 2002 11:38:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGbAv06373
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 11:37:10 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA17817
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 11:34:22 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 27 Nov 2002 16:30:46 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XKBZAA95>; Wed, 27 Nov 2002 11:37:08 -0500
Message-ID: <B3FE60C05AD31D4C96E07EBC5000639E1D7FC8@EMSHQS2>
From: "Choi, Don" <choid@ncr.disa.mil>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>, Scott Bradner <sob@harvard.edu>
Subject: RE: [Ieprep] problem context
Date: Wed, 27 Nov 2002 11:37:03 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Ran,

It is not what I want, nor what the DISA Center for Standards wants, nor
what DISA wants, it is what DoD wants. And it is not just U.S. DoD, but our
counterparts in many other countries. 

What DoD wants is, simply put, when a mission critical user makes a call,
the call goes through and stays up. It does not say calls have to be
pre-empted nor packets should be dropped. It happened that in a circuit
switched network, pre-emption was the chosen solution for this requirement.
So, MLPP is a SOLUTION for this requirement in circuit switched networks,
not a requirement. Even in circuit switched networks, there had been
proposals to support this requirement without using preemption.

It has been a policy of the current U.S. administration and the previous
administration to use products and services based on commercial standards,
not based on military standards. And the current administration wants
IP-centric solutions for our needs. So, it is of critical importance that we
(DoD) have commercial stantandards for IP-based solutions that support our
requirements. And we (DISA) think that IETF is the place to develop these
standards. 

An alternative to this, if IETF can not develop such standards for some
reason, is military standards developed by a dumb guy like me. This
alternative does not serve anyone, tax payers, the administration, DoD and
the internet community. 

We are not saying the Internet has to support this requirement. This
requirement is applicable only to the products and services to be sold to
DoD, and hopefully to our counterparts in other countries. The current
international situation calls for not just interoperability within DoD, but
combined interoperability with our allies and partnership countries.

Have a great Thanksgiving.

Don
-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Tuesday, November 26, 2002 4:44 PM
To: Scott Bradner
Cc: ieprep
Subject: Re: [Ieprep] problem context



On Tuesday, Nov 26, 2002, at 16:25 America/Montreal, Scott Bradner 
wrote:
>> Along those lines, I don't think the goal of an MLPP service is to
>> throw away bits according to diffserv-style priorities.  I think 
>> levels
>> in a scheme like MLPP only make sense in an application specific
>> context, possibly only in the context of audio media even....
>
> I expect you are right

	MLPP as implemented today in DSN ("AutoVon") actually throws away
existing live calls (the "pre-emption" part) if a trunk is out of
capacity and a higher precedence call appears on the scene.  MLPP
as formerly implemented in some DoD IP networks (~10 years back)
dropped lower precedence packets in order to avoid dropping higher
precedence packets when a link was underprovisioned relative to
offered load.

	It would be useful if Don would clarify more precisely what he
is looking for.  It could be either the quoted approach up top,
my (poor quality) summary of current/past DoD deployment, or something
else entirely.

Ran


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 11:39:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18116
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 11:39:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARGg0Y07050
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 11:42:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGg0v07047
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 11:42:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18111
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 11:39:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGa9v05978;
	Wed, 27 Nov 2002 11:36:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGZtv05861
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 11:35:55 -0500
Received: from chntex03.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17718
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 11:33:07 -0500 (EST)
Received: by chntex03.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <XDXAGDA8>; Wed, 27 Nov 2002 11:33:24 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A414997@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] problem context
Date: Wed, 27 Nov 2002 11:33:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Personally (not representing any organization's "concerns"), I am basically
neutral as to whether the appropriate solution is at the IP layer, or the
application (e.g., SIP) layer . Similarly, I would be comfortable with
whatever "level" of gateway (router, SIP gateway, application gateway) is
most effective.   At least for VOIP (and probably for video feeds, etc.) the
application/SIP layer is probably more promising.

If a problem develops (I don't think it is a problem today, but I am not
convinced it is IMPOSSIBLE to have a problem) with elastic applications, it
might be more appropriate to address the solution at a lower level.

-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com]
Sent: Tuesday, November 26, 2002 7:53 PM
To: Gunn, Janet
Cc: ieprep
Subject: Re: [Ieprep] problem context



On Tuesday, Nov 26, 2002, at 18:32 America/Montreal, Gunn, Janet wrote:
> It seems to me that MLPP is a technical solution to solve a particular
> problem in a (fixed) circuit switched network.
>
> Just as eMLPP is a different technical solution to solve a similar 
> problem
> in a (mobile) circuit switched network.
>
> I am not sure that it makes sense to REPLICATE either MLPP or eMLPP in 
> an IP
> network.
>
> However, it may very well be useful to identify an (IP specific) 
> technical
> solution that solves the same basic problem.
>
> And it would DEFINITELY be useful to identify ways of interoperating 
> with
> MLPP and eMLPP across the relevant gateways.

There are at least 2 (maybe more) different layers that one can use to 
consider this
question:  application-layer (e.g. SIP servers) and IP-layer.  I am 
very unclear
which of these is meant.  Some folks use "gateway" to mean a SIP 
gateway,
some to mean another application-layer gateway, and some to mean an IP 
router.

If we look at this as an IP-layer issue, then DiffServ/IP-ToS is an 
approach that
can work *within a single administrative domain*.  The security issues 
(e.g.
DDOS attack using IP ToS bits) are primarily a problem on an 
inter-domain
boundary.  Within a single administrative domain, the authorities for 
that
domain can use domain-specific policies and mechanisms to mitigate their
operational risk.

If we look at this as a SIP issue, then it seems like the main concern 
might
be to ensure that whatever markings are associated with a telephone call
are preserved (or modified only as appropriate at an administrative
boundary -- example:  country X might by policy disregard/remove 
markings
originating on an international call from country Y).  Because of our
layered architecture, having a call marked with some bit pattern inside
SIP does NOT automatically imply any change from best-effort handling by
the IP-layer.  It would not prohibit it, but neither would it 
automatically
imply such.

I'm not quite sure which of these (or maybe some other items) is the 
focus
of the concern at NCS, and which of these is the focus of the concern at
DISA Centre for Standards.  It would help if those perspectives could 
be made
more clearly.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 12:17:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20052
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 12:17:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARHK4S10364
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 12:20:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHK4v10361
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 12:20:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20011
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 12:17:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHERv09832;
	Wed, 27 Nov 2002 12:14:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARH8av09319
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 12:08:36 -0500
Received: from almso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19308
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:05:48 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id gARH89Ln025040
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:08:32 -0500 (EST)
Received: from OCCLUST03EVS1.ugd.att.com (135.71.164.11) by attrh3i.attrh.att.com (6.5.019)
        id 3DDD63A1002819F6; Wed, 27 Nov 2002 12:08:08 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [Ieprep] any commercial usage for "emergency QoS"?
Date: Wed, 27 Nov 2002 12:07:20 -0500
Message-ID: <456FD0E7B215B24ABBAD711614E4A7A201609846@OCCLUST03EVS1.ugd.att.com>
Thread-Topic: [Ieprep] any commercial usage for "emergency QoS"?
Thread-Index: AcKV/5q/l8JU3RzeRmKBX43WUXTSWwANq7HQ
From: "Dvorak, Charles A (Chuck), ALASO" <cdvorak@att.com>
To: "Nguyen, An" <nguyena@ncs.gov>, "Bill Woodcock " <woody@pch.net>,
        "RJ Atkinson " <rja@extremenetworks.com>
Cc: <ieprep@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gARH8bv09320
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

One thing barely mentioned about this Nairobi demo was the excessive
latency (nearly 700ms if I recall), which was not really evident due to
the lack of stringent interactions. Most of the focus has been on how
many packets were lost...

The effects are delay on speech quality are well modeled by the E-model
(G.107). Even with zero packet loss, users consider such large delays to
have substantially degraded quality, to the point of making such calls
unusable for routine conversations/discussions/negotiations.

Chuck Dvorak 

> -----Original Message-----
> From: Nguyen, An [mailto:nguyena@ncs.gov]
> Sent: Wednesday, November 27, 2002 5:26 AM
> To: 'Bill Woodcock '; 'RJ Atkinson '
> Cc: 'ieprep@ietf.org '
> Subject: RE: [Ieprep] any commercial usage for "emergency QoS"?
> 
> 
> Bill,
> 
> Sorry I was not there for the demos. I wondered if you took 
> into account the
> peak internet usage time when you gave the demos. I heard the 
> demos were
> given around 4:00PM EST( please correct me if I am wrong). 
> That would have
> been around 3:00 or 4:00 AM in Nairobi??? Do you consider 
> those two time
> zones are in the peak usage intervals? In other words, was the highway
> basically empty when your traveled? What is the utilization 
> factor of your
> pipes when you VoiceIP calls traverse from one point to another? 
> 
> It would be nice if you could show us that given the traffic 
> utilization
> factor of , say, from .1 to 0.5, your voiceIP can still be 
> good or something
> to that extent. 
> 
> I truly believe that quality of the call is related to 
> traffic utilization
> and congestion of the network.
> 
> Regards,
> 
> An
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 12:33:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20715
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 12:33:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARHZt711057
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 12:35:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHZsv11054
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 12:35:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20684
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 12:33:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHZ7v10980;
	Wed, 27 Nov 2002 12:35:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHYDv10908
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 12:34:13 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20605
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:31:24 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gARHRtd12477;
	Wed, 27 Nov 2002 09:27:55 -0800 (PST)
Date: Wed, 27 Nov 2002 09:27:55 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Dvorak, Charles A (Chuck), ALASO" <cdvorak@att.com>
cc: "Nguyen, An" <nguyena@ncs.gov>, RJ Atkinson  <rja@extremenetworks.com>,
        <ieprep@ietf.org>
Subject: RE: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <456FD0E7B215B24ABBAD711614E4A7A201609846@OCCLUST03EVS1.ugd.att.com>
Message-ID: <Pine.GSO.4.44.0211270927020.12471-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 27 Nov 2002, Dvorak, Charles A (Chuck), ALASO wrote:
    > users consider such large delays to have substantially degraded
    > quality, to the point of making such calls unusable for routine
    > conversations/discussions/negotiations.

No we don't.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 12:36:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20873
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 12:36:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARHdHN11899
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 12:39:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHdHv11896
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 12:39:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20862
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 12:36:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHcXv11802;
	Wed, 27 Nov 2002 12:38:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHZiv11035
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 12:35:44 -0500
Received: from imo-r03.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20653
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:32:56 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r03.mx.aol.com (mail_out_v34.13.) id b.1c0.226395f (24895);
	Wed, 27 Nov 2002 12:35:20 -0500 (EST)
Message-ID: <1c0.226395f.2b165c57@aol.com>
Date: Wed, 27 Nov 2002 12:35:19 EST
Subject: Re: [Ieprep] Use of ToS bits for "emergency" preferential treatment
To: woody@pch.net, sob@harvard.edu
CC: rja@extremenetworks.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_1c0.226395f.2b165c57_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_1c0.226395f.2b165c57_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/26/2002 8:46:58 PM Eastern Standard Time, woody@pch.net 
writes:

> That's a host requirement, not a service provider requirement.
> 
[MAP] I understand that the specific references are "Host Requirements", but 
I have to believe that the point of this JTA requirement is that the 8-bit 
field must be passed end-to-end (through "hosts", "routers", and whatever) 
unchanged.


sob@harvard.edu writes:

> OBE
>     the 8-bit TOS field is no more
>     6 bits are the differv DSCP (see RFC 2474)
>     2 bits are ECN (see RFC 3168)
> 
[MAP] So, I would still interpret that the DoD requirement is to pass the 8 
bits unchanged, no matter what they have been renamed. Is this requirement 
wrong or impossible to meet?


In a message dated 11/26/2002 9:23:26 PM Eastern Standard Time, 
rja@extremenetworks.com writes:

> Standard 3 == {RFC-1122, RFC-1123} with some updates.
> 
> Parts of STD3 are in fact badly out of date.  Several parts of it are 
> defunct,
> but there has never been enough energy in IETF to revisit the documents.
> 
[MAP] According to the official list, STD 3 consists of RFC 1122 and 1123, 
not  some additional unspecified updates. While 1122 is "updated by" 1349 and 
1123 is "updated by" 1349 and 2181, 1349 is in turn obsoleted by 2474 
(DiffServ) and 2181 does not address the TOS field. Guess this clearly points 
out one of the procedural shortcomings in the IETF which allows "out-of-date" 
and "defunct" standards to continue to exist. Looks like something that 
should be addressed by someone who cares about procedures.


In a message dated 11/26/2002 10:03:32 PM Eastern Standard Time, 
rja@extremenetworks.com writes:

> Many IP routers/L3 switches can be configured to set/clear/reset the IP ToS
> or DiffServ byte, generally based on ACLs configured by the router 
> administrator.
> 
[MAP] And I suppose if they want to comply with the JTA requirement, they 
would also be capable of being configured to leave these bits alone.

Mike Pierce
Artel


--part1_1c0.226395f.2b165c57_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/26/2002 8:46:58 PM Eastern Standard Time, woody@pch.net writes:
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">That's a host requirement, not a service provider requirement.
<BR></BLOCKQUOTE>
<BR>[MAP] I understand that the specific references are "Host Requirements", but I have to believe that the point of this JTA requirement is that the 8-bit field must be passed end-to-end (through "hosts", "routers", and whatever) unchanged.
<BR>
<BR>
<BR>sob@harvard.edu writes:
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">OBE
<BR> &nbsp;&nbsp;&nbsp;the 8-bit TOS field is no more
<BR> &nbsp;&nbsp;&nbsp;6 bits are the differv DSCP (see RFC 2474)
<BR> &nbsp;&nbsp;&nbsp;2 bits are ECN (see RFC 3168)
<BR></BLOCKQUOTE>
<BR>[MAP] So, I would still interpret that the DoD requirement is to pass the 8 bits unchanged, no matter what they have been renamed. Is this requirement wrong or impossible to meet?
<BR>
<BR>
<BR>In a message dated 11/26/2002 9:23:26 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Standard 3 == {RFC-1122, RFC-1123} with some updates.
<BR>
<BR>Parts of STD3 are in fact badly out of date. &nbsp;Several parts of it are defunct,
<BR>but there has never been enough energy in IETF to revisit the documents.
<BR></BLOCKQUOTE>
<BR>[MAP] According to the official list, STD 3 consists of RFC 1122 and 1123, not &nbsp;some additional unspecified updates. While 1122 is "updated by" 1349 and 1123 is "updated by" 1349 and 2181, 1349 is in turn obsoleted by 2474 (DiffServ) and 2181 does not address the TOS field. Guess this clearly points out one of the procedural shortcomings in the IETF which allows "out-of-date" and "defunct" standards to continue to exist. Looks like something that should be addressed by someone who cares about procedures.
<BR>
<BR>
<BR>In a message dated 11/26/2002 10:03:32 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Many IP routers/L3 switches can be configured to set/clear/reset the IP ToS
<BR>or DiffServ byte, generally based on ACLs configured by the router administrator.
<BR></BLOCKQUOTE>
<BR>[MAP] And I suppose if they want to comply with the JTA requirement, they would also be capable of being configured to leave these bits alone.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_1c0.226395f.2b165c57_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 12:37:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20886
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 12:37:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARHdLX11922
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 12:39:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHdLv11919
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 12:39:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20869
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 12:36:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHcVv11782;
	Wed, 27 Nov 2002 12:38:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHZdv11027
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 12:35:39 -0500
Received: from imo-r02.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20649
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:32:50 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r02.mx.aol.com (mail_out_v34.13.) id j.175.126e5023 (24895);
	Wed, 27 Nov 2002 12:35:18 -0500 (EST)
Message-ID: <175.126e5023.2b165c56@aol.com>
Date: Wed, 27 Nov 2002 12:35:18 EST
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
To: rja@extremenetworks.com, woody@pch.net
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_175.126e5023.2b165c56_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_175.126e5023.2b165c56_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/26/2002 9:50:17 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> So the demo might be an existance proof that VoIP works fine over
> a set of best-effort IP networks across 2-3 continents ?
> 
[MAP] And there's never been an argument that the quality isn't good when the 
network is not overloaded and there are no major faults anywhere. What some 
on this discussion have not yet understood, is that we are trying to talk 
about "preparedness" for a traffic overload/fault condition that has never 
occurred. It did not occur on Sept 11 or in the "Baltimore Train Tunnel". 
Whether some like it or not, that is the mission of both NCS and DoD - 
preparing for what we hope never happens.

Yes the demonstration was interesting, but completely irrelavent to the task 
at hand.

In fact, I have a question about that demonstration. If I understood the 
explanation, the end user in Nairobi was using a 128 kbit/s interface which 
went to something where he was then sharing a 384 kbit/s interface to get to 
the Internet backbone with, what I thought I heard quickly mumbled, was 
"thousands of users" (who were mostly asleep). Obviously, the results would 
be very much different if a lot of those other sleeping users were also awake 
and trying to make voice calls, like if there were a major disaster.

In addition, I do not consider a call made on a speaker phone and broadcast 
over a PA system as being a sufficient demonstration of the effect that the 
round-trip delay would have on a normal conversation.

Another question: Was it stated during the presentation that the packet loss 
ratio was 40%? Whatever the loss ratio, why are packets lost? Is it because 
of congestion at some point (and discard because the buffer is full)?

Mike Pierce
Artel


--part1_175.126e5023.2b165c56_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/26/2002 9:50:17 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">So the demo might be an existance proof that VoIP works fine over
<BR>a set of best-effort IP networks across 2-3 continents ?
<BR></BLOCKQUOTE>
<BR>[MAP] And there's never been an argument that the quality isn't good when the network is not overloaded and there are no major faults anywhere. What some on this discussion have not yet understood, is that we are trying to talk about "preparedness" for a traffic overload/fault condition that has never occurred. It did not occur on Sept 11 or in the "Baltimore Train Tunnel". Whether some like it or not, that is the mission of both NCS and DoD - preparing for what we hope never happens.
<BR>
<BR>Yes the demonstration was interesting, but completely irrelavent to the task at hand.
<BR>
<BR>In fact, I have a question about that demonstration. If I understood the explanation, the end user in Nairobi was using a 128 kbit/s interface which went to something where he was then sharing a 384 kbit/s interface to get to the Internet backbone with, what I thought I heard quickly mumbled, was "thousands of users" (who were mostly asleep). Obviously, the results would be very much different if a lot of those other sleeping users were also awake and trying to make voice calls, like if there were a major disaster.
<BR>
<BR>In addition, I do not consider a call made on a speaker phone and broadcast over a PA system as being a sufficient demonstration of the effect that the round-trip delay would have on a normal conversation.
<BR>
<BR>Another question: Was it stated during the presentation that the packet loss ratio was 40%? Whatever the loss ratio, why are packets lost? Is it because of congestion at some point (and discard because the buffer is full)?
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_175.126e5023.2b165c56_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 12:37:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20927
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 12:37:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARHdrO11947
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 12:39:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHdrv11944
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 12:39:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20895
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 12:37:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHd2v11871;
	Wed, 27 Nov 2002 12:39:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHbev11725
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 12:37:40 -0500
Received: from imo-d09.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20800
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:34:51 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d09.mx.aol.com (mail_out_v34.13.) id j.192.115dfe21 (24895);
	Wed, 27 Nov 2002 12:35:17 -0500 (EST)
Message-ID: <192.115dfe21.2b165c55@aol.com>
Date: Wed, 27 Nov 2002 12:35:17 EST
Subject: Re: [Ieprep] problem context
To: rja@extremenetworks.com, choid@ncr.disa.mil
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_192.115dfe21.2b165c55_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_192.115dfe21.2b165c55_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/25/2002 1:19:39 PM Eastern Standard Time, 
rja@extremenetworks.com writes:


> On Monday, Nov 25, 2002, at 12:52 America/Montreal, Choi, Don wrote:
> > The requirement for MLPP like service in internet (IP-based network) has
> > been part of IEPREP WG all along.
> 
>     Disagree.  It has NOT been here "all along".   It is an example
> of "feature creep" or "charter creep".  I've been at each IEprep BOF
> or WG meeting.  

[MAP] I know this has been a point of disagreement, since IEPREP often 
concentrated on the "Authorized Emergency" applicaiton and referred to the US 
GETS service as the primary example. But the charter  is equally applicable 
to the MLPP (or "Assured Service", as I have been presenting) when it talks 
about "facilitate recovery operations for ... terrorist attacks" and 
"Internet Prepardness".

> 
>     Also work specifying an MLPP mechanism is outside charter, since IEprep
> 

[MAP] We understand that IEPREP will not define the actual mechanisms.


>     The WG to address MLPP is probably DiffServ.  I infer that DoD/NCS folks 
> haven't
> succeeded (yet ?) in persuading DiffServ to specify something that DoD/NCS 
> folks like.
> None the less, DiffServ is the WG where MLPP mechanisms are most likely 
> actually
> to get specified and where desires for MLPP need to get expressed (assuming 
> folks
> want MLPP to actually happen inside IETF specs).  Earlier it sounded like 
> you all
> grasped this fact and were trying to work within DiffServ; I must have 
> 

[MAP] Yes, we believe that some of the solutions (read: mechanisms) should be 
DiffServ enhancements, so we expect to eventually go there. But we also 
believe there are other parts to the solution, so it is necessary to get the 
requirements and framework defined in another WG first. IEPREP was chartered 
to do that for emergency services. MLPP (or "Assured Service") fits within 
that set of "Emergency Services". As has been discussed, the solution set is 
expected to be used for both the MLPP-like (mostly military network) and the 
GET-like (civilian network) applications.


Mike Pierce
Artel




--part1_192.115dfe21.2b165c55_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/25/2002 1:19:39 PM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">On Monday, Nov 25, 2002, at 12:52 America/Montreal, Choi, Don wrote:
<BR>&gt; The requirement for MLPP like service in internet (IP-based network) has
<BR>&gt; been part of IEPREP WG all along.
<BR>
<BR> &nbsp;&nbsp;&nbsp;Disagree. &nbsp;It has NOT been here "all along". &nbsp;&nbsp;It is an example
<BR>of "feature creep" or "charter creep". &nbsp;I've been at each IEprep BOF
<BR>or WG meeting. &nbsp;MLPP hasn't even been discussed at most of them.</BLOCKQUOTE>
<BR>
<BR>[MAP] I know this has been a point of disagreement, since IEPREP often concentrated on the "Authorized Emergency" applicaiton and referred to the US GETS service as the primary example. But the charter &nbsp;is equally applicable to the MLPP (or "Assured Service", as I have been presenting) when it talks about "facilitate recovery operations for ... terrorist attacks" and "Internet Prepardness".
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<BR> &nbsp;&nbsp;&nbsp;Also work specifying an MLPP mechanism is outside charter, since IEprep
<BR>does not do protocol design.</BLOCKQUOTE>
<BR>
<BR>[MAP] We understand that IEPREP will not define the actual mechanisms.
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"> &nbsp;&nbsp;&nbsp;The WG to address MLPP is probably DiffServ. &nbsp;I infer that DoD/NCS folks haven't
<BR>succeeded (yet ?) in persuading DiffServ to specify something that DoD/NCS folks like.
<BR>None the less, DiffServ is the WG where MLPP mechanisms are most likely actually
<BR>to get specified and where desires for MLPP need to get expressed (assuming folks
<BR>want MLPP to actually happen inside IETF specs). &nbsp;Earlier it sounded like you all
<BR>grasped this fact and were trying to work within DiffServ; I must have misunderstood.</BLOCKQUOTE>
<BR>
<BR>[MAP] Yes, we believe that some of the solutions (read: mechanisms) should be DiffServ enhancements, so we expect to eventually go there. But we also believe there are other parts to the solution, so it is necessary to get the requirements and framework defined in another WG first. IEPREP was chartered to do that for emergency services. MLPP (or "Assured Service") fits within that set of "Emergency Services". As has been discussed, the solution set is expected to be used for both the MLPP-like (mostly military network) and the GET-like (civilian network) applications.
<BR>
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR>
<BR></FONT></HTML>

--part1_192.115dfe21.2b165c55_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 12:37:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20943
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 12:37:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARHdwo11962
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 12:39:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHdwv11959
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 12:39:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20905
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 12:37:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHd1v11848;
	Wed, 27 Nov 2002 12:39:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHbFv11476
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 12:37:15 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20748
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:34:26 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gARHV5d12552;
	Wed, 27 Nov 2002 09:31:05 -0800 (PST)
Date: Wed, 27 Nov 2002 09:31:05 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Choi, Don" <choid@ncr.disa.mil>
cc: "'RJ Atkinson'" <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>,
        Scott Bradner <sob@harvard.edu>
Subject: RE: [Ieprep] problem context
In-Reply-To: <B3FE60C05AD31D4C96E07EBC5000639E1D7FC8@EMSHQS2>
Message-ID: <Pine.GSO.4.44.0211270929021.12471-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 27 Nov 2002, Choi, Don wrote:
    > It has been a policy of the current U.S. administration and the previous
    > administration to use products and services based on commercial standards,
    > not based on military standards.
    > We (DISA) think that IETF is the place to develop these standards.

Do you really not see the contradiction here?  "We want to buy an
off-the-shelf solution that has shared fate with what other people want.
Therefore you must redesign your product to meet our exact
specifications and convince everyone else to buy something other than
what they want?"

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 12:37:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20965
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 12:37:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARHe3O12031
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 12:40:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHe3v12028
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 12:40:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20909
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 12:37:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHd1v11831;
	Wed, 27 Nov 2002 12:39:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHbDv11448
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 12:37:13 -0500
Received: from imo-r05.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20745
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:34:25 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r05.mx.aol.com (mail_out_v34.13.) id j.181.1295940c (24895);
	Wed, 27 Nov 2002 12:35:23 -0500 (EST)
Message-ID: <181.1295940c.2b165c5a@aol.com>
Date: Wed, 27 Nov 2002 12:35:22 EST
Subject: Re: [Ieprep] VoIP demo in Atlanta
To: rja@extremenetworks.com, nguyena@ncs.gov
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_181.1295940c.2b165c5a_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_181.1295940c.2b165c5a_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/27/2002 6:45:08 AM Eastern Standard Time, 
rja@extremenetworks.com writes:


> Dave Oran, who knows a fair bit about the internals of the IP phone that
> Bill was using for the demos, said that the particular IP phone that was 
> used
> for the demo always adds substantial implementation-specific FEC beneath the
> G.711 codec output and above UDP.  That is, this FEC is a normal property 
> of that
> particular IP phone in its default configuration.  


[MAP] Interesting addition to the the whole notion of VoIP. G.711 takes 
exactly 64 kbit/s in circuit mode. It has been generally said that it takes 
80 kbit/s over IP because of the overhead (similar to what the IETF liked to 
call "Cell Tax" when talking about ATM). If an FEC needs to be added to 
tolerate the commonly occurring packet loss ratio, what does this add to the 
required bandwidth? I would suspect at least another 10-15 kbit/s if it can 
tolerate a 40% packet loss ratio.

Perhaps Dave would like to tell us exactly what bandwidth this phone uses.

Mike Pierce
Artel


--part1_181.1295940c.2b165c5a_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/27/2002 6:45:08 AM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Dave Oran, who knows a fair bit about the internals of the IP phone that
<BR>Bill was using for the demos, said that the particular IP phone that was used
<BR>for the demo always adds substantial implementation-specific FEC beneath the
<BR>G.711 codec output and above UDP. &nbsp;That is, this FEC is a normal property of that
<BR>particular IP phone in its default configuration. &nbsp;</FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR>
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">[MAP] Interesting addition to the the whole notion of VoIP. G.711 takes exactly 64 kbit/s in circuit mode. It has been generally said that it takes 80 kbit/s over IP because of the overhead (similar to what the IETF liked to call "Cell Tax" when talking about ATM). If an FEC needs to be added to tolerate the commonly occurring packet loss ratio, what does this add to the required bandwidth? I would suspect at least another 10-15 kbit/s if it can tolerate a 40% packet loss ratio.
<BR>
<BR>Perhaps Dave would like to tell us exactly what bandwidth this phone uses.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_181.1295940c.2b165c5a_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 12:41:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21180
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 12:41:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARHhkW12310
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 12:43:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHhkv12307
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 12:43:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21132
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 12:40:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHh2v12222;
	Wed, 27 Nov 2002 12:43:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHgKv12185
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 12:42:20 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21034
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:39:31 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gARHa6d12618;
	Wed, 27 Nov 2002 09:36:06 -0800 (PST)
Date: Wed, 27 Nov 2002 09:36:06 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: "'RJ Atkinson '" <rja@extremenetworks.com>,
        "'ieprep@ietf.org '" <ieprep@ietf.org>
Subject: RE: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D8E@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211270918240.12414-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > Sorry I was not there for the demos. I wondered if you took into account the
    > peak internet usage time when you gave the demos. I heard the demos were
    > given around 4:00PM EST( please correct me if I am wrong). That would have
    > been around 3:00 or 4:00 AM in Nairobi?

I don't remember the exact times, I do remember that, Brian's time, one
was about 8pm, and the other about 10pm.  However, that's not terribly
relevant, since those were just two phone calls, and these phones are used
day in and day out, during business hours, evening hours, et cetera.  The
point was that this works really well, not that two specific calls worked
really well.

    > It would be nice if you could show us that given the traffic utilization
    > factor of , say, from .1 to 0.5, your voiceIP can still be good or something
    > to that extent.

It's not "my VoIP," it's an open standard.  It's _your_ VoIP!  :-)  If you
have doubts about it, why don't you actually try it yourself, and then the
doubts will go away, and you'll also start tying to avoid using the PSTN
whenever you can.  I'm not selling anything here, I don't need to.  I'm
just pointing out the obvious.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 12:49:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21453
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 12:49:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARHpiD12710
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 12:51:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHpiv12707
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 12:51:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21436
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 12:48:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHp2v12666;
	Wed, 27 Nov 2002 12:51:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHo5v12622
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 12:50:05 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21380
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:47:16 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gARHhod12679;
	Wed, 27 Nov 2002 09:43:50 -0800 (PST)
Date: Wed, 27 Nov 2002 09:43:50 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: sob@harvard.edu, <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: Re: [Ieprep] Use of ToS bits for "emergency" preferential treatment
In-Reply-To: <1c0.226395f.2b165c57@aol.com>
Message-ID: <Pine.GSO.4.44.0211270932250.12471-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 27 Nov 2002 Mpierce1@aol.com wrote:
    > > That's a host requirement, not a service provider requirement.
    > [MAP] I understand that the specific references are "Host Requirements", but
    > I have to believe that the point of this JTA requirement is that the 8-bit
    > field must be passed end-to-end (through "hosts", "routers", and whatever)
    > unchanged.

This is the IETF.  We're a _standards body_.  We _deal in specifics_.  Not
"whatevers."  That was a host requirement.  That means that it was
required of the manufacturers of hosts and their operating systems.
There's _also_ a router requirements standard, which specifies what's
required of routers.  There's _also_ a service providers requirements
standard, which specifies what's required of service providers.

Again, you're looking at the _host_ requirements.  That specifies, as
exactly as possible, what's required of _hosts_.  No one is asking you to
believe or surmise anything that's not clearly stated in the respective
standards.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 12:55:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21644
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 12:55:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARHvop12947
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 12:57:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHvov12944
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 12:57:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21628
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 12:55:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHv2v12911;
	Wed, 27 Nov 2002 12:57:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHuNv12874
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 12:56:23 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21550
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 12:53:34 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gARHoCd12720;
	Wed, 27 Nov 2002 09:50:12 -0800 (PST)
Date: Wed, 27 Nov 2002 09:50:12 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: rja@extremenetworks.com, <ieprep@ietf.org>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <175.126e5023.2b165c56@aol.com>
Message-ID: <Pine.GSO.4.44.0211270948120.12471-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 27 Nov 2002 Mpierce1@aol.com wrote:
    > We are trying to talk about "preparedness" for a traffic
    > overload/fault condition that has never occurred. It did not occur
    > on Sept 11 or in the "Baltimore Train Tunnel".

Right, so those were both examples of complete disconnection.  What's the
condition that you believe has never occurred?  Can you define it for us?
We're engineers; if you can define a problem, we can try to solve it.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 13:09:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22356
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 13:09:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARIBta14336
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 13:11:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIBtv14333
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 13:11:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22310
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 13:09:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIB6v14267;
	Wed, 27 Nov 2002 13:11:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIAUv14230
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 13:10:30 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22210
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 13:07:41 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gARI4Jd12811;
	Wed, 27 Nov 2002 10:04:19 -0800 (PST)
Date: Wed, 27 Nov 2002 10:04:19 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
cc: RJ Atkinson <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] a practical VoIP issue
In-Reply-To: <7480.1038400120@cs.ucl.ac.uk>
Message-ID: <Pine.GSO.4.44.0211271000510.12725-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 27 Nov 2002, Ken Carlberg wrote:
    > > If one really wants to be able to use Internet infrastructure during
    > > an emergency, designing a VoIP system that can do NAT/Firewall traversal
    > > might be a pretty important component.
    > yes, a good point. and its actually being worked on in another group,
    > as well as industry.

STUN is a finger-in-the-dike which a) isn't yet deployable and b) will be
of _very_ little help in the general case.  It's a really ugly hack on top
of a really ugly hack.  The problem is the NAT, and it doesn't solve that.
It only lets you detect it.  To generalize, all of the other NAT traversal
schemes I know of fall into about the same bucket.  They do what they say
they do, but that basically amounts to the statically-configured traversal
of a specific, friendly NAT which you also have configuration access to.
And we can deal with those _without_ STUN and its ilk, so they're not
actually all that helpful.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 13:16:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22758
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 13:16:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARIIjl14760
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 13:18:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIIjv14757
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 13:18:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22739
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 13:15:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIH1v14658;
	Wed, 27 Nov 2002 13:17:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIFVv14567
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 13:15:31 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22519
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 13:12:12 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gARIE0vV014542;
	Wed, 27 Nov 2002 13:14:00 -0500 (EST)
Date: Wed, 27 Nov 2002 13:14:00 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211271814.gARIE0vV014542@newdev.harvard.edu>
To: Mpierce1@aol.com, sob@harvard.edu, woody@pch.net
Subject: Re: [Ieprep] Use of ToS bits for "emergency" preferential treatment
Cc: ieprep@ietf.org, rja@extremenetworks.com
In-Reply-To: <1c0.226395f.2b165c57@aol.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> [MAP] So, I would still interpret that the DoD requirement is to pass the 8 
> bits unchanged, no matter what they have been renamed. Is this requirement 
> wrong or impossible to meet?

maybe meaningless - the two low order bits will be random and
change randomly where ECN is in used - the *function* they
seem to want (passing the QoS-related bits) is only relevent
to the high-order 6 bits

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 13:22:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22965
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 13:22:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARIOOs15107
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 13:24:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIOOv15104
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 13:24:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22954
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 13:21:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIN3v15023;
	Wed, 27 Nov 2002 13:23:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARILov14970
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 13:21:50 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22860
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 13:19:01 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gARIFdd12936;
	Wed, 27 Nov 2002 10:15:39 -0800 (PST)
Date: Wed, 27 Nov 2002 10:15:39 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
cc: RJ Atkinson <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <6736.1038399810@cs.ucl.ac.uk>
Message-ID: <Pine.GSO.4.44.0211271012030.12725-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 27 Nov 2002, Ken Carlberg wrote:
    > one caveat to keep in mind.  some ISPs place ICMP messages on separate
    > queues that can experience worse treatment (loss/delay) than other
    > flows.

That's CAR.  Yes, however it's actually not a separate queue, it's a drop
algorithm applied to the same queue.  So it affects drop rate but not
delay.  And it's only applied over a certain threshold, typically one that
constitutes a DoS attack.  So it's pretty obvious when it's being applied.

    > hence, traceroutes can be a bit deceptive at times.

As Ran pointed out, it doesn't affect the results of a traceroute, though
it may cause some of the return packets to be lost.  The answer that you
get is unaffected.

    > and yes, i'll conceded that the tier-1 ISPs in the states don't do this
    > between their peers :-)

Actually, depending upon who you condier a tier-1, I believe that some do.
It's certainly a common practice generally, between peers more than facing
customers, usually.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 13:22:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22987
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 13:22:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARIOTV15129
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 13:24:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIOSv15126
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 13:24:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22958
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 13:21:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIN5v15047;
	Wed, 27 Nov 2002 13:23:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIN0v15009
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 13:23:00 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA22890
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 13:20:11 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 27 Nov 2002 18:16:35 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XKBZA13J>; Wed, 27 Nov 2002 13:22:58 -0500
Message-ID: <B3FE60C05AD31D4C96E07EBC5000639E1D7FCA@EMSHQS2>
From: "Choi, Don" <choid@ncr.disa.mil>
To: "'Bill Woodcock'" <woody@pch.net>
Cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] problem context
Date: Wed, 27 Nov 2002 13:22:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Bill,

It is not exactly clear who are "we" "other people" and "they" in your
email. Assuming "we" are DoD, and "other people" and "they" are public, I do
not see why public has to buy what we want. I fail to see what we have to
buy has anything to do with what public has to buy. Industry builds and
sells more than one box. And I do not see "our (DoD) exact specifications".
We want IETF standards, not DoD specifications.

It may be possible that some parts of the industry where they have similar
requirements choose to buy products and services based on the IETF standards
that support DoD requirements. But this would be totally voluntary.

Don

-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Wednesday, November 27, 2002 12:31 PM
To: Choi, Don
Cc: 'RJ Atkinson'; ieprep; Scott Bradner
Subject: RE: [Ieprep] problem context


      On Wed, 27 Nov 2002, Choi, Don wrote:
    > It has been a policy of the current U.S. administration and the
previous
    > administration to use products and services based on commercial
standards,
    > not based on military standards.
    > We (DISA) think that IETF is the place to develop these standards.

Do you really not see the contradiction here?  "We want to buy an
off-the-shelf solution that has shared fate with what other people want.
Therefore you must redesign your product to meet our exact
specifications and convince everyone else to buy something other than
what they want?"

                                -Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 13:30:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23294
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 13:30:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARIX1h15582
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 13:33:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIX1v15579
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 13:33:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23275
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 13:30:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIW2v15535;
	Wed, 27 Nov 2002 13:32:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARIT0v15278
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 13:29:00 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23078
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 13:26:10 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gARIMnd13031;
	Wed, 27 Nov 2002 10:22:49 -0800 (PST)
Date: Wed, 27 Nov 2002 10:22:49 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: "Choi, Don" <choid@ncr.disa.mil>
cc: ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] problem context
In-Reply-To: <B3FE60C05AD31D4C96E07EBC5000639E1D7FCA@EMSHQS2>
Message-ID: <Pine.GSO.4.44.0211271018270.12725-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Wed, 27 Nov 2002, Choi, Don wrote:
    > I fail to see what we have to buy has anything to do with what
    > public has to buy.

Forgive me if I'm drawing an insupportable conclusion, but it's always
been my assumption that when the government talked about preferring
off-the-shelf solutions to ones custom-tailored for it at higher cost, the
intent was to buy _off-the-shelf solutions_ (what the public buys) rather
than ones _custom-tailored for it at higher cost_ (what the military
prefers to buy).  The two principal benefits being greater practicality
due to greater shared fate with those who pay most of the money, and a
lowered cost of operation.

    > We want IETF standards, not DoD specifications.

We've got a plethora to choose from.  There's certainly no need for any
more in this area, particularly in advance of a needs assessment.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 14:41:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25649
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 14:41:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARJiE020065
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 14:44:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARJiEv20062
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 14:44:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25642
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 14:41:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARJb6v19451;
	Wed, 27 Nov 2002 14:37:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARJa4v19215
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 14:36:04 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25419
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 14:33:16 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.2/8.12.2) id gARJZ6xt014917;
	Wed, 27 Nov 2002 14:35:06 -0500 (EST)
Date: Wed, 27 Nov 2002 14:35:06 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200211271935.gARJZ6xt014917@newdev.harvard.edu>
To: choid@ncr.disa.mil, Mpierce1@aol.com, rja@extremenetworks.com
Subject: Re: [Ieprep] problem context
Cc: ieprep@ietf.org
In-Reply-To: <192.115dfe21.2b165c55@aol.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> [MAP] Yes, we believe that some of the solutions (read: mechanisms) should be 
> DiffServ enhancements, 

they could also be diffserv usages  (i.e. no enhancements required)

Scott
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 16:31:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28399
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 16:31:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARLY4w26091
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 16:34:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARLY4v26088
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 16:34:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28386
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 16:31:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARLXFv26062;
	Wed, 27 Nov 2002 16:33:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARLWgv25946
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 16:32:42 -0500
Received: from dewberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28305
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 16:29:52 -0500 (EST)
Received: from cs.columbia.edu (slip-32-100-239-250.ca.us.prserv.net [32.100.239.250])
	(user=hgs10 mech=PLAIN bits=0)
	by dewberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gARLW6Lp027645
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 27 Nov 2002 16:32:17 -0500 (EST)
Message-ID: <3DE51A2E.2060306@cs.columbia.edu>
Date: Wed, 27 Nov 2002 14:17:02 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: "Joel M. Halpern" <joel@stevecrocker.com>, ieprep@ietf.org
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
References: <39D3862C-018D-11D7-B29D-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Let me try a few additional angles on this problem.

- I don't think we need to posit that any mechanism be universal for it 
to be useful. Since this is all about probabilities, any *helpful* 
mechanism is a net gain. (In other words, we should only look at the 
mechanisms that don't require some critical mass to operate.)

- I think it would be helpful if we more clearly distinguished two 
scenarios, namely the "controlled edge" and the "opportunistic edge" 
(since we're talking primarily about modifying edge properties). In the 
'controlled edge', an emergency responder would use a network controlled 
by some (say) government entity. There, lots of things become possible. 
If necessary, one can do congestion control by pulling rank.

The second scenario is the opportunistic edge: an authorized person 
takes over some existing commercial facility or asks for assistance. 
There, at best, the local owner can assist.

- I'm not convinced that a static traffic classifier is particularly 
helpful for edge prioritization needs. I can see three possible types of 
classification:

(P) by protocol; e.g., prioritize UDP (under the assumption that 
time-critical application use it);
(A) by source or destination address;
(N) by port number

or some combination of these. (P) seems too crude and too much subject 
to DDOS attacks, either inbound or outbound. The attacker has to guess 
nothing.

(A) doesn't work for our needs, since the destination of emergency 
communication is generally unknown and can be anywhere in the Internet. 
It does work pretty well for VPNs.

(N) looks more promising, except that it has similar problems to (P). If 
the number of ports is small, this requires extensive coordination. All 
applications would have to be 'trained' to use these ports. If everybody 
uses the same "emergency" port, any modest security-by-obscurity would 
be blown and the port would become an inviting DDOS target.

Thus, I don't think that COS-by-filter is particularly helpful here.

An alternate model might be worth considering: Assume for a moment that 
we have an NSIS protocol that is suitable for edge QoS control. (I 
realize that some have well-founded doubts whether this will ever get 
deployed, but that would be something to discuss with the NSIS working 
group, I presume.) One of the primary scaling problems with existing 
resource control approaches is not the protocol itself but rather the 
AAA backend. Among other things, when the network is under the weather, 
having to go and ask some faraway places for authorization is not 
exactly probability-of-completion-enhancing.

However, fortunately, the problem here is somewhat easier. Authorized 
emergency personnel could easily have a cert signed by the local 
authorities that authorizes them to use the resources, similar to the 
GETS mechanism. The local NSIS entity doesn't have to worry about that 
Officer Smith gets charged vs. Officer Jones nor may be particularly 
concerned whether Officer Smith still has an "account", as long as it 
trusts the issuing authority and certs get issued with some reasonable 
frequency. Thus, this requires only a single CA entry in the NSIS 
router, without the usual complexity. One can forego any CRL checking in 
all likelihood, given that rogue officers can presumably be dealt with 
in other ways after the fact. Since the volume of emergency calls in any 
particular place is likely to be low, the additional PK verification 
delay is not likely to matter much either - it doesn't have to scale to 
every single phone call or web access. (Rohan and I discussed this 
roughly in Atlanta; he may not agree with the details above.)

Using a dynamic filter avoids the DOS problem and should have no 
complexity impact on the rest of Internet.

Thus, if this makes sense, it might be worth asking the NSIS working 
group to consider such requirements, in the spirit of the SIPPING effort.

Henning

> 
> Everything in Joel's note makes sense to me.  The last bit also applies 
> to me
> and I should mention it more often.  I'm pretty indifferent about what 
> useless
> gorp folks choose to put into SIP or other applications -- provided 
> there is not
> an increased in implemented/deployed gorp at the layers below the 
> Application Layer.
> 


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 16:31:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28414
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 16:31:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARLY6p26106
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 16:34:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARLY6v26103
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 16:34:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28390
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 16:31:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARLXDv26044;
	Wed, 27 Nov 2002 16:33:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARLW6v25932
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 16:32:06 -0500
Received: from marionberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28301
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 16:29:16 -0500 (EST)
Received: from cs.columbia.edu (slip-32-100-239-250.ca.us.prserv.net [32.100.239.250])
	(user=hgs10 mech=PLAIN bits=0)
	by marionberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id gARLVk4e019161
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 16:31:52 -0500 (EST)
Message-ID: <3DE51707.4070704@cs.columbia.edu>
Date: Wed, 27 Nov 2002 14:03:35 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'ieprep@ietf.org'" <ieprep@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] "BCP" for emergency app designers
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Given all the discussion we've had along the way about who can do what, 
I wonder if one productive output of the WG might be a set of guidelines 
for designers of emergency communications applications. I'm not sure yet 
whether this will turn out to be more than motherhood/apple-pie/turkey 
statements ("use a robust codec"), but there might be some principles 
that are more in the zero-conf domain. For example, it is probably a 
good idea to design applications so that they remain useful in network 
islands. (As one simple example, one might be a bit more generous with 
DNS timeouts and rather use some old data for an A record rather than 
just giving up.) Basically, things should work even if the DHCP server, 
DNS server and maybe part of the routing infrastructure are 
dysfunctional. (See the application-overlay-routing work that's been 
done at MIT, I believe.)

Maybe this is just zeroconf, but this is kind of an "involuntary" zeroconf.

Henning


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Nov 27 17:26:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00275
	for <ieprep-archive@odin.ietf.org>; Wed, 27 Nov 2002 17:26:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARMTDr30060
	for ieprep-archive@odin.ietf.org; Wed, 27 Nov 2002 17:29:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARMTDv30057
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 17:29:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00244
	for <ieprep-web-archive@ietf.org>; Wed, 27 Nov 2002 17:26:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARMS3v29943;
	Wed, 27 Nov 2002 17:28:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARMRLv29918
	for <ieprep@optimus.ietf.org>; Wed, 27 Nov 2002 17:27:21 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00164
	for <ieprep@ietf.org>; Wed, 27 Nov 2002 17:24:30 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18HAeG-00025H-00; Wed, 27 Nov 2002 17:27:12 -0500
Date: Wed, 27 Nov 2002 17:27:12 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: "Nguyen, An" <nguyena@ncs.gov>
cc: "'Bill Woodcock '" <woody@pch.net>,
        "'RJ Atkinson '" <rja@extremenetworks.com>,
        "'ieprep@ietf.org '" <ieprep@ietf.org>
Subject: Try it, you might like it RE: [Ieprep] any commercial usage for
 "emergency QoS"?
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D8E@emshqs1.ncr.disa.mil>
Message-ID: <Pine.GSO.4.44.0211271722430.7997-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

On Wed, 27 Nov 2002, Nguyen, An wrote:
> It would be nice if you could show us that given the traffic utilization
> factor of , say, from .1 to 0.5, your voiceIP can still be good or something
> to that extent.

I have an idea, why not buy an IP Phone and try it yourself?


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 00:52:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10364
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 00:52:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAS5t7R19246
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 00:55:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS5t7v19243
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 00:55:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10361
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 00:52:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS5p9v19155;
	Thu, 28 Nov 2002 00:51:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS5otv19133
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 00:50:55 -0500
Received: from mail1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10244
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 00:48:00 -0500 (EST)
Received: from bgreenew2k (dhcp-10-24-19-69.cisco.com [10.24.19.69]) by mail1.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id VAA18925; Wed, 27 Nov 2002 21:50:38 -0800 (PST)
Reply-To: <bgreene@cisco.com>
From: "Barry Raveendran Greene" <bgreene@cisco.com>
To: "Choi, Don" <choid@ncr.disa.mil>, "'Bill Woodcock'" <woody@pch.net>
Cc: "ieprep" <ieprep@ietf.org>
Subject: RE: [Ieprep] problem context
Date: Wed, 27 Nov 2002 21:50:18 -0800
Message-ID: <LNEHJBNJAPFNLEGJHCPEGEOIKIAA.bgreene@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <B3FE60C05AD31D4C96E07EBC5000639E1D7FCA@EMSHQS2>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

[Pardon me for being behind, but the volume of "stuff" on this alias is a
bit overwhelming.]

"We want IETF standards, not DoD specifications."

Keep in mind - an IETF "standard" is something that has been peer reviewed,
coded, and used.  That last part "used" is one of the major things that make
the IETF world different from the rest of the standards communities.  Taking
a document all the way to an official  "Internet Standard" is hard.

So, set you expectations.



-----Original Message-----
From: ieprep-admin@ietf.org [mailto:ieprep-admin@ietf.org]On Behalf Of Choi,
Don
Sent: Wednesday, November 27, 2002 10:23 AM
To: 'Bill Woodcock'
Cc: ieprep
Subject: RE: [Ieprep] problem context

Bill,

It is not exactly clear who are "we" "other people" and "they" in your
email. Assuming "we" are DoD, and "other people" and "they" are public, I do
not see why public has to buy what we want. I fail to see what we have to
buy has anything to do with what public has to buy. Industry builds and
sells more than one box. And I do not see "our (DoD) exact specifications".
We want IETF standards, not DoD specifications.

It may be possible that some parts of the industry where they have similar
requirements choose to buy products and services based on the IETF standards
that support DoD requirements. But this would be totally voluntary.

Don

-----Original Message-----
From: Bill Woodcock [mailto:woody@pch.net]
Sent: Wednesday, November 27, 2002 12:31 PM
To: Choi, Don
Cc: 'RJ Atkinson'; ieprep; Scott Bradner
Subject: RE: [Ieprep] problem context


      On Wed, 27 Nov 2002, Choi, Don wrote:
    > It has been a policy of the current U.S. administration and the
previous
    > administration to use products and services based on commercial
standards,
    > not based on military standards.
    > We (DISA) think that IETF is the place to develop these standards.

Do you really not see the contradiction here?  "We want to buy an
off-the-shelf solution that has shared fate with what other people want.
Therefore you must redesign your product to meet our exact
specifications and convince everyone else to buy something other than
what they want?"

                                -Bill

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 01:24:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10861
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 01:24:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAS6R2u20745
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 01:27:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS6R1v20742
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 01:27:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10849
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 01:24:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS6N3v20601;
	Thu, 28 Nov 2002 01:23:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS6Mrv20581
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 01:22:53 -0500
Received: from samsara.kgbinternet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10794
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 01:19:57 -0500 (EST)
Received: (from nobody@localhost)
	by samsara.kgbinternet.com (8.11.6/8.11.6) id gAS6Mfn18739;
	Thu, 28 Nov 2002 00:22:41 -0600
Date: Thu, 28 Nov 2002 00:22:41 -0600
Message-Id: <200211280622.gAS6Mfn18739@samsara.kgbinternet.com>
X-Authentication-Warning: samsara.kgbinternet.com: nobody set sender to carl@ietfwatch.net using -f
From: "Carl Ford" <carl@ietfwatch.net>
To: Bill Woodcock <woody@pch.net>, Mpierce1@aol.com, rja@extremenetworks.com,
        <ieprep@ietf.org>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
X-Mailer: Open WebMail 1.52 20011204
X-OriginatingIP: 67.81.93.146 (ietfwatch.carl)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

My first question would be what if access were to be unattainable to the Internet.  

When Hurrican Floyd hit north jersey,  we lost the tandem and therefore access to the 
outside world from the PSTN, the Internet worked because it was more redundant than 
the local switch.  But fundamentally the question that should be asked is what 
scenarios are there that would make the Internet inaccessible and what should be 
done to prepare for that.  Am I making sense?

kind regards,

carl


> On Wed, 27 Nov 2002 Mpierce1@aol.com wrote:
>     > We are trying to talk about "preparedness" for a traffic
>     > overload/fault condition that has never occurred. It did not occur
>     > on Sept 11 or in the "Baltimore Train Tunnel".
> 
> Right, so those were both examples of complete disconnection.  What's the
> condition that you believe has never occurred?  Can you define it for us?
> We're engineers; if you can define a problem, we can try to solve it.
> 
>                                 -Bill
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 01:24:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10874
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 01:24:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAS6R4B20760
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 01:27:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS6R4v20757
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 01:27:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10854
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 01:24:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS6N4v20619;
	Thu, 28 Nov 2002 01:23:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS6Mrv20583
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 01:22:53 -0500
Received: from samsara.kgbinternet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10795
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 01:19:57 -0500 (EST)
Received: (from nobody@localhost)
	by samsara.kgbinternet.com (8.11.6/8.11.6) id gAS6Mfu18737;
	Thu, 28 Nov 2002 00:22:41 -0600
Date: Thu, 28 Nov 2002 00:22:41 -0600
Message-Id: <200211280622.gAS6Mfu18737@samsara.kgbinternet.com>
X-Authentication-Warning: samsara.kgbinternet.com: nobody set sender to carl@ietfwatch.net using -f
From: "Carl Ford" <carl@ietfwatch.net>
To: Bill Woodcock <woody@pch.net>, Mpierce1@aol.com, rja@extremenetworks.com,
        <ieprep@ietf.org>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
X-Mailer: Open WebMail 1.52 20011204
X-OriginatingIP: 67.81.93.146 (ietfwatch.carl)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

My first question would be what if access were to be unattainable to the Internet.  

When Hurrican Floyd hit north jersey,  we lost the tandem and therefore access to the 
outside world from the PSTN, the Internet worked because it was more redundant than 
the local switch.  But fundamentally the question that should be asked is what 
scenarios are there that would make the Internet inaccessible and what should be 
done to prepare for that.  Am I making sense?

kind regards,

carl


> On Wed, 27 Nov 2002 Mpierce1@aol.com wrote:
>     > We are trying to talk about "preparedness" for a traffic
>     > overload/fault condition that has never occurred. It did not occur
>     > on Sept 11 or in the "Baltimore Train Tunnel".
> 
> Right, so those were both examples of complete disconnection.  What's the
> condition that you believe has never occurred?  Can you define it for us?
> We're engineers; if you can define a problem, we can try to solve it.
> 
>                                 -Bill
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 01:38:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11120
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 01:38:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAS6f0D21773
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 01:41:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS6f0v21770
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 01:41:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11116
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 01:38:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS6b2v21119;
	Thu, 28 Nov 2002 01:37:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS6aKv21039
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 01:36:20 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11036
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 01:33:25 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAS6Tvo16955;
	Wed, 27 Nov 2002 22:29:58 -0800 (PST)
Date: Wed, 27 Nov 2002 22:29:57 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Carl Ford <carl@ietfwatch.net>
cc: Mpierce1@aol.com, <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <200211280622.gAS6Mfu18737@samsara.kgbinternet.com>
Message-ID: <Pine.GSO.4.44.0211272225590.16789-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 28 Nov 2002, Carl Ford wrote:
    > My first question would be what if access were to be unattainable
    > to the Internet.

That certainly happens, as we've all noticed from time to time.  And when
it does, no amount of QoS or additional rules or more fragile routers or
guys with guns are going to move your packets for you.  The only thing
that's going to help is having your connectivity restored, and the only
way that'll happen quickly is if you share fate with the largest number of
other users.  That is, when there's a problem, you _really_ want to be
_just like everybody else_, since the aggregated bulk of the users are the
ones who'll be restored first.

    > But fundamentally the question that should be asked is what
    > scenarios are there that would make the Internet inaccessible and
    > what should be done to prepare for that.

Keep a candle, some matches, and a good book handy?  :-)

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 07:21:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26368
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 07:21:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gASCNvt16934
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 07:23:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASCNvv16931
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 07:23:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26352
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 07:21:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASCN7v16891;
	Thu, 28 Nov 2002 07:23:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASCMPv16868
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 07:22:25 -0500
Received: from mtiwmhc12.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26313
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 07:19:37 -0500 (EST)
Received: from cs.columbia.edu ([12.84.225.123])
          by mtiwmhc12.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP
          id <20021128122158.SVTV13909.mtiwmhc12.worldnet.att.net@cs.columbia.edu>;
          Thu, 28 Nov 2002 12:21:58 +0000
Message-ID: <3DE609FC.7040303@cs.columbia.edu>
Date: Thu, 28 Nov 2002 07:20:12 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Accounting
References: <1B77A3AA-020B-11D7-9C68-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Quick responses:
- There is (slow) work in the SIPPING WG on accounting requirements for 
SIP-related sessions. Sankaran Narayanan and I have put out a draft for 
DIAMETER enhancements and there is also requirements work. (We also had 
an earlier RADIUS draft, but RADIUS is no longer politically correct. 
Cisco has a proprietary set of RADIUS enhancements for VoIP services, I 
believe.)

My understanding of the Atlanta discussion was that this was a major 
facet of the problem.

- There are probably two modes that matter: when connecting to a 
traditional circuit-switched network and otherwise. For CSN, the typical 
dial-in-style by-the-minute accounting probably works just fine. For 
hypothetical bill-by-the-byte services, doing accounting at the SIP 
layer makes little sense.

I think there was some sense that this was actually more about auditing 
than traditional send-a-paper-bill type of accounting.

Yes, there's a SIP MIB, but I doubt that it would make a good accounting 
interface. (It doesn't do timestamping of requests, for example.)

RJ Atkinson wrote:
> 
> So I remain very confused about what the accounting advocates
> are asking for.  I might be slower than most to puzzle some
> stuff out, but what I got out of the Accounting presentation
> was roughly this:
> 
>     - Accounting is a requirement.
>     - We don't mean that packet accounting is a requirement.
> 
> Which begs the question of precisely which stuff folks think operators
> need to perform accounting on.  Scott Bradner suggested that maybe
> folks meant that there should be some form of accounting within SIP.
> Is that suggestion correct ?
> 
> I'd really like to understand precisely what folks think is required.
> 
> When folks say that "accounting is a requirement" do they really
> mean that " A SIP implementation must be able to perform accounting
> for (some specific list of objects/events)" or mean something else ?
> 
> - If the quoted sentence above is close, could folks please be specific and
>     enumerate which specific objects/events need to have accounting 
> support ?
> - If something else, then please be specific and tell us what exactly
>     folks want to perform accounting on ?
> 
> I don't know off-hand whether a (draft) SIP MIB exists yet or not.
> If folks are thinking about accounting within SIP and if a (draft)
> SIP MIB exists, could those folks please check and see if the MIB
> already has counters for the objects/events of concern ?  And if
> the (draft) MIB exists and is missing objects/events, maybe those
> particular objects could be requested from the WG that is working
> on the MIB ?
> 
> Also, would it be consistent with the Accounting advocates desires to
> say something like this:
> 
>     Network operators that do not operate (SIP servers) are not required
>     to perform any accounting in order to support IEprep services.
> 
> If yes, then that is a good start and could we please document that
> understanding some place.
> 
> If not, what edits to "(SIP servers)" would make that sentence true ?
> In other words, what accounting do the accounting advocates want ISPs
> to perform particularly to support IEprep services ?
> 
> Thanks,
> 
> Ran
> rja@extremenetworks.com
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 07:39:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26650
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 07:39:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gASCfj018106
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 07:41:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASCfiv18103
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 07:41:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26630
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 07:38:57 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASCf4v18090;
	Thu, 28 Nov 2002 07:41:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASCeKv18065
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 07:40:20 -0500
Received: from mtiwmhc13.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26627
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 07:37:32 -0500 (EST)
Received: from cs.columbia.edu ([12.84.225.123])
          by mtiwmhc13.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP
          id <20021128124016.FCAU24110.mtiwmhc13.worldnet.att.net@cs.columbia.edu>;
          Thu, 28 Nov 2002 12:40:16 +0000
Message-ID: <3DE60E2F.7040400@cs.columbia.edu>
Date: Thu, 28 Nov 2002 07:38:07 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: Bill Woodcock <woody@pch.net>, ieprep@ietf.org
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
References: <BAD75957-01B2-11D7-8014-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

One should also add to this demo that it would have supported roughly 5 
people making phone calls simultaneously, if I remember the link 
bandwidth description correctly. (The codec used was G.711, I believe, 
since that's the default Cisco 7960 codec.)


RJ Atkinson wrote:
> 
> On Tuesday, Nov 26, 2002, at 21:31 America/Montreal, Bill Woodcock wrote:
> 
>>> By the way, during the Nairobi VoIP demo in Atlanta, was there any
>>> use of IP ToS bits, DiffServ, or other QoS ?
>>
>>
>> Nope.  We wanted it to work.  Demos which fail aren't as impressive.
> 
> 
> So the demo might be an existance proof that VoIP works fine over
> a set of best-effort IP networks across 2-3 continents ?
> 
> Do you happen to have a traceroute handy for that to document how
> many ASs, hops, and continents that the demo traversed ?  (Feel free
> to omit the last few IP addresses since this list is permanently archived;
> we don't want to accidentally encourage bored folks to attack the
> innocent user in Nairobi).
> 
> Ran
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 07:40:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26698
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 07:40:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gASCgbr18155
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 07:42:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASCgbv18152
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 07:42:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26664
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 07:39:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASCg0v18133;
	Thu, 28 Nov 2002 07:42:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASCfwv18119
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 07:41:58 -0500
Received: from mtiwmhc12.worldnet.att.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26638
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 07:39:10 -0500 (EST)
Received: from cs.columbia.edu ([12.84.225.123])
          by mtiwmhc12.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP
          id <20021128124131.SZKX13909.mtiwmhc12.worldnet.att.net@cs.columbia.edu>;
          Thu, 28 Nov 2002 12:41:31 +0000
Message-ID: <3DE60E91.706@cs.columbia.edu>
Date: Thu, 28 Nov 2002 07:39:45 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Woodcock <woody@pch.net>
CC: RJ Atkinson <rja@extremenetworks.com>, ieprep@ietf.org
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
References: <Pine.GSO.4.44.0211261844030.6731-100000@paixhost.pch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I did ping tests very shortly after the demo. I measured 7% packet loss 
from the wireless IETF network and from Columbia, averaged over roughly 
200 packets. Sorry to say, even the Cisco phone doesn't sound like this 
with 40% packet loss.

Bill Woodcock wrote:
>     > Do you happen to have a traceroute handy for that to document how
>     > many ASs, hops, and continents that the demo traversed ?
> 
> We had the slide (which I'll put up permanently) showing how many hops,
> AS path length, loss, and latency across a full-mesh of myself, Scott
> Bradner, Patrik Faltstrom, and Brian Longwe.  We also have a traceroute
> (attached) from the day before, showing the path from Nairobi to the
> hotel.  Both times we were getting variable loss, up to about 40%.
> Most of those outward-facing IPs seem to be ICMP-blocked, so that's a
> little hard to replicate at the moment.
> 
>                                 -Bill
> 
> 
> 
>   1     6 ms     3 ms     3 ms  192.168.14.1
>   2    13 ms    15 ms    16 ms  64.86.232.121
>   3    41 ms    54 ms    30 ms  64.86.231.9
>   4    27 ms    70 ms    48 ms  64.86.231.1
>   5   622 ms   636 ms   619 ms  212.49.70.105
>   6   641 ms   618 ms   620 ms  216.129.151.150
>   7   619 ms   593 ms   642 ms  216.129.151.149
>   8   621 ms   627 ms   634 ms  216.129.150.249
>   9   635 ms   613 ms   602 ms  66.133.0.45
>  10   614 ms   602 ms   696 ms  209.244.160.241
>  11   612 ms   645 ms   612 ms  64.159.17.38
>  12   639 ms   609 ms   631 ms  209.244.160.150
>  13   608 ms   621 ms   660 ms  129.250.3.48
>  14   639 ms   620 ms   656 ms  129.250.5.99
>  15   648 ms   641 ms   644 ms  129.250.2.180
>  16   643 ms   628 ms   643 ms  129.250.2.49
>  17   671 ms   636 ms   674 ms  129.250.26.227
>  18   633 ms   641 ms   655 ms  157.238.161.202
>  19   672 ms   639 ms   646 ms  204.42.70.246
> 
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 08:55:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27944
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 08:55:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gASDvp621508
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 08:57:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASDvpv21505
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 08:57:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27927
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 08:55:04 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASDv6v21476;
	Thu, 28 Nov 2002 08:57:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASDurv21453
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 08:56:53 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA27912
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 08:54:04 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 28 Nov 2002 13:50:27 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XKBZARNQ>; Thu, 28 Nov 2002 08:56:53 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D97@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'RJ Atkinson '" <rja@extremenetworks.com>
Cc: "'Bill Woodcock '" <woody@pch.net>,
        "'ieprep@ietf.org '"
	 <ieprep@ietf.org>
Subject: RE: [Ieprep] any commercial usage for "emergency QoS"?
Date: Thu, 28 Nov 2002 08:56:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Probably, G.711 with Packet Loss Consealment (PLC) was implemented on the
Cisco 7960. PLC basically derives AT RANDOM missing or late packets from the
previous or subsequent ones in the jitter buffer. If packet loss is over
20%, users will definitely notice the QoS degradation ... 

Please read this to find out.

http://www.cconvergence.com/article/CTM20021005S0009

Regards,

An 


-----Original Message-----
From: Henning Schulzrinne
To: RJ Atkinson
Cc: Bill Woodcock; ieprep@ietf.org
Sent: 11/28/02 7:38 AM
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?

One should also add to this demo that it would have supported roughly 5 
people making phone calls simultaneously, if I remember the link 
bandwidth description correctly. (The codec used was G.711, I believe, 
since that's the default Cisco 7960 codec.)


RJ Atkinson wrote:
> 
> On Tuesday, Nov 26, 2002, at 21:31 America/Montreal, Bill Woodcock
wrote:
> 
>>> By the way, during the Nairobi VoIP demo in Atlanta, was there any
>>> use of IP ToS bits, DiffServ, or other QoS ?
>>
>>
>> Nope.  We wanted it to work.  Demos which fail aren't as impressive.
> 
> 
> So the demo might be an existance proof that VoIP works fine over
> a set of best-effort IP networks across 2-3 continents ?
> 
> Do you happen to have a traceroute handy for that to document how
> many ASs, hops, and continents that the demo traversed ?  (Feel free
> to omit the last few IP addresses since this list is permanently
archived;
> we don't want to accidentally encourage bored folks to attack the
> innocent user in Nairobi).
> 
> Ran
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 09:10:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28157
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 09:10:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gASECjR22548
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 09:12:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASECjv22545
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 09:12:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28142
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 09:09:57 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASEC1v22531;
	Thu, 28 Nov 2002 09:12:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASEBWv22515
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 09:11:32 -0500
Received: from samsara.kgbinternet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28121
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 09:08:45 -0500 (EST)
Received: (from nobody@localhost)
	by samsara.kgbinternet.com (8.11.6/8.11.6) id gASEBRN01907;
	Thu, 28 Nov 2002 08:11:27 -0600
Date: Thu, 28 Nov 2002 08:11:27 -0600
Message-Id: <200211281411.gASEBRN01907@samsara.kgbinternet.com>
X-Authentication-Warning: samsara.kgbinternet.com: nobody set sender to carl@ietfwatch.net using -f
From: "Carl Ford" <carl@ietfwatch.net>
To: Bill Woodcock <woody@pch.net>, Carl Ford <carl@ietfwatch.net>,
        Mpierce1@aol.com, <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
X-Mailer: Open WebMail 1.52 20011204
X-OriginatingIP: 67.81.93.146 (ietfwatch.carl)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

I was hoping for a discussion on redundancy.  

As a "bell-head" I have been involved in providing customers with alternate serving 
wire centers and SONET.  Both were aimed at making the communication path more 
redundant, but both were from the same provider.  With the Internet my sense is that 
we can provide better redundancy by saying the following.

1 ISPs should be chosen that are not utilizing the same methodology of transport.  
Wireless, dial-up, dedicated (particularly if selected from an alternative carrier) all add 
to redundancy.

2) Internal Intranets that support multiple connection points to ISPs provide even more 
redundancy.  I am not sure here if it should be stated that some reserve to rebuild a 
backbone may be a good idea.

3) Security and QoS methodologies should be thought of as when available, and 
ingress into them should be planned for an any to any methodology.  Meaning it is 
great if we give the emergency services there own edge devices with priority services, 
but it probably more likely that they are going to have to connect up at a library / 
Internet Cafe using some low quality edge point to reach the Internet.

Am I making sense?

Kind Regards,

Carl Ford 




> On Thu, 28 Nov 2002, Carl Ford wrote:
>     > My first question would be what if access were to be unattainable
>     > to the Internet.
> 
> That certainly happens, as we've all noticed from time to time.  And when
> it does, no amount of QoS or additional rules or more fragile routers or
> guys with guns are going to move your packets for you.  The only thing
> that's going to help is having your connectivity restored, and the only
> way that'll happen quickly is if you share fate with the largest number of
> other users.  That is, when there's a problem, you _really_ want to be
> _just like everybody else_, since the aggregated bulk of the users are the
> ones who'll be restored first.
> 
>     > But fundamentally the question that should be asked is what
>     > scenarios are there that would make the Internet inaccessible and
>     > what should be done to prepare for that.
> 
> Keep a candle, some matches, and a good book handy?  :-)
> 
>                                 -Bill



--
Sent from KGB Internet Solutions OpenWebMail
http://www.kgbinternet.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 09:22:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28346
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 09:22:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gASEOg622969
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 09:24:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASEOgv22966
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 09:24:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28343
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 09:21:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASEO2v22953;
	Thu, 28 Nov 2002 09:24:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASENMv22922
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 09:23:22 -0500
Received: from [209.22.88.17] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA28335
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 09:20:35 -0500 (EST)
Received: from mtassp3.ncr.disa.mil by [209.22.88.17]
          via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; 28 Nov 2002 14:16:56 UT
Received: by mtassp3.ncr.disa.mil with Internet Mail Service (5.5.2653.19)
	id <XKBZARRV>; Thu, 28 Nov 2002 09:23:22 -0500
Message-ID: <7F18415E4D63CB45BB9B3A591F68D12D5B3D98@emshqs1.ncr.disa.mil>
From: "Nguyen, An" <nguyena@ncs.gov>
To: "'Sean Donelan '" <sean@donelan.com>
Cc: "''Bill Woodcock ' '" <woody@pch.net>,
        "''RJ Atkinson ' '"
	 <rja@extremenetworks.com>,
        "''ieprep@ietf.org ' '" <ieprep@ietf.org>
Subject: RE: Try it, you might like it RE: [Ieprep] any commercial usage f
	or "emergency QoS"?
Date: Thu, 28 Nov 2002 09:23:14 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

You see ... the nature of the NCS mission is to be able to use it in times
of emergency or network congestion, not during "Normal" time. That is why I
am interested in how it performs during "Non-normal" time. 

Speaking of VoiceIP deployment, you can ask DISA folks in Eagle Building to
see how happy they are. Ran might have some knowledge of it.

An

P.S. Ran, I did not mean to put you on a spot.


-----Original Message-----
From: Sean Donelan
To: Nguyen, An
Cc: 'Bill Woodcock '; 'RJ Atkinson '; 'ieprep@ietf.org '
Sent: 11/27/02 5:27 PM
Subject: Try it, you might like it RE: [Ieprep] any commercial usage for
"emergency QoS"?

On Wed, 27 Nov 2002, Nguyen, An wrote:
> It would be nice if you could show us that given the traffic
utilization
> factor of , say, from .1 to 0.5, your voiceIP can still be good or
something
> to that extent.

I have an idea, why not buy an IP Phone and try it yourself?

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Nov 28 11:32:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29974
	for <ieprep-archive@odin.ietf.org>; Thu, 28 Nov 2002 11:32:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gASGYxV28919
	for ieprep-archive@odin.ietf.org; Thu, 28 Nov 2002 11:34:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASGYxv28916
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 11:34:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29959
	for <ieprep-web-archive@ietf.org>; Thu, 28 Nov 2002 11:32:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASGY7v28883;
	Thu, 28 Nov 2002 11:34:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASGXqv28866
	for <ieprep@optimus.ietf.org>; Thu, 28 Nov 2002 11:33:52 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29939
	for <ieprep@ietf.org>; Thu, 28 Nov 2002 11:31:03 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gASGRdo20437;
	Thu, 28 Nov 2002 08:27:39 -0800 (PST)
Date: Thu, 28 Nov 2002 08:27:39 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Carl Ford <carl@ietfwatch.net>
cc: Mpierce1@aol.com, <rja@extremenetworks.com>, <ieprep@ietf.org>
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
In-Reply-To: <200211281411.gASEBRN01907@samsara.kgbinternet.com>
Message-ID: <Pine.GSO.4.44.0211280825100.20376-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Thu, 28 Nov 2002, Carl Ford wrote:
    > 1 ISPs should be chosen that are not utilizing the same methodology of transport.
    > 2) Internal Intranets that support multiple connection points to ISPs

Yes, those are current best-practices, and widely followed.

There's actually fairly active discussion of that first point an many
mailing lists, since people always want to make sure that the ISPs they
buy fron share as little _upstream_ commonality as possible, as well.
This is sometimes thought to be in conflict with the sometimes-professed
goal of regional aggregation, but I think that's a reasonable sacrifice.

    > 3) Security and QoS methodologies should be thought of as when available, and
    > ingress into them should be planned for an any to any methodology.  Meaning it is
    > great if we give the emergency services there own edge devices with priority services,
    > but it probably more likely that they are going to have to connect up at a library /
    > Internet Cafe using some low quality edge point to reach the Internet.

Yes, I agree.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 09:45:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00872
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 09:45:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATEluU03542
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 09:47:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATEluv03539
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 09:47:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00861
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 09:45:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATElBv03518;
	Fri, 29 Nov 2002 09:47:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATEkdv03490
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 09:46:39 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00851
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 09:43:51 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.153])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 111207A0A; Fri, 29 Nov 2002 06:46:31 -0800 (PST)
Date: Fri, 29 Nov 2002 09:42:40 -0500
Subject: Re: [Ieprep] problem context
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: "Choi, Don" <choid@ncr.disa.mil>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <B3FE60C05AD31D4C96E07EBC5000639E1D7FC8@EMSHQS2>
Message-Id: <CFFE6369-03A8-11D7-9A09-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 27, 2002, at 11:37 America/Montreal, Choi, Don wrote:
> What DoD wants is, simply put, when a mission critical user makes a 
> call,
> the call goes through and stays up. It does not say calls have to be
> pre-empted nor packets should be dropped.

	It is very helpful to get the objective outlined and on the table.
Thanks much for that.

	I had thought MLPP meant "Multi-Level Precedence & Pre-emption",
but that must be a misunderstanding since you seem to say above that
"pre-emption" is not part of the requirement.  Please help me understand
whether pre-emption (e.g. dropping other packets at the IP-layer,
dropping other calls inside a SIP server) is a requirement.

	I assume "calls" means "telephony applications running over IP";
if that isn't your meaning, please clarify.

	Is that for "calls" on DoD IP networks (e.g. NIPRnet, SIPRnet, base 
LANs,
service-specific or agency-specific networks), on commercial networks 
where no
DoD contract is present, for DoD networks operated by a contractor 
(e.g. DREN),
or for some other scope of networks ?

	Also, is the scope limited to VoIP applications ?  Or does it include 
all
IP-based applications ?

	I ask because according to some folks working on DISN, the scope of 
DISA objectives
is *broader* than just MLPP handling for voice calls, but instead 
includes application
of MLPP at the packet level (IP layer) to a broader array of 
applications that
might run over IP.  This causes me some confusion.

	Is your objective the same as the DISN folks' objective ?  Or are 
their multiple
objectives in different parts of DISA ?  Is the NCS objective for the 
commercial
world identical to the DISA objective for DoD IP networks ?

	Aside:  The big challenge with the objective you have outlined at the 
top is that
"The Internet" is *unaware of* voice calls.  "The Internet" as 
available from
commercial ISPs [1] deals in IP packets *only*.  Similarly, the current 
DISN
deployment mostly (no doubt some exceptions exist) deals just in IP 
packet transport
from an access router (e.g. at a base) across the WAN to another access 
router
(e.g. at a different base).

	Now there are some methods already outlined on this list, which mostly 
do not use
any IETF standard and do not require any new IETF standards, that can 
generally achieve
the objective you outline at the top.  Here is an example:

	- overprovision the backbone, but do not bother with QoS there (no 
standard needed)
	- enable router-based queuing on access routers (e.g. Sprint's CoS 
service)
		(router-based queuing is not subject to IETF standards; many vendors 
support it)
	- either overprovision the site LAN and/or deploy QoS within the
		single site (e.g. building, base, ship, plane).  (no standard needed)
		- Within a single site, enterprise users often deploy IEEE 802.1p
		  precedence inside an Ethernet LAN/MAN (IEEE standard exists; no 
IETF std relevant)
		and DiffServ/IP-ToS (IETF std exists already), combined with 
vendor-specific
		filter rules to apply/remove/modify QoS and QoS markings (router 
filters
		aren't subject to IETF standardisation, except maybe in a MIB spec; 
most
		vendors already support this).

> We are not saying the Internet has to support this requirement. This
> requirement is applicable only to the products and services to be sold 
> to
> DoD, and hopefully to our counterparts in other countries. The current
> international situation calls for not just interoperability within 
> DoD, but
> combined interoperability with our allies and partnership countries.

	It seems to me (and some others here who have agreed with the general
concept) that the solution approach I outlined just above will work for
the objective at the top.

	If I'm missing something, which I guess is likely, then please help me
understand what more you are seeking.  (I'm mostly an IP-layer and 
routing
kind of person these days, so I'm likely missing stuff up inside SIP or
elsewhere in the application layer because of my own ignorance.)

Ran
rja@extremenetworks.com


[1] ISPs are somewhat different from content providers.  The latter 
group
would include (by my own definition) folks such as MSN or AOL, each of 
whom
reportedly [2] outsources much of its WAN IP/dialup services to one or 
another
ISP.

[2] According to The Washington Post.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 13:08:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04548
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 13:08:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATIAR013483
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 13:10:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATIARv13480
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 13:10:27 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04519
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 13:07:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATI97v13445;
	Fri, 29 Nov 2002 13:09:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATI88v13408
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 13:08:08 -0500
Received: from imo-d05.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04442
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 13:05:17 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d05.mx.aol.com (mail_out_v34.13.) id j.8f.25c89d90 (3699);
	Fri, 29 Nov 2002 13:07:56 -0500 (EST)
Message-ID: <8f.25c89d90.2b1906fc@aol.com>
Date: Fri, 29 Nov 2002 13:07:56 EST
Subject: Re: [Ieprep] Accounting
To: rja@extremenetworks.com, ieprep@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 6.0 for Windows XP US sub 51
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

In a message dated 11/27/2002 9:20:51 AM Eastern Standard Time, 
rja@extremenetworks.com writes:


[RJA] So I remain very confused about what the accounting advocates
are asking for.  I might be slower than most to puzzle some
stuff out, but what I got out of the Accounting presentation
was roughly this:

    - Accounting is a requirement.
    - We don't mean that packet accounting is a requirement.

[MAP] We start with the requirement that any system that handles IEPREP or 
any kind of priority telephone calls must be capable of performing 
accounting, i.e., maintaining Call Detail Records. Just because packet 
technology is used, doesn't change the current requirement in any way. (And 
it doesn't change what a "call" is from the end user's perspective.)


[RJA] Which begs the question of precisely which stuff folks think operators
need to perform accounting on.  Scott Bradner suggested that maybe
folks meant that there should be some form of accounting within SIP.
Is that suggestion correct ?

[MAP] At the requirements level in IEPREP, we're trying to stay away from 
specific implementations (like SIP). However, I guess we all know that we're 
talking about SIP. I have to presume that the complete solution to the 
accounting requirements I've detailed would be in SIP. But I can't be certain 
that SIP is sufficient until we have an agreement on what the requirements 
are and then examine SIP.


[RJA] I'd really like to understand precisely what folks think is required.

When folks say that "accounting is a requirement" do they really
mean that " A SIP implementation must be able to perform accounting
for (some specific list of objects/events)" or mean something else ?

- If the quoted sentence above is close, could folks please be specific and
    enumerate which specific objects/events need to have accounting support ?
- If something else, then please be specific and tell us what exactly
    folks want to perform accounting on ?

[MAP] Any implementation that handles "call" setup must be able to perform 
accounting.

<snip>


[RJA] Also, would it be consistent with the Accounting advocates desires to
say something like this:

    Network operators that do not operate (SIP servers) are not required
    to perform any accounting in order to support IEprep services.

[MAP] Clearly if the solution is completely in SIP, the above sentence would 
be true. I suspect this is true.


Mike Pierce
Artel
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 13:15:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04768
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 13:15:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATIHiw13740
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 13:17:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATIHiv13737
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 13:17:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04763
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 13:14:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATIGRv13692;
	Fri, 29 Nov 2002 13:16:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATIA1v13474
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 13:10:01 -0500
Received: from imo-d04.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04508
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 13:07:10 -0500 (EST)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d04.mx.aol.com (mail_out_v34.13.) id j.19f.c7a9d1a (3699);
	Fri, 29 Nov 2002 13:09:18 -0500 (EST)
Message-ID: <19f.c7a9d1a.2b19074e@aol.com>
Date: Fri, 29 Nov 2002 13:09:18 EST
Subject: Re: [Ieprep] problem context
To: rja@extremenetworks.com, choid@ncr.disa.mil
CC: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_19f.c7a9d1a.2b19074e_boundary"
X-Mailer: AOL 6.0 for Windows XP US sub 51
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


--part1_19f.c7a9d1a.2b19074e_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/29/2002 9:48:06 AM Eastern Standard Time, 
rja@extremenetworks.com writes:


On Wednesday, Nov 27, 2002, at 11:37 America/Montreal, Choi, Don wrote:
> What DoD wants is, simply put, when a mission critical user makes a call,
> the call goes through and stays up. It does not say calls have to be
> pre-empted nor packets should be dropped.

[RJA]    It is very helpful to get the objective outlined and on the table.
Thanks much for that.

[MAP] I believe the above is no different than what we have said multiple 
times in drafts and previous e-mails and meetings.


[RJA]    I had thought MLPP meant "Multi-Level Precedence & Pre-emption",
but that must be a misunderstanding since you seem to say above that
"pre-emption" is not part of the requirement.  Please help me understand
whether pre-emption (e.g. dropping other packets at the IP-layer,
dropping other calls inside a SIP server) is a requirement.

[MAP] Dropping other calls inside a SIP server would be a requirement if 
there were no other way to achieve the general requirement as Don stated it 
above. However, I truely believe that IP gives us better ways to do it than 
the call preemption that is employed in the circuit-switched world. But we 
haven't been able to get to a discussion of how it could do this, since we're 
stuck on an argument of whether any preferential treatment is required at all.


[RJA]    I assume "calls" means "telephony applications running over IP";
if that isn't your meaning, please clarify.

[MAP] We mean "calls" in the same sense as the word has meant for a long 
time, that is, a "telephone call between two end user". At the application 
layer, the meaning of this isn't changed by the use of IP to carry the bits.


 [RJA]   Also, is the scope limited to VoIP applications ?  Or does it 
include all
IP-based applications ?

[MAP]  As I believe has been identified, we need to consider equivalent 
preferential treatments for things other than "calls" (or VoIP application).


[RJA]    Aside:  The big challenge with the objective you have outlined at 
the top is that
"The Internet" is *unaware of* voice calls.  "The Internet" as available from
commercial ISPs [1] deals in IP packets *only*.  Similarly, the current DISN
deployment mostly (no doubt some exceptions exist) deals just in IP packet 
transport
from an access router (e.g. at a base) across the WAN to another access router
(e.g. at a different base).

[MAP] Yes, we're aware that the Internet is unaware of voice calls. That is 
why we have proposed that some form of "packet marking" will be needed to 
achieve the preferential treament goals. Isn't that exactly what AF and EF 
did?


[RJA]    Now there are some methods already outlined on this list, which 
mostly do not use
any IETF standard and do not require any new IETF standards, that can 
generally achieve
the objective you outline at the top.  Here is an example:

    - overprovision the backbone, but do not bother with QoS there (no 
standard needed)
    - enable router-based queuing on access routers (e.g. Sprint's CoS 
service)
        (router-based queuing is not subject to IETF standards; many vendors 
support it)
    - either overprovision the site LAN and/or deploy QoS within the
        single site (e.g. building, base, ship, plane).  (no standard needed)
    - Within a single site, enterprise users often deploy IEEE 802.1p
        precedence inside an Ethernet LAN/MAN (IEEE standard exists; no IETF 
std relevant)
        and DiffServ/IP-ToS (IETF std exists already), combined with 
vendor-specific
        filter rules to apply/remove/modify QoS and QoS markings (router 
filters
        aren't subject to IETF standardisation, except maybe in a MIB spec; 
most
        vendors already support this).

[MAP] As I believe we have made clear, overprovisioning is not an acceptable 
solution for the emergency/disaster situations that we are addressing. Could 
we eliminate that from any further discussion? Of course, router-based 
queuing on access routers is a part of the answer. Yes, within a LAN, there 
are other solutions.

But the bottom line, after all the existing solutions are laid on the table, 
is that none have been able to explain how priority calls get the required 
treatment over regular calls on IP-based networks in a situation of 
congestion using existing standards.


Mike Pierce
Artel


--part1_19f.c7a9d1a.2b19074e_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 11/29/2002 9:48:06 AM Eastern Standard Time, rja@extremenetworks.com writes:
<BR>
<BR>
<BR>On Wednesday, Nov 27, 2002, at 11:37 America/Montreal, Choi, Don wrote:
<BR>&gt; What DoD wants is, simply put, when a mission critical user makes a call,
<BR>&gt; the call goes through and stays up. It does not say calls have to be
<BR>&gt; pre-empted nor packets should be dropped.
<BR>
<BR>[RJA] &nbsp;&nbsp;&nbsp;It is very helpful to get the objective outlined and on the table.
<BR>Thanks much for that.
<BR>
<BR>[MAP] I believe the above is no different than what we have said multiple times in drafts and previous e-mails and meetings.
<BR>
<BR>
<BR>[RJA] &nbsp;&nbsp;&nbsp;I had thought MLPP meant "Multi-Level Precedence &amp; Pre-emption",
<BR>but that must be a misunderstanding since you seem to say above that
<BR>"pre-emption" is not part of the requirement. &nbsp;Please help me understand
<BR>whether pre-emption (e.g. dropping other packets at the IP-layer,
<BR>dropping other calls inside a SIP server) is a requirement.
<BR>
<BR>[MAP] Dropping other calls inside a SIP server would be a requirement if there were no other way to achieve the general requirement as Don stated it above. However, I truely believe that IP gives us better ways to do it than the call preemption that is employed in the circuit-switched world. But we haven't been able to get to a discussion of how it could do this, since we're stuck on an argument of whether any preferential treatment is required at all.
<BR>
<BR>
<BR>[RJA] &nbsp;&nbsp;&nbsp;I assume "calls" means "telephony applications running over IP";
<BR>if that isn't your meaning, please clarify.
<BR>
<BR>[MAP] We mean "calls" in the same sense as the word has meant for a long time, that is, a "telephone call between two end user". At the application layer, the meaning of this isn't changed by the use of IP to carry the bits.
<BR>
<BR>
<BR> [RJA] &nbsp;&nbsp;Also, is the scope limited to VoIP applications ? &nbsp;Or does it include all
<BR>IP-based applications ?
<BR>
<BR>[MAP] &nbsp;As I believe has been identified, we need to consider equivalent preferential treatments for things other than "calls" (or VoIP application).
<BR>
<BR>
<BR>[RJA] &nbsp;&nbsp;&nbsp;Aside: &nbsp;The big challenge with the objective you have outlined at the top is that
<BR>"The Internet" is *unaware of* voice calls. &nbsp;"The Internet" as available from
<BR>commercial ISPs [1] deals in IP packets *only*. &nbsp;Similarly, the current DISN
<BR>deployment mostly (no doubt some exceptions exist) deals just in IP packet transport
<BR>from an access router (e.g. at a base) across the WAN to another access router
<BR>(e.g. at a different base).
<BR>
<BR>[MAP] Yes, we're aware that the Internet is unaware of voice calls. That is why we have proposed that some form of "packet marking" will be needed to achieve the preferential treament goals. Isn't that exactly what AF and EF did?
<BR>
<BR>
<BR>[RJA] &nbsp;&nbsp;&nbsp;Now there are some methods already outlined on this list, which mostly do not use
<BR>any IETF standard and do not require any new IETF standards, that can generally achieve
<BR>the objective you outline at the top. &nbsp;Here is an example:
<BR>
<BR> &nbsp;&nbsp;&nbsp;- overprovision the backbone, but do not bother with QoS there (no standard needed)
<BR> &nbsp;&nbsp;&nbsp;- enable router-based queuing on access routers (e.g. Sprint's CoS service)
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(router-based queuing is not subject to IETF standards; many vendors support it)
<BR> &nbsp;&nbsp;&nbsp;- either overprovision the site LAN and/or deploy QoS within the
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;single site (e.g. building, base, ship, plane). &nbsp;(no standard needed)
<BR> &nbsp;&nbsp;&nbsp;- Within a single site, enterprise users often deploy IEEE 802.1p
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;precedence inside an Ethernet LAN/MAN (IEEE standard exists; no IETF std relevant)
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and DiffServ/IP-ToS (IETF std exists already), combined with vendor-specific
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;filter rules to apply/remove/modify QoS and QoS markings (router filters
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;aren't subject to IETF standardisation, except maybe in a MIB spec; most
<BR> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;vendors already support this).
<BR>
<BR>[MAP] As I believe we have made clear, overprovisioning is not an acceptable solution for the emergency/disaster situations that we are addressing. Could we eliminate that from any further discussion? Of course, router-based queuing on access routers is a part of the answer. Yes, within a LAN, there are other solutions.
<BR>
<BR>But the bottom line, after all the existing solutions are laid on the table, is that none have been able to explain how priority calls get the required treatment over regular calls on IP-based networks in a situation of congestion using existing standards.
<BR>
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_19f.c7a9d1a.2b19074e_boundary--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 15:09:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07021
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 15:09:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATKBwN18610
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 15:11:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATKBvv18607
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 15:11:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07015
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 15:09:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATKAKv18566;
	Fri, 29 Nov 2002 15:10:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATK9Nv18519
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 15:09:23 -0500
Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06950
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 15:06:31 -0500 (EST)
Received: from mail.nps.navy.mil by [140.32.132.66]
          via smtpd (for [132.151.6.1]) with ESMTP; Fri, 29 Nov 2002 12:05:14 -0800
Received: from ro179-23.ro.nps.navy.mil (ro179-23.ro.nps.navy.mil [131.120.179.23])
	by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id gATK60bR012294;
	Fri, 29 Nov 2002 12:06:00 -0800 (PST)
Subject: Re: [Ieprep] "BCP" for emergency app designers
From: Rex Buddenberg <budden@nps.navy.mil>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: "'ieprep@ietf.org'" <ieprep@ietf.org>
In-Reply-To: <3DE51707.4070704@cs.columbia.edu>
References: <3DE51707.4070704@cs.columbia.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1038599081.24117.27.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 29 Nov 2002 12:02:09 -0800
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Wed, 2002-11-27 at 11:03, Henning Schulzrinne wrote:
> Given all the discussion we've had along the way about who can do what, 
> I wonder if one productive output of the WG might be a set of guidelines 
> for designers of emergency communications applications. 

You've gotten to the conclusion that I started with.  Most of the
emergency services plus-ups we need have nothing to do with protocols
(at least ones we don't already have).  They have to do with
provisioning, business practices and network operations.

For organizing your thoughts ... I've been teaching plowshares -->
swords networking for some time now and we've found through observation
that most of the issues fall into four categories consistently.

1.  Higher availability.  There are three principles of high
availability engineering: 
	- eliminate single points of failure.  So provision altroutes and
especially diverse altroutes.  Backup power and such all fall in this
category
	- reliable crossover.  Stateless routers running IP do this, so no
problems
	- detect failures as they occur -- net management.  SNMP already exists
so the issue is business practices.

2.  Security.  Falls into three categories:
	7 - object level security to protect authenticity (critically
important) and confidentiality (close behind).  Non-repudiation and
integrity fall in this bin as well.  (End-to-end and off-line crypto are
synonyms to object level security here).  
	3 - enclave protection.  Firewalls, intrusion detection, password
protection, gate guards -- all deal with perimeter control.  Less
important for emergency services, listed here for completeness.
	1 - link protection.  Link crypto, spread spectrum etc all fall in this
category.  Again, for completeness ... not usually important for EMS,
but important to understand since we keep trying to use these solutions
for the Layer 7 problems above -- bad fit.

3.  QoS control.  I won't fan these flames any further here. Except that
some of the Layer 3 security controls can help (your qos experience will
be better without spam than with).

4.  Reach to mobile platforms.  
	- loosely coupled applications work best because qos isn't as good here
as in wired -- interactivity may be very low (e.g. if there's a satcom
link involved).  (Interactive voice is like telnet -- tightly coupled
and guaranteed to degrade).  I claim that the protocols here are
inadequate -- 802.11 has a lot of bandaids -- but doubt that we want to
suck them into scope of ieprep.  Note that a lot of the real issue here
is provisioning.  
	

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 17:28:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09776
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 17:28:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATMVKf23827
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 17:31:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATMVKv23824
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 17:31:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09770
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 17:28:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATMUBv23794;
	Fri, 29 Nov 2002 17:30:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATMTTv23761
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 17:29:29 -0500
Received: from samsara.kgbinternet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09707
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 17:26:37 -0500 (EST)
Received: (from nobody@localhost)
	by samsara.kgbinternet.com (8.11.6/8.11.6) id gATMTJW18374;
	Fri, 29 Nov 2002 16:29:19 -0600
Date: Fri, 29 Nov 2002 16:29:19 -0600
Message-Id: <200211292229.gATMTJW18374@samsara.kgbinternet.com>
X-Authentication-Warning: samsara.kgbinternet.com: nobody set sender to carl@ietfwatch.net using -f
From: "Carl Ford" <carl@ietfwatch.net>
To: Bill Woodcock <woody@pch.net>, Carl Ford <carl@ietfwatch.net>,
        Mpierce1@aol.com, <rja@extremenetworks.com>, <ieprep@ietf.org>
X-Mailer: Open WebMail 1.52 20011204
X-OriginatingIP: 67.81.93.146 (ietfwatch.carl)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Subject: [Ieprep] Looking for governmental feedback as well
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

Bill Woodcock replied
> On Thu, 28 Nov 2002, Carl Ford wrote:
>     > 1 ISPs should be chosen that are not utilizing the same methodology 
of transport.
>     > 2) Internal Intranets that support multiple connection points to ISPs
> 
> Yes, those are current best-practices, and widely followed.

I am not sure this is accurate for government contracting.  I would love to 
hear from a GSA person.  My sense is that more often than not they may base 
things on geographic issues only.

Kind Regards,

Carl
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 18:01:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10360
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 18:01:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATN4Jt25114
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 18:04:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN4Jv25111
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 18:04:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10337
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 18:01:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN33v24996;
	Fri, 29 Nov 2002 18:03:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN2Nv24959
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 18:02:23 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10284
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 17:59:31 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.89])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id DC7BF7A0A; Fri, 29 Nov 2002 15:02:11 -0800 (PST)
Date: Fri, 29 Nov 2002 17:19:22 -0500
Subject: Re: [Ieprep] Use of ToS bits for "emergency" preferential treatment
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <1c0.226395f.2b165c57@aol.com>
Message-Id: <9C8B30B4-03E8-11D7-9A09-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gATN2Nv24960
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


On Wednesday, Nov 27, 2002, at 12:35 America/Montreal, Mpierce1@aol.com 
wrote:
> [MAP] So, I would still interpret that the DoD requirement is to pass 
> the 8 bits unchanged, no matter what they have been renamed. Is this 
> requirement wrong or impossible to meet?

It is quite realistic as long as it is a DoD owned & DoD operated 
network, since
DoD would control the deployed network configuration.  It is quite 
unrealistic
to expect the IP ToS bits to remain unchanged whilst transiting someone
else's (e.g. a commercial ISP's, some other non-DoD private) network.

> [MAP] According to the official list, STD 3 consists of RFC 1122 and 
> 1123, not  some additional unspecified updates. While 1122 is "updated 
> by" 1349 and 1123 is "updated by" 1349 and 2181, 1349 is in turn 
> obsoleted by 2474 (DiffServ) and 2181 does not address the TOS field. 
> Guess this clearly points out one of the procedural shortcomings in 
> the IETF which allows "out-of-date" and "defunct" standards to 
> continue to exist. Looks like something that should be addressed by 
> someone who cares about procedures.

That's a fair analysis.  IETF is not at all good about keeping things 
current.
Or keeping the set of Full Standard RFCs closely aligned with the 
current technical
reality.

In fact, one of the issues in front of the IETF right now is that our 
processes
are perceived by (some, many) IETF folks as too heavy-weight.  Among 
other things,
this is perceived by (some, many) as making it too hard to get the 
really deployed
specs all the way to Full Standard RFC in a timely manner.

> In a message dated 11/26/2002 10:03:32 PM Eastern Standard Time, 
> rja@extremenetworks.com writes:
>
> Many IP routers/L3 switches can be configured to set/clear/reset the 
> IP ToS
> or DiffServ byte, generally based on ACLs configured by the router 
> administrator.
>
>
> [MAP] And I suppose if they want to comply with the JTA requirement, 
> they would also be capable of being configured to leave these bits 
> alone.

As far as I know, for most commercial switch/router products, leaving 
the IP ToS bits
unmodified is the default configuration.  Certainly it is the default 
for Extreme's
boxes, though we can be configured to do any number of other things if 
the network
operator chooses to deploy some other policy.

Ran
rja@extremenetworks.com


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 18:01:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10373
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 18:01:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATN4Kb25129
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 18:04:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN4Kv25126
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 18:04:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10341
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 18:01:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN35v25028;
	Fri, 29 Nov 2002 18:03:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN2Uv24967
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 18:02:30 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10290
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 17:59:37 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.89])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id BC9CF7A0F; Fri, 29 Nov 2002 15:02:18 -0800 (PST)
Date: Fri, 29 Nov 2002 17:39:13 -0500
Subject: Re: [Ieprep] alternate model for edge QoS
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <3DE51A2E.2060306@cs.columbia.edu>
Message-Id: <62B78A8C-03EB-11D7-9A09-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 27, 2002, at 14:17 America/Montreal, Henning 
Schulzrinne wrote:
> An alternate model might be worth considering: Assume for a moment 
> that we have an NSIS protocol that is suitable for edge QoS control. 
> (I realize that some have well-founded doubts whether this will ever 
> get deployed, but that would be something to discuss with the NSIS 
> working group, I presume.) One of the primary scaling problems with 
> existing resource control approaches is not the protocol itself but 
> rather the AAA backend.

That was not the problem with RSVP deployments and is not the problem 
with RSVP MD5.
The problem with RSVP deployments included at least (1) too much state 
in routers,
(2) paths vary dynamically with normal IP routing which increases 
robustness/resilience
but means that the packets spend a portion of their time travelling 
paths where
no reservations are in place.  The issues with RSVP MD5 centre on the 
computational
expense of computing MD5, the computational expense of key management, 
and the
difficulty of deploying inter-domain scalable dynamic key management.  
Even the DoD
key management systems are single domain -- and they are probably 
better than what
the commercial sector is using.

>  Among other things, when the network is under the weather, having to 
> go and ask some faraway places for authorization is not exactly 
> probability-of-completion-enhancing.

True, but not the main reason why RSVP and NSIS aren't likely to be 
deployable.

> However, fortunately, the problem here is somewhat easier. Authorized 
> emergency personnel could easily have a cert signed by the local 
> authorities that authorizes them to use the resources, similar to the 
> GETS mechanism. The local NSIS entity doesn't have to worry about that 
> Officer Smith gets charged vs. Officer Jones nor may be particularly 
> concerned whether Officer Smith still has an "account", as long as it 
> trusts the issuing authority and certs get issued with some reasonable 
> frequency. Thus, this requires only a single CA entry in the NSIS 
> router, without the usual complexity. One can forego any CRL checking 
> in all likelihood, given that rogue officers can presumably be dealt 
> with in other ways after the fact. Since the volume of emergency calls 
> in any particular place is likely to be low, the additional PK 
> verification delay is not likely to matter much either - it doesn't 
> have to scale to every single phone call or web access. (Rohan and I 
> discussed this roughly in Atlanta; he may not agree with the details 
> above.)

How does the cert get to the router exactly ?
What are the details of your plan here (from the viewpoint of the 
router, please) ?

Validating a signature is computationally *expensive*; validating is 
less expensive
than signing if one is using RSA, but still expensive.

> Using a dynamic filter avoids the DOS problem and should have no 
> complexity impact on the rest of Internet.

Please do explain more.  I don't understand the details of who gives 
whom a CERT
about what, when, and when whom needs to do what with it.

Thanks,

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 18:02:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10386
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 18:02:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATN4LN25144
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 18:04:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN4Lv25141
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 18:04:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10345
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 18:01:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN37v25076;
	Fri, 29 Nov 2002 18:03:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN2dv24979
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 18:02:39 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10299
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 17:59:46 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.89])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id BA1E57A10; Fri, 29 Nov 2002 15:02:28 -0800 (PST)
Date: Fri, 29 Nov 2002 17:52:54 -0500
Subject: Re: Try it, you might like it RE: [Ieprep] any commercial usage f or "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "''ieprep@ietf.org ' '" <ieprep@ietf.org>
To: "Nguyen, An" <nguyena@ncs.gov>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D5B3D98@emshqs1.ncr.disa.mil>
Message-Id: <4C0B7A6E-03ED-11D7-9A09-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 28, 2002, at 09:23 America/Montreal, Nguyen, An wrote:
> You see ... the nature of the NCS mission is to be able to use it in 
> times
> of emergency or network congestion, not during "Normal" time. That is 
> why I
> am interested in how it performs during "Non-normal" time.
>
> Speaking of VoiceIP deployment, you can ask DISA folks in Eagle 
> Building to
> see how happy they are. Ran might have some knowledge of it.

Where "Eagle" == "Skyline", one word:
	Unhappy

More words:
	Initial deployment was widely characterised to me as "unusably bad".
After some tiger team work by the equipment vendor (not Extreme) for 
that
site, the deployment is now viewed as "mostly usable".  But a lot of the
folks over there still say they wish they had a plain old PBX.  The 
quote
I heard most (from N people over there) was:

	The beauty of our VoIP deployment is that when the IP network is down,
	one cannot call the IT folks to open a trouble ticket on the network.

> P.S. Ran, I did not mean to put you on a spot.

No problem.

Now I will note that folks using Bill's VoIP are addressing a different 
problem.

Bill's system is intended to enhance ability of NOC staff to talk with 
other
NOC/vendor staff to keep the IP networks up when the PSTN has already 
failed
and the Internet is still partly/mostly working (e.g. Kobe, Northridge, 
9/11/01
in Lower Manhatten scenarios).

The DISA Skyline deployment was intended to reduce deployment costs of 
a PSTN-like
service in an office building (and in fact connects to the PSTN inside 
the building).
The users expected it to provide PBX-like quality and service -- and 
say that their
current VoIP deployment still does not achieve that level of service in 
normal
circumstances.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 18:02:01 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10399
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 18:02:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATN4MB25159
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 18:04:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN4Mv25156
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 18:04:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10348
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 18:01:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN36v25060;
	Fri, 29 Nov 2002 18:03:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN2Zv24975
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 18:02:35 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10296
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 17:59:43 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.89])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 9CBE27A0E; Fri, 29 Nov 2002 15:02:25 -0800 (PST)
Date: Fri, 29 Nov 2002 17:43:17 -0500
Subject: Re: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: <ieprep@ietf.org>
To: Bill Woodcock <woody@pch.net>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211272225590.16789-100000@paixhost.pch.net>
Message-Id: <F42EA960-03EB-11D7-9A09-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Thursday, Nov 28, 2002, at 01:29 America/Montreal, Bill Woodcock 
wrote:
>       On Thu, 28 Nov 2002, Carl Ford wrote:
>> My first question would be what if access were to be unattainable
>> to the Internet.
>
> That certainly happens, as we've all noticed from time to time.  And 
> when
> it does, no amount of QoS or additional rules or more fragile routers 
> or
> guys with guns are going to move your packets for you.  The only thing
> that's going to help is having your connectivity restored, and the only
> way that'll happen quickly is if you share fate with the largest 
> number of
> other users.  That is, when there's a problem, you _really_ want to be
> _just like everybody else_, since the aggregated bulk of the users are 
> the
> ones who'll be restored first.

DISA/NCS are able to cause their preferred circuits to be restored first
iff they have appropriate contracts in place with the layer-1 operator.
For the PSTN, having such contracts would not be unusual today (and for 
many
years now).

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 18:02:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10415
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 18:02:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATN4Pe25175
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 18:04:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN4Pv25171
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 18:04:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10355
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 18:01:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN36v25044;
	Fri, 29 Nov 2002 18:03:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN2Xv24971
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 18:02:33 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10293
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 17:59:40 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.89])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 27AF67A0A; Fri, 29 Nov 2002 15:02:23 -0800 (PST)
Date: Fri, 29 Nov 2002 17:41:07 -0500
Subject: Re: Try it, you might like it RE: [Ieprep] any commercial usage for "emergency QoS"?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: "'ieprep@ietf.org '" <ieprep@ietf.org>
To: Sean Donelan <sean@donelan.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Pine.GSO.4.44.0211271722430.7997-100000@clifden.donelan.com>
Message-Id: <A6B45A20-03EB-11D7-9A09-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 27, 2002, at 17:27 America/Montreal, Sean Donelan 
wrote:
> On Wed, 27 Nov 2002, Nguyen, An wrote:
>> It would be nice if you could show us that given the traffic 
>> utilization
>> factor of , say, from .1 to 0.5, your voiceIP can still be good or 
>> something
>> to that extent.
>
> I have an idea, why not buy an IP Phone and try it yourself?

The DISA Skyline building is full of cisco IP phones.  I'll check model
numbers the next time I'm over there to compare with Bill, but I'd be
startled if they don't already have a pile of phones interoperable
with Bill's (likely even the same model number).  Last time I was at
Courthouse Road, they still had real phones there, however.

So running the test ought not require money to buy a phone even.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 18:02:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10416
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 18:02:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATN4Pw25189
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 18:04:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN4Pv25178
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 18:04:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10353
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 18:01:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN34v25012;
	Fri, 29 Nov 2002 18:03:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATN2Qv24963
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 18:02:26 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10287
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 17:59:33 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.89])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id A0B357A0E; Fri, 29 Nov 2002 15:02:15 -0800 (PST)
Date: Fri, 29 Nov 2002 17:28:52 -0500
Subject: Re: [Ieprep] Internet faults, VoIP demo, etc
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <175.126e5023.2b165c56@aol.com>
Message-Id: <F0142988-03E9-11D7-9A09-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Wednesday, Nov 27, 2002, at 12:35 America/Montreal, Mpierce1@aol.com 
wrote:
> [MAP] And there's never been an argument that the quality isn't good 
> when the network is not overloaded and there are no major faults 
> anywhere. What some on this discussion have not yet understood, is 
> that we are trying to talk about "preparedness" for a traffic 
> overload/fault condition that has never occurred. It did not occur on 
> Sept 11 or in the "Baltimore Train Tunnel". Whether some like it or 
> not, that is the mission of both NCS and DoD - preparing for what we 
> hope never happens.

The Baltimore Train Tunnel was unquestionably a major fault.  It cut a 
whole
lot of fibres from a whole bunch of different fibre networks.

Similarly, a LOT of fibre was cut in lower Manhatten on 9/11, and in 
Kobe,
and in Northridge during that earthquake.

In each of these cases, the Internet just kept working, routing around 
the
massive fibre damage.  So claiming that "a fault condition has never 
occurred"
is just factually wrong.

Lack of "traffic overload" is not an accident, but the result of good 
network
engineering by professionals at a lot of different organisations.

> Obviously, the results would be very much different if a lot of those 
> other sleeping users were also awake and trying to make voice calls, 
> like if there were a major disaster.

Probably not asleep at 8pm.  Also, email/web/etc are TCP-based 
applications,
so would naturally back off when confronted with a non-responsive UDP 
flow
(e.g. VoIP).

> In addition, I do not consider a call made on a speaker phone and 
> broadcast over a PA system as being a sufficient demonstration of the 
> effect that the round-trip delay would have on a normal conversation.

I'd bet that a demo could be arranged between US east and west coast 
from the
NCS/DISA offices -- main question would be whether an Ethernet port 
outside
the sundry firewalls/NATs could be obtained since VoIP doesn't work 
well through
firewalls/NATs.  If NCS/DISA folks are interested in this, I'd suggest 
dropping
me and Bill and note.

And exactly *what* demonstration parameters would be sufficient in your 
view ?
You've said the Atlanta ones were not, but have not indicated which 
test parameters
are sufficient, making it hard for anyone to meet your spec.

> Another question: Was it stated during the presentation that the 
> packet loss ratio was 40%? Whatever the loss ratio, why are packets 
> lost? Is it because of congestion at some point (and discard because 
> the buffer is full)?

No one has questioned that congestion is a potential issue on access 
links.

Ran
rja@extremenetworks.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 18:10:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10525
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 18:10:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATNDAV25885
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 18:13:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATNDAv25882
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 18:13:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10517
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 18:10:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATNC1v25865;
	Fri, 29 Nov 2002 18:12:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATNBiv25850
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 18:11:44 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10511
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 18:08:51 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.89])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id A35A27A0E; Fri, 29 Nov 2002 15:11:33 -0800 (PST)
Date: Fri, 29 Nov 2002 18:11:33 -0500
Subject: Re: [Ieprep] Accounting
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep@ietf.org
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <8f.25c89d90.2b1906fc@aol.com>
Message-Id: <E706EF3C-03EF-11D7-9A09-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Friday, Nov 29, 2002, at 13:07 America/Montreal, Mpierce1@aol.com 
wrote:
> [RJA] So I remain very confused about what the accounting advocates
> are asking for.  I might be slower than most to puzzle some
> stuff out, but what I got out of the Accounting presentation
> was roughly this:
>
>     - Accounting is a requirement.
>     - We don't mean that packet accounting is a requirement.
>
> [MAP] We start with the requirement that any system that handles 
> IEPREP or
> any kind of priority telephone calls must be capable of performing
> accounting, i.e., maintaining Call Detail Records. Just because packet
> technology is used, doesn't change the current requirement in any way. 
> (And
> it doesn't change what a "call" is from the end user's perspective.)

Do you mean "call detail records" inside SIP only ?
What do you want from the IP routers ?  nothing ?

> [RJA] Which begs the question of precisely which stuff folks think 
> operators
> need to perform accounting on.  Scott Bradner suggested that maybe
> folks meant that there should be some form of accounting within SIP.
> Is that suggestion correct ?
>
> [MAP] At the requirements level in IEPREP, we're trying to stay away 
> from
> specific implementations (like SIP). However, I guess we all know that 
> we're
> talking about SIP. I have to presume that the complete solution to the
> accounting requirements I've detailed would be in SIP. But I can't be 
> certain
> that SIP is sufficient until we have an agreement on what the 
> requirements
> are and then examine SIP.

OK, so you likely mean within "SIP or equivalent telephone call 
management
applications".  Right or wrong ?

> [RJA] I'd really like to understand precisely what folks think is 
> required.
>
> When folks say that "accounting is a requirement" do they really
> mean that " A SIP implementation must be able to perform accounting
> for (some specific list of objects/events)" or mean something else ?
>
> - If the quoted sentence above is close, could folks please be 
> specific and
>     enumerate which specific objects/events need to have accounting 
> support ?
> - If something else, then please be specific and tell us what exactly
>     folks want to perform accounting on ?
>
> [MAP] Any implementation that handles "call" setup must be able to 
> perform
> accounting.

OK.  So in my mind, "call setup" is an application layer function only
when one is using VoIP.  Am I confused about this ?  If so, please 
someone
clarify.

> <snip>
> [RJA] Also, would it be consistent with the Accounting advocates 
> desires to
> say something like this:
>
>     Network operators that do not operate (SIP servers) are not 
> required
>     to perform any accounting in order to support IEprep services.
>
> [MAP] Clearly if the solution is completely in SIP, the above sentence 
> would
> be true. I suspect this is true.

Mike's reply has been very helpful.  There are a couple of things that 
I'd
like folks to read/correct still.  And if anyone has different answers 
than
Mike had, please speak up and help me understand the differences.

Ran

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 18:26:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10810
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 18:26:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATNTA226286
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 18:29:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATNTAv26281
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 18:29:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10799
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 18:26:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATNS3v26260;
	Fri, 29 Nov 2002 18:28:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATNRbv26244
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 18:27:37 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10749
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 18:24:42 -0500 (EST)
Received: from extremenetworks.com (unknown [10.0.8.89])
	by smtp1.extremenetworks.com (Postfix) with ESMTP
	id 478C57A0E; Fri, 29 Nov 2002 15:27:23 -0800 (PST)
Date: Fri, 29 Nov 2002 18:27:23 -0500
Subject: Re: [Ieprep] problem context
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: ieprep <ieprep@ietf.org>
To: Mpierce1@aol.com
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <19f.c7a9d1a.2b19074e@aol.com>
Message-Id: <1D13938C-03F2-11D7-9A09-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.548)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gATNRbv26245
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


On Friday, Nov 29, 2002, at 13:09 America/Montreal, Mpierce1@aol.com 
wrote:
> [MAP] Yes, we're aware that the Internet is unaware of voice calls. 
> That is why we have proposed that some form of "packet marking" will 
> be needed to achieve the preferential treament goals. Isn't that 
> exactly what AF and EF did?

	Neither AF nor EF is widely deployed.  Each has some deployment.  I 
know of
two EF deployments in large WAN networks (a US academic/research 
network and
a European academic/research network).  The AF deployments that I'm 
aware of
are all inside single-domain private networks (e.g. corporate 
LAN/MAN/WAN
situations).  DiffServ appears to not be practical to deploy for 
eng/ops reasons
in an inter-domain situation where at least one domain is a commercial 
ISP.

	DiffServ/802.1p are widely implemented in switches/routers.  
Implementation
quality varies widely today.  Most of the deployments seem to be inside 
a single
administrative domain inside an "enterprise" private network.  Most of 
the issues
identified here and elsewhere relate to inter-domain DiffServ (e.g. 
where ISP A hands
marked packets to ISP B and someone expects ISPs A and B to do 
non-best-effort things
based on the packet markings).  For operational security reasons, ISPs 
often clear the
IP ToS byte in current deployments (which might impair our ability to 
deploy ECN, btw).

	So if DoD wants to use DiffServ *inside* DoD, I think that is 
practical (and
think I've said so in the past).  It is the deployment of inter-domain 
QoS
(of any sort, including DiffServ) that seems intractible right now.  
One of
the IAB documents (RFC-2990 ??) talks about this as well.

> [RJA]    Now there are some methods already outlined on this list, 
> which mostly do not use
> any IETF standard and do not require any new IETF standards, that can 
> generally achieve
> the objective you outline at the top.  Here is an example:
>
>    - overprovision the backbone, but do not bother with QoS there (no 
> standard needed)
>    - enable router-based queuing on access routers (e.g. Sprint's CoS 
> service)
>        (router-based queuing is not subject to IETF standards; many 
> vendors support it)
>    - either overprovision the site LAN and/or deploy QoS within the
>        single site (e.g. building, base, ship, plane).  (no standard 
> needed)
>    - Within a single site, enterprise users often deploy IEEE 802.1p
>        precedence inside an Ethernet LAN/MAN (IEEE standard exists; no 
> IETF std relevant)
>        and DiffServ/IP-ToS (IETF std exists already), combined with 
> vendor-specific
>        filter rules to apply/remove/modify QoS and QoS markings 
> (router filters
>        aren't subject to IETF standardisation, except maybe in a MIB 
> spec; most
>        vendors already support this).
>
> [MAP] As I believe we have made clear, overprovisioning is not an 
> acceptable solution for the emergency/disaster situations that we are 
> addressing. Could we eliminate that from any further discussion?

	We can't eliminate that until the folks who want to eliminate that can
deliver a persuasive argument that it can't work (and explaining why
the past scenarios where it DID work aren't applicable is probably
a part of that).

	So far, I keep hearing NCS/DISA-funded folks say that 
"overprovisioning is not
acceptable" but I haven't heard any technical reasons why that is the 
case.
To my ears, it just sounds like policy rather than engineering.

	(And to be fair, apparently the operators' several claims that 
overprovisioning
has worked fine so far in various emergencies isn't persuading the 
NCS/DISA-funded
folks here either).

> Of course, router-based queuing on access routers is a part of the 
> answer. Yes, within a LAN, there are other solutions.
>
> But the bottom line, after all the existing solutions are laid on the 
> table, is that none have been able to explain how priority calls get 
> the required treatment over regular calls on IP-based networks in a 
> situation of congestion using existing standards.

	And I thought that was NOT Don's stated objective.  His objective was 
that the
preferredcalls were able to get through, which is one that the 
operators here seem
to think can be achieved (through some combination of over-provisioning 
and these other
mechanisms I discussed earlier).  Maybe I mis-read his objective ?

	The DoD tactical nets are a huge pain, due to lack of 
bandwidth/capacity,
but DoD operates all the equipment on those nets and so can deploy 
link-specific
solutions (e.g. router-queuing, link-layer QoS of whatever is 
available, others)
on those networks.  At least some of the services (e.g. Navy) were 
doing so in the
early/mid 90s on at least some of their tactical networks.[1]

Ran
rja@extremenetworks.com

[1] It didn't hurt that they still have a lot of routers with John 
Moy's code,
	including TOS/QoS support that works well.

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Nov 29 22:36:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15245
	for <ieprep-archive@odin.ietf.org>; Fri, 29 Nov 2002 22:36:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAU3cXL03352
	for ieprep-archive@odin.ietf.org; Fri, 29 Nov 2002 22:38:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAU3cXv03349
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 22:38:33 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15228
	for <ieprep-web-archive@ietf.org>; Fri, 29 Nov 2002 22:35:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAU3Y9v02707;
	Fri, 29 Nov 2002 22:34:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAU3XIv02692
	for <ieprep@optimus.ietf.org>; Fri, 29 Nov 2002 22:33:18 -0500
Received: from seahorse.shentel.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14923
	for <ieprep@ietf.org>; Fri, 29 Nov 2002 22:30:24 -0500 (EST)
Received: from steves (ha96s010.d.shentel.net [204.111.96.10])
	by seahorse.shentel.net (8.11.6/8.11.6) with SMTP id gAU3WXM04500;
	Fri, 29 Nov 2002 22:32:33 -0500
From: "Steve Silverman" <steves@shentel.net>
To: "RJ Atkinson" <rja@extremenetworks.com>, "Sean Donelan" <sean@donelan.com>
Cc: <ieprep@ietf.org>
Subject: RE: Try it, you might like it RE: [Ieprep] any commercial usage for "emergency QoS"?
Date: Fri, 29 Nov 2002 22:32:46 -0500
Message-ID: <KMEJKAPHBBCMCDDGMBLOIEAHCBAA.steves@shentel.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <A6B45A20-03EB-11D7-9A09-00039357A82A@extremenetworks.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

While advertised as VoIP, the Skyline building, like most
implementations is actually VoLAN.  The IP is along for the ride.
With a 100Mb Ethernet, the line utilization is rarely as high as
.01.  In addition, voice has priority over data.  You would have a
hard time achieving a 10% loading on such a LAN.  At the WAN
interface, they convert to TDM.

>From what I've heard, very few users are using VoIP on a WAN where
the IP has to contend with moderately loaded (> 30% loaded lines).
I would very much like to hear from anyone with real experience with
VoIP over a typically loaded WAN.

Steve Silverman


> -----Original Message-----
> From: ieprep-admin@ietf.org
> [mailto:ieprep-admin@ietf.org]On Behalf Of
> RJ Atkinson
> Sent: Friday, November 29, 2002 5:41 PM
> To: Sean Donelan
> Cc: 'ieprep@ietf.org '
> Subject: Re: Try it, you might like it RE: [Ieprep] any
> commercial usage
> for "emergency QoS"?
>
>
>
> On Wednesday, Nov 27, 2002, at 17:27 America/Montreal,
> Sean Donelan
> wrote:
> > On Wed, 27 Nov 2002, Nguyen, An wrote:
> >> It would be nice if you could show us that given the traffic
> >> utilization
> >> factor of , say, from .1 to 0.5, your voiceIP can
> still be good or
> >> something
> >> to that extent.
> >
> > I have an idea, why not buy an IP Phone and try it yourself?
>
> The DISA Skyline building is full of cisco IP phones.
> I'll check model
> numbers the next time I'm over there to compare with
> Bill, but I'd be
> startled if they don't already have a pile of phones interoperable
> with Bill's (likely even the same model number).  Last
> time I was at
> Courthouse Road, they still had real phones there, however.
>
> So running the test ought not require money to buy a phone even.
>
> Ran
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>
>


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 30 07:11:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03376
	for <ieprep-archive@odin.ietf.org>; Sat, 30 Nov 2002 07:11:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAUCDZJ02693
	for ieprep-archive@odin.ietf.org; Sat, 30 Nov 2002 07:13:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUCDYv02690
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 30 Nov 2002 07:13:34 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03357
	for <ieprep-web-archive@ietf.org>; Sat, 30 Nov 2002 07:10:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUCCXv02641;
	Sat, 30 Nov 2002 07:12:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUCBYv02599
	for <ieprep@optimus.ietf.org>; Sat, 30 Nov 2002 07:11:34 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03326
	for <ieprep@ietf.org>; Sat, 30 Nov 2002 07:08:46 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAUCBWl8007909
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Sat, 30 Nov 2002 07:11:33 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAUCBVdG009275
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 30 Nov 2002 07:11:32 -0500 (EST)
Message-ID: <3DE8AB52.6060209@cs.columbia.edu>
Date: Sat, 30 Nov 2002 07:13:06 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Steve Silverman <steves@shentel.net>
CC: ieprep@ietf.org
Subject: Re: Try it, you might like it RE: [Ieprep] any commercial usage for
 "emergency QoS"?
References: <KMEJKAPHBBCMCDDGMBLOIEAHCBAA.steves@shentel.net>
In-Reply-To: <KMEJKAPHBBCMCDDGMBLOIEAHCBAA.steves@shentel.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The University of Kentucky uses a VoIP system in many of its buildings, 
including the desk I'm currently sitting at. It's converted to PRI 
on-site. From my experience so far, the quality is at least equivalent 
to a traditional PBX. One should note, however, that the LAN was 
installed maybe three years ago, so it might be in better shape than 
many. (See recent reports on the LAN outages at a Boston-area teaching 
hospital.)

Steve Silverman wrote:

> While advertised as VoIP, the Skyline building, like most
> implementations is actually VoLAN.  The IP is along for the ride.
> With a 100Mb Ethernet, the line utilization is rarely as high as
> .01.  In addition, voice has priority over data.  You would have a
> hard time achieving a 10% loading on such a LAN.  At the WAN
> interface, they convert to TDM.
>
> >From what I've heard, very few users are using VoIP on a WAN where
> the IP has to contend with moderately loaded (> 30% loaded lines).
> I would very much like to hear from anyone with real experience with
> VoIP over a typically loaded WAN.
>
> Steve Silverman
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 30 08:49:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04855
	for <ieprep-archive@odin.ietf.org>; Sat, 30 Nov 2002 08:49:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAUDpul06357
	for ieprep-archive@odin.ietf.org; Sat, 30 Nov 2002 08:51:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUDpuv06354
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 30 Nov 2002 08:51:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04852
	for <ieprep-web-archive@ietf.org>; Sat, 30 Nov 2002 08:49:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUDp5v06342;
	Sat, 30 Nov 2002 08:51:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUDoYv06321
	for <ieprep@optimus.ietf.org>; Sat, 30 Nov 2002 08:50:34 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04831
	for <ieprep@ietf.org>; Sat, 30 Nov 2002 08:47:45 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAUDiLo04779;
	Sat, 30 Nov 2002 05:44:21 -0800 (PST)
Date: Sat, 30 Nov 2002 05:44:21 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Carl Ford <carl@ietfwatch.net>
cc: Mpierce1@aol.com, <rja@extremenetworks.com>, <ieprep@ietf.org>
In-Reply-To: <200211292229.gATMTJW18374@samsara.kgbinternet.com>
Message-ID: <Pine.GSO.4.44.0211300542200.4718-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] Re: Looking for governmental feedback as well
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 29 Nov 2002, Carl Ford wrote:
    > >     > 1 ISPs should be chosen that are not utilizing the same methodology
    > >     > 2) Internal Intranets that support multiple connection points to ISPs
    > > Yes, those are current best-practices, and widely followed.
    > I am not sure this is accurate for government contracting.

Yes, sorry, I shouldn't have made such a generalization.  I guess it would
be more accurate to say that there's a relatively widespread understanding
that these are desirable purchasing criteria, and that they guide the
purchasing decisions of many of the larger and better-informed buyers of
Internet services.  But they're not _majority_ practices, since the
_majority_ of sites aren't multi-homed in the first place, only larger
ones are.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 30 09:19:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05185
	for <ieprep-archive@odin.ietf.org>; Sat, 30 Nov 2002 09:19:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAUELg507365
	for ieprep-archive@odin.ietf.org; Sat, 30 Nov 2002 09:21:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUELgv07362
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 30 Nov 2002 09:21:42 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05179
	for <ieprep-web-archive@ietf.org>; Sat, 30 Nov 2002 09:18:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEK3v07319;
	Sat, 30 Nov 2002 09:20:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEJCv07270
	for <ieprep@optimus.ietf.org>; Sat, 30 Nov 2002 09:19:12 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05111
	for <ieprep@ietf.org>; Sat, 30 Nov 2002 09:16:23 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAUEJ9l8014784
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Sat, 30 Nov 2002 09:19:09 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gAUEIvdG017897
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 30 Nov 2002 09:19:08 -0500 (EST)
Message-ID: <3DE8C92F.3090601@cs.columbia.edu>
Date: Sat, 30 Nov 2002 09:20:31 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] alternate model for edge QoS
References: <62B78A8C-03EB-11D7-9A09-00039357A82A@extremenetworks.com>
In-Reply-To: <62B78A8C-03EB-11D7-9A09-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> That was not the problem with RSVP deployments and is not the problem
> with RSVP MD5.
> The problem with RSVP deployments included at least (1) too much state
> in routers,

This might have been a problem a few years ago, but I'm having a hard 
time believing that a router that can handle on the order of 100,000 
route entries has trouble with, say, a few hundred reservation entries. 
As was pointed out by Fred, there are large MPLS path counts in 
operation today, with no noticeable state problems. (Not counting the 
pain of configuration.)

To be more precise, we have to distinguish three types of states:

(1) scheduling state; this only matters if you have per-flow queueing
(2) filtering/policing state, which polices flows;
(3) reservation state, one for each reservation, but only affecting the 
control processor

 From what I can tell, (3) is not a major issue. Given the hundreds of 
MB on a backbone router and the tens of MB on an edge router and the 
roughly 500 bytes/reservation, you'd need lots of reservations to even 
come close to mattering.

I don't think you need per-flow queueing. For DOS prevention, you'd want 
  filtering, so that only reserved flows get into the "reserved" queue. 
This seems similar to the type of reverse-address filtering and other 
firewall-style filtering that edge routers already do. I don't know if 
any router operates in this mode, but it wouldn't seem difficult to set 
up a series of rule that says "if <match reservation spec i>, set DSCP 
to X" (for i=1 through N) (if none match, set DSCP to 0). Would, say, an 
Extreme box support such filtering rules?

I had earlier cited publications indicating performance achievable on 
commodity computing platforms that are very similar to modern control 
processors. If you have other indications for modern routers, please let 
me know.

>
> (2) paths vary dynamically with normal IP routing which increases
> robustness/resilience
> but means that the packets spend a portion of their time travelling
> paths where
> no reservations are in place.  The issues with RSVP MD5 centre on the
> computational
> expense of computing MD5, the computational expense of key management,
> and the
> difficulty of deploying inter-domain scalable dynamic key management.
> Even the DoD
> key management systems are single domain -- and they are probably better
> than what
> the commercial sector is using.

Web servers routinely handle large volumes of TLS connections. I found 
http://www.isoc.org/isoc/conferences/ndss/02/proceedings/papers/coarfa.pdf 
which measures performance on reasonable hardware. As one number, Apache 
on a 900 MHz PIII seems to do about 250 transactions/second, which seems 
more than enough for most reservation needs and far above what I can 
picture for emergency edge reservation needs. (Even if we assume that 
each reservation lasts only 30 seconds and no state is kept across 
refreshes, this would still be about 6000 reservations that you could 
maintain.)

>
> Please do explain more.  I don't understand the details of who gives
> whom a CERT
> about what, when, and when whom needs to do what with it.

For concreteness, let's assume that FEMA is in charge of this 
hypothetical program. FEMA sends, in some secure fashion, a cert to each 
operator it cares to (based on whatever business relationships it might 
set up). Each operator installs the CA cert in the control processor, 
just like any other CA root cert. Obviously, this happens during 
non-emergency conditions and can be as simple as a signed S/MIME mail. 
There's no need for secrecy, just integrity, since this is a public key 
only. Alternatively, the operator can just download the .p12 file from 
the FEMA web server. There may even be automated ways of doing this; I 
haven't followed all the recent PKI-related WGs. This operation is 
repeated at cert lifetime intervals; these seem to be roughly yearly.

When a signed resource request comes along that claims to be signed by 
the FEMA CA, the control processor verifies this assertion. If this 
checks out, the holder of the cert (presumably, an authorized emergency 
worker) gets her reservation, if not, the attempt fails. No real-time 
interaction with outside entities is required.

(I've simplified this a bit. In reality, you'd want a slightly more 
expressive authorization certificate, but the basic operation is the same.)

This is no different than any of the standard PK setups that are used 
within closed user communities. (As one example I'm familiar with: A 
large European telecom company has issued each employee a smartcard 
ID-badge that has his or her public key on it and uses this for system 
logins and cafeteria meals. I've seen the same on laptops used by 
Microsoft employees.) Unlike a global PK system for random "civilians", 
this is much easier to deploy - the number of certifying entities is 
very small. Similarly, the number of certified users is relatively 
modest and each of them has a close relationship with the certifying entity.

>
>
> Thanks,
>
> Ran


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 30 09:23:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05268
	for <ieprep-archive@odin.ietf.org>; Sat, 30 Nov 2002 09:23:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAUEQEY07554
	for ieprep-archive@odin.ietf.org; Sat, 30 Nov 2002 09:26:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEQDv07551
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 30 Nov 2002 09:26:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05262
	for <ieprep-web-archive@ietf.org>; Sat, 30 Nov 2002 09:23:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEP2v07524;
	Sat, 30 Nov 2002 09:25:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEORv07495
	for <ieprep@optimus.ietf.org>; Sat, 30 Nov 2002 09:24:27 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05247
	for <ieprep@ietf.org>; Sat, 30 Nov 2002 09:21:38 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAUEIJo05000;
	Sat, 30 Nov 2002 06:18:19 -0800 (PST)
Date: Sat, 30 Nov 2002 06:18:19 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: RJ Atkinson <rja@extremenetworks.com>
cc: Mpierce1@aol.com, ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] Internet faults, VoIP demo, etc
In-Reply-To: <F0142988-03E9-11D7-9A09-00039357A82A@extremenetworks.com>
Message-ID: <Pine.GSO.4.44.0211300549060.4718-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

    > Another question: Was it stated during the presentation that the
    > packet loss ratio was 40%?

Four people measured loss between 27% and 30% during that call.  Henning
measured 0%, and then subsequently amended that to, I believe, 7%.  30%
loss is typical on the connection to the phone in Nairobi, sometimes
lower, sometimes higher.

    > Whatever the loss ratio, why are packets lost? Is it because of
    > congestion at some point (and discard because the buffer is full)?

The simple answer is that they're discarded because they weren't paid for.
There are several thousand 128K DSL circuits terminating on a 384K
satellite link there, which means, in ISP-speak, about a thousand-to-one
subscriber ratio, which is one order of magnitude higher than you'd
typically find here in the States, for instance.  If they could afford to
pay ten times more for their service, which they can't, because it's not a
wealthy country, they'd receive service comparable to that which we
recieve here.  To put things in perspective, if you were in Korea, your
service would be as much better than US service as US service is than
Kenyan service.  So there's certainly a lot that can be done if the
government wanted to improve the quality of service, rather than mandate
QoS.

Another way to look at it is that the everyday operating conditions in
Kenya simulate what the Internet would be like here in the U.S. if 90% of
it were offline due to a disaster or something.  Or if ten times as many
people were all trying to use it simultaneously.  Which is one of the many
reasons we're so interested in putting phones in developing countries.


                                -Bill



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 30 09:40:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05613
	for <ieprep-archive@odin.ietf.org>; Sat, 30 Nov 2002 09:40:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAUEh8808430
	for ieprep-archive@odin.ietf.org; Sat, 30 Nov 2002 09:43:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEh8v08427
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 30 Nov 2002 09:43:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05610
	for <ieprep-web-archive@ietf.org>; Sat, 30 Nov 2002 09:40:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEg2v08386;
	Sat, 30 Nov 2002 09:42:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEf2v08354
	for <ieprep@optimus.ietf.org>; Sat, 30 Nov 2002 09:41:02 -0500
Received: from paixhost.pch.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05595
	for <ieprep@ietf.org>; Sat, 30 Nov 2002 09:38:13 -0500 (EST)
Received: from ns1.pch.net (ns1.pch.net [206.220.231.1])
	by paixhost.pch.net (8.11.6/8.11.6) with ESMTP id gAUEYqo05060;
	Sat, 30 Nov 2002 06:34:52 -0800 (PST)
Date: Sat, 30 Nov 2002 06:34:52 -0800 (PST)
From: Bill Woodcock <woody@pch.net>
To: Mpierce1@aol.com
cc: rja@extremenetworks.com, <choid@ncr.disa.mil>, <ieprep@ietf.org>
Subject: Re: [Ieprep] problem context
In-Reply-To: <19f.c7a9d1a.2b19074e@aol.com>
Message-ID: <Pine.GSO.4.44.0211300625160.4718-100000@paixhost.pch.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

      On Fri, 29 Nov 2002 Mpierce1@aol.com wrote:
    > [MAP] Dropping other calls inside a SIP server would be a requirement if
    > there were no other way to achieve the general requirement as Don stated it
    > above. However, I truely believe that IP gives us better ways to do it than
    > the call preemption that is employed in the circuit-switched world. But we
    > haven't been able to get to a discussion of how it could do this, since we're
    > stuck on an argument of whether any preferential treatment is required at all.

I think that many of us are trying to get you to address the question of
why you prefer preferential treatment to maximizing the liklihood of call
completion.  We look at what we think your high-level requirement is, "get
calls through," and then what you're saying "QoS, packet-marking,
call-awareness" and they appear to be diametrically opposed.  We like the
high-level goal, and can't see why you don't want to actually achieve it.

    >> "The Internet" is *unaware of* voice calls.
    > Yes, we're aware that the Internet is unaware of voice calls. That
    > is why we have proposed some form of "packet marking"

One of the things Ran has been trying to explain is that "packet marking"
doesn't make the Internet aware of phone calls.  These are orthoganal.
You can mark packets however you like, and it will not make them be
treated differently.  If it did, that would be a _really bad thing_.  You
_really don't want it to do that_.  The solution to getting calls through
is to buy the service you need, not to redesign the Internet to be
channel-switched.

    > As I believe we have made clear, overprovisioning is not an acceptable
    > solution for the emergency/disaster situations that we are addressing.

No, nobody has made that clear.  In fact, it's the only solution that's
actually worked.  Since it works, and the others don't, what is it that
you don't like about it?

    > But the bottom line, after all the existing solutions are laid on the table,
    > is that none have been able to explain how priority calls get the required
    > treatment over regular calls on IP-based networks in a situation of
    > congestion using existing standards.

Since nobody has demonstrated a need for that, no, nobody's engineered
that particular combination.  Since that combination appears to be
incongruous with your stated high-level goal, I think everyone who matters
is waiting for your (collective your) public statements to all come into
line before taking any action.

                                -Bill


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 30 09:49:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05872
	for <ieprep-archive@odin.ietf.org>; Sat, 30 Nov 2002 09:49:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAUEqG008581
	for ieprep-archive@odin.ietf.org; Sat, 30 Nov 2002 09:52:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEqGv08578
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 30 Nov 2002 09:52:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05842
	for <ieprep-web-archive@ietf.org>; Sat, 30 Nov 2002 09:49:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEk2v08496;
	Sat, 30 Nov 2002 09:46:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUEk0v08482
	for <ieprep@optimus.ietf.org>; Sat, 30 Nov 2002 09:46:00 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA05698
	for <ieprep@ietf.org>; Sat, 30 Nov 2002 09:43:10 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.10333-0@bells.cs.ucl.ac.uk>; Sat, 30 Nov 2002 14:45:40 +0000
To: Mpierce1@aol.com
Cc: ieprep@ietf.org
Subject: Re: [Ieprep] Accounting
Date: Sat, 30 Nov 2002 14:45:38 +0000
Message-ID: <21739.1038667538@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>


> [MAP] We start with the requirement that any system that handles IEPREP
> or any kind of priority telephone calls must be capable of performing
> accounting, i.e., maintaining Call Detail Records. 

why?  I don't mean to be dense, but I'm curious if your response is
rooted in reasons that relate to supporting a business model you have
in mind.

part of the reason I have not been convinced about accounting as a
requirement is that my exposure to it has never been one in which it
operates in real-time as a means of affecting the flow that transits a
network.  labeling and subsequent authentication/policing of flows
represent mechanisms that operates at real time.  accounting is an
after-the-fact third mechanism that may or may not be used.

customers that would pay for a service like GETS, or one based on MLPP, 
would certainly want accounting and so I'm not saying there isn't a need
for it.  but since IEPREP is broader in scope than these two systems,
we can't tie in a third mechanism that in certain cases plays no role.
for example, the land-line based system of GTPS (in the UK) has no
need for accounting. 


the problem I have with the above statement "must be capable of
performing accounting" is that it implies that a mechanism must exist
for accounting -- whether one uses it or not for *any and all* IEPREP
type services.  I've mentioned in the past that if there was a specific
set of requirements for a specific service (e.g., IP-based Autovon),
then that is where one would place the requirement for accounting.

one thing I can probably do in the draft-carlberg-ets-telephony-00.txt
draft is take a rough inverse of your statement and state that
the ability to perform accounting must not be precluded.

-ken




_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 30 15:57:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12089
	for <ieprep-archive@odin.ietf.org>; Sat, 30 Nov 2002 15:57:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAUL00o22324
	for ieprep-archive@odin.ietf.org; Sat, 30 Nov 2002 16:00:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUL00v22309
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 30 Nov 2002 16:00:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12044
	for <ieprep-web-archive@ietf.org>; Sat, 30 Nov 2002 15:57:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUKx2v22243;
	Sat, 30 Nov 2002 15:59:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUKvZv22163
	for <ieprep@optimus.ietf.org>; Sat, 30 Nov 2002 15:57:35 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12017
	for <ieprep@ietf.org>; Sat, 30 Nov 2002 15:54:42 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Sat, 30 Nov 2002 15:57:00 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2002113015571506697
 ; Sat, 30 Nov 2002 15:57:15 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <XNSVFKZ1>; Sat, 30 Nov 2002 15:58:44 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E779C5@mcl-its-exs01.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] a practical VoIP issue
Date: Sat, 30 Nov 2002 15:57:06 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

>Apparently VoIP systems use a wide range of dynamically 
> assigned
> UDP ports, which most firewalls block and which most NATs cannot cope
> with properly.
> 
> 	If one really wants to be able to use Internet 
> infrastructure during
> an emergency, designing a VoIP system that can do 
> NAT/Firewall traversal
> might be a pretty important component.

There exist SIP aware firewalls that can cope with NAT and dynamically
assigned UDP ports.  Are you suggesting something different? 

Kimberly
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Sat Nov 30 16:01:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12167
	for <ieprep-archive@odin.ietf.org>; Sat, 30 Nov 2002 16:01:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAUL42X22410
	for ieprep-archive@odin.ietf.org; Sat, 30 Nov 2002 16:04:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUL42v22407
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 30 Nov 2002 16:04:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12164
	for <ieprep-web-archive@ietf.org>; Sat, 30 Nov 2002 16:01:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUKw4v22191;
	Sat, 30 Nov 2002 15:58:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUKidv21945
	for <ieprep@optimus.ietf.org>; Sat, 30 Nov 2002 15:44:39 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11826
	for <ieprep@ietf.org>; Sat, 30 Nov 2002 15:41:46 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Sat, 30 Nov 2002 15:44:10 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2002113015442617937
 ; Sat, 30 Nov 2002 15:44:26 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <XNT4A122>; Sat, 30 Nov 2002 15:44:13 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E779C4@mcl-its-exs01.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'RJ Atkinson'" <rja@extremenetworks.com>, Mpierce1@aol.com
Cc: ieprep@ietf.org
Subject: RE: [Ieprep] Re: ToS bits in STD-3
Date: Sat, 30 Nov 2002 15:44:23 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>

> On Tuesday, Nov 26, 2002, at 20:04 America/Montreal, Mpierce1@aol.com 
> wrote:
> > Perhaps you could comment on the applicability/correctness of the 
> > following requirement out of the DoD Joint Technical Architecture 
> > document:
> >
> > "In addition, all implementations of IP must pass the 8-bit 
> > Type-of-Service
> > (TOS) byte transparently up and down through the transport layer
> > as defined in IETF Standard 3, Host Requirements."
 

This thread is an example of people talking about different things.  We
began with a discussion about what happens to "DiffServ" marked packets when
they traverse an ISP boundary.  The above was then offered about what a host
should do when it gets/sends a "DiffServ" marked packet. These are different
things. 

Here is an example of the first ... ISP A labels some packets blue, perhaps
it does this for local reasons (e.g., preferential treatment for internal
routing).  Now, ISP B gets some traffic from ISP A.  ISP B has a decision to
make...it can keep blue ones blue or it can relabel them a default color.  

If ISP B gives some special treatment to blue packets and it doesn't choose
to relabel those coming from ISP A then it has just created a vulnerability
for itself. It now has to trust ISP A will not overwhelm it or break ISP B's
handling of blue packets.  Unfortunately, it's also a hard problem to figure
out how to charge ISP A for blue packets over regular ones sent to ISP B
(note this is very different than the Telco model and there are some
fundamental problems in this area).  Hence, without remarking, ISP B would
open itself up to vulnerability without any financial incentives for it.
Therefore, many ISPs choose to remark (this includes the largest ISPs).  

Here is an example of the host topic ... Joe's machine receives some blue
packets for some application it is running.  The application should be
informed this stuff came in as blue.  In addition, the application might
want to send information that packets associated with this application to be
sent over the network should also be colored blue.  

I hope this is more clear now.

Kimberly

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



