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

Re: VoIP Traversal of Non-upgraded Firewall & NATs @ IETF
by Pete Cordell 07 Aug '01

07 Aug '01

Just to confirm the announcement I made at the SIP meeting this morning.... This meeting is now on... It will be held in: Hilton Rooms 10, 11, & 12 Thursday 17:45 -> 19:00 (although we'll make it shorter if we can) Hope to see you there. Pete. ============================================= Pete Cordell Tech-Know-Ware pete(a)tech-know-ware.com +44 1473 635863 ============================================= ----- Original Message ----- From: Pete Cordell <pete(a)tech-know-ware.com> To: <midcom(a)ietf.org>; 'sip-ietf (E-mail)' <sip(a)ietf.org>; <sipping(a)ietf.org>; SG16 <ITU-SG16(a)MAILBAG.INTEL.COM>; <TIPHON(a)LIST.ETSI.FR> Cc: Steve Davies <SDavies(a)Ridgeway-Sys.com> Sent: 01 August 2001 10:03 Subject: VoIP Traversal of Non-upgraded Firewall & NATs @ IETF > Dear All, > > I would like to have a meeting at the IETF (informal BOF?) discussing > methods for VoIP and Multimedia over IP traversing non-upgraded firewalls > and NATs. These methods are intended to supplement the firewall > architecture, and not require upgrade to existing firewall/NAT components, > or clients (and other infrastructure such as proxies). > > There is a draft discussing one proposal at: > > http://www.ietf.org/internet-drafts/draft-davies-fw-nat-traversal-00.txt > > If others have ideas in this area, then please contact me and we can arrange > some sort of agenda. (Although note that I will be out of contact until the > Sunday before the IETF - i.e. this Sunday! - so we might have to organise > this at the IETF.) > > I hope the format will be something like: > > - Overview presentation of method > - How this is secure and maintains administrator control > - (Repeat for each proposal) > - Collect issues that need to be addressed before going to a formal BOF. > > (The modified agenda involves the final item being changed to 'chaos'!) > > At this stage I would like to avoid discussion about how this compares to > MidCom and other approaches - such as Rosenberg's - as I think it will > quickly turn into a blood bath. - We should save that for the formal BOF! > > I'm hoping to hold the meeting in: > > The King's Suite/Sandringham 1 on > Thursday 17:45 -> 18:45, > > but I obviously haven't had a chance to check this with the organisers. > Therefore, please look out for final details on the noticeboard, and > probably the door of the King's Suite. > > I look forward to seeing you all, > > Pete. > > (P.S. Sorry for putting this on the SG16 and TIPHON lists, but I'm well > aware that many of you attend the IETF and I wanted to make sure you had the > opportunity to come along.) > > ============================================= > Pete Cordell > Tech-Know-Ware > pete(a)tech-know-ware.com > +44 1473 635863 > ============================================= > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Rapporteur's Meeting, 24-28 Sept 2001
by Paul E. Jones 06 Aug '01

06 Aug '01

To Experts of ITU-T SG16 Questions D, F, G, 2, 3, 4 and 5/16 Cc Mr. P-A. Probst, Chairman of SG16 <probst-pa(a)bluewin.ch> Mr. G. Wreikat, Vice-Chairman of SG16 <wreikat(a)hotmail.com> Mr. F. Tosco, Chairman of WP2/16 <Federico.Tosco(a)tilab.com> Mr. F. Bigi, ITU-TSB <Fabio.Bigi(a)itu.int> Mr. L. Brown, Rapporteur Q.11/16 <Les.Brown(a)mindspeed.com> Mr. P. Luthi, Rapporteur for Q.1/16 <Patrick_Luthi(a)pictel.com> Mr. H. Wildfeuer, Cisco <hwildfeu(a)cisco.com> De T Taylor Rapporteur for Q.D/16 <taylor(a)nortelnetworks.com> M Buckley Rapporteur for Q.F/16 <mikebuckley(a)44comms.com> M Euchner Rapporteur for Q.G/16 <Martin.Euchner(a)icn.siemens.de> P Jones Rapporteur for Q.2/16 <paulej(a)packetizer.com> G Freundlich Rapporteur for Q.3/16 <ggf(a)avaya.com> S Okubo Rapporteur for Q.4/16 <okubo(a)giti.waseda.ac.jp> P Reddy Rapporteur for Q.5/16 <paul.k.reddy(a)intel.com> ------------------------------------------------------------ Subject: Notice of Joint Rapporteur Meeting in Santa Barbara Date: 6 August 2001 ------------------------------------------------------------ Dear experts of Questions D, F, G, 2-5/16, The subject meeting of ITU-T SG16 experts will be held in Santa Barbara, USA at the kind invitation of Cisco Systems. Please note that Q.11/16 will meet concurrently at the same place and has joint session(s) with Q.2/16 and Q.3/16. Please note that Q.1/16 will meet concurrently and has joint session(s) with Q.D, F, G, 1-5. 1. Date ^^^^^^^ 24 (Monday) - 28 (Friday) September 2001 Meeting will start at 9:00 AM on the first day closing around 18:00 on the final day 2. Venue ^^^^^^^^ Fess Parker's Doubletree Resort 633 East Cabrillo Boulevard Santa Barbara, CA 93103 USA Tel: +1 877 893 0892 (Free Call in US and Canada) Tel: +1 805 564 4333 Fax: +1 805 962 1814 http://www.fpdtr.com/ 3. Topics (tentative) ^^^^^^^^^^^^^^^^^^^^^ 1) Review of the relevant group activities 2) Q.2/16 Multimedia over packet networks using H.323 systems - Progress work on: * Annex Gv2/H.225.0 * H.323 Annex N (QoS) * H.323 Annex O (I-net protocols) * H.323 Annex P "Modem Relay" * H.450.x new recommendations * H.GEF.1 (GEF Framework) * H.GEF.3 (Presence) * H.GEF.4 (Emergency Services) * H.225.0v5 * H.323v5 3) Q.3/16 Infrastructure and interoperability for Multimedia over packet networks - Progress work on: * H.245 V9 (if needed) * H.248 V2 * New H.248 packages * MoIP (modem over IP) as it relates to Q.3 4) Q.4/16 Video and data conferencing using Internet-supported services - Describe service scenarios - Describe technical requirements - Elaborate the workplan 5) Q.5/16 Mobility for Multimedia Systems and Services - Progress work on: * H.MMS.0 (General MM) * H.MMS.1 (H.323 Mobility) * H.MMS.2 (Global MM Interop) * H.MMS.3 (Presence) * H.MMS.4 (IM and Mobility Interoperability) 6) Q.D/16 Interoperability of Multimedia Systems and Services - Establishing principles for interoperability of multimedia signalling systems 7) Q.F/16 Quality of Service and End-to-end Performance in Multimedia Systems - Progress work on: * H.qos.arch (QoS Architecture) * H.mmclass (Multimedia QoS Service classification) * H.mmcp (Call processing performance in Multimedia Systems) * H.priority (Techniques and procedures for controlling service priority) * H.323 Annex N (QoS signalling and control in H.323 systems) * H.trans.control (QoS signalling to Transport Domains) * H.qos.m (QoS management issues) * H.policy (QoS Policy Server Signalling) * H.resilience (Error Resilience for media codecs) 8) Q.G/16 - Progress work on: * H.235 V3 * H.235 Annex F (Hybrid Security Profile) * H.235 Annex G (H.MMS.1 security) * work on emergency security services 8) Interaction with other groups 9) Future work plan 4. Documents ^^^^^^^^^^^^ /// Registration of the document: by 23:59 UTC, 14 September /// /// Distribution of the document: by 23:59 UTC, 17 September /// /// Use the ftp site (or e-mail reflector) for distribution /// 1) When you are going to submit a document, please notify Glen Freundlich <ggf(a)avaya.com>, meeting document manager of this meeting, as soon as possible, by 23:59 UTC, Friday 14 September at the latest. Document number AVD-nnnn will be allocated. Early indication of your submission plan is welcome and encouraged. Note - Prefix "AVD" comes from Audio, Video and Data. 2) You are advised to include a header as follows: ------------------------------------------------------------------ | | | ITU Telecommunication Standardization Sector Document AVD-{nnnn}| | Study Group 16 {Version m if relevant}| | Q.D, F, G, 2-5/16 Rapporteur Meeting {Date}| | Santa Barbara, 24-28 September 2001 | | | | SOURCE*: { } | | TITLE : { } | | PURPOSE: {Proposal, Discussion, Information, Report, etc.} | | | | _________________________ | | | | | | | | *Contact: Name, e-mail | ------------------------------------------------------------------ 3) All the contributors are requested to distribute their documents as early as possible, at least 7 calendar days in advance of the meeting (23:59 UTC, Monday 17 September or before) by posting them at either of the following: - PictureTel ftp site (please advise Mr. Freundlich of your posting) Site: standard.pictel.com/avc-site Login name: anonymous Directory: Incoming - Intel e-mail reflector e-mail address: itu-sg16(a)mailbag.intel.com Please avoid the use of reflector when your document is voluminous. 4) Input documents can be retrieved from /0109_San directory of the ftp site. 5) The document distribution / presentation at the meeting will be all electronic. Participants must bring along their laptop and Ethernet card. It is recommended that participants bring an Ethernet cable at least 7 meters in length. 5. Logistic information ^^^^^^^^^^^^^^^^^^^^^^^ The meeting will be hosted by Cisco Systems and held at the Fess Parker's Doubletree Resort hotel in Santa Barbara, California, USA. The best way to get to Santa Barbara is to fly into the Santa Barbara Airport (SBA). There are convenient flights available to this airport from Los Angeles, San Francisco, San Jose, Denver and Phoenix. The hotel is located 10 min south of the airport, using Highway 101. Car rentals and taxis are available at the Santa Barbara Airport. Please see http://www.fpdtr.com/maps.html for detailed directions to the hotel. Drive time from Los Angeles is 2 hours. 6. Registration ^^^^^^^^^^^^^^^ To register your meeting attendance, please send e-mail to Paul E. Jones <paulej(a)packetizer.com> specifying the name of the person(s) attending and the company name. Please also make your hotel reservations directly with the hotel. 7. Hotel Room Reservation ^^^^^^^^^^^^^^^^^^^^^^^^^ When making reservations, mention that you are attending the meeting hosted by Cisco Systems to get the special discounted room rate. The room rate is set at $155/night (including the weekend nights). In order to confirm this discounted rate and availability please book your reservation before August 31, 2001. After August 31, 2001, rooms and rates will be based on availability. We are looking forward to meeting with you in Santa Barbara. Sincerely yours, Tom TAYLOR Mike BUCKLEY Martin EUCHNER Paul JONES (meeting manager of this meeting) Glen FREUNDLICH Sakae OKUBO Paul REDDY ---------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

H.235 -rejectReason
by Silvy Samuel 06 Aug '01

06 Aug '01

Hi, In case of an unsecured endpoint sending a RAS/H.225 message to GK , what should the reject Reason be? Is it correct if RAS messages from unsecured EPs also are rejected by GK with securityDenial, and H.225 messages with releaseComplete with reason security Denied)? Thanks and Regards, Silvy. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Question about the reuse of transport addresses in replacementFor
by Lyons, Terry 02 Aug '01

02 Aug '01

Is this restriction on the use of replacementFor generally honored? Is there any mention of the topic in H.323 or H.225.0? Is the Appendix making a normative statement? APPENDIX V / H.245 The replacementFor procedure ... Note also that in H.323 systems, receivers are required to re-use the existing media and media control transport addresses. The switch over point to the new logical channel is marked by the RTP header. - 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

1 0

[Megaco] Purpose Of Annex C
by Tom-PT Taylor 01 Aug '01

01 Aug '01

Before last month's SG 16 meeting I raised the point of the proper use of Annex C values. Today I discovered that we already have it covered. See section 7.2.10, which states unequivocally that Annex C is for the Local and Remote descriptors. One of the open issues on the list is whether we can deprecate the Modem descriptor. If we do so, the corresponding Annex C property can remain there and I would remove mention of it from my SDP-TDM draft. There were some other Annex C properties that I had proposed to remove because they belonged in LocalControl. This wasn't done at the last SG 16 meeting because orderly procedure required list agreement plus alternative packages to put them in. The specific items I would focus on are Mode (tag 1002 in C.1), DialledN (tag 901F in C.9) and DiallingN (tag 9020 in C.9). Mode is in LocalControl already, and the other two are covered by the NAS package. I had also mentioned Gain (tag 100C in C.1) and Jitterbuff (tag 100D in C.1) previously. At this point I'd say Gain might suitably be specified by direction. Jitterbuff should be moved into RTP. Tom Taylor taylor(a)nortelnetworks.com Ph. +1 613 736 0961 (ESN 396 1490) _______________________________________________ Megaco mailing list Megaco(a)ietf.org http://www.ietf.org/mailman/listinfo/megaco

2 1

[Sipping] VoIP Traversal of Non-upgraded Firewall & NATs @ IETF
by Pete Cordell 01 Aug '01

01 Aug '01

Dear All, I would like to have a meeting at the IETF (informal BOF?) discussing methods for VoIP and Multimedia over IP traversing non-upgraded firewalls and NATs. These methods are intended to supplement the firewall architecture, and not require upgrade to existing firewall/NAT components, or clients (and other infrastructure such as proxies). There is a draft discussing one proposal at: http://www.ietf.org/internet-drafts/draft-davies-fw-nat-traversal-00.txt If others have ideas in this area, then please contact me and we can arrange some sort of agenda. (Although note that I will be out of contact until the Sunday before the IETF - i.e. this Sunday! - so we might have to organise this at the IETF.) I hope the format will be something like: - Overview presentation of method - How this is secure and maintains administrator control - (Repeat for each proposal) - Collect issues that need to be addressed before going to a formal BOF. (The modified agenda involves the final item being changed to 'chaos'!) At this stage I would like to avoid discussion about how this compares to MidCom and other approaches - such as Rosenberg's - as I think it will quickly turn into a blood bath. - We should save that for the formal BOF! I'm hoping to hold the meeting in: The King's Suite/Sandringham 1 on Thursday 17:45 -> 18:45, but I obviously haven't had a chance to check this with the organisers. Therefore, please look out for final details on the noticeboard, and probably the door of the King's Suite. I look forward to seeing you all, Pete. (P.S. Sorry for putting this on the SG16 and TIPHON lists, but I'm well aware that many of you attend the IETF and I wanted to make sure you had the opportunity to come along.) ============================================= Pete Cordell Tech-Know-Ware pete(a)tech-know-ware.com +44 1473 635863 ============================================= _______________________________________________ Sipping mailing list http://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors(a)cs.columbia.edu for questions on current sip Use sip(a)ietf.org for new developments of core SIP

1 0

MoIP Reliable Transport Internet Draft
by Herb Wildfeuer 31 Jul '01

31 Jul '01

The "MoIP Reliable Transport Requirements and Evaluation" contribution that was discussed and modified at the Baltimore TR.30.1 meeting as 10107061R1.doc is now available as an Internet Draft at: ftp://ftp.tiaonline.org/TR-30/TR301/Public/TR-30.1/2001-07_Baltimore/Draft IETF Contribution.txt There have not been any changes to the document other than converting it to the Internet Draft (I-D) format. This document has been approved by the majority of the participants of the TR30.1 committee. Please provide me with your company name and contact information if you would like to be added to the I-D. The goal of this effort is to provide this I-D to the IETF transport group for discussion in an effort to further the work of a new transport protocol for MoIP. Best Regards, - Herb

1 0