draft-ietf-beep-framework-04.txt   draft-ietf-beep-framework-05.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 10, 2001 October 10, 2000 Expires: April 14, 2001 October 14, 2000
The Blocks Extensible Exchange Protocol Framework The Blocks Extensible Exchange Protocol Framework
draft-ietf-beep-framework-04 draft-ietf-beep-framework-05
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 10, 2001. This Internet-Draft will expire on April 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 34, line 16 skipping to change at page 34, line 16
C: MSG 0 1 . 40 173 C: MSG 0 1 . 40 173
C: Content-Type: text/xml C: Content-Type: text/xml
C: C:
C: <start number='1'> C: <start number='1'>
C: <profile uri='http://xml.resource.org/profiles/TLS'> C: <profile uri='http://xml.resource.org/profiles/TLS'>
C: <![CDATA[<ready version="oops" />]]> C: <![CDATA[<ready version="oops" />]]>
C: </profile> C: </profile>
C: </start> C: </start>
C: END C: END
S: RPY 0 1 . 110 181 S: RPY 0 1 . 110 193
S: Content-Type: text/xml S: Content-Type: text/xml
S: S:
S: <profile uri='http://xml.resource.org/profiles/TLS'> S: <profile uri='http://xml.resource.org/profiles/TLS'>
S: <error code='501'>version attribute S: <![CDATA[<error code='501'>version attribute
S: poorly formed in &lt;ready&gt; element</error> S: poorly formed in &lt;ready&gt; element</error>]]>
S: </profile> S: </profile>
S: END S: END
In this case, a positive reply is sent (as channel creation In this case, a positive reply is sent (as channel creation
succeeded), but the encapsulated response contains an indication as succeeded), but the encapsulated response contains an indication as
to why the operation failed. to why the operation failed.
3.1.2 Message Syntax 3.1.2 Message Syntax
Section 7.2 defines the messages that are used in the TLS transport Section 7.2 defines the messages that are used in the TLS transport
skipping to change at page 39, line 18 skipping to change at page 39, line 18
C: MSG 0 1 . 40 183 C: MSG 0 1 . 40 183
C: Content-Type: text/xml C: Content-Type: text/xml
C: C:
C: <start number='1'> C: <start number='1'>
C: <profile uri='http://xml.resource.org/profiles/sasl/OTP'> C: <profile uri='http://xml.resource.org/profiles/sasl/OTP'>
C: <![CDATA[<blob>AGJsb2NrbWFzdGVy</blob>]]> C: <![CDATA[<blob>AGJsb2NrbWFzdGVy</blob>]]>
C: </profile> C: </profile>
C: </start> C: </start>
C: END C: END
S: RPY 0 1 . 252 166 S: RPY 0 1 . 252 178
S: Content-Type: text/xml S: Content-Type: text/xml
S: S:
S: <profile uri='http://xml.resource.org/profiles/sasl/OTP'> S: <profile uri='http://xml.resource.org/profiles/sasl/OTP'>
S: <error code='534'>authentication mechanism is S: <![CDATA[<error code='534'>authentication mechanism is
S: too weak</error> S: too weak</error>]]>
S: </profile> S: </profile>
S: END S: END
In this case, a positive reply is sent (as channel creation In this case, a positive reply is sent (as channel creation
succeeded), but the encapsulated response contains an indication as succeeded), but the encapsulated response contains an indication as
to why the operation failed. to why the operation failed.
Otherwise, the server sends a challenge (or signifies success), e.g., Otherwise, the server sends a challenge (or signifies success), e.g.,
C: MSG 0 1 . 40 183 C: MSG 0 1 . 40 183
skipping to change at page 41, line 15 skipping to change at page 41, line 15
may be exchanged unidirectionally during channel creation, e.g., may be exchanged unidirectionally during channel creation, e.g.,
C: MSG 0 1 . 40 133 C: MSG 0 1 . 40 133
C: Content-Type: text/xml C: Content-Type: text/xml
C: C:
C: <start number='1'> C: <start number='1'>
C: <profile C: <profile
C: uri='http://xml.resource.org/profiles/sasl/CRAM-MD5' /> C: uri='http://xml.resource.org/profiles/sasl/CRAM-MD5' />
C: </start> C: </start>
C: END C: END
S: RPY 0 1 . 252 173 S: RPY 0 1 . 252 185
S: Content-Type: text/xml S: Content-Type: text/xml
S: S:
S: <profile uri='http://xml.resource.org/profiles/sasl/CRAM-MD5'> S: <profile uri='http://xml.resource.org/profiles/sasl/CRAM-MD5'>
S: <blob>PDE4OTYuNjk3MTcwOTUyQHBvc3RvZmZpY2UucmVzdG9uLm1jaS5uZXQ+ S: <![CDATA[<blob>PDE4OTYuNjk3MTcwOTUyQHBvc3RvZmZpY2UucmVzdG9uLm1
</blob> jaS5uZXQ+</blob>]]>
S: </profile> S: </profile>
S: END S: END
Note that this example implies that the "blob" element in the Note that this example implies that the "blob" element in the
server's reply appears on two lines -- this is an artifact of the server's reply appears on two lines -- this is an artifact of the
presentation; in fact, only one line is used. presentation; in fact, only one line is used.
4.1.2 Message Syntax 4.1.2 Message Syntax
Section 7.3 defines the messages that are used for each profile in Section 7.3 defines the messages that are used for each profile in
 End of changes. 9 change blocks. 
12 lines changed or deleted 12 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/