draft-ietf-apex-party-03.txt   draft-ietf-apex-party-04.txt 
Network Working Group E. Dixon Network Working Group E. Dixon
Internet-Draft H. Franklin Internet-Draft H. Franklin
Expires: February 12, 2002 J. Kint Expires: April 12, 2002 J. Kint
Invisible Worlds, Inc. Invisible Worlds, Inc.
G. Klyne G. Klyne
Baltimore Technologies MIMEsweeper Group
D. New D. New
S. Pead S. Pead
M. Rose
Invisible Worlds, Inc. Invisible Worlds, Inc.
August 14, 2001 M. Rose
Dover Beach Consulting, Inc.
M. Schwartz
NetTopBox, Inc.
October 12, 2001
The APEX Option Party Pack, Part Deux! The APEX Option Party Pack, Part Deux!
draft-ietf-apex-party-03 draft-ietf-apex-party-04
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.
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://
http://www.ietf.org/ietf/1id-abstracts.txt. 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 February 12, 2002. This Internet-Draft will expire on April 12, 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract Abstract
APEX, at its core, provides a best-effort application-layer datagram APEX, at its core, provides a best-effort application-layer datagram
service. Options are used to alter the semantics of the core service. Options are used to alter the semantics of the core
service. This memo defines various options to change the default service. This memo defines various options to change the default
behavior of APEX's "relaying mesh". behavior of APEX's "relaying mesh".
Table of Contents Table of Contents
1. The attachOverride Option . . . . . . . . . . . . . . . . . 3 1. The attachOverride Option . . . . . . . . . . . . . . . . . 3
2. The dataTiming Option . . . . . . . . . . . . . . . . . . . 5 2. The dataTiming Option . . . . . . . . . . . . . . . . . . . 5
2.1 Upper-Bounds on Delivery . . . . . . . . . . . . . . . . . . 6 2.1 Upper-Bounds on Delivery . . . . . . . . . . . . . . . . . . 6
skipping to change at page 2, line 15 skipping to change at page 2, line 19
Table of Contents Table of Contents
1. The attachOverride Option . . . . . . . . . . . . . . . . . 3 1. The attachOverride Option . . . . . . . . . . . . . . . . . 3
2. The dataTiming Option . . . . . . . . . . . . . . . . . . . 5 2. The dataTiming Option . . . . . . . . . . . . . . . . . . . 5
2.1 Upper-Bounds on Delivery . . . . . . . . . . . . . . . . . . 6 2.1 Upper-Bounds on Delivery . . . . . . . . . . . . . . . . . . 6
2.1.1 Final Hop Report . . . . . . . . . . . . . . . . . . . . . . 7 2.1.1 Final Hop Report . . . . . . . . . . . . . . . . . . . . . . 7
2.1.2 Timing Error Report . . . . . . . . . . . . . . . . . . . . 9 2.1.2 Timing Error Report . . . . . . . . . . . . . . . . . . . . 9
2.2 Reporting on Delayed Delivery . . . . . . . . . . . . . . . 11 2.2 Reporting on Delayed Delivery . . . . . . . . . . . . . . . 11
2.2.1 Transient Timing Report . . . . . . . . . . . . . . . . . . 12 2.2.1 Transient Timing Report . . . . . . . . . . . . . . . . . . 12
3. The hold4Endpoint Option . . . . . . . . . . . . . . . . . . 14 3. The hold4Endpoint Option . . . . . . . . . . . . . . . . . . 14
4. Initial Registrations . . . . . . . . . . . . . . . . . . . 16 4. The dataHopping Option . . . . . . . . . . . . . . . . . . . 16
4.1 Registration: The attachOverride Option . . . . . . . . . . 16 5. Initial Registrations . . . . . . . . . . . . . . . . . . . 19
4.2 Registration: The dataTiming Option . . . . . . . . . . . . 16 5.1 Registration: The attachOverride Option . . . . . . . . . . 19
4.3 Registration: The hold4Endpoint Option . . . . . . . . . . . 16 5.2 Registration: The dataTiming Option . . . . . . . . . . . . 19
5. The APEX Party Pack DTD . . . . . . . . . . . . . . . . . . 17 5.3 Registration: The hold4Endpoint Option . . . . . . . . . . . 19
6. Security Considerations . . . . . . . . . . . . . . . . . . 18 5.4 Registration: The dataHopping Option . . . . . . . . . . . . 20
References . . . . . . . . . . . . . . . . . . . . . . . . . 19 6. The APEX Party Pack DTD . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 19 7. Security Considerations . . . . . . . . . . . . . . . . . . 22
A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 References . . . . . . . . . . . . . . . . . . . . . . . . . 23
B. IANA Considerations . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 23
C. Revision History . . . . . . . . . . . . . . . . . . . . . . 23 A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
C.1 Changes from draft-ietf-apex-party-02 . . . . . . . . . . . 23 B. IANA Considerations . . . . . . . . . . . . . . . . . . . . 26
C.2 Changes from draft-ietf-apex-party-01 . . . . . . . . . . . 23 C. Revision History . . . . . . . . . . . . . . . . . . . . . . 27
C.3 Changes from draft-ietf-apex-party-00 . . . . . . . . . . . 23 C.1 Changes from draft-ietf-apex-party-03 . . . . . . . . . . . 27
Full Copyright Statement . . . . . . . . . . . . . . . . . . 24 C.2 Changes from draft-ietf-apex-party-02 . . . . . . . . . . . 27
C.3 Changes from draft-ietf-apex-party-01 . . . . . . . . . . . 27
C.4 Changes from draft-ietf-apex-party-00 . . . . . . . . . . . 27
Full Copyright Statement . . . . . . . . . . . . . . . . . . 28
1. The attachOverride Option 1. The attachOverride Option
Section 4.1 contains the APEX option registration for the Section 5.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
skipping to change at page 5, line 7 skipping to change at page 5, line 7
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' code='556'>overriden</terminate> 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 5.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 6).
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
and transfer data without delay -- in the absence of processing and transfer data without delay -- in the absence of processing
options, if a relay is unavailable then data is silently dropped. options, if a relay is unavailable then data is silently dropped.
The "dataTiming" option provides for controlled queuing delays in The "dataTiming" option provides for controlled queuing delays in
processing, whilst providing reasonable deterministic behavior for processing, whilst providing reasonable deterministic behavior for
the originator. the originator.
There are two types of delay addressed by the "dataTiming" option: There are two types of delay addressed by the "dataTiming" option:
skipping to change at page 12, line 8 skipping to change at page 12, line 8
If the relay does not receive an "ok" element from the recipient If the relay does not receive an "ok" element from the recipient
endpoint within the number of milli-seconds indicated by the value endpoint within the number of milli-seconds indicated by the value
of the "reportAfter" attribute, then its value is set to zero and of the "reportAfter" attribute, then its value is set to zero and
the APEX report service is invoked to send a transient timing the APEX report service is invoked to send a transient timing
report. report.
2.2.1 Transient Timing Report 2.2.1 Transient Timing Report
If the APEX report service (c.f., Section 6.2 of [1]) is invoked to If the APEX report service (c.f., Section 6.2 of [1]) is invoked to
send a timing error report, it issues a data operation with: send a transient timing report, it issues a data operation with:
o its originator identifying the report service associated with the o its originator identifying the report service associated with the
issuing relay issuing relay
o its recipient identifying the endpoint address of the originator o its recipient identifying the endpoint address of the originator
associated with the "dataTiming" option associated with the "dataTiming" option
o its content consisting of a "statusResponse" element having: o its content consisting of a "statusResponse" element having:
* its "transID" attribute equal to the "transID" attribute of the * its "transID" attribute equal to the "transID" attribute of the
skipping to change at page 14, line 7 skipping to change at page 14, line 7
<destination identity='barney@example.com'> <destination identity='barney@example.com'>
<reply code='350' /> <reply code='350' />
</destination> </destination>
</statusResponse> </statusResponse>
</data-content> </data-content>
</data> </data>
S: <ok /> S: <ok />
3. The hold4Endpoint Option 3. The hold4Endpoint Option
Section 4.3 contains the APEX option registration for the Section 5.3 contains the APEX option registration for the
"hold4Endpoint" option. "hold4Endpoint" 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 silently drop data for a recipient if its processing options, is to silently drop data for a recipient if its
endpoint isn't attached. The "hold4Endpoint" option provides for endpoint isn't attached. The "hold4Endpoint" option provides for
data to be queued if the recipient endpoint is not attached. data to be queued if the recipient endpoint is not attached.
If this option is present in the "data" operation (c.f., Section If this option is present in the "data" operation (c.f., Section
4.4.4 of [1]), and the value of the "hold4Endpoint" attribute is true 4.4.4 of [1]), and the value of the "hold4Endpoint" attribute is true
then: then:
skipping to change at page 16, line 5 skipping to change at page 16, line 5
<originator identity='fred@example.com' /> <originator identity='fred@example.com' />
<recipient identity='barney@example.com' /> <recipient identity='barney@example.com' />
<option internal='hold4Endpoint' /> <option internal='hold4Endpoint' />
<option internal='dataTiming' targetHop='all' <option internal='dataTiming' targetHop='all'
mustUnderstand='true' transID='86' /> mustUnderstand='true' transID='86' />
<dataTiming noLaterThan='18000' /> <dataTiming noLaterThan='18000' />
</option> </option>
</data> </data>
S: <ok /> S: <ok />
4. Initial Registrations 4. The dataHopping Option
To detect misconfigurations that cause forwarding loops in the APEX
relaying mesh, the APEX pubsub service re-introduces a mechanism
similar to the IP TTL [2] mechanism, in the form of an APEX option.
Section 5.4 contains the APEX option registration for the
"dataHopping" option.
If this option is present in the "data" operation (c.f., Section
4.4.4 of [1]) and the value of the "noMoreThan" attribute is non-
zero, then:
o For Step 5.2 of Section 4.4.4.1 of [1]:
Immediately prior to sending the data to the next relay, the value
of the "noMoreThan" attribute is reduced by 1.
If the value of the "noMoreThan" attribute becomes less than or
equal to zero, an error in processing has occurred, the data
element is not sent to the next relay, and if the "reportErrors"
attribute is true, the APEX report service is invoked to send an
error report.
Further, note that because this option is processed on a per-hop
basis, the originator must set the "targetHop" attribute to the value
"all" and the "mustUnderstand" attribute to the value "true".
If the APEX report service (c.f., Section 6.2 of [1]) is invoked to
send an error report, it issues a data operation with:
o its originator identifying the report service associated with the
issuing relay
o its recipient identifying the endpoint address of the originator
associated with the "dataHopping" option
o its content consisting of a "statusResponse" element having:
* its "transID" attribute equal to the "transID" attribute of the
"dataHopping" option
* and identifying the original recipient with a permanent failure
indicator
For example:
+-------+ +-------+
| | -- data -------> | |
| appl. | | relay |
| | <--------- ok -- | #1 |
+-------+ +-------+
C: <data content='cid:1@example.com'>
<originator identity='appl=pubsub/topic=fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataHopping' targetHop='all'
mustUnderstand='true' transID='86' />
<dataHopping noMoreThan='2' reportErrors='true' />
</option>
</data>
S: <ok />
+-------+ +-------+
| | -- data -------> | |
| relay | | relay |
| #1 | <--------- ok -- | #2 |
+-------+ +-------+
C: <data content='cid:1@example.com'>
<originator identity='appl=pubsub/topic=fred@example.com' />
<recipient identity='barney@example.com' />
<option internal='dataHopping' targetHop='all'
mustUnderstand='true' transID='86' />
<dataHopping noMoreThan='1' reportErrors='true' />
</option>
</data>
S: <ok />
relay #2 determines that further relaying is necessary:
+-------+ +-------+
| | <------- data -- | |
| relay | | relay |
| #1 | -- ok ---------> | #2 |
+-------+ +-------+
C: <data content='#Content'>
<originator identity='apex=report@example.com' />
<recipient identity='appl=pubsub/topic=fred@example.com' />
<data-content Name='Content'>
<statusResponse transID='86'>
<destination identity='barney@example.com'>
<reply code='550' />
</destination>
</statusResponse>
</data-content>
</data>
S: <ok />
5. Initial Registrations
The APEX option registration template is defined in Section 7.1 of The APEX option registration template is defined in Section 7.1 of
[1]. [1].
4.1 Registration: The attachOverride Option 5.1 Registration: The attachOverride Option
Option Identification: attachOverride Option Identification: attachOverride
Present in: APEX's "attach" element Present in: APEX's "attach" element
Contains: nothing Contains: nothing
Processing Rules: c.f., Section 1 Processing Rules: c.f., Section 1
Contact Information: c.f., the "Authors' Addresses" section of this Contact Information: c.f., the "Authors' Addresses" section of this
memo memo
4.2 Registration: The dataTiming Option 5.2 Registration: The dataTiming Option
Option Identification: dataTiming Option Identification: dataTiming
Present in: APEX's "data" element Present in: APEX's "data" element
Contains: dataTiming (c.f., Section 5) Contains: dataTiming (c.f., Section 6)
Processing Rules: c.f., Section 2 Processing Rules: c.f., Section 2
Contact Information: c.f., the "Authors' Addresses" section of this Contact Information: c.f., the "Authors' Addresses" section of this
memo memo
4.3 Registration: The hold4Endpoint Option 5.3 Registration: The hold4Endpoint Option
Option Identification: hold4Endpoint Option Identification: hold4Endpoint
Present in: APEX's "data" element Present in: APEX's "data" element
Contains: nothing Contains: nothing
Processing Rules: c.f., Section 3 Processing Rules: c.f., Section 3
Contact Information: c.f., the "Authors' Addresses" section of this Contact Information: c.f., the "Authors' Addresses" section of this
memo memo
5. The APEX Party Pack DTD 5.4 Registration: The dataHopping Option
Option Identification: dataHopping
Present in: APEX's "data" element
Contains: dataHopping (c.f., Section 6)
Processing Rules: c.f., Section 4
Contact Information: c.f., the "Authors' Addresses" section of this
memo
6. The APEX Party Pack DTD
<!-- <!--
DTD for the APEX option party pack, as of 2001-05-14 DTD for the APEX option party pack, as of 2001-05-14
Refer to this DTD as: Refer to this DTD as:
<!ENTITY % APEXPARTY PUBLIC "-//IETF//DTD APEX PARTY//EN" ""> <!ENTITY % APEXPARTY PUBLIC "-//IETF//DTD APEX PARTY//EN" "">
%APEXPARTY; %APEXPARTY;
--> -->
<!ENTITY % APEXCORE PUBLIC "-//IETF//DTD APEX CORE//EN" <!ENTITY % APEXCORE PUBLIC "-//IETF//DTD APEX CORE//EN"
%APEXCORE; %APEXCORE;
<!-- <!--
DTD data types: DTD data types:
entity syntax/reference example entity syntax/reference example
====== ================ ======= ====== ================ =======
hopcount
HOPS 0..255 17
milli-seconds milli-seconds
MILLISECS 0..2147483647 60000 MILLISECS 0..2147483647 60000
--> -->
<!ENTITY % HOPS "CDATA">
<!ENTITY % MILLISECS <!ENTITY % MILLISECS
"CDATA"> "CDATA">
<!ELEMENT dataHopping EMPTY>
<!ATTLIST dataHopping
noMoreThan %HOPS; "0"
reportErrors
(true|false) "false">
<!ELEMENT dataTiming EMPTY> <!ELEMENT dataTiming EMPTY>
<!ATTLIST dataTiming <!ATTLIST dataTiming
noLaterThan %MILLISECS; "0" noLaterThan %MILLISECS; "0"
returnTrip %MILLISECS; "0" returnTrip %MILLISECS; "0"
reportAfter %MILLISECS; "0" reportAfter %MILLISECS; "0"
reportErrors reportErrors
(true|false) "false"> (true|false) "false">
6. Security Considerations 7. Security Considerations
Consult [1]'s Section 11 for a discussion of security issues. Consult [1]'s Section 11 for a discussion of security issues.
In addition: In addition:
o The dataTiming option (Section 2) may be used to expose private o The dataTiming option (Section 2) may be used to expose private
network topology. Accordingly, an administrator may wish to network topology. Accordingly, an administrator may wish to
choose to disable this option except at the ingress/egress points choose to disable this option except at the ingress/egress points
for its administrative domain. for its administrative domain.
skipping to change at page 19, line 10 skipping to change at page 23, line 10
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-05 (work in progress), August 2001. Core", draft-ietf-apex-core-05 (work in progress), August 2001.
[2] Newman, D., "Deliver By SMTP Service Extension", RFC 2852, June [2] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981.
[3] 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
Santa Rosa, CA 95401 Santa Rosa, CA 95401
US US
skipping to change at page 20, line 5 skipping to change at page 24, line 5
Invisible Worlds, Inc. Invisible Worlds, Inc.
131 Stony Circle 131 Stony Circle
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: jkint@invisible.net EMail: jkint@invisible.net
URI: http://invisible.net/ URI: http://invisible.net/
Graham Klyne Graham Klyne
Baltimore Technologies MIMEsweeper Group
1310 Waterside 1310 Waterside
Arlington Business Park Arlington Business Park
Theale, Reading RG7 4SA Theale, Reading RG7 4SA
UK UK
Phone: +44 118 903 8000 Phone: +44 118 903 8000
EMail: gk@acm.org EMail: Graham.Klyne@MIMEsweeper.com
Darren New Darren New
Invisible Worlds, Inc. 5390 Caminito Exquisito
131 Stony Circle San Diego, CA 92130
Suite 500
Santa Rosa, CA 95401
US US
Phone: +1 707 578 2350 Phone: +1 858 350 9733
EMail: dnew@invisible.net EMail: dnew@san.rr.com
URI: http://invisible.net/
Scott Pead Scott Pead
Invisible Worlds, Inc. Invisible Worlds, Inc.
131 Stony Circle 131 Stony Circle
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: spead@invisible.net EMail: spead@invisible.net
URI: http://invisible.net/ URI: http://invisible.net/
Marshall T. Rose Marshall T. Rose
Invisible Worlds, Inc. Dover Beach Consulting, Inc.
131 Stony Circle POB 255268
Suite 500 Sacramento, CA 95865-5268
Santa Rosa, CA 95401
US US
Phone: +1 707 578 2350 Phone: +1 916 483 8878
EMail: mrose@invisible.net EMail: mrose@dbc.mtview.ca.us
URI: http://invisible.net/
Michael F. Schwartz
NetTopBox, Inc.
EMail: schwartz@CodeOnTheRoad.com
URI: http://www.CodeOnTheRoad.com
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors gratefully acknowledge the contributions of Chris Newman The authors gratefully acknowledge the contributions of Chris Newman
and Bob Wyman. Further, the dataTiming option is similar in function and Bob Wyman. Further, the dataTiming option is similar in function
to "Deliver By" SMTP service extension defined by Dan Newman in [2]. to "Deliver By" SMTP service extension defined by Dan Newman in [3].
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 5.
Appendix C. Revision History Appendix C. Revision History
Note to RFC editor: please remove this entire appendix, and the Note to RFC editor: please remove this entire appendix, and the
corresponding entries in the table of contents, prior to publication. corresponding entries in the table of contents, prior to publication.
C.1 Changes from draft-ietf-apex-party-02 C.1 Changes from draft-ietf-apex-party-03
o Moved the dataHopping option from the APEX pubsub service
specification.
C.2 Changes from draft-ietf-apex-party-02
o Corrected one typo, used better grammar in one spot. o Corrected one typo, used better grammar in one spot.
o Added some text on the deterministic behavior of the "returnTrip" o Added some text on the deterministic behavior of the "returnTrip"
attribute. attribute.
o Added some text on relay optimization of non-connections. o Added some text on relay optimization of non-connections.
o Removed the reference to "xml.resource.org" in the DTD. o Removed the reference to "xml.resource.org" in the DTD.
C.2 Changes from draft-ietf-apex-party-01 C.3 Changes from draft-ietf-apex-party-01
o A page-break was fixed. o A page-break was fixed.
C.3 Changes from draft-ietf-apex-party-00 C.4 Changes from draft-ietf-apex-party-00
o When terminating an association due to processing the o When terminating an association due to processing the
"attachOverride" option, the "code" attribute of the terminate "attachOverride" option, the "code" attribute of the terminate
operation must be supplied. operation must be supplied.
o A small number of typos were corrected. 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.
 End of changes. 37 change blocks. 
58 lines changed or deleted 191 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/