|
Hi, I looked over this draft over the weekend
and I have some comments and questions. 1) It is hard to understand why a new feature (call control) is being
designed as an extension to a notification message. The resulting
protocol design obscures the function of the protocol and creates special case
processing that may lead to problems. Is there a reason that new message types
were not specified for call request and response? 2) Given the stated intent of maintaining strict independence between
call and connection control, were other (existing) call control protocols
considered (rather than beginning a new call control protocol specification)? 3) The network models being used in section 4.3 and section 7 are not
clear. In particular the relationships between the call controllers, network
boundaries, ingress/egress nodes, and ingress/egress links are not clear.
Figures would be very helpful here. 4) Simultaneous Call and connection establishment can be very handy in
the common case of a call with a single connection. This model should be
supported (and in fact it is in the case of so called “connection setup
without a call”). 5) The call control mechanism defined appears to support only IPv4 or
IPv6 addressed endpoints from a single address space. Is this correct? Regards, Ben From: owner-ccamp@ops.ietf.org
[mailto:owner-ccamp@ops.ietf.org] On Behalf
Of Brungard, Deborah A, ALABS All, As discussed at the last CCAMP meeting, the authors of this
draft would like the draft to be considered for WG Last Call. Although it
appears to be a 00 draft, the material was previously in
draft-ietf-ccamp-gmpls-te-ason-03.txt. At least one implementation exists. This email begins a two week Working Group Last Call on the
draft: The last call will complete on June 19th at 9PM EST. Comments should be addressed to the mailing list or, if
anonymity is preferred, to me. On a point of procedure, as both Adrian and
myself are co-authors, anyone who has an issue with this draft going to WG
Last Call should contact one of our ADs, Ross (rcallon@juniper.net) or Bill (fenner@research.att.com). Thanks, Deborah t ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================ |