list,
i am wondering what the right way is to introduce new OIDs, or request that new OIDs be introduced, to existing schemas. the ipNetwork class could benefit with a couple new optional attributes.
the ipNetworkVLAN (only a suggested name) can be used to indicate the VLAN associated with an ipNetworkNumber. due to the increasing use of VLANs, the datapoint being represented in LDAP makes sense to me.
another seemingly logical OID would be ipNetCIDR (suggestion only) which would be similar to the ipNetmaskNumber, but would be the short form notation.
thank you,
brendan kearney
Brendan Kearney wrote:
list,
i am wondering what the right way is to introduce new OIDs, or request that new OIDs be introduced, to existing schemas. the ipNetwork class could benefit with a couple new optional attributes.
The ipNetwork class is part of RFC2307, I suggest you write a new Internet Draft defining the attributes you propose and send it to the ldapext mailing list for discussion.
http://www.ietf.org/mail-archive/web/ldapext/current/maillist.html
the ipNetworkVLAN (only a suggested name) can be used to indicate the VLAN associated with an ipNetworkNumber. due to the increasing use of VLANs, the datapoint being represented in LDAP makes sense to me.
another seemingly logical OID would be ipNetCIDR (suggestion only) which would be similar to the ipNetmaskNumber, but would be the short form notation.
thank you,
brendan kearney
On Tue, 2014-09-16 at 21:38 +0100, Howard Chu wrote:
Brendan Kearney wrote:
list,
i am wondering what the right way is to introduce new OIDs, or request that new OIDs be introduced, to existing schemas. the ipNetwork class could benefit with a couple new optional attributes.
The ipNetwork class is part of RFC2307, I suggest you write a new Internet Draft defining the attributes you propose and send it to the ldapext mailing list for discussion.
http://www.ietf.org/mail-archive/web/ldapext/current/maillist.html
the ipNetworkVLAN (only a suggested name) can be used to indicate the VLAN associated with an ipNetworkNumber. due to the increasing use of VLANs, the datapoint being represented in LDAP makes sense to me.
another seemingly logical OID would be ipNetCIDR (suggestion only) which would be similar to the ipNetmaskNumber, but would be the short form notation.
thank you,
brendan kearney
Please excuse my ignorance on the subject, but is a specific format required? are specific details required? a template or any suggested reading would be greatly appreciated.
thank you,
brendan kearney
Brendan Kearney wrote:
On Tue, 2014-09-16 at 21:38 +0100, Howard Chu wrote:
Brendan Kearney wrote:
list,
i am wondering what the right way is to introduce new OIDs, or request that new OIDs be introduced, to existing schemas. the ipNetwork class could benefit with a couple new optional attributes.
The ipNetwork class is part of RFC2307, I suggest you write a new Internet Draft defining the attributes you propose and send it to the ldapext mailing list for discussion.
Please excuse my ignorance on the subject, but is a specific format required? are specific details required? a template or any suggested reading would be greatly appreciated.
The format is defined in RFC2629. These days it's easiest to write in XML http://xml2rfc.ietf.org/
Also follow RFC4520.
Howard Chu wrote:
Brendan Kearney wrote:
On Tue, 2014-09-16 at 21:38 +0100, Howard Chu wrote:
Brendan Kearney wrote:
list,
i am wondering what the right way is to introduce new OIDs, or request that new OIDs be introduced, to existing schemas. the ipNetwork class could benefit with a couple new optional attributes.
The ipNetwork class is part of RFC2307, I suggest you write a new Internet Draft defining the attributes you propose and send it to the ldapext mailing list for discussion.
Please excuse my ignorance on the subject, but is a specific format required? are specific details required? a template or any suggested reading would be greatly appreciated.
The format is defined in RFC2629. These days it's easiest to write in XML http://xml2rfc.ietf.org/
Also follow RFC4520.
Many more hints for writing I-Ds: http://www.rfc-editor.org/
Ciao, Michael.
openldap-technical@openldap.org
-
Brendan Kearney -
Howard Chu -
Michael Ströder