diff --git a/draft-ymbk-idr-l3nd-ulpc.xml b/draft-ymbk-idr-l3nd-ulpc.xml
index 87314dd..2d1ec22 100644
--- a/draft-ymbk-idr-l3nd-ulpc.xml
+++ b/draft-ymbk-idr-l3nd-ulpc.xml
@@ -103,7 +103,7 @@
     PDU is defined as follows:</t>
 
 <!--
-    protocol "Version = 0:8,Type = 8:8,Payload Length:32,ULPC Type:8,AttrCount:8,Serial Number:32,Attribute List ...:32"
+    protocol "Version = 0:8,Type = 8:8,Payload Length:32,ULPC Type:8,AttrCount:8,Serial Number:32,Attribute Sub-TLV List ...:32"
 -->
 
     <figure>
@@ -189,13 +189,13 @@
       for an particular address family on a specific link at any point
       in time; receipt of a new BGP ULPC PDU for a particular address
       family replaces the data any previous one; but does not actually
-      affect the session unless there is a BGP Restart Attribute
-      sub-TLV.</t>
+      affect the session<!-- unless there is a BGP Restart Attribute
+      sub-TLV-->.</t>
 
-      <t>If there are one or more open BGP sessions, absent a BGP
-      Restart sub-TLV, receipt of a new BGP ULPC PDU SHOULD not affect
-      these sessions.  The received data are stored for a future session
-      restart.</t>
+      <t>If there are one or more open BGP sessions, <!-- absent a BGP
+      Restart sub-TLV, --> receipt of a new BGP ULPC PDU SHOULD not
+      affect these sessions.  The received data are stored for a future
+      session restart.</t>
       
       <t>As a link may have multiple encapsulations and multiple
       addresses for an IP encapsulation, which address of which
@@ -210,22 +210,27 @@
       <t>If a peering address has been announced as a loopback, i.e.
       MUST BE flagged as such in the L3ND Encapsulation PDU (see <xref
       target="I-D.ymbk-idr-l3nd"/> Sec. 10.2), a two or three hop BGP
-      session MUST be established.  Otherwise a direct one hop session
-      is used.  The BGP session to a loopback will forward to the peer's
-      address which was marked as Primary in the L3ND Encapsulation
-      Flags, iff it is in a subnet which is shared with both BGP
-      speakers.  If the primary is not in a common subnet, then the BGP
-      speaker MAY pick a forwarding next hop that is in a subnet they
-      share.  If there are multiple choices, the BGP speaker SHOULD have
-      signaled which subnet to choose in an Upper-Layer Protocol
+      session MUST be established as needed.  Otherwise a direct one hop
+      session is used.  The BGP session to a loopback will forward to
+      the peer's address which was marked as Primary in the L3ND
+      Encapsulation Flags, iff it is in a subnet which is shared with
+      both BGP speakers.  If the primary is not in a common subnet, then
+      the BGP speaker MAY pick a forwarding next hop that is in a subnet
+      they share.  If there are multiple choices, the BGP speaker SHOULD
+      have signaled which subnet to choose in an Upper-Layer Protocol
       Configuration PDU Attribute.</t>
 
       <t>Attributes MUST be unique in the Attribute List.  I.e. a
       particular Attr Type MUST NOT occur more than once in the
-      Attribute List.  If a ULPC PDU is received with multiple
-      occurances of the same Attr Type, an Error ACK should be
+      Attribute List.  If a ULPC PDU is received with more than one
+      occurrence of a particular Attr Type, an Error ACK MUST be
       returned.</t>
+
+      <t>As there are separate PDU Attr Types for IPv4 and IPv6 peering
+      addresses, separate sessions for the two AFIs MAY be created for
+      the same ASN in one ULPC PDU.</t>
         
+<!--
       <section anchor="restart" title="BGP Restart">
 
 	<t>When all attributes in PDU have been processed, stop the
@@ -238,9 +243,9 @@
 	<t>If there is no current BGP session to the specified peer,
 	start one.</t>
 
-<!--
+<!- -
     protocol "Attr Type = 0:8,Attr Len = 4/16:8,Dest IP:128"
--->
+- ->
 
         <figure>
           <artwork>
@@ -260,7 +265,7 @@
             </artwork>
           </figure>
         </section>
-
+-->
       <section anchor="asn" title="BGP ASN">
 
         <t>The four octet Autonomous System number MUST be specified.
@@ -323,7 +328,7 @@
 
         <t>As usual, the BGP OPEN capability negotiation will determine
         the AFI/SAFIs to be transported over the peering, see <xref
-        target="RFC4760"/> .</t>
+        target="RFC4760"/>.</t>
 
 <!--
     protocol "Attr Type = 3:8,Attr Len = 17:8,My IPv6 Peering Address:128,Prefix Len:8"