September 2001 - sg16-avd - lists.packetizer.com

Is H.225.0 Progress message really optional though it is used in Fast Start ?
by Lyons, Terry 05 Oct '01

05 Oct '01

H.323 v4 says: 8.1.7 Fast connect procedure . . . When the called endpoint desires to proceed with the Fast Connect procedure, it sends a Q.931 message (Call Proceeding, Progress, Alerting, or Connect) containing a fastStart element selecting from amongst the OpenLogicalChannel proposals offered by the calling endpoint. However, H.225.0 says that Progress is CM to receive and act on. Does that mean that a receiver can ignore Progress and believe that Fast Start was refused? The transmitter and receiver can then disagree about whether Fast Start concluded. How should we resolve the inconsistency? - TLyons(a)sonusnet.com +1 732 625-3003 ext 212 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

2 1

Re: Proposed Change to ITU-SG16 Mail List Procedures
by Chip Sharp 28 Sep '01

28 Sep '01

Most listserv software allows you to configure it so that only list members can send email to the list. If you configured the mail list in this manner, then only list members could send email. If someone sends spam, you remove that member from the list. Since most abusive spam is automatically generated, it is doubtful the originator will go through the trouble of subscribing to the list before sending. The downside is that people who monitor the list behind a mail exploder (or newsgroup) will not be able to post without subscribing individually. Anyway, this is another option to think of. Chip At 09:16 PM 9/25/2001, Meyer, Greg W wrote: >Dear ITU-SG16 Experts: > >I have noticed a dramatic increase in SPAM on the ITU-SG16 mail list. As >administrator of the list, I would like to hear about a proposed change that >will decrease the amount of SPAM and other mail messages including >potentially harmful email (viruses, etc.). > >I can set LISTSERV to require the sender of a message to acknowledge the >message before LISTSERV will send it. So to send a message, you would send >it in the usual way but before it gets sent to the mail list, LISTSERV will >send you a message. If you respond to the message, you authorize LISTSERV to >send the message. Since most SPAM is spoofed, the "sender" will not >acknowledge LISTSERV and the message will not get sent. > >I would appreciate hearing if there are any concerns with this method before >I implement it. I will follow-up this email later to announce what action I >have taken to this ITU-SG16 list. > >Thank you, > >Greg Meyer >Intel Corporation >email: greg.w.meyer(a)intel.com > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >For help on this mail list, send "HELP ITU-SG16" in a message to >listserv(a)mailbag.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

AW: Meeting Reminder
by Euchner Martin 28 Sep '01

28 Sep '01

Has anyone registered with the Dublin hotel received already a confirmation back? I'm not absolutely certain, if they have received my reservation request. Kind Regards Martin Euchner. ----------------------------------------------------------------------- | Dipl.-Inf. Phone: +49 89 722 55790 | Martin Euchner Fax : +49 89 722 46841 | Siemens AG | ICN M SR 3 mailto:Martin.Euchner@icn.siemens.de <mailto:Martin.Euchner@icn.siemens.de> | mailto:martin.euchner@ties.itu.int <mailto:martin.euchner@ties.itu.int> | Hofmannstr. 51 Intranet: http://intranet.icn.siemens.de/marketing/sr/pages/122/122_euchner.htm <http://intranet.icn.siemens.de/marketing/cs27/> | D-81359 Muenchen Internet: http://www.siemens.de <http://www.siemens.de> | __________________ | Germany ----------------------------------------------------------------------- -----Ursprüngliche Nachricht----- Von: Paul E. Jones [SMTP:paulej@PACKETIZER.COM] Gesendet am: Freitag, 28. September 2001 09:44 An: ITU-SG16(a)mailbag.cps.INTEL.COM Betreff: Meeting Reminder Wichtigkeit: Hoch Dear Experts, I just wanted to remind you that today is the last day to reserve your room for the Rapporteur's meeting in Dublin at the special discounted rate. If you have not already done so, I encourage you to make that reservation. Also, don't forget to send me an e-mail to let me you that you will be attending the meeting. Best Regards, Paul ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Release complete reason
by Francois Audet 28 Sep '01

28 Sep '01

Hi guys, What is the meaning of releaseCompleteReason=invalidRevision in RELEASE COMPLETE? Does it mean invalid revision of H.225.0? Or is it more general (like invalid versionId in the vendorId field for example). I suspect it is supposed to mean invalid revision of H.225.0. It isn't documented in H.225.0 (or H.323). I also suspect that if you want to do anything fancy like rejecting a call based on vendorId/productId/versionId, you'd should use the nonStandardReason? Any views? ---- François AUDET, Nortel Networks mailto:audet@nortelnetworks.com <mailto:audet@nortelnetworks.com> , tel:+1 408 495 3756

2 1

Meeting Reminder
by Paul E. Jones 28 Sep '01

28 Sep '01

