Fwd: Manual Post Requested for draft-howard-rfc2307bis

I guess this will show up in a couple of days.

Major differences from version 01 of the rfc2307bis document:

1) Added host and hostos attribute options to allow system-specific values for 
attributes when needed. (E.g. to accommodate different homeDirectory locations 
on various machines.)

2) Added integerOrderingMatch ORDERING rules to attributes with integer 
syntax. Admins frequently need to search for things like (uidNumber>=1000) and 
the lack of the ORDERING rules was a great impediment.

3) Added new groupOfMembers structural objectclass with "member" as an 
optional attribute, to support groups with zero members. This class should be 
used whenever a structural group class is needed. The use of 
groupOfUniqueNames (and groupOfNames) is deprecated.

4) Added references to PAM and LDAP Password Policy. The use of LDAP 
information for authentication via NSS mechanisms is deprecated. The use of 
shadowAccount information for password policy is deprecated.

5) Added Naming Considerations section with caveats re: user and group naming.

-------- Original Message --------
Subject: Manual Post Requested for draft-howard-rfc2307bis
Date: Sun,  9 Aug 2009 14:31:24 -0700 (PDT)
From: IETF I-D Submission Tool <[email protected]>
To: [email protected]
CC: [email protected],[email protected]

Manual Posting Requested for following Internet-Draft:

I-D Submission Tool URL: 
https://datatracker.ietf.org/idst/status.cgi?submission_id=17311


Filename:	   draft-howard-rfc2307bis
Version:	   02
Staging URL:	   http://www.ietf.org/staging/draft-howard-rfc2307bis-02.txt
Title:		   An Approach for Using LDAP as a Network Information Service
Creation_date:	   2009-08-09
WG ID:		   Indvidual Submission
Number_of_pages: 32
Abstract:
This document describes a mechanism for mapping entities related to
TCP/IP and the UNIX system [UNIX] into [X.500] entries so that they
may be resolved with the Lightweight Directory Access Protocol
[RFC4511].  A set of attribute types and object classes are proposed,
along with specific guidelines for interpreting them.  The intention
is to assist the deployment of LDAP as an organizational nameservice.
No proposed solutions are intended as standards for the Internet.
Rather, it is hoped that a general consensus will emerge as to the
appropriate solution to such problems, leading eventually to the
adoption of standards.  The proposed mechanism has already been
implemented with some success.

Submitter: Howard Chu ([email protected])

Author(s):
Luke Howard, [email protected]
Howard Chu, [email protected]


Comment:
The form grabbed too much text for the Abstract, trimmed it back down to the 
proper text.