- sg16-avd - lists.packetizer.com

Re: (very) short summary of IETF E.164 BOF
by Scott Bradner 15 Sep '98

15 Sep '98

Pete gave a good summary of the BOF - one thing I'd add is that for more info on the DNS-based resolution you should take a look at RFC 1703 ftp://ftp.iana.org/in-notes/rfc1703.txt Scott

1 0

(very) short summary of IETF E.164 BOF
by Pete Cordell 15 Sep '98

15 Sep '98

Dear All, Following one of the inter-gk conference calls, I picked up an action to find out what is happening in the IETF E.164 area. Although I wasn't actually at the BOF this is what I have managed to pick up from a colleague. Firstly, a working group is to be created, which is likely to be (will be?) chaired by Scott Petrack. The details of the scope have not been fully fleshed out yet. The input to the process will be an E.164/telephone number. Whether local short-cut codes and private networks are supported is still to be decided. The output has not been decided, but could range from a simple IP address, to something that may include alternate E.164 number, to something that would list a full set of remote endpoint capabilities. A number of proposals were discussed most of which had the theme of: convert E.164 number/telephone number to domain name, then convert domain name to IP address. The latter stage may involve something like the gateway location work. One proposal (Falstrom(?)) is to use DNS NAPTR records to convert E.164 numbers to domain names. To do this each digit would be separated by a dot, the sequence reversed, and then the domain name e164.int appended to it. e.g.: +44-1473-646436 -> 6.3.4.6.4.6.3.7.4.1.4.4.e164.int This could match multiple NAPTR records. The NAPTR records map to a domain name and include with them what service is associated with that domain name. e.g. The above address could map to: IN NAPTR 100 10 "s" "h323call+N2R" tele2.se IN NAPTR 100 10 "s" "sipcall+N2R" tele3.se The first one indicates that the h323call+N2R service is at address tele2.se, and that there is a SRV record (indicated by the "s") for it. The other values indicate priorities. (Not sure what the +N2R indicates) A set of these queries would be returned to the querier, and it could select the service it was interested in and would do a DNS SRV look-up to convert this to an IP address. One issue with this is that it has a single top-level domain. Huitema suggested that multiple organisations should be able to provide the top level mappings, which he called a conflicting claims method. Other proposals had variations on this theme, some of which included references to other databases such as X.500, LDAP and so on (Brown). This seems quite sensible and is well worth keeping an eye. Apparently not much has happened on the mailing list since, but this could be because Scott hasn't produced the minutes yet!!! Hope this helps, Pete ================================= Pete Cordell BT Labs E-Mail: pete.cordell(a)bt-sys.bt.co.uk Tel: +44 1473 646436 Fax: +44 1473 645499 =================================

1 0

RE: H.225 Annex G
by Roy, Radhika R, ALINT 13 Sep '98

13 Sep '98

Yes, there is only one editor. Suggestions are given to the editor and ITU-T SG16 members via contributions. Radhika R. Roy AT&T > ---------- > From: Jim Toga[SMTP:jim.toga@intel.com] > Sent: Friday, September 11, 1998 11:24 AM > To: Roy, Radhika R, ALINT; Andrew Draper; Chris Purvis WVdevmt-WS; > Douglas Clowes; Gene Schroeder; Hal Purdy; Joon Maeng; Kaynam Hedayat; > Korpi Markku PN VS LP3; Kumar, Vineet; Mayer, Paul G; Michele Bozier > WVdevmt-WS; Nancy-M Greene; Orit Levin; Paul E. Jones; Pete Cordell; Santo > Wiryaman; Sengodan Senthil NRC/Boston; Sree Peyyety; Youngho Lim; > 'ggf(a)lucent.com' > Subject: RE: H.225 Annex G > > My assumption was that there was only one editor.... > > > At 08:59 AM 9/11/98 -0400, Roy, Radhika R, ALINT wrote: > >Glen: > > > >Thanks for the update. > > > >I have also a plan to present a complete version of the modified Annex G > >along the line as I proposed earlier as this version appears to be > >incomplete considering the facts that has described in my proposed > outlines > >of Annex G document (as well clarifications made in the subsequent > emails). > > > >Regards, > >Radhika > > > >> ---------- > >> From: Glen Freundlich[SMTP:ggf@lucent.com] > >> Reply To: ggf(a)lucent.com > >> Sent: Thursday, September 10, 1998 12:48 AM > >> To: Andrew Draper; Chris Purvis WVdevmt-WS; Douglas Clowes; Gene > >> Schroeder; ggf; Hal Purdy; Jim Toga; Joon Maeng; Kaynam Hedayat; Korpi > >> Markku PN VS LP3; Kumar, Vineet; Mayer, Paul G; Michele Bozier > WVdevmt-WS; > >> Nancy-M Greene; Orit Levin; Paul E. Jones; Pete Cordell; Roy, Radhika > R, > >> ALTEC; Santo Wiryaman; Sengodan Senthil NRC/Boston; Sree Peyyety; > Youngho > >> Lim > >> Subject: H.225 Annex G > >> > >> <<File: annexg.zip>> > >> Attached is my first attempt at Annex G. I'm sure I've omitted things > or > >> misrepresented things, so please review this and send your comments as > >> soon as possible. I'd like to get another version around for comments > >> before I distribute it to the SG16 list. > >> > >> Glen > >> > >> p.s.: I've sent this only to the group of people who have been on the > >> conference calls. > >> > >> -- > >> Glen Freundlich ggf(a)lucent.com > >> Lucent Technologies office: +1 303 538 2899 > >> 11900 N. Pecos fax: +1 303 538 3907 > >> Westminster, Colorado 80234 USA > >> > > > > ***************************************************** > *** +1-503-264-8816(voice) Intel - Hillsboro, OR. > *** > *** mailto:jim.toga@intel.com mailto:james.toga@ties.itu.int *** > *** PGP keyID 36 07 86 49 7D 74 DF 57 50 CB BA 32 08 9C 7C 41 *** > ***************************************************** >

