TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format

Clausen, Thomas; Dearlove, Christopher

doi:10.17487/rfc7631

Cited by 4 publications

(5 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, it is also optionally possible to skip/omit encoding or encryption of the capsules at all. It is worth mentioning that the whole capsule can be enveloped in a Type-LengthValue (TLV) element as an optional information in order to be transparent to the involved protocols across the stack [15]. Also, there is no fixed space/size reserved for the segments in the capsule structure in order to save space when a segment is constant compared to previous communicated instances of an extended resource ID.…”

Section: Figmentioning

confidence: 99%

Transparent Clouds: An Enhancement to Abstraction

Moghaddam

Lemieux

Cheriet

2017

2017 IEEE 10th International Conference on Cloud Computing (CLOUD)

View full text Add to dashboard Cite

Abstract-With the introduction of various hardware/software technologies such as Cloud Technologies or Virtualization technologies, there has been a great potential to reuse ICT artifacts thanks to Abstraction and also Exchangeability features achieved via these technologies. These technologies also provide various advantages with respect to sustainability including resource consumption reduction (in the use phase only or in the whole life cycle). However, there is an additional but untapped potential associated with the anonymization of resources introduced by both abstraction and exchangeability features. By realizing on this potential, we can improve cloud solutions and reduce their by-product opacity, which usually prevents leveraging on the specialized but tweakable (i.e., nonessential modifications without changing the main function) features of components that are captured in the component models. This is especially a challenge in the case heterogeneous/disaggregated infrastructure where developing models to cover everything is practically impossible. In this work, by leveraging on the concept of pathways, we develop a few mechanisms that enable transparency and therefore tweakability of features even in the presence of abstraction and heterogeneity. In particular, the layered-stack approach to system decomposition is considered because of its role in both software defined networking (SDN) and Network Function Virtualization (NFV) system decompositions. For a concrete example, the case of dynamic frequency scaling of processors is considered and it is shown that the associated consumption could be considerably reduced without requiring additional changes to the middle components.

show abstract

Section: Figmentioning

confidence: 99%

Transparent Clouds: An Enhancement to Abstraction

Moghaddam

Lemieux

Cheriet

2017

2017 IEEE 10th International Conference on Cloud Computing (CLOUD)

View full text Add to dashboard Cite

show abstract

“…Since the publication of [RFC5444] in 2009, several RFCs have been published, including [RFC5497], [RFC6130], [RFC6621], [RFC7181], [RFC7182], [RFC7183], [RFC7188], [RFC7631], and [RFC7722], that use the format of [RFC5444]. The ITU-T recommendation [G9903] also uses the format of [RFC5444] for encoding some of its control signals.…”

Section: History and Purposementioning

confidence: 99%

“…A protocol defining new TLVs MUST respect the naming and organizational rules in [RFC7631]. It SHOULD follow the guidance in [RFC7188], see Section 6.3.…”

Section: Tlvsmentioning

confidence: 99%

Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444

Herberg¹,

Clausen²,

Rogge³

et al. 2017

Self Cite

View full text Add to dashboard Cite

RFC 5444 specifies a generalized Mobile Ad Hoc Network (MANET) packet/message format and describes an intended use for multiplexed MANET routing protocol messages; this use is mandated by RFC 5498 when using the MANET port or protocol number that it specifies. This document updates RFC 5444 by providing rules and recommendations for how the multiplexer operates and how protocols can use the packet/message format.

show abstract

“…For the registry where an Expert Review is required, the designated expert SHOULD take the same general recommendations into consideration as are specified by [RFC5444] and [RFC7631].…”

Section: Expert Review: Evaluation Guidelinesmentioning

confidence: 99%

“…This specification modifies the Message TLV Type 7, replacing Table 4 of [RFC7631] by Table 2, changing the description of the Type Extension MPR_WILLING, and adding the Type Extension TLV_TYPES. Each of these TLVs MUST NOT be included more than once in a Message TLV Block.…”

Section: Message Tlv Typesmentioning

confidence: 99%