Re: [MIB-DOCTORS] [OPS-DIR]http://www.ietf.org/internet-drafts/draft-ietf-ippm-storetraceroutes-10.txtand RFC 4560

["Romascanu, Dan (Dan)" <dromasca at avaya.com>]

David,

Are you referring to types definitions or to schema names as in 

<xs:complexType name="inetAddress">

Dan
 

> -----Original Message-----
> From: David Harrington [mailto:ietfdbh at comcast.net] 
> Sent: Monday, August 11, 2008 5:54 PM
> To: Romascanu, Dan (Dan); 'Juergen Quittek'; wkenneth at us.ibm.com
> Cc: Randy_Presuhn at mindspring.com; 'MIB Doctors (E-mail)'; 
> ops-dir at ietf.org
> Subject: RE: 
> [OPS-DIR]http://www.ietf.org/internet-drafts/draft-ietf-ippm-s
> toretraceroutes-10.txtand RFC 4560
> 
> Hi,
> 
> In MIB-land, we have naming conventions, documented in 
> RFC4181, that recommend objects and TCs be preceded by a 
> prefix derived from the MIB module name to help ensure global 
> uniqueness.
> 
> The existing standard InetAddress datatype is from the 
> INET-ADDRESS-MIB.
> 
> I recommend the module defined in this document be given a 
> unique name (e.g., ippm), and the datatypes defined in this 
> module be named using a prefix derived from the module name, 
> so the ippmInetAddress does not conflict with the 
> yangInetAddress or the xsdmiInetAddress and so on, and 
> neither definition is confused with the existing standard 
> InetAddress datatype from the INET-ADDRESS-MIB.
> 
> dbh 
> 
> > -----Original Message-----
> > From: ops-dir-bounces at ietf.org
> > [mailto:ops-dir-bounces at ietf.org] On Behalf Of Romascanu, Dan (Dan)
> > Sent: Monday, August 11, 2008 8:50 AM
> > To: Juergen Quittek; wkenneth at us.ibm.com
> > Cc: Randy_Presuhn at mindspring.com; MIB Doctors (E-mail); 
> > ops-dir at ietf.org
> > Subject: 
> > [OPS-DIR]http://www.ietf.org/internet-drafts/draft-ietf-ippm-s
> > toretraceroutes-10.txtand RFC 4560
> > 
> > The Internet-Draft
> > http://www.ietf.org/internet-drafts/draft-ietf-ippm-storetrace
> > routes-10.
> > txt is on the agenda of the IESG telechat this week for approval as 
> > Proposed Standard. The document proposes an Information 
> Model and an 
> > XML-based data model that reuse or try to be compatible 
> with some of 
> > the objects defined in the DISMAN-TRACEROUTE-MIB in 
> RRFC4560. It would
> be
> > good for the authors of RFC4560 and other to have a look at this 
> > document and comment if they see any problem.
> > 
> > Thanks and Regards,
> > 
> > Dan
> > _______________________________________________
> > OPS-DIR mailing list
> > OPS-DIR at ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-dir
> > 
> 
> 
_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS at ietf.org
https://www.ietf.org/mailman/listinfo/mib-doctors