1 0

H.225 Annex G
by Glen Freundlich 11 Sep '98

11 Sep '98

I have uploaded a draft of H.225 Annex G to the incoming directory of avc-site as h225_annexg.zip. Regards, Glen -- Glen Freundlich ggf(a)lucent.com Lucent Technologies office: +1 303 538 2899 11900 N. Pecos fax: +1 303 538 3907 Westminster, Colorado 80234 USA

1 0

RE: H.225 Annex G
by Roy, Radhika R, ALINT 11 Sep '98

11 Sep '98

Glen: Thanks for the update. I have also a plan to present a complete version of the modified Annex G along the line as I proposed earlier as this version appears to be incomplete considering the facts that has described in my proposed outlines of Annex G document (as well clarifications made in the subsequent emails). Regards, Radhika > ---------- > From: Glen Freundlich[SMTP:ggf@lucent.com] > Reply To: ggf(a)lucent.com > Sent: Thursday, September 10, 1998 12:48 AM > To: Andrew Draper; Chris Purvis WVdevmt-WS; Douglas Clowes; Gene > Schroeder; ggf; Hal Purdy; Jim Toga; Joon Maeng; Kaynam Hedayat; Korpi > Markku PN VS LP3; Kumar, Vineet; Mayer, Paul G; Michele Bozier WVdevmt-WS; > Nancy-M Greene; Orit Levin; Paul E. Jones; Pete Cordell; Roy, Radhika R, > ALTEC; Santo Wiryaman; Sengodan Senthil NRC/Boston; Sree Peyyety; Youngho > Lim > Subject: H.225 Annex G > > <<File: annexg.zip>> > Attached is my first attempt at Annex G. I'm sure I've omitted things or > misrepresented things, so please review this and send your comments as > soon as possible. I'd like to get another version around for comments > before I distribute it to the SG16 list. > > Glen > > p.s.: I've sent this only to the group of people who have been on the > conference calls. > > -- > Glen Freundlich ggf(a)lucent.com > Lucent Technologies office: +1 303 538 2899 > 11900 N. Pecos fax: +1 303 538 3907 > Westminster, Colorado 80234 USA >

2 1

Discussion TD re MPEG stream packetization
by Sakae OKUBO 11 Sep '98

11 Sep '98

Dear Q.12-14/16 experts, I have sent the following TD to Geneva: ftp://standard.pictel.com/avc-site/9809_Gen/Input_TD/MPEG_pac.zip Source: Q12 Rap Title: Study on MPEG stream packetization Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ***********************************************************

1 0

Drafts H.450.9 and H.RDC
by Sakae OKUBO 10 Sep '98

10 Sep '98

Dear Q.12-14/16 experts, The following files have been moved from /Incoming to: ftp://stanard.pictel.com/avc-site/9809_Gen/Input_TD/h450.8_980910.zip (G Freundlich) ftp://stanard.pictel.com/avc-site/9809_Gen/Input_TD/H_RDC_Proposal.zip (M Duckworth) Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ***********************************************************

1 0

H.RDC proposal available on ftp site
by Mark Duckworth 10 Sep '98

10 Sep '98

My Temporary Document regarding H.RDC is available at ftp://standard.pictel.com/avc-site/Incoming/H_RDC_Proposal.zip This is a proposal for carrying the Common Remote Device Control protocol on a new Data Link Protocol in an H.323 conference. This simple Data Link Protocol runs over a bidirectional unreliable logical channel. It allows many RDC nodes to communicate with each other in a multipoint conference. Mark Duckworth PictureTel Corporation

1 0

H.450.8 - Identification Services
by Glen Freundlich 10 Sep '98

10 Sep '98

I have uploaded the draft of H.450.8, Identification Services, to the incoming directory of the avc-site. The file appears as h450.8_980910.zip. The hope was to propose this for determination at the upcoming SG16 meeting. Regards, Glen -- Glen Freundlich ggf(a)lucent.com Lucent Technologies office: +1 303 538 2899 11900 N. Pecos fax: +1 303 538 3907 Westminster, Colorado 80234 USA

1 0

H.225 Annex G
by Glen Freundlich 10 Sep '98

10 Sep '98

Attached is my first attempt at Annex G. I'm sure I've omitted things or misrepresented things, so please review this and send your comments as soon as possible. I'd like to get another version around for comments before I distribute it to the SG16 list. Glen p.s.: I've sent this only to the group of people who have been on the conference calls. -- Glen Freundlich ggf(a)lucent.com Lucent Technologies office: +1 303 538 2899 11900 N. Pecos fax: +1 303 538 3907 Westminster, Colorado 80234 USA

1 0