- sg16-avd - lists.packetizer.com

Re: onIteration; Re: [SUSPECT ATTACHMENT] H.248.1 Editing Meeting:
by Christian Groves 06 Jun '05

06 Jun '05

Hello Albrecht, Yes I meant the "onIteration" part. This is to align with the note in H.248.34 e.g. NOTE – This may be achieved in H.248.1 by setting the Notify Complete flag to "onIteration" (this value of NotifyComplete will be available in H.248.1 version 3) and activating the signal completion event in the Generic Package (see E.1/H.248.1). Regards, Christian Albrecht.Schwarz(a)alcatel.de wrote: > Just to ensure: NotifyCompletion parameter "onIteration" is meant. > Right? > Thanks > Albrecht > > > > > > Christian Groves > > <christian.groves@ER To: Kevin Boyle > <kboyle(a)NORTELNETWORKS.COM> > ICSSON.COM> cc: > > Subject: [SUSPECT > ATTACHMENT] H.248.1 Editing Meeting: Week 3 Comments > 06.06.2005 07:59 > > > > > > > > < Attachment TD5 Input Draft_h248.1v3 Week 3_chg_comment.zip removed > > > > Hello Kevin, all, > > Please find attached my marked up comments for Week 3. > > In addition, the changes from AVD-2563 for NotifyCompletion have not > been > included in H.248.1 at all. This affects more than just the ASN.1 > > Regards, Christian > > > ------------------------------------------------------------------------ > - > CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY > ------------------------------------------------------------------------ > - > WARNING: This message has an attachment that could contain executable > code. > > Please review the attachment carefully to ensure you do not > inadvertently > execute embedded programs that could contain viruses. > > We suggest you review the following URL to stay up-to-date with current > virus threats: > > http://wwwin.cisco.com/support/library/mcafee/virus_info.shtml > > 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: j565xQbw010993 > > 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 > > > > > >

1 0

onIteration; Re: [SUSPECT ATTACHMENT] H.248.1 Editing Meeting: Week 3
by Albrecht.Schwarz＠alcatel.de 06 Jun '05

06 Jun '05

Just to ensure: NotifyCompletion parameter "onIteration" is meant. Right? Thanks Albrecht Christian Groves <christian.groves@ER To: Kevin Boyle <kboyle(a)NORTELNETWORKS.COM> ICSSON.COM> cc: Subject: [SUSPECT ATTACHMENT] H.248.1 Editing Meeting: Week 3 Comments 06.06.2005 07:59 < Attachment TD5 Input Draft_h248.1v3 Week 3_chg_comment.zip removed > Hello Kevin, all, Please find attached my marked up comments for Week 3. In addition, the changes from AVD-2563 for NotifyCompletion have not been included in H.248.1 at all. This affects more than just the ASN.1 Regards, Christian ------------------------------------------------------------------------- CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY ------------------------------------------------------------------------- WARNING: This message has an attachment that could contain executable code. Please review the attachment carefully to ensure you do not inadvertently execute embedded programs that could contain viruses. We suggest you review the following URL to stay up-to-date with current virus threats: http://wwwin.cisco.com/support/library/mcafee/virus_info.shtml 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: j565xQbw010993 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

1 0

[SUSPECT ATTACHMENT] H.248.1 Editing Meeting: Week 3 Comments
by Christian Groves 06 Jun '05

06 Jun '05

Hello Kevin, all, Please find attached my marked up comments for Week 3. In addition, the changes from AVD-2563 for NotifyCompletion have not been included in H.248.1 at all. This affects more than just the ASN.1 Regards, Christian ------------------------------------------------------------------------- CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY ------------------------------------------------------------------------- WARNING: This message has an attachment that could contain executable code. Please review the attachment carefully to ensure you do not inadvertently execute embedded programs that could contain viruses. We suggest you review the following URL to stay up-to-date with current virus threats: http://wwwin.cisco.com/support/library/mcafee/virus_info.shtml 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: j565xQbw010993 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

