[IMXPwg] next rev of drafts, incomplete

Marshall Rose mrose@dbc.mtview.ca.us
Tue, 19 Sep 2000 22:16:48 -0700


This is a multi-part message in MIME format.

------=_NextPart_000_009A_01C02287.4D97D7A0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_009B_01C02287.4D97D7A0"


------=_NextPart_001_009B_01C02287.4D97D7A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

hi. here is thext next set of drafts, still being edited. issues:

I. imxp-core

waiting to hear from dave confirming the reverse/forward dns lookup thing.

II. imxp-access

none.

III. imxp-presence

1. what we call the "publish" operation is called the "notify" operation by
CPIM, we have our own "notify" operation which doesn't have a CPIM parallel.

the reason we call it "publish" is because it's what a publisher uses to
"publish" new presence information, and also how the service "publishes"
presence information to subscribers.

the reason we call it "notify" is because it's what a watcher gets when
someone gets a subscription to someone's presence information.

i suggest we just live with it.

2. i question whether using rfc2533 really yields capabilities info or not.
darren doesn't think so. or rather, he doesn't think that it yields the
stuff that you want in terms of capabilities (e.g., "i accept text/html").

graham - can you clarify?

IV. imxp-message

this is just skeletal.

graham - do you want to work on this?

/mtr


