2009/344 Bridging Updates

[James Carlson]

Sebastien Roy writes:
> > Consider the reference updated.
> 
> Excellent, thanks.  +1

The related changes in the spec are:

@@ -635,17 +635,17 @@
 
 2.1 Packet Observability
 
-    Each bridge instance will be assigned an "observability device,"
-    using the /dev/net/ facility implemented for "Clearview: IP
-    Observability Devices" (PSARC 2006/475).  These nodes will be
-    named by the bridge name plus a trailing "0".
+    Each bridge instance will be assigned a DLPI device intended for
+    observability purposes, using the /dev/net/ facility implemented
+    for "Clearview Nemo unification and vanity naming" (PSARC
+    2006/499).  These nodes will be named by the bridge name plus a
+    trailing "0".
 
-    The observability node is intended for use with snoop and
-    wireshark.  It behaves as a standard Ethernet interface, but does
-    not permit the transmission of packets.  All transmitted packets
-    are silently dropped.  It's not possible to plumb IP on top;
-    attempts to do DL_BIND_REQ without using the passive option will
-    fail.
+    This special node is intended for use with snoop and wireshark.
+    It behaves as a standard Ethernet interface, but does not permit
+    the transmission of packets.  All transmitted packets are silently
+    dropped.  It's not possible to plumb IP on top; attempts to do
+    DL_BIND_REQ without using the passive option will fail.
 
     The user of this node will get a single unmodified copy of every
     packet handled by the bridge, similar to a "monitoring" port on a

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677