1 0

Re: H.248.1v3 Editorial Comments - Week 2
by Christian Groves 02 Jun '05

02 Jun '05

Hello Annie, Please see my comments below. Regards, Christian Benitez, Mariana (Annie) wrote: > > 2) For section 7.2.7 on Notify. The use of TerminationIDList would be > valid for a Notify: > For example, if there were a Modify command enabling an event on > Wildcarded TerminationID (same RequestID), if the event were detected on > several of those terminationIDs simultaneously then the Notify could > have a TerminationIDList (with the single RequestID, as long as any > parameters returned if at all were the same). > A TerminationID List is a list of fully qualified names. [CHG] I did think of this example but is it realistic that the MG would behave in this way? Events would have to occur at preciously the same time. As the timestamp would have to be the same. The observed event parameters would have to be exactly the same. It sounds like we could be overcomplicating the notify mechanism. > > 3)For section 7.2.8 on Service Change: "Note: The use of > TerminationIDList is not valid in the initial H.248.1v1 ServiceChange > command. ", don't think this statement is required as section 11.3 on > 'Negotiation of Protocol Version' already covers this with the > following: "Regardless of the version placed in the ServiceChangeVersion > parameter, the message containing the command shall be encoded as a > version 1 message. " [CHG] I know about this statement however I think it would be easy for implementors to look at the parameters of a ServiceChange and code these according to v1. The terminationIDlist may be easy to overlook. Especially when the binary encoding already has TerminationIDlist in it. > > Thank you, > Best Regards, > > Marianne & Annie > > > > -----Original Message----- > From: Christian Groves [ <mailto:christian.groves@ericsson.com> > mailto:christian.groves@ericsson.com] > Sent: Tuesday, May 31, 2005 1:29 AM > To: Kevin Boyle > Cc: SG16 > Subject: [WARNING: A/V UNSCANNABLE] [SUSPECT ATTACHMENT] H.248.1v3 > Editorial Comments - Week 2 > > > Hello Kevin, all, > > Please find my Week 2 comments marked up in the attached document. I > have also > made a number of comments using the word comment tool. > > Regards, Christian > ------------------------------------------------------------------------ > - > CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY > ------------------------------------------------------------------------ > - > WARNING: This message has an attachment that could contain executable > code. > > Please review the attachment carefully to ensure you do not > inadvertently > execute embedded programs that could contain viruses. > > We suggest you review the following URL to stay up-to-date with current > virus threats: > > <http://wwwin.cisco.com/support/library/mcafee/virus_info.shtml> > http://wwwin.cisco.com/support/library/mcafee/virus_info.shtml > > 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> > 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/> 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> > http://wwwin.cisco.com/support/library/faqs/solution002471.html > > * This unique quarantine identifier: j4V5T3bw020768 > > 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 > > > . >

1 0

RE: H.248.1v3 Editorial Comments - Week 2
by Kevin Boyle 01 Jun '05

01 Jun '05

