Visual RFC.
ALL RFCs / RFC 2849
Read the RFC ↗
RFC 2849 / DIRECTORY INTERCHANGE

Rename an entry and choose its parent

05

A relative distinguished name, or RDN, is the entry’s name within its parent. modrdn and moddn are two changetype spellings for the Modify DN operation.

RFC 2849 · Modify DN grammar and example 6EXAMPLE
4 / 4
Rename an entry and choose its parentA third case additionally supplies newsuperior: ou=Games,dc=example. The new entry name is cn=River under that existing parent. This is a requested move within the illustrative directory, not a promise that any server-to-server move will work.Rename and move an entryou=Picnicou=Gamescn=Rivermove requestnewrdn: cn=Riverdeleteoldrdn: 1newsuperior: ou=Games,dc=examplecn values: RiverNew parent must already existRFC2849 · fictional data · simplified illustrations
04
Move to an existing parent

A third case additionally supplies newsuperior: ou=Games,dc=example. The new entry name is cn=River under that existing parent. This is a requested move within the illustrative directory, not a promise that any server-to-server move will work.

Source for this drawing: RFC 2849 · Read RFC source: Modify DN grammar and example 6 ↗

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
New to this? Start hereA quick picture + helpful background

A message needs an address.

Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.

Helpful first, if these ideas are unfamiliar

These pictures are analogies to help you learn. The linked RFC explains the actual rules.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

What changed
Unexplained deleteoldrdn flagVerified technical erratum 4009

The verified erratum explains 0 as retaining the old RDN values and 1 as deleting them. RFC4511 §4.9 clarifies that values forming the new RDN are retained.

Read the updated RFC section ↗
KEY POINT

newrdn: supplies the new relative name. deleteoldrdn: is required: 0 retains old naming values as ordinary attributes; 1 removes old values that are not part of the new RDN.

  • newrdn: supplies the new relative name. deleteoldrdn: is required: 0 retains old naming values as ordinary attributes; 1 removes old values that are not part of the new RDN.
  • Keeping an old naming value does not preserve a second entry at the old DN. The operation renames the existing entry and can move it with optional newsuperior:.
  • The new parent must exist. Schema, authorization, name conflicts and server capabilities can cause failure; arbitrary cross-server or cross-naming-context moves are not guaranteed. Simple cn/parent examples omit full DN escaping.
DETAILS

Fictional directory data. Fragments illustrate the format; no file, URL or directory is accessed. Import outcomes still depend on schema, permissions and server support.

Read the RFC section ↗

All chapters in RFC 2849

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