RE: Query

WG discussions based on the Midcom protocol evaluation resulted in the
selection of SNMPv3 as the "best choice" of the 5 exisiting protocols
evaluated. Refer to
http://www.ietf.org/internet-drafts/draft-ietf-midcom-protocol-eval-06.txt
for the reasons Megaco/H.248 was deemed less suitable.

Mary 

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Tajinder Singh
Sent: Thursday, March 24, 2005 3:56 PM
To: '[email protected]'
Subject: RE: [midcom] Query


The first draft refers indirectly to snmp v3 while the second one refers to
simco. 
What about Megaco/H.248 since some of the vendors have implemented it in
accordance with Midcom architecture? 
Does Midcom ietf community recommend one protocol over the other? 


Thanks 
Tajinder 
 
  
  
  
-----Original Message----- 
From: [email protected] [mailto:[email protected]] On Behalf Of
Martin Stiemerling 
Sent: Thursday, March 24, 2005 7:30 AM 
To: Pravin Chawda; [email protected] 
Subject: Re: [midcom] Query 
Hi, 
--On Donnerstag, 24. März 2005 16:13 Uhr +0530 Pravin Chawda 
<[email protected]> wrote: 
| 
| Dear Sir/Madam 
| 
| I have a query, is there any protocol identified which suites Midcom to 
| communicate between middlebox and Midcom Agents. 
The MIDCOM MIB module currently developed by the MIDCOM working 
group is the MIDCOM protocol, see 
<http://www.ietf.org/internet-drafts/draft-ietf-midcom-mib-05.txt> 
Another protocol implementing MIDCOM excatly as the MIB would do: 
<http://www.ietf.org/internet-drafts/draft-stiemerling-midcom-simco-07.txt> 
Regards, 
 Martin 
| 
| Warm regards!!! 
| Pravin Chawda 
| 
| -------------------------------------- 
| Sr. Technical Associate 
| Center of Excellence 
| Intelligent Networks - VoIP 
| Mahindra Britsh Telecom Ltd 
| Office  : +91 20 56018100   Extn 2867 
| -------------------------------------- 
| 
| 
| ********************************************************* 
| Disclaimer: 
| 
| The contents of this E-mail (including the contents of the enclosure(s) 
| or attachment(s) if any) are privileged and confidential material of MBT 
| and should not be disclosed to, used by or copied in any manner by anyone 
| other than the intended addressee(s).   In case you are not the desired 
| addressee, you should delete this message and/or re-direct it to the 
| sender.  The views expressed in this E-mail message (including the 
| enclosure(s) or attachment(s) if any) are those of the individual sender, 
| except where the sender expressly, and with authority, states them to be 
| the views of MBT. 
| 
| This e-mail message including attachment/(s), if any, is believed to be 
| free of any virus.  However, it is the responsibility of the recipient to 
| ensure that it is virus free and MBT is not responsible for any loss or 
| damage arising in any way from its use 
| 
| ********************************************************* 
| 
| _______________________________________________ 
| midcom mailing list 
| [email protected] 
| https://www1.ietf.org/mailman/listinfo/midcom 



_______________________________________________ 
midcom mailing list 
[email protected] 
https://www1.ietf.org/mailman/listinfo/midcom

_______________________________________________
midcom mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/midcom