------=_NextPart_001_009B_01C02287.4D97D7A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4207.2601" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>hi. here is thext next set of drafts, still being =
edited.=20
issues:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I. imxp-core</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>waiting to hear from dave confirming the =
reverse/forward dns=20
lookup thing.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>II. imxp-access</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>none.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>III. imxp-presence</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>1. what we call the "publish" operation is called =
the "notify"=20
operation by CPIM, we have our own "notify" operation which doesn't have =
a CPIM=20
parallel.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>the reason we call it "publish" is because it's what =
a=20
publisher uses to "publish" new presence information, and also how the =
service=20
"publishes" presence information to subscribers.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>the reason we call it "notify" is because it's what =
a watcher=20
gets when someone gets a subscription to someone's presence=20
information.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>i suggest we just live with it.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>2. i question whether using rfc2533 really yields =
capabilities=20
info or not. darren doesn't think so. or rather, he doesn't think that =
it yields=20
the stuff that you want in terms of capabilities (e.g., "i accept=20
text/html").</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>graham - can you clarify?</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>IV. imxp-message</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>this is just skeletal.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>graham - do you want to work on this?</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>/mtr</FONT></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_001_009B_01C02287.4D97D7A0--

------=_NextPart_000_009A_01C02287.4D97D7A0
Content-Type: text/html;
	name="imxp-presence.html"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="imxp-presence.html"

<html><head><title>The IMXP Presence Service</title>
<STYLE type=3D'text/css'>
    .title { color: #990000; font-size: 22px; line-height: 22px; =
font-weight: bold; text-align: right;
             font-family: helvetica, arial, sans-serif }
    .filename { color: #666666; font-size: 18px; line-height: 28px; =
font-weight: bold; text-align: right;
                  font-family: helvetica, arial, sans-serif }
    p.copyright { color: #000000; font-size: 10px;
                  font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    p { margin-left: 2em; margin-right: 2em; }
    ol { margin-left: 2em; margin-right: 2em; }
    ul.text { margin-left: 2em; margin-right: 2em; }
    pre { margin-left: 3em; color: #333333 }
    ul.toc { color: #000000; line-height: 16px;
             font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    H3 { color: #333333; font-size: 16px; line-height: 16px; =
font-family: helvetica, arial, sans-serif }
    H4 { color: #000000; font-size: 14px; font-family: helvetica, arial, =
sans-serif }
    TD.header { color: #ffffff; font-size: 10px; font-family: arial, =
helvetica, san-serif; valign: top }
    TD.author-text { color: #000000; font-size: 10px;
                     font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    TD.author { color: #000000; font-weight: bold; margin-left: 4em; =
font-size: 10px; font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    A:link { color: #990000; font-size: 10px; text-transform: uppercase; =
font-weight: bold;
             font-family: MS Sans Serif, verdana, charcoal, helvetica, =
arial, sans-serif }
    A:visited { color: #333333; font-weight: bold; font-size: 10px; =
text-transform: uppercase;
                font-family: MS Sans Serif, verdana, charcoal, =
helvetica, arial, sans-serif }
    A:name { color: #333333; font-weight: bold; font-size: 10px; =
text-transform: uppercase;
             font-family: MS Sans Serif, verdana, charcoal, helvetica, =
arial, sans-serif }
    .link2 { color:#ffffff; font-weight: bold; text-decoration: none;
             font-family: monaco, charcoal, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
             font-size: 9px }
    .RFC { color:#666666; font-weight: bold; text-decoration: none;
           font-family: monaco, charcoal, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
           font-size: 9px }
    .hotText { color:#ffffff; font-weight: normal; text-decoration: =
none;
               font-family: charcoal, monaco, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
               font-size: 9px }
</style>
</head>
<body bgcolor=3D"#ffffff"text=3D"#000000" alink=3D"#000000" =
vlink=3D"#666666" link=3D"#990000">
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<table width=3D"66%" border=3D"0" cellpadding=3D"0" =
cellspacing=3D"0"><tr><td><table width=3D"100%" border=3D"0" =
cellpadding=3D"2" cellspacing=3D"1">
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Network Working Group</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">M.T. Rose</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Internet-Draft</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">Invisible Worlds, Inc.</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Expires: March 20, 2001</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">G. Klyne</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Content Technologies Limited</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">D.H. Crocker</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Brandenburg Consulting</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">September 19, 2000</td></tr>
</table></td></tr></table>
<div align=3D"right"><font face=3D"monaco, MS Sans Serif" =
color=3D"#990000" size=3D"+3"><b><br><span class=3D"title">The IMXP =
Presence Service</span></b></font></div>
<div align=3D"right"><font face=3D"monaco, MS Sans Serif" =
color=3D"#666666" size=3D"+2"><b><span =
class=3D"filename">draft-mrose-imxp-presence-01</span></b></font></div>
<font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<h3>Status of this Memo</h3>
<p>
This document is an Internet-Draft and is in full conformance with all =
provisions of Section 10 of RFC2026.</p>
<p>
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups.
Note that other groups may also distribute working documents as
Internet-Drafts.</p>
<p>
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any =
time.
It is inappropriate to use Internet-Drafts as reference material or to =
cite
them other than as "work in progress."</p>
<p>
The list of current Internet-Drafts can be accessed at
<a =
href=3D'http://www.ietf.org/ietf/1id-abstracts.txt'>http://www.ietf.org/i=
etf/1id-abstracts.txt</a>.</p>
<p>
The list of Internet-Draft Shadow Directories can be accessed at
<a =
href=3D'http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html<=
/a>.</p>
<p>
This Internet-Draft will expire on March 20, 2001.</p>

<h3>Copyright Notice</h3>
<p>
Copyright (C) The Internet Society (2000). All Rights Reserved.</p>

<h3>Abstract</h3>

<p>
This memo describes the IMXP presence service,
addressed as the well-known endpoint "imxp=3Dpresence".
The presence service is used to manage presence information for IMXP
endpoints.
</p>
<a name=3D"toc"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Table of Contents</h3>
<ul compact class=3D"toc">
<b><a href=3D"#anchor1">1.</a>&nbsp;
Introduction<br></b>
<b><a href=3D"#anchor2">2.</a>&nbsp;
Management of Presence Information<br></b>
<b><a href=3D"#anchor3">2.1</a>&nbsp;
Update of Presence Information<br></b>
<b><a href=3D"#anchor4">2.2</a>&nbsp;
Distribution of Presence Information<br></b>
<b><a href=3D"#anchor5">2.3</a>&nbsp;
Distribution of Watcher Information<br></b>
<b><a href=3D"#anchor6">3.</a>&nbsp;
Format of Presence Entries<br></b>
<b><a href=3D"#service.presence">4.</a>&nbsp;
The Presence Service<br></b>
<b><a href=3D"#anchor7">4.1</a>&nbsp;
Use of XML and MIME<br></b>
<b><a href=3D"#operation.subscribe">4.2</a>&nbsp;
The Subscribe Operation<br></b>
<b><a href=3D"#operation.watch">4.3</a>&nbsp;
The Watch Operation<br></b>
<b><a href=3D"#operation.publish">4.4</a>&nbsp;
The Publish Operation<br></b>
<b><a href=3D"#operation.terminate">4.5</a>&nbsp;
The Terminate Operation<br></b>
<b><a href=3D"#operation.notify">4.6</a>&nbsp;
The Notify Operation<br></b>
<b><a href=3D"#operation.reply">4.7</a>&nbsp;
The Reply Operation<br></b>
<b><a href=3D"#presence.definition">5.</a>&nbsp;
Registration: The Presence Service<br></b>
<b><a href=3D"#imxp-presence.dtd">6.</a>&nbsp;
The Presence Service DTD<br></b>
<b><a href=3D"#rfc.references">&#167;</a>&nbsp;
References<br></b>
<b><a href=3D"#rfc.authors">&#167;</a>&nbsp;
Authors' Addresses<br></b>
<b><a href=3D"#cpim.mapping">A.</a>&nbsp;
Mapping for the CPIM Presence Service<br></b>
<b><a href=3D"#anchor8">B.</a>&nbsp;
Changes from draft-mrose-imxp-presence-00<br></b>
<b><a href=3D"#anchor9">C.</a>&nbsp;
Acknowledgements<br></b>
<b><a href=3D"#rfc.copyright">&#167;</a>&nbsp;
Full Copyright Statement<br></b>
</ul>
<br clear=3D"all">

<a name=3D"anchor1"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>1.&nbsp;Introduction</h3>

<p>
This memo describes a presence service that is built upon the
<a href=3D"#IMXP-CORE">IMXP</a>[1] "relaying mesh",
which,
in turn,
is specified as a <a href=3D"#BEEP-FRAMEWORK">BEEP</a>[2] profile.
</p>

<p>
IMXP,
at its core,
provides a best-effort datagram service.
With the exception of a co-resident IMXP report service
(used for error reporting),
all other IMXP services are provided on top of IMXP's "relaying mesh",
e.g.,
</p>
</font><pre>
   +----------+     +----------+    +----------+
   |   IMXP   |     |   IMXP   |    |          |
   |  access  |     | presence |    |   ...    |=20
   | service  |     | service  |    |          |=20
   +----------+     +----------+    +----------+
        |                |               |
        |                |               |
+------------------------------------------------+---------+
|                                                |  IMXP   |
|                    IMXP core                   |  report |
|                                                | service |
+------------------------------------------------+---------+
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
Applications communicate with IMXP services by sending data to a
"well-known endpoint" (WKE).
</p>

<p>
The IMXP presence service is used to manage presence information
for IMXP endpoints.
Although the presence service is logically layered above the IMXP core,
implementers may choose to physically co-reside the presence service =
with
IMXP core software.
</p>

<p>
IMXP applications communicate with the presence service by exchanging
data with the well-known endpoint "imxp=3Dpresence" in the corresponding
administrative domain,
e.g., "imxp=3Dpresence@example.com" is the endpoint associated with the
presence service in the "example.com" administrative domain.
</p>

<p>
Note that within a single administrative domain,
the presence service makes use of the IMXP
<a href=3D"#IMXP-ACCESS">access</a>[4] service in order to determine
if an originator is allowed to view or manage presence information.
</p>

<p>
The presence service described in this memo is compatible with the
<a href=3D"#IM-COMMON">Common Profile for Instant Messaging</a>[3].
Specifically,
<a href=3D"#cpim.mapping">Mapping for the CPIM Presence Service</a> =
defines a lossless mapping for the CPIM
presence service.
</p>

<a name=3D"anchor2"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>2.&nbsp;Management of Presence Information</h3>

<p>
Management of presence information falls into three categories:

<ul class=3D"text">

<li>
applications may update the presence entry associated with an
endpoint;
</li>

<li>
applications may subscribe to receive presence information about an
endpoint; and,
</li>

<li>
applications may find out who is subscribed to receive presence
information.
</li>

</ul>

Each is now described in turn.
</p>

<p>

</p>

<h4><a name=3D"anchor3">2.1</a>&nbsp;Update of Presence Information</h4>

<p>
When an application wants to modify the presence entry
associated with an endpoint,
it sends a publish operation to the service,
e.g.,
</p>
</font><pre>
    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' content=3D'#Content'>
         &lt;recipient identity=3D'imxp=3Dpresence@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;publish publisher=3D'fred@example.com' transID=3D'1'
                      timeStamp=3D'14 May 2000 13:30:00 -0800'>
                 &lt;presence publisher=3D'fred@example.com'
                        lastUpdate=3D'14 May 2000 13:02:00 -0800'
                        publisherInfo=3D'http://www.example.com/fred/'>
                     &lt;tuple destination=3D'im:fred@example.com'
                       availableUntil=3D'14 May 2000 14:02:00 -0800' />
                     &lt;tuple
                       destination=3D'mailto:fred@bedrock.example.com'
                       availableUntil=3D'31 Dec 2525 23:59:59 -0800' />
                 &lt;/presence>
             &lt;/publish>
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
The service immediately responds with a reply operation
containing the same transaction-identifier,
e.g.,
</p>
</font><pre>
                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  | pres. |
                               |       | -- ok ---------> |  svc. |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dpresence@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'fred@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;reply code=3D'250' transID=3D'1' />
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>

</p>

<h4><a name=3D"anchor4">2.2</a>&nbsp;Distribution of Presence =
Information</h4>

<p>
When an application wants to (periodically) receive the
presence entry associated with an endpoint,
it sends a subscribe operation to the service,
e.g.,
</p>
</font><pre>
    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'wilma@example.com' content=3D'#Content'>
         &lt;recipient identity=3D'imxp=3Dpresence@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;subscribe publisher=3D'fred@example.com' =
duration=3D'86400'
                        transID=3D'100' />
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
The service immediately responds with a publish operation
containing the same transaction-identifier,
e.g.,
</p>
</font><pre>
                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  | pres. |
                               |       | -- ok ---------> |  svc. |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dpresence@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'wilma@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;publish publisher=3D'fred@example.com' transID=3D'100'
                      timeStamp=3D'14 May 2000 13:30:00 -0800'>
                 &lt;presence publisher=3D'fred@example.com'
                        lastUpdate=3D'14 May 2000 13:02:00 -0800'
                        publisherInfo=3D'http://www.example.com/fred/'>
                     &lt;tuple destination=3D'im:fred@example.com'
                       availableUntil=3D'14 May 2000 14:02:00 -0800' />
                 &lt;/presence>
             &lt;/publish>
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>

</p>

<p>
Subsequently,
for up to the specified "duration",
the service sends new publish operations whenever there are any
changes to the endpoint's presence information.
If the "duration" is zero-valued,
a one time poll of the presence information is achieved;
otherwise,
at the end of the "duration",
a terminate operation is sent.
</p>

<p>

</p>

<p>
Either the subscriber or the service may cancel a subscription by
sending a terminate operation,
e.g.,
</p>
</font><pre>
    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'wilma@example.com' content=3D'#Content'>
         &lt;recipient identity=3D'imxp=3Dpresence@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;terminate transID=3D'100' />
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />

                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  | pres. |
                               |       | -- ok ---------> |  svc. |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dpresence@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'wilma@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;reply code=3D'250' transID=3D'100' />
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />

or

                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  | pres. |
                               |       | -- ok ---------> |  svc. |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dpresence@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'wilma@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;terminate transID=3D'100' />
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>

</p>

<h4><a name=3D"anchor5">2.3</a>&nbsp;Distribution of Watcher =
Information</h4>

<p>
When an application wants to (periodically) receive notices
about endpoints that are subscribed to receive presence information,
it sends a watch operation to the service,
e.g.,
</p>
</font><pre>
    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' content=3D'#Content'>
         &lt;recipient identity=3D'imxp=3Dpresence@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;watch publisher=3D'fred@example.com' duration=3D'86400'
                    transID=3D'2' />
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
The service immediately responds with a reply operation
containing the same transaction-identifier,
e.g.,
</p>
</font><pre>
                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  | pres. |
                               |       | -- ok ---------> |  svc. |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dpresence@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'fred@example.com' />
         &lt;data-content Name=3D'Content'
             &lt;reply code=3D'250' transID=3D'2' />
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
For each current subscriber,
the service immediately sends a notify operation
containing the same transaction-identifier,
e.g.,
</p>
</font><pre>
                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  | pres. |
                               |       | -- ok ---------> |  svc. |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dpresence@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'fred@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;notify subscriber=3D'wilma@example.com' transID=3D'2' =
/>
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
Subsequently,
for up to the specified "duration",
the service sends new notify operations whenever an application
subscribes successfully.
If the "duration" is zero-valued,
a one time poll of the watcher information is achieved;
otherwise,
at the end of the "duration",
a terminate operation is sent.
</p>

<p>

</p>

<p>
Either the watcher or the service may cancel the request by
sending a terminate operation,
e.g.,
</p>
</font><pre>
    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' content=3D'#Content'>
         &lt;recipient identity=3D'imxp=3Dpresence@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;terminate transID=3D'2' />
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />


                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  | pres. |
                               |       | -- ok ---------> |  svc. |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dpresence@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'fred@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;reply code=3D'250' transID=3D'2' />
          &lt;/data-content>
     &lt;/data>
  S: &lt;ok />

or

                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  | pres. |
                               |       | -- ok ---------> |  svc. |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dpresence@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'fred@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;terminate transID=3D'2' />
          &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<a name=3D"anchor6"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>3.&nbsp;Format of Presence Entries</h3>

<p>
Each administrative domain is responsible for maintaining a
"presence entry" for each of its endpoints
(regardless of whether those endpoints are currently attached to the
relaying mesh).
</p>

<p>
<a href=3D"#imxp-presence.dtd">The Presence Service DTD</a> defines the =
syntax for presence entries.
Each presence entry has
a "publisher" attribute,
a "lastUpdate" attribute,
a "publisherInfo" attribute,
and contains one or more "tuple" elements:

<ul class=3D"text">

<li>
the "publisher" attribute specifies the endpoint associated with the
presence entry;
</li>

<li>
the "lastUpdate" attribute specifies the date and time that the
service last updated the presence entry;
</li>

<li>
the "publisherInfo" attribute specifies arbitrary information about
the publisher (using a URI); and,
</li>

<li>
each "tuple" element specifies information about an entity=20
associated with the endpoint.
</li>

</ul>

Each "tuple" element has
a "destination" attribute,
an "availableUntil" attribute,
a "tupleInfo" attribute,
and contains zero or more "capability" elements:

<ul class=3D"text">

<li>
the "destination" attribute identifies the entity as a URI
(e.g., "im:fred@example.com" or "mailto:fred@bedrock.example.com");
</li>

<li>
the "availableUntil" attribute specifies the latest date and time
that the entity is capable of receiving messages;
</li>

<li>
the "tupleInfo" attribute specifies arbitrary information about
the entity (using a URI); and,
</li>

<li>
each "capability" element contains a specification as to the kinds
of content the entity is capable of receiving.
</li>

</ul>

Each "capability" element contains arbitrary character data formatted
according to the standard indicated in the element's "baseline" =
attribute.
</p>

<a name=3D"service.presence"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>4.&nbsp;The Presence Service</h3>

<p>
<a href=3D"#presence.definition">Registration: The Presence Service</a> =
contains the IMXP service
registration for the presence service:

<ul class=3D"text">

<li>
Within an administrative domain,
the service is addressed using the well-known endpoint of
"imxp=3Dpresence".
</li>

<li>
<a href=3D"#imxp-presence.dtd">The Presence Service DTD</a> defines the =
syntax of the
operations exchanged with the service.
</li>

<li>
A consumer of the service initiates communications by sending data
containing the subscribe, watch, or publish operation.
</li>

<li>
In addition to replying to these operations,
the service may also initiate communications by
sending data containing the terminate, publish, or notify operations.
</li>

</ul>

</p>

<p>
An implementation of the service must maintain
information about both presence entries and in-progress operations in
persistent storage.
</p>

<p>
Consult Section 6.1.1 of <a href=3D"#IMXP-CORE">[1]</a> for a discussion =
on
the properties of long-lived transaction-identifiers.
</p>

<p>

</p>

<h4><a name=3D"anchor7">4.1</a>&nbsp;Use of XML and MIME</h4>

<p>
Section 4.1 of <a href=3D"#IMXP-CORE">[1]</a> describes how
arbitrary MIME content is exchanged as a BEEP payload.
For example,
to transmit:
</p>
</font><pre>
    &lt;data originator=3D'imxp=3Dpresence@example.com' content=3D'...'>
        &lt;recipient identity=3D'fred@example.com' />
    &lt;/data>

where "..." refers to:

    &lt;reply code=3D'250' transID=3D'1' />

then the corresponding BEEP operation might look like this:

    C: MSG 1 1 . 42 1234
    C: Content-Type: multipart/related; boundary=3D"boundary";
    C:               start=3D"&lt;1@example.com>";
    C:               type=3D"text/xml"
    C:=20
    C: --boundary
    C: Content-Type: text/xml
    C: Content-ID: &lt;1@example.com>
    C:=20
    C: &lt;data originator=3D'fred@example.com'
    C:       content=3D'cid:2@example.com'>
    C:     &lt;recipient identity=3D'imxp=3Daccess@example.com' />
    C: &lt;/data>
    C: --boundary
    C: Content-Type: text/xml
    C: Content-Transfer-Encoding: binary
    C: Content-ID: &lt;2@example.com>
    C:=20
    C: &lt;reply code=3D'250' transID=3D'1' />
    C: --boundary--
    C: END

or this:

    C: MSG 1 1 . 42 1234
    C: Content-Type: text/xml
    C:=20
    C: &lt;data originator=3D'fred@example.com' content=3D'#Content'>
    C:     &lt;recipient identity=3D'imxp=3Dpresence@example.com' />
    C:     &lt;data-content Name=3D'Content'>
    C:         &lt;reply code=3D'250' transID=3D'1' />
    C:     &lt;/data-content>
    C: &lt;/data>
    C: END
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<h4><a name=3D"operation.subscribe">4.2</a>&nbsp;The Subscribe =
Operation</h4>

<p>
When an application wants to (periodically) receive the
presence entry associated with an endpoint,
it sends a "subscribe" element to the service.
</p>

<p>
The "subscribe" element has a "publisher" attribute, a "duration"
attribute, a "transID" attribute, and no content:

<ul class=3D"text">

<li>
the "publisher" attribute specifies the endpoint associated with the
presence entry;
</li>

<li>
the "transID" attribute specifies the transaction-identifier
associated with this operation; and,
</li>

<li>
the "duration" attribute specifies the maximum number of seconds
for which the originator is interested in receiving updated presence
information.
</li>

</ul>

</p>

<p>

</p>

<p>
When the service receives a "subscribe" element,
we refer to the "publisher" attribute of that element as the "subject",
and the service performs these steps:

<ol class=3D"text">

<li>
If the subject is outside of this administrative domain,
a "reply" element having code 553 is sent as data to the originator.
</li>

<li>
If the subject does not refer to a valid endpoint,
a "reply" element having code 550 is sent as data to the originator.
</li>

<li>
If the subject's access entry does not contain a
"presence:subscribe" token for the originator,
a "reply" element having code 537 is sent as data to the originator.
</li>

<li>
If the originator already has an in-progress subscribe operation
for the subject,
then the previous subscribe operation is silently terminated,
and processing continues.
</li>

<li>
If the "transID" attribute refers to an in-progress subscribe or
watch operation for the originator,
a "reply" element having code 555 is sent as data to the originator.
</li>

<li>
Otherwise:

<ol class=3D"text">

<li>
A "publish" element,
corresponding to the subject's presence entry,
is immediately sent as data to the originator.
</li>

<li>
For each endpoint currently watching subscribers to the subject's
presence information,
a "notify" element is immediately as sent as data
(c.f., Step 6.3 of <a href=3D"#operation.notify">The Notify =
Operation</a>).
</li>

<li>
For up to the amount of time indicated by the "duration" attribute of =
the
"subscribe" element,
if the subject's presence entry changes,
an updated "presence" element is sent as data to the originator
using the <a href=3D"#operation.publish">publish operation</a>.
Finally,
when the amount of time indicated by the "duration" attribute expires,
a <a href=3D"#operation.terminate">terminate operation</a> is
sent to the originator.
</li>

</ol>

Note that if the duration is zero-valued,
then the subscribe operation is making a one-time poll of the presence
information.
Accordingly,
Step 6.3 above does not occur.
</li>

</ol>

</p>

<p>
Regardless of whether a "publish" or "reply" element is sent to the
originator,
the "transID" attribute is identical to the value found in the =
"subscribe"
element sent by the originator.
</p>

<p>

</p>

<h4><a name=3D"operation.watch">4.3</a>&nbsp;The Watch Operation</h4>

<p>
When an application wants to (periodically) receive notices
about endpoints that are subscribed to receive presence information,
it sends a "watch" element to the service.
</p>

<p>
The "watch" element has a "publisher" attribute, a "duration"
attribute, a "transID" attribute, and no content:

<ul class=3D"text">

<li>
the "publisher" attribute specifies the endpoint associated with the
presence entry;
</li>

<li>
the "transID" attribute specifies the transaction-identifier
associated with this operation; and,
</li>

<li>
the "duration" attribute specifies the maximum number of seconds
for which the originator is interested in watching subscribers.
</li>

</ul>

</p>

<p>

</p>

<p>
When the service receives a "watch" element,
we refer to the "publisher" attribute of that element as the "subject",
and the service performs these steps:

<ol class=3D"text">

<li>
If the subject is outside of this administrative domain,
a "reply" element having code 553 is sent as data to the originator.
</li>

<li>
If the subject does not refer to a valid endpoint,
a "reply" element having code 550 is sent as data to the originator.
</li>

<li>
If the subject's access entry does not contain a "presence:watch"
token for the originator,=20
a "reply" element having code 537 is sent as data to the originator.
</li>

<li>
If the originator already has an in-progress watch operation for
the subject,
then the previous watch operation is silently terminated,
and processing continues.
</li>

<li>
If the "transID" attribute refers to an in-progress subscribe or
watch operation for the originator,
a "reply" element having code 555 is sent as data to the originator.
</li>

<li>
Otherwise:

<ol class=3D"text">

<li>
A "reply" element having code 250 is sent as data to the
originator.
</li>

<li>
For each endpoint currently subscribing to the subject's presence
information,
a "notify" element is immediately sent as data to the originator
(c.f., <a href=3D"#operation.notify">The Notify Operation</a>).
Finally,
when the amount of time indicated by the "duration" attribute expires,
a <a href=3D"#operation.terminate">terminate operation</a> is
sent to the originator.
</li>

<li>
For up to the amount of time indicated by the "duration" attribute of =
the
"watch" element,
whenever a subscribe operation succeeds,
a "notify" element is sent as data to the originator.
Finally,
when the amount of time indicated by the "duration" attribute expires,
the a <a href=3D"#operation.terminate">terminate operation</a> is
sent to the originator.
</li>

</ol>

Note that if the duration is zero-valued,
then the watch operation is making a one-time poll of the presence
information.
Accordingly,
Step 6.3 above does not occur.
</li>

</ol>

</p>

<p>
Regardless of whether a "notify" or "reply" element is sent to the
originator,
the "transID" attribute is identical to the value found in the =
"presence"
element sent by the originator.
</p>

<h4><a name=3D"operation.publish">4.4</a>&nbsp;The Publish =
Operation</h4>

<p>
When an application wants to modify the presence entry
associated with an endpoint,
it sends a "publish" element to the service.
In addition,
the service sends a "publish" element to endpoints that have
subscribed to see presence information
(c.f., <a href=3D"#operation.subscribe">The Subscribe Operation</a>).
</p>

<p>
The "publish" element has a "publisher" attribute,
a "transID" attribute,
and contains a "presence" element:

<ul class=3D"text">

<li>
the "publisher" attribute specifies the endpoint to be associated
with the presence entry;
</li>

<li>
the "transID" attribute specifies the transaction-identifier
associated with this operation;
</li>

<li>
the "timeStamp" attribute specifies the current date and time; and,
</li>

<li>
the "presence" element contains the desired presence entry for the
endpoint.
</li>

</ul>

</p>

<p>
When the service sends a "publish" element,
the "transID" attribute specifies the transaction-identifier
associated with the subscribe operation that caused this "publish"
element to be sent,
and the "timeStamp" attribute is the service's notion of the current
date and time.
No reply is sent by the receiving endpoint.
</p>

<p>

</p>

<p>
When the service receives a "publish" element,
we refer to the "publisher" attribute of that element as the "subject",
and the service performs these steps:

<ol class=3D"text">

<li>
If the "publisher" attribute of the "publish" element doesn't match the
"publisher" attribute of the "presence" element contained in the
"publish" element,
a "reply" element having code 503 is sent as data to the originator.
</li>

<li>
If the subject is outside of this administrative domain,
a "reply" element having code 553 is sent as data to the originator.
</li>

<li>
If the subject does not refer to a valid endpoint,
a "reply" element having code 550 is sent as data to the originator.
</li>

<li>
If the subject's access entry does not contain a "presence:publish" =
token
for the originator,
a "reply" element having code 537 is sent as data to the originator.
</li>

<li>
If the "lastUpdate" attribute of the "publish" element is not
semantically identical to the last update time of the subject's presence
entry,
a "reply" element having code 555 is sent as data to the originator.
(This allows a simple mechanism for atomic updates.)
</li>

<li>
Otherwise:

<ol class=3D"text">

<li>
The subject's presence entry is updated from the "publish" element.
</li>

<li>
The last update time of the presence entry is set to the current time.
</li>

<li>
A "reply" element having code 250 is sent as data to the originator.
</li>

</ol>

</li>

</ol>

</p>

<p>
When sending the "reply" element,
the "transID" attribute is identical to the value found in the "publish"
element sent by the originator.
</p>

<p>

</p>

<h4><a name=3D"operation.terminate">4.5</a>&nbsp;The Terminate =
Operation</h4>

<p>
When an application no longer wishes to subscribe to
presence information
or to watch endpoints that are subscribed to receive presence =
information,
it sends a "terminate" element to the service;
similarly,
when the service no longer considers an application to be subscribing
or watching,
a "terminate" element is sent to the application.
</p>

<p>
The "terminate" element contains only a "transID" attribute
that specifies the transaction-identifier associated an in-progress
subscribe or watch operation.
Section 10.2 of <a href=3D"#IMXP-CORE">[1]</a> defines the syntax for =
the
"terminate" element.
</p>

<p>
When the service receives a "terminate" element,
it performs these steps:

<ol class=3D"text">

<li>
If the transaction-identifier does not refer to a previous
publish or watch operation for the originator,
an "error" element having code 550 is returned.
</li>

<li>
Otherwise,
the previous publish or watch operation for the originator is =
terminated,
and a "reply" element having code 250 is sent as data to the originator.
</li>

</ol>

Note that following a terminate operation,
the originator may receive further presence or watcher updates.
Although the service will send no further updates after processing a
terminate operation and sending the reply operation,
earlier updates may be in transit.
</p>

<p>

</p>

<h4><a name=3D"operation.notify">4.6</a>&nbsp;The Notify Operation</h4>

<p>
The service sends a "notify" element to endpoints that are watching
other endpoints subscribed to presence information
(c.f., <a href=3D"#operation.watch">The Watch Operation</a>).
</p>

<p>
The "notify" element has a "subscriber" attribute, a "transID"
attribute, and no content:

<ul class=3D"text">

<li>
the "subscriber" attribute specifies the endpoint that is
subscribed to presence information; and,
</li>

<li>
the "transID" attribute specifies the transaction-identifier
associated with the watch operation that caused this "notify" element
to be sent.
No reply is sent by the receiving endpoint.
</li>

</ul>

</p>

<h4><a name=3D"operation.reply">4.7</a>&nbsp;The Reply Operation</h4>

<p>
While processing operations,
the service may respond with a "reply" element.
Consult Sections 10.2 and 6.1.2 of <a href=3D"#IMXP-CORE">[1]</a>,
respectively,
for the syntax and semantics of the reply operation.
</p>

<a name=3D"presence.definition"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>5.&nbsp;Registration: The Presence Service</h3>

<p>

<blockquote class=3D"text"><dl>

<dt>Well-Known Endpoint:</dt>
<dd>
imxp=3Dpresence
</dd>

<dt>Syntax of Messages Exchanged:</dt>
<dd>
c.f.,
<a href=3D"#imxp-presence.dtd">The Presence Service DTD</a>
</dd>

<dt>Sequence of Messages Exchanged:</dt>
<dd>
c.f.,
<a href=3D"#service.presence">The Presence Service</a>
</dd>

<dt>Access Control Tokens:</dt>
<dd>
presence:subscribe,
presence:watch, presence:publish
</dd>

<dt>Contact Information:</dt>
<dd>
c.f., the "Authors' Addresses"
section of this memo
</dd>

</dl></blockquote>

</p>

<a name=3D"imxp-presence.dtd"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>6.&nbsp;The Presence Service DTD</h3>
</font><pre>
&lt;!--
  DTD for the IMXP presence service, as of 2000-06-11


  Refer to this DTD as:

    &lt;!ENTITY % IMXPPRESENCE PUBLIC "-//Blocks//DTD IMXP PRESENCE//EN"
           "http://xml.resource.org/profiles/IMXP/imxp-presence.dtd">
    %IMXPPRESENCE;
  -->=20


&lt;!ENTITY % IMXPCORE PUBLIC "-//Blocks//DTD IMXP CORE//EN"
           "http://xml.resource.org/profiles/IMXP/imxp-core.dtd">
%IMXPCORE;


&lt;!--
  Synopsis of the IMXP presence service

    service WKE: imxp=3Dpresence

    message exchanges:

        consumer initiates    service replies
        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D    =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
        subscribe             publish or reply
        terminate             reply
        watch                 reply
        publish               reply

        service initiates     consumer replies
        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D     =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
        terminate             (nothing)
        publish               (nothing)
        notify                (nothing)


    access control:

        token                 target
        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D    =
=3D=3D=3D=3D=3D=3D
        presence:subscribe    for "publisher" of "subscribe" element
        presence:watch        for "publisher" of "watch" element
        presence:publish      for "publisher" of "publish" element
  -->


&lt;!ELEMENT subscribe   EMPTY>
&lt;!ATTLIST subscribe
          publisher   %ENDPOINT;        #REQUIRED
          transID     %UNIQID;          #REQUIRED
          duration    %SECONDS;         #REQUIRED>

&lt;!ELEMENT watch       EMPTY>
&lt;!ATTLIST watch
          publisher   %ENDPOINT;        #REQUIRED
          transID     %UNIQID;          #REQUIRED
          duration    %SECONDS;         #REQUIRED>


&lt;!-- publisher attributes must match in publish and presence -->

&lt;!ELEMENT publish     (presence)>
&lt;!ATTLIST publish
          publisher   %ENDPOINT;        #REQUIRED
          transID     %UNIQID;          #REQUIRED
          timeStamp   %TIMESTAMP;       #REQUIRED>
   =20
&lt;!ELEMENT notify      EMPTY>
&lt;!ATTLIST notify
          subscriber  %ENDPOINT;        #REQUIRED
          transID     %UNIQID;          #REQUIRED>


&lt;!--
  presence entries
  -->
   =20
&lt;!ELEMENT presence    (tuple+)>
&lt;!ATTLIST presence
          publisher   %ENDPOINT;        #REQUIRED
          lastUpdate  %TIMESTAMP;       #REQUIRED
          publisherInfo
                      %URI;             "">=20
   =20
&lt;!ELEMENT tuple       (capability*)>
&lt;!ATTLIST tuple
          destination %URI;             #REQUIRED
          availableUntil
                      %TIMESTAMP;       #REQUIRED
          tupleInfo %URI;               "">=20

&lt;!-- e.g., baseline=3D'rfc2533' -->
&lt;!ELEMENT capability (#PCDATA)*>
&lt;!ATTLIST capability
          baseline    NMTOKEN           #REQUIRED>

</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">
<a name=3D"rfc.references"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>
References</h3>
<table width=3D"99%" border=3D"0">
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"IMXP-CORE">[1]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, <a href=3D"mailto:gk@acm.org">Klyne, G.</a> and <a =
href=3D"mailto:dcrocker@brandenburg.com">D.H. Crocker</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-mrose-imxp-core-01.txt"=
>The IMXP</a>", draft-mrose-imxp-core-01 (work in progress), September =
2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"BEEP-FRAMEWORK">[2]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-beep-framework-02.=
txt">The Blocks Extensible Exchange Protocol Framework</a>", =
draft-ietf-beep-framework-02 (work in progress), September =
2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"IM-COMMON">[3]</a></b></td>
<td class=3D"author-text"><a =
href=3D"mailto:dcrocker@brandenburg.com">Crocker, D.H.</a>, <a =
href=3D"mailto:thanos@networkprojects.com">Diacakis, A.</a>, <a =
href=3D"mailto:flo@networkprojects.com">Mazzoldi, F.</a>, <a =
href=3D"mailto:huitema@microsoft.com">Huitema, C.</a>, <a =
href=3D"mailto:gk@acm.org">Klyne, G.</a>, <a =
href=3D"mailto:mrose@invisible.net">Rose, M.T.</a>, <a =
href=3D"mailto:jdrosen@dynamicsoft.com">Rosenberg, J.</a>, <a =
href=3D"mailto:rsparks@dynamicsoft.com">Sparks, R.</a> and <a =
href=3D"mailto:suga@flab.fujitsu.co.jp">H. Sugano</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-thenine-im-common-00.tx=
t">A Common Profile for Instant Messaging (CPIM)</a>", =
draft-thenine-im-common-00 (work in progress), August 2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"IMXP-ACCESS">[4]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, <a href=3D"mailto:gk@acm.org">Klyne, G.</a> and <a =
href=3D"mailto:dcrocker@brandenburg.com">D.H. Crocker</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-mrose-imxp-access-01.tx=
t">The IMXP Access Service</a>", draft-mrose-imxp-access-01 (work in =
progress), September 2000.</td></tr>
</table>

<a name=3D"rfc.authors"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Authors' Addresses</h3>
<table width=3D"99%" border=3D"0" cellpadding=3D"0" cellspacing=3D"0">
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Marshall T. Rose</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Invisible Worlds, Inc.</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">1179 North McDowell Boulevard</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Petaluma, CA  94954-6559</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">US</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+1 707 789 3700</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:mrose@invisible.net">mrose@invisible.net</a></td></tr>
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"http://invisible.net/">http://invisible.net/</a></td></tr>
<tr cellpadding=3D"3"><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Graham Klyne</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Content Technologies Limited</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">1220 Parkview</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Arlington Business Park</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Theale, Reading  RG7 4SA</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">UK</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+44 118 930 1300</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:gk@acm.org">gk@acm.org</a></td></tr>
<tr cellpadding=3D"3"><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">David H. Crocker</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Brandenburg Consulting</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">675 Spruce Drive</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Sunnyvale, CA  94086</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">US</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+1 408 246 8253</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:dcrocker@brandenburg.com">dcrocker@brandenburg.com</a></td=
></tr>
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"http://www.brandenburg.com/">http://www.brandenburg.com/</a></td>=
</tr>
</table>

<a name=3D"cpim.mapping"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix A.&nbsp;Mapping for the CPIM Presence Service</h3>

<p>
IMXP to CPIM Presence Information:
</p>
</font><pre>
CPIM presence             IMXP presence
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
entityInfo                publisherInfo
tuple->destination        tuple->destination
tuple->status             if currentTime >=3D tuple->lastUpdate
                             then 'closed' else 'open'
tuple content             tuple->tupleInfo
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">
<br>
<br>

<p>
CPIM to IMXP Presence Information:
</p>
</font><pre>
IMXP presence             CPIM presence
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
publisher                 notify->target
lastUpdate                currentTime
publisherInfo             empty
tuple->destination        tuple->destination
tuple->availableUntil     if status =3D 'closed'
                             then currentTime else muchLater
tuple->tupleInfo          empty
tuple content             empty
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">
<br>
<br>

<p>
Requesting a Subscription:
</p>
</font><pre>
CPIM subscribe            IMXP subscribe
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
watcher                   data->originator
target                    publisher
duration                  duration
transID                   transID
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">
<br>
<br>

<p>
Transmitting Presence Information:
</p>
</font><pre>
CPIM notify               IMXP publish
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
watcher                   data->originator
target                    publisher
transID                   transID
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">
<br>
<br>

<p>
Terminating a Subscription:
</p>
</font><pre>
CPIM unsubscribe          IMXP terminate
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
watcher                   data->originator
target                    stateful lookup based on transID
transID                   transID
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<a name=3D"anchor8"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix B.&nbsp;Changes from draft-mrose-imxp-presence-00</h3>

<p>

<ul class=3D"text">

<li>
<a href=3D"#cpim.mapping">Mapping for the CPIM Presence Service</a> =
added to harmonize with the
<a href=3D"#IM-COMMON">CPIM specification</a>[3].
</li>

<li>
The "mailbox" elements in the presence information are now called
"tuple" elements.
</li>

<li>
Updated to reflect the current
<a href=3D"#BEEP-FRAMEWORK">BEEP framework</a>[2].
</li>

</ul>

</p>

<a name=3D"anchor9"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix C.&nbsp;Acknowledgements</h3>

<p>
The authors gratefully acknowledge the contributions of:
Darren New
and
Scott Pead.
</p>
<a name=3D"rfc.copyright"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Full Copyright Statement</h3>
<p class=3D'copyright'>
Copyright (C) The Internet Society (2000). All Rights Reserved.</p>
<p class=3D'copyright'>
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.</p>
<p class=3D'copyright'>
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.</p>
<p class=3D'copyright'>
This document and the information contained herein is provided on an
&quot;AS IS&quot; basis and THE INTERNET SOCIETY AND THE INTERNET =
ENGINEERING
TASK FORCE DISCLAIMS 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.</p>
<h3>Acknowledgement</h3>
<p class=3D'copyright'>
Funding for the RFC editor function is currently provided by the
Internet Society.</p>
</font></body></html>

------=_NextPart_000_009A_01C02287.4D97D7A0
Content-Type: text/html;
	name="imxp-core.html"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="imxp-core.html"

<html><head><title>The IMXP</title>
<STYLE type=3D'text/css'>
    .title { color: #990000; font-size: 22px; line-height: 22px; =
font-weight: bold; text-align: right;
             font-family: helvetica, arial, sans-serif }
    .filename { color: #666666; font-size: 18px; line-height: 28px; =
font-weight: bold; text-align: right;
                  font-family: helvetica, arial, sans-serif }
    p.copyright { color: #000000; font-size: 10px;
                  font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    p { margin-left: 2em; margin-right: 2em; }
    ol { margin-left: 2em; margin-right: 2em; }
    ul.text { margin-left: 2em; margin-right: 2em; }
    pre { margin-left: 3em; color: #333333 }
    ul.toc { color: #000000; line-height: 16px;
             font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    H3 { color: #333333; font-size: 16px; line-height: 16px; =
font-family: helvetica, arial, sans-serif }
    H4 { color: #000000; font-size: 14px; font-family: helvetica, arial, =
sans-serif }
    TD.header { color: #ffffff; font-size: 10px; font-family: arial, =
helvetica, san-serif; valign: top }
    TD.author-text { color: #000000; font-size: 10px;
                     font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    TD.author { color: #000000; font-weight: bold; margin-left: 4em; =
font-size: 10px; font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    A:link { color: #990000; font-size: 10px; text-transform: uppercase; =
font-weight: bold;
             font-family: MS Sans Serif, verdana, charcoal, helvetica, =
arial, sans-serif }
    A:visited { color: #333333; font-weight: bold; font-size: 10px; =
text-transform: uppercase;
                font-family: MS Sans Serif, verdana, charcoal, =
helvetica, arial, sans-serif }
    A:name { color: #333333; font-weight: bold; font-size: 10px; =
text-transform: uppercase;
             font-family: MS Sans Serif, verdana, charcoal, helvetica, =
arial, sans-serif }
    .link2 { color:#ffffff; font-weight: bold; text-decoration: none;
             font-family: monaco, charcoal, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
             font-size: 9px }
    .RFC { color:#666666; font-weight: bold; text-decoration: none;
           font-family: monaco, charcoal, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
           font-size: 9px }
    .hotText { color:#ffffff; font-weight: normal; text-decoration: =
none;
               font-family: charcoal, monaco, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
               font-size: 9px }
</style>
</head>
<body bgcolor=3D"#ffffff"text=3D"#000000" alink=3D"#000000" =
vlink=3D"#666666" link=3D"#990000">
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<table width=3D"66%" border=3D"0" cellpadding=3D"0" =
cellspacing=3D"0"><tr><td><table width=3D"100%" border=3D"0" =
cellpadding=3D"2" cellspacing=3D"1">
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Network Working Group</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">M.T. Rose</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Internet-Draft</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">Invisible Worlds, Inc.</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Expires: March 20, 2001</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">G. Klyne</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Content Technologies Limited</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">D.H. Crocker</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Brandenburg Consulting</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">September 19, 2000</td></tr>
</table></td></tr></table>
<div align=3D"right"><font face=3D"monaco, MS Sans Serif" =
color=3D"#990000" size=3D"+3"><b><br><span class=3D"title">The =
IMXP</span></b></font></div>
<div align=3D"right"><font face=3D"monaco, MS Sans Serif" =
color=3D"#666666" size=3D"+2"><b><span =
class=3D"filename">draft-mrose-imxp-core-01</span></b></font></div>
<font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<h3>Status of this Memo</h3>
<p>
This document is an Internet-Draft and is in full conformance with all =
provisions of Section 10 of RFC2026.</p>
<p>
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups.
Note that other groups may also distribute working documents as
Internet-Drafts.</p>
<p>
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any =
time.
It is inappropriate to use Internet-Drafts as reference material or to =
cite
them other than as "work in progress."</p>
<p>
The list of current Internet-Drafts can be accessed at
<a =
href=3D'http://www.ietf.org/ietf/1id-abstracts.txt'>http://www.ietf.org/i=
etf/1id-abstracts.txt</a>.</p>
<p>
The list of Internet-Draft Shadow Directories can be accessed at
<a =
href=3D'http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html<=
/a>.</p>
<p>
This Internet-Draft will expire on March 20, 2001.</p>

<h3>Copyright Notice</h3>
<p>
Copyright (C) The Internet Society (2000). All Rights Reserved.</p>

<h3>Abstract</h3>

<p>
This memo describes IMXP,
an extensible,
asynchronous message relaying service for application layer
programs.
</p>
<a name=3D"toc"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Table of Contents</h3>
<ul compact class=3D"toc">
<b><a href=3D"#anchor1">1.</a>&nbsp;
Introduction<br></b>
<b><a href=3D"#anchor2">1.1</a>&nbsp;
Overview<br></b>
<b><a href=3D"#anchor3">1.2</a>&nbsp;
Architecture at a Glance<br></b>
<b><a href=3D"#anchor4">2.</a>&nbsp;
Service Principles<br></b>
<b><a href=3D"#anchor5">2.1</a>&nbsp;
Modes of Operation<br></b>
<b><a href=3D"#anchor6">2.2</a>&nbsp;
Naming of Entities<br></b>
<b><a href=3D"#imxp.provisioning">3.</a>&nbsp;
Service Provisioning<br></b>
<b><a href=3D"#anchor7">3.1</a>&nbsp;
Connection Establishment<br></b>
<b><a href=3D"#anchor8">3.2</a>&nbsp;
Authentication<br></b>
<b><a href=3D"#anchor9">3.3</a>&nbsp;
Authorization<br></b>
<b><a href=3D"#anchor10">3.4</a>&nbsp;
Confidentiality<br></b>
<b><a href=3D"#anchor11">3.5</a>&nbsp;
Routing Integrity<br></b>
<b><a href=3D"#anchor12">3.6</a>&nbsp;
Traffic Analysis<br></b>
<b><a href=3D"#imxp.profile">4.</a>&nbsp;
The IMXP<br></b>
<b><a href=3D"#imxp.xml-and-mime">4.1</a>&nbsp;
Use of XML and MIME<br></b>
<b><a href=3D"#anchor13">4.2</a>&nbsp;
Profile Identification and Initialization<br></b>
<b><a href=3D"#anchor14">4.3</a>&nbsp;
Message Syntax<br></b>
<b><a href=3D"#imxp.messages">4.4</a>&nbsp;
Message Semantics<br></b>
<b><a href=3D"#operation.attach">4.4.1</a>&nbsp;
The Attach Operation<br></b>
<b><a href=3D"#anchor15">4.4.2</a>&nbsp;
The Terminate Operation<br></b>
<b><a href=3D"#operation.data">4.4.3</a>&nbsp;
The Data Operation<br></b>
<b><a href=3D"#relay.data">4.4.3.1</a>&nbsp;
Relay Processing of Data<br></b>
<b><a href=3D"#appl.data">4.4.3.2</a>&nbsp;
Application Processing of Data<br></b>
<b><a href=3D"#imxp.access">4.5</a>&nbsp;
IMXP Access Policies<br></b>
<b><a href=3D"#imxp.options">5.</a>&nbsp;
IMXP Options<br></b>
<b><a href=3D"#option.statusRequest">5.1</a>&nbsp;
The statusRequest Option<br></b>
<b><a href=3D"#imxp.services">6.</a>&nbsp;
IMXP Services<br></b>
<b><a href=3D"#anchor16">6.1</a>&nbsp;
Use of the IMXP Core DTD<br></b>
<b><a href=3D"#anchor17">6.1.1</a>&nbsp;
Transaction-Identifiers<br></b>
<b><a href=3D"#operation.reply">6.1.2</a>&nbsp;
The Reply Operation<br></b>
<b><a href=3D"#service.report">6.2</a>&nbsp;
The Report Service<br></b>
<b><a href=3D"#imxp.reply-codes">7.</a>&nbsp;
IMXP Reply Codes<br></b>
<b><a href=3D"#option.registration">8.</a>&nbsp;
IMXP Option Registration Template<br></b>
<b><a href=3D"#service.registration">9.</a>&nbsp;
IMXP Service Registration Template<br></b>
<b><a href=3D"#anchor18">10.</a>&nbsp;
Initial Registrations<br></b>
<b><a href=3D"#imxp.definition">10.1</a>&nbsp;
Registration: The IMXP Profile<br></b>
<b><a href=3D"#imxp-core.dtd">10.2</a>&nbsp;
The IMXP Core DTD<br></b>
<b><a href=3D"#imxp-gstn.definition">10.3</a>&nbsp;
Registration: The IMXP Service-Selector for GSTN<br></b>
<b><a href=3D"#statusRequest.definition">10.4</a>&nbsp;
Registration: The statusRequest Option<br></b>
<b><a href=3D"#report.definition">10.5</a>&nbsp;
Registration: The Report Service<br></b>
<b><a href=3D"#imxp-report.dtd">10.6</a>&nbsp;
The Report Service DTD<br></b>
<b><a href=3D"#security">11.</a>&nbsp;
Security Considerations<br></b>
<b><a href=3D"#anchor19">12.</a>&nbsp;
IANA Considerations<br></b>
<b><a href=3D"#rfc.references">&#167;</a>&nbsp;
References<br></b>
<b><a href=3D"#rfc.authors">&#167;</a>&nbsp;
Authors' Addresses<br></b>
<b><a href=3D"#anchor20">A.</a>&nbsp;
Changes from draft-mrose-imxp-core-00<br></b>
<b><a href=3D"#anchor21">B.</a>&nbsp;
Acknowledgements<br></b>
<b><a href=3D"#rfc.copyright">&#167;</a>&nbsp;
Full Copyright Statement<br></b>
</ul>
<br clear=3D"all">

<a name=3D"anchor1"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>1.&nbsp;Introduction</h3>

<p>
Network applications can be broadly distinguished by five
operational characteristics:

<ul class=3D"text">

<li>
server push or client pull;
</li>

<li>
synchronous (interactive)
or asynchronous (batch);
</li>

<li>
time-assured or time-insensitive;
</li>

<li>
best-effort or reliable; and,
</li>

<li>
stateful or stateless.
</li>

</ul>

For example:

<ul class=3D"text">

<li>
the world-wide web is a pull, synchronous, time-insensitive, reliable,
stateless service; whilst
</li>

<li>
Internet mail is a push, asynchronous, time-insensitive,
best-effort (without DSN), stateless service.
</li>

</ul>

</p>

<p>
Messaging applications vary considerably in their operational
requirements.
For example,
some messaging applications require assurance of timeliness and =
reliability,
whilst others do not.
</p>

<p>
These features come at a cost,
in terms of both infrastructural and configuration complexity.
Accordingly,
the underlying service must be extensible to support different
requirements in a consistent manner.
</p>

<p>
This memo defines a core messaging service that supports a range
of operational characteristics.
The core service supports a variety of tailored services for both
user-based and programmatic exchanges.
</p>

<p>

</p>

<h4><a name=3D"anchor2">1.1</a>&nbsp;Overview</h4>

<p>
IMXP provides an extensible,
asynchronous message relaying service for application layer programs.
</p>

<p>
IMXP,
at its core,
provides a best-effort datagram service.
Each datagram,
simply termed "data",
is originated and received by IMXP "endpoints" --
applications that dynamically attach to the IMXP "relaying mesh".
</p>

<p>
The data transmitted specifies:

<ul class=3D"text">

<li>
an originating endpoint;
</li>

<li>
an opaque content (via a URI-reference);
</li>

<li>
one or more recipient endpoints; and,
</li>

<li>
zero or more options.
</li>

</ul>

Options are used to alter the semantics of the the service,
may occur on a per-recipient or per-data basis,
and may be processed by either a single or multiple relays.
</p>

<p>
Additional IMXP services are provided on top of the relaying mesh;
e.g., access control and presence information.
Typically these services are provided by servers that are
co-resident with one or more relays within an administrative domain.
</p>

<p>
IMXP is specified as a <a href=3D"#BEEP-FRAMEWORK">BEEP</a>[1] =
"profile".
Accordingly,
many aspects of IMXP (e.g., authentication) are provided within the
BEEP framework.
Throughout this memo,
the terms "peer", "initiator", "listener", "client", and "server" are
used in the context of BEEP.
In particular,
Section 2.1 of the BEEP framework memo discusses the roles that a BEEP
peer may perform.
</p>

<p>
When reading this memo,
note that the terms "endpoint" and "relay" are specific to IMXP,
they do not exist in the context of BEEP.
</p>

<h4><a name=3D"anchor3">1.2</a>&nbsp;Architecture at a Glance</h4>

<p>
The IMXP stack:
</p>
</font><pre>
   +-------------+
   | IMXP        |        an IMXP process is either:
   |     process |
   +-------------+            - an application attached as an IMXP
   |             |              endpoint; or,
   |    IMXP     |
   |             |            - an IMXP relay
   +-------------+
   |             |        IMXP services are realized as applications
   |    BEEP     |        having a special relationship with the IMXP
   |             |        relays in their administrative domain
   +-------------+
   |   TCP/IP    |
   +-------------+
   |     ...     |
   +-------------+
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>

</p>

<p>
The IMXP entities:
</p>
</font><pre>
       administrative domain #1          administrative domain #2
    +----------------------------+    +----------------------------+
    |   +------+                 |    |                 +------+   |
    |   |      |                 |    |                 |      |   |
    |   | appl |                 |    |                 | appl |   |
    |   |      |                 |    |                 |      |   |
    |   +......+       +------+  |    |  +------+       +......+   |
    |   |      |       |      |  |    |  |      |       |      |   |
    |   |end-  |       |relay |  |    |  |relay |       |end-  |   |
    |   | point|       |      |  |    |  |      |       | point|   |
    |   +------+       +------+  |    |  +------+       +------+   |
    |   |      |       |      |  |    |  |      |       |      |   |
    |   | IMXP |       | IMXP |  |    |  | IMXP |       | IMXP |   |
    |   |      |       |      |  |    |  |      |       |      |   |
    |   +------+       +------+  |    |  +------+       +------+   |
    |   |      |       |      |  |    |  |      |       |      |   |
    |   | BEEP |       | BEEP |  |    |  | BEEP |       | BEEP |   |
    |   |      |       |      |  |    |  |      |       |      |   |
    |   +------+       +------+  |    |  +------+       +------+   |
    |        ||         ||  ||   |    |   ||  ||         ||        |
    |        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D  =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D  =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D        |
    +----------------------------+    +----------------------------+

                   | &lt;---- IMXP relaying mesh ----> |



        Note: routing between administrative domains is configured
              using SRV RRs.  Accordingly, the actual number of
              relays between two endpoints is not fixed.
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<a name=3D"anchor4"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>2.&nbsp;Service Principles</h3>

<h4><a name=3D"anchor5">2.1</a>&nbsp;Modes of Operation</h4>

<p>
IMXP is used in two modes:

<blockquote class=3D"text"><dl>

<dt>endpoint-relay:</dt>
<dd>

in which the endpoint is always the BEEP initiator of the service,
whilst relays are always the BEEP listeners.
In this context,
applications attach as endpoints,
and then the transmission of data occurs.
</dd>

<dt>relay-relay:</dt>
<dd>

in which relays typically,
though not necessarily,
reside in different administrative domains.
In this context,
only the transmission of data occurs.
</dd>

</dl></blockquote>

</p>

<p>
In the endpoint-relay mode,
an endpoint (BEEP initiator) may:

<ul class=3D"text">

<li>
attach as one or more endpoints;
</li>

<li>
send data to other endpoints;
</li>

<li>
receive data from other endpoints; and,
</li>

<li>
terminate any of its attachments.
</li>

</ul>

A relay (BEEP listener),
in addition to servicing requests from a BEEP initiator, may:

<ul class=3D"text">

<li>
terminate any of the endpoint's attachments;
</li>

<li>
deliver data from other endpoints; and,
</li>

<li>
indicate the delivery status of data sent earlier by the endpoint.
</li>

</ul>

</p>

<p>
In the relay-relay mode,
the BEEP initiators and listeners transmit data on behalf of
endpoints.
</p>

<p>

</p>

<h4><a name=3D"anchor6">2.2</a>&nbsp;Naming of Entities</h4>

<p>
Endpoints are named using the "addr-spec" syntax of
<a href=3D"#RFC0822">RFC 822</a>[2],
i.e., "local@domain".
</p>

<p>
Using the service-selector convention of
<a href=3D"#RFC2846">RFC 2846</a>[3],
all endpoint identities having a local-part starting with "imxp=3D" are
reserved for use by IMXP services registered with the IANA.
</p>

<p>
Relays,
although not named,
belong to an administrative domain,
as identified by a FQDN,
e.g., "example.com".
</p>

<p>
In IMXP,
the "endpoint" is the fundamental entity.
IMXP is carried over BEEP,
which has the "peer" as its fundamental entity.
The relationship between BEEP peer entities and IMXP endpoint entities
are defined by IMXP's <a href=3D"#imxp.access">Access Policies</a>.
</p>

<a name=3D"imxp.provisioning"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>3.&nbsp;Service Provisioning</h3>

<h4><a name=3D"anchor7">3.1</a>&nbsp;Connection Establishment</h4>

<p>
The <a href=3D"#RFC2782">SRV algorithm</a>[4] is used to
determine the IP address and TCP port number assigned to a relay for
an administrative domain:

<blockquote class=3D"text"><dl>

<dt>service:</dt>
<dd>
"imxp-edge" (for the endpoint-relay mode),
or "imxp-mesh" (for the relay-relay mode);
</dd>

<dt>protocol:</dt>
<dd>
"tcp"; and,
</dd>

<dt>domain:</dt>
<dd>
the administrative domain.
</dd>

</dl></blockquote>

</p>

<h4><a name=3D"anchor8">3.2</a>&nbsp;Authentication</h4>

<p>
Authentication is a matter of provisioning for each BEEP peer
(c.f., <a href=3D"#imxp.access">IMXP Access Policies</a>).
</p>

<p>
An IMXP relay might be provisioned to allow a BEEP peer identity to
coincide with a given endpoint identity.
For example,
a relay in the "example.com" administrative domain may be configured
to allow a BEEP peer identified as "fred@example.com" to be authorized
to attach as the IMXP endpoint "fred@example.com".
</p>

<h4><a name=3D"anchor9">3.3</a>&nbsp;Authorization</h4>

<p>
Authorization is a matter of provisioning for each BEEP peer
(c.f., <a href=3D"#imxp.access">IMXP Access Policies</a>).
</p>

<p>
Typically,
a relay requires that its BEEP peer authenticate as a prelude to
authorization,
but an endpoint usually does not require the same of its BEEP peer.
</p>

<h4><a name=3D"anchor10">3.4</a>&nbsp;Confidentiality</h4>

<p>
Confidentiality is a matter of provisioning for each BEEP peer.
</p>

<p>
Typically,
any data considered sensitive by an originating endpoint will have its
content encrypted for the intended recipient endpoint(s),
rather than relying on hop-by-hop encryption.
Similarly,
an originating endpoint will sign the content if end-to-end
authentication is desired.
</p>

<p>

</p>

<h4><a name=3D"anchor11">3.5</a>&nbsp;Routing Integrity</h4>

<p>
Data are routed according to SRV entries in the DNS.
Accordingly,
routing integrity is a function of the DNS and the applications making
use of the DNS.
Additional assurance is provided if the BEEP initiator requires that
the BEEP listener authenticate itself.
</p>

<h4><a name=3D"anchor12">3.6</a>&nbsp;Traffic Analysis</h4>

<p>
Hop-by-hop protection of data transmitted through the relaying mesh
(endpoint identities and content) is afforded at the BEEP level
through the use of a transport security profile.
Other traffic characteristics,
e.g., volume and timing of transmissions,
is not protected from third-party analysis.
</p>

<a name=3D"imxp.profile"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>4.&nbsp;The IMXP</h3>

<p>
<a href=3D"#imxp.definition">Registration: The IMXP Profile</a> contains =
the BEEP profile
registration for IMXP.
</p>

<h4><a name=3D"imxp.xml-and-mime">4.1</a>&nbsp;Use of XML and MIME</h4>

<p>
Each BEEP payload exchanged via IMXP consists of an XML document and
possibly an arbitrary MIME content.
</p>

<p>
If only an XML document is sent in the BEEP payload,
then the mapping to a BEEP payload is straight-forward,
e.g.,
</p>
</font><pre>
    C: MSG 1 2 . 111 27
    C: Content-Type: text/xml
    C:=20
    C: &lt;terminate transID=3D'1' />
    C: END
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
Otherwise,
if an arbitrary MIME content is present,
it is indicated by a <a href=3D"#RFC2396">URI-reference</a>[5]
in the XML control document.
The URI-reference may contain an absolute-URI
(and possibly a fragment-identifier),
or it may be a relative-URI consisting only of a fragment-identifier.
Arbitrary MIME content is included in the BEEP payload by using a
<a href=3D"#RFC2387">"multipart/related"</a>[6],
identified using a <a href=3D"#RFC2392">"cid" URL</a>[7],
and the XML control document occurs as the start of the =
"multipart/related",
e.g.,
</p>
</font><pre>   =20
    C: MSG 1 1 . 42 1234
    C: Content-Type: multipart/related; boundary=3D"boundary";
    C:               start=3D"&lt;1@example.com>";
    C:               type=3D"text/xml"
    C:=20
    C: --boundary
    C: Content-Type: text/xml
    C: Content-ID: &lt;1@example.com>
    C:=20
    C: &lt;data originator=3D'fred@example.com'
    C:       content=3D'cid:2@example.com'>
    C:     &lt;recipient identity=3D'barney@example.com' />
    C: &lt;/data>
    C: --boundary
    C: Content-Type: image/gif
    C: Content-Transfer-Encoding: binary
    C: Content-ID: &lt;2@example.com>
    C:=20
    C: ...
    C: --boundary--
    C: END
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
Because BEEP provides an 8bit-wide path, a "transformative"
Content-Transfer-Encoding
(e.g., "base64" or "quoted-printable")
should not be used.
Further,
note that <a href=3D"#RFC2045">MIME</a>[8] requires that the value
of the "Content-ID" header be globally unique.
</p>

<p>
If the arbitrary MIME content is itself an XML document,
it may be contained with the control document directly,
and identified using a URI-reference consisting of only a
fragment-identifier,
e.g.,
</p>
</font><pre>   =20
    C: MSG 1 1 . 42 283
    C: Content-Type: text/xml
    C:=20
    C: &lt;data originator=3D'fred@example.com' content=3D'#Content'>
    C:     &lt;recipient identity=3D'barney@example.com' />
    C:     &lt;data-content Name=3D'Content'>
    C:         &lt;statusResponse transID=3D'86'>
    C:             &lt;destination identity=3D'barney@example.com'>
    C:                 &lt;reply code=3D'250' />
    C:             &lt;/destination>
    C:         &lt;statusResponse>
    C:     &lt;/data-content>
    C: &lt;/data>
    C: END
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>

</p>

<h4><a name=3D"anchor13">4.2</a>&nbsp;Profile Identification and =
Initialization</h4>

<p>
The IMXP is identified as
</p>
</font><pre>
    http://xml.resource.org/profiles/IMXP
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
in the BEEP "profile" element during channel creation.
</p>

<p>
No elements are required to be exchanged during channel creation;
however, in the endpoint-relay mode,
the BEEP initiator will typically include an "attach" element during
channel creation, e.g.,
</p>
</font><pre>
    &lt;start number=3D'1'>
        &lt;profile uri=3D'http://xml.resource.org/profiles/IMXP'>
            &lt;![CDATA[&lt;attach transID=3D'1'>
                &lt;recipient identity=3D'fred@example.com' />
            &lt;/attach>]]&gt;
        &lt;/profile>
    &lt;/start>
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<h4><a name=3D"anchor14">4.3</a>&nbsp;Message Syntax</h4>

<p>
<a href=3D"#imxp-core.dtd">The IMXP Core DTD</a> defines the BEEP =
payloads that are
used in the IMXP.
</p>

<p>

</p>

<h4><a name=3D"imxp.messages">4.4</a>&nbsp;Message Semantics</h4>

<h4><a name=3D"operation.attach">4.4.1</a>&nbsp;The Attach =
Operation</h4>

<p>
When an application wants to attach to the relaying mesh as a given
endpoint,
it sends an "attach" element to a relay,
e.g.,
</p>
</font><pre>
    +-------+                  +-------+
    |       | -- attach -----> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;attach transID=3D'1'>
  C:     &lt;recipient identity=3D'fred@example.com' />
  C: &lt;/attach>
  S: &lt;ok />

or

    +-------+                  +-------+
    |       | -- attach -----> |       |
    |       |                  |       |
    |       | &lt;--------- ok -- |       |
    | appl. |                  | relay |
    |       | -- attach -----> |       |
    |       |                  |       |
    |       | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;attach transID=3D'1'>
  C:     &lt;recipient identity=3D'fred@example.com' />
  C: &lt;/attach>
  S: &lt;ok />
  C: &lt;attach transID=3D'2'>
  C:     &lt;recipient identity=3D'wilma@example.com' />
  C: &lt;/attach>
  S: &lt;ok />











or

    +-------+                  +-------+
    |       | -- attach -----> |       |
    | appl. |                  | relay |
    |       | &lt;------ error -- |       |
    +-------+                  +-------+

  C: &lt;attach transID=3D'1'>
  C:     &lt;recipient identity=3D'fred@example.com' />
  C: &lt;/attach>
  S: &lt;error code=3D'537'>access denied&lt;/error>
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
The "attach" element has a "transID" attribute,
and contains a "recipient" element,
which,
in turn,
has an "identity" attribute and contains zero or more "option" elements:

<ul class=3D"text">

<li>
the "transID" attribute specifies the transaction-identifier
associated with this operation;
</li>

<li>
the "identity" attribute specifies the desired endpoint; and,
</li>

<li>
the "option" elements,
if any,
specify additional processing options
(<a href=3D"#imxp.options">IMXP Options</a>).
</li>

</ul>

</p>

<p>
When a relay receives an "attach" element,
it performs these steps:

<ol class=3D"text">

<li>
If the transaction-identifier refers to a previous attach operation
on this BEEP channel (that has not yet been terminated),
an "error" element having code 555 is returned.
</li>

<li>
If the relay is in a different administrative domain than this endpoint,
an "error" element having code 553 is returned.
</li>

<li>
If the application is not authorized to attach as this endpoint,
an "error" element having code 537 is returned.
</li>

<li>
If any options are present,
they are examined.
</li>

<li>
If another application has already attached as this endpoint,
an "error" element having code 554 is returned.
</li>

<li>
Otherwise,
the application is bound as this endpoint,
and an "ok" element is returned.
</li>

</ol>

</p>

<p>

</p>

<h4><a name=3D"anchor15">4.4.2</a>&nbsp;The Terminate Operation</h4>

<p>
When an application or relay wants to detach an endpoint,
it sends a "terminate" element,
e.g.,
</p>
</font><pre>   =20
    +-------+                  +-------+
    |       | -- terminate --> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;terminate transID=3D'1' />
  S: &lt;ok />

or

    +-------+                  +-------+
    |       | -- terminate --> |       |
    | appl. |                  | relay |
    |       | &lt;------ error -- |       |
    +-------+                  +-------+

  C: &lt;terminate transID=3D'13' />
  S: &lt;error code=3D'550'>unknown transaction-identifier&lt;/error>

or

    +-------+                  +-------+
    |       | &lt;-- terminate -- |       |
    | appl. |                  | relay |
    |       | -- ok ---------> |       |
    +-------+                  +-------+

  C: &lt;terminate transID=3D'1' />
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
The "terminate" element has a "transID" attribute
that specifies the transaction-identifier associated a previous
attach operation, and has no content.
</p>

<p>
When an application or relay receives a "terminate" element,
it performs these steps:

<ol class=3D"text">

<li>
If the transaction-identifier does not refer to a previous attach
operation on this BEEP channel (that has not yet been terminated),
an "error" element having code 550 is returned.
</li>

<li>
Otherwise,
the application is no longer bound as the corresponding endpoint,
and an "ok" element is returned.
</li>

</ol>

</p>

<h4><a name=3D"operation.data">4.4.3</a>&nbsp;The Data Operation</h4>

<p>
When an application or relay wants to transmit data over the
relaying mesh,
it sends a "data" element,
e.g.,
</p>
</font><pre>
    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |   #1  | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' =
content=3D'cid:1@example.com'>
         &lt;recipient identity=3D'barney@example.com' />
     &lt;/data>
  S: &lt;ok />

or

    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |   #1  | &lt;------ error -- |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' =
content=3D'cid:1@example.com'>
         &lt;recipient identity=3D'barney@example.com' />
     &lt;/data>
  S: &lt;error code=3D'450'>barney@example.com not attached&lt;/error>

or

                               +-------+                  +-------+
                               |       | -- data -------> |       |
                               | relay |                  | appl. |
                               |       | &lt;--------- ok -- |   #2  |
                               +-------+                  +-------+
   =20
  C: &lt;data originator=3D'fred@example.com' =
content=3D'cid:1@example.com'>
         &lt;recipient identity=3D'barney@example.com' />
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>

</p>

<p>
The "data" element has an "originator" and a "content" attribute,
and contains one or more "recipient" elements,
zero or more "option" elements,
and, optionally, a "data-content" element:

<ul class=3D"text">

<li>
the "originator" attribute specifies the endpoint sending the
data;
</li>

<li>
the "content" attribute is a URI-reference that specifies the
contents of the data
(c.f., <a href=3D"#imxp.xml-and-mime">Use of XML and MIME</a>);
</li>

<li>
each "recipient" element refers to an endpoint destination for the
data;
</li>

<li>
the "option" elements,
if any,
specify additional processing options
(<a href=3D"#imxp.options">IMXP Options</a>),
termed per-data options; and,
</li>

<li>
the "data-content" element,
if present,
specifies a nested XML entity using a URI fragment-identifier as the
value of the "content" attribute.
</li>

</ul>

Each "recipient" element has an "identity" attribute,
and contains zero or more option elements:

<ul class=3D"text">

<li>
the "identity" attribute specifies the destination endpoint;
and
</li>

<li>
the "option" elements,
if any,
specify additional processing options for this recipient,
termed per-recipient options.
</li>

</ul>

</p>

<p>

</p>

<h4><a name=3D"relay.data">4.4.3.1</a>&nbsp;Relay Processing of =
Data</h4>

<p>
When a relay receives a "data" element,
it performs these steps:

<ol class=3D"text">

<li>
If the BEEP client is not authorized to originate or relay data on
behalf of the "originator" endpoint,
an "error" element having code 537 is returned.
</li>

<li>
If any per-data options are present,
they are examined.
</li>

<li>
For each recipient:

<ol class=3D"text">

<li>
If any per-recipient options are present,
they are examined.
</li>

<li>
If the recipient endpoint is not in the administrative domain
associated with the relay,
then an IMXP session is established to a relay that accepts data for
the recipient's administrative domain,=20
and a new "data" element,
containing only that "recipient" element (and all applicable options),
is sent to that relay.
<br>
<br>

If no errors
(e.g., an IMXP session can not be established)
occur during processing,
and if the recipient's relay returns an "ok" element,
then the recipient is considered to be successfully processed.
</li>

<li>
Otherwise,
the IMXP access service must allow the originator endpoint to
communicate with the recipient endpoint
(the recipient's <a href=3D"#IMXP-ACCESS">access entry</a>[9] must =
contain
a "core:data" token for the originator),
and the recipient endpoint must be currently attached.
<br>
<br>

If so,
a new "data" element,
containing only that "recipient" element (and no options),
is sent to the corresponding application,
and the recipient is considered to be successfully processed.
</li>

</ol>

</li>

<li>
If no recipients could be successfully processed,
an "error" element is returned;
otherwise,
an "ok" element is returned.
</li>

</ol>

Note that an implementation may choose to optimize its behavior by
grouping multiple recipients in a single "data" element that is
subsequently transmitted.
It may do so providing that the optimization retains these semantics
and any other semantics related to per-data and per-recipient options.
</p>

<p>
Finally,
note that a relay receiving a "data" element from an application may
be configured to add domain-specific options.
</p>

<p>

</p>

<h4><a name=3D"appl.data">4.4.3.2</a>&nbsp;Application Processing of =
Data</h4>

<p>
When an application receives a "data" element,
it performs these steps:

<ol class=3D"text">

<li>
If any per-data options are present,
they are not processed (but may be noted).
</li>

<li>
For each recipient:

<ol class=3D"text">

<li>
If any per-recipient options are present,
they are not processed (but may be noted).
</li>

<li>
If the application is not attached as the recipient endpoint,
then an error in processing has occurred.
</li>

<li>
Otherwise,
the "data" element is further processed in an application-specific =
manner,
and the recipient is considered to be successfully processed.
</li>

</ol>

</li>

<li>
If no recipients could be successfully processed,
an "error" element is returned;
otherwise,
an "ok" element is returned.
</li>

</ol>

</p>

<p>

</p>

<h4><a name=3D"imxp.access">4.5</a>&nbsp;IMXP Access Policies</h4>

<p>
Access to IMXP is provided by the juxtaposition of:

<ul class=3D"text">

<li>
authenticating as a BEEP peer;
</li>

<li>
attaching as an IMXP endpoint; and,
</li>

<li>
being listed as an actor by the IMXP access service
(c.f., <a href=3D"#IMXP-ACCESS">[9]</a>).
</li>

</ul>

Each of these activities occurs according to the policies of the
relevant administrative domain:

<ul class=3D"text">

<li>
each administrative domain is responsible for keeping its own house in
order through "local provisioning"; and,
</li>

<li>
each administrative domain decides the level of trust to associate
with other administrative domains.
</li>

</ul>

</p>

<p>

</p>

<p>
IMXP access policies are used in these contexts:

<ul class=3D"text">

<li>
In the endpoint-relay mode,
when an application wishes to attach to the relaying mesh,
local provisioning maps BEEP peer identities to allowed IMXP endpoints
(c.f., Step 3 of <a href=3D"#operation.attach">The Attach =
Operation</a>).
<br>
<br>

Typically,
the identity function is used,
e.g.,
if an application authenticates itself
as the BEEP peer named as "fred@example.com",
it is allowed to attach
as the IMXP endpoint named as "fred@example.com".
<br>
<br>

Using the subaddress-specification convention of <a =
href=3D"#RFC2846">RFC 2846</a>[3],
an application authorized to attach as a given IMXP endpoint is also
authorized to attach as any sub-address of that IMXP endpoint,
e.g., an application authorized to attach as the IMXP endpoint
"fred@example.com" is also authorized to attach as the IMXP endpoint
"fred/wb@example.com".
</li>

<li>
In the endpoint-relay mode,
when an application wishes to send data,
local provisioning maps attached endpoints to allowed originators
(c.f., Step 1 of <a href=3D"#relay.data">Relay Processing of Data</a>).
<br>
<br>

Typically,
the identity function is used,
e.g.,
if an application attaches as the IMXP endpoint named as =
"fred@example.com",
it is allowed to send data originating from the same IMXP endpoint.
However,
other policies are permissible,
for example,
the administrative domain may allow the application attached as the
IMXP endpoint named as "wilma@example.com" to send data originating
as either "wilma@example.com" or "fred@example.com".
</li>

<li>
In the relay-relay mode,
when a relay is sending data,
no access policies, per se, are applied.
</li>

<li>
In the relay-relay mode,
when a relay is receiving data,
local provisioning maps BEEP peer identities to allowed originators
(c.f., Step 1 of <a href=3D"#relay.data">Relay Processing of Data</a>).
<br>
<br>

Typically,
if a BEEP peer authenticates itself as being from the same
administrative domain as the originator of the data,
or if the BEEP peer authenticates itself as being from a "trusted"
intermediate relay,
then the data is accepted.
</li>

<li>
Finally,
when a relay is delivering to an endpoint within its own
administrative domain,
it consults the recipient's access entry looking for an entry having
the originator as an actor
(c.f., Step 3.3 of <a href=3D"#relay.data">Relay Processing of =
Data</a>).
</li>

</ul>

</p>

<a name=3D"imxp.options"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>5.&nbsp;IMXP Options</h3>

<p>
IMXP,
at its core,
provides a best-effort datagram service.
Options are used to alter the semantics of the core service.
</p>

<p>
The semantics of the IMXP "option" element are context-specific.
Accordingly,
the specification of an IMXP option must define:

<ul class=3D"text">

<li>
the identity of the option;
</li>

<li>
the context in which the option may appear;
</li>

<li>
what content, if any, is contained within the option; and,
</li>

<li>
the processing rules for the option.
</li>

</ul>

An <a href=3D"#option.registration">option registration template</a>
organizes this information.
</p>

<p>
An "option" element is contained within either a "data" element or
a "recipient" element,
either of which is termed the "containing element".
The "option" element has several attributes and contains arbitrary =
content:

<ul class=3D"text">

<li>
the "internal" and the "external" attributes,
exactly one of which is present,
uniquely identify the option;
</li>

<li>
the "targetHop" attribute specifies which relays should process the
option;
</li>

<li>
the "seeNoEvil" attribute specifies whether the option,
if unrecognized, may be safely ignored;
</li>

<li>
the "transID" attribute specifies a transaction-identifier for the
option; and,
</li>

<li>
the "localize" attribute,
if present,
specifies one or more language tokens,
each identifying a desirable language tag to be used if textual
diagnostics are returned to the originator.
</li>

</ul>

The value of the "internal" attribute is the IANA-registered name for
the option.
If the "internal" attribute is not present,
then the value of the "external" attribute is a URI or URI with a
fragment-identifier.
Note that a relative-URI value is not allowed.
</p>

<p>

</p>

<p>
The "targetHop" attribute specifies which relay(s) should
process the option:

<blockquote class=3D"text"><dl>

<dt>   this:</dt>
<dd>
the option applies to this relay,
and must be removed prior to transmitting the containing element.
</dd>

<dt>   final:</dt>
<dd>
the option applies to this relay,
only if the the relay is able to transmit the containing element
directly to the recipient.
</dd>

<dt>   all:</dt>
<dd>
the option applies to this relay and is
retained for the next.
</dd>

</dl></blockquote>

Note that a final relay does not remove any options as it transmits
the containing element directly to the recipient.
</p>

<p>
The "seeNoEvil" attribute specifies whether the relay
may ignore the option if it is unrecognized,
and is consulted only if the "targetHop" attribute indicates that the
option applies to that relay.
If the option applies,
and if the value of the "seeNoEvil" attribute is "false",
and if the relay does not "understand" the option,
then this is considered a processing error.
</p>

<p>

</p>

<h4><a name=3D"option.statusRequest">5.1</a>&nbsp;The statusRequest =
Option</h4>

<p>
<a href=3D"#statusRequest.definition">Registration: The statusRequest =
Option</a> contains the IMXP option
registration for the "statusRequest" option.
</p>

<p>
If this option is present,
then each applicable relay sends a "statusResponse" message to the
originator.
This is done by issuing a data operation
whose originator is the report service associated with the issuing =
relay,
whose recipient is the endpoint address of the "statusRequest"
originator,
and whose content is a "statusResponse" element.
</p>

<p>
A "statusRequest" option MUST NOT be present in any data operation
containing a "statusResponse" element.
</p>

<p>

</p>

<p>
Consider these examples:
</p>
</font><pre>
    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |   #1  | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' =
content=3D'cid:1@example.com'>
         &lt;recipient identity=3D'barney@example.com' />
         &lt;option internal=3D'statusRequest' targetHop=3D'final'
                 seeNoEvil=3D'false' transID=3D'86' />
     &lt;/data>
  S: &lt;ok />

                               +-------+                  +-------+
                               |       | -- data -------> |       |
                               | relay |                  | appl. |
                               |       | &lt;--------- ok -- |   #2  |
                               +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' =
content=3D'cid:1@example.com'>
         &lt;recipient identity=3D'barney@example.com' />
     &lt;/data>
  S: &lt;ok />

    +-------+                  +-------+
    |       | &lt;------- data -- |       |
    | appl. |                  | relay |
    |   #1  | -- ok ---------> |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dreport@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'fred@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;statusResponse transID=3D'86'>
                 &lt;destination identity=3D'barney@example.com'>
                     &lt;reply code=3D'250' />
                 &lt;/destination>
             &lt;statusResponse>
         &lt;/data-content>   =20
     &lt;/data>
  S: &lt;ok />






or

    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |   #1  |
    +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' =
content=3D'cid:1@example.com'>
         &lt;recipient identity=3D'barney@rubble.com' />
         &lt;option internal=3D'statusRequest' targetHop=3D'final'
                 seeNoEvil=3D'false' transID=3D'86' />
     &lt;/data>
  S: &lt;ok />
                               +-------+                  +-------+
                               |       | -- data -------> |       |
                               | relay |                  | relay |
                               |   #1  | &lt;------ error -- |   #2  |
                               +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' =
content=3D'cid:1@example.com'>
         &lt;recipient identity=3D'barney@rubble.com' />
         &lt;option internal=3D'statusRequest' targetHop=3D'final'
                 seeNoEvil=3D'false' transID=3D'86' />
     &lt;/data>
  S: &lt;error code=3D'550'>unknown endpoint identity&lt;/error>
 =20
    +-------+                  +-------+
    |       | &lt;------- data -- |       |
    | appl. |                  | relay |
    |       | -- ok ---------> |   #1  |
    +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dreport@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'fred@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;statusResponse transID=3D'86'>
                 &lt;destination identity=3D'barney@example.com'>
                     &lt;reply code=3D'550'>unknown endpoint
                                       identity&lt;/reply>
                 &lt;/destination>
             &lt;statusResponse>
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />







or   =20

    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |   #1  |
    +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' =
content=3D'cid:1@example.com'>
         &lt;recipient identity=3D'barney@rubble.com' />
         &lt;option internal=3D'statusRequest' targetHop=3D'final'
                 seeNoEvil=3D'false' transID=3D'86' />
     &lt;/data>
  S: &lt;ok />
                               +-------+                  +-------+
                               |       | -- data -------> |       |
                               | relay |                  | relay |
                               |   #1  | &lt;--------- ok -- |   #2  |
                               +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' =
content=3D'cid:1@example.com'>
         &lt;recipient identity=3D'barney@rubble.com' />
         &lt;option internal=3D'statusRequest' targetHop=3D'final'
                 seeNoEvil=3D'false' transID=3D'86' />
     &lt;/data>
  S: &lt;ok />
 =20
                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  | relay |
                               |   #1  | -- ok ---------> |   #2  |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Dreport@rubble.com' =
content=3D'#Content'>
          &lt;recipient identity=3D'fred@example.com' />
          &lt;data-content Name=3D'Content'>
              &lt;statusResponse transID=3D'86'>
              &lt;destination identity=3D'barney@rubble.com'>
                  &lt;reply code=3D'250' />
              &lt;/destination>
              &lt;statusResponse>
          &lt;/data-content>
      &lt;/data>
  S: &lt;ok />





    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |   #1  |
    +-------+                  +-------+
   =20
  C: &lt;data originator=3D'imxp=3Dreport@rubble.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'fred@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;statusResponse transID=3D'86'>
                 &lt;destination identity=3D'barney@rubble.com'>
                     &lt;reply code=3D'250' />
                 &lt;/destination>
             &lt;statusResponse>
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
Note that a trace of a data's passage through the relaying mesh
can be achieved by setting the "targetHop" attribute to "all".
</p>

<a name=3D"imxp.services"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>6.&nbsp;IMXP Services</h3>

<p>
IMXP,
at its core,
provides a best-effort datagram service.
Errors are reported through the use of a co-resident IMXP report =
service.
All other IMXP services are provided on top of the relaying mesh,
e.g.,
</p>
</font><pre>
   +----------+     +----------+    +----------+
   |   IMXP   |     |   IMXP   |    |          |
   |  access  |     | presence |    |   ...    |=20
   | service  |     | service  |    |          |=20
   +----------+     +----------+    +----------+
        |                |               |
        |                |               |
+------------------------------------------------+---------+
|                                                |  IMXP   |
|                    IMXP core                   |  report |
|                                                | service |
+------------------------------------------------+---------+
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
Applications communicate with IMXP services by sending data to a
"well-known endpoint" (WKE).
</p>

<p>
The specification of an IMXP service must define:

<ul class=3D"text">

<li>
the WKE of the service;
</li>

<li>
the syntax of messages exchanged with the service;
</li>

<li>
the sequence of messages exchanged with the service; and,
</li>

<li>
what access control tokens are consulted by the service.
</li>

</ul>

A <a href=3D"#service.registration">service registration template</a>
organizes this information.
</p>

<p>
Note that both the IMXP <a href=3D"#IMXP-ACCESS">access</a>[9] and
<a href=3D"#IMXP-PRESENCE">presence</a>[10] services are logically
layered above the IMXP core;
however,
implementers may choose to physically co-reside these services with
IMXP relay software.
</p>

<p>
Finally,
note that within a single administrative domain,
the relaying mesh makes use of the IMXP access service in order to
determine if an originator is allowed to transmit data to a recipient
(c.f., Step 3.3 of <a href=3D"#relay.data">Relay Processing of Data</a>)

</p>

<p>

</p>

<h4><a name=3D"anchor16">6.1</a>&nbsp;Use of the IMXP Core DTD</h4>

<p>
The specification of an IMXP service may use definitions found in the
IMXP <a href=3D"#imxp-core.dtd">core DTD</a>.
For example,
the <a href=3D"#operation.reply">reply operation</a> is defined
to provide a common format for responses.
</p>

<h4><a name=3D"anchor17">6.1.1</a>&nbsp;Transaction-Identifiers</h4>

<p>
In using IMXP's transaction-identifiers,
note the following:

<ul class=3D"text">

<li>
In the endpoint-relay mode,
transaction-identifiers are meaningful only during the lifetime of a
BEEP channel.
<br>
<br>

For example,
when an application issues the attach operation,
the associated transaction-identifier has meaning only within the
context of the BEEP channel used for the attach operation.
When the BEEP connection is released,
the channel no longer exists and the application is no longer attached
to the relaying mesh.
</li>

<li>
In contrast,
when an application communicates with an IMXP service,
transaction-identifiers are often embedded in the data that is sent.
This means that transaction-identifiers are potentially long-lived.
<br>
<br>

For example,
an application may attach as an endpoint,
send data (containing an embedded transaction-identifier) to a service,
and,
some time later,
detach from the relaying mesh.
Later on,
a second application may attach as the same endpoint,
and send data of its own (also containing embedded =
transaction-identifiers).
Subsequently,
the second application may receive data from the service responding to
the first application's request and containing the
transaction-identifier used by the first application.
</li>

</ul>

To minimize the likelihood of ambiguities with long-lived
transaction-identifiers,
the values of transaction-identifiers generated by applications should
appear to be unpredictable.
</p>

<p>

</p>

<h4><a name=3D"operation.reply">6.1.2</a>&nbsp;The Reply Operation</h4>

<p>
Many IMXP services make use of a reply operation.
Accordingly,
<a href=3D"#imxp-core.dtd">The IMXP Core DTD</a> contains a definition =
of a "reply" element
that can be used for this purpose.
</p>

<p>
The "reply" element has a "code" attribute,
a "transID" attribute,
an optional "xml:lang" attribute,
and may contain arbitrary textual content:

<ul class=3D"text">

<li>
the "code" element specifies a three-digit reply code
(c.f., <a href=3D"#imxp.reply-codes">IMXP Reply Codes</a>);
</li>

<li>
the "transID" attribute specifies the transaction-identifier
corresponding to this reply;
</li>

<li>
the "xml:lang" attribute,
if present,
specifies the language that the element's content is written in; and,
</li>

<li>
the textual content is a diagnostic (possibly multiline) which is
meaningful to implementers,
perhaps administrators,
and possibly even users.
</li>

</ul>

</p>

<p>

</p>

<h4><a name=3D"service.report">6.2</a>&nbsp;The Report Service</h4>

<p>
<a href=3D"#report.definition">Registration: The Report Service</a> =
contains the IMXP service
registration for the report service:

<ul class=3D"text">

<li>
Within an administrative domain,
the service is addressed using the well-known endpoint of
"imxp=3Dreport".
</li>

<li>
<a href=3D"#imxp-report.dtd">The Report Service DTD</a> defines the =
syntax of the
operations exchanged with the service.
</li>

<li>
A consumer of the service does not initiate communications with the
service.
</li>

<li>
The service initiates communications by sending data containing the
"statusResponse" operation.
</li>

</ul>

</p>

<p>
Unlike other IMXP services,
the report service is co-resident with the IMXP core -- the report =
service is
provided by each and every relay.
</p>

<p>
If a relay processes a
<a href=3D"#option.statusRequest">"statusRequest" option</a>,
then it sends data to the originator containing a
<a href=3D"#imxp-report.dtd">"statusResponse" element</a>.
</p>

<p>
The "statusResponse" element has a "transID" attribute and contains
one or more "destination" elements:

<ul class=3D"text">

<li>
the "transID" attribute specifies the value contained in the
"statusRequest" option; and,
</li>

<li>
each "destination" element has an "identity" attribute and contains
a "reply" element:

<ul class=3D"text">

<li>
the "identity" attribute specifies the recipient endpoint that is
being reported on; and,
</li>

<li>
the <a href=3D"#operation.reply">"reply" element</a>
specifies the delivery status of that recipient.
</li>

</ul>

</li>

</ul>

</p>

<a name=3D"imxp.reply-codes"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>7.&nbsp;IMXP Reply Codes</h3>
</font><pre>
code    meaning
=3D=3D=3D=3D    =3D=3D=3D=3D=3D=3D=3D
250     transaction successful

421     service not available

450     requested action not taken

451     requested action aborted

454     temporary authentication failure

500     general syntax error (e.g., poorly-formed XML)

501     syntax error in parameters (e.g., non-valid XML)=20

504     parameter not implemented

530     authentication required

534     authentication mechanism insufficient

535     authentication failure

537     action not authorized for user

538     authentication mechanism requires encryption

550     requested action not taken

553     parameter invalid

554     transaction failed (e.g., policy violation)

555     transaction already in progress
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<a name=3D"option.registration"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>8.&nbsp;IMXP Option Registration Template</h3>

<p>
When an IMXP option is registered,
the following information is supplied:

<blockquote class=3D"text"><dl>

<dt>Option Identification:</dt>
<dd>
specify the NMTOKEN or the URI
that authoritatively identifies this option.
</dd>

<dt>Present in:</dt>
<dd>
specify the IMXP elements in which the
option may appear.
</dd>

<dt>Contains:</dt>
<dd>
specify the XML content that is contained
within the "option" element.
</dd>

<dt>Processing Rules:</dt>
<dd>
specify the processing rules
associated with the option.
</dd>

<dt>Contact Information:</dt>
<dd>
specify the postal and electronic
contact information for the author of the profile.
</dd>

</dl></blockquote>

</p>

<a name=3D"service.registration"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>9.&nbsp;IMXP Service Registration Template</h3>

<p>
When an IMXP service is registered,
the following information is supplied:

<blockquote class=3D"text"><dl>

<dt>Well-Known Endpoint:</dt>
<dd>
specify the local-part of an
endpoint identity,
starting with "imxp=3D".
</dd>

<dt>Syntax of Messages Exchanged:</dt>
<dd>
specify the elements
exchanged with the service.
</dd>

<dt>Sequence of Messages Exchanged:</dt>
<dd>
specify the order in
which data is exchanged with the service.
</dd>

<dt>Access Control Tokens:</dt>
<dd>
specify the token(s) used to
control access to the service (c.f., <a href=3D"#IMXP-ACCESS">[9]</a>).
</dd>

<dt>Contact Information:</dt>
<dd>
specify the postal and electronic
contact information for the author of the profile.
</dd>

</dl></blockquote>

</p>

<a name=3D"anchor18"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>10.&nbsp;Initial Registrations</h3>

<h4><a name=3D"imxp.definition">10.1</a>&nbsp;Registration: The IMXP =
Profile</h4>

<p>

<blockquote class=3D"text"><dl>

<dt>Profile Identification:</dt>
<dd>
<a =
href=3D"http://xml.resource.org/profiles/IMXP">http://xml.resource.org/pr=
ofiles/IMXP</a>
</dd>

<dt>Messages exchanged during Channel Creation:</dt>
<dd>
"ready"
</dd>

<dt>Messages starting one-to-one exchanges:</dt>
<dd>
"attach", "terminate", or "data"
</dd>

<dt>Messages in positive replies:</dt>
<dd>
"ok"
</dd>

<dt>Messages in negative replies:</dt>
<dd>
"error"
</dd>

<dt>Messages in one-to-many exchanges:</dt>
<dd>
none
</dd>

<dt>Message Syntax:</dt>
<dd>
c.f., <a href=3D"#imxp-core.dtd">The IMXP Core DTD</a>
</dd>

<dt>Message Semantics:</dt>
<dd>
c.f., <a href=3D"#imxp.messages">Message Semantics</a>
</dd>

<dt>Contact Information:</dt>
<dd>
c.f., the "Authors' Addresses"
section of this memo
</dd>

</dl></blockquote>

</p>

<p>

</p>

<h4><a name=3D"imxp-core.dtd">10.2</a>&nbsp;The IMXP Core DTD</h4>
</font><pre>
&lt;!--
  DTD for the IMXP core, as of 2000-09-19


  Refer to this DTD as:

    &lt;!ENTITY % IMXPCORE PUBLIC "-//Blocks//DTD IMXP CORE//EN"
               "http://xml.resource.org/profiles/IMXP/imxp-core.dtd">
    %IMXPCORE;
  -->=20


&lt;!ENTITY % IMCOMMON PUBLIC "-//Blocks//DTD IM COMMON//EN"
           "http://xml.resource.org/syntaxes/IM/im-common.dtd">
%IMCOMMON;


&lt;!--
  DTD data types:

       entity        syntax/reference     example
       =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D     =
=3D=3D=3D=3D=3D=3D=3D
    IMXP endpoint
       ENDPOINT      addr-spec,            fred@example.com
                     c.f., [RFC-0822]    =20

    zero or more language tags
        LOCS         NMTOKENS              "en-US"

    a 3-digit reply code
        XYZ           [1-5][1-9][1-9]      500
  -->

&lt;!ENTITY  % ENDPOINT  "CDATA">
&lt;!ENTITY % LOCS       "NMTOKEN">
&lt;!ENTITY  % XYZ       "CDATA">




   =20






&lt;!--
  BEEP profile http://xml.resource.org/profiles/IMXP
 =20
     role       MSG         RSP         ERR
    =3D=3D=3D=3D=3D=3D      =3D=3D=3D         =3D=3D=3D         =
=3D=3D=3D
      I         attach      ok          error=20

    I or L      terminate   ok          error=20

    I or L      data        ok          error=20
  -->


&lt;!ELEMENT attach      (recipient,option*)>
&lt;!ATTLIST attach
          transID     %UNIQID;          #REQUIRED>


&lt;!ELEMENT terminate   EMPTY>
&lt;!ATTLIST terminate
          transID     %UNIQID;          #REQUIRED>


&lt;!ELEMENT data        (recipient+,option*,data-content?)>
&lt;!ATTLIST data
          originator  %ENDPOINT;        #REQUIRED
          content     %URI;             #REQUIRED>
   =20
&lt;!ELEMENT recipient   (option*)>
&lt;!ATTLIST recipient
          identity    %ENDPOINT;        #REQUIRED>

&lt;!ELEMENT data-content
                      ANY>
&lt;!ATTLIST Name        ID                #REQUIRED>

&lt;!ELEMENT ok          EMPTY>

&lt;!ELEMENT error       (#PCDATA)*>
&lt;!ATTLIST error
          code        %XYZ;              #REQUIRED
          xml:lang    %LANG;             #IMPLIED>

&lt;!ELEMENT reply       (#PCDATA)*>
&lt;!ATTLIST reply
          code        %XYZ;             #REQUIRED
          transID     %UNIQID;          #REQUIRED
          xml:lang    %LANG;            #IMPLIED>

&lt;!-- either the "internal" or the "external" attribute is present in
     an option -->

&lt;!ELEMENT option      ANY>
&lt;!ATTLIST option
          internal    NMTOKEN           ""
          external    %URI;             ""
          targetHop   (this|final|all)  "final"
          seeNoEvil   (true|false)      "true"
          transID     %UNIQID;          #REQUIRED
          localize    %LOCS;            "i-default">

</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<h4><a name=3D"imxp-gstn.definition">10.3</a>&nbsp;Registration: The =
IMXP Service-Selector for GSTN</h4>

<p>

<blockquote class=3D"text"><dl>

<dt>Service-Selector Name:</dt>
<dd>
IMXP
</dd>

<dt>Description of Use:</dt>
<dd>
Specifies endpoints for registered
IMXP services on the host indicated by the address domain name,
c.f., <a href=3D"#imxp.services">IMXP Services</a>
</dd>

<dt>Security Considerations:</dt>
<dd>
The definition of a
service-related endpoint does not introduce security concerns, per se;
however,
because the defined endpoints are service control points,
the nature of messages sent to them may introduce security concerns
</dd>

<dt>Contact Information:</dt>
<dd>
c.f., the "Authors' Addresses"
section of this memo
</dd>

</dl></blockquote>

</p>

<h4><a name=3D"statusRequest.definition">10.4</a>&nbsp;Registration: The =
statusRequest Option</h4>

<p>

<blockquote class=3D"text"><dl>

<dt>Option Identification:</dt>
<dd>
statusRequest
</dd>

<dt>Present in:</dt>
<dd>
IMXP's "data" and "recipient" elements
</dd>

<dt>Contains:</dt>
<dd>
nothing
</dd>

<dt>Processing Rules:</dt>
<dd>
c.f.,
<a href=3D"#option.statusRequest">The statusRequest Option</a>
</dd>

<dt>Contact Information:</dt>
<dd>
specify the postal and electronic
contact information for the author of the feature.
</dd>

</dl></blockquote>

</p>

<h4><a name=3D"report.definition">10.5</a>&nbsp;Registration: The Report =
Service</h4>

<p>

<blockquote class=3D"text"><dl>

<dt>Well-Known Endpoint:</dt>
<dd>
imxp=3Dreport
</dd>

<dt>Syntax of Messages Exchanged:</dt>
<dd>
c.f.,
<a href=3D"#imxp-report.dtd">The Report Service DTD</a>
</dd>

<dt>Sequence of Messages Exchanged:</dt>
<dd>
c.f.,
<a href=3D"#service.report">The Report Service</a>
</dd>

<dt>Access Control Tokens:</dt>
<dd>
none
</dd>

<dt>Contact Information:</dt>
<dd>
specify the postal and electronic
contact information for the author of the feature.
</dd>

</dl></blockquote>

</p>

<p>

</p>

<h4><a name=3D"imxp-report.dtd">10.6</a>&nbsp;The Report Service =
DTD</h4>
</font><pre>
&lt;!--
  DTD for the IMXP report service, as of 2000-06-11


  Refer to this DTD as:

    &lt;!ENTITY % IMXPREPORT PUBLIC "-//Blocks//DTD IMXP REPORT//EN"
             "http://xml.resource.org/profiles/IMXP/imxp-report.dtd">
    %IMXPREPORT;
  -->=20


&lt;!ENTITY % IMXPCORE PUBLIC "-//Blocks//DTD IMXP CORE//EN"
           "http://xml.resource.org/profiles/IMXP/imxp-core.dtd">
%IMXPCORE;


&lt;!--
  Synopsis of the IMXP report service

    service WKE: imxp=3Dreport

    message exchanges:

        service initiates    consumer replies
        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D    =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
        statusResponse       (nothing)

    access control tokens: none
  -->


&lt;!ELEMENT statusResponse
                      (destination+)>
&lt;!ATTLIST statusResponse
          transID     %TRANSID;         #REQUIRED>

&lt;!ELEMENT destination (reply)>
&lt;!ATTLIST destination
          identity    %ENDPOINT;        #REQUIRED>

</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<a name=3D"security"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>11.&nbsp;Security Considerations</h3>

<p>
Consult <a href=3D"#imxp.provisioning">Service Provisioning</a> and
<a href=3D"#imxp.access">IMXP Access Policies</a> for a discussion of =
security issues,
e.g., routing integrity.
In addition,
since IMXP is a profile of the BEEP,
consult <a href=3D"#BEEP-FRAMEWORK">[1]</a>'s Section 8 for a discussion =
of
BEEP-specific security issues.
</p>

<p>
In addition,
the <a href=3D"#option.statusRequest">statusRequest option</a>
may be used to expose private network topology.
Accordingly,
administrators may wish to choose to disable this option except at the
ingress/egress points for their domain.
</p>

<a name=3D"anchor19"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>12.&nbsp;IANA Considerations</h3>

<p>
The IANA maintains a list of:

<ul class=3D"text">

<li>
IMXP options,
c.f., <a href=3D"#imxp.options">IMXP Options</a> and <a =
href=3D"#option.registration">IMXP Option Registration Template</a>;
and,
</li>

<li>
IMXP services,
c.f., <a href=3D"#imxp.services">IMXP Services</a> and
<a href=3D"#service.registration">IMXP Service Registration =
Template</a>.
</li>

</ul>

</p>

<p>
The IANA makes the registrations specified in=20
<a href=3D"#imxp.definition">Registration: The IMXP Profile</a>,
<a href=3D"#imxp-gstn.definition">Registration: The IMXP =
Service-Selector for GSTN</a>,
<a href=3D"#statusRequest.definition">Registration: The statusRequest =
Option</a>,
and
<a href=3D"#report.definition">Registration: The Report Service</a>.
</p>
<a name=3D"rfc.references"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>
References</h3>
<table width=3D"99%" border=3D"0">
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"BEEP-FRAMEWORK">[1]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-beep-framework-02.=
txt">The Blocks Extensible Exchange Protocol Framework</a>", =
draft-ietf-beep-framework-02 (work in progress), September =
2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC0822">[2]</a></b></td>
<td class=3D"author-text">Crocker, D., "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc822.txt">Standard for the format =
of ARPA Internet text messages</a>", RFC 822, STD 11, Aug =
1982.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC2846">[3]</a></b></td>
<td class=3D"author-text">Allocchio, C., "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc2846.txt">GSTN Address Element =
Extensions in E-mail Services</a>", RFC 2846, June 2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC2782">[4]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:arnt@troll.no">Gulbrandsen, =
A.</a>, <a href=3D"mailto:">Vixie, P.</a> and <a =
href=3D"mailto:levone@microsoft.com">L. Esibov</a>, "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc2782.txt">A DNS RR for specifying =
the location of services (DNS SRV)</a>", RFC 2782, February =
2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC2396">[5]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:timbl@w3.org">Berners-Lee, =
T.</a>, <a href=3D"mailto:fielding@ics.uci.edu">Fielding, R.T.</a> and =
<a href=3D"mailto:masinter@parc.xerox.com">L. Masinter</a>, "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc2396.txt">Uniform Resource =
Identifiers (URI): Generic Syntax</a>", RFC 2396, August 1998.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC2387">[6]</a></b></td>
<td class=3D"author-text"><a =
href=3D"mailto:XIson@cnj.digex.com">Levinson, E.</a>, "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc2387.txt">The MIME =
Multipart/Related Content-type</a>", RFC 2387, August 1998.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC2392">[7]</a></b></td>
<td class=3D"author-text"><a =
href=3D"mailto:XIson@cnj.digex.net">Levinson, E.</a>, "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc2392.txt">Content-ID and =
Message-ID Uniform Resource Locators</a>", RFC 2392, August =
1998.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC2045">[8]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:ned@innosoft.com">Freed, =
N.</a> and <a href=3D"mailto:nsb@nsb.fv.com">N. Borenstein</a>, "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc2045.txt">Multipurpose Internet =
Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>", =
RFC 2045, November 1996.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"IMXP-ACCESS">[9]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, <a href=3D"mailto:gk@acm.org">Klyne, G.</a> and <a =
href=3D"mailto:dcrocker@brandenburg.com">D.H. Crocker</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-mrose-imxp-access-01.tx=
t">The IMXP Access Service</a>", draft-mrose-imxp-access-01 (work in =
progress), September 2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"IMXP-PRESENCE">[10]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, <a href=3D"mailto:gk@acm.org">Klyne, G.</a> and <a =
href=3D"mailto:dcrocker@brandenburg.com">D.H. Crocker</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-mrose-imxp-presence-01.=
txt">The IMXP Presence Service</a>", draft-mrose-imxp-presence-01 (work =
in progress), September 2000.</td></tr>
</table>

<a name=3D"rfc.authors"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Authors' Addresses</h3>
<table width=3D"99%" border=3D"0" cellpadding=3D"0" cellspacing=3D"0">
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Marshall T. Rose</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Invisible Worlds, Inc.</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">1179 North McDowell Boulevard</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Petaluma, CA  94954-6559</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">US</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+1 707 789 3700</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:mrose@invisible.net">mrose@invisible.net</a></td></tr>
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"http://invisible.net/">http://invisible.net/</a></td></tr>
<tr cellpadding=3D"3"><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Graham Klyne</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Content Technologies Limited</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">1220 Parkview</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Arlington Business Park</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Theale, Reading  RG7 4SA</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">UK</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+44 118 930 1300</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:gk@acm.org">gk@acm.org</a></td></tr>
<tr cellpadding=3D"3"><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">David H. Crocker</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Brandenburg Consulting</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">675 Spruce Drive</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Sunnyvale, CA  94086</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">US</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+1 408 246 8253</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:dcrocker@brandenburg.com">dcrocker@brandenburg.com</a></td=
></tr>
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"http://www.brandenburg.com/">http://www.brandenburg.com/</a></td>=
</tr>
</table>

<a name=3D"anchor20"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix A.&nbsp;Changes from draft-mrose-imxp-core-00</h3>

<p>

<ul class=3D"text">

<li>
Updated to reflect the current
<a href=3D"#BEEP-FRAMEWORK">BEEP framework</a>[1].
</li>

<li>
Relaying options passed to,
but not interpreted by,
endpoints.
</li>

<li>
<a href=3D"#imxp.access">IMXP Access Policies</a> includes an explicit =
discussion of
sub-addreses.
</li>

</ul>

</p>

<a name=3D"anchor21"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix B.&nbsp;Acknowledgements</h3>

<p>
The authors gratefully acknowledge the contributions of:
Darren New
and
Scott Pead.
</p>
<a name=3D"rfc.copyright"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Full Copyright Statement</h3>
<p class=3D'copyright'>
Copyright (C) The Internet Society (2000). All Rights Reserved.</p>
<p class=3D'copyright'>
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.</p>
<p class=3D'copyright'>
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.</p>
<p class=3D'copyright'>
This document and the information contained herein is provided on an
&quot;AS IS&quot; basis and THE INTERNET SOCIETY AND THE INTERNET =
ENGINEERING
TASK FORCE DISCLAIMS 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.</p>
<h3>Acknowledgement</h3>
<p class=3D'copyright'>
Funding for the RFC editor function is currently provided by the
Internet Society.</p>
</font></body></html>

------=_NextPart_000_009A_01C02287.4D97D7A0
Content-Type: text/html;
	name="imxp-message.html"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="imxp-message.html"

<html><head><title>Use of IMXP to Provision Instant Messaging</title>
<STYLE type=3D'text/css'>
    .title { color: #990000; font-size: 22px; line-height: 22px; =
font-weight: bold; text-align: right;
             font-family: helvetica, arial, sans-serif }
    .filename { color: #666666; font-size: 18px; line-height: 28px; =
font-weight: bold; text-align: right;
                  font-family: helvetica, arial, sans-serif }
    p.copyright { color: #000000; font-size: 10px;
                  font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    p { margin-left: 2em; margin-right: 2em; }
    ol { margin-left: 2em; margin-right: 2em; }
    ul.text { margin-left: 2em; margin-right: 2em; }
    pre { margin-left: 3em; color: #333333 }
    ul.toc { color: #000000; line-height: 16px;
             font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    H3 { color: #333333; font-size: 16px; line-height: 16px; =
font-family: helvetica, arial, sans-serif }
    H4 { color: #000000; font-size: 14px; font-family: helvetica, arial, =
sans-serif }
    TD.header { color: #ffffff; font-size: 10px; font-family: arial, =
helvetica, san-serif; valign: top }
    TD.author-text { color: #000000; font-size: 10px;
                     font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    TD.author { color: #000000; font-weight: bold; margin-left: 4em; =
font-size: 10px; font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    A:link { color: #990000; font-size: 10px; text-transform: uppercase; =
font-weight: bold;
             font-family: MS Sans Serif, verdana, charcoal, helvetica, =
arial, sans-serif }
    A:visited { color: #333333; font-weight: bold; font-size: 10px; =
text-transform: uppercase;
                font-family: MS Sans Serif, verdana, charcoal, =
helvetica, arial, sans-serif }
    A:name { color: #333333; font-weight: bold; font-size: 10px; =
text-transform: uppercase;
             font-family: MS Sans Serif, verdana, charcoal, helvetica, =
arial, sans-serif }
    .link2 { color:#ffffff; font-weight: bold; text-decoration: none;
             font-family: monaco, charcoal, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
             font-size: 9px }
    .RFC { color:#666666; font-weight: bold; text-decoration: none;
           font-family: monaco, charcoal, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
           font-size: 9px }
    .hotText { color:#ffffff; font-weight: normal; text-decoration: =
none;
               font-family: charcoal, monaco, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
               font-size: 9px }
</style>
</head>
<body bgcolor=3D"#ffffff"text=3D"#000000" alink=3D"#000000" =
vlink=3D"#666666" link=3D"#990000">
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<table width=3D"66%" border=3D"0" cellpadding=3D"0" =
cellspacing=3D"0"><tr><td><table width=3D"100%" border=3D"0" =
cellpadding=3D"2" cellspacing=3D"1">
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Network Working Group</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">M.T. Rose</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Internet-Draft</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">Invisible Worlds, Inc.</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Expires: March 20, 2001</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">G. Klyne</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Content Technologies Limited</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">D.H. Crocker</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Brandenburg Consulting</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">September 19, 2000</td></tr>
</table></td></tr></table>
<div align=3D"right"><font face=3D"monaco, MS Sans Serif" =
color=3D"#990000" size=3D"+3"><b><br><span class=3D"title">Use of IMXP =
to Provision Instant Messaging</span></b></font></div>
<div align=3D"right"><font face=3D"monaco, MS Sans Serif" =
color=3D"#666666" size=3D"+2"><b><span =
class=3D"filename">draft-mrose-imxp-message-00</span></b></font></div>
<font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<h3>Status of this Memo</h3>
<p>
This document is an Internet-Draft and is in full conformance with all =
provisions of Section 10 of RFC2026.</p>
<p>
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups.
Note that other groups may also distribute working documents as
Internet-Drafts.</p>
<p>
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any =
time.
It is inappropriate to use Internet-Drafts as reference material or to =
cite
them other than as "work in progress."</p>
<p>
The list of current Internet-Drafts can be accessed at
<a =
href=3D'http://www.ietf.org/ietf/1id-abstracts.txt'>http://www.ietf.org/i=
etf/1id-abstracts.txt</a>.</p>
<p>
The list of Internet-Draft Shadow Directories can be accessed at
<a =
href=3D'http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html<=
/a>.</p>
<p>
This Internet-Draft will expire on March 20, 2001.</p>

<h3>Copyright Notice</h3>
<p>
Copyright (C) The Internet Society (2000). All Rights Reserved.</p>

<h3>Abstract</h3>

<p>
This memo describes how to use IMXP to provision an
instant messaging service.
</p>
<a name=3D"toc"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Table of Contents</h3>
<ul compact class=3D"toc">
<b><a href=3D"#anchor1">1.</a>&nbsp;
Introduction<br></b>
<b><a href=3D"#anchor2">2.</a>&nbsp;
Overview of the Instant Messaging Service<br></b>
<b><a href=3D"#anchor3">2.1</a>&nbsp;
Addressing of INSTANT INBOXes<br></b>
<b><a href=3D"#anchor4">2.2</a>&nbsp;
IMXP Access Policies<br></b>
<b><a href=3D"#anchor5">3.</a>&nbsp;
Format of Instant Messages<br></b>
<b><a href=3D"#anchor6">4.</a>&nbsp;
The Instant Messaging Service<br></b>
<b><a href=3D"#anchor7">4.1</a>&nbsp;
The Message Operation<br></b>
<b><a href=3D"#rfc.references">&#167;</a>&nbsp;
References<br></b>
<b><a href=3D"#rfc.authors">&#167;</a>&nbsp;
Authors' Addresses<br></b>
<b><a href=3D"#cpim.mapping">A.</a>&nbsp;
Mapping for the CPIM Instant Messaging Service<br></b>
<b><a href=3D"#anchor8">B.</a>&nbsp;
Acknowledgements<br></b>
<b><a href=3D"#rfc.copyright">&#167;</a>&nbsp;
Full Copyright Statement<br></b>
</ul>
<br clear=3D"all">

<a name=3D"anchor1"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>1.&nbsp;Introduction</h3>

<p>
This memo describes an instant messaging service that is built upon the
<a href=3D"#IMXP-CORE">IMXP</a>[1] "relaying mesh",
which,
in turn,
is specified as a <a href=3D"#BEEP-FRAMEWORK">BEEP</a>[2] profile.
</p>

<p>
IMXP,
at its core,
provides a best-effort datagram service.
Accordingly,
INSTANT INBOXes are realized as applications which attach to IMXP's
"relaying mesh",
and INSTANT MESSAGEs are sent as data between the applications.
</p>

<p>
Note that within a single administrative domain,
the IMXP
<a href=3D"#IMXP-ACCESS">access</a>[4] service determines
if an originator is allowed to send data (containing instant messages).
</p>

<p>
The instant messaging service described in this memo is compatible
with the <a href=3D"#IM-COMMON">Common Profile for Instant =
Messaging</a>[3].
Specifically,
<a href=3D"#cpim.mapping">Mapping for the CPIM Instant Messaging =
Service</a> defines a lossless mapping for the CPIM
instant messaging service.
</p>

<a name=3D"anchor2"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>2.&nbsp;Overview of the Instant Messaging Service</h3>

<h4><a name=3D"anchor3">2.1</a>&nbsp;Addressing of INSTANT INBOXes</h4>

<h4><a name=3D"anchor4">2.2</a>&nbsp;IMXP Access Policies</h4>

<a name=3D"anchor5"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>3.&nbsp;Format of Instant Messages</h3>

<a name=3D"anchor6"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>4.&nbsp;The Instant Messaging Service</h3>

<h4><a name=3D"anchor7">4.1</a>&nbsp;The Message Operation</h4>
<a name=3D"rfc.references"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>
References</h3>
<table width=3D"99%" border=3D"0">
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"IMXP-CORE">[1]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, <a href=3D"mailto:gk@acm.org">Klyne, G.</a> and <a =
href=3D"mailto:dcrocker@brandenburg.com">D.H. Crocker</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-mrose-imxp-core-01.txt"=
>The IMXP</a>", draft-mrose-imxp-core-01 (work in progress), September =
2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"BEEP-FRAMEWORK">[2]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-beep-framework-02.=
txt">The Blocks Extensible Exchange Protocol Framework</a>", =
draft-ietf-beep-framework-02 (work in progress), September =
2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"IM-COMMON">[3]</a></b></td>
<td class=3D"author-text"><a =
href=3D"mailto:dcrocker@brandenburg.com">Crocker, D.H.</a>, <a =
href=3D"mailto:thanos@networkprojects.com">Diacakis, A.</a>, <a =
href=3D"mailto:flo@networkprojects.com">Mazzoldi, F.</a>, <a =
href=3D"mailto:huitema@microsoft.com">Huitema, C.</a>, <a =
href=3D"mailto:gk@acm.org">Klyne, G.</a>, <a =
href=3D"mailto:mrose@invisible.net">Rose, M.T.</a>, <a =
href=3D"mailto:jdrosen@dynamicsoft.com">Rosenberg, J.</a>, <a =
href=3D"mailto:rsparks@dynamicsoft.com">Sparks, R.</a> and <a =
href=3D"mailto:suga@flab.fujitsu.co.jp">H. Sugano</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-thenine-im-common-00.tx=
t">A Common Profile for Instant Messaging (CPIM)</a>", =
draft-thenine-im-common-00 (work in progress), August 2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"IMXP-ACCESS">[4]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, <a href=3D"mailto:gk@acm.org">Klyne, G.</a> and <a =
href=3D"mailto:dcrocker@brandenburg.com">D.H. Crocker</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-mrose-imxp-access-01.tx=
t">The IMXP Access Service</a>", draft-mrose-imxp-access-01 (work in =
progress), September 2000.</td></tr>
</table>

<a name=3D"rfc.authors"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Authors' Addresses</h3>
<table width=3D"99%" border=3D"0" cellpadding=3D"0" cellspacing=3D"0">
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Marshall T. Rose</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Invisible Worlds, Inc.</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">1179 North McDowell Boulevard</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Petaluma, CA  94954-6559</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">US</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+1 707 789 3700</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:mrose@invisible.net">mrose@invisible.net</a></td></tr>
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"http://invisible.net/">http://invisible.net/</a></td></tr>
<tr cellpadding=3D"3"><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Graham Klyne</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Content Technologies Limited</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">1220 Parkview</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Arlington Business Park</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Theale, Reading  RG7 4SA</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">UK</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+44 118 930 1300</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:gk@acm.org">gk@acm.org</a></td></tr>
<tr cellpadding=3D"3"><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">David H. Crocker</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Brandenburg Consulting</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">675 Spruce Drive</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Sunnyvale, CA  94086</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">US</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+1 408 246 8253</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:dcrocker@brandenburg.com">dcrocker@brandenburg.com</a></td=
></tr>
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"http://www.brandenburg.com/">http://www.brandenburg.com/</a></td>=
</tr>
</table>

<a name=3D"cpim.mapping"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix A.&nbsp;Mapping for the CPIM Instant Messaging Service</h3>

<p>
IMXP to CPIM transmission:
</p>
</font><pre>
CPIM message              IMXP data
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
source                    originator
destination               recipient
transID                   generated at gateway=20
message content           data content
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">
<br>
<br>

<p>
CPIM to IMXP transmission:
</p>
</font><pre>
IMXP data                 CPIM message
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
orginator                 source
recipient                 destination
options                   empty
data content              message content=20
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<a name=3D"anchor8"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix B.&nbsp;Acknowledgements</h3>

<p>
tbd...
</p>
<a name=3D"rfc.copyright"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Full Copyright Statement</h3>
<p class=3D'copyright'>
Copyright (C) The Internet Society (2000). All Rights Reserved.</p>
<p class=3D'copyright'>
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.</p>
<p class=3D'copyright'>
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.</p>
<p class=3D'copyright'>
This document and the information contained herein is provided on an
&quot;AS IS&quot; basis and THE INTERNET SOCIETY AND THE INTERNET =
ENGINEERING
TASK FORCE DISCLAIMS 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.</p>
<h3>Acknowledgement</h3>
<p class=3D'copyright'>
Funding for the RFC editor function is currently provided by the
Internet Society.</p>
</font></body></html>

------=_NextPart_000_009A_01C02287.4D97D7A0
Content-Type: text/html;
	name="imxp-access.html"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="imxp-access.html"

<html><head><title>The IMXP Access Service</title>
<STYLE type=3D'text/css'>
    .title { color: #990000; font-size: 22px; line-height: 22px; =
font-weight: bold; text-align: right;
             font-family: helvetica, arial, sans-serif }
    .filename { color: #666666; font-size: 18px; line-height: 28px; =
font-weight: bold; text-align: right;
                  font-family: helvetica, arial, sans-serif }
    p.copyright { color: #000000; font-size: 10px;
                  font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    p { margin-left: 2em; margin-right: 2em; }
    ol { margin-left: 2em; margin-right: 2em; }
    ul.text { margin-left: 2em; margin-right: 2em; }
    pre { margin-left: 3em; color: #333333 }
    ul.toc { color: #000000; line-height: 16px;
             font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    H3 { color: #333333; font-size: 16px; line-height: 16px; =
font-family: helvetica, arial, sans-serif }
    H4 { color: #000000; font-size: 14px; font-family: helvetica, arial, =
sans-serif }
    TD.header { color: #ffffff; font-size: 10px; font-family: arial, =
helvetica, san-serif; valign: top }
    TD.author-text { color: #000000; font-size: 10px;
                     font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    TD.author { color: #000000; font-weight: bold; margin-left: 4em; =
font-size: 10px; font-family: verdana, charcoal, helvetica, arial, =
sans-serif }
    A:link { color: #990000; font-size: 10px; text-transform: uppercase; =
font-weight: bold;
             font-family: MS Sans Serif, verdana, charcoal, helvetica, =
arial, sans-serif }
    A:visited { color: #333333; font-weight: bold; font-size: 10px; =
text-transform: uppercase;
                font-family: MS Sans Serif, verdana, charcoal, =
helvetica, arial, sans-serif }
    A:name { color: #333333; font-weight: bold; font-size: 10px; =
text-transform: uppercase;
             font-family: MS Sans Serif, verdana, charcoal, helvetica, =
arial, sans-serif }
    .link2 { color:#ffffff; font-weight: bold; text-decoration: none;
             font-family: monaco, charcoal, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
             font-size: 9px }
    .RFC { color:#666666; font-weight: bold; text-decoration: none;
           font-family: monaco, charcoal, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
           font-size: 9px }
    .hotText { color:#ffffff; font-weight: normal; text-decoration: =
none;
               font-family: charcoal, monaco, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;
               font-size: 9px }
</style>
</head>
<body bgcolor=3D"#ffffff"text=3D"#000000" alink=3D"#000000" =
vlink=3D"#666666" link=3D"#990000">
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<table width=3D"66%" border=3D"0" cellpadding=3D"0" =
cellspacing=3D"0"><tr><td><table width=3D"100%" border=3D"0" =
cellpadding=3D"2" cellspacing=3D"1">
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Network Working Group</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">M.T. Rose</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Internet-Draft</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">Invisible Worlds, Inc.</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Expires: March 20, 2001</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">G. Klyne</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Content Technologies Limited</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">D.H. Crocker</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Brandenburg Consulting</td></tr>
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">September 19, 2000</td></tr>
</table></td></tr></table>
<div align=3D"right"><font face=3D"monaco, MS Sans Serif" =
color=3D"#990000" size=3D"+3"><b><br><span class=3D"title">The IMXP =
Access Service</span></b></font></div>
<div align=3D"right"><font face=3D"monaco, MS Sans Serif" =
color=3D"#666666" size=3D"+2"><b><span =
class=3D"filename">draft-mrose-imxp-access-01</span></b></font></div>
<font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<h3>Status of this Memo</h3>
<p>
This document is an Internet-Draft and is in full conformance with all =
provisions of Section 10 of RFC2026.</p>
<p>
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups.
Note that other groups may also distribute working documents as
Internet-Drafts.</p>
<p>
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any =
time.
It is inappropriate to use Internet-Drafts as reference material or to =
cite
them other than as "work in progress."</p>
<p>
The list of current Internet-Drafts can be accessed at
<a =
href=3D'http://www.ietf.org/ietf/1id-abstracts.txt'>http://www.ietf.org/i=
etf/1id-abstracts.txt</a>.</p>
<p>
The list of Internet-Draft Shadow Directories can be accessed at
<a =
href=3D'http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html<=
/a>.</p>
<p>
This Internet-Draft will expire on March 20, 2001.</p>

<h3>Copyright Notice</h3>
<p>
Copyright (C) The Internet Society (2000). All Rights Reserved.</p>

<h3>Abstract</h3>

<p>
This memo describes the IMXP access service,
addressed as the well-known endpoint "imxp=3Daccess".
The access service is used to control use of both the IMXP
"relaying mesh" and other IMXP services.
</p>
<a name=3D"toc"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Table of Contents</h3>
<ul compact class=3D"toc">
<b><a href=3D"#anchor1">1.</a>&nbsp;
Introduction<br></b>
<b><a href=3D"#anchor2">2.</a>&nbsp;
Management of Access Information<br></b>
<b><a href=3D"#anchor3">2.1</a>&nbsp;
Retrieval of Access Information<br></b>
<b><a href=3D"#anchor4">2.2</a>&nbsp;
Update of Access Information<br></b>
<b><a href=3D"#anchor5">3.</a>&nbsp;
Format of Access Entries<br></b>
<b><a href=3D"#service.access">4.</a>&nbsp;
The Access Service<br></b>
<b><a href=3D"#anchor6">4.1</a>&nbsp;
Use of XML and MIME<br></b>
<b><a href=3D"#operation.get">4.2</a>&nbsp;
The Get Operation<br></b>
<b><a href=3D"#operation.set">4.3</a>&nbsp;
The Set Operation<br></b>
<b><a href=3D"#operation.reply">4.4</a>&nbsp;
The Reply Operation<br></b>
<b><a href=3D"#access.definition">5.</a>&nbsp;
Registration: The Access Service<br></b>
<b><a href=3D"#imxp-access.dtd">6.</a>&nbsp;
The Access Service DTD<br></b>
<b><a href=3D"#rfc.references">&#167;</a>&nbsp;
References<br></b>
<b><a href=3D"#rfc.authors">&#167;</a>&nbsp;
Authors' Addresses<br></b>
<b><a href=3D"#anchor7">A.</a>&nbsp;
Changes from draft-mrose-imxp-access-00<br></b>
<b><a href=3D"#anchor8">B.</a>&nbsp;
Acknowledgements<br></b>
<b><a href=3D"#rfc.copyright">&#167;</a>&nbsp;
Full Copyright Statement<br></b>
</ul>
<br clear=3D"all">

<a name=3D"anchor1"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>1.&nbsp;Introduction</h3>

<p>
This memo describes a access service that is built upon the
<a href=3D"#IMXP-CORE">IMXP</a>[1] "relaying mesh",
which,
in turn,
is specified as a <a href=3D"#BEEP-FRAMEWORK">BEEP</a>[2] profile.
</p>

<p>
IMXP
at its core,
provides a best-effort datagram service.
With the exception of a co-resident IMXP report service
(used for error reporting),
all other IMXP services are provided on top of IMXP's "relaying mesh",
e.g.,
</p>
</font><pre>
   +----------+     +----------+    +----------+
   |   IMXP   |     |   IMXP   |    |          |
   |  access  |     | presence |    |   ...    |=20
   | service  |     | service  |    |          |=20
   +----------+     +----------+    +----------+
        |                |               |
        |                |               |
+------------------------------------------------+---------+
|                                                |  IMXP   |
|                    IMXP core                   |  report |
|                                                | service |
+------------------------------------------------+---------+
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
Applications communicate with IMXP services by sending data to a
"well-known endpoint" (WKE).
</p>

<p>
The IMXP access service is used to control use of both the relaying
mesh and other IMXP services.
Although the access service is logically layered above the IMXP core,
implementers may choose to physically co-reside the access service with
IMXP core software.
</p>

<p>
IMXP applications communicate with the access service by exchanging
data with the well-known endpoint "imxp=3Daccess" in the corresponding
administrative domain,
e.g., "imxp=3Daccess@example.com" is the endpoint associated with the
access service in the "example.com" administrative domain.
</p>

<p>
Note that within a single administrative domain,
the relaying mesh makes use of the IMXP access service in order to
determine if an originator is allowed to transmit data to a recipient
(c.f., Step 3.3 of Section 4.4.3.1 of <a href=3D"#IMXP-CORE">[1]</a>).
</p>

<a name=3D"anchor2"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>2.&nbsp;Management of Access Information</h3>

<p>
Management of access information falls into two categories:

<ul class=3D"text">

<li>
applications may retrieve the access entry associated with an
endpoint;
and,
</li>

<li>
applications may modify the access entry associated with an
endpoint.
</li>

</ul>

Each is now described in turn.
</p>

<p>

</p>

<h4><a name=3D"anchor3">2.1</a>&nbsp;Retrieval of Access =
Information</h4>

<p>
When an application wants to retrieve the access entry
associated with an endpoint,
it sends a "get" element to the service,
e.g.,
</p>
</font><pre>
    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' content=3D'#Content'>
         &lt;recipient identity=3D'imxp=3Daccess@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;get owner=3D'fred@example.com' transID=3D'1' />
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
The service immediately responds with a set operation
containing the access entry and the same transaction-identifier,
e.g.,
</p>
</font><pre>
                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  |access |
                               |       | -- ok ---------> |  svc. |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Daccess@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'fred@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;set owner=3D'fred@example.com' transID=3D'1'
                 timeStamp=3D'14 May 2000 13:32:00 -0800'>
                 &lt;access owner=3D'fred@example.com'
                         lastUpdate=3D'14 May 2000 13:02:00 -0800'>
                     &lt;entry actor=3D'*@example.com'
                            actions=3D'core:data presence:subscribe' />
                     &lt;entry actor=3D'*@*' actions=3D'core:data' />
                 &lt;/access>
             &lt;/set>
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<h4><a name=3D"anchor4">2.2</a>&nbsp;Update of Access Information</h4>

<p>
When an application wants to modify the access entry
associated with an endpoint,
it sends a "set" element to the service,
e.g.,
</p>
</font><pre>
    +-------+                  +-------+
    |       | -- data -------> |       |
    | appl. |                  | relay |
    |       | &lt;--------- ok -- |       |
    +-------+                  +-------+

  C: &lt;data originator=3D'fred@example.com' content=3D'#Content'>
         &lt;recipient identity=3D'imxp=3Daccess@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;set owner=3D'fred@example.com' transID=3D'1'
                 timeStamp=3D'14 May 2000 13:32:00 -0800'> ... &lt;/set>
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
The service immediately responds with a reply operation
containing the same transaction-identifier,
e.g.,
</p>
</font><pre>
                               +-------+                  +-------+
                               |       | &lt;------- data -- |       |
                               | relay |                  |access |
                               |       | -- ok ---------> |  svc. |
                               +-------+                  +-------+

  C: &lt;data originator=3D'imxp=3Daccess@example.com' =
content=3D'#Content'>
         &lt;recipient identity=3D'fred@example.com' />
         &lt;data-content Name=3D'Content'>
             &lt;reply code=3D'250' transID=3D'1' />
         &lt;/data-content>
     &lt;/data>
  S: &lt;ok />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<a name=3D"anchor5"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>3.&nbsp;Format of Access Entries</h3>

<p>
Each administrative domain is responsible for maintaining an
"access entry" for each of its endpoints
(regardless of whether those endpoints are currently attached to the
relaying mesh).
</p>

<p>
<a href=3D"#imxp-access.dtd">The Access Service DTD</a> defines the =
syntax for access entries.
Each access entry has an "owner" attribute,
a "lastUpdate" attribute,
and contains one or more "entry" elements:

<ul class=3D"text">

<li>
the "owner" attribute specifies the endpoint associated with the
access entry;
</li>

<li>
the "lastUpdate" attribute specifies the date and time that the
service last updated the access entry; and,
</li>

<li>
each "entry" element specifies,
with respect to the owner's endpoint,
an actor and zero or more allowed actions for that actor.
</li>

</ul>

Within an entry,
actions are specified as service/operation pairs,
(e.g., "presence:publish" refers to the "publish" operation of the
"presence" service).
To refer to all services and/or all operations,
the reserved value "all" is used
(e.g., "all:data", "presence:all", and so on).
Note that the service specified as "core" is reserved for use by the
relaying mesh,
e.g., the "core:data" action is consulted by the relaying mesh
(c.f., Step 3.3 of Section 4.4.3.1 of <a href=3D"#IMXP-CORE">[1]</a>).
</p>

<p>
An actor is an IMXP endpoint and is specified using the "addr-spec"
syntax of <a href=3D"#RFC0822">RFC 822</a>[3],
i.e., "local@domain".
However,
both the "local" and "domain" parts may contain limited wildcarding:

<ul class=3D"text">

<li>
The "local" part is either:

<ul class=3D"text">

<li>
a literal string (e.g., "fred"); or,
</li>

<li>
the value "imxp=3D*", specifying all IMXP services; or,
</li>

<li>
the value "*", specifying any endpoint other than an IMXP service.
</li>

</ul>

</li>

<li>
The "domain" part is either:

<ul class=3D"text">

<li>
a FQDN (e.g., "example.com"); or,
</li>

<li>
the value "*", specifying all administrative domains.
</li>

</ul>

</li>

</ul>

</p>

<p>
Regardless of the "entry" elements present in an access entry,
four additional elements are always considered to exist at the end
of the access entry:
</p>
</font><pre>
  &lt;entry actor=3D'imxp=3D*@domain' actions=3D'all:all' />
  &lt;entry actor=3D'imxp=3D*@*'      actions=3D'core:data' />
  &lt;entry actor=3D'local@domain'  actions=3D'all:all' />
  &lt;entry actor=3D'*@*'           actions=3D'' />
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
where "local@domain" specifies the endpoint associated with
the access entry.
</p>

<p>
Ordering of "entry" elements within an access element is
significant:
a process examining an access element selects the first "entry"
element that matches the actor in question.
For example,
consider this access entry:
</p>
</font><pre>
    &lt;access owner=3D'fred@example.com'
            lastUpdate=3D'14 May 2000 13:02:00 -0800'>
        &lt;entry actor=3D'wilma@example.com' actions=3D'all:all' />
        &lt;entry actor=3D'mr.slate@example.com' actions=3D'core:data' =
/>
        &lt;entry actor=3D'*@example.com'
             actions=3D'core:data presence:subscribe presence:watch' />
        &lt;entry actor=3D'*@*' actions=3D'core:data' />
    &lt;/access>
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<p>
Briefly:

<ul class=3D"text">

<li>
For endpoints within the "example.com" administrative domain:

<ul class=3D"text">

<li>
"fred", "wilma", and all IMXP services,
are allowed access to all operations for all IMXP services;
</li>

<li>
"mr.slate" is allowed access only to send data through the relaying
mesh; and,
</li>

<li>
any other endpoint is allowed access to send data and invoke the
"subscribe" and "watch" operations of the IMXP presence service.
</li>

</ul>

</li>

<li>
For any endpoint outside the "example.com" administrative domain,
the endpoint is allowed access to send data,
regardless of whether it is an IMXP service.
</li>

</ul>

Note that although the four additional elements are always present,
the ordering semantics cause the final element to be unused.
</p>

<a name=3D"service.access"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>4.&nbsp;The Access Service</h3>

<p>
<a href=3D"#access.definition">Registration: The Access Service</a> =
contains the IMXP service
registration for the access service:

<ul class=3D"text">

<li>
Within an administrative domain,
the service is addressed using the well-known endpoint of
"imxp=3Daccess".
</li>

<li>
<a href=3D"#imxp-access.dtd">The Access Service DTD</a> defines the =
syntax of the
operations exchanged with the service.
</li>

<li>
A consumer of the service initiates communications by sending data
containing either the get or set operation.
</li>

<li>
The service replies to these operations,
and does not initiate communications.
</li>

</ul>

</p>

<p>
An implementation of the service must maintain information about
access entries in persistent storage.
</p>

<p>
Consult Section 6.1.1 of <a href=3D"#IMXP-CORE">[1]</a> for a discussion =
on
the properties of long-lived transaction-identifiers.
</p>

<p>

</p>

<h4><a name=3D"anchor6">4.1</a>&nbsp;Use of XML and MIME</h4>

<p>
Section 4.1 of <a href=3D"#IMXP-CORE">[1]</a> describes how
arbitrary MIME content is exchanged as a BEEP payload.
For example,
to transmit:
</p>
</font><pre>
    &lt;data originator=3D'fred@example.com' content=3D'...'>
        &lt;recipient identity=3D'imxp=3Daccess@example.com' />
    &lt;/data>

where "..." refers to:

    &lt;get owner=3D'fred@example.com' transID=3D'1' />

then the corresponding BEEP operation might look like this:

    C: MSG 1 2 . 42 1234
    C: Content-Type: multipart/related; boundary=3D"boundary";
    C:               start=3D"&lt;1@example.com>";
    C:               type=3D"text/xml"
    C:=20
    C: --boundary
    C: Content-Type: text/xml
    C: Content-ID: &lt;1@example.com>
    C:=20
    C: &lt;data originator=3D'fred@example.com'
    C:       content=3D'cid:2@example.com'>
    C:     &lt;recipient identity=3D'imxp=3Daccess@example.com' />
    C: &lt;/data>
    C: --boundary
    C: Content-Type: text/xml
    C: Content-Transfer-Encoding: binary
    C: Content-ID: &lt;2@example.com>
    C:=20
    C: &lt;get owner=3D'fred@example.com' transID=3D'1' />
    C: --boundary--
    C: END

or this:

    C: MSG 1 1 . 42 255
    C: Content-Type: text/xml
    C:=20
    C: &lt;data originator=3D'fred@example.com' content=3D'#Content'>
    C:     &lt;recipient identity=3D'imxp=3Daccess@example.com' />
    C:     &lt;data-content Name=3D'Content'>
    C:         &lt;get owner=3D'fred@example.com' transID=3D'1' />
    C:     &lt;/data-content>
    C: &lt;/data>
    C: END
</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">

<h4><a name=3D"operation.get">4.2</a>&nbsp;The Get Operation</h4>

<p>
When an application wants to retrieve the access entry
associated with an endpoint,
it sends a "get" element to the service.
</p>

<p>
The "get" element has an "owner" attribute,
a "transID" attribute,
and no content:

<ul class=3D"text">

<li>
the "owner" attribute specifies the endpoint associated with the
access entry; and,
</li>

<li>
the "transID" attribute specifies the transaction-identifier
associated with this operation.
</li>

</ul>

</p>

<p>
When the service receives a "get" element,
we refer to the "owner" attribute of that element as the "subject",
and the service performs these steps:

<ol class=3D"text">

<li>
If the subject is outside of this administrative domain,
a "reply" element having code 553 is sent as data to the originator.
</li>

<li>
If the subject does not refer to a valid endpoint,
a "reply" element having code 550 is sent as data to the originator.
</li>

<li>
If the subject's access entry does not contain a "access:get" token
for the originator,
a "reply" element having code 537 is sent as data to the originator.
</li>

<li>
Otherwise,
a "set" element,
corresponding to the subject's access entry,
is sent as data to the originator.
</li>

</ol>

</p>

<p>
Regardless of whether a "set" or "reply" element is sent to the =
originator,
the "transID" attribute is identical to the value found in the "get"
element sent by the originator.
</p>

<p>

</p>

<h4><a name=3D"operation.set">4.3</a>&nbsp;The Set Operation</h4>

<p>
When an application wants to modify the access entry
associated with an endpoint,
it sends a "set" element to the service.
</p>

<p>
The "set" element has an "owner" attribute,
a "transID" attribute,
and contains an "access" element:

<ul class=3D"text">

<li>
the "owner" attribute specifies the endpoint to be associated with the
access entry;
</li>

<li>
the "transID" attribute specifies the transaction-identifier
associated with this operation;
</li>

<li>
the "timeStamp" attribute specifies the current date and time; and,
</li>

<li>
the "access" element contains the desired access entry for the
endpoint.
</li>

</ul>

</p>

<p>

</p>

<p>
When the service receives a "set" element,
we refer to the "owner" attribute of that element as the "subject",
and the service performs these steps:

<ol class=3D"text">

<li>
If the "owner" attribute of the "set" element doesn't match the
"owner" attribute of the "access" element contained in the "set" =
element,
a "reply" element having code 503 is sent as data to the originator.
</li>

<li>
If the subject is outside of this administrative domain,
a "reply" element having code 553 is sent as data to the originator.
</li>

<li>
If the subject does not refer to a valid endpoint,
a "reply" element having code 550 is sent as data to the originator.
</li>

<li>
If the subject's access entry does not contain a "access:set" token
for the originator,
a "reply" element having code 537 is sent as data to the originator.
</li>

<li>
If the "lastUpdate" attribute of the "set" element is not
semantically identical to the last update time of the subject's access
entry,
a "reply" element having code 555 is sent as data to the originator.
(This allows a basic mechanism for atomic updates.)
</li>

<li>
Otherwise:

<ol class=3D"text">

<li>
The subject's access entry is updated from the "set" element.
</li>

<li>
The last update time of the access entry is set to the current time.
</li>

<li>
A "reply" element having code 250 is sent as data to the originator.
</li>

</ol>

</li>

</ol>

</p>

<p>
When sending the "reply" element,
the "transID" attribute is identical to the value found in the "set"
element sent by the originator.
</p>

<p>

</p>

<h4><a name=3D"operation.reply">4.4</a>&nbsp;The Reply Operation</h4>

<p>
While processing operations,
the service may respond with a "reply" element.
Consult Sections 10.2 and 6.1.2 of <a href=3D"#IMXP-CORE">[1]</a>,
respectively,
for the syntax and semantics of the reply operation.
</p>

<a name=3D"access.definition"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>5.&nbsp;Registration: The Access Service</h3>

<p>

<blockquote class=3D"text"><dl>

<dt>Well-Known Endpoint:</dt>
<dd>
imxp=3Daccess
</dd>

<dt>Syntax of Messages Exchanged:</dt>
<dd>
c.f.,
<a href=3D"#imxp-access.dtd">The Access Service DTD</a>
</dd>

<dt>Sequence of Messages Exchanged:</dt>
<dd>
c.f.,
<a href=3D"#service.access">The Access Service</a>
</dd>

<dt>Access Control Tokens:</dt>
<dd>
access:get, access:set
</dd>

<dt>Contact Information:</dt>
<dd>
c.f., the "Authors' Addresses"
section of this memo
</dd>

</dl></blockquote>

</p>

<a name=3D"imxp-access.dtd"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>6.&nbsp;The Access Service DTD</h3>
</font><pre>
&lt;!--
  DTD for the IMXP access service, as of 2000-09-19


  Refer to this DTD as:

    &lt;!ENTITY % IMXPACCESS PUBLIC "-//Blocks//DTD IMXP ACCESS//EN"
             "http://xml.resource.org/profiles/IMXP/imxp-access.dtd">
    %IMXPACCESS;
  -->=20


&lt;!ENTITY % IMXPCORE PUBLIC "-//Blocks//DTD IMXP CORE//EN"
           "http://xml.resource.org/profiles/IMXP/imxp-core.dtd">
%IMXPCORE;


&lt;!--
  DTD data types:

       entity        syntax/reference     example
       =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D     =
=3D=3D=3D=3D=3D=3D=3D
    access actor
        ACTOR        an ENDPOINT or a     *@example.com
                     wildcard
  -->

&lt;!ENTITY  % ACTOR   "CDATA">   =20



















&lt;!--
  Synopsis of the IMXP access service

    service WKE: imxp=3Daccess

    message exchanges:

        consumer initiates    service replies
        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D    =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
        get                   set or reply
        set                   reply

    access control:

        token                 target
        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D            =3D=3D=3D=3D=3D=3D
        access:get            for "owner" of "access" element
        access:set            for "owner" of "access" element
  -->


&lt;!ELEMENT get         EMPTY>
&lt;!ATTLIST get
          owner       %ENDPOINT;        #REQUIRED
          transID     %UNIQID;          #REQUIRED>
   =20

&lt;!-- owner attributes must match in set and access -->

&lt;!ELEMENT set         (access)>
&lt;!ATTLIST set
          owner       %ENDPOINT;        #REQUIRED
          transID     %UNIQID;          #REQUIRED
          timeStamp   %TIMESTAMP;       #REQUIRED>


&lt;!--
  access entries
  -->
   =20
&lt;!ELEMENT access      (entry+)>
&lt;!ATTLIST access
          owner       %ENDPOINT;        #REQUIRED
          lastUpdate  %TIMESTAMP;       #REQUIRED>
   =20
&lt;!ELEMENT entry       EMPTY>
&lt;!ATTLIST entry
          actor       %ACTOR;           #REQUIRED
          actions     NMTOKENS          "">

</pre><font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">
<a name=3D"rfc.references"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>
References</h3>
<table width=3D"99%" border=3D"0">
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"IMXP-CORE">[1]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, <a href=3D"mailto:gk@acm.org">Klyne, G.</a> and <a =
href=3D"mailto:dcrocker@brandenburg.com">D.H. Crocker</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-mrose-imxp-core-01.txt"=
>The IMXP</a>", draft-mrose-imxp-core-01 (work in progress), September =
2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"BEEP-FRAMEWORK">[2]</a></b></td>
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.T.</a>, "<a =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-beep-framework-02.=
txt">The Blocks Extensible Exchange Protocol Framework</a>", =
draft-ietf-beep-framework-02 (work in progress), September =
2000.</td></tr>
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC0822">[3]</a></b></td>
<td class=3D"author-text">Crocker, D., "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc822.txt">Standard for the format =
of ARPA Internet text messages</a>", RFC 822, STD 11, Aug =
1982.</td></tr>
</table>

<a name=3D"rfc.authors"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Authors' Addresses</h3>
<table width=3D"99%" border=3D"0" cellpadding=3D"0" cellspacing=3D"0">
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Marshall T. Rose</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Invisible Worlds, Inc.</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">1179 North McDowell Boulevard</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Petaluma, CA  94954-6559</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">US</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+1 707 789 3700</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:mrose@invisible.net">mrose@invisible.net</a></td></tr>
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"http://invisible.net/">http://invisible.net/</a></td></tr>
<tr cellpadding=3D"3"><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Graham Klyne</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Content Technologies Limited</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">1220 Parkview</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Arlington Business Park</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Theale, Reading  RG7 4SA</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">UK</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+44 118 930 1300</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:gk@acm.org">gk@acm.org</a></td></tr>
<tr cellpadding=3D"3"><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">David H. Crocker</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Brandenburg Consulting</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">675 Spruce Drive</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">Sunnyvale, CA  94086</td></tr>
<tr><td class=3D"author-text">&nbsp;</td>
<td class=3D"author-text">US</td></tr>
<tr><td class=3D"author" align=3D"right">Phone:&nbsp;</td>
<td class=3D"author-text">+1 408 246 8253</td></tr>
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"mailto:dcrocker@brandenburg.com">dcrocker@brandenburg.com</a></td=
></tr>
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>
<td class=3D"author-text"><a =
href=3D"http://www.brandenburg.com/">http://www.brandenburg.com/</a></td>=
</tr>
</table>

<a name=3D"anchor7"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix A.&nbsp;Changes from draft-mrose-imxp-access-00</h3>

<p>

<ul class=3D"text">

<li>
Updated to reflect the current
<a href=3D"#BEEP-FRAMEWORK">BEEP framework</a>[2].
</li>

</ul>

</p>

<a name=3D"anchor8"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix B.&nbsp;Acknowledgements</h3>

<p>
The authors gratefully acknowledge the contributions of:
Darren New
and
Scott Pead.
</p>
<a name=3D"rfc.copyright"><br><hr size=3D"1" shade=3D"0"></a>
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Full Copyright Statement</h3>
<p class=3D'copyright'>
Copyright (C) The Internet Society (2000). All Rights Reserved.</p>
<p class=3D'copyright'>
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.</p>
<p class=3D'copyright'>
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.</p>
<p class=3D'copyright'>
This document and the information contained herein is provided on an
&quot;AS IS&quot; basis and THE INTERNET SOCIETY AND THE INTERNET =
ENGINEERING
TASK FORCE DISCLAIMS 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.</p>
<h3>Acknowledgement</h3>
<p class=3D'copyright'>
Funding for the RFC editor function is currently provided by the
Internet Society.</p>
</font></body></html>

------=_NextPart_000_009A_01C02287.4D97D7A0--