- sg16-avd - lists.packetizer.com

You are now subscribed to the ITU-SG16 list
by L-Soft list server at Intel Corporation (1.8c) 29 Sep '98

29 Sep '98

Tue, 29 Sep 1998 06:48:32 Your subscription to the ITU-SG16 list (Mailing list for parties associated with ITU-T Study Group 16) has been accepted. Please save this message for future reference, especially if this is the first time you subscribe to an electronic mailing list. If you ever need to leave the list, you will find the necessary instructions below. Perhaps more importantly, saving a copy of this message (and of all future subscription notices from other mailing lists) in a special mail folder will give you instant access to the list of mailing lists that you are subscribed to. This may prove very useful the next time you go on vacation and need to leave the lists temporarily so as not to fill up your mailbox while you are away! You should also save the "welcome messages" from the list owners that you will occasionally receive after subscribing to a new list. To send a message to all the people currently subscribed to the list, just send mail to ITU-SG16(a)MAILBAG.INTEL.COM. This is called "sending mail to the list", because you send mail to a single address and LISTSERV makes copies for all the people who have subscribed. This address (ITU-SG16(a)MAILBAG.INTEL.COM) is also called the "list address". You must never try to send any command to that address, as it would be distributed to all the people who have subscribed. All commands must be sent to the "LISTSERV address", LISTSERV(a)MAILBAG.INTEL.COM. It is very important to understand the difference between the two, but fortunately it is not complicated. The LISTSERV address is like a FAX number that connects you to a machine, whereas the list address is like a normal voice line connecting you to a person. If you make a mistake and dial the FAX number when you wanted to talk to someone on the phone, you will quickly realize that you used the wrong number and call again. No harm will have been done. If on the other hand you accidentally make your FAX call someone's voice line, the person receiving the call will be inconvenienced, especially if your FAX then re-dials every 5 minutes. The fact that most people will eventually connect the FAX machine to the voice line to allow the FAX to go through and make the calls stop does not mean that you should continue to send FAXes to the voice number. People would just get mad at you. It works pretty much the same way with mailing lists, with the difference that you are calling hundreds or thousands of people at the same time, and consequently you can expect a lot of people to get upset if you consistently send commands to the list address. You may leave the list at any time by sending a "SIGNOFF ITU-SG16" command to LISTSERV(a)MAILBAG.INTEL.COM. You can also tell LISTSERV how you want it to confirm the receipt of messages you send to the list. If you do not trust the system, send a "SET ITU-SG16 REPRO" command and LISTSERV will send you a copy of your own messages, so that you can see that the message was distributed and did not get damaged on the way. After a while you may find that this is getting annoying, especially if your mail program does not tell you that the message is from you when it informs you that new mail has arrived from ITU-SG16. If you send a "SET ITU-SG16 ACK NOREPRO" command, LISTSERV will mail you a short acknowledgement instead, which will look different in your mailbox directory. With most mail programs you will know immediately that this is an acknowledgement you can read later. Finally, you can turn off acknowledgements completely with "SET ITU-SG16 NOACK NOREPRO". Following instructions from the list owner, your subscription options have been set to "REPRO MIME" rather than the usual LISTSERV defaults. For more information about subscription options, send a "QUERY ITU-SG16" command to LISTSERV(a)MAILBAG.INTEL.COM. Contributions sent to this list are automatically archived. You can get a list of the available archive files by sending an "INDEX ITU-SG16" command to LISTSERV(a)MAILBAG.INTEL.COM. You can then order these files with a "GET ITU-SG16 LOGxxxx" command, or using LISTSERV's database search facilities. Send an "INFO DATABASE" command for more information on the latter. This list is available in digest form. If you wish to receive the digested version of the postings, just issue a SET ITU-SG16 DIGEST command. More information on LISTSERV commands can be found in the LISTSERV reference card, which you can retrieve by sending an "INFO REFCARD" command to LISTSERV(a)MAILBAG.INTEL.COM.

1 0

Re: decided version of H.323 Annex D is now in the Incoming direc tory of the avc-site
by Rahul Chopra 28 Sep '98

28 Sep '98

Vineet: Wanted to know where the avc-site was? Would appeciate it. Thanks. Rahul > -----Original Message----- > From: Kumar, Vineet [SMTP:vineet.kumar@INTEL.COM] > Sent: Monday, September 28, 1998 5:18 PM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: decided version of H.323 Annex D is now in the Incoming > directory of the avc-site > > The decided version of H.323 Annex D is now in the Incoming directory of > the > avc-site. Is there a new directory where all the decided and determined > documents need to be uploaded ? > > vineet > -------------------------------------------------------------------------- > -- > -------------------------- > Vineet Kumar vineet.kumar(a)intel.com > Intel Corporation, JF3-212 (+1) 503-264-3439 > (phone) > Hillsboro, OR 97124-5961 (+1) 503-264-3375 > (fax) > -------------------------------------------------------------------------- > -- > --------------------------

1 0

