The Experts below are selected from a list of 3699 Experts worldwide ranked by ideXlab platform

Christopher Dearlove - One of the best experts on this subject based on the ideXlab platform.

  • rules for designing protocols using the generalized packet Message Format from rfc 5444
    RFC, 2017
    Co-Authors: Ulrich Herberg, Thomas Clausen, Henning Rogge, Christopher Dearlove
    Abstract:

    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. In particular, the mandatory rules prohibit a number of uses that have been suggested in various proposals and that would have led to interoperability problems, to the impediment of protocol extension development, and/or to an inability to use optional generic parsers.

  • Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444
    2017
    Co-Authors: Ulrich Herberg, Thomas Clausen, Henning Rogge, Christopher Dearlove
    Abstract:

    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. In particular, the mandatory rules prohibit a number of uses that have been suggested in various proposals and that would have led to interoperability problems, to the impediment of protocol extension development, and/or to an inability to use optional generic parsers.

  • tlv naming in the mobile ad hoc network manet generalized packet Message Format
    RFC, 2015
    Co-Authors: Thomas Clausen, Christopher Dearlove
    Abstract:

    This document reorganizes the naming of already-allocated TLV (type- length-value) types and type extensions in the "Mobile Ad hoc NETwork (MANET) Parameters" registries defined by RFC 5444 to use names appropriately. It has no consequences in terms of any protocol implementation. This document also updates the Expert Review guidelines in RFC 5444, so as to establish a policy for consistent naming of future TLV type and type extension allocations. It makes no other changes to RFC 5444.

  • Rules For Designing Protocols Using the RFC 5444 Generalized Packet/ Message Format
    2015
    Co-Authors: Ulrich Herberg, Thomas Clausen, Henning Rogge, Christopher Dearlove
    Abstract:

    RFC 5444 specifies a generalized MANET packet/Message Format and describes an intended use to multiplex MANET routing protocol Messages that is mandated for use by RFC 5498. This document updates RFC 5444 by providing rules and recommendations for how the multiplexer operates and how protocols can use the packet/Message Format. In particular, the mandatory rules prohibit a number of uses of RFC 5444 that have been suggested in various proposals, and which would have led to interoperability problems, to the impediment of protocol extension development, and to an inability to use optional generic RFC 5444 parsers.

  • TLV Naming in the MANET Generalized Packet/Message Format
    2014
    Co-Authors: Thomas Clausen, Christopher Dearlove
    Abstract:

    TLVs (type-length-value structures) as defined by RFC5444 have both a type (one octet) and a type extension (one octet), together forming a full type (of two octets). RFC5444 sets up IANA registries for TLV types, specifying that an allocation of a TLV type entails creation of an IANA registry for the corresponding type extensions. In some cases, reserving all 256 type extensions for use for a common purpose for a given TLV is meaningful, and thus it makes sense to record a common name for such a TLV type (and all of its type extensions) in the corresponding IANA registries. An example of such is a LINK_METRIC TLV Type, with its type extensions reserved for use to be indicating the "kind" of metric expressed by the value of the TLV. In some other cases, there may not be 256 full types that share a common purpose and, as such, it is not meaningful to record a common name for all the type extensions for a TLV type in the corresponding IANA registries. Rather, it is appropriate to record an individual name per full type. This document reorganizes the naming of already allocated TLV types and type extensions in those registries to use names appropriately. It has no consequences in terms of any protocol implementation. This document also updates the Expert Review guidelines from RFC5444, so as to establish a policy for consistent naming of future TLV type and type extension allocations.

