In a layered approach to protocol architecture, protocols have a relationship to one another such that a protocol at layer (n) uses the services of the layer below it \u2014 the (n \u2212 1) services \u2014 which, in turn, are provided by a layer (n \u2212 1) protocol. One of the services used by a layer (n) protocol is the encapsulation<\/i> of its (n) Protocol Data Units (PDUs) in a way which is transparent to it. Such encapsulation is realized by the carriage of the (n) PDUs as user data in an (n \u2212 1) Service Data Unit (SDU).<\/p>\n
In a limited case, the operation of a particular protocol at layer (n \u2212 1) implies the operation, above layer (n \u2212 1), of a single layer (n) protocol or single set of related (n) \/ (n + 1)… protocols. However, in a more general case, there may be more than one protocol (or set of related protocols starting) at layer (n) that can operate above layer (n \u2212 1) in a given environment. In such cases, there is a need for explicit identification<\/i> of the protocol (or set of protocols starting) at layer (n).<\/p>\n
There also may be a need to manipulate the (n \u2212 1) protocol (i.e. the encapsulating<\/i> protocol) in certain ways specific to the layer (n) protocol (i.e. the encapsulated<\/i> protocol). Such manipulations form the basis of a set of procedures that must be specified for the layer (n) protocol.<\/p>\n
The above observations regarding protocol identification and encapsulation are also applicable in cases where an (n) layer is further divided into sublayers.<\/p>\n
Cases in which an (n) protocol operates for the purpose of establishing a parallel universe of protocols (regardless of the layered structure of that universe) also give rise to a need for the (n) protocol to be able to identify the protocol(s) in the parallel universe. In these cases, however, there is no encapsulating\/encapsulated relationship between the (n) protocol and the parallel universe set of protocols.<\/p>\n
The above principles lead to a need to establish a framework for protocol identification and encapsulation. These principles apply to the relationship between two protocols (recognizing that one of them may be a set of related protocols) and can be applied recursively. This Recommendation | International Standard provides a framework for explicit protocol identification and for protocol encapsulation. Implicit protocol identification (see 4.2) is beyond the scope of this Recommendation | International Standard.<\/p>\n","protected":false},"excerpt":{"rendered":"
Information technology. Framework for protocol identification and encapsulation<\/b><\/p>\n\n\n
\n Published By<\/td>\n Publication Date<\/td>\n Number of Pages<\/td>\n<\/tr>\n \n BSI<\/b><\/a><\/td>\n 1997<\/td>\n 28<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":351321,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[667,2641],"product_tag":[],"class_list":{"0":"post-351313","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-35-100-01","7":"product_cat-bsi","9":"first","10":"instock","11":"sold-individually","12":"shipping-taxable","13":"purchasable","14":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/351313","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/351321"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=351313"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=351313"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=351313"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}