draft-ietf-apex-party-00.txt   draft-ietf-apex-party-01.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Expires: October 30, 2001 J. Kint Expires: October 30, 2001 J. Kint
Invisible Worlds, Inc. Invisible Worlds, Inc.
G. Klyne G. Klyne
Baltimore Technologies Baltimore Technologies
D. New D. New
S. Pead S. Pead
M. Rose M. Rose
Invisible Worlds, Inc. Invisible Worlds, Inc.
The APEX Option Party Pack, Part Deux! The APEX Option Party Pack, Part Deux!
draft-ietf-apex-party-00 draft-ietf-apex-party-01
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 Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 25 skipping to change at page 2, line 25
4. Initial Registrations . . . . . . . . . . . . . . . . . . . 16 4. Initial Registrations . . . . . . . . . . . . . . . . . . . 16
4.1 Registration: The attachOverride Option . . . . . . . . . . 16 4.1 Registration: The attachOverride Option . . . . . . . . . . 16
4.2 Registration: The dataTiming Option . . . . . . . . . . . . 16 4.2 Registration: The dataTiming Option . . . . . . . . . . . . 16
4.3 Registration: The hold4Endpoint Option . . . . . . . . . . . 16 4.3 Registration: The hold4Endpoint Option . . . . . . . . . . . 16
5. The APEX Party Pack DTD . . . . . . . . . . . . . . . . . . 17 5. The APEX Party Pack DTD . . . . . . . . . . . . . . . . . . 17
6. Security Considerations . . . . . . . . . . . . . . . . . . 18 6. Security Considerations . . . . . . . . . . . . . . . . . . 18
References . . . . . . . . . . . . . . . . . . . . . . . . . 19 References . . . . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 19
A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
B. IANA Considerations . . . . . . . . . . . . . . . . . . . . 22 B. IANA Considerations . . . . . . . . . . . . . . . . . . . . 22
Full Copyright Statement . . . . . . . . . . . . . . . . . . 23 C. Changes from draft-ietf-apex-party-00 . . . . . . . . . . . 23
Full Copyright Statement . . . . . . . . . . . . . . . . . . 24
1. The attachOverride Option 1. The attachOverride Option
Section 4.1 contains the APEX option registration for the Section 4.1 contains the APEX option registration for the
"attachOverride" option. "attachOverride" option.
The default behavior of the APEX relaying mesh, in the absence of The default behavior of the APEX relaying mesh, in the absence of
processing options, is to allow at most one application to attach as processing options, is to allow at most one application to attach as
a particular endpoint, on a "first come, first served" basis. The a particular endpoint, on a "first come, first served" basis. The
"attachOverride" option provides gives preference to the current "attachOverride" option provides gives preference to the current
application trying to attach. application trying to attach.
If this option is present in the "attach" operation (c.f., Section If this option is present in the "attach" operation (c.f., Section
4.4.1 of [1]) and if any application is already attached as the 4.4.1 of [1]) and if any application is already attached as the
specified endpoint, that endpoint has its attachment terminated specified endpoint, that endpoint has its attachment terminated
(c.f., Section 4.4.3 of [1]) concurrently with processing of that (c.f., Section 4.4.3 of [1]) concurrently with processing of that
"attach" operation. "attach" operation. The "code" attribute of the resulting
"terminate" operation is set to 556.
Note that any data being expected by the previously-attached Note that any data being expected by the previously-attached
application may instead be delivered to the last application to application may instead be delivered to the last application to
successfully attach. Accordingly, applications should take care to successfully attach. Accordingly, applications should take care to
properly deal with incoming data having unrecognized transaction- properly deal with incoming data having unrecognized transaction-
identifiers (c.f., Section 6.1.1 of [1]). identifiers (c.f., Section 6.1.1 of [1]).
This option provides for a new attachment to automatically terminate This option provides for a new attachment to automatically terminate
any existing attachment for the same endpoint. For example, This any existing attachment for the same endpoint. For example, This
might be helpful when a new attachment is required from a different might be helpful when a new attachment is required from a different
skipping to change at page 4, line 18 skipping to change at page 4, line 19
| | <-- terminate -- | relay | -- ok ---------> | #2 | | | <-- terminate -- | relay | -- ok ---------> | #2 |
| appl. | | | +-------+ | appl. | | | +-------+
| #1 | -- ok ---------> | | | #1 | -- ok ---------> | |
+-------+ +-------+ +-------+ +-------+
C: <attach endpoint='fred@example.com' transID='2'> C: <attach endpoint='fred@example.com' transID='2'>
<option internal='attachOverride' transID='3' /> <option internal='attachOverride' transID='3' />
</attach> </attach>
S: <ok /> S: <ok />
C: <terminate transID='1' /> C: <terminate transID='1' code='556'>overriden</terminate>
S: <ok /> S: <ok />
2. The dataTiming Option 2. The dataTiming Option
Section 4.2 contains the APEX option registration for the Section 4.2 contains the APEX option registration for the
"dataTiming" option. This option contains a "dataTiming" element "dataTiming" option. This option contains a "dataTiming" element
(c.f., Section 5). (c.f., Section 5).
The default behavior of the APEX relaying mesh is "immediate, best The default behavior of the APEX relaying mesh is "immediate, best
effort" and expects that all relays and endpoints are able to process effort" and expects that all relays and endpoints are able to process
skipping to change at page 19, line 8 skipping to change at page 19, line 8
o The hold4Endpoint option (Section 3) may be used to facilitate o The hold4Endpoint option (Section 3) may be used to facilitate
denial-of-service attacks. Accordingly, an administrator may wish denial-of-service attacks. Accordingly, an administrator may wish
to impose administrative limits on this attribute (e.g., always to impose administrative limits on this attribute (e.g., always
require that the "dataTiming" option also be present with a short- require that the "dataTiming" option also be present with a short-
lived "noLaterThan" attribute). lived "noLaterThan" attribute).
References References
[1] Rose, M., Klyne, G. and D. Crocker, "The Application Exchange [1] Rose, M., Klyne, G. and D. Crocker, "The Application Exchange
Core", draft-ietf-apex-core-02 (work in progress), May 2001. Core", draft-ietf-apex-core-03 (work in progress), May 2001.
[2] Newman, D., "Deliver By SMTP Service Extension", RFC 2852, June [2] Newman, D., "Deliver By SMTP Service Extension", RFC 2852, June
2000. 2000.
Authors' Addresses Authors' Addresses
Eric Dixon Eric Dixon
Invisible Worlds, Inc. Invisible Worlds, Inc.
131 Stony Circle 131 Stony Circle
Suite 500 Suite 500
skipping to change at page 21, line 7 skipping to change at page 21, line 7
Suite 500 Suite 500
Santa Rosa, CA 95401 Santa Rosa, CA 95401
US US
Phone: +1 707 578 2350 Phone: +1 707 578 2350
EMail: mrose@invisible.net EMail: mrose@invisible.net
URI: http://invisible.net/ URI: http://invisible.net/
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors gratefully acknowledge the contributions of Chris Newman; The authors gratefully acknowledge the contributions of Chris Newman
further, the dataTiming option is similar in function to "Deliver By" and Bob Wyman. Further, the dataTiming option is similar in function
SMTP service extension defined by Dan Newman in [2]. to "Deliver By" SMTP service extension defined by Dan Newman in [2].
Appendix B. IANA Considerations Appendix B. IANA Considerations
The IANA makes the registrations specified in Section 4. The IANA makes the registrations specified in Section 4.
Appendix C. Changes from draft-ietf-apex-party-00
o When terminating an association due to processing the
"attachOverride" option, the "code" attribute of the terminate
operation must be supplied.
o A small number of typos were corrected.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
 End of changes. 7 change blocks. 
8 lines changed or deleted 18 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/