Thomas Clausen - One of the best experts on this subject based on the ideXlab platform.

  • rules for designing protocols using the generalized packet Message Format from rfc 5444
    RFC, 2017
    Co-Authors: Ulrich Herberg, Thomas Clausen, Henning Rogge, Christopher Dearlove
    Abstract:

    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. In particular, the mandatory rules prohibit a number of uses that have been suggested in various proposals and that would have led to interoperability problems, to the impediment of protocol extension development, and/or to an inability to use optional generic parsers.

  • Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444
    2017
    Co-Authors: Ulrich Herberg, Thomas Clausen, Henning Rogge, Christopher Dearlove
    Abstract:

    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. In particular, the mandatory rules prohibit a number of uses that have been suggested in various proposals and that would have led to interoperability problems, to the impediment of protocol extension development, and/or to an inability to use optional generic parsers.

  • tlv naming in the mobile ad hoc network manet generalized packet Message Format
    RFC, 2015
    Co-Authors: Thomas Clausen, Christopher Dearlove
    Abstract:

    This document reorganizes the naming of already-allocated TLV (type- length-value) types and type extensions in the "Mobile Ad hoc NETwork (MANET) Parameters" registries defined by RFC 5444 to use names appropriately. It has no consequences in terms of any protocol implementation. This document also updates the Expert Review guidelines in RFC 5444, so as to establish a policy for consistent naming of future TLV type and type extension allocations. It makes no other changes to RFC 5444.

  • Rules For Designing Protocols Using the RFC 5444 Generalized Packet/ Message Format
    2015
    Co-Authors: Ulrich Herberg, Thomas Clausen, Henning Rogge, Christopher Dearlove
    Abstract:

    RFC 5444 specifies a generalized MANET packet/Message Format and describes an intended use to multiplex MANET routing protocol Messages that is mandated for use by RFC 5498. This document updates RFC 5444 by providing rules and recommendations for how the multiplexer operates and how protocols can use the packet/Message Format. In particular, the mandatory rules prohibit a number of uses of RFC 5444 that have been suggested in various proposals, and which would have led to interoperability problems, to the impediment of protocol extension development, and to an inability to use optional generic RFC 5444 parsers.

  • TLV Naming in the MANET Generalized Packet/Message Format
    2014
    Co-Authors: Thomas Clausen, Christopher Dearlove
    Abstract:

    TLVs (type-length-value structures) as defined by RFC5444 have both a type (one octet) and a type extension (one octet), together forming a full type (of two octets). RFC5444 sets up IANA registries for TLV types, specifying that an allocation of a TLV type entails creation of an IANA registry for the corresponding type extensions. In some cases, reserving all 256 type extensions for use for a common purpose for a given TLV is meaningful, and thus it makes sense to record a common name for such a TLV type (and all of its type extensions) in the corresponding IANA registries. An example of such is a LINK_METRIC TLV Type, with its type extensions reserved for use to be indicating the "kind" of metric expressed by the value of the TLV. In some other cases, there may not be 256 full types that share a common purpose and, as such, it is not meaningful to record a common name for all the type extensions for a TLV type in the corresponding IANA registries. Rather, it is appropriate to record an individual name per full type. This document reorganizes the naming of already allocated TLV types and type extensions in those registries to use names appropriately. It has no consequences in terms of any protocol implementation. This document also updates the Expert Review guidelines from RFC5444, so as to establish a policy for consistent naming of future TLV type and type extension allocations.

Martin Maiers - One of the best experts on this subject based on the ideXlab platform.

  • a community standard xml Message Format for sequencing based typing data
    Tissue Antigens, 2007
    Co-Authors: Martin Maiers
    Abstract:

    An electronic messaging Format has been developed and is proposed as a community standard. This Format allows explicit representation of typing results for polymorphic immunogenetic gene systems such as killer cell immunoglobulin-like receptor and human leukocyte antigen. Primary data in the form of Sequence Specific Oligonucleotide (SSO)/Sequence Specific Primer (SSP) reactivities and sequencing-based typing sequences can be linked with nomenclature-based results allowing complete representation of the permanent inFormation.

  • A community standard XML Message Format for sequencing‐based typing data
    Tissue Antigens, 2007
    Co-Authors: Martin Maiers
    Abstract:

    An electronic messaging Format has been developed and is proposed as a community standard. This Format allows explicit representation of typing results for polymorphic immunogenetic gene systems such as killer cell immunoglobulin-like receptor and human leukocyte antigen. Primary data in the form of Sequence Specific Oligonucleotide (SSO)/Sequence Specific Primer (SSP) reactivities and sequencing-based typing sequences can be linked with nomenclature-based results allowing complete representation of the permanent inFormation.

