November 2003 - sg16-avd - lists.packetizer.com

TISPAN vs Q.NCAP?; Re: New draft on Gate Control protocol
by simao.campos＠ITU.INT 26 Nov '03

26 Nov '03

Forwarding on behalf of Mr Schwarz -----Original Message----- From: Albrecht.Schwarz(a)alcatel.de [mailto:Albrecht.Schwarz@alcatel.de] Sent: 26 November 2003 14:31 To: CHATRAS Bruno FTRD/DAC/ISS Cc: TISPAN_WG3(a)LIST.ETSI.ORG; tsg16q3(a)itu.int; tsg11ncap(a)itu.int; megaco(a)ietf.org Subject: TISPAN vs Q.NCAP?; Re: New draft on Gate Control protocol Dear Mr Chatras, due to the fact that I'm neither involved in TISPAN WG3 nor SG11 NCAP, I'm wondering how is the relation between Draft Q.NCAP3 and your TISPAN H.248 Profile? Are these complemental or disjoint activities? Thanks, Albrecht Schwarz ALCATEL |---------+---------------------------------> | | CHATRAS Bruno | | | FTRD/DAC/ISS | | | <bruno.chatras@FRANCET| | | ELECOM.COM> | | | Sent by: "TISPAN_WG3: | | | Protocols" | | | <TISPAN_WG3(a)LIST.ETSI.| | | ORG> | | | | | | | | | 25.11.2003 18:49 | | | Please respond to | | | CHATRAS Bruno | | | FTRD/DAC/ISS | | | | |---------+---------------------------------> >--------------------------------------------------------------------------- ---------------------------------| | | | To: TISPAN_WG3(a)LIST.ETSI.ORG | | cc: | | Subject: New draft on Gate Control protocol | >--------------------------------------------------------------------------- ---------------------------------| Dear Colleagues, A new draft of the ETSI Gate Control protocol specification is available as TD070 at the following location. http://docbox.etsi.org/tispan/tispan/50-20031201-Sophia/02TD070%20H248Profil e%20GC.zip I take the opportunity of this message to remind you that this ES has some dependencies on the EMP Package defined in TS 101 332. During the TISPAN meeting we agreed that this package should be registered by IANA and that a corrigendum to TS 101 332 should be issued. However, the EMP package is still missing on the IANA web site where packages are supposed to be registered (http://www.iana.org/assignments/megaco-h248) and apparently, there is no input contribution with a proposed corrigendum to TS 101 332. Regards, Bruno Mail archive for TISPAN_WG3 can be browsed at the following url : http://list.etsi.org/TISPAN_WG3.html

1 0

White contribution COM 16-C8-E on Questions
by OKUBO Sakae 26 Nov '03

26 Nov '03

Dear WP2/16 experts, For your consideration. At 04:55 +0100 03/11/26, ITU Web Notification system wrote: >The following files have been updated since 2003-11-25 > >System : DMS >Group : itu-t >updated : 2003-11-25 23:58:05 >title : [ C 8 ] Proposed text of the Study Group 16 >Questions for the Study Period 2005-2008 >url : >http://www.itu.int/md/meetingdoc.asp?lang=e&parent=T01-SG16-C-0008&type=sit… >------------------------------------------------------------- Summary This document contains a consolidated and revised version of the set of Questions under SG 16 from the SG 16 management viewpoint and is provided to the SG 16 meeting as a starting point for discussions as the set of Questions for use in the next study period. The SG management invites contributions from the ITU-T membership for the SG 16 meeting 20-30 January 2004 to improve the current set of Questions. In this document, Questions 7, 8, 15 are suppressed, Q.13 is merged with Q.11, Q.5 is converted into a horizontal Q.K, and a new Q.5 is proposed. Further, the text for Q.J in this document is the proposed draft new Question from last meeting incorporating a few comments received. It should be noted that part of the revisions shown here for draft revised Questions D, F, G, K, 1, 2, 3, 4, and 5 were though out in the Paris meeting of (current) WP2 Questions D, F, G, 2-5/16 (see TD 10/WP2). Nevertheless, the final decision of the set of Questions to be submitted to WTSA will be taken by SG 16 in its meeting January 2004. This final set of Questions will be drafted according to the template/guidelines from TSAG (see SG 16 TD 55/Gen). Section 1 of the document presents the assumptions and principles for the preparation of this draft, Section 2 revisits the concept of FSAs, Horizontal and Vertical Questions, and Priority Areas. Section 3 contains the text of the Questions. Annex A contains a list of the current Questions and a map to the proposed revised texts of this document. Annex B lists a map of the current SG 16 Questions to the "building blocks" defined by the TSAG Study Group Restructuring discussion group. -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering Waseda University ******************************************************************** <YRP> Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan <Nishi-Waseda> 29-7 Waseda University Bldg. Tel: +81 3 5286 9841 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo Fax: +81 3 5286 3832 169-0051 Japan ********************************************************************

