[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PWE3] I-D ACTION:draft-riegel-pwe3-tdm-requirements-00.txt
Dear Daniel,
it was not our intention to describe a particular protocol in the
requirements document. It is our intention to come to a clear
specification on the requirements we have for a PWE3 TDM Emulation protocol.
As long as there is not a consensus about the requirements a protocol
should fulfill there is hardly a way to design the appropriate protocol
itself (or decide about a protocol proposal).
I agree with you, that the I-D is in its -00 revision quite generic, but
that is not a bug but a feature; it allows for further contributions and
refinements coming out of the discussion in the PWE3 working group.
Do you have proposals for further requirements we should add to the I-D?
Any comment and input is highly appreciated.
Bye
Max
Daniel Feldman wrote:
> Dear Mr. Riegel,
> this document seems to me as the Lowest common denominator of
> TDMoIP and CESoPSN (indeed, it is called TDMoPSN).
>
> Not surprisingly, it is generic enough to not say anything about
> what is to be implemented.
> Are we agreeing to disagree? Does this mean that there is not
> going to be a REAL standard way of encapsulating TDMoPSN?
>
> Thanks in advance,
> Daniel Feldman.
>
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Wednesday, June 19, 2002 1:28 PM
> Cc: pwe3@ietf.org
> Subject: [PWE3] I-D ACTION:draft-riegel-pwe3-tdm-requirements-00.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> Title : Requirements for Edge-to-Edge Emulation of TDM
> Circuits over Packet Switching Networks (PSN)
> Author(s) : M. Riegel et al.
> Filename : draft-riegel-pwe3-tdm-requirements-00.txt
> Pages : 20
> Date : 18-Jun-02
>
> This document specifies the particular requirements for edge-to-
> edge-emulation of circuits carrying time division multiplexed (TDM)
> digital signals over packet-switched networks. It is based on the
> common framework of PWE3 as defined in [PWE3-FW] and the
> considerations on protocol layering in PWE3 as discussed in [PWE3-
> LAYERS].
> It makes references to requirements in [PWE3-REQ] where applicable
> and complements [PWE3-REQ] by defining additional requirements
> originating from specifics of TDM circuits.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-riegel-pwe3-tdm-requirements-00.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-riegel-pwe3-tdm-requirements-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www
> or
> <http://www.ietf.org/shadow.html>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-riegel-pwe3-tdm-requirements-00.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.
>
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3