Yongzheng Zhang - One of the best experts on this subject based on the ideXlab platform.

  • ICNP - A semantics aware approach to automated reverse engineering unknown protocols
    2012 20th IEEE International Conference on Network Protocols (ICNP), 2012
    Co-Authors: Yipeng Wang, Liyan Wang, Zhibin Zhang, M. Zubair Shafiq, Yongzheng Zhang
    Abstract:

    Extracting the protocol Message Format specifications of unknown applications from network traces is important for a variety of applications such as application protocol parsing, vulnerability discovery, and system integration. In this paper, we propose ProDecoder, a network trace based protocol Message Format inference system that exploits the semantics of protocol Messages without the executable code of application protocols. ProDecoder is based on the key insight that the n-grams of protocol traces exhibit highly skewed frequency distribution that can be leveraged for accurate protocol Message Format inference. In ProDecoder, we first discover the latent relationship among n-grams by first grouping protocol Messages with the same semantics and then inferring Message Formats by keyword based clustering and cluster sequence alignment. We implemented and evaluated ProDecoder to infer Message Format specifications of SMB (a binary protocol) and SMTP (a textual protocol). Our experimental results show that ProDecoder accurately parses and infers SMB protocol with 100% precision and recall. For SMTP, ProDecoder achieves approximately 95% precision and recall.

  • A semantics aware approach to automated reverse engineering unknown protocols
    2012 20th IEEE International Conference on Network Protocols (ICNP), 2012
    Co-Authors: Yipeng Wang, Zubair M. Shafiq, Liyan Wang, Zhibin Zhang, Yongzheng Zhang
    Abstract:

    Extracting the protocol Message Format specifications of unknown applications from network traces is important for a variety of applications such as application protocol parsing, vulnerability discovery, and system integration. In this paper, we propose ProDecoder, a network trace based protocol Message Format inference system that exploits the semantics of protocol Messages without the executable code of application protocols. ProDecoder is based on the key insight that the n-grams of protocol traces exhibit highly skewed frequency distribution that can be leveraged for accurate protocol Message Format inference. In ProDecoder, we first discover the latent relationship among n-grams by first grouping protocol Messages with the same semantics and then inferring Message Formats by keyword based clustering and cluster sequence alignment. We implemented and evaluated ProDecoder to infer Message Format specifications of SMB (a binary protocol) and SMTP (a textual protocol). Our experimental results show that ProDecoder accurately parses and infers SMB protocol with 100% precision and recall. For SMTP, ProDecoder achieves approximately 95% precision and recall.

Yipeng Wang - One of the best experts on this subject based on the ideXlab platform.

  • ICNP - A semantics aware approach to automated reverse engineering unknown protocols
    2012 20th IEEE International Conference on Network Protocols (ICNP), 2012
    Co-Authors: Yipeng Wang, Liyan Wang, Zhibin Zhang, M. Zubair Shafiq, Yongzheng Zhang
    Abstract:

    Extracting the protocol Message Format specifications of unknown applications from network traces is important for a variety of applications such as application protocol parsing, vulnerability discovery, and system integration. In this paper, we propose ProDecoder, a network trace based protocol Message Format inference system that exploits the semantics of protocol Messages without the executable code of application protocols. ProDecoder is based on the key insight that the n-grams of protocol traces exhibit highly skewed frequency distribution that can be leveraged for accurate protocol Message Format inference. In ProDecoder, we first discover the latent relationship among n-grams by first grouping protocol Messages with the same semantics and then inferring Message Formats by keyword based clustering and cluster sequence alignment. We implemented and evaluated ProDecoder to infer Message Format specifications of SMB (a binary protocol) and SMTP (a textual protocol). Our experimental results show that ProDecoder accurately parses and infers SMB protocol with 100% precision and recall. For SMTP, ProDecoder achieves approximately 95% precision and recall.

  • A semantics aware approach to automated reverse engineering unknown protocols
    2012 20th IEEE International Conference on Network Protocols (ICNP), 2012
    Co-Authors: Yipeng Wang, Zubair M. Shafiq, Liyan Wang, Zhibin Zhang, Yongzheng Zhang
    Abstract:

    Extracting the protocol Message Format specifications of unknown applications from network traces is important for a variety of applications such as application protocol parsing, vulnerability discovery, and system integration. In this paper, we propose ProDecoder, a network trace based protocol Message Format inference system that exploits the semantics of protocol Messages without the executable code of application protocols. ProDecoder is based on the key insight that the n-grams of protocol traces exhibit highly skewed frequency distribution that can be leveraged for accurate protocol Message Format inference. In ProDecoder, we first discover the latent relationship among n-grams by first grouping protocol Messages with the same semantics and then inferring Message Formats by keyword based clustering and cluster sequence alignment. We implemented and evaluated ProDecoder to infer Message Format specifications of SMB (a binary protocol) and SMTP (a textual protocol). Our experimental results show that ProDecoder accurately parses and infers SMB protocol with 100% precision and recall. For SMTP, ProDecoder achieves approximately 95% precision and recall.