IPTComm Announcements | 8 Jan 19:35 2007

IPTComm 2007 Second Call for Papers

Please find enclosed the Second Call for Papers for a new conference devoted to IP telecommunications to be
held in New York, July 2007. You are encouraged to circulate this CFP to interested colleagues, mailing
lists, forums and blogs.

Submission deadline: February 28, 2007

Greg Bond
IPTComm 2007 Co-Chair



IPTComm 2007

19, 20 July 2007
Columbia University


SUBMISSION DEADLINE: February 28, 2007

While standards and products now support PSTN-equivalent services for voice, video and text over IP,
there are significant difficulties in deploying large-scale, reliable and secure IP
telecommunication systems. Services that go beyond basic call features remain hard to develop and deploy.

The aim of the IPTComm conference is to serve as a platform for researchers from academia and research labs,
(Continue reading)

Spencer Dawkins | 8 Aug 18:42 2005

Closing PILC Mailing List?

Dear Former PILCers,

When the PILC working group concluded, Aaron and I agreed to keep the 
mailing list open for ongoing discussions, but we haven't been having 
much in the way of ongoing discussions.

I would like to close the mailing list - any objections? If so, please 
let me know in the next couple of weeks.



pilc mailing list
pilc <at> ietf.org

Carlos Becker Westphall | 21 Jul 22:20 2005

CFP - NOMS 2006 - 10th IEEE/IFIP Network Operations and Management Symposium (NOMS 2006)

We apologize if you receive multiple copies of this CFP.

                 10th IEEE/IFIP
Network Operations and Management Symposium (NOMS 2006)


                 Call for Papers

           "Management of Integrated
     End-to-end Communications and Services"

The 10th IEEE/IFIP Network Operations and Management
Symposium (NOMS 2006) will be held 3-7 April 2006 in
the Vancouver Convention and Exhibition Center, Vancouver,
Canada. Held in even-numbered years since 1988, NOMS 2006
will follow the 18 year tradition of NOMS and IM as the
primary forum for technical exchange of the research,
standards, development, systems integration, service
provider, and user communities. NOMS 2006 will present
up-to-date approaches and technical solutions for
integrated systems and services including communication
networks, host systems, enterprise applications, service
oriented architectures, and delivery of management services.
The conference provides a peer-reviewed program of technical
sessions, application sessions, tutorials, posters,
application sessions, and panels as well as vendor exhibits.

Integrated systems and services require considerations for
today's multi-service and multi-domain environment of
(Continue reading)

Falk | 13 Jul 12:17 2005



Panda GateDefender has detected malicious content (Virus) in the following file: [Garry.cpl]

The file has been deleted to protect the network.
07/13/2005 09:12 +0100




pilc mailing list
pilc <at> ietf.org
Aaron Falk | 19 Jan 19:46 2005

Liaison Statement to ITU-R from the IETF Transport Directorate on TCP over Satellite Collaboration

This is a heads-up since folks on the PILC list may be interested.
There may be some discussion on the TCPSAT mail list related to the
note below.  Coordinates to subscribe to TCPSAT and a pointer to the
the letter from ITU-R to the IETF appear at the bottom of the


----- Forwarded message from Aaron Falk <falk <at> ISI.EDU> -----

From: Aaron Falk <falk <at> ISI.EDU>
To: Valery Timofeev <valery.timofeev <at> itu.int>, Jinxing Li <jinxing.li <at> itu.int>
Cc: Mark Allman <mallman <at> icir.org>, Scott Bradner <sob <at> harvard.edu>,
   Allison Mankin <mankin <at> psg.com>,
   Transport Directorate List <tsv <at> newdev.harvard.edu>
Date: Thu, 13 Jan 2005 17:38:06 -0800
Subject: Liaison Statement to ITU-R from the IETF Transport Directorate on TCP over Satellite Collaboration
User-Agent: Mutt/
Organization: USC ISI

Dear Director Timofeev,

We were very interested to read your letter of 13 October 2004 [1]
informing the IETF of a new Study Group 4 Recommendation on
"Performance enhancements of TCP over satellite networks."  Beyond the
issue of whether the Recommendation may include RFC abstracts (we
believe Scott Bradner has already addressed this), we would like to
offer some technical feedback on IETF technologies and activities
which might be of interest to SG4.

(Continue reading)

Gorry Fairhurst | 17 Jan 20:30 2005

Re: I-D ACTION:draft-iab-link-indications-01.txt

Bernard Aboba wrote:

>> I like the idea behind this document, were you planning to develop it
>> further?
> It is an IAB document, so yes, we are planning on continuing to develop it.
>> Although many issues seem to have been explored for the network layer, 
>> the
>> Transport layer considerations seem much less developed. I think it 
>> could be
>> better to have more on the implications of providing this information 
>> to the
>> transport-layer within a general Internet context.
> Yes, I think that is fair.  Recommendations welcome.
>> When I was reading it, I was trying to understand whether the prime
>> motivation was to handle end hosts that were directly connected to the 
>> link
>> reporting its state, or whether the document was also addressing the case
>> with other L2 or L3 elements (routers, bridges) between the link and 
>> the end
>> host.
> The unifying concept for both direct connection and distant links is 
(Continue reading)

Aaron Falk | 12 Jan 02:16 2005

I-D ACTION:draft-iab-link-indications-01.txt

Of possible interest to this list.


----- Forwarded message from Internet-Drafts <at> ietf.org -----

A New Internet-Draft is available from the on-line Internet-Drafts
directories.  This draft is a work item of the Internet Architecture
Board Working Group of the IETF.

	Title		: Architectural Implications of Link Indications
	Author(s)	: B. Aboba
	Filename	: draft-iab-link-indications-01.txt
	Pages		: 33
	Date		: 2005-1-11
   This document provides an overview of the role of link indications
   within the Internet Architecture.  While the judicious use of link
   indications can provide performance benefits, experience has also
   shown that that inapropriate use can degrade both robustness and
   performance.  This document summarizes current proposals, describes
   the architectural issues and provides examples of appropriate and
   inappropriate uses of link layer indications.

A URL for this Internet-Draft is:

----- End forwarded message -----

(Continue reading)

Allison, Art | 12 Oct 17:45 2004

Call For Proposals NAB 2005

NAB2005 will host the 59th NAB Broadcast Engineering Conference on April
16-21 at the Las Vegas Convention Center in Las Vegas, Nevada.  The
conference addresses the most recent developments in broadcast technology
and focuses on the opportunities and challenges that face broadcast
engineering professionals around the world.

Each year hundreds of broadcast professionals from around the world attend
the conference.  They include practicing broadcast engineers and
technicians, engineering consultants, contract engineers, broadcast
equipment manufacturers, distributors, R&D engineers plus anyone
specifically interested in the latest broadcast technologies.

The NAB Broadcast Engineering Conference is a highly technical conference
where presenters deliver technical papers ranging over a variety of topics
relevant to the broadcast and allied industries.  Presentations are limited
to thirty minutes in length, including five or ten minutes for questions
from the audience.  The conference rooms are equipped with audio visual
equipment that will accommodate standard computer presentations.  Presenters
must bring their own computers.

We invite you to submit a proposal to present a technical paper at our
conference by accessing http://www.nabshow.com/forms/beccallforpapers.asp.
Proposals should be clearly written and be no more than 200 words in length.
Your proposal should explain precisely what conference attendees can be
expected to learn from your paper.  Papers promoting company products or
services will not be accepted.  However, papers explaining the underlying
technologies used in broadcast products or services will be acceptable.

The deadline for submitting your proposal is October 15, 2004.  The
(Continue reading)

Sara Alouf | 7 Oct 17:46 2004

CFP Performance 2005

  ** Apologies for multiple copies of this message **

                   CALL FOR PAPERS

                   PERFORMANCE 2005

The 24th IFIP WG 7.3 International Symposium on Computer 
Performance Modeling, Measurement and Evaluation

                   October 3-7, 2005
                 Juan-les-Pins, France

Sponsored by IFIP WG 7.3, the Computer Performance Foundation 

The PERFORMANCE 2005 conference solicits papers on the 
development and application of state-of-the-art analytic, 
simulation, and measurement-based performance evaluation 
techniques. Topics of interest include, but are not 
limited to:

* Performance-oriented design and evaluation of:
  communication networks, mobile and wireless systems,
  Internet servers and E-commerce systems, Web services,
  Web architectures, peer-to-peer systems, grid computing,
  computer architectures, database systems, operating
(Continue reading)

Lakshmi Priya | 3 Aug 07:46 2004

RE: interoperability issue with TCP PEP

   Thanks, Eric.

Guess I was not very clear with my question.
Consider the scenario below:

H1-P1 -> terrestial link
P1--P2 -> satellite link
H2-P2 -> terrestial link

End host	PEP node	PEP node	End host

H1 ----------P1------------P2----------H2

In a split PEP connection there would be 3 TCP connections (between the
If PEP is transparent to end user the session properties (atleast the 4
tuples H1,H2,srcport1,dstport1)
should be the same for the TCP sessions between H1-P1 and P2-H2.Both these
sessions would ideally be spoofed with session tuples -
H1,H2,srcport1,dstport1 as expected by end users H1 and H2. This can be done
in many ways, since there is no specification. The information of the
session just needs to be passed from P1 to P2.

Eric, as per your reply
>> It seems that an ideally constructed transport proxy would leave all the
relevant information (obviously port numbers, but also bidirectional
space, urgent pointers, I suppose the Push flag and any IP header service
markings) undisturbed.
(Continue reading)

rfc-editor | 13 Jul 22:45 2004

BCP 89, RFC 3819 on Advice for Internet Subnetwork Designers

A new Request for Comments is now available in online RFC libraries.

        BCP 89
        RFC 3819

        Title:      Advice for Internet Subnetwork Designers
        Author(s):  P. Karn, Ed., C. Bormann, G. Fairhurst,
                    D. Grossman, R. Ludwig, J. Mahdavi, G. Montenegro,
                    J. Touch, L. Wood
        Status:     Best Current Practice
        Date:       July 2004
        Mailbox:    karn <at> qualcomm.com, cabo <at> tzi.org,
                    gorry <at> erg.abdn.ac.uk, Dan.Grossman <at> motorola.com,
                    Reiner.Ludwig <at> ericsson.com,
                    jmahdavi <at> earthlink.net, gab <at> sun.com,
                    touch <at> isi.edu, lwood <at> cisco.com
        Pages:      60
        Characters: 152174
        SeeAlso:    BCP 89

        I-D Tag:    draft-ietf-pilc-link-design-15.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3819.txt

This document provides advice to the designers of digital
communication equipment, link-layer protocols, and packet-switched
local networks (collectively referred to as subnetworks), who wish to
support the Internet protocols but may be unfamiliar with the
Internet architecture and the implications of their design choices on
(Continue reading)