| ng_sscfu.4 (123943) | ng_sscfu.4 (130857) |
|---|---|
| 1.\" 2.\" Copyright (c) 2001-2003 3.\" Fraunhofer Institute for Open Communication Systems (FhG Fokus). 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: --- 12 unchanged lines hidden (view full) --- 21.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 22.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 23.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 24.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 25.\" SUCH DAMAGE. 26.\" 27.\" Author: Hartmut Brandt <harti@freebsd.org> 28.\" | 1.\" 2.\" Copyright (c) 2001-2003 3.\" Fraunhofer Institute for Open Communication Systems (FhG Fokus). 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: --- 12 unchanged lines hidden (view full) --- 21.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 22.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 23.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 24.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 25.\" SUCH DAMAGE. 26.\" 27.\" Author: Hartmut Brandt <harti@freebsd.org> 28.\" |
| 29.\" $FreeBSD: head/share/man/man4/ng_sscfu.4 123943 2003-12-28 22:34:47Z ru $ | 29.\" $FreeBSD: head/share/man/man4/ng_sscfu.4 130857 2004-06-21 17:42:49Z mpp $ |
| 30.\" 31.\" ng_sscfu(4) man page 32.\" 33.Dd October 24, 2003 34.Dt NG_SSCFU 4 35.Os FreeBSD 36.Sh NAME 37.Nm ng_sscfu --- 8 unchanged lines hidden (view full) --- 46netgraph node implements ITU-T recommendation Q.2130. 47This recommendation specifies the Service Specific Coordination 48Function at the UNI. 49This is a thin sub-layer between the SSCOP (see 50.Xr ng_sscop 4 ) 51and the UNI signalling. 52This node does not really implement a protocol but 53provides a mapping between the signals at the upper layer of the SSCOP and | 30.\" 31.\" ng_sscfu(4) man page 32.\" 33.Dd October 24, 2003 34.Dt NG_SSCFU 4 35.Os FreeBSD 36.Sh NAME 37.Nm ng_sscfu --- 8 unchanged lines hidden (view full) --- 46netgraph node implements ITU-T recommendation Q.2130. 47This recommendation specifies the Service Specific Coordination 48Function at the UNI. 49This is a thin sub-layer between the SSCOP (see 50.Xr ng_sscop 4 ) 51and the UNI signalling. 52This node does not really implement a protocol but 53provides a mapping between the signals at the upper layer of the SSCOP and |
| 54the signals, the UNI expectes at its lower layer. | 54the signals, the UNI expects at its lower layer. |
| 55It also provides default values for the parameters of the SSCOP. 56.Pp 57After creation of the node, the SSCF instance must be created by sending 58an enable message to the node. 59If the node is enabled, default SSCOP parameters 60can be retrieved and and set in the corresponding SSCOP instance. 61.Pp 62The node is shutdown either by a --- 36 unchanged lines hidden (view full) --- 99}; 100.Ed 101.Pp 102The arrows in the comment show the direction of the signal whether it 103is a signal that comes out of the node 104.Ql -> 105or is sent by the node user to the node 106.Ql <- . | 55It also provides default values for the parameters of the SSCOP. 56.Pp 57After creation of the node, the SSCF instance must be created by sending 58an enable message to the node. 59If the node is enabled, default SSCOP parameters 60can be retrieved and and set in the corresponding SSCOP instance. 61.Pp 62The node is shutdown either by a --- 36 unchanged lines hidden (view full) --- 99}; 100.Ed 101.Pp 102The arrows in the comment show the direction of the signal whether it 103is a signal that comes out of the node 104.Ql -> 105or is sent by the node user to the node 106.Ql <- . |
| 107The type of data expected for the signal is specified in parantheses. | 107The type of data expected for the signal is specified in parentheses. |
| 108This data starts at the 109.Fa data 110field of the message structure. 111.El 112.Pp 113If the 114.Dv lower 115hook is disconnected and the node is enabled, the protocol state is --- 40 unchanged lines hidden --- | 108This data starts at the 109.Fa data 110field of the message structure. 111.El 112.Pp 113If the 114.Dv lower 115hook is disconnected and the node is enabled, the protocol state is --- 40 unchanged lines hidden --- |