draft-ietf-beep-framework-07.txt   draft-ietf-beep-framework-08.txt 
Network Working Group M.T. Rose Network Working Group M.T. Rose
Internet-Draft Invisible Worlds, Inc. Internet-Draft Invisible Worlds, Inc.
Expires: April 30, 2001 October 30, 2000 Expires: May 14, 2001 November 13, 2000
The Blocks Extensible Exchange Protocol Framework The Blocks Extensible Exchange Protocol Framework
draft-ietf-beep-framework-07 draft-ietf-beep-framework-08
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any 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 April 30, 2001. This Internet-Draft will expire on May 14, 2001.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract Abstract
This memo describes a generic application protocol framework for This memo describes a generic application protocol framework for
connection-oriented, asynchronous interactions. The framework connection-oriented, asynchronous interactions. The framework
permits simultaneous and independent exchanges within the context of permits simultaneous and independent exchanges within the context of
skipping to change at page 9, line 17 skipping to change at page 9, line 17
The frame header consists of a three-character keyword (one of: The frame header consists of a three-character keyword (one of:
"MSG", "RPY", "ERR", "ANS", or "NUL"), followed by zero or more "MSG", "RPY", "ERR", "ANS", or "NUL"), followed by zero or more
parameters. A single space character (decimal code 32, " ") parameters. A single space character (decimal code 32, " ")
separates each component. The header is terminated with a CRLF pair. separates each component. The header is terminated with a CRLF pair.
The channel number ("channel") must be a non-negative integer (in The channel number ("channel") must be a non-negative integer (in
the range 0..2147483647). the range 0..2147483647).
The message number ("msgno") must be a non-negative integer (in the The message number ("msgno") must be a non-negative integer (in the
range 0..2147483647) and have a different value than all other "MSG" range 0..2147483647) and have a different value than all other "MSG"
messages for which a reply has not been completely received. messages on the same channel for which a reply has not been
completely received.
The continuation indicator ("more", one of: decimal code 42, "*", or The continuation indicator ("more", one of: decimal code 42, "*", or
decimal code 46, ".") specifies whether this is the final frame of decimal code 46, ".") specifies whether this is the final frame of
the message: the message:
intermediate ("*"): at least one other frame follows for the intermediate ("*"): at least one other frame follows for the
message; or, message; or,
complete ("."): this frame completes the message. complete ("."): this frame completes the message.
skipping to change at page 42, line 45 skipping to change at page 42, line 45
Contact Information: specify the postal and electronic contact Contact Information: specify the postal and electronic contact
information for the author of the profile. information for the author of the profile.
5.2 Feature Registration Template 5.2 Feature Registration Template
When a feature for the channel management profile is registered, the When a feature for the channel management profile is registered, the
following information is supplied: following information is supplied:
Feature Identification: specify a string that identifies this Feature Identification: specify a string that identifies this
feature. Unless the feature is registered with the IANA, the feature. Unless the feature is registered with the IANA, the
feature's identification MUST start with "x-". feature's identification must start with "x-".
Feature Semantics: specify the semantics of the feature. Feature Semantics: specify the semantics of the feature.
Contact Information: specify the postal and electronic contact Contact Information: specify the postal and electronic contact
information for the author of the feature. information for the author of the feature.
6. Initial Registrations 6. Initial Registrations
6.1 Registration: BEEP Channel Management 6.1 Registration: BEEP Channel Management
skipping to change at page 55, line 12 skipping to change at page 55, line 12
Crocker provided helpful suggestions on the nature of segmentation Crocker provided helpful suggestions on the nature of segmentation
in the framing mechanism. in the framing mechanism.
Appendix B. IANA Considerations Appendix B. IANA Considerations
The IANA registers "beep" as a GSSAPI[14] service name, as specified The IANA registers "beep" as a GSSAPI[14] service name, as specified
in Section 4.1. in Section 4.1.
The IANA maintains a list of: The IANA maintains a list of:
o BEEP profiles, c.f., Section 5.1; and, o standards-track BEEP profiles, c.f., Section 5.1; and,
o features for the channel management profile, c.f., Section 5.2. o standards-track features for the channel management profile,
c.f., Section 5.2.
For each list, the IESG is responsible for assigning a designated
expert to review the specification prior to the IANA making the
assignment. As a courtesy to developers of non-standards track BEEP
profiles and channel management features, the mailing list
bxxpwg@invisible.net may be used to solicit commentary.
The IANA makes the registrations specified in Section 6.2 and The IANA makes the registrations specified in Section 6.2 and
Section 6.3. It is recommended that the IANA register these profiles Section 6.3. It is recommended that the IANA register these profiles
using the IANA as a URI-prefix, and populate those URIs with the using the IANA as a URI-prefix, and populate those URIs with the
respective profile registrations. respective profile registrations.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
 End of changes. 7 change blocks. 
7 lines changed or deleted 15 lines changed or added

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