ACM Home Page
Please provide us with feedback. Feedback
Packet types: abstract specification of network protocol messages
Full text PdfPdf (435 KB)
Source Applications, Technologies, Architectures, and Protocols for Computer Communication archive
Proceedings of the conference on Applications, Technologies, Architectures, and Protocols for Computer Communication table of contents
Stockholm, Sweden
Pages: 321 - 333  
Year of Publication: 2000
ISBN:1-58113-223-9
Also published in ...
Authors
Peter J. McCann  Bell Laboratories, 263 Shuman Blvd., Naperville, IL
Satish Chandra  Bell Laboratories, 263 Shuman Blvd., Naperville, IL
Sponsor
SIGCOMM: ACM Special Interest Group on Data Communication
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 7,   Downloads (12 Months): 80,   Citation Count: 13
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/347059.347563
What is a DOI?

ABSTRACT

In writing networking code, one is often faced with the task of interpreting a raw buffer according to a standardized packet format. This is needed, for example, when monitoring network traffic for specific kinds of packets, or when unmarshaling an incoming packet for protocol processing. In such cases, a programmer typically writes C code that understands the grammar of a packet and that also performs any necessary byte-order and alignment adjustments. Because of the complexity of certain protocol formats, and because of the low-level of programming involved, writing such code is usually a cumbersome and error-prone process. Furthermore, code written in this style loses the domain-specific information, viz. the packet format, in its details, making it difficult to maintain.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
Mary L. Bailey, Burra Gopal, Michael A. Pagels, Larry L. Peterson, and Prasenjit Sarkar. PathFinder: A patternbased packet classifier. In Proceedings of the First Symposium on Operating Systems Design and Implementation. USENIX Association, November 1994.
 
3
Anindya Basu, Mark Hayden, Greg Morrisett, and Thorsten von Eicken. A language-based approach to protocol construction. In Proceedings of the ACM SIGPLAN Workshop on Domain Specic Languages (WDSL), Paris, France, January 1997.
4
 
5
Gerard Berry and Georges Gonthier. The ESTEREL synchronous programming language: Design, semantics, implementation. Technical Report 842, Ecole Nationale Superieure des Mines de Paris, 1988.
6
 
7
 
8
CCITT. Recommendation X.208: Specication of Abstract Syntax Notation One (ASN.1), 1988.
9
10
 
11
 
12
International Telecommunication Union. Recommendation Q.931 - ISDN user-network interface layer 3 specication for basic call control, May 1998.
 
13
Mahesh Jayaram and Ron K. Cytron. Efficient demultiplexing of network packets by automatic parsing. In Proceedings of the Workshop on Compiler Support for System Software (WCSSS), 1996.
14
15
 
16
Steven McCanne and Van Jacobsen. The BSD packet lter: A newarchitecture for user-level packet capture. In 1993 Winter USENIX, pages 259-269, January 1993.
17
 
18
Michael Mouly. CSN.1 Specication, Version 2. Cell & Sys, 1998.
 
19
Object Management Group. CORBA/IIOP 2.2 Specication, 1998.
20
 
21
J. Postel. RFC 791: Internet Protocol, September 1981. Obsoletes RFC0760. See also STD0005. Status: STANDARD.
 
22
W. Simpson. RFC 1662: PPP in HDLC-like framing, July 1994. See also STD0051 . Obsoletes RFC1549 . Status: STANDARD.
 
23
R. Srinivasan. RFC 1832: XDR: External data representation standard, August 1995. Status: DRAFT STANDARD.
 
24
Masanobu Yuhara, Brian N. Bershad, Chris Maeda, and J. Eliot B. Moss. Efficient packet demultiplexing for multiple endpoints and large messages. In Proceedings of the 1994 Winter USENIX Conference, pages 153-165, January 1994.

CITED BY  13

Collaborative Colleagues:
Peter J. McCann: colleagues
Satish Chandra: colleagues