H.248.1v3 Editorial Comments - Week 2

[Christian Groves]

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 at ericsson.com>
> mailto:christian.groves at 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
> 
> 
> .
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 8646 bytes
Desc: not available
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20050602/dea8cd1b/attachment-0006.bin>