Sorry. I was sick and out of the office the last half of last week, and I have been struggling to get caught back up. I will have the week 1 changes up later today, and the week 2 changes up tomorrow. The only change I did not make per request was an update to section 6.2.3 that indicated that a particular statement was redundant. That one particular statement was specifically added because of questions and arguments about what is or is not to be supported in a package. I would just as soon see it left in. I have made all the other updates per the week 1 requests, including the non-trivial task of making the use of capitalization of the word "descriptor" consistent. Kevin _____ From: Benitez, Mariana (Annie) [mailto:anniebp@lucent.com] Sent: Tuesday, May 31, 2005 4:12 PM To: 'Christian Groves'; kboyle(a)NORTELNETWORKS.COM Cc: SG16; Picha, Marianne (Marianne) Subject: RE: H.248.1v3 Editorial Comments - Week 2 Kevin/Christian, One question: Will there be a notification sent when the editor has the updated text based on the comments compilation and the new document posted on the web (http://ftp3.itu.int/av-arch/avc-site/2005-2008/H.248.1_Editing/)? Don't believe I've seen anything posted for Week One - Want to make sure we're not missing something in this process... Christian et. al, 1) We would agree that for your comment on section 7.2.5 'Audit Value' that the example using ContextList, the message reply should have a command reply. The command: Context=*{ContextAttr{ContextList={*}},AuditValue=Root{Audit{}}} Returns: INSTEAD OF: Context=*{ContextAttr{ContextList={1,2,3,4}}} THE REPLY SHOULD BE: Context=*{ContextAttr{ContextList={1,2,3,4}}, AuditValue=ROOT{}} 2) For section 7.2.7 on Notify. The use of TerminationIDList would be valid for a Notify: For example, if there were a Modify command enabling an event on Wildcarded TerminationID (same RequestID), if the event were detected on several of those terminationIDs simultaneously then the Notify could have a TerminationIDList (with the single RequestID, as long as any parameters returned if at all were the same). A TerminationID List is a list of fully qualified names. 3)For section 7.2.8 on Service Change: "Note: The use of TerminationIDList is not valid in the initial H.248.1v1 ServiceChange command. ", don't think this statement is required as section 11.3 on 'Negotiation of Protocol Version' already covers this with the following: "Regardless of the version placed in the ServiceChangeVersion parameter, the message containing the command shall be encoded as a version 1 message. " Thank you, Best Regards, Marianne & Annie -----Original Message----- From: Christian Groves [ <mailto:christian.groves@ericsson.com> mailto:christian.groves@ericsson.com] Sent: Tuesday, May 31, 2005 1:29 AM To: Kevin Boyle Cc: SG16 Subject: [WARNING: A/V UNSCANNABLE] [SUSPECT ATTACHMENT] H.248.1v3 Editorial Comments - Week 2 Hello Kevin, all, Please find my Week 2 comments marked up in the attached document. I have also made a number of comments using the word comment tool. Regards, Christian ------------------------------------------------------------------------- CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY ------------------------------------------------------------------------- WARNING: This message has an attachment that could contain executable code. Please review the attachment carefully to ensure you do not inadvertently execute embedded programs that could contain viruses. We suggest you review the following URL to stay up-to-date with current virus threats: <http://wwwin.cisco.com/support/library/mcafee/virus_info.shtml> http://wwwin.cisco.com/support/library/mcafee/virus_info.shtml 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> 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/> 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> http://wwwin.cisco.com/support/library/faqs/solution002471.html * This unique quarantine identifier: j4V5T3bw020768 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

1 0

Week 1 changes
by Kevin Boyle 01 Jun '05

01 Jun '05

All, I apologize for the delay in getting the week 1 changes posted. I was ill most of last week and I have been struggling since to get caught up. I have posted the updated draft with the week 1 changes as TD-8 to the incoming folder. I will be working on all the edits requested this week this evening and tomorrow to have them posted tomorrow as TD-8R1. I will post each weeks changes as a revision to TD-8. Thanks for your patience as I recover from my illness. Kevin

1 0

To Mr.Dave Lindberg
by Noah Luo 01 Jun '05

01 Jun '05

Dear Dave Would you please tell me your e-mail address? With Best Regards 　　　　　　　　Noah Luo 　　　　　　　　noah(a)huawei.com 　　　　　　　　　　2005-06-01

1 0

H.248.1v3 Editorial Comments - Week 2
by Marianne Picha 31 May '05

31 May '05

Kevin and others, Attached are comments from Lucent marked as tracked changes and embedded comments. Only sections with comments are included. Regards, Marianne Picha

1 0

Two RFCs of potencial interest (4094 & 4109)
by simao.campos＠ITU.INT 31 May '05

31 May '05

Dear colleagues, FYI: - RFC 4094 on Analysis of Existing Quality-of-Service SignalingProtocols --> Q.24? - RFC 4109 on Algorithms for Internet Key Exchange version 1 (IKEv1) --> Q.25? Best regards, Simao

1 0

[SUSPECT ATTACHMENT] H.248.1v3 Editorial Comments - Week 2
by Christian Groves 31 May '05

31 May '05

Hello Kevin, all, Please find my Week 2 comments marked up in the attached document. I have also made a number of comments using the word comment tool. Regards, Christian ------------------------------------------------------------------------- CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY ------------------------------------------------------------------------- WARNING: This message has an attachment that could contain executable code. Please review the attachment carefully to ensure you do not inadvertently execute embedded programs that could contain viruses. We suggest you review the following URL to stay up-to-date with current virus threats: http://wwwin.cisco.com/support/library/mcafee/virus_info.shtml 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: j4V5T3bw020768 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

1 0

Re: H.248.1 V3 Editorial Comments: Contr. (3) "Identifier"
by Christian Groves 31 May '05

31 May '05

Hello all, I would support Alrechts proposal for option 2. Reards, Christian Albrecht.Schwarz(a)alcatel.de wrote: > Dear Colleagues, > > a contribution to "ID" usage. > Regards > Albrecht > > > (See attached file: TDx2 AlcatelContribution_AbrIdentifier.doc) >

1 0

H.248.1 V3 Editorial Comments: Contr. (4) Key Words for Requirements
by Albrecht.Schwarz＠alcatel.de 30 May '05

30 May '05

Dear Colleagues, a contribution for usage of key words for requirements level indication. Regards Albrecht (See attached file: TDx3 AlcatelContribution_KeyWords_Requirements.doc)

1 0

H.248.1 V3 Editorial Comments: Contr. (3) "Identifier"
by Albrecht.Schwarz＠alcatel.de 30 May '05

30 May '05

Dear Colleagues, a contribution to "ID" usage. Regards Albrecht (See attached file: TDx2 AlcatelContribution_AbrIdentifier.doc)

1 0

H.248.1 V3 Editorial Comments: Contr. (2) to week 2 sections
by Albrecht.Schwarz＠alcatel.de 30 May '05

30 May '05

Dear Colleagues, editorial change proposals are proposed in the attachement. There are two subsequent contributions/emails with comments going beyond "week 2". Regards Albrecht (See attached file: TD4 Input Draft_h248.1v3 Week 2 commentsALCATEL.doc)

1 0

H.248.1 V3 Editorial Comments: Contr. (1) to
by Albrecht.Schwarz＠alcatel.de 30 May '05

30 May '05

Dear Colleagues, comment to heading wording. Regards Albrecht (See attached file: TDx1 AlcatelContribution_§7.1.14.7 heading.doc) "Kevin Boyle" <kboyle(a)nortel.c To: "Kevin Boyle" <kboyle(a)nortel.com>, itu-sg16(a)external.cisco.com om> cc: Sent by: Subject: RE: Meeting Announcement: H.248.1 Version 3 Online Editing Meetin owner-tsg16q3@it u.int 23.05.2005 16:25 Please respond to "Kevin Boyle" Colleagues, Per the schedule posted last week, the input drafts for the H.248.1 V3 Editing meeting have been uploaded. There are 7 documents, marked TD1 - TD7: TD1 - H.248.1 V3 Input Draft TD2 - H.248.1 V3 Clean Version TD3 - H.248.1 V3 Week 1 sections TD4 - H.248.1 V3 Week 2 sections TD5 - H.248.1 V3 Week 3 sections TD6 - H.248.1 V3 Week 4 sections TD7 - H.248.1 V3 Week 5 sections These are currently in the Incoming folder, but will soon be available in the H.248.1_Editing directory. The documents will also be available through the following URLs: http://ftp3.itu.int/av-arch/avc-site/2005-2008/H.248.1_Editing/ ftp://avguest:Avguest@ftp3.itu.int/avc-site/2005-2008/H.248.1_Editing/ Kevin

1 0

FW: [AVT] Fwd: I-D ACTION:draft-wing-behave-symmetric-rtprtcp-00.
by Euchner Martin 27 May '05

27 May '05

This new Internet Draft appears of potential interest to H.460.ma. With kind regards Martin Euchner. ----------------------------------------------------------------------- | Dipl.-Inf. Rapporteur | Martin Euchner Phone: +49 89 722 55790 | Siemens AG.....................Fax : +49 89 722 62366 | COM GC PS 3 mailto:Martin.Euchner@siemens.com | mailto:martin.euchner@ties.itu.int | Hofmannstr. 51 Intranet: http://ietf.icn.siemens.de/sr3/Standardisation_Topics/security/ | D-81359 Muenchen Internet: http://www.siemens.de/ | __________________ | Germany ----------------------------------------------------------------------- -----Original Message----- From: avt-bounces(a)ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Colin Perkins Sent: Freitag, 27. Mai 2005 19:33 To: IETF AVT Working Group Subject: [AVT] Fwd: I-D ACTION:draft-wing-behave-symmetric-rtprtcp-00.txt FYI - this is relevant to AVT. Colin Begin forwarded message: > From: Internet-Drafts(a)ietf.org > Date: 24 May 2005 20:41:03 BDT > To: i-d-announce(a)ietf.org > Subject: I-D ACTION:draft-wing-behave-symmetric-rtprtcp-00.txt > Reply-To: internet-drafts(a)ietf.org > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : A Definition of Symmetric RTP and Symmetric RTCP > Author(s) : D. Wing > Filename : draft-wing-behave-symmetric-rtprtcp-00.txt > Pages : 7 > Date : 2005-5-24 > > This document defines "symmetric RTP" and "symmetric RTCP" and > explains the value of their use. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-wing-behave-symmetric- > rtprtcp-00.txt _______________________________________________ Audio/Video Transport Working Group avt(a)ietf.org https://www1.ietf.org/mailman/listinfo/avt

1 0

Biel/Bienne Meeting (17 - 20 May 2005)
by Paul E. Jones 27 May '05

27 May '05

SG16 Experts, We completed a successful meeting of Questions 1, 2, 5, 21, 25 and 29/16 in Biel/Bienne the week of 17-20 May 2005. The documents for the meeting are available at the following location: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0505_Bie/ The meeting documents may also be accessed via FTP: Host name: ftp3.itu.int <ftp://ftp3.itu.int/> Directory: /avc-site/2005-2008 Username: avguest Password: Avguest The report for the Biel/Bienne meeting is contained in AVD-2747a <http://ftp3.itu.int/av-arch/avc-site/2005-2008/0505_Bie/AVD-2747a.zip> . The next SG16 meeting will be held in Geneva at the ITU facilities 26 July - 5 August 2005. I look forward to seeing you there! Best Regards, Paul E. Jones

1 0

Re: H.248.1 V3 Editorial Comments: § 7.1.
by Christian Groves 25 May '05

25 May '05

Hello Kevin, I would concur with Albrecht on this. Regards, Christian Albrecht.Schwarz(a)alcatel.de wrote: > We have still an open item in § 7.1.11: > > > [Editor's Note: There is a problem if a signal is specified with a > direction that doesn't make sense or is impossible. This is an > attempt > at some text. Contributions for this are solicited.] > > Discussion: > After some analysis this item may result (if at all) in a dedicated > Error Code. Code #452 "No such signal in this package" is > inappropriate. > On the other side, there seems to be no real justification for a new > codepoint. The next sentence ("error codepoint #501") seems to be > applicable as well for the indicated situation. > > Proposal: > Delete Editor's note. No further text changes proposed. > > Albrecht Schwarz > ALCATEL > > > >

1 0

RE: Meeting Announcement: H.248.1 Version 3 Online Editing Meetin
by OKUBO Sakae 23 May '05

23 May '05

Dear Kevin and all, At 10:25 -0400 05/05/23, Kevin Boyle wrote: >[...] >These are currently in the Incoming folder, but will soon be >available in the H.248.1_Editing directory. > >The documents will also be available through the following URLs: ><http://ftp3.itu.int/av-arch/avc-site/2005-2008/H.248.1_Editing/>http://f tp3.itu.int/av-arch/avc-site/2005-2008/H.248.1_Editing/ ><ftp://avguest:Avguest@ftp3.itu.int/avc-site/2005-2008/H.248.1_Editing/>f tp://avguest:Avguest@ftp3.itu.int/avc-site/2005-2008/H.248.1_Editing/ They have been moved to the place indicated above. -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering Waseda University ****************************************************************** 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 H.323 videoconferencing: arranged by advice ******************************************************************

1 0

RE: Meeting Announcement: H.248.1 Version 3 Online Editing Meetin
by Kevin Boyle 23 May '05

23 May '05

Colleagues, Per the schedule posted last week, the input drafts for the H.248.1 V3 Editing meeting have been uploaded. There are 7 documents, marked TD1 - TD7: TD1 - H.248.1 V3 Input Draft TD2 - H.248.1 V3 Clean Version TD3 - H.248.1 V3 Week 1 sections TD4 - H.248.1 V3 Week 2 sections TD5 - H.248.1 V3 Week 3 sections TD6 - H.248.1 V3 Week 4 sections TD7 - H.248.1 V3 Week 5 sections These are currently in the Incoming folder, but will soon be available in the H.248.1_Editing directory. The documents will also be available through the following URLs: http://ftp3.itu.int/av-arch/avc-site/2005-2008/H.248.1_Editing/ ftp://avguest:Avguest@ftp3.itu.int/avc-site/2005-2008/H.248.1_Editing/ Kevin

1 0

H.248.1 V3 Editorial Comments: § 7.1.11
by Albrecht.Schwarz＠alcatel.de 23 May '05

23 May '05

We have still an open item in § 7.1.11: [Editor's Note: There is a problem if a signal is specified with a direction that doesn't make sense or is impossible. This is an attempt at some text. Contributions for this are solicited.] Discussion: After some analysis this item may result (if at all) in a dedicated Error Code. Code #452 "No such signal in this package" is inappropriate. On the other side, there seems to be no real justification for a new codepoint. The next sentence ("error codepoint #501") seems to be applicable as well for the indicated situation. Proposal: Delete Editor's note. No further text changes proposed. Albrecht Schwarz ALCATEL

1 0

H.248.1 V3 Editorial Comments:
by Albrecht.Schwarz＠alcatel.de 23 May '05

23 May '05

A minor editorial comment to the examples in $ 6.3.4 and § 7.1.4: It's proposed to align to upper case for "Descriptor". Albrecht Schwarz ALCATEL 7.1.4: Media descriptor TerminationState Descriptor Stream descriptor LocalControl descriptor Local descriptor Remote descriptor Statistics descriptor

1 0

Meeting Announcement: H.248.1 Version 3 Online Editing Meeting
by Kevin Boyle 18 May '05

18 May '05

>From C Groves Rapporteur for Q.3/16 <christian.groves(a)ericsson.com> K Boyle II Editor of H.248.1 Version 3 <kboyle(a)nortel.com> ------------------------------------------------------------------- Subject: Notice of Online Editing Meeting for H.248.1 Version 3 Date: 23 May - 1 July 2005 ------------------------------------------------------------------- Dear Experts of Question 3/16, As agreed at the Melbourne meeting, a meeting for the purpose of editing H.248.1 Version 3 will be held via email over the course of several weeks. Details of the meeting are contained herein. 1. Date ^^^^^^^ 23rd (Monday) May - 1st (Friday) July 2005 Meeting will be conducted via email. The meeting will be considered to be convened at 0900 EDT on 23 May, and concluded at 1700 EDT on 1 July. 2. Venue ^^^^^^^^ The ITU-T SG16 mailing list: itu-sg16(a)external.cisco.com No pre-registration is necessary. 3. Topics ^^^^^^^^^ 1) Editing of H.248.1 Version 3 in preparation for the July/August SG16 meeting. 4. Documents ^^^^^^^^^^^^ 1) File format: The editor's documents will be in Word. 2) E-mail reflector E-mail address: itu-sg16(a)external.cisco.com To subscribe: Send e-mail to majordomo(a)cisco.com In the body of the message, put: subscribe itu-sg16 Please avoid the use of reflector when your document is voluminous. 3) Input documents can be retrieved from the H.248.1_Editing directory of the ftp site. The documents will also be available through the following URLs: http://ftp3.itu.int/av-arch/avc-site/2005-2008/H.248.1_Editing/ ftp://avguest:Avguest@ftp3.itu.int/avc-site/2005-2008/H.248.1_Editing/ 4) The document distribution / presentation at the meeting will be all electronic. 5. Logistic information ^^^^^^^^^^^^^^^^^^^^^^^ 1) The editor will produce an input version of the document by 0900 EDT on May 16. 2) Each week, a portion of the document will be open for editorial comment. The schedule shall be as follows: 23 - 27 May -- Sections 1 - 7.1.14 30 May - 3 June -- Sections 7.1.15 - 14.4 6 - 10 June -- Annex A 6 - 17 June -- Annex B 20 - 24 June -- Annexes C, D, E, F, Appendices I, II, III 27 June - 1 July -- Cleanup Review 3) On Monday and Tuesday of each week, editorial comments may be posted to the list or emailed to the editor, copying the Rapporteur. The editor will compile all comments, and update the text on Wednesday. By 0900 EDT on Thursday each week, the editor will post updated text for the group's review. Thursday and Friday will be used for any further editorial commentary on the newly updated text. The editor will then finalize the text of the section. 4) By 0900 EDT on 27 June, the editor will post the resulting complete text from the editing of the previous weeks. The entire text will be open to further editorial comment on the same schedule as the previous weeks. 5) The resulting text will be the editor's input draft to the SG16 meeting in Geneva. 6) Note that *NO TECHNICAL CHANGES* will be accepted during this meeting. All proposed changes must be editorial. Technical changes to the proposed text must be proposed to the SG16 meeting in July/August per the normal contribution procedures. 7) For postings to the mailing list, please use the following subject line: "H.248.1 V3 Editorial Comments" 6. Registration ^^^^^^^^^^^^^^^ No registration is necessary, though subscription to the SG16 exploder is required. We are looking forward to a productive editing meeting. Sincerely yours, Kevin BOYLE II (Editor) Christian GROVES (Rapporteur) ----------

