[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Updates to OIDs
- To: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
- Subject: Updates to OIDs
- From: Brendan Kearney <bpk678@gmail.com>
- Date: Tue, 16 Sep 2014 08:41:07 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:date:content-type:mime-version :content-transfer-encoding; bh=jwzpg/wIErAyA9JP6ldcdLjp5zOFCIlEu8QkNgWvuZs=; b=tPlx3GyX5fBRrlWWM8TXoW5iWsa29GpoIPVx5NxlnuSO5tAvWs7vVqEtLsr7SUaIqw 0NhtfAbAIplMc2odb5xONoSAgx2I2HyKuRoS5zCWWez26I3pIQvjrO08T0lTNN/0HKE+ aOf2GG5LDcrMndBG7dtfI8e6tARlIfvCA1vzGKyEtGCmaQgmtKC2wb/iU9j9tORWspYY HJDmDXFTXMb15ay/X3x9t7y3xXHzia8q2wfDxhQzrCbuJ9S9gmVUywh3djIDYliDDcsr XPcqC3kDGoJUH9u4EoRFGyI1IblqsMzVqjPp9XL72QG8b69UPSWWlVBUCMtUxJ/AHC7z q/YA==
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