Re: [PWOT] RE: draft-danenberg-sonet-ces-mpls-mib-00.txt

Danny McPherson <danny@ambernetworks.com> Fri, 02 March 2001 20:56 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 PAA18314 for <pwot-archive@odin.ietf.org>; Fri, 2 Mar 2001 15:56:58 -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 PAA27726; Fri, 2 Mar 2001 15:52:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27694 for <pwot@ns.ietf.org>; Fri, 2 Mar 2001 15:52:30 -0500 (EST)
Received: from tcb.net (tcb.net [205.168.100.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA18079 for <pwot@ietf.org>; Fri, 2 Mar 2001 15:52:26 -0500 (EST)
Received: from sofos.tcb.net (sofos.tcb.net [127.0.0.1]) by tcb.net (8.9.3/8.9.3) with ESMTP id NAA02376; Fri, 2 Mar 2001 13:51:34 -0700
Message-Id: <200103022051.NAA02376@tcb.net>
X-Mailer: exmh version 2.0.3
To: ellanti@home.com
cc: mpls@UU.NET, pwot@ietf.org
From: Danny McPherson <danny@ambernetworks.com>
Reply-To: danny@ambernetworks.com
Subject: Re: [PWOT] RE: draft-danenberg-sonet-ces-mpls-mib-00.txt
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 02 Mar 2001 13:51:33 -0700
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

See Section 10 of Andy's -03 draft.  As mentioned, additional 
work needs to be done to support DS-n and other services.  

-danny


> I think  SONET/SDH CEM solution assumes that the client equipment connected
> to an MPLS network is interfacing on a OC-N interface. What if the client
> equipment is interfacing to MPLS network on T3/T1 interface. How is such
> client signal (DS1/DS3) transported if the CEM is very explicit about
> SONET/SDH ? Isn't it a goal to keep  TDM to the network boundaries only and
> not have TDM aggregation creep into the core of MPLS network? I think it is
> more of a network architectural issue and I think carriers can help us with
> the problem definition.


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