Internet-Drafts | 9 Sep 2003 15:50
Picon
Favicon

I-D ACTION:draft-ietf-ieprep-ets-telephony-06.txt

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		: IP Telephony Requirements for Emergency 
                          Telecommunication Service
	Author(s)	: K. Carlberg, R. Atkinson
	Filename	: draft-ietf-ieprep-ets-telephony-06.txt
	Pages		: 6
	Date		: 2003-9-9
	
This document presents a list of requirements in support of Emergency
Telecommunications Service (ETS) within the context of IP telephony.
It is an extension to the general requirements presented in [3].
Solutions to these requirements are not presented in this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ieprep-ets-telephony-06.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-ets-telephony-06.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

(Continue reading)

Ken Carlberg | 9 Sep 2003 15:59
Picon

RE: I-D ACTION:draft-ietf-ieprep-ets-telephony-06.txt

FYI.  The latest version of the telephony requirements draft reflects
minor changes requested by the AD in order for it to be advanced for
review by the IESG.  Item 5 of section 3 (Requirements) was revised, and
new text in the form of item 2 was added to section 4 (Issues).

I forgot to mention that the previous announcement on the General
Requirements draft reflected minor changes requested by the IESG.

-ken

> -----Original Message-----
> From: ieprep-admin <at> ietf.org [mailto:ieprep-admin <at> ietf.org] On Behalf
Of
> Internet-Drafts <at> ietf.org
> Sent: Tuesday, September 09, 2003 9:51 AM
> To: IETF-Announce:
> Cc: ieprep <at> ietf.org
> Subject: [Ieprep] I-D ACTION:draft-ietf-ieprep-ets-telephony-06.txt
> 
> 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		: IP Telephony Requirements for Emergency
>                           Telecommunication Service
> 	Author(s)	: K. Carlberg, R. Atkinson
> 	Filename	: draft-ietf-ieprep-ets-telephony-06.txt
> 	Pages		: 6
(Continue reading)

Sean Donelan | 30 Sep 2003 04:30
Favicon

The world's biggest data consumers don't think priority is such a big priority


"Priority" is a buzzword networking executives use to describe assigning
levels of importance to network traffic. The practice is intended to
ensure that a company's most important data gets through a crowded
connection.

But it's a different story for the health care industry and government
agencies, whose notoriously large data appetites have created a market for
connections 10 times the size of a typical data pipe. Since these
customers haven't yet come close to stressing their connection's capacity,
they have no need for expensive and hard-to-manage priority systems, AT&T
Ethernet Services Director Franco Callocchia said.

http://news.com.com/2100-1035_3-5083779.html
James M. Polk | 30 Sep 2003 19:31
Picon
Favicon

Re: The world's biggest data consumers don't think priority is such a big priority

Just because someone with a lofty title said it - it doesn't make what he 
said right

The US Gov and others already employ priority networks; those that don't, 
haven't moved their time critical applications over to their Ethernet 
networks (yet)

At 10:30 PM 9/29/2003 -0400, Sean Donelan wrote:

>"Priority" is a buzzword networking executives use to describe assigning
>levels of importance to network traffic. The practice is intended to
>ensure that a company's most important data gets through a crowded
>connection.
>
>But it's a different story for the health care industry and government
>agencies, whose notoriously large data appetites have created a market for
>connections 10 times the size of a typical data pipe. Since these
>customers haven't yet come close to stressing their connection's capacity,
>they have no need for expensive and hard-to-manage priority systems, AT&T
>Ethernet Services Director Franco Callocchia said.
>
>http://news.com.com/2100-1035_3-5083779.html
>
>
>_______________________________________________
>Ieprep mailing list
>Ieprep <at> ietf.org
>https://www1.ietf.org/mailman/listinfo/ieprep

cheers,
(Continue reading)

King, Kimberly S. | 30 Sep 2003 21:53
Picon
Favicon

working group of potential interest

Description of Working Group:

Lemonade is tasked to provide a set of enhancements and profiles of 
Internet email submission, transport, and retrieval protocols to 
facilitate operation on platforms with constrained resources, or 
communications links with high latency or limited bandwidth. 