Re: Draft H.323 Annexes E and F uploaded
by Alexandre Chatilov 28 Sep '98

28 Sep '98

ftp://standard.pictel.com/avc-site/Incoming/ -----Original Message----- From: Rahul Chopra [mailto:rchopra@NETSPEAK.COM] Sent: Monday, September 28, 1998 2:51 PM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: Draft H.323 Annexes E and F uploaded Joerg: Where is the avc-site? Would apprecate a pointer Thanks. Rahul > -----Original Message----- > From: Joerg Ott [SMTP:jo@INFORMATIK.UNI-BREMEN.DE] > Sent: Monday, September 28, 1998 5:35 PM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: Draft H.323 Annexes E and F uploaded > > Folks, > > I have uploaded the determined documents H.323 Annex E and > H.323 Annex F into the Incoming directory of the AVC ftp site. > The file names are: > > H323-AnnexE-4.02.doc (equivalent to TD-47/PLEN) > H323-AnnexF-03.doc (equivalent to TD-51/PLEN) > > Joerg

1 0

Re: Draft H.323 Annexes E and F uploaded
by Rahul Chopra 28 Sep '98

28 Sep '98

Joerg: Where is the avc-site? Would apprecate a pointer Thanks. Rahul > -----Original Message----- > From: Joerg Ott [SMTP:jo@INFORMATIK.UNI-BREMEN.DE] > Sent: Monday, September 28, 1998 5:35 PM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: Draft H.323 Annexes E and F uploaded > > Folks, > > I have uploaded the determined documents H.323 Annex E and > H.323 Annex F into the Incoming directory of the AVC ftp site. > The file names are: > > H323-AnnexE-4.02.doc (equivalent to TD-47/PLEN) > H323-AnnexF-03.doc (equivalent to TD-51/PLEN) > > Joerg

1 0

Draft H.323 Annexes E and F uploaded
by Joerg Ott 28 Sep '98

28 Sep '98

Folks, I have uploaded the determined documents H.323 Annex E and H.323 Annex F into the Incoming directory of the AVC ftp site. The file names are: H323-AnnexE-4.02.doc (equivalent to TD-47/PLEN) H323-AnnexF-03.doc (equivalent to TD-51/PLEN) Joerg

1 0

decided version of H.323 Annex D is now in the Incoming directory of the avc-site
by Kumar, Vineet 28 Sep '98

28 Sep '98

The decided version of H.323 Annex D is now in the Incoming directory of the avc-site. Is there a new directory where all the decided and determined documents need to be uploaded ? vineet ---------------------------------------------------------------------------- -------------------------- Vineet Kumar vineet.kumar(a)intel.com Intel Corporation, JF3-212 (+1) 503-264-3439 (phone) Hillsboro, OR 97124-5961 (+1) 503-264-3375 (fax) ---------------------------------------------------------------------------- --------------------------

1 0

sourceInfo field in RAS LRQ messages
by Meir Fuchs 27 Sep '98

27 Sep '98

Hi, The H.225.0 (v2) standard describes the sourceInfo field in RAS LRQ messages as follows: sourceInfo - indicates the sender of the LRQ. The gatekeeper can use this information to decide how to respond to the LRQ. A gatekeeper recieves an ARQ and wishes to resolve the called endpoint by sending an LRQ to neighboring gatekeepers. What would you expect the gatekeeper to put in the sourceInfo field of the LRQ ? Several answers come to mind: a. The source info of the calling endpoint (copied from the srcInfo field of the RAS ARQ message). b. Some info identifying the gatekeeper itself. c. Nothing at all or anything at all ? Any help is greatly appreciated. Regards, Meir.

1 0

test, please ignore
by Michael F. Speer 26 Sep '98

26 Sep '98

test, please ignore Michael

1 0

Re: Authentication
by Chris Purvis WVdevmt-WS 17 Sep '98

17 Sep '98

>How does GKs authenticate each other?, As yet, they don't... >and furthermore, how does a GK >authenticate an H.323 entity under its zone so that it can be sure it is >talking with the entitiy it claims to be?, I haven't seen anything on >this on the proposals for Anex G I've read. ...however, in version 2 of H.225.0 all RAS messages may contain authentication tokens. H.235 specifies the framework within which this works, although it does not prescribe any particular authentication mechanism. I would expect similar authentication tokens to appear in any inter-gatekeeper or inter-administrative-domain messages where authentication is required. Regards, Chris -- Dr Chris Purvis - Senior Development Engineer, WAVE CC Software Madge Networks Ltd, Wexham Springs, Framewood Road, Wexham, Berks. Phone:+44 1753 661359 email: cpurvis(a)madge.com

1 0

Authentication
by William Pimentel 16 Sep '98

16 Sep '98

How does GKs authenticate each other?, and furthermore, how does a GK authenticate an H.323 entity under its zone so that it can be sure it is talking with the entitiy it claims to be?, I haven't seen anything on this on the proposals for Anex G I've read. Thank you. William Pimentel

1 0