datatracker.ietf.org
Sign in
Version 5.6.2.p6, 2014-09-03
Report a bug

Extensible Markup Language (XML) Formats for Representing Resource Lists
RFC 4826

Document type: RFC - Proposed Standard (May 2007; Errata)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4826 (Proposed Standard)
Responsible AD: Ted Hardie
Send notices to: rjsparks@nostrum.com, hisham.khartabil@telio.no

Network Working Group                                       J. Rosenberg
Request for Comments: 4826                                         Cisco
Category: Standards Track                                       May 2007

                   Extensible Markup Language (XML)
                Formats for Representing Resource Lists

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   In multimedia communications, presence, and instant messaging
   systems, there is a need to define Uniform Resource Identifiers
   (URIs) that represent services that are associated with a group of
   users.  One example is a resource list service.  If a user sends a
   Session Initiation Protocol (SIP) SUBSCRIBE message to the URI
   representing the resource list service, the server will obtain the
   state of the users in the associated group, and provide it to the
   sender.  To facilitate definition of these services, this
   specification defines two Extensible Markup Language (XML) documents.
   One document contains service URIs, along with their service
   definition and a reference to the associated group of users.  The
   second document contains the user lists that are referenced from the
   first.  This list of users can be utilized by other applications and
   services.  Both documents can be created and managed with the XML
   Configuration Access Protocol (XCAP).

Rosenberg                   Standards Track                     [Page 1]
RFC 4826                   XML Resource Lists                   May 2007

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Resource Lists Documents . . . . . . . . . . . . . . . . . . .  4
     3.1.  Structure  . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.2.  Schema . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.3.  Example Document . . . . . . . . . . . . . . . . . . . . .  9
     3.4.  Usage with XCAP  . . . . . . . . . . . . . . . . . . . . . 10
       3.4.1.  Application Unique ID  . . . . . . . . . . . . . . . . 10
       3.4.2.  MIME Type  . . . . . . . . . . . . . . . . . . . . . . 10
       3.4.3.  XML Schema . . . . . . . . . . . . . . . . . . . . . . 10
       3.4.4.  Default Namespace  . . . . . . . . . . . . . . . . . . 10
       3.4.5.  Additional Constraints . . . . . . . . . . . . . . . . 11
       3.4.6.  Data Semantics . . . . . . . . . . . . . . . . . . . . 11
       3.4.7.  Naming Conventions . . . . . . . . . . . . . . . . . . 11
       3.4.8.  Resource Interdependencies . . . . . . . . . . . . . . 12
       3.4.9.  Authorization Policies . . . . . . . . . . . . . . . . 12
   4.  RLS Services Documents . . . . . . . . . . . . . . . . . . . . 13
     4.1.  Structure  . . . . . . . . . . . . . . . . . . . . . . . . 13
     4.2.  Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     4.3.  Example Document . . . . . . . . . . . . . . . . . . . . . 15
     4.4.  Usage with XCAP  . . . . . . . . . . . . . . . . . . . . . 16
       4.4.1.  Application Unique ID  . . . . . . . . . . . . . . . . 16
       4.4.2.  MIME Type  . . . . . . . . . . . . . . . . . . . . . . 16
       4.4.3.  XML Schema . . . . . . . . . . . . . . . . . . . . . . 16
       4.4.4.  Default Namespace  . . . . . . . . . . . . . . . . . . 16
       4.4.5.  Additional Constraints . . . . . . . . . . . . . . . . 16
       4.4.6.  Data Semantics . . . . . . . . . . . . . . . . . . . . 17
       4.4.7.  Naming Conventions . . . . . . . . . . . . . . . . . . 17
       4.4.8.  Resource Interdependencies . . . . . . . . . . . . . . 18
       4.4.9.  Authorization Policies . . . . . . . . . . . . . . . . 20
     4.5.  Usage of an RLS Services Document by an RLS  . . . . . . . 20
   5.  SIP URI Canonicalization . . . . . . . . . . . . . . . . . . . 22
   6.  Extensibility  . . . . . . . . . . . . . . . . . . . . . . . . 23
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 24
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 24
     8.1.  XCAP Application Unique IDs  . . . . . . . . . . . . . . . 24
       8.1.1.  resource-lists . . . . . . . . . . . . . . . . . . . . 24
       8.1.2.  rls-services . . . . . . . . . . . . . . . . . . . . . 24
     8.2.  MIME Type Registrations  . . . . . . . . . . . . . . . . . 25
       8.2.1.  application/resource-lists+xml . . . . . . . . . . . . 25

[include full document text]