1 0

Question on T.38
by Francesco De Marco 09 May '05

09 May '05

Gentlemen, I'm writing for a question about T.38 and h245 requestMode. At par. D.5 of H.323 AnnexD, it is written: "either endpoint may detect fax tones (i.e. CNG or CED) or the presence of V.21 carrier and HDLC flags. Typical scenarios for facsimile call detection rely on the analysis of CNG calling tone and a response of the CED answer tone and/or the initiation of fax procedures using the V.21 carrier and HDLC flags. Note that in some implementations the presence of either CNG or CED are optional. Therefore, both endpoints should take an active role in order to properly detect fax." and "When using two unidirectional fax channels, the endpoint that detected the tone shall initiate the standard H.245 Mode Request procedure by sending a requestMode message to its remote counterpart" The question is: if both the endpoints detect the tone, both can send a requestMode and this can happen at the same time; in this case both will receive, other than send, a requestMode. How is solved this situation? Has one of them to accept the change and the other has to reject it, or both can accept the change? Is there a standard procedure to be applied in this case (based for example on the master-slave decision, or what else)? I know that one possible solution is to implement the application so that only the "receiving fax endpoint" (i.e. the one detecting the CED at his local analog interface) sends the requestMode, but this seems not being recomanded by AnnexD. Kind regards, Francesco

1 0

Contribution AVD-2737 uploaded
by Louis Fourie 09 May '05

09 May '05

Experts, I have uploaded Draft H.235.8 (AVD-2737) to the Incoming directory. - Louis Fourie Cisco Systems

1 0