1 0

FW: RFC 3644 on Policy Quality of Service (QoS) Information Model
by simao.campos＠ITU.INT 19 Nov '03

19 Nov '03

For your information. Best regards, Simao -----Original Message----- From: rfc-editor(a)rfc-editor.org [mailto:rfc-editor@rfc-editor.org] Sent: 18 November 2003 22:47 Cc: rfc-editor(a)rfc-editor.org; policy(a)ietf.org Subject: RFC 3644 on Policy Quality of Service (QoS) Information Model A new Request for Comments is now available in online RFC libraries. RFC 3644 Title: Policy Quality of Service (QoS) Information Model Author(s): Y. Snir, Y. Ramberg, J. Strassner, R. Cohen, B. Moore Status: Standards Track Date: November 2003 Mailbox: yramberg(a)cisco.com, ysnir(a)cisco.com, john.strassner(a)intelliden.com, ronc(a)lyciumnetworks.com, remoore(a)us.ibm.com Pages: 73 Characters: 170150 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-policy-qos-info-model-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3644.txt This document presents an object-oriented information model for representing Quality of Service (QoS) network management policies. This document is based on the IETF Policy Core Information Model and its extensions. It defines an information model for QoS enforcement for differentiated and integrated services using policy. It is important to note that this document defines an information model, which by definition is independent of any particular data storage mechanism and access protocol. This document is a product of the Policy Framework Working Group of the IETF. This is now a Proposed Standard Protocol. 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. 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(a)IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info(a)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(a)RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR(a)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.

1 0

FW: I-D ACTION:draft-h350-directory-services-00.txt
by simao.campos＠ITU.INT 19 Nov '03

19 Nov '03

For your information... Best regards, Simao -----Original Message----- From: Internet-Drafts(a)ietf.org [mailto:Internet-Drafts@ietf.org] Sent: 18 November 2003 21:05 Subject: I-D ACTION:draft-h350-directory-services-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : H.350 Directory Services Author(s) : T. Johnson Filename : draft-h350-directory-services-00.txt Pages : 27 Date : 2003-11-18 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-h350-directory-services-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-h350-directory-services-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-h350-directory-services-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.

1 0

FW: [AVT] RFC 3611 on RTP Control Protocol Extended Reports (RTCP
by simao.campos＠ITU.INT 06 Nov '03

06 Nov '03

For your information. Best regards, Simao -----Original Message----- From: rfc-editor(a)rfc-editor.org [mailto:rfc-editor@rfc-editor.org] Sent: 05 November 2003 20:05 Cc: rfc-editor(a)rfc-editor.org; avt(a)ietf.org Subject: [AVT] RFC 3611 on RTP Control Protocol Extended Reports (RTCP XR) A new Request for Comments is now available in online RFC libraries. RFC 3611 Title: RTP Control Protocol Extended Reports (RTCP XR) Author(s): T. Friedman, R. Caceres, A. Clark, Eds. Status: Standards Track Date: November 2003 Mailbox: timur.friedman(a)lip6.fr, caceres(a)watson.ibm.com, alan(a)telchemy.com Pages: 55 Characters: 126736 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-rtcp-report-extns-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3611.txt This document defines the Extended Report (XR) packet type for the RTP Control Protocol (RTCP), and defines how the use of XR packets can be signaled by an application if it employs the Session Description Protocol (SDP). XR packets are composed of report blocks, and seven block types are defined here. The purpose of the extended reporting format is to convey information that supplements the six statistics that are contained in the report blocks used by RTCP's Sender Report (SR) and Receiver Report (RR) packets. Some applications, such as multicast inference of network characteristics (MINC) or voice over IP (VoIP) monitoring, require other and more detailed statistics. In addition to the block types defined here, additional block types may be defined in the future by adhering to the framework that this document provides. This document is a product of the Audio/Video Transport Working Group of the IETF. This is now a Proposed Standard Protocol. 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. 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(a)IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info(a)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(a)RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR(a)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.

1 0