The basics of this proposal are to add an RR type which says at each level of delegation, how many more bits of prefix are used up.

Delegation from the root for zone IPv4.INT

For purposes of example, I've referred to the new address to name tree as IPv4.INT, but any base would work. The glue RRs for delegating the IPv4.INT zone from the INT servers would be: 
IPv4.INT.	SOA	NS.INTERNIC.NET. HOSTMASTER.INTERNIC.NET. (
			1994123000	;serial
			10800	;refresh
			900	;retry
			604800	;expire
			86400 ) ;minim
	NS	NS.INTERNIC.NET.
	NS	AOS.ARL.ARMY.MIL.
	NS	NS1.ISI.EDU.
	NS	C.PSI.NET.
	NS	TERP.UMD.EDU.
	NS	NS.NASA.GOV.
	NS	NIC.NORDU.NET.
	NS	NS.ISC.ORG.
	NS	NS.NIC.DDN.MIL.
	PFX	8
Which defines the root of the tree and specifies that the next label represents the next (i.e. the first) 8 bits of the address.

Zone IPv4.INT

Within the IPv4.INT zone the above RRs would be repeated, followed by delegations for all the combinations of the first 8 bits that are defined. A typical delegation might look like this: 
18	NS	STRAWB.MIT.EDU.
	NS	W20NS.MIT.EDU.
	NS	BITSY.MIT.EDU.
	PFX	9
Specifying that net 18 is delegated to MIT and they use the next 9 bits for the next level of delegation.

Another delegation would be: 

28	NS	NIC.DSI.NET.
	NS	NOC.DSI.NET.
	PFX	24
Which shows the delegation of net 28 to the DSI which uses the next 24 bits (i.e. all the rest) for the sub-identifier, i.e. as a flat assignment space (for delegation purposes).

Two more, interesting delegation examples (from the root to the root) show how the Class B and Class C parts of the number space would be delegated. Class B uses 8 more bits and Class C 16 more bits for delegation. 

128	NS	NS.INTERNIC.NET.
	NS	AOS.ARL.ARMY.MIL.
	NS	NS1.ISI.EDU.
	NS	C.PSI.NET.
	NS	TERP.UMD.EDU.
	NS	NS.NASA.GOV.
	NS	NIC.NORDU.NET.
	NS	NS.ISC.ORG.
	NS	NS.NIC.DDN.MIL.
	PFX	8
      o
      o
      o
192	NS	NS.INTERNIC.NET.
	NS	AOS.ARL.ARMY.MIL.
	NS	NS1.ISI.EDU.
	NS	C.PSI.NET.
	NS	TERP.UMD.EDU.
	NS	NS.NASA.GOV.
	NS	NIC.NORDU.NET.
	NS	NS.ISC.ORG.
	NS	NS.NIC.DDN.MIL.
	PFX	16

Zone 192.IPv4.INT

In the 192.IPv4.INT zone, the IDs are 16 bit numbers. Here's an example delegation for nets 192.1.5.0 and 192.1.6.0 (both are BBN nets). 
261	NS	SPOOLER1.BBN.COM.
	NS	SPOOLER2.BBN.COM.
	PFX	8
262	NS	SPOOLER1.BBN.COM.
	NS	SPOOLER2.BBN.COM.
	PFX	8

Zone 18.IPv4.INT

Now let's follow the delegation of net 18 further as it's an interesting case. Remember above that the next level of delegation was 9 bits wide, allowing subnet numbers from 1-510. The zone would start with the same authority records as above (with an SOA), and some typical delegations (one to an independent lab, and another for a subnet maintained by the same authority) might be: 
52	NS	MINTAKA.LCS.MIT.EDU.
	NS	TOWER.LCS.MIT.EDU.
	NS	OSSIPEE.LCS.MIT.EDU.
	NS	LAMPANG.LCS.MIT.EDU.
	PFX	15
500	NS	STRAWB.MIT.EDU.
	NS	W20NS.MIT.EDU.
	NS	BITSY.MIT.EDU.
	PFX	15

Zone 52.18.IPv4.INT

And some final RRs at the leaf nodes: 
1	PTR	RADOLE.LCS.MIT.EDU.	 ; 18.26.0.1
500	PTR	OTHER-HOST.LCS.MIT.EDU.	 ; 18.26.1.244
1024	PTR	YET-ANOTHER.LCS.MIT.EDU. ; 18.26.4.0
The actual domain name for that last entry is 1024.52.18.IPv4.INT. as it's host 1024 on subnet 52 of net 18.