This working group addresses issues specific to intermediaries in
the World Wide Web infrastructure, providing generic mechanisms which
are useful in several application domains (proxies operated by access
providers, content delivery surrogates, etc).
Intermediaries are commonly deployed to help scale the WWW. Lack of
mechanisms to control and communicate with them brings about
scalability issues with intermediaries themselves, and lack of
strong, scalable coherence mechanisms limits their adoption by both
end users and content publishers.
Furthermore, access providers who wish to provision caching proxies
in their networks have no standardized mechanism to announce such
devices to user agents. As a result, many access providers resort to
the use of interception proxies, which break the end-to-end
relationship between client and server at the transport layer,
leading to undesired behaviors.
Accordingly, the group's work items are to:
1) Develop a resource update protocol.
2) Gather requirements for an intermediary discovery and description
mechanism.
quot;
type="token"
default="UTF-8" />
<attribute name="cksum"
type="token" />
<attribute name="cksumAlg"
type="token"
default="CRC32" />
</extension>
</simpleContent>
</complexType>
<!-- URL fields -->
<element name="fUrl"
type="rdeCsv:anyURIType"
substitutionGroup="rdeCsv:field" />
<complexType name="anyURIType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="anyURI" />
</extension>
</complexContent>
</complexType>
<!--
End of schema.
-->
</schema>
<CODE ENDS>
9.2. RDE Domain Object
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:domain-1.0" />
<import namespace="urn:ietf:params:xml:ns:secDNS-1.1" />
<import namespace="urn:ietf:params:xml:ns:rgp-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" />
<annotation>
<documentation>
Registry Data Escrow Domain provisioning schema
</documentation>
</annotation>
<element name="abstractDomain"
type="rdeDomain:abstractContentType"
substitutionGroup="rde:content"
abstract="true" />
<element name="domain"
substitutionGroup="rdeDomain:abstractDomain" />
<element name="delete"
type="rdeDomain:deleteType"
substitutionGroup="rde:delete" />
<!-- Content Type -->
<complexType name="abstractContentType">
<complexContent>
<extension base="rde:contentType">
<sequence>
<element name="name"
type="eppcom:labelType" />
<element name="roid"
type="eppcom:roidType" />
<element name="uName"
type="eppcom:labelType"
minOccurs="0" />
<element name="idnTableId"
type="rdeIDN:idType"
minOccurs="0" />
<element name="originalName"
type="eppcom:labelType"
minOccurs="0" />
<element name="status"
type="domain:statusType"
maxOccurs="11" />
<element name="rgpStatus"
type="rgp:statusType"
minOccurs="0"
maxOccurs="unbounded" />
<element name="registrant"
type="eppcom:clIDType"
minOccurs="0" />
<element name="contact"
type="domain:contactType"
minOccurs="0"
maxOccurs="unbounded" />
<element name="ns"
type="domain:nsType"
minOccurs="0" />
<element name="clID
It is expected that after requirements for intermediary discovery
and description are gathered and evaluated, the working group will
re-charter to continue that work.
Issues pertaining to coordination between multiple administrative
domains are explicitly out of scope in this group's work items. Work
associated with the modification of messages by intermediaries is
also out of scope. Additionally, this group will only address
application-level (e.g., HTTP) intermediaries.