From fa2d66ca1808e8bcd9bcf95737f08b071032187f Mon Sep 17 00:00:00 2001 From: Harald Welte Date: Sat, 17 Oct 2020 13:09:34 +0200 Subject: ns2: More verbose comments on gprs_ns2_vc_mode Change-Id: I647b9d883c1acc47cd352196a819a9c9bf8dc6ff --- include/osmocom/gprs/gprs_ns2.h | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) (limited to 'include/osmocom/gprs/gprs_ns2.h') diff --git a/include/osmocom/gprs/gprs_ns2.h b/include/osmocom/gprs/gprs_ns2.h index 497265e5..fddc896a 100644 --- a/include/osmocom/gprs/gprs_ns2.h +++ b/include/osmocom/gprs/gprs_ns2.h @@ -20,8 +20,13 @@ struct gprs_ns_ie_ip4_elem; struct gprs_ns_ie_ip6_elem; enum gprs_ns2_vc_mode { - NS2_VC_MODE_BLOCKRESET, /* The VC will use RESET/BLOCK/UNBLOCK to start the connection and do ALIVE/ACK */ - NS2_VC_MODE_ALIVE, /* The will only use ALIVE/ACK */ + /*! The VC will use RESET/BLOCK/UNBLOCK to start the connection and do ALIVE/ACK. + * This is what is needed for Frame Relay transport, and if you use a R97/R99 Gb + * interface over an IP transport (never standardized by 3GPP) */ + NS2_VC_MODE_BLOCKRESET, + /*! The VC will only use ALIVE/ACK (no RESET/BLOCK/UNBLOCK), which is for Gb-IP + * interface compliant to 3GPP Rel=4 or later. */ + NS2_VC_MODE_ALIVE, }; /*! Osmocom NS primitives according to 48.016 5.2 Service primitves */ -- cgit v1.2.3