Re: [Megaco] Re: Usage of LocalControl,Local and Remote Descriptors!
"H.S.Sureshchandra" <suresh@ipgen.com> Tue, 10 June 2003 05:41 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02299 for <megaco-archive@lists.ietf.org>; Tue, 10 Jun 2003 01:41:17 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5A5dIB06033; Tue, 10 Jun 2003 01:39:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5A5bMB05504 for <megaco@optimus.ietf.org>; Tue, 10 Jun 2003 01:37:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02159 for <megaco@ietf.org>; Tue, 10 Jun 2003 01:37:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Pbmt-0001oI-00 for megaco@ietf.org; Tue, 10 Jun 2003 01:35:15 -0400
Received: from [202.144.91.188] (helo=ipgen-india.com) by ietf-mx with esmtp (Exim 4.12) id 19Pbmf-0001nF-00 for megaco@ietf.org; Tue, 10 Jun 2003 01:35:02 -0400
Received: from sureshchandra [192.168.1.230] by ipgen-india.com [192.168.1.15] with SMTP (MDaemon.PRO.v5.0.7.T) for <megaco@ietf.org>; Tue, 10 Jun 2003 11:06:53 +0530
Message-ID: <02b001c32f12$b2f9d4a0$e601a8c0@sureshchandra>
From: "H.S.Sureshchandra" <suresh@ipgen.com>
To: Tom Taylor <taylor@nortelnetworks.com>, Simran Chadha <simran_chadha1@rediffmail.com>
Cc: Megaco List <megaco@ietf.org>
References: <20030204052156.14303.qmail@webmail28.rediffmail.com> <3E400D7B.8080102@nortelnetworks.com>
Subject: Re: [Megaco] Re: Usage of LocalControl,Local and Remote Descriptors!
Date: Tue, 10 Jun 2003 11:09:42 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-MDRemoteIP: 192.168.1.230
X-Return-Path: suresh@ipgen.com
X-MDaemon-Deliver-To: megaco@ietf.org
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Hello Tom, I do not see incorporation of any of the observations made by my colleague Simran Chadha in the new RFC 3525, as "promised" by you in your earlier mail. Please clarify. Thanks ! Suresh ----- Original Message ----- From: "Tom Taylor" <taylor@nortelnetworks.com> To: "Simran Chadha" <simran_chadha1@rediffmail.com> Cc: "Megaco List" <megaco@ietf.org> Sent: Wednesday, February 05, 2003 12:29 AM Subject: Re: [Megaco] Re: Usage of LocalControl,Local and Remote Descriptors! > That "cannot not" is a typo -- I'll remove the "not" during the "authors' 48 hours" > interval prior to formal publication as a new RFC. > > On your second point: the two paragraphs apply independently to ReserveGroup and > ReserveValue. That is, it is possible to have ReserveGroup TRUE and ReserveValue > FALSE -- in which case the MG reserves for multiple session descriptions but is > restricted to one codec in each -- or vice versa. Or both could be TRUE, or both FALSE. > > On the third point, the intended meaning would be conveyed by replacing "if it > cannot support any of the alternatives" with "if it can support none of the > alternatives". Perhaps I can also do that during the "authors' 48 hours" period, > though we would usually do it through the ITU-T Implementor's Guide. > > The task of developing an unambiguous protocol specification is not simple. Your > points have eluded others in the three years since first approval. Thank you for > your contribution. > > Simran Chadha wrote: > > > > Hi List, > > > > Can someone please help me at the earliest on the issues raised earlier > > by me - particularly, usage of LocalControl,Local and Remote Descriptors ? > > > > Thanks in advance. > > > > Simran Chadha > > On Thu, 30 Jan 2003 Simran Chadha wrote : > > > >> Hi List, > >> > >> Can you please help me with clarifications in my understanding of > >> sections 7.1.7 and 7.1.8 on the use of LocalControl,Local and Remote > >> Descriptors. > >> > >> As per draft-ietf-megaco-3015corr-03, in section 7.1.7, > >> If the value of a Reserve property is True, the MG SHALL reserve > >> resources for all alternatives specified in the Local and/or Remote > >> descriptors for which it currently has resources available. It SHALL > >> respond with the alternatives for which it reserves resources. If it > >> cannot not support any of the alternatives, it SHALL respond with a > >> reply to the MGC that contains empty Local and/or Remote descriptors. > >> The use of two negations - "cannot not" in the last statement will > >> imply that - If it can support any of the alternatives, it SHALL > >> respond with a reply to the MGC that contains empty Local and/or > >> Remote descriptors. > >> I don't think this is what is meant to be conveyed here. > >> > >> Also in section 7.1.7 the first para starts - If the value of a > >> Reserve property is True, ..... > >> while the second para starts - If the value of a Reserve property is > >> False, .... > >> Now as there are two Reserve properties - one Reserve Group and the > >> other Reserve Value, One could be False and the other could be True. > >> Then in this case what will be the inference - Should para 1 apply or > >> para 2 ? Both the paras would seem to be mutually exclusive in what is > >> needed to be done. > >> > >> Also statements like "if it cannot support any of the alternatives ... > >> " - will have two meanings. > >> 1. Any - Not even one - NONE of the alternatives is supported. > >> 2. Any - Atleast one - While a few alternatives can be supported, a > >> few might not be. > >> > >> The protocol needs to be more clear on such aspects in the documents > >> henceforth. The English language is understood in different parts of > >> the world. Variations to agreed usage of the language terms will make > >> it difficult for new users of Megaco protocol, like me. > >> > >> Can someone please educate me on the exact usage and meaning of > >> LocalControl,Local and Remote Descriptors ? > >> > >> Thanks and awaiting comments and clarifications > >> > >> Simran Chadha > > > > > > > > _______________________________________________ > > Megaco mailing list > > Megaco@ietf.org > > https://www1.ietf.org/mailman/listinfo/megaco > > > > _______________________________________________ > Megaco mailing list > Megaco@ietf.org > https://www1.ietf.org/mailman/listinfo/megaco > _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco
- [Megaco] Usage of LocalControl,Local and Remote D… Simran Chadha
- [Megaco] Re: Usage of LocalControl,Local and Remo… Simran Chadha
- Re: [Megaco] Re: Usage of LocalControl,Local and … Tom Taylor
- Re: [Megaco] Re: Usage of LocalControl,Local and … H.S.Sureshchandra
- Re: [Megaco] Re: Usage of LocalControl,Local and … Tom Taylor