June 2005 - sg16-avd - lists.packetizer.com

[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 02 Jun '05

02 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