http://www.ietf.org/html.charters/lemonade-charter.html
RJ Atkinson | 30 Sep 2003 23:13
Favicon

Re: The world's biggest data consumers don't think priority is such a big priority


On Tuesday, Sep 30, 2003, at 13:31 America/Montreal, James M. Polk 
wrote:
> Just because someone with a lofty title said it - it doesn't make what 
> he said right

The term "right" is highly subjective.  Reasonable people could have
different values for "right" in any number of circumstances.  The quote
that Sean supplied is quite useful, IMHO, because it explains what the
commercial marketplace (in the form of at least one major service 
provider)
believes is needed and practical.  If you find published quotes from
other service providers with different views, you are certainly free
to post them for perusal, but jumping on Sean that way is excessive.

> The US Gov and others already employ priority networks; those that 
> don't, haven't moved their time critical applications over to their 
> Ethernet networks (yet)

Your claim is far too bold, hence untrue.

All of our time-critical applications run over Ethernet (using our own
equipment).  I seriously doubt that you are as omniscient as your
claim would require.  Some organisations do run time-critical apps
over Ethernet.  No doubt, there are some organisations that do not.

And the US DoD, in the form of the currently deployed DISN, does NOT
use priority in its IP networks (specifically NIPRnet, SIPRnet),
according to the folks that operate those networks.  Those folks
further say that the US DoD JCS has *prohibited* deployment of
(Continue reading)

RJ Atkinson | 30 Sep 2003 23:24
Favicon

Re: The world's biggest data consumers don't think priority is such a big priority


On Tuesday, Sep 30, 2003, at 17:13 America/Montreal, RJ Atkinson wrote:
> All of our time-critical applications run over Ethernet (using our own
> equipment).  I seriously doubt that you are as omniscient as your
> claim would require.  Some organisations do run time-critical apps
> over Ethernet.  No doubt, there are some organisations that do not.

Just to be clear:

	Some folks regularly do run time-critical apps over Ethernet,
*without enabling any sort of prioritisation*.

	A well-engineered switched Ethernet infrastructure can provide
tremendous predictability and excellent operational characteristics
without enabling any form of prioritisation.  This is particularly
true for modern Ethernet, where switching is most commonly deployed,
the low cost of high-speed Ethernet kit makes it economical to
over-provision capacity, and a variety of ring technologies exist
for resilience.

Yours,

Ran
James M. Polk | 1 Oct 2003 01:46
Picon
Favicon

Re: The world's biggest data consumers don't think priority is such a big priority

Ran

Needless to say, I completely disagree with your position and don't rely on 
quotes from people I don't know (like you do apparently) to get my 
information. I like first hand knowledge.

I feel that any further reaction would not be in this list's best interest 
(a rat hole) - but am available to talk during, before, or after our 
meeting in Minneapolis at whatever length you wish about this

BTW - I was at no time getting on Sean for what he sent to the list - I was 
merely reacting to the quoted person's claim that prioritization in IP was 
not necessary. I actually appreciate reading that someone said this 
(therefore - Thank you Sean for sending this to the list!)

At 05:13 PM 9/30/2003 -0400, RJ Atkinson wrote:

>On Tuesday, Sep 30, 2003, at 13:31 America/Montreal, James M. Polk wrote:
>>Just because someone with a lofty title said it - it doesn't make what he 
>>said right
>
>The term "right" is highly subjective.  Reasonable people could have
>different values for "right" in any number of circumstances.  The quote
>that Sean supplied is quite useful, IMHO, because it explains what the
>commercial marketplace (in the form of at least one major service provider)
>believes is needed and practical.  If you find published quotes from
>other service providers with different views, you are certainly free
>to post them for perusal, but jumping on Sean that way is excessive.
>
>>The US Gov and others already employ priority networks; those that don't, 
(Continue reading)

Mpierce1 | 1 Oct 2003 05:55
Picon
Favicon

Re: The world's biggest data consumers don't think priority is such ...