Dear Experts, I just wanted to remind you that today is the last day to reserve your room for the Rapporteur's meeting in Dublin at the special discounted rate. If you have not already done so, I encourage you to make that reservation. Also, don't forget to send me an e-mail to let me you that you will be attending the meeting. Best Regards, Paul ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: Proposed Change to ITU-SG16 Mail List Procedures
by Meyer, Greg W 26 Sep '01

26 Sep '01

"This looks to be heading towards a "vote" situation." Actually no, I wasn't looking for votes. I wanted to know if there were any issues with my proposal; if the proposed change would either prohibit or significantly inhibit the intended purpose of the mail list. I've seen many great responses and very much appreciate the feedback. A major consideration for any change is the ability to send and receive mail in a timely manner. Any change that requires more administrative time will surely impact timely service since this is not my primary job function and I travel frequently (periods of not having access). I think Chris' summation below is accurate and, with few exceptions, will impact the subscribers minimally while according some degree of immunity to spam and other unauthorized use of the mail list. I would like to implement the proposal for a 30-day trial period. At the end of the period (end of Oct), I will see how much spam and other unauthorized mail went through compared to the last 30 days and also ask for feedback from you (the subscribers). My intention is to make the ITU-SG16 mail list better, not worse. So if it becomes clear that there are significant issues during the trial, I will terminate it and return to the current method (open to all who send without the "authorization" step). Clearly, Mr. Okubo's point of Listserv's timely response period will determine whether the proposed change is acceptable. In my experience, the vast majority of Listserv responses are within a few minutes (usually less than one minute). However, I have seen some extended delays when major network issues are experienced (Code Red, Nimda, etc.). These have been the exceptions and the purpose of a 30-day trial is to determine if extended delays are more prevalent than I believe them to be. I will do some testing prior to going live with the change. My target start is Monday, Oct 1. Again, I appreciate your feedback and look forward to making the ITU-SG16 list better for your use. Thanks, Greg Meyer Intel Corporation mailto:greg.w.meyer@intel.com +1.503.264.9506 -----Original Message----- From: Chris Wayman Purvis [mailto:cwp@ISDN-COMMS.CO.UK] Sent: Wednesday, September 26, 2001 8:30 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: Proposed Change to ITU-SG16 Mail List Procedures This looks to be heading towards a "vote" situation. I vote for the two-stage process. Most people read lots, post occasionally, and this solution only introduces a slight pain when posting, is minimal work for the list administrator and, most importantly, keeps the list open. Regards, Chris -- Dr Chris Purvis -- Development Manager ISDN Communications Ltd, The Stable Block, Ronans, Chavey Down Road Winkfield Row, Berkshire. RG42 6LY ENGLAND Phone: +44 1344 899 007 Fax: +44 1344 899 001 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Proposed Change to ITU-SG16 Mail List Procedures
by Meyer, Greg W 26 Sep '01

26 Sep '01

Dear ITU-SG16 Experts: I have noticed a dramatic increase in SPAM on the ITU-SG16 mail list. As administrator of the list, I would like to hear about a proposed change that will decrease the amount of SPAM and other mail messages including potentially harmful email (viruses, etc.). I can set LISTSERV to require the sender of a message to acknowledge the message before LISTSERV will send it. So to send a message, you would send it in the usual way but before it gets sent to the mail list, LISTSERV will send you a message. If you respond to the message, you authorize LISTSERV to send the message. Since most SPAM is spoofed, the "sender" will not acknowledge LISTSERV and the message will not get sent. I would appreciate hearing if there are any concerns with this method before I implement it. I will follow-up this email later to announce what action I have taken to this ITU-SG16 list. Thank you, Greg Meyer Intel Corporation email: greg.w.meyer(a)intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

5 4

Re: Proposed Change to ITU-SG16 Mail List Procedures
by Skran, Dale 26 Sep '01

26 Sep '01

Sounds like a great idea. Dale Skran -----Original Message----- From: Meyer, Greg W [mailto:greg.w.meyer@INTEL.COM] Sent: Tuesday, September 25, 2001 9:17 PM To: ITU-SG16(a)mailbag.cps.INTEL.COM Subject: Proposed Change to ITU-SG16 Mail List Procedures Dear ITU-SG16 Experts: I have noticed a dramatic increase in SPAM on the ITU-SG16 mail list. As administrator of the list, I would like to hear about a proposed change that will decrease the amount of SPAM and other mail messages including potentially harmful email (viruses, etc.). I can set LISTSERV to require the sender of a message to acknowledge the message before LISTSERV will send it. So to send a message, you would send it in the usual way but before it gets sent to the mail list, LISTSERV will send you a message. If you respond to the message, you authorize LISTSERV to send the message. Since most SPAM is spoofed, the "sender" will not acknowledge LISTSERV and the message will not get sent. I would appreciate hearing if there are any concerns with this method before I implement it. I will follow-up this email later to announce what action I have taken to this ITU-SG16 list. Thank you, Greg Meyer Intel Corporation email: greg.w.meyer(a)intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: Proposed Change to ITU-SG16 Mail List Procedures
by Les Brown 26 Sep '01

26 Sep '01

Hal, The problem with this approach is that many companies use an outgoing email address that is different/modified from the users incoming address, so users would have to register both addresses (once they figure out that they have 2 addresses). I had this problem with a list that I maintained, so I found it easier to open it up to allow anyone to post to it. Les Brown At 08:46 AM 9/26/2001 -0400, you wrote: >Greetings, > >There is also another way to limit posting to the list that does not involve >the two-step process. The list can be limited so that only those registered >for the list can post to it. I know that is a feature of majordomo that I >use for some of my lists. > >Hal > > > -----Original Message----- > > From: Meyer, Greg W [mailto:greg.w.meyer@INTEL.COM] > > Sent: Tuesday, September 25, 2001 9:17 PM > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > Subject: Proposed Change to ITU-SG16 Mail List Procedures > > > > > > Dear ITU-SG16 Experts: > > > > I have noticed a dramatic increase in SPAM on the ITU-SG16 > > mail list. As > > administrator of the list, I would like to hear about a > > proposed change that > > will decrease the amount of SPAM and other mail messages including > > potentially harmful email (viruses, etc.). > > > > I can set LISTSERV to require the sender of a message to > > acknowledge the > > message before LISTSERV will send it. So to send a message, > > you would send > > it in the usual way but before it gets sent to the mail list, > > LISTSERV will > > send you a message. If you respond to the message, you > > authorize LISTSERV to > > send the message. Since most SPAM is spoofed, the "sender" will not > > acknowledge LISTSERV and the message will not get sent. > > > > I would appreciate hearing if there are any concerns with > > this method before > > I implement it. I will follow-up this email later to announce > > what action I > > have taken to this ITU-SG16 list. > > > > Thank you, > > > > Greg Meyer > > Intel Corporation > > email: greg.w.meyer(a)intel.com > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > For help on this mail list, send "HELP ITU-SG16" in a message to > > listserv(a)mailbag.intel.com > > > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >For help on this mail list, send "HELP ITU-SG16" in a message to >listserv(a)mailbag.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

2 1

AW: Proposed Change to ITU-SG16 Mail List Procedures
by Euchner Martin 26 Sep '01

26 Sep '01

Greg, I appreciate your initiative to reduce the email spam on this list. I understand that spam is at least annoying, but sometimes even dangerous when viruses are conveyed. Of course, an effective countermeasure is required, that is also simple to use. While I'm not a mailing list expert and do not know about the particular constraint of this list, my understanding is, that posting a message to this list now would become a 2 stage process. This could counter the spam but at the price of user friendliness. My slight concern is, that some people might feel discouraged to post something just because the procedure sounds complicated. As traffic has already decreased considerably as compared to former years, we should seek for a procedure that does not put burden on the honest users. I'm not certain whether anybody can send stuff to this list, regardless of being subscribed or not. Thus, this sounds as a minimal precaution to make sure that any posting origins just from an authorized email address, where authorization means that the originator has been registered by the mailing list administrator. Is the listserv system able to check this? Would this help? Kind Regards Martin Euchner. ----------------------------------------------------------------------- | Dipl.-Inf. Phone: +49 89 722 55790 | Martin Euchner Fax : +49 89 722 46841 | Siemens AG | ICN M SR 3 mailto:Martin.Euchner@icn.siemens.de <mailto:Martin.Euchner@icn.siemens.de> | mailto:martin.euchner@ties.itu.int <mailto:martin.euchner@ties.itu.int> | Hofmannstr. 51 Intranet: http://intranet.icn.siemens.de/marketing/sr/pages/122/122_euchner.htm <http://intranet.icn.siemens.de/marketing/cs27/> | D-81359 Muenchen Internet: http://www.siemens.de <http://www.siemens.de> | __________________ | Germany ----------------------------------------------------------------------- -----Ursprüngliche Nachricht----- Von: Meyer, Greg W [SMTP:greg.w.meyer@INTEL.COM] Gesendet am: Mittwoch, 26. September 2001 03:17 An: ITU-SG16(a)mailbag.cps.INTEL.COM Betreff: Proposed Change to ITU-SG16 Mail List Procedures Dear ITU-SG16 Experts: I have noticed a dramatic increase in SPAM on the ITU-SG16 mail list. As administrator of the list, I would like to hear about a proposed change that will decrease the amount of SPAM and other mail messages including potentially harmful email (viruses, etc.). I can set LISTSERV to require the sender of a message to acknowledge the message before LISTSERV will send it. So to send a message, you would send it in the usual way but before it gets sent to the mail list, LISTSERV will send you a message. If you respond to the message, you authorize LISTSERV to send the message. Since most SPAM is spoofed, the "sender" will not acknowledge LISTSERV and the message will not get sent. I would appreciate hearing if there are any concerns with this method before I implement it. I will follow-up this email later to announce what action I have taken to this ITU-SG16 list. Thank you, Greg Meyer Intel Corporation email: greg.w.meyer(a)intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

5 4