FW: RFC 3944 on H.350 Directory Services

Euchner Martin martin.euchner at siemens.com
Mon Dec 13 03:36:25 EST 2004


FYI:

-----Original Message-----
From: 	ietf-announce-bounces at ietf.org [mailto:ietf-announce-bounces at ietf.org]  On Behalf Of rfc-editor at rfc-editor.org
Sent:	Samstag, 11. Dezember 2004 01:24
To:	ietf-announce at ietf.org
Cc:	rfc-editor at rfc-editor.org
Subject:	RFC 3944 on H.350 Directory Services

 <<Untitled Attachment>>  <<ATT51554.txt>> 
A new Request for Comments is now available in online RFC libraries.

RFC 3944
Title:      H.350 Directory Services
Author(s):  T. Johnson, S. Okubo, S. Campos
Status:     Informational
        Date:	December 2004
	Mailbox:    Tyler_Johnson at unc.edu, sokubo at waseda.jp,
	simao.campos at itu.int
	Pages:      30
	Characters: 61160
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-johnson-h350-directory-serv-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3944.txt


The International Telecommunications Union Standardization Sector (ITU-T) has created the H.350 series of Recommendations that specify directory services architectures in support of multimedia conferencing protocols.  The goal of the architecture is to 'directory enable' multimedia conferencing so that these services can leverage existing identity management and enterprise directories.  A particular goal is to enable an enterprise or service provider to maintain a canonical source of users and their multimedia conferencing systems, so that multiple call servers from multiple vendors, supporting multiple protocols, can all access the same data store.
Because SIP is an IETF standard, the contents of H.350 and H.350.4 are made available via this document to the IETF community.  This document contains the entire normative text of ITU-T Recommendations H.350 and H.350.4 in sections 4 and 5, respectively.  The remaining sections are included only in this document, not in the ITU-T version.
This memo provides information for the Internet community.  It does not specify an Internet standard of any kind.  Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.  Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG.  Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs.  For example:
        To:	rfc-info at RFC-EDITOR.ORG
        Subject:	getting rfcs

help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

..

Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
-------------------------------------------------------------------------
CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY
-------------------------------------------------------------------------
In order to maintain computing infrastructure integrity, Cisco Systems
Enterprise Messaging Services and InfoSec teams have set a mail policy
disallowing executable attachments in email.

This message contained an executable attachment type that is prohibited 
by this policy. The attachment has been removed from this message and 
copied to quarantine by our systems. It will be held in quarantine for
seven days in the event that the content needs to be retrieved.

Please be aware many viruses attempt to look like legitimate email or 
notifications from anti-virus systems. We will clearly mark a seperation
between our notifications and the original email as follows:

  "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY"

For further reference information about viruses and email antivirus 
efforts within Cisco, please visit:

http://wwwin.cisco.com/it/ems/services/antiviral

If your concern isn't addressed by the information in this notification 
or the above web page, you may open a support request:

http://wwwin.cisco.com/support/

Select "Messaging", "Email-Related", "Mail Routing"

Please include in the text of your case the following information:

* Full headers of the message. Documentation on displaying the full 
headers is available at this URL:

http://wwwin.cisco.com/support/library/faqs/solution002471.html 

* This unique quarantine identifier: iBD8aMm4007020

If the matter is urgent, you may follow up by calling one of the below 
referenced numbers. Please make every effort to provide the above 
requested information via the support web tool prior to calling as it 
will greatly aid the resolution of your issue.

Americas:
1 408 526 8888

Asiapac
+61 2 8446 8888

EMEA
+31 20 485 4888

Japan
+81 3 5549 6888

US (Toll Free)
1| 800| 888| 8187| (ext.68888)

Thank you for your cooperation,

Enterprise Messaging Services
Cisco Systems, Inc
-------------- next part --------------
An embedded message was scrubbed...
From: unknown sender
Subject: 
Date: Mon, 13 Dec 2004 09:34:07 +0100
Size: 709
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20041213/68af9c9b/attachment-0003.mht>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT51554.txt
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20041213/68af9c9b/attachment-0003.txt>


More information about the sg16-avd mailing list