In a message dated 9/30/2003 5:15:46 PM Eastern Standard Time, rja <at> extremenetworks.com writes:


Those folks
further say that the US DoD JCS has *prohibited* deployment of
prioritisation in DoD IP networks (unless a JCS waiver is obtained;
DISA network ops folks tell me they do not have such a waiver).


The words in the above statemet seem to have been jumbled. To correct the word order: The JCS has prohibited further deployment of IP networks (for mission critical communications) until the necessary prioritization is possible. They do not have such a waiver.

I don't think that the "ops folks" are the ones to be telling you what the requirements are for the future. I think they tend to think and concern themselves with what is currently in use. You need to talk to the standards people and those planning the future networks.

Mike Pierce
RJ Atkinson | 1 Oct 2003 15:58
Favicon

Re: The world's biggest data consumers don't think priority is such a big priority


On Tuesday, Sep 30, 2003, at 19:46 America/Montreal, James M. Polk 
wrote:
> Needless to say, I completely disagree with your position and don't 
> rely on quotes from people I don't know (like you do apparently) to 
> get my information. I like first hand knowledge.

James,

	You claimed that no one was using Ethernet for critical services
without prioritisation (exact quote follows):

> The US Gov and others already employ priority networks; those that 
> don't,
> haven't moved their time critical applications over to their Ethernet
> networks (yet)

	I have first-hand knowledge of several sites that do use Ethernet
for time-critical applications and do not employ prioritisation.
I work at such a site.  I know of other such sites in various places
around the world.  I'll take any data I can get.  Different data
gets different weight in my analysis, depending on an assessment
of its quality.

	Moreover, unless one is omniscient, which no one on this list
is, one could not know whether 'all of those that don't use priority
networks' do (or don't do) *anything*.  There are far too many networks
in the world for anyone to know all the pertinent details about all
of them.  Yet you claim to have just such knowledge.

	Your claim was too extreme.  Had you said "many" or "some" or
"few" rather than "those that don't", it might have been a lot more
plausible statement.  However, you didn't do so and did not clarify
your meaning when questioned about it yesterday.  Pity that.

> I was merely reacting to the quoted person's claim that prioritization
> in IP was not necessary.

Nonsense.  There was no comment about "prioritisation in IP" in
that article.  You badly misread the article at the URL provided.

(For any who tuned in late, the URL is:
	http://news.com.com/2100-1035_3-5083779.html )

1)  The article at that URL does NOT anyplace contain the phrase "IP"
	or the phrase "Internet Protocol".
2)  The article more than once states that AT&T is discussing an
	"Ethernet service".
3)  Ethernet is not IP, and is in fact at a lower layer in a
     a conventional protocol architecture.

Now, as it happens, IEEE 802.1p (now packaged in a revised 802.1d)
specifies Ethernet precedence.  In some ways, that IEEE mechanism is
similar to the IP precedence mechanism.  I know of a number of sites
that use 802.1p and also a number of sites that don't use 802.1p.

Now, since a private email has erroneously suggested that my employer
would benefit from users not deploying QoS, I'll clarify that point.
My employer quite possibly has the *best* implementation of IP ToS,
DiffServ, and 802.1p available.  Some of our customers enable some
of those features, some do not.  It would be advantageous for my
employer if more folks enabled those features, because it would provide
additional crisp differentiation from many of our competitors.
However, on an IETF list, I express my own views about the standards
topics under discussion, rather than advocating standards positions
because they might advantage my employer.  This might be confusing
to some.  It does not confuse those who've watched me in the IETF
context over the years.

In any event, the issues with IP prioritisation on this IETF list have 
been
focused on the inter-domain context, where deployment of inter-domain
DiffServ (or similar) mechanism creates a significant (Distributed)
Denial of Service attack vector not present otherwise.  If anyone
has a technical approach that enables deployment of DiffServ in an
inter-domain context without creating a (D)DOS attack vector,
I'm sure it would be of general interest to this list (it probably
deserves a new Subject: line, however :-).

Yours,

Ran Atkinson
rja <at> extremenetworks.com

Gmane