< draft-irtf-dtnrg-sdnv-00.txt   draft-irtf-dtnrg-sdnv-01.txt >
Network Working Group W. Eddy Network Working Group W. Eddy
Internet-Draft Verizon Internet-Draft Verizon
Intended status: Informational September 17, 2007 Intended status: Informational January 9, 2009
Expires: March 20, 2008 Expires: July 13, 2009
Using Self-Delimiting Numeric Values in Protocols Using Self-Delimiting Numeric Values in Protocols
draft-irtf-dtnrg-sdnv-00 draft-irtf-dtnrg-sdnv-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 20, 2008. This Internet-Draft will expire on July 13, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Abstract Abstract
Self-Delimiting Numeric Values (SDNVs) have recently been introduced Self-Delimiting Numeric Values (SDNVs) have recently been introduced
as a field type within proposed Delay-Tolerant Networking protocols. as a field type within proposed Delay-Tolerant Networking protocols.
The basic goal of an SDNV is to hold a non-negative integer value of The basic goal of an SDNV is to hold a non-negative integer value of
arbitrary magnitude, without consuming much more space than arbitrary magnitude, without consuming much more space than
necessary. The primary motivation is to conserve the bits sent necessary. The primary motivation is to conserve the bits sent
across low-capacity or energy-intensive links typical of NASA deep- across low-capacity or energy-intensive links typical of NASA deep-
space missions, with a secondary goal of allowing the protocol to space missions, with a secondary goal of allowing the protocol to
skipping to change at page 2, line 38 skipping to change at page 3, line 4
3. Basic Algorithms . . . . . . . . . . . . . . . . . . . . . . . 8 3. Basic Algorithms . . . . . . . . . . . . . . . . . . . . . . . 8
3.1. Encoding Algorithm . . . . . . . . . . . . . . . . . . . . 8 3.1. Encoding Algorithm . . . . . . . . . . . . . . . . . . . . 8
3.2. Decoding Algorithm . . . . . . . . . . . . . . . . . . . . 8 3.2. Decoding Algorithm . . . . . . . . . . . . . . . . . . . . 8
4. Comparison to Alternatives . . . . . . . . . . . . . . . . . . 10 4. Comparison to Alternatives . . . . . . . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
8. Informative References . . . . . . . . . . . . . . . . . . . . 16 8. Informative References . . . . . . . . . . . . . . . . . . . . 16
Appendix A. SNDV Python Source Code . . . . . . . . . . . . . . . 18 Appendix A. SNDV Python Source Code . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20
Intellectual Property and Copyright Statements . . . . . . . . . . 21
1. Introduction 1. Introduction
This section begins by describing a common problem encountered in This section begins by describing a common problem encountered in
network protocol engineering. It then provides some background on network protocol engineering. It then provides some background on
the Self-Delimiting Numeric Values (SDNVs) proposed for use in Delay- the Self-Delimiting Numeric Values (SDNVs) proposed for use in Delay-
Tolerant Networking (DTN) protocols, and motivates their potential Tolerant Networking (DTN) protocols, and motivates their potential
applicability in other networking protocols. The DTN Research Group applicability in other networking protocols. The DTN Research Group
(DTNRG) within the Internet Research Task Force was created SDNVs to (DTNRG) within the Internet Research Task Force was created SDNVs to
meet the challenges it attempts to solve, and it has been noted that meet the challenges it attempts to solve, and it has been noted that
skipping to change at page 21, line 4 skipping to change at line 618
Author's Address Author's Address
Wesley M. Eddy Wesley M. Eddy
Verizon Federal Network Systems Verizon Federal Network Systems
NASA Glenn Research Center NASA Glenn Research Center
21000 Brookpark Rd, MS 54-5 21000 Brookpark Rd, MS 54-5
Cleveland, OH 44135 Cleveland, OH 44135
Phone: 216-433-6682 Phone: 216-433-6682
Email: weddy@grc.nasa.gov Email: weddy@grc.nasa.gov
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 7 change blocks. 
10 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/