RE: [Iptel] read-only compliance for TRIP MIB

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

They did not specify that MIN-ACCESS of read-only is OK in 
their MODULE COMPLIANCE. That is fine by me, but if they do
so, then of course read-only implementation cannot claim
compliance. So adding an extra MODULE-COMPLIANCE seems a
very easy and simple way to address this.

Thanks,
Bert 

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: woensdag 14 januari 2004 16:14
> To: mreview@ops.ietf.org
> Subject: FW: [Iptel] read-only compliance for TRIP MIB
> 
> 
> This came up in IPTEL. Comments?
> 
> Regards,
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: iptel-admin@ietf.org [mailto:iptel-admin@ietf.org]On 
> Behalf Of David Zinman
> Sent: 14 January, 2004 4:01 PM
> To: iptel@ietf.org
> Subject: [Iptel] read-only compliance for TRIP MIB
> 
> 
> There has been a request to include a "read-only" compliance
> section in the TRIP MIB. If most implementations plan on 
> doing read-write support then it might not useful. 
> However, if there is enough support for read-only compliance,
> another draft will be issued to support it.
> 
> Comments, preferences??
> 
> The decision will be made by Tuesday Jan 20.
> 
> DZ
> 
> 
> 
> _______________________________________________
> Iptel mailing list
> Iptel@ietf.org
> https://www.ietf.org/mailman/listinfo/iptel
>