Re: [PWOT] draft-anavi-tdmoip-01.txt

"Andrew G. Malis" <Andy.Malis@vivacenetworks.com> Tue, 06 March 2001 05:37 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19138 for <pwot-archive@odin.ietf.org>; Tue, 6 Mar 2001 00:37:01 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA15838; Tue, 6 Mar 2001 00:25:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA15804 for <pwot@ns.ietf.org>; Tue, 6 Mar 2001 00:25:56 -0500 (EST)
Received: from avocet.prod.itd.earthlink.net (avocet.prod.itd.earthlink.net [207.217.121.50]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19024 for <pwot@ietf.org>; Tue, 6 Mar 2001 00:25:55 -0500 (EST)
Received: from AMALIS.earthlink.net (sdn-ar-002lanorlP047.dialsprint.net [63.178.73.159]) by avocet.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id VAA02360; Mon, 5 Mar 2001 21:25:50 -0800 (PST)
Message-Id: <5.0.2.1.2.20010306000013.03abc1f8@viva.vivacenet.com>
X-Sender: andymalis@mail.earthlink.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 06 Mar 2001 00:25:46 -0500
To: Motty Anavi <motty@radusa.com>
From: "Andrew G. Malis" <Andy.Malis@vivacenetworks.com>
Subject: Re: [PWOT] draft-anavi-tdmoip-01.txt
Cc: pwot@ietf.org, Yaakov Stein <yaakov_s@rad.co.il>, Schwarzbauer Hanns Juergen <HannsJuergen.Schwarzbauer@icn.siemens.de>
In-Reply-To: <NEBBKJPHCLKELBGJCKOIAEJOCCAA.motty@radusa.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: pwot-admin@ietf.org
Errors-To: pwot-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <pwot.ietf.org>
X-BeenThere: pwot@ietf.org

Motty,

>     This draft proposes a simple way of transporting TDM circuits over IP.
>It can be found on the IETF web site at:
>http://www.ietf.org/internet-drafts/draft-anavi-tdmoip-01.txt
>
>I would appreciate any comments you might have.

I agree that it's very simple, but it seems to have skimped on many of the 
issues and details that have been discussed previously in 
draft-boyle-sts-ip-00.txt and draft-malis-sonet-ces-mpls-03.txt, such as 
non-synchronous timing recovery, synchronous justification events, outage 
signaling, efficiency, and interactions with Internet traffic engineering.

In addition, AAL1 and AAL2 also make a number of assumptions based upon 
their usage above ATM, such as insured cell sequentiality and particular 
jitter and loss bounds, that need to be made explicit if you attempt to use 
them over IP rather than ATM.  I would be interested in hearing if you are 
aware of their successful use in non-ATM environments.

My final comment is that your text is very unclear regarding the use of 
RTP.  Its use is discussed in section 2, but not in section 5.  Is it used, 
or not?

Cheers,
Andy

========

At 3/5/2001 12:22 PM -0500, Motty Anavi wrote:
>FYI,
>
>-- Cheers, Motty
>
>Motty Anavi               |900 Corporate Dr.
>RAD data communication    |Mahwah, NJ 07430
>Dir. of Product Management|(201)529-1100x213
>e-mail: motty@radusa.com
>
>
>
>_______________________________________________
>pwot mailing list
>pwot@ietf.org
>http://www.ietf.org/mailman/listinfo/pwot


_______________________________________________
pwot mailing list
pwot@ietf.org
http://www.ietf.org/mailman